Running 'pkg version' in a stable/12 jail under FreeBSD 13.0-ALPHA1
Hi! I have two BEs: default (stable/12-c243202-g49038d1723a9) and fbsd13 (main-c255946-gbd72252aace3) and a stable/12 jail. Ports tree is mounted ro,nullfs from the host into the jail. 1. Booting the default BE and running pkg in the jail: # pkg version -vPL= meson-0.56.0 < needs updating (port has 0.56.2) mutt-2.0.3 < needs updating (port has 2.0.4) 2. Booting the fbsd13 BE and running pkg in the jail: # pkg version -vPL= autoconf-2.69_3? orphaned: devel/autoconf [...] meson-0.56.0 ? orphaned: devel/meson mime-support-3.62 ? orphaned: misc/mime-support mutt-2.0.3 ? orphaned: mail/mutt [...] zstd-1.4.5_1 ? orphaned: archivers/zstd This also happens with a svn checkout of ports inside the jail. -- Herbert ___ 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: Running 'pkg version' in a stable/12 jail under FreeBSD 13.0-ALPHA1
On Thu, 14 Jan 2021 10:42:55 +0100, "Herbert J. Skuhra" wrote: > > Hi! > > I have two BEs: default (stable/12-c243202-g49038d1723a9) and fbsd13 > (main-c255946-gbd72252aace3) and a stable/12 jail. Ports tree is > mounted ro,nullfs from the host into the jail. > > 1. Booting the default BE and running pkg in the jail: > > # pkg version -vPL= > meson-0.56.0 < needs updating (port has 0.56.2) > mutt-2.0.3 < needs updating (port has 2.0.4) > > 2. Booting the fbsd13 BE and running pkg in the jail: > > # pkg version -vPL= > autoconf-2.69_3? orphaned: devel/autoconf > [...] > meson-0.56.0 ? orphaned: devel/meson > mime-support-3.62 ? orphaned: misc/mime-support > mutt-2.0.3 ? orphaned: mail/mutt > [...] > zstd-1.4.5_1 ? orphaned: archivers/zstd > > This also happens with a svn checkout of ports inside the jail. Please ignore. This is obviously not supported: make: "/usr/ports/Mk/bsd.port.mk" line 1204: UNAME_r (13.0-CURRENT) and OSVERSION (1202505) do not agree on major version number. I thought this had worked a few days ago. I have to run: env UNAME_r=12.2-STABLE pkg version -vPL= -- Herbert ___ 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?
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?
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: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?
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: boot loader blank screen
Is there a bugzilla issue for this yet? It's affecting a lot of people, and it will be easier for us to monitor progress with Bugzilla than with the mailing list. -Alan On Thu, Jan 14, 2021 at 12:15 AM Jakob Alvermark wrote: > > On 1/14/21 4:49 AM, monochrome wrote: > > I should add my experience to this since its different and haven't > > seen anyone else mention it. > > I see the new boot loader, it's not blank, but its large text, and > > it's very SLOW. > > I can see each char drawn, and then when it gets to the bottom and has > > to redraw all the lines to scroll up for new lines, it loads so slowly > > it's like watching an 8086 on a 300 baud modem, or slower! Takes like > > an extra 30 seconds to get through all the loaded modules, then back > > to normal speed boot with the same large font. > > > > added these lines and everything is back to normal with new appearance > > and small font like before, and at normal speed. > > hw.vga.textmode="0" > > vbe_max_resolution=1280x800 > > > > also removed the old lines for the amdgpu efi problem with no effect > > so I assume those are no longer necessary and why I'm seeing this change? > > #hw.syscons.disable=1 > > #kern.vty=vt > > #hw.vga.textmode=1 > > > > am using X and everything seems fine for now > > > > system: > > AMD Ryzen 5 2400G, using integrated vega GPU > > ASRock B450M Pro4 > > 13-current > > > > > > > > On 1/5/21 8:54 PM, David Wolfskill wrote: > >> On Wed, Jan 06, 2021 at 12:46:08AM +0200, Toomas Soome wrote: > >>> ... > the 58661b3ba9eb should hopefully fix the loader text mode issue, > it would be cool if you can verify:) > > thanks, > toomas > >>> > >>> I think, I got it fixed (at least idwer did confirm for his system, > >>> thanks). If you can test this patch: > >>> > http://148-52-235-80.sta.estpak.ee/0001-loader-rewrite-font-install.patch > >>> < > http://148-52-235-80.sta.estpak.ee/0001-loader-rewrite-font-install.patch> > > >>> it would be really nice. > >>> > >>> thanks, > >>> toomas > >> > >> I tested with each of the following "stanzas' in /boot/loader.conf, > >> using vt (vs. syscons) in each case (though that breaks video reset > >> on resume after suspend): > >> > >> # hw.vga.textmode="0" > >> vbe_max_resolution=1280x800 > >> > >> This works, and provides a graphical console (depth 32). > >> > >> > >> hw.vga.textmode="0" > >> # vbe_max_resolution=1280x800 > >> > >> This also works, and provides a low-resolution (and depth 16) > >> graphical console (800x320 or something similar, IIRC). > >> > >> > >> # hw.vga.textmode="0" > >> # vbe_max_resolution=1280x800 > >> > >> (That is, not specifying anything for hw.vga.textmode or > >> vbe_max_resolution.) > >> > >> This boots OK, but I see no kernel probe messages or single- to > >> multi-user mode messages. I can use (e.g.) Ctl+Alt+F2 to switch to > >> vty1, see a "login: " prompt, and that (also) works. (This is the > >> initial symptom I had reported.) > >> > >> > >> hw.vga.textmode="1" > >> # vbe_max_resolution=1280x800 > >> > >> This works -- boots OK, and I see kernel probe (&c.) messages; this is a > >> text console (mostly blue text; some white, against a dark background. > >> It's a medium-light blue, so it's easy enough to read (unlike a navy > >> blue, for example). > >> > >> > >> FreeBSD g1-55.catwhisker.org 13.0-CURRENT FreeBSD 13.0-CURRENT #113 > >> main-c255601-g9fd96b416c45-dirty: Tue Jan 5 17:24:45 PST 2021 > >> r...@g1-55.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY > > >> amd64 > > > +1 on the slowness. > > I like the graphics mode, it's very pretty. > > But slow. It seems to depend a lot on the screen resolution. On my small > laptop, 1366x768, it's fairly OK. On the 1080p laptop it is very much > slower, it takes about 35 seconds longer compared to the old loader. > > Booting on a 4K monitor, well, I didn't time it... > > > Jakob > > ___ > 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"
