reporting command results?

Supergibbon · August 28, 2010, 12:27pm

Hi,
I’m new to Linux and am trying to get my Wireless working using fwfingers sticky on getting it going. Everything’s gone as he(she?) said so far, though on 4 and 5 after getting the command results he says to report it so the computer knows they’re there. I’m afraid I’m clueless as to how to do that, and it’s a closed thread.
Anyone got suggestions what reporting means please?

Supergibbon · August 28, 2010, 2:43pm

Ok, bit more info as to where I’ve got to if it’s helpful.

I’m pretty sure I’ve got firmware installed (was told b43 was installed after doing sudo /usr/sbin/install_bcm43xx_firmware).

The steps 4 and 5, he suggested were checking for a wireless device using /usr/sbin/iwconfig followed by determining if your adapter is recieving any broadcast from your AP using sudo /usr/sbin/iwlist scan.

After doing dmseg | less (step 3) I was told ‘driver’s loaded but no devices found’
After doing the usr/sbin/iwconfig (step 4), I get ‘ESSID: off/any’ and ‘Access Point: Not-Associated’. He notes that the entries on mine will be different to his, his are from a working wireless interface…the main point is that any output requires the driver to be loaded and functioning. This fact should be reported.
Using Sudo /usr/sbin/iwlist scan (step 4) gives me the Addresses and ESSID’s of the 2 networks within range of me. He notes that ‘whatevver results from that command, report it as well.’

Could anyone tell me how to report the info I have and ‘report’ it in the right place. It seems to me I (hopefully) have everything in there somewhere, but don’t know where to imput/report it all to get it up and running.

Anyone any ideas?

lwfinger · August 28, 2010, 6:05pm

Normally, one copies the information from the terminal window and pastes that
into the message. Can you not do that? From a terminal, the normal CTRL-C and
CTRL-V do not work, but the Edit pulldown has the operations and the shortcuts
(You need to SHIFT as well). If you need to switch from Linux to some other OS
to get net access, you will need to put the info in a file to get access while
on-line.

The commands that will be of interest are:


dmesg | egrep "ssb|b43"
sudo /usr/sbin/iwlist scan

In addition tell us if you are using NetworkManager or ifup, KDE or Gnome, and
the version of openSUSE.

Supergibbon · August 29, 2010, 3:53pm

Thanks for getting back to Larry. So far I’ve spent about 10 hours or so trawling forums trying to work this out and needed to take a break yesterday before it drove me nuts!

It’s the latest version 11.3 on KDE. I’ve tried both Network Manager and ifup, but NM refuses to do anything/load when clicked on and I don’t know what parameters/IP’s etc. to put into ifup.

First I installed b43 using:

1 sudo /usr/sbin/install_bcm43xx_firmware

and was told it had successfully installed.

next up I did:

/usr/sbin/iwconfig and got-

lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11bg ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off

Supergibbon · August 29, 2010, 3:55pm

sudo /usr/sbin/iwlist scan
root’s password:
lo Interface doesn’t support scanning.

eth0 Interface doesn’t support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:1F:33:EF:0F:ED
Channel:1
Frequency:2.412 GHz (Channel 1)
Quality=29/70 Signal level=-81 dBm
Encryption key:on
ESSID:“HotelZulu”
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s
Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
Mode:Master
Extra:tsf=0000000000959528
Extra: Last beacon: 1184ms ago
IE: Unknown: 0009486F74656C5A756C75
IE: Unknown: 010882848B960C121824
IE: Unknown: 030101
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
IE: Unknown: 2A0100
IE: Unknown: 32043048606C
IE: Unknown: DD180050F2020101820003A4000027A4000042435E0062322F00
IE: Unknown: DD1E00904C334C101BFFFF000000000000000000000000000000000000000000
IE: Unknown: 2D1A4C101BFFFF000000000000000000000000000000000000000000
IE: Unknown: DD1A00904C3401001B00000000000000000000000000000000000000
IE: Unknown: 3D1601001B00000000000000000000000000000000000000
IE: Unknown: DD0900037F01010000FF7F
IE: Unknown: DD0A00037F04010000000000
IE: Unknown: DD820050F204104A000110104400010210570001011041000100103B00010310470010565AA94967C14C0EAA8FF349E6F593111021000D4E6574676561722C20496E632E10230007574E523230303010240007574E523230303010420004353637381054000800060050F204000110110007574E5232303030100800020084103C000103
Cell 02 - Address: 00:0E:2E:EB:A0:56
Channel:11
Frequency:2.462 GHz (Channel 11)
Quality=34/70 Signal level=-76 dBm
Encryption key:on
ESSID:“default”
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s
Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
Mode:Master
Extra:tsf=00000034f9f0419b
Extra: Last beacon: 398ms ago
IE: Unknown: 000764656661756C74
IE: Unknown: 010882840B160C121824
IE: Unknown: 03010B
IE: Unknown: 2A0100
IE: Unknown: 32043048606C
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
IE: Unknown: DD0700E04C01020300

