View previous topic :: View next topic |
Author |
Message |
micheloe n00b
Joined: 24 Oct 2004 Posts: 13
|
Posted: Sun Oct 31, 2004 1:25 pm Post subject: kernel (2.6.7) boot messages garbled on serial ... [SOLVED] |
|
|
Hello,
I'm using a serial console on my Ultra-10. Almost everything works OK: I'm seeing the OBP messages as well as the SILO boot prompt. But as soon the kernel should be displaying boot messages, I only get garbled messages on the screen. As soon as init starts, everything is fine again. Also, agetty is running fine on the serial console. This is what it looks like:
Code: |
Boot device: disk File and args:
SILO Version 1.4.8
boot:
Allocated 8 Megs of memory at 0x40000000 for kernel
Loaded kernel version 2.6.7
Remapping the kernel... done.
Booting Linux...
POLB u EEBo rm31. 990/81:5
iu eso .. ro@co)(c eso .. 0463(etoLnx334)# o c 50:25 ET20
RH U4
tentades 80:0c:19
<cutting most of the garbled output here>
ET-s NO eoeyrqie nraol ieytm
X3f:wieacs ilb nbe uigrcvr.
koradsatn. omtitra eod
X3f:sa:opa lau nraol s
ET-s d1 rhnioe eee
X3f:rcvr opee
ET-s one ieytmwt ree aamd.
VS one ot(x3flsse)raol.
Mutddvso dv
Gentoo Linux; http://www.gentoo.org/
Copyright 1999-2004 Gentoo Foundation; Distributed under the GPLv2
* Mounting proc at /proc ... [ ok ]
|
It looks as if there's something wrong with the serial console speed, or with the amount of databits/stopbits. I believe many characters are lost. I can rule out the console cable as the "evil part", since I've used it sucessfully with Ultra-2 machines and other Ultra-10 machines (running 2.4 kernels)
Here's the current configuration:
- BootPROM version: OBP 3.19.4 1999/04/28 15:05
- ttya-mode: 38400,8,n,1,-
- kernel append line in silo.conf: "console=tty0 console=ttyS0,38400n8r"
(I also tried omitting the "r" flag; same result)
- Terminal (SecureCRT) settings: 38400 baud, 8 databits, no parity, 1 stopbit
Previously I had it configured for 9600 baud, with the same result. Any clues on this?
I also have an issue with using CTRL-Break / Stop-A after linux is booted. It seems like the sequence is totally ignored, or not arriving at the console session. I tried mapping a totally different key sequence to send the break signal, but no luck. The break signal is working fine before the system is started (I can interrupt the boot sequence to enter the bootprompt). And:
Code: |
# cat /proc/sys/kernel/stop-a
1
|
agetty in the inittab is configured as follows:
Code: |
# SERIAL CONSOLE
c0:12345:respawn:/sbin/agetty -L -f /etc/issueserial 38400 ttyS0 vt100
|
Any clues or hints are greatly appreciated.
Kind regards,
Michel
Last edited by micheloe on Sat Apr 30, 2005 4:51 pm; edited 1 time in total |
|
Back to top |
|
|
micheloe n00b
Joined: 24 Oct 2004 Posts: 13
|
Posted: Sat Apr 30, 2005 4:50 pm Post subject: |
|
|
FYI ("said the schizofrenic guy to himself"...),
I solved this issue today by (finally) installing a new kernel. Yesterday I emerged gentoo-sources-2.6.11-r6 and I've configured this kernel version today. Just rebooted my Ultra10, and the kernel boot messages aren't garbled anymore!
Just checked The CTRL-Break | Stop-A functionality; this works now, too. Now I'm 100% happy with my Gentoo Linux install on my Ultra 10! This makes my life much easier, since my Ultra10 is (co)located elsewhere and wired with a serial connection to another server (in case mine dies...)
Kind regards,
Michel |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|