Hi
I have an IBM Thinkpad A21m P3 processor. I installed Redhat Linux 7.1 and loaded the drivers for my Lucent MiniPCI modem which I got at this website: http://www.sfu.ca/~cth/ltm
to work with kernel 2.4.2-2.
Red Hat 7.1:
Peter Rayner <peter.rayner@csiro.au>
ltmodem-kv_2.4.2_2-8.22a3-
My linux install says on an i686(but the i686 driver did not work, plus I wasn't sure which process is the i686).
Anyway, I decided to updrage to Redhat ver.8. The install went fine, except that my modem does not work anymore. Now I have a new kernel 2.4.18-14, and so Had to find new drivers for the modem. So I went back to the above website, and saw that they had a few drivers:
1. Red Hat 8.0:
Paul Dyke <g0luc@yahoo.com>
ltmodem-kv_2.4.18_18.8.0-8
2. Red Hat 8.0:
Paul Dyke <g0luc@yahoo.com>
ltmodem-kv_2.4.18_18.8.0-8
3. Red Hat 8:
Marvin Stodolsky <stodolsk@rcn.com>
ltmodem-kv_2.4.18_14-8.26a
I didn't know which one I should use, and decided to try all of them. To my disappointment, when I used kppp and query the modem, I got the message "can't open modem"
So am stuck, and really don't know what to do next. I have no idea how to uninstall the installed packages for the modem, and I do not want to go back to using version 7.1. If anyone has any idea on how I can solve this issue, I would be most grateful.
with thanks
Bhagiratha
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Hi
I thank you for your help, but how do I get my system up to date via errata if I cannot connect to the internet via linux to use the up2date connector. My system is dual boot with win2000, can I download the necessary files and transfer them to floppy? Also, I took a look at the errata update website and only saw security fixes. Where doI get the new kernel version and how do I go about installing it?
Your feedback will be most appreciated.
Bhagiratha
It's not really practical to move the updates via floppy. There's too much data (about 400Mb at present) and a buch of the files won't fit on a floppy. But there are other options.
The easiest way would be to borrow a serial modem (which the stock system will know how to use) and apply the updates via up2date. An alternative to that is to download all of the updates onto a system with a CD burner and burn a CD with RockRidge extensions. I've got a shell script that will apply the updates, if you need to use that mechanism.
Hi
I thank you for your help, but how do I get my system up to date via errata if I cannot connect to the internet via linux to use the up2date connector. My system is dual boot with win2000, can I download the necessary files and transfer them to floppy? Also, I took a look at the errata update website and only saw security fixes. Where doI get the new kernel version and how do I go about installing it?
Your feedback will be most appreciated.
Bhagiratha
Hi
Thanks for the info. I think I will go for the cd burning install. if you can help me with the proper procedure, and with the shell script you mentioned.
Also, what are RockRidge extentions? I was checking my linux system and I have the 2.4.18-14 kernel, but you said I should bring my kernel version up to 2.4.18-8.0. Isn't my present kernel higher than what you said I should get?
I am a bit confused....please help
Regards
bhagiratha
The kernel version was a typo on my part the current kernel in the updates is 2.4.18-18.8.0, which is later than what you have. "RockRidge extensions" are a form of CD mastering that preserve the file attributes and permissions and directory structure as needed by a Linux system. If you only have access to a windows box for downloading and burning you may be able to get away with burning the CD with Joliet (the default on windows).
The script that I use to apply the updates to machines that don't have access to up2date (for security reasons) is below:
#!/bin/sh
#
# NAME
# apply-updates
#
# SYNOPSIS
# apply-updates [-test] path-to-updates-dir
#
# DESCRIPTION
#
# Applies RedHat updates in a sensible manner. Can be invoked with
# the first argument as "-test" for a dry-run to check for failing
# dependancies. This script expects to find ix86 dirs and a noarch
# dir in the specified directory. If the contents of the updates dir from
# ftp://ftp.redhat.com/pub/r
# are downloaded to the local machine you will have the correct
# directory structure.
#
# NOTES
# The ncftp client can do recursive "gets" in an intelligent manner and is
# easiest method of downloading and keeping the updates collection
# current. When retrieving later updates any files encountered that are
# identical on the local machine and the remote server wll be skipped.
# The command that I use is:
#
# ncftp> get -RT athalon i386 i586 i686 images noarch
#
# assuming that I'm in my updates dir on the local machne.
#
# This script will need to be modified each time updates are downloaded
# as new updates are released all the time and the update packages listed
# below are only correct as of the last time I refreshed my updates
# collection.
#
# While you can usually get away with applying the updates in multi-user
# mode, there may be times when this will result in a non-bootable system.
# Also, if the updates include a new kernel it is best to manually save your
# existing kernel before applying the updates. This can be done something
# like:
#
# root # cd /lib/modules
# root # cp -pdr 2.4.18-14 2.4.18-14-dist
# root # cd /boot
# root # for f in *2.4.18-14*; do cp -p $f $f-dist; done
#
# After the updates have been applied the saved files/dirs can be moved
# back to their normal names, like:
#
# root # cd /lib/modules
# root # mv 2.4.18-14-dist 2.4.18-14
# root # cd /boot
# root # for f in *-dist; do mv $f `basename $f '-dist'`; done
#
# Doing this allows you to include a boot stanza in /boot/grub/grub.conf
# like:
# title RedHat Dist (2.4.18-14)
# root (hd0,0)
# kernel /vmlinuz-2.4.18-14 ro root=/dev/sda2
# initrd /initrd-2.4.18-14.img
#
# enabling you to boot the old kernel if the updated kernel has problems.
#
# If your boot configuration requires requires an initrd, you'll need to
# make a new one with:
#
# root# cd /boot
# root# mkinitrd -v initrd-2.4.18-18.8.0.img 2.4.18-18.8.0
#
# RedHat does include an initrd image in their kernel update and you don't
# ordinarily need to build your own initrd. The exceptions are if you have
# non-RedHat disk or network drivers. In that case you'll probably also need
# to build a custom kernel for those.
#
# This patch list is complete as of 10 Dec 2002
#
# AUTHOR
# Jim Levie, email: jim@entrophy-free.net
#
if [ $1 = "-test" ]; then
MODE=test
FLGF="-F --nosignature --test"
FLGU="-U --nosignature --test"
FLGI="-i --nosignature --test"
ROOT=$2
else
mode=run
FLGF="-v -F --nosignature"
FLGU="-v -U --nosignature"
FLGI="-v -i --nosignature"
ROOT=$1
fi
ATHL=$ROOT/athlon
if [ ! -d $ATHL ]; then
echo "<$ROOT> doesn't contain the athlon update dir"
exit
fi
I386=$ROOT/i386
if [ ! -d $I386 ]; then
echo "<$ROOT> doesn't contain the i386 update dir"
exit
fi
I586=$ROOT/i586
if [ ! -d $I586 ]; then
echo "<$ROOT> doesn't contain the i586 update dir"
exit
fi
I686=$ROOT/i686
if [ ! -d $I686 ]; then
echo "<$ROOT> doesn't contain the i686 update dir"
exit
fi
NOAR=$ROOT/noarch
if [ ! -d $NOAR ]; then
echo "<$ROOT> doesn't contain the noarch update dir"
exit
fi
ARCH=`uname -m`
KERNEL=0
rpm -q kernel-2.4.18-18.8.0 >/dev/null
if [ $? = 1 ]; then
if [ $ARCH = "athlon" ]; then
rpm $FLGF $ATHL/kernel-2.4.18-18.8.0
$I386/kernel-BOOT-2.4.18-1
$I386/kernel-doc-2.4.18-18
$ATHL/kernel-smp-2.4.18-18
$I386/kernel-source-2.4.18
elif [ $ARCH = "i686" ]; then
rpm $FLGF $I686/kernel-2.4.18-18.8.0
$I386/kernel-BOOT-2.4.18-1
$I686/kernel-bigmem-2.4.18
$I686/kernel-debug-2.4.18-
$I386/kernel-doc-2.4.18-18
$I686/kernel-smp-2.4.18-18
$I386/kernel-source-2.4.18
$I686/kernel-uml-2.4.18-18
elif [ $ARCH = "i586" ]; then
rpm $FLGF $I586/kernel-2.4.18-18.8.0
$I386/kernel-BOOT-2.4.18-1
$I386/kernel-doc-2.4.18-18
$I586/kernel-smp-2.4.18-18
$I386/kernel-source-2.4.18
else
rpm $FLGF $I386/kernel-2.4.18-18.8.0
$I386/kernel-BOOT-2.4.18-1
$I386/kernel-doc-2.4.18-18
$I386/kernel-source-2.4.18
fi
KERNEL=1
fi
rpm $FLGF $I386/Canna-3.5b2-70.8.0.1
$I386/Canna-devel-3.5b2-70
$I386/Canna-libs-3.5b2-70.
rpm $FLGF $I386/fetchmail-5.9.0-21.i
rpm $FLGF $I386/galeon-1.2.6-0.8.0.i
$I386/mozilla-1.0.1-26.i38
$I386/mozilla-chat-1.0.1-2
$I386/mozilla-devel-1.0.1-
$I386/mozilla-dom-inspecto
$I386/mozilla-js-debugger-
$I386/mozilla-mail-1.0.1-2
$I386/mozilla-nspr-1.0.1-2
$I386/mozilla-nspr-devel-1
$I386/mozilla-nss-1.0.1-26
$I386/mozilla-nss-devel-1.
$I386/mozilla-psm-1.0.1-26
rpm $FLGF $I386/ggv-1.99.9-5.i386.rp
rpm $FLGF $I386/gv-3.5.8-19.i386.rpm
rpm $FLGF $I386/kamera-3.0.3-5.i386.
rpm $FLGF $I386/kcoloredit-3.0.3-5.i
rpm $FLGF $I386/kdebase-3.0.3-14.i38
$I386/kdebase-devel-3.0.3-
$I386/kdelibs-3.0.3-8.3.i3
$I386/kdelibs-devel-3.0.3-
$I386/kdenetwork-devel-3.0
$I386/kdenetwork-libs-3.0.
$I386/kdict-3.0.3-3.2.i386
$I386/kdvi-3.0.3-5.i386.rp
$I386/kfax-3.0.3-5.i386.rp
$I386/kfile-pdf-3.0.3-5.i3
$I386/kfile-png-3.0.3-5.i3
$I386/kfract-3.0.3-5.i386.
$I386/kghostview-3.0.3-5.i
$I386/kiconedit-3.0.3-5.i3
$I386/kit-3.0.3-3.2.i386.r
$I386/kmail-3.0.3-3.2.i386
$I386/knewsticker-3.0.3-3.
$I386/knode-3.0.3-3.2.i386
$I386/kooka-3.0.3-5.i386.r
$I386/kpaint-3.0.3-5.i386.
$I386/kpf-3.0.3-3.2.i386.r
$I386/kppp-3.0.3-3.2.i386.
$I386/kruler-3.0.3-5.i386.
$I386/ksirc-3.0.3-3.2.i386
$I386/ksnapshot-3.0.3-5.i3
$I386/ktalkd-3.0.3-3.2.i38
$I386/kuickshow-3.0.3-5.i3
$I386/kview-3.0.3-5.i386.r
$I386/kviewshell-3.0.3-5.i
$I386/kviewshell-devel-3.0
$I386/kxmlrpcd-3.0.3-3.2.i
$I386/lisa-3.0.3-3.2.i386.
rpm $FLGF $I386/korn-3.0.3-3.2.i386.
rpm $FLGF $I386/krb5-devel-1.2.5-7.i
$I386/krb5-libs-1.2.5-7.i3
$I386/krb5-server-1.2.5-7.
$I386/krb5-workstation-1.2
rpm $FLGF $I386/libkscan-3.0.3-5.i38
$I386/libkscan-devel-3.0.3
rpm $FLGF $I386/samba-2.2.7-2.i386.r
$I386/samba-client-2.2.7-2
$I386/samba-common-2.2.7-2
$I386/samba-swat-2.2.7-2.i
rpm $FLGF $I386/tetex-1.0.7-57.1.i38
$I386/tetex-dvips-1.0.7-57
rpm $FLGF $I386/wget-1.8.2-5.i386.rp
rpm $FLGF $I386/xinetd-2.3.7-5.i386.
rpm $FLGF $NOAR/hwdata-0.48-1.noarch
rpm $FLGF $NOAR/kde-i18n-Afrikaans-3
rpm $FLGF $NOAR/kde-i18n-Brazil-3.0.
rpm $FLGF $NOAR/kde-i18n-British-3.0
rpm $FLGF $NOAR/kde-i18n-Catalan-3.0
rpm $FLGF $NOAR/kde-i18n-Chinese-3.0
rpm $FLGF $NOAR/kde-i18n-Chinese-Big
rpm $FLGF $NOAR/kde-i18n-Czech-3.0.3
rpm $FLGF $NOAR/kde-i18n-Danish-3.0.
rpm $FLGF $NOAR/kde-i18n-Dutch-3.0.3
rpm $FLGF $NOAR/kde-i18n-Estonian-3.
rpm $FLGF $NOAR/kde-i18n-Finnish-3.0
rpm $FLGF $NOAR/kde-i18n-French-3.0.
rpm $FLGF $NOAR/kde-i18n-German-3.0.
rpm $FLGF $NOAR/kde-i18n-Greek-3.0.3
rpm $FLGF $NOAR/kde-i18n-Hebrew-3.0.
rpm $FLGF $NOAR/kde-i18n-Hungarian-3
rpm $FLGF $NOAR/kde-i18n-Icelandic-3
rpm $FLGF $NOAR/kde-i18n-Italian-3.0
rpm $FLGF $NOAR/kde-i18n-Japanese-3.
rpm $FLGF $NOAR/kde-i18n-Korean-3.0.
rpm $FLGF $NOAR/kde-i18n-Norwegian-3
rpm $FLGF $NOAR/kde-i18n-Norwegian-N
rpm $FLGF $NOAR/kde-i18n-Polish-3.0.
rpm $FLGF $NOAR/kde-i18n-Portuguese-
rpm $FLGF $NOAR/kde-i18n-Romanian-3.
rpm $FLGF $NOAR/kde-i18n-Russian-3.0
rpm $FLGF $NOAR/kde-i18n-Serbian-3.0
rpm $FLGF $NOAR/kde-i18n-Slovak-3.0.
rpm $FLGF $NOAR/kde-i18n-Slovenian-3
rpm $FLGF $NOAR/kde-i18n-Spanish-3.0
rpm $FLGF $NOAR/kde-i18n-Swedish-3.0
rpm $FLGF $NOAR/kde-i18n-Turkish-3.0
rpm $FLGF $NOAR/kde-i18n-Ukrainian-3
rpm $FLGF $NOAR/squirrelmail-1.2.8-1
if [ $KERNEL -eq 1 ]; then
echo "*************************
echo "* *"
echo "* NOTE: This script updated the kernel! *"
echo "* *"
echo "* Don't forget to adjust /boot/grub/grub.conf to account for *"
echo "* the new kernel. You may also need to create a new *"
echo "* /boot/initrd-2.4.18-18.8.0
echo "* *"
echo "* Also be sure to check the .rpmnew config files for any *"
echo "* adjustments that might be needed for existing services. *"
echo "* *"
echo "*************************
fi
Hi Jim
Just to update you on what is happening with the system. I runed the "rpm -qa" command and it came up with the following items
1. ltmodem-kv_2.4.18.8.0-8.26
2. ltmodem-kv_2.4.18_18.7.x-8
I think this means that I have two sets of packages installed for my modem. I tried then to runed the "grep ltmodem" command, but northing happened. Is there something else I need to add to remove those files from the system?
I thnk you again for all your help.
Bernard
What I meant for you to do was to execute the command:
rpm -qa | grep ltmodem
typed in exactly as shown. But in any case we can see that there are a couple of ltmodem packages installed (neither of which are correct for the kernel you have). So let's remove those with:
rpm -e ltmodem-kv_2.4.18.8.0-8.26
rpm -e ltmodem-kv_2.4.18_18.7.x-8
Then get the updates applied and install the ltmodem-kv_2.4.18_18.8.0-8
Hi Jim
I found myself and external usrobotics faxmodem (sportster 005686-03, model 0701, v.90 56k standard and x2 technology compatible.
I tryied looking for the drivers on the usrobotics website, but did see anything listed. Also, linux and windows 2000 didn't detect the modem, how do I know that the modem is functional. There are also, DIP switches on the back of the modem, should I try to set it? I checked my BIOS and my serial port is enable.
Any help will be most welcome
Bernard
That modem uses a standard "Hayes compatible" command set, so you don't need special drivers to talk to it. The serial port should be ttyS0, so you ought to be able to tell what ever PPP dialer you are using to connect via that port.
Unless someone has used the modem for something wierd, the default swith configuration should be okay.
I did as you said and set my port to ttyS0. I query the modem, but the results came out nill. ATI - ATI7 lines came out with no info. I then tryied to connect to the net, but I only see the window "Initializing Modem..." and it just stays there, northing else happens.
On the modem, the AA, RD, SD, TR, and CS lights all stay light up.
This are my DIP Switch Settings
1 up data terminal ready normal
2 up verbal result codes
3 down display result codes
4 up echo offline commands
5 down auto answer off
6 up carrier detect normal
7 up load NVRAM defaults
8 down smart mode
Hope this will help you in solving the problem.
with thanks
Bernard
I've chased down an identical modem. Your switch settings are correct, but I'm not happy with the modem lights. Until you initiate a call only the CS light should be lit.
Two things to check. Lets make sure we have the correct tty port. You should be able to do:
wilowisp> dmesg | grep tty
ttyS0 at 0x03f8 (irq = 4) is a 16550A
and find a ttyS? device using that I/O port & IRQ. That will be the serial port the modem will connect to. Also make sure that you have the correct cable.
HI Jim
Sad to say, I couldn't execute the command you sent me. The Root Console came back with this message:
bash: wilowisp: command not found
But when I typed : dmesg|grep tty , I got this
ttySO at 0x03f8 (irq=4) is a 16550A
From their I went to the control center and checked my interrupts. Interrupt 4 was not listed. Under IO Ports, I/O Range 03f8-03ff is used by "serial(auto).
I hate to asked this, but what now?
I am really trying to figure this thing out, please help.
"wilowisp>" is the prompt on my laptop, it wasn't meant to be a part of the command.
Okay, it is ttyS0. That's what I thought it should be but it never hurts to make sure.
Are you certain that you have the correct cable?
Do you know for certain that the modem works. You shouldn''t be seeing all of the lights on before a connection is made and it bothers me that it's behaving this way. All of the lights being on make me wonder if the modem is working.
Hi Jim
the cable I have is one that has a serial end that goes to the back of my serial port, and the other end has 25 pins like the end of a parallel cable.
Today, when I puted on the modem I noticed the CS light blinks on occasion. I tryied using the kppp mini-terminal, it tells me that the modem but when I type the commands I see northing on the screen, but the RD, SD, TR, CS lights stay on until I press quit to cancell. Tell me this....when you query the modem, shouldn't you see information about the modem? Why when I query mines, no info is displayed?
Regards
Okay, let me see if I've got this right. With the modem connected and powered on are all the lights lit before you attempt a connection?
If attempt to talk to the modem with minicom, selecting /dev/ttyS0 as the device, will "AT <return>" do anthing, and when talking to it with minicom are all the lights on?
ok
with the modem connected and powered on, all the lights do NOT remain lit. Only the CS light stays lit. when I try to connect 4 lights remain lit, which are CS,TR,SD and RD. those 4 stay lit whiles the modem tries to initialize.
Via kppp mini-terminal, the /dev/ttyS0 device is selected, when I typed AT return, the 4 lights remain lit, but northing happens...I get no response, I don't even see the AT command character I just typed.
Well buddy, hope this info helps.
Yes, that helps a lot in figuring out what is happening.
It sounds like kppp is locked up in some sort of loop talking to the modem, hence the SD/RD lights are fully lit. I'm not real sure at the moment what to tell you to do about that as myself and everybody else around here uses Gnome. I do have KDE on this laptop and I'll look into the setup issues on kppp later and get back to you.
Hi Jim
Guess what? I solved the problem. Actually I got my hands on another external modem, managed to get on to the net and did a redhat network update. I now have the new kernel version "2.4.18-18.8.0". After the update went through, I installed the driver for my internal modem, and it is working just fine. I have one problem that came up. When the redhat Grub loader boots, it now gives me the option of booting into the old 2.4.18-14 kernel. How do I remove this option from the boot menu?
this is what comes up:
Grub version 0.92 (638k lower / 195520k upper memory)
Red Hat linux (2.4.18-18.8.0)
Red Hat Linux (2.4.18-14)
DOS
I only want to have the option of the NEW kernel and DOS.
How do I go about doing that?
Once again, I thank you for all the help you have given me. Talk to you soon,,.....
Bernard
It's is better to keep the option of booting the original kernel, because we know that it works (although the modem doesn't). Think of it as a "back door" that will let you boot the system in the event that some problem were to show up with the newer kernel.
When I update any RedHat box I always retain the distributed kernel that came off the CD's. Later when other kernels are released I'll delete the previous once I'm satified that the new kernel is working okay. Keep in mind that later updates may well include a newer kernel than what you are now running.
My advice is to always keep the distro kernel and the current kernel so that you are always able to boot the system. If you really, really don't want that boot option, edit /boot/grub/grubconf and remove the boot stanza for that kernel.
So are we done with this? If so, please select a comment as the answer and grade it.
Business Accounts
Answer for Membership
by: jleviePosted on 2002-12-09 at 12:59:37ID: 7556292
The first thing I'd suggest is to bring your 8.0 system up to date w/respect to the RedHat errata. That will bring your kernel version up to 2.4.18-8.0. Then check to see what ltmodem packages the system thinks are installed (rpm -qa | grep ltmodem) and remove them.
An A21 should be using the i686 kernel, so I'd go for ltmodem-kv_2.4.18_18.8.0-8