Results 1 to 4 of 4
Hello All,
Though I consider myself "better than average" when using a Centos/Redhat box, my Slackware 12.1 skills are lackluster. I'm working to correct that with my recent install of ...
- 10-26-2008 #1Just Joined!
- Join Date
- Oct 2008
- Posts
- 2
Long story but probably easy fix I'm missing
Hello All,
Though I consider myself "better than average" when using a Centos/Redhat box, my Slackware 12.1 skills are lackluster. I'm working to correct that with my recent install of Slackware on one of my desktops. Due to some files manipulation needs, I installed Slack on box A, pulled some important files off box B to Box A, then swapped Hard Drives. The Slack boots up and I can log in, but ETH0 doesn't start. I have tried to re-Setup using the install DVD but no luck. I've tried starting it with 'ifconfig eth0 up'.
What are the steps to enable it? Where is the eth0 config files and/or how can I redo the 'autoconfig' for ETH0??
Quick NFO:
Slackware 12.1
ETH0 is part of the MoBo, so it's probably that basic driver (I can't remember, like Broadcom or something)
Thank you ALL!!
- 10-26-2008 #2
Welcome to the forums!
You can configure the network with `netconfig`
But first, what happens if you issue these commands (as root):
Any errors?Code:ifconfig -a # Does that show eth0? /etc/rc.d/rc.inetd restart /etc/rc.d/rc.inet1 restart
Can't tell an OS by it's GUI
- 10-27-2008 #3Just Joined!
- Join Date
- Oct 2008
- Posts
- 2
Thank you
ifconfig -a only shows my loopback device, no ETH#
A restart of either inetds do not show errors, but simply bring up the prompt again. No change or appearance of anything starting (or restarting)
Thank you for any further advice.
- 10-27-2008 #4And you did run that as root? Hmmm, then it seems your network cards aren't recognized. Might need a modprobe of some kind.
Originally Posted by josephd79
What's the output of:
And for good measure:Code:dmesg|grep eth[01]
Code:/sbin/lspci|grep -i ethernet
Can't tell an OS by it's GUI


Reply With Quote