antidrugue

Then use
instead.

And disable the buggy one

__________________
"To express yourself in freedom, you must die to everything of yesterday. From the 'old', you derive security; from the 'new', you gain the flow."

-Bruce Lee

dravenloft

/Hangs head in shame/ You mean there're two 8139 drivers? Methinks at some point there should be a kernel config tool that organises things in less of a list... I apparently had skipped over this interesting bit of detail.

dravenloft

Hurray!! Kernel compiled.

bad thing... it doesn't boot:
ok
1) this happens no matter what device I select. hda, hde, LABEL=/ whatever. It also doesn't matter if rootfs is on (hd0,0) or (hd1,0) to GRUB.

2) I don't have the slightest idea where to fix this. I don't know if it has to do with a make-kpkg option, or if it's something I did in my .config (or maybe didn't do).

What I do know is that this is a real bummer.

dravenloft

Ok. This thread is pretty well done for me.

Turns out that that experimental 8139c driver needs to be off, and the same for an experimental tulip driver. You also have to, for some reason, use make-kpkg --initrd (something I'd already learned the hard way more than once... you'd think I'd remember eventually).

ikkem

this worked great for me I finally got the kernel to compile thank you verry much.....
but now iptables does not start I can't start shorewall anymore
I was planning to upgrade to etch but I will do that when I have succes in compiling the kernel with iptables capability

thanks in advance....