You are not logged in.
Pages: 1
Hi all!
After an Archlinux basic installation i can't get the nforce2-network (Asus A7N8X-X) working. I tried loading the forcedeth module and installing the nvidia-drivers. But nothing worked.
Has someone a suggestion or a link to some nforce2-howtos?
THX
And sorry for my bad English.
I'm Newbie.
Sorry for my bad English.
Offline
please post your
rc.conf modules section and network config
modprobe.conf
it is hard to guess what went wrong
you tried hwd to get the right module for your network card?
Offline
which kernel are you running? with 2.6 it is really easy to get network support going, probably easier that with 2.4. something to keep in mind, though, is that the nvidia supplied drivers will not work with kernel 2.6.
for kernel 2.6 all you need to get your network running is adding forcedeth to the modules section of /etc/rc.conf then ensuring that your ip address is correct. if you have a router with dhcp enabled, it is really easy, but you will need to know something about networking if you don't.
Offline
hwd (nice thing) said I should load the forcedeth module, so I wrote this in my rc.conf. The strange thing about that is that twice the "network start" worked, but mostly failed. Don't know whats going wrong.
I'm using kernel 2.6 and I have a router with dhcp.
Here ist my rc.conf:
#
# /etc/rc.conf - Main Configuration for Arch Linux
#
#
# Localization
#
# HARDWARECLOCK: set to "UTC" or "localtime"
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: fount in /usr/share/kbd/consolefonts (only needed for non-us)
# USECOLOR: use ANSI color sequences in startup messages
#
HARDWARECLOCK="localtime"
TIMEZONE=Europe/Berlin
KEYMAP=de-latin1
CONSOLEFONT=
USECOLOR="yes"
#
# Networking
#
HOSTNAME="myhost"
#
# Module to load at boot-up (in this order)
# (prefix a module with a ! to disable it)
#
MODULES=(nvidia forcedeth snd-intel8x0 !usbserial !ide-scsi)
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# (prefix an interface in INTERFACES with a ! to disable it)
#
# Note: to use DHCP, set your interface to be "dhcp" (eth0="dhcp")
#
lo="lo 127.0.0.1"
eth0="dhcp"
INTERFACES=(lo eth0)
#
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# (prefix a route in ROUTES with a ! to disable it)
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
#
# Daemons to start at boot-up (in this order)
# (prefix a daemon with a ! to disable it)
#
DAEMONS=(syslogd klogd !pcmcia network netfs crond)
# End of file
Sorry for my bad English.
Offline
Perhaps you should try removing the ( !) from ROUTES: (!gateway) in rc.conf.
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
Perhaps you should try removing the ( !) from ROUTES: (!gateway) in rc.conf.
I've tried this, but it's the same problem.
Sorry for my bad English.
Offline
if your nic is dead there is no need for trying.
you could disable it in bios and plug in another and run it as eth0
arch + gentoo + initng + python = enlisy
Offline
I can't say it is dead, it works fine with XP.
Sorry for my bad English.
Offline
you tried this
enter this to modprobe.conf
alias eth0 forecdeth
and remove it from rc.conf's module list
Offline
if you run
ifconfig
and the card is not showing up, it's not working.
if it's working you can go on and configure your network conf.
arch + gentoo + initng + python = enlisy
Offline
I have a Shuttle NF2 board that I'm using w/ Arch & using the onboard NIC w/ NP. When I 1st finished the Arch install & logged in I simply ran "modprobe forcedeth" & then "dhcpcd eth0" & voila I had network access for pacman. Next I edited modprobe.conf the way tpowa suggests. Here's the lines from my rc.conf:
# Module to load at boot-up (in this order)
# (prefix a module with a ! to disable it)
#
MODULES=(eth0 !usbserial !ide-scsi snd-cs46xx snd-pcm-oss)
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# (prefix an interface in INTERFACES with a ! to disable it)
#
# Note: to use DHCP, set your interface to be "dhcp" (eth0="dhcp")
#
lo="lo 127.0.0.1"
eth0="dhcp"
INTERFACES=(lo eth0)
#
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# (prefix a route in ROUTES with a ! to disable it)
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
#
# Daemons to start at boot-up (in this order)
# (prefix a daemon with a ! to disable it)
#
DAEMONS=(syslogd klogd hotplug !pcmcia network netfs alsamixer gdm)
Offline
i think you don't need to load eth0 in modules list
it's loaded automatically with the network
by the way
i added the nvidia nforce drivers to staging a while ago
pacman -S nforce
perhaps some of you want to try it
enjoy
Offline
i think you don't need to load eth0 in modules list
it's loaded automatically with the networkby the way
i added the nvidia nforce drivers to staging a while ago
pacman -S nforce
perhaps some of you want to try it
enjoy
You are correct, sir...removed the eth0 from modules list & networking still work fine. TYVM for the suggestion. I'm scared to try the NF2 drivers, as I've read they don't work. I have everything pretty well lined out now...don't wanna mess it up. From what I've gathered the only driver that works for nforce2 onboard lan is the reverse engineered nvidia module (forcedeth0)...I'm far from a linux expert so feel free to correct me if I'm wrong, but I'm sure I've seen some try the NF2 drivers w/ no success in getting the onboard lan up & running.
Offline
i think you can safely try the new nforce drivers
it builds two modules
if they don't work go back to the old config and all is fine
but if evrything works now you don't need any other drivers :-)
it was just a thought because i can't test the package because i have no nforce chipset based board
Offline
i think you can safely try the new nforce drivers
it builds two modules
if they don't work go back to the old config and all is fine
but if evrything works now you don't need any other drivers :-)it was just a thought because i can't test the package because i have no nforce chipset based board
k...I'll give 'em a go afterwhile....I'd do right now, but have a carpenter on the way to do some house repairs & I must get everything in order. I'll report bak on how they work.
Offline
Pages: 1