Re: Regarding automation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Also if the above suggestions, did not help any and if you send
output of

# chkconfig slmodemd --list
send us
# lsmod

to see if ungrab-winmodem and slamr are loaded or not? you can check
if they are present in the system by doing

# ls /lib/modules/`uname -r`/extra/ -l
should output three, ungrab-winmodem.ko, slamr.ko, and slusb..ko.

Regards,

Antonio

On 6/20/08, Antonio Olivares <olivares14031@xxxxxxxxx> wrote:
> Nitin,
>
> Did you add modprobe ungrab-winmodem, and modprobe slamr in
> /etc/rc.d/init.d/slmodemd
>
> start() {
>         modprobe ungrab-winmodem  <--- this
>         modprobe slamr                      <---- this
>         echo -n "Starting SmartLink Modem driver for $SLMODEMD_DEVICE: "
>         $prog /dev/null 2>/dev/null \
>             --country=$SLMODEMD_COUNTRY $SLMODEMD_OPTS /dev/$SLMODEMD_DEVICE
> &
>         RETVAL=$?
>         [ $RETVAL -eq 0 ] && success $"$prog startup" || failure
> $"$prog startup"
>         echo
>         [ $RETVAL -eq 0 ] && touch /var/lock/subsys/$prog
>         return $RETVAL
> }
>
> start
> {
>
> }
>
> procedure.
>
>
> Did you add the line [1] into modprobe.conf?
>
> [1]
>
> 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)
>
> As a single line., if that does not work, you can add before
>
> modprobe ungrab-winmodem
> modprobe slamr
>
> the following, if you added [1] as root su -, as a single line..
>
> The following creates the /dev/slamr0 every time, if you add it into
> /etc/rc.d/init.d/slmodemd after start procedure
>
> start() {
>
> if ! [[ -e $SLMODEMD_DEVICE ]] &> /dev/null; then
>     {
>         echo -n "Creating devices ..."
>         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  ||
>         {
>                 echo "failed."
>                 exit -1
>         }
>      }
>  fi
>         modprobe ungrab-winmodem  <--- this
>         modprobe slamr                      <---- this
> ...
> } /* end of start() procedure */
>
> If you did everything suggested, please send the output of
>
> # chkconfig slmodemd --list
>
> to us, we can do our best to fix this so you won't have to compile and
> install everytime.
>
> Regards,
>
> Antonio
>
> On 6/20/08, Nitin Niroula <nitinniroula@xxxxxxxxx> wrote:
>> i tried Antonio's instruction but it didn't work. According to Marvin,
>> when I use 'mknod' it says file exists, but when i use 'slmodemd -c
>> USA /dev/slamr0' it says "cannot setup device". So when i reboot i
>> have to compile, load drivers,and use slmodemd. Is there any way out?
>>
>> Waiting for your reply,
>> Nitin
>>
>

[Index of Archives]     [Linux Media Development]     [Asterisk]     [DCCP]     [Netdev]     [X.org]     [Xfree86]     [Fedora Women]     [Linux USB]

  Powered by Linux