ndiswrapper-general Mailing List for ndiswrapper (Page 9)
Status: Beta
Brought to you by:
pgiri
You can subscribe to this list here.
2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(119) |
Dec
(497) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
(482) |
Feb
(314) |
Mar
(398) |
Apr
(259) |
May
(245) |
Jun
(372) |
Jul
(272) |
Aug
(282) |
Sep
(119) |
Oct
(150) |
Nov
(122) |
Dec
(137) |
2005 |
Jan
(278) |
Feb
(245) |
Mar
(133) |
Apr
(107) |
May
(91) |
Jun
(68) |
Jul
(83) |
Aug
(108) |
Sep
(114) |
Oct
(117) |
Nov
(54) |
Dec
(100) |
2006 |
Jan
(121) |
Feb
(112) |
Mar
(60) |
Apr
(129) |
May
(78) |
Jun
(71) |
Jul
(70) |
Aug
(64) |
Sep
(16) |
Oct
(37) |
Nov
(98) |
Dec
(27) |
2007 |
Jan
(32) |
Feb
(38) |
Mar
(21) |
Apr
(23) |
May
(29) |
Jun
(12) |
Jul
(26) |
Aug
(6) |
Sep
(3) |
Oct
(1) |
Nov
(2) |
Dec
(2) |
2008 |
Jan
(4) |
Feb
(9) |
Mar
(8) |
Apr
(7) |
May
(3) |
Jun
(7) |
Jul
(8) |
Aug
(5) |
Sep
(1) |
Oct
(7) |
Nov
(4) |
Dec
(1) |
2009 |
Jan
(12) |
Feb
|
Mar
(7) |
Apr
|
May
(2) |
Jun
(7) |
Jul
|
Aug
(1) |
Sep
(16) |
Oct
(12) |
Nov
|
Dec
|
2010 |
Jan
(4) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2011 |
Jan
|
Feb
|
Mar
(3) |
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
(5) |
Sep
(2) |
Oct
|
Nov
|
Dec
(1) |
2012 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Pavel R. <pr...@gn...> - 2007-05-30 23:57:41
|
On Wed, 2007-05-30 at 19:06 +0100, Paulo da Silva wrote: > Pavel Roskin escreveu: > > There is a file called oops-tracing.txt in Linux sources under > > Documentation. It describes how to get the error messages from the > > kernel. > > > None of my log files report any oops! I forgot to say this in my last > post. Is there anything else I can do to help? The instructions in that file also apply to kernel panics, which would not appear in the logs because the kernel won't write to any files, only to the console. Debugging kernel issues is hard and requires more than writing two-line replies. A good start would be if you post a complete and detailed description of the problem with enough information for others to reproduce it. It would also help if you actually check the kernel messages on the console when the system stops working. -- Regards, Pavel Roskin |
From: Paulo da S. <psd...@es...> - 2007-05-30 18:06:45
|
Pavel Roskin escreveu: > On Mon, 2007-05-28 at 23:04 +0100, Paulo da Silva wrote: > >> usbcore: deregistering interface driver ndiswrapper >> >> _________________________________________________________________________________ >> Here rmmod ndiswrapper hangs until I reboot! >> Is there a way to fix this, so than rmmod could remove ndiswrapper? >> > > It should be possible. Hanging is not a correct behavior. > > There is a file called oops-tracing.txt in Linux sources under > Documentation. It describes how to get the error messages from the > kernel. > > None of my log files report any oops! I forgot to say this in my last post. Is there anything else I can do to help? Regards. Paulo |
From: Pavel R. <pr...@gn...> - 2007-05-30 01:01:07
|
On Mon, 2007-05-28 at 23:04 +0100, Paulo da Silva wrote: > usbcore: deregistering interface driver ndiswrapper > > _________________________________________________________________________________ > Here rmmod ndiswrapper hangs until I reboot! > Is there a way to fix this, so than rmmod could remove ndiswrapper? It should be possible. Hanging is not a correct behavior. There is a file called oops-tracing.txt in Linux sources under Documentation. It describes how to get the error messages from the kernel. -- Regards, Pavel Roskin |
From: James S. <Sha...@ea...> - 2007-05-29 02:52:34
|
> No way :-) > My card is a USB. No buttons or whatever. > I tried everything. Removing it for example. Nothing works. > The blue led remains always off after the problem occurs. Perhaps you also need to remove the usb modules. Which you may not be able to unload if you can't unload ndiswrapper. Or if you have need of the usb modules in such a way that they can't be unloaded. Such as your root(/) filesystem being on a usb drive. Just load them in the reverse order that you unloaded them in, and vise versa. If this started after you upgraded your kernel, distro, and/or ndiswrapper, you may try downgrading one of them and see if that changes and/or fixes your problem. If you think it's hardware related, you may try using a different usb port. Or see if that usb device has the same issue on another machine. You may also check /var/log/dmesg, and messages, and others for any indication as to what may be going on. |
From: Paulo da S. <psd...@es...> - 2007-05-29 01:12:16
|
James Shatto escreveu: ... > For my BCM4318, I have a button, which doubles as the led. I actually tell my mom to push that button(the blue one) rather the power(the red one) to disconnect me from the internet and free up the bandwidth(dialup) for her to use. > > When the blue button is pushed the led goes off and I have to do the following to bring it back up. > > No way :-) My card is a USB. No buttons or whatever. I tried everything. Removing it for example. Nothing works. The blue led remains always off after the problem occurs. Since I cannot remove the module, I need to reboot to get the connection back. Whenever, in very very rare cases, the module can be removed its reinsertion causes the card to be operational again. There is some SW problem that is causing the module not being removable. About the causes why the card is crashing its a very strange situation! I have been working withount any problem for more than a year! A couple of months ago this problem began to occur ... I thought it was a problem with the card but after I replaced it the problem din't go away. |
From: James S. <Sha...@ea...> - 2007-05-29 00:30:11
|
> I am successfully using ndiswrapper with a asus wl-167g. It worked fine > except for a few ndiswrapper versions. > > > Recently my card got a HW malfunction that may occur after hours, > sometimes days. In these cases the card stops working (the led is off). > Unfortunately, if I try to remove the mdule, the rm command stays > undefinitely in execution. Another rm just says the module is busy. To > recover I need to reboot the PC. For my BCM4318, I have a button, which doubles as the led. I actually tell my mom to push that button(the blue one) rather the power(the red one) to disconnect me from the internet and free up the bandwidth(dialup) for her to use. When the blue button is pushed the led goes off and I have to do the following to bring it back up. 1) push the button again (the led comes back on) 2) # /etc/init.d/networking stop 3) # rmmod ndiswrapper 4) # modprobe ndiswrapper 5) # /etc/init.d/networking start And it works again. Alternatives include using ifconfig instead of the networking (distro specific) script. And/or modprobe -r ndiswrapper, instead of rmmod. Anyone know if there's a way to automate the above? Just bringing the network down and up is not enough. HTH |
From: Paulo da S. <psd...@es...> - 2007-05-28 22:04:52
|
Paulo da Silva escreveu: > Pavel Roskin escreveu: > >> Hello! >> >> On Thu, 2007-05-03 at 00:19 +0100, Paulo da Silva wrote: >> >> >> >>> Recently my card got a HW malfunction that may occur after hours, >>> sometimes days. Unfortunately the problem seems to have nothing to do with the card, but with some other, probabilly HW, thing. >>> In these cases the card stops working (the led is off). >>> Unfortunately, if I try to remove the module, the rm command stays >>> undefinitely in execution. Another rm just says the module is busy. To >>> recover I need to reboot the PC. >>> >>> >> It's very likely that you have some kind of kernel oops. See dmesg >> output. >> >> I replaced my card for a new one and the problem didn't occur anymore. >> That's what I first thought of ... ... OK! I have reproduced the situation ... Here is the output of dmesg. BTW, it seems the problem has nothing to do with the card! The new card also hangs! It may take hours (rarely 1 to 2 days) however. If any further info is needed pls. let me know. _________________________________________________________________________________ ndiswrapper: driver rt2500usb (Ralink,10/17/2005, 2.01.00.0000) loaded wlan0: ethernet device ......................... using NDIS driver: rt2500usb, version: 0x20000, NDIS version: 0x500, vendor: 'Ralink Technology Inc.', ................conf wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2PSK; AES/CCMP with WPA, WPA2, WPA2PSK usbcore: registered new interface driver ndiswrapper usb 3-3: USB disconnect, address 2 ndiswrapper (set_essid:59): setting essid failed (00010003) ndiswrapper (set_auth_mode:661): setting auth mode to 1 failed (00010003) ndiswrapper (iw_set_wep:915): setting authentication mode failed (FFFFFFA1) ndiswrapper (set_essid:59): setting essid failed (00010003) ndiswrapper (set_auth_mode:661): setting auth mode to 1 failed (00010003) ndiswrapper (iw_set_wep:915): setting authentication mode failed (FFFFFFA1) ndiswrapper (set_essid:59): setting essid failed (00010003) ndiswrapper (set_auth_mode:661): setting auth mode to 1 failed (00010003) ndiswrapper (iw_set_wep:915): setting authentication mode failed (FFFFFFA1) ndiswrapper (set_essid:59): setting essid failed (00010003) ndiswrapper (set_auth_mode:661): setting auth mode to 1 failed (00010003) ndiswrapper (iw_set_wep:915): setting authentication mode failed (FFFFFFA1) ndiswrapper (set_essid:59): setting essid failed (00010003) ndiswrapper (set_auth_mode:661): setting auth mode to 1 failed (00010003) ndiswrapper (iw_set_wep:915): setting authentication mode failed (FFFFFFA1) usbcore: deregistering interface driver ndiswrapper _________________________________________________________________________________ Here rmmod ndiswrapper hangs until I reboot! Is there a way to fix this, so than rmmod could remove ndiswrapper? Thanks. Paulo |
From: <ea...@gm...> - 2007-05-26 09:15:10
|
Hi there, I've been working on an Ndiswrapper frontend that will include all its functions, from adding and removing drivers, to managing the interface alia= s and kernel module. I'm rewriting most of it and want to add good alias management (remove add aliases from the interface). I had previously asked about the device listing that ndiswrapper does, at the old forum: http://ndiswrapper.sourceforge.net/phpBB2/viewtopic.php?t=3D1102 So, since each driver can be associated with more than one device and because more than one valid device may exist, does that mean that there can be more than one alias in /etc/modprobe.conf pointing to ndiswrapper? For example: alias wlan0 ndiswrapper alias wlan1 ndiswrapper alias eth1 ndiswrapper Will the ndiswrapper kernel module be able to be used by more than one device at once? If yes, then I was thinking of controlling the association of the hardware with the interfaces by using UDEV rules. I have read the man page and there wasn't any indication of what to do when multiple devices are present, and since I only have one wireless card, I'd appreciate any enlightenment on this subject. Thanks in advance! Cheers, Eug=E9ne |
From: Paulo da S. <psd...@es...> - 2007-05-13 14:39:04
|
Hi. I noticed that the order of parameters matters. Sometimes, when changing from drivers versions, I need to change the order of some parameters to have it working back again. Is there any reason for that or is it just a result of bugs? Is there any prefered order to specify the parameters? iwconfig $ETH essid $ESSID mode $MODE channel $CHANNEL key $HKEY ifconfig $ETH $IP Is this right? Should I specify a command for each parameter? Sometimes I need to reissue the iwconfig again after the ifconfig? Should the ifconfig come before iwconfig? BTW I have defined in the router access restrictions based on the IP addresses. Thanks for any enlightments. I know nothing about this stuff except for try/error experiments. Regards. Paulo |
From: Thomas P. <tho...@gm...> - 2007-05-13 07:53:01
|
There are several reports about the 4965AGN working with ndiswrapper. See <http://ubuntuforums.org/showthread.php?t=396204> and <http://www.davtar.org/blog/?p=28>. thomas |
From: CD B. <cd...@gm...> - 2007-05-12 16:07:40
|
Following the instructions I was able to get this card working perfectly. The only point of note is the selection of which INF file to use to load the driver. As advised, download the latest driver from Linksys and unzip. The files of interest are in the root directory of the zip file and are called: LSIPNDS.inf WMP11NDS.sys Using these two files, I was able to load the driver and it worked instantly. ndiswrapper -i LSIPNDS.inf followed by, ndiswrapper -l WMP11NDS.sys: driver installed then, depmod -a To load the driver during bootup: Put the following line in your init files: /etc/rc.d/rc.local modprobe ndiswrapper Use KWiFiManager to select a wireless access point to connect to and then: dhcpcd wlan0 (enter whatever interface name if it isn't wlan0) Use the wireless tools to scan and configure the wireless interface as required. A simple and effective wireless manager is: Wireless Assistant: http://wlassistant.sourceforge.net/ Don't bother fighting with NetworkManager - it is advertised as "Pain-Free Networking" but it is total crap to try and build - Dependency HELL! Thanks for a great and effective project. CD 'Bar' Baric |
From: Michael S. <nom...@ya...> - 2007-05-12 02:13:11
|
I installed ndiswrapper successfuly on my laptop I did all the ndiswrapper -i stuff and a ndiswrapper -l returned a success. modprobe ndiswrapper && dmesg returned the following ndiswrapper version 1.43 loaded (smp=no) ndiswrapper: driver bcmwl5 (Broadcom,06/26/2004, 3.70.17.0) loaded ACPI: PCI Interrupt Link [LNKF] enabled at IRQ 10 ACPI: PCI Interrupt 0000:02:03.0[A] -> Link [LNKF] -> GSI 10 (level, low) -> IRQ 10 ndiswrapper: using IRQ 10 wlan0: ethernet device 00:90:4b:9a:a9:be using NDIS driver: bcmwl5, version: 0x3461100, NDIS version: 0x501, vendor: '', 14E4:4320.5.conf wlan0: encryption modes supported: WEP; TKIP with WPA; AES/CCMP with WPA usbcore: registered new interface driver ndiswrapper but when I do a iwconfig I get the following messeges lo no wireless extensions eth0 no wireless extensions wlan0 no wireless extensions any hel will be greatly apreciated!! __________________________________ Yahoo! Clever: Sie haben Fragen? Yahoo! Nutzer antworten Ihnen. www.yahoo.de/clever |
From: David G. M. <da...@da...> - 2007-05-08 01:36:11
|
I updated ndiswrapper on my laptop to 1.43 and Red Hat pushed out a new kernel (2.6.18-8.1.3.el5). Not sure which change fixed the lock-up problem but my laptop (HP Pavilion zv6015, BCM4306 wireless NIC, x86_64 kernel) has had the wireless interface up since this morning with no problems. If desired, I can try the previous RHEL kernel with ndiswrapper 1.43 which would pin down which change fixed the problem. I may go back to running the 2.6.21 kernel anyway since my secure digital card reader works with it. It's just nice to know that I can use an "official" RHEL kernel if the need arises. Cheers, Dave -- Politics, n. Strife of interests masquerading as a contest of principles. -- Ambrose Bierce |
From: <som...@ya...> - 2007-05-07 19:23:55
|
Giridhar Pemmasani wrote: > --- "som...@ya..." <som...@ya...> wrote: > >> Well I've managed to resolve all errors so as far as dmesg and iwconfig >> are concerned, everything is fine. > > This chipset is not known to work. If it does work now, please add it to wiki > (http://ndiswrapper.sourceforge.net/joomla) with relevant information. > Not only can I not find any mention of the card on that website, I cannot figure out how to add it to the 'works' list. |
From: CD B. <cd...@gm...> - 2007-05-06 06:00:18
|
ollowing the instructions I was able to get this card working perfectly. The only point of note is the selection of which INF file to use to load the driver. As advised, download the latest driver from Linksys and unzip. The files of interest are in the root directory of the zip file and are called: LSIPNDS.inf WMP11NDS.sys Using these two files, I was able to load the driver and it worked instantly. ndiswrapper -i LSIPNDS.inf followed by, ndiswrapper -l WMP11NDS.sys: driver installed then, depmod -a To load the driver during bootup: Put the following line in your init files: /etc/rc.d/rc.local modprobe ndiswrapper Use KWiFiManager to select a wireless access point to connect to and then: dhcpcd wlan0 (enter whatever interface name if it isn't wlan0) Use the wireless tools to scan and configure the wireless interface as required. A simple and effective wireless manager is: Wireless Assistant: http://wlassistant.sourceforge.net/ Don't bother fighting with NetworkManager - it is advertised as "Pain-Free Networking" but it is total crap to try and build - Dependency HELL! Thanks for a great and effective project. CD 'Bar' Baric |
From: ShakaZ <sha...@ya...> - 2007-05-05 03:21:38
|
[input] [input] [input] [input] Hello i've been trying to login to the new ndiswrapper forum several times but the system is borked. Registered with 3 different mail adresses & every time i try to login i get redirected to the front page without being logged, so it's impossible to enter a message on the forum... and by the looks of it i don't seem to be the only one to have this problem as that forum still containt only a few messages from member of the ndiswrapper team... please fix this or a least don't ask not to open new topics on the "old" forum untill it is... Best regards ShakaZ --------------------------------- Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses. |
From: <som...@ya...> - 2007-05-04 12:23:11
|
Giridhar Pemmasani wrote: > > This chipset is not known to work. If it does work now, please add it to wiki > (http://ndiswrapper.sourceforge.net/joomla) with relevant information. > Yes people told me it wouldn't work and that this was 'known'. I think the term 'known' needs to be written as such, with inverted commas, since clearly it was infact only /thought/ not to work. I'll get onto the wiki shortly once I know enough to write something useful. I'll also put a complete guide up there about how exactly to get it working because it was not easy (frustrating that I'm stuck on this last little thing) |
From: Rodrigo L. <tro...@gm...> - 2007-05-04 04:45:20
|
> That indicates a possible issue. Try latest svn trunk (revision 2329) and > give feedback. > I tried to test the latest svn now, but I continue to receive oops with a little different call stack. But now I don't need to use netconsole, because the kernel not hangs and I can see the oops in syslog. May 4 00:29:45 dig kernel: Unable to handle kernel NULL pointer dereference at 0000000000000018 RIP: May 4 00:29:45 dig kernel: [<ffffc20000ecde54>] May 4 00:29:45 dig kernel: PGD 5a0b067 PUD 5590067 PMD 0 May 4 00:29:45 dig kernel: Oops: 0002 [1] SMP May 4 00:29:45 dig kernel: CPU 1 May 4 00:29:45 dig kernel: Modules linked in: ndiswrapper hsfhda hsfserial hsfengine(P) hsfosspec nvidia(P) snd_hda_intel snd_hda_codec uvcvideo May 4 00:29:45 dig kernel: Pid: 30075, comm: iwconfig Tainted: P 2.6.21 #4 May 4 00:29:45 dig kernel: RIP: 0010:[<ffffc20000ecde54>] [<ffffc20000ecde54>] May 4 00:29:45 dig kernel: RSP: 0018:ffff8100055dfb88 EFLAGS: 00010286 May 4 00:29:45 dig kernel: RAX: 0000000000000018 RBX: 0000000000000000 RCX: ffff8100396e6000 May 4 00:29:45 dig kernel: RDX: 000000000d010205 RSI: ffff8100055dfcec RDI: 000000000d010205 May 4 00:29:45 dig kernel: RBP: 00000000000000e8 R08: ffff8100055dfd04 R09: 0000000000000004 May 4 00:29:45 dig kernel: R10: ffff81003883e618 R11: ffff8100055dfc9c R12: ffff8100396e6000 May 4 00:29:45 dig kernel: R13: 0000000000000004 R14: ffffc200007f2000 R15: ffff8100055dfd04 May 4 00:29:45 dig kernel: FS: 00002b7f04060de0(0000) GS:ffff810001f69540(0000) knlGS:00000000f72f86b0 May 4 00:29:45 dig kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b May 4 00:29:45 dig kernel: CR2: 0000000000000018 CR3: 0000000006347000 CR4: 00000000000006e0 May 4 00:29:45 dig kernel: Process iwconfig (pid: 30075, threadinfo ffff8100055de000, task ffff81003a3beb40) May 4 00:29:45 dig kernel: Stack: ffff8100055dfcf8 ffff810000000006 ffff8100055dfd04 ffff810000000004 May 4 00:29:45 dig kernel: ffff8100055dfc9c ffff8100055dfcec 0000000000000000 0000000000000000 May 4 00:29:45 dig kernel: ffff81000901e2c0 ffffffff80479b69 ffff81000112e1b8 000000000d010102 May 4 00:29:45 dig kernel: Call Trace: May 4 00:29:45 dig kernel: [<ffffffff80479b69>] __alloc_skb+0x89/0x160 May 4 00:29:45 dig kernel: [<ffffffff8899c6df>] :ndiswrapper:miniport_query_info_needed+0xff/0x1f0 May 4 00:29:45 dig kernel: [<ffffffff8899c6d4>] :ndiswrapper:miniport_query_info_needed+0xf4/0x1f0 May 4 00:29:45 dig kernel: [<ffffffff8899c7de>] :ndiswrapper:miniport_query_info+0xe/0x20 May 4 00:29:45 dig kernel: [<ffffffff8898a793>] :ndiswrapper:iw_get_tx_power+0x23/0x50 May 4 00:29:45 dig kernel: [<ffffffff8048a152>] ioctl_standard_call+0x92/0x3d0 May 4 00:29:45 dig kernel: [<ffffffff8898a770>] :ndiswrapper:iw_get_tx_power+0x0/0x50 May 4 00:29:45 dig kernel: [<ffffffff8898a770>] :ndiswrapper:iw_get_tx_power+0x0/0x50 May 4 00:29:45 dig kernel: [<ffffffff8048a595>] wireless_process_ioctl+0x105/0x3d0 May 4 00:29:45 dig kernel: [<ffffffff8047fdb9>] netdev_run_todo+0x229/0x240 May 4 00:29:45 dig kernel: [<ffffffff8047f74c>] dev_ioctl+0x34c/0x3c0 May 4 00:29:45 dig kernel: [<ffffffff8021dd17>] do_page_fault+0x437/0x800 May 4 00:29:45 dig kernel: [<ffffffff804de384>] thread_return+0x0/0xfc May 4 00:29:45 dig kernel: [<ffffffff80472d30>] sock_ioctl+0x220/0x240 May 4 00:29:45 dig kernel: [<ffffffff802875df>] do_ioctl+0x2f/0xa0 May 4 00:29:45 dig kernel: [<ffffffff802878f3>] vfs_ioctl+0x2a3/0x2e0 May 4 00:29:45 dig kernel: [<ffffffff80287979>] sys_ioctl+0x49/0x80 May 4 00:29:45 dig kernel: [<ffffffff80209a4e>] system_call+0x7e/0x83 May 4 00:29:45 dig kernel: May 4 00:29:45 dig kernel: May 4 00:29:45 dig kernel: Code: 89 18 89 5c 24 30 be 04 00 00 00 40 b5 01 c7 44 24 34 01 00 May 4 00:29:45 dig kernel: RIP [<ffffc20000ecde54>] May 4 00:29:45 dig kernel: RSP <ffff8100055dfb88> May 4 00:29:45 dig kernel: CR2: 0000000000000018 Thanks, Rodrigo. |
From: Giridhar P. <pg...@ya...> - 2007-05-03 20:40:26
|
--- "som...@ya..." <som...@ya...> wrote: > Well I've managed to resolve all errors so as far as dmesg and iwconfig > are concerned, everything is fine. This chipset is not known to work. If it does work now, please add it to wiki (http://ndiswrapper.sourceforge.net/joomla) with relevant information. > But if I connect to our network (which is wep, unfortunately) i get > 'failed. succeeded. signal strength 0' See FAQ; you may need to specify 'open' encryption method (e.g., iwconfig wlan0 key <blah> open'). Giri __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
From: Giridhar P. <pg...@ya...> - 2007-05-03 17:22:39
|
--- Rodrigo Luiz <tro...@gm...> wrote: > I have a Broadcom 4311, using the windows driver version 4.40.19.0, > listed in wiki page of ndiswrapper. I don't have this card (like many other cards being used with ndiswrapper), so I can't reproduce. > Call Trace: > [<ffffffff889a3307>] :ndiswrapper:win2lin2+0xe/0x11 > [<ffffffff8022c65c>] try_to_wake_up+0x44c/0x470 That indicates a possible issue. Try latest svn trunk (revision 2329) and give feedback. Giri __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
From: Paulo da S. <psd...@es...> - 2007-05-03 13:59:38
|
Pavel Roskin escreveu: > Hello! > > On Thu, 2007-05-03 at 00:19 +0100, Paulo da Silva wrote: > > >> Recently my card got a HW malfunction that may occur after hours, >> sometimes days. In these cases the card stops working (the led is off). >> Unfortunately, if I try to remove the mdule, the rm command stays >> undefinitely in execution. Another rm just says the module is busy. To >> recover I need to reboot the PC. >> > > It's very likely that you have some kind of kernel oops. See dmesg > output. > I replaced my card for a new one and the problem didn't occur anymore. At the time I looked at several logs, "messages" included, for all ndiswrapper lines but nothing strange was there. I didn't look for "oops" however. I just posted this here in the hope that some part of the code could cause this and be somehow identifiable. I am using my laptop as a X terminal and these crashes/reboots are a headache. Besides they are unpredictable and very sparse in time. So, I am not able, at least by now (too busy), to return to my damaged card. Sorry. May be I could find a way to use it in an old computer I have without disturbing my work too much. Thanks anyway for answer. Regards. Paulo |
From: Rodrigo L. <tro...@gm...> - 2007-05-03 13:53:42
|
Hi. I have a Broadcom 4311, using the windows driver version 4.40.19.0, listed in wiki page of ndiswrapper. Sometimes, my kernel hangs and caps blinks. And I don't discover how to reproduce it. I just leave on my laptop on the night and on morning it hangs. Or when I work in laptop, the kernel hang sometimes too. I use netconsole to read the oops and sometimes the stack is different. Here is the log when load ndiswrapper: May 2 23:55:50 dig kernel: ndiswrapper version 1.42 loaded (smp=yes) May 2 23:55:51 dig kernel: ndiswrapper (link_pe_images:577): fixing KI_USER_SHARED_DATA address in the driver May 2 23:55:51 dig kernel: ndiswrapper: driver bcmwl5 (Broadcom,03/23/2006, 4.40.19.0) loaded May 2 23:55:51 dig kernel: ACPI: PCI Interrupt Link [LK4E] enabled at IRQ 19 May 2 23:55:51 dig kernel: ACPI: PCI Interrupt 0000:03:00.0[A] -> Link [LK4E] -> GSI 19 (level, high) -> IRQ 19 May 2 23:55:51 dig kernel: PCI: Setting latency timer of device 0000:03:00.0 to 64 May 2 23:55:51 dig kernel: ndiswrapper: using IRQ 19 May 2 23:55:51 dig kernel: wlan0: ethernet device 00:1a:73:0d:a0:48 using NDIS driver: bcmwl5, version: 0x4281300, NDIS version: 0x501, vendor: '', 14E4:4311.5.conf May 2 23:55:51 dig kernel: wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2PSK; AES/CCMP with WPA, WPA2, WPA2PSK May 2 23:55:51 dig kernel: usbcore: registered new interface driver ndiswrapper Later, the oops when hangs: Unable to handle kernel NULL pointer dereference at 0000000000000018 RIP: [<ffffc20000ecde54>] PGD ad77067 PUD 378ad067 PMD 0 Oops: 0002 [1] SMP CPU 1 Modules linked in: netconsole ndiswrapper hsfhda hsfserial hsfengine(P) nvidia(P) hsfosspec snd_hda_intel snd_hda_codec Pid: 15188, comm: iwconfig Tainted: P 2.6.21 #4 RIP: 0010:[<ffffc20000ecde54>] [<ffffc20000ecde54>] RSP: 0018:ffff81003008fb78 EFLAGS: 00010282 RAX: 0000000000000018 RBX: 0000000000000000 RCX: ffff810038d3f008 RDX: 000000000d010207 RSI: 00000000000000e8 RDI: 000000000d010207 RBP: 000000000d010207 R08: ffff81003008fd04 R09: 0000000000000004 R10: ffff81003c04ba18 R11: ffff81003008fc9c R12: ffff810038d3f008 R13: 0000000000000004 R14: ffffc200007f2008 R15: ffff81003008fd04 FS: 00002ac044128de0(0000) GS:ffff810001f69540(0000) knlGS:00000000f73476b0 CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: 0000000000000018 CR3: 000000002fa47000 CR4: 00000000000006e0 Process iwconfig (pid: 15188, threadinfo ffff81003008e000, task ffff810022e76180) Stack: ffff81003008fc7c ffff81003008fccc 0000000000000000 0000000000000000 ffff81003008fc9c ffff81003008fcec 0000000000000000 0000000000000000 0000000000000000 0000000000000286 ffff810035dbdac0 0000000000000000 Call Trace: [<ffffffff8899e9c2>] :ndiswrapper:miniport_query_info_needed+0x192/0x2c0 [<ffffffff8899e9b7>] :ndiswrapper:miniport_query_info_needed+0x187/0x2c0 [<ffffffff8899eafe>] :ndiswrapper:miniport_query_info+0xe/0x20 [<ffffffff8898b273>] :ndiswrapper:iw_get_sensitivity+0x23/0x50 [<ffffffff8048a152>] ioctl_standard_call+0x92/0x3d0 [<ffffffff8898b250>] :ndiswrapper:iw_get_sensitivity+0x0/0x50 [<ffffffff8047fdb9>] netdev_run_todo+0x229/0x240 [<ffffffff804de384>] thread_return+0x0/0xfc [<ffffffff80287979>] sys_ioctl+0x49/0x80 18 00 34 Kernel panic - not syncing: Aiee, killing interrupt handler! Another oops with different stack: Unable to handle kernel NULL pointer dereference at 0000000000000018 RIP: [<ffffc20000ecde54>] PGD 34980067 PUD 38fb8067 PMD 0 Oops: 0002 [1] SMP CPU 1 Modules linked in: netconsole ndiswrapper hsfhda hsfserial hsfengine(P) hsfosspec nvidia(P) snd_hda_intel snd_hda_codec uvcvideo Pid: 453, comm: iwconfig Tainted: P 2.6.21-g0f6551a9 #3 RIP: 0010:[<ffffc20000ecde54>] [<ffffc20000ecde54>] RSP: 0018:ffff81002c0adb38 EFLAGS: 00010282 RAX: 0000000000000018 RBX: 0000000000000000 RCX: ffff8100395fe008 RDX: 000000000d01020e RSI: 00000000000000e8 RDI: 000000000d01020e RBP: 000000000d01020e R08: ffff81002c0adcb8 R09: 0000000000000010 R10: ffff810039208818 R11: ffff81002c0adc5c R12: ffff8100395fe008 R13: 0000000000000010 R14: ffffc200007f2008 R15: ffff81002c0adcb8 FS: 00002b9abbba7de0(0000) GS:ffff810001f69540(0000) knlGS:00000000f6a68bb0 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000018 CR3: 000000003301c000 CR4: 00000000000006e0 Process iwconfig (pid: 453, threadinfo ffff81002c0ac000, task ffff810019e15680) Stack: ffffffff889a3307 ffff81002c0adccc ffff81002c0adcd4 ffffc20000000004 ffff81002c0adc5c ffff81002c0adcac 0000000000000000 0000000000000000 ffff81002c0adc7c ffff81002c0adccc 0000000000000000 0000000000000000 Call Trace: [<ffffffff889a3307>] :ndiswrapper:win2lin2+0xe/0x11 [<ffffffff8022c65c>] try_to_wake_up+0x44c/0x470 [<ffffffff8899e9a2>] :ndiswrapper:miniport_query_info_needed+0x192/0x2c0 [<ffffffff8899e997>] :ndiswrapper:miniport_query_info_needed+0x187/0x2c0 [<ffffffff8899e9f6>] :ndiswrapper:miniport_query_info_needed+0x1e6/0x2c0 [<ffffffff8899eade>] :ndiswrapper:miniport_query_info+0xe/0x20 [<ffffffff8898b2f0>] :ndiswrapper:iw_get_range+0x0/0x270 [<ffffffff804cea1a>] wext_handle_ioctl+0x16a/0x450 [<ffffffff803155a1>] __up_read+0x21/0xb0 [<ffffffff80286e63>] vfs_ioctl+0x2a3/0x2e0 be 01 RIP Kernel panic - not syncing: Aiee, killing interrupt handler! This kernel used in the last oops is 2.6.21 with wireless-dev git. I tried to unload unnecessary modules, like sound, modem, webcam, but kernel still hangs. I tried use another version of ndiswrapper like 1.41 and I didn't have no success too. Other kernels verions hangs too. This link is an output of my ndiswrapper-buginfo http://pastebin.ca/468937 Some suggestion? Thanks, Rodrigo Luiz. |
From: <som...@ya...> - 2007-05-03 10:21:11
|
James Shatto wrote: >> I've read that ndiswrapper doesn't support my wireless card. > > Technically it's your manufacturer that doesn't support it. Did you really expect something else from a Win* named product? > >> The card / driver: >> Winbond W89C33 >> WLAN Driver MIM 2120 > > Perhaps if you provided more usefull information so that support can be added or fixed. Like the vender:device number for the card (lspci -n): > 00:15.0 0200: 1050:0033 > > Or any related error messages you're getting from dmesg or /var/log/(dmesg|messages|syslog|kern.log|???) > > Something like: > > "Installed ndis drivers: > netw33 driver present, hardware present" > > "ndiswrapper: module not supported by Novell, setting U taint flag > ndiswrapper version 1.2 loaded (preempt=no,smp=no) > ndiswrapper (import:245): unknown symbol: NTOSKRNL.EXE:isprint > ndiswrapper (load_sys_files:520): unable to prepare driver 'netw33'" > > "loadndiswrapper failed (11); check system log for messages from 'loadndisdriver'" > > Which I cut and pasted from a german google result for that(or similar) card and ndiswrapper version 1.38. Not that I have any clue how to read german. You should also note that you'll need the 32 bit or 64 bit versions of the windows driver depending on how your system is setup. > > Other usefull information like what distro, kernel version, ndiswrapper version, and related information can help us better help you. > > An informative english result: > https://answers.launchpad.net/ubuntu/+question/3336 > > HTH, > James > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ Well I've managed to resolve all errors so as far as dmesg and iwconfig are concerned, everything is fine. What I can't get working is the actual connection. I've got hp's wireless-tools, and gtkwifi installed, and I can see all the networks. But if I connect to our network (which is wep, unfortunately) i get 'failed. succeeded. signal strength 0' None of the tools I know of report anything as wrong. I'm not at my machine right now, but I will be looking up how to ping with linux shortly. After that I'm stuck. |
From: Pavel R. <pr...@gn...> - 2007-05-02 23:35:31
|
Hello! On Thu, 2007-05-03 at 00:19 +0100, Paulo da Silva wrote: > Recently my card got a HW malfunction that may occur after hours, > sometimes days. In these cases the card stops working (the led is off). > Unfortunately, if I try to remove the mdule, the rm command stays > undefinitely in execution. Another rm just says the module is busy. To > recover I need to reboot the PC. It's very likely that you have some kind of kernel oops. See dmesg output. > Is there anything the developers can do to enforce the possibility of > the module removal? I think this would be a nice improvement to > ndiswrapper. There is an option in the kernel called CONFIG_MODULE_FORCE_UNLOAD. But I think you have a bigger problem than just a stuck module, and the need for reboot is justified. -- Regards, Pavel Roskin |
From: Paulo da S. <psd...@es...> - 2007-05-02 23:20:12
|
I am successfully using ndiswrapper with a asus wl-167g. It worked fine except for a few ndiswrapper versions. When in the very few times the connection breaks, in general caused by the laptop moving, a script just shuts down the net (ifconfig) and remove the module, reinsert it again and relaunch the net. This never failed. Recently my card got a HW malfunction that may occur after hours, sometimes days. In these cases the card stops working (the led is off). Unfortunately, if I try to remove the mdule, the rm command stays undefinitely in execution. Another rm just says the module is busy. To recover I need to reboot the PC. Is there anything the developers can do to enforce the possibility of the module removal? I think this would be a nice improvement to ndiswrapper. Thanks. Paulo |