IBM T30 wireless network card no longer working

Bug #104551 reported by John McHugh
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned
linux-source-2.6.20 (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

The internal wireless card in my ibm t30 laptop is no longer working in feisty. I then loaded edgy onto the laptop to find that the wireless card works perfectly on it, until you download the updates. Then the wireless is broken again.

Revision history for this message
Brett Clippingdale (brett-clippingdale) wrote :

I had the same problem on my T30 (that is, with the Prism-based IBM internal wireless card, not the Cisco one).

The problem is that the hostap and orinoco kernel modules are competing for control of the card. This is mentioned as a likely problem on NetworkManager site:
(http://live.gnome.org/NetworkManagerHardware)

hostap: "Supports unencrypted, WEP, WPA, and WPA2 networks. Be aware that if you have both this driver and the 'orinoco' driver installed, they may fight for control of the wireless card and render it inoperable to NetworkManager. You should either disable one of these drivers, or ensure that only one driver is able to control the card."

I'd love to see this working by default; in the meantime, however, you can fix it easily:

1) Confirm you have the same kind of wireless card:

brett@boca:~$ lspci | grep Network
02:02.0 Network controller: Intersil Corporation Prism 2.5 Wavelan chipset (rev 01)

2) If so, add the following to /etc/modprobe/blacklist:

(as root, ie. $sudo vi /etc/modprobe.d/blacklist, or $sudo gedit /etc/modprobe.d/blacklist, and add the following lines)

blacklist orinoco
blacklist orinoco_pci
blacklist hermes
blacklist p80211
blacklist prism2_pci

Note that you have the option of blacklisting either the hostap modules or the orinoco ones, but the hostap are considerable more capable under NetworkManager, so keep the hostap ones (hostap, hostap_pci, plus ieee80211_crypt for any WPA card -- not specific to this one) which will all load by default. I was surprised I had to blacklist p80211 and prism2_pci, but it didn't fully work otherwise ... perhaps someone else can reason why.

3) reboot

After this, all should work nicely.

Revision history for this message
John McHugh (mrmcq2u) wrote : Re: [Bug 104551] Re: IBM T30 wireless network card no longer working

I installed feisty from a different DVD image and the wireless seems to work
properly now, on roaming that is, I'm afraid to try and connect to my
network through another method like manually in case it breaks th wireless
and i need to reinstall again. Feel like a real idiot now, but the issue
seems to be fixed, its still broken in edgy though after you update that is.
Thanks for the quick replies and offered help on the subject. if i do find
the courage to try and connect to my access point manually and it breaks il
be sure to give you a shout though. Thanks again.

On 4/9/07, Brian Murray <email address hidden> wrote:
>
> ** Changed in: Ubuntu
> Assignee: (unassigned) => Brian Murray
> Status: Unconfirmed => Needs Info
>
> --
> IBM T30 wireless network card no longer working
> https://bugs.launchpad.net/bugs/104551
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Brett Clippingdale (brett-clippingdale) wrote :
Revision history for this message
Brett Clippingdale (brett-clippingdale) wrote :

Those with Prism 2 cards should also investigate updating the firmware, but exercise caution:

http://linux.junsun.net/intersil-prism/

Revision history for this message
John McHugh (mrmcq2u) wrote :

after reinstalling ubuntu feisty the original problem has started to acure
again. in network my wireless card comes up as wifi(0) or something like
that but its listed as a wired network, I applied all the updates to feisty
and am now baffled at how it worked out of the box once but not again. When
it was working out of the box in the network manager it would be detected as
eth1 and as a wireless not wired connection. Brett I did what you said and
it just made things more confusing, now in network manager i have two
wireless connections wlan1 and wifi 0 , both are set to roaming. I cant
modify the settings to take them off roaming or to disable them. the wifi
network applet on the gnome pannel detects my wireless network but seems to
crash when trying to connect.

On 4/10/07, Brett Clippingdale <email address hidden> wrote:
>
> Those with Prism 2 cards should also investigate updating the firmware,
> but exercise caution:
>
> http://linux.junsun.net/intersil-prism/
>
> --
> IBM T30 wireless network card no longer working
> https://bugs.launchpad.net/bugs/104551
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Brett Clippingdale (brett-clippingdale) wrote :

