From: David Lang <david.lang@digitalinsight.com>
To: Bob Chiodini <robert.chiodini-1@ksc.nasa.gov>
Cc: linux-kernel@vger.kernel.org
Subject: Re: serial console on x86
Date: Fri, 5 Sep 2003 01:12:32 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0309050109110.19320-100000@dlang.diginsite.com> (raw)
In-Reply-To: <1062700460.16972.9.camel@tweedy.ksc.nasa.gov>
On Thu, 4 Sep 2003, Bob Chiodini wrote:
>
> On Thu, 2003-09-04 at 12:45, David Lang wrote:
> > I am attempting to install linux (debian 3 based) on some dual athlon
> > boxes with no video card. The BIOS does include serial console
> > capabilities
> >
> > once the system is installed I have no problem booting from the hard
> > drive, but when I attempt to boot from a CD to install (ISOLINUX custom
> > boot disk) I see the lilo prompt, the loading kernel message, the loading
> > initrd.gz message and then it prints 'Ready.' and reboots the same
> > bootdisk will work just fine if I install a video card in the machine (and
> > the same kernel with lilo boots just fine without a video card after it
> > gets installed)
> >
> > any ideas why the kernel may crash before printing any messages in this
> > situation? I've tried this with 2.4.17 and 2.4.22 with the exact same
> > results.
> >
> > David Lang
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
>
> David,
>
> Do you have a SERIAL directive in your syslinux.cfg (or ISOLINUX
> equivalent) file on the boot CD?
>
> Per the Syslinux readme.doc:
>
>
> SERIAL port [[baudrate] flowcontrol]
>
> I have been using:
>
> serial 0 38400 0x003
>
> on an embedded system, booting from either a CompactFlash or
> DiskOnChip.
>
> My flowcontrol parm is:
>
> 0x001 - Assert DTR + 0x002 - Assert RTS for a NULL modem cable.
>
> The port number corresponds to ports detected by the BIOS.
>
I haven't tried the serial directive yet (in the past I've been able to
get things to work with just the console=ttyS0 on the append line)
I'll give this a try tomorrow.
David Lang
prev parent reply other threads:[~2003-09-05 8:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-04 16:45 David Lang
2003-09-04 17:09 ` Richard B. Johnson
2003-09-04 17:24 ` David Lang
2003-09-04 18:03 ` Richard B. Johnson
2003-09-04 18:34 ` Bob Chiodini
2003-09-05 8:12 ` David Lang [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.44.0309050109110.19320-100000@dlang.diginsite.com \
--to=david.lang@digitalinsight.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robert.chiodini-1@ksc.nasa.gov \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®