> Date: Wed, 3 Apr 2013 14:08:20 +0100 > From: Stuart Henderson <s...@spacehopper.org> > > moving this to tech@ - original message with dmesg is at > http://marc.info/?l=openbsd-misc&m=136498447228598&w=2 - summary: > asus P8H77-M, intel 7 series chipset, "Intel HD Graphics 3000" > running i386 or amd64, fails during boot with recent kernels unless > inteldrm disabled.
/var/log/Xorg.0.log, from before you upgraded the machine, might provide us some clues. And defenitely also provide pcidump -vxx output. But ultimately having serial console output is pretty much a requirement for being able to debug this properly. > On 2013/04/03 07:54, Vijay Sankar wrote: > > Quoting Stuart Henderson <s...@spacehopper.org>: > > > > >On 2013-04-03, Vijay Sankar <vsan...@foretell.ca> wrote: > > >>The following system runs -current from January 2013 without any > > >>problems. But attempts to install from the past few snapshots have > > >>failed. > > >> > > >>Installation of April 2, 2013 -current went through without any issues > > >>but upon first reboot, the console was blank, I could not access the > > >>system using SSH and it does not respond to pings. > > > > > >How far do you get before the console goes blank, does the kernel start > > >and print text, and then go blank part-way through booting? > > > > > >To help narrow things down, do you get further if at the boot loader > > >you do this: > > > > > >boot -c > > >disable inteldrm > > >quit > > > > > >It looks like there is a header for a serial port on the motherboard, > > >if you have a connector somewhere and can hook it up via null modem to > > >another machine you might get more information (e.g. if it panics while > > >switching video mode you'll be able to get a trace). > > > > > > > > > > Thank you so much. That was exactly it. For the past two days, I was > > poring through all the messages re. UEFI boot and so on and was going > > in the wrong direction. Once I disabled inteldrm I am able to use the > > system now without any problems. > > > > Not sure whether this is worthy of your time but if there are any > > logs or debug information I can provide, I will be happy to do that. > > > > Thanks again, > > > > Vijay > > The most useful thing if it's possible (short of getting a system to > a developer working in this area), would probably be to get a serial > console on the machine and capture a boot log with "option DRMDEBUG" > in kernel config. Though maybe someone on tech@ will have an idea of > something else to try. > >
