[Fwd: Re: Hardware detection question/problem]
I also lost use of my ethernet (Intel 82801bd PRO 100 integrated) on an ibm netvista after update and reboot. I tried to load discover2 but was unable to get it to install. After reading Dave's note I tried discover1 and the network became available again.
Is there a way to "go back" to the last known configuration when finding an update broke something? In mycase I lost the network and had pains getting the system back to where it was prior.
>
> From: Dave Marples <dave@marples.net>
> Date: 2004/04/29 Thu PM 03:06:50 EDT
> To: debian-testing@lists.debian.org
> Subject: Re: Hardware detection question/problem
>
> The latest discover seems to be called 'discover', and it won't
> auto-update due to dependencies, so [apt-get install discover] is your
> friend. The current version in sarge (for me at least) fixes most of
> the problems I had with NICs etc....only outstanding issue was that
> alsa wouldn't load. That was due to discover being _too_ good and
> loading the i810 module when I really wanted the one from alsa....a
> suitable line in /etc/discover.conf to ignore the sound module fixed
> that.
>
> Everything's peachy again...
>
> DAVE
>
> On 29 Apr 2004, at 05:03, Anders Ellenshøj Andersen wrote:
>
> > On Thursday 29 April 2004 05:37, Joe Spears wrote:
> >> The hardware detection problem appears to be that the "discover"
> >> package
> >> in Sarge was renamed to "discover1".
> >
> > Well I don't know what crazy stuff is going on in sarge these days,
> > but in sid
> > we have discover, and discover1.
> > discover is the latest version, based on libdiscover2.
> > discover1 is the old version, based on the original libdiscover
> > library.
> >
> > Anders
> >
> > --
> > This email was generated using KMail from KDE 3.2.2 on Debian GNU/Linux
> >
> >
> > --
> > To UNSUBSCRIBE, email to debian-testing-REQUEST@lists.debian.org
> > with a subject of "unsubscribe". Trouble? Contact
> > listmaster@lists.debian.org
> >
>
>
Reply to: