Bug 46721 - Wireless not active during installation or after boot
Summary: Wireless not active during installation or after boot
Status: NEW
Alias: None
Product: Networking
Classification: Unclassified
Component: Wireless (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: networking_wireless@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-30 16:45 UTC by lars.nooden+kernel
Modified: 2019-02-27 19:12 UTC (History)
2 users (show)

See Also:
Kernel Version: 3.6
Subsystem:
Regression: No
Bisected commit-id:


Attachments
dmesg (39.19 KB, text/plain)
2012-08-30 16:45 UTC, lars.nooden+kernel
Details
dmesg after pci=biosirq (34.67 KB, application/octet-stream)
2012-08-31 07:32 UTC, lars.nooden+kernel
Details

Description lars.nooden+kernel 2012-08-30 16:45:07 UTC
Created attachment 78811 [details]
dmesg

The i386 has a Ralink corp. RT2561/RT61 802.11g PCI wireless card. However, the installation process seems unable to use it to find any wireless networks, not even open networks. Same goes after booting and trying manually.  This is true even with the new kernel:

# uname -a
Linux easynote 3.6.0-030600rc3-generic #201208221735 SMP Wed Aug 22 21:45:31 UTC 2012 i686 i686 i686 GNU/Linux

# rfkill list all
0: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: yes

What information is needed to make a proper bug report?
Comment 1 Alan 2012-08-30 19:59:46 UTC
[   15.649864] rt61pci 0000:00:06.0: enabling device (0000 -> 0002)
[   15.649882] rt61pci 0000:00:06.0: can't find IRQ for PCI INT A; please try using pci=biosirq
[   15.649900] rt61pci 0000:00:06.0: setting latency timer to 64
Comment 2 lars.nooden+kernel 2012-08-31 07:32:38 UTC
Created attachment 78861 [details]
dmesg after pci=biosirq
Comment 3 lars.nooden+kernel 2012-08-31 07:34:19 UTC
I tried setting pci=biosirq in the grub menu and the only difference I see is that the consoles vanish.  I can still log in via ssh though.

# rfkill list all
0: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: yes

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