Toshiba R200 Marvell Yukon not supported by default

[Davyd]

The Marvell Yukon gigabit ethernet driver in the Toshiba Portege R200 is not
supported by default by the Breezy kernel. In addition to this, the version of
the Yukon driver, sk98lin in the 2.6.12 source tree is rather out of date. You
can get an updated version (8.35) from the Marvell website.

This driver has had issues in the past. I'm not sure if they are still present,
I don't use wired ethernet that often. It may be desirable to put this driver
into its own package.

[Richard Kleeman (kleeman)]

Duplicate of bug #12509??

[Stephan Rügamer (sruegamer)]

Yes and No...

I just set the laptop keyword, to declare this as a "to be reviewd" bug for the
LaptopMission (see http://wiki.ubuntu.com/LaptopTesting)

[Stephan Rügamer (sruegamer)]

I just set a dependency on #6142
So I don't want to mark it as duplicate.

[Richard Kleeman (kleeman)]

Sounds good to me.

[Matthew Garrett (mjg59)]

Easiest thing to do may be to include the Marvell driver but only use it on
devices that are unsupported by the kernel driver. This is easy enough to manage.

[Greg Taylor (gtaylor)]

(In reply to comment #0)
> The Marvell Yukon gigabit ethernet driver in the Toshiba Portege R200 is not
> supported by default by the Breezy kernel. In addition to this, the version of
> the Yukon driver, sk98lin in the 2.6.12 source tree is rather out of date. You
> can get an updated version (8.35) from the Marvell website.
>
> This driver has had issues in the past. I'm not sure if they are still present,
> I don't use wired ethernet that often. It may be desirable to put this driver
> into its own package.
This is also an issue on the Toshiba Tecra A4. I had to finish the install with
my wireless connection (which worked). Since the wired NIC wasn't picked up,
wireless became eth0 which caused all sorts of funny things to happen.

[Greg Taylor (gtaylor)]

It looks like there are some drivers available at
http://www.syskonnect.com/syskonnect/support/driver/d0102_driver.html.

[Sven Broeckling (sven-broeckling)]

I noticed the same on my Asus v6800v. While hoary runs quite well with the
sk98lin module, breezy just comes with ne non-working (for me) skge driver.
Would it be possible to compile the old driver too? That would make it possible
to use breezy out of the box on Marvell Yukon NICs, without building the kernel.

The interface comes up correct, with :

Sep 10 17:04:40 deepblue kernel: [4294678.341000] skge addr 0xfbffc000 irq 5
chip Yukon-Lite rev 9
Sep 10 17:04:40 deepblue kernel: [4294678.341000] skge eth0: addr 00:11:d8:89:ae:c4

in messages, but even if i set an ip address, it's not possible to get traffic
through the nic. No logs, nothing else

[LarsIvarIgesund (larsivar)]

I have a Toshiba Tecra A3 with a Marvell Yukon-card. It don't work with any of the syskonnect
drivers in the vanillakernel (sk98lin, skge), including 2.6.13. To make it work, I have patched
the kernel with the sk9elin driver from www.syskonnect.com, version 8.23.

Neither Hoary, nor Breezy preview works for me, and the wireless isn't an option (although it
might work) as it needs additional setup through wpa_supplicant to work in my network.

lspci lists the ethcard as:

Ethernet controller: Marvell Technology Group Ltd. 88E8036 Fast Ethernet Controller (rev 10)

[Dan Berger (dan-theidiots)]

(In reply to comment #8)
> I noticed the same on my Asus v6800v. While hoary runs quite well with the
> sk98lin module, breezy just comes with ne non-working (for me) skge driver.

I have the same exact problem with the Asus A8V-E Deluxe, which has the Marvell
88E8053. SysKonnect's drivers worked perfectly in Hoary but don't in Breezy.
Here is what the driver's install log says:

+++ Compile the driver
+++ ====================================
make: Entering directory `/usr/src/linux-headers-2.6.12-8-386'
  Building modules, stage 2.
  MODPOST
make: Leaving directory `/usr/src/linux-headers-2.6.12-8-386'
+++ Compiler error

> Would it be possible to compile the old driver too?

I think that this would be the best intermediary solution.

[Matthew Garrett (mjg59)]

Can you try 2.6.12-8-686-8.13 (ie, the latest kernel image)? It has a new driver
that should support your hardware.

[Dan Berger (dan-theidiots)]

(In reply to comment #11)
> Can you try 2.6.12-8-686-8.13 (ie, the latest kernel image)? It has a new driver
> that should support your hardware.

I loaded the module 'sky2' and while it seemed to work intially, after a few
seconds of network activity and access, the network goes down and becomes
unreachable. A quick ifdown/rmmod/modprobe fixes this for a few seconds but then
it once again goes down.

My card does get detected though, which is a start :)

[Greg Taylor (gtaylor)]

This still remains in a state of non-functioning in the latest Breezy on the
Toshiba Tecra A4. Should I make another bug post for this or keep watching here?

[Matthew Garrett (mjg59)]

Make sure you're running 2.6.12-8.13. It'll break, but it's better than nothing.
I'm working on integrating the sk98lin driver now.

[Richard Kleeman (kleeman)]

You can integrate sk98lin by patching the kernel using the vendor code. This can
be done in a Debian/Ubuntu friendly way. See the howto here (last few lines)

http://www.ubuntuforums.org/showthread.php?t=47615

[Greg Taylor (gtaylor)]

(In reply to comment #14)
> Make sure you're running 2.6.12-8.13. It'll break, but it's better than nothing.
> I'm working on integrating the sk98lin driver now.

I'm running the absolute latest versions of everything to assist with laptop
testing. The wireless situation has improved but the Yukon remains "Unknown" and
without support as of now.

[Matthew Garrett (mjg59)]

What happens if you attempt to load the sky2 module?

[Richard Kleeman (kleeman)]

The network often hangs with sky2 at present. Here is some recent discussion by
the kernel maintainer:

http://marc.theaimsgroup.com/?l=linux-netdev&m=112673920904041&w=2

[Stephan Rügamer (sruegamer)]

Hi,

this is the output of /var/log/messages after loading the driver during bootup

Sep 19 20:02:21 localhost kernel: [4294794.332000] sky2 eth0: disabling interface
Sep 19 20:02:38 localhost kernel: [4294810.994000] sky2 eth0: enabling interface
Sep 19 20:02:38 localhost kernel: [4294810.996000] sky2 eth0: hw error interrupt
status 0x20
Sep 19 20:02:38 localhost kernel: [4294811.007000] sky2 eth0: hw error interrupt
status 0x20
Sep 19 20:02:38 localhost kernel: [4294811.018000] sky2 eth0: hw error interrupt
status 0x24
Sep 19 20:02:44 localhost kernel: [4294816.728000] sky2 eth0: Link is up at 1000
Mbps, full duplex, flowcontrol both
Sep 19 20:02:59 localhost kernel: [4294831.520000] sky2 eth0: hw error interrupt
status 0x24
Sep 19 20:03:03 localhost kernel: [4294836.085000] sky2 eth0: hw error interrupt
status 0x4
Sep 19 20:04:21 localhost kernel: [4294913.853000] sky2 eth0: hw error interrupt
status 0x24
Sep 19 20:05:42 localhost kernel: [4294995.414000] sky2 eth0: disabling interface

here is more output of /var/log/syslog after dhclient3

Sep 19 20:02:38 localhost kernel: [4294810.994000] sky2 eth0: enabling interface
Sep 19 20:02:38 localhost kernel: [4294810.996000] sky2 eth0: hw error interrupt
status 0x20
Sep 19 20:02:38 localhost kernel: [4294810.996000] sky2 eth0: ram data read
parity error
Sep 19 20:02:38 localhost kernel: [4294811.007000] sky2 eth0: hw error interrupt
status 0x20
Sep 19 20:02:38 localhost kernel: [4294811.007000] sky2 eth0: ram data read
parity error
Sep 19 20:02:38 localhost kernel: [4294811.018000] sky2 eth0: hw error interrupt
status 0x24
Sep 19 20:02:38 localhost kernel: [4294811.018000] sky2 eth0: ram data read
parity error
Sep 19 20:02:38 localhost kernel: [4294811.018000] sky2 eth0: RX parity error

I would say, remove this driver, because it annoys more people to have this
driver in the kernel, then no driver at all.

Put the driver as test module somewhere else, and we can test it before we
declare it as usable driver for this card.

tested on toshiba portege r200 with todays daily iso, 2.6.12-8.14 kernel rev.

regards,

\sh

[Matthew Garrett (mjg59)]

Fixed in the latest kernel.

[Richard Kleeman (kleeman)]

As per 6142,

sudo modprobe sk98lin gives:

FATAL: Module sk98lin not found.
Is the patch operational?

[Matthew Garrett (mjg59)]

No. Reopening.

[Corey Burger (corey.burger)]

Seems to be fixed now. Stephan Hermann concurs