Framework 16 (Ryzen 9 7940HS) and FreeBSD 14.0-RELEASE

G

gerry

Hi,

I just received the new model from Frame.work and tried to boot 14.0-RELEASE.

It makes it to the Install FREEBSD screen, I selected the Verbose Boot option, and it makes it to

ppc0 failed to probe at irq7 on isa0

and freezes.

As a note, you have to turn off the Secure Boot in the BIOS or it will not even try to boot.

if someone wants to dive deeper into this, I’ll be happy to provide whatever additional information/assistance is needed. I know this is brand new hardware, and right now I am just seeing what will run on it.

Edit: movie of boot up in verbose mode linked below.it runs pretty fast, but it has pretty much everything from the initial install menu on.

Video here

you can somewhat scrub the video if you download it to your device, but the scrolling is so fast it is still hard to read everything. I’ll take any suggestions as to how to better capture this!
 
I also ordered one and planned to use it as new daily driver with FreeBSD (later batch though, will probably not get it before end of Q1), so I am very curious about your progress!
 
Hi gerry, have you made any further progress beyond this point?

My Framework 16 arrived yesterday and I tried 13.3, 14-STABLE and the latest 15-CURRENT snapshot and they all stop at the same point (what you wrote above, "ppc0 failed to probe at irq7 on isa0")
 
Following up on my own post -

Assuming that the problem is ppc probing from the boot message, I tried again with 14.0-RELEASE and disabled ppc probing by adding

Code: 
hint.ppc.0.disabled=1

to /boot/loader.conf on the installation media.

Now booting stops at:

Code: 
ppc0: not probed (disabled)

That means the problem very likely is whatever comes after parallel port probing...
 
pebkac said:
That means the problem very likely is whatever comes after parallel port probing...
Click to expand...
Maybe it's uart*.

See https://lists.freebsd.org/archives/freebsd-current/2024-February/005672.html
Code: 
Unable to boot -CURRENT on Thinkpad P16s G2
...
ppc0: cannot reserve I/O port range
ppc0 failed to probe at irq 7 on isa0
uart0 failed to probe at port 0x3f8 irq 4 on isa0
...

Reply: https://lists.freebsd.org/archives/freebsd-current/2024-March/005693.html
Code: 
...
Short follow-up: disabling uart0 and uart1 at the loader prompt allowed 
us to boot and install FreeBSD (the -CURRENT snapshot from 2024-02-29 in 
case it matters).
...

Reply: https://lists.freebsd.org/archives/freebsd-current/2024-March/005696.html
Code: 
...
UARTS on AMD can be a bit different.  Some BIOS implementations seem
to set them up to work like legacy ports others do not.  On a Naples
platform I helped add support for them since they were not setup
in the legacy configuration.  The AMD servers I'm using now have them
setup in legacy mode and just work like on other systems.

If I remember right those UARTS were defined in ACPI.  On a laptop they
probably don't have serial ports and the probe is getting stuck on
something.  It might be good to instrument it to see what.
...
 
pebkac said:
Aaaaand one more follow up -

This is the solution:

https://codeberg.org/grahamperrin/freebsd-src/issues/8

I.e. adding

Code: 
hint.uart.0.disabled=1
hint.uart.1.disabled=1

...is enough to boot and install FreeBSD14-RELEASE.

Did not yet check anything beyond basic installation like Xorg, WIFI etc of course.
Click to expand...
Disabling uart.0 and uart.1 has stopped the freeze/lockup using the FreeBSD-14.0-RELEASE-amd64-memstick install, but it does reboot with a "Page Fault while in kernel mode page not present" that I am going to try to capture but it happens so fast.

Do you have the Ryzen 9 motherboard?

On mine it makes it past:
Identifying the Framework Numpad Module and Keypad module

iichid1: Interrupt setup failed, Fallback to sampling
hidbus1: <HID bus> on iichid1
ng_hci_process_command_timeout: ubt0hci - unable to complete HCI command OGF=0x3, OCF=0x3. Timeout
and in the blurry screen I can read:
some references to Bluetooth stack for device ubt0
HMS0: <PIXA3854:06 093A 0274 Mouse> on hidbus1 although some of that was blurry
and I think it says:
fault virtual address = 0xffffff80c05b3eb40

I may try to find time to redirect the console to a USB port and try to capture the boot via a serial port on another computer.
 
