Shatz The following info is withint Smartlink.txt The following install and remove commands are to be written as single lines. They should be written somewhere in your /etc/modprobe.d/ folders or /etc/modprobe.conf depending on which your System has. If you to /etc/modules a line slamr all will occur on bootup. # Preloads ungrab-winmodem and creates a device node upon "modprobe slamr" install slamr modprobe --ignore-install ungrab-winmodem ; modprobe --ignore-install slamr; test -e /dev/slamr0 || (/bin/mknod -m 660 /dev/slamr0 c 242 0 2>/dev/null && chgrp uucp /dev/slamr0) # Removes slamr and ungrab-winmodem successively: remove slamr /sbin/modprobe -r --ignore-remove slamr ; /sbin/modprobe -r --ignore-remove ungrab-winmodem You should also check without slamr.ko loading, whether # modprobe ungrab-winmodem # modprobe snd-intel8x0m will support a subsequent success with: # slmodemd -c RUSSIA --alsa modem:1 MarvS On 2/21/07, shatz <axx@xxxxxxxx> wrote:
Marvin Stodolsky wrote: > A reason for the failure now is that most current Linux have ports > created in volatile RAM space, /dev/.udev ,i.e. /dev/slamr0 is not > stable upon shutdown > However the devices can be manually created under root/adm > persmission with: > mknod -m 600 /dev/slamr0 c 242 0 > Then all will likely work as before. Do then the > # modprobe ungrab-winmodem > # modprobe slamr > Try next the > slmodemd -c RUSSIA /dev/slamr0 > As u told me, I've removed hsf* drivers then reinstalled slmodem&ungrab-winmodem and got a success! It works fine till reboot :) manual creation of dev/slamr0 doesn't help, BTW, I suppose installer does this itself the right way if running under root (I found this in inst output): --- mkdir -p /dev mknod -m 600 /dev/slamr0 c 242 0 ; mknod -m 600 /dev/slamr1 c 242 1 ; mknod -m 600 /dev/slamr2 c 242 2 ; mknod -m 600 /dev/slamr3 c 242 3 ; echo -n mknod -m 600 /dev/slusb0 c 243 0 ; mknod -m 600 /dev/slusb1 c 243 1 ; mknod -m 600 /dev/slusb2 c 243 2 ; mknod -m 600 /dev/slusb3 c 243 3 ; echo -n make install KERNEL_VER=2.6.17-5mdv --- Thank you Marvin for helping me with this "Designed-for-WinXP" piece of hardw :) so after reboot I'm giving commands: mknod -m 600 /dev/slamr0 c 242 0 modprobe ungrab-winmodem modprobe slamr slmodemd <....> and then modem successfully starts. What's the best way to automate this process and to force these modules to load at startup? Jacques Goldberg wrote: > This device 1019:b732 indeed attaches to a 1039:7013 and the > 1019:b732 is an HSP56 WDM (read, PCTel). > 1019 identifies Elitegroup Computer Systems, a major Taiwan manufacturer. You're absolutely right, modem's made by ECS, it's model is AM303W, and in windows it's recognized as PCTel.
