Remove one = from NAME== in the first line. See also http://bugs.archlinux.org/task/4612

I tried and I also read the other task but, but it's the same

try NAME= and GROUP=

ah and MODE=

now I have:

KERNEL=="ttySL[0-9]", NAME="%k", MODE="0660", GROUP="tty", SYMLINK+="modem"
ACTION=="add", DRIVER=="slamr", RUN+="/lib/udev/load-modules.sh ppp-generic"
ACTION=="add", DRIVER=="slusb", RUN+="/lib/udev/load-modules.sh ppp-generic"

but I still continue to have no symlink and wrong permissions on device

remove NAME="%k" completely

I remove it, but no changes.

KERNEL=="ttySL[0-9]", MODE="0660", GROUP="tty", SYMLINK+="modem"
ACTION=="add", DRIVER=="slamr", RUN+="/lib/udev/load-modules.sh ppp-generic"
ACTION=="add", DRIVER=="slusb", RUN+="/lib/udev/load-modules.sh ppp-generic"

How can I verify that udev read etc/udev/rules.d/slmodem.rules ?

run udevtest /dev/yourdevice then errors should be shown

running slmodem daemon without using che rc. script I got this:

[root@p4m ~]# slmodemd --country=ITALY /dev/slamr0
SmartLink Soft Modem: version 2.9.11 Mar 12 2006 19:54:57
error: cannot find group 'uucp': No such file or directory
symbolic link `/dev/ttySL0' -> `/dev/pts/1' created.
modem `slamr0' created. TTY is `/dev/pts/1'
Use `/dev/ttySL0' as modem device, Ctrl+C for termination.

group 'uucp' could be the problem?

hmm could be

I add group 'uucp' with command: groupadd uucp
now I got these:

[firetux@p4m ~]$ ls -l /dev/ttySL0
lrwxrwxrwx 1 root root 10 2006-05-20 16:03 /dev/ttySL0 -> /dev/pts/1
[firetux@p4m ~]$ ls -l /dev/pts/1
crw-rw---- 1 root uucp 136, 1 2006-05-20 16:03 /dev/pts/1
[firetux@p4m ~]$ ls -l /dev/slamr0
crw-r--r-- 1 root root 242, 0 2006-05-20 15:52 /dev/slamr0
[firetux@p4m ~]$ ls -l /dev/modem
ls: /dev/modem: No such file or directory
[firetux@p4m ~]$

are you using udev 091 or 092?

[root@p4m ~]# pacman -Qi udev
Name : udev
Version : 091-6

could you please try 092 from testing? perhaps it is already fixed in it.

I upgrade udev to version 092-3. Nothing change :-(

hmm am i right ttySL is a symolic link?
if yes the rule cannot work because on symlinks you cannot change rights only on base device this is possible

when you run slmodemd it create /dev/pts/1 and /dev/ttySL0. ttySL* is a symbolic link to the first one

[root@p4m ~]# ls -l /dev/ttySL0 /dev/pts/1
crw-rw---- 1 root uucp 136, 1 2006-05-20 16:53 /dev/pts/1
lrwxrwxrwx 1 root root 10 2006-05-20 16:53 /dev/ttySL0 -> /dev/pts/1
[root@p4m ~]#

If the rule doesn't work with symlinks I think you have to add group 'uucp' during installation of slmodem-utils, so user can add ourself to this group.
Now another question: why it doesn't create the link /dev/modem ? For the same explanation?
Thank you

this is really crazy, because pts/1 could be anything and not only your modem :(
i donT' want to have a rule on /dev/pts devices
hmmm have you time to meet on irc it's better to fix this online together then through bugtracker.

[tobias@Wohnung ~]$ slmodemd --help
Usage: slmodemd [option...] <device>
Where 'device' is name of modem device (default `/dev/slamr0')
and 'option' may be:
-h, --help this usage
-u, --usage this usage
-v, --version show version and exit
-c, --country=VAL default modem country name (default `USA')
--countrylist show list of supported countries
-a, --alsa ALSA mode (see README for howto)
-g, --group=VAL Modem TTY group (default `uucp')
-p, --perm=VAL Modem TTY permission (default `0660')
-r, --ringdetector with internal ring detector (software)
-n, --nortpriority run with regular priority
-s, --shortbuffer use short buffer (4 periods length)
-d, --debug=VAL debug level (default `0')
-l, --log=VAL logging mode (default `5')
to set the group the slmodemd is needed and not udev

DRIVER=="slamr", SYMLINK+="modem" RUN+="/lib/udev/load-modules.sh ppp-generic"
DRIVER=="slusb", SYMLINK+="modem" RUN+="/lib/udev/load-modules.sh ppp-generic"
are those rules helping to get the modem symlink and ppp-generic loaded?

please try these:
ACTION=="add", DRIVER=="slamr", SYMLINK+="modem", RUN+="/lib/udev/load-modules.sh ppp-generic"
ACTION=="add", DRIVER=="slusb", SYMLINK+="modem", RUN+="/lib/udev/load-modules.sh ppp-generic"

in PKGBUILD of slmodem-utils you had put only one '>' (instead of '>>') in the second 'echo', so /etc/udev/rules.d/slmodem.rules is

'ACTION=="add", DRIVER=="slusb", SYMLINK+="modem", RUN+="/lib/udev/load-modules.sh ppp-generic"'

I add it but, but no symlink yet :(
I will change options for slmodemd, I think you can completly remove slmodem.rules

ppp-generic is still loaded or do you have serial ports in your pc?

I don't have serial port. I load 'ppp-generic' and after 'slamr'

is this working?
ACTION=="add", DRIVER=="slamr", NAME="%k", SYMLINK+="modem", RUN+="/lib/udev/load-modules.sh ppp-generic"
ACTION=="add", DRIVER=="slusb", NAME="%k", SYMLINK+="modem", RUN+="/lib/udev/load-modules.sh ppp-generic"

it doesn't work. I think that it doesn't work because is not the module 'slamr' or 'slusb' that create a device but is 'slmodem' that create /dev/slamr, /dev/pts/1 and /dev/ttySL0 (as symbolic link to /dev/pts/1)

sorry to say so but, slmodem does not exist!
there are 2 modules slamr and slusb no slmodem module

sorry, not 'slmodem' as module...but 'slmodemd' (daemon)

hmm ok an other try:
KERNEL=="slamr", NAME="slamr0", MODE="0660", GROUP="tty", SYMLINK+="modem", RUN+="/lib/udev/load-modules.sh ppp-generic"
KERNEL=="slusb", NAME="slusb0", MODE="0660", GROUP="tty", SYMLINK+="modem", RUN+="/lib/udev/load-modules.sh ppp-generic"

it doesn't work

ok then if you have time, try to find any information on /sys/ about the modem, perhaps then it's possible to find a rules that fits.

with 'lspci' I get this:

00:1f.6 Modem: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller (rev 01)

and I found directory /sys/devices/pci0000:00/0000:00:1f.6 , in this folder there are:

[root@p4m ~]# ls -l /sys/devices/pci0000:00/0000:00:1f.6
totale 0
lrwxrwxrwx 1 root root 0 2006-05-24 13:53 bus -> ../../../bus/pci
-r--r--r-- 1 root root 4096 2006-05-24 13:53 class
-rw-r--r-- 1 root root 256 2006-05-24 13:53 config
-r--r--r-- 1 root root 4096 2006-05-24 13:53 device
lrwxrwxrwx 1 root root 0 2006-05-24 13:53 driver -> ../../../bus/pci/drivers/slamr
-r--r--r-- 1 root root 4096 2006-05-24 13:53 irq
-r--r--r-- 1 root root 4096 2006-05-24 13:53 local_cpus
-r--r--r-- 1 root root 4096 2006-05-24 13:53 modalias
drwxr-xr-x 2 root root 0 2006-05-24 13:53 power
-r--r--r-- 1 root root 4096 2006-05-24 13:53 resource
-rw------- 1 root root 256 2006-05-24 13:53 resource0
-rw------- 1 root root 128 2006-05-24 13:53 resource1
-r--r--r-- 1 root root 4096 2006-05-24 13:53 subsystem_device
-r--r--r-- 1 root root 4096 2006-05-24 13:53 subsystem_vendor
--w------- 1 root root 4096 2006-05-24 13:53 uevent
-r--r--r-- 1 root root 4096 2006-05-24 13:53 vendor
[root@p4m ~]#

what information do you need?

you are using the alsa mode aren't you? so probably this is the reason for the issue, perhaps it works on a normal slmodem as it should.

I'm using normal slmodemd, not alsa mode.

status?

I still have the same problem

status on new packages?

closing due to not answering