Ubuntu

Wireless Problem with Upgrade to 9.10

Asked by Jim Hyde

I have two laptops running Ubuntu--a Dell Mini 9 ( running 8.04 this machine) and a Dell 1530 which I just upgraded to 9.10 from 9.04. The problem is with the Dell 1530.

Prior to upgrading to 9.10 things worked fine. When I upgraded the install went fine and all of the applications I have tried Open Office etc. seem to work. All EXCEPT my wireless Internet access. The machine recognizes the wireless signals, automatically handshakes with them. I can print wirelessly. However, I have no Internet access. I cannot follow the Ububtu Troubleshooting guide because I cannot access the internet.

Thus I am reliant on using this machine the Mini 9 running 8.04.

Can you help me trouble shoot this problem. I assume the problem is with the driver for the Wireless card. I have pasted below the message I get when I run: sudo lshw -C network as directed in the trouble shooting guide.

root@jim-laptop:/home/jim# sudo lshw -C network
  *-network
       description: Ethernet interface
       product: 88E8040 PCI-E Fast Ethernet Controller
       vendor: Marvell Technology Group Ltd.
       physical id: 0
       bus info: pci@0000:09:00.0
       logical name: eth0
       version: 12
       serial: 00:15:c5:81:b6:e2
       capacity: 100MB/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=sky2 driverversion=1.23 firmware=N/A latency=0 link=no multicast=yes port=twisted pair
       resources: irq:29 memory:f9ffc000-f9ffffff ioport:de00(size=256)
  *-network
       description: Network controller
       product: BCM4312 802.11a/b/g
       vendor: Broadcom Corporation
       physical id: 0
       bus info: pci@0000:0b:00.0
       version: 01
       width: 32 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list
       configuration: driver=b43-pci-bridge latency=0
       resources: irq:17 memory:f9efc000-f9efffff
  *-network
       description: Wireless interface
       physical id: 2
       logical name: wlan0
       serial: 00:1e:4c:67:15:63
       capabilities: ethernet physical wireless
       configuration: broadcast=yes ip=192.168.1.100 multicast=yes wireless=IEEE 802.11bg
root@jim-laptop:/home/jim#

Note: I also tried connecting directly through an Ethernet connection this did not work either.

Thanks for your help.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Mark Rijckenberg
Solved:
Last query:
Last reply:
Revision history for this message
Juan Carlos Inostroza (jci) said : 		#1

Hi,

please post the following:

- output of ifconfig -a
- output of route -n
- output of /etc/resolv.conf

Also, are you using Network Manager to handle the wireless connection?

Revision history for this message
Jim Hyde (james-hyde) said : 		#2

Hi

Here's the output requested. Note I get "permission denied" when I tried running /etc/resolv.conf.
NOTE. I am using the network connections selection under System->preferences->network connections.

root@jim-laptop:/home/jim# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:15:c5:81:b6:e2
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
          Interrupt:16

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:4 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:240 (240.0 B) TX bytes:240 (240.0 B)

wlan0 Link encap:Ethernet HWaddr 00:1e:4c:67:15:63
          inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0
          inet6 addr: fe80::21e:4cff:fe67:1563/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:9651 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7668 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1280475 (1.2 MB) TX bytes:4742022 (4.7 MB)

wmaster0 Link encap:UNSPEC HWaddr 00-1E-4C-67-15-63-36-37-00-00-00-00-00-00-00-00
          UP RUNNING MTU:0 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

root@jim-laptop:/home/jim# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 2 0 0 wlan0
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 wlan0
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 wlan0
root@jim-laptop:/home/jim# /etc/resolv.conf
bash: /etc/resolv.conf: Permission denied
root@jim-laptop:/home/jim#

Thanks for your help.

Revision history for this message
Juan Carlos Inostroza (jci) said : 		#3

Hi Jim,

sorry, I misplaced a command. The output of /etc/resolv.conf should be

$ cat /etc/resolv.conf

what i can see here is that your network connection *does actually* work and the default gateway is being set to wlan0 (the wireless interface), so the problem just could be name resolution and/or router support.

Let's dissect this, shall we? :-)

First, Are you using Network Manager?

Try the following on a terminal:

$ ping 192.168.1.1
(or the IP address of your internet router)

This *should* work.

Try then:

$ ping www.google.com
$ ping 74.125.45.105

(both are the same in my case)

At least one of them should work.

Try getting the output of the following

$ ls -als /etc/resolv.conf

Then

$ cat /etc/resolv.conf

See what's the output of it. In my case it's "192.168.1.1". If the file is empty, then it could be a name resolution problem. Not a big deal.

In my case, the output of "cat /etc/resolv.conf" its "192.168.1.1" (my trustry router). Also does name resolution, so to test it, I'll run the following command to check:

$ nslookup - 192.168.1.1

a prompt should appear
>

type any domain i.e. "www.google.com" and wait for the results. In my case:

> www.google.com
Server: 192.168.1.1
Address: 192.168.1.1#53

Non-authoritative answer:
www.google.com canonical name = www.l.google.com.
Name: www.l.google.com
Address: 74.125.45.99
....

If this test did not work, please check the setup of Name servers in your router. Could be just that.

Then check for the permissions on /etc/resolv.conf

$ ls -als /etc/resolv.conf

In my case,

jci@zaphod:/media/JCI$ ls -als /etc/resolv.conf
4 -rw-r--r-- 1 root root 53 2009-11-10 22:00 /etc/resolv.conf

Hope this helps. Good luck!
--j

Revision history for this message
Mark Rijckenberg (markrijckenberg) said : 		#4

Hi,

Please first follow Juan Carlos Inostroza's advice.

Furthermore, please also follow this procedure below to give us more info about the wireless issue.

Please first connect your network card to the wireless router using an ethernet cable (also known as a LAN cable).

In order to gather essential troubleshooting information about your wireless card, please follow this procedure:

