On Tue, Jul 12, 2016 at 01:28:21AM +0200, stolendata.net wrote: > I just managed to get it to boot. The machine is running sort of headless > with only the on-board IGP available, using 32MB of shared memory. I > stepped this setting up in the BIOS to give the IGP 64MB of RAM and i386 > now boots, both the full install as well as the ramdisk kernel. > > If it's of any value, dmesg.boot: http://pastebin.com/raw/ww0ezzed > And sensors: http://pastebin.com/raw/ZZSNk6mG > > Pardon the ANSI codes or whatever the garbage in the dmesg output is. I've > no idea why that shows up in 5.9.
Can you show the output of "machine memory" at the boot> prompt? I'm wondering if this machine has an odd memory layout. (The trash in dmesg was just scribbled memory from a previous boot, linux from the looks of it) -ml > > (I'm mailing these to dmesg@... as well) > > > On Tue, Jul 12, 2016 at 12:32 AM, Mike Larkin <[email protected]> wrote: > > > On Tue, Jul 12, 2016 at 12:30:23AM +0200, stolendata.net wrote: > > > Alright, ddb prompt pops up on i386. Last output from kernel: > > > > > > real mem ... > > > avail mem ... > > > kernel: page fault trap, code=0 > > > Stopped at memcpy+0x13: repe movsl (%esi),%es:(%edi) > > > > in ddb: > > trace > > > > ps > > > > take some pictures and send some links. > > > > > > > > > > If there's any chance you think you can guide me through pulling some > > > valuable info from here and on, I'm game. > > > > > > > >
