Re: SUSE, YaST and dial-up failure

Wed, 10 Nov 2004 16:06:37 -0800 

Fisher, Robert (FXNZ CHC) wrote:

I love this.....

Poster explains his problem, his hardware and OS and all of the details he
thinks are relevant.

Repliers ask more questions which are answered.
A replier (who is really familiar with the particular OS) responds with a
detailed step by step explanation of the problem and the steps to get it
fixed.

What a wonderful world?



Thanks for this post Robert. For some reason Volker's mail hasn't arrived in my inbox. I did manage to get it from http://www.mail-archive.com/[email protected]/msg25777.html though (:


http://www.mail-archive.com/[email protected]/msg25777.html

        From other posts I take it that your kernel got updated, but not your
        modem driver (curse these losemodems). Kernel modules these days usually
        have to be recompiled when there's a kernel change.

good to know, I should have checked before I set off.

> - KInternet will no longer dial and but does not throw any > errors and I have looked at tail -f /var/local/messages without seeing > anything that looked like an error.

        The correct thing to do is to right-click on the kinternet panel applet
        and to select view log. It probably fails after a few lines with a
        /dev/LT... device can't be opened or similar. You could check with lsmod
        whether the lucent module is loaded, I suspect it isn't (which is your
        problem).

There is no error message in the log the final lines are
        local IP address 192.168.99.1
        remote IP address 192.168.99.99

        >    -    kppp says it cannot open the modem but gives no hint as to why

        You should never need to even know kppp exists on a SuSE system.

I ran it in the hope of some light on my problem.\

> The only other error I have is that "/etc/resolv.conf does not exist" > but I don't know if this is relevant!

        Runs as root
        umask 022
        touch /etc/resolv.conf
        to shut up the errors and useless logging.

Thanks, done

        To fix your system, check that the latest kernel and ltmodem are
        kernel-default-2.6.5-7.111
        ltmodem-2.6.2-38.8
        
        (rpm -q kernel-default ltmodem)

this reports
kernel-default-2.6.5-7.111
ltmodem-2.6.2-38.8
as you say above, do I just need to load the module? if so what is the best way 
of doing this?

        If you can get hold of the ltmodem package file by other means (e.g.
        another computer) you can install it with rpm -Uvh ltmodem.....
        and things should start working.

no problem i I do need something, I have a dual boot with the ntfs module 
running

        If you can't get hold of the file, your pretty much only option is to
        downgrade kernel + modem driver to the same level. Copy them both from
        the media into some directory, then run
        rpm -e --nodeps kernel-default ltmodem
        If you use one of the other kernels, adjust commands as necessary.
        Warning do not reboot now - you just deleted all the boot files.
        Install the shipped kernel and driver:
        rpm -Uvh kernel-default-2.6.4-52.i586.rpm ltmodem-2.6.2-36.i586.rpm

I haven't done this yet in the hope of getting the current version running

         Ignore all that bootloader stuff, if lilo needs to be run, installing
        the kernel rpm will run it if necessary (and has done for yonks).
        Reboot just in case. Download both newest kernel and ltmodem (it's
        sufficient to download just the .patch.rpm versions). Install with rpm
        -Uvh ... That should be all.

Is this the now best route or will I end up here again...?

        Always reboot after kernel upgrades.

        Send feedback to SuSE that YOU upgrading the kernel without the ltmodem
        *REALLY SUCKS*.

        Volker

thanks for your help

Andy

Reply via email to