https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202309
Oliver Pinter <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Ray"@FreeBSD.org, | |[email protected], | |[email protected] See Also| |https://bugs.freebsd.org/bu | |gzilla/show_bug.cgi?id=1940 | |63 CC|Ray"@FreeBSD.org |[email protected] Marcel Moolenaar <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Open CC|[email protected] | Assignee|[email protected] |[email protected] Status|Open |In Progress Douglas King <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] Ed Maste <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] Marcel Moolenaar <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|[email protected] |[email protected] Vaclav Mocek <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from Marcel Moolenaar <[email protected]> --- If I can read the screen correctly, it looks like the resolution is 1366x768, with a stride of 1366 and a color depth of 32 bits per pixel (or 4 bytes per pixel). The console output seems to be using a stride that's just wrong. Since the stride is coming from UEFI, it's hard to think of a reason why the kernel would do this. Have you tried updating the firmware? --- Comment #2 from Oliver Pinter <[email protected]> --- Yes, today I updated to latest bios from HP, but the issue still exists. How could I extract these information without serial port or change the settings in loader or kernel? --- Comment #3 from Marcel Moolenaar <[email protected]> --- Created attachment 160509 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=160509&action=edit loader with 'gop' command --- Comment #4 from Marcel Moolenaar <[email protected]> --- (In reply to Oliver Pinter from comment #2) I committed revision 287299 (-current), that adds a 'gop' command to the loader. I attached a pre-compiled EFI loader with this command to this PR. Can you run 'gop get' and 'gop list' and add the output to this PR? Also: can you try different modes (if possible) and see if that makes a difference? --- Comment #5 from Douglas King <[email protected]> --- Created attachment 162834 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=162834&action=edit BIOS information dmidecode output --- Comment #6 from Douglas King <[email protected]> --- Created attachment 162835 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=162835&action=edit Dmidecode output --- Comment #7 from Douglas King <[email protected]> --- I am having the same issue trying to install on an HP Elitebook 2540p. The error happens at the same point shown in the video except the whole output is "squished" in the top 5-10% of the disply. The display changes with user interaction but none of it is viewable. The text from the boot process remains unaffected. Booting without EFI freezes slightly earlier in the boot. 'gop' only has one mode listed. --- Comment #8 from Oliver Pinter <[email protected]> --- The issue still exists and the same on most recent stable from 2016.01.18. --- Comment #9 from Vaclav Mocek <[email protected]> --- I have the same issue with an older Lenovo Ideapad S205, where during the boot the screen is garbled. I tested the snapshot 10.2-r293802 and 11-r293801, both are failing. I had the same issue with Linux three years back - the video mode was not set correctly even in Grub2 and workaround was to use the option gfxmode, which overwrites the detected values. So, I suspect that the UEFI GOP provides partly incorrect information and the efifb is not set correctly. Unfortunately, I have no clue how to debug these thing on FreeBSD, any hint would be welcomed. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "[email protected]"
