Thread: [Ndiswrapper-general] SMC 2802W V2
Status: Beta
Brought to you by:
pgiri
From: Bjoern B. <de...@do...> - 2004-07-03 13:39:32
|
Hi everybody ! I'm really near to give it all up, so you're my last hope. Since about a week, i'm trying to get a SMC 2802W V2 PCI card to work. I tried ndiswrapper version from 0.6 up to the newest cvs version, but there was no success ever. Every time I try "loadndisdriver 2802w" after inserting the modules, the whole system just freezes. Even the network is down, i can't reach the system from anywhere. I've already tried the kernels 2.6.6 and 2.6.7 (acpi enabled) and the smc driver from the cd and from the list with the supported cards. Also i changed the pci slot, the card is located in. This is what "lspci -n" tells me: 0000:00:0a.0 Class 0280: 1260:3890 (rev 01) Any suggestions what i could do ? Tell me if you need further information about my kernel, system or anything else. |
From: Bjoern B. <de...@do...> - 2004-07-03 14:54:59
|
> What distro are you using? I'm using gentoo linux. > Do you have wireless enabled in your kernel? roger > After insmoding ndiswrapper, do you get anything in your syslog? And > _why_ are you using loadndisdriver at all? You should never call it > manually, it's done withing the module it self. Here is what i do: # ndiswrapper -i /usr/lib/hotplug/drivers/2802W.inf Installing 2802w Forcing parameter EnableRadio|0 to EnableRadio|1 # ndiswrapper -l Installed ndis drivers: 2802w hardware present When I now try to "modprobe ndiswrapper" with version the newest cvs version, the system freezes. |
From: Rainer K. <ke...@ra...> - 2004-07-03 18:03:23
|
Do you have another card that shares it's interrupts with the SMC? Did you try compiling with DEBUG and debug messages printed to the console? > -----Original Message----- > From: ndi...@li... > [mailto:ndi...@li...]On Behalf Of > Bjoern Biesenbach > Sent: Saturday, July 03, 2004 4:55 PM > To: ndi...@li... > Subject: Re: [Ndiswrapper-general] SMC 2802W V2 > > > > What distro are you using? > I'm using gentoo linux. > > > Do you have wireless enabled in your kernel? > roger > > > After insmoding ndiswrapper, do you get anything in your syslog? And > > _why_ are you using loadndisdriver at all? You should never call it > > manually, it's done withing the module it self. > > Here is what i do: > # ndiswrapper -i /usr/lib/hotplug/drivers/2802W.inf > Installing 2802w > Forcing parameter EnableRadio|0 to EnableRadio|1 > > # ndiswrapper -l > Installed ndis drivers: > 2802w hardware present > > When I now try to "modprobe ndiswrapper" with version the > newest cvs version, the system freezes. > > > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > digital self defense, top technical experts, no vendor pitches, > unmatched networking opportunities. Visit www.blackhat.com > _______________________________________________ > Ndiswrapper-general mailing list > Ndi...@li... > https://lists.sourceforge.net/lists/listinfo/ndiswrapper-general > |
From: Bjoern B. <de...@do...> - 2004-07-03 18:20:52
|
> Do you have another card that shares it's interrupts with the SMC? No, the card should be alone on interrupt 12, as /proc/interrupts tells me when loading prism54 drivers (which don't work with this card) > Did you try compiling with DEBUG and debug messages printed to the > console? I enabled debug, but i can't see the output in syslog, because the system freezes immediately. Or is there a possibility to dump the messages to console ? |
From: Giridhar P. <gi...@lm...> - 2004-07-03 22:31:41
|
You shouldn't be using loadndisdriver manually. You should just load ndiswrapper module and if your installation is correct, it will load the windows modules automatically. I was told 0.7 works fine with this chipset (0.8 works too, but without WEP). Neither of them should crash the kernel. If it is crashing, then, as FAQ says, you should enable DEBUG and submit system log. -- Giri |
From: Bjoern B. <de...@do...> - 2004-07-03 23:29:59
|
> I was told 0.7 works fine with this chipset (0.8 works too, but > without WEP). Neither of them should crash the kernel. If it is > crashing, then, as FAQ says, you should enable DEBUG and submit system > log. That's the big problem, the system doesn't log anything, because it freezes immediately. |