Re: uefi(8) fails to boot from ZFS with compression=zstd

2020-10-23 Thread Toomas Soome
Does it boot when you copy loader.efi to bootx64.efi? Toomas > On 23. Oct 2020, at 05:02, Jan Beich wrote: > > After r366657 (currently, on r366953) I've tried to boot from a > compression=zstd dataset but it failed to reach loader(8), see below. > However, switching to CSM path (boot1.efi

Re: Zpool doesn't boot anymore after FreeBSD 12.1

2020-10-22 Thread Toomas Soome
> On 22. Oct 2020, at 23:29, Cassiano Peixoto wrote: > > > Hi Toomas, > > Thank you for this patch. Can I know when it will be MFCed? I'd like to try. MFC will take a bit because I need to bring it together with asize updates, so we would need to do a bit of cherry-picking and testing.

Re: Zpool doesn't boot anymore after FreeBSD 12.1

2020-10-22 Thread Toomas Soome
Hi! Please try 366951:) I think, it should get things better for you. rgds, toomas > On 22. Oct 2020, at 20:37, Sergey V. Dyatko wrote: > > On Thu, 22 Oct 2020 16:42:16 +0300 > Andriy Gapon wrote: > >> On 22/10/2020 16:39, Cassiano Peixoto wrote: >>> Hi Andriy, >>> >>> I've just tried

Re: Zpool doesn't boot anymore after FreeBSD 12.1

2020-10-22 Thread Toomas Soome
> On 22. Oct 2020, at 16:42, Andriy Gapon wrote: > > On 22/10/2020 16:39, Cassiano Peixoto wrote: >> Hi Andriy, >> >> I've just tried copying my zfsloader from 11.2-STABLE (R350026) to FreeBSD >> 12.1 >> and 12.2 (STABLE) and fixed the issue. >> >> I also tried to use zfsloader of 11.3 but

Re: Zpool doesn't boot anymore after FreeBSD 12.1

2020-10-22 Thread Toomas Soome
There are few issues. with vmware, you should rather grow existing boot disk - just to keep setup simple. If you are adding disks, make sure they are properly partitioned. int13 error code 4 should be ’sector not found’, I have no idea why are you getting this one, but clearly there is

Re: Freeze during early boot

2020-09-10 Thread Toomas Soome
> On 10. Sep 2020, at 03:57, Mason Loring Bliss wrote: > > Hi, all. I'd like to see FreeBSD running on a new class of box I've got > here. Not new hardware. These are Atom chips on Micro-ITX motherboards, and > are interesting in that they are low-power and have dual gigabit NICs. > They're

Re: OpenZFS support merged

2020-08-25 Thread Toomas Soome
> On 25. Aug 2020, at 22:49, driesm.michi...@gmail.com wrote: > >> -Original Message- >> From: owner-freebsd...@freebsd.org On >> Behalf Of Matthew Macy >> Sent: Tuesday, 25 August 2020 04:39 >> To: freebsd-current ; freebsd-fs > f...@freebsd.org>; freebsd-hack...@freebsd.org >>

Re: OpenZFS support merged

2020-08-25 Thread Toomas Soome
> On 25. Aug 2020, at 19:35, Danilo Egêa Gondolfo wrote: > > On Tue, Aug 25, 2020 at 3:39 AM Matthew Macy wrote: > >> r364746 merged OpenZFS support in to HEAD. >> >> The change should be transparent unless you want to use new features. >> I caution against 'zpool upgrade' for the next few

Re: Geli encryption issue on r362779

2020-07-10 Thread Toomas Soome
> On 10. Jul 2020, at 18:05, Thomas Laus wrote: > >> On 2020-07-10 03:56, Toomas Soome wrote: >>> >>> ok, then next one is r363042. By nature it is an safeguard against read >>> past disk end. >>> >>> If that does not do, we really nee

Re: Boot failure on refreshed Dell Precision 7550

2020-07-10 Thread Toomas Soome
> On 10. Jul 2020, at 16:43, Shawn Webb wrote: > > On Fri, Jul 10, 2020 at 04:36:41PM +0300, Toomas Soome wrote: >> >> >>> On 10. Jul 2020, at 16:25, Shawn Webb wrote: >>> >>> Hey all, >>> >>> I just got in a new Dell Pr

Re: Boot failure on refreshed Dell Precision 7550

2020-07-10 Thread Toomas Soome
> On 10. Jul 2020, at 16:25, Shawn Webb wrote: > > Hey all, > > I just got in a new Dell Precision 7550 laptop. Tried booting FreeBSD > on it and UEFI boot failed. The screen goes black immedately when > selecting the memstick and around ten to twenty seconds later, the > system reboots. >

Re: Geli encryption issue on r362779

2020-07-10 Thread Toomas Soome
> On 7. Jul 2020, at 19:18, Thomas Laus wrote: > > On 2020-07-07 08:26, Toomas Soome wrote: >> Hi! >> >> I believe, 362989 should fix your issue. Please do let me know. >> > I updated to r362989. I built world and kernel after clearing out >

Re: Geli encryption issue on r362779

2020-07-07 Thread Toomas Soome
Hi! I believe, 362989 should fix your issue. Please do let me know. thanks, toomas > On 30. Jun 2020, at 20:19, Thomas Laus wrote: > > On 2020-06-30 11:31, Toomas Soome wrote: >> >> hi! >> >> 362431: https://svnweb.freebsd.org/base?view=revision=362431 >&

