Wireless: Intel 802.11 b/g/n with Bluetooth in HP dvdt-7000 Quad Edition Series Machine

Hi:

While I was going step by step in the sticky to get my wireless to work on my openSUSE 12.1 install; I found this in the Yast → Hardware Profile after saving the file as text (couldn’t locate any wireless device as is).

Firmware iwlwifi-2030-5.ucode not found and the wireless device is not enabled (similar, not exactly this message). I looked at /lib/firmware and found bunch of iwlwifi* files but not exactly this one.

I found iwlwifi-2030-6.ucode from the web and pasted it in /lib/firmware, still didn’t work (same error iwlwifi-2030-5.ucode not found) . I tried renaming the same file as iwlwifi-2030-5.ucode, threw an error that version 6 is not supported by the driver.

I’ve updated all the files using “Update all when update available from Yast”. I hope I have the latest driver. I couldn’t find iwlwifi-2030-5.ucode anywhere on the web. If somebody can help me locate this file somewhere or any update needed to the driver, please let me know.

Thanks,
Arun

FYI: ethernet works fine. Didn’t test bluetooth, but seems to work (it searches for devices).

On 08/16/2012 08:56 AM, arunms wrote:
>
> Hi:
>
> While I was going step by step in the sticky to get my wireless to work
> on my openSUSE 12.1 install; I found this in the Yast → Hardware
> Profile after saving the file as text (couldn’t locate any wireless
> device as is).
>
> Firmware iwlwifi-2030-5.ucode not found and the wireless device is not
> enabled (similar, not exactly this message). I looked at /lib/firmware
> and found bunch of iwlwifi* files but not exactly this one.
>
> I found iwlwifi-2030-6.ucode from the web and pasted it in
> /lib/firmware, still didn’t work (same error iwlwifi-2030-5.ucode not
> found) . I tried renaming the same file as iwlwifi-2030-5.ucode, threw
> an error that version 6 is not supported by the driver.
>
> I’ve updated all the files using “Update all when update available from
> Yast”. I hope I have the latest driver. I couldn’t find
> iwlwifi-2030-5.ucode anywhere on the web. If somebody can help me locate
> this file somewhere or any update needed to the driver, please let me
> know.

You could likely add the wireless repo and install the compat-wireless package
for your kernel, which would switch to using version 6 of the firmware; however,
the missing firmware is an oversight on the part of Intel. In other instances,
they have deleted an old version when they submitted a newer firmware file to
the repo that is the source for the kernel-firmware package. I could not find
any mention of version 5 in the commit logs for the repo, thus I do not know if
that is the reason for the missing firmware here.

I sent a message to the wireless group at Intel and Cc’d the wireless mailing
list asking about this firmware, and requesting that it be submitted to the
firmware repo. I also asked them to send me a copy. If/when that happens, I will
make it available on a publicly-accessible FTP site, and notify you here.

Thanks lwfinger](http://forums.opensuse.org/members/lwfinger.html) for the information and for the efforts to get the firmware. In the mean time, I’ll try the compat-wireless package and see if it helps.

Thanks,
Arun

Thanks lwfinger](http://forums.opensuse.org/members/lwfinger.html). Installing compat-wireless made my wireless to work.

On 08/17/2012 02:06 PM, arunms wrote:
>
> Thanks ‘lwfinger’ (http://forums.opensuse.org/members/lwfinger.html).
> Installing compat-wireless made my wireless to work.

I finally heard back from the Intel wireless group. It turns out that the
firmware iwlwifi-2030-5.ucode was an experimental version that was only used
internally, and never will be released. I told them that I thought it was poor
practice to release a driver for which the firmware would never be available.
Unfortunately, my opinion is not likely to carry much weight. :frowning:

Be careful when upgrading your kernel as a kernel change without the
corresponding compat-wireless package will not work. Once you change to openSUSE
12.2, then the in-kernel driver will work, thus the situation is temporary.

Thanks lwfinger for the update.