Step 1: Open Terminal from "Applications->Accessories->Terminal"

Step 2: Please copy-paste the following command from the https://answers.launchpad.net/ubuntu website in Firefox into the Linux Terminal. Do NOT copy-paste from the Email message into the Terminal, as that will only copy PART of the command. The command STARTS with the word sudo and ENDS with the word restart. So please copy-paste the ENTIRE command below from Firefox into a Terminal, press <enter>, then enter password when sudo asks for password, then press enter again.

sudo lshw -C network; sudo iwlist scanning; cat /etc/network/interfaces; cat /etc/lsb-release; lspci -nn; lsusb; sudo lshw -C usb; uname -a; dmesg | grep ound; dmesg | grep b43; dmesg | grep iwl; iwconfig; sudo /etc/init.d/networking restart

Step 3: Please post results (copy/paste terminal output) on this thread

Regards,

Mark

Revision history for this message
Mark Rijckenberg (markrijckenberg) said : 		#5

Please first try the solution from Tom Haddon from this location:

https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/385293

If that does not help, please try the solution from Ayuthia from this location:

http://ubuntuforums.org/showthread.php?p=8297306

Revision history for this message
Jim Hyde (james-hyde) said : 		#6

Juan Carlos-I think you are getting there. Here's what happens when I
follow your instructions.

1. When I ping the router 192.68.1.1 I get the appropriate response
times back
2. When I ping www.google.com I get: Ping Unknown host
3. When I ping 74.125.45.105---Voila! I get response times back
Also I went ahead and entered the IP address in Firefox again Voila! The
page came up. There is clearly a problem with the address translation--no?
4. I have pasted below the output from the other commands as instructed.

Again, I really appreciate all of the effort you have put into this. I
feel at least now as if we are getting there.

Jim

November 12, 2009 0729

root@jim-laptop:/home/jim# ls -als /etc/resolv.conf
4 -rw-r--r-- 1 root root 30 2009-11-12 07:29 /etc/resolv.conf
root@jim-laptop:/home/jim#

root@jim-laptop:/home/jim# cat /etc/resolv.conf
# Generated by NetworkManager
root@jim-laptop:/home/jim# nslookup - 192.168.1.1
 > www.google.com
Server: 192.168.1.1
Address: 192.168.1.1#53

Non-authoritative answer:
www.google.com canonical name = www.l.google.com.
Name: www.l.google.com
Address: 66.249.81.104
root@jim-laptop:/home/jim# ls -als /etc/resolv.conf
4 -rw-r--r-- 1 root root 30 2009-11-12 07:29 /etc/resolv.conf
root@jim-laptop:/home/jim#

Juan Carlos Inostroza wrote:

> Your question #89742 on Ubuntu changed:
> https://answers.edge.launchpad.net/ubuntu/+question/89742
>
> Status: Open => Needs information
>
> Juan Carlos Inostroza requested for more information:
> Hi Jim,
>
> sorry, I misplaced a command. The output of /etc/resolv.conf should be
>
> $ cat /etc/resolv.conf
>
> what i can see here is that your network connection *does actually* work
> and the default gateway is being set to wlan0 (the wireless interface),
> so the problem just could be name resolution and/or router support.
>
> Let's dissect this, shall we? :-)
>
> First, Are you using Network Manager?
>
> Try the following on a terminal:
>
> $ ping 192.168.1.1
> (or the IP address of your internet router)
>
> This *should* work.
>
> Try then:
>
> $ ping www.google.com
> $ ping 74.125.45.105
>
> (both are the same in my case)
>
> At least one of them should work.
>
> Try getting the output of the following
>
> $ ls -als /etc/resolv.conf
>
> Then
>
> $ cat /etc/resolv.conf
>
> See what's the output of it. In my case it's "192.168.1.1". If the file
> is empty, then it could be a name resolution problem. Not a big deal.
>
> In my case, the output of "cat /etc/resolv.conf" its "192.168.1.1" (my
> trustry router). Also does name resolution, so to test it, I'll run the
> following command to check:
>
> $ nslookup - 192.168.1.1
>
> a prompt should appear
>
>
> type any domain i.e. "www.google.com" and wait for the results. In my
> case:
>
>
>> www.google.com
>>
> Server: 192.168.1.1
> Address: 192.168.1.1#53
>
> Non-authoritative answer:
> www.google.com canonical name = www.l.google.com.
> Name: www.l.google.com
> Address: 74.125.45.99
> ....
>
> If this test did not work, please check the setup of Name servers in
> your router. Could be just that.
>
> Then check for the permissions on /etc/resolv.conf
>
> $ ls -als /etc/resolv.conf
>
> In my case,
>
> jci@zaphod:/media/JCI$ ls -als /etc/resolv.conf
> 4 -rw-r--r-- 1 root root 53 2009-11-10 22:00 /etc/resolv.conf
>
> Hope this helps. Good luck!
> --j
>
>

--
************************************************************
James Hyde
Associate Professor Emeritus
Tufts University School of Medicine
Department of Public Health and Community Medicine
136 Harrison Ave.
Boston, Ma 02111
<email address hidden>
************************************************************

Revision history for this message
Jim Hyde (james-hyde) said : 		#7

Mark--here.s the output as instructed.

sudo lshw -C network; sudo iwlist scanning; cat
/etc/network/interfaces; cat /etc/lsb-release; lspci -nn; lsusb; sudo
lshw -C usb; uname -a; dmesg | grep ound; dmesg | grep b43; dmesg | grep
iwl; iwconfig; sudo /etc/init.d/networking restart
[sudo] password for jim:
  *-network
       description: Ethernet interface
       product: 88E8040 PCI-E Fast Ethernet Controller
       vendor: Marvell Technology Group Ltd.
       physical id: 0
       bus info: pci@0000:09:00.0
       logical name: eth0
       version: 12
       serial: 00:15:c5:81:b6:e2
       size: 100MB/s
       capacity: 100MB/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list ethernet
