On Thu, November 26, 2015 11:27 am, YASUOKA Masahiko wrote: > On Thu, 26 Nov 2015 11:10:33 -0500 > "Joe Gidi" <j...@entropicblur.com> wrote: >> On Thu, November 26, 2015 10:59 am, YASUOKA Masahiko wrote: >>> On Thu, 26 Nov 2015 09:57:12 -0500 >>> "Joe Gidi" <j...@entropicblur.com> wrote: >>>> On Thu, November 26, 2015 5:20 am, YASUOKA Masahiko wrote: >>>>> On Wed, 11 Nov 2015 15:33:06 -0500 >>>>> "Joe Gidi" <j...@entropicblur.com> wrote: >>>>>> I recently installed a UEFI-capable Asus M5A97 LE R2.0 motherboard >>>>>> in >>>>>> one >>>>>> of my systems and tried to boot the November 11th amd64 >>>>>> miniroot58.fs >>>>>> image to test UEFI booting. I get to the bootloader, but it appears >>>>>> to >>>>>> fail while loading the kernel and goes into a reboot loop. Here's >>>>>> everything I see on screen before it reboots: >>>>>> >>>>>> probing: pc0 mem[640K 2984M 4M 48K 5103M] >>>>>> disk: hd0 hd1 hd2* >>>>>>>> OpenBSD/amd64 EFIBOOT 3.29 >>>>>> boot> >>>>>> cannot open hd0a:/etc/random.seed: No such file or directory >>>>>> booting hd0a:/bsd:3273216+1394144+2409472+0+569344=0x74d238 >>>>> >>>>> I'd like to figure out where the efiboot is stopping. Can you >>>>> replace >>>>> the BOOTX64.EFI in the miniroot58.fs and check the output? >>>> >>>> Sure, I now get these two lines after the 'booting' line: >>>> >>>> GOP setmode failed(7) >>>> Hit any key to reboot >>> >>> The bootloader changs the video resolution before start the kernel. >>> It seems to fail. "GOP", Graphic Output Protocol, returns an error. >>> 7 means EFI_DEVICE_ERROR. >>> >>>> Please let me know if I can do any further testing, and thank you for >>>> looking into this. >>> >>> Can you provide the result of "machine video" and try to change the >>> video mode to the best and some others. >>> >>> >>> And also please try the diff below. >> >> This appears to fix it. I did not have to change the video mode. Output >> from the bootloader: > > UEFI seems to have refused changing the video mode since it > isn't to change. > > Can you try this again? (I'd like to verify whether the assumption > above is correct).
Is there something specific you want me to test? With the latest bootloader you provided, the 'machine video' output is still the same: boot> machine video Mode 0: 80 x 25 Mode 1: 80 x 50 Mode 2: 100 x 31 Current Mode = 2 I am able to boot successfully from miniroot.fs and run through a UEFI install as described by jasper@ here: https://blog.jasper.la/openbsd-uefi-bootloader-howto/ The only thing I did differently from his blog post was to use the bootloader you provided, rather than copying in the one from /mnt/usr/mdec. The newly installed system boots successfully, but then it seems to fail to initialize video properly at the end of the boot process. My monitor goes into an endless cycle of trying to sync up. I can ssh in and see this in /var/log/messages: Nov 26 11:45:55 opteron /bsd: root on sd0a (ef051b8fc18f2fbe.a) swap on sd0b dump on sd0b Nov 26 11:45:55 opteron /bsd: ttm_bo_ioremap bus_space_map failed Nov 26 11:45:55 opteron /bsd: drm:pid0:evergreen_init *ERROR* disabling GPU acceleration Nov 26 11:45:55 opteron /bsd: drm:pid0:radeon_bo_unpin *WARNING* 0xffff8000002922c0 unpin not necessary Nov 26 11:45:55 opteron /bsd: drm:pid0:radeon_bo_unpin *WARNING* 0xffff8000002922c0 unpin not necessary Nov 26 11:45:55 opteron /bsd: ttm_bo_ioremap bus_space_map failed Nov 26 11:45:55 opteron /bsd: error: [drm:pid0:radeonfb_create] *ERROR* failed to create fbcon object -12 Nov 26 11:45:55 opteron ntpd[27846]: /var/db/ntpd.drift is empty Nov 26 11:45:55 opteron savecore: no core dump My video card is: radeondrm0 at pci1 dev 0 function 0 "ATI Radeon HD 5450" rev 0x00 drm0 at radeondrm0 radeondrm0: msi And the radeondrm-firmware-20150927 package is installed. Thanks again for all your help. -- Joe Gidi j...@entropicblur.com "You cannot buy skill." -- Ross Seyfried