Re: Geli encryption issue on r362779

2020-06-30 Thread Toomas Soome
> On 30. Jun 2020, at 20:19, Thomas Laus wrote: > > On 2020-06-30 11:31, Toomas Soome wrote: >> >> hi! >> >> 362431: https://svnweb.freebsd.org/base?view=revision=362431 >> >> The majority of the code is now shared with loader (libsa/libi386),

Re: Geli encryption issue on r362779

2020-06-30 Thread Toomas Soome
> On 30. Jun 2020, at 15:01, Thomas Laus wrote: > > This is a repost to this list because of my submission email address did > not match the one on record. > > == > List: > > I just upgraded a couple of computers from r362220 to r362779 and have > booting

Re: Why is the console a graphic/bitmapped console, and not text/character by default

2020-04-12 Thread Toomas Soome
> On 12. Apr 2020, at 08:34, Chris wrote: > > On Sun, 12 Apr 2020 08:04:43 +0300 Toomas Soome tso...@me.com > <mailto:tso...@me.com> said > >> You have UEFI setup? With UEFI, there is no text mode. >> If mouse copy/paste is working is not a property of scr

Re: Why is the console a graphic/bitmapped console, and not text/character by default

2020-04-11 Thread Toomas Soome
You have UEFI setup? With UEFI, there is no text mode. If mouse copy/paste is working is not a property of screen mode but it if the console driver does implement it or not. Sent from my iPhone > On 12. Apr 2020, at 07:41, Chris wrote: > > Sorry for the ling title. But wasn't sure how make

Re: When will the FreeBSD (u)EFI work?

2020-03-28 Thread Toomas Soome
> On 28. Mar 2020, at 05:28, Chris wrote: > > On Fri, 27 Mar 2020 18:31:50 -0700 bsd-li...@bsdforge.com > said > >> On Fri, 27 Mar 2020 17:27:27 -0600 Warner Losh i...@bsdimp.com said >> > On Fri, Mar 27, 2020 at 4:54 PM Chris wrote: >> > > > On Sat, 28 Mar

Re: head -r538966 on OrangePi+ 2ed: boot loader crashes when USB drive is present at power-on/boot: its a misaligned access by code from -r354746

2020-03-19 Thread Toomas Soome
I think this should fix it. We need to create copy of dos partition array, so we will get proper alignment. tsoome@freebsd-2:/usr/src % svn diff stand/common/part.c Index: stand/common/part.c === --- stand/common/part.c (revision

Re: what 3rd party boot mgr is required to boot multiple freebsd versions?

2020-03-17 Thread Toomas Soome
> On 17. Mar 2020, at 15:51, Matthew Seaman wrote: > > On 17/03/2020 12:58, Florian Limberger wrote: >> On 16.03.20 23:33, Chris wrote: >> >>> For the record. I'm *only* using FreeBSD in this situation. I >>> only mentioned Windows above, for the use of it's boot manager. >> >> If you only

about loader & console

2020-03-02 Thread Toomas Soome
Hi! I have been busy with other bits for some time, but now back to poking some bits. What we have now (on current): x86: vidconsole on BIOS systems. Text mode, the screen is managed by teken terminal emulator, we “draw” on vga text buffer. comconsole: serial port driver shared by BIOS and

Re: current does not boot on vmware fusion 11

2020-02-15 Thread Toomas Soome
> On 15. Feb 2020, at 22:19, Alexander V. Chernikov wrote: > > Hi folks, > > I upgraded vmware fusion to version 11 recently and noticed that my -amd64 VM > stops booting immediately after printing EFI framebuffer information. > > VM pops up a message stating that "The firmware encountered

Re: r351900 broke UEFI boot on VMware VMs

2020-02-14 Thread Toomas Soome
> On 14. Feb 2020, at 13:43, Yuri Pankov wrote: > > Hi Toomas, > > I was finally able to find the revision that has broken UEFI boot on VMware > VMs, that is ESXi 6.7 and Workstation 15.x, for me at least -- VM simply > powers off (sometimes with uninformative message about runtime

Re: Panic in gptzfsboot?

2020-02-05 Thread Toomas Soome
Fixed, sorry about the mess:) thanks, toomas > On 5. Feb 2020, at 12:30, Toomas Soome wrote: > > > >> On 5. Feb 2020, at 12:05, Stefan Eßer wrote: >> >> Am 05.02.20 um 10:14 schrieb Toomas Soome: >>>> On 5. Feb 2020, at 11:12, Stefan Eßer >>

Re: Panic in gptzfsboot?

2020-02-05 Thread Toomas Soome
> On 5. Feb 2020, at 12:05, Stefan Eßer wrote: > > Am 05.02.20 um 10:14 schrieb Toomas Soome: >>> On 5. Feb 2020, at 11:12, Stefan Eßer >> <mailto:s...@freebsd.org>> wrote: >>> >>> I have just re-built world and kernel and get a boot fail

Re: Panic in gptzfsboot?

2020-02-05 Thread Toomas Soome
> On 5. Feb 2020, at 11:12, Stefan Eßer wrote: > > I have just re-built world and kernel and get a boot failure: > > panic: free: guard2 fail @ 0x412f6c50 + 513 from unknown:0 > --> Press a key in the console to reboot <-- > > I'll try to boot from a memory stick, now, but wanted to let >

Re: btxld not found

2020-01-28 Thread Toomas Soome
> On 28. Jan 2020, at 18:08, Nick Hibma wrote: > > >> On Tue, Jan 28, 2020, 4:57 AM Nick Hibma > <mailto:n...@van-laarhoven.org>> wrote: >> > On 28/01 /2020, at 12:39, Toomas Soome > > <mailto:tso...@me.com>> wrote: >> > >&

Re: btxld not found

2020-01-28 Thread Toomas Soome
> On 28. Jan 2020, at 13:36, Nick Hibma wrote: > > Folks, > > Could anyone explain to me what I am doing wrong? make installworld fails > each time with the following error > > ===> stand/i386/libi386 (install) > ===> stand/i386/loader_4th (install) > strip -R .comment -R .note -o

Re: UEFI and loader.efi in base/head past r355103

2019-12-16 Thread Toomas Soome
> On 16. Dec 2019, at 08:30, Trond Endrestøl > wrote: > > On Sun, 15 Dec 2019 20:41+0100, Trond Endrestøl wrote: > >> I updated the loader.efi stored in the ESP of my laptop, Lenovo >> ThinkPad E590T (20NB), running boot firmware 1.22, as I wanted to try >> out base/head r355441. >> >> As

Re: EFI loader failure, after 20191114-r354699 Z87MX-D3H

2019-11-28 Thread Toomas Soome
> On 28. Nov 2019, at 22:20, Andrey Fesenko wrote: > > Fixed > Thanks. And yea, that one is nasty. I have some guess but nothing too solid… it may take time to get figured out. Have you tested BIOS boot? rgds, toomas > On Thu, Nov 28, 2019 at 11:18 PM Toom

Re: EFI loader failure, after 20191114-r354699 Z87MX-D3H

2019-11-28 Thread Toomas Soome
> On 28. Nov 2019, at 22:16, Andrey Fesenko wrote: > > On Thu, Nov 28, 2019 at 3:03 PM Toomas Soome <mailto:tso...@me.com>> wrote: >> >> hi! >> >> I did try to reach you, but mail did bounce back… >> >> unicast ping me:) >>