physical tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=sky2
driverversion=1.23 duplex=full firmware=N/A ip=192.168.1.105 latency=0
link=yes multicast=yes port=twisted pair speed=100MB/s
       resources: irq:29 memory:f9ffc000-f9ffffff ioport:de00(size=256)
  *-network
       description: Network controller
       product: BCM4312 802.11a/b/g
       vendor: Broadcom Corporation
       physical id: 0
       bus info: pci@0000:0b:00.0
       version: 01
       width: 32 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list
       configuration: driver=b43-pci-bridge latency=0
       resources: irq:17 memory:f9efc000-f9efffff
  *-network
       description: Wireless interface
       physical id: 2
       logical name: wlan0
       serial: 00:1e:4c:67:15:63
       capabilities: ethernet physical wireless
       configuration: broadcast=yes ip=192.168.1.100 multicast=yes
wireless=IEEE 802.11bg
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wmaster0 Interface doesn't support scanning.

wlan0 Scan completed :
          Cell 01 - Address: 00:14:BF:DF:17:93
                    Channel:6
                    Frequency:2.437 GHz (Channel 6)
                    Quality=62/70 Signal level=-48 dBm
                    Encryption key:on
                    ESSID:"HerkulonVt"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
                              24 Mb/s; 36 Mb/s; 54 Mb/s
                    Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
                    Mode:Master
                    Extra:tsf=00000024502c5187
                    Extra: Last beacon: 368ms ago
                    IE: Unknown: 000A4865726B756C6F6E5674
                    IE: Unknown: 010882848B962430486C
                    IE: Unknown: 030106
                    IE: Unknown: 2A0104
                    IE: Unknown: 2F0104
                    IE: Unknown: 32040C121860
                    IE: Unknown: DD06001018020010
                    IE: WPA Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (1) : TKIP
                        Authentication Suites (1) : PSK

