Wi-Fi is still not connecting
- Vous devez vous identifier ou créer un compte pour écrire des commentaires
I used to run Trisquel on an old desktop Dell, and, after updating the kernel to the latest Linux-Libre from jxself, the wi-fi would work. Now I've bought a Lenovo laptop, installed all the updates and Linux-Libre, but wi-fi is still not working, nor through the internal wi-fi hardware, nor through the dongle. I only get device not ready, and no wi-fi connections are listed. What can I do?
I forgot to mention that on the old desktop I used an wi-fi dongle that had a free drive, but it's not working on the laptop. I only get "device no ready"
Hehe, I connected another dongle that uses the same free driver and it worked. But this one is huge and even has a full sized wi-fi antenna!
Are you certain it is the same chipset (not only the same driver) at work? You can plug both and show us the output of 'lsusb' (to be executed in a terminal). If it is, then the non-functioning adapter must be defective. Otherwise, there must simply be no free firmware available for it.
Bus 003 Device 002: ID 8087:8000 Intel Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 0bda:b728 Realtek Semiconductor Corp.
Bus 001 Device 005: ID 0bda:579a Realtek Semiconductor Corp.
Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 001 Device 003: ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n
Bus 001 Device 007: ID 148f:3070 Ralink Technology, Corp. RT2870/RT3070 Wireless Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
I don't think it's showing up. That Ralink, isn't it the internal one? As far as I know both dongles are Atheros...
Your Ralink one needs proprietary software in order to function. The AR9271 does not, but it does need a (free software) firmware. Please be sure to install the package open-ath9k-htc-firmware.
That package is installed and updated, maybe the dongle is broken... But I tested some weeks ago with this laptop's original Windows 10 installation, and it worked... And I formatted my laptop again because I had partioned it wrongly, and the bigger worked out of the box, with no updates whatsoever!
Didn't you write in https://trisquel.info/forum/wi-fi-still-not-connecting#comment-85892 that the adapter with the Atheros chipset works (as it should)? The package "open-ath9k-htc-firmware", which is installed by default, aim to make that chipset work.
The adapter with the Ralink chipset cannot work with free software: the driver is under the GPL but is useless without a proprietary firmware that Trisquel obviously does not ship.
I have 2 adaptors that use the Atheros chipset, I was just trying to figure out why the smaller one doesn’t work... Sorry for sounding like a newbie, but I actually am one.
Those two lines indicate that one of your adapter has an Atheros chipset; the other one a Ralink chipset:
Bus 001 Device 003: ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n
Bus 001 Device 007: ID 148f:3070 Ralink Technology, Corp. RT2870/RT3070 Wireless Adapter
Is there a third adapter? If so, was it plugged when you executed 'lsusb'?
Yes, there was, another model, but with the same Atheros chipset. It lights up, but it doesn't blink. And it says the device isn't ready, at the side of the clock. But this big Atheros adaptor worked as soon as I plugged it, even before any system or kernel update. The small one should be broken, I guess...
Yes, there was, another model, but with the same Atheros chipset. It lights
up, but it doesn't blink. And it says the device isn't ready, at the side of
the clock. But this big Atheros adaptor worked as soon as I plugged it, even
before any system or kernel update. The small one should be broken, I
guess...
Those two lines indicate that one of your adapter has an Atheros chipset; the
other one a Ralink chipset:
Bus 001 Device 003: ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n
Bus 001 Device 007: ID 148f:3070 Ralink Technology, Corp. RT2870/RT3070
Wireless Adapter
Is there a third adapter? If so, was it plugged when you executed 'lsusb'?
I have 2 adaptors that use the Atheros chipset, I was just trying to figure
out why the smaller one doesn’t work... Sorry for sounding like a newbie,
but I actually am one.
Didn't you write in
https://trisquel.info/forum/wi-fi-still-not-connecting#comment-85892 that the
adapter with the Atheros chipset works (as it should)?
The adapter with the Ralink chipset cannot work with free software: the
driver is under the GPL but is useless without a proprietary firmware that
Trisquel obviously does not ship.
That package is installed and updated, maybe the dongle is broken... But I
tested some weeks ago with this laptop's original Windows 10 installation,
and it worked... And I formatted my laptop again because I had partioned it
wrongly, and the bigger worked out of the box, with no updates whatsoever!
Your Ralink one need proprietary software in order to function. The AR9271
does not, but it does need a (free software) firmware. Please be sure to
install the package open-ath9k-htc-firmware.
Bus 003 Device 002: ID 8087:8000 Intel Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 0bda:b728 Realtek Semiconductor Corp.
Bus 001 Device 005: ID 0bda:579a Realtek Semiconductor Corp.
Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card
Reader Controller
Bus 001 Device 003: ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n
Bus 001 Device 007: ID 148f:3070 Ralink Technology, Corp. RT2870/RT3070
Wireless Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
I don't think it's showing up. That Ralink, isn't it the internal one? As far
as I know both dongles are Atheros...
Are you certain it is the same chipset (not only the same driver) at work?
You can plug both and show us the output of 'lsusb' (to be executed in a
terminal). If it is, then the non-functioning adapter must be defective.
Otherwise, there must simply be no free firmware available for it.
I am running a Dell Latitude E5500 and I am experiencing connectivity problems with Trisquel (7.0 full GNOME version), too.
My wireless card is an Intel, not the usual Broadcom card that comes with Dell laptops and creates so many connectivity problems for Linux users. I am not saying the problem is not the Intel card, it very well could be; I am simply noting the usual Broadcom problem is definitely not the problem.
Using the ethernet/cable connection is a breeze. It's automatic.
But when I boot up and try to connect via wireless, no wireless connections appear (there are four of them to choose from here, two with passwords, two without). All other computers and wireless devices connect without issue--so, suffice to say, the problem is not the wireless service. This Dell is running other distros on the hard drive and are connecting just fine.
I've tried everything. I am befuddled. I don't get it.
Anyone?
The problem is the intel wifi. That will not work with free software. You can get an internal or external replacement. See e.g. https://fsf.org/ryf
Danke. That explains a few things.
I went to the page and I liked the look of this: Penguin Wireless N USB Adapter for GNU / Linux (TPE-N150USB) -- but the price is forty-four bucks. eBay has them for under twenty five. Why such a jump in price? Do funds go to support fsf.org when they are purchased here?
And I am assuming this item is just plug and play. Is that right?
Some of the vendors do donate to e.g. Trisquel. Also the FSF recommended stuff is guaranteed to work. Of course you could get lucky buying elsewhere. The nasty thing is, apparently the manufacturers change the internals of the stuff they sell without changing model name. So one might work and another might not... It's messy and ugly. Not sure about the plug-n-play.
Linux-libre includes the driver and firmware needed by that USB dongle, so yes, it's "plug and play" for Trisquel.
Some of the vendors do donate to e.g. Trisquel. Also the FSF recommended
stuff is guaranteed to work. Of course you could get lucky buying elsewhere.
The nasty thing is, apparently the manufacturers change the internals of the
stuff they sell without changing model name. So one might work and another
might not... It's messy and ugly. Not sure about the plug-n-play.
Linux-libre includes the driver and firmware needed by that USB dongle, so
yes, it's "plug and play" for Trisquel.
I used to run Trisquel on an old desktop Dell, and, after updating the kernel
to the latest Linux-Libre from jxself, the wi-fi would work. Now I've bought
a Lenovo laptop, installed all the updates and Linux-Libre, but wi-fi is
still not working, nor through the internal wi-fi hardware, nor through the
dongle. I only get device not ready, and no wi-fi connections are listed.
What can I do?
Danke. That explains a few things.
I went to the page and I liked the look of this: Penguin Wireless N USB
Adapter for GNU / Linux (TPE-N150USB) -- but the price is forty-four bucks.
eBay has them for under twenty five. Why such a jump in price? Do funds go
to support fsf.org when they are purchased here?
The problem is the intel wifi. That will not work with free software. You can
get an internal or external replacement. See e.g. https://fsf.org/ryf
I find use of the TP usb wifi radio to be plug-and-play with Trisquel7, on a Toshiba Satellite laptop, which also has the Intel wifi thing, known not to be supported by software libre. One minor annoyance, though: If I boot or awaken this machine, with the wifi switched on and the usb not plugged in, the system will try to activate the intel, causing slow-down and, presumably, a huge log of the situation. From another post, I learned of blacklisting the offending module; will try this. Meanwhile, it is enough to start with the front panel wifi switch off, and the dongle unplugged. Once the system is going, I insert the dongle, and throw the switch, and all's well.
Thanks for the help, lembas, onpon4, and Dave_Hunt. I think I can take it from here.
Apologies to rjltrevisan, for hijacking your thread. That was not my intention. Hope you get all your connectivity issues handled!
Update: I opted to purchase my USB dongle from inside Thailand. I was not able to find anywhere the Penguin dongle as advertised on this site, but I did find this: TP-LINK Model NO. TL-WN722 from a shop in Hua Hin. It has precisely the same chip set as the Penguin model-and it worked perfectly-plug and play.
I forgot to mention that on the old desktop I used an wi-fi dongle that had a
free drive, but it's not working on the laptop. I only get "device no ready"
Hehe, I connected another dongle that uses the same free driver and it
worked. But this one is huge and even has a full sized wi-fi antenna!
I am running a Dell Latitude E5500 and I am experiencing connectivity
problems with Trisquel (7.0 full GNOME version), too.
My wireless card is an Intel, not the usual Broadcom card that usually comes
with Dell laptops and creates so many connectivity problems for Linux users.
I am not saying the problem is not the Intel card, it very well could be; I
am simply noting the usual Broadcom problem is definitely not the problem.
Using the ethernet/cable connection is a breeze. It's automatic.
But when I boot up and try to connect via wireless, no wireless connections
appear (there are four of them to choose from here, two with passwords, two
without--but none appear). All other computers and wireless devices connect
without issue--so, suffice to say, the problem is not the wireless service.
My other laptops running other distros are connecting just fine, too.
I've tried everything. I am befuddled. I don't get it.
Anyone?
I find use of the TP usb wifi radio to be plug-and-play with Trisquel7, on a
Toshiba Satellite laptop, which also has the Intel wifi thing, known not to
be supported by software libre. One minor annoyance, though: If I boot or
awaken this machine, with the wifi switched on and the usb not plugged in,
the system will try to activate the intel, causing slow-down and, presumably,
a huge log of the situation. From another post, I learned of blacklisting
the offending module; will try this. Meanwhile, it is enough to start with
the front panel wifi switch off, and the dongle unplugged. Once the system
is going, I insert the dongle, and throw the switch, and all's well.
Thanks for the help, lembas, onpon4, and Dave_Hunt. I think I can take it
from here.
Apologies to rjltrevisan, for hijacking your thread. That was not my
intention. Hope you get all your connectivity issues handled!
able to find anywhere the Penguin dongle as advertised on this site, but I
did find this: TP-LINK Model NO. TL-WN722 from a shop in Hua Hin. It has
precisely the same chip set as the Penguin model-and it worked perfectly-plug
and play.
- Vous devez vous identifier ou créer un compte pour écrire des commentaires