Re: EFI loader failure, after 20191114-r354699 Z87MX-D3H

2019-11-28 Thread Toomas Soome
hi! I did try to reach you, but mail did bounce back… unicast ping me:) rgds, toomas > On 28. Nov 2019, at 11:43, Andrey Fesenko wrote: > > Hello, > > Around starting 20191114 r354699 (memstick tested), my desktop not > boot normally. Boot only loader menu (black and white mode) after >

Testing needed:)

2019-11-25 Thread Toomas Soome
Hi! Can someone with arm media file path type of storage device and someone with apple UEFI 1.10 test https://reviews.freebsd.org/D22553 please:) Other tests are also very welcome:) thanks, toomas ___ freebsd-current@freebsd.org mailing list

Re: CURRENT October images do not create a bootable install

2019-11-08 Thread Toomas Soome
> On 8. Nov 2019, at 20:34, Chris wrote: > > On Fri, 8 Nov 2019 10:32:25 +0100 gljennj...@gmail.com > <mailto:gljennj...@gmail.com> said > >> On Thu, 07 Nov 2019 09:41:01 -0800 >> Chris wrote: >> > On Thu, 7 Nov 2019 17:28:16 +0200 Toomas Soome ts

Re: CURRENT October images do not create a bootable install

2019-11-07 Thread Toomas Soome
> On 7. Nov 2019, at 21:07, Chris wrote: > > On Thu, 7 Nov 2019 20:09:12 +0200 Toomas Soome tso...@me.com > <mailto:tso...@me.com> said > >> > On 7. Nov 2019, at 19:37, Chris.H wrote: >> > > On Thu, 7 Nov 2019 17:28:16 +0200 Toomas Soome tso...@me.c

Re: CURRENT October images do not create a bootable install

2019-11-07 Thread Toomas Soome
> On 7. Nov 2019, at 19:37, Chris.H wrote: > > On Thu, 7 Nov 2019 17:28:16 +0200 Toomas Soome tso...@me.com said > >> > On 7. Nov 2019, at 17:23, Daniel Nebdal wrote: >> > >> On Thu, 7 Nov 2019 09:49:52 +0100 gljennj...@gmail.com said >> >>

Re: CURRENT October images do not create a bootable install

2019-11-07 Thread Toomas Soome
> On 7. Nov 2019, at 17:23, Daniel Nebdal wrote: > >> On Thu, 7 Nov 2019 09:49:52 +0100 gljennj...@gmail.com said >> I chose GPT. > > Maybe whoever wrote the EFI/BIOS code in your machine went all-in on > "Legacy", and it only handles MBR disks (or disks < 2.2TB)? > After all, it seems like

Re: CURRENT October images do not create a bootable install

2019-11-07 Thread Toomas Soome
> On 7. Nov 2019, at 10:38, Chris wrote: > > On Thu, 7 Nov 2019 10:15:49 +0200 Toomas Soome tso...@me.com > <mailto:tso...@me.com> said > >> > On 7. Nov 2019, at 10:05, Chris wrote: >> > > On Thu, 7 Nov 2019 08:31:14 +0100 gljennj...@gmail.com

