3Com Office Connect (3CRWE154G72)

kevkiwi · 01-02-2006, 05:32 PM

Quote:

Originally Posted by Hangdog42

In your first post you say you are using ndiswrapper, yet the card is named eth1 (ndiswrapper tries to create wlan0) and in your dump of /proc/interrupts ndiswrapper isn't in the list.

After much stumbling about I guessed that Ubuntu must be loading the prism54 driver but it wasn't working. A bit more Googling got me the following command:

sudo modprobe -r prism54

This allowed ndiswrapper to take control and suddenly I was on the net via my 3Com wireless card. I haven't quite figured out how to get everything set up so that it boots up with wireless enabled but I'm happy to be able to run Linux on my laptop.

Thanks for all your help.

Cheers,
Kevin

kimothy · 03-01-2006, 10:41 AM

Quote:

Originally Posted by Hangdog42

Sorry, I should have noticed this earlier.......

In your first post you say you are using ndiswrapper, yet the card is named eth1 (ndiswrapper tries to create wlan0) and in your dump of /proc/interrupts ndiswrapper isn't in the list. It should be if you were using it. What this is leading me to believe is that Ubuntu is trying to use some other driver for this card (and probably a native linux one at that) and either the driver is completely wrong or the firmware its using isn't up to the task. Your earlier dmesg output suggests that the firmware loads OK, but then the card has trouble with it.

I would spend some quality time in your system logs and see what module Ubuntu is trying to use with this card. That might give us some clues as to what Ubuntu is trying to do.

Im using slackware now, and I'm still trying to get the card working...

When i type dmesg in the terminal i get this at the end of the output.

Code:

 11
eth1: resetting device...
eth1: uploading firmware...
prism54: request_firmware() failed for 'isl3890'
eth1: could not upload firmware ('isl3890')
eth1: islpci_reset: failure
eth1: removing device
ACPI: PCI interrupt for device 0000:07:00.0 disabled
Unloaded prism54 driver
Loaded prism54 driver, version 1.2
ACPI: PCI Interrupt 0000:07:00.0[A] -> Link [C0C3] -> GSI 11 (level, low) -> IRQ 11
eth1: resetting device...
eth1: uploading firmware...
prism54: request_firmware() failed for 'isl3890'
eth1: could not upload firmware ('isl3890')
eth1: islpci_reset: failure
ndiswrapper: version magic '2.6.15.4 preempt PENTIUM4 gcc-3.4' should be '2.6.15.4 preempt PENTIUM4 gcc-3.3'
eth1: resetting device...
eth1: uploading firmware...
prism54: request_firmware() failed for 'isl3890'
eth1: could not upload firmware ('isl3890')
eth1: islpci_reset: failure
eth1: resetting device...
eth1: uploading firmware...
prism54: request_firmware() failed for 'isl3890'
eth1: could not upload firmware ('isl3890')
eth1: islpci_reset: failure
root@bebe:/home/kim#

If I'm not wrong, I strongly belive that the wifi card is trying to run with the native prism54 drivers that follow the kernel (2.6.15.4, in my case). The output shows that the firmware dosn't load proberly. Any suggestions of what i can do?

Pleace reply

kevkiwi · 03-02-2006, 06:36 AM

Have you tried the command "sudo modprobe -r prism54"?

When I did this my system no longer tried to load the prism54 driver and ndiswrapper was able to control my wireless card.

Cheers,
Kevin

kimothy · 03-02-2006, 06:59 AM

I don't think that's the problem, cause slackware normaly don't load the prism54 drivers.

Take a look at this...

Code:

root@bebe:/home/kim# modprobe -r prism54
root@bebe:/home/kim# modprobe ndiswrapper
FATAL: Error inserting ndiswrapper (/lib/modules/2.6.15.4/misc/ndiswrapper.ko): Invalid module format
root@bebe:/home/kim#

Invalid module? That have to be a problem!

Hangdog42 · 03-02-2006, 07:55 AM

Yeah, that's a problem. I'm guessing something went wrong in the ndiswrapper compile. Give it another go and see if that does the trick.

kimothy · 03-02-2006, 09:02 AM

I got this error during install og ndiswrapper...

Code:

