Messages in this thread |  | | From | Michael Nelson <> | Date | Wed, 13 Nov 1996 03:16:43 -0800 (PST) | Subject | Re[2]: 2.1.8 problems |
| |
"Theodore Y. Ts'o" <tytso@MIT.EDU> wrote: > > Could people who are reporting "serial problems" with Linux report such > problems to linux-kernel with much greater detail? i.e., what version > were you using before (where things were working), and what was the > first kernel version that you upgraded to that started failing.
I did, in my initial report. You must have missed it. Anyway, it worked fine with 2.1.6 and 2.0.25, failed under 2.1.8 and 2.1.9. 2.1.7 had other problems (oopsed every few minutes), but the serial/ppp stuff worked ok in that version.
> What UART do you have in your system?
16550AFN
> What UART was detected in the bootup messages?
16550A
> What application were you using, and how did you determine that "half the > characters are getting through"?
Using "chat" to establish a ppp session:
A NORMAL chat session under 2.1.6 looks like this: ==================================================
Nov 12 16:55:06 seahunt chat[114]: abort on (BUSY) Nov 12 16:55:06 seahunt chat[114]: abort on (ERROR) Nov 12 16:55:06 seahunt chat[114]: abort on (NO CARRIER) Nov 12 16:55:06 seahunt chat[114]: timeout set to 90 seconds Nov 12 16:55:06 seahunt chat[114]: send (ATDT9999999^M) Nov 12 16:55:06 seahunt chat[114]: expect (CONNECT) Nov 12 16:55:25 seahunt chat[114]: ATDT9999999^M^M Nov 12 16:55:25 seahunt chat[114]: CONNECT -- got it Nov 12 16:55:25 seahunt chat[114]: send (^M) Nov 12 16:55:25 seahunt chat[114]: expect (ession) Nov 12 16:55:25 seahunt chat[114]: 28800/ARQ/VFC/LAPM/V42BIS^M Nov 12 16:55:27 seahunt chat[114]: ^M Nov 12 16:55:27 seahunt chat[114]: Press <RETURN> to begin Login Session -- got it Nov 12 16:55:27 seahunt chat[114]: send (login_id^M) Nov 12 16:55:27 seahunt chat[114]: expect (word:) Nov 12 16:55:27 seahunt chat[114]: login_id^M Nov 12 16:55:27 seahunt chat[114]: Password: -- got it Nov 12 16:55:27 seahunt chat[114]: send (password^M)
A FAILING chat session under 2.1.8 and 2.1.9 looks like this: =============================================================
Nov 12 16:48:02 seahunt chat[290]: abort on (BUSY) Nov 12 16:48:02 seahunt chat[290]: abort on (ERROR) Nov 12 16:48:02 seahunt chat[290]: abort on (NO CARRIER) Nov 12 16:48:02 seahunt chat[290]: timeout set to 90 seconds Nov 12 16:48:02 seahunt chat[290]: send (ATDT9999999^M) Nov 12 16:48:02 seahunt chat[290]: expect (CONNECT) Nov 12 16:48:20 seahunt chat[290]: ATDT9999999^M Nov 12 16:48:20 seahunt chat[290]: CONNECT -- got it Nov 12 16:48:20 seahunt chat[290]: send (^M) Nov 12 16:48:20 seahunt chat[290]: expect (ession) Nov 12 16:48:22 seahunt chat[290]: 28800/^M Nov 12 16:49:50 seahunt chat[290]: Press <RETUR> to begin Logi (notice the difference in the above lines and the ones that worked succesfully in the first session above under 2.0.25... these are strings coming IN from the modem, and they are incomplete with missing characters) Nov 12 16:49:50 seahunt chat[290]: alarm Nov 12 16:49:50 seahunt chat[290]: Failed
After reading Alain's note about adding "uart 16550A" to the invocation of setserial, I tried 2.1.9 again... now it works, now the chat session looks exactly like the one above shown for 2.1.6.
I have had the same rc.serial for a couple years now and never had to use the "uart 16550A" switch for setserial before, but apparently it is necessary under 2.1.8 and 2.1.9.
Michael
-- Michael Nelson nelson@seahunt.imat.com San Francisco, CA michaeln@csd.sgi.com
|  |