Compiling 2.6.7 Kernel

subaruwrx · 06-30-2004, 11:29 PM

Quote:

Originally posted by keefaz
permission is for read, write, execute a file then ownership let the system decide which user/group has the right to do the previous action (read, write, execute).

So for example if (as root) you did chmod -x /bin/bash (do no try it lol), all users, ever root himself won't be abble to execute bash (wich would be annoying).

First is permissions, second is ownerchip, if you tweak permissions to /dev devices, ever root won't be abble to access devices.

As I said try to add your user to audio and video groups in /etc/group
then chown root:audio /dev/mixer* (change group for all mixer files)
chown root:audio /dev/dsp*
chown root:audio /dev/sequencer*
chown root:audio /dev/audio*

and for video :
chown root:video /dev/fb*
chown root:video /dev/vbi*
chown root:video /dev/video*
chown root:video /dev/vtx*

The part in /etc/group should be like :
audio:x:17:YourUser
video:x:18:YourUser

if video and audio groups do not exist add them by :
# groupadd -g 17 audio
# groupadd -g 18 video

What if I want it to be availble to root also?

bonecrusher · 06-30-2004, 11:54 PM

Quote:

Originally posted by subaruwrx
What if I want it to be availble to root also?

root owns the house, brother
just make root the owner

subaruwrx · 07-01-2004, 12:00 AM

Quote:

Originally posted by bonecrusher
root owns the house, brother
just make root the owner

By default root is already the owner.

What seems to be the problem, bro?

bonecrusher · 07-01-2004, 07:47 AM

Quote:

Originally posted by subaruwrx
By default root is already the owner.
What seems to be the problem, bro?

That was my question to you ?

I didn't mean to seem rude if that is what you thought. As far as I know if root owns something you can access it if your root... Maybe I misunderstood your question? Your quote you had above is correct but a little misleading. He is saying that root can't even access something if root doesn't own it ... yet he has root owning everything.
I think he was getting at the fact that you would be able to access these devices even if your not root. If that is the case then you will have to add the groups mentioned to those users in question. (As he shows...) But if you just wanna access them as root, you shouldn't have a problem there, either...
And as someone already might have mentioned, I seriously doubt that file permission/ownership is the reason why you can't access your sound. If you are root, and can't get to them to do anything, look elsewhere for the problem. I think someone mentioned that your drivers probably weren't loaded. You probably just need to recompile your kernel again and just make sure that this time you go in to sound under devices and under alsa and make EVERYTHING a MODULE. Then recompile all. Then your system should find the correct modules for your sound... hope this helps ya somewhat. I have you compiling them all as modules because obviously the ones your using now arent right. This should cover all bases. Make sure you also enable hotplugging, too. When you get all this done, run alsaconfig again. It should find them this time.

-bc

r_jensen11 · 07-01-2004, 09:32 AM

Wouldn't you have it chmodded either 5 or 7 for the first variable?

bonecrusher · 07-01-2004, 10:05 AM

Quote:

Originally posted by r_jensen11
Wouldn't you have it chmodded either 5 or 7 for the first variable?

That depends on the device. Like I said I would keep as much space between device permissions and yourself as possible.. don't mess with 'em. If you want to access some device and it says you have to be root, then you can change groups on the device, ( keefaz has already given a good method of doing this.) But I would seriously think long and hard about changing permissions...

chmod 755,555,544 etc all give execute privledges to the file. But your devices should be installed in such a way that they should be fine as is.

4=read
2=write
1=execute
add them up for *7*

777 would be rwx(read/write/execute) on all levels.
444 would be just read priv for all levels.
555 would be read and execute all permission levels.
etc etc etc

BUT BE CAREFUL MESSING WITH DEVICE PERMISSIONS... I WARNED YA!

-bc

bonecrusher · 07-01-2004, 10:19 AM

Quote:

Originally posted by r_jensen11
Hmm, if lspci sees the sound card, I'm thinking maybe you just don't have the drivers for the card installed? Are they modules that you built them as? If they are, are they loaded?

Subaru:

do this command be4 you go recompiling as I mentioned above:

Code:

/root# lsmod

and post the results here...
'lsmod' will tell us if you have your sound modules loaded...

-bc

subaruwrx · 07-01-2004, 11:05 AM

Below is the result from lsmod. I also find it strange cause previously before I upgrade to Kernel 2.6.7, I did a lsmod and saw some extra info under "Used by". Now after upgrading, it became this.

Immediately after upgraded to Kernel 2.6.7, I had problems with my MS USB Intellimouse Optical and my network card. But managed to solve them, now left this sound problem unsolved.

Code:

Module Size Used by
ppp_synctty 6724 -
ppp_async 9156 -
ppp_generic 18768 -
slhc 6020 -
appletalk 28332 -
ipx 22568 -
p8022 1348 -
psnap 2408 -
llc 5048 -
soundcore 6240 -
apm 14480 -
ipv6 207808 -
usbmouse 3812 -
usbhid 29184 -
ohci_hcd 17956 -
ehci_hcd 24772 -
usbcore 92212 -
ds 12932 -
pcmcia_core 45892 -
ide_scsi 12904 -
agpgart 26472 -