Finally:

dmesg | egrep “ssb|b43” gives -

9.747126] b43-pci-bridge 0000:03:02.0: PCI INT A -&gt; GSI 21 (level, low) -&gt; IRQ 21
9.756078] ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x0D, vendor 0x4243)
9.756091] ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x09, vendor 0x4243)
9.756101] ssb: Core 2 found: PCI (cc 0x804, rev 0x0C, vendor 0x4243)
9.756110] ssb: Core 3 found: PCMCIA (cc 0x80D, rev 0x07, vendor 0x4243)
9.775225] ssb: Sonics Silicon Backplane found on PCI device 0000:03:02.0
9.934759] b43-phy0: Broadcom 4318 WLAN found (core revision 9)

10.088995] Registered led device: b43-phy0::radio
47.786099] b43 ssb0:0: firmware: requesting b43/ucode5.fw
47.801991] b43 ssb0:0: firmware: requesting b43/pcm5.fw
47.823463] b43 ssb0:0: firmware: requesting b43/b0g0initvals5.fw
47.837062] b43 ssb0:0: firmware: requesting b43/b0g0bsinitvals5.fw
48.215068] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
4373.476045] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:

So it tells me the firmware’s installed but dmesg |egrep tells me it’s still requesting.
Also, I can’t find the command to repeat but one of the list tells me that the ‘drivers are loaded but device not found’.
If there’s any other info that’d help, such as Access Point, Vendor etc. then I can refind them, but for now I’m feeling a bit stuck.
Keep on digging eh, I’ll a way in the end (I hope)
Ps. sorry for doing 2 posts but I couldn’t work out what the 6 video or picture files I wasn’t allowed were so split the message in 2.

Supergibbon · August 29, 2010, 4:57pm

Just found one more command that might be uselful in showing what’s going on.

nm-tool gives:

iain@linux-w7tn:~> nm-tool

NetworkManager Tool

State: connected

Device: wlan0 ----------------------------------------------------------------
Type: 802.11 WiFi
Driver: b43
State: disconnected
Default: no
HW Address: 00:14:A5:27:EB:2D

Capabilities:

Wireless Properties
WEP Encryption: yes
WPA Encryption: yes
WPA2 Encryption: yes

Wireless Access Points
HotelZulu: Infra, 00:1F:33:EF:0F:ED, Freq 2412 MHz, Rate 54 Mb/s, Strength 54 WPA WPA2
default: Infra, 00:0E:2E:EB:A0:56, Freq 2462 MHz, Rate 54 Mb/s, Strength 48 WPA
Device: eth0 [Auto eth0] ----------------------------------------------------
Type: Wired
Driver: 8139too
State: connected
Default: yes
HW Address: 00:0F:B0:BA:5B:9C

Capabilities:
Carrier Detect: yes
Speed: 100 Mb/s

Wired Properties
Carrier: on

IPv4 Settings:
Address: 192.168.2.103
Prefix: 24 (255.255.255.0)
Gateway: 192.168.2.1

DNS: 192.168.2.1

iain@liain@linux-w7tn:~> nm-tool

NetworkManager Tool

State: connected

Device: wlan0 ----------------------------------------------------------------
Type: 802.11 WiFi
Driver: b43
State: disconnected
Default: no
HW Address: 00:14:A5:27:EB:2D

Capabilities:

Wireless Properties
WEP Encryption: yes
WPA Encryption: yes
WPA2 Encryption: yes

Wireless Access Points
HotelZulu: Infra, 00:1F:33:EF:0F:ED, Freq 2412 MHz, Rate 54 Mb/s, Strength 54 WPA WPA2
default: Infra, 00:0E:2E:EB:A0:56, Freq 2462 MHz, Rate 54 Mb/s, Strength 48 WPA
Device: eth0 [Auto eth0] ----------------------------------------------------
Type: Wired
Driver: 8139too
State: connected
Default: yes
HW Address: 00:0F:B0:BA:5B:9C

