Pegasus driver fails to initialize when not a module

Pegasus driver fails to initialize when not a module

Post by root » Thu, 16 Aug 2001 14:30:05



Chipsets: VIA KT133, VIA MVP4
Adapter: DLink DSB-650 (pegasus version, NOT the klsi one).
Drivers Used: usb-uhci -or- uhci, pegasus
Kernel Versions: 2.4.3, 2.4.6, 2.4.8, 2.4.8-ac2 (at least as far as I've tested).

Problem:
I've got a DLink DSB-650 USB net adapter based on the pegasus chipset. It
works fine when the driver is compiled as a module, but when the driver is
linked into the kernel, it fails to detect the adapter. The USB layer
initializes ok, and my USB keyboard and mouse are detected (although
doing this on a system with a PS/2 or AT kb/mouse changes nothing), but
the NIC is not, even though the pegasus driver prints out  it's loading
string and copyright message.

--ex--
pegasus.c: v0.4.19 2001/06/07 (C) 1999-2001:ADMtek AN986 Pegasus USB
Ethernet driver
usb.c: registered new driver pegasus
--ex--

After this, the kernel loads the net drivers, and (in my case) horks
because there is no eth0 to autoconfigure and mount a nfsroot filesystem
from.

However, on the same system with the same BIOS settings, and the only
change being that pagasus.c is compiled as a module (and not into the
kernel) it works perfectly, and I can use the USB adapter without trouble.

 This happens under either UHCI driver, and regardless of what USB options
are set. With debug on, I get a 'set_configuration_failed()' message from
pegasus under 'normal' uhci, and no notable error message under uhci-je.

My best guess is that either (a) something's wrong with the driver that
makes it not work when linked in, or (b) the driver is working, but is
dong it's initialization in the background, and is not
finishing in time to have eth0 ready for autoconfig/nfsroot (i.e. eth0
would appear some time after 'init' kicked off.

Any suggestions?

- Dave Acklam

P.S. Yes, I read the lkml faq, the kernel docs, the source for
pegasus.c/pegasus.h, et al... Please don't shoot the first-time poster...

If you need the kernel config, I'll be happy to e-mail it to you

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

1. Pegasus driver fails to initialize when not a module (re-post)

--> I don't know if this message made it to the list (I had some e-mail
--> trouble), so I'm trying again.

Chipsets: VIA KT133, VIA MVP4
Adapter: DLink DSB-650 (pegasus version, NOT the klsi one).
Drivers Used: usb-uhci -or- uhci, pegasus
Kernel Versions: 2.4.3, 2.4.6, 2.4.8, 2.4.8-ac2 (at least as far as I've tested).

Problem:
I've got a DLink DSB-650 USB net adapter based on the pegasus chipset. It
works fine when the driver is compiled as a module, but when the driver is
linked into the kernel, it fails to detect the adapter. The USB layer
initializes ok, and my USB keyboard and mouse are detected (although
doing this on a system with a PS/2 or AT kb/mouse changes nothing), but
the NIC is not, even though the pegasus driver prints out  it's loading
string and copyright message.

--ex--
pegasus.c: v0.4.19 2001/06/07 (C) 1999-2001:ADMtek AN986 Pegasus USB
Ethernet driver
usb.c: registered new driver pegasus
--ex--

After this, the kernel loads the net drivers, and (in my case) horks
because there is no eth0 to autoconfigure and mount a nfsroot filesystem
from.

However, on the same system with the same BIOS settings, and the only
change being that pagasus.c is compiled as a module (and not into the
kernel) it works perfectly, and I can use the USB adapter without trouble.

 This happens under either UHCI driver, and regardless of what USB options
are set. With debug on, I get a 'set_configuration_failed()' message from
pegasus under 'normal' uhci, and no notable error message under uhci-je.

My best guess is that either (a) something's wrong with the driver that
makes it not work when linked in, or (b) the driver is working, but is
dong it's initialization in the background, and is not
finishing in time to have eth0 ready for autoconfig/nfsroot (i.e. eth0
would appear some time after 'init' kicked off.

Any suggestions?

- Dave Acklam

P.S. Yes, I read the lkml faq, the kernel docs, the source for
pegasus.c/pegasus.h, et al... Please don't shoot the first-time poster...

If you need the kernel config, I'll be happy to e-mail it to you

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

2. How do I make a shared object (.so) file?

3. PB G3 eth0 fails to initialize (module not loading?)...

4. PWD/CWD in ksh prompt howto?

5. Failed to initialize the NVdriver kernel module...

6. LAN adapter configuration problems

7. Failed to load module "ati" (module does not exist,0)

8. policy editor questions...

9. e100 driver fails to initialize NIC on 2.5.44

10. 2.4.18-rc1: Tulip driver fails to initialize 21140 card

11. e100 driver fails to initialize the hardware after ker nel bootup through kexec

12. e100 driver fails to initialize the hardware after kernel bootup through kexec

13. Compiling pegasus module(latest) on COL 2.3 @Home USB