auto lo
iface lo inet loopback

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=9.10
DISTRIB_CODENAME=karmic
DISTRIB_DESCRIPTION="Ubuntu 9.10"
00:00.0 Host bridge [0600]: Intel Corporation Mobile PM965/GM965/GL960
Memory Controller Hub [8086:2a00] (rev 0c)
00:01.0 PCI bridge [0604]: Intel Corporation Mobile PM965/GM965/GL960
PCI Express Root Port [8086:2a01] (rev 0c)
00:1a.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family)
USB UHCI Controller #4 [8086:2834] (rev 02)
00:1a.1 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family)
USB UHCI Controller #5 [8086:2835] (rev 02)
00:1a.7 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family)
USB2 EHCI Controller #2 [8086:283a] (rev 02)
00:1b.0 Audio device [0403]: Intel Corporation 82801H (ICH8 Family) HD
Audio Controller [8086:284b] (rev 02)
00:1c.0 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI
Express Port 1 [8086:283f] (rev 02)
00:1c.1 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI
Express Port 2 [8086:2841] (rev 02)
00:1c.4 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI
Express Port 5 [8086:2847] (rev 02)
00:1d.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family)
USB UHCI Controller #1 [8086:2830] (rev 02)
00:1d.1 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family)
USB UHCI Controller #2 [8086:2831] (rev 02)
00:1d.2 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family)
USB UHCI Controller #3 [8086:2832] (rev 02)
00:1d.7 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family)
USB2 EHCI Controller #1 [8086:2836] (rev 02)
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge
[8086:2448] (rev f2)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801HEM (ICH8M) LPC
Interface Controller [8086:2815] (rev 02)
00:1f.1 IDE interface [0101]: Intel Corporation 82801HBM/HEM
(ICH8M/ICH8M-E) IDE Controller [8086:2850] (rev 02)
00:1f.2 SATA controller [0106]: Intel Corporation 82801HBM/HEM
(ICH8M/ICH8M-E) SATA AHCI Controller [8086:2829] (rev 02)
00:1f.3 SMBus [0c05]: Intel Corporation 82801H (ICH8 Family) SMBus
Controller [8086:283e] (rev 02)
01:00.0 VGA compatible controller [0300]: nVidia Corporation G86
[GeForce 8400M GS] [10de:0427] (rev a1)
03:09.0 FireWire (IEEE 1394) [0c00]: Ricoh Co Ltd R5C832 IEEE 1394
Controller [1180:0832] (rev 05)
03:09.1 SD Host controller [0805]: Ricoh Co Ltd R5C822
SD/SDIO/MMC/MS/MSPro Host Adapter [1180:0822] (rev 22)
03:09.2 System peripheral [0880]: Ricoh Co Ltd R5C592 Memory Stick Bus
Host Adapter [1180:0592] (rev 12)
03:09.3 System peripheral [0880]: Ricoh Co Ltd xD-Picture Card
Controller [1180:0852] (rev 12)
09:00.0 Ethernet controller [0200]: Marvell Technology Group Ltd.
88E8040 PCI-E Fast Ethernet Controller [11ab:4354] (rev 12)
0b:00.0 Network controller [0280]: Broadcom Corporation BCM4312
802.11a/b/g [14e4:4312] (rev 01)
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 010: ID 0930:6545 Toshiba Corp. Kingston DataTraveler 2.0
Stick (4GB) / PNY Attache 4GB Stick
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 0483:2016 SGS Thomson Microelectronics
Fingerprint Reader
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 05a9:2640 OmniVision Technologies, Inc. OV2640
Webcam
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Linux jim-laptop 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:04:26
UTC 2009 i686 GNU/Linux
[ 1.033277] hub 6-0:1.0: USB hub found
[ 1.033549] hub 7-0:1.0: USB hub found
[ 1.049720] device-mapper: multipath round-robin: version 1.0.0 loaded
[ 1.052930] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[ 2.117181] ssb: Sonics Silicon Backplane found on PCI device
0000:0b:00.0
[ 7.714158] lp: driver loaded but no devices found
[ 7.816054] sdhci-pci 0000:03:09.1: SDHCI controller found
[1180:0822] (rev 22)
[ 9.345738] uvcvideo: Found UVC 1.00 device Laptop Integrated Webcam
(05a9:2640)
[ 9.363230] uvcvideo: UVC non compliance - GET_DEF(PROBE) not
supported. Enabling workaround.
[ 9.617777] b43-phy0: Broadcom 4311 WLAN found (core revision 10)
[ 11.585245] input: HDA Intel Mic at Ext Front Jack as
/devices/pci0000:00/0000:00:1b.0/sound/card0/input10
[ 11.585335] input: HDA Intel HP Out at Ext Front Jack as
/devices/pci0000:00/0000:00:1b.0/sound/card0/input11
[ 11.585409] input: HDA Intel HP Out at Ext Front Jack as
/devices/pci0000:00/0000:00:1b.0/sound/card0/input12
[ 1475.095047] usb-storage: device found at 2
[ 5786.894200] usb-storage: device found at 3
[ 6888.817881] usb-storage: device found at 4
[ 8204.109410] usb-storage: device found at 6
[ 8898.682081] usb-storage: device found at 7
[10714.025190] usb-storage: device found at 8
[12682.670067] usb-storage: device found at 9
[13132.809666] usb-storage: device found at 10
[ 2.027249] b43-pci-bridge 0000:0b:00.0: PCI INT A -> GSI 17 (level,
low) -> IRQ 17
[ 2.027271] b43-pci-bridge 0000:0b:00.0: setting latency timer to 64
[ 9.617777] b43-phy0: Broadcom 4311 WLAN found (core revision 10)
[ 18.973128] b43 ssb0:0: firmware: requesting b43/ucode5.fw
[ 19.663988] b43 ssb0:0: firmware: requesting b43/pcm5.fw
[ 20.425059] b43 ssb0:0: firmware: requesting b43/b0g0initvals5.fw
[ 20.866103] b43 ssb0:0: firmware: requesting b43/b0g0bsinitvals5.fw
[ 20.984113] b43-phy0: Loading firmware version 410.2160 (2007-05-26
15:32:10)
[ 21.060613] Registered led device: b43-phy0::tx
[ 21.060646] Registered led device: b43-phy0::rx
[ 21.060673] Registered led device: b43-phy0::radio
[ 758.972519] b43-pci-bridge 0000:0b:00.0: PCI INT A disabled
[ 759.583270] b43-pci-bridge 0000:0b:00.0: restoring config space at
offset 0xf (was 0x100, writing 0x107)
[ 759.583352] b43-pci-bridge 0000:0b:00.0: restoring config space at
offset 0x4 (was 0x0, writing 0xf9efc000)
[ 759.583368] b43-pci-bridge 0000:0b:00.0: restoring config space at
offset 0x3 (was 0x0, writing 0x10)
[ 759.583391] b43-pci-bridge 0000:0b:00.0: restoring config space at
offset 0x1 (was 0x100000, writing 0x100107)
[ 760.437370] b43-pci-bridge 0000:0b:00.0: PCI INT A -> GSI 17 (level,
low) -> IRQ 17
[ 761.968338] b43-phy0: Loading firmware version 410.2160 (2007-05-26
15:32:10)
[ 762.080604] Registered led device: b43-phy0::tx
[ 762.080636] Registered led device: b43-phy0::rx
[ 762.080666] Registered led device: b43-phy0::radio
[ 1602.120518] b43-pci-bridge 0000:0b:00.0: PCI INT A disabled
[ 1602.724296] b43-pci-bridge 0000:0b:00.0: restoring config space at
offset 0xf (was 0x100, writing 0x107)
[ 1602.724378] b43-pci-bridge 0000:0b:00.0: restoring config space at
offset 0x4 (was 0x0, writing 0xf9efc000)
[ 1602.724394] b43-pci-bridge 0000:0b:00.0: restoring config space at
offset 0x3 (was 0x0, writing 0x10)
[ 1602.724413] b43-pci-bridge 0000:0b:00.0: restoring config space at
offset 0x1 (was 0x100000, writing 0x100107)
[ 1603.576246] b43-pci-bridge 0000:0b:00.0: PCI INT A -> GSI 17 (level,
low) -> IRQ 17
[ 1605.092057] b43-phy0: Loading firmware version 410.2160 (2007-05-26
15:32:10)
[ 1605.232594] Registered led device: b43-phy0::tx
[ 1605.232626] Registered led device: b43-phy0::rx
[ 1605.232655] Registered led device: b43-phy0::radio
[ 6676.040510] b43-pci-bridge 0000:0b:00.0: PCI INT A disabled
[ 6676.771035] b43-pci-bridge 0000:0b:00.0: restoring config space at
offset 0xf (was 0x100, writing 0x107)
[ 6676.771117] b43-pci-bridge 0000:0b:00.0: restoring config space at
offset 0x4 (was 0x0, writing 0xf9efc000)
[ 6676.771133] b43-pci-bridge 0000:0b:00.0: restoring config space at
offset 0x3 (was 0x0, writing 0x10)
[ 6676.771156] b43-pci-bridge 0000:0b:00.0: restoring config space at
offset 0x1 (was 0x100000, writing 0x100107)
[ 6677.623851] b43-pci-bridge 0000:0b:00.0: PCI INT A -> GSI 17 (level,
low) -> IRQ 17
[ 6679.199647] b43-phy0: Loading firmware version 410.2160 (2007-05-26
15:32:10)
[ 6679.283612] Registered led device: b43-phy0::tx
[ 6679.283642] Registered led device: b43-phy0::rx
[ 6679.283672] Registered led device: b43-phy0::radio
[ 8759.724520] b43-pci-bridge 0000:0b:00.0: PCI INT A disabled
[ 8760.327186] b43-pci-bridge 0000:0b:00.0: restoring config space at
offset 0xf (was 0x100, writing 0x107)
[ 8760.327268] b43-pci-bridge 0000:0b:00.0: restoring config space at
offset 0x4 (was 0x0, writing 0xf9efc000)
[ 8760.327285] b43-pci-bridge 0000:0b:00.0: restoring config space at
offset 0x3 (was 0x0, writing 0x10)
[ 8760.327308] b43-pci-bridge 0000:0b:00.0: restoring config space at
offset 0x1 (was 0x100000, writing 0x100107)
[ 8761.179043] b43-pci-bridge 0000:0b:00.0: PCI INT A -> GSI 17 (level,
low) -> IRQ 17
[ 8762.656437] b43-phy0: Loading firmware version 410.2160 (2007-05-26
15:32:10)
[ 8762.796603] Registered led device: b43-phy0::tx
[ 8762.796631] Registered led device: b43-phy0::rx
[ 8762.796660] Registered led device: b43-phy0::radio
[ 9682.708519] b43-pci-bridge 0000:0b:00.0: PCI INT A disabled
[ 9683.315682] b43-pci-bridge 0000:0b:00.0: restoring config space at
offset 0xf (was 0x100, writing 0x107)
[ 9683.315764] b43-pci-bridge 0000:0b:00.0: restoring config space at
offset 0x4 (was 0x0, writing 0xf9efc000)
[ 9683.315780] b43-pci-bridge 0000:0b:00.0: restoring config space at
offset 0x3 (was 0x0, writing 0x10)
[ 9683.315803] b43-pci-bridge 0000:0b:00.0: restoring config space at
offset 0x1 (was 0x100000, writing 0x100107)
[ 9684.168560] b43-pci-bridge 0000:0b:00.0: PCI INT A -> GSI 17 (level,
low) -> IRQ 17
[ 9685.628063] b43-phy0: Loading firmware version 410.2160 (2007-05-26
15:32:10)
[ 9685.741765] Registered led device: b43-phy0::tx
[ 9685.741796] Registered led device: b43-phy0::rx
[ 9685.741826] Registered led device: b43-phy0::radio
[12495.756513] b43-pci-bridge 0000:0b:00.0: PCI INT A disabled
[12496.476029] b43-pci-bridge 0000:0b:00.0: restoring config space at
offset 0xf (was 0x100, writing 0x107)
[12496.476112] b43-pci-bridge 0000:0b:00.0: restoring config space at
offset 0x4 (was 0x0, writing 0xf9efc000)
[12496.476128] b43-pci-bridge 0000:0b:00.0: restoring config space at
offset 0x3 (was 0x0, writing 0x10)
[12496.476147] b43-pci-bridge 0000:0b:00.0: restoring config space at
offset 0x1 (was 0x100000, writing 0x100107)
[12497.330409] b43-pci-bridge 0000:0b:00.0: PCI INT A -> GSI 17 (level,
low) -> IRQ 17
[12498.820317] b43-phy0: Loading firmware version 410.2160 (2007-05-26
15:32:10)
[12498.904610] Registered led device: b43-phy0::tx
[12498.904641] Registered led device: b43-phy0::rx
[12498.904671] Registered led device: b43-phy0::radio
lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11bg ESSID:"HerkulonVt"
          Mode:Managed Frequency:2.437 GHz Access Point:
