Hm, sounds to me like you didn't reboot after installing the new kernel,
or you didn't upgrade the ltmodem package at the same time as you
upgraded the kernel. If you use the ltmodem driver, you must always use
the ltmodem package which matches your kernel package. Installing the
updates for both packages and rebooting should however give you a
functional system. If it doesn't, and uninstalling/installing the
ltmodem package fixes it, then that's a good workaround but there's
still something foul. Not enough info for a good bug report though.

Volker


The ltmodem came in with the kernel, I didn't have to make a choice on that one - it installed ltmodem-2.6.2-38.9, the previous was xxx.8 it came down at the same point. I can also assure you that I rebooted as soon as YOU had run the kernel patch. If this looks like being an ongoing issue then I'd love to provide more info, SuSE patches seem to come in pretty regularly - what would be useful? It does seem to be me alone that is having this problem though, which kind of points a finger.

I was just about to send this and then had a thought - my first kernel download was interrupted and then resumed. I think that this one was too - I have a feeling my partner needed to get online so I stopped it and then picked it up again - wouldn't swear that it was during the kernel download but it may well have been. I'll see if I can get a clean run on the next one and see what happens.

Slightly off this topic - do you and the list tend to install a new version, as you installed 9.2 the other day, or continue to patch the old one. Presumably endlessly patching 9.1 won't ever take me to 9.2 and upwards but I'm getting very attached to this system now. Is it an inevitable new install at some point or is there a sensible way to maintain a current system?

Cheers,

Andy

Reply via email to