Intel 845e and RedHat 7.2 problems

denali

Golden Member
Oct 10, 1999
1,122
0
0
At work we just got a couple of Dell Dimension 4500's these have mainboards that use the Intel 845e chipset. I'm having problems getting
the USB and sound to work. I have updated the system to the latest files
using up2date. Any help would be appreciated.

When I run sndconfig I get

Model Intel Corporation | unknown device 8086:24c5

The USB fails at boot below is the messages from boot.log

Aug 1 12:42:00 hasp151 rc.sysinit: Mounting USB filesystem: succeeded
Aug 1 12:42:00 hasp151 rc.sysinit: Initializing USB controller (usb-uhci): succeeded
Aug 1 12:42:00 hasp151 modprobe: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters
Aug 1 12:42:00 hasp151 modprobe: /lib/modules/2.4.9-34/kernel/drivers/usb/usb-ohci.o: init_module: No such device
Aug 1 12:42:00 hasp151 modprobe: /lib/modules/2.4.9-34/kernel/drivers/usb/usb-ohci.o: insmod /lib/modules/2.4.9-34/kernel/drivers/usb/usb-ohci.o failed
Aug 1 12:42:00 hasp151 modprobe: /lib/modules/2.4.9-34/kernel/drivers/usb/usb-ohci.o: insmod usb-ohci failed
Aug 1 12:42:00 hasp151 rc.sysinit: Initializing USB controller (usb-ohci): failed
 

BlackOmen

Senior member
Aug 23, 2001
526
0
0
If you look at the 2nd line, you have Initializing USB controller (usb-uhci): succeeded. The bottom line also states Initializing USB controller (usb-ohci): failed.

Intel motherboards use a UHCI usb controller, for which the driver loaded correctly. You can ignore the lines deailing with the OHCI driver (which are used by AMD, SiS and ALI on their cipsets). If you want to get rid of the error messages, edit /etc/modules (or the RedHat equivalent) and remove a line that mentions usb-ohci. Since your usb controller is working, you just need to load drivers for your devices.

As far as sound, there is a driver for the intel chipsets, however I don't know what it is called. Redhat probably build it for you and supplied it in
/lib/modules/(kernel version)/kernel/drivers/sound

If you can find it in there, loading it should only require modprobe driver. Remove any .o extensions when you load the driver.