On Wednesday 25 October 2006 06:34, you wrote: > On Wed, Oct 25, 2006 at 02:45:46AM -0700, C_Wakefield wrote: > > Thanks for the idea. I just compiled 2.6.18.1 with .config from my only > > running debian kernel: 2.6.16-2-amd64-k8-smp with gcc-4.0 using the > > symlink in /etc/alternatives/gcc. Again, no joy. > > My next, is to use gcc-2.95, but not sure if it that's a good idea, given > > it's age? > > > > What is odd, also, is that debian linux-images: 2.6.18-1-amd64 and > > 2.6.17-2-amd64 won't boot my machine either! > > If you compile 2.6.16 yourself, does that boot? > > Maybe a change in 2.6.17 broke support for your mainboard. > > Which board do you have? Which bios version? What chipset does it use? > > -- > Len Sorensen Just did a "backup" install with the lastest weekly build. Obviously it boots and installs the system, but when you boot as a standalone, it won't boot! The current kernel for etch is vmlinuz-2.6.17-2-amd64.
I've checked the logs, can't find anything like I'm seeing in the first seconds of boot. What I do seeing flying by is what definitely looks like a segfault dump. l don't know what else to do but keep the thread ticking. Chris W. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
