[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#259252: marked as done (Soyo SY-K7VME + AMD)



Your message dated Tue, 13 Jul 2004 22:34:14 +0200
with message-id <200407132234.14976.aragorn@tiscali.nl>
and subject line Bug#259252: Soyo SY-K7VME + AMD
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 13 Jul 2004 17:28:14 +0000
>From bgood97@yahoo.com Tue Jul 13 10:28:14 2004
Return-path: <bgood97@yahoo.com>
Received: from web40702.mail.yahoo.com [66.218.78.159] 
	by spohr.debian.org with smtp (Exim 3.35 1 (Debian))
	id 1BkR4g-0005XA-00; Tue, 13 Jul 2004 10:28:14 -0700
Message-ID: <[🔎] 20040713172743.85979.qmail@web40702.mail.yahoo.com>
Received: from [24.225.76.128] by web40702.mail.yahoo.com via HTTP; Tue, 13 Jul 2004 10:27:43 PDT
Date: Tue, 13 Jul 2004 10:27:43 -0700 (PDT)
From: Bill Gooding <bgood97@yahoo.com>
Subject: Soyo SY-K7VME + AMD
To: submit@bugs.debian.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Delivered-To: submit@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-5.8 required=4.0 tests=BAYES_01,FROM_ENDS_IN_NUMS,
	HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 



Package: installation-reports

Debian-installer-version: 7-8-2004 Daily build image
of sarge-i386-netinst.iso 
uname -a: Linux elisa 2.6.6-1-386 #1 Wed May 12
13:19:06 EST 2004 i686 GNU/Linux

Date: 7-8-2004
Method: Used the cd image to install, booted initially
from the cd, no
proxy, connected to the internet through router/DHCP
server

Machine: Custom built, Motherboard = Soyo SY-K7VME
Processor:  AMD Athlon XP 2500+
Memory: 512 M
Root Device: IDE hard drive, Western Digital
Root Size/partition table: 

Filesystem           1K-blocks      Used Available
Use% Mounted on
/dev/hda1               366015    101293    245194 
30% /
tmpfs                   242476         0    242476  
0% /dev/shm
/dev/hda8             14514496   3930228   9846968 
29% /home
/dev/hda9              1921872      8239   1811096  
1% /home2
/dev/hda7              1830261      9286   1723327  
1% /tmp
/dev/hda5             14418320   1867896  11818016 
14% /usr
/dev/hda6              2883672    413864   2323324 
16% /var

Output of lspci:

0000:00:00.0 Host bridge: VIA Technologies, Inc.
VT8378 [KM400] Chipset Host Bridge
0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8237
PCI Bridge
0000:00:10.0 USB Controller: VIA Technologies, Inc.
VT82xxxxx UHCI USB 1.1 Controller (rev 80)
0000:00:10.1 USB Controller: VIA Technologies, Inc.
VT82xxxxx UHCI USB 1.1 Controller (rev 80)
0000:00:10.2 USB Controller: VIA Technologies, Inc.
VT82xxxxx UHCI USB 1.1 Controller (rev 80)
0000:00:10.3 USB Controller: VIA Technologies, Inc.
USB 2.0 (rev 82)
0000:00:11.0 ISA bridge: VIA Technologies, Inc. VT8235
ISA Bridge
0000:00:11.1 IDE interface: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master
IDE (rev 06)
0000:00:11.5 Multimedia audio controller: VIA
Technologies, Inc. VT8233/A/8235/8237 AC97 Audio
Controller (rev 50)
0000:00:12.0 Ethernet controller: VIA Technologies,
Inc. VT6102 [Rhine-II] (rev 74)
0000:01:00.0 VGA compatible controller: VIA
Technologies, Inc. VT8378 [S3 UniChrome] Integrated
Video (rev 01)


Base System Installation Checklist:

Initial boot worked:    [O ]
Configure network HW:   [O ]
Config network:         [O ]
Detect CD:              [O ]
Load installer modules: [O ]
Detect hard drives:     [O ]
Partition hard drives:  [O ]
Create file systems:    [O ]
Mount partitions:       [O ]
Install base system:    [O ]
Install boot loader:    [O ]
Reboot:                 [O ]
[O] = OK, [E] = Error (please elaborate below), [ ] =
didn't try it

Comments/Problems:

I originally downloaded the CD corresponding to the
beta4 version.
Unfortunately this version could not get its address
from DHCP.  The
time expired before the process could complete.  I had
a CD for the
woody install process which did properly work with
DHCP.  This problem
has been corrected since the daily build CD did get
its address
through DHCP.  In the installation process, I used the
daily build cd
for 7-8-2004 and expert26 option at the boot prompt.

The other two problems I had were with the built-in
video card and the
soundcard.  I got the video card working properly with
some
adjustments.  The soundcard is not working yet, but I
am really not
that concerned about it since I do not really use it. 
I do not
consider these things to be bugs in the installer
since I cannot
elimiate the possibility that I did something wrong in
the setup or
that the motherboard may be a little new and not yet
perfectly
supported.

On the built-in video card, I used the auto-detect
capabilities
whenever possible.  Overall, these functions did a
very good job.  The
only error in my XF86Config-4 file was the video card
driver.  I
forgot which one was orginally selected (maybe apm?),
but the first
thing I did was change that value to "via".  This only
partially
worked, I could only get the lowest possible
resolution.  After a
little research, I decided to try the "vesa" driver. 
This worked, I
got the resolution up to 1600x1200.  I am not sure why
this worked,
but I do not think it does any harm to my system since
it does work.

On the soundcard, I do not know much because I am not
that motivated
to look at the problem.  I only know that the kernel
appears to load
the drivers, but the soundcard is not available in
/proc/asound/cards.
It may be that some oss drivers are interfering with
some alsa
drivers.  I may try to compile a custom 2.6 kernel
with sound modules
as loadable and use alsa.  But as I said, I did not
really research
this.

On the plus side, the usb support worked very well
although I only
have a usb mouse to test it with.  Also, I orginally
used a PS/2 mouse
and I did not change the XF86Config-4 file when I
changed to the usb
mouse.  Despite that, the system still worked fine and
so I do not see
a reason to change the XF86Config-4 file.

One other suggestion, on the website
http://www.debian.org/devel/debian-installer/ it says
"After using the
Debian-Installer, please send us an installation
report using the
template, so we can track and fix any problems you may
find."  After
following the template link, I noticed that the report
is submitted to
a bug list.  Since I don't consider what I have to be
a bug, I was not
going to report it.  I asked on IRC and they said they
want to collect
all experiences with the installer (which is what I
thought since if I
was creating an installer, I would want all reports
given the
difficulty in testing many configurations).  I suggest
you add an
extra sentence, something like "We also encourage all
successful
installation reports to be sent using this template so
that we can get
as much information as possible on the largest number
of hardware
configurations".  You may get more reports this way.




		
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
http://promotions.yahoo.com/new_mail 

---------------------------------------
Received: (at 259252-done) by bugs.debian.org; 13 Jul 2004 20:34:46 +0000
>From aragorn@tiscali.nl Tue Jul 13 13:34:46 2004
Return-path: <aragorn@tiscali.nl>
Received: from (elrond.fjphome.nl) [195.240.184.66] 
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1BkTzC-0007ZN-00; Tue, 13 Jul 2004 13:34:46 -0700
Received: from galadriel.fjphome.nl ([10.19.66.21] ident=fjp)
	by elrond.fjphome.nl with esmtp (Exim 3.35 #1 (Debian))
	id 1BkTyh-00070v-00
	for <259252-done@bugs.debian.org>; Tue, 13 Jul 2004 22:34:15 +0200
From: Frans Pop <aragorn@tiscali.nl>
To: 259252-done@bugs.debian.org
Subject: Re: Bug#259252: Soyo SY-K7VME + AMD
Date: Tue, 13 Jul 2004 22:34:14 +0200
User-Agent: KMail/1.6
References: <[🔎] 20040713172743.85979.qmail@web40702.mail.yahoo.com>
In-Reply-To: <[🔎] 20040713172743.85979.qmail@web40702.mail.yahoo.com>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <200407132234.14976.aragorn@tiscali.nl>
Delivered-To: 259252-done@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
	autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 

Thank you for submitting the report.

On Tuesday 13 July 2004 19:27, Bill Gooding wrote:
> On the soundcard, I do not know much because I am not
> that motivated
> to look at the problem.  I only know that the kernel
> appears to load
> the drivers, but the soundcard is not available in
> /proc/asound/cards.
> It may be that some oss drivers are interfering with
> some alsa drivers.

This could well be the cause of your problem. The installer (and discover and 
hotplug) are mostly geared towards 2.4. Some module tuning is necessary when 
you run 2.6.
An alternative to building your own kernel is to exclude modules in 
discover.conf and hotplug's blacklist.

> One other suggestion, on the website
> http://www.debian.org/devel/debian-installer/
> [...]
> You may get more reports this way. 

I have forwarded your suggestion. Thanks.

Closing this report as there are no installer related issues.



Reply to: