Failed to bring up eth0

If you see that when you are booting up, so do l but nevertheless everything works great for me and l have a solid connection to the net.

Wayne

I see that during boot up.

And tried to bring it up by ifup eth0, it fail as well.

No network connection at all.

I got the same error message.?? The problem was my wireless B-PCI adapter card.?? I have a Linksys WMP11 wireless adapter card that connects to a Linksys B router.?? MEPIS can not detect my wireless card in my Dell Dimension 2350.?? MEPIS was able to detect my broadband connection when plugged in??through??the ethernet port.?? My ethernet connection is built-in to the??motherboard--no ethernet card.

N??

schlu,
Did you try using the MEPIS System Center to start eth0 after configuring it for DHCP?
Jim A.
Russell, KY USA

I'm having the same problem with an eMachine.
I removed the windows partitions and installed Mepis on automatic install. It worked well except no network connection.

On boot-up:
"PCI cannot allocate resource region 3 of device 0000:00:00.0
:
Failed to bring up eth0
Failed to bring up ath0
Failed to bring up wlan0"

I did try to start eth0 from the Mepis OS Center. But it would not start. I changed the Bios Plug N Play to No, but that had no effect.

I note, the eMachine uses AMD Athlon 64 bit chip. I saw someone else mention the 64 bit chip, wondering if it's relavent.

I'm having the same problem, only in kernels 2.6.10 and later, I don't have this problem in 2.4.x kernels such as 2.4.29, also didn't have it in the 2.6.7 kernel. Can't get eth0 to start, no net access. lspci reports my network controller as:
Ethernet controller: Lite-On Communications Inc LNE100TX (rev 20)
Machine is a PII-266, Intel 440LX chipset. Encountered this since upgrade to Mepis 3.3 from Mepis 2004-4.

Same with the IBM 600e (ancient laptop). It uses a Xircom card and Mepis 2.6 just can't deal with it. Kubuntu and Kanotix work fine with it. Fortunately the Mepis 2.4 kernel compile works with this old beast.

Al C.

I have the same problem on my machine also using 3.3.1. So ended up going back to earlier version and have no problem with old version.
steve

I, too, have an eMachine, and I get that same message, but my internet works just fine.