I am having a very annoying problem. My network connection only lasts a few minutes, and then it justs stops. I realize I may not be looking in the right places for the answer, so I would be glad to follow any suggestions or provide any additional info anyone might want.
I recently did a major upgrade on a lot of my hardware. I bought a new NForce 3 motherboards and a Athlon 64 3000+ cpu. I kept most everything else except for the ram. Since this is a NForce 3 board, and I didn't feel like patching the 2.4 kernels, I am running the 2.6 series. This same problem has come up in 2.6.1 and 2.6.2.
Neither of my onboard NICs are supported by a kernel module, so I have loaded in a PCI ethernet card. The first one was a netgear that needed the natsemi module. I added natsemi to my rc.conf and have dhcp enabled. It all boots up fine and connects just fine too. After a few minutes, the connection stops though. I threw in a realtek 8139 PCI card which uses a different module and I got the same results. I am sure the PCI cards are fine, they have been tested in another computer, and under windows in the same PC that linux won't work on.
I haven't been able to sync pacman for awhile because my connection keeps dying in the middle of downloading.
Does anyone have any suggestions? Are there any particular logs I should look at?
What happens if you use a static IP instead of DHCP ?
Good question, I shall try to find out.
Well, I have eliminated faulty hardware as the cause. Also, I've run other linux distros on the same computer and they've worked just fine. So now it's down to one of the packages I'm using in Arch or the way one of them is configured.
The most annoying part is that I can't update my system because the connection keeps dying before pacman -Syu can finish.
Thanks for the help.
Missing arch bunches!
Well, from here on it's pretty much guessing. Turning off ACPI is always worth a try - as a kernel parameter and/or in the BIOS.
Also, turning off as much as possible in the BIOS that is not needed (especially the stuff coming from the NForce3 chipset).
As I said - just guessing ;-)
before and after stop of working?
any info from
(errors about interupts or so?)
The impossible missions are the only ones which succeed.
Well, what do you know? The noapic option seems to have fixed it. Seems like that apci crap is good for all of nothing. Now I'm spending some time trying to get everything else back up and going. I've let the system go to shit in the last month.
Is there anyway, short of not compiling apci support into the kernel, that I can make it boot with noapic everytime? I'm still running lilo since grub is giving me fits. Can I squeeze it in lilo.conf anywhere?
Thank you very much for all your help.
You can manage acpi at boot-time with append in lilo.conf...
append = "acpi=off"
Should do it.
apic and acpi are two different things. ACPI is a power management system. APIC is something usually used for SMP systems, but added to some single cpu machines (can't tell you exactly what it does). The default kernel has it enabled, and doing an append line (or adding to an existing) should fix it.
Don't make it acpi=off though; acpi isn't your problem. Make it exactly the thing you typed in when you first booted (noapic).
I just wanted to make sure that you knew the difference between acpi and apic.
I have discovered that all of mans unhappiness derives from only one source, not being able to sit quietly in a room
- Blaise Pascal
Advanced Programmable Interrupt Controller....
Like sounds good....but no idea what it does (SMP)
sorry must not confuse issue.....
Sorry - I misread the earlier post. First it's apic, then apci...my eyes are getting blurry.
Yea, I just assumed apci and apic were the same thing. Kinda like center and centre, just some bloke with another language programing it.
Well actually, I need to make sure it was apic that was giving me fits. I actually upgraded my kernel too, and I noticed 2.6.3 had many fixes for network modules.
Thanks for the ammend line, lilo's man page is way too convoluted, and lilo.conf's man page is way too simplistic. Do you really think the same person wrote both?