ianw1974 Posted February 15, 2006 Report Share Posted February 15, 2006 Hi Arne, Sent you a pm with a few email addys in, and also a newly created one which might actually work better than the webmail ones. It could be that the webmail ones got filtered or something, because of anti-virus software, or other reasons and didn't allow the .exe to get through. Or maybe not. The relay error normally means you aren't authenticated to use the smtp server your trying to send via. Send me a private message if any problems, will keep the post clean then for other stuff. Quote Link to comment Share on other sites More sharing options...
Arne Posted February 15, 2006 Author Report Share Posted February 15, 2006 ops.... That was to fast i believe. Please check Quote Link to comment Share on other sites More sharing options...
Qchem Posted February 15, 2006 Report Share Posted February 15, 2006 Thanks Qchem.her is the line 05:00.0 Class 0280: 1814:0201 (rev 01) OK, I've found that chipset on the ndiswrapper database, someone has got it working with ndiswrapper 0.9 and the RT2500 drivers for XP (the .inf and .sys) from ftp://ftp.a-link.com/wl54h/WL54driver2.2.6.0.zip Someone else with the same chipset mentions that the win2k drivers from the same zip are more stable. Quote Link to comment Share on other sites More sharing options...
Arne Posted February 15, 2006 Author Report Share Posted February 15, 2006 Sent it to your last address. Hopefully OK. Quote Link to comment Share on other sites More sharing options...
ianw1974 Posted February 15, 2006 Report Share Posted February 15, 2006 Hi Arne, Yes, got the email :P However, this file is the adobe reader. Are there any other files? List them here, and I'll let you know which one we need. See qchem's post above, seems there are some drivers, so will save you emailing them to me. If they fail, list the files and then we can get them sent over to me. Quote Link to comment Share on other sites More sharing options...
Arne Posted February 15, 2006 Author Report Share Posted February 15, 2006 Qchem, Many thank's for your effort. This is very good news. I have downloaded already Does it mean that ndiswrapper 1.9 cannot be used but version 0.9 is OK Ian, anyway her is the other files: setup.exe 3.6MB start.exe 3.2MB Rt25009x.sys 206.8KB Rt2500.sys 206.1KB Quote Link to comment Share on other sites More sharing options...
Qchem Posted February 15, 2006 Report Share Posted February 15, 2006 Does it mean that ndiswrapper 1.9 cannot be used but version 0.9 is OK It probably just means that was the version the person used at the time. I would expect it to work with all later versions. Quote Link to comment Share on other sites More sharing options...
ianw1974 Posted February 16, 2006 Report Share Posted February 16, 2006 I find it funny that the .sys files are already extracted but no .inf file with them. I presume the setup.exe has more files within it or something. Not sure what the start.exe is, probably some sort of front-end gui screen to choose the installer from. Try the link from qchem, if you have real problems, give me a shout, and we'll try the setup.exe Quote Link to comment Share on other sites More sharing options...
Arne Posted February 16, 2006 Author Report Share Posted February 16, 2006 It's time for a summary. 1. Upgraded kernel to 'kernel-i586-up-1GB-2.6.12.15' 2. Installed 'kernel-source-2.6-2.6.12-15mdk.i586.rpm 3. Link to kernel-source established with 'ln -s /usr/src/linux-<kernel-version> /lib/modules/VERSION/build' 4. Deleted default ndiswrapper with urpme and downloaded and installed latest version 1.9 5. Check that 'wireless-tools' is installed 6. Downloaded 'WL54driver2.2.6.0.zip' from a link thankfully provided by Qchem. 7. Extracted the 'INF and the SYS, from 'win2k' directory on the driver file, to a separat directory. 8. Go to the separat directory and run 'ndiswrapper -i Rt2500.INF' 9. Run 'ndiswrapper -l' and get 'Installed ndis drivers: rt2500 driver present, hardware present' 10. Run 'ndiswrapper -m' and get: [root@ast2 arne]# cat /etc/modprobe.confinstall scsi_hostadapter /sbin/modprobe ata_piix; /sbin/modprobe ahci; /bin/true install usb-interface /sbin/modprobe uhci-hcd; /bin/true alias wlan0 ndiswrapper confirm that the last line is 'alias wlan0 ndiswrapper' 11. Run 'depmod -a' No error messages 12. Run 'modprobe ndiswrapper'. No error meassages 13. Syslog shows 'ndiswrapper version 1.9 loaded'. Which is the version I installed see pkt 4 above 14. I cannot see 'ndiswrapper: driver "rt2500" added in syslog 15. Check cd '/etc/ndiswrapper' and get: [root@ast2 arne]# cd /etc/ndiswrapper[root@ast2 ndiswrapper]# ls rt2500/ [root@ast2 ndiswrapper]# cd rt2500/ [root@ast2 rt2500]# ls 1814:0201:1462:6833.5.conf 1814:0201:185F:12A0.5.conf 1814:0201:1462:6834.5.conf 1814:0201:185F:22A0.5.conf 1814:0201:1462:6835.5.conf 1814:0201:18E8:6146.5.conf 1814:0201:16EF:9140.5.conf 1814:0201:18E8:6151.5.conf 1814:0201:16EF:9220.5.conf 1814:0201.5.conf@ 1814:0201:16EF:9230.5.conf rt2500.inf 1814:0201:1814:2560.5.conf rt2500.sys The 3 last entries is the right 'conf, inf and sys files' 16. Light is not on in the card which it should. Ejecting and reinserting the card don't bring on the light on the card. 17. 'wlan0: ndiswrapper ethernet device xx:xx:xx:xx:xx:xx' do not show up in the syslog. Syslog shows this: Feb 16 13:46:18 ast2 kernel: rt2500: module license 'unspecified' taints kernel.Feb 16 13:46:18 ast2 kernel: PCI: Enabling device 0000:05:00.0 (0000 -> 0002) Feb 16 13:46:18 ast2 kernel: ACPI: PCI Interrupt 0000:05:00.0[A] -> Link [LNKB] -> GSI 9 (level, low) -> IRQ 9 Feb 16 13:46:18 ast2 kernel: PCI: Setting latency timer of device 0000:05:00.0 to 64 Feb 16 13:46:19 ast2 ifplugd(ra0)[4153]: ifplugd 0.28 initializing. Feb 16 13:46:19 ast2 ifplugd(ra0)[4153]: Using interface ra0/00:11:50:90:F7:05 Feb 16 13:46:19 ast2 ifplugd(ra0)[4153]: Using detection mode: IFF_RUNNING Feb 16 13:46:19 ast2 ifplugd(ra0)[4153]: Initialization complete, link beat detected. Feb 16 13:46:19 ast2 ifplugd(ra0)[4153]: Executing '/etc/ifplugd/ifplugd.action ra0 up'. Feb 16 13:46:19 ast2 hal.dev[4156]: DEVNAME is not set Feb 16 13:46:21 ast2 dhclient: DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 5 Feb 16 13:46:26 ast2 dhclient: DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 6 Feb 16 13:46:30 ast2 kernel: ra0: no IPv6 routers present Feb 16 13:46:32 ast2 dhclient: DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 20 Feb 16 13:46:52 ast2 dhclient: DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 12 Feb 16 13:47:04 ast2 dhclient: DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 12 Feb 16 13:47:16 ast2 dhclient: DHCPDISCOVER on ra0 to 255.255.255.255 port 67 interval 6 Feb 16 13:47:22 ast2 dhclient: No DHCPOFFERS received. Feb 16 13:47:22 ast2 ifplugd(ra0)[4153]: client: Determining IP information for ra0... failed. Feb 16 13:47:22 ast2 ifplugd(ra0)[4153]: Program execution failed, return value is 1. Feb 16 13:47:22 ast2 ifplugd(ra0)[4153]: Exiting. 18. Run 'iwconfig' gives: [root@ast2 rt2500]# iwconfiglo no wireless extensions. sit0 no wireless extensions. ra0 RT2500 Wireless ESSID:"" Mode:Auto Frequency=1 MHz Bit Rate:11 Mb/s RTS thr:off Fragment thr:off Encryption key:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 19. Run 'iwlist wlan0 scan' gives ' root@ast2 rt2500]# iwlist wlan0 scanwlan0 Interface doesn't support scanning. 20. Run 'iwconfig wlan0 essid 'ESSID' gives [root@ast2 arne]# iwconfig wlan0 essid 'ESSID'Error for wireless request "Set ESSID" (8B1A) : SET failed on device wlan0 ; No such device. Something is missing and this ra0 stuff I believe is wrong. Quote Link to comment Share on other sites More sharing options...
ianw1974 Posted February 16, 2006 Report Share Posted February 16, 2006 Can you post the output from an ifconfig -a. I want to see if the interface is called wlan0 or something else. Quote Link to comment Share on other sites More sharing options...
Arne Posted February 16, 2006 Author Report Share Posted February 16, 2006 Here it is: [root@ast2 arne]# ifconfig -a lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:560 (560.0 B) TX bytes:560 (560.0 B) ra0 Link encap:Ethernet HWaddr 00:11:50:90:F7:05 inet6 addr: fe80::211:50ff:fe90:f705/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:28 errors:0 dropped:0 overruns:0 frame:0 TX packets:44 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2463 (2.4 KiB) TX bytes:1760 (1.7 KiB) Interrupt:9 Base address:0x4000 sit0 Link encap:IPv6-in-IPv4 NOARP MTU:1480 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Quote Link to comment Share on other sites More sharing options...
Qchem Posted February 16, 2006 Report Share Posted February 16, 2006 your iwconfig output is telling you that the interface is called ra0 Quote Link to comment Share on other sites More sharing options...
ianw1974 Posted February 16, 2006 Report Share Posted February 16, 2006 You will need to change /etc/modprobe.conf so that wlan0 is ra0 instead. This will cause problems otherwise, I had similar with my card!! Mine was ath0, and I had to change modprobe.conf to match this, instead of wlan0. Quote Link to comment Share on other sites More sharing options...
Arne Posted February 16, 2006 Author Report Share Posted February 16, 2006 My /etc/modprobe.conf look like this now alias ra0 rt2500 Quote Link to comment Share on other sites More sharing options...
Arne Posted February 16, 2006 Author Report Share Posted February 16, 2006 What should I change it to????? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.