Re: Current kernel build broken with linuxkpi?
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_MODULES; things on that list get built _after_ buildkernel (installkernel??) for reasons I thought I understood. You are telling me I need to update this _before_ buildkernel? Perplexedly, He telling you to update the port itself -- e.g., /usr/ports/graphics/drm-kmod, as the port was recently updated: r561457 | manu | 2021-01-13 03:22:25 -0800 (Wed, 13 Jan 2021) | 6 lines graphics/drm-{current,devel}-kmod: Update to latest source This fix a compilation problem with a pre 1300135 source tree. Reported by:Filippo Moretti So you need to update the "ports files" to get that update, then rebuild the port (in concert with rebuilding the kernel, as you are doing). Peace, david Just as a curiosity because I was hit by this and the thread was helpful: I was unable to build the kernel with an up to date drm-current-kmod, but as soon as I switched to drm-devel-kmod, I was able to. The running kernel was uname -K: 1300133. Thanks everyone for having added their input here. -- Evilham ___ 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: Current kernel build broken with linuxkpi?
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; built successfully; built the kernel - successfully; and installed kernel then world with no hiccups. Thanks to everyone for their help. Respectfully, Robert Huff -- Hello ... my name is SARS-CoV-2. You are not wearing a mask? Prepare to die! ___ 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: Current kernel build broken with linuxkpi?
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, Robert "ENOBRAIN" Huff -- Hello ... my name is SARS-CoV-2. You are not wearing a mask? Prepare to die! ___ 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: Current kernel build broken with linuxkpi?
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, Robert Huff -- Hello ... my name is SARS-CoV-2. You are not wearing a mask? Prepare to die! ___ 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: Current kernel build broken with linuxkpi?
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 out-of-date. > When I try to upgrade drm-current-kmod (r561457) I get: > > ===> drm-current-kmod-5.4.62.g20210113 not supported on older > CURRENT, no > kernel support. > *** Error code 1 > > Stop. > make: stopped in /usr/ports/graphics/drm-current-kmod > > Huh? > What is my path forward? (That does not involve reinstalling the > OS.) Either upgrade the kernel without the drm PORTS_ whatever thing h upgrade drm-current-kmod h add back the PORTS_thing if you really want it upgrade kernel again If I understand things correctly: things in the PORTS_MODULES list are upgraded _after_ the kernel is completely rebuilt. I am hitting this _during_ the rebuild. I'm not sure if they will be upgraded after it's installed.. also, did you upgrade the world? The version stuff that ports checks comes from /usr/include. So the question becomes: _will_ removing the IGNORE line work? Why wouldn't it? ___ 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: Current kernel build broken with linuxkpi?
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 (r561457) I get: > > > > ===> drm-current-kmod-5.4.62.g20210113 not supported on older > > CURRENT, no > > kernel support. > > *** Error code 1 > > > > Stop. > > make: stopped in /usr/ports/graphics/drm-current-kmod > > > > Huh? > > What is my path forward? (That does not involve reinstalling the > > OS.) > > Either > > upgrade the kernel without the drm PORTS_ whatever thing �� > upgrade drm-current-kmod �� add back the PORTS_thing if you > really want it upgrade kernel again If I understand things correctly: things in the PORTS_MODULES list are upgraded _after_ the kernel is completely rebuilt. I am hitting this _during_ the rebuild. So the question becomes: _will_ removing the IGNORE line work? Respectfully, Robert Huff -- Hello ... my name is SARS-CoV-2. You are not wearing a mask? Prepare to die! ___ 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: Current kernel build broken with linuxkpi?
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 the kernel because drm-current-kmod is out-of-date. When I try to upgrade drm-current-kmod (r561457) I get: ===> drm-current-kmod-5.4.62.g20210113 not supported on older CURRENT, no kernel support. *** Error code 1 Stop. make: stopped in /usr/ports/graphics/drm-current-kmod Huh? What is my path forward? (That does not involve reinstalling the OS.) Either upgrade the kernel without the drm PORTS_ whatever thing → upgrade drm-current-kmod → add back the PORTS_thing if you really want it → upgrade kernel again or remove the IGNORE line in the port's Makefile → upgrade drm-current-kmod → upgrade the kernel. You have discovered precisely why this (building kmods from ports when building the kernel itself) is not a very good feature :) ___ 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: Current kernel build broken with linuxkpi?
"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. When I try to upgrade drm-current-kmod (r561457) I get: ===> drm-current-kmod-5.4.62.g20210113 not supported on older CURRENT, no kernel support. *** Error code 1 Stop. make: stopped in /usr/ports/graphics/drm-current-kmod Huh? What is my path forward? (That does not involve reinstalling the OS.) Anxiously, Robert Huff -- Hello ... my name is SARS-CoV-2. You are not wearing a mask? Prepare to die! ___ 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: Current kernel build broken with linuxkpi?
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). Respectfully, Robert Huff -- Hello ... my name is SARS-CoV-2. You are not wearing a mask? Prepare to die! ___ 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: Current kernel build broken with linuxkpi?
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 make buildkernel > those sources are getting built too. That would be the SOURCE option? Yes 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). (And I assume a note about this will appear in UPDATING?) A note about what ? Cheers, Respectfully, Robert Huff ___ 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" ___ 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: Current kernel build broken with linuxkpi?
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 sources are getting built too. > > That would be the SOURCE option? Yes > Further: if I have that set ... does that mean I can remove it > from PORTS_MODULES? I don't know what that is > (And I assume a note about this will appear in UPDATING?) A note about what ? Cheers, > > Respectfully, > > > Robert Huff > > > ___ > 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" -- Emmanuel Vadot ___ 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: Current kernel build broken with linuxkpi?
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 option? Further: if I have that set ... does that mean I can remove it from PORTS_MODULES? (And I assume a note about this will appear in UPDATING?) Respectfully, Robert Huff ___ 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: Current kernel build broken with linuxkpi?
On Wed, 13 Jan 2021 14:52:32 -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 _after_ buildkernel (installkernel??) for reasons I > thought I understood. > You are telling me I need to update this _before_ buildkernel? > > > Perplexedly, > > > Robert Huff > 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 that I did, we introduce changes that breaks external kmods, you first need to upgrade your ports/package (not your ports tree) so the new sources are updated too and then do a make buildkernel. That really sucks but still helps a bit when there isn't conflicted changes in the source tree but you still need to rebuild your kernel module. -- Emmanuel Vadot ___ 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: Current kernel build broken with linuxkpi?
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 _after_ buildkernel (installkernel??) for reasons I > thought I understood. > You are telling me I need to update this _before_ buildkernel? > > > Perplexedly, > He telling you to update the port itself -- e.g., /usr/ports/graphics/drm-kmod, as the port was recently updated: r561457 | manu | 2021-01-13 03:22:25 -0800 (Wed, 13 Jan 2021) | 6 lines graphics/drm-{current,devel}-kmod: Update to latest source This fix a compilation problem with a pre 1300135 source tree. Reported by:Filippo Moretti So you need to update the "ports files" to get that update, then rebuild the port (in concert with rebuilding the kernel, as you are doing). Peace, david -- David H. Wolfskill da...@catwhisker.org "What happened at the Capitol last Wednesday, then, wasn't the first time Trump's base took him literally. It was the culmination of having taken him literally the entire duration of his presidency." - Chris Cillizza See https://www.catwhisker.org/~david/publickey.gpg for my public key. signature.asc Description: PGP signature
Re: Current kernel build broken with linuxkpi?
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. You are telling me I need to update this _before_ buildkernel? Perplexedly, Robert Huff -- Hello ... my name is SARS-CoV-2. You are not wearing a mask? Prepare to die! ___ 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: Current kernel build broken with linuxkpi?
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@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 DRM port you are using before the issue will > be fixed. > > --HPS > > ___ > 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" OpenPGP_signature Description: OpenPGP digital signature
Re: Current kernel build broken with linuxkpi?
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 DRM port you are using before the issue will be fixed. --HPS ___ 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: Current kernel build broken with linuxkpi?
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-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: Current kernel build broken with linuxkpi?
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 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 update your ports tree. I believe manu@ just fixed this. > > --HPS > > ___ > 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" OpenPGP_signature Description: OpenPGP digital signature
Re: Current kernel build broken with linuxkpi?
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 update your ports tree. I believe manu@ just fixed this. --HPS ___ 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"