• Home
  • Help
  • Search
  • Login
  • Register
Pages: [1]
Author Topic: Linux 2.6.36-rc7 - ethernet not working  (Read 3452 times)
Linux777
Newbie
*

Karma: 0
Posts: 5


View Profile
« on: October 10, 2010, 12:22:35 PM »

Hello!
I have simple SheevaPlug. I got Angstrom (my own build, stable 2009 branch) working on it from SD card. I've also built kernel from git - 2.6.36-rc7 version, it boots, SD and USB working, but ethernet not.

I also know about ioremap problem in latest kernel, and simple patch which allows it to work:

MV-643xx 10/100/1000 ethernet driver version 1.4
mv643xx_eth smi: probed
net eth0: port 0 with MAC address f0:ad:4e:00:05:eb

In my system I see eth0, I can configure it, but wireshark tell me that no packets going from sheevaplug...
I boot kernel 2.6.36-rc7 by TFTP, uImage successfully downloaded, it boots, but after this no packets...

P.S.
Please, add adequate support of mainline kernels. This is not convenient to sit on some exotic branches... It's important for me to use latest kernels, built by my own hands.
Logged

birdman
Sr. Member
****

Karma: 4
Posts: 443


View Profile WWW
« Reply #1 on: October 10, 2010, 06:10:18 PM »

Please, add adequate support of mainline kernels.
Of whom are you asking that?
I'm running 2.6.35.7 - which is the latest official release and the eth0 port works fine for me there
Quote
It's important for me to use latest kernels, built by my own hands.
So what support are you asking for?  That would be someone else's hands.
Logged

Linux777
Newbie
*

Karma: 0
Posts: 5


View Profile
« Reply #2 on: October 16, 2010, 07:30:58 AM »

Please, add adequate support of mainline kernels.
Of whom are you asking that?
I'm running 2.6.35.7 - which is the latest official release and the eth0 port works fine for me there
Who released "latest official release"? kernel.org or Marvell?
P.S.
Can't see any foreseeable reason for such forks as Marvell do, really... O_o
Logged

birdman
Sr. Member
****

Karma: 4
Posts: 443


View Profile WWW
« Reply #3 on: October 16, 2010, 04:42:14 PM »

Who released "latest official release"? kernel.org or Marvell?
kernel.org.  cxbiker61 applies a few patches, but none affect Ethernet, AFAIK.
Quote
Can't see any foreseeable reason for such forks as Marvell do, really... O_o
I don't see a fork.  I do see some patches to cover new hardware before it gets included into the standard kernel, but that's normal.
Logged

weltall
Newbie
*

Karma: 1
Posts: 11


View Profile
« Reply #4 on: October 21, 2010, 01:26:05 AM »

i've the same problem but on 2.6.36 which is now a stable release on kernel.org. dhclient stalls indefinitely, trying to set an ip and doing a ping makes the interface led blink but nothing else the network is unreacheable.
Logged

Stupendoussteve
Newbie
*

Karma: 0
Posts: 2


View Profile
« Reply #5 on: October 23, 2010, 12:06:32 PM »

i've the same problem but on 2.6.36 which is now a stable release on kernel.org. dhclient stalls indefinitely, trying to set an ip and doing a ping makes the interface led blink but nothing else the network is unreacheable.

I am having this same issue with stock 2.6.36 and the Sheevaplug. It works fine with the previous stable 2.6.35.7.

Check your arp table (arp -v), I have noticed mine shows "incomplete" where it should be showing hardware addresses, like they're being corrupted at some point.

I am in the process of building a custom 2.6.36 using the driver from 2.6.35.7, and seeing if it functions again. Afterwards I am going to move from commit 9b2c2ff7a1c04e69842254dd4afe0f8ad4efa439 (which appears to be the last one applied in 2.6.35) up until 50a749c1f2fc8f03232c174c9dbc78a78f9bebfd, where it isn't working to try and figure out at what point it was broken.

To some of the above commentary, 2.6.36 was only just released, until that point the latest official release was 2.6.35.7... the "rc" part shows as much, it is a candidate and not the actual stable release, rather a development snapshot.
« Last Edit: October 23, 2010, 12:20:38 PM by Stupendoussteve » Logged

Stupendoussteve
Newbie
*

Karma: 0
Posts: 2


View Profile
« Reply #6 on: October 23, 2010, 01:25:48 PM »

The issue should be fixed in the next kernel bump. It looks like it was caused by commit c477d0447db08068a497e7beb892b2b2a7bff64b, and fixed in commit be8c648051048bc66fbca590d00f3e8543ec32af (still in Linux-next). It you patch it into your kernel it should function with 2.6.36 (will confirm once mine finishes compiling).

Update: Indeed it works.
Code:
[steve@sheeva ~]$ uname -a
Linux sheeva.lannet 2.6.36p1 #1 Sat Oct 23 16:21:30 CDT 2010 armv5tel Feroceon 88FR131 rev 1 (v5l) Marvell SheevaPlug Reference Board GNU/Linux
[steve@sheeva ~]$ ping google.com
PING google.com (74.125.227.52) 56(84) bytes of data.
64 bytes from 74.125.227.52: icmp_seq=1 ttl=55 time=25.6 ms
« Last Edit: October 23, 2010, 03:59:08 PM by Stupendoussteve » Logged

weltall
Newbie
*

Karma: 1
Posts: 11


View Profile
« Reply #7 on: October 24, 2010, 01:13:57 AM »

it worked well also here thanks Smiley
Logged

Linux777
Newbie
*

Karma: 0
Posts: 5


View Profile
« Reply #8 on: November 06, 2010, 05:26:27 PM »

Now I just updated to 2.6.37-rc1 from git and ethernet working OK.
P.S.
No need in non-mainline kernels, now we just download from kernel.org and it works Wink
Logged

Pages: [1]
Print
Jump to: