Hi all,

I compile pcspeaker as module in my kernel config.

In KDE when you can choose use system beep which makes the audio come out the pc speaker it works only for root. Not other users of the same pc.

The root can log out, the other user log in and it dont work.

Can a module be owned by root. I have to 'modprobe pcspkr' in /etc/rc.modules at boot up for it.

This is not critical I know, but the reason that I'm asking this is in case I need to ever do this for a different module I would just like to learn how you, well I guess 'chown' it?

This also applies to me with a logitech mx310. KDE says 'libusb' is found but KDE cannot access it because of permissions. Which 'libusb' would that be? I guess I have to learn to fix that one too for normal users.

The mouse does work for normal user accounts, however the normal users cannot check off use 800 dpi vs 400 dpi. Again, not a big deal, but I need to learn how to give access to modules.

Thank you in advance.

Hi Fogie

A kernel module is not 'owned' by any user. It is loaded by the kernel and then offers the required functionality to the system (like, support for a piece of hardware). The access to the hardware usually takes place through a device file (/dev/mouse or the likes) and this is where user permissions come into play. The access and ownership attributes of the device file determine whether you as ordinary user can access or use certain hardware.

For instance, to be able to use most of your computer's hardware, you should add your user at least to the groups sys,disk,floppy,cdrom,scanner. This is the desired way of doing things, and is better than go out editing the permissions of device files to 777.

Eric

Hi Eric,

OK I will give that a try and report back, thank you for the reply.

Fogie

HI Eric,

I got the system beep working

Apparently this mouse issue is a combination of the way pat properly the linux way loads usb support at 600 and not 666 which is what kde wants has a mention about this at:

http://64.233.161.104/search?q=cache...s&ct=clnk&cd=1

maybe the next kde has this guys code in it and my problem will be solved in next slackware, as slax even lets normal users do 800 dpi.

if i log in as root/kdesu then change to 800 dpi my users get 800 dpi until next reboot. oh well, i just su then for now, slack 11 soon w/newer kde probably has me covered.

Maybe you can modify the udev rules for that device to match those perms?


Cheers,
Tink

on my test partition, with default slack 10.2 load .. I removed all KDE and then installed the very latest KDE slackware packages that KDE has on their web-site and no luck. Still can't change the dpi settings of the mouse if non-root. And I can do it on SuSE and even vector.

Did you look at the udev rules?


Cheers,
Tink

I've been muscling my way trying to read up on udev. Quite simply I'm having a hard time comprehending it. I've only spent an hour reading on it tho. I need to spend some more time on it.

Well it appears Pat did not configure KDE correctly and KDE has a how-to for this issue located at:

http://docs.kde.org/stable/en/kdebas...use/index.html

however, that "fix" does not work, and I'm so lost on udev

That's debatable ...

BUT: Slack doesn't have PAM, that's true, hence anything relying on
pam_console will obviously fail to do the trick.


Cheers,
Tink

I wonder if I need to do something like Eric has on his wiki for my hotplug? That was what they were kind of talking about in the KDE section that the issue is hotplug related.

http://www.slackware.com/~alien/doku...lackware:fixes

anyone understand how one might translate Eric's work from a scanner to a usb mouse?

this program works , takes care of a logitech mouse, tho I have no idea what people with other high dpi mice from other manufacturer's would do in slackware tho.

http://lomoco.linux-gamers.net/

old thread,

but i finally figured out how to get access to usb devices as non-root.

works for my scanner and now i can get 800 dpi w/the mouse

there's no post number but it's from the person 'dignome'

here:
http://qemu.dad-answers.com/viewtopi...4c0534e38b6798