Capabilities:
Carrier Detect: yes
Speed: 100 Mb/s

Wired Properties
Carrier: on

IPv4 Settings:
Address: 192.168.2.103
Prefix: 24 (255.255.255.0)
Gateway: 192.168.2.1

DNS: 192.168.2.1

lwfinger · August 29, 2010, 4:57pm

Requesting firmware is OK. If it cannot find and load it, then you get a
different message. That part is OK.

Connecting to either of the AP’s in your scan list will be difficult as the
signals are very weak. From what I can see, you only need to use the applet to
create a new connection for your AP.

I have said this many times, but firmware is NOT a driver!!

Supergibbon · August 29, 2010, 6:56pm

Hi again,

Sorry to sound like a dunce, I’m used to a lifetime of clicking my way round windows. By the applet do you mean Network Manager applet? This refuses to load or do anything at all when clicked on. I can move to my flatmates room where the router is to get a better signal.
Sorry for taking your time, it’s greatly appreciated as it’s all driving me a bit nuts. : )

Iain

lwfinger · August 29, 2010, 8:31pm

On 08/29/2010 12:06 PM, Supergibbon wrote:
> Sorry to sound like a dunce, I’m used to a lifetime of clicking my way
> round windows. By the applet do you mean Network Manager applet? This
> refuses to load or do anything at all when clicked on. I can move to my
> flatmates room where the router is to get a better signal.
> Sorry for taking your time, it’s greatly appreciated as it’s all
> driving me a bit nuts. : )

One thing to remember, there are several desktops on Linux. I will be giving you
the instructions for KDE. If you have Gnome, then things may be different. If
you click on the applet, do you see a popup? That is all you will get. Click on
the “Manage Connections” option and fill in the connection details on the
wireless tab on the screen that comes up.

Supergibbon · August 29, 2010, 9:50pm

No, as I was saying Network Manager applet is doing nothing - no popup’s, no ‘manage connections’, no applet. I dont know if that’s a faulty KDE installation, I could try reinstalling, or maybe there’s links/instructions on connecting with ifup?

lwfinger · August 29, 2010, 10:18pm

On 08/29/2010 03:06 PM, Supergibbon wrote:
>
> No, as I was saying Network Manager applet is doing nothing - no
> popup’s, no ‘manage connections’, no applet. I dont know if that’s a
> faulty KDE installation, I could try reinstalling, or maybe there’s
> links/instructions on connecting with ifup?

No applet is different that nothing happening. What do you see with the command
‘ps ax | grep etw’?

Supergibbon · August 29, 2010, 10:49pm

I get

iain@linux-w7tn:~> ps ax | grep etw
4683 ? S 0:00 /usr/bin/knetworkmanager
9895 ? Ssl 0:00 /usr/sbin/NetworkManager
9924 ? S 0:00 /sbin/dhclient -d -sf /usr/lib/NetworkManager/nm-dhcp-client.action -pf /var/run/dhclient-eth0.pid -lf /var/lib/dhcp/dhclient-010fc334-5cca-4837-bb69-8a90356c6542-eth0.lease -cf /var/run/nm-dhclient-eth0.conf eth0
10521 pts/0 S+ 0:00 grep etw

lwfinger · August 30, 2010, 2:35am

Obviously knetworkmanager is running. There should be an applet icon in the
lower-right corner of the screen in the system tray.

Supergibbon · August 30, 2010, 7:56pm

There probably should be but there isn’t I’m afraid. If it is running then it definitely isn’t obvious - there’s no applet icon in any corner. In fact there’s no network manager icon at all without doing a search, and once you get to that one then there’s no response at all when you click it.

lwfinger · August 30, 2010, 9:12pm

On 08/30/2010 01:36 PM, Supergibbon wrote:
>
> There probably should be but there isn’t I’m afraid. If it is running
> then it definitely isn’t obvious - there’s no applet icon in any corner.
> In fact there’s no network manager icon at all without doing a search,
> and once you get to that one then there’s no response at all when you
> click it.

I have never seen knetworkmanager fail to load an icon in the system tray when
it starts. You should reinstall NetworkManager and knetworkmanager to see if
that will fix the problem. There will be nothing showing for NetworkManager.