I've found that mine isn't blacklisted.  It just doesn't like my Viking modem.

On Thursday 04 October 2001 18:17, you wrote:
> Bob, with the following question to Mandrake I got their knowledgebase
> automated answer below -- in essence my HW is 'blacklisted' :-(
> Good/better luck for your problem .................. Horst
>
>  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> USB modul rejects hardware at boot:
>                               Oct 3 14:20:50 horx
> kernel: usb.c: registered new driver usbdevfs
>                               Oct 3 14:20:50 horx
> kernel: usb.c: registered new driver hub
>                               Oct 3 14:20:50 horx
> kernel: usb-ohci.c: 00:07.4 (Advanced Micro Devices
>                               [AMD] AMD-756 [Viper] USB): blacklisted,
> erratum #4
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Look through /var/log/messages and see if you can find where you were
> telling it to load. Look for a "blacklisted" message, basically
>             saying that the USB developers had some sort of problem with
> that particular chipset, so they aborted running it. One user fixed it by
>             upgrading to the kernel version on Cooker. I don't normally
> recommend a Cooker kernel as worthy until it gets a bit more stable (but
>             since your USB isn't working at all, what do you have to
> lose?). After digging through my logs (quoted below), it does appear you
> have
>             the exact chipset that will not work. Quoted from logs: LM8
> doesn`t start the usb-devices right. In the log-messagges I found the
>             following lines: Jun 10 16:29:18 localhost
> kernel: usb-ohci.c: 00:07.4 (Advanced Micro Devices [AMD] AMD-756 [Viper]
> USB):
>             blacklisted, erratum #4 Jun 10 16:30:00 localhost
> CROND[1640]: (root) CMD ( /sbin/rmmod -as) Jun 10 16:39:37 localhost
> kernel:
>             usb-ohci.c: 00:07.4 (Advanced Micro Devices [AMD] AMD-756
> [Viper] USB): blacklisted, erratum #4 Jun 10 16:39:37 localhost
>
> modprobe: /lib/modules/2.4.3-20mdk/kernel/drivers/usb/usb-ohci.o.gz: Jun
> 10 16:39:37 localhost modprobe: Hint: insmod errors can be
>             caused by incorrect module parameters, including invalid IO or
> IRQ parameters Jun 10 16:39:37 localhost modprobe: init_module: No
>             such device Jun 10 16:39:37 localhost
> modprobe: /lib/modules/2.4.3-20mdk/kernel/drivers/usb/usb-ohci.o.gz: insmod
>             /lib/modules/2.4.3-20mdk/kernel/drivers/usb/usb-ohci.o.gz
> failed Jun 10 16:39:37 localhost modprobe:
>
> /lib/modules/2.4.3-20mdk/kernel/drivers/usb/usb-ohci.o.gz: insmod
> usb-interface failed Jun 10 16:39:37 localhost usb: Loading USB
>             interface failed Jun 10 16:39:37 localhost usb: Mount USB
> filesystem succeeded Jun 10 16:39:37 localhost usb: Loading USB printer
>             succeeded Regards...MandrakeSoft Support Team

-- 
Bob Crandell
Assured Computing
30004 Carol Ave.
Eugene, Ore 97402
[EMAIL PROTECTED]
www.assuredcomp.com
541-914-3985

Reply via email to