00:14:BF:DF:17:93
          Bit Rate=48 Mb/s Tx-Power=20 dBm
          Retry long limit:7 RTS thr:off Fragment thr:off
          Power Management:off
          Link Quality=69/70 Signal level=-41 dBm Noise level=-71 dBm
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:0 Missed beacon:0

 * Reconfiguring network
interfaces... Ignoring unknown
interface wlan0=wlan0.
Ignoring unknown interface eth0=eth0.

[ OK ]
jim@jim-laptop:~$

Mark Rijckenberg wrote:
> Your question #89742 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/89742
>
> Mark Rijckenberg requested for more information:
> Hi,
>
> Please first follow Juan Carlos Inostroza's advice.
>
> Furthermore, please also follow this procedure below to give us more
> info about the wireless issue.
>
> Please first connect your network card to the wireless router using an
> ethernet cable (also known as a LAN cable).
>
> In order to gather essential troubleshooting information about your
> wireless card, please follow this procedure:
>
> Step 1: Open Terminal from "Applications->Accessories->Terminal"
>
> Step 2: Please copy-paste the following command from the
> https://answers.launchpad.net/ubuntu website in Firefox into the Linux
> Terminal. Do NOT copy-paste from the Email message into the Terminal, as
> that will only copy PART of the command. The command STARTS with the
> word sudo and ENDS with the word restart. So please copy-paste the
> ENTIRE command below from Firefox into a Terminal, press <enter>, then
> enter password when sudo asks for password, then press enter again.
>
> sudo lshw -C network; sudo iwlist scanning; cat /etc/network/interfaces;
> cat /etc/lsb-release; lspci -nn; lsusb; sudo lshw -C usb; uname -a;
> dmesg | grep ound; dmesg | grep b43; dmesg | grep iwl; iwconfig; sudo
> /etc/init.d/networking restart
>
> Step 3: Please post results (copy/paste terminal output) on this thread
>
> Regards,
>
> Mark
>
>

--
************************************************************
James Hyde
Associate Professor Emeritus
Tufts University School of Medicine
Department of Public Health and Community Medicine
136 Harrison Ave.
Boston, Ma 02111
<email address hidden>
************************************************************

Revision history for this message
Mark Rijckenberg (markrijckenberg) said : 		#8

Please read "Problem 2" at the following location:

http://jetpackweb.com/blog/2009/10/29/ubuntu-9-10-karmic-koala-and-broadcom-bcm4312/

