Not sure exactly how to explain what I think the bug may be, but here goes. I have the via82xx internal modem in my laptop. I have the alsa module, and it is loaded along with slmodem, and works fine for root, however, the /dev/modem symlink doesn't seem to be getting the proper group settings. In the /etc/conf.d/slmodem I have the following # Config file for /etc/init.d/slmodemd DEV=/dev/ttySL0 COUNTRY=USA GROUP=dialout # The following symlink will be created if uncommented LN_DEV=/dev/modem # Raise priority to reduce modem dropouts NICE=-6 # ALSA Options: # The following sets the ALSA (alsasound) init script to # be a dependancy of the slmodem one. It does also provides # ALSA support. MODULE=alsa # The modem hardware slot # use "modem:0", "modem:1", etc. HW_SLOT=modem:1 The /dev/modem symlink is linked to /dev/ttySL0 which is linked to /dev/pts/1 - /dev/pts/1 has the root:dialout permissions, however /dev/ttySL0 and /dev/modem are both root:root. I am using udev, without using the static tarball. If any other information is needed, please don't hesitate to ask. Reproducible: Always Steps to Reproduce: 1. 2. 3. Expected Results: /dev/modem device should be set to group dialout.
Oh, forgot, this is using gentoo-dev-sources-2.6.11-r2 and slmodem 2.9.9a-r2
symlinks "rights" cannot be modified - always have lrwxrwxrwx. dialout group is there for a reason. just add your user to this group and you'll be fine.
That is the thing - my user IS in the dialout group. lsof doesn't show anything using /dev/ttySL0, and using root or sudo to run wvdial works fine.
a) what rights does your _real_ device inode have? b) did you looked in syslog to see the possible reason? c) have you searched bugzilla for the similar problems? My wild guess is that you have the same problem bug #79897
is this a duplicate of #79897?
After recompiling glibc, wvstreams, and wvdial, I still cannot dial out as a user, I sent an email to gentoo-laptop with all (i think) pertinent info, hopefully someone there can suggest something.
what version of wvstreams do you have?
I have net-libs/wvstreams 4.0.1-r2 emerged.
Created attachment 53160 [details, diff] slmodem.diff I think this is caused by udev recently stopping to look into permissions.d, cany ou please try the attached ebuild-patch+ remerge and if it helps you?
ok, then it's not duplicate of that bug. @stefan: the name of the group is dialout @steev: if slmodem.diff (of course, with group changed to dialout) does not work with you, please run wvdial from a terminal as normal user and post here the output.
Patch applied with no problems, compiled fine, installed fine. Still didn't work - I am using the IN kernel (as module) alsa via 82xx modem drivers, and the output of wvdial is steev@mebius ~ $ wvdial --> WvDial: Internet dialer version 1.54.0 --> Cannot open /dev/ttySL0: Device or resource busy --> Cannot open /dev/ttySL0: Device or resource busy --> Cannot open /dev/ttySL0: Device or resource busy
I think it is locking mechanism... You should have rwx in /var/lock, or else device locking will fail. On my system, "ls -l /var | grep lock" has the output: drwxrwxr-x 3 root uucp 31 Mar 12 13:52 lock so, in order to successfully lock a serial device, I must be in group uucp. Unfortunatelly, ebuilds cannot control owner/group on common directories very well. Please tell me if this solved your problem.
That fixed it! I am closing the bug, but I am interested in why lock needed to be rwx - it was drwxr-xr-x so i chmoded it to 775, and its working fine now as my normal user.
