Re: Wireless interface stopped working in Etch
Partial success - the interface is now working! Florian Kulzer wrote: On Mon, Nov 13, 2006 at 11:21:34 +, Chris Lale wrote: [...] Florian Kulzer wrote: [...] It could also be that you are missing some other modules, e.g. some parts of the ieee80211 stack. No ieee80211 packages are installed on either system. I meant the kernel modules for ieee80211. No results when I grep lsmod for '802' or 'ieee'. [..] Diff'ing the output of lsmod [...] Try to compare this for the two cases: lsmod | cut -d -f1 | sort Ah - much neater! fresh install working install 8250_pci8250_pci 8250_pnp8250_pnp ac ac ac97_codec agpgart agpgart autofs4 battery battery binfmt_misc button button crc_ccitt crc_ccitt cs46xx dm_mirror dm_mirror dm_mod dm_mod dm_snapshot dm_snapshot drm e100e100 evdev evdev ext3ext3 fan fan fat fat firmware_class firmware_class floppy floppy gameportgameport generic generic i2c_corei2c_core i2c_piix4 i2c_piix4 ide_coreide_core ide_diskide_disk intel_agp intel_agp ipv6 irdairda irtty_sir irtty_sir jbd jbd lockd looploop lp mbcache mbcache mii mii Module Module mousedevmousedev nfs nfs_acl nls_cp437 nls_cp437 nls_iso8859_1 nls_iso8859_1 nsc_irccnsc_ircc nvram parport parport parport_pc parport_pc pci_hotplug pci_hotplug pcmcia pcmcia pcmcia_core pcmcia_core pcspkr pcspkr piixpiix ppdev processor processor psmouse psmouse rsrc_nonstatic rsrc_nonstatic rt2500 rt2500 rtc rtc savage serio_raw
Re: Wireless interface stopped working in Etch
Update: The card is also working fine with ndiswrapper. The only thing is that I still get errors when I take the interface down: # ifdown eth1 ndiswrapper (set_infra_mode:200): setting operating mode to 2 failed (C0010015) Error for wireless request Set Mode (8B06) : SET failed on device eth1 ; Invalid argument The last two lines are very similar to the error I get with the RT2500 driver. I have removed rt2500-modules-... .deb with dpkg. I have removed the lines pre-up ifconfig eth1 up pre-up iwpriv eth1 set AuthMode=OPEN from /etc/network/interfaces. Yet something still seems to be trying to use 'SET' (possibly 'set AuthMode'?). -- Chris. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Wireless interface stopped working in Etch
On Mon, Nov 13, 2006 at 11:21:34 +, Chris Lale wrote: Hello Florian. Here are the answers to your questions and suggestions. I would be grateful for any other thoughts you might have. Florian Kulzer wrote: On Fri, Nov 10, 2006 at 20:46:11 +, Chris Lale wrote: [...] [...] I have begun again with a new fresh install, so the wireless interface has been autmatically named 'eth1'. I have not changed it to 'wlan0' this time. The interface on the working system remains 'wlan0'. dmesg reports this when the wireless pccard is ejected and reinserted (identical on both systems): pccard: card ejected from slot 0 ACPI: PCI interrupt for device :02:00.0 disabled pccard: Cardbus card inserted into slot 0 PCI: Enabling device :02:00.0 ( - 0002) ACPI: PCI Interrupt :02:00.0[A] - Link [LNKA] -. GSI 11 (level, low) - IRQ 11 rt2500 1.1.0 CVS 2005/07/10 http://rt2x00.serialmonkey.com PCI: Seting latency timer of device :02:00.0 to 64 dmesg | egrep 'eth1|rt2500' gives this (identical on both systems): rt2500 1.1.0 CVS 2005/07/10 http://rt2x00.serialmonkey.com rt2500 1.1.0 CVS 2005/07/10 http://rt2x00.serialmonkey.com Are you able to set ESSID and key with iwconfig directly? Yes. iwconfig initially shows this (identical on both systems): RT2500 Wireless ESSID: [...] Encryption key:off Link Quality-0/100 Signal level=-120dBm Noise level:-256 dBm [...] After 'iwconfig eth1 essid solarsystem', and 'iwconfig eth1 key restricted 1234567890' iwconfig reports this (identical on both systems): RT2500 Wireless ESSID:solarsystem [...] Encryption key:1234-5678-90 Security mode:restricted Link Quality-0/100 Signal level=-120dBm Noise level:-256 dBm [...] So, it seems that the signal is not yet detected, and there is no link yet. (Later, after bringing up the interface on the working system, the signal level is reported as being around -77dBm.) Does the card associate with the access point? Can you detect the beacon of the AP with iwlist wlan0 scan? Any error messages? No, not at this point. 'iwlist eth1 scan' issued repeatedly on either system always gives eth1No scan results If I bring up the interface on the working system with 'ifconfig wlan0 up, these appear in dmesg: spurious 8529A interrupt: IRQ15 (Link and Tx/Rx interface leds both light up) wlan0: no IPv6 routers present Issuing 'iwlist wlan0 scan' repeatedly gives a list of local APs, with mine always in Cell 01 and showing the signal level and that there is a link eg Quality:62/100 Signal level:-77dBm Noise level:-195dBm If I bring up the interface on the fresh install with 'ifconfig eth1 up', no leds light up and only this message appears in dmesg: spurious 8529A interrupt: IRQ15. If I issue 'iwlist eth1 scan' at intervals of a second or more, I still get eth1No scan results However, if I do 'iwlist eth1 scan' twice in quick succession, I get a list of various cells identifying neighbouring APs including my own (solarsystem). 'iwconfig' still shows no link. If I take down the interface on either system (eg with 'ifconfig eth1 down'), 'iwlist eth1 scan' or 'iwlist wlan0 scan' report the first few cells (excluding my own) regardless of the interval between commands. My /etc/network/interfaces file has this added to it (identical on both systems apart from the interface name): iface eth1 inet static address 192.168.1.5 netmask 255.255.255.0 gateway 192.168.1.1 wireless-essid solarsystem wireless-key 1234567890 On the fresh install after 'ifup eth1', repeatedly issuing 'iwlist eth1 scan' sometimes reports 'No scan results',sometimes a number of cells including my own, sometimes a number of cells excluding my own. 'iwconfig' shows that there is still no link. It could also be that you are missing some other modules, e.g. some parts of the ieee80211 stack. No ieee80211 packages are installed on either system. I meant the kernel modules for ieee80211. You could try if the driver works with WEP/WPA disabled at the AP. Disabling WEP/WPA on the AP and setting encryption key off makes no difference. Diff'ing the output of lsmod A diff of lsmod shows the modules in a different order on each system. I ran sort on the result of each lsmod and looked at the result with comm. The 1st column shows lines unique to the fresh install, the 2nd column shows lines unique to the working install and the 3rd column shows lines common to both: [ snip - I really cannot read that table... ] Try to compare this for the two cases: lsmod | cut -d -f1 | sort Is there a way of finding out what causes a particular module to be loaded? and the kernel configuration for both cases might be helpful, too. The kernel configuration files are identical according to both
Re: Wireless interface stopped working in Etch
Hello Florian. Here are the answers to your questions and suggestions. I would be grateful for any other thoughts you might have. Florian Kulzer wrote: On Fri, Nov 10, 2006 at 20:46:11 +, Chris Lale wrote: [...] It seems that the kernel modules are different. lsmod reports what looks like a difference in size: original system: rt2500 149988 1 fresh install: rt2500 151748 1 Is it possible to copy the module over from the original system to the new system? Which files are involved? The file should be called rt2500.ko and it will be somewhere in /lib/modules/kernel-version/kernel/drivers/net/ or thereabouts. If you run dpkg-deb --contents on the .deb file that you generated with module-assistant you will get a listing of all file locations. I am not sure if the other kernel will let you load the module since the version magic string will probably not match. (see /sbin/modinfo rt2500 | grep vermagic) I don't now think that the problem lies with the rt2500 module produced by module assistant from the rt2500-source package. The rt2500 modules seem identical on the working system and the fresh install. They have the same file size and the same magic string 2.6.17-2-686 SMP mod_unload 686 REGPARM gcc-4.1. I copied rt2500.ko from the working install to the fresh install. It did not object, but it did not solve the problem either. I would first poke at a few other things: dmesg | egrep 'wlan0|rt2500' I have begun again with a new fresh install, so the wireless interface has been autmatically named 'eth1'. I have not changed it to 'wlan0' this time. The interface on the working system remains 'wlan0'. dmesg reports this when the wireless pccard is ejected and reinserted (identical on both systems): pccard: card ejected from slot 0 ACPI: PCI interrupt for device :02:00.0 disabled pccard: Cardbus card inserted into slot 0 PCI: Enabling device :02:00.0 ( - 0002) ACPI: PCI Interrupt :02:00.0[A] - Link [LNKA] -. GSI 11 (level, low) - IRQ 11 rt2500 1.1.0 CVS 2005/07/10 http://rt2x00.serialmonkey.com PCI: Seting latency timer of device :02:00.0 to 64 dmesg | egrep 'eth1|rt2500' gives this (identical on both systems): rt2500 1.1.0 CVS 2005/07/10 http://rt2x00.serialmonkey.com rt2500 1.1.0 CVS 2005/07/10 http://rt2x00.serialmonkey.com Are you able to set ESSID and key with iwconfig directly? Yes. iwconfig initially shows this (identical on both systems): RT2500 Wireless ESSID: [...] Encryption key:off Link Quality-0/100 Signal level=-120dBm Noise level:-256 dBm [...] After 'iwconfig eth1 essid solarsystem', and 'iwconfig eth1 key restricted 1234567890' iwconfig reports this (identical on both systems): RT2500 Wireless ESSID:solarsystem [...] Encryption key:1234-5678-90 Security mode:restricted Link Quality-0/100 Signal level=-120dBm Noise level:-256 dBm [...] So, it seems that the signal is not yet detected, and there is no link yet. (Later, after bringing up the interface on the working system, the signal level is reported as being around -77dBm.) Does the card associate with the access point? Can you detect the beacon of the AP with iwlist wlan0 scan? Any error messages? No, not at this point. 'iwlist eth1 scan' issued repeatedly on either system always gives eth1No scan results If I bring up the interface on the working system with 'ifconfig wlan0 up, these appear in dmesg: spurious 8529A interrupt: IRQ15 (Link and Tx/Rx interface leds both light up) wlan0: no IPv6 routers present Issuing 'iwlist wlan0 scan' repeatedly gives a list of local APs, with mine always in Cell 01 and showing the signal level and that there is a link eg Quality:62/100 Signal level:-77dBm Noise level:-195dBm If I bring up the interface on the fresh install with 'ifconfig eth1 up', no leds light up and only this message appears in dmesg: spurious 8529A interrupt: IRQ15. If I issue 'iwlist eth1 scan' at intervals of a second or more, I still get eth1No scan results However, if I do 'iwlist eth1 scan' twice in quick succession, I get a list of various cells identifying neighbouring APs including my own (solarsystem). 'iwconfig' still shows no link. If I take down the interface on either system (eg with 'ifconfig eth1 down'), 'iwlist eth1 scan' or 'iwlist wlan0 scan' report the first few cells (excluding my own) regardless of the interval between commands. My /etc/network/interfaces file has this added to it (identical on both systems apart from the interface name): iface eth1 inet static address 192.168.1.5 netmask 255.255.255.0 gateway 192.168.1.1 wireless-essid solarsystem wireless-key 1234567890 On the fresh install after 'ifup eth1', repeatedly issuing 'iwlist eth1 scan' sometimes reports 'No scan results',sometimes a number of cells including my own, sometimes a number of cells excluding my own.
Re: Wireless interface stopped working in Etch
Florian Kulzer wrote: [...] On Fri, Nov 10, 2006 at 20:46:11 +, Chris Lale wrote: Is it possible to copy the module over from the original system to the new system? Which files are involved? The file should be called rt2500.ko and it will be somewhere in /lib/modules/kernel-version/kernel/drivers/net/ or thereabouts. If you run dpkg-deb --contents on the .deb file that you generated with module-assistant you will get a listing of all file locations. I am not sure if the other kernel will let you load the module since the version magic string will probably not match. (see /sbin/modinfo rt2500 | grep vermagic) I would first poke at a few other things: dmesg | egrep 'wlan0|rt2500' Are you able to set ESSID and key with iwconfig directly? Does the card associate with the access point? Can you detect the beacon of the AP with iwlist wlan0 scan? Any error messages? It could also be that you are missing some other modules, e.g. some parts of the ieee80211 stack. You could try if the driver works with WEP/WPA disabled at the AP. Diff'ing the output of lsmod and the kernel configuration for both cases might be helpful, too. Thanks very much Florian. Looks like I've got plenty to look at this weekend! -- Chris. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Wireless interface stopped working in Etch
My Edimax EW-7108pcg PCMCIA wifi card (rt2500 driver) works perfectly in my constantly upgraded version of Etch (Testing). I installed the rt2500 driver some weeks ago. The same driver, built in the same way, will not work in a fresh install of Etch in a new partition on the same machine (Thinkpad T20). In both cases I built the rt2500 module from the rt2500-source package using module assistant. The resulting modules package was the same version: rt2500-modules-2.6.17-2-686 version 1.1.0+cvs20060620-3+2.6.17-9 On the fresh install I have also tried the rt2x00 module. On the fresh install I have also tried ndswrapper for the Edimax card and another card (D-Link DWL-G650), but no luck. The interface will not come up (using ifup). With the rt2500 module, the card is detected and the rt2500 module loads OK in both cases. The only difference that I can find between the two systems is that the name allocated to the wireless interface is different. On the working system, the command iwconfig gives wlan0 for the wireless interface: lo no wireless extensions. eth0 no wireless extensions. irda0 no wireless extensions. wlan0RT2500 Wireless ESSID:essid-of-my-modem/router [...] sit0 no wireless extensions. On the fresh install, the interface's name has been changed from wlan0 to eth1. (Also, irda0 and sit0 are not detected): lo no wireless extensions. eth0 no wireless extensions. eth1 RT2500 Wireless ESSID: [...] When I installed ndiswrapper on the fresh install, the wireless interface appeared as wlan0_rename lo no wireless extensions. eth0 no wireless extensions. wlan0_rename RT2500 Wireless ESSID: [...] Does anyone know what might be causing the wireless interface to have different names on the fresh install of Etch? Any suggestions gratefully received. -- Chris. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Wireless interface stopped working in Etch
On Fri, Nov 10, 2006 at 16:38:50 +, Chris Lale wrote: My Edimax EW-7108pcg PCMCIA wifi card (rt2500 driver) works perfectly in my constantly upgraded version of Etch (Testing). I installed the rt2500 driver some weeks ago. The same driver, built in the same way, will not work in a fresh install of Etch in a new partition on the same machine (Thinkpad T20). In both cases I built the rt2500 module from the rt2500-source package using module assistant. The resulting modules package was the same version: rt2500-modules-2.6.17-2-686 version 1.1.0+cvs20060620-3+2.6.17-9 On the fresh install I have also tried the rt2x00 module. On the fresh install I have also tried ndswrapper for the Edimax card and another card (D-Link DWL-G650), but no luck. The interface will not come up (using ifup). With the rt2500 module, the card is detected and the rt2500 module loads OK in both cases. The only difference that I can find between the two systems is that the name allocated to the wireless interface is different. On the working system, the command iwconfig gives wlan0 for the wireless interface: lo no wireless extensions. eth0 no wireless extensions. irda0 no wireless extensions. wlan0RT2500 Wireless ESSID:essid-of-my-modem/router [...] sit0 no wireless extensions. On the fresh install, the interface's name has been changed from wlan0 to eth1. (Also, irda0 and sit0 are not detected): lo no wireless extensions. eth0 no wireless extensions. eth1 RT2500 Wireless ESSID: [...] When I installed ndiswrapper on the fresh install, the wireless interface appeared as wlan0_rename lo no wireless extensions. eth0 no wireless extensions. wlan0_rename RT2500 Wireless ESSID: [...] Does anyone know what might be causing the wireless interface to have different names on the fresh install of Etch? Any suggestions gratefully received. The usual suspect for issues with the names of network devices is /etc/udev/rules.d/z25_persistent-net.rules. As far as the general problem with the device is concerned: It seems that eth1 in the new install is accepted as a wireless network device, so it should work. Did you adjust the data in /etc/network/interfaces to match the new name of the device? Ifup needs this information to set the ESSID, encryption key, etc. -- Regards, Florian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Wireless interface stopped working in Etch
Florian Kulzer wrote: On Fri, Nov 10, 2006 at 16:38:50 +, Chris Lale wrote: My Edimax EW-7108pcg PCMCIA wifi card (rt2500 driver) works perfectly in my constantly upgraded version of Etch (Testing). I installed the rt2500 driver some weeks ago. The same driver, built in the same way, will not work in a fresh install of Etch in a new partition on the same machine (Thinkpad T20). In both cases I built the rt2500 module from the rt2500-source package using module assistant. The resulting modules package was the same version: rt2500-modules-2.6.17-2-686 version 1.1.0+cvs20060620-3+2.6.17-9 On the fresh install I have also tried the rt2x00 module. On the fresh install I have also tried ndswrapper for the Edimax card and another card (D-Link DWL-G650), but no luck. The interface will not come up (using ifup). With the rt2500 module, the card is detected and the rt2500 module loads OK in both cases. The only difference that I can find between the two systems is that the name allocated to the wireless interface is different. On the working system, the command iwconfig gives wlan0 for the wireless interface: lo no wireless extensions. eth0 no wireless extensions. irda0 no wireless extensions. wlan0RT2500 Wireless ESSID:essid-of-my-modem/router [...] sit0 no wireless extensions. On the fresh install, the interface's name has been changed from wlan0 to eth1. (Also, irda0 and sit0 are not detected): lo no wireless extensions. eth0 no wireless extensions. eth1 RT2500 Wireless ESSID: [...] When I installed ndiswrapper on the fresh install, the wireless interface appeared as wlan0_rename lo no wireless extensions. eth0 no wireless extensions. wlan0_rename RT2500 Wireless ESSID: [...] Does anyone know what might be causing the wireless interface to have different names on the fresh install of Etch? Any suggestions gratefully received. The usual suspect for issues with the names of network devices is /etc/udev/rules.d/z25_persistent-net.rules. As far as the general problem with the device is concerned: It seems that eth1 in the new install is accepted as a wireless network device, so it should work. I think you must be right - this is not the problem. I substituted wlan0 for eth1 in /etc/udev/rules.d/z25_persistent-net.rules and rebooted (there must be a better way). iwconfig now reported wlan0. I also modified /etc/network/interfaces, substituting wlan0 for eth0, but the interface still would not work. Did you adjust the data in /etc/network/interfaces to match the new name of the device? Ifup needs this information to set the ESSID, encryption key, etc. Yes, this all looks OK: iface wlan0 inet static address 192.168.1.3 netmask 255.255.255.0 gateway 192.168.1.1 wireless-essid solarsystem wireless-key 0123456789 It seems that the kernel modules are different. lsmod reports what looks like a difference in size: original system: rt2500 149988 1 fresh install: rt2500 151748 1 Is it possible to copy the module over from the original system to the new system? Which files are involved? -- Chris. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Wireless interface stopped working in Etch
On Fri, Nov 10, 2006 at 20:46:11 +, Chris Lale wrote: Florian Kulzer wrote: On Fri, Nov 10, 2006 at 16:38:50 +, Chris Lale wrote: My Edimax EW-7108pcg PCMCIA wifi card (rt2500 driver) works perfectly in my constantly upgraded version of Etch (Testing). I installed the rt2500 driver some weeks ago. The same driver, built in the same way, will not work in a fresh install of Etch in a new partition on the same machine (Thinkpad T20). In both cases I built the rt2500 module from the rt2500-source package using module assistant. The resulting modules package was the same version: rt2500-modules-2.6.17-2-686 version 1.1.0+cvs20060620-3+2.6.17-9 [...] With the rt2500 module, the card is detected and the rt2500 module loads OK in both cases. The only difference that I can find between the two systems is that the name allocated to the wireless interface is different. On the working system, the command iwconfig gives wlan0 for the wireless interface: lo no wireless extensions. eth0 no wireless extensions. irda0 no wireless extensions. wlan0RT2500 Wireless ESSID:essid-of-my-modem/router [...] sit0 no wireless extensions. On the fresh install, the interface's name has been changed from wlan0 to eth1. (Also, irda0 and sit0 are not detected): lo no wireless extensions. eth0 no wireless extensions. eth1 RT2500 Wireless ESSID: [...] [...] Does anyone know what might be causing the wireless interface to have different names on the fresh install of Etch? Any suggestions gratefully received. The usual suspect for issues with the names of network devices is /etc/udev/rules.d/z25_persistent-net.rules. As far as the general problem with the device is concerned: It seems that eth1 in the new install is accepted as a wireless network device, so it should work. I think you must be right - this is not the problem. I substituted wlan0 for eth1 in /etc/udev/rules.d/z25_persistent-net.rules and rebooted (there must be a better way). iwconfig now reported wlan0. I also modified /etc/network/interfaces, substituting wlan0 for eth0, but the interface still would not work. Did you adjust the data in /etc/network/interfaces to match the new name of the device? Ifup needs this information to set the ESSID, encryption key, etc. Yes, this all looks OK: iface wlan0 inet static address 192.168.1.3 netmask 255.255.255.0 gateway 192.168.1.1 wireless-essid solarsystem wireless-key 0123456789 It seems that the kernel modules are different. lsmod reports what looks like a difference in size: original system: rt2500 149988 1 fresh install: rt2500 151748 1 Is it possible to copy the module over from the original system to the new system? Which files are involved? The file should be called rt2500.ko and it will be somewhere in /lib/modules/kernel-version/kernel/drivers/net/ or thereabouts. If you run dpkg-deb --contents on the .deb file that you generated with module-assistant you will get a listing of all file locations. I am not sure if the other kernel will let you load the module since the version magic string will probably not match. (see /sbin/modinfo rt2500 | grep vermagic) I would first poke at a few other things: dmesg | egrep 'wlan0|rt2500' Are you able to set ESSID and key with iwconfig directly? Does the card associate with the access point? Can you detect the beacon of the AP with iwlist wlan0 scan? Any error messages? It could also be that you are missing some other modules, e.g. some parts of the ieee80211 stack. You could try if the driver works with WEP/WPA disabled at the AP. Diff'ing the output of lsmod and the kernel configuration for both cases might be helpful, too. -- Regards, Florian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Wireless interface not working
Werner Otto [EMAIL PROTECTED] writes: Sorry for the scrappy info: I am running the testing version of Debian. lspci Network controller: Intel Corp. PRO/Wireless 2200BG (rev 05) as for the wireless tools, I have been searching for a source to add to my sources.list file to obtain the wireless tools iwconfig. Maybe this would be my first step. You might want to look at the following sites for more information: http://ipw2200.sourceforge.net/ I have not tried this, so i do not know how it works. the ipw2100 module works. so I assume this one works too. http://ndiswrapper.sourceforge.net/ This approach uses the windows drivers. Both methods will require a compilation of kernel modules. You might want to lookup kernel-package to compile kernel modules the debian way. apt-cache show kernel-package -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Wireless interface not working
Sorry for the scrappy info: I am running the testing version of Debian. lspci Network controller: Intel Corp. PRO/Wireless 2200BG (rev 05) as for the wireless tools, I have been searching for a source to add to my sources.list file to obtain the wireless tools iwconfig. Maybe this would be my first step. On Fri, 15 Oct 2004 11:46:47 +0100, Ruairi Newman [EMAIL PROTECTED] wrote: Hi, Coud we have a little more information? What wireless chipset is in your laptop? What have you tried so far? Are you running stable, testing or unstable? Regards, R. On Fri, 15 Oct 2004 11:16:58 +0100, Werner Otto [EMAIL PROTECTED] wrote: I installed debina on my Dell Latitide D505. I am unable to get my wireless working. Can someone please lead me in the right direction. -- Kind Regards Werner Otto 07818298666 02087423424 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Wireless interface not working
On Sat, Oct 16, 2004 at 03:17:34PM +0100, Werner Otto wrote: as for the wireless tools, I have been searching for a source to add to my sources.list file to obtain the wireless tools iwconfig. Maybe this would be my first step. How about any Debian mirror? From packages.debian.org: Package wireless-tools * stable (net): Tools for manipulating Linux Wireless Extensions 23-2: alpha arm hppa i386 ia64 m68k mips mipsel powerpc s390 sparc * testing (net): Tools for manipulating Linux Wireless Extensions 26+27pre25-2: alpha arm hppa i386 ia64 m68k mips mipsel powerpc s390 sparc * unstable (net): Tools for manipulating Linux Wireless Extensions 26+27pre26-2: alpha arm hppa i386 ia64 m68k mips mipsel powerpc s390 sparc -- Carl Fink [EMAIL PROTECTED] Jabootu's Minister of Proofreading http://www.jabootu.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Wireless interface not working
Hi All, I installed debina on my Dell Latitide D505. I am unable to get my wireless working. Can someone please lead me in the right direction. -- Kind Regards Werner Otto -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Wireless interface not working
Hi, Coud we have a little more information? What wireless chipset is in your laptop? What have you tried so far? Are you running stable, testing or unstable? Regards, R. On Fri, 15 Oct 2004 11:16:58 +0100, Werner Otto [EMAIL PROTECTED] wrote: I installed debina on my Dell Latitide D505. I am unable to get my wireless working. Can someone please lead me in the right direction. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Wireless interface not working
On Fri, 15 Oct 2004, Werner Otto wrote: I installed debina on my Dell Latitide D505. I am unable to get my wireless working. Can someone please lead me in the right direction. we'd need more info if we do not have that dell box to do your homework for yoou - what is the output of lspci - what tools dis oyu use to try to get wireless working - what version of iwconfig tools - what and where is your wireless config files - what commands were issued - was the wireless card recognized during bootup more fun(boring) reading on config'g your fav wl cards http://Linux-Wireless.Org c ya alvin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Wireless interface not working
On Fri, Oct 15, 2004 at 11:16:58AM +0100, Werner Otto wrote: I installed debina on my Dell Latitide D505. I am unable to get my wireless working. To add to what others posted, did you install the wireless tools? What's the output of iwconfig? What kernel version are you running? Have you read http://www.catb.org/~esr/faqs/smart-questions.html ? -- Carl Fink [EMAIL PROTECTED] Jabootu's Minister of Proofreading http://www.jabootu.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
