Please translate the following for a newbie....
I have downloaded a modem driver that I need here is the file name:
intel536-4.68-rh9-up.tgz The Readme instructions are: 6 steps to install 1. login as ROOT 2. extract the archive into a directory with "tar -zxvf <archivename>.tgz" 3. cd into the directory it created. 4. Type: make clean 5. Type: make 536 6. Type: make install What exactly does No2 of these instructions mean?? How do I do it? Sorry for asking such an easy question but I have a lot to learn!!! |
What it means is that you should cd into the directory you saved the .tgz file and type in:
tar -zxvf intel536-4.68-rh9-up.tgz when it has finished extracting, cd into the new directory created by the untarring and then continue from step 4. |
1. $ su
Password: <root's password> 2. # tar -xvzf intel536-4.68-rh9-up.tgz 3. # cd intel536-4.68 (or something like that, type intel and then hit TAB, it will give you the cohice or finish it up for you) from here on you'll be installing the driver: 4. # make clean 5. # make 536 6. # make install Have fun! |
Thanks so much .... I'll give it a try.
:-) |
Here is a great install help site for us newbs :)
http://linux-newbie.sunsite.dk/lnag_...how_do_install HTH, mark |
Well, it went pear shaped..... :-(
|
It wouldn't install right... It went right at first as you can see below, but then it wouldn't work right Any idea what this lot means?
[root@localhost root]# tar -zxvf intel536-4.68-rh9-up.tgz Intel536-4.68-RH9-UP/ Intel536-4.68-RH9-UP/coredrv/ Intel536-4.68-RH9-UP/coredrv/softserial.c Intel536-4.68-RH9-UP/coredrv/softserial_io.c Intel536-4.68-RH9-UP/coredrv/softserial_ioctl.c Intel536-4.68-RH9-UP/coredrv/softserial.h Intel536-4.68-RH9-UP/coredrv/clmmain.c Intel536-4.68-RH9-UP/coredrv/coredrv.c Intel536-4.68-RH9-UP/coredrv/rts.c Intel536-4.68-RH9-UP/coredrv/task.c Intel536-4.68-RH9-UP/coredrv/uart.c Intel536-4.68-RH9-UP/coredrv/locks.c Intel536-4.68-RH9-UP/coredrv/makefile Intel536-4.68-RH9-UP/coredrv/536core.lib Intel536-4.68-RH9-UP/coredrv/hamdefs.h Intel536-4.68-RH9-UP/coredrv/hamcore.h Intel536-4.68-RH9-UP/coredrv/rts.h Intel536-4.68-RH9-UP/coredrv/uart.h Intel536-4.68-RH9-UP/coredrv/tasker.h Intel536-4.68-RH9-UP/coredrv/sys_ver.h Intel536-4.68-RH9-UP/coredrv/softcore.h Intel536-4.68-RH9-UP/coredrv/lock_lin.h Intel536-4.68-RH9-UP/coredrv/wwh_dflt.c Intel536-4.68-RH9-UP/coredrv/wwh_dflt.h Intel536-4.68-RH9-UP/makefile Intel536-4.68-RH9-UP/Intel536_boot Intel536-4.68-RH9-UP/Intel536_inst Intel536-4.68-RH9-UP/readme.txt Intel536-4.68-RH9-UP/license.txt Intel536-4.68-RH9-UP/hamregistry Intel536-4.68-RH9-UP/config_check Intel536-4.68-RH9-UP/Intel536.o [root@localhost root]# cd Intel536-4.68-RH9-UP [root@localhost Intel536-4.68-RH9-UP]# make clean cd coredrv; make clean make[1]: Entering directory `/root/Intel536-4.68-RH9-UP/coredrv' rm -f *.ko *.o *~ core make[1]: Leaving directory `/root/Intel536-4.68-RH9-UP/coredrv' rm -f *.o [root@localhost Intel536-4.68-RH9-UP]# make 536 Module precompile check Current running kernel is: 2.4.20-8 /lib/modules... autoconf.h does not exist please install kernel source make: *** [check] Error 1 [root@localhost Intel536-4.68-RH9-UP]# make install bash Intel536_inst running kernel 2.4.20-8 installing hamregistry, used for persistant storage installing Intel536 driver install: cannot stat `Intel536.o': No such file or directory redhat hamboot rc2.d and rc3.d scripts starting module and utilities error loading Intel536 done [root@localhost Intel536-4.68-RH9-UP]# To be honest I'm getting fed up with Linux. I SOOOOO want it to work and I spent days and days with my last modem (a conexant winmodem) and so I bought this new Intel one and still no luck! ANy help greatfully recieved.... |
Quote:
did you bother to read the documentation before you got fed up? https://www.redhat.com/docs/manuals/ |
Quote:
:study: I loaded up everthing from the CDs (I thought) but obviously I have much to learn...... hence the posting in the Newbies section! Anyway, I did wonder about the Kernel message bit and went to the "Add/ remove Applications" and installed all the things that might be needed (and no doubt some that aren't!) However, still no luck. I think the kernal source code is installed now and this time through I got a different error message: [root@localhost Intel536-4.68-RH9-UP]# make clean cd coredrv; make clean make[1]: Entering directory `/root/Intel536-4.68-RH9-UP/coredrv' rm -f *.ko *.o *~ core make[1]: Leaving directory `/root/Intel536-4.68-RH9-UP/coredrv' rm -f *.o [root@localhost Intel536-4.68-RH9-UP]# make536 bash: make536: command not found [root@localhost Intel536-4.68-RH9-UP]# make 536 Module precompile check Current running kernel is: 2.4.20-8 /lib/modules... autoconf.h exists diff: /boot/vmlinuz.autoconf.h: No such file or directory autoconf.h matches running kernel diff: /boot/vmlinuz.version.h: No such file or directory version.h matches running kernel cd coredrv; make \ "PSTN_DEF=-DTARGET_SELAH -DTARGET_LINUX -DLINUX" \ 536core; make[1]: Entering directory `/root/Intel536-4.68-RH9-UP/coredrv' cc -DTARGET_SELAH -DTARGET_LINUX -DLINUX -Wall -O -I /lib/modules/`uname -r`/bui ld/include -I ../inc -fno-common -DTARGET_SELAH -c -o coredrv.o coredrv.c coredrv.c:284: warning: `power_callback' defined but not used cc -DTARGET_SELAH -DTARGET_LINUX -DLINUX -Wall -O -I /lib/modules/`uname -r`/build/include -I ../inc -fno-common -DTARGET_SELAH -c -o clmmain.o clmmain.c cc -DTARGET_SELAH -DTARGET_LINUX -DLINUX -Wall -O -I /lib/modules/`uname -r`/build/include -I ../inc -fno-common -DTARGET_SELAH -c -o rts.o rts.c cc -DTARGET_SELAH -DTARGET_LINUX -DLINUX -Wall -O -I /lib/modules/`uname -r`/build/include -I ../inc -fno-common -DTARGET_SELAH -c -o task.o task.c cc -DTARGET_SELAH -DTARGET_LINUX -DLINUX -Wall -O -I /lib/modules/`uname -r`/build/include -I ../inc -fno-common -DTARGET_SELAH -c -o uart.o uart.c cc -DTARGET_SELAH -DTARGET_LINUX -DLINUX -Wall -O -I /lib/modules/`uname -r`/build/include -I ../inc -fno-common -DTARGET_SELAH -c -o wwh_dflt.o wwh_dflt.c cc -DTARGET_SELAH -DTARGET_LINUX -DLINUX -Wall -O -I /lib/modules/`uname -r`/build/include -I ../inc -fno-common -DTARGET_SELAH -c -o locks.o locks.c cc -DTARGET_SELAH -DTARGET_LINUX -DLINUX -Wall -O -I /lib/modules/`uname -r`/build/include -I ../inc -fno-common -DTARGET_SELAH -c -o softserial_io.o softserial_io.c cc -DTARGET_SELAH -DTARGET_LINUX -DLINUX -Wall -O -I /lib/modules/`uname -r`/build/include -I ../inc -fno-common -DTARGET_SELAH -c -o softserial_ioctl.o softserial_ioctl.c cc -DTARGET_SELAH -DTARGET_LINUX -DLINUX -Wall -O -I /lib/modules/`uname -r`/build/include -I ../inc -fno-common -DTARGET_SELAH -c -o softserial.o softserial.c strip --strip-debug 536core.lib ld -r coredrv.o clmmain.o rts.o task.o uart.o wwh_dflt.o locks.o softserial_io.o softserial_ioctl.o softserial.o 536core.lib -o Intel536.o make[1]: Leaving directory `/root/Intel536-4.68-RH9-UP/coredrv' cp coredrv/Intel536.o . [root@localhost Intel536-4.68-RH9-UP]# make install bash Intel536_inst running kernel 2.4.20-8 installing hamregistry, used for persistant storage installing Intel536 driver redhat hamboot rc2.d and rc3.d scripts starting module and utilities done [root@localhost Intel536-4.68-RH9-UP]# That lot reads to me like something happened - it appears to have installed now, but still my modem doesn't work, and still my 'Hardware browser" doesn't see the modem. As always, any help appreciated..... (PS I am trying my best!) |
My best advice is to return that intel modem and spend $30 more for an external modem. Less CPU overhead, easier to configure, and more stable.
|
Hmmmm... no doubt very good advice, although I would rather sort out my present one (either of my present ones!).
I'm keen to learn Linux, and I must admit, all the hassle I've had has taught me loads.... I would like to have ONE positive result from all my hard work though before giving up and buying modem No 3! If you have any idea what is wrong in the above listing I'm keen to try again! |
Take comfort in this:
Open source means total system administration on the software and code level. Linux only makes up about 5% of the current targeted operating systems for viruses. The possibilites are endless. The main problem with what is listed above has to do with a technology called "WinModems." Granted there is support for some of them in linux, but it operates much differently from a true modem. Hardware modems have their own built in com port. Software (win)modems use cpu resources to "make" a com port. The hassle just isn't worth it. I would say my advise would fix your problem and you would have a more stable internet connection and less cpu overhead on your computer. |
All times are GMT -5. The time now is 06:13 PM. |