The workaround there might help.

An alternative might be to set up OpenDNS in Ubuntu 9.10:

http://ubuntu-tutorials.com/2008/06/17/enhance-your-network-connection-with-opendns/

Revision history for this message
Jim Hyde (james-hyde) said : 		#9

Mark--

Sadly, I now find myself in worse shape than before. The Haddon fix did
nothing. The second solution proposed (Ayuthia) seems to have completely
wiped out my wireless. I cannot see the wireless anymore, cannot print
wirelessly either. The LAN connection does work--I can print, see my
Mozilla e-mail, but same problem with Firefox--if I enter the IP address
I can see sites but not otherwise.

The result of all of this seems to be that the wireless has been shut
down while the LAN connection is the default.

How can I get back to at least where I was before?

Jim

Mark Rijckenberg wrote:
> Your question #89742 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/89742
>
> Status: Needs information => Answered
>
> Mark Rijckenberg proposed the following answer:
> Please first try the solution from Tom Haddon from this location:
>
> https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/385293
>
> If that does not help, please try the solution from Ayuthia from this
> location:
>
> http://ubuntuforums.org/showthread.php?p=8297306
>
>

--
************************************************************
James Hyde
Associate Professor Emeritus
Tufts University School of Medicine
Department of Public Health and Community Medicine
136 Harrison Ave.
Boston, Ma 02111
<email address hidden>
************************************************************

Revision history for this message
Mark Rijckenberg (markrijckenberg) said : 		#10

n order to gather essential troubleshooting information about your wireless card, please follow this procedure:

Step 1: Open Terminal from "Applications->Accessories->Terminal"

Step 2: Please copy-paste the following command from the https://answers.launchpad.net/ubuntu website in Firefox into the Linux Terminal. Do NOT copy-paste from the Email message into the Terminal, as that will only copy PART of the command. The command STARTS with the word sudo and ENDS with the word restart. So please copy-paste the ENTIRE command below from Firefox into a Terminal, press <enter>, then enter password when sudo asks for password, then press enter again.

sudo lshw -C network; sudo iwlist scanning; cat /etc/network/interfaces; cat /etc/lsb-release; lspci -nn; lsusb; sudo lshw -C usb; uname -a; dmesg | grep ound; dmesg | grep b43; dmesg | grep iwl; iwconfig; sudo /etc/init.d/networking restart

Step 3: Please post results (copy/paste terminal output) on this thread

Revision history for this message
Mark Rijckenberg (markrijckenberg) said : 		#11

I understand why your wireless b43 driver has been deactivated.

You did the steps from Ayuthia, but the steps before were not done. The b43 driver was blacklisted without installing the replacement wl driver using this command:

sudo aptitude install bcmwl-kernel-source

So either you install bcmwl-kernel-source (to use the wl wireless driver) or you undo the changes by REMOVING the following 2 lines from /etc/modprobe.d/blacklist.conf:

blacklist b43
blacklist ssb

Once your wireless is working again, I suggest the following concerning your DNS issue:

"Please read "Problem 2" at the following location:

http://jetpackweb.com/blog/2009/10/29/ubuntu-9-10-karmic-koala-and-broadcom-bcm4312/

The workaround there might help.

An alternative might be to set up OpenDNS in Ubuntu 9.10:

http://ubuntu-tutorials.com/2008/06/17/enhance-your-network-connection-with-opendns/

"

Revision history for this message
Mark Rijckenberg (markrijckenberg) said : 		#12

After removing the 2 lines in the /etc/modprobe.d/blacklist.conf file, please run the following command and reboot:

sudo update-initramfs -u

Revision history for this message
Jim Hyde (james-hyde) said : 		#13

Mark-

Thanks for your note--I'll have to try this later today.

Mark Rijckenberg wrote:
> Your question #89742 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/89742
>
> Status: Needs information => Answered
>
> Mark Rijckenberg proposed the following answer:
> I understand why your wireless b43 driver has been deactivated.
>
> You did the steps from Ayuthia, but the steps before were not done. The
> b43 driver was blacklisted without installing the replacement wl driver
> using this command:
>
> sudo aptitude install bcmwl-kernel-source
>
> So either you install bcmwl-kernel-source (to use the wl wireless
> driver) or you undo the changes by REMOVING the following 2 lines from
> /etc/modprobe.d/blacklist.conf:
>
> blacklist b43
> blacklist ssb
>
> Once your wireless is working again, I suggest the following concerning
> your DNS issue:
>
> "Please read "Problem 2" at the following location:
>
> http://jetpackweb.com/blog/2009/10/29/ubuntu-9-10-karmic-koala-and-
> broadcom-bcm4312/
>
> The workaround there might help.
>
> An alternative might be to set up OpenDNS in Ubuntu 9.10:
>
> http://ubuntu-tutorials.com/2008/06/17/enhance-your-network-connection-
> with-opendns/
>
> "
>
>

--
************************************************************
James Hyde
Associate Professor Emeritus
Tufts University School of Medicine
Department of Public Health and Community Medicine
136 Harrison Ave.
Boston, Ma 02111
<email address hidden>
************************************************************

Revision history for this message
Juan Carlos Inostroza (jci) said : 		#14

Hi,

this was a simple "no dns configured"

3. When I ping 74.125.45.105---Voila! I get response times back
Also I went ahead and entered the IP address in Firefox again Voila! The
page came up. There is clearly a problem with the address translation--no?
4. I have pasted below the output from the other commands as instructed.

root@jim-laptop:/home/jim# cat /etc/resolv.conf
# Generated by NetworkManager
 (read, empty file, no nameservers)

root@jim-laptop:/home/jim# nslookup - 192.168.1.1
 > www.google.com
Server: 192.168.1.1
Address: 192.168.1.1#53

