HELLO AND WELCOME! Before you can post your question, you'll have to register -- it's completely free and registered users see less advertising! If you just want to browse through the existing questions, just select the forum that you want to visit from the selection below. Otherwise, click here to register!. We highly recommend that you print a copy of our Guide for New Members. Enjoy!

Slack 10- Marvell Gigabit LAN

Another question...
When I installed Slack 10 this morning, on a regular IDE drive (for those of you that are familiar with my SATA woes), the setup went as planned, including network setup. I used a static IP (behind a router) during the setup. However, when I logged into the system after the installation, my network would not, well... WORK (I am on Win right now). I looked at ifconfig and it showed my IP as the loopback 127.0.0.1. Now, I thought that maybe my wife's computer was running at the IP I tried to assign my Slack box, so I figured that it was just a matter of two systems not being able to have the same IP (duh), BUT when I issued 'ifconfig eth0 down', I recieved an error of 'no eth0 device'. I looked in the /dev/ directory, and there is no eth0.
My question (this is really basic and I apologize), how do I look at the system and see if my LAN was ever installed, or if I am getting some sort of odd error? Would you recommend looking at dmesg (does dmesg only log startup status...??)? Thanx.

UPDATE 1639 PST
Nevermind... it was a simple case of the NIC not being supported by Slack. Luckily, vendor has Linux drivers and an excellent installation script that requires no user intervention. All is well...