ath5k driver works only on live disc, doesn't work after install
- Login o registrati per inviare commenti
Hi there,
I'm considering installing trisquel _again_, but last time I could not find a solution to this problem -- that the wireless driver only functions from the live disc, not from the version of trisquel that gets installed to my hard drive. It's such a great distro, and everything works so well (I am typing this from the live disc) that I would hate to have this one hurdle hold me back -- what kinds of diagnostics can I provide to help? lsmod? iwconfig? let me know and i will post. Has anyone else encountered this problem?
Thanks!
Could it be related to this? http://www.ubuntu.com/getubuntu/releasenotes/810#Atheros%20ath5k%20wireless%20driver%20not%20enabled%20by%20default I do indeed have the ath5k driver...
> the wireless driver only functions from the
> live disc, not from the version of trisquel that gets installed to my hard
> drive.
> Could it be related to this?
> http://www.ubuntu.com/getubuntu/releasenotes/810#Atheros%20ath5k%20wireless%20driver%20not%20enabled%20by%20default
> I do indeed have the ath5k driver...
Maybe. Try this on the installed Trisquel:
echo ath5k | sudo tee -a /etc/modules
and reboot.
For more info, please include the output of dmesg and lsmod. (you can
use http://trisquel.pastebin.com for that)
_______________________________________________
Trisquel-users mailing list
name at domain
http://listas.trisquel.info/mailman/listinfo/trisquel-users
Thank you! I have installed Trisquel 3.0 to my hard drive, performed the steps you suggested, and I am now connected to an unsecured network at a local coffee shop :) However, I am still having problems at home, where we are using WPA. When I tried to connect this morning, one of the two orbs in the Networking icon lit up, but the applet continued to spin until it came back with the password authentication dialog. In the password field was a much longer string (an encrypted form of our passphrase?). I tried resubmitting my information a couple of times, but got the same results. I am doing a system update here, but if that doesn't solve the problem, what would you suggest for troubleshooting WPA (in terms of output / logs to send to the pastebin)? Thanks in advance,
Alternatively, would it be possible to somehow export the configuration from the NetworkManager Applet from the live disc and import it to the installation on my hard drive? Just a thought.. I did a bit of digging around, but couldn't seem to find it.
On another note, I found that I had to update my sources.list to have a 'us.' at the beginning of each entry's URL to get the files for the update. Should that go in a different thread / issue list? For reference, is there somewhere that can I find a definitive list of sources for Trisquel? Again, thanks in advance,
The length of your password on the field I'm sure it's not the problem,
happens the same to me. Maybe you are typing wrong your key or maybe
have you selected a different kind of encryption that doesn't match with
the real one.
Check if you have selected the infrastructure mode and personal WPA and
WPA2 which is the one commonly used at home.
The problem can also be related with your ip configuration, on the IPv4
parameters check if you have selected the automatic mode (DHCP) it will
save you of problems if you don't need to use a static IP.
I hope this helps you ;)
El dc 07 de 10 de 2009 a les 20:47 +0000, en/na name at domain va
escriure:
> Thank you! I have installed Trisquel 3.0 to my hard drive, performed the
> steps you suggested, and I am now connected to an unsecured network at a
> local coffee shop :) However, I am still having problems at home, where we
> are using WPA. When I tried to connect this morning, one of the two orbs in
> the Networking icon lit up, but the applet continued to spin until it came
> back with the password authentication dialog. In the password field was a
> much longer string (an encrypted form of our passphrase?). I tried
> resubmitting my information a couple of times, but got the same results. I am
> doing a system update here, but if that doesn't solve the problem, what would
> you suggest for troubleshooting WPA (in terms of output / logs to send to the
> pastebin)? Thanks in advance,
> _______________________________________________
> Trisquel-users mailing list
> name at domain
> http://listas.trisquel.info/mailman/listinfo/trisquel-users
--
Aitor Ruano Miralles <name at domain>
_______________________________________________
Trisquel-users mailing list
name at domain
http://listas.trisquel.info/mailman/listinfo/trisquel-users
Thank you for the above suggestions. Unfortunately, I am still not having success. Currently, I am on a neighbor's unencrypted wireless network. I also found that I am unable to connect to a network that is encrypted with WEP (at a friend's house, where he gave me the connection information). Here we are using WPA2. This leads me to the conclusion that while my wireless drivers and DHCP client are working, there is some small difference in configuration between the live environment and the installed environment that is preventing the use of encryption, but I am at a loss to find what that is.
I have compared the ouput of dmesg, lsmod, and modprobe -l between the live environment and the installed environment. This was the only difference that stood out to me (the former is the from the live environment, while the latter is from the installed) but I am not sure what to do about it:
jake@jake-laptop:/media/Cruzer/Documents/wireless$ grep aes lsmod.txt
aes_x86_64 16384 1
aes_generic 36264 1 aes_x86_64
jake@jake-laptop:/media/Cruzer/Documents/wireless$ lsmod | grep aes
aes_x86_64 16384 0
aes_generic 36264 1 aes_x86_64
I have copied the output of dmesg from the installed environment to the trisquel pastebin here:
http://trisquel.pastebin.com/m5ed80229
and from lsmod here:
http://trisquel.pastebin.com/m25898a62
Any suggestions on how to proceed are very welcome. Thank you!
Well, I found the source of the problem, at least here at home. My friend found a number of posts concerning hidden ESSID's and once we set my home router to broadcast its ESSID, that allowed me to connect. Apparently the support for hidden networks is not 100%, although that still doesn't explain why it worked on the live disc? Anyways, perhaps this will give someone else something else to try, if they are similarly stuck. Thanks again,
- Login o registrati per inviare commenti