[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Two Lenny problems

On Sun, 21 Feb 2010 23:06:16 -0500 (EST), Cecil Knutson wrote:
> No, I have never searched for anything in a web page.  Didn't know it  
> could be done, didn't look for it.

Amazing.  OK, my apologies.  I will try to make fewer assumptions.

> Opera does the same, did it, found it,  
> read it, opened a terminal, SU'd, cd'd to /etc/modprobe.d, saw  
> "blacklist", double-clicked it ...

Double clicked it?  In a terminal window?  Are you sure you were
in a terminal window?

> and opened it with Kword, modified the file  
> by adding "blacklist snd_intel8x0, file failed to save.  So, now what?

You say you "su"d.  By that I assume that you entered "su" as a command
with no operands, then responded to the password prompt by entering
the password for root.  You then should have seen a shell prompt which
ends with the pound sign (#) instead of the dollar sign ($).  If you
"su"d to any user other than root, or if you entered the wrong password,
it didn't work.  If you did not see a shell prompt ending with # instead
of $, then it didn't work as you expected.  I'm not familiar
with Kword, but it appears to be a word processor for the KDE
desktop environment.  I don't recommend that you use a word processor
of any sort.  I earlier recommended gedit, which is a graphical text
editor for the GNOME desktop environment.  I thought that's what you
were running.  I didn't realize you were using KDE.

Long term, I recommend that you learn to use vi, which is considered
the "standard" full-screen text editor on Unix and Unix-like systems.
The second most popular text editor is GNU emacs.  Most Linux text editors
are extensions of, or takeoffs from, one of these two basic editors.
But for now, I'd like to keep things as simple as possible.  I'd like
to avoid too many simultaneous learning curves.  Let's try nano.
It is a very simple WYSIWYG (What You See Is What You Get) full-screen
text editor that comes standard with Debian systems.  Finally, I don't
recommend that you edit /etc/modprobe.d/blacklist.  That file belongs
to a package (udev, to be precise) and might possibly be replaced
in a future security update to udev, wiping out your changes.  I
suggest that you create a new file called /etc/modprobe.d/local.
That is how my web page recommends that it be done.  (You don't seem
to read very carefully.  You have asked that I be patient, but I ask
the same thing of you.  Don't stop reading too soon.  Make sure you
understand the procedure before trying something.)

For illustrative purposes, I will assume that your ordinary,
non-root userid is "cecil" and that your hostname is "debian1".
I will show the console log complete with standard shell prompts.
Everything up to and including the $ (or #) and the trailing
blank is typed by the shell.  Don't try to type that.  Everything
after the "$ " or the "# " is what you type.


cecil@debian1:~$ cd /etc/modprobe.d
cecil@debian1:/etc/modprobe.d$ su
Password: [enter the root password here]
debian1:/etc/modprobe.d# nano local
. (editing session)
debian1:/etc/modprobe.d# exit
cecil@debian1:/etc/modprobe.d$ exit


Notice that the shell prompt changes from ending with a $ (used
for non-root users) to ending with a # (used for root only) upon
the successful switch to the root user.  It switches back to a $
upon the first "exit" command.  (The second "exit" command terminates
the terminal window.)

During the editing session you will add a single line to the file
which contains


blacklist snd_intel8x0


save it, then exit the editor.  Then, shutdown and reboot.
Upon reboot, run alsamixer and see if you see different results
than before.

Reply to: