I fought with a machine last week that had a broadcom nic. I found that I could not get it to work with a 2.2 kernel without recompiling the kernel, which I did, just long enough to hit the network so I could upgrade to a 2.4 kernel. It's been a week, so I'm not sure I remember correctly, but I think it worked out of the box with the 2.4 kernel.There is no networking. I need to build a module for my nic which doesn't have a .deb package. I have the source but need the kernel source which wasn't installed. I discovered that unilike what many people told me I don't need to rebuild the kernel.
I also need to figure out why X isn't working.
There is also no mouse detection.
Whenever I boot it it tries to start X. Several error messages. This is a hassle.
Before I do anything else I'd like to stop this. I know it has something to to with something called "runlevel" What do I put in what file to change this.
I would suggest you break these issues out into separate email threads, and give each thread a meaninful subject line, like "broadcom nic fails on 2.2 kernel" or "X tries to start on boot but can't" or "mouse not detected in X" or "mouse not detected in console" or "mouse not detected in console or X".
No, in Debian, the starting up of X is not dependent on the runlevel. That's the way some other distros, like RH and Mandrake I believe, do it. But Debian does not. Instead, you'll need to uninstall or otherwise deactivate the login manager, which is most likely xdm, wdm, kdm, or gdm. The quickest/easiest fix is probably to get to a console and run "apt-get remove xdm" and then repeat the command, replacing xdm with wdm, kdm, and gdm. Later, when you've gotten X working, you can reinstall your preferred login manager with a command like "apt-get install gdm".
-- Kent
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
