Brian Berrigan <bberrign@renc.igs.net> wrote:
I have been a new Suse user for a year or so, but fairly experienced with computers, now using AMD 2.4G and an internal Conexant HCF56k modem (14F1 1036), on an Asus A7S333 mb with 512 MB ram.
Everything was going well with my dual-boot W98se/Suse 8.0 until the latest Suse kernel security update (0004) and a new driver (4363) for my NVidia GeForce2MX400. Had a lot of problems, sound and modem mostly. I had to go back to Win98 since August '03 to reach Internet. Big frustration...hate M/S arrogant junk.
I goofed: it was wrong to try the NV 4363 (Suse rpm) update using Yast2/Sax2, and not first going into runlevel 3/(no Gui) state. I only saw that warning later! Now my modem won't work despite redoing Yast2 config ( Kinternet logerr: no such dev/modem, but ok in Win98), and re-installing Conexant driver ..beta030427..rpm. My computer works so-so but i'm not sure how to restore it without a complete re-install of 8.0 (or a new 9.0), and thus lose all the patches, updates etc.? I think links got messed up but i'm lost. I could send error logs as needed for any kind help you could offer. My thanks to all the great people on this helpful list. Should i just start over? BrianB.
Brian- my thought is "just starting over" is more than what is required. you need selective "patching" However, you have the problem listed in such broad brush terms, its hard to know where to start. Getting your "modem" to work is probably your first problem to solve (assuming you have xterm, and KDE or gnome working... so what did you do to get your modem to work in the first place ??? __________________________________________________________________ McAfee VirusScan Online from the Netscape Network. Comprehensive protection for your entire computer. Get your free trial today! http://channels.netscape.com/ns/computing/mcafee/index.jsp?promo=393397 Get AOL Instant Messenger 5.1 free of charge. Download Now! http://aim.aol.com/aimnew/Aim/register.adp?promo=380455
GarUlbricht7@netscape.net wrote:
Brian- my thought is "just starting over" is more than what is required. you need selective "patching" > its hard to know where to start. Getting your "modem" to work is probably your first problem to solve ssuming you have xterm, and KDE or gnome working... so what did you do to get your modem to work in the first place ???
Thank you for taking the time to reply. When i bought the box and its internal modem, i got it working online by downloading and installing a driver from the Conant website, set up Kmail and Kinternet and Konqueror, used YaST2 to configure the modem, and all was fine. After i messed up the last update (all prior YOU updates went fine), my modem won't contact my ISP, log shows "ATZ -modem not responding" Now i have tried to rpm -e the same driver, then redone the YaST2 modem config and Kmail, etc, reinstalled the driver with rpm -Uhv <driver>. After an rpm -e, xterm as root first shows "<driver> not installed, then after the rpm -ihv or -Uhv (tried both, separately), it will say "<driver> already installed". But i can't find where it is failing to connect. Hope this explains it better. I will keep trying as i love Suse. Again thanks for any help, BrianB.
On 10/30/2003 12:59 AM, Brian Berrigan wrote:
Now i have tried to rpm -e the same driver, then redone the YaST2 modem config and Kmail, etc, reinstalled the driver with rpm -Uhv <driver>.
IIANM, this may also load a kernel module. rpm -e may delete the file, but won't remove the loaded module. Check with lsmod. If you uninstall the driver, rmmod the module, then try reinstalling. It might help.
After an rpm -e, xterm as root first shows "<driver> not installed, then after the rpm -ihv or -Uhv (tried both, separately), it will say "<driver> already installed".
Maybe it checks the running modules. Just a guess.
But i can't find where it is failing to connect. Hope this explains it better. I will keep trying as i love Suse. Again thanks for any help, BrianB.
Your other message said something about no dev for modem. Send us: ls -l /dev/modem and since this is a link to the actual modem port, ls -l /dev/<dev file modem linked to> -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
Joe Morris (NTM) wrote:
IIANM, this may also load a kernel module. rpm -e may delete the file, but won't remove the loaded module. Check with lsmod. If you uninstall the driver, rmmod the module, then try reinstalling. It might help.
Maybe it checks the running modules. Just a guess.
Your other message said something about no dev for modem. Send us: ls -l /dev/modem and since this is a link to the actual modem port, ls -l /dev/<dev file modem linked to>
Joe Morris, thanks very much for your help...it is appreciated; i know i must learn a lot more to use Suse better, esp the command line. Now my problem is i can only reach you via Win98, and i can't find a way to get the suse 'ls ' files, which you asked to see, from suse to here?? Using Reiserfs which isn't visible to Win?? I can tell you that in ls -l /dev/modem, it shows "/dev/ttyS2 (this last is yellowed!) Pretty sure my modem was put on Com3 by the seller. ls -l /dev/ttyS2 shows 'no such file', going from poor memory?! In lsmod there is nothing showing that has anything to do with a modem. I'll go back to suse and try to rmmod the driver and reinstall it. After that I think i'll try ttyS0 and ttyS1 in case that's the problem. BrianB.
participants (3)
-
Brian Berrigan -
GarUlbricht7＠netscape.net -
Joe Morris (NTM)