SlackwareThis Forum is for the discussion of Slackware Linux.
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.
1a. So, I would locate the correct driver for my drive(more than one correct?), and edit the fstab and lilo.conf for...scsi emulation? Would enabling emulation possibly eliminate the need to find a driver?
6. I'm using blackbox primarily and exiting by selecting 'exit' from the menu, but it does the same thing for kde, gnome and fvwm2.
3. Do you mean logout?? just right click on desktop and select logout............If you want to change window managers, from command line type--xwmconfig
this will bring up a menu so you can select ....KDE, Gnome, FVWM, etc......
4. open up the kde control center, select peripherals>keyboard.
there will be 3 radial buttons, titled Numlock on keyboard. select what you want and click apply.
2. Right now I boot kdm from console by "init 4". Is this the most efficient way to do this if I don't want an automatic boot into a display manager?
Just edit your /etc/inittab file so that the default is 4 and not 3.
3. Once I'm in X, how to I exit it to console instead of to display manager? Is it just a matter of "init 3" from a terminal?
If you want to get totally out of X yes. If you just want another terminal you can use ALT+F6 as it's always running in Slackware (you can use other F -keys too ).
5. What, if any, is the difference between a module and a driver.
Well a driver in Linux is any piece of code that lets the kernel
talk to a specific piece of hardware. A module is any piece of kernel
code which is loaded in after the kernel has already been compiled (it's
not built into the kernel). Often times modules are used for hardware drivers of various sorts. There are however kernel modules that provide support for
different network protocols and/or for different filesystems. --- Hope this is good enough ---
7. I have a billion questions so I'll leave it at that.
3. I would prefer to boot into a regular console and startx from there, but be able to exit my wm back to console at will. So, as I understand it, I can open a virtual terminal and 'init 3' to exit completely, or Alt F6 to a new terminal and Alt F1? back to my wm? That would be really cool.
1. So I don't want runlevel 4 as my default, but would like to know if there's any other options for running a display manager from terminal. No big deal, just curious.
5. Good to know the difference between modules and drivers. I'll put some more reading into figuring out how to install my driver. Any rules of thumb on when to recompile and when to just add a module?
4. I could use the KDE control center, but that's all I did in Mandrake and it's the reason I switched to Slack! How would I do the same thing command-line? Thanks though!
7. Seriously; I will start tons of threads if no one stops me.
I boot into console mode and to start X, I use the startx command (go figure). When I'm in X, I can hit ctrl+alt+F1 (thru F6) to change to a virtual terminal (and F1 is showing whatever warnings, errors, etc are being sent to /var/log/XFree86.0.log), then I can switch between them with just alt+F[1-6]. Then to switch back to X, hit alt+F7.
But something is seriously wrong if you can't exit your windowmanager without locking up your system. Post your .xinitrc file so maybe we can work it out.
What kind of burner do you have? Your first post said SCSI, but then you mentioned scsi-emulation which is for IDE devices. If it's SCSI, then you will need a kernel that supports SCSI, whether you use one that is pre-compiled or compile it yourself. If it's IDE, then try running the following command:
cdrecord dev=ATAPI -scanbus
If your burner shows up then you can burn without using scsi-emulation.
I assumed my burner was SCSI, turns out I shouldn't assume things like that! Problem solved, although there was a warning when I ran cdrecord -scanbus saying ATA packet interface libscg code was pre alpha and there might be fatal errors. This looks like a stock warning, to be noted, but not related specifically to me, yes?
My /etc/X11/xinit/xinitrc(I haven't set up a .xinitrc yet):
if [ -f $sysresources ]; then
xrdb -merge $sysresources
if [ -f $sysmodmap ]; then
if [ -f $userresources ]; then
xrdb -merge $userresources
if [ -f $usermodmap ]; then
# Start the window manager:
: The freeze happens with no error messages preceding it, every time I exit X, whether by "init 3" when I have kdm running, or a menu logout when using startx. There are no error messages when I Ctrl+Alt+F1` either(Thanks for the tip!)
: Another problem I had that now I think might be related is that I(perhaps unwisely) left the console screen up all night instead of shutting down or something, and this morning I had nothing on the screen at all and had to hard reboot that too! I'm thinking I have some problems. Which is ok, because I have less problems than I did before!
I checked my dmesg, too, but didn't see anything obviously wrong, but...
P.S. Now I think the freeze might not be a total freeze, because if I Ctrl+Alt+F2, during an X session, for example, I have the same problem, which is that I have a login prompt, but typing does nothing. In this case, if I Ctrl+Alt+F7 back to X, everything is normal there. What gives?
Check /var/log/XFree86.[number].log for the errors it gave, if any. I have the same problem right now because when I compiled my kernel I messed up the framebuffer settings, so that could be your problem too... dunno.
there is a utility "xf86config" that you can use to configure the keyboard from the command prompt. Or you can edit the file /etc/X11/XF86Config manually. It is pretty well commented. You can also browse the X11 website.
As for booting without anything on your screen, maybe some of the power saving features turned on (like turning off the hard disks)... I've never had that happen, so I can't help you there really.
Ok, that's interesting...
I checked my XFree86.0.log and everything seemed normal (i.e. the markers were all "information," "default" or "from /etc/X11/XF86Config" except...
(WW) Open APM failed (/dev/apm_bios) (No such device)
:which I take to mean XFree86 tried to use a power management feature I don't have in my BIOS.
-and, since you mentioned framebuffer...
(**) NV(0): Depth 24, (--) framebuffer bpp 32
:which I believe to be the correct setting for my monitor, but am not sure.
8. How do I stop XFree86 from using power management?
9. Do I need a framebuffer? Is the penguin logo the main feature at this point? And if I don't need it, can I get rid of it without recompiling the kernel? I might be recompliling at this point anyway since I realized I don't need SCSI support(brilliant!).
In lilo you can choose your vga setting. I believe vga = normal is the one that doesn't use the framebuffer - it runs at a much lower res, but works. I think the only advantages are higher res and a penguin logo (i hear you can change that, too).
I know that in the 2.6 kernels, power management is an optional install. No clue where to set that, though KDE has a few things of its own about power management in the control center. The thing is, if you just disable power saving features in the kernel without changing your software configs, you could get some errors when it tries to run them. All guessing on my part.