You don't say that you compiled this new kernel. Did you? Or did you just try to run a binary you found somewhere? It's generally not a good idea, as others have said, to mix and match very much, because you may not get something that works. In any case, the actual reason for the failure is likely just above the kernel oops message. And, isn't Speakup wonderful that you can still read your screen after the computer has crashed? Try that with some other OS. Debee Norling writes: > From: Debee Norling <NorlingDeborah at fhda.edu> > > I have another booting problem but I think it is caused by my > mis-understanding of something. Maybe some of you good explainers can make > this clear for me. > > I thought that the kernel was independent from the software running on a > particular machine. I know that a person runs some distribution, then often > downloads later kernel source, recompiles it and everything is fine. > > I thought I'd start by doing something simpler. I simply tried to boot > Slackware 8 with a speakup-enabled slackware 9 kernel, and later I tried to > use a slackware 8 boot disk after I'd installed 9.1 on my hard disk. In both > cases, I couldn't boot. I got a kernel panic (which speakup read fine.) Why? > > --Debee > > > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup -- Janina Sajka, Director Technology Research and Development Governmental Relations Group American Foundation for the Blind (AFB) Chair, Accessibility Workgroup Free Standards Group (FSG) Email: janina at afb.net Phone: (202) 408-8175
