pkg, drm-next-kmod and base packages

Discussion:

(too old to reply)

Boris Samorodov

2018-05-09 18:59:58 UTC

Hi All,

I use self-built base packages. How can I test/use drm-next-kmod?
Packages for kernel and drm-nex-kmod are in conflict:
-----
╰→ sudo pkg install drm-next-kmod-4.11.g20180224

Updating FreeBSD-base repository catalogue...
FreeBSD-base repository is up to date.
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
Updating passap repository catalogue...
passap repository is up to date.
All repositories are up to date.
Checking integrity... done (1 conflicting)
- drm-next-kmod-4.11.g20180224 [FreeBSD] conflicts with
FreeBSD-kernel-pkg64x-12.0.s20180509041454 [installed] on
/boot/modules/drm.ko
Checking integrity... done (0 conflicting)
The following 3 package(s) will be affected (of 0 checked):

Installed packages to be REMOVED:
FreeBSD-kernel-pkg64x-12.0.s20180509041454

New packages to be INSTALLED:
drm-next-kmod: 4.11.g20180224 [FreeBSD]
gpu-firmware-kmod: g20180206_1 [FreeBSD]

Number of packages to be removed: 1
Number of packages to be installed: 2

The operation will free 91 MiB.

Proceed with this action? [y/N]:
-----

--
WBR, bsam

Johannes Dieterich

2018-05-10 07:45:48 UTC

Permalink

Post by Boris Samorodov
Hi All,
I use self-built base packages. How can I test/use drm-next-kmod?
-----
╰→ sudo pkg install drm-next-kmod-4.11.g20180224
Updating FreeBSD-base repository catalogue...
FreeBSD-base repository is up to date.
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
Updating passap repository catalogue...
passap repository is up to date.
All repositories are up to date.
Checking integrity... done (1 conflicting)
- drm-next-kmod-4.11.g20180224 [FreeBSD] conflicts with
FreeBSD-kernel-pkg64x-12.0.s20180509041454 [installed] on
/boot/modules/drm.ko
Checking integrity... done (0 conflicting)
FreeBSD-kernel-pkg64x-12.0.s20180509041454
drm-next-kmod: 4.11.g20180224 [FreeBSD]
gpu-firmware-kmod: g20180206_1 [FreeBSD]
Number of packages to be removed: 1
Number of packages to be installed: 2
The operation will free 91 MiB.
-----

Since I don't have a system with pkgbase configured, is there a way to figure out what files conflict? It surprises me that there are any since we do not override anything normally (some kernel modules are indeed overlapping but they get installed in different directories).

Thanks,

jmd

Theron

2018-05-10 15:30:37 UTC

Permalink

Post by Johannes Dieterich
Hi

Post by Boris Samorodov
Hi All,
I use self-built base packages. How can I test/use drm-next-kmod?
-----
Checking integrity... done (1 conflicting)
- drm-next-kmod-4.11.g20180224 [FreeBSD] conflicts with
FreeBSD-kernel-pkg64x-12.0.s20180509041454 [installed] on
/boot/modules/drm.ko
Checking integrity... done (0 conflicting)
-----

Since I don't have a system with pkgbase configured, is there a way to figure out what files conflict?

The pkg output indicates that /boot/modules/drm.ko is the conflicting file.

Post by Johannes Dieterich
It surprises me that there are any since we do not override anything normally (some kernel modules are indeed overlapping but they get installed in different directories).

On a non-pkgbase -CURRENT system, drm.ko and drm2.ko from base are in
/boot/kernel/, while drm.ko from drm-stable-kmod is in /boot/modules/.
Any kernel modules from base being placed outside of /boot/kernel is not
what I would expect for a non-pkgbase system; is there a reason pkgbase
should not follow this rule?

Theron

Andreas Nilsson

2018-05-10 16:05:56 UTC

Permalink

Post by Theron

Post by Johannes Dieterich
Hi

Since I don't have a system with pkgbase configured, is there a way to
figure out what files conflict?

The pkg output indicates that /boot/modules/drm.ko is the conflicting file.

Post by Johannes Dieterich
It surprises me that there are any since we do not override anything
normally (some kernel modules are indeed overlapping but they get installed
in different directories).

On a non-pkgbase -CURRENT system, drm.ko and drm2.ko from base are in
/boot/kernel/, while drm.ko from drm-stable-kmod is in /boot/modules/. Any
kernel modules from base being placed outside of /boot/kernel is not what I
would expect for a non-pkgbase system; is there a reason pkgbase should not
follow this rule?
Theron

I recently converted my system to pkgbase, but I have no such package as
FreeBSD-kernel-pkg64x. How and from where did you get the sources?

I seem to remember that the git repo FreeBSDDesktop
<https://github.com/FreeBSDDesktop>/freebsd-base-graphics
<https://github.com/FreeBSDDesktop/freebsd-base-graphics> shipped the
module in /boot/modules. If you are using that git repo, you do not need
the port.

Best regards
Andreas

Boris Samorodov

2018-05-11 21:08:42 UTC

Permalink

Post by Andreas Nilsson

Post by Theron

Post by Johannes Dieterich
Hi

Since I don't have a system with pkgbase configured, is there a way to
figure out what files conflict?

The pkg output indicates that /boot/modules/drm.ko is the conflicting file.

Post by Johannes Dieterich
It surprises me that there are any since we do not override anything
normally (some kernel modules are indeed overlapping but they get installed
in different directories).

On a non-pkgbase -CURRENT system, drm.ko and drm2.ko from base are in
/boot/kernel/, while drm.ko from drm-stable-kmod is in /boot/modules/. Any
kernel modules from base being placed outside of /boot/kernel is not what I
would expect for a non-pkgbase system; is there a reason pkgbase should not
follow this rule?

I recently converted my system to pkgbase, but I have no such package as
FreeBSD-kernel-pkg64x. How and from where did you get the sources?

That is my custom kernel. I build that one and GENERIC plus their
counterparts with debug symbols per each build.

Post by Andreas Nilsson
I seem to remember that the git repo FreeBSDDesktop
<https://github.com/FreeBSDDesktop>/freebsd-base-graphics
<https://github.com/FreeBSDDesktop/freebsd-base-graphics> shipped the
module in /boot/modules. If you are using that git repo, you do not need
the port.

Actually my point is that pkg-base packages and ports packages are in
conflict and cannot coexist currently.

Post by Andreas Nilsson
Best regards
Andreas

--
WBR, bsam