I'm experiencing similar connectivity problems on Ubuntu 10.04 64-bit.
Booting with mem=3G seems to fix the problem.
--
Skge broken for Marvell network chip
https://bugs.launchpad.net/bugs/131965
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
bug reported : bug 595262
--
Skge broken for Marvell network chip
https://bugs.launchpad.net/bugs/131965
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/m
Tim - OK, I've fixed Oops, but still exist issue with 100Mb/s instead of
1Gb/s.
** Attachment added: "dmesg.log"
http://launchpadlibrarian.net/50414903/dmesg.log
--
Skge broken for Marvell network chip
https://bugs.launchpad.net/bugs/131965
You received this bug notification because you are a
Expired, no response from the original reporter.
** Changed in: linux (Ubuntu)
Importance: Medium => Undecided
** Changed in: linux (Ubuntu)
Status: In Progress => Invalid
** Changed in: linux (Ubuntu)
Assignee: Tim Gardner (timg-tpi) => (unassigned)
--
Skge broken for Marvell n
Given that the original reporter hasn't commented on this bug in over 3
years I'm going to close this one and ask that you guys start your own
bugs (since you all have different issues).
Julien - Use 'ubuntu-bug linux' to upload your system information whilst
running the kernel causing the problem
** Attachment added: "lspci.vvnn.log"
http://launchpadlibrarian.net/50402989/lspci.vvnn.log
--
Skge broken for Marvell network chip
https://bugs.launchpad.net/bugs/131965
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
I get 100Mb/s instead of 1000Mb/s on Gigabit card.
** Attachment added: "dmesg.log"
http://launchpadlibrarian.net/50402988/dmesg.log
--
Skge broken for Marvell network chip
https://bugs.launchpad.net/bugs/131965
You received this bug notification because you are a member of Ubuntu
Bugs, which
Julien or Alex - please attach the output of 'lspci -vvnn' and 'dmesg'
from the kernel version that _is_ failing to bring up your network.
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
--
Skge
still exist in 10.04 server
--
Skge broken for Marvell network chip
https://bugs.launchpad.net/bugs/131965
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com
Also try with a mainline 2.6.32, same problem.
--
Skge broken for Marvell network chip
https://bugs.launchpad.net/bugs/131965
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https
I can confirm it's still an issue on lucid amd64, the i386 didn't have
the problem.
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
Skge broken for Marvell network chip
https://bugs.launchpad.net/bugs/131965
You received this bug notification because you are a member of Ubuntu
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: NVidia [HDA NVidia], device 0: AD198x Analog [AD198x Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USER
Hi Julien,
As Jeremy mentioned, if you are able to test with the latest Lucid Beta
release, that would be great.
http://cdimage.ubuntu.com/releases/lucid/beta-1/ . If the issue does
remain, can you reproduce the issue and then run the following command
which will automatically gather and attach r
Julien,
Are you able to test against Lucid? I'd like to see if it is the same in
the current development version.
Thanks!
~JFo
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
Skge broken for Marvell network chip
https://bugs.launchpad.net/bugs/131965
You received this bug
It's still a problem on Karmic amd64.
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
Skge broken for Marvell network chip
https://bugs.launchpad.net/bugs/131965
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubun
This bug report was marked as Triaged a while ago but has not had any
updated comments for quite some time. Please let us know if this issue
remains in the current Ubuntu release,
http://www.ubuntu.com/getubuntu/download . If the issue remains, click
on the current status under the Status column
I can confirmed the problem :
Jaunty amd64, kernel 2.6.28.
With 3 Gb of RAM, all is OK
With 4 Gb, the network is down. I can't access to the Internet, and can't even
access to my router with the local adress (192.168.X.X).
I tried the fix which Jim posted a link, but recompiled the kernel with
I have found the following but I am reluctant to shove this into the
pipeline without more info. This applies to one board but there could
be a common thread. I have emailed a query to the author of the patch
which, along with the commentary, is here:
http://patchwork.ozlabs.org/patch/22884/
-
I've managed to get around this problem by installing an old Linksys NIC
in one of the PCI slots and telling bios to ignore the onboard NIC.
Apparently a different driver is installed...
I happened to grab a SUSE .iso 64 bit cd and went with it cause for once
(out of numerous Ubuntu installs) the
StanS, Now that Jaunty is released, please upgrade and test again. As for what
we want, see Leann's comment 13 above for pointers. This bug is for the skge
driver for the Marvell NIC. Please confirm. If you managed to receive an
address via DHCP, the
NIC had to be working. You can verify th
For the record - it was the Beta install of Jaunty. Not sure if that
will make a difference ?
--
Skge broken for Marvell network chip
https://bugs.launchpad.net/bugs/131965
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I am not able to network after installing Jaunty. I've followed numerous
suggestions on the forums to no avail.
DHCP appears to be working as an IP address is assigned.
What information shall I provide ?
--
Skge broken for Marvell network chip
https://bugs.launchpad.net/bugs/131965
You received
Please try the Jaunty release. This update contains fixes for restarting the
interface
under conditions similar to yours. Let us know the result so we can either
pursue this
further or close the bug.
--
Skge broken for Marvell network chip
https://bugs.launchpad.net/bugs/131965
You received t
Marked the development kernel as Triaged with Medium priority, based on
the feedback and information provided in the last few posts. I will
close the task against the old kernel.
Assigned to Ubuntu Kernel Team.
Thank you.
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
Ass
Hello,
I am having the same problem with DGE-530T on 32bit x86 machine with
Hardy [ 2.6.24-19-generic]. Also, as mentioned in this post I am able to
reproduce this failure by using vlc - streaming. Since, there is no
reported fix, I will compile a custom kernel with sk98lin (deprecated).
I'm also
** Attachment added: "version.log"
http://launchpadlibrarian.net/18020087/version.log
--
Skge broken for Marvell network chip
https://bugs.launchpad.net/bugs/131965
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
** Attachment added: "uname-a.log"
http://launchpadlibrarian.net/18020081/uname-a.log
--
Skge broken for Marvell network chip
https://bugs.launchpad.net/bugs/131965
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
** Attachment added: "lspci-vvnn.log"
http://launchpadlibrarian.net/18020075/lspci-vvnn.log
--
Skge broken for Marvell network chip
https://bugs.launchpad.net/bugs/131965
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
Hello,
I am finding the exact same issue with the latest 2.6.27-4 kernel
(Intrepid Alpha5 -- 64-bit). Supplying the kernel with the mem=3G boot
parameter allows the skge driver to pass traffic. Without it...all seems
functional but no traffic is passed.
I have attached the requested outputs/logs
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
To: [EMAIL PROTECTED]
Sent: Sunday, August 24, 2008 6:33:10 AM
Subject: [Bug 131965] Re: Skge broken for Marvell network chip
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. W
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering is this still an issue
for you? Can you try with latest Ubuntu release? Thanks in advance.
--
Skge broken for
Thanks for the files. Just for future reference, if you could attach
each file as a separate attachment it would be much appreciated. Could
you actually try booting without the mem=3G parameter. Hopefully useful
error messages may be logged which will help with debugging. Thanks.
--
Skge brok
Update on testing 2.6.24-3-generic. Without the mem=3G still not able
to pass network traffic. See attached log files.
** Attachment added: "skge.tar.gz"
http://launchpadlibrarian.net/11240582/skge.tar.gz
--
Skge broken for Marvell network chip
https://bugs.launchpad.net/bugs/131965
You rec
Per the kernel team's bug policy, can you please attach the following
information for the newer Hardy kernel. Please be sure to attach each
file as a separate attachment.
* uname -a > uname-a.log
* cat /proc/version_signature > version.log
* dmesg > dmesg.log
* sudo lspci -vvnn > lspci-vvnn.log
Just a note that the kernel source package for the Hardy release is now
just 'linux' not 'linux-source-2.6.24'. The naming convention changed
as of this new release. Sorry for any confusion. I've gone ahead and
reassigned to the appropriate package.
** Changed in: linux (Ubuntu)
Sourcepackagena
Update:
This problem still exists in Hardy 64-bit. Using skge module. Without mem=3G
passed to the kernel this driver does not work.
Details of my working setup:
>From /boot/grub/men.lst
kernel /boot/vmlinuz-2.6.24-2-generic root=UUID=80479eaf-1974-4e71-ad71
-a7982df90353 mem=3G ro qui
Update:
I have played around with a few things. Right now I have network traffic with
reasonable speed. Not sure which of the kernel parms worked Maybe all of them
but I suspect it was booting the kernel with mem=3G that worked. So must be a
bug with skge or sk98lin and addressing over 3Gb me
OK one more update. skge driver works with mem=3G passed to the kernel.
[EMAIL PROTECTED]:~# lsmod | grep sk
skge 47248 0
[EMAIL PROTECTED]:~# lshw -C network
*-network
description: Ethernet interface
product: 88E8001 Gigabit Ethernet Controller
Sorry not sure what I was thinking. I am not using Feisty. I am using
Gutsy(7.10) 64-bit version.
--
Skge broken for Marvell network chip
https://bugs.launchpad.net/bugs/131965
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
I think Feisty 64-bit might have a problematic skge module. I can use
the network through 32-bit Live CD's and installed versions from Ubuntu
and Fedora with no problem. Vista 32-bit is also installed on this
machine and working. With the 64-bit version though I can see the
adapter and assign a
Hi ! I'm french so please scuse me for my poor english. Last night I tried to
install a Feisty Fawn release on a computer with an Asus P4P800 Deluxe
motherboard and I experienced a strange behavior of my NIC.. The installation
procedure worked fine until the progression reached 82% : Mirrors Che
** Description changed:
Binary package hint: linux-image-2.6.22-9-generic
Since upgrade to Gutsy, a few weeks ago, I've been having problem with
random lockups in the skge driver. They occur with varying frequency,
usually once every two days or so, but sometimes a little more often.
Allright. The bug, after not being produced for a long while, occurred
again tonight.
Here's the wanted messages-log.
** Attachment added: "Messages-log when the problem occured."
http://launchpadlibrarian.net/8981119/messages.0
--
Skge broken for Marvell network chip
https://bugs.launchpad.
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It would be helpful to have more than just the output of
'dmesg" as it seems to be missing a fair bit at the beginning. So if
you could reproduce the issue and then attach '/var/log/messages' to
your bug report th
Bug #37784 seems related, although the symptoms differ quite a lot.
I have no problem with large uploads, as is described. In fact, when
video-streaming I managed to hang the driver pretty repeatedly, while
when copying the video material over to the Mac, everything went smooth.
Also, for me I di
Also note; this is a regression from Feisty.
--
Skge broken for Marvell network chip
https://bugs.launchpad.net/bugs/131965
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
h
Relevant lshw;
*-pci:0
description: PCI bridge
product: CK804 PCI Bridge
vendor: nVidia Corporation
physical id: 9
bus info: [EMAIL PROTECTED]:00:09.0
version: a2
width: 32 bits
clock: 66MHz
capabilities
48 matches
Mail list logo
