not an idea really but further experience Since LiveDvD-10.1 boots, albeit buggily, on the netbook. I tried to use the kernel config provided with it. I ran make oldconfig then opened up the menu and whittled away the extraneous modules, built the new kernel, installed it and rebooted. This time, after a flurry of red exclamation points, it reached the login and crashed there.
Is it feasible that I should go back in and compile in that kernel log option, what's it called? Then after it crashes, reboot into the working kernel, and see if that log has been created? Hey, I guess that counts as an idea :) BTW, the major problem with the LiveDvD is the tendency for the syslog(?) console to bleed into all the other consoles -- messages just popped onto the screen. mw On 10/23/09, walt <w41...@gmail.com> wrote: > On 10/22/2009 04:31 PM, walt wrote: >> On 10/21/2009 11:25 AM, Maxim Wexler wrote: > >>> The kernel panicked. The relevant messages are: >>> >>> <...> >>> VFS: Mounted root (ext2 filesystem) readonly on device 8:1, >>> Freeing unused kernel memory: 276k freed >>> Warning: unable to open an initial console > >> ...I don't know if that warning is important. > > Apparently it is important. I just discovered /var/log/kern.log, > which logs things that happen even before / is mounted. > > Here is the relevant part: > > Oct 23 08:18:39 k2 kernel: EXT3-fs: mounted filesystem with writeback data > mode. > Oct 23 08:18:39 k2 kernel: VFS: Mounted root (ext3 filesystem) readonly on > device 8:7. > Oct 23 08:18:39 k2 kernel: Freeing unused kernel memory: 256k freed > Oct 23 08:18:39 k2 kernel: kjournald starting. Commit interval 5 seconds > Oct 23 08:18:39 k2 kernel: udev: starting version 141 > > No such warning for me. The question is why not? Any ideas? > > >
