mrv8k was removed from Linux tree

[Simon]

The two relevant lines from /var/log/syslog are:

Mar 11 15:12:12 ubuntu firmware_helper[6861]: main: error loading '/lib/firmware/mrv8k-b.fw' for device '/class/firmware/0000:03:00.0' with driver 'mrv8k'

Mar 11 15:12:13 ubuntu NetworkManager: <debug info>^I[1142089933.667043] (): New device added (hal udi is '/org/freedesktop/Hal/devices/pci_11ab_1faa').

[j^ (j)]

does this driver not work in network-manger or does it not work at all?
if it does not work at all this is a ndiswrapper or kernel bug,
if it works with iwconfig etc, but not with network-manager it is a network-manager bug and it would be good to get the full log of NetworkManager

[Fabio Silva (woldpt)]

I think it is a kernel bug, as you said.

My 'dmesg':
-------------------------------------
4294685.511000] mrv8k: Marvel 8xxx Wireless driver, 0.0.2
[4294685.511000] mrv8k: Copyright(c) 2005 Luc Saillard <email address hidden>
[4294685.511000] mrv8k: mrv8k_init_one: enter
[4294685.511000] ACPI: PCI Interrupt 0000:00:08.0[A] -> GSI 19 (level, low) -> IRQ 177
[4294685.511000] mrv8k: bar1 (0xdfff0000) relocated at 0xe0f80000
[4294685.511000] mrv8k: bar2 (0xdffe0000) relocated at 0xe0fa0000
[4294685.593000] 8139too Fast Ethernet driver 0.9.27
[4294685.698000] mrv8k: Firmware 'mrv8k-b.fw' not available or load failed.
[4294685.698000] mrv8k: mrv8k_init_one: return -2
[4294685.698000] mrv8k: Command SET_RADIO. len=12 state=off preamble=auto
[4294685.698000] mrv8k: queue command (dbde4200)
[4294685.698000] mrv8k: kickoff command (dbde4200)
(...)
[4294686.705000] mrv8k: mrv8k_init_one: return -2
[4294686.705000] mrv8k: probe of 0000:00:08.0 failed with error -2
------------------------------------

And if I blacklist this module and run ndiswrapper with cdrom .inf driver (as I did in Breezy) I get kernel panic :-(

Theorically it is a kernel's problem, I think...
In Breezy it was so easy... :-(

[Simon (simon-turvey)]

I'm not so sure it's possible to conclude that this is a kernel bug just yet
- unless you have more information than that which I presented in the
original report. It seems clear from the line:

Mar 11 15:12:12 ubuntu firmware_helper[6861]: main: error loading
'/lib/firmware/mrv8k-b.fw' for device '/class/firmware/0000:03:00.0'
with driver 'mrv8k'

that the driver is present but the firmware is not.

From Fabio's email:

[4294685.698000] mrv8k: Firmware 'mrv8k-b.fw' not available or load failed.

Also indicative of the firmware being missing.

Cheers,

Simon

On 3/31/06, Fabio Silva <email address hidden> wrote:
>
> I think it is a kernel bug, as you said.
>
> My 'dmesg':
> -------------------------------------
> 4294685.511000] mrv8k: Marvel 8xxx Wireless driver, 0.0.2
> [4294685.511000] mrv8k: Copyright(c) 2005 Luc Saillard <email address hidden>
> [4294685.511000] mrv8k: mrv8k_init_one: enter
> [4294685.511000] ACPI: PCI Interrupt 0000:00:08.0[A] -> GSI 19 (level,
> low) -> IRQ 177
> [4294685.511000] mrv8k: bar1 (0xdfff0000) relocated at 0xe0f80000
> [4294685.511000] mrv8k: bar2 (0xdffe0000) relocated at 0xe0fa0000
> [4294685.593000] 8139too Fast Ethernet driver 0.9.27
> [4294685.698000] mrv8k: Firmware 'mrv8k-b.fw' not available or load
> failed.
> [4294685.698000] mrv8k: mrv8k_init_one: return -2
> [4294685.698000] mrv8k: Command SET_RADIO. len=12 state=off preamble=auto
> [4294685.698000] mrv8k: queue command (dbde4200)
> [4294685.698000] mrv8k: kickoff command (dbde4200)
> (...)
> [4294686.705000] mrv8k: mrv8k_init_one: return -2
> [4294686.705000] mrv8k: probe of 0000:00:08.0 failed with error -2
> ------------------------------------
>
> And if I blacklist this module and run ndiswrapper with cdrom .inf driver
> (as I did in Breezy) I get kernel panic :-(
>
> Theorically it is a kernel's problem, I think...
> In Breezy it was so easy... :-(
> --
> Netgear WG511 v2 not supported on Flight 5 Live CD
> https://launchpad.net/malone/bugs/34458
>

[Matt Zimmerman (mdz)]

If there is a bug here, it is in the kernel.

Ben, is there redistributable firmware available for this driver? If not, there is nothing we can do.

[Rune Kock (rune-kock)]

I recommend that this driver is removed!

Even after I install the firmware, it still doesn't work. The upstream author (http://www.saillard.org/linux/mrv8k/) has no documentation on how to use it. I don't think the driver is finished at all!

It is not part of the plain vanilla kernel, but is added by Debian or Ubuntu.

And, as long as the mrv8k-driver tries to load at boot, ndiswrapper doesn't work.

Rune

[Fabio Silva (woldpt)]

I deleted the driver from /lib/modules/2.6.15-23-k7/kernel/drivers/net/wireless

This resolved MY problem. Ndiswrapper runs fine again like in Breezy. I hope it helps somebody too

[Cafuego (cafuego)]

I just had a go as well (WG511v3) but no joy. The `mrv8k' driver is nowhere near finished and the kernel complains about it when it's loaded:

[17181720.872000] eth1 (WE) : Driver using old /proc/net/wireless support, please fix driver !

The upstream driver hasn't been changed since Dec 16, 2005.

I suggest adding mrv8k to /etc/modprobe.d/blacklist by default, as it doesn't actually work and interferes with a workaround (ndiswrapper).

[stefab (bluefuture)]

Please see also this message from the kernel mailing list:
http://<email address hidden>/msg28683.html

[Launchpad Janitor (janitor)]

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 linux-source-2.6.15 kernel bug to the new "linux" package. We appreciate your patience and understanding as we make this transition. Also, if you would be interested in testing the upcoming Intrepid Ibex 8.10 release, it is available at http://www.ubuntu.com/testing . Please let us know your results. Thanks!

[Leann Ogasawara (leannogasawara)]

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.

[Pete Graner (pgraner)]

This was fixed at some point since the original report... Marking as Fixed Released

[Leann Ogasawara (leannogasawara)]

I believe this bug has been resolved so I'll go ahead and mark this Fix Released. If this is not the case, please confirm the issue remains in the most recent development release, currently Jaunty 9.04 Alpha 5 - http://cdimage.ubuntu.com/releases/jaunty/ . Then set the status back to "New". Thanks.

[Shahar Or (mightyiam)]

I can't change status to new for some reason...
Anyway, the problem is that the driver isn't ready and is not in Linux tree any more.