Ethan Benson wrote: > > On Thu, Feb 15, 2001 at 09:21:48PM -0500, Daniel Jacobowitz wrote: > > On Thu, Feb 15, 2001 at 06:15:31PM -0800, Mike Fedyk wrote: > > > Look in /boot/vmlinux-2.2.17, you'll see. > > > > > > Ethan, what kind of machines need CONFIG_BOOTX_TEXT=n with quik? > > > > At least the 7200, I believe. > > correct, i talked to ben about this recently the problem is the way > this particular feature trys to access the OF framebuffer, on > oldworlds with non-existant or very broken OF video drivers this code > would crash OF. he told me this should be fixed in recent kernels but > i have not tested this. (i don't intend to since the only oldworld i
... > BOOTX_TEXT is a misnomor though, it really doesn't have much to do > with BootX at all. its also not required for either BootX or > non-BootX booting. > Why do we need BOOTX_TEXT in the debian kernel? Is the installer using the debugger? Are these early messages also reported do klogd? If so, I can only see six lines that show up before I get a display on my mac. System.map ... symbols ... device tree ... How does this really help? Does the maintainer use xmon to test anything before it is released? If so, I could understand him wanting to use the exact kernel he had his debugger on... This is obviously creating problems. What's the big reason to have this enabled? Mike