** WARNING: Kernel seems to have 4K size stack option (CONFIG_4KSTACKS) removed; many Windows drivers will need at least 8K size stacks. You should read wiki about 4K size stack issue. Don't complain about crashes until you resolve this.

Something wrong with my kernel maybe?

Hangdog42 · 03-02-2006, 01:42 PM

Maybe yes, and maybe no.....

You need to find the .config file for your kernel, and see if the CONFIG_4KSTACKS parameter is set. If it is Y, then you may have a problem depending on your Windows driver (some drivers do work with 4K stacks). If the parameter is N or not set, then don't worry about this warning. For some reason, ndiswrapper throws this warning even if CONFIG_4KSTACKS is either missing or not set, even though the only time it is a worry is if it is set to Y.

kimothy · 03-02-2006, 02:11 PM

Sorry i can't find the option CONFIG_4KSTACKS. What is it realy? Maybe I'll find it i xconfig, but it's a long list...

Hangdog42 · 03-02-2006, 04:48 PM

Quote:

Originally Posted by kimothy

Sorry i can't find the option CONFIG_4KSTACKS. What is it realy? Maybe I'll find it i xconfig, but it's a long list...

For starters, use grep to help you find it. Also, be sure that you're looking in the kernel .config file. The xconfig file has nothing to do with it.

kimothy · 03-03-2006, 03:19 AM

Code:

root@bebe:/home/kim# grep -F CONFIG_4KSTACKS /usr/src/linux-2.6.15.4/.config
root@bebe:/home/kim# grep -F CONFIG_4KSTACKS /usr/src/linux-2.6.15.4/
root@bebe:/home/kim#

nope, did'nt do the trick. I also searched the .config using kwrite, but could'nt find it that way either...

does'nt "make xconfig" change the settings in the .config file?

Any way, what do you think of it?

Hangdog42 · 03-03-2006, 08:22 AM

Well, as I said, as long as the .config doesn't contain a CONFIG_4KSTACKS=Y, then you should be OK. That warning is almost certainly being triggered by the fact that the CONFIG_4KSTACKS isn't being found by the ndiswrapper config script. In other words, I don't see anything to worry about with teh 4K stacks problem.

kimothy · 03-03-2006, 08:58 AM

I installed ndiswrapper over again (with the 4k stack warning), and i still cant modprobe it...

Code:

root@bebe:/home/kim# ndiswrapper -i /home/kim/Misc/3com/3com/Driver/3C154G72.INF
Installing 3c154g72
Forcing parameter EnableRadio|0 to EnableRadio|1
Forcing parameter EnableRadio|0 to EnableRadio|1
root@bebe:/home/kim# ndiswrapper -l
Installed drivers:
3c154g72                driver installed, hardware present
root@bebe:/home/kim# modprobe ndiswrapper
FATAL: Error inserting ndiswrapper (/lib/modules/2.6.15.4/misc/ndiswrapper.ko): Invalid module format
root@bebe:/home/kim#

Any ideas?

Is there any thing i have to do before modprobing it?

Thanks for the help so far :-)

Hangdog42 · 03-03-2006, 09:40 AM

I had a look at the ndiswrapper FAQ and there are several potential reasons for this to keep happening. Have a look and see if any of them apply to you.

kimothy · 03-03-2006, 01:12 PM

You know what? I reinstalled slack. Then i installed my own 2.6.15.5 kernel in /boot-test. Then i installed ndiswrapper and the drivers from the cd. modprobed ndiswrapper and it worked! I was so happy and so i installed the kernel into /boot and i did'nt work. I went back to the /boot-test kernel and i worked. Then i tried to install ndiswrapper when in /boot kernel, and then it would'nt work in any of the 2.6.15.5 kernels (/boot and /boot-test). It makes me so MAD!!! Tried a lot of stuff and so i can't boot up /boot 2.4 stock or /boot 2.6. Only /boot-test work, and now I am going to install slack again to see if I can make it work.

When I say it worked, I did't actully surf the internet, but the light (link) was bliking once in a while, which indicates it's working.

I'm so MAD right now. I'm so sick of installing slack!

Thanks for all the help so far, I'll need som more i suspect...

kimothy · 03-03-2006, 01:55 PM

Hi again. It still work in my /boot-test folder, but only after i start firfox (or som service thats gets started with it???)

Give me a pointer pleace :-)