no usb or network on 2.6 kernel
 

Hi,

I was using kernel 2.4.22-10mdk that comes w/ mandrake 9.2

I've installed 2.6, I get some strange error messages during boot-up saying some of my /etc/fstab needs to be changed. My cdrom now is no longer called /dev/scd0 but is now called /dev/hdc. Among other differences. Other than that my USB optical mouse doens't work anymore, I've already selected all the USB options on config that I can think of.

Another problem is no network either. I select all network options I can think of in the kernel configuration but I have no network enabled after boot-up.

Is there any particular option that I might be missing? Are other people having this same problem?

On a separate note: I'm using reiserfs. Does that mean that I have to select reiserfs as compiled into kernel insetad of separate module? I had already selected it as a module and it still booted-up successfully, that's why I was wondering.

Thanks for any help

Re: no usb or network on 2.6 kernel
 

well, this should not be a problem, eh? ;) i think i've heard that before, so it should be okay...



i just bought an usb optical mouse (logitech) today, and i got it to work without many problems. here's part of my .config (can't copy and paste right now, so I hope there won't be any typos :)):

this should be all you need. since your mouse was working with 2.4.x you should not need to change your XF86Config(-4)


network is working all right for me... didn't change anything since 2.4.x (using some sis-networkcard)


sounds strange to me, too.... sound like the module is loaded before any harddisk-access ;) ...

i have most of those usb options that u listed as Modules. Do you think that would be a problem?

ok i got usb mouse to work. BUt it's working as psaux mouse when listed on the hardware tab of Mandrake Control Center.

Also, the network is still down, I try to use drakconnect but after the second screen it goes back to the beginning instead of letting me configure my ip address etc.

Also I think that my cd-burner, which was previously listed as /dev/scd0 and now is listed as /dev/hdc is not recognied as a burner as it should. But I'll worry about that later.

Thanks for the help so far. But what could be causing these other problems now? Does drakconnect work for you on 2.6 if u are using Mandrake?

Thanks

btw.: is there a way to pause the scrolling of messages as linux boots up? I tried the pause key but it doesn't seem to work.

The reason why you drive changed from /dev/scd0 to /dev/hdc was that your drive was scsi emulated before and somehow after you compiled your kernel you did add string "hdc=ide-scsi" option to your boot loader which makes it back to unemulated mode. you just need add to /etc/grub.conf if you are using grub.
Don't know about lilo.

Also, for your ethenet card. do you need to compile a driver or something to get your card working? what kind ethernet card do you have?

regarding my cd drive:

Originally I had the following line on my lilo for the 2.6.0 section (as well as for my current 2.4.22 section):
append="quiet failsafe devfs=nomount splash=silent hdc=ide-scsi acpi=ht"

But then I decided to remove that line from my 2.6.0, and only keep it at the 2.4.22-10mdk section since I thought that was more of a Mandrake dependant thing. That line includes the "hdc=ide-scsi" that u said I should remove. But like I said I had already removed it for my 2.6, so shouldn't that have fixed the problem?

as for my network:

I have network working fine for 2.4.22 (that's why I'm sending this post right now). I don't change any network settings when I go to 2.6. If I have something installed as a module that I should have as internally in the kernel, should I modprobe something? My ethernet card is some generic card called admtek. It's recognized by 2.4 fine... Maybe I have to modprobe something when in 2.6.

Thanks

regarding u wanting to see the messages at start up, try (after boot up,from ur shell that is)

Here's how to diagnose a problem like this ...

(1) Can the device be seen? Commands like lspci, lsusb and so on will tell you whether or not the device can be physically seen on the system bus. On 2.6 systems, there's also the /sys directory to look at...

(1a) If you have kudzu, or something like it, then take a look at its output (dmesg), and also its hardware configuration database, probably /etc/sysconfig/hwconf.

(2) Does the device exist in /dev? You pretty-much need to refer to the output from step (1) to see where the device/controller is physically located, to be sure that the dev-entry exists. On 2.6 systems with udev it's a lot easier, because the directory isn't cluttered with thousands of useless entries, and dmesg shows you the messages that it produces when identifying and registering each device.

(2a) If you conclude that the device is not there, device-name issues will be red herrings, because the naming of devices depends upon what udev or the kernel can actually see. The root cause of the problem will be the device drivers in the kernel. I like to put all of the drivers needed to boot the system directly into the kernel, but the "initrd" sequence at boot-time can also load them, from modules.

(3) User-interface device issues, specifically mice and keyboards, depend mostly on the configuration of XWindows/XOrg, assuming that the system can "see" that the devices exist.

(4) Removable-device issues can also suggest a failure of the "hot plugging" mechanism, which responds to notifications that the device has been added or removed. Hot-plugging is also a kernel selectable option, chosen at installation.

(5) If you're not sure what driver is needed, one way to "cheat" is to boot a LiveCD, then do lsmod to see what device-driver kernel modules are loaded... If the device is active, then the driver should be there, and even if it's not the best one for that device, it's obviously one that does work...