public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
* Why no kernel message on my DOC system?
@ 2002-01-26 10:13 周 锐
  2002-01-26 10:45 ` David Woodhouse
  0 siblings, 1 reply; 6+ messages in thread
From: 周 锐 @ 2002-01-26 10:13 UTC (permalink / raw)
  To: linux-mtd

Hello,everyone.

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:

boot=/dev/nftla
map=/boot/map
install=/boot/boot.b-mtd
default=doc-full
serial=0,9600n8
image=/boot/bzImage-2.4.17
        label=doc
        root=/dev/ram0
        read-write
        initrd=/boot/initrd.img.gz
        append="console=ttyS0,9600n8"
image=/boot/bzImage-2.4.17-full
        label=doc-full
        root=/dev/ram0
        read-write
        initrd=/boot/initrd.img.gz
        append="console=ttyS0,9600n8"

The command to put lilo on it and the output is:

#mount /dev/nftla1 /mnt
#cd /mnt
#rdev boot/bzImage-2.4.17-full /dev/ram0
#lilo-mtd -v -C lilo.conf -r /mnt
Patched LILO for M-Systems' DiskOnChip 2000
LILO version 21, Copyright 1992-1998 Werner Almesberger

Reading boot sector from /dev/nftla
Warning: /dev/nftla is not on the first disk
Merging with /boot/boot.b-mtd
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
Setting DELAY to 20 (2 seconds)
Boot image: /boot/bzImage-2.4.17
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
Mapping RAM disk /boot/initrd.img.gz
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
Added doc
Boot image: /boot/bzImage-2.4.17-full
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
Mapping RAM disk /boot/initrd.img.gz
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
invalidate: busy buffer
Added doc-full *
/boot/boot.5D00 exists - no backup copy made.
Writing boot sector.

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.

My lilo.conf for my harddisk is :

boot=/dev/hda
map=/boot/map
install=/boot/boot.b
default=linux
serial=0,9600n8
image=/boot/bzImage-2.4.17-full
        label=linux
        root=/dev/hda1
        read-only
        append = "console=ttyS0,9600n8"

The command to put lilo on harddisk is simple:
#lilo
and the output is normal.

Another question, how could I choose boot image when I use lilo on the 
serial port? Sending Ctrl+a f in minicom and do what else?


_________________________________________________________________
与联机的朋友进行交流，请使用 MSN Messenger：
http://messenger.microsoft.com/cn

^ permalink raw reply	[flat|nested] 6+ messages in thread
* Re: Why no kernel message on my DOC system?
  2002-01-26 10:13 周 锐
@ 2002-01-26 10:45 ` David Woodhouse
  0 siblings, 0 replies; 6+ messages in thread
From: David Woodhouse @ 2002-01-26 10:45 UTC (permalink / raw)
  To: 周 锐; +Cc: linux-mtd

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

^ permalink raw reply	[flat|nested] 6+ messages in thread
* Re: Why no kernel message on my DOC system?
@ 2002-01-27  4:00 周 锐
  2002-01-28 23:46 ` David Woodhouse
  0 siblings, 1 reply; 6+ messages in thread
From: 周 锐 @ 2002-01-27  4:00 UTC (permalink / raw)
  To: dwmw2; +Cc: linux-mtd

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

^ permalink raw reply	[flat|nested] 6+ messages in thread
* Re: Why no kernel message on my DOC system?
  2002-01-27  4:00 周 锐
@ 2002-01-28 23:46 ` David Woodhouse
  0 siblings, 0 replies; 6+ messages in thread
From: David Woodhouse @ 2002-01-28 23:46 UTC (permalink / raw)
  To: 周 锐; +Cc: linux-mtd

san_blabla@hotmail.com said:
>  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. 

It's a LILO problem. Why are you installing LILO to /dev/ram0 instead of 
/dev/nftla? Won't that make it look in the wrong place for stuff?

--
dwmw2

^ permalink raw reply	[flat|nested] 6+ messages in thread
* Re: Why no kernel message on my DOC system?
@ 2002-01-29 10:45 周 锐
  0 siblings, 0 replies; 6+ messages in thread
From: 周 锐 @ 2002-01-29 10:45 UTC (permalink / raw)
  To: dwmw2; +Cc: linux-mtd

Because I want to use an initrd as my root device so that I can put more 
things in the fiel system. Below is my lilo.conf:

boot=/dev/nftla 
map=/boot/map 
install=/boot/boot.b-mtd 
default=doc-full 
serial=0,9600n8 
image=/boot/bzImage-2.4.17 
       label=doc 
       root=/dev/ram0 
       read-write 
       initrd=/boot/initrd.img.gz 
       append="console=ttyS0,9600n8" 
image=/boot/bzImage-2.4.17-full 
       label=doc-full 
       root=/dev/ram0 
       read-write 
       initrd=/boot/initrd.img.gz 
       append="console=ttyS0,9600n8"

So I think I am installing LILO on /dev/nftla, only use /dev/ram0 to mount 
my root file system.


>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: Mon, 28 Jan 2002 23:46:14 +0000
>
>
>san_blabla@hotmail.com said:
> >  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.
>
>It's a LILO problem. Why are you installing LILO to /dev/ram0 instead of
>/dev/nftla? Won't that make it look in the wrong place for stuff?
>
>--
>dwmw2
>
>


_________________________________________________________________
与联机的朋友进行交流，请使用 MSN Messenger：
http://messenger.microsoft.com/cn

^ permalink raw reply	[flat|nested] 6+ messages in thread
* Re: Why no kernel message on my DOC system?
@ 2002-01-29 13:06 周 锐
  0 siblings, 0 replies; 6+ messages in thread
From: 周 锐 @ 2002-01-29 13:06 UTC (permalink / raw)
  To: dwmw2; +Cc: linux-mtd

I am considering to use GRUB as my bootloader instead of LILO, but I didn't 
find out any detailed documentation about how to do this, can anyone give 
me some instructions or where can I find a document about this.

My DiskOnChip is DOC Mellennium MD-2810-D08.


>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: Mon, 28 Jan 2002 23:46:14 +0000
>
>
>san_blabla@hotmail.com said:
> >  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.
>
>It's a LILO problem. Why are you installing LILO to /dev/ram0 instead of
>/dev/nftla? Won't that make it look in the wrong place for stuff?
>
>--
>dwmw2
>
>
>
>______________________________________________________
>Linux MTD discussion mailing list
>http://lists.infradead.org/mailman/listinfo/linux-mtd/


_________________________________________________________________
与联机的朋友进行交流，请使用 MSN Messenger：
http://messenger.microsoft.com/cn

^ permalink raw reply	[flat|nested] 6+ messages in thread
end of thread, other threads:[~2002-01-29 12:56 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-01-29 10:45 Why no kernel message on my DOC system? 周 锐
  -- strict thread matches above, loose matches on Subject: below --
2002-01-29 13:06 周 锐
2002-01-27  4:00 周 锐
2002-01-28 23:46 ` David Woodhouse
2002-01-26 10:13 周 锐
2002-01-26 10:45 ` David Woodhouse

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox