I wanted to run FreeBSD kernel Successfully in my ARM 64 bit processor based laptop, but wanted to know which one includes full version under "aarch64"?
So, given that there isn't an image specific to your machine, choose one of the generic ones (bootonly, disc1, dvd1, memstick or mini-memstick). Differences between them are explained on the release announcement page: https://www.freebsd.org/releases/13.1R/announce. "memstick" is usually a good choice.
The 'problem' with ARM based systems isn't the processor, it's the fact all those machines don't use a separate processor, they use a SoC. A SoC isn't standardized, thus there's no good way to create a 'generic' configuration.
On the other hand we have good support for Rockchip based SOC.
If I were to try FreeBSD on Chromebook that is what I would try.
Rockchip Chromebooks.
No guarantees it would work though.
I have already shopped the Rockchip Chromebooks and mentally devised a plan.
First Problem, Notebooks have a UART? Chances of lvds display working without support? Zero.
Second problem UEFI BIOS on Chromebook/box is custom. Some you can access some you cannot.
Perhaps these use a custom u-boot on Chromebooks instead being an ARM device.... Where do you find that?
Then down to the device level. Do you think all the notebook accessories are going to work? I doubt it.
Chrome Arm laptops are not really hackable in my opinion.
Too many variables.
Buy a PineBook if you want Arm Notebook. Even that is not officially supported.
@ghostwalker might be a good person to ask about Rockchip Chromebooks on FreeBSD.
That's interesting. I don't have any experience with ARM-based laptops and I thought that with aarch64 we now had a kind of standardised architecture where a generic system image would work on most machines, just like amd64 images work on most 64bit x86 machines no matter the particular make. If that's not the case: what kind of hardware is supported by the generic aarch64 FreeBSD images?
Checkout the /boot/dtb directory on aarch64 generic for an idea.
With the generic images you must flash it and then flash u-boot to it from ports/packages on some devices.
You see u-boot has two schemes.
Some where u-boot.bin is a file on the disk and some Arm uses a flashed file to bootsectors of the microSD card.
So you could look at the generic images as a starting point.
Some platforms will work with generic, file based u-boots for example (All Pi).
For u-boot flashed to bootsector you need to do that additional step for generic to boot.
Then you come down to displays. I have had a bear of a time with HDMI. RockPro64 several people noted thier HDMI works. MIne does not. Two different monitors. I give up. I don't need it for my use case.
So you really need to start off with a serial console then graduate to a display. That is my advice.
Whomever invented universal PNP and ACPI needs to be commended.
Its those little things in life that you don't realize in use until missing.
I tried to use freebsd-update on my rock64 on eMMC and FreeBSD no longer works.
FreeBSD 13.1 changed something and the eMMC loses power during bootup.
microSD card based FreeBSD 13.1 works fine.
Something weird you would never see on X86. Power and resistor control at the dtb (software) level.
Maybe there is an emmc.dtbo that is out of place...I really dunno.
FreeBSD 13.0 on eMMC for now.
Anything will have growing pains. I just feel Arm brings it to a lower level. Fractured would be an apt term.
I believed that the Aarch64 will able to run on ARM based 64 Bit processor SOCs. Below I have added the details of the processor and generic ones may have a chance if not at all?
What you say
Whomever invented universal PNP and ACPI needs to be commended.
Its those little things in life that you don't realize in use until missing.
I tried to use freebsd-update on my rock64 on eMMC and FreeBSD no longer works.
FreeBSD 13.1 changed something and the eMMC loses power during bootup.
microSD card based FreeBSD 13.1 works fine.
Something weird you would never see on X86. Power and resistor control at the dtb (software) level.
Maybe there is an emmc.dtbo that is out of place...I really dunno.
FreeBSD 13.0 on eMMC for now.
Anything will have growing pains. I just feel Arm brings it to a lower level. Fractured would be an apt term.
emmc works on various devices
if linux works on that laptop you can try to pull the dtb from there and use it
if there is no linux support or bad linux support then you can forget about any bsd
Yes that was just one case where an upgrade went sideways. The eMMC used to work but quit working.
I am sure stuff like that has happened on x86 before. I just like to whine.
Real world examples.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
old.reddit.com
