4 ms·

>The ones in base are fairly old, but the ones in ports are equivalent to Linux 4.16, so about six months old. Yes they're ported from Linux, I don't see why th

>The ones in base are fairly old, but the ones in ports are equivalent to Linux 4.16, so about six months old. Yes they're ported from Linux, I don't see why that's a problem. Is this matrix outdated? https://wiki.freebsd.org/Graphics/AMD-GPU-Matrix https://wiki.freebsd.org/Graphics/AMD-GPU-Matrix >The rest of your post can be summed up with "I like systemd." It's not about systemd in particular, it's about modern service and system management in general https://www.freebsdnews.com/2018/08/21/benno-rice-the-tragedy-of-systemd-bsdcan-2018/ https://www.freebsdnews.com/2018/08/21/benno-rice-the-traged... You also forget about software argument, why to use freebsd if you would use linux-layer all the way.

boomboomsubban 8y ago
>Is this matrix outdated? I would guess that it is reflecting the drivers in base, the page above that gives directions on using this driver in ports. https://www.freshports.org/graphics/drm-fbsd12.0-kmod/ https://www.freshports.org/graphics/drm-fbsd12.0-kmod/ I'm sure improvements could be made to FreeBSD init, but all you're saying is you'd prefer one more like systemd. Then you're free to use something else. >You also forget about software argument, why to use freebsd if you would use linux-layer all the way. You aren't using a Linux layer all the way, you are for video card drivers. As for why, they're free software. Using the Linux ones makes more sense than building new ones from scratch.
- ernst_klim 8y ago
  >4.16 DRM I see. For 11.2 its 4.11, so it didn't support my vega card. Upgrade to 12 leaded me to kernel panic on startup on my shitty laptop's cpu, this bug [1]. >You aren't using a Linux layer all the way, you are for video card drivers. I was talking about lack of hardware and software support, so you need a compatibility layer for commercial linux software. [1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233534 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233534
  - loeg 8y ago
    > I was talking about lack of hardware and software support, so you need a compatibility layer for commercial linux software. The linuxkpi kernel API compatibility layer is for open source software (e.g., dual-licensed BSD/GPL Linux DRM drivers), not for commercial Linux software. The linuxemul syscall ABI layer can be used to run commercial Linux software, but is an entirely different and unrelated component. It has nothing to do with hardware support. This is like claiming that because WINE exists, Linux uses Windows for hardware support.

boomboomsubban 8y ago

>Is this matrix outdated? I would guess that it is reflecting the drivers in base, the page above that gives directions on using this driver in ports. https://www.freshports.org/graphics/drm-fbsd12.0-kmod/ https://www.freshports.org/graphics/drm-fbsd12.0-kmod/ I'm sure improvements could be made to FreeBSD init, but all you're saying is you'd prefer one more like systemd. Then you're free to use something else. >You also forget about software argument, why to use freebsd if you would use linux-layer all the way. You aren't using a Linux layer all the way, you are for video card drivers. As for why, they're free software. Using the Linux ones makes more sense than building new ones from scratch.

ernst_klim 8y ago
>4.16 DRM I see. For 11.2 its 4.11, so it didn't support my vega card. Upgrade to 12 leaded me to kernel panic on startup on my shitty laptop's cpu, this bug [1]. >You aren't using a Linux layer all the way, you are for video card drivers. I was talking about lack of hardware and software support, so you need a compatibility layer for commercial linux software. [1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233534 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233534
- loeg 8y ago
  > I was talking about lack of hardware and software support, so you need a compatibility layer for commercial linux software. The linuxkpi kernel API compatibility layer is for open source software (e.g., dual-licensed BSD/GPL Linux DRM drivers), not for commercial Linux software. The linuxemul syscall ABI layer can be used to run commercial Linux software, but is an entirely different and unrelated component. It has nothing to do with hardware support. This is like claiming that because WINE exists, Linux uses Windows for hardware support.