gerry said:
Disabling uart.0 and uart.1 has stopped the freeze/lockup using the FreeBSD-14.0-RELEASE-amd64-memstick install, but it does reboot with a "Page Fault while in kernel mode page not present" that I am going to try to capture but it happens so fast.

Do you have the Ryzen 9 motherboard?
Click to expand...

I guess so, from my dmesg:

CPU: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics (3992.67-MHz K8-class CPU) Origin="AuthenticAMD" Id=0xa70f41 Family=0x19 Model=0x74 Stepping=1 Features=0x178bfbff Features2=0x7ef8320b AMD Features=0x2e500800 AMD Features2=0x75c237ff Structured Extended Features=0xf1bf97a9 Structured Extended Features2=0x405fde Structured Extended Features3=0x10000000 XSAVE Features=0xf AMD Extended Feature Extensions ID EBX=0x791ef257 SVM: NP,NRIP,VClean,AFlush,DAssist,NAsids=32768 TSC: P-state invariant, performance statistics

The uart hints were the only things I had to change, after that, everything worked smoothly...

I remember I had a fault once or twice on boot as well though, but then the second time booting worked fine each time, so maybe a race condition somewhere or so.

You also might try to remove the pluggable port modules to see if it has something to do with them?

I don't use the separate Numpad keyboard module btw, maybe this one interferes?
 
pebkac said:
I guess so, from my dmesg:

CPU: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics (3992.67-MHz K8-class CPU) Origin="AuthenticAMD" Id=0xa70f41 Family=0x19 Model=0x74 Stepping=1 Features=0x178bfbff Features2=0x7ef8320b AMD Features=0x2e500800 AMD Features2=0x75c237ff Structured Extended Features=0xf1bf97a9 Structured Extended Features2=0x405fde Structured Extended Features3=0x10000000 XSAVE Features=0xf AMD Extended Feature Extensions ID EBX=0x791ef257 SVM: NP,NRIP,VClean,AFlush,DAssist,NAsids=32768 TSC: P-state invariant, performance statistics

The uart hints were the only things I had to change, after that, everything worked smoothly...

I remember I had a fault once or twice on boot as well though, but then the second time booting worked fine each time, so maybe a race condition somewhere or so.

You also might try to remove the pluggable port modules to see if it has something to do with them?

I don't use the separate Numpad keyboard module btw, maybe this one interferes?
Click to expand...
Thanks for the information!

I just removed the numpad and all port modules except 1 usb-c that is where the memstick is plugged in and it endless reboots. I see it recognized the keyboard, but shortly thereafter it faults and reboots.

I’ll see if I have luck redirecting console to a usb port and capturing that on another computer to get the exact details.
 
gerry said:
Thanks for the information!

I just removed the numpad and all port modules except 1 usb-c that is where the memstick is plugged in and it endless reboots. I see it recognized the keyboard, but shortly thereafter it faults and reboots.

I’ll see if I have luck redirecting console to a usb port and capturing that on another computer to get the exact details.
Click to expand...
So I am not convinced you can redirect console during an initial installation boot, but I will keep digging. I have tried recording the boot sequence via my phone, but the scroll is so fast, especially just before the crash that the video is nothing but a blur of overlaid text.
 
gerry said:
So I am not convinced you can redirect console during an initial installation boot, but I will keep digging. I have tried recording the boot sequence via my phone, but the scroll is so fast, especially just before the crash that the video is nothing but a blur of overlaid text.
Click to expand...
A few more thoughts:

You should be able to enable crash dumping to the USB stick, no? Then you should be able to read the crash dump on another system...

Second: My Framework is from a later batch and has a BIOS version from 24 January or so I think (which I have not updated myself), maybe you might want to check that as well and possibly update it.

Also, if you want to compare your PCI devices:

Code: 
$ pciconf -lv
hostb0@pci0:0:0:0:    class=0x060000 rev=0x00 hdr=0x00 vendor=0x1022 device=0x14e8 subvendor=0xf111 subdevice=0x0005
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    class      = bridge
    subclass   = HOST-PCI
amdiommu0@pci0:0:0:2:    class=0x080600 rev=0x00 hdr=0x00 vendor=0x1022 device=0x14e9 subvendor=0xf111 subdevice=0x0005
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    class      = base peripheral
    subclass   = IOMMU
