[SOLVED] Second of two problems

[JimBoCol]

This one is the biggie. This has been driving me crazy since I installed Ubuntu. I have no way of knowing if I am connected to my wireless network. The straw that broke the Camel's back was last night when for one reason or another, the connection was dropped, and I had no way of knowing it. I messed around for 3 1/2 hours changing software settings, and running in circles. I finally decided to just reboot the system, and the connection came back. I still had no way of knowing that.

Had the LEDs on my notebook adapter been working, I could have saved myself hours of frustration and aggravation.

I am still so ticked off over that, I'm to the point that if this can not be corrected, this may very well be the end of my using Linux.

I assume this problem will arise from the adapter card. I took screen shots of everything.

Note all of the blank spaces that when clicked on, display LEDs, and nothing more, (led1.jpg)


I have taken a screen shot of the properties of each of those entries, (led_properties.jpg).

how do I get the LEDs on my adapter working so I know when there is a connection, and when data is being transmitted and received?

thanks,
Jim.

[Rubberman]

What desktop are you running? There is an icon in the task bar on top of the screen in the Gnome desktop that shows the connection status and signal strength. If you have accidentally removed it, you can restore the icon.

[JimBoCol]

What desktop are you running? There is an icon in the task bar on top of the screen in the Gnome desktop that shows the connection status and signal strength. If you have accidentally removed it, you can restore the icon.

There never was any icon on any task bar. I think I'm running Gnome. I see a lot of that referenced. Or perhaps GNU, I see tha too. To be honest, I really don't have any idea what I"m running. I don't even know how I got the wireless working. When I first installed Linux, it could not see the card,. and I just kept downloading things that had to do with wireless until I finally was able to surf the Internet. If you have read my previous posts, my wireless card appears to be dead, and shows no signs of life at all, but there is a connection. This makes trying to figure out email problems nearly impossible, because I don't' know if it's hung, trying to connect and being rejected, timing out, or anything. I see no signs of any network activity. I have Thunderibird, and Evolution both, and they behave in the same manor.

Thanks,
Jim.

[devils casper]

Execute this in Terminal

cat /etc/lsb-release

Post output here.

Right click on Top Panel and select Add Applet. Select Network Applet from the list and check if it display relevant information of your Card.

[JimBoCol]

Execute this in Terminal

cat /etc/lsb-release

Post output here.

jim@TP-T23:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=9.10
DISTRIB_CODENAME=karmic
DISTRIB_DESCRIPTION="Ubuntu 9.10"
jim@TP-T23:~$

Right click on Top Panel and select Add Applet. Select Network Applet from the list and check if it display relevant information of your Card.

The only thing like that available was add to Panel. Once I opened that, the only thing that had anything to do with a Network was Connect to a Server.

The only things I saw on add to panel that had anything to do with display was Brightness, and Character Palette.

Thanks,
JIm.

[reed9]

GNOME is the default in regular Ubuntu.

Screenshots of the networkmanager are
here and here.

The wireless icon is the far left in the first and one to the left of the envelope icon in the second. You're missing that?

[reed9]

Oh, hey, I don't think we ever established just what the chipset of your wireless is. Can you post the output of

lspci -vnn

There is probable a solution to the LED light problem as well.

[JimBoCol]

GNOME is the default in regular Ubuntu.

Screenshots of the networkmanager are
here and here.

The wireless icon is the far left in the first and one to the left of the envelope icon in the second. You're missing that?

There is a strange little icon there today that was never there before. It's green,and black, and when I mouse over it, it tells me that I"m connected to what SSID, and the signal strength. When I right click on it, I am presented with three options, Connect, About, Quit. When I mouse over connect, it expands another menu showing me the various local available SSIDs

Now that's more like it. Where did it come from, and why has it only just now appeared?

Thanks,
Jim.

[JimBoCol]

Oh, hey, I don't think we ever established just what the chipset of your wireless is. Can you post the output of

lspci -vnn

There is probable a solution to the LED light problem as well.

Here it is:

