Hi,
On Tue, 12 Jul 2016 21:17:20 -0300
Friedrich Locke wrote:
> I wonder if that's possible to boot obsd amd64 5.9 CD on a computer whose
> bios is setted to boot UEFI secure mode off.
5.9 CD doesn't support UEFI boot. If the computer doesn't have legacy
mode BIOS, you need to use an USB memory
On Thu, November 26, 2015 10:13 pm, Jonathan Gray wrote:
> Can you include a full dmesg when booted via uefi with radeondrm
> still enabled? pcidump -v output would be helpful as well.
>
> We may have to read the video bios out of the acpi VFCT table
> when booting via efi and the radeondrm code do
On Thu, Nov 26, 2015 at 11:51:03AM -0500, Joe Gidi wrote:
> 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/m
[big snip]
>> 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 /
On Thu, 26 Nov 2015 11:51:03 -0500
"Joe Gidi" wrote:
> On Thu, November 26, 2015 11:27 am, YASUOKA Masahiko wrote:
>> On Thu, 26 Nov 2015 11:10:33 -0500
>> "Joe Gidi" wrote:
>>> On Thu, November 26, 2015 10:59 am, YASUOKA Masahiko wrote:
On Thu, 26 Nov 2015 09:57:12 -0500
"Joe Gidi" wr
On Thu, November 26, 2015 11:27 am, YASUOKA Masahiko wrote:
> On Thu, 26 Nov 2015 11:10:33 -0500
> "Joe Gidi" wrote:
>> On Thu, November 26, 2015 10:59 am, YASUOKA Masahiko wrote:
>>> On Thu, 26 Nov 2015 09:57:12 -0500
>>> "Joe Gidi" wrote:
On Thu, November 26, 2015 5:20 am, YASUOKA Masahiko
On Thu, 26 Nov 2015 11:10:33 -0500
"Joe Gidi" wrote:
> On Thu, November 26, 2015 10:59 am, YASUOKA Masahiko wrote:
>> On Thu, 26 Nov 2015 09:57:12 -0500
>> "Joe Gidi" wrote:
>>> On Thu, November 26, 2015 5:20 am, YASUOKA Masahiko wrote:
On Wed, 11 Nov 2015 15:33:06 -0500
"Joe Gidi" wro
On Thu, November 26, 2015 10:59 am, YASUOKA Masahiko wrote:
> Hi,
>
> On Thu, 26 Nov 2015 09:57:12 -0500
> "Joe Gidi" wrote:
>> On Thu, November 26, 2015 5:20 am, YASUOKA Masahiko wrote:
>>> On Wed, 11 Nov 2015 15:33:06 -0500
>>> "Joe Gidi" wrote:
I recently installed a UEFI-capable Asus M5A
Hi,
On Thu, 26 Nov 2015 09:57:12 -0500
"Joe Gidi" wrote:
> On Thu, November 26, 2015 5:20 am, YASUOKA Masahiko wrote:
>> On Wed, 11 Nov 2015 15:33:06 -0500
>> "Joe Gidi" wrote:
>>> I recently installed a UEFI-capable Asus M5A97 LE R2.0 motherboard in
>>> one
>>> of my systems and tried to boot t
On Thu, November 26, 2015 5:20 am, YASUOKA Masahiko wrote:
> On Wed, 11 Nov 2015 15:33:06 -0500
> "Joe Gidi" 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
On Wed, 11 Nov 2015 15:33:06 -0500
"Joe Gidi" 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
Thank you for your report and test. Next snapshot will include the fix.
On Mon, 5 Oct 2015 15:35:34 -0500
Brian Conway wrote:
> (Re-adding misc@ for the thrilling conclusion.)
>
> Success! It boots to installer without issue. EFI-enabled dmesg follows.
>
> Thanks again for your work.
>
> Bria
(Re-adding misc@ for the thrilling conclusion.)
Success! It boots to installer without issue. EFI-enabled dmesg follows.
Thanks again for your work.
Brian
OpenBSD 5.8-current (RAMDISK_CD) #1254: Tue Sep 22 19:46:40 MDT 2015
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_C
On Wed, 23 Sep 2015 14:40:52 -0500
Brian Conway wrote:
>> This picture shows
>>
>> Load address: Loader Data (2) 0xd0 for 4096KB FATAL
>>
>> This is what I want to know. 0xd0 + 4M is overlapping the kernel
>> area.
>>
>> I think the following diff or
>>
>> http://yasuoka.net/~yasuoka/
> This picture shows
>
> Load address: Loader Data (2) 0xd0 for 4096KB FATAL
>
> This is what I want to know. 0xd0 + 4M is overlapping the kernel
> area.
>
> I think the following diff or
>
> http://yasuoka.net/~yasuoka/BOOTX64.EFI
> (updated)
>
> will fix the problem.
Great, thanks
On Tue, 22 Sep 2015 14:20:22 -0500
Brian Conway wrote:
>> Can you try the diff following or
>>
>> http://yasuoka.net/~yasuoka/BOOTX64.EFI
>>
>> ? Then enter "machine memory" on "boot> " prompt and check the last line.
>> It shows whether the memory area for kernel is free or not. Like
>>
>>
> Can you try the diff following or
>
> http://yasuoka.net/~yasuoka/BOOTX64.EFI
>
> ? Then enter "machine memory" on "boot> " prompt and check the last line.
> It shows whether the memory area for kernel is free or not. Like
>
> Load address: Conventional(7) 0x for KB
>
> is good sign
Hi,
On Thu, 17 Sep 2015 20:47:22 -0500
Brian Conway wrote:
> The NUC 2820 I was previously testing snapshots with has moved on to a
> better place (and lacked any meaningful serial console support), but
> here are some logs from an MSI AM1I motherboard, both the attempted
> UEFI boot and the succ
18 matches
Mail list logo