hostb1@pci0:0:1:0:    class=0x060000 rev=0x00 hdr=0x00 vendor=0x1022 device=0x14ea subvendor=0x0000 subdevice=0x0000
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    class      = bridge
    subclass   = HOST-PCI
hostb2@pci0:0:2:0:    class=0x060000 rev=0x00 hdr=0x00 vendor=0x1022 device=0x14ea subvendor=0x0000 subdevice=0x0000
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    class      = bridge
    subclass   = HOST-PCI
pcib1@pci0:0:2:2:    class=0x060400 rev=0x00 hdr=0x01 vendor=0x1022 device=0x14ee subvendor=0x1022 subdevice=0x1453
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    class      = bridge
    subclass   = PCI-PCI
pcib2@pci0:0:2:4:    class=0x060400 rev=0x00 hdr=0x01 vendor=0x1022 device=0x14ee subvendor=0x1022 subdevice=0x1453
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    class      = bridge
    subclass   = PCI-PCI
hostb3@pci0:0:3:0:    class=0x060000 rev=0x00 hdr=0x00 vendor=0x1022 device=0x14ea subvendor=0x0000 subdevice=0x0000
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    class      = bridge
    subclass   = HOST-PCI
pcib3@pci0:0:3:1:    class=0x060400 rev=0x00 hdr=0x01 vendor=0x1022 device=0x14ef subvendor=0x1022 subdevice=0x1453
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    device     = 'Family 19h USB4/Thunderbolt PCIe tunnel'
    class      = bridge
    subclass   = PCI-PCI
none0@pci0:0:3:2:    class=0x000000 rev=0x00 hdr=0x00 vendor=0x0000 device=0x0000 subvendor=0x0000 subdevice=0x0000
    class      = old
    subclass   = non-VGA display device
none1@pci0:0:3:3:    class=0x000000 rev=0x00 hdr=0x00 vendor=0x0000 device=0x0000 subvendor=0x0000 subdevice=0x0000
    class      = old
    subclass   = non-VGA display device
none2@pci0:0:3:4:    class=0x000000 rev=0x00 hdr=0x00 vendor=0x0000 device=0x0000 subvendor=0x0000 subdevice=0x0000
    class      = old
    subclass   = non-VGA display device
hostb4@pci0:0:4:0:    class=0x060000 rev=0x00 hdr=0x00 vendor=0x1022 device=0x14ea subvendor=0x0000 subdevice=0x0000
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    class      = bridge
    subclass   = HOST-PCI
pcib4@pci0:0:4:1:    class=0x060400 rev=0x00 hdr=0x01 vendor=0x1022 device=0x14ef subvendor=0x1022 subdevice=0x1453
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    device     = 'Family 19h USB4/Thunderbolt PCIe tunnel'
    class      = bridge
    subclass   = PCI-PCI
hostb5@pci0:0:8:0:    class=0x060000 rev=0x00 hdr=0x00 vendor=0x1022 device=0x14ea subvendor=0x0000 subdevice=0x0000
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    class      = bridge
    subclass   = HOST-PCI
pcib5@pci0:0:8:1:    class=0x060400 rev=0x00 hdr=0x01 vendor=0x1022 device=0x14eb subvendor=0x0005 subdevice=0xf111
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    class      = bridge
    subclass   = PCI-PCI
pcib6@pci0:0:8:2:    class=0x060400 rev=0x00 hdr=0x01 vendor=0x1022 device=0x14eb subvendor=0x0005 subdevice=0xf111
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    class      = bridge
    subclass   = PCI-PCI
pcib7@pci0:0:8:3:    class=0x060400 rev=0x00 hdr=0x01 vendor=0x1022 device=0x14eb subvendor=0x0005 subdevice=0xf111
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    class      = bridge
    subclass   = PCI-PCI
intsmb0@pci0:0:20:0:    class=0x0c0500 rev=0x71 hdr=0x00 vendor=0x1022 device=0x790b subvendor=0xf111 subdevice=0x0005
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    device     = 'FCH SMBus Controller'
    class      = serial bus
    subclass   = SMBus
none3@pci0:0:20:3:    class=0x060100 rev=0x51 hdr=0x00 vendor=0x1022 device=0x790e subvendor=0xf111 subdevice=0x0005
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    device     = 'FCH LPC Bridge'
    class      = bridge
    subclass   = PCI-ISA
