This is part of The Pile, a partial archive of some open source mailing lists and newsgroups.
Subject: Re: What else did RH6.1 install forget....
From: Vidiot <brown@mrvideo.vidiot.com>
Date: Sat, 4 Mar 2000 19:33:09 -0600 (CST)
>login as root
>/usr/sbin/sndconfig
>RH 6.0 I believe by default /usr/sbin was in your path ..6.1 it is not
>do a 'env' to show your environment and you'll notice it's not there.
>maybe you just couldn't locate sndconfig
>next time try 'locate sndconfig' or whatever program your looking for.
In my particular case, zroot has /usr/sbin as part of the path, as it is
my restored zsh root user.
The sndconfig program fixed the oversight.
It wasn't that I couldn't locate sndconfig, I totally forgot about it, since
6.0 handled that correctly and did a config/search for a sound card, while
6.1 did not. And it was the custom install that I ultimately did.
===
Subject: Re: What else did RH6.1 install forget....
From: Vidiot <brown@mrvideo.vidiot.com>
Date: Sun, 5 Mar 2000 08:21:54 -0600 (CST)
>In this case he just had to run sndconfig, as you've always had to do.
>Tom.
Here's one for ya. It seems that alot of people missed this one. I didn't
know about it as it appears to be new in 6.1. It is a program called kudzu.
No, I didn't discover it on my own, it was pointed out to me.
In any event, according to the man page:
kudzu detects and configures new and/or changed hardware
on a system. When started, kudzu detects the current
hardware, and checks it against a database stored in
/etc/sysconfig/hwconf, if one exists. It then determines
if any hardware has been added or removed from the system.
If so, it gives the users the opportunity to configure any
added hardware, and unconfigure any removed hardware. It
then updates the database in /etc/sysconfig/hwconf.
So, when is it started. I went looking. Yep, found it in /etc/rc.d/init.d.
Starts at run levels 3, 4 or 5. I looked at the script and saw the
following text:
case "$1" in
start)
echo -n "Checking for new hardware"
I remembered seeing the "Checking for new hardware" line in the boot stuff.
Something that I hadn't seen before. The fact that it didn't find any new
hardware was not unexpected, as I hadn't put in any new hardware since
installing 6.1.
But... after discovering that the PCI sound card was not installed and after
being informed about kudzu, it dawned on me that the new program that was
supposed to find new hardware, did not find the "new" hardware.
To prove that it is a PCI sound card, this is what /etc/sysconfig/hwconf
has in it:
class: AUDIO
bus: PCI
detached: 0
driver: es1371
desc: "Ensoniq|ES1371 [AudioPCI-97]"
vendorId: 1274
deviceId: 1371
If I understand all of the above correctly, I should never have had a
sound card problem. The very first boot should have detected the card
and installed it by asking me about it, which it never has. In theory,
I should never have had to run sndconfig.
Ah, but wait. There is more to this story. Consider the following:
ls -la /etc/sysconfig/hwconf
-rw-r--r-- 1 root root 1382 Feb 29 07:34 /etc/sysconfig/hwconf
The sndconfig program never even touched the hwconf file. It already had
the info for the sound card in there, after I had done the install and days
before I ran sndconfig. The date is equal to when the partition table
for /dev/hdb was fixed and brought on line.
This is the order of entries in hwconf:
-
class: OTHER
desc: "Acer Laboratories Inc. [ALi]|M1531 [Aladdin IV]"
-
class: OTHER
desc: "Acer Laboratories Inc. [ALi]|M1533 [Aladdin IV]"
-
class: OTHER
desc: "Acer Laboratories Inc. [ALi]|M5229"
-
class: NETWORK
desc: "Realtek|8029"
-
class: SCSI
desc: "Adaptec|AHA-7850"
-
class: VIDEO
desc: "NVidia / SGS Thomson|Riva128"
-
class: AUDIO
desc: "Ensoniq|ES1371 [AudioPCI-97]"
-
class: MOUSE
desc: "Generic PS/2 Mouse"
-
class: CDROM
desc: "MATSHITA CR-585"
-
class: FLOPPY
desc: "IOMEGA ZIP 100 ATAPI"
-
class: HD
desc: "Maxtor 85400D5"
-
class: HD
desc: "Maxtor 92049U6"
As can be seen, the audio card was found and listed before other physical
items, yet it wasn't "enabled". Would explain why kudzu didn't find it
as new hardware. It was already there.
Is there a hole in the initial configuration procedure somewhere? Why would
the system find the sound card, yet not "turn it on?"
Is this a bug that needs to be fixed in 6.2? I see nothing in the updates
& errata area of the web site that discusses the above. One of two things
needs to happen during the install:
1) Find the sound card and finish installing the modules so that the
card will work. Don't do half the job by listing it in the
hwconf file.
2) Don't look for a sound card at all during the install. That way
the hwconf file should not get an entry and when kudzu is started
for the first time, it will find the sound card and query the user
for what to do next.
===