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.
There is less than 12 hours left to vote in the 2015 LinuxQuestions.org Members Choice Awards. Click here to go to the polls. Vote now and make sure your voice is heard!
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.
I managed to reconfigure both of the files I needed for correct keyboard layout (uk), these being xorg and rc.keymap, and I managed to get the uk keymap working in the console, but when I started up Gnome, it came up with a dialogue box which asked whether I wanted the X settings for the keymap or the Gnome ones... So I chose X and it flooded me with error messages!
Also, just in case anyone can answer this too, my PCM volume resets every time I boot up... its a pain always resetting, so how do I get it to stick?
I guess you've figured out by now that you should've picked the GNOME keyboard settings instead of X . I had this same thing happen to me but I picked GNOME no problems. You *might* want to check your keyboard settings using the Applications --> Desktop Preferences --> Keyboard applett and make sure that your keyboard is selected under the Layouts tab. Then log out of X and back in. If you get the message about picking which settings for your keyboard you know which one to pick this time . If that doesn't do the trick then you might want to head over to the Dropline Forums and post about your situation there. The folks at DLG have always been very helpful to me and they have more specific knowledge of DLG and it's innerworkings.
As far as the PCM sound thing, after you used alsamixer to set your volumes did you save them using the command:
If so, make sure you have the file rc.alsa in /etc/rc.d. If it's there, make sure it is set to execute at startup by doing:
ls -l /etc/rc.d/rc.alsa
The first part of the output (-rxw's) should look EXACTLY like this,
Originally posted by Oholiab My Gnome keyboard applet won't open
Sorry, just noticed that you are using 10.1. The "non-opening" keyboard applet is a "known bug" with Dropline Gnome 2.8.x and Slackware 10.1. It is due to the version of glibc that DLG was compiled with (Slackware 10.0), versus a newer version of glibc in in Slackware 10.1. You may want to check out some of the threads on their Forum Board to see what I'm talking about. Funny thing is I was initially hit with this "bug" but I found I had either a bad burn or a bad CD1 ISO download. I re-downloaded the CD1 ISO, re-burned it, and re-installed (formatting rather than "upgrading") and now my keyboard applet works just fine. The next version of DLG, 2.8.10, should be release in a few weeks and it will be compiled/tested on Slackware 10.1 so most of those type anomolies should be gone when it comes out. We'll have all NEW anomolies to report on .
Originally posted by Oholiab and bash can't find the command alsactl!
alsactl (alsa control) is actually part of the alsa-utils package, which is installed with Dropline Gnome (ver 1.0.8-i686-1dl), so it *should* be in /sbin. You are setting your mixer settings (alsamixer) either from a text login or from a terminal logged in as root? In order for the mixer settings to "stay put" you will need to set them as root and then use alsactl store, again as root. Reason I ask is I don't think /sbin is in the "users" path, whereas it is in "roots" path. Again, just wondering.
The PCM levels are sorted... no more resetting the volume... I'm still getting error messages because of the keyboard setup though... I'll give you details next time I boot up, but at least its not affecting anything!
So the information from each (yours and mine) are identical, except for the different keyboards and locale. That being said, are you still getting errors? If so are they keeping you from using your keyboard as you would normally use it?