jim@TP-T23:~$ sudo lspci -vnn
[sudo] password for jim: 
00:00.0 Host bridge [0600]: Intel Corporation 82830 830 Chipset Host Bridge [8086:3575] (rev 04)
	Subsystem: IBM Device [1014:021d]
	Flags: bus master, fast devsel, latency 0
	Memory at d0000000 (32-bit, prefetchable) [size=256M]
	Capabilities: [40] Vendor Specific Information <?>
	Capabilities: [a0] AGP version 2.0
	Kernel driver in use: agpgart-intel
	Kernel modules: intel-agp

00:01.0 PCI bridge [0604]: Intel Corporation 82830 830 Chipset AGP Bridge [8086:3576] (rev 04)
	Flags: bus master, 66MHz, fast devsel, latency 96
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
	Memory behind bridge: c0100000-c01fffff
	Prefetchable memory behind bridge: e0000000-ebffffff
	Kernel modules: shpchp

00:1d.0 USB Controller [0c03]: Intel Corporation 82801CA/CAM USB Controller #1 [8086:2482] (rev 02)
	Subsystem: IBM Device [1014:0220]
	Flags: bus master, medium devsel, latency 0, IRQ 11
	I/O ports at 1800 [size=32]
	Kernel driver in use: uhci_hcd

00:1d.1 USB Controller [0c03]: Intel Corporation 82801CA/CAM USB Controller #2 [8086:2484] (rev 02)
	Subsystem: IBM Device [1014:0220]
	Flags: bus master, medium devsel, latency 0, IRQ 11
	I/O ports at 1820 [size=32]
	Kernel driver in use: uhci_hcd

00:1d.2 USB Controller [0c03]: Intel Corporation 82801CA/CAM USB Controller #3 [8086:2487] (rev 02)
	Subsystem: IBM Device [1014:0220]
	Flags: bus master, medium devsel, latency 0, IRQ 11
	I/O ports at 1840 [size=32]
	Kernel driver in use: uhci_hcd

00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev 42)
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=02, subordinate=08, sec-latency=64
	I/O behind bridge: 00002000-00006fff
	Memory behind bridge: c0200000-cfffffff
	Prefetchable memory behind bridge: f0000000-f7ffffff
	Kernel modules: shpchp

00:1f.0 ISA bridge [0601]: Intel Corporation 82801CAM ISA Bridge (LPC) [8086:248c] (rev 02)
	Flags: bus master, medium devsel, latency 0
	Kernel modules: iTCO_wdt, intel-rng

00:1f.1 IDE interface [0101]: Intel Corporation 82801CAM IDE U100 Controller [8086:248a] (rev 02) (prog-if 8a [Master SecP PriP])
	Subsystem: IBM Device [1014:0220]
	Flags: bus master, medium devsel, latency 0, IRQ 11
	I/O ports at 01f0 [size=8]
	I/O ports at 03f4 [size=1]
	I/O ports at 0170 [size=8]
	I/O ports at 0374 [size=1]
	I/O ports at 1860 [size=16]
	Memory at 40000000 (32-bit, non-prefetchable) [size=1K]
	Kernel driver in use: ata_piix

00:1f.3 SMBus [0c05]: Intel Corporation 82801CA/CAM SMBus Controller [8086:2483] (rev 02)
	Subsystem: IBM Device [1014:0220]
	Flags: medium devsel, IRQ 11
	I/O ports at 1880 [size=32]
	Kernel modules: i2c-i801

00:1f.5 Multimedia audio controller [0401]: Intel Corporation 82801CA/CAM AC'97 Audio Controller [8086:2485] (rev 02)
	Subsystem: IBM Device [1014:0222]
	Flags: bus master, medium devsel, latency 0, IRQ 11
	I/O ports at 1c00 [size=256]
	I/O ports at 18c0 [size=64]
	Kernel driver in use: Intel ICH
	Kernel modules: snd-intel8x0

