You are not logged in.
First some info: I'm using a Biostar M7VIG Pro (via-rhine NIC) motherboard with a Duron CPU.
When starting the network 'dhcp' is 'busy' until it times out. What makes this strange is I ready intalled Rehat on the same system without any problems!
I also tried using 'dhclient' but it times out too...
Any ideas?
Offline
did you configure your eth0 and network settings in /etc/rc.conf correctly?
AKA uknowme
I am not your friend
Offline
No, my settings are correct; that's not the problem!
I just re-build the kernel (stable 2.4.22) with the '.config' from Redhat and the network starts fine now! I'm comparing the two ArchLinux/Redhat configure files now to see what settings are different. Hope to post the results soon...
Offline
did you have a line
alias eth0 via-rhine
in your /etc/modules.conf ?
Offline
I have the modules.conf configured right. The network work great with the re-built kernel!
I just finished two more test builds of the kernel & have it narrowed down to just a few different .config settings. I'm using a divide & conquer approach…
Offline
I think I found the problem. The ArchLinux kernel is built with 'CONFIG_SMP=y" when I build the kernel with '#CONFIG_SMP is not set' the network starts up like it should! With 99.99% plus of all machines with only 1 CPU, why is the kernel built for multi-CPU(s)????
Offline
in one word...monolithic. our kernel has most of the most common selections built in or as modules. in most cases smp should not cause issues, but in rare cases it may. that is what the ABS system is for.
as for moduloe loading...if you are loading the network module in rc.conf then there is no need to have it set in modules.conf. in fact there is no need to use modules.conf at all in arch.
AKA uknowme
I am not your friend
Offline
Actually for better/faster testing I was manually (/etc/rc.d/network start) starting the network. The configuration is NOT the problem, I did a couple more test and it is the '#CONFIG_SMP=y' option built into the kernel causing the problem! I also found that if you pass the 'NOAPIC' parameter to the stock ArchLinux kernel (via grub) that the network will also start fine. It make me think it's a interrupt related issue…
It's always easier added (building) to a working system then trying to debug a non-working system. I think the initial installed kernel should be changed to one that is safest (least problematic features) for most systems. How about making a separate SMP-Kernel like you do for SCSI?
Tempus Fugit,
Czar
Offline
I have an asus board at home with the via-rhine and that worked out of the box (well ... after modprobing via-rhine that is). So this isn't a via-rhine wide problem ... I guess
apt-get install arch
Offline
I have an asus board at home with the via-rhine and that worked out of the box (well ... after modprobing via-rhine that is). So this isn't a via-rhine wide problem ... I guess
Mine is a via-rhine that works out the box as well, works perfectly with the old kernel 2.4.21-2 and the 2.4.22. So it must be some nasty very little known bug, I would suggest googling it to see if it has been fixed, and if not, maybe submit it to some kernel higher uppers.
Kritoke
http://counter.li.org/ Registered Linux User #318963 kritoke@jabber.org
Offline