console handover: boot [ttyB0] -> real [ttyS0]
Hi,
it is the first time I'm trying to install Linux on HP9000 rp3410 machine. I'm booting off Debian 5.0.3 CD, PALO selects 64bit kernel, later on the kernel detects ttyS0 but the console output stops at:
PDC Stable Storage facility v0.30
STI GSC/PCI core graphics driver Version 0.9a
Generic RTC Driver v1.07
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled 0000:e0:01.0: ttyS0 at MMIO 0xfffffffff4051000 (irq = 74) is a 16550A console handover: boot [ttyB0] -> real [ttyS0]
<that's it>
I tried to pass serial=ttyS0 to the kernel but then the output stops a wee while later as well:
STI GSC/PCI core graphics driver Version 0.9a
Generic RTC Driver v1.07
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled 0000:e0:01.0: ttyS0 at MMIO 0xfffffffff4051000 (irq = 74) is a 16550A 0000:e0:01.1: ttyS1 at MMIO 0xfffffffff4050000 (irq = 74) is a 16550A 0000:e0:01.1: ttyS2 at MMIO 0xfffffffff4050010 (irq = 74) is a 16550A 0000:e0:01.1: ttyS3 at MMIO 0xfffffffff4050038 (irq = 74) is a 16550A
brd: module loaded
mice: PS/2 mouse device common for all mice
TCP cubic registered
NET: Registered protocol family 17
turn off boot console ttyB0
<that's it>
I'm connected over serial to MP and using COnsole from there.
What am I doing wrong / how to make it work?
Thanks!
Michal
Quoted 1 line · Michal Ludvig
Hi,
Hi,
Quoted 2 lines
I tried to pass serial=ttyS0 to the kernel but then the output stops a wee while later as well:
Try ttyS1
HTH
Signature · 2 lines
Thibaut VARENE http://www.parisc-linux.org/~varenet/
Quoted 5 lines · Thibaut VARENE
Quoted 2 lines · Michal Ludvig
I tried to pass serial=ttyS0 to the kernel but then the output stops a wee while later as well:
Try ttyS1
That's it, thanks!
Now I'm a bit confused - where are all the serial ports? I've got 'remote', 'console' and 'ups' pigtails hanging off the back of the server. Are they all usable as ttySx? Is there one more port hidden somewhere?
Is it configurable which one of ttyS0 - ttyS3 turns the ttyB0 boot console to?
Michal
Quoted 5 lines · Michal Ludvig
Quoted 4 lines · Thibaut VARENE
Quoted 2 lines · Michal Ludvig
I tried to pass serial=ttyS0 to the kernel but then the output stops a wee while later as well:
Quoted 8 lines
Quoted 1 line
Try ttyS1
That's it, thanks!
Now I'm a bit confused - where are all the serial ports? I've got 'remote', 'console' and 'ups' pigtails hanging off the back of the server. Are they all usable as ttySx? Is there one more port hidden somewhere?
This should answer your question:
http://wiki.parisc-linux.org/GuardianServiceProcessor
Quoted 2 lines
Is it configurable which one of ttyS0 - ttyS3 turns the ttyB0 boot console to?
I'm not sure I can make sense of that question. At boot time you can choose which physical port you want to hook your cable to (provided it's a console port, see the above link) and it's then up to you to make sure that you tell the kernel which UART you're connected to.
rp34xx machines' first ("default") console port is detected by the linux kernel as ttyS1, this is due to inner workings of the kernel and you have no control over that.
Signature · 2 lines
Thibaut VARENE http://www.parisc-linux.org/~varenet/
On Tue, Dec 15, 2009 at 12:39:06PM +1300, Michal Ludvig wrote:
...
Quoted 2 lines
Is it configurable which one of ttyS0 - ttyS3 turns the ttyB0 boot console to?
ttyB0 is the "PDC Console" device name - linux kernel is using PDC to push characters to the device defined in PDC (aka BIOS) to be console. Interrupt the autoboot process and look at "in all".
ttyS0-ttyS3 are enumerations of Serial devices that the linux kernel discovers when respective drivers are loaded. ttyB0 and ttyS<n> are just different drivers accessing the same HW - preferably not at the same time and that's why the kernel stops using ttyB0 later.
That make more sense?
grant
Quoted 9 lines · Grant Grundler
On Tue, Dec 15, 2009 at 12:39:06PM +1300, Michal Ludvig wrote:
...Quoted 2 lines
Is it configurable which one of ttyS0 - ttyS3 turns the ttyB0 boot console to?
ttyB0 is the "PDC Console" device name - linux kernel is using PDC to push characters to the device defined in PDC (aka BIOS) to be console. Interrupt the autoboot process and look at "in all".
Quoted 6 lines
ttyS0-ttyS3 are enumerations of Serial devices that the linux kernel discovers when respective drivers are loaded. ttyB0 and ttyS<n> are just different drivers accessing the same HW - preferably not at the same time and that's why the kernel stops using ttyB0 later.
That make more sense?
Yes it does :-) Thanks!
Michal