If if wasn't broke, why fix it? You said "it worked out of the box
once," did you do anything to make it not work, or was it simply doing
updates?

Yes, you will see both wlan1 and wifi0, I see that also from CLI but
this hardly creates a problem. Though confusing, just ignore wifi0
and use wlan1.

This is no doubt frustrating for you, but to make progress in
diagnosing the root cause, try changing just one thing at a time if
possible. Constantly reinstalling just puts us back at square one, to
some degree.

So, to understand your current situation:

- Which of the install DVDs did you use this time?
- How are you determining that the cards are set to "roaming", why is
this a problem, and why do you want to disable them?

Please post the results of the following:
$uname -a
$lspci -v
$lsmod
$ifconfig -a
$iwconfig
$iwlist scanning

Brett

On 4/11/07, Tretle <email address hidden> wrote:
> after reinstalling ubuntu feisty the original problem has started to acure
> again. in network my wireless card comes up as wifi(0) or something like
> that but its listed as a wired network, I applied all the updates to feisty
> and am now baffled at how it worked out of the box once but not again. When
> it was working out of the box in the network manager it would be detected as
> eth1 and as a wireless not wired connection. Brett I did what you said and
> it just made things more confusing, now in network manager i have two
> wireless connections wlan1 and wifi 0 , both are set to roaming. I cant
> modify the settings to take them off roaming or to disable them. the wifi
> network applet on the gnome pannel detects my wireless network but seems to
> crash when trying to connect.
>
> On 4/10/07, Brett Clippingdale <email address hidden> wrote:
> >
> > Those with Prism 2 cards should also investigate updating the firmware,
> > but exercise caution:
> >
> > http://linux.junsun.net/intersil-prism/
> >
> > --
> > IBM T30 wireless network card no longer working
> > https://bugs.launchpad.net/bugs/104551
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> >
>
> --
> IBM T30 wireless network card no longer working
> https://bugs.launchpad.net/bugs/104551
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
John McHugh (mrmcq2u) wrote :
Download full text (17.2 KiB)