01:00.0 VGA compatible controller [0300]: S3 Inc. SuperSavage IX/C SDR [5333:8c2e] (rev 05)
	Subsystem: IBM Device [1014:01fc]
	Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 11
	Memory at c0100000 (32-bit, non-prefetchable) [size=512K]
	Memory at e8000000 (32-bit, prefetchable) [size=64M]
	Memory at e4000000 (32-bit, prefetchable) [size=64M]
	Memory at e0000000 (32-bit, prefetchable) [size=32M]
	[virtual] Expansion ROM at e2000000 [disabled] [size=64K]
	Capabilities: [dc] Power Management version 2
	Capabilities: [80] AGP version 2.0
	Kernel modules: savagefb

02:00.0 CardBus bridge [0607]: Texas Instruments PCI1420 PC card Cardbus Controller [104c:ac51]
	Subsystem: IBM Device [1014:023b]
	Flags: bus master, medium devsel, latency 168, IRQ 11
	Memory at 50000000 (32-bit, non-prefetchable) [size=4K]
	Bus: primary=02, secondary=03, subordinate=06, sec-latency=176
	Memory window 0: f0000000-f3fff000 (prefetchable)
	Memory window 1: c4000000-c7fff000
	I/O window 0: 00002000-000020ff
	I/O window 1: 00002400-000024ff
	16-bit legacy interface ports at 0001
	Kernel driver in use: yenta_cardbus
	Kernel modules: yenta_socket

02:00.1 CardBus bridge [0607]: Texas Instruments PCI1420 PC card Cardbus Controller [104c:ac51]
	Subsystem: IBM Device [1014:023b]
	Flags: bus master, medium devsel, latency 168, IRQ 11
	Memory at 51000000 (32-bit, non-prefetchable) [size=4K]
	Bus: primary=02, secondary=07, subordinate=07, sec-latency=176
	Memory window 0: f4000000-f7fff000 (prefetchable)
	Memory window 1: c8000000-cbfff000
	I/O window 0: 00002800-000028ff
	I/O window 1: 00002c00-00002cff
	16-bit legacy interface ports at 0001
	Kernel driver in use: yenta_cardbus
	Kernel modules: yenta_socket

02:02.0 Communication controller [0780]: Agere Systems WinModem 56k [11c1:0449] (rev 01)
	Subsystem: AMBIT Microsystem Corp. Device [1468:0410]
	Flags: bus master, medium devsel, latency 0, IRQ 11
	Memory at c0201000 (32-bit, non-prefetchable) [size=256]
	I/O ports at 6440 [size=8]
	I/O ports at 6000 [size=256]
	Capabilities: [f8] Power Management version 2

02:08.0 Ethernet controller [0200]: Intel Corporation 82801CAM (ICH3) PRO/100 VE (LOM) Ethernet Controller [8086:1031] (rev 42)
	Subsystem: IBM Device [1014:0209]
	Flags: bus master, medium devsel, latency 66, IRQ 11
	Memory at c0200000 (32-bit, non-prefetchable) [size=4K]
	I/O ports at 6400 [size=64]
	Capabilities: [dc] Power Management version 2
	Kernel driver in use: e100
	Kernel modules: e100

07:00.0 Network controller [0280]: Atheros Communications Inc. AR5008 Wireless Network Adapter [168c:0023] (rev 01)
	Subsystem: D-Link System Inc Device [1186:3a6e]
	Flags: bus master, 66MHz, medium devsel, latency 168, IRQ 11
	Memory at c8000000 (32-bit, non-prefetchable) [size=64K]
	Capabilities: [40] #80 [0000]
	Kernel driver in use: ath9k
	Kernel modules: ath9k

jim@TP-T23:~$

Thanks,
Jim.

[reed9]

Alright, I believe for the LED, there might be some way to trigger it by changing the values of various files in /sys/class/leds/ath9k*

I'm not sure exactly what might need to be done, but I'll look around.

You can also try installing some backported drivers, which may contain an update for the ath9k module. Could possibly fix it.

sudo apt-get install linux-backports-modules-karmic