Some time ago I queried this list to find out why kppp failed to dial my
ISP properly when I updated from kernel 2.0.36 to 2.2.1. The symptom was
that kppp got as far as "Initialising Modem" and no further. Wvdial
also failed to find my internal sportster 33k modem (port 0x3e8, irq
7)but minicom could communicate with it. I did have success with x-isp
and 2.2.1 but I prefer kppp and the email from Ryan proved to have the
answer to my problem. I had used the MANUAL /etc/rc.d/serial settings
for all my serial ports and had used 16550 instead of the 16550A
reported by the kernel during the boot. Kernel 2.0.36 was happy with
16550 but not 2.2.1. My system is SuSE 6.0 and kernel 2.2.4. I'm very
happy with it.
I've set the uart to 115200 under kppp and the relevant part of
/etc/rc.d/serial is as follows ...
###############################################################
#
# MANUAL CONFIGURATION
#
# If you want to do manual configuration of one or more of your
# serial ports, uncomment and modify the relevant lines.
#
###############################################################
# These are the standard COM1 through COM4 devices
#
run_setserial /dev/ttyS0 uart 16550A port 0x3F8 irq 4
run_setserial /dev/ttyS1 uart 16550A port 0x2F8 irq 3
run_setserial /dev/ttyS2 uart 16550A port 0x3E8 irq 7
# run_setserial /dev/ttyS3 uart 16450 port 0x2E8 irq 3
Thanks Ryan!
the original uart settings not verified the type
Ryan wrote:
>
> I had a similar problem when I upgraded to kernel 2.2.4
>
> With the old kernel (2.0.36) I had to (at boot time) set my UART to my modem to
> 16550 rather than 16550A, because for some reason if it was at 16550A it ran
> REALLY slow. But it worked great at 16550. When I got the new kernel, I could
> not connect via ppp. And after a week of hair pulling I decided to try UART
> 16550A, and with the new kernel it now works fine!
> This may not be relevant to your problems, but it might help. Try using
> different UARTs. To set different UARTs use 'setserial /dev/modem UART
> xxxxx' -- if you find that this fixes the problem, edit your
> /sbin/init.d/boot.local file and add the setserial line to it. Or you can edit
> /sbin/init.d/serial and add the line at the bottom as well, both methods with
> set your modem to the proper setting at boot time. For my modem I also use
> the spd_vhi flag to set my modem to use the fastest settings. My line in
> /sbin/init.d/boot.local is: 'setserial /dev/modem IRQ 10 UART 16550A
> spd_vhi' .
>
> Good luck!
>
> Later,
> Ryan
> |ceman
>
--
To get out of this list, please send email to [EMAIL PROTECTED] with
this text in its body: unsubscribe suse-linux-e
Check out the SuSE-FAQ at http://www.suse.com/Support/Doku/FAQ/ and the
archive at http://www.suse.com/Mailinglists/suse-linux-e/index.html