Re: CURRENT October images do not create a bootable install

2019-11-07 Thread Toomas Soome
> On 7. Nov 2019, at 10:05, Chris wrote: > > On Thu, 7 Nov 2019 08:31:14 +0100 gljennj...@gmail.com said > >> On Wed, 06 Nov 2019 17:23:08 -0800 >> Chris wrote: >> > I put a box together to test 13 about a mos ago. >> > It's a second gen core i3. But whether choosing automatic >> > disk

Re: SVN r354253 breaks buildworld

2019-11-02 Thread Toomas Soome
> On 2. Nov 2019, at 23:30, Michael Butler wrote: > > On 11/2/19 5:15 PM, Toomas Soome wrote: >> Should be fixed by r354265. > > The problem has moved .. now the kernel won't build .. > > Building /usr/obj/usr/src/amd64.amd64/sys/VM01/avl.o > Building /usr/obj/us

Re: SVN r354253 breaks buildworld

2019-11-02 Thread Toomas Soome
Should be fixed by r354265. rgds, toomas > On 2. Nov 2019, at 17:20, Michael Butler wrote: > > Something missing from SVN r354253? > > Building /usr/obj/usr/src/amd64.amd64/rescue/rescue/rescue > ld: error: undefined symbol: lz4_init referenced by spa_misc.c:2066 >

Re: SVN r354253 breaks buildworld

2019-11-02 Thread Toomas Soome
> On 2. Nov 2019, at 17:20, Michael Butler wrote: > > Something missing from SVN r354253? Yes, the fix is coming soon, sorry about it. rgds, toomas > > Building /usr/obj/usr/src/amd64.amd64/rescue/rescue/rescue > ld: error: undefined symbol: lz4_init referenced by spa_misc.c:2066 >

Re: Can't boot current on Minnowboard

2019-09-24 Thread Toomas Soome
> On 24 Sep 2019, at 21:12, Renato Botelho wrote: > > On 24/09/19 15:10, Toomas Soome wrote: >> >> >>> On 24 Sep 2019, at 20:50, Renato Botelho wrote: >>> >>> As reported at pfSense ticket [1], we can't see console after booting >>

Re: Can't boot current on Minnowboard

2019-09-24 Thread Toomas Soome
> On 24 Sep 2019, at 20:50, Renato Botelho wrote: > > As reported at pfSense ticket [1], we can't see console after booting > FreeBSD installer iso on Minnowboard. This video [2] demonstrates the > problem. > > Basically I can see all kernel messages but nothing from userland after > kernel

Re: Lockdown adaX numbers to allow booting ?

2019-09-19 Thread Toomas Soome
> On 19 Sep 2019, at 21:48, Kurt Jaeger wrote: > > Hi! > Also the question is, what you mean with ???system looses track > >>> I interpret the hang during boot as 'it looses track'. So I guess >>> it tries to read the kernel from the wrong drives. > >> no, loader does probe disks

Re: Lockdown adaX numbers to allow booting ?

2019-09-19 Thread Toomas Soome
> On 19 Sep 2019, at 18:57, Kurt Jaeger wrote: > > Hi! > >>> We have a system with 10 SATA disks. 2 disks are for the system, >>> 8 disks drive a data pool 'bck', configured as raidz2, for backup purposes: >>> >>> bck72.8T 38.7T 34.1T- - 1%53% 1.00x ONLINE

Re: Lockdown adaX numbers to allow booting ?

2019-09-19 Thread Toomas Soome
> On 19 Sep 2019, at 17:02, Kurt Jaeger wrote: > > Hi! > > We have a system with 10 SATA disks. 2 disks are for the system, > 8 disks drive a data pool 'bck', configured as raidz2, for backup purposes: > > bck72.8T 38.7T 34.1T- - 1%53% 1.00x ONLINE - > > The

Re: ESXi VM does not boot in UEFI mode from 20190906 snapshot ISO

2019-09-18 Thread Toomas Soome
> On 18 Sep 2019, at 18:01, Yuri Pankov wrote: > > I have tested several snapshot ISOs available for download: > > FreeBSD-13.0-CURRENT-amd64-20190822-r351363-disc1.iso - OK > FreeBSD-13.0-CURRENT-amd64-20190829-r351591-disc1.iso - OK > FreeBSD-13.0-CURRENT-amd64-20190906-r351901-disc1.iso -

Re: r352368 can't boot

2019-09-18 Thread Toomas Soome
> On 17 Sep 2019, at 14:21, Warner Losh wrote: > > > > On Tue, Sep 17, 2019, 11:24 AM Toomas Soome <mailto:tso...@me.com>> wrote: > > >> On 17 Sep 2019, at 13:09, Warner Losh > <mailto:i...@bsdimp.com>> wrote: >> >> >

Re: r352368 can't boot

2019-09-17 Thread Toomas Soome
> On 17 Sep 2019, at 13:09, Warner Losh wrote: > > > > On Tue, Sep 17, 2019, 6:47 AM Toomas Soome <mailto:tso...@me.com>> wrote: > > > > On 17 Sep 2019, at 08:30, KIRIYAMA Kazuhiko > <mailto:k...@truefc.org>> wrote: > > > >

Re: r352368 can't boot

