From: "周 锐" <san_blabla@hotmail.com>
To: dwmw2@infradead.org
Cc: linux-mtd@lists.infradead.org
Subject: Re: Why no kernel message on my DOC system?
Date: Sun, 27 Jan 2002 04:00:58 +0000 [thread overview]
Message-ID: <F501VThKL3XUK99tGKp000144c0@hotmail.com> (raw)
Because in /dev/nftla1 there is only kernel image and initrd on it, so I
have not tested to use 'root=/dev/nftla1' on my harddisk. But I do test to
use lilo-mtd on my harddisk and boot from it, the kernel messages came out
and the /proc/cmdline is:
auto BOOT_IMAGE=blabla-doc rw root=100 console=tty0 console=ttyS0,9600n8
On the contrary, if boot from DiskOnChip, the /proc/cmdline is
unrecognizable strings.
>From: David Woodhouse <dwmw2@infradead.org>
>To: "周 锐" <san_blabla@hotmail.com>
>CC: linux-mtd@lists.infradead.org
>Subject: Re: Why no kernel message on my DOC system?
>Date: Sat, 26 Jan 2002 10:45:04 +0000
>
>
>san_blabla@hotmail.com said:
> > I've build up an X86 Linux system using MTD DiskOnChip driver, using
> > serial port as my console. The Linux system can boot form DOC and I
> > can also login into the system, the problem is that I can't see any
> > kernel printk messages. But if I put the same kernel on my harddisk
> > and boot up using harddisk, I can see all kernel messages, still
> > using serial port as my console. my lilo.conf for DOC is:
>
>I suspect it's a LILO problem - when you log in after it's booted from the
>DiskOnChip, what are the contents of /proc/cmdline?
>
>
> > I don't know why it output "invalidate: busy buffer", but as I said
> > before, the DOC can boot up and I can even login.
>
>LILO is asking the kernel to invalidate a buffer of the ramdisk. But on a
>ramdisk, the buffer is the _only_ copy of the data, so it's marked busy
and
>cannot be invalidated. I think this is harmless.
>
>
> > My lilo.conf for my harddisk is :
>
> > The command to put lilo on harddisk is simple: #lilo and the output is
> > normal.
>
>If you boot using LILO on the hard disk, but with 'root=/dev/nftla', do
>you see the console messages then?
>
>
>--
>dwmw2
>
>
>
>______________________________________________________
>Linux MTD discussion mailing list
>http://lists.infradead.org/mailman/listinfo/linux-mtd/
_________________________________________________________________
享用世界上最大的 Web 电子邮件系统 ―― MSN Hotmail。
http://www.hotmail.com/cn
next reply other threads:[~2002-01-27 3:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-27 4:00 周 锐 [this message]
2002-01-28 23:46 ` Why no kernel message on my DOC system? David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2002-01-29 13:06 周 锐
2002-01-29 10:45 周 锐
2002-01-26 10:13 周 锐
2002-01-26 10:45 ` David Woodhouse
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=F501VThKL3XUK99tGKp000144c0@hotmail.com \
--to=san_blabla@hotmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
/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