On Tue, Aug 29, 2006 at 11:15:49PM +0200, Geert Stappers wrote: > On Tue, Aug 29, 2006 at 05:58:17PM +0200, Sven Luther wrote: > > Package: debian-installer > > Severity: normal > <snip/> > > Attached is the full serial log. > <snip/> > > [boot]0015 Setup Done > > Built 1 zonelists > > Kernel command line: console=hvsi0 console=hvc0 console=ttyS0,9600 > > console=tty0 > > Why four consoles?
because if you install on a virtualized partition, it will be hvc0, while if you install directly, like i do, it will be hvsi0, no idea what the serial console is on powermacs (the Xserve G5 actually have a serial console), and tty0 is for the real console. > How knows the kernel which one to use? the kernel will output to all of those existing, while the interactive one being the last one. Since i have not yet seen a case where hvsi0, hvc0 and ttyS0 are present at the same time, this works just fine. Obviously, the p505 lacking a graphical output, tty0 is also not existent. I can't say this is the most smart thing to do, the kernel guys must have been smoking something serious when they decided to name the serial devices in a thousand different ways. I had to resort to that since the p505 firmware is not able to add bootargs on the commandline when using a zimage, and the above is what the 2.6.17 powerpc64 kernels has as default commandline. > <snip/> > > Intel(R) PRO/1000 Network Driver - version 7.0.33-k2-NAPI > > Copyright (c) 1999-2005 Intel Corporation. > > ehci_hcd 0000:c8:01.2: irq 323, io mem 0x40070002000 > > ehci_hcd 0000:c8:01.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004 > > usb usb1: configuration #1 chosen from 1 choice > > hub 1-0:1.0: USB hub found > > hub 1-0:1.0: 5 ports detected > > ohci_hcd 0000:c8:01.0: OHCI Host Controller > > ohci_hcd 0000:c8:01.0: new USB bus registered, assigned bus number 2 > > ohci_hcd 0000:c8:01.0: irq 323, io mem 0x40070001000 > > usb usb2: configuration #1 chosen from 1 choice > > hub 2-0:1.0: USB hub found > > hub 2-0:1.0: 3 ports detected > > ohci_hcd 0000:c8:01.1: OHCI Host Controller > > ohci_hcd 0000:c8:01.1: new USB bus registered, assigned bus number 3 > > ohci_hcd 0000:c8:01.1: irq 323, io mem 0x40070000000 > > usb usb3: configuration #1 chosen from 1 choice > > hub 3-0:1.0: USB hub found > > hub 3-0:1.0: 2 ports detected > > e1000: 0000:c0:01.0: e1000_probe: (PCI-X:133MHz:64-bit) 00:11:25:7e:2c:d6 > > e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection > > e1000: 0000:c0:01.1: e1000_probe: (PCI-X:133MHz:64-bit) 00:11:25:7e:2c:d7 > > e1000: eth1: e1000_probe: Intel(R) PRO/1000 Network Connection > > > > -- System Information: > > Debian Release: testing/unstable > > > I wonder why serial output dies there, as I see no reason "to switch console" Indeed. Do you have an idea of what comes next ? And who is doing the above output ? I thought it was coldplug, but since enabling set -x and various debug doesn't help, these outputs probably come from the kernel messages directly. I guess the console is directed to somewhere random, and thus not shown. What is strange is that when doing the same on a JS21 blade in a blade center, it works just fine, so something funny is going on here. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
