Re: [Xen-devel] RAMDISK: Image too big

Quoting Ian Pratt
>  > Well. I don't see more. I hope it's not due to that I changed
> >
> > printk before
> > "make world" and not before "make dist".
>
> Are you sure the printk change is still there? 'make world' blows away
> and reconstructs the kernel trees.

Yes, it's still there. I'm not sure if I misunderstood: I didn't activate the 
serial console to check for messages. I assumed that console_io refers to any 
console.

I don't want to drive your patience too far. I can arrange myself with 2.4 not 
working on this machine. However, if I can help you finding that bug, I'd be 
happy to do so.
-- 
Marcus


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel

<Prev in Thread]

Current Thread

[Next in Thread>

Previous by Date:

Re: [Xen-devel] Re: BUG: xen-unstable boot stuck after mtrr, Chris Wedgwood

Next by Date:

RE: [Xen-devel] drdb, thomas constans

Previous by Thread:

RE: [Xen-devel] RAMDISK: Image too big, Ian Pratt

Next by Thread:

[Xen-devel] Re: NetBSD port and a couple of remarks, Thorsten Glaser

Indexes:

[Date] [Thread] [Top] [All Lists]