Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 133457 - Automated attempts at booting using serial console fails
Summary: Automated attempts at booting using serial console fails
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Release Media
Classification: Unclassified
Component: Everything (show other bugs)
Hardware: Alpha Linux
: High normal (vote)
Assignee: Alpha Porters
URL:
Whiteboard:
Keywords: InVCS
Depends on:
Blocks:
 
Reported: 2006-05-16 02:23 UTC by Stormy
Modified: 2006-09-01 14:12 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stormy 2006-05-16 02:23:17 UTC
Hello, 

Klorei on freenode asked me to post this.

First off the machine: API Networks CS20 Dual 833 Mhz EV68AL cpu's 2gb/ram

With this machine the only real option I get is serial connection.  With that and the right communication settings it drops me in to the SRM console. from the SRM console you are supposed to be able to type boot (device in my case dqb0) -flags "0 console=ttyS0" and, boot the first kernel option passing console=ttyS# into the  kernel configuration options.  Which is it not.  That option I just showed above infact boots the kernel option "0", but does not pass the console message along with it.  Other options such as boot dqb0 -flags "console=ttyS0", bring you into the aboot console.  Even in the aboot console you type l for listing of the options, and it plainly says right there, that you should list your kernel option number, then any args you have after it. for example: 0 console=ttyS0, or 0 "console=ttyS0", both times neither one passes and I still get the frame buffer.

Needless to say ish broken.

Current work around solution that I have found is to get into aboot, hit b for custom boot, pick the gentoo kernel/path that you want to use, put console=ttyS0 then append the rest of that options parameters upon the line.  That boots correctly.
Comment 1 Thomas Cort (RETIRED) gentoo-dev 2006-06-13 18:00:56 UTC
I looked at the debian install CD to see how they handled this. They have a separate boot flag for serial console. Maybe the 2006.1 live cd could have a configuration like this:

0:/boot/gentoo initrd=/boot/gentoo.igz root=/dev/ram0 init=/linuxrc dokeymap looptype=zisofs loop=/zisofs cdroot
1:/boot/gentoo2.4 initrd=/boot/gentoo2.4.igz root=/dev/ram0 init=/linuxrc  dokeymap looptype=zisofs loop=/zisofs cdroot 
2:/boot/gentoo console=ttyS0 initrd=/boot/gentoo.igz root=/dev/ram0 init=/linuxrc dokeymap looptype=zisofs loop=/zisofs cdroot
3:/boot/gentoo2.4 console=ttyS0 initrd=/boot/gentoo2.4.igz root=/dev/ram0 init=/linuxrc dokeymap looptype=zisofs loop=/zisofs cdroot 

Then someone could enable serial console just by using "boot [CD-ROM] -flags 2" or "boot [CD-ROM] -flags 3".
Comment 2 Chris Gianelloni (RETIRED) gentoo-dev 2006-06-14 07:38:48 UTC
That works for me.  Kloeri, what do you think?  I can add the serial options to catalyst, so it'll all be automatic for you for 2006.1... =]
Comment 3 Bryan Østergaard (RETIRED) gentoo-dev 2006-06-14 09:29:49 UTC
No problem with that.
Comment 4 Chris Gianelloni (RETIRED) gentoo-dev 2006-06-15 15:19:58 UTC
I've added this into the catalyst CVS, so it'll show up in 2.0_rc48.
Comment 5 Chris Gianelloni (RETIRED) gentoo-dev 2006-09-01 14:12:14 UTC
FIXED in 2006.1's release.