Re: big problem with TP-LINK WiFi card
On Wed, 14 Mar 2012 02:41:03 +0100, Bernard wrote: > Camaleón wrote: (...) >>> Is this kernel likely to have taken into account the bug that concerns >>> my PCI wireless card ? >>> >>> >> Can't confirm on this, this is "test & try". >> >> > As for the right way to connect to Squeeze-backports, you were entirely > right. As soon as I called the proper apt-get install command, the > install of kernel 3.2.0 did start and proceeded successfully to the end. > Well, it wasn't bootable right away. Indeed, when upgrading from Lenny > to Squeeze, I had choosen to remain with GRUB 1, and, on my > /boot/grub/menu.lst, the lines related to the newly installed 3.2.0 > kernel did not have anything about 'initrd'. I had to manually add the > expected line, and then, after that, the new kernel did boot all right. > > So far, everything seems to work all right with this new kernel... but I > haven't tested everything yet... Good! > HOWEVER, as far as my TP-LINK pci wireless card is concerned, THIS IS > EXACTLY THE SAME THING AS BEFORE ! Connexion is quick and strong, but > it only lasts anytime from 30 seconds to one and a half minute, after > what the system freezes and the only way to get out is to disconnect > mains power ! Then you can open a bug report for that, including the full logs as well as what package versions are you using (wireless-tools and the firmware file for the card, if any). > I can see that newer 3.2.x kernels are available to compile and install > from scatch. But how shall I know which one - if any - has taken into > account and corrected the bug that concerns wireless connexions with my > TP-LINK pci card ? You don't know, you try and test :-) > As for the Squeeze distro with newer kernels that one can boot from a > CD, where - at what url - should I download the iso image to burn ? Not Squeeze, but another distribution of your choice that includes an updated kernel... maybe aptosid, Fedora, openSUSE? Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jjqddf$3nj$5...@dough.gmane.org
Re: big problem with TP-LINK WiFi card
Camaleón wrote: On Mon, 12 Mar 2012 12:37:27 +0100, Bernard wrote: Camaleón wrote: On Sat, 10 Mar 2012 23:33:02 +0100, Bernard wrote: [stuff deleted] If I were to upgrade kernels, which kernel would you recommend ? I'd go for the 3.x branch. Is this kernel likely to have taken into account the bug that concerns my PCI wireless card ? Can't confirm on this, this is "test & try". As for the right way to connect to Squeeze-backports, you were entirely right. As soon as I called the proper apt-get install command, the install of kernel 3.2.0 did start and proceeded successfully to the end. Well, it wasn't bootable right away. Indeed, when upgrading from Lenny to Squeeze, I had choosen to remain with GRUB 1, and, on my /boot/grub/menu.lst, the lines related to the newly installed 3.2.0 kernel did not have anything about 'initrd'. I had to manually add the expected line, and then, after that, the new kernel did boot all right. So far, everything seems to work all right with this new kernel... but I haven't tested everything yet... HOWEVER, as far as my TP-LINK pci wireless card is concerned, THIS IS EXACTLY THE SAME THING AS BEFORE ! Connexion is quick and strong, but it only lasts anytime from 30 seconds to one and a half minute, after what the system freezes and the only way to get out is to disconnect mains power ! I can see that newer 3.2.x kernels are available to compile and install from scatch. But how shall I know which one - if any - has taken into account and corrected the bug that concerns wireless connexions with my TP-LINK pci card ? As for the Squeeze distro with newer kernels that one can boot from a CD, where - at what url - should I download the iso image to burn ? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f5ff72...@teaser.fr
Re: big problem with TP-LINK WiFi card
On Mon, 12 Mar 2012 12:37:27 +0100, Bernard wrote: > Camaleón wrote: >> On Sat, 10 Mar 2012 23:33:02 +0100, Bernard wrote: >>> If I were to upgrade kernels, which kernel would you recommend ? >>> >>> >> I would try with the backports one, as it's easier to install. If that >> also fails, I would compile the latest stable kernel from sources >> available at kernel's site (now 3.2.9). >> >> >> > The only one that I could find on my Squeeze backports is > 3.2.0-0.bpo.1-686-pae > > #apt-get install -s linux-image-3.2.0-0.bpo.1-686-pae (...) > some packages cannot be installed. This may mean that you have requested > something impossible... etc... > The following information could help you : > > The following packages have non satisfied dependances: > linux-image-3.2.0-0.bpo.1-686-pae : depends : linux-base (>=3~) but > 2.6.32-41 will have to be installed > Recommends : firmware-linux-free (>=3~) but 2.6.32.41 will have to > be installed > E: Defectuous packages I wonder if you have properly configured your "sources.list" and priorities to handle backports. Instructions can be found here: http://backports-master.debian.org/Instructions/ Also, better use synaptic, it's easier to see what's needed and what's missing. Anyway, if you are unsure about how "backports" work, I would try first to play with it inside a testing system, such a virtual machine, to avoid breaking things within your current system. > Kernel 2.6.32-41, which I supposedly should install... is the one that > is already running on that system !! Sure, maybe due to your repository priorities. > I guess that I will have to do a new kernel compiling from sources and > headers and installation from scratch. That's another option. > But is it safe to try installing a 3.2 vintage on my system ? What's a "vintage" system? You mean your hardware is old? > Will it take up a lot more RAM ? Compiling? Yes, and also cpu. Compiling is an intesinve task and can take up to hours to complete, depending on your kernel config options and your hardware :-) > The only other 2.6 kernel that I could find is 2.6.33-20 (also to be > installed from scratch). Do you think that it might be safer to test > that one first ? I'd go for the 3.x branch. > Is this kernel likely to have taken into account the bug that concerns > my PCI wireless card ? Can't confirm on this, this is "test & try". Well, you can also try with a LiveCD of any distribution that has an updated kernel, you can load the LiveCD and test your wifi from there, leaving your current installation untouched. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jjl3an$28k$6...@dough.gmane.org
Re: big problem with TP-LINK WiFi card
Camaleón wrote: On Sat, 10 Mar 2012 23:33:02 +0100, Bernard wrote: Camaleón wrote: If I were to upgrade kernels, which kernel would you recommend ? I would try with the backports one, as it's easier to install. If that also fails, I would compile the latest stable kernel from sources available at kernel's site (now 3.2.9). Greetings, The only one that I could find on my Squeeze backports is 3.2.0-0.bpo.1-686-pae #apt-get install -s linux-image-3.2.0-0.bpo.1-686-pae .. some packages cannot be installed. This may mean that you have requested something impossible... etc... The following information could help you : The following packages have non satisfied dependances: linux-image-3.2.0-0.bpo.1-686-pae : depends : linux-base (>=3~) but 2.6.32-41 will have to be installed Recommends : firmware-linux-free (>=3~) but 2.6.32.41 will have to be installed E: Defectuous packages # Kernel 2.6.32-41, which I supposedly should install... is the one that is already running on that system !! I guess that I will have to do a new kernel compiling from sources and headers and installation from scratch. But is it safe to try installing a 3.2 vintage on my system ? Will it take up a lot more RAM ? The only other 2.6 kernel that I could find is 2.6.33-20 (also to be installed from scratch). Do you think that it might be safer to test that one first ? Is this kernel likely to have taken into account the bug that concerns my PCI wireless card ? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f5ddff7.5050...@teaser.fr
Re: big problem with TP-LINK WiFi card
On Sat, 10 Mar 2012 23:33:02 +0100, Bernard wrote: > Camaleón wrote: >> There are many issues reported for system freezes regarding that kernel >> module (ath9k), there is even a documented bug at the Linuxwireless >> site: >> >> http://linuxwireless.org/en/users/Drivers/ath9k/bugs#Hangs_with_PCI_devices_and_SMP_systems >> >> And even on Debian BTS: >> >> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611946 >> >> I would try with an updated kernel. >> >> > Thanks for this information. I might end up updating the kernel, but at > this stage I am still trying to understand what happens and if there is > another way to go around. Installing an updated kernel will not hurt, you can keep the current one (Debian Squeeze stock) and compiling (or installing from backports) a new one. > I also have an ASUS laptop on which I installed Debian Squeeze on a > dual boot together with MSWIN XP. This laptop allows a wireless > connexion, even though nothing was installed other than what already > existed on "MSWIN-XP". Wireless connexions are fully operational, even > though they are often active for hours. I searched about the chipset > used. It appeared to be the same as on the Desktop ! > > lspci on the laptop (the one that works fine) says : > > Atheros Communications Inc. AR928X Wireless Network Adapter (PCI-express > rev 01 This is a PCI-Express based card. > (while on the Desktop where no wireless connexion can operate for any > longer than one or two minutes without system freeze, this is a AR9287 > Wireless Network Adapter, TP-LINK TL-WN751ND) This is a PCI based card. > As stated, both machines are on Squeeze. On the laptop where everything > works fine, kernel is 2.6.32-5-686 (Debian 2.6.32.30), while it is > Debian 2.6.32-41 on the problematic Desktop. The afore mentioned bug was present on PCI cards while not in PCI-Express based cards, maybe that's the difference. *** Hangs with PCI devices and SMP systems This issue was due to a hardware limitation on our PCI devices whereby our device's FIFO queue got filled up and caused a loop. This issue is only present on our 11n PCI devices, its not present on our PCI-express devices nor our legacy 802.11abg devices. *** > I carried a few more tests on the problematic Desktop. I tested 'Wicd' > instead of 'NetworkManager'. (...) The problem is on the kernel module, I can't see how user space tools such can cope with this unless getting an updated kernel/driver. > If I were to upgrade kernels, which kernel would you recommend ? I would try with the backports one, as it's easier to install. If that also fails, I would compile the latest stable kernel from sources available at kernel's site (now 3.2.9). Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jji881$jrs$4...@dough.gmane.org
Re: big problem with TP-LINK WiFi card
Bernard, 10.03.2012: > Camaleón wrote: > >On Fri, 09 Mar 2012 11:08:31 +0100, Bernard wrote: > > > >>Bernard wrote: > >>>Hi to Everyone, > >>> > >>>On the Desktop of my association, there was no wireless card. So, I > >>>purchased one that is said to be Debian compatible. It is a PCI card > >>>TP-LINK > >>>TL-WN751ND > >>> > >>>It is supposedly based on an Atheros chipset AR 9227 > >>> > >>>I plugged it inside the Central Unit on a PCI slot, and then booted the > >>>Debian Squeeze system. > > > >(...) > > > >>P.S. : I carried new tests. As said above, now that my WiFi is > >>configured, every attempt to boot, leads to "freezing" of the system in > >>the middle of gnome start... EXCEPT IF I shutdown my DSL/WiFi box ! As > >>long as no connexion is possible, the system starts all right ; I can > >>see the other WiFi available in the area (I don't have the > >>passwords...). This being said, if I reboot my WiFi connexion on the DSL > >>modem, then, as said before, connexion does happen all right, it seems > >>fully operational, but only for about 45 to 60 seconds, system freezing > >>happens next. My TL-WN751ND card is supposed to work with Debian kernel > >>module ath9k, which is supposed to be loaded with the wireless-tools > >>package, which is alreeady installed. > > > >There are many issues reported for system freezes regarding that > >kernel module (ath9k), there is even a documented bug at the > >Linuxwireless site: > > > >http://linuxwireless.org/en/users/Drivers/ath9k/bugs#Hangs_with_PCI_devices_and_SMP_systems > > > >And even on Debian BTS: > > > >http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611946 > > > >I would try with an updated kernel. > > > >Greetings, > > > Thanks for this information. I might end up updating the kernel, but > at this stage I am still trying to understand what happens and if > there is another way to go around. I also have an ASUS laptop on > which I installed Debian Squeeze on a dual boot together with MSWIN > XP. This laptop allows a wireless connexion, even though nothing was > installed other than what already existed on "MSWIN-XP". Wireless > connexions are fully operational, even though they are often active > for hours. I searched about the chipset used. It appeared to be the > same as on the Desktop ! > > lspci on the laptop (the one that works fine) says : > > Atheros Communications Inc. AR928X Wireless Network Adapter > (PCI-express rev 01 > > (while on the Desktop where no wireless connexion can operate for > any longer than one or two minutes without system freeze, this is a > AR9287 Wireless Network Adapter, TP-LINK TL-WN751ND) > > As stated, both machines are on Squeeze. On the laptop where > everything works fine, kernel is 2.6.32-5-686 (Debian 2.6.32.30), > while it is Debian 2.6.32-41 on the problematic Desktop. > > I carried a few more tests on the problematic Desktop. I tested > 'Wicd' instead of 'NetworkManager'. Even though I had uninstalled > (#apt-get remove --purge) the old Wicd package and re-installed a > new one , it did reckognise my WiFi, but I couldn't get any > connexion: the password did not seem to be accepted ; it said "wrong > password". True enough, this is a "pasphrase", not a key, that was > required, and I had nothing else than a WPA-PSK key, the very same > one that was being reckognized by NM. I tested several times to no > avail. > > I am willing to test 'ifup', but I don't know what I should write in > my /etc/network/interfaces file. I carried a few tests, to no avail. > > I also tested another chip that I have purchased in the same time. > It is a "mini-PCI" wireless card (TP-LINK model TL-WN861N). I had to > purchase a special "mini-pci to pci adaptator" in order to be able > to insert it in a PCI slot in said Desktop. This one is not being > reckognized "out of the box" as the TL-WN751ND was. You must install > 'firmware-atheros' before it gets acknowledged. This one is > supposedly driven by AR922X wireless-network-adapter. But I got > nowhere with this. #iwconfig said that it was on wlan1, but I could > never even see any wireless network with it. I also tested it on > MSWIN, where it seemed reckognized all write after proper > installation with appropriate drivers... but in the end I never got > any connexion ; it seems to be that my DSL box wifi signal was too > weak for this chipset... The other chipset, the one that connects OK > to Debian for a short time before system freeze, works perfectly > under MSWIN. Did you hook up any antenna cable to the mini-pci card? The mini-pci wireless card in my laptop has two antennas running from the base up along the side and top borders of the monitor (within the case). That may be the reason for your card not seeing any signal. (My laptop's from 2004, though, so maybe some newer cards don't need them anymore.) > So, I wonder why an atheros wifi card works so well on a laptop with > Squeeze, and another very closely related Atheros chipset refuses to > work on an
Re: big problem with TP-LINK WiFi card
Camaleón wrote: On Fri, 09 Mar 2012 11:08:31 +0100, Bernard wrote: Bernard wrote: Hi to Everyone, On the Desktop of my association, there was no wireless card. So, I purchased one that is said to be Debian compatible. It is a PCI card TP-LINK TL-WN751ND It is supposedly based on an Atheros chipset AR 9227 I plugged it inside the Central Unit on a PCI slot, and then booted the Debian Squeeze system. (...) P.S. : I carried new tests. As said above, now that my WiFi is configured, every attempt to boot, leads to "freezing" of the system in the middle of gnome start... EXCEPT IF I shutdown my DSL/WiFi box ! As long as no connexion is possible, the system starts all right ; I can see the other WiFi available in the area (I don't have the passwords...). This being said, if I reboot my WiFi connexion on the DSL modem, then, as said before, connexion does happen all right, it seems fully operational, but only for about 45 to 60 seconds, system freezing happens next. My TL-WN751ND card is supposed to work with Debian kernel module ath9k, which is supposed to be loaded with the wireless-tools package, which is alreeady installed. There are many issues reported for system freezes regarding that kernel module (ath9k), there is even a documented bug at the Linuxwireless site: http://linuxwireless.org/en/users/Drivers/ath9k/bugs#Hangs_with_PCI_devices_and_SMP_systems And even on Debian BTS: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611946 I would try with an updated kernel. Greetings, Thanks for this information. I might end up updating the kernel, but at this stage I am still trying to understand what happens and if there is another way to go around. I also have an ASUS laptop on which I installed Debian Squeeze on a dual boot together with MSWIN XP. This laptop allows a wireless connexion, even though nothing was installed other than what already existed on "MSWIN-XP". Wireless connexions are fully operational, even though they are often active for hours. I searched about the chipset used. It appeared to be the same as on the Desktop ! lspci on the laptop (the one that works fine) says : Atheros Communications Inc. AR928X Wireless Network Adapter (PCI-express rev 01 (while on the Desktop where no wireless connexion can operate for any longer than one or two minutes without system freeze, this is a AR9287 Wireless Network Adapter, TP-LINK TL-WN751ND) As stated, both machines are on Squeeze. On the laptop where everything works fine, kernel is 2.6.32-5-686 (Debian 2.6.32.30), while it is Debian 2.6.32-41 on the problematic Desktop. I carried a few more tests on the problematic Desktop. I tested 'Wicd' instead of 'NetworkManager'. Even though I had uninstalled (#apt-get remove --purge) the old Wicd package and re-installed a new one , it did reckognise my WiFi, but I couldn't get any connexion: the password did not seem to be accepted ; it said "wrong password". True enough, this is a "pasphrase", not a key, that was required, and I had nothing else than a WPA-PSK key, the very same one that was being reckognized by NM. I tested several times to no avail. I am willing to test 'ifup', but I don't know what I should write in my /etc/network/interfaces file. I carried a few tests, to no avail. I also tested another chip that I have purchased in the same time. It is a "mini-PCI" wireless card (TP-LINK model TL-WN861N). I had to purchase a special "mini-pci to pci adaptator" in order to be able to insert it in a PCI slot in said Desktop. This one is not being reckognized "out of the box" as the TL-WN751ND was. You must install 'firmware-atheros' before it gets acknowledged. This one is supposedly driven by AR922X wireless-network-adapter. But I got nowhere with this. #iwconfig said that it was on wlan1, but I could never even see any wireless network with it. I also tested it on MSWIN, where it seemed reckognized all write after proper installation with appropriate drivers... but in the end I never got any connexion ; it seems to be that my DSL box wifi signal was too weak for this chipset... The other chipset, the one that connects OK to Debian for a short time before system freeze, works perfectly under MSWIN. So, I wonder why an atheros wifi card works so well on a laptop with Squeeze, and another very closely related Atheros chipset refuses to work on another machine on Squeeze. If I were to upgrade kernels, which kernel would you recommend ? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f5bd69e.1040...@teaser.fr
Re: big problem with TP-LINK WiFi card
On Fri, 09 Mar 2012 11:08:31 +0100, Bernard wrote: > Bernard wrote: >> Hi to Everyone, >> >> On the Desktop of my association, there was no wireless card. So, I >> purchased one that is said to be Debian compatible. It is a PCI card >> TP-LINK >> TL-WN751ND >> >> It is supposedly based on an Atheros chipset AR 9227 >> >> I plugged it inside the Central Unit on a PCI slot, and then booted the >> Debian Squeeze system. (...) > P.S. : I carried new tests. As said above, now that my WiFi is > configured, every attempt to boot, leads to "freezing" of the system in > the middle of gnome start... EXCEPT IF I shutdown my DSL/WiFi box ! As > long as no connexion is possible, the system starts all right ; I can > see the other WiFi available in the area (I don't have the > passwords...). This being, if I reboot my WiFi connexion on the DSL > modem, then, as said before, connexion does happen all right, it seems > fully operational, but only for about 45 to 60 seconds, system freezing > happens next. My TL-WN751ND card is supposed to work with Debian kernel > module ath9k, which is supposed to be loaded with the wireless-tools > package, which is alreeady installed. There are many issues reported for system freezes regarding that kernel module (ath9k), there is even a documented bug at the Linuxwireless site: http://linuxwireless.org/en/users/Drivers/ath9k/bugs#Hangs_with_PCI_devices_and_SMP_systems And even on Debian BTS: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611946 I would try with an updated kernel. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jjd88o$f1t$8...@dough.gmane.org
Re: big problem with TP-LINK WiFi card
Bernard wrote: Hi to Everyone, On the Desktop of my association, there was no wireless card. So, I purchased one that is said to be Debian compatible. It is a PCI card TP-LINK TL-WN751ND It is supposedly based on an Atheros chipset AR 9227 I plugged it inside the Central Unit on a PCI slot, and then booted the Debian Squeeze system. As a rather pleasant surprise, the wireless system was being acknowledged immediately, and I could display a list of wireless networks available in my area, amongst which I saw my own DSL wireless network on which I have been able to connect any other laptop or desktop computer that ever came to my house. I clicked to that Network on the list, and then entered all the digits of my WPA password. This being done, I got the message that I was connected and that the connexion was allright. Well, then I launched Firefox (I mean Iceweasel) and called for a web page... As soon as the connexion to that page was achieved, THE SYSTEM FROZE and I could do nothing more... The mouse was no longer active, same for the keyboard or anything else, CTRL-ALT-DEL did nothing, and I had no other choice than disconnecting power. At reboot, the freezing did appear right away, in the process of gnome launching. Same at each new attempt. I first thought that the chipset may have been faulty or damaged. So I tested it under MSWIN (XP) since I have a dual boot on that desktop. Under MSWIN, after the appropriate install with the provided CDROM, the TL-WN751ND card did operate all right. After the password was typed, connexion happened and operated without freezing the system or any other trouble. So, it is most likely that the hardware is not faulty here. I understand that I should probably have first checked if my Debian Squeeze system was ready with the appropriate packages to run that wireless chipset, instead of right away trusting the fact that it seemed to be reckognized 'out of the box'. However, now that things are that way, I wonder what files I should delete (booting from a rescue disk maybe), so that I am able to de-install or install whatever is needed to get that chipset working. Thanks in advance for your help P.S. : I carried new tests. As said above, now that my WiFi is configured, every attempt to boot, leads to "freezing" of the system in the middle of gnome start... EXCEPT IF I shutdown my DSL/WiFi box ! As long as no connexion is possible, the system starts all right ; I can see the other WiFi available in the area (I don't have the passwords...). This being, if I reboot my WiFi connexion on the DSL modem, then, as said before, connexion does happen all right, it seems fully operational, but only for about 45 to 60 seconds, system freezing happens next. My TL-WN751ND card is supposed to work with Debian kernel module ath9k, which is supposed to be loaded with the wireless-tools package, which is alreeady installed. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f59d69f.8020...@teaser.fr
big problem with TP-LINK WiFi card
Hi to Everyone, On the Desktop of my association, there was no wireless card. So, I purchased one that is said to be Debian compatible. It is a PCI card TP-LINK TL-WN751ND It is supposedly based on an Atheros chipset AR 9227 I plugged it inside the Central Unit on a PCI slot, and then booted the Debian Squeeze system. As a rather pleasant surprise, the wireless system was being acknowledged immediately, and I could display a list of wireless networks available in my area, amongst which I saw my own DSL wireless network on which I have been able to connect any other laptop or desktop computer that ever came to my house. I clicked to that Network on the list, and then entered all the digits of my WPA password. This being done, I got the message that I was connected and that the connexion was allright. Well, then I launched Firefox (I mean Iceweasel) and called for a web page... As soon as the connexion to that page was achieved, THE SYSTEM FROZE and I could do nothing more... The mouse was no longer active, same for the keyboard or anything else, CTRL-ALT-DEL did nothing, and I had no other choice than disconnecting power. At reboot, the freezing did appear right away, in the process of gnome launching. Same at each new attempt. I first thought that the chipset may have been faulty or damaged. So I tested it under MSWIN (XP) since I have a dual boot on that desktop. Under MSWIN, after the appropriate install with the provided CDROM, the TL-WN751ND card did operate all right. After the password was typed, connexion happened and operated without freezing the system or any other trouble. So, it is most likely that the hardware is not faulty here. I understand that I should probably have first checked if my Debian Squeeze system was ready with the appropriate packages to run that wireless chipset, instead of right away trusting the fact that it seemed to be reckognized 'out of the box'. However, now that things are that way, I wonder what files I should delete (booting from a rescue disk maybe), so that I am able to de-install or install whatever is needed to get that chipset working. Thanks in advance for your help -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f59280a.3040...@teaser.fr