Below is me modules.conf

Code:

# --- BEGIN: Generated by ALSACONF, do not edit. ---
# --- ALSACONF verion 0.9.0 ---
alias char-major-116 snd
alias snd-card-0 snd-emu10k1
alias char-major-14 soundcore
alias sound-slot-0 snd-card-0
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss
options snd major=116 cards_limit=1
options snd-emu10k1 index=0
# --- END: Generated by ALSACONF, do not edit. ---

alias char-major-195 nvidia

subaruwrx · 07-05-2004, 02:09 AM

Tuttle · 07-05-2004, 07:24 AM

q. can you still boot into your old 2.4 kernel? if not, you could re-install the packages and re run lilo in order to see which modules are loaded and what the name of each module is. Now you are familiar with the process of fiddling with a new kernel it doesn't matter if you break anything and this is the best way to find out all the module names relevant to a good working system.
I cannot see a soundcard there, snd-emu10k1 should at least be there since that is what alsaconf has previousley detected.

subaruwrx · 07-05-2004, 09:17 AM

Quote:

Originally posted by Tuttle
q. can you still boot into your old 2.4 kernel? if not, you could re-install the packages and re run lilo in order to see which modules are loaded and what the name of each module is. Now you are familiar with the process of fiddling with a new kernel it doesn't matter if you break anything and this is the best way to find out all the module names relevant to a good working system.
I cannot see a soundcard there, snd-emu10k1 should at least be there since that is what alsaconf has previousley detected.

I can't boot into my old 2.4 kernel anymore.

Anyway, what does this line do in modules.conf?

options snd-emu10k1 index=0

Tuttle · 07-05-2004, 09:33 AM

It won't do anything if the soundcard isn't loaded! Seriously, you can set your system up to boot 2.6 and 2.4 kernel so that you can reboot and switch between the two to help troubleshoot your missing modules. The module you are looking for is snd_emu10k1 which can be found in:
device drivers -> sound -> advanced linux sound architecture -> pci devices.
I would advise you say no to oss and setup the alsa modules, you can set it as a m or y, you can set all these as modules if you like.

edit: sorry, lost the screeny!

r_jensen11 · 07-05-2004, 12:35 PM

Quote:

Originally posted by Tuttle
q. can you still boot into your old 2.4 kernel? if not, you could re-install the packages and re run lilo in order to see which modules are loaded and what the name of each module is. Now you are familiar with the process of fiddling with a new kernel it doesn't matter if you break anything and this is the best way to find out all the module names relevant to a good working system.
I cannot see a soundcard there, snd-emu10k1 should at least be there since that is what alsaconf has previousley detected.

Of course, why wouldn't you be able to? I have some weird situations on my computer with the original kernel not acting like it did originally (Doesn't realize that /dev/hde isn't the first disk, so I have to boot from CD-ROM to install LILO whenever I change LILO so I can boot into Windows XP). But I'm liking 2.4.26 more than 2.6.7. With SCSI-emulation working on 2.4.26 and having direct read/write for 2.6.7, there can be some conflictions, but since most drivers are written for the 2.4 kernel, I think that's what I'm sticking with this time around.

bonecrusher · 07-06-2004, 08:06 AM

If it were me, (and this is BTW how I do it...) I would load all alsa stuff as modules per the Alsa web site.
On my sound card I loaded everything as a module (I mean everything...---from the kernel config- i e make menuconfig) and then let my computer decide what it wanted to load after I ran alsaconf... but you can of course just choose those modules you really want. Just make sure you pick the ones you absolutely have to have in the kernel.. ie your soundcore etc.

Oh and also, like others have maybe mentioned, I DID NOT load anything from OSS sound (The options underneath ALSA marked as Deprecated.) This really shouldn't make problems, (As I have loaded them before,) but why load them if alsa works just fine? (Which it does... - I use KDE and GNOME with no probs...)

-bc

And PS: I run 2.6.7-mm5 (and before that plain 2.6.7) with no problems what so ever. So just because you run a 2.4 doesn't mean you will or won't have problems. It just means you always need to be careful what you do when you compile more then anything.
Yes-you may come across bugs in the 2.6.7 kernel, but I doubt this is the reason you guys are having problems.
And Jensen: I wasn't addr this to you, I meant in general, you are right about more drivers probably working for a 2.4 kernel, but as I said, I have no problems. And I DO load many diff drivers (such as a web cam driver and others.. not even written for 2.6.7)

jt42 · 07-06-2004, 07:12 PM

One of the things I saw while having a quick peek through the alsa docs in slackware was the following blurb (paraphrased):

You can't use the aliased name as the alias target so...

alias sound-card-0 snd-emu10k1
alias sound-slot-0 snd-card-0

should become

alias sound-card-0 snd-emu10k1
alias sound-slot-0 snd-emu10k1

if I am reading the docs and modprobe.conf stuff correctly.

I've used it both ways with 2.4.26 and 2.6.7 and sound has worked ok. I checked the website and the only place I could see this referenced is the OSS-Emulation.txt file.

-j

(ps my hint for making multiple kernel recompiles more "fun": install ccache and set HOSTCC to 'ccache gcc'