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.
EDIT: It stopped working. Disregard this post. /EDIT
I got it working!!!
For those of you in the same situation try this....
The first thing I'd want to do is get my network going (if it isn't already). The netconfig utility that ran during setup, could not probe for my network adapter. However, I know that it uses the sundance module. How did I know that? Well, when I first bought those NICs, I typed D-Link 530TXS Linux (the "S" is significant in the model number) into a search engine (Google) and found the tidbit I needed in mailing list archives and the like.
Now, during setup we configured our network with the exception of the driver module for the network adapter. That means, all we have to do is load the module, and start the network. Slackware's startup scripts look for a script file named rc.netdevice in the /etc/rc.d directory. This is where the system init scripts are located on Slackware system. (It uses the BSD style init script mechanism)
It is very easy to create this file from the command line. As root, type:
This will redirect the output of the echo command into the specified text file that will get created. The quotes are important, because there is a space in the string we are echoing. Use the correct module name for your network adapter, of course.
Now, set the file executable:
chmod 755 /etc/rc.d/rc.netdevice
That's it, on the next reboot your network should initialize.
Alternatively, to load a network adapter module, you could uncomment the appropriate module loading line (or add one) in the /etc/rc.d/rc.modules init script.
Now, I don't feel like rebooting at the moment, so I'm going to just type a few simple commands to start the network.
I'm loading the module, then using the ifconfig utility to specify the interface, IP address of the machine, and subnet mask, and then using the route command to specify my router as the gateway.
You probably will want to attempt to start the XFree86 GUI now. By default, Slackware is set up to use the VESA Framebuffer driver for your display hardware. The /etc/X11/XF86Config file is a copy of the file XF86Config-vesa in the same directory.
So if you type startx you may have a usable GUI if the settings are compatible with your display hardware. That will do in a pinch, but you will want to properly configure XFree86 and use the accelerated driver for your video card (which hopefully exists, otherwise you've got some generic options)
All I did was switch his Sundance module for the 3c59x module that is compatible with my card, rebooted, and ping'd www.google.com, and now on tty1, the ping command is running... still... I can't figure out how to shut it off.....
Did it stop working after a reboot? If so, your driver module probably wasn't initialized correctly on boot. Since the sundance module worked for you, what does "modprobe sundance" give you now? After you modprobe does ifconfig show eth0?
All you need to load the proper driver for your ethernet is to enter
alias eth0 3c59x
in the file "/etc/modules.conf". After you do this, you have to enter
to activate this configuration change. Your network configurations on slackware must be in a file named "/etc/ rc.d/rc.inet1.conf", at least in slackware 9.1 which I have installed.
The rc.netdevice must be conceived for any special driver, may be wireless, as the normal ethernet cards are properly recognized by the kernel and may be treated at "/etc/modules.conf" or at /etc/rc.d/rc.modules.
I use the 3c59x module, not the sundance module, but I sort of thought that the modprobe was a temporary fix.
Anyway, thanks, you guys, I hope this is a permanent fix!
One thing.... my modules.conf file said something to the effect of "GENERATED BY ALSACONF DON'T EDIT", But I ignored that and made my changes anyway. I do not expect any drastic consequences, but should I ?
nope, modprobe is vital tool for loading drivers and modules.
Sorry, it's 6.4.26
kernel 6.4.26 wow...
was Doc right ? do time machines have flux capacitors and time circuits ?
i take it linux survived all this software patent crap. is windows still around ?
what are Nvidia GeForce12's like ?
does kernel 6.4.X support quantum CPU's ?