Non-authoritative answer:
www.google.com canonical name = www.l.google.com.
Name: www.l.google.com
Address: 66.249.81.104

Meaning : it worked. Why suggesting the change on the wireless cards?

Jim:

please revert the changes made in the wireless driver. It was just the name resolving problem:

On a terminal, check for /etc/resolv.conf

$ cat /etc/resolv.conf

it should contain AT LEAST one line with the following:

nameserver <IP ADDRESS>

if there's not, then add it manually

$ sudo su
# echo "nameserver <192.168.1.1>" >> /etc/resolv.conf

don't reboot. This is only a workaround. If it works, please let us know. It may be a problem in your router configuration.

Revision history for this message
Juan Carlos Inostroza (jci) said : 		#15

Correction:

if there's not, then add it manually

$ sudo su
# echo "nameserver 192.168.1.1" >> /etc/resolv.conf

don't reboot. This is only a workaround. If it works, please let us know. It may be a problem in your router configuration.

Revision history for this message
Jim Hyde (james-hyde) said : 		#16

Mark:

I tried to follow your two suggested fixes--neither worked. I can access
my network with the LAN cable but the wireless appears completely shut
down whereas before it was at least allowing me to connect to the
network and print.

There is obviously something I have done to mess things up. Advice?

Jim

************************************************************
James Hyde
Associate Professor Emeritus
Tufts University School of Medicine
Department of Public Health and Community Medicine
136 Harrison Ave.
Boston, Ma 02111
<email address hidden>
************************************************************

Mark Rijckenberg wrote:
> Your question #89742 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/89742
>
> Status: Needs information => Answered
>
> Mark Rijckenberg proposed the following answer:
> I understand why your wireless b43 driver has been deactivated.
>
> You did the steps from Ayuthia, but the steps before were not done. The
> b43 driver was blacklisted without installing the replacement wl driver
> using this command:
>
> sudo aptitude install bcmwl-kernel-source
>
> So either you install bcmwl-kernel-source (to use the wl wireless
> driver) or you undo the changes by REMOVING the following 2 lines from
> /etc/modprobe.d/blacklist.conf:
>
> blacklist b43
> blacklist ssb
>
> Once your wireless is working again, I suggest the following concerning
> your DNS issue:
>
> "Please read "Problem 2" at the following location:
>
> http://jetpackweb.com/blog/2009/10/29/ubuntu-9-10-karmic-koala-and-
> broadcom-bcm4312/
>
> The workaround there might help.
>
> An alternative might be to set up OpenDNS in Ubuntu 9.10:
>
> http://ubuntu-tutorials.com/2008/06/17/enhance-your-network-connection-
> with-opendns/
>
> "
>
>

Revision history for this message
Mark Rijckenberg (markrijckenberg) said : 		#17

Please send us full output of this command:

cat /etc/modprobe.d/blacklist.conf

Revision history for this message
Jim Hyde (james-hyde) said : 		#18

Juan Carlos--

I seem to have lost my wireless completely now. I was following the
steps outlined by Mark in his response. The result is that I now seem to
have LAN access through the ethernet cable but the wireless seems to be
completely shutdown. I can access my e-mail, Firefox etc. but only with
the cable connected.

I'm sure it is my fault. Perhaps I should have only followed one help
path instead of two? Suggestions?

Jim

************************************************************
James Hyde
Associate Professor Emeritus
Tufts University School of Medicine
Department of Public Health and Community Medicine
136 Harrison Ave.
Boston, Ma 02111
<email address hidden>
************************************************************

Juan Carlos Inostroza wrote:
> Your question #89742 on Ubuntu changed:
> https://answers.edge.launchpad.net/ubuntu/+question/89742
>
> Status: Open => Answered
>
> Juan Carlos Inostroza proposed the following answer:
> Hi,
>
> this was a simple "no dns configured"
>
> 3. When I ping 74.125.45.105---Voila! I get response times back
> Also I went ahead and entered the IP address in Firefox again Voila! The
> page came up. There is clearly a problem with the address translation--no?
> 4. I have pasted below the output from the other commands as instructed.
>
> root@jim-laptop:/home/jim# cat /etc/resolv.conf
> # Generated by NetworkManager
> (read, empty file, no nameservers)
>
> root@jim-laptop:/home/jim# nslookup - 192.168.1.1
> > www.google.com
> Server: 192.168.1.1
> Address: 192.168.1.1#53
>
> Non-authoritative answer:
> www.google.com canonical name = www.l.google.com.
> Name: www.l.google.com
> Address: 66.249.81.104
>
> Meaning : it worked. Why suggesting the change on the wireless cards?
>
> Jim:
>
> please revert the changes made in the wireless driver. It was just the
> name resolving problem:
>
> On a terminal, check for /etc/resolv.conf
>
> $ cat /etc/resolv.conf
>
> it should contain AT LEAST one line with the following:
>
> nameserver <IP ADDRESS>
>
> if there's not, then add it manually
>
> $ sudo su
> # echo "nameserver <192.168.1.1>" >> /etc/resolv.conf
>
> don't reboot. This is only a workaround. If it works, please let us
> know. It may be a problem in your router configuration.
>
>

Revision history for this message
Jim Hyde (james-hyde) said : 		#19

Mark--as requested:

jim@jim-laptop:~$ cat /etc/modprobe.d/blacklist.conf
# This file lists those modules which we don't want to be loaded by
# alias expansion, usually so some other driver will be loaded for the
# device instead.

# evbug is a debug tool that should be loaded explicitly
blacklist evbug

# these drivers are very simple, the HID drivers are usually preferred
blacklist usbmouse
blacklist usbkbd

# replaced by e100
blacklist eepro100

# replaced by tulip
blacklist de4x5

# causes no end of confusion by creating unexpected network interfaces
blacklist eth1394

