From: Kyle Rose <krose@akamai.com>
To: linux-kernel@vger.kernel.org
Subject: sk98lin for 2.6.23-rc1
Date: Thu, 26 Jul 2007 11:16:36 -0400 [thread overview]
Message-ID: <46A8BAD4.8020004@akamai.com> (raw)
>From http://www.krose.org/~krose/computing.html:
Since the sky2 driver continues to suck ass (which is a technical
description for "it hangs all the time under load, at least on my
hardware" :-) ), I've fixed the sk98lin driver to compile for
linux-2.6.23-rc1. Those who continue to have problems with sky2 can
still use 2.6.23-rc1, simply by doing the following:
1.
Make sure you have the headers for your kernel properly installed
and linked to /usr/src/linux-$KVER.
2.
Download the sk98lin source from Marvell's site
<http://www.marvell.com/drivers/search.do>.
3.
Untar the driver and run the install.sh according to the
directions. It will fail.
4.
Look in /tmp for a directory called Sk98something. Go to
http://www.krose.org/~krose/projects/sk98lin/ and copy the
Makefile <http://www.krose.org/%7Ekrose/projects/sk98lin/Makefile>
and sky2.c <http://www.krose.org/%7Ekrose/projects/sk98lin/sky2.c>
into /tmp/Sk98something/all.
5.
Change into /tmp/Sk98something/all and execute:
sudo -H make -C /usr/src/linux-$KVER M=`pwd` modules
sudo -H make -C /usr/src/linux-$KVER M=`pwd` modules_install
6.
Blacklist sky2 in /etc/modprobe.d/blacklist, and (maybe not
necessary) manually load sk98lin in /etc/modules.
There. You're done. Stable networking at last... er, again.
Unfortunately, you lose the nicest differential feature of
sky2---WOL---but that's a small price to pay for networking stability of
a desktop machine. It's nice to be able to watch MythTV again without
having to sudo bash -c 'ifdown eth0; rmmod sky2; modprobe sky2; ifup
eth0' every few minutes.
Personally, I'd like to see sk98lin remain in the kernel proper until
sky2 goes at least 6 months without reported problems. The fact that I
am not the only one still seeing issues is a clear indication that sky2
(even with the recent patches in 2.6.23-rc1) is not yet ready to replace
sk98lin.
I'm happy to help debug the remaining issues with sky2, Stephen; just
let me know what information you need.
Kyle
next reply other threads:[~2007-07-26 15:28 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-26 15:16 Kyle Rose [this message]
2007-07-26 16:28 ` sk98lin for 2.6.23-rc1 Jan Engelhardt
2007-07-26 16:30 ` Kyle Rose
2007-07-26 16:41 ` Jan Engelhardt
2007-07-27 1:07 ` Kyle Rose
2007-07-26 16:57 ` Adrian Bunk
2007-07-26 22:58 ` Chris Stromsoe
2007-07-26 23:38 ` Bill Davidsen
2007-07-26 23:41 ` Jeff Garzik
2007-07-30 3:01 ` Rob Sims
2007-09-05 9:22 ` Stephen Hemminger
2007-09-05 19:42 ` James Corey
2007-09-05 21:04 ` Kyle Rose
2007-09-05 23:00 ` Stephen Hemminger
2007-09-08 17:44 ` Bill Davidsen
2007-09-08 19:11 ` Adrian Bunk
2007-09-09 2:42 ` Kyle Rose
2007-09-09 4:48 ` Willy Tarreau
2007-09-09 11:13 ` Adrian Bunk
2007-09-11 8:05 ` Stephen Hemminger
2007-09-11 11:54 ` Adrian Bunk
2007-09-11 14:29 ` Bill Davidsen
2007-09-11 15:03 ` Adrian Bunk
2007-09-11 22:37 ` Willy Tarreau
2007-09-11 22:20 ` James Corey
2007-09-09 12:54 ` Chris Stromsoe
2007-11-06 22:23 ` Stephen Hemminger
2007-11-07 1:42 ` Chris Stromsoe
2007-09-10 14:32 ` Bill Davidsen
2007-09-10 15:39 ` Adrian Bunk
2007-09-11 4:23 ` Kyle Moffett
2007-09-12 16:46 ` Torsten Kaiser
2007-07-26 19:17 ` Stephen Hemminger
2007-07-26 23:52 ` Bill Davidsen
2007-07-27 1:13 ` Kyle Rose
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46A8BAD4.8020004@akamai.com \
--to=krose@akamai.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox