Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
help! I am new to linux and have recently installed red-hat 6.1 on my old pc (pentium 200mhx) and its great, but my ethernet card is not recognised by the install.
it is a d-link 'DFE-530TX'. I tried to configure it myself specifying the 'via-rhine' interface in Client Task -> Basic Host Information along with an IP address of 10.10.10.2 and subnet of 255.0.0.0, but when I reboot a message flashes up that says 'delaying eth0 initiation [FAILED]'.
when i tried doing it via a shell i got a message saying the device is busy (despite issuing a 'network stop' command). I tried unplugging the cable ;-) but that didnt work
The kernel is old also 2.2.12-20. forgive ignorance dont know if that is relevant
can anyone help? / tell me what to do (in lamens terms!)
Be very sure which NIC you have. D-Link should burn in hell for naming two completetly different cards with such disceptively close names (ok, maybe hell is a little stringent but they should definitely be sent to their rooms without their dinner).
The D-Link DFE-530TX board uses VIA Rhine (VT86C100A and 3043) driver.
The D-Link DE-530TX board uses the Tulip driver.
tried all that but without avail, eth0 is aliased to UNKNOWN
I have downloaded and compiled the via-diagnostics utility from the website mentioned earlier in the thread and the output is this:
[root@localhost netdrv]# ls
instr.txt pci-scan.c pci-scan.o via-diag via-rhine.c
kern_compat.h pci-scan.h usingl~1.htm via-diag.c via-rhine.o
[root@localhost netdrv]# ./via-diag
via-diag.c:v2.08 12/17/2002 Donald Becker (email@example.com) http://www.scyld.com/diag/index.html
Index #1: Found a VIA VT6102 Rhine-II (type 3065) adapter at 0xd800.
Station address 00:50:ba:fb:28:de.
Tx disabled, Rx disabled, half-duplex (0x0804).
Receive mode is 0x00: Unknown/invalid.
Transmit mode is 0x00: Normal transmit, 128 byte threshold.
No interrupt sources are pending (0000).
Use '-a' or '-aa' to show device registers,
'-e' to show EEPROM contents, -ee for parsed contents,
or '-m' or '-mm' to show MII management registers.
[root@localhost netdrv]# insmod via-rhine
./via-rhine.o: unresolved symbol pci_drv_unregister
./via-rhine.o: unresolved symbol pci_drv_register
[root@localhost netdrv]# [root@localhost netdrv]# ls
I just reviewed you post and didn't notice if you disabled plug -n - play in the bios. you generally get an opportunity to change bios settings when you boot (F2 seems to be the favorite for this feature but it could list others). If you haven't, try it and then insmod.