Re: Panic in gptzfsboot?

> 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 > oth

Re: btxld not found

> 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

> 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 loader_4th

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

> 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

> 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

> 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

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 > star

Testing needed:)

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 https:/

Re: CURRENT October images do not create a bootable install

> 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

> 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

> 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

> 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

> 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

> 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 layo

Re: SVN r354253 breaks buildworld

> 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/o

Re: SVN r354253 breaks buildworld

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 > (/usr/src/sys/cddl/cont

Re: SVN r354253 breaks buildworld

> 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

> 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

> 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 ?

> 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 to

Re: Lockdown adaX numbers to allow booting ?

> 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 ?

> 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

> 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 - F

Re: r352368 can't boot

> 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

> 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

> 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 `shutd

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

> 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 (after

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

> 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 Denninger

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

is). 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: >>> >>>>> O

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

> 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

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 mo

Re: Can't boot current under bhyve on current

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 >> see

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

> 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

> 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

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

> 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 > r350115)

Re: UEFI boot broken in 13?

> 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 b

Re: Triveal bootloader patch for FreeBSD 11.2 regression

> 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 durin

Re: Got the same error from gptzfsboot this morning

> 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 rece

Re: Question about 'gptzfsboot'

> 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 hard

Re: Question about 'gptzfsboot'

> 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 when up

Re: Question about 'gptzfsboot'

> 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: N

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

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 point

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

> 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 >&

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

> 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)

> 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 >> variables

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

> 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)

> 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 /boot/lo

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

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 cont

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

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

> 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

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

> 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 >

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

> 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 does

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

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 e

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

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 mo

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

> 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 e

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

> 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

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 booti

Re: UEFI boot hangs after loader

welcomed. > > > > /H > > > > > > 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 > > > q

Re: UEFI boot hangs after loader

; Right ... I've the binaries in /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 Soom

Re: UEFI boot hangs after loader

rts 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

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 ? >> >> rgd

Re: UEFI boot hangs after loader

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...@m

Re: UEFI boot hangs after loader

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 20:45

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?i

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

> 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

> 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 other

Re: UEFI Loader problems in CURRENT

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

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 P

Re: FreeBSD EFI projects

> 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

> 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

> 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

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 b

Re: boot errors since upgrading to 12-current

> 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

> 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 space an

Re: boot errors since upgrading to 12-current

> On 15 Aug 2018, at 06:06, tech-lists wrote: > > On 14/08/2018 21:16, Toomas Soome wrote: >>> On 14 Aug 2018, at 22:37, tech-lists wrote: >>> Hello, >>> context: amd64, FreeBSD 12.0-ALPHA1 #0 r337682, ZFS. The system is >>> *not* root-on-zfs.

Re: boot errors since upgrading to 12-current

> On 14 Aug 2018, at 22:37, tech-lists wrote: > > Hello, > > context: amd64, FreeBSD 12.0-ALPHA1 #0 r337682, ZFS. The system is *not* > root-on-zfs. It boots to an SSD. The three disks indicated below are spinning > rust. > > NAMESTATE READ WRITE CKSUM > storage

Re: "Can't load kernel" after r337232 -> r337285 update (amd64)

> On 4 Aug 2018, at 14:19, David Wolfskill wrote: > > Yesterday, the daily build/smoike-test of head yielded: > > FreeBSD g1-215.catwhisker.org 12.0-CURRENT FreeBSD 12.0-CURRENT #68 > r337232M/337232:1200076: Fri Aug 3 03:52:52 PDT 2018 > r...@g1-215.catwhisker.org:/common/S4/obj/usr/

Re: Unable to UEFI boot 11.2 via pxeboot

Update commited:) rgds, toomas > >> On 2. Aug 2018, at 14:45, Toomas Soome wrote: >> >> Could you check the current with >> https://svnweb.freebsd.org/changeset/base/337131 >> >> thanks, >> toomas >> >>> On 2 Aug 2018, at 15:32,

Re: Unable to UEFI boot 11.2 via pxeboot

> On 2 Aug 2018, at 16:42, Kyle Evans wrote: > > On Thu, Aug 2, 2018 at 7:45 AM, Toomas Soome wrote: >>> On 2 Aug 2018, at 15:32, Toomas Soome wrote: >>> >>> >>> >>>> On 2 Aug 2018, at 15:08, Timo Völker >>> <mailto:t

Re: Unable to UEFI boot 11.2 via pxeboot

> On 2 Aug 2018, at 15:08, Timo Völker wrote: > > It seems this issue is related to current as well. I did a quick test and got > this output, while I tried to (pxe)boot FreeBSD current (without a USB stick > plugged in) > > https://ibb.co/no8Fve > > Best regards > > Timo the hint is abou

Re: Unable to UEFI boot 11.2 via pxeboot

Could you check the current with https://svnweb.freebsd.org/changeset/base/337131 <https://svnweb.freebsd.org/changeset/base/337131> thanks, toomas > On 2 Aug 2018, at 15:32, Toomas Soome wrote: > > > >> On 2 Aug 2018, at 15:08, Timo Völker > <mailto:timo.

Re: [UEFI] Boot issues on some UEFI implementations

> On 27 Jul 2018, at 13:02, O. Hartmann wrote: > > On Fri, 27 Jul 2018 08:54:48 +0300 > Toomas Soome wrote: > >>> On 27 Jul 2018, at 08:46, O. Hartmann wrote: >>> >>> On Thu, 26 Jul 2018 19:23:43 +0300 >>> Toomas Soome wrote: >>&

Re: [UEFI] Boot issues on some UEFI implementations

> On 27 Jul 2018, at 08:46, O. Hartmann wrote: > > On Thu, 26 Jul 2018 19:23:43 +0300 > Toomas Soome wrote: > > (reply inline/at the end) > > >>> On 26 Jul 2018, at 16:58, O. Hartmann wrote: >>> >>> On Wed, 25 Jul 2018 07:30:32 -0

Re: [UEFI] Boot issues on some UEFI implementations

> On 26 Jul 2018, at 16:58, O. Hartmann wrote: > > On Wed, 25 Jul 2018 07:30:32 -0700 (PDT) > "Rodney W. Grimes" <mailto:freebsd-...@pdx.rh.cn85.dnsmgr.net>> wrote: > >>>> On 25 Jul 2018, at 12:10, O. Hartmann wrote: >>>> >&g

Re: [UEFI] Boot issues on some UEFI implementations

> On 25 Jul 2018, at 12:10, O. Hartmann wrote: > > On Wed, 25 Jul 2018 11:46:07 +0300 > Toomas Soome wrote: > >>> On 25 Jul 2018, at 10:59, O. Hartmann wrote: >>> >>> On Tue, 24 Jul 2018 08:53:36 +0300 >>> Toomas Soome wrote: >>

Re: [UEFI] Boot issues on some UEFI implementations

> On 25 Jul 2018, at 10:59, O. Hartmann wrote: > > On Tue, 24 Jul 2018 08:53:36 +0300 > Toomas Soome wrote: > > > Hello Toomas Soome, > > I CC Allan Jude since I discovered something weird today regarding the UEFI > boot capabilities of USB flash devices and

Re: [UEFI] Boot issues on some UEFI implementations

> On 24 Jul 2018, at 09:20, Allan Jude wrote: > > On 2018-07-13 07:00, O. Hartmann wrote: >> The problem is some kind of weird. I face UEFI boot problems on GPT drives >> where the first partition begins at block 40 of the hdd/ssd. >> >> I have two host in private use based on an >> outdated

Re: [UEFI] Boot issues on some UEFI implementations

> On 24 Jul 2018, at 08:16, O. Hartmann wrote: > > On Mon, 23 Jul 2018 10:56:04 +0300 > Toomas Soome wrote: > >>> On 23 Jul 2018, at 10:27, O. Hartmann wrote: >>> >>> On Fri, 13 Jul 2018 18:44:23 +0300 >>> Toomas Soome mailto:tso...@me.

Re: [UEFI] Boot issues on some UEFI implementations

> On 23 Jul 2018, at 10:27, O. Hartmann wrote: > > On Fri, 13 Jul 2018 18:44:23 +0300 > Toomas Soome mailto:tso...@me.com>> wrote: > >>> On 13 Jul 2018, at 17:44, O. Hartmann >> <mailto:o.hartm...@walstatt.org>> wrote: >>> >>>

Re: [UEFI] Boot issues on some UEFI implementations

> On 13 Jul 2018, at 17:44, O. Hartmann wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Am Fri, 13 Jul 2018 14:26:51 +0300 > Toomas Soome mailto:tso...@me.com>> schrieb: > >>> On 13 Jul 2018, at 14:00, O. Hartmann wrote: >>>

Re: [UEFI] Boot issues on some UEFI implementations

> On 13 Jul 2018, at 14:00, O. Hartmann wrote: > > The problem is some kind of weird. I face UEFI boot problems on GPT drives > where the first partition begins at block 40 of the hdd/ssd. > > I have two host in private use based on an > outdated ASRock Z77-Pro4-M and Z77-Pro4 mainboard (IvyB

Re: Unable to UEFI boot 11.2 ISO (latest 12.0 as well)

d vänlig hälsning/Best Regards > Linus Sundqvist > System Engineer, Loopia AB > > On 05/07/18 09:17, Toomas Soome wrote: >> Could you check, show currdev from OK prompt before setting it. >> >> Somehow the boot device path is shown but we fail to recognize it (a

Re: Unable to UEFI boot 11.2 ISO (latest 12.0 as well)

> Linus Sundqvist > System Engineer, Loopia AB > >> On 04/07/18 16:50, Toomas Soome wrote: >> set currdev=cd1: >> include /boot/loader.rc >> >> This should give menu/boot. >> >> Rgds, >> Toomas >> >> Sent from my iPhone >> >

Re: Unable to UEFI boot 11.2 ISO (latest 12.0 as well)

here is ls cd1: > https://imgur.com/FPsixOw > > Med vänlig hälsning/Best Regards > Linus Sundqvist > System Engineer, Loopia AB > >> On 04/07/18 15:08, Toomas Soome wrote: >> Can you post lsdev -v output? >> >> Also, could you try ls command? Like, ls cd0:

Re: Unable to UEFI boot 11.2 ISO (latest 12.0 as well)

Can you post lsdev -v output? Also, could you try ls command? Like, ls cd0: Rgds, Toomas Sent from my iPhone > On 4 Jul 2018, at 12:28, Linus Sundqvist wrote: > > Hi, > > I'm unable to boot up the amd64 11.2 disk1 ISO as well as the latest amd64 > 12.0 disk1 ISO (20180628) using UEFI on

Re: ZFS: I/O error - blocks larger than 16777216 are not supported

> On 29 Jun 2018, at 05:47, KIRIYAMA Kazuhiko wrote: > > At Tue, 26 Jun 2018 09:48:10 +0300, > Toomas Soome wrote: >> >> >> >>> On 26 Jun 2018, at 05:08, KIRIYAMA Kazuhiko wrote: >>> >>> At Thu, 21 Jun 2018 10:48:28 +0300, >>&

Re: ZFS: I/O error - blocks larger than 16777216 are not supported

> On 26 Jun 2018, at 05:08, KIRIYAMA Kazuhiko wrote: > > At Thu, 21 Jun 2018 10:48:28 +0300, > Toomas Soome wrote: >> >> >> >>> On 21 Jun 2018, at 09:00, KIRIYAMA Kazuhiko wrote: >>> >>> At Wed, 20 Jun 2018 23:34:48 -0400, >&

Re: ZFS: I/O error - blocks larger than 16777216 are not supported

> On 21 Jun 2018, at 09:00, KIRIYAMA Kazuhiko wrote: > > At Wed, 20 Jun 2018 23:34:48 -0400, > Allan Jude wrote: >> >> On 2018-06-20 21:36, KIRIYAMA Kazuhiko wrote: >>> Hi all, >>> >>> I've been reported ZFS boot disable problem [1], and found >>> that this issue occers form RAID configuratio

Re: ZFS: I/O error - blocks larger than 16777216 are not supported

> On 21 Jun 2018, at 06:34, Allan Jude wrote: > > On 2018-06-20 21:36, KIRIYAMA Kazuhiko wrote: >> Hi all, >> >> I've been reported ZFS boot disable problem [1], and found >> that this issue occers form RAID configuration [2]. So I >> rebuit with RAID5 and re-installed 12.0-CURRENT >> (r33398

<    1   2   3   >