1814:3290 [HP ProBook 4540s Notebook PC] Ralink RT3290 card not supported

[rojanu]

Here is my system details

# lspci | grep Network
03:00.0 Network controller: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe
# uname -a
Linux etl-aliustek 3.8.0-13-generic #22-Ubuntu SMP Fri Mar 15 17:49:38 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu Raring Ringtail (development branch)
Release: 13.04
Codename: raring

I have installed the firmware by doing

git clone git://git.kernel.org/pub/scm/linux/kernel/git/dwmw2/linux-firmware.git
sudo cp linux-firmware/rt3290.bin /lib/firmware

however, my wireless card is still not picked up

# lshw -class network
  *-network UNCLAIMED
       description: Network controller
       product: RT3290 Wireless 802.11n 1T/1R PCIe
       vendor: Ralink corp.
       physical id: 0
       bus info: pci@0000:03:00.0
       version: 00
       width: 32 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list
       configuration: latency=0
       resources: memory:d0610000-d061ffff

I looked at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1049466 and to my understanding, this card should be supported on 13.04?

Any Ideas? Thanks

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-13-generic 3.8.0-13.22
ProcVersionSignature: Ubuntu 3.8.0-13.22-generic 3.8.3
Uname: Linux 3.8.0-13-generic x86_64
ApportVersion: 2.9.1-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ali 2178 F.... pulseaudio
                      ali 4037 F.... pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Date: Sun Mar 17 22:08:55 2013
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=63b9f0af-b301-4ce7-84dd-11ce3b60c60c
InstallationDate: Installed on 2013-02-25 (20 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: Hewlett-Packard HP ProBook 4540s
MarkForUpload: True
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-13-generic root=UUID=dbdc7f5b-f7e2-48a0-814e-cd8efdc073dc ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-13-generic N/A
 linux-backports-modules-3.8.0-13-generic N/A
 linux-firmware 1.104
RfKill:

SourcePackage: linux
UpgradeStatus: Upgraded to raring on 2013-03-16 (0 days ago)
dmi.bios.date: 01/29/2013
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68IRR Ver. F.40
dmi.board.name: 17F6
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 58.1D
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68IRRVer.F.40:bd01/29/2013:svnHewlett-Packard:pnHPProBook4540s:pvrA1019D1103:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.1D:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP ProBook 4540s
dmi.product.version: A1019D1103
dmi.sys.vendor: Hewlett-Packard

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.9 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-rc3-raring/

[JParnell (justin-d-parnell)]

Can also confirm bug is present upstream.

HP Envy M6-1148CA

jazzyj@beatsbox:~$ lspci | grep Network
02:00.0 Network controller: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe
jazzyj@beatsbox:~$ uname -a
Linux beatsbox 3.9.0-030900rc3-generic #201303171935 SMP Sun Mar 17 23:36:17 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
jazzyj@beatsbox:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu Raring Ringtail (development branch)
Release: 13.04
Codename: raring
jazzyj@beatsbox:~$ sudo lshw -class network
  *-network
       description: Ethernet interface
       product: RTL8111/8168 PCI Express Gigabit Ethernet controller
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 0.2
       bus info: pci@0000:01:00.2
       logical name: eth0
       version: 0a
       serial: 6c:3b:e5:81:91:c5
       size: 100Mbit/s
       capacity: 1Gbit/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full firmware=rtl8411-1_0.0.3 06/18/12 ip=192.168.1.133 latency=0 link=yes multicast=yes port=MII speed=100Mbit/s
       resources: irq:52 ioport:2000(size=256) memory:f0004000-f0004fff memory:f0000000-f0003fff
  *-network DISABLED
       description: Wireless interface
       product: RT3290 Wireless 802.11n 1T/1R PCIe
       vendor: Ralink corp.
       physical id: 0
       bus info: pci@0000:02:00.0
       logical name: wlan0
       version: 00
       serial: a4:17:31:a3:e4:25
       width: 32 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=rt2800pci driverversion=3.9.0-030900rc3-generic firmware=0.37 latency=0 link=no multicast=yes wireless=IEEE 802.11bgn
       resources: irq:17 memory:f0110000-f011ffff

[Joseph Salisbury (jsalisbury)]

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

[rojanu (rojanu)]

Hi,

The wi-fi chip Ralink RT3290 is common in notebooks but is not supported by
linux-kernel

A bug is raised on Ubuntu launchpad
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1156363

Some information about my system is attached

Tested on 3.6, 3.8, 3.9rc3 and 3.9rc4

Keywords: wifi, networking, kernel

[rojanu (rojanu)]

Sorry missed that, attached is the requested info

Thanks

On Thu, Mar 28, 2013 at 12:45 AM, Larry Finger
<email address hidden> wrote:
> On 03/27/2013 06:13 PM, Ali Ustek wrote:
>>
>> Hi,
>>
>> The wi-fi chip Ralink RT3290 is common in notebooks but is not
>> supported by linux-kernel
>>
>> A bug is raised on Ubuntu launchpad
>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1156363
>>
>> Some information about my system is attached
>>
>> Tested on 3.6, 3.8, 3.9rc3 and 3.9rc4
>>
>> Keywords: wifi, networking, kernel
>
>
> Nearly everything that you posted tells us nothing. One critical piece of
> information is given by "lspci -nn".
>
>
>

[Sedat Dilek (dileks)]

On Thu, Mar 28, 2013 at 10:03 AM, Stanislaw Gruszka <email address hidden> wrote:
> On Thu, Mar 28, 2013 at 08:18:37AM +0000, Ali Ustek wrote:
>> >> The wi-fi chip Ralink RT3290 is common in notebooks but is not
>> >> supported by linux-kernel
>
> This device is supported since 3.7 . You most likely compile kernel
> without CONFIG_RT2800PCI_RT3290.
>

Hi Ali,

your kernel-config (self-compiled or the one of your $distro) and
dmesg logs are always helpful, the same to lspci/lsusb outputs.
And... informations to your $distro plus used your
$network-userspace-apps like network-manager (NM), wpa-supplicant etc.
are helpful... if you want your issue be tracked... successfully :-).

