[SuSE Linux] kppp and modem busy follow-up
I recently re-installed SuSE Linux 6.1 and cannot get kppp to work properly; it always reports that the modem is busy.
My modem is an external model on Com 1, which worked fine with Linux 6.0. I have gone through the same procedure that I did with Linux 6.0, recompiling the kernel to include TCP/IP and PPP and commenting out the lock in /etc/ppp/options.
I have rechecked my kernel settings and recompiled it (again) to no avail, and don't wish to re-install Linux. Does anyone have an idea what my problem is?
As a follow-up to my original message, herewith the answer to the problem and how I got around it. The problem was caused by a serial port conflict, caused by SuSE 6.1 loading its own serial driver as well as the one I compiled into the kernel. The clue was my boot sequence which contained: Configuring serial ports ttyS0 at 0x03fB (irq=4) is a 16550A Serial driver version 4.27 with HUB-6 MANY-PORT MULTIPORT SHARE_IRQ enabled It was the latter driver which was causing the problem. The cure was to rename /lib/modules/2.2.5 to /lib/modules/2.2.5.saved and then to recompile the kernel, followed by make modules and make_modules install. The renaming of the folder removes all the original modules which 6.1 provides automatically and after the make modules_install the new /lib/modules/2.2.5 contains all the modules that I compiled into the kernel. On reboot the serial port worked correctly, and I could access the modem, but had a number of modprobe errors during boot-up The Can't locate module char-major-4 report has been discussed before, and I used the /etc/conf.modules fox for that. I also had a report 'Can't locate module nls_iso8859-1' when I mounted my DOS drives, and cured that by copying the offended modules from the old modules directory. All now seems to be working well. Many thanks for those who responded to my original message. -- Andrew Tuson -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
Hi, On Tue, Jun 01, Andrew Tuson wrote: [...]
The problem was caused by a serial port conflict, caused by SuSE 6.1 loading its own serial driver as well as the one I compiled into the kernel. The clue was my boot sequence which contained:
This is a problem of kernel 2.2.x: It allows you to load some driver as module even when it's already contained in the kernel. In the case of sd_mod this can have much worse effects than with the serial driver ;) We have a quick hack for the serial driver, but are working on a more general solution to the problem (registering drivers or capabilities). For the moment we should maybe add the some hints to the documentation: If you want to recompile your kernel, do a "rpm -e kernmod" before, so there are only the modules around you really need. [...]
Andrew Tuson -o) Hubert Mantel Goodbye, dots... /\\ _\_v
-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
participants (2)
-
andy@forum.demon.co.uk
-
mantel@suse.de