You are not logged in.
Oh yeah, networkmanager works wonders. No need to mess with network and dhcpcd.
It detects all the wireless networks and everything.
joe@trusktr.io - joe at true skater dot io.
Offline
Oh no! I've encountered the exact same problem again! This time i know for fact the "network" group issue is not related.
I've started from scratch on a third computer, a desktop. I've followed the exact directions in the wiki as I have done before.
Here's exactly what i've done so far:
I've set up rc.conf so it contains:
etho="dhcp"
INTERFACEs=(eth0)
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
Turned off computer, plugged cable in, booted, then network [FAIL]s to start at boot.
Added root to "network" group: network:x:90:root
Rebooted, network still fails.
Tried dhcpcd eth0 but that returns "dhcpcd: timed out" after "waiting for carrier" and trying "/etc/rc.d/network restart" gives [FAIL]
Then i increased timeout limit in /etc/conf.d/dhcpcd to 60, but "/etc/rc.d/network restart" still gives [FAIL].
And now I am here. So I was wrong about it working if root is added to the "network" group. It's just not working. I have no idea what to do or why it's not working. I have no idea what I did previously on my laptop to get it to work! So strange.
Last edited by trusktr (2010-07-01 03:40:16)
joe@trusktr.io - joe at true skater dot io.
Offline
Is that a copy & paste from your rc.conf? If so, you might want to change etho to eth0
Offline
Can you post your DAEMONS array (the last line in your rc.conf)?
Offline
oh hehe, no i typed that out. it is eth0.
Hey Karol, here's my daemons (default ones with a new arch install):
DAEMONS=(syslog-ng network netfs crond)
joe@trusktr.io - joe at true skater dot io.
Offline
Try putting dbus or hal (if you're using hal)
DAEMONS=(syslog-ng hal network netfs crond)
Are you dualbooting on any of your computers?
What is your network setup beyond your computers: you link them with ethernet cables to a router and your router is connected to your ISP's line, is that right?
Last edited by karol (2010-07-05 14:47:05)
Offline
Yeah that's exatly right, to a router then the internet.
I don't think hal comes with ArchLinux by default, it comes with gnome. But i'm not connected yet so there's no way to get it!
joe@trusktr.io - joe at true skater dot io.
Offline
Did you try dhclient as hokasch suggested?
Are you dualbooting with Windows?
Offline
I can't try dhclient because i have no connection to download it with hehe.
I'm not dualbooting, just Arch Linux with one hard drive.
I'mma have a go at it tomorrow and see what happens.
joe@trusktr.io - joe at true skater dot io.
Offline
Use the machine you are using to access the forums to download it.
aur S & M :: forum rules :: Community Ethos
Resources for Women, POC, LGBT*, and allies
Offline
I had a similar problem.
Check here http://bbs.archlinux.org/viewtopic.php?id=99797
or here http://bbs.archlinux.org/viewtopic.php?id=86260
2nd link solved my problem.
Offline
hey fsckd, i could certainly download it and inject it into the system, but i want to be able to accomplish this without the help of any external machines as if it was my only computer, just to make sure Arch can truly be started standalone.
Hey kylepotts, i tried it but that only appears to work with wireless cards. I'm simply trying to connect my LAN (wired) connection but it just doesn't want to.
joe@trusktr.io - joe at true skater dot io.
Offline
Hey, just in case, i have the rt2561/rt61 chipset for ethernet.
joe@trusktr.io - joe at true skater dot io.
Offline
OK, i got it to work:
All I did was exactly this:
i commented out the line
eth0="dhcp"
in rc.conf and replaced it with:
eth0="eth0 192.168.0.6 netmask 255.255.255.0 broadcast 192.168.0.255"
Then i restarted the network with "/etc/rc.d/network restart" and it started working and "ping google.com" returned positive results.
Then immediately after that i returned to using the line
eth0="dhcp"
in rc.conf and now the network works just fine!!
This leads me to believe that perhaps dhcp was assigning a conflicting ip address to my device that was matching that of another computer or something.
I have no idea for sure what the problem really was though. At least it works now!
joe@trusktr.io - joe at true skater dot io.
Offline
all that is very weird indeed. please add solved to the threads title, as it magically solved itself in the end.
Offline
I ran into this bug again installing Arch on my 7th machine! It seems to be random. A random mixture of restarting my cable box, restarting my router, and restarting /etc/rc.d/network seems to get everything totally by chance. All in all it doesn't seem to be Arch related, but rather my cable box/router getting mixed up or something. I still don't know exactly what it is though.
My 3rd and 4th machines had this problem, but my 5th and 6th Arch installs worked perfectly, and then just now my 7th machine had the problem again.
joe@trusktr.io - joe at true skater dot io.
Offline
This seems to work:
1. Restart the cable box and network router box.
2. Restart /etc/rc.d/network with this command: ...$ /etc/rc.d/network restart
3. Lastly, refresh the eth0 interface with this command: ...$ dhcpcd -k eth0; dhcpcd eth0
And that should be it. That last command seems to remove any faulty setting with the interface and remakes them for the refreshed network.
joe@trusktr.io - joe at true skater dot io.
Offline