Check also docs section for debugging the different wifi-drivers on
<wireless.kernel.org>.

Hope this helps you!

Regards,
- Sedat -

> Stanislaw
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to <email address hidden>
> More majordomo info at http://vger.kernel.org/majordomo-info.html

[rojanu (rojanu)]

I know it is supported after 3.6 but the kernel (3.9.rc4) I have from
Ubuntu upstream hasn't got it, that is the reason I have raised a bug
and trying to get it fixed.

On Thu, Mar 28, 2013 at 9:03 AM, Stanislaw Gruszka <email address hidden> wrote:
> On Thu, Mar 28, 2013 at 08:18:37AM +0000, Ali Ustek wrote:
>> >> The wi-fi chip Ralink RT3290 is common in notebooks but is not
>> >> supported by linux-kernel
>
> This device is supported since 3.7 . You most likely compile kernel
> without CONFIG_RT2800PCI_RT3290.
>
> Stanislaw

[rojanu (rojanu)]

Hi Sedat,

The kernel I am using is from Ubuntu and I am using NM.

All the other logs I have attached on to launchpad bug
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1156363
if that's any help at all.

Thanks

On Thu, Mar 28, 2013 at 9:19 AM, Sedat Dilek <email address hidden> wrote:
> On Thu, Mar 28, 2013 at 10:03 AM, Stanislaw Gruszka <email address hidden> wrote:
>> On Thu, Mar 28, 2013 at 08:18:37AM +0000, Ali Ustek wrote:
>>> >> The wi-fi chip Ralink RT3290 is common in notebooks but is not
>>> >> supported by linux-kernel
>>
>> This device is supported since 3.7 . You most likely compile kernel
>> without CONFIG_RT2800PCI_RT3290.
>>
>
> Hi Ali,
>
> your kernel-config (self-compiled or the one of your $distro) and
> dmesg logs are always helpful, the same to lspci/lsusb outputs.
> And... informations to your $distro plus used your
> $network-userspace-apps like network-manager (NM), wpa-supplicant etc.
> are helpful... if you want your issue be tracked... successfully :-).
>
> Check also docs section for debugging the different wifi-drivers on
> <wireless.kernel.org>.
>
> Hope this helps you!
>
> Regards,
> - Sedat -
>
>> Stanislaw
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
>> the body of a message to <email address hidden>
>> More majordomo info at http://vger.kernel.org/majordomo-info.html

[rojanu (rojanu)]

