Thread: [Ndiswrapper-general] WLAGS48B - Agrere Chipset
Status: Beta
Brought to you by:
pgiri
From: Christopher N. <ch...@ne...> - 2005-09-06 19:32:30
|
Good Day, I was flipping though Linux Journal and came across an article that mentioned ndiswrapper. I thought I'd try it out but I don't see my wireless chip supported in the "List". Someone else asked about this chipset a while back on this list but I didn't see any replies to it. This is my built in card for a Toshiba A10 Satellite notebook. Installing the driver gives: [root@heidrun toshiba-wifi]# ndiswrapper -i WLAGS48B.INF Installing wlags48b no vendor <- this line repeated ~ 23 times Checking out the status shows: [root@heidrun toshiba-wifi]# ndiswrapper -l Installed ndis drivers: wlags48b invalid driver! The files that were installed were only the INF file: [root@heidrun toshiba-wifi]# ls /etc/ndiswrapper/wlags48b/ wlags48b.inf The files in the self extracting windows EXE are: [root@heidrun toshiba-wifi]# ls devpathXP.reg SA10BXWLN.exe WDAGS48B.DLL WLAGS48B.INF DrvUpdt.exe WAAGS48B.DLL wifi.exe WLAGS48B.SYS README.TXT WCAGS48B.EXE wlags48b.cat Since I couldn't get the windows driver to install properly I didn't modprobe the module into the kernel on FC4. [root@heidrun toshiba-wifi]# uname -a Linux heidrun.localdomain 2.6.12-1.1447_FC4 #1 Fri Aug 26 20:29:51 EDT 2005 i686 i686 i386 GNU/Linux So how do I go about fixing up this driver to work with ndiswrapper? Cheers, Chris --=20 PGP Public Key: http://www.nesser.org/pgp-key/ 15:24:32 up 52 min, 2 users, load average: 0.55, 0.37, 0.34 |
From: Giridhar P. <gi...@lm...> - 2005-09-07 14:02:50
|
Christopher Ness wrote: > the "List". Someone else asked about this chipset a while back on this > list but I didn't see any replies to it. This is my built in card for = a > Toshiba A10 Satellite notebook. Usually no-reply means not enough information is given or same/similar question answered before. Provide web link for the driver. And give at least ndiswrapper version. > wlags48b invalid driver! This is probably an old INF file without vendor ID. Are you using latest driver available for Windows XP/NT/2000? > So how do I go about fixing up this driver to work with ndiswrapper? If this driver is not reported to work, it likely won't. You need to supp= ly useful debug trace (see Wiki on Bugs) in that case. Giri |
From: Christopher N. <ch...@ne...> - 2005-09-07 14:51:53
|
On Wed, 2005-09-07 at 10:08 -0400, Giridhar Pemmasani wrote: > Christopher Ness wrote: > > the "List". Someone else asked about this chipset a while back on this > > list but I didn't see any replies to it. This is my built in card for = a > > Toshiba A10 Satellite notebook. >=20 > Usually no-reply means not enough information is given or same/similar > question answered before. That's why I mentioned the unanswered question above. I wanted the list to know I did some digging before asking for help. > Provide web link for the driver. And give at least ndiswrapper version. ndiswrapper-1.3rc1 The driver is the latest for this card from the Toshiba support site. Since this is a 2 year old laptop the card isn't bleeding edge and is only 802.11b. You can get the .exe file from toshiba or from my site: http://www.nesser.org/pub/toshiba-wifi/ The README.TXT file identifies it as: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Agere Systems May 2002 NDIS 5 Miniport Driver for Microsoft Windows XP Variant 2 Version: 7.62 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > wlags48b invalid driver! >=20 > This is probably an old INF file without vendor ID. Are you using latest > driver available for Windows XP/NT/2000? >=20 > > So how do I go about fixing up this driver to work with ndiswrapper? >=20 > If this driver is not reported to work, it likely won't. You need to supp= ly > useful debug trace (see Wiki on Bugs) in that case. Let me see if I understand how ndiswrapper works. I need to install the windows binaries using the -i flag. Does it matter if the kernel module is loaded or not at this point? Could the 4KSTACKS of my kernel be causing these errors with installing the driver? I'd like to ask before I go about recompiling the kernel. [root@heidrun ndiswrapper-1.3rc1]# grep CONFIG_4KSTACKS /boot/config-2.6.12= -1.1447_FC4 CONFIG_4KSTACKS=3Dy I can't really give a good bug report yet as I haven't even loaded the kernel module. I just am trying to get the installation of the windows drivers to work successfully for now. Thanks for the help Giri, Chris --=20 PGP Public Key: http://www.nesser.org/pgp-key/ 10:26:03 up 28 min, 4 users, load average: 0.67, 0.40, 0.30 |
From: Daniel R. <dan...@in...> - 2005-09-07 15:45:14
|
I would like to comment on this one: Christopher Ness wrote: >On Wed, 2005-09-07 at 10:08 -0400, Giridhar Pemmasani wrote: > > >>Christopher Ness wrote: >> >> >>>the "List". Someone else asked about this chipset a while back on this >>>list but I didn't see any replies to it. This is my built in card for a >>>Toshiba A10 Satellite notebook. >>> >>> >>Usually no-reply means not enough information is given or same/similar >>question answered before. >> In fact it looks like *most* of the posts in this list get no answers. In the (recent) past I tried also to get some help from this list to install NDISwrapper, without success as well. I am involved in freeware since quite some years, and always have been so happy to find friendly support from the freeware community. I must confess that I felt very sorry that I could'nt even *install* NDISwrapper after literally days of hard trying, kernal crashes, and with no help from others (although my configuration had nothing special: fedora core 4 and a MA111 USB). Would you like to know what I did? I am very sorry to confess this: I bought driverloader, and my system ran in just a few minutes. Again, I really support freeware, GNU and the rest, and again, I stay sorry that I was not able to use successfully NDISwrapper. Well, I bet that I am not alone! Have a good time Daniel |
From: Jonas P. <za...@xm...> - 2005-09-07 16:34:35
|
Daniel Ranc wrote: > I would like to comment on this one: > Christopher Ness wrote: >> On Wed, 2005-09-07 at 10:08 -0400, Giridhar Pemmasani wrote: >>> Usually no-reply means not enough information is given or same/similar >>> question answered before. >>> > In fact it looks like *most* of the posts in this list get no answers. > In the (recent) past I tried also to get some help from this list to > install NDISwrapper, without success as well. I am involved in freeware > since quite some years, and always have been so happy to find friendly > support from the freeware community. It appears that ndiswrapper is still not quite for the average user. My personal experince is that when it works it works great, and when it fails it is rather tricky to track down the problem - hardly suprising considering what it does. As a Gentoo user with a recent 2.6 kernel it "just works" (from a kernel module perspective that is, getting the appropriate driver may or may not be an adventure) - even together with SwSuspend2, but with Debian and 2.4 I had less luck. When I had an odd (possibly broken) Belkin card, I found very little information that could help me - the user who put information about his success on the wiki was impossible to get hold of. YMMV. I suspect that few users stay on the list after they got their system to work. > I must confess that I felt very > sorry that I could'nt even *install* NDISwrapper after literally days of > hard trying, kernal crashes, and with no help from others (although my > configuration had nothing special: fedora core 4 and a MA111 USB). > Would you like to know what I did? I am very sorry to confess this: I > bought driverloader, and my system ran in just a few minutes. Again, I > really support freeware, GNU and the rest, and again, I stay sorry that > I was not able to use successfully NDISwrapper. Well, I bet that I am > not alone! Well, I used LinuxAnt's stuff under 2.4 (I still have the license I paid for), but IMHO ndiswrapper works better. I even tried LinuxAnt with my troublesome Belkin card, but at least under Gentoo it was harder to install (but then emerge is VERY clever) and in the end it didn't work any better (since the problem was with either the driver or the HW - both of which were the same). Still, you may be right in that ndiswrapper is not quite mainstream yet - when driverloader works for you, you pay to get their support really. Over here you may be lucky to get something better for free - or you might not... / Jonas -- Jonas Petersson | XMS Penvision | mailto:Jon...@xm... Box 3294, Västgötegatan 13, S-600 03 Norrköping | http://www.xms.se/ Tel: +46 11 400 13 00 | Dir: +46 11 400 13 05 | Fax: +46 11 10 30 50 |
From: Giridhar P. <gi...@lm...> - 2005-09-07 17:13:09
|
On Wed, 07 Sep 2005 17:44:42 +0200, Daniel Ranc <dan...@in...> said: Daniel> help from others (although my configuration had nothing Daniel> special: fedora core 4 and a MA111 USB). Would you like to You need to identify chipset, not card - I don't have all cards to figure out what chipset is in them. If it is MA111v2, I guess it contains SIS163 chipset, which doesn't work with ndiswrapper yet (there is lot of work going on in DEVEL branch for this). And mailing list/forums have many messages on this subject. If it is MA111v1, it contains Prism1, which is supported by open source driver. Daniel> know what I did? I am very sorry to confess this: I bought Daniel> driverloader, and my system ran in just a few Daniel> minutes. Again, I really support freeware, GNU and the rest, Daniel> and again, I stay sorry that I was not able to use Daniel> successfully NDISwrapper. Well, I bet that I am not alone! I don't see why you should be sorry. You use what works for you. ndiswrapper is not competing with Linuxant, as the resources available for ndiswrapper is negligible compared to Linuxant's, what with $20 for each use of their driver - we don't even have one card for each chipset that is _already_ supported. -- Giri |
From: Dominique R. <do...@le...> - 2005-09-08 08:39:43
|
Le Wed, Sep 07, 2005 at 05:44:42PM +0200, Daniel Ranc [daniel.ranc@int-ev= ry.fr] a =E9crit: > >>Usually no-reply means not enough information is given or same/simila= r > >>question answered before. > >> > In fact it looks like *most* of the posts in this list get no answers.=20 [...] > hard trying, kernal crashes, and with no help from others (although my=20 > configuration had nothing special: fedora core 4 and a MA111 USB). This is a perfect example of "answered before". If you look in the list archive, you will see threads about this one around 12/2004 and later, that state that this one doesn't work yet. Look for "ma111", "sis162" or "sis163" to find these. Dom |
From: Giridhar P. <gi...@lm...> - 2005-09-07 17:04:23
|
=46rom PCIID (11C1:AB20), it looks like this is orinoco chipset, for which open source driver (orinoco) should work. If this indeed is orinoco, ndiswrapper won't work with it since this is PCMCIA 16-bit card and not cardbus card. --=20 Giri |
From: Christopher N. <ch...@ne...> - 2005-09-07 17:39:18
|
On Wed, 2005-09-07 at 13:04 -0400, Giridhar Pemmasani wrote: > From PCIID (11C1:AB20), it looks like this is orinoco chipset, for > which open source driver (orinoco) should work. >=20 > If this indeed is orinoco, ndiswrapper won't work with it since this > is PCMCIA 16-bit card and not cardbus card. Yes, it is a PCMCIA card. And I am currently using the orinoco drivers, but it does not support scanning or many other features I was hoping the windows drivers would support. Thanks for your time. I guess I was barking up the wrong tree and should try the latest orinoco drivers. Regards, Chris --=20 PGP Public Key: http://www.nesser.org/pgp-key/ 13:37:23 up 3:39, 5 users, load average: 0.05, 0.15, 0.08 |