console in UEFI boot

[karu.pruun]

Apparently this is due to the 32 bitness of the original operating system
that came with the machine: the UEFI spec requires that UEFI and OS bitness
match. The original OS was probably a 32 bit Windows.

Peeter

--

On Thu, Jul 7, 2016 at 11:14 PM, Bernard Mentink <bmentink at gmail.com> wrote:

> In my case, I have a small Atom based micro-PC which is 64bits with a
> 32-bit UEFI ...
> I use it as a media center PC ...
>
> On Fri, Jul 8, 2016 at 6:58 AM, Samuel Paik <sam at paiks.org> wrote:
>
>> Some Windows 8 PCs (particularly Atom based tablets with 1-2 GB
>> non-expandable RAM) have 64-bit capable CPUs but come with 32-bit UEFI boot
>> roms.
>>
>> On Thu, Jul 7, 2016 at 5:43 AM, karu.pruun <karu.pruun at gmail.com> wrote:
>>
>>> Hi Bernie
>>>
>>> I don't know. Do you mean your machine is 64bit but has a 32bit EFI?
>>> This is a good overview of UEFI
>>>
>>>
>>> https://www.happyassassin.net/2014/01/25/uefi-boot-how-does-that-actually-work-then/
>>>
>>> I think the terminology is that the type of your firmware is either BIOS
>>> or UEFI, and the latter can emulate BIOS boot if needed.
>>>
>>> I should also retract my original complaint: booting now works fine on
>>> macbookpro even without interfering, ie setting 'mode 0' at loader prompt.
>>> No idea why the error is gone. All I did is correct the vfs.root.mountfrom
>>> variable so I don't need to enter it by hand in the middle of the boot
>>> sequence; and delete /etc/issue left over from the boot CD. In any case,
>>> the problem now is that i915 does not load; the machine gets stuck.
>>>
>>> Cheers
>>>
>>> Peeter
>>>
>>> --
>>>
>>>
>>> On Thu, Jul 7, 2016 at 12:03 AM, Bernard Mentink <bmentink at gmail.com>
>>> wrote:
>>>
>>>> Hi Peeter,
>>>>
>>>> So is there a 32 bit EFI loader available for machines with a 32bit EFI
>>>> bios?
>>>>
>>>> Cheers,
>>>> Bernie
>>>>
>>>> On Wed, Jul 6, 2016 at 9:51 PM, karu.pruun <karu.pruun at gmail.com>
>>>> wrote:
>>>>
>>>>> Update: the console works fine if one escapes to loader prompt and
>>>>> sets mode to either 0 (80x25) or 1 (80x50), and then boots the system up.
>>>>> The original mode set by EFI is 2 (210x55). When the system has booted up,
>>>>> ttyv0 will still be smaller in the top left corner, but switching to any
>>>>> other ttyv gives a full display (105x32).
>>>>>
>>>>> So all in all: using DragonFly 4.5 and UEFI I have a multiboot machine
>>>>> (macbookpro 15) with DragonFly, MacOSX, and I also installed FreeBSD for
>>>>> testing purposes.
>>>>>
>>>>> For those interested: DragonFly can be installed manually as described
>>>>> on the manual page gpt(8). The difference is in creating partitions. For
>>>>> booting, create a 1 GB partition and format without labelling:
>>>>>
>>>>> gpt add -s 2000000 -t "DragonFly UFS1" adX
>>>>> newfs /dev/adXsY
>>>>>
>>>>> where X and Y are the disk and slice respectively. Other partitions
>>>>> can be labelled as usual. cpdup boot stuff to the boot partition as
>>>>> explained in gpt(8), and the rest to other partitions. When you're
>>>>> finished, mount the EFI system partition
>>>>>
>>>>> mount -t msdos /dev/adsX /mnt
>>>>>
>>>>> and copy DragonFly's EFI bootloader to it
>>>>>
>>>>> mkdir -p /mnt/EFI/dragonfly
>>>>> cp /boot/boot1.efi /mnt/EFI/dragonfly/dragonfly_x64.efi
>>>>>
>>>>> If you have an EFI boot manager like refind, you can boot DragonFly or
>>>>> any other system by choosing the respective EFI bootloader at startup. If
>>>>> you don't have a boot manager, then EFI will look for
>>>>>
>>>>> \EFI\BOOT\BOOTx64.EFI
>>>>>
>>>>> so copy DragonFly's EFI bootloader to this file,
>>>>>
>>>>> cp /boot/boot1.efi /mnt/EFI/boot/bootx64.efi
>>>>>
>>>>>
>>>>> Cheers
>>>>>
>>>>> Peeter
>>>>>
>>>>> --
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Tue, Jul 5, 2016 at 1:19 PM, karu.pruun <karu.pruun at gmail.com>
>>>>> wrote:
>>>>> > Hello
>>>>> >
>>>>> > I am booting DragonFly via UEFI on a macbookpro and running into
>>>>> > issues with console. UEFI puts console into a resolution 1680x1050,
>>>>> > but as soon as kernel has loaded and starts it switches to 40x25 mode
>>>>> > (or something similar, i.e. the default mode one sees at say CD
>>>>> boot),
>>>>> > but does not quite succeed: there's a 40x25 black-white quadrant in
>>>>> > the top-left corner and the rest is gray. This is compounded with
>>>>> > another issue: when booting is almost finished, the console starts
>>>>> > printing line feeds very fast although no key is pressed. In the end
>>>>> > the console is unusable as the prompt gets line feeds 10x a second
>>>>> and
>>>>> > nothing can be entered. Not sure the keyboard works at all. Aside
>>>>> from
>>>>> > that the system is running fine when used via ssh.
>>>>> >
>>>>> > When booted using a CD the console and keyboard are fine.
>>>>> >
>>>>> > Can I set a variable in loader.conf or elsewhere to switch the mode
>>>>> > back to 1680x1050 or something else?
>>>>> >
>>>>> > Cheers
>>>>> >
>>>>> > Peeter
>>>>> >
>>>>> > --
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> -------------------------------------------------------------------------------------------------------------------------------------
>>>> Life is a sexually transmitted disease with a 100% mortality rate.
>>>>
>>>> -------------------------------------------------------------------------------------------------------------------------------------
>>>>
>>>
>>>
>>
>
>
> --
>
> -------------------------------------------------------------------------------------------------------------------------------------
> Life is a sexually transmitted disease with a 100% mortality rate.
>
> -------------------------------------------------------------------------------------------------------------------------------------
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.dragonflybsd.org/pipermail/users/attachments/20160708/6f6e9faf/attachment-0003.htm>