I have checked the Ubuntu kernel config on my laptop and it has
$ grep -i RT2800PCI /boot/config-3.8.0-18-generic
CONFIG_RT2800PCI=m
CONFIG_RT2800PCI_RT33XX=y
CONFIG_RT2800PCI_RT35XX=y
CONFIG_RT2800PCI_RT53XX=y
CONFIG_RT2800PCI_RT3290=y

and I tried to compile the kernel myself to no avail.

any ideas?

On Thu, Mar 28, 2013 at 12:18 PM, Ali Ustek <email address hidden> wrote:

> Hi Sedat,
>
> The kernel I am using is from Ubuntu and I am using NM.
>
> All the other logs I have attached on to launchpad bug
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1156363
> if that's any help at all.
>
> Thanks
>
> On Thu, Mar 28, 2013 at 9:19 AM, Sedat Dilek <email address hidden>
> wrote:
> > On Thu, Mar 28, 2013 at 10:03 AM, Stanislaw Gruszka <email address hidden>
> wrote:
> >> On Thu, Mar 28, 2013 at 08:18:37AM +0000, Ali Ustek wrote:
> >>> >> The wi-fi chip Ralink RT3290 is common in notebooks but is not
> >>> >> supported by linux-kernel
> >>
> >> This device is supported since 3.7 . You most likely compile kernel
> >> without CONFIG_RT2800PCI_RT3290.
> >>
> >
> > Hi Ali,
> >
> > your kernel-config (self-compiled or the one of your $distro) and
> > dmesg logs are always helpful, the same to lspci/lsusb outputs.
> > And... informations to your $distro plus used your
> > $network-userspace-apps like network-manager (NM), wpa-supplicant etc.
> > are helpful... if you want your issue be tracked... successfully :-).
> >
> > Check also docs section for debugging the different wifi-drivers on
> > <wireless.kernel.org>.
> >
> > Hope this helps you!
> >
> > Regards,
> > - Sedat -
> >
> >> Stanislaw
> >> --
> >> To unsubscribe from this list: send the line "unsubscribe
> linux-wireless" in
> >> the body of a message to <email address hidden>
> >> More majordomo info at http://vger.kernel.org/majordomo-info.html
>

[MM (mmme)]

Hi I have an HP Envy dv4-5243cl

I'm trying to get this to work in 12.04. At present I've only tested the 12.04 from the Live CD....

For me the problem is not the driver support in the kernel, to me I'm having more like an ACPI issue.

My Envy assigns the F12 as the WiFi switch, I think this is common in all the Eny line of laptops.

For a distro that has the latest 3.8x or 3.9x kernel this will work , but if I reboot the wifi does not work, unless I press the F12 at the Grub menu, then reboot, or if I shut down the pc then turn it back on it works this way also.

lspci always shows the device too.

The F12 also does not work under Unbuntu, red color= off white color= on and in Ubuntu it's always red.

I hope Canonical will start supporting this driver in the HP Envy line of computers so that the F12 key works to turn the wifi on and off, as well as getting the driver to stick on a reboot, without having to always first press the F12 then reboot, or shut the comptuer off...

THANKS

[dudumomo (dudumomo-gmail)]

Same issue here, not working

I'm having Ubuntu 13.10 but Network Manager do not recognize my RT3290.
WICD does but the connection drop few secondes after or the signal is very weak.

I've tried with the latest available kernel 3.11.0-999-generic and downloaded the latest linux firmware from their git depo, without sucess.

Hope you can help !

PS: My computer is an Asus X450JF

[penalvch (penalvch)]

rojanu, is this still an issue for you in Raring+? If so, as per h20565.www2.hp.com/portal/site/hpsc/template.PAGE/public/psi/swdHome/?sp4ts.oid=5229457&spf_p.tpst=swdMain&spf_p.prp_swdMain=wsrp-navigationalState%3DswEnvOID%253D4059%257CswLang%253D%257Caction%253DlistDriver&javax.portlet.begCacheTok=com.vignette.cachetoken&javax.portlet.endCacheTok=com.vignette.cachetoken#BIOS an update is available for your BIOS (F.43). If you update to this following https://help.ubuntu.com/community/BiosUpdate , does it change anything? If it doesn't, could you please both specify what happened, and just provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful.

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Thank you for your understanding.

[rojanu (rojanu)]

I had upgraded to Saucy a while back but the wireless wasn't working. However, I just upgraded to kernel 3.11.0-15 and the wireless is working

[penalvch (penalvch)]

rojanu, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1156363/comments/15 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.