Hi, my dmesg and kern.log seem full of info which floods the useful info you requested. I did spot it mentioning initialising OpenFirmware framebuffer driver. Any idea of how to get the whole dmesg output?
Also, I get many copies of this error in kern.log IN from bad port 64 at c014f020 Regards the framebuffer, Interestingly, this does not lock up the fb: ls -1 -R / whereas ls -R / does. Column widths perhaps? append="video=ofonly" appears to have no effect on this lockup so far. Regards, David On Tuesday 17 February 2004 23:39, Benjamin Herrenschmidt wrote: > On Wed, 2004-02-18 at 09:45, David Pye wrote: > > I've rushed ahead and made the change to mine, and it doesn't seem to > > make any difference. > > > > Sometimes a hang on boot, but what DEFINITELY triggers it is doing > > something like ls /dev on a console. From an xterm it's fine, but from > > the console - bang the framebuffer locks solid. The box is still running > > fine though. > > Are you _certain_ you actually tested with video=ofonly ? That is > append=" video=ofonly" in yaboot.conf ? Send me a dmesg log of that > case so I can check if offb is really picking up the display. > > Ben.