2019-09-16 Thread Toomas Soome
> On 17 Sep 2019, at 08:30, KIRIYAMA Kazuhiko wrote: > > Hi,all > > Yesterday I've updated latest head (r352368) and rebuild > 13.0-CURRENT. All went fine, but when I boot, it's stopped > at boot stage. Then I typed `boot', booted normally and put > login prompt and login go ahead. But

Re: HELP: UEFI/ZFS Boot failure: Ignoring Boot000A: Only one DP found

2019-08-26 Thread Toomas Soome
> On 27 Aug 2019, at 08:08, Warner Losh wrote: > > On Mon, Aug 26, 2019, 5:32 PM Rebecca Cran > wrote: > >> On 8/26/19 5:22 AM, O. Hartmann wrote: >> >>> >>> the other thing is the weird Lenovo handling of the UEFI vars. The only >> way to >>> boot the E540

Re: HELP: UEFI/ZFS Boot failure: Ignoring Boot000A: Only one DP found

2019-08-21 Thread Toomas Soome
> On 22 Aug 2019, at 06:04, O. Hartmann wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Am Wed, 21 Aug 2019 22:29:29 + > greg@unrelenting.technology schrieb: > >> August 22, 2019 12:23 AM, "O. Hartmann" wrote: >> >>> Am Wed, 21 Aug 2019 15:58:24 -0500 >>> Karl

Re: HELP: UEFI/ZFS Boot failure: Ignoring Boot000A: Only one DP found

2019-08-21 Thread Toomas Soome
rgds, toomas > > On Wed, Aug 21, 2019 at 3:59 PM Karl Denninger wrote: > >> BEGIN PGP SIGNED MESSAGE- >>> Hash: SHA256 >>> >>> Am Wed, 21 Aug 2019 22:34:21 +0300 >>> Toomas Soome schrieb: >>> >>>>> On 21

Re: HELP: UEFI/ZFS Boot failure: Ignoring Boot000A: Only one DP found

2019-08-21 Thread Toomas Soome
> On 21 Aug 2019, at 22:30, O. Hartmann wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Am Wed, 21 Aug 2019 22:14:46 +0300 > Toomas Soome mailto:tso...@me.com>> schrieb: > >> If you drop into efi shell, can you start efi/boot/bootx64.efi

Re: HELP: UEFI/ZFS Boot failure: Ignoring Boot000A: Only one DP found

2019-08-21 Thread Toomas Soome
If you drop into efi shell, can you start efi/boot/bootx64.efi manually? you should have fs0: or like for ESP. rgds, toomas > On 21 Aug 2019, at 20:58, O. Hartmann wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > I ran into serious trouble booting several boxes off UEFI. On

Re: Can't boot current under bhyve on current

2019-08-16 Thread Toomas Soome
Could you test with larger memory setup - instead of 512M, 1-2G? rgds, toomas > On 16 Aug 2019, at 22:00, Sean Eric Fagan wrote: > >> I think vm-bhyve hides stderr output from bhyve by default, but there might >> be a flag to make it display the stderr output. Can you try doing that to >>

Re: PCengines APU2C4, 12-STABLE: bootloader failure: Panic: free: guard2 fail @ 0x1000 + 2311663946 from

2019-07-30 Thread Toomas Soome
> On 30 Jul 2019, at 15:43, O. Hartmann wrote: > > On Wed, 24 Jul 2019 18:07:22 +0300 > Toomas Soome wrote: > >>> On 24 Jul 2019, at 16:48, O. Hartmann wrote: >>> >>> -BEGIN PGP SIGNED MESSAGE- >>> Hash: SHA256 >>&

Re: PCengines APU2C4, 12-STABLE: bootloader failure: Panic: free: guard2 fail @ 0x1000 + 2311663946 from

2019-07-24 Thread Toomas Soome
> On 24 Jul 2019, at 21:30, Hartmann, O. wrote: > > On Wed, 24 Jul 2019 18:07:22 +0300 > Toomas Soome mailto:tso...@me.com>> wrote: > >>> On 24 Jul 2019, at 16:48, O. Hartmann >> <mailto:ohartm...@walstatt.org>> >>> wrote: >&g

Re: PCengines APU2C4, 12-STABLE: bootloader failure: Panic: free: guard2 fail @ 0x1000 + 2311663946 from

2019-07-24 Thread Toomas Soome
t;> Hash: SHA256 >> >> Am Wed, 24 Jul 2019 12:09:16 +0300 >> Toomas Soome schrieb: >> >>>> On 24 Jul 2019, at 11:11, O. Hartmann wrote: >>>> >>>> -BEGIN PGP SIGNED MESSAGE- >>>> Hash: SHA256 >>>>

Re: PCengines APU2C4, 12-STABLE: bootloader failure: Panic: free: guard2 fail @ 0x1000 + 2311663946 from

2019-07-24 Thread Toomas Soome
> On 24 Jul 2019, at 11:11, O. Hartmann wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Hallo, > > on APU2C4 from PCengines with latest firmware apu2_v4.9.0.7.rom, SeaBIOS > rel-1.12.1.3-0-g300e8b7, booting via legacy MBR FreeBSD 12-STABLE r350274 > (the same with >

Re: UEFI boot broken in 13?

2019-06-04 Thread Toomas Soome
> On 4 Jun 2019, at 04:38, Johannes Lundberg wrote: > > Hi > > I'm using poudriere-image to create usb memstick images. The images are > identical except OS version. They are tested on a laptop with 13-CURRENT > installed as only OS, having UEFI boot and root on zfs. > > 12-STABLE memstick

Re: Triveal bootloader patch for FreeBSD 11.2 regression

2019-05-05 Thread Toomas Soome
> On 5 May 2019, at 04:44, John Wehle wrote: > > Bug 236585 - BTX Halted upgrading FreeBSD 11.2 UFS from r344213 to r345199 > > has a triveal patch which may also apply to: > > Bug 215459 - Installing card reader causes bootloader to fail with BTX Halted > > Bug 235509 - BTX Freezes

Re: Got the same error from gptzfsboot this morning

2019-05-04 Thread Toomas Soome
> On 4 May 2019, at 21:34, Warner Losh wrote: > > On Thu, May 2, 2019 at 9:12 AM Thomas Laus wrote: > >> Toomas: >> >> My laptop has been booting up flawlessly since I installed the >> gptzfsboot file that you sent. It also successfully rebooted from a >> cold start this morning but I

Re: Question about 'gptzfsboot'

2019-04-29 Thread Toomas Soome
> On 29 Apr 2019, at 21:47, Thomas Laus wrote: > > On 2019-04-29 14:27, Thomas Laus wrote: >> It was more than a broken console. All of the other 2 computers that I >> upgraded to r346885 were essentially 'dead'. I could not even remotely >> login to them via ssh. All of them required a

Re: Question about 'gptzfsboot'

2019-04-26 Thread Toomas Soome
> On 26 Apr 2019, at 16:20, Thomas Laus wrote: > > Toomas Soome [tso...@me.com] wrote: >> >> The key is about LBA in first message. Make sure you have latest >> boot code installed with gpart. >> > I always update the bootcode with gpart each time w

Re: Question about 'gptzfsboot'

2019-04-26 Thread Toomas Soome
> On 26 Apr 2019, at 14:31, Thomas Laus wrote: > > List: > > I have been having gptzfsboot issues with my two laptops since 12.0 was > still CURRENT. I receive 'error 1' on the first boot most days. > > gptzfsboot: error 1 LBA 18446744072709551608 > gptzfsboot: error 1 LBA 1 > gptzfsboot:

Re: ZFS: can't read MOS of zpool...

2019-04-09 Thread Toomas Soome
When did you update the bootblocks last time? You can grab iso/usb image with current and check if loader there can see your pools - and if yes, update the boot blocks on disk… rgds, toomas > On 9 Apr 2019, at 20:37, Alexandre C. Guimarães wrote: > > Hello, > > I can't say the precise

Re: GPT boot has less features than legacy MBR-based one (Was: UEFI, loader.efi and /boot.config)

2019-01-21 Thread Toomas Soome
> On 21 Jan 2019, at 14:45, Lev Serebryakov wrote: > > On 21.01.2019 15:39, Toomas Soome wrote: > >>>> Is too complicated? Boot1.efi doesn't allow that, but loader.efi does. >>> loader.efi lives on ESP partition, do I understand it right? So, it >>&g

Re: GPT boot has less features than legacy MBR-based one (Was: UEFI, loader.efi and /boot.config)

2019-01-21 Thread Toomas Soome
> On 21 Jan 2019, at 14:15, Lev Serebryakov wrote: > > On 20.01.2019 20:05, Warner Losh wrote: > >> Is too complicated? Boot1.efi doesn't allow that, but loader.efi does. > loader.efi lives on ESP partition, do I understand it right? So, it > could not be damaged with "bad" upgrade? > > --

Re: GPT boot has less features than legacy MBR-based one (Was: UEFI, loader.efi and /boot.config)

2019-01-19 Thread Toomas Soome
> On 19 Jan 2019, at 11:52, Lev Serebryakov wrote: > > Hello Warner, > > Saturday, January 19, 2019, 12:17:29 AM, you wrote: > >> Also most UEFI BIOSes I've used (which isn't a lot) allow one to choose >> which Boot variable to use to boot. Some will even create new Boot >>

Re: GPT boot has less features than legacy MBR-based one (Was: UEFI, loader.efi and /boot.config)

2019-01-18 Thread Toomas Soome
> On 18 Jan 2019, at 21:33, Rodney W. Grimes > wrote: > >> >> >>> On 18 Jan 2019, at 19:57, Lev Serebryakov wrote: >>> >>> On 18.01.2019 20:13, Warner Losh wrote: >>> > Also, there are same problems with GPT/BIOS setup (which uses GPT but > legacy boot) :-( > What

Re: GPT boot has less features than legacy MBR-based one (Was: UEFI, loader.efi and /boot.config)

2019-01-18 Thread Toomas Soome
> On 18 Jan 2019, at 19:57, Lev Serebryakov wrote: > > On 18.01.2019 20:13, Warner Losh wrote: > >>> Also, there are same problems with GPT/BIOS setup (which uses GPT but >>> legacy boot) :-( >>> >> >> What same problems? I don't think we've touched how gptboot has handed off >> to

Re: UEFI, loader.efi and /boot.config

2019-01-18 Thread Toomas Soome
The loader.efi (EFI application) can receive command line arguments, set up in UEFI boot manager. rgds, toomas > On 18 Jan 2019, at 16:14, Kurt Jaeger wrote: > > Hello, > >> I was wondering if people will expect /boot.config to still be read and so >> code should be added to loader to

Re: Boot loader stuck after first stage upgrading 11.2 to 12.0-RC2

2018-12-04 Thread Toomas Soome
device checks. Rgds, Toomas Sent from my iPhone > On 4 Dec 2018, at 22:19, Ian Lepore wrote: > > On Tue, 2018-12-04 at 21:51 +0200, Toomas Soome via freebsd-stable > wrote: >> >>> >>> On 4 Dec 2018, at 19:59, Mark Martinec >> i> wrote: >>> &

Re: Boot loader stuck after first stage upgrading 11.2 to 12.0-RC2

2018-12-04 Thread Toomas Soome
> On 4 Dec 2018, at 19:59, Mark Martinec wrote: > >>> 2018-11-29 18:43, Toomas Soome wrote: >>>> I just did push biosdisk updates to stable/12, I wonder if you could >>>> test those bits… > > Myself wrote: >>> Thank you! I haven't tried

Re: Boot loader stuck after first stage upgrading 11.2 to 12.0-RC2

2018-12-02 Thread Toomas Soome
> On 2 Dec 2018, at 01:11, Mark Martinec wrote: > > 2018-11-29 18:43, Toomas Soome wrote: >> I just did push biosdisk updates to stable/12, I wonder if you could >> test those bits… > > Thank you! I haven't tried it yet, but I wonder whether this fix was > alre

Re: WITH_CTF breaks CD loader: "File too big"

2018-12-02 Thread Toomas Soome
> On 2 Dec 2018, at 17:08, Yuri Pankov wrote: > > Hi, > > Building disc1.iso using `make release` and having WITH_CTF set in > src.conf leads to "File too big" displayed when booting the image. > > Would it make sense to build loader and related parts without CTF > unconditionally as it

Re: Boot loader stuck after first stage upgrading 11.2 to 12.0-RC2

2018-11-29 Thread Toomas Soome
I just did push biosdisk updates to stable/12, I wonder if you could test those bits… rgds, toomas > On 29 Nov 2018, at 17:01, Mark Martinec wrote: > > After successfully upgraded three hosts from 11.2-p4 to 12.0-RC2 (amd64, > zfs, bios), I tried my luck with one of our production hosts, and

Re: Fujitsu Lifebook E751 (iGPU: HM65): distorted console with UEFI boot

2018-11-28 Thread Toomas Soome
Note about hw.vga.textmode: this tunable has no meaning for UEFI - first of all, there is no API to change to VGA text mode in UEFI, secondly, there may or may not be VGA (firmware) at all. We only do land in kernel with linear framebuffer mode active and all we have is information about that

Re: UEFI GOP: screen goes blank during boot after loader is finished

2018-11-17 Thread Toomas Soome
> On 17 Nov 2018, at 18:29, Subbsd wrote: > > On Fri, Nov 16, 2018 at 8:03 AM Warner Losh > wrote: >> >> >> >> On Thu, Nov 15, 2018 at 12:10 PM Rebecca Cran wrote: >>> >>> On Wednesday, 14 November 2018 19:56:56 MST Warner Losh wrote: >>> What is the ConOut

Re: UEFI: How to go about updating the ESP with loader.efi during installworld

2018-11-04 Thread Toomas Soome
> On 4 Nov 2018, at 23:25, Allan Jude wrote: > > On 2018-11-04 16:20, Rebecca Cran wrote: >> I'm currently working on creating and updating the ESP (EFI System >> Partition) >> for UEFI booting during installation and installworld. >> >> During installation, with my changes it gets mounted

Re: installer loader hangs going from 20181026 to 20181101 snapshot with Supermicro virtual IPMI disks

2018-11-02 Thread Toomas Soome
Darn, I will get to it. Thanks for reporting it, Toomas Sent from my iPhone > On 2 Nov 2018, at 07:43, Yuri Pankov wrote: > > Hi, > > Trying to boot latest -current snapshot (20181101) on Supermicro H8DG6 > using the IPMI virtual CD hangs after displaying the disks information, > however

Re: UEFI boot hangs after loader

2018-10-24 Thread Toomas Soome
gt; > > > > On 23 October 2018 at 21:33, Harry Newton > <mailto:h...@yewbarrow.net>> wrote: > > > > > Right ... I've the binaries in /boot, freshly made. This might be a silly > > > question ... do I not need to copy them (or dd

Re: UEFI boot hangs after loader

2018-10-24 Thread Toomas Soome
/boot, freshly made. This might be a silly >>> question ... do I not need to copy them (or dd the boot1.efifat image) to >>> the EFI partition ? >>> >>> /H >>> >>> On 23 October 2018 at 21:30, Toomas Soome wrote: >>> >>

Re: UEFI boot hangs after loader

2018-10-23 Thread Toomas Soome
t parts onto the > UEFI partition ? If so, how ? > > > On 23 October 2018 at 21:17, Toomas Soome <mailto:tso...@me.com>> wrote: > ok, in that case I’d suggest to test out if forth based one is still working > - at least you can get the bootable system. And then there is a

Re: UEFI boot hangs after loader

2018-10-23 Thread Toomas Soome
ton wrote: > > So it's got FORTH in it, but my loader is lua based, and also doesn't > appear to read loader.rc. > > /H > > On 23 October 2018 at 21:03, Toomas Soome wrote: > >> hm. in that case, whats the content of /boot/loader.rc ? >> >> rgds, >>

Re: UEFI boot hangs after loader

2018-10-23 Thread Toomas Soome
though not as I said just before the kernel is loaded but in point of fact > before the menu. > > I've also rebuilt the kernel and still can't use efibootmgr which is puzzling > me. > > /H > > > On 23 October 2018 at 20:56, Toomas Soome <mailto:tso...@me.com>&

Re: UEFI boot hangs after loader

2018-10-23 Thread Toomas Soome
Do you get boot menu? if so, press esc to get to ok prompt, then type start - if its bootfort based loader, it will load the kernel and modules. lsmod will then list the loaded files. If the loader prompt is still usable, then next command would be: boot rgds, toomas > On 23 Oct 2018, at

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

2018-10-23 Thread Toomas Soome
> 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?i

Re: head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated

2018-10-22 Thread Toomas Soome
> On 22 Oct 2018, at 13:58, Mark Millard wrote: > > On 2018-Oct-22, at 2:27 AM, Toomas Soome http://me.com/>> > wrote: >> >>> On 22 Oct 2018, at 06:30, Warner Losh wrote: >>> >>> On Sun, Oct 21, 2018 at 9:28 PM Warner Losh wrote: >>

Re: head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated

2018-10-22 Thread Toomas Soome
> On 22 Oct 2018, at 06:30, Warner Losh wrote: > > On Sun, Oct 21, 2018 at 9:28 PM Warner Losh > wrote: > >> >> >> On Sun, Oct 21, 2018 at 8:57 PM Mark Millard via freebsd-stable < >> freebsd-sta...@freebsd.org> wrote: >> >>> [I built based on WITHOUT_ZFS= for

Re: UEFI Loader problems in CURRENT

2018-09-30 Thread Toomas Soome
If the hung/crash is after printout of bootorder, and the fix (at least in some cases) is about setting the boot device (with linux tools, but I’d assume the efi bootmanager setup would do the same), it means, we do get bad value from efi boot manager variables, and if the fbsd installer and/or

Re: FreeBSD EFI projects

2018-09-19 Thread Toomas Soome
I still have it all in the queue, just the paid work is taking its toll and then FreeBSD and illumos :) Next week I am on vacation trip but then I’ll be back and kicking. Rgds, Toomas Sent from my iPhone > On 20 Sep 2018, at 02:37, Warner Losh wrote: > >> On Wed, Sep 19, 2018 at 4:33

Re: FreeBSD EFI projects

2018-09-19 Thread Toomas Soome
> On 19 Sep 2018, at 18:31, Rodney W. Grimes > wrote: > >> On Wed, Sep 19, 2018 at 6:06 PM, Rodney W. Grimes >> wrote: On Wed, Sep 19, 2018 at 5:34 PM, Rodney W. Grimes wrote: >> On 9/18/18 4:11 AM, Greg V wrote: >> >>> >>> I can confirm that the kernel already

Re: r336921 broke booting on MBP 2017, EFIRT related

2018-08-29 Thread Toomas Soome
> On 29 Aug 2018, at 14:53, Yuri Pankov wrote: > > Yuri Pankov wrote: >> Konstantin Belousov wrote: >>> On Wed, Aug 29, 2018 at 12:37:52PM +0300, Yuri Pankov wrote: Hi, I've noticed that all recent snapshots (ALPHA3, ALPHA2, ALPHA1, 20180802) fail to boot on MBP 2017:

Re: r336921 broke booting on MBP 2017, EFIRT related

2018-08-29 Thread Toomas Soome
> On 29 Aug 2018, at 15:05, Toomas Soome wrote: > > > >> On 29 Aug 2018, at 14:53, Yuri Pankov > <mailto:yur...@yuripv.net>> wrote: >> >> Yuri Pankov wrote: >>> Konstantin Belousov wrote: >>>> On Wed, Aug 29, 2018 at 12:37:52P

4kn and biosdisk.c

2018-08-16 Thread Toomas Soome
hi! if you have 4kn disks and BIOS capable of 4k IO with INT13, could you please test https://reviews.freebsd.org/D11174 and give some feedback:) The patch itself has been in use for some time in illumos. PS: as noted in test plan, this only can be tested

Re: boot errors since upgrading to 12-current

2018-08-15 Thread Toomas Soome
> On 15 Aug 2018, at 16:52, tech-lists wrote: > > On 15/08/2018 13:20, tech-lists wrote: >> On 15/08/2018 12:49, Kyle Evans wrote: >>> On Wed, Aug 15, 2018 at 6:22 AM, tech-lists wrote: >>>> Hello Toomas, >>>> >>>> On 15/08/2018 07

Re: boot errors since upgrading to 12-current

2018-08-15 Thread Toomas Soome
> On 15 Aug 2018, at 14:22, tech-lists wrote: > > Hello Toomas, > > On 15/08/2018 07:31, Toomas Soome wrote: >> Well that does explain the problem, if you look on the sizes reported… so >> your BIOS is reporting wrong sizes, is unable to access whole 4TB s

  1   2   >