Re: pkg, drm-next-kmod and base packages

[Boris Samorodov]

10.05.2018 19:05, Andreas Nilsson пишет:
> On Thu, May 10, 2018 at 5:30 PM, Theron  wrote:
> 
>> On 05/10/18 03:45, Johannes Dieterich wrote:
>>
>>> Hi
>>>
>>> On Wednesday, May 9, 2018, Boris Samorodov wrote:
>>>
 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:
 -
 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.
>>
>>> 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.

> I seem to remember that the git repo 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.

> Best regards
> Andreas

-- 
WBR, bsam
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: pkg, drm-next-kmod and base packages

[Andreas Nilsson]

On Thu, May 10, 2018 at 5:30 PM, Theron  wrote:

> On 05/10/18 03:45, Johannes Dieterich wrote:
>
>> Hi
>>
>> On Wednesday, May 9, 2018, Boris Samorodov wrote:
>>
>>> 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:
>>> -
>>> 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.
>
>> 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
/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
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: pkg, drm-next-kmod and base packages

[Theron]

On 05/10/18 03:45, Johannes Dieterich wrote:

Hi

On Wednesday, May 9, 2018, Boris Samorodov wrote:

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:
-
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.

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
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: pkg, drm-next-kmod and base packages

[Johannes Dieterich]

Hi

On Wednesday, May 9, 2018, Boris Samorodov wrote:
> 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]:
> -
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
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

pkg, drm-next-kmod and base packages

[Boris Samorodov]

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
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"