• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Some problems going to Linux 2.4.17 with Debian

MGMorden

Diamond Member
I've recently installed Debian Woody on my Linux system to try it out. I'm liking it alright so far, but I can't get a custom Kernel working. Default install ships with 2.2.20. I've used apt-get to download and install 2.4.17 optimized for an Athlon which works fine, but if I compile 2.4.17 on my own (to get my own choices in like the preemptible process scheduling patch) then networking stops working. The NIC is still picked up fine and it seems to configure correctly with the DHCP server, but whenver I try to access the internet the hostname lookup fails. Any ideas?

Any help would be greatly appreciated.
 
you sure you have the driver for the nic selected in kernel config?

edit: here's what i have selected in "networking options"

<*> Packet socket
<*> Unix domain sockets
[*] TCP/IP networking
[*] IP: multicasting

thats it...other than that i just have my network card's driver selected in "network device support"
 
I've got those same options selected and am compiling in support for my NIC via a module (NIC is being detected fine AFAIK. shows proper IRQ and everything).
 
damn...so you modprobe/insmod the module and it loads up fine but then networking still doesnt work....hrmm...ok i think my n00bie-ness is taking over...i can help you no further 🙁

good luck though
 
It's definately something with the kernel binary. I symlinked the "good" module directory to the one I was having problems with and rebooted. Came up apparently fine again but still failed hostname lookup. Symlinked the custom compile directory to the "good" one, try to boot with "good" kernel and I get an infinite loop at bootup 🙁.
 
Did you make sure you have atleast the woody versions of the kernel utils like modutils? There's info in one of the kernel docs as to which packages need to be updated for 2.4 kernels.
 


<< Did you make sure you have atleast the woody versions of the kernel utils like modutils? There's info in one of the kernel docs as to which packages need to be updated for 2.4 kernels. >>



I didnt update anything other than the kernel on my system and I never had any problems with it. Im probably lucky though 😛
 


<<

<< Did you make sure you have atleast the woody versions of the kernel utils like modutils? There's info in one of the kernel docs as to which packages need to be updated for 2.4 kernels. >>



I didnt update anything other than the kernel on my system and I never had any problems with it. Im probably lucky though 😛
>>


same here 😕
 


<<

<<

<< Did you make sure you have atleast the woody versions of the kernel utils like modutils? There's info in one of the kernel docs as to which packages need to be updated for 2.4 kernels. >>



I didnt update anything other than the kernel on my system and I never had any problems with it. Im probably lucky though 😛
>>


same here 😕
>>



Now Im trying to decide between reinstalling with woody + XFS or just updating everything. ext2fs worries me, but Im lazy...
 


<<

<<

<<

<< Did you make sure you have atleast the woody versions of the kernel utils like modutils? There's info in one of the kernel docs as to which packages need to be updated for 2.4 kernels. >>



I didnt update anything other than the kernel on my system and I never had any problems with it. Im probably lucky though 😛
>>


same here 😕
>>



Now Im trying to decide between reinstalling with woody + XFS or just updating everything. ext2fs worries me, but Im lazy...
>>


i'm lazy too, so i use ext3 =)
 
It depends on what you use, things like modutils and pppd need updated to work, if you build a completlely monolithic kernel and don't dialup you won't notice =) There are other things, but I can't think of them off hand.
 


<< It depends on what you use, things like modutils and pppd need updated to work, if you build a completlely monolithic kernel and don't dialup you won't notice =) There are other things, but I can't think of them off hand. >>



dsl for connection, and I think I built the ethernet driver into the kernel... I know I used a module at some point for that, but I think it was right after installation to get it up and running...
 
Card is a Realtek 8139. I've given up for now (throwing Slackare back on it at least for a while. I'm doing a project for class that needs a server so Slackware will be the easiet thing to setup for me).
 
Back
Top