On Thu, Jan 21, 2021 at 3:50 AM Emmanuel Vadot
wrote:
> On Wed, 20 Jan 2021 22:21:09 -0800
> Steve Kargl wrote:
>
> > On Thu, Jan 21, 2021 at 07:18:07AM +0100, Hans Petter Selasky wrote:
> > > On 1/21/21 7:13 AM, Steve Kargl wrote:
> > > > It is 'make buildkernel' in /usr/src after a 'make build
On Thu, Jan 21, 2021 at 11:50:15AM +0100, Emmanuel Vadot wrote:
> On Wed, 20 Jan 2021 22:21:09 -0800
> Steve Kargl wrote:
>
> > On Thu, Jan 21, 2021 at 07:18:07AM +0100, Hans Petter Selasky wrote:
> > > On 1/21/21 7:13 AM, Steve Kargl wrote:
> > > > It is 'make buildkernel' in /usr/src after a 'm
On Wed, 20 Jan 2021 22:21:09 -0800
Steve Kargl wrote:
> On Thu, Jan 21, 2021 at 07:18:07AM +0100, Hans Petter Selasky wrote:
> > On 1/21/21 7:13 AM, Steve Kargl wrote:
> > > It is 'make buildkernel' in /usr/src after a 'make buildworld'.
> > > I have 'PORTS_MODULES+= graphics/drm-current-kmod' in
On Thu, Jan 21, 2021 at 07:18:07AM +0100, Hans Petter Selasky wrote:
> On 1/21/21 7:13 AM, Steve Kargl wrote:
> > It is 'make buildkernel' in /usr/src after a 'make buildworld'.
> > I have 'PORTS_MODULES+= graphics/drm-current-kmod' in /etc/make.conf.
>
> Try to update the ports tree. I'm not awar
On 1/21/21 7:13 AM, Steve Kargl wrote:
It is 'make buildkernel' in /usr/src after a 'make buildworld'.
I have 'PORTS_MODULES+= graphics/drm-current-kmod' in /etc/make.conf.
Try to update the ports tree. I'm not aware of any current build issues
in this area.
--HPS
___
-current-kmod/work/drm-kmod-drm_v5.4.62_7/linuxkpi/gplv2/include/linux/pci.h:10:
> > In file included from
> > /usr/src/sys/compat/linuxkpi/common/include/linux/pci.h:51:
> > In file included from
> > /usr/src/sys/compat/linuxkpi/common/include/linux/dmapool.h:36:
> > In file i
On 1/21/21 6:46 AM, Steve Kargl wrote:
My buildkernel after a buildworld is dying with
In file included from
/media/obj/usr/src/i386.i386/sys/MOBILE/usr/ports/graphics/drm-current-kmod/work/drm-kmod-drm_v5.4.62_7/linuxkpi/gplv2/include/linux/pci.h:10:
In file included from
/usr/src/sys/compat
My buildkernel after a buildworld is dying with
In file included from
/media/obj/usr/src/i386.i386/sys/MOBILE/usr/ports/graphics/drm-current-kmod/work/drm-kmod-drm_v5.4.62_7/linuxkpi/gplv2/include/linux/pci.h:10:
In file included from
/usr/src/sys/compat/linuxkpi/common/include/linux/pci.h:51
On dc., gen. 13 2021, David Wolfskill wrote:
On Wed, Jan 13, 2021 at 02:52:32PM -0500, Robert Huff wrote:
Hans Petter Selasky :
> You need to update that DRM port you are using before the
> issue
> will be fixed.
I'm confused.
I have drm-current-kmod listed in PORTS_MODULE
And ... we have a winner. (So far.)
The system in question has 11+ hours uptime running:
FreeBSD 13.0-ALPHA1 #1 main-c1149-g79a5c790bd: Sat Jan 16 09:02:47 EST 2021
amd64
(Now rebuilding 1100+ ports )
I commented out the IGNORE line from drm-current-kmod;
Yesterday I typod:
> So, yes as I believe I said buildkernel ran successfully.
Please make that:
So, yes as I believe I said buildworld ran successfully.
[Whack! Whack! Whack!]
Respectfully,
Rober
Greg writes:
> also, did you upgrade the world?
> The version stuff that ports checks comes from /usr/include.
I follow the process specified at the end of UPDATING.
So, yes as I believe I said buildkernel ran successfully.
Respectfully,
On Thu, Jan 14, 2021 at 08:36, Robert Huff wrote:
Hello:
> I am trying to upgrade a system running:
>
> FreeBSD 13.0-CURRENT #0 r365372: Sun Sep 6 10:51:26 EDT 2020
amd64
>
> Per this discussion, I cannot compile the kernel because
> drm-current-kmod is
Hello:
> > I am trying to upgrade a system running:
> >
> > FreeBSD 13.0-CURRENT #0 r365372: Sun Sep 6 10:51:26 EDT 2020 amd64
> >
> > Per this discussion, I cannot compile the kernel because
> > drm-current-kmod is out-of-date.
> > When I try to upgrade drm-current-kmod (r
On Thu, Jan 14, 2021 at 08:05, Robert Huff wrote:
"Houston ... we have a problem."
Scenario: Chicken, meet egg?
I am trying to upgrade a system running:
FreeBSD 13.0-CURRENT #0 r365372: Sun Sep 6 10:51:26 EDT 2020 amd64
Per this discussion, I cannot compile
"Houston ... we have a problem."
Scenario: Chicken, meet egg?
I am trying to upgrade a system running:
FreeBSD 13.0-CURRENT #0 r365372: Sun Sep 6 10:51:26 EDT 2020 amd64
Per this discussion, I cannot compile the kernel because
drm-current-kmod is out-of-date.
Chris writes:
> >> Further: if I have that set ... does that mean I can
> >> remove it from PORTS_MODULES?
> >
> > I don't know what that is
> eg;
> PORTS_MODULES=x11/nvidia-driver-304
> for the nvidia driver, for example. see src.conf(5).
Actually make.conf(5).
On 2021-01-13 13:28, Emmanuel Vadot wrote:
On Wed, 13 Jan 2021 16:19:09 -0500
Robert Huff wrote:
Emmanuel Vadot writes:
>That's one of the problems of having external kmods.
>drm-current-kmod have the option by default to install it's
> sources in /usr/local/sys/ and when doing a
On Wed, 13 Jan 2021 16:19:09 -0500
Robert Huff wrote:
>
> Emmanuel Vadot writes:
>
> > That's one of the problems of having external kmods.
> > drm-current-kmod have the option by default to install it's
> > sources in /usr/local/sys/ and when doing a make buildkernel
> > those sou
Emmanuel Vadot writes:
> That's one of the problems of having external kmods.
> drm-current-kmod have the option by default to install it's
> sources in /usr/local/sys/ and when doing a make buildkernel
> those sources are getting built too.
That would be the SOURCE opt
>
That's one of the problems of having external kmods.
drm-current-kmod have the option by default to install it's sources
in /usr/local/sys/ and when doing a make buildkernel those sources are
getting built too.
One problem is that when, like with the latest update to linuxkpi tha
On Wed, Jan 13, 2021 at 02:52:32PM -0500, Robert Huff wrote:
>
> Hans Petter Selasky :
>
> > You need to update that DRM port you are using before the issue
> > will be fixed.
>
> I'm confused.
> I have drm-current-kmod listed in PORTS_MODULES; things on that
> list get built _af
Hans Petter Selasky :
> You need to update that DRM port you are using before the issue
> will be fixed.
I'm confused.
I have drm-current-kmod listed in PORTS_MODULES; things on that
list get built _after_ buildkernel (installkernel??) for reasons I
thought I understood.
Hi HPS! thanks, that solved the issue. sorry dint realize i had to
recompile the drm.
Cheers
Santi
On 1/13/21 2:45 PM, Hans Petter Selasky wrote:
> On 1/13/21 3:42 PM, Hans Petter Selasky wrote:
>> On 1/13/21 3:40 PM, Santiago Martinez wrote:
>>> Thanks Peter, this is what i got
>>>
>>> root@t
On 1/13/21 3:42 PM, Hans Petter Selasky wrote:
On 1/13/21 3:40 PM, Santiago Martinez wrote:
Thanks Peter, this is what i got
root@tucho:/usr/src # git status
On branch main
Your branch is up to date with 'origin/main'.
am i missing something?
portsnap fetch update
You need to update that
On 1/13/21 3:40 PM, Santiago Martinez wrote:
Thanks Peter, this is what i got
root@tucho:/usr/src # git status
On branch main
Your branch is up to date with 'origin/main'.
am i missing something?
portsnap fetch update
Maybe?
--HPS
___
freebsd-cu
Thanks Peter, this is what i got
root@tucho:/usr/src # git status
On branch main
Your branch is up to date with 'origin/main'.
am i missing something?
Santi
On 1/13/21 2:34 PM, Hans Petter Selasky wrote:
> On 1/13/21 3:31 PM, Santiago Martinez wrote:
>> Hi there,
>>
>> Just wondering if someb
On 1/13/21 3:31 PM, Santiago Martinez wrote:
Hi there,
Just wondering if somebody else is having issues building the kernel
(amd64) with the latest current.
I have tried with clean, etc and same issue.
Uploaded the make output into "pastebin.com"
https://pastebin.com/va5HCYtY
Try to updat
Hi there,
Just wondering if somebody else is having issues building the kernel
(amd64) with the latest current.
I have tried with clean, etc and same issue.
Uploaded the make output into "pastebin.com"
https://pastebin.com/va5HCYtY
Thanks
Santi
OpenPGP_signature
Description: OpenPGP d
required
by drm drivers that use linuxkpi.
A new drm-fbsd12.1-kmod port for 12-STABLE (later includes also
12.1-RELEASE) will be created. The goal is to provide support for
hardware that is supported by Linux 5.0, in FreeBSD 12.1.
In an emergency, drivers for 12-STABLE can (hopefully) be built direc
On 01/06/17 11:04, blubee blubeeme wrote:
I was looking at the linuxkpi source code in /sys/compat/linuxkpi and I had
a question.
A lot of those files just look like linux files brought over to FreeBSD, is
there any reason why those files couldn't be implemented in BSD w/o the
dependenci
I was looking at the linuxkpi source code in /sys/compat/linuxkpi and I had
a question.
A lot of those files just look like linux files brought over to FreeBSD, is
there any reason why those files couldn't be implemented in BSD w/o the
dependencies on the other Linux headers?
For example
32 matches
Mail list logo
