On Wed, February 4, 2015 15:04, Jakob Alvermark wrote:
>
> On 31 dec 2014, at 16:24, Jakob Alvermark wrote:
>
>
>> On Tue, December 30, 2014 17:00, Nathan Whitehorn wrote:
>>
>>>
>>
>>> On 12/30/14 06:40, Jakob Alvermark wrote:
>>>
>>>
Hi,
Have been playing with this machine for a while now.
It is a quad core Pentium N3540 (ValleyView/Bay Trail), 8 GB RAM. It
came with a Broadcom WiFi card which I swapped for an Intel which
is supported by FreeBSD. Also swapped the hard drive for an SSD.
When first trying to boot FreeBSD with UEFI it would not boot.
It stops after the loader is trying to start the kernel.
My workaround now is using refind, http://www.rodsbooks.com/refind/
to set the screen resolution to 800x600. (Native is 1366x768) Only
then will it boot using UEFI. I tried setting it to 1024x768, then
it crashes. If it helps I can get the backtrace.
>>>
>>> [Not sure what's going on here]
>>>
>>>
>
>
> A follow up on this:
>
>
> I tried this on my desktop machine (AMD FX-8350, Radeon HD 5450) to see
> if it has the issue, and it has! I went on to try it on my desktop machine
> at work (Core i3-4130, Radeon HD 4350) and it boots!
>
> On the Acer, resolution set to 1024x768:
>
>
>>> FreeBSD EFI boot block
>>>
> Loader path: /boot/loader.efi
> Consoles: EFI console
> Image base: 0x7502f000
> EFI version: 2.40
> EFI Firmware: INSYDE Corp. (rev 21522.39)
>
>
> ---
> Start @ 0x802e1000 ...
> EFI framebuffer information:
> addr, size 0x8000, 0x30 dimensions 1024 x 768 stride
> 1024
> masks 0x00ff, 0xff00, 0x00ff, 0xff00
>
> ---
>
>
> kernel trap12 with interrupts disabled
>
>
> Fatal trap 12: page fault while in kernel mode
> cpuid = 0; apic id = 00 fault virtual address = 0x13 fault code
> = supervisor read data, page not present
> instruction pointer = 0x20:0x80a20834 stack pointer
> = 0x28:0x81604170
> frame pointer = 0x28:0x81604290 code segment
> = base 0x0, limit 0xf, type 0x1b
> = DPL 0, pres 1, long 1, def32 0, gran 1
> processor eflags = resume, IOPL = 0 current process = 0
> ()
> [ thread pid 0 tid 0]
> Stopped at kvprintf+0xd4:movzbl (%r14),%eax
>
>
>
>
>
>
>
> On the home desktop resolution 1024x768:
>
>
>>> FreeBSD EFI boot block
>>>
> Loader path: /boot/loader.efi
> Consoles: EFI console
> Image base: 0xb08ac000
> EFI version: 2.31
> EFI Firmware: American Megatrends (rev 4.653)
>
>
> ---
> Start @ 0x802e1000 ...
> EFI framebuffer information:
> addr, size 0xc000, 0x30 dimensions 1024 x 768 stride
> 1024
> masks 0x00ff, 0xff00, 0x00ff, 0xff00
>
> ---
> kernel trap12 with interrupts disabled
>
>
> Fatal trap 12: page fault while in kernel mode
> cpuid = 0; apic id = 00 fault virtual address = 0x13 fault code
> = supervisor read data, page not present
> instruction pointer = 0x20:0x80a20654 stack pointer
> = 0x28:0x81603d70
> frame pointer = 0x28:0x81603e90 code segment
> = base 0x0, limit 0xf, type 0x1b
> = DPL 0, pres 1, long 1, def32 0, gran 1
> processor eflags = resume, IOPL = 0 current process = 0
> ()
> [ thread pid 0 tid 0]
> Stopped at kvprintf+0xd4:movzbl (%r14),%eax
>
>
>
>
>
> On the work desktop:
>
>
>>> FreeBSD EFI boot block
>>>
> Loader path: /boot/loader.efi
> Consoles: EFI console
> Image base: 0xbb7aa000
> EFI version: 2.31
> EFI Firmware: American Megatrends (rev 4.654)
>
>
> ---
> Start @ 0x802e1000 ...
> EFI framebuffer information:
> addr, size 0xe000, 0x30 dimensions 1024 x 768 stride
> 1024
> masks 0x00ff, 0xff00, 0x00ff, 0xff00
>
> And then it boots normally.
>
>
>
> Does anyone have any clues on what's going on here?
>
>
> (This all typed manually from screenshots taken with my phone, there
> might be typos.)
Another update!
As I found out the EFI loader has the capability to change screen modes I
dumped refind and started playing with this again.
"mode 5" gives me 1024x768 and a panic:
---
kernel trap 12 with interrupts disabled
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0x1f2d0ec
fault code = supervisor read data, page not present
instruction pointer = 0x20:0x8030003d
stack pointer = 0x28:0x81616f70
frame pointer = 0x28:0x0
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= resume, IOPL = 0
current process = 0 ()
---
What struck me then was this line:
instruction pointer = 0x20:0x8030003d
and the fact that:
EFI framebuffer information:
addr, size 0x8000, 0x30
Coincidence? Maybe n