hostb6@pci0:0:24:0:    class=0x060000 rev=0x00 hdr=0x00 vendor=0x1022 device=0x14f0 subvendor=0x0000 subdevice=0x0000
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    class      = bridge
    subclass   = HOST-PCI
hostb7@pci0:0:24:1:    class=0x060000 rev=0x00 hdr=0x00 vendor=0x1022 device=0x14f1 subvendor=0x0000 subdevice=0x0000
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    class      = bridge
    subclass   = HOST-PCI
hostb8@pci0:0:24:2:    class=0x060000 rev=0x00 hdr=0x00 vendor=0x1022 device=0x14f2 subvendor=0x0000 subdevice=0x0000
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    class      = bridge
    subclass   = HOST-PCI
hostb9@pci0:0:24:3:    class=0x060000 rev=0x00 hdr=0x00 vendor=0x1022 device=0x14f3 subvendor=0x0000 subdevice=0x0000
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    class      = bridge
    subclass   = HOST-PCI
hostb10@pci0:0:24:4:    class=0x060000 rev=0x00 hdr=0x00 vendor=0x1022 device=0x14f4 subvendor=0x0000 subdevice=0x0000
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    class      = bridge
    subclass   = HOST-PCI
hostb11@pci0:0:24:5:    class=0x060000 rev=0x00 hdr=0x00 vendor=0x1022 device=0x14f5 subvendor=0x0000 subdevice=0x0000
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    class      = bridge
    subclass   = HOST-PCI
hostb12@pci0:0:24:6:    class=0x060000 rev=0x00 hdr=0x00 vendor=0x1022 device=0x14f6 subvendor=0x0000 subdevice=0x0000
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    class      = bridge
    subclass   = HOST-PCI
hostb13@pci0:0:24:7:    class=0x060000 rev=0x00 hdr=0x00 vendor=0x1022 device=0x14f7 subvendor=0x0000 subdevice=0x0000
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    class      = bridge
    subclass   = HOST-PCI
none4@pci0:1:0:0:    class=0x028000 rev=0x00 hdr=0x00 vendor=0x14c3 device=0x0616 subvendor=0x14c3 subdevice=0xe616
    vendor     = 'MEDIATEK Corp.'
    device     = 'MT7922 802.11ax PCI Express Wireless Network Adapter'
    class      = network
nvme0@pci0:2:0:0:    class=0x010802 rev=0x01 hdr=0x00 vendor=0x15b7 device=0x5030 subvendor=0x15b7 subdevice=0x5030
    vendor     = 'Sandisk Corp'
    device     = 'WD Black SN850X NVMe SSD'
    class      = mass storage
    subclass   = NVM
vgapci0@pci0:193:0:0:    class=0x030000 rev=0xc1 hdr=0x00 vendor=0x1002 device=0x15bf subvendor=0xf111 subdevice=0x0005
    vendor     = 'Advanced Micro Devices, Inc. [AMD/ATI]'
    device     = 'Phoenix1'
    class      = display
    subclass   = VGA
hdac0@pci0:193:0:1:    class=0x040300 rev=0x00 hdr=0x00 vendor=0x1002 device=0x1640 subvendor=0xf111 subdevice=0x0005
    vendor     = 'Advanced Micro Devices, Inc. [AMD/ATI]'
    device     = 'Rembrandt Radeon High Definition Audio Controller'
    class      = multimedia
    subclass   = HDA
none5@pci0:193:0:2:    class=0x108000 rev=0x00 hdr=0x00 vendor=0x1022 device=0x15c7 subvendor=0xf111 subdevice=0x0005
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    device     = 'Family 19h (Model 74h) CCP/PSP 3.0 Device'
    class      = encrypt/decrypt
xhci0@pci0:193:0:3:    class=0x0c0330 rev=0x00 hdr=0x00 vendor=0x1022 device=0x15b9 subvendor=0xf111 subdevice=0x0005
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    class      = serial bus
    subclass   = USB
xhci1@pci0:193:0:4:    class=0x0c0330 rev=0x00 hdr=0x00 vendor=0x1022 device=0x15ba subvendor=0xf111 subdevice=0x0005
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    class      = serial bus
    subclass   = USB
none6@pci0:193:0:5:    class=0x048000 rev=0x63 hdr=0x00 vendor=0x1022 device=0x15e2 subvendor=0xf111 subdevice=0x0005
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    device     = 'ACP/ACP3X/ACP6x Audio Coprocessor'
    class      = multimedia
