I am getting a kernel panic from ndiswrapper in two versions, 0.11 and 0.12. Version 0.10 works without many problems. The error message is Kernel Panic:Not syncing fatal exception in interupt. This is what I found in dmesg. ndiswrapper version 0.12 loaded (preempt=yes,smp=no) ndiswrapper: using irq 11 ndiswrapper (ndis_set_rx_mode_proc:588): Unable to set packet filter (C00000BB) ndiswrapper (set_essid:53): setting essid failed (C0010015) ndiswrapper (ndis_set_rx_mode_proc:588): Unable to set packet filter (C00000BB) wlan0: ndiswrapper ethernet device 00:0f:3d:4b:51:77 using driver mrv8k51 ndiswrapper: driver mrv8k51 (D-Link,1/09/2004,2.3.0.1) added ndiswrapper (set_essid:53): setting essid failed (C0010015) ndiswrapper (ndis_set_rx_mode_proc:588): Unable to set packet filter (C00000BB) Reproducible: Always Steps to Reproduce: 1.emerge ndiswrapper (versions 0.11 or 0.12) 2.Reboot system 3.Wait for kernal panic. (Occurs after about 5 to 20 minutes with the system sitting idle. Actual Results: System Locked up with a Kernel Panic. Expected Results: Should have handled any and all traffic being run on my dlink wireless card using the windows drivers loaded with ndiswrapper. Portage 2.0.51-r3 (default-linux/x86/2004.2, gcc-3.4.3, glibc-2.3.4.20040808-r1, 2.6.9-gentoo-r1 i686) ================================================================= System uname: 2.6.9-gentoo-r1 i686 AMD Duron(tm) Processor Gentoo Base System version 1.4.16 Autoconf: sys-devel/autoconf-2.59-r5 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.15.90.0.1.1-r3 Headers: sys-kernel/linux26-headers-2.6.8.1-r1 Libtools: sys-devel/libtool-1.5.2-r7 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=athlon -O2 -pipe" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=athlon -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks fixpackages sandbox sfperms" GENTOO_MIRRORS="http://gentoo.oregonstate.edu/ ftp://ftp.gtlib.cc.gatech.edu/pub/gentoo http://csociety-ftp.ecn.purdue.edu/pub/gentoo/ ftp://csociety-ftp.ecn.purdue.edu/pub/gentoo/ http://gentoo.mirror.sdv.fr" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" USE="3dnow 3dnowex X Xaw3d aalib acpi adns alsa amd apache2 apm arts artswrappersuid authdaemond avi berkdb bitmap-fonts blender-game bonobo bootspla c cdparanoia cdr cdrom cjk clamav codecs crypt cups dga directfb divx4linux dmx dnd dv dvd dvdread emoticon encode erandom esd f77 fam fbcon ffmpeg fftw flac fmod foomaticdb foreign-package foreign-sysvinit fortran freetds freetype fs gb gd gdbm gif gimpprint glade glut gnome gnomedb gpm gsl gstreamer gtk gtk2 gtkhtml guile icq imagemagick imap imlib imlib2 innodb ipv6 jabber java javascript jikes joystick jpeg junit jython kde kerberos lcms libg++ libgda libwww lzo mad maildir mailwrapper mbox mcal md5sum memlimit mikmod mmx mmx2 motif mozcalendar mozdomi mozilla mozp3p mozsvg mpeg mpeg4 mpi mplayer msn music mysql mysqli native ncurses net nls nntp nptl nvidia offensive oggvorbis openal opengl opens oscar oss pam pdf pdflib pear-db perl php png ppds prelude pthreads python qt quicktime readline regexp samba sasl scanner sdl slang slp snmp soap sockets socks5 speedo speex spell spl sqlite ssl svg svga tcltk tcpd threads tiff tools transcode truetype type1 unicode unsafe usb vhosts videos virus-scan wifi wmf wxwin wxwindows x86 xine xinetd xml xml2 xmms xpm xscreensaver xsl xv xvid yahoo zeo zlib"
I have also placed a bug report with the bug tracker on sourceforge for the ndiswrapper project.
(grr, why do people not look at metadata.xml for the herd to assign this to)
All ndiswrapper bug reports need to include the following: # cat /proc/version # gcc --version # ls -l /usr/src/linux (no / at the end) # uname -a # grep 'CONFIG_4KSTACKS' /usr/src/linux/.config Post that info here and then I can take a look at it.
cat /proc/version Linux version 2.6.9-gentoo-r1 (root@insanity) (gcc version 3.4.2 (Gentoo Linux 3.4.2-r2, ssp-3.4.1-1, pie-8.7.6.5)) #3 Fri Oct 22 23:16:08 CDT 2004 gcc --version gcc (GCC) 3.4.3 20041125 (Gentoo Linux 3.4.3-r1, ssp-3.4.3-0, pie-8.7.7) Copyright (C) 2004 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. ls -l /usr/src/linux lrwxrwxrwx 1 root root 30 Oct 22 17:33 /usr/src/linux -> /usr/src/linux-2.6.9-gentoo-r1 uname -a Linux insanity 2.6.9-gentoo-r1 #3 Fri Oct 22 23:16:08 CDT 2004 i686 AMD Duron(tm) Processor AuthenticAMD GNU/Linux grep 'CONFIG_4KSTACKS' /usr/src/linux/.config # CONFIG_4KSTACKS is not set
I haven't experienced any troubles with 0.11 but 0.12 seems to lock my system hard (no magic sysrq, reset/power cycle needed) after 5-20 minutes as well. I reverted to 0.11 and all seems well so far. please log # cat /proc/version Linux version 2.6.9-gentoo-r3 (root@please) (gcc version 3.4.3 (Gentoo Linux 3.4.3, ssp-3.4.3-0, pie-8.7.6.5)) #2 SMP Fri Nov 12 14:30:58 PST 2004 please log # gcc --version gcc (GCC) 3.4.3 20041125 (Gentoo Linux 3.4.3-r1, ssp-3.4.3-0, pie-8.7.6.7) Copyright (C) 2004 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. please log # ls -l /usr/src/linux lrwxrwxrwx 1 root root 22 Nov 7 17:13 /usr/src/linux -> linux-2.6.9-gentoo-r3/ please log # uname -a Linux please 2.6.9-gentoo-r3 #2 SMP Fri Nov 12 14:30:58 PST 2004 i686 AMD Athlon(tm) MP 2000+ AuthenticAMD GNU/Linux please log # grep 'CONFIG_4KSTACKS' /usr/src/linux/.config # CONFIG_4KSTACKS is not set
kernel 2.6.9 & ndiswrapper 0.10 works, kernel 2.6.9 & ndiswrapper 0.11,0.12 kernel panic kernel 2.6.10 & ndiswrapper 0.10 fails to compile. kernel 2.6.10 & ndiswrapper 0.12 so far seems to work. No kernel panic. My suggestion is to mask 0.11 and 0.12 for the 2.6.9 kernel I have been up now about 2 hours since compiling the new kernel. If it fails I will submit a followup. Also nothing else in my setup has changed except for the kernel. As to the compile failure for 2.6.10 and 0.10 this is the output. ------------------------------- make -C //usr/src/linux M=/var/tmp/portage/ndiswrapper-0.10/work/ndiswrapper-0.10/driver \ NDISWRAPPER_VERSION=0.10 \ EXTRA_VERSION= modules make[2]: Entering directory `/usr/src/linux-2.6.10-gentoo' CC [M] /var/tmp/portage/ndiswrapper-0.10/work/ndiswrapper-0.10/driver/wrapper.o /var/tmp/portage/ndiswrapper-0.10/work/ndiswrapper-0.10/driver/wrapper.c: In function `ndis_suspend_pci': /var/tmp/portage/ndiswrapper-0.10/work/ndiswrapper-0.10/driver/wrapper.c:892: error: too many arguments to function `pci_save_state' /var/tmp/portage/ndiswrapper-0.10/work/ndiswrapper-0.10/driver/wrapper.c: In function `ndis_resume_pci': /var/tmp/portage/ndiswrapper-0.10/work/ndiswrapper-0.10/driver/wrapper.c:923: error: too many arguments to function `pci_restore_state' /var/tmp/portage/ndiswrapper-0.10/work/ndiswrapper-0.10/driver/wrapper.c: In function `ndis_init_one_pci': /var/tmp/portage/ndiswrapper-0.10/work/ndiswrapper-0.10/driver/wrapper.c:1453: error: too many arguments to function `pci_restore_state' make[3]: *** [/var/tmp/portage/ndiswrapper-0.10/work/ndiswrapper-0.10/driver/wrapper.o] Error 1 make[2]: *** [_module_/var/tmp/portage/ndiswrapper-0.10/work/ndiswrapper-0.10/driver] Error 2 make[2]: Leaving directory `/usr/src/linux-2.6.10-gentoo' make[1]: *** [default] Error 2 make[1]: Leaving directory `/var/tmp/portage/ndiswrapper-0.10/work/ndiswrapper-0.10/driver' make: *** [all] Error 2 -------------------------------------
yes, 0.10 will not compile with a kernel version greater then 2.6.9. It's not suppose to. If you want to use 2.6.10, you must use 0.12 or greater. 0.12-r1 is the new stable package, run emerge --sync. Robert, really important to compile your modules and kernel with the same compiler. I recommend you re-compile your kernel. giggles, any reason you're using SMP? It's known to cause issues with certain drivers. Also whats the hardware you're using?
I spoke to soon on version 0.12 not kernel panicking with the 2.6.10 kernel. As to the compiler, I used gcc-3.4.3 and I compiled the kernel then the 0.12 ndiswrapper driver. So I am using the same version of gcc for both the kernel and the modules. I always use the same version of gcc for my compiles unless I hit a program that won't compile under gcc-3.4. And usually the next minor version fixes that so I tend to have very very little on my machine compiled with gcc 3.3. I will try version 0.12-r1 next and see if it crashes me like version 0.12 did on the 2.6.10 kernel. I do know that version 0.12-r1 caused me a kernel panic under 2.6.9-r1. Any suggestions are welcome as I am now stuck at 2.6.9 until the version 0.12 kernel panic can be solved. I am more than willing to try suggestions and report the results.
Unfortunately just saying kernel panic doesn't provide enough info. We're going to need some dmesg outputs here. and some kernel oops messages. But most likely, this is caused by the Windows driver you are using. Try a different one.
Created attachment 46919 [details] dmesg for ndiswrapper-0.12 and kernel-2.6.10-gentoo Attached is the output from dmesg msg012.txt is with ndiswrapper-0.12 and 2.6.10-gentoo. Current results so far 2.6.9 kernel panic's with versions 0.11,0.12 and 0.12-r1 2.6.10 kernel panics's with version 0.12 Didn't try 0.11, and I am using version 0.12-r1 now. So far no panic. After 24 hours I will give a followup on version 0.12-r1
Created attachment 46920 [details] dmesg for ndiswrapper-0.12-r1 and kernel-2.6.10-gentoo Attached is the output from dmesg msg012.txt is with ndiswrapper-0.12-r1 and 2.6.10-gentoo. Current results so far 2.6.9 kernel panic's with versions 0.11,0.12 and 0.12-r1 2.6.10 kernel panics's with version 0.12 Didn't try 0.11, and I am using version 0.12-r1 now. So far no panic. After 24 hours I will give a followup on version 0.12-r1
0.12 and 0.12-r1 produce the same compiled code. The only difference is the ebuild checks some settings in your kernel config to make sure they're not set. I'd still try different Windows drivers. Also what version of wireless-tools do you have? Try rebuilding them with kernel 2.6.10 as the API that wireless-tools uses has been upgraded in 2.6.10.
I am using wireless-tools-27-pre26 and I will rebuild them. As to the windows drivers, those are the drivers that came with the card. The card is the D-Link DWL-G510,from lspci -- Ethernet controller: Marvell Technology Group Ltd. Marvell W8300 802.11 Adapter (rev 07) from lspci -n -- Class 0200: 11ab:1fa6 (rev 07). Do you know of another set of windows drivers or a set of linux drivers for this card. I have been looking but to date the mrv8k51 (D-Link,1/09/2004,2.3.0.1) driver is the only one that I have found to be recomended for this card. (personally I would have prefered to use a linksys card but the better half she wanted dlink because of rebates. Oh well.) Oh I don't know if this will help or not, but from linux I am unable to use ntp servers to set my clock via the wireless card. From windows it works just fine, and from linux using the realtek:8139 it works just fine. I find it very strange that just that one protocoll doesn't work with the wireless card using linux.
Well here are some other drivers I found for your card from the ndiswrapper website. As far as the D-Link driver goes, a user commented not to use the WinXP driver. ftp://ftp1.planet.com.tw/Wireless_Lan/WL-3563/DR-WL3563v230.zip As far as the D-Link card itself, users recommend the Asus card drivers over D-Link's own drivers. Same chipset and all. http://www.asus.com.tw/support/download/item.aspx?ModelName=WL-138G gigggles, I've address a few comments to you so scroll up. As far as SMP, I'll make an ebuild for ndiswrapper 1.0rc1 just for you to try if you must use SMP for a test. Because SMP kernel support isn't 100% fixed until 1.0rc1, so it's not surprising you get problems with the latest stable.
Doug: I am running SMP because it is an SMP box. Dual Athlon MPs. Or, if you were asking about the card it is a Marvell. 0.11 is still running like a charm, tho I am happy to try a new one if it is available.
Doug it seems that my computer is a bit backwards. Where others would use the asus drivers first and win xp last, my machine seems to like the winxp drivers. I was using the win 98 drivers and I was getting the kernel panics. I tried the asus drivers and they also caused kernel panics. Do you want me to load back in the asus drivers and send you the kernel Oops message and the win 98 and send the oops message?
Created attachment 47616 [details] Text of kernel panic msg aka Oops message this is the kernel panic msg for 2.6.10 kernel and ndiswrapper-0.12-r3
Created attachment 47617 [details] Current kernel config Current kernel config for 2.6.10-gentoo
I have included two new attachments. #1, my kernel oops message (from 01/04/05) #2, my current kernel configuration. note: on the sourceforge bug tracker for ndiswrapper there was a comment about preempt. I am assuming that they meant the selection ofthe preemptable kernel. Based on that I am recompiling my kernel without preempt. I will let you know if it takes care of the kernel panic. The other thing that was mentioned was that the CVS tree may work with a preempt kernel. additional information. I am currently using the d-link winXP driver. Let me know if you want me to post the binary as an attachment.
removing preempt from the kernel didn't help. Still had a kernel panic.
Here's 2 ideas. try turning off ACPI first. and test again. If you still receive a kernel panic try removing iptables.
Created attachment 48437 [details] ndiswrapper-1.0_rc2.ebuild I had similar trouble to giggles1 where 0.11 worked fine with SMP but 0.12 caused the system to hang after many messages like: Dec 17 17:53:26 bioeng109 Linux version 2.6.9-gentoo-r9 (root@bioeng109) (gcc version 3.3.4 20040623 (Gentoo Linux 3.3.4-r1, ssp-3.3.2-2, pie-8.7.6)) #4 SMP Fri Dec 17 17:44:05 NZDT 2004 ... Dec 17 17:58:22 bioeng109 ndiswrapper version 0.12 loaded (preempt=yes,smp=yes) Dec 17 17:58:24 bioeng109 ACPI: PCI interrupt 0000:02:03.0[A] -> GSI 17 (level, low) -> IRQ 17 Dec 17 17:58:24 bioeng109 ndiswrapper: using irq 17 Dec 17 17:58:25 bioeng109 wlan0: ndiswrapper ethernet device 00:90:4b:74:c8:53 using driver oem17 Dec 17 17:58:25 bioeng109 wlan0: encryption modes supported: WEP, WPA with TKIP, WPA with AES/CCMP Dec 17 17:58:25 bioeng109 ndiswrapper: driver oem17 (Broadcom,06/25/2004, 3.40.73.0) added ... Dec 17 20:50:22 kern.err bad: scheduling while atomic! Dec 17 20:50:22 kern.warning [<b8105f38>] dump_stack+0x1e/0x22 Dec 17 20:50:22 kern.warning [<b82eb7d9>] schedule+0xb11/0xb16 Dec 17 20:50:22 kern.warning [<b812c755>] worker_thread+0x207/0x225 Dec 17 20:50:22 kern.warning [<b813049c>] kthread+0xb7/0xbc Dec 17 20:50:22 kern.warning [<b81032ad>] kernel_thread_helper+0x5/0xb Dec 17 20:50:22 kern.err bad: scheduling while atomic! ... I tried ndiswrapper 1.0rc1 with gentoo-dev-sources-2.6.10-r4 but had similar problems: Jan 10 17:02:47 bioeng109 ndiswrapper: driver oem17 (Broadcom,06/25/2004, 3.40.73.0) added ... Jan 10 17:04:06 bioeng109 ndiswrapper (KfLowerIrql:111): IRQL 0 != DISPATCH_LEVEL Jan 10 17:04:06 bioeng109 scheduling while atomic: events/0/0xfffffeff/6 Jan 10 17:04:06 bioeng109 [<b8103f7e>] dump_stack+0x1e/0x30 Jan 10 17:04:06 bioeng109 [<b82f8b82>] schedule+0xbd2/0xbe0 Jan 10 17:04:06 bioeng109 [<b812d275>] worker_thread+0x215/0x240 Jan 10 17:04:06 bioeng109 [<b81315ba>] kthread+0xba/0xc0 Jan 10 17:04:06 bioeng109 [<b81012f5>] kernel_thread_helper+0x5/0x10 ... However, ndiswrapper 1.0rc2 has been working fine the last 8 hours.
Doug: I removed acpi support from the kernel but that didn't help with version 0.12. I am currently trying ndiswrapper-1.0rc2 pre-release version. So far it seems to be working. I will post back if it locks up on me. I also managed to do the install using emerge. I have to hand it to all the developers that worked on portage. The system is very userfriendly. Modifying a script to support a new version isn't hard at all.
I am still out of town. I will try this new version when I get back.
Further update. While using ndiswrapper-1.0rc2 my system rebooted itself instead of just locking up with a kernel panic. So I have removed acpi support again and letting the system run. Hopefully it will stay up over the next 72 hours.
Created attachment 48528 [details] ndiswrapper-1.0_rc2.ebuild I can't recommend using a renamed version of my 0.12 ebuilds. I'd use this ebuild. However this is not the last revision of this ebuild. There will be a newer one once ndiswrapper 1.0 rc3 comes out. The notices also need to be updated.
i have also had lots of problems with 0.12 and 2.6.10 (p4HT), but 1.0rc seems to work just fine
A thought occured to me and I did some checking. It seems that in the .conf files generated by version 0.10 doesn't have the following line thats in the 1.0 version (didn't check 0.12) mac_address|XX:XX:XX:XX:XX:XX. I am wondering if this could be having some effect on the problems that I have been seeing with all versions past 0.10? Anyway I have also posted this thought to the open discussion forums on the ndiswrapper site. I will let you know what if any respones I get from them.
Additional info. When I run the program ndiswrapper-buginfo it unloads then reloads the ndiswrapper module. When it does this I lose wlan0. Trying to restart wlan0 results in the error message that no such device exists. Now the text from /tmp/ndiswrapper-buginfo.gz generated by the ndiswrapper-buginfo program. ----------- utils: -rwxr-xr-x 1 root root 15736 Jan 22 11:32 /sbin/loadndisdriver -rwxr-xr-x 1 root root 20345 Jan 22 11:32 /usr/sbin/ndiswrapper ------------------------------------ kernel: Linux version 2.6.10-gentoo-r5 (root@insanity) (gcc version 3.4.3 20050110 (Gentoo Linux 3.4.3.20050110, ssp-3.4.3.20050110-0, pie-8.7.7)) #1 Thu Jan 20 13:59:04 CST 2005 kernel sources are in /lib/modules/2.6.10-gentoo-r5/build ------------------------------------ gcc --version: gcc (GCC) 3.4.3 20041125 (Gentoo Linux 3.4.3-r1, ssp-3.4.3-0, pie-8.7.7) Copyright (C) 2004 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. ------------------------------------ installed drivers: /etc/ndiswrapper: total 0 drwxr-xr-x 2 root root 288 Jan 22 11:34 mrv8k51 /etc/ndiswrapper/mrv8k51: total 276 lrwxrwxrwx 1 root root 51 Jan 22 11:34 11AB:1FA6.5.conf -> /etc/ndiswrapper/mrv8k51/11AB:1FA6:11AB:1FA4.5.conf -rw-r--r-- 1 root root 159 Jan 22 11:34 11AB:1FA6:1186:3B08.5.conf -rw-r--r-- 1 root root 159 Jan 22 11:34 11AB:1FA6:1186:3B09.5.conf -rw-r--r-- 1 root root 159 Jan 22 11:34 11AB:1FA6:11AB:1FA4.5.conf -r-xr-xr-x 1 root root 8642 Jan 22 11:34 mrv8k51.inf -rw-r--r-- 1 root root 256896 Jan 22 11:34 mrv8k51.sys Reloading ndiswrapper... [<c036b7b0>] (snd_via82xx_interrupt+0x0/0x140) [<d135c660>] (ndis_irq_th+0x0/0xd0 [ndiswrapper]) Disabling IRQ #11 ndiswrapper version 1.0rc3 loaded (preempt=yes,smp=no) ndiswrapper: driver mrv8k51 (D-Link,1/09/2004,2.3.0.1) added PCI: Found IRQ 11 for device 0000:00:0a.0 PCI: Sharing IRQ 11 with 0000:00:07.5 ndiswrapper: using irq 11 ndiswrapper (ndiswrapper_add_one_pci_dev:186): Windows driver couldn't initialize the device (C0000001) ndiswrapper: probe of 0000:00:0a.0 failed with error -22 -----------------
First off... don't use rc3. Use rc4 if you want to use anything. There's an official ebuild by me for it. Secondly, compile with USE="debug". Thirdly, there looks like there's more underlying problems based on that dmesg output. Fourth, did you remember to re-install your driver? Since rc3 and up require a reinstall. Lastly, I still think there's an issue with your Windows driver.
Just saw your comments about rc4 being out. I am running emerge sync now. As to the drivers, yes I know that I have to reinstall the drivers. If rc4 works I will post to let you know. If it crashes I will collect as much info as I can and post it. Also I will build with USE="debug" on this one.
Update on 1.0_rc4. I am still getting occaisional lockups. I did compile ndiswrapper with USE="debug" and I will post the relative parts of /var/log/kernel/current. At this point I am waiting to see if I get the same debug messages when it locks up. Once I have collected a bit more info I will also post the ndiswrapper-buginfo file as well with the other info I have collected.
I am also getting the same hard lockups with 0.12 (including 0.12-r3) with many "scheduling while atomic!" in the logs. Tried 1.0_rc4 but it caused a hard lockup upon loading the module (this may have been because I installed the wrong windows driver). Posting my data here in hopes that it helps. I'll also post again if my 1.0_rc4 woes aren't due to an incorrect driver. # cat /proc/version Linux version 2.6.10-ck1 (root@slate) (gcc version 3.3.4 20040623 (Gentoo Linux 3.3.4-r1, ssp-3.3.2-2, pie-8.7.6)) #3 SMP Mon Jan 24 13:19:47 EST 2005 # gcc --version gcc (GCC) 3.3.4 20040623 (Gentoo Linux 3.3.4-r1, ssp-3.3.2-2, pie-8.7.6) Copyright (C) 2003 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. # ls -l /usr/src/linux (no / at the end) lrwxrwxrwx 1 root root 16 Jan 24 13:17 /usr/src/linux -> linux-2.6.10-ck1 # uname -a Linux slate 2.6.10-ck1 #3 SMP Mon Jan 24 13:19:47 EST 2005 i686 Mobile Intel(R) Pentium(R) 4 CPU 3.20GHz GenuineIntel GNU/Linux # grep 'CONFIG_4KSTACKS' /usr/src/l # CONFIG_4KSTACKS is not setinux/.config
Edward what card do you have? I am using D-Link's DWL-G510 and My best results have so far come from the WinXP drivers from the cd that came with the card.
Created attachment 49682 [details] Ndiswrapper information on crashes (using 1.0_rc4) This is small extracts from the kernel log as well as the info produced by ndiswrapper-buginfo progam.
I am using the internal card on a Dell Inpspiron 5160, the following is the lspci info for it: 0000:02:02.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03) Subsystem: Dell Wireless 1350 WLAN Mini-PCI Card Flags: bus master, fast devsel, latency 32, IRQ 18 Memory at faffc000 (32-bit, non-prefetchable) I reinstalled the new driver I am using (didn't save a copy of the old one) with 0.12_rc3 and it worked the same as before, i.e. worked fine up until it locked up :) When attempting to load ndiswrapper 1.0_rc4 I get a kernel panic. I don't have a copy of the actual panic but below is what was in the kernel log: Jan 27 19:45:33 [kernel] ndiswrapper version 1.0rc4 loaded (preempt=yes,smp=yes) Jan 27 19:45:33 [kernel] ndiswrapper (wrap_spin_lock_init:415): spinlock used is not compatible with KSPIN_LOCK; is CONFIG_DEBUG_SPINLOCK disabled? 8, 4 I think next I'll try 1.0_rc4 with a vanilla 2.6.10 kernel.
Edward does your laptop have multiple processors? I noticed in your earlier post that you had (prempt=yes,smp=yes). If your laptop doesn't have more than one processor, disable smp in the kernel.
It's a hyperthreaded Pentium-IV, so it has two logical cpu's. I've been running 1.0_rc4 on a vanilla 2.6.10 kernel with preempt disabled (smp still enabled) and so far all has been well. Next I'll see if turning on preempt brings the problem back.
ndiswrapper 1.1 has been extremely stable on my system. I would REALLY urge the gentoo devs to mark it stable and/or put a post merge message of: do NOT! go into the IRC channel to ask for help. reason?.. they were INCREDIBLY RUDE!!! just because I saw no where that there has been any newer versions released. I got a kernel panic with 0.12 thinking it was the newest I went to report. NEVER again.... few other comments I'd like to make for future ebuilds are: include the kernel path for needed support (such as NET_RADIO) for 2.6 kernels Device Drivers ---> Networking support ---> Wireless LAN (non-hamradio) ---> [*] Wireless LAN drivers (non-hamradio) & Wireless Extensions and perhaps reinstalling if neccessary the drivers: for driver in `ls /etc/ndiswrapper` do mv /etc/ndiswrapper/${driver} /tmp ndiswrapper -i /tmp/${driver}/${driver}.inf done
Thx leaf. Looks like this is slowly getting squared away. I'd really like to see it tested with version 1.1. Also, verify your Windows driver. 1.1 should be a little more strict on the requirements of the Windows driver. Going to close this one out. If there are any more issues. Please re-open or open a new bug with specific card info.
