Re: Loader goes to LINES=16 and kernel stays on that :(

On 2025-05-12 22:36, Toomas Soome wrote: On 12. May 2025, at 22:50, Jakob Alvermark wrote: On 2025-05-10 22:13, Adrian Chadd wrote: On Sat, 10 May 2025 at 13:10, Warner Losh wrote: Yea. This is due to the new, larger font and a hidden bug. Hasn't this been fixed in -HEAD? I though

Re: Loader goes to LINES=16 and kernel stays on that :(

> On 12. May 2025, at 22:50, Jakob Alvermark wrote: > > On 2025-05-10 22:13, Adrian Chadd wrote: >> >> >> On Sat, 10 May 2025 at 13:10, Warner Losh > > wrote: >>> Yea. This is due to the new, larger font and a hidden bug. >> >> Hasn't this been fixed in -HEAD? I tho

Re: Loader goes to LINES=16 and kernel stays on that :(

On 2025-05-10 22:13, Adrian Chadd wrote: On Sat, 10 May 2025 at 13:10, Warner Losh wrote: Yea. This is due to the new, larger font and a hidden bug. Hasn't this been fixed in -HEAD? I thought tsoome was working on it. Oh, here: https://reviews.freebsd.org/D50258 Want to try that out

Re: Loader goes to LINES=16 and kernel stays on that :(

On Sun, 11 May 2025, Toomas Soome wrote: On 11. May 2025, at 00:31, Bjoern A. Zeeb wrote: On Sat, 10 May 2025, Toomas Soome wrote: [..] https://reviews.freebsd.org/D50258 [..] It would be really nice if you could test it.Thanks, Toomas On it; I'll reboot as soon as buildworld dedic

Re: Loader goes to LINES=16 and kernel stays on that :(

.. and I use this to get a smaller font, in /etc/rc.conf : # font8x8="/usr/share/vt/fonts/vgarom-8x8.fnt" font8x16="/usr/share/vt/fonts/vgarom-8x16.fnt -adrian

Re: Loader goes to LINES=16 and kernel stays on that :(

> On 11. May 2025, at 00:31, Bjoern A. Zeeb > wrote: > > On Sat, 10 May 2025, Toomas Soome wrote: > > [..] >>> https://reviews.freebsd.org/D50258 > [..] > >> It would be really nice if you could test it.Thanks, >> Toomas > > On it; I'll reboot as soon as buildworld dedicded to rebuild hal

Re: Loader goes to LINES=16 and kernel stays on that :(

On Sat, 10 May 2025, Toomas Soome wrote: [..] https://reviews.freebsd.org/D50258 [..] It would be really nice if you could test it.Thanks, Toomas On it; I'll reboot as soon as buildworld dedicded to rebuild half my obj despite only applied the one change. I thought on main this is all inc

Re: Loader goes to LINES=16 and kernel stays on that :(

It would be really nice if you could test it.Thanks,ToomasSent from my iPhoneOn 10. May 2025, at 23:14, Adrian Chadd wrote:On Sat, 10 May 2025 at 13:10, Warner Losh wrote:Yea. This is due to the new, larger font and a hidden bug.  Hasn't this been fixed in -HEAD? I thought tsoom

Re: Loader goes to LINES=16 and kernel stays on that :(

On Sat, 10 May 2025 at 13:10, Warner Losh wrote: > Yea. This is due to the new, larger font and a hidden bug. > Hasn't this been fixed in -HEAD? I thought tsoome was working on it. Oh, here: https://reviews.freebsd.org/D50258 Want to try that out and see if it fixes things? -adrian > > Wa

Re: Loader goes to LINES=16 and kernel stays on that :(

Yea. This is due to the new, larger font and a hidden bug. Warner On Sat, May 10, 2025, 1:28 PM Bjoern A. Zeeb wrote: > Hi, > > I've been trying to get my laptop updated to main of the day for a > few days. > > loader.efi (lua) gets loaded; I see the EFI bits flashing by in a tiny > font and t

Re: Loader needs to be updated message

On Sun, Sep 08, 2024 at 11:23:46AM -0600, Warner Losh wrote: Great. This warning is new so people keep things uptodate. There has been minor breakage due to really old loader.efi not updating, but i backed that silent (mostly) breakage and added the loud version thing you see now. It shouldn't b

Re: Loader needs to be updated message

On Sun, Sep 8, 2024, 10:51 AM void wrote: > On Sun, Sep 08, 2024 at 09:14:50AM -0600, Warner Losh wrote: > >On Sun, Sep 8, 2024, 7:50 AM void wrote: > >> > >> Do you think a source upgrade on the server would fix the issue? > >> > >Yes. But the warning at this time isn't super urgent for you. It

Re: Loader needs to be updated message

On Sun, Sep 08, 2024 at 09:14:50AM -0600, Warner Losh wrote: On Sun, Sep 8, 2024, 7:50 AM void wrote: Do you think a source upgrade on the server would fix the issue? Yes. But the warning at this time isn't super urgent for you. It is telling you of problems in the future. Can confirm - th

Re: Loader needs to be updated message

On Sun, Sep 08, 2024 at 09:14:50AM -0600, Warner Losh wrote: On Sun, Sep 8, 2024, 7:50 AM void wrote: Do you think a source upgrade on the server would fix the issue? Yes. But the warning at this time isn't super urgent for you. It is telling you of problems in the future. related: do you

Re: Loader needs to be updated message

On Sun, Sep 8, 2024, 7:50 AM void wrote: > On Sat, Sep 07, 2024 at 09:34:27PM -0600, Warner Losh wrote: > > > >Yes. If you are getting the too old error, then there is a preupdate world > >booting a stable/13 after my change I think. > > > >Warner > > So, on the server (15.0-CURRENT #0 n270917-5d

Re: Loader needs to be updated message

On Sat, Sep 07, 2024 at 09:34:27PM -0600, Warner Losh wrote: Yes. If you are getting the too old error, then there is a preupdate world booting a stable/13 after my change I think. Warner So, on the server (15.0-CURRENT #0 n270917-5dbf886104b4: Thu Jul 4 ) ls -lah /boot/gptzfsboot -r--r--r-

Re: Loader needs to be updated message

On Sat, 7 Sep 2024 21:31:21 -0600 Warner Losh wrote: > On Sat, Sep 7, 2024, 9:16 PM Tomoaki AOKI wrote: > > > On Sat, 7 Sep 2024 19:38:47 -0700 > > Mark Millard wrote: > > > > > void wrote on > > > Date: Sat, 07 Sep 2024 17:27:00 UTC : > > > > > > > On Sat, Sep 07, 2024 at 08:20:07AM -0700, M

Re: Loader needs to be updated message

On Sat, Sep 7, 2024, 9:24 PM Tomoaki AOKI wrote: > On Sat, 7 Sep 2024 19:52:53 -0700 > Mark Millard wrote: > > > Tomoaki AOKI wrote on > > Date: Sun, 08 Sep 2024 01:54:28 UTC : > > > > > On Sun, 8 Sep 2024 02:01:02 +0100 > > > void wrote: > > > > > > > On Sun, Sep 08, 2024 at 09:23:02AM +0900,

Re: Loader needs to be updated message

On Sat, Sep 7, 2024, 9:16 PM Tomoaki AOKI wrote: > On Sat, 7 Sep 2024 19:38:47 -0700 > Mark Millard wrote: > > > void wrote on > > Date: Sat, 07 Sep 2024 17:27:00 UTC : > > > > > On Sat, Sep 07, 2024 at 08:20:07AM -0700, Mark Millard wrote: > > > > > > >I'm more interested in what is there than

Re: Loader needs to be updated message

On Sat, 7 Sep 2024 19:52:53 -0700 Mark Millard wrote: > Tomoaki AOKI wrote on > Date: Sun, 08 Sep 2024 01:54:28 UTC : > > > On Sun, 8 Sep 2024 02:01:02 +0100 > > void wrote: > > > > > On Sun, Sep 08, 2024 at 09:23:02AM +0900, Tomoaki AOKI wrote: > > > > > > . . . > > > > If not automounted,

Re: Loader needs to be updated message

On Sat, 7 Sep 2024 19:38:47 -0700 Mark Millard wrote: > void wrote on > Date: Sat, 07 Sep 2024 17:27:00 UTC : > > > On Sat, Sep 07, 2024 at 08:20:07AM -0700, Mark Millard wrote: > > > > >I'm more interested in what is there than just what is not > > >there. May be show something analogous to:

Re: Loader needs to be updated message

Tomoaki AOKI wrote on Date: Sun, 08 Sep 2024 01:54:28 UTC : > On Sun, 8 Sep 2024 02:01:02 +0100 > void wrote: > > > On Sun, Sep 08, 2024 at 09:23:02AM +0900, Tomoaki AOKI wrote: > > > > . . . > > If not automounted, you can mount ESP manually as msdosfs there, at > least for bare-metal host.

Re: Loader needs to be updated message

On Sat, Sep 7, 2024, 8:39 PM Mark Millard wrote: > void wrote on > Date: Sat, 07 Sep 2024 17:27:00 UTC : > > > On Sat, Sep 07, 2024 at 08:20:07AM -0700, Mark Millard wrote: > > > > >I'm more interested in what is there than just what is not > > >there. May be show something analogous to: > > > >

Re: Loader needs to be updated message

void wrote on Date: Sat, 07 Sep 2024 17:27:00 UTC : > On Sat, Sep 07, 2024 at 08:20:07AM -0700, Mark Millard wrote: > > >I'm more interested in what is there than just what is not > >there. May be show something analogous to: > > > ># gpart list | grep -E '(Name|type|efi|media)' > >1. Name: mmcs

Re: Loader needs to be updated message

On Sun, 8 Sep 2024 02:01:02 +0100 void wrote: > On Sun, Sep 08, 2024 at 09:23:02AM +0900, Tomoaki AOKI wrote: > > >Can it be in reverse? > > > >I've not read (even if it's already provided somewhere or attached) the > >vmrun.sh script, but isn't there any possibility that it somehow > >uses load

Re: Loader needs to be updated message

On Sun, Sep 08, 2024 at 09:23:02AM +0900, Tomoaki AOKI wrote: Can it be in reverse? I've not read (even if it's already provided somewhere or attached) the vmrun.sh script, but isn't there any possibility that it somehow uses loader on bare-metal (regardless on /boot/ or on ESP) to kick the gue

Re: Loader needs to be updated message

On Sat, 7 Sep 2024 17:07:23 -0600 Warner Losh wrote: > On Sat, Sep 7, 2024 at 12:24 PM void wrote: > > > On Sat, Sep 07, 2024 at 11:47:12AM -0600, Warner Losh wrote: > > >Wait. On the guest? > > > > > >Then what's the VM system you're using? > > > > > >Warner > > > > Bhyve. > > > > The server i

Re: Loader needs to be updated message

On Sat, Sep 7, 2024 at 12:24 PM void wrote: > On Sat, Sep 07, 2024 at 11:47:12AM -0600, Warner Losh wrote: > >Wait. On the guest? > > > >Then what's the VM system you're using? > > > >Warner > > Bhyve. > > The server is freebsd-current. The guest is 13.2-stable. > I see the error in the ascii bea

Re: Loader needs to be updated message

On Sat, Sep 07, 2024 at 11:47:12AM -0600, Warner Losh wrote: Wait. On the guest? Then what's the VM system you're using? Warner Bhyve. The server is freebsd-current. The guest is 13.2-stable. I see the error in the ascii beastie menu when booting the guest with vmrun.sh --

Re: Loader needs to be updated message

Wait. On the guest? Then what's the VM system you're using? Warner On Sat, Sep 7, 2024 at 11:27 AM void wrote: > On Sat, Sep 07, 2024 at 08:20:07AM -0700, Mark Millard wrote: > > >I'm more interested in what is there than just what is not > >there. May be show something analogous to: > > > >#

Re: Loader needs to be updated message

On Sat, Sep 07, 2024 at 08:20:07AM -0700, Mark Millard wrote: I'm more interested in what is there than just what is not there. May be show something analogous to: # gpart list | grep -E '(Name|type|efi|media)' 1. Name: mmcsd1s1 efimedia: HD(1,MBR,,0x8000,0x3b68000) rawtype: 12 t

Re: Loader needs to be updated message

void wrote on Date: Sat, 07 Sep 2024 13:19:24 UTC : > hello again, > > On Fri, Sep 06, 2024 at 03:13:59PM -0700, Mark Millard wrote: > > > >What shows if you do the likes of (showing an amd64 context example): > > > ># ls -lah /boot/efi/efi/*/* > >-r-xr-xr-x 1 root wheel 643K Aug 24 05:32 /boot/

Re: Loader needs to be updated message

hello again, On Fri, Sep 06, 2024 at 03:13:59PM -0700, Mark Millard wrote: What shows if you do the likes of (showing an amd64 context example): # ls -lah /boot/efi/efi/*/* -r-xr-xr-x 1 root wheel 643K Aug 24 05:32 /boot/efi/efi/BOOT/bootx64.efi -rwxr-xr-x 1 root wheel 643K Aug 24 05:32 /b

Re: Loader needs to be updated message

On Fri, Sep 06, 2024 at 03:13:59PM -0700, Mark Millard wrote: What shows if you do the likes of (showing an amd64 context example): # ls -lah /boot/efi/efi/*/* -r-xr-xr-x 1 root wheel 643K Aug 24 05:32 /boot/efi/efi/BOOT/bootx64.efi -rwxr-xr-x 1 root wheel 643K Aug 24 05:32 /boot/efi/efi/FR

Re: Loader needs to be updated message

void wrote on Date: Fri, 06 Sep 2024 18:12:10 UTC : > On Fri, Sep 06, 2024 at 09:00:58AM -0600, Warner Losh wrote: > > >man loader.efi has the instructions. > > I followed the instructions: > > # gpart list | grep -Ew '(Name|efi)' > 1. Name: da0p1 > type: efi > 2. Name: da0p2 > 3. Name: da0p3

Re: Loader needs to be updated message

On Sat, Sep 07, 2024 at 02:50:52AM +0900, Tomoaki AOKI wrote: Some additional explanation. Before, loader.efi itself could not be kicked directly from UEFI firmware and needs boot1.efi to kick loader.efi. In this case, boot code in ESP (uEFI System Partition, formatted with FAT32, 16 or possibl

Re: Loader needs to be updated message

On Fri, Sep 06, 2024 at 09:00:58AM -0600, Warner Losh wrote: man loader.efi has the instructions. I followed the instructions: # gpart list | grep -Ew '(Name|efi)' 1. Name: da0p1 type: efi 2. Name: da0p2 3. Name: da0p3 1. Name: da0 The manpage says: " Second, let's mount the

Re: Loader needs to be updated message

On Fri, 6 Sep 2024 09:00:58 -0600 Warner Losh wrote: > On Fri, Sep 6, 2024, 8:44 AM void wrote: > > > On Fri, Sep 06, 2024 at 08:25:16AM -0600, Warner Losh wrote: > > >On Fri, Sep 6, 2024 at 8:13 AM void wrote: > > > > > >> Hi, > > >> > > >> when booting -current (arm64) after building world &

Re: Loader needs to be updated message

On Fri, Sep 6, 2024, 8:44 AM void wrote: > On Fri, Sep 06, 2024 at 08:25:16AM -0600, Warner Losh wrote: > >On Fri, Sep 6, 2024 at 8:13 AM void wrote: > > > >> Hi, > >> > >> when booting -current (arm64) after building world & friends and > rebooting, > >> the beastie menu shows "Loader needs to

Re: Loader needs to be updated message

On Fri, Sep 06, 2024 at 08:25:16AM -0600, Warner Losh wrote: On Fri, Sep 6, 2024 at 8:13 AM void wrote: Hi, when booting -current (arm64) after building world & friends and rebooting, the beastie menu shows "Loader needs to be updated". I presume this to be gptzfsboot because the system is r

Re: Loader needs to be updated message

On Fri, Sep 6, 2024 at 8:13 AM void wrote: > Hi, > > when booting -current (arm64) after building world & friends and rebooting, > the beastie menu shows "Loader needs to be updated". > > I presume this to be gptzfsboot because the system is root-on-zfs. > > The issue I'm having is that I can't s

Re: Loader can't find /boot/ua/loader.lua on UFS after main-n255828-18054d0220c

On Mon, Jun 06, 2022 at 09:46:21AM +, Filippo Moretti wrote: > > Is it now safe to attempt updating current with UFS?SincerelyFilippo > Yes. Kirk committed a fix: commit bc218d89200faa021def77732f3d9fde4f4dee13 Author: Kirk McKusick Date: Tue May 31 19:55:54 2022 -0700 Two bug

Re: Loader can't find /boot/ua/loader.lua on UFS after main-n255828-18054d0220c

Is it now safe to attempt updating current with UFS?SincerelyFilippo On Wednesday, June 1, 2022 at 01:07:20 AM GMT+2, Warner Losh wrote: On Tue, May 31, 2022 at 3:55 PM Olivier Cochard-Labbé wrote: Same problem here:- I'm building FreeBSD head on a builder machine, and NFS mounti

Re: Loader can't find /boot/ua/loader.lua on UFS after main-n255828-18054d0220c

On Tue, May 31, 2022 at 3:55 PM Olivier Cochard-Labbé wrote: > Same problem here: > - I'm building FreeBSD head on a builder machine, and NFS mounting its > /usr/src and /usr/obj to 4 others > > Results: > - 2 of them, UEFI+ZFS machines works great ((Thinkpad T420 and AMD Epyc > with Tyan motherb

Re: Loader can't find /boot/ua/loader.lua on UFS after main-n255828-18054d0220c

Same problem here: - I'm building FreeBSD head on a builder machine, and NFS mounting its /usr/src and /usr/obj to 4 others Results: - 2 of them, UEFI+ZFS machines works great ((Thinkpad T420 and AMD Epyc with Tyan motherboard) - 2 of them, BIOS+UFS machines meet this "can't find /boot/ua/loader.l

Re: Loader can't find /boot/ua/loader.lua on UFS after main-n255828-18054d0220c

On 30 May 2022 8:38:27 pm AWST, David Wolfskill wrote: >On Mon, May 30, 2022 at 05:16:57AM -0700, Alastair Hogge wrote: >> ... >> I have not been able to use a new /boot/loader.efi (following -CURRENT) >> since >> mid to late 2021, and your symptoms look the same; fortunately, I found >> bug

Re: Loader can't find /boot/ua/loader.lua on UFS after main-n255828-18054d0220c

In message , Warner Losh writes: > --8495bd05e03b4d42 > Content-Type: text/plain; charset="UTF-8" > Content-Transfer-Encoding: quoted-printable > > On Mon, May 30, 2022 at 8:14 AM Toomas Soome wrote: > > > > > > > On 30. May 2022, at 17:06, Warner Losh wrote: > > > > > > > > On Mon,

Re: Loader can't find /boot/ua/loader.lua on UFS after main-n255828-18054d0220c

On Mon, May 30, 2022 at 8:14 AM Toomas Soome wrote: > > > On 30. May 2022, at 17:06, Warner Losh wrote: > > > > On Mon, May 30, 2022 at 4:26 AM David Wolfskill > wrote: > >> On Mon, May 30, 2022 at 08:40:10AM +0300, Toomas Soome wrote: >> > ... >> > Does loader_4th have same issue? >> > >>

Re: Loader can't find /boot/ua/loader.lua on UFS after main-n255828-18054d0220c

On Mon, May 30, 2022 at 08:06:32AM -0600, Warner Losh wrote: > ... > > On Mon, May 30, 2022 at 08:40:10AM +0300, Toomas Soome wrote: > > > ... > > > Does loader_4th have same issue? > > > > > > > I don't know; I hadn't tried it. I will do so later today & report > > back. > > > > So if it's

Re: Loader can't find /boot/ua/loader.lua on UFS after main-n255828-18054d0220c

> On 30. May 2022, at 17:06, Warner Losh wrote: > > > > On Mon, May 30, 2022 at 4:26 AM David Wolfskill > wrote: > On Mon, May 30, 2022 at 08:40:10AM +0300, Toomas Soome wrote: > > ... > > Does loader_4th have same issue? > > > > I don't know; I hadn't tri

Re: Loader can't find /boot/ua/loader.lua on UFS after main-n255828-18054d0220c

On Mon, May 30, 2022 at 4:26 AM David Wolfskill wrote: > On Mon, May 30, 2022 at 08:40:10AM +0300, Toomas Soome wrote: > > ... > > Does loader_4th have same issue? > > > > I don't know; I hadn't tried it. I will do so later today & report > back. > So if it's only one system, and it's only

Re: Loader can't find /boot/ua/loader.lua on UFS after main-n255828-18054d0220c

t; > So *those* get updated. > > > > I haven't updated from /boot/boot0 recently (and have a requirement that > > whatever is in the MBR is able to boot stable/12, stable/13, and head). > > > > Is updating (from head's /boot/bot0) recommended at this point?

Re: Loader can't find /boot/ua/loader.lua on UFS after main-n255828-18054d0220c

On Mon, May 30, 2022 at 05:16:57AM -0700, Alastair Hogge wrote: > ... > I have not been able to use a new /boot/loader.efi (following -CURRENT) > since > mid to late 2021, and your symptoms look the same; fortunately, I found > bug > report 264282[0] last night, which I think is related. Yamagi h

Re: Loader can't find /boot/ua/loader.lua on UFS after main-n255828-18054d0220c

On Mon, May 30, 2022 at 05:16:57AM -0700, Alastair Hogge wrote: > ... > I have not been able to use a new /boot/loader.efi (following -CURRENT) > since > mid to late 2021, and your symptoms look the same; fortunately, I found > bug > report 264282[0] last night, which I think is related. Yamagi h

Re: Loader can't find /boot/ua/loader.lua on UFS after main-n255828-18054d0220c

On 2022-05-30 07:10, David Wolfskill wrote: > -- but only on one machine (of the 3 that I use for daily tracking head > (and stable/12 & stable/13) -- the build machine ("freebeast"). > > Each is amd64, using ... venerable ... BIOS/MBR & UFS -- stuff that has > generally been functionally stable f

Re: Loader can't find /boot/ua/loader.lua on UFS after main-n255828-18054d0220c

On Mon, May 30, 2022 at 03:26:45AM -0700, David Wolfskill wrote: > On Mon, May 30, 2022 at 08:40:10AM +0300, Toomas Soome wrote: > > ... > > Does loader_4th have same issue? > > > > I don't know; I hadn't tried it. I will do so later today & report > back. > After updating sources fro

Re: Loader can't find /boot/ua/loader.lua on UFS after main-n255828-18054d0220c

r is in the MBR is able to boot stable/12, stable/13, and head). > > Is updating (from head's /boot/bot0) recommended at this point? > > > > (And in case it wasn't obvious, I made a silly typo in the Subject; it > should have read: > > | Subject: Re: Load

Re: Loader can't find /boot/ua/loader.lua on UFS after main-n255828-18054d0220c

On Mon, May 30, 2022 at 08:40:10AM +0300, Toomas Soome wrote: > ... > Does loader_4th have same issue? > I don't know; I hadn't tried it. I will do so later today & report back. Thanks! Peace, david -- David H. Wolfskill da...@catwhisker.org "Putin is a paran

Re: Loader can't find /boot/ua/loader.lua on UFS after main-n255828-18054d0220c

and head). > > Is updating (from head's /boot/bot0) recommended at this point? >> > > (And in case it wasn't obvious, I made a silly typo in the Subject; it > should have read: > > | Subject: Re: Loader can't find /boot/lua/loader.lua on UFS after > |  mai

Re: Loader can't find /boot/ua/loader.lua on UFS after main-n255828-18054d0220c

he MBR is able to boot stable/12, stable/13, and head). > > Is updating (from head's /boot/bot0) recommended at this point? >> > > (And in case it wasn't obvious, I made a silly typo in the Subject; it > should have read: > > | Subject: Re: Loader can'

Re: Loader can't find /boot/ua/loader.lua on UFS after main-n255828-18054d0220c

And in case it wasn't obvious, I made a silly typo in the Subject; it should have read: | Subject: Re: Loader can't find /boot/lua/loader.lua on UFS after | main-n255828-18054d0220c Sorry: I don't have loader messages showing up on serial console on that machine at this point, so I had

Re: Loader can't find /boot/ua/loader.lua on UFS after main-n255828-18054d0220c

Sorry for top posting... Did you upgrade your boot blocks? Warner On Sun, May 29, 2022, 5:11 PM David Wolfskill wrote: > -- but only on one machine (of the 3 that I use for daily tracking head > (and stable/12 & stable/13) -- the build machine ("freebeast"). > > Each is amd64, using ... venera

Re: loader/boot fonts are painfully small (again)

Why not add the option to in/decrease the font size with the +/- keys to the boot menu? And/or PgUP/Down or Up/Down arrow. Last resort: 9 & 0 are the last unused numbers in the boot menu. -- =|o) "Stell' Dir vor es geht und keiner kriegt's hin." (Wolfgang Neuss)

Re: loader/boot fonts are painfully small (again)

Am 15.02.2021 um 16:55 schrieb Daniel Nebdal: On Fri, 12 Feb 2021 at 15:33, Rodney W. Grimes < freebsd-...@gndrsh.dnsmgr.net> wrote: On 11. Feb 2021, at 23:21, Yuri Pankov wrote: Lenovo P51 laptop, 15'' 4k (3840x2160) display. Booting from the latest available current snapshot (20210107),

Re: loader/boot fonts are painfully small (again)

On Fri, 12 Feb 2021 at 15:33, Rodney W. Grimes < freebsd-...@gndrsh.dnsmgr.net> wrote: > > > > > > > On 11. Feb 2021, at 23:21, Yuri Pankov wrote: > > > > > > Lenovo P51 laptop, 15'' 4k (3840x2160) display. > > > > > > Booting from the latest available current snapshot (20210107), fonts > > > wer

Re: loader/boot fonts are painfully small (again)

> > > > On 11. Feb 2021, at 23:21, Yuri Pankov wrote: > > > > Lenovo P51 laptop, 15'' 4k (3840x2160) display. > > > > Booting from the latest available current snapshot (20210107), fonts > > were at least readable; updating to the latest bits (manually installing > > new loader as well) made t

Re: loader/boot fonts are painfully small (again)

> On 11. Feb 2021, at 23:21, Yuri Pankov wrote: > > Lenovo P51 laptop, 15'' 4k (3840x2160) display. > > Booting from the latest available current snapshot (20210107), fonts > were at least readable; updating to the latest bits (manually installing > new loader as well) made them really small

Re: loader lsdev crashes loader (Was: head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated)

On Tue, Oct 23, 2018 at 08:54:24AM -0600, Warner Losh wrote: > On Tue, Oct 23, 2018 at 5:54 AM Toomas Soome wrote: > > > > > > On 23 Oct 2018, at 13:53, Lev Serebryakov wrote: > > > > > > On 22.10.2018 12:27, Toomas Soome wrote: > > > > > >> It would help to get output from loader lsdev -v comma

Re: loader lsdev crashes loader (Was: head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated)

On Tue, Oct 23, 2018 at 5:54 AM Toomas Soome wrote: > > > On 23 Oct 2018, at 13:53, Lev Serebryakov wrote: > > > > On 22.10.2018 12:27, Toomas Soome wrote: > > > >> It would help to get output from loader lsdev -v command. > > current loader crashes on "lsdev" for me: > > https://bugs.freebsd.or

Re: loader lsdev crashes loader (Was: head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated)

> On 23 Oct 2018, at 13:53, Lev Serebryakov wrote: > > On 22.10.2018 12:27, Toomas Soome wrote: > >> It would help to get output from loader lsdev -v command. > current loader crashes on "lsdev" for me: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232483 (it is not > threadripper-related

Re: Loader post r338064 deletes GOP screen when asking geli passphrase

On Mon, Aug 20, 2018 at 1:01 PM, Harry Schmalzbauer wrote: > Hello, > > as far as I understand, r338064 should bring back default loader > environment. > > I'm UEFI booting r338093/amd64 (LynxPoint/Haswell). > > Since today, the GOP-console output of the first loader lines get deleted > when the g

Re: loader and load: path?

Anthony Jenkins From: Steven Hartland To: freebsd-current@freebsd.org Sent: Monday, March 7, 2016 9:18 AM Subject: Re: loader and load: path? So your saying "kldload zfs" fails because it can't find opensolaris or are you giving it absolute paths? If so try withou

Re: loader and load: path?

7, 2016 9:18 AM Subject: Re: loader and load: path? So your saying "kldload zfs" fails because it can't find opensolaris or are you giving it absolute paths? If so try without absolute paths. Regards Steve On 07/03/2016 14:09, Larry Rosenman wrote: > If I type load /

Re: loader and load: path?

So your saying "kldload zfs" fails because it can't find opensolaris or are you giving it absolute paths? If so try without absolute paths. Regards Steve On 07/03/2016 14:09, Larry Rosenman wrote: If I type load /boot/kernel/kernel, and then load /boot/kernel/zfs.ko, the loader (loade

RE: loader lszfs command

> -Original Message- > From: Garrett Cooper [mailto:yaneurab...@gmail.com] > Sent: Thursday, August 7, 2014 5:10 PM > To: dte...@freebsd.org > Cc: Sean Bruno; freebsd-current > Subject: Re: loader lszfs command > > On Thu, Aug 7, 2014 at 4:42 PM, wrote: > &

Re: loader lszfs command

On Thu, 7 Aug 2014 14:17-0700, dte...@freebsd.org wrote: > Hi, > > People have been pestering me to update the Forth code to present > a menu of ZFS datasets (*cough* boot environments *cough*). > > Would love to, but existing code seems broken. > > Can *anybody* produce meaningful output from

Re: loader lszfs command

On Thu, Aug 7, 2014 at 4:42 PM, wrote: > >> -Original Message- >> From: Garrett Cooper [mailto:yaneurab...@gmail.com] >> Sent: Thursday, August 7, 2014 4:29 PM >> To: sbr...@freebsd.org >> Cc: dte...@freebsd.org; freebsd-current >> Subject:

Re: loader lszfs command

On Thursday 07 August 2014 16:42:42 dte...@freebsd.org wrote: > Maybe if I update boot0 to a HEAD copy maybe? > Have already tried updating /boot/loader with no change. -r-xr-xr-x 1 root wheel 262144 Aug 1 12:24 /boot/loader* -r-xr-xr-x 1 root wheel 299008 Aug 1 12:24 /boot/zfsloader* It

RE: loader lszfs command

> -Original Message- > From: Garrett Cooper [mailto:yaneurab...@gmail.com] > Sent: Thursday, August 7, 2014 4:29 PM > To: sbr...@freebsd.org > Cc: dte...@freebsd.org; freebsd-current > Subject: Re: loader lszfs command > > Hi Devin! > > On Thu, Aug

Re: loader lszfs command

Hi Devin! On Thu, Aug 7, 2014 at 4:15 PM, Sean Bruno wrote: > On Thu, 2014-08-07 at 14:17 -0700, dte...@freebsd.org wrote: >> Hi, >> >> People have been pestering me to update the Forth code to present >> a menu of ZFS datasets (*cough* boot environments *cough*). >> >> Would love to, but existin

Re: loader lszfs command

On Thu, 2014-08-07 at 14:17 -0700, dte...@freebsd.org wrote: > Hi, > > People have been pestering me to update the Forth code to present > a menu of ZFS datasets (*cough* boot environments *cough*). > > Would love to, but existing code seems broken. > > Can *anybody* produce meaningful output fr

Re: loader don't load loader.conf if device.hints has errors

Hello, Lev. You wrote 10 августа 2013 г., 15:01:57: LS> Hello, Current. LS> I've make simple mistake (DOS-style EOL) in /boot/device.hints and LS> /boot/loader.conf was skipped too with strange (device.hints-related) LS> message: LS> FreeBSD/x86 bootstrap loader, Revision 1.1 LS> (r...@fbsd-c-64

Re: loader is aborted with 'out of memory'

In article <4f393b95.7070...@gmail.com> Chuck Burns writes: > On 2/13/2012 7:06 AM, TAKAHASHI Yoshihiro wrote: >> I got the following error of the current loader if I put the xxx_after >> line into loader.conf to wait a key after load the xxx module. >> >> --- >> Error: out of memory >> Module xx

Re: loader is aborted with 'out of memory'

On 2/13/2012 7:06 AM, TAKAHASHI Yoshihiro wrote: I got the following error of the current loader if I put the xxx_after line into loader.conf to wait a key after load the xxx module. --- Error: out of memory Module xxx Error executing read -p "Press Enter" Aborted! --- The loader.conf is: xxx_l

Re: loader crash / BTX halted on 9.0-RC2 DVD with AMD pseudo-RAID

On Tuesday, November 22, 2011 10:07:52 pm John Nielsen wrote: > On Nov 22, 2011, at 10:26 AM, John Baldwin wrote: > > > On Monday, November 21, 2011 1:45:36 pm John Nielsen wrote: > >> This weekend I downloaded the Freebsd 9.0 RC2 amd64 ISO image and burned > >> it > > to a DVD. I have a comput

Re: loader crash / BTX halted on 9.0-RC2 DVD with AMD pseudo-RAID

On Nov 22, 2011, at 10:26 AM, John Baldwin wrote: > On Monday, November 21, 2011 1:45:36 pm John Nielsen wrote: >> This weekend I downloaded the Freebsd 9.0 RC2 amd64 ISO image and burned it > to a DVD. I have a computer that currently runs Windows 7 but I plan to > install FreeBSD on it in the

Re: loader crash / BTX halted on 9.0-RC2 DVD with AMD pseudo-RAID

On Monday, November 21, 2011 1:45:36 pm John Nielsen wrote: > This weekend I downloaded the Freebsd 9.0 RC2 amd64 ISO image and burned it to a DVD. I have a computer that currently runs Windows 7 but I plan to install FreeBSD on it in the near future so I booted it up from the DVD to check the h

viapm attach failure (was Re: loader vs PCI)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 20-May-2003 Julian Elischer wrote: > > Is there any capability in the loader to do such things as get/set a PCI > config space register? > > Looking at the man page I'd say not, but there is mention of > some PNP capacity (though not currently w

Re: Loader-Problem with current kernel

David Wolfskill wrote: Did you remember to create /boot/device.hints? Cheers, david Hi, the file didn't exist so i just copied the /usr/src/sys/i386/conf/GENERIC.hints to /boot/device.hints. I think it is ok because i compiled the GENERIC-kernel. Unfortunately it doesn't help. The machine hang

Re: loader problem

Quoting Lars Eggert <[EMAIL PROTECTED]>: | Hi, | | after an installworld with last night's sources, my machine resets in | the the loader. It prints the "BTX loader" line, and then immediately | resets. I restored the old /boot/loader (from 10/2), which lets me boot | again. | | Any ide

Re: loader problem

Lars Eggert wrote: > > after an installworld with last night's sources, my machine resets in > the the loader. It prints the "BTX loader" line, and then immediately > resets. I restored the old /boot/loader (from 10/2), which lets me boot > again. > > Any ideas? The same happens on my laptop

Re: loader failure

On 16-May-2002 Dag-Erling Smorgrav wrote: > John Baldwin <[EMAIL PROTECTED]> writes: >> e -n 100 > > Yep, this (well, e -w -n 100 blah, and a number of variations) is what > I tried. This works on my PWS 500au but not on the DS20. >> e -n 100 vmem: > > I guess the address space specifier is

Re: loader failure

On Wed, 15 May 2002, John Baldwin wrote: > On 15-May-2002 Dag-Erling Smorgrav wrote: > > John Baldwin <[EMAIL PROTECTED]> writes: > >> The kernel overflowed it's stack. In SRM, you can try to debug this > >> by using 'e sp' to get the stack pointer then get a stack dump and save > >> a copy of i

Re: loader failure

John Baldwin <[EMAIL PROTECTED]> writes: > e -n 100 Yep, this (well, e -w -n 100 blah, and a number of variations) is what I tried. > e -n 100 vmem: I guess the address space specifier is what was missing. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PR

Re: loader failure

> > Brian Somers <[EMAIL PROTECTED]> writes: > > > This was fixed an hour or so ago. Phk backed out the daddr_t size > > > change pending investigation. > > > > Does that fix the loader too, or just the kernel? > > I'm not sure, I'm just rebuilding now. > > Remember, /boot/loader.old is left

Re: loader failure

On 15-May-2002 Dag-Erling Smorgrav wrote: > John Baldwin <[EMAIL PROTECTED]> writes: >> The kernel overflowed it's stack. In SRM, you can try to debug this >> by using 'e sp' to get the stack pointer then get a stack dump and save >> a copy of it in a log or something, reboot the machine, then u

Re: loader failure

> Brian Somers <[EMAIL PROTECTED]> writes: > > This was fixed an hour or so ago. Phk backed out the daddr_t size > > change pending investigation. > > Does that fix the loader too, or just the kernel? I'm not sure, I'm just rebuilding now. Remember, /boot/loader.old is left around... handy in

Re: loader failure

Brian Somers <[EMAIL PROTECTED]> writes: > This was fixed an hour or so ago. Phk backed out the daddr_t size > change pending investigation. Does that fix the loader too, or just the kernel? DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "u

Re: loader failure

> > no matter which kernel I try to boot. Booting my new kernel with the > > old loader (from the DP1 dist) works fine until it tries to start > > init(8): > > > > spec_getpages: preposterous offset 0xfff8f446 > > exec /sbin/init: error 5 > > spec_getpages: preposterous offset 0xfff8

Re: loader failure

John Baldwin <[EMAIL PROTECTED]> writes: > The kernel overflowed it's stack. In SRM, you can try to debug this > by using 'e sp' to get the stack pointer then get a stack dump and save > a copy of it in a log or something, reboot the machine, then use gdb's > list command on the kernel.debug to f

  1   2   >