LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   modprobe ndiswrapper system freeze on suse 9.1 (https://www.linuxquestions.org/questions/linux-newbie-8/modprobe-ndiswrapper-system-freeze-on-suse-9-1-a-279998/)

686plus 01-20-2005 12:28 AM

modprobe ndiswrapper system freeze on suse 9.1
 
I've recently installed SuSE 9.1 onto a laptop so it will dual boot with xp. In trying to set up my wireless card using ndiswrapper, I run into a problem with the command modprobe ndiswrapper. The system just freezes. I'm not sure where to start because I'm not exactly sure what's happening. Is there a log file I can check?

All my searches just tell me how to get ndiswrapper going. The lq tutorial is good too, I just can't ndiswrapper loaded.

The laptop is sony with a 900mhz celeron and 256mb ram.

0pal_t0ad 01-20-2005 02:16 AM

I'm pretty sure i've read something about that on the ndiswrapper website before, but i didn't take much notice 'cos i didn't have that problem :)

Hangdog42 01-20-2005 07:36 AM

I'd check /var/log/syslog and /var/log/messages and see if there is anything there. They are the most likely locations for a log entry. There have been lots of reports of this sort of problem, but is usually happened on some flavor of Red Hat and frequently was related to the fact that RH had 4K stacks compiled into their standard kernel and not all windows drivers could live with that.

686plus 01-23-2005 04:09 PM

Hangdog42,

I decided to ditch SuSE on the laptop and installed FC2. While compiling ndiswrapper, it did detect the 4k stacks and told me not to whine when it crashes. Now that I'm certain that's the problem (certain on SuSE too), any suggestions?

Can I change the kernel to 8k stacks? I've never tweaked with the kernel before.

I also found a realtek RTL8180L driver for linux, but it (and a related tutorial on this site) says it will only work with kernel 2.4 or earlier. I'm using 2.6.5.

Can anyone make a suggestion on which route to take? I can also get my hands on wlan card with the intersil prism chipset, if that's a better option. I could barely get that to work with windows, though.

Hangdog42 01-23-2005 04:47 PM

Quote:

Can I change the kernel to 8k stacks? I've never tweaked with the kernel before.
Yes you can, but if you haven't built a kernel before, this probably isn't the time to start. The good news is that Linuxant seems to compile kernel for FC that solve this problem. You can find the RPMs here . Since I run Slackware, I've never used these kernels, but I have seen some people here at LQ use them successfully.

686plus 02-12-2005 05:56 PM

Sorry for the long delay. I've had some family members with health issues.

I installed the linuxant kernel rpm on fedora core 2 (there wasn't a match available for my kernel, though). No luck.

I did a fresh install of fedora core 3, but the default kernel 2.6.9-1.667 that was on the dvd I could grab still has the 4k stack. I found a linuxant 16k stack rpm for that kernel and distro and installed it. I installed ndiswrapper-1.0 after changing the kernel and installed the lastest realtek 8180 driver. The system still freezes when I try to load the module using /sbin/modprobe ndiswrapper.

When i check lspci the card shows up and ndiswrapper -l shows the driver and hardware present. I'm at a dead end. It should be working now, shouldn't it?

I've also got another card with a prism chipset that is listed by the manufacturer as compatible with linux-wlan-ng. I can't get that installed though.

Anyone have ideas where to go from here? This is the last hang-up before I ditch XP completely.

Thanks

Hangdog42 02-14-2005 08:02 AM

After you reboot from a freeze, have you checked the logs to see if anything is there about what the system was trying to do when it froze? It might be helpful. About the only other suggestion I can make at this point are pretty substantial work. You could either compile your own kernel so you can get away from the 4K stacks, or you could switch distros. Red Hat distros and ndiswrapper are frequently not a good fit.

686plus 02-16-2005 05:11 PM

Here's my lspci output:

Code:

[root@localhost log]# /sbin/lspci
00:00.0 Host bridge: Intel Corp. 82815 815 Chipset Host Bridge and Memory Controller Hub (rev 11)
00:02.0 VGA compatible controller: Intel Corp. 82815 CGC [Chipset Graphics Controller] (rev 11)
00:1e.0 PCI bridge: Intel Corp. 82801 Mobile PCI Bridge (rev 03)
00:1f.0 ISA bridge: Intel Corp. 82801BAM ISA Bridge (LPC) (rev 03)
00:1f.1 IDE interface: Intel Corp. 82801BAM IDE U100 (rev 03)
00:1f.2 USB Controller: Intel Corp. 82801BA/BAM USB (Hub #1) (rev 03)
00:1f.3 SMBus: Intel Corp. 82801BA/BAM SMBus (rev 03)
00:1f.4 USB Controller: Intel Corp. 82801BA/BAM USB (Hub #2) (rev 03)
00:1f.5 Multimedia audio controller: Intel Corp. 82801BA/BAM AC'97 Audio (rev 03)
01:00.0 FireWire (IEEE 1394): Texas Instruments TSB43AA22 IEEE-1394 Controller (PHY/Link Integrated) (rev 02)
01:02.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev 80)
01:02.1 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev 80)
01:08.0 Ethernet controller: Intel Corp. 82801BA/BAM/CA/CAM Ethernet Controller (rev 03)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8180L 802.11b MAC (rev 20)
[root@localhost log]#

Hers's my /var/log/messages output (when I try to load the module):

Code:

Feb 16 10:45:08 localhost gconfd (root-4845): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
Feb 16 10:48:12 localhost su(pam_unix)[4817]: session closed for user root
Feb 16 10:50:48 localhost kernel: ndiswrapper version 1.0 loaded (preempt=no,smp=no)
Feb 16 10:52:58 localhost syslogd 1.4.1: restart.
Feb 16 10:52:58 localhost syslog: syslogd startup succeeded

The ndiswrapper -l command shows the driver and hardware present when I try to modprobe ndiswrapper.

I'm not very familiar with reading logs, but it looks like the module actually gets loaded. The system just freezes up after. Also, the "session closed for user root" line seems curious to me. Does that mean my superuser session ended? Is that normal?

It seems everything should work, it just doesn't. I guess my next question would be do you know any good howtos on building my own kernel? It seems like that is my next course of action.

Hangdog42 02-21-2005 10:03 AM

Sorry for the delay. I was away for a bit without internet access......


Quote:

Also, the "session closed for user root" line seems curious to me. Does that mean my superuser session ended? Is that normal?
If you look at the first part of that line you'll see the pam_unix statement. PAM is an authentication program and it looks to me like it is started by su to root and then that su session is shut down. I don't think it is anything to worry about and it probably isn't related to the modprobe crash problem.

You are right, it does look like the ndiswrapper module loads fine, it just hangs when you try to use it. That does suggest to me that the 4K stacks are the problem. So if you want to compile your own kernel, I would suggest running through the Suse forum here for distro specific advice. Otherwise, I've stolen a lot of good advice and written one you can find here but it is somewhat Slackware specific, particularly in how to modify LILO. I believe Suse uses GRUB as the bootloader so you'll have to find out how to modify GRUB.

You also might have a look at the site snecklifter references. It has kernels for RH, and it may have kernels for Suse.

686plus 02-26-2005 10:37 AM

Thanks. I'll check those out.

Baryn 03-30-2005 06:09 PM

My system used to work fine, wifi and all. Now I have this problem, inexplicably.

I'm all for Linux and everything, but with a catch twenty-two for every solution, you think that maybe this platform needs some kind of organization.

Hangdog42 03-30-2005 07:39 PM

The problem isn't with linux, the problem is with wireless card manufacturers. For cards made by manufacturers who either write their own drivers or release the specs for their cards, linux support is just fine. However, a large number of manufacturers won't write drivers and won't release specs, so hacks like ndiswrapper are the end result. So if you don't like the way your wireless card is supported, please vent at your card vendor, they're the ones responsible for the mess.


All times are GMT -5. The time now is 04:13 PM.