I see many posts around about wifi problems but have not yet seen any with my problem.
My wifi used to work and I do not know what made it go off-line as I mostly use my wired connection.
Running SuSE 13-3, GNOME, kernel 2.6.34.7-0.7-default on a HP laptop.
I wanted to include some diagnostic and configuration downloads from my computer but I am being told I have 5 images included in my post when I Paste the text. Don’t know why!
Can anyone, in simple basic terms as I am new to Linux, tell me how to get wifi up and running again?
On 01/11/2011 11:36 AM, lak 726 wrote:
>
> I see many posts around about wifi problems but have not yet seen any
> with my problem.
>
> My wifi used to work and I do not know what made it go off-line as I
> mostly use my wired connection.
>
> Running SuSE 13-3, GNOME, kernel 2.6.34.7-0.7-default on a HP laptop.
>
> I wanted to include some diagnostic and configuration downloads from my
> computer but I am being told I have 5 images included in my post when I
> Paste the text. Don’t know why!
>
> Can anyone, in simple basic terms as I am new to Linux, tell me how to
> get wifi up and running again?
The first thing to check is if your wireless switch is off. If you think it
really is on, then run the command ‘/usr/sbin/rfkill list’. If that command is
not found, then ‘sudo zypper in rfkill’. If your wireless is hard blocked, your
switch is off, or at least the system thinks so.
On 01/11/2011 12:36 PM, lak 726 wrote:
>
> Thank you for quick answer.
>
> Unfortunately still not able to enable wireless. Did what lwfinger
> suggested to no avail (the wifi powerswitch IS on).
Post the output of ‘/usr/sbin/rfkill list’ and ‘dmesg | grep 3945’.
On 01/11/2011 03:36 PM, lak 726 wrote:
>
> I can not believe, after battling this for weeks, problem is solved!
>
> The last entries did it!
>
> To answer your question, I can only suggest I am running VMWare on the
> computer . . .
>
> Thank you and have a very nice day.
>
> 0130 here off to bed with a smile.
Good to get it working. You are likely to need the “/usr/sbin/rfkill unblock
all” to be executed with each reboot. Normally, I would put such commands in
/etc/rc.d/boot.local; however, that may be too soon. Try it and if the soft
block is still on when you get logged in, report that and we will set up a way
that does function.
Wireless and Bluetooth working, even after reboot but, but . . .
Now, when booting, I am asked to enter Keyring password before the network will start. That is both wired and wireless.
Had a look in Local Security. Only reference to Network is “Enable basic system services in runlevel 3 (mulituser with network)” and “Enable basic system services in runlevel 5 (multiuser with network and graphical login)”. Status for both is “Configure”.
Will changes here make a difference?
I can easily live with having to enter Keyring password. This is far better than nothing!
I have not found it jet, but there is anywhere in openSUSE an graphical solution to activate unlocking the GNOME keyring (“seahorse”) every time you log in as a user.
I still do not know how to configure that generally but:
After I log into my GNOME on 11.4 factory-tested.
A window appears and says:
Enter password for keyring ‘Default’ to unlock An application wants access to the keyring ‘Default’, but it is locked
And there something after the box for entering the password: “/ Details:”
2) After I clicked on the “/” there are some options appearing, especially:
/ Details:
] Automatically unlock this keyring whenever I’m logged in
…]
I have not tested that option jet in openSUSE 11.3 or my (a bit dead played) 11.4 installation - but maybe there is an option like this in your installation and you are willing to take the risk to test it?
Regards and have a lot of luck and fun!
pistazienfresser