well i did have it all working, then i tried to get beryl working but it
killed xserver, i fixed it to a degree but i was unable to get the
resolutions i was getting before :( I didnt back up the xorg.conf silly me.
To answer your question on which cd i am using, im using the same one that
worked out of box the last time, i labelled it ubuntu feisty beta working so
im sure of that. I have determined that both of the wifi settings are using
roaming through the network monitor bundled with feisty, I am unable to
change the settings of wither of them which means that they are both
enabled and this could be the problem. It detects my router downstairs but
wont connect.

the results you asked for are as follows,

tretle@tretle-laptop:~$ uname -a
Linux tretle-laptop 2.6.20-14-generic #2 SMP Mon Apr 2 20:37:49 UTC 2007
i686 GNU/Linux
tretle@tretle-laptop:~$ lspci -v
00:00.0 Host bridge: Intel Corporation 82845 845 (Brookdale) Chipset Host
Bridge (rev 04)
        Flags: bus master, fast devsel, latency 0
        Memory at e0000000 (32-bit, prefetchable) [size=64M]
        Capabilities: <access denied>

00:01.0 PCI bridge: Intel Corporation 82845 845 (Brookdale) Chipset AGP
Bridge (rev 04) (prog-if 00 [Normal decode])
        Flags: bus master, 66MHz, fast devsel, latency 96
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
        I/O behind bridge: 00003000-00003fff
        Memory behind bridge: d0100000-d01fffff
        Prefetchable memory behind bridge: e8000000-efffffff

00:1d.0 USB Controller: Intel Corporation 82801CA/CAM USB (Hub #1) (rev 02)
(prog-if 00 [UHCI])
        Subsystem: IBM ThinkPad A/T/X Series
        Flags: bus master, medium devsel, latency 0, IRQ 11
        I/O ports at 1800 [size=32]

00:1d.1 USB Controller: Intel Corporation 82801CA/CAM USB (Hub #2) (rev 02)
(prog-if 00 [UHCI])
        Subsystem: IBM ThinkPad A/T/X Series
        Flags: bus master, medium devsel, latency 0, IRQ 11
        I/O ports at 1820 [size=32]

00:1d.2 USB Controller: Intel Corporation 82801CA/CAM USB (Hub #3) (rev 02)
(prog-if 00 [UHCI])
        Subsystem: IBM ThinkPad A/T/X Series
        Flags: bus master, medium devsel, latency 0, IRQ 11
        I/O ports at 1840 [size=32]

00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 42)
(prog-if 00 [Normal decode])
        Flags: bus master, fast devsel, latency 0
        Bus: primary=00, secondary=02, subordinate=08, sec-latency=64
        I/O behind bridge: 00004000-00008fff
        Memory behind bridge: d0200000-dfffffff
        Prefetchable memory behind bridge: f0000000-f80fffff

00:1f.0 ISA bridge: Intel Corporation 82801CAM ISA Bridge (LPC) (rev 02)
        Flags: bus master, medium devsel, latency 0

00:1f.1 IDE interface: Intel Corporation 82801CAM IDE U100 (rev 02) (prog-if
8a [Master SecP PriP])
        Subsystem: IBM ThinkPad A/T/X Series
        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 20000000 (32-bit, non-prefetchable) [size=1K]

00:1f.3 SMBus: Intel Corp...

Revision history for this message
John McHugh (mrmcq2u) wrote :
Download full text (18.6 KiB)

I think i might have some useful info for you, when i was running the
install with the working wireless i used airsnort, these are the settings i
used for a successful scan : Network device : eth1 , Driver type :Host
AP/Orinoco . So is it the orinoco driver which sets the network device to
eth1. if so how do i set the orinoco driver to be the default wireless
network driver on my machine. When it was working it displeyed my wired
network connection as eth0 and my wireless as eth1. I hope that info can
prove useful to you.

On 4/11/07, John McHugh <email address hidden> wrote:
>
> well i did have it all working, then i tried to get beryl working but it
> killed xserver, i fixed it to a degree but i was unable to get the
> resolutions i was getting before :( I didnt back up the xorg.conf silly
> me. To answer your question on which cd i am using, im using the same one
> that worked out of box the last time, i labelled it ubuntu feisty beta
> working so im sure of that. I have determined that both of the wifi settings
> are using roaming through the network monitor bundled with feisty, I am
> unable to change the settings of wither of them which means that they are
> both enabled and this could be the problem. It detects my router downstairs
> but wont connect.
>
> the results you asked for are as follows,
>
>
> tretle@tretle-laptop:~$ uname -a
> Linux tretle-laptop 2.6.20-14-generic #2 SMP Mon Apr 2 20:37:49 UTC 2007
> i686 GNU/Linux
> tretle@tretle-laptop:~$ lspci -v
> 00:00.0 Host bridge: Intel Corporation 82845 845 (Brookdale) Chipset Host
> Bridge (rev 04)
> Flags: bus master, fast devsel, latency 0
> Memory at e0000000 (32-bit, prefetchable) [size=64M]
> Capabilities: <access denied>
>
> 00:01.0 PCI bridge: Intel Corporation 82845 845 (Brookdale) Chipset AGP
> Bridge (rev 04) (prog-if 00 [Normal decode])
> Flags: bus master, 66MHz, fast devsel, latency 96
> Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
> I/O behind bridge: 00003000-00003fff
> Memory behind bridge: d0100000-d01fffff
> Prefetchable memory behind bridge: e8000000-efffffff
>
> 00:1d.0 USB Controller: Intel Corporation 82801CA/CAM USB (Hub #1) (rev
> 02) (prog-if 00 [UHCI])
> Subsystem: IBM ThinkPad A/T/X Series
> Flags: bus master, medium devsel, latency 0, IRQ 11
> I/O ports at 1800 [size=32]
>
> 00:1d.1 USB Controller: Intel Corporation 82801CA/CAM USB (Hub #2) (rev
> 02) (prog-if 00 [UHCI])
> Subsystem: IBM ThinkPad A/T/X Series
> Flags: bus master, medium devsel, latency 0, IRQ 11
> I/O ports at 1820 [size=32]
>
> 00:1d.2 USB Controller: Intel Corporation 82801CA/CAM USB (Hub #3) (rev
> 02) (prog-if 00 [UHCI])
> Subsystem: IBM ThinkPad A/T/X Series
> Flags: bus master, medium devsel, latency 0, IRQ 11
> I/O ports at 1840 [size=32]
>
> 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 42)
> (prog-if 00 [Normal decode])
> Flags: bus master, fast devsel, latency 0
> Bus: primary=00, secondary=02, subordinate=08, sec-latency=64
> I/O behind bridge: 00004000-00008fff
> Memory behind ...

Revision history for this message
Brett Clippingdale (brett-clippingdale) wrote :
Download full text (20.5 KiB)

One thing at a time, but I can give you the info you need for Beryl
in a separate thread. Getting Beryl/Compiz working right on the T30
is a huge chore, so let's get to that later.

Based on your output from iwconfig, it looks as though wlan0 is in
fact connected to the "belkin54g" network.

It would be interesting to isolate that from the wired connection.
What happens if you disconnect the ethernet cable used by eth0 and
then try the network connection? ie. ping yahoo.com to see if you
still have internet?

BTW, I'm tracking several bugs that may be related to your wireless
issues, including the following:

https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/73759/

https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/42504/

https://bugs.launchpad.net/ubuntu/+source/ndiswrapper/+bug/85468/

On 4/11/07, Tretle <email address hidden> wrote:
> I think i might have some useful info for you, when i was running the
> install with the working wireless i used airsnort, these are the settings i
> used for a successful scan : Network device : eth1 , Driver type :Host
> AP/Orinoco . So is it the orinoco driver which sets the network device to
> eth1. if so how do i set the orinoco driver to be the default wireless
> network driver on my machine. When it was working it displeyed my wired
> network connection as eth0 and my wireless as eth1. I hope that info can
> prove useful to you.
>
> On 4/11/07, John McHugh <email address hidden> wrote:
> >
> > well i did have it all working, then i tried to get beryl working but it
> > killed xserver, i fixed it to a degree but i was unable to get the
> > resolutions i was getting before :( I didnt back up the xorg.conf silly
> > me. To answer your question on which cd i am using, im using the same one
> > that worked out of box the last time, i labelled it ubuntu feisty beta
> > working so im sure of that. I have determined that both of the wifi settings
> > are using roaming through the network monitor bundled with feisty, I am
> > unable to change the settings of wither of them which means that they are
> > both enabled and this could be the problem. It detects my router downstairs
> > but wont connect.
> >
> > the results you asked for are as follows,
> >
> >
> > tretle@tretle-laptop:~$ uname -a
> > Linux tretle-laptop 2.6.20-14-generic #2 SMP Mon Apr 2 20:37:49 UTC 2007
> > i686 GNU/Linux
> > tretle@tretle-laptop:~$ lspci -v
> > 00:00.0 Host bridge: Intel Corporation 82845 845 (Brookdale) Chipset Host
> > Bridge (rev 04)
> > Flags: bus master, fast devsel, latency 0
> > Memory at e0000000 (32-bit, prefetchable) [size=64M]
> > Capabilities: <access denied>
> >
> > 00:01.0 PCI bridge: Intel Corporation 82845 845 (Brookdale) Chipset AGP
> > Bridge (rev 04) (prog-if 00 [Normal decode])
> > Flags: bus master, 66MHz, fast devsel, latency 96
> > Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
> > I/O behind bridge: 00003000-00003fff
> > Memory behind bridge: d0100000-d01fffff
> > Prefetchable memory behind bridge: e8000000-efffffff
> >
> > 00:1d.0 USB Controller: Intel Corporation 82801CA/CAM USB (Hub #1) (rev
> > 02) (pro...

Revision history for this message
John McHugh (mrmcq2u) wrote :
Download full text (22.0 KiB)

the orinoco drivers are running perfectly now, i just blacklisted hostap
instead of orinoco. i can go back to to hostap and chec

On 4/12/07, Brett Clippingdale <email address hidden> wrote:
>
> One thing at a time, but I can give you the info you need for Beryl
> in a separate thread. Getting Beryl/Compiz working right on the T30
> is a huge chore, so let's get to that later.
>
> Based on your output from iwconfig, it looks as though wlan0 is in
> fact connected to the "belkin54g" network.
>
> It would be interesting to isolate that from the wired connection.
> What happens if you disconnect the ethernet cable used by eth0 and
> then try the network connection? ie. ping yahoo.com to see if you
> still have internet?
>
> BTW, I'm tracking several bugs that may be related to your wireless
> issues, including the following:
>
> https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/73759/
>
> https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/42504/
>
> https://bugs.launchpad.net/ubuntu/+source/ndiswrapper/+bug/85468/
>
> On 4/11/07, Tretle < <email address hidden>> wrote:
> > I think i might have some useful info for you, when i was running the
> > install with the working wireless i used airsnort, these are the
> settings i
> > used for a successful scan : Network device : eth1 , Driver type :Host
> > AP/Orinoco . So is it the orinoco driver which sets the network device
> to
> > eth1. if so how do i set the orinoco driver to be the default wireless
> > network driver on my machine. When it was working it displeyed my wired
> > network connection as eth0 and my wireless as eth1. I hope that info can
> > prove useful to you.
> >
> > On 4/11/07, John McHugh <email address hidden> wrote:
> > >
> > > well i did have it all working, then i tried to get beryl working but
> it
> > > killed xserver, i fixed it to a degree but i was unable to get the
> > > resolutions i was getting before :( I didnt back up the xorg.confsilly
> > > me. To answer your question on which cd i am using, im using the same
> one
> > > that worked out of box the last time, i labelled it ubuntu feisty beta
> > > working so im sure of that. I have determined that both of the wifi
> settings
> > > are using roaming through the network monitor bundled with feisty, I
> am
> > > unable to change the settings of wither of them which means that they
> are
> > > both enabled and this could be the problem. It detects my router
> downstairs
> > > but wont connect.
> > >
> > > the results you asked for are as follows,
> > >
> > >
> > > tretle@tretle-laptop:~$ uname -a
> > > Linux tretle-laptop 2.6.20-14-generic #2 SMP Mon Apr 2 20:37:49 UTC
> 2007
> > > i686 GNU/Linux
> > > tretle@tretle-laptop:~$ lspci -v
> > > 00:00.0 Host bridge: Intel Corporation 82845 845 (Brookdale) Chipset
> Host
> > > Bridge (rev 04)
> > > Flags: bus master, fast devsel, latency 0
> > > Memory at e0000000 (32-bit, prefetchable) [size=64M]
> > > Capabilities: <access denied>
> > >
> > > 00: 01.0 PCI bridge: Intel Corporation 82845 845 (Brookdale) Chipset
> AGP
> > > Bridge (rev 04) (prog-if 00 [Normal decode])
> > > Flags: bus master, 66MHz, fast devsel, latenc...

Revision history for this message
Michael R. Head (burner) wrote :

This is likely related to bug 63989

Revision history for this message
John McHugh (mrmcq2u) wrote :

still broken in hardy by the way

On Jul 31, 2007 2:51 AM, Michael R. Head <email address hidden> wrote:

> This is likely related to bug 63989
>
> --
> IBM T30 wireless network card no longer working
> https://bugs.launchpad.net/bugs/104551
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
John McHugh (mrmcq2u) wrote : New invitation from John McHugh

You have been invited to connect as friends with John McHugh <email address hidden>

Please accept or reject this invitation by clicking below:
http://www.bebo.com/in/7095643932a768709231b135

......................................................................
Please do not reply directly to this email.

This email was sent to you at the direct request of John McHugh <email address hidden>. You have not been added to a mailing list.

If you would prefer not to receive invitations from ANY Bebo members please click here - http://www.bebo.com/unsub/7095643932a768709231

Bebo, Inc., 795 Folsom St, 6th Floor, San Francisco, CA 94107, USA.

Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

Revision history for this message
Ike Panhc (ikepanhc) wrote :

This bug report is being closed because we received no response to the previous inquiry for information. Please reopen if this is still an issue in the current Ubuntu release, Jaunty Jackalope 9.04 - http://www.ubuntu.com/getubuntu/download. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

Changed in linux (Ubuntu):
status: Incomplete → Won't Fix
Revision history for this message
John McHugh (mrmcq2u) wrote :

www.adh1.health-tablets.com

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.