(I love the WTF downvote, but anyway, that's not why I'm posting) I didn't
try it since I've chosen a paid solution, but if someone still has an issue
with Bitmask like that, try erasing your config files, it might make it work
(or not, but still worth a try, since a reinstall keeps your
I have wifi now.
Thankfully, I didn't reinstall a thing.
I just modified the content of the interfaces file according to what the text
install asks for (wpa-psk).
and something about avahi-daemon, which I told not to start at boot anymore
(wlan0 avahi appeared on ifconfig).
Now, The problem
It seems the network stuff is dealt with in network-manager in the liveCD.
But it doesn't explain why I could connect in wifi before since I have no
sort of network-manager I'm aware of.
I'm trying some manual configuration, but no success yet.
I've put in
allow-hotplug wlan0
iface wlan0 inet
If you boot off a live Trisquel media, does the wifi work?
Something new happened:
I managed to turn the green wifi light on by bypassing hardware switch in
software:
http://madwifi-project.org/wiki/UserDocs/MiniPCI
actually, it only made my wlan hardblocked to yes in rfkill.
But I need to put the antenna on with sudo ifconfig wlan0 up
at each boot.
GOOD NEWS EVERYONE!
I'm nearly done with this:
I managed to keep the hardware block (rfkill) off, even though if it fails
again, I'll resort to taping the proper pin on my wifi card.
So for now, it works.
I tried rebooting again with a Trisquel liveCD, and the wifi is recognized. I
tried a
Tehnoetic time.
Looks like I really have broken something.
My wifi green light is off, no matter if the ardware switch is on or off. and
the FN key+F5 does work, but has no effect on hardware wifi.
I tried
rmmod -f ath9k
sudo rfkill unblock all
sudo modprobe ath9k
and since it gave me a FATAL: something
Aw man... Are you sure it's a hardware issue??
It worked fine until now. There was a bad contact with the switch button pnce
(for a short while), but since I can't access it...
Since I just removed that thing from the kernel witout being able to put it
back, is there zero chances for the
The ath9k module couldn't be found because you, just like I and almost
everyone else once did, had the assumption that the ‘rmmod’ command is a
safe way to unload modules inserted with the ‘modprobe’ command.
The thing is: The ‘--remove’ option of the ‘modprobe’ command resolves
module
And here my memory fails at me again...
After using ‘insmod’, load the module with ‘modprobe’, and after that,
it's recommended that you restart the system (I'm not the master of
module loading, but I think this is needed).
Here's what happened: I was trying to setup KVM. So I made manual changes
regarding my network interfaces.
Somehow, KVM worked.
I don't remember why, but I had to restart my machine.
I then noticed that my bridge was finally up. I also noticed a much slower
reboot because of some network
https://trac.torproject.org/projects/tor/ticket/11776
I think I restarted my machine because Bitmask started, but wasn't able to
get a connection.
added to the above, it really seems to be a network issue.
13 matches
Mail list logo
