hello i have just installed opensuse 12.3 gnome on my Acer Aspire 5536 laptop and i cannot see any networks to connect to,i have had to go to my Apple Macmini upstairs to get onto this forum,i looked on google and it said to the left of my name i should see all the networks,all i can see under my name is unavailable,system settings,logout,lock and power off,any ideas please on how to connect to my network ?
thank you.
On 03/18/2013 12:26 PM, geordiejohn50 wrote:
>
> hello i have just installed opensuse 12.3 gnome on my Acer Aspire 5536
> laptop and i cannot see any networks to connect to,i have had to go to
> my Apple Macmini upstairs to get onto this forum,i looked on google and
> it said to the left of my name i should see all the networks,all i can
> see under my name is unavailable,system settings,logout,lock and power
> off,any ideas please on how to connect to my network ?
> thank you.
My auto does not work. Can you fix it?
What does the above statement have to do with this problem? It provides the same
amount of information about Linux and wireless as you did!!
The only thing we know is that you use Gnome under openSUSE 12.3, but not what
kind of wireless device you have (lspci -nn, or lsusb), if you are trying to use
NetworkManager, or if the output of the dmesg command shows that the firmware is
missing.
2.2. No Network after InstallationDirectly after installation, NetworkManager is not started automatically and thus WiFi cannot be configured. To enable networking (WiFi), reboot the machine once manually.
source:- https://www.suse.com/releasenotes/x86_64/openSUSE/12.3/#idm47311841257152
thanks for the replies but i have given up on Opensuse and installed something else,this is the first distro i have tried where it did not show me a list of networks near me.
Too bad. i too installed 12.3 couple of days back and everything just works out of box
Ipv6 is enables by default. You need to go to yast and enable ipv4 instead.
With all due respect, that is irrelevant to the OPs connectivity problem.
I had this problem when I installed opensuse 12.3. It would only look for IPv6 networks. My router was only compatible with IPv4 so I needed to make it detect that instead.
i don’t know when the entire world(routers,isps etc) will start supporting ipv6. This is frustrating 
On 03/18/2013 11:56 PM, vazhavandan wrote:
>
> Icabob4;2537658 Wrote:
>> I had this problem when I installed opensuse 12.3. It would only look
>> for IPv6 networks. My router was only compatible with IPv4 so I needed
>> to make it detect that instead.
>
> i don’t know when the entire world(routers,isps etc) will start
> supporting ipv6. This is frustrating
Do any small home routers support DNS other that forwarding it on to the name
servers supplied by the ISP? For testing, I have 5 routers and none of them do.
The problem is generally with the ISP, at least mine is. Since I switched to
Google’s public servers when I was still using 11.4, I have had no problems.
I just installed OpenSUSE 12.3 with GNOME desktop on a Dell Inspiron 1501 (120gb hard drive, 1gb ram, 1.8ghz amd sempron, ati xpress1150) and I’m having the same problem. No list of wireless networks. Only wired connection is listed in network manager. No wireless. I’ve tried several restarts. I also tried to update the firmware as I had a similar issue in ubuntu using this code:
it went to a black screen and listed a bunch of codes followed by returning an error something like watchdog detected a failure at cpu 0, returning to text window
but the system just crashes there. Terminal returns b43 firmware is up to date after I rebooted.
Please help, I can’t get wireless to work. Thank you.
On 03/21/2013 08:36 AM, bmasseur wrote:
>
> I just installed OpenSUSE 12.3 with GNOME desktop on a Dell Inspiron
> 1501 (120gb hard drive, 1gb ram, 1.8ghz amd sempron, ati xpress1150) and
> I’m having the same problem. No list of wireless networks. Only wired
> connection is listed in network manager. No wireless. I’ve tried several
> restarts. I also tried to update the firmware as I had a similar issue
> in ubuntu using this code:
>
> ‘b43 - Linux Wireless’
> (http://wireless.kernel.org/en/users/Drivers/b43#openSUSE)
>
> it went to a black screen and listed a bunch of codes followed by
> returning an error something like watchdog detected a failure at cpu 0,
> returning to text window
>
> but the system just crashes there. Terminal returns b43 firmware is up
> to date after I rebooted.
>
> Please help, I can’t get wireless to work. Thank you.
How exactly does the terminal return that the b43 firmware is up to date? That
statement means nothing to me.
First of all, check the output of ‘dmesg’ for mention of firmware loaded. You
can also check the contents of /lib/firmware/b43/ for files.
Next, post the output of ‘/sbin/lspci -nn | grep Network’. That will tell us
what device you have. I have no idea what wifi card is in an Inspiron 1501. In
all likelihood, not all of them have the same card.
What does ‘/usr/sbin/iwconfig’ report? Do you have a wlan0 device?
If you do, what does ‘sudo /usr/sbin/iwlist scan’ show? Do you see any networks
listed?
If you see “Network down”, check if your wireless switch is on? Report the
output of ‘/usr/sbin/rfkill list’.
marla@linux-17z5:~> sudo zypper install b43-fwcutter
root's password:
Retrieving repository 'Update Repository (DEBUG)' metadata ...............[done]
Building repository 'Update Repository (DEBUG)' cache ....................[done]
Retrieving repository 'Main Update Repository' metadata ..................[done]
Building repository 'Main Update Repository' cache .......................[done]
Loading repository data...
Reading installed packages...
'b43-fwcutter' is already installed.
No update candidate for 'b43-fwcutter-012-21.1.1.x86_64'. The highest available version is already installed.
Resolving package dependencies...
Nothing to do.
I typed dmesg into the console but I think you meant something different by ‘for mention of firmware’ as in running this command in connection with the firmware updater? Anyways, it returned these lines too many times to paste all but it just runs through different numbers inside of the brackets.
[19117.292161] atkbd serio0: Unknown key released (translated set 2, code 0x8d on isa0060/serio0).
[19117.292174] atkbd serio0: Use 'setkeycodes e00d <keycode>' to make it known.
Also my /b43 folder is full of a bunch of .fw files. I don’t know how I would list them here, I just navigated to the folder in files to check.
marla@linux-17z5:~> /sbin/lspci -nn | grep Network
05:00.0 Network controller [0280]: Broadcom Corporation BCM4311 802.11a/b/g [14e4:4312] (rev 01)
marla@linux-17z5:~> /usr/sbin/iwconfig
eth0 no wireless extensions.
lo no wireless extensions.
The WIFI light on my laptop is off but pressing the switch button doesn’t do anything. Thanks for the help so far.
On 03/21/2013 08:16 PM, bmasseur wrote:
>
> lwfinger;2539063 Wrote:
>> How exactly does the terminal return that the b43 firmware is up to
>> date? That
>> statement means nothing to me.
>
>
> Code:
> --------------------
> marla@linux-17z5:~> sudo zypper install b43-fwcutter
> root’s password:
> Retrieving repository ‘Update Repository (DEBUG)’ metadata …[done]
> Building repository ‘Update Repository (DEBUG)’ cache …[done]
> Retrieving repository ‘Main Update Repository’ metadata …[done]
> Building repository ‘Main Update Repository’ cache …[done]
> Loading repository data…
> Reading installed packages…
> ‘b43-fwcutter’ is already installed.
> No update candidate for ‘b43-fwcutter-012-21.1.1.x86_64’. The highest available version is already installed.
> Resolving package dependencies…
Installing firmware for Broadcom devices requires two parts. The first is
b43-fwcutter, which is open source and can be distributed by openSUSE. The
second part is the data file read by fwcutter to extract the firmware. That
component cannot be distributed and is gotten to your system by running the
script file /usr/sbin/install_bcm43xx_firmware.
>> First of all, check the output of ‘dmesg’ for mention of firmware
>> loaded. You
>> can also check the contents of /lib/firmware/b43/ for files.
>
> I typed dmesg into the console but I think you meant something
> different by ‘for mention of firmware’ as in running this command in
> connection with the firmware updater? Anyways, it returned these lines
> too many times to paste all but it just runs through different numbers
> inside of the brackets.
No, the command dmesg dumps the current log to the terminal. I meant for you to
look at that output to see if you saw a statement like
b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
> Also my /b43 folder is full of a bunch of .fw files. I don’t know how I
> would list them here, I just navigated to the folder in files to check.
I just asked you to see if there were files there. The only way to get them
there is usually the right way, but we will check later.
> lwfinger;2539063 Wrote:
>> Next, post the output of ‘/sbin/lspci -nn | grep Network’. That will
>> tell us
>> what device you have. I have no idea what wifi card is in an Inspiron
>> 1501. In
>> all likelihood, not all of them have the same card.
>
>
> Code:
> --------------------
> marla@linux-17z5:~> /sbin/lspci -nn | grep Network
> 05:00.0 Network controller [0280]: Broadcom Corporation BCM4311 802.11a/b/g [14e4:4312] (rev 01)
> --------------------
A BCM4311 is an old, but good variety.
>
> lwfinger;2539063 Wrote:
>> What does ‘/usr/sbin/iwconfig’ report? Do you have a wlan0 device?
>
>
> Code:
> --------------------
> marla@linux-17z5:~> /usr/sbin/iwconfig
> eth0 no wireless extensions.
>
> lo no wireless extensions.
You do not have a wlan device, therefore the driver is not loaded.
> --------------------
>
>
>
>
> lwfinger;2539063 Wrote:
>> If you do, what does ‘sudo /usr/sbin/iwlist scan’ show? Do you see any
>> networks
>> listed?
>>
>> If you see “Network down”, check if your wireless switch is on? Report
>> the
>> output of ‘/usr/sbin/rfkill list’.
>
> The WIFI light on my laptop is off but pressing the switch button
> doesn’t do anything. Thanks for the help so far.
You have no wireless device driver, thus nothing is reading the switch signal
even if it is working.
Please post the output of
sudo /sbin/modprobe -v b43
ls /lib/firmware/b43/ucode*
marla@linux-17z5:~> sudo /sbin/modprobe -v b43
marla@linux-17z5:~> ls /lib/firmware/b43/ucode*
/lib/firmware/b43/ucode11.fw /lib/firmware/b43/ucode16_sslpn_nobt.fw
/lib/firmware/b43/ucode13.fw /lib/firmware/b43/ucode17.fw
/lib/firmware/b43/ucode14.fw /lib/firmware/b43/ucode19.fw
/lib/firmware/b43/ucode15.fw /lib/firmware/b43/ucode20.fw
/lib/firmware/b43/ucode16_lp.fw /lib/firmware/b43/ucode22_sslpn.fw
/lib/firmware/b43/ucode16_mimo.fw /lib/firmware/b43/ucode5.fw
/lib/firmware/b43/ucode16_sslpn.fw /lib/firmware/b43/ucode9.fw
I also downloaded b43-fwcutter from the opensuse software source and reinstalled.
I’m still a little confused about the dmesg command. Did that run correctly or is there still something you need me to do with that?
And was there anything else I was supposed to do from your last post that I missed? Thanks again for the help.
I think you misunderstood dmesg . It just reads the messages that the OS/Kernel spews out in copious amounts.
On 03/22/2013 12:16 AM, vazhavandan wrote:
>
> bmasseur;2539295 Wrote:
>>
>> I’m still a little confused about the dmesg command. Did that run
>> correctly or is there still something you need me to do with that?.
> I think you misunderstood dmesg . It just reads the messages that the
> OS/Kernel spews out in copious amounts.
You have the necessary firmware, and the modprobe command shows that b43 is
loaded. You do need to read the output of the dmesg command to see what is
going wrong. It is too long to post here, but if you want to post it on
susepaste, I can look at it.
Well when I typed dmesg is returned those two lines so many times that they were still there when I scrolled all the way to the top of terminal (I could not go back far enough to even see where I entered the command), so could there be something at the beginning that I missed? And how is it that the terminal can be full to a point where I can’t scroll back to the beginning? I’m using GNOME terminal and I had noticed that there are two other terminals (something I’ve never seen in another linux), is this the best terminal to be using? And what’s the difference? I didn’t find anything about it on google really.
Also, the errors I get from running the firmware update take me out of the terminal window so I can’t copy/paste them, but here is a picture from my phone of the screen:
sorry, iDrive has got to be the worst file hosting service I’ve ever used. It makes it impossible to embed or link the pictures… the site design is exceedingly frustrating and gives one the impression that it was set up intentionally to make things difficult for you… >:(
https://www.idrive.com/idrive/sh/sh?k=juhue44616
https://www.idrive.com/idrive/sh/sh?k=gsgxz89414
https://www.idrive.com/idrive/sh/sh?k=iocts17802
so those links should take you to the image. You might have to download it, when I try to view the image it only shows me the top 10%
Thanks again for the help so far.
On 03/22/2013 12:36 PM, bmasseur wrote:
>
> Well when I typed dmesg is returned those two lines so many times that
> they were still there when I scrolled all the way to the top of terminal
> (I could not go back far enough to even see where I entered the
> command), so could there be something at the beginning that I missed?
> And how is it that the terminal can be full to a point where I can’t
> scroll back to the beginning? I’m using GNOME terminal and I had noticed
> that there are two other terminals (something I’ve never seen in another
> linux), is this the best terminal to be using? And what’s the
> difference? I didn’t find anything about it on google really.
You do not need to rerun the firmware update again. I thought I made that clear.
I do not know about Gnome, but the KDE terminal lets you set the amount of
scrollback lines. Mine are set to infinity - the console output is placed on disk.
OK, now some Linux 101. Anytime you want to capture output of a command, you use
the redirection operators (> or >>). The first one sends the output to a file,
and the second adds the output to a file. It gets a little more complicated if
some or all of the output has been directed to the standard error device rather
than the standard output, but we will ignore that for now. Thus to capture the
output of the dmesg command,
dmesg > dmesg.out
If you want to read the dmesg output, but not save it in a file, then use
dmesg | less
The | is the character for “pipe”, thus the above command will send the output
to the pager program named less. You can see the full command set for less from
‘man less’, but a space gets you the next screenful, q quits, and / lets you
enter a search term.
On 2013-03-19 16:40, Larry Finger wrote:
>>
>
> Do any small home routers support DNS other that forwarding it on to the
> name servers supplied by the ISP?
I think mine does, but I don’t use that feature.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)