Chuck Bearden wrote: > On Wed, Apr 28, 2004 at 08:54:00PM -0800, Tim Jordan wrote: >> Try apt-get install discover1 >> >> This fixed removed the old discover package then installed discover1, >> searched and loaded all necessary modules. > > So is discover1 to be preferred over discover? discover is > supposedly based on libdiscover2, while discover1 is based on > libdiscover1. I have discover 2.0.4-3, and my sound and network > hardware are not being detected automatically. It looks to me as if > I need to do what Jim Seymour did and manually add hw info back into > pci.lst. >
It looks like there are a few open bugs with discover in testing, but specific hardware problems need to be added to the bugtracker so they can be fixed instead of worked around. http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=discover > Chuck > >> TJ >> On Wed, 2004-04-14 at 01:07, Jim Seymour wrote: >> >>> The last updates to Sarge I applied this week seem to have >>> damaged discover. In order to get networking up now I have to >>> modprobe the ethernet driver, then ifconfig eth0 up and then >>> restart networking. Sound no longer works either. I do not remember >>> if discover was updated this week. Is anyone else having a problem >>> with some hardware no longer being detected and modules loaded? Is >>> there a known cure? Also KDE disappeared from the login choices >>> when Sarge boots. >>> >>> Thanks, >>> >>> Jim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
