On Thu, Apr 01, 2004 at 03:50:50PM -0800, Sean O'Dell wrote: > On Thursday 01 April 2004 03:08 pm, Alan Chandler wrote: > > On Thursday 01 April 2004 23:34, Sean O'Dell wrote: > > > Solved this, pretty much. Basically, when I upgraded, two things > > > happened that I didn't know about. One, the kernel driver for my network > > > card stopped getting loaded; something happened during dist-upgrade or > > > upgrade that caused it to be removed from the list of modules to load. I > > > compiled the driver static in the kernel and the network was able to load > > > after that. Also, kdm apparently was un-installed by something during > > > dist-upgrade or upgrade. So, once I got the network back up, removing > > > and re-installing various things got me back in working order. > > > > It would probably be better for you to use a standard debian kernel and add > > the name of the ethernet driver into /etc/modules > > Why? Is Debian a pain to use with custom-compiled kernels? No, not at all. I don't think I've ever used a standard Debian kernel, except immediately after installation. The only disadvantage to this seems to be the need to recompile whenever I get some new hardware; with the Debian kernel chances are the module has already been built. You can get the best of both worlds by applying the Debian patches (AIUI mainly security-related) to kernel.org source and building a custom kernel from that. -- Pigeon Be kind to pigeons Get my GPG key here: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x21C61F7F
Attachment:
pgpoJtq9fhoNi.pgp
Description: PGP signature