hdac1@pci0:193:0:6:    class=0x040300 rev=0x00 hdr=0x00 vendor=0x1022 device=0x15e3 subvendor=0xf111 subdevice=0x0005
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    device     = 'Family 17h/19h HD Audio Controller'
    class      = multimedia
    subclass   = HDA
none7@pci0:194:0:0:    class=0x130000 rev=0x00 hdr=0x00 vendor=0x1022 device=0x14ec subvendor=0xf111 subdevice=0x0005
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    class      = non-essential instrumentation
none8@pci0:194:0:1:    class=0x118000 rev=0x00 hdr=0x00 vendor=0x1022 device=0x1502 subvendor=0xf111 subdevice=0x0005
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    device     = 'AMD IPU Device'
    class      = dasp
none9@pci0:195:0:0:    class=0x130000 rev=0x00 hdr=0x00 vendor=0x1022 device=0x14ec subvendor=0xf111 subdevice=0x0005
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    class      = non-essential instrumentation
xhci2@pci0:195:0:3:    class=0x0c0330 rev=0x00 hdr=0x00 vendor=0x1022 device=0x15c0 subvendor=0xf111 subdevice=0x0005
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    class      = serial bus
    subclass   = USB
xhci3@pci0:195:0:4:    class=0x0c0330 rev=0x00 hdr=0x00 vendor=0x1022 device=0x15c1 subvendor=0xf111 subdevice=0x0005
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    class      = serial bus
    subclass   = USB
none10@pci0:195:0:5:    class=0x0c0340 rev=0x00 hdr=0x00 vendor=0x1022 device=0x1668 subvendor=0xf111 subdevice=0x0005
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    device     = 'Pink Sardine USB4/Thunderbolt NHI controller'
    class      = serial bus
    subclass   = USB
none11@pci0:195:0:6:    class=0x0c0340 rev=0x00 hdr=0x00 vendor=0x1022 device=0x1669 subvendor=0xf111 subdevice=0x0005
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    device     = 'Pink Sardine USB4/Thunderbolt NHI controller'
    class      = serial bus
    subclass   = USB
 
I have installed the BIOS update and still end up in a crash/reboot cycle. I’ll see what I need to do to enable the crash dump to the memstick this weekend. I’ll also compare the pci info to see if there are any differences, which there shouldn’t be. Thanks again for your patience and help!
 
Great update (didn't expect that to work): With FreeBSD 14.1 and the installation as described in this post, the AMD GPU is fully supported by Wayland:

forums.freebsd.org

AMD Ryzen 9 7940HS (Radeon 780M) - Graphics now working!

This was a very rocky road and maybe its just me, but I found next to no helpful information in getting the 780M graphics of the fairly new AMD 7940HS to work on FreeBSD. Here is a short list of the things I had to do to get this working: Upgrade to FreeBSD 15-CURRENT, it looks like the...
forums.freebsd.org forums.freebsd.org

drm-61-kmod is not yet in quarterly packages, so you need to build yourself, but quarterly ports tree is good enough, so it mixes fine with quarterly packages...

EDIT: To be clear, graphics also worked before, but you needed to use the framebuffer driver which is good enough for Xorg, but not for Wayland.
Very happy to be able to type this from my Hyprland desktop...
 
Thank you Pebcak for that information! I have been busy for several weeks and I wasn’t paying attention! I may have some questions as I try what you (and that post) suggest. ?
 
FW16 user without external GPU unit looking to get FreeBSD running well for KDE.

WIth graphics is only the install of drm-61-kmod without adding kld_list="amdgpu" to /etc/rc.conf required for the proper video drivers?

I imagine so, because I get a black screen when I add it, but just seeing if on right path.

Thanks!
 
rotaecho said:
I get a black screen
Click to expand...
The automatic/handbooklike installation of drm-something-kmod seems to be kind of a common problem at the moment.
Since in most cases (also in mine) it's simply to build the
drm-kmod from ports:
1. remove the installed drm-XX-kmod:
pkg remove drm-61-kmod or pkg remove drm-kmod, or whatever you have installed
2. Then build the drm-kmod by ports (drm-kmod is a meta-package that will automatically install the right one for your machine; in most cases it works):
cd /usr/ports/graphics/drm-kmod/
make install clean
3. you may throw the old mod out of the kernel ( kldunload), and reload the new one ( kldload);( kldstat to see current loaded modules)
- or simply reboot

shall work now.
Uh, no, sorry.
You have to add
Code: 
kld_list=amdgpu
to your
/etc/rc.conf
before you reboot, otherwise this kernel module will not be loaded automatically when start up (you may load it everytime you want a GUI by hand, if you like... *cough*, but that's more comfortable, of course)
 
I did a fresh install, as trying to document my process till I get something working.

I did a fresh install, first pkg install was drm-kmod

When I add:

kld_list="amdgpu" in /etc/rc.conf doesn't seem where I put it, the screen just goes black.

I'll revisit it tomorrow. Too many waste hours today
 
rotaecho said:
first pkg install was drm-kmod
Click to expand...
NOT pkg install
build by ports

🤓
There are two major ways to Install Software on FreeBSD:
packages and ports

(very short as a simple, brief overview, so not covering every detail to be exactly right)

packages are already compiled binary files you simply download - quickest, most comfortable way, and for most cases the easiest, recommend way.

ports are directories containing just the makefiles, and a (short) description of the software packages.
Building by ports means, you download the source, and compile it yourself on your machine.
Sounds complicated, but it's not. In fact it's pretty simple, 'cause the Makefile does all the work.
It's simply done by cd into the according directory (the port), just do
make install, and wait - the makefile does it all.
In almost all cases it simply runs errorless through (This ain't Linux 😁),
and because you also said 'install' the package is not only made (compiled), but also installed on your machine.

(and you don't need to completely reinstall your system for that; FreeBSD has nothing like a 'Registry' you will mess up over time, by simply install and deinstall many packages.)
 
Maturin said:
NOT pkg install
build by ports

🤓
There are two major ways to Install Software on FreeBSD:
packages and ports

(very short as a simple, brief overview, so not covering every detail to be exactly right)

packages are already compiled binary files you simply download - quickest, most comfortable way, and for most cases the easiest, recommend way.

ports are directories containing just the makefiles, and a (short) description of the software packages.
Building by ports means, you download the source, and compile it yourself on your machine.
Sounds complicated, but it's not. In fact it's pretty simple, 'cause the Makefile does all the work.
It's simply done by cd into the according directory (the port), just do
make install, and wait - the makefile does it all.
In almost all cases it simply runs errorless through (This ain't Linux 😁),
and because you also said 'install' the package is not only made (compiled), but also installed on your machine.

(and you don't need to completely reinstall your system for that; FreeBSD has nothing like a 'Registry' you will mess up over time, by simply install and deinstall many packages.)
Click to expand...

Ah, I did read that, I figured the pkgs were safer bet since already built. Especially when building large systems like KDE or desktop environments.

What is a good way to determine if one should use pkgs or ports? Such as, if the laptop is HCL certified, is it best to use pkgs vs ports? And when laptop isn't certified stick to ports?

I read in the Handbook that you souldn't mix the two, just trying to learn the ins and outs of FreeBSD again. It's a different beast than Solaris of what I'm more familiar with; making commitment to FreeBSD just a bit dated on that information; last real time I used FreeBSD was in 98'!

I haven't compiled a port on FreeBSD in over a decade, and about two of those when I was compiling stuff like X11 and what not for Solaris 6-9 days hehe.

Thanks for the help and pointers!

-Will
 
rotaecho said:
I read in the Handbook that you souldn't mix the two
Click to expand...
Normally that's right, and you should stick to pkg installation for now, even if building X.org, and KDE may not take a week anymore (I also remember those days :cool:), it will take perhaps a bit more than a whole night (I never built KDE by source, I dont use it; so very roughly estimated - and to this topic at the moment of no importance.[the youngsters have no idea when I tell you, we also don't have to mess with mode lines on tubes anymore 😁)
However, this is an exception.
Do all your installation by pkg install, except the one for drm-kmod.
We just need to get your machine up, and useful running - details later.
Just follow the steps in my first post.It should work.
(You do have the ports tree installed? [/usr/ports/ exists, and is not empty?] Otherwise you need of course install it first.)
The build will last a couple of minutes. Then reboot, and see if you finally get a X-server running (as root 'startx'); if so, you may keep on following the steps in the handbook, add your user(s) to the video group, install the rest (with pkg install), etc.
 
You must log in or register to reply here.
Back
Top