[Sussex] Debian install - Still no sound (from cdrw/dvd)
Steve Dobson
steve.dobson at krasnegar.demon.co.uk
Sat Sep 13 18:41:00 UTC 2003
Hi John
On Fri, Sep 12, 2003 at 09:31:32PM +0100, John D. wrote:
> On Friday 12 September 2003 3:36 pm, Steve Dobson wrote:
> > Try this as "root"
> >
> > # cd /dev/sound
> > # chmod 666 *
>
> OK, done
>
> > If "stuff" means the system as a whole then yes. If you mean
> > "stuff" to means "related to sound" then no - some of the devices
> > you are looking at are your disks (hda for example).
>
> From the mountain of reading that I have tried to comprehend, I understand
> that the "666" is changing something (permissions?) in the numerical way?
When you do a "ls -l" you get a lot of detail about the files meta data
(data that is held against the file but not part of the data itself - like
who owns it, the size, etc). Here is the break down.
$ ls -l /dev/dsp
lr-xr-xr-x 1 root root 9 Sep 6 23:47 /dev/dsp -> sound/dsp
^\ /\ /\ / ^ ^ ^ ^ ^ ^ ^ ^ ^
| V V V | | | +--- 8 ------+ +- 9 --+ +--- 10 --+
1 2 3 4 5 6 7
1: The file type:
-: A regualar file
l: A symbolic link to another file
c: A character special file (one of the two types of devices)
b: A character special file (the other of the two types of devices)
There are more, see "ls"'s manpage for the full list.
2: The three permission allowed to the owner or the file.
r: Read
w: Write
x: eXecute
3: The three permission allowed by non-oners of a file but in the
same group
4: The three permission allowed by every one not covered above.
5: The number of inodes that reference this file (to techie to go
into here).
6: The owner of the file
7: The group the file is in.
8: The date of last modification
9: The file name
10: If a symbolic link then where that link points.
The command "chmod" changes the three permissions flags for the
three sets of users (the owner, those in the same group, and
others [everyone else]).
The number is in base 8 (octal) and is broken down as such:
Octal Binary Description
4 100 Read permission granted
2 010 Write permission granted
1 001 Exceute permission granted
There for 666 (110110110) gives Read and Write permission to each
set of users.
After a reboot do you see the same output that I get from mine?
<snip esound [esd] installation>
> Yes, I got the accending tones
Good - the sound device drivers are loaded into the kernel and the
sound can be driven.
> > Also try installing tkmixer so you can set the volume of the sound
> > system.
> >
> > # app-get install tkmixer
>
> OK, done that - I did actually manage to get "aumix" installed, and the sound
> output level seemed OK (set at approx 80%)
>
> You mention "cdplay without arguements" and the default cdrom being the dvd
> player. So with that in mind, I presume that the arguements bit means things
> like "-t and -l" etc, and after reading the man page for cdtool and from what
> it says, have tried the following
>
> cdplay -d /dev/hdc
>
> That has given me this
>
> john at debian:~$ cdplay -d /dev/hdc
> cdplay: ioctl cdrommsf
> john at debian:~$
That works for me. The CD starts playing (I don't hear the sound out of the
laptop's speakers but from the flashing light on the CDROM drive I think that
the CD is being played. If there was a 3.5mm jack on the CD and I pluged
headphones in I'm sure I'd hear the sound. Also if I use "kscd" (a
graphical CD player) I can see stuff like the length of the CD.
> It did actually make the green light flash a couple of times before giving me
> the bash reply.
Does the green light keep flashing. If so then plug headphones in and
you should get sound.
> That's as far as I have managed to get (apart from now understanding the hda
> 1 thru 4)
>
> The part of the output of the "ls -al /dev" command that I mentioned earlier
> that has confused me is this part.
>
> lr-xr-xr-x 1 root root 30 Sep 12 20:46 hdb ->
> ide/host0/bus0/target1/lun0/cd
> lr-xr-xr-x 1 root root 30 Sep 12 20:46 hdc ->
> ide/host0/bus1/target0/lun0/cd
These are your CDROM & DVD devices
> The "hdc -> ide/host0/bus1/target0/lun0/cd" part looks like the path? that I
> had to use with mandrake to get XMMS to play anything (and as I could never
> remember that lot, I have never bothered to use XMMS under mandrake),
> nevertheless, I have tried it in the "kscd options" instead of the default
> /dev/cdrom - with the resulting "Error 11 (SIGSEGV)" and the application
> crashing (as usual).
Where does /dev/cdrom point? On my system I see this that /dev/cdrom points
at cdroms/cdrom0 (which is /dev/cdroms/cdrom0) and /dev/cdroms/cdrom0 points
at ../ide/host0/bus1/target0/lun0/cd (which is
/dev/ide/host0/bus1/target0/lun0/cd).
> p.s. thanks for the command about running dpkg --install opera etc etc - it
> didn't work. I kept getting dependency problems, which I tried to resolve
> with the apt-get facility, but was unsuccessful. The problem is to do with
> libqt3-mt which seems to be obsolete, and it wouldn't install the 3 packages
> that have replaced it. I googled for it, but only came up with the suggestion
> to try and install the "static" version instead of the shared-qt version.
> This has worked and I've got the opera back (though for reasons that I don't
> understand - when I started opera, it started up with the same preferences
> that I had before - would this be because there was still some kind of
> preferences file left in the system ???
No I get those problems too. This is because we are running testing and
opera is compiled against the old (stable) libqt3 librarys. Try installing
the static version.
--
Debian Tip of the E-Mail:
Debian Hint #19: If you're interested in building packages from source, you
should consider installing the apt-src package.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://mailman.lug.org.uk/pipermail/sussex/attachments/20030913/09eba58a/attachment.pgp
More information about the Sussex
mailing list