# snd_intel8x0m can interfere with snd_intel8x0, doesn't seem to support
much
# hardware on its own (Ubuntu bug #2011, #6810)
blacklist snd_intel8x0m

# Conflicts with dvb driver (which is better for handling this device)
blacklist snd_aw2

# causes failure to suspend on HP compaq nc6000 (Ubuntu: #10306)
blacklist i2c_i801

# replaced by p54pci
blacklist prism54

# replaced by b43 and ssb.
blacklist bcm43xx

# most apps now use garmin usb driver directly (Ubuntu: #114565)
blacklist garmin_gps

# replaced by asus-laptop (Ubuntu: #184721)
blacklist asus_acpi

# low-quality, just noise when being used for sound playback, causes
# hangs at desktop session start (Ubuntu: #246969)
blacklist snd_pcsp

# ugly and loud noise, getting on everyone's nerves; this should be done
by a
# nice pulseaudio bing (Ubuntu: #77010)
blacklist pcspkr

# EDAC driver for amd76x clashes with the agp driver preventing the aperture
# from being initialised (Ubuntu: #297750). Blacklist so that the driver
# continues to build and is installable for the few cases where its
# really needed.
blacklist amd76x_edac
blacklist b43
jim@jim-laptop:~$

************************************************************
James Hyde
Associate Professor Emeritus
Tufts University School of Medicine
Department of Public Health and Community Medicine
136 Harrison Ave.
Boston, Ma 02111
<email address hidden>
************************************************************

Mark Rijckenberg wrote:
> Your question #89742 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/89742
>
> Status: Open => Needs information
>
> Mark Rijckenberg requested for more information:
> Please send us full output of this command:
>
> cat /etc/modprobe.d/blacklist.conf
>
>

Revision history for this message
Mark Rijckenberg (markrijckenberg) said : 		#20

Run the command

gksudo gedit /etc/modprobe.d/blacklist.conf

Then, inside the gedit editor, scroll down to the last line and REMOVE this line:

blacklist b43

Then save the change and reboot.

Revision history for this message
Jim Hyde (james-hyde) said : 		#21

Mark: Eureka!! That was the fix. Both the wireless and the LAN
connection appear to work fine. The problem with the DNS lookup also
seems to have been solved. Thanks to all you guys for your help.

Jim

************************************************************
James Hyde
Associate Professor Emeritus
Tufts University School of Medicine
Department of Public Health and Community Medicine
136 Harrison Ave.
Boston, Ma 02111
<email address hidden>
************************************************************

Mark Rijckenberg wrote:
> Your question #89742 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/89742
>
> Status: Open => Answered
>
> Mark Rijckenberg proposed the following answer:
> Run the command
>
> gksudo gedit /etc/modprobe.d/blacklist.conf
>
>
> Then, inside the gedit editor, scroll down to the last line and REMOVE this line:
>
> blacklist b43
>
> Then save the change and reboot.
>
>

Revision history for this message
Jim Hyde (james-hyde) said : 		#22

Juan Carlos:

It seems with the last changed suggested by Mark that the problem is
fixed. I have both wireless and LAN access and the DNS lookup problem is
resolved. Thanks for all of your help. This is what makes me a believer
in Ubuntu.

Jim

************************************************************
James Hyde
Associate Professor Emeritus
Tufts University School of Medicine
Department of Public Health and Community Medicine
136 Harrison Ave.
Boston, Ma 02111
<email address hidden>
************************************************************

Juan Carlos Inostroza wrote:
> Your question #89742 on Ubuntu changed:
> https://answers.edge.launchpad.net/ubuntu/+question/89742
>
> Juan Carlos Inostroza posted a new comment:
> Correction:
>
> if there's not, then add it manually
>
> $ sudo su
> # echo "nameserver 192.168.1.1" >> /etc/resolv.conf
>
> don't reboot. This is only a workaround. If it works, please let us
> know. It may be a problem in your router configuration.
>
>

Revision history for this message
Best Mark Rijckenberg (markrijckenberg) said : 		#23

Great to read it is solved now. :-) Sorry for the confusion I caused. Well done.

Revision history for this message
Jim Hyde (james-hyde) said : 		#24

Mark--I'm sure it was something I did wrong. I am very much a novice
with this stuff. I appreciate yours and Juan Carlos patience not to
mention knowledge.

************************************************************
James Hyde
Associate Professor Emeritus
Tufts University School of Medicine
Department of Public Health and Community Medicine
136 Harrison Ave.
Boston, Ma 02111
<email address hidden>
************************************************************

Mark Rijckenberg wrote:
> Your question #89742 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/89742
>
> Status: Open => Answered
>
> Mark Rijckenberg proposed the following answer:
> Great to read it is solved now. :-) Sorry for the confusion I caused.
> Well done.
>
>

Revision history for this message
Mark Rijckenberg (markrijckenberg) said : 		#25

Hi Jim,

One more thing:

If the issue in this thread is solved, may I ask you to set the thread status to "solved"? It is currently in "open" status, which will invite others to investigate why this thread is still "open"

Thanks and good luck with using open source,

Mark

Revision history for this message
Jim Hyde (james-hyde) said : 		#26

Thanks Mark Rijckenberg, that solved my question.

Revision history for this message
Jim Hyde (james-hyde) said : 		#27

will do

************************************************************
James Hyde
Associate Professor Emeritus
Tufts University School of Medicine
Department of Public Health and Community Medicine
136 Harrison Ave.
Boston, Ma 02111
<email address hidden>
************************************************************

Mark Rijckenberg wrote:
> Your question #89742 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/89742
>
> Status: Open => Answered
>
> Mark Rijckenberg proposed the following answer:
> Hi Jim,
>
> One more thing:
>
> If the issue in this thread is solved, may I ask you to set the thread
> status to "solved"? It is currently in "open" status, which will invite
> others to investigate why this thread is still "open"
>
> Thanks and good luck with using open source,
>
> Mark
>
>