Results 1 to 3 of 3
I used scanModem to figure out the drivers requierd and used
slmodem-2.9.11-20080126.tar
After the make install command I am getting
[root@localhost ungrab-winmodem-20070505]# modprobe ungrab-winmodem
bash: modprobe: command not found
Error....WHats ...
- 05-27-2008 #1Just Joined!
- Join Date
- May 2008
- Posts
- 2
smarlink modem under Linux kernel 2.6.9-1.667
I used scanModem to figure out the drivers requierd and used
slmodem-2.9.11-20080126.tar
After the make install command I am getting
[root@localhost ungrab-winmodem-20070505]# modprobe ungrab-winmodem
bash: modprobe: command not found
Error....WHats the reason
The terminal listing is --------------------------------
[sri@localhost ~]$ cd /home/sri/newDriver/slmodem-2.9.11-20080126
[sri@localhost slmodem-2.9.11-20080126]$ make KERNEL_DIR=/lib/modules/2.6.9-1.66 7/build
make -C modem all
make[1]: Entering directory `/home/sri/newDriver/slmodem-2.9.11-20080126/modem'
make[1]: Leaving directory `/home/sri/newDriver/slmodem-2.9.11-20080126/modem'
make -C drivers KERNEL_DIR=/lib/modules/2.6.9-1.667/build
make[1]: Entering directory `/home/sri/newDriver/slmodem-2.9.11-20080126/drivers '
cc -I/lib/modules/2.6.9-1.667/build/include -o kernel-ver kernel-ver.c
make all KERNEL_VER=2.6.9-1.667
make[2]: Entering directory `/home/sri/newDriver/slmodem-2.9.11-20080126/drivers '
make modules -C /lib/modules/2.6.9-1.667/build SUBDIRS=/home/sri/newDriver/slmod em-2.9.11-20080126/drivers
make[3]: Entering directory `/lib/modules/2.6.9-1.667/build'
Building modules, stage 2.
MODPOST
make[3]: Leaving directory `/lib/modules/2.6.9-1.667/build'
make[2]: Leaving directory `/home/sri/newDriver/slmodem-2.9.11-20080126/drivers'
make[1]: Leaving directory `/home/sri/newDriver/slmodem-2.9.11-20080126/drivers'
[sri@localhost slmodem-2.9.11-20080126]$ make
make -C modem all
make[1]: Entering directory `/home/sri/newDriver/slmodem-2.9.11-20080126/modem'
make[1]: Leaving directory `/home/sri/newDriver/slmodem-2.9.11-20080126/modem'
make -C drivers KERNEL_DIR=/lib/modules/2.6.9-1.667/build
make[1]: Entering directory `/home/sri/newDriver/slmodem-2.9.11-20080126/drivers'
cc -I/lib/modules/2.6.9-1.667/build/include -o kernel-ver kernel-ver.c
make all KERNEL_VER=2.6.9-1.667
make[2]: Entering directory `/home/sri/newDriver/slmodem-2.9.11-20080126/drivers'
make modules -C /lib/modules/2.6.9-1.667/build SUBDIRS=/home/sri/newDriver/slmodem-2.9.11-20080126/drivers
make[3]: Entering directory `/lib/modules/2.6.9-1.667/build'
Building modules, stage 2.
MODPOST
make[3]: Leaving directory `/lib/modules/2.6.9-1.667/build'
make[2]: Leaving directory `/home/sri/newDriver/slmodem-2.9.11-20080126/drivers'
make[1]: Leaving directory `/home/sri/newDriver/slmodem-2.9.11-20080126/drivers'
[root@localhost slmodem-2.9.11-20080126]# make install
make -C modem all
make[1]: Entering directory `/home/sri/newDriver/slmodem-2.9.11-20080126/modem'
make[1]: Leaving directory `/home/sri/newDriver/slmodem-2.9.11-20080126/modem'
make -C drivers KERNEL_DIR=/lib/modules/2.6.9-1.667/build
make[1]: Entering directory `/home/sri/newDriver/slmodem-2.9.11-20080126/drivers'
cc -I/lib/modules/2.6.9-1.667/build/include -o kernel-ver kernel-ver.c
make all KERNEL_VER=2.6.9-1.667
make[2]: Entering directory `/home/sri/newDriver/slmodem-2.9.11-20080126/drivers'
make modules -C /lib/modules/2.6.9-1.667/build SUBDIRS=/home/sri/newDriver/slmodem-2.9.11-20080126/drivers
make[3]: Entering directory `/lib/modules/2.6.9-1.667/build'
Building modules, stage 2.
MODPOST
make[3]: Leaving directory `/lib/modules/2.6.9-1.667/build'
make[2]: Leaving directory `/home/sri/newDriver/slmodem-2.9.11-20080126/drivers'
make[1]: Leaving directory `/home/sri/newDriver/slmodem-2.9.11-20080126/drivers'
make install -C drivers KERNEL_DIR=/lib/modules/2.6.9-1.667/build
make[1]: Entering directory `/home/sri/newDriver/slmodem-2.9.11-20080126/drivers'
cc -I/lib/modules/2.6.9-1.667/build/include -o kernel-ver kernel-ver.c
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.9-1.667
make[2]: Entering directory `/home/sri/newDriver/slmodem-2.9.11-20080126/drivers'
install -D -m 644 slamr.ko /lib/modules/2.6.9-1.667/extra/slamr.ko
install -D -m 644 slusb.ko /lib/modules/2.6.9-1.667/extra/slusb.ko
/sbin/depmod -a
make[2]: Leaving directory `/home/sri/newDriver/slmodem-2.9.11-20080126/drivers'
make[1]: Leaving directory `/home/sri/newDriver/slmodem-2.9.11-20080126/drivers'
install -D -m 755 modem/slmodemd /usr/sbin/slmodemd
rm -f -rf /var/lib/slmodem
install -d -D -m 755 /var/lib/slmodem
[root@localhost slmodem-2.9.11-20080126]# cd /home/sri/newDriver/ungrab-winmodem-20070505
[root@localhost ungrab-winmodem-20070505]# modprobe ungrab-winmodem
bash: modprobe: command not found
[root@localhost ungrab-winmodem-20070505]#
- 05-27-2008 #2
Odd, sounds like modprobe is not in your env Path.
Try:Check your ENV:Code:# whereis modprobe
Try running modprobe with the full path.Code:# env | grep -i ^path
Men occasionally stumble over the truth,
but most of them pick themselves up
and hurry off as if nothing had happened.
Winston Churchill
... then the Unix-Gods created "man" ...
- 05-28-2008 #3Just Joined!
- Join Date
- May 2008
- Posts
- 2
wvdial times out
I got the modprobe thing corrected ... I was in a subdir..changed to root
by su -
Now after /usr/lib/slmodemd is running...
I checked wvdialconfig /etc/wvdial.conf also..its producing the correct
file...
Only thing is wvdial timesout intead of connecting...
please give a listing of a correct /etc/wvdial.conf file...


Reply With Quote