Bug 724820 - Wireless module does not work on Toshiba Portege r830
Summary: Wireless module does not work on Toshiba Portege r830
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: comps
Version: 15
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-21 22:01 UTC by Lech Lobocki
Modified: 2014-03-17 03:28 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-25 18:08:10 UTC
Type: ---


Attachments (Terms of Use)
Comment (77.53 KB, text/plain)
2011-07-25 17:52 UTC, Lech Lobocki
no flags Details

Description Lech Lobocki 2011-07-21 22:01:29 UTC
Description of problem:

Wireless module does not work on Toshiba Portege r830
(Centrino Advanced N6230)

On Ubuntu 11.04 it works with no problems


Version-Release number of selected component (if applicable):
 2.6.38.7-30.fc15.x86_64,  modules iwlcore/iwlagn/mac80211/cfg80211

How reproducible:
100%

Steps to Reproduce:
1. ifconfig
2.
3.
  
Actual results:

eth0      Link encap:Ethernet  HWaddr E8:9D:87:A9:18:21  
          inet addr:192.168.1.77  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::ea9d:87ff:fea9:1821/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1427 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1479 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:749238 (731.6 KiB)  TX bytes:239549 (233.9 KiB)
          Interrupt:20 Memory:c4800000-c4820000 

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:152 errors:0 dropped:0 overruns:0 frame:0
          TX packets:152 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:15548 (15.1 KiB)  TX bytes:15548 (15.1 KiB)

virbr0    Link encap:Ethernet  HWaddr 4A:58:E7:01:B8:16  
          inet addr:192.168.122.1  Bcast:192.168.122.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:38 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:5230 (5.1 KiB)


Expected results:

wlan0     ........

Additional info:

lshw:

        *-pci:2
             description: PCI bridge
             product: Cougar Point PCI Express Root Port 3
             vendor: Intel Corporation
             physical id: 1c.2
             bus info: pci@0000:00:1c.2
             version: b4
             width: 32 bits
             clock: 33MHz
             capabilities: pci pciexpress msi pm normal_decode bus_master cap_list
             configuration: driver=pcieport
             resources: irq:18 memory:c2600000-c26fffff
           *-network UNCLAIMED
                description: Network controller
                product: Intel Corporation
                vendor: Intel Corporation
                physical id: 0
                bus info: pci@0000:04:00.0
                version: 34
                width: 64 bits
                clock: 33MHz
                capabilities: pm msi pciexpress cap_list
                configuration: latency=0
                resources: memory:c2600000-c2601fff

On Ubuntu, there is a description of the Centrino Advanced N6230 instead

Comment 1 John W. Linville 2011-07-25 15:12:52 UTC
Please attach the output of running 'dmesg' shortly after a reboot, and also the output of 'lspci -n' -- thanks!

Comment 2 Lech Lobocki 2011-07-25 17:52:52 UTC
Created attachment 915354 [details]
Comment

(This comment was longer than 65,535 characters and has been moved to an attachment by Red Hat Bugzilla).

Comment 3 John W. Linville 2011-07-25 18:08:10 UTC
Email from bug reporter:

"I've found the solution today - it was a missing iwl6000g2b-firmware
package.
After installing it, the wifi started to working.
So, I guess, the installer should be fixed instead, driver is OK."

I have added iwl6000g2b-firmware to the comps file.


Note You need to log in before you can comment on or make changes to this bug.