The problem has already been stated unclearly. Traffic of over 10Mbps would cause timeout in about mins kernel: Can you attach the output of sudo dmidecode to this bug? I installed Kubuntu 6. Browse Requests Reports Product Dashboard. Attachments Terms of Use upstream-fix 6. Here’s a note from the newly released 2.

Uploader: Arashizragore
Date Added: 12 September 2005
File Size: 56.24 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 90277
Price: Free* [*Free Regsitration Required]

Because Marvsll must install the driver manually, I don’t shut my laptop down and it’s been 1 week now and everything is still fine. Dmesg looks good, but I just can’t get an IP.

Comment 12 Andy Gospodarek The reason that is significant, is that the bridging devices can often push more traffic through the box than when using the device as an endpoint. Bug attachments Output of dmidecode edit dmidecode output edit Add attachment.

If it remains maevell issue, could you please just make a comment to this? Mine has worked without any problems on FedoraCore6, but it is not recognized in F7-test4.

CONFIG_SKY2: SysKonnect Yukon2 support (EXPERIMENTAL)

It would be great for us to collect a list so we can help others that have problems. In the original thread on linux-net which 46 quoted from there are links to firmware downloads from Gigabyte and Jetway. I can also confirm that this problem is also present in the latest RHEL5.


This isn’t fixed, see reply. See full activity log.

The information about this bug in Launchpad is automatically pulled daily from the remote bug. Jyri Sillanpaa ubuntu-amorco wrote on October 23rd, 9. Ben Collins has backported the msrvell driver 0. Comment 11 Andy Gospodarek We have problems with Marvell 88E gigabit ethernet interface. Have you happenened to notice if the sky2-based hardware is the slower or faster link, or does it even matter?

[ubuntu] Marvell Yukon 88E sky2, sk98lin or skge?

You can find the srpm here: Tags for this Thread marvell 88eskge sk98lin sky2 marvell. Wow this thread came to life a few months later. Once testing of the upstream kernel is complete, please mark this bug as “Confirmed”.

Here’s dmesg grepped for sky2. When I say the interface came up, I do not mean pull an IP. BB code is On. I had originally thought that Windows 7 somehow broke my nic because I temporarily loaded it on the box to update firmware on some of my other devices.


If you could give it a spin, I’d appreciate it. Greg, can you attach the output of ‘uname -r’ and ‘modinfo sky2 grep version’, please?

Linux source code: drivers/net/ethernet/marvell/sky2.c (v) – Bootlin

Everything works fine in Windows. Page 1 of 2. With that said, I have installed Arch some 2 months ago kernel 3.

When installing, I get no error messages but am unable to pull an IP from my Marvell ethernet interface eth0. This request is not yet committed for inclusion in an Update release.

Here is a copy of the email that was sent out to address it: September 15th, 5.