Ok, so I have installed arch linux, and somehow managed to get my audigy soundcard function. To do this I had to compile a custom kernel (2.6.0-test9).
In the "make xconfig"-thing I chose support for devfs, obviously.
Now, when I log in as root, everything works real fine.
Logging in using my normal user, however, KDE gives me this error message when trying to open Konsole:
"Unable to find suitable terminal device" or something.
My current theory is that my normal user does not have access to parts of the devfs-filesystem (perhaps pty or pts?), but I have been unable to solve this sh*t.
Please help a frustrated newbie, before I mess something up playing around as root =P
My sound blaster Audigy worked fine in 2.4.2x
Just use ALSA instead of the default OSS.
"Contrary to popular belief, penguins are not the salvation of modern technology. Neither do they throw parties for the urban proletariat."
sarah31: Thanks for the tip, unfortunately it didn't work. Now I get a "bad line X in fstab" at startup, where X is the line I added. But that line, as I understand it, mounts devfs, but devfs has always mounted (my /dev-folder is not empty, and I do get sound even when logging in as normal user).
The exact error message given by Konsole is: "Unable to open a suitable terminal device".
Here's what I've tried so far:
Added something like this in my /etc/devfsd.conf:
REGISTER ^pts/.* PERMISSIONS root.users=rwxrwxrwx
REGISTER ^pts/.* PERMISSIONS root.users=0660
REGISTER * PERMISSIONS root.users=rwxrwxrwx
Added this in fstab:
none /dev/pts devfs defaults 0 0
Any advice would be greatly appreciated (please try to keep it relatively explicit though
Are you sure you are typing the line correctly in fstab? Notice nothing about devfs.
none /dev/pts devpts default 0 0
Don't forget to post your PKGBUILD in your thread when you announce a new package in incoming.
see HERE for details
devpts not devfs
I am not your friend
Oh, sorry, what I really did write in my fstab was
"none /dev/pts devpts default 0 0"
This morning it suddenly stopped working when logging in as root too! Now I'm totally confused. The root should have access to anything, right?
I guess that should really be "defaults" and not "default", but nothing works.
I enabled the "/dev/pts file system for Unix98 PTY's" option in xconfig, could this cause problems?
I've searched around, but there really don't seem to be many who has gotten the exact "Unable to open a suitable terminal device" error message, and that's really strange. I mean, my configuration, both hardware and in xconfig, should be very common, so _somebody_ out there must have gotten into the same problem I have!
i got it when i tried a 2.6 kernel on my old test box. adding the line discussed here worked for me. i know lots of people who had this problem.
I am not your friend
Question: is the kernel on the Arch Linux CD (or the one you get using pacman) compiled with support for sound/alsa?
In that case, will I just need to edit my module.conf something like this post indicates (except with snd_emu10k1.o)?
yes OSS is enabled in the kernel or you have the option to install alsa if you prefer. i am not sure if the OSS module is enabled in the stock kernel though. you can look at the config file in the abs directory or online via the cvs web interface.
I am not your friend
I also had the problem about pseudo terminals and adding the /dev/pts line worked for me as well. In the kernel I enabled in pseudo file systems both devfs and devpts.
Is it possible you didn't compile it in your kernel?
Just making a stab here--as Sarah said I too know several people who had the same problem, including myself, who fixed it by adding the devpts to /etc/fstab
Well, thank you all for bearing with me (was a little frustrated at the steep lurning curve GNU/linux has).
I'm sure I could have gotten 2.6 to work using the advice you've given me, but I think I'll just stick with the 2.4.22 kernel you get with pacman, since it should be possible to get sound working using it. I'm going to try all the good advice in the "newbie" and "kernel" section, and if I don't get it working I'll come back and ask many more stupid questions
Well, that was certainly alot easier than anticipated!
Great support people! Arch Linux has a new recruit! 8)
(BTW: the Guest above was me. Forgot to log in..)