Re: Why no kernel message on my DOC system?

[David Woodhouse <dwmw2@infradead.org>]

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