Mumia W.. wrote:
On 04/19/2008 05:17 PM, Steven Jones wrote:
Mumia W.. wrote:
On 04/19/2008 05:58 AM, Steven Jones wrote:
I know this is old hat, but due to a bug in the 2.6 kernel and the
megaraid driver I can boot a 2.6 kernel....2.4 works fine, but I
have to add NIC modules for me Asus board, Realtek 8110 and a Marvel
sk98lin. The std one (sk89lin) in debian 2.4.27-4 does not work and
there isnt one I can find for the 8110.
Anyway, I think I have downloaded all the things I need to compile a
debianised kernel the kernel packager way.
I have applied the modules/patch for the asus motherboard's on-board
NIC, but what I cant find so far is how to get a 2.4.27 kernel
source to 2.4.27-4....ie there would seem to be a need to apply some
debianised kernel patches applied to the 2.4 deb source package I
downloaded? or is it already patched?
You shouldn't need the Debian patches. A Debian system will run with a
I know but I wanted a "patched" kernel, I am assuming any bugs etc
will then have been fixed.
But the kernel developers are fixing bugs too. As they add features and
fix bugs, they increment the kernel version numbers, e.g. 2.4.28,
2.4.29, ... 2.4.36.
However, I think you'll be better off getting an updated
2.4 kernel from http://www.kernel.org/ . As far as the revision number
in 2.4.27-4 is concerned, you will determine what number(s) go after the
dash. Read "man make-kpkg" to find out how to specify the version and
Yep, I have read make-kpkg.
If you're still attached to the idea of using a Debianized kernel,
you can place a Debian Sarge repository in your sources.list and
download the 2.4 kernel source from Sarge.
I have done so, still wont work, ie compile the 3rd party sources.
Each patch is designed to be used against a particular version of the
Linux kernel. You might have an incompatible group of patches. For
example, if Asus board patch is for 2.4.27, but the sk98lin patch is for
2.4.32, you have a problem because you won't be able to get both patches
into a single kernel.
yes...I have found I can compile 2.4.36 but not .27 or .30....I seem to
be in a mess....or 2.6.8, anything new like 36 has the buggy megaraid
driver so I can boot...
The patches say 2.4.20+
Another possible problem is that the patches are designed for patching
vanilla kernels, but you're trying to patch a Debian kernel. Even slight
changes can throw a patch off, so try to be sure that your patches are
designed for Debian's 2.4.27 kernel.
Ive gone to kernel org for kernels, once I get a patched and working
kernel I will try patching these....however something called main.o
fails when ever I try and compile.
Note, the binary kernels for Sarge
will probably not work for Etch because the initrd creator has been
I boot off a 2.4 kernel now...seems fine, I even went from 2.4.27-3 to
-4 and it still boots OK. Except all the NICs dont work....I just
installed an Intel PT1000 pci-e and the stock e1000 module wont detect
it...the stock sk98lin wont work either....so Im pretty buggered for
Is another module grabbing control of the network interfaces?
I suggest you ignore Sarge and get 2.4.36 from kernel.org. BTW, after
you've applied all these patches, you won't have a "Debianized"
kernel. You'll have a Jonianized kernel ;-)
didnt work as the megraid driver is fsked...
I might have to as I cant compile either of the supplied sources for
the NICs to the 2.4.27 I have.
One r1000 is a seperate module but it fails, the other sk98lin is a
patch to the kernel but menuconfig drops out when I try and go into
the 1000 sub-category and
It looks like fixing these problems will be more difficult that just
getting megaraid_mbox to work properly. What bug in megaraid_mbox are
you referring to above?
dunno, lack of booting...
"This email has been sent to you as someone requested for this address
to be subscribed to Bug#438337. This bug is currently filed against
linux-2.6." ie me....
Anyway, now I suggest you check out the 22.214.171.124 kernel from kernel.org
and see if the bug has been fixed. First look at the ChangeLogs. If a
later kernel is available, get that one instead.
Might get there yet....so far Ive not been able to build a bootable
kernel...locks up at the megaraid load, or fails to compile....
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact email@example.com