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

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

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

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

; 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

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

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

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

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

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

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

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: r 310850: buildworld failure due to: nandfs.c:1049:15: error: too many arguments to function call,

om >> macro 'NULL' >> #define NULL((void *)0) >> ^~~ >> 1 error generated. >> *** [nandfs.o] Error code 1 > > This looks like the culprit to me: > > On 30 Dec 2016, at 20:06, Toomas Soome wrote: >> Author: tsoome &

Re: r 310850: buildworld failure due to: nandfs.c:1049:15: error: too many arguments to function call,

> On 30. dets 2016, at 21:40, Toomas Soome wrote: > > >> On 30. dets 2016, at 21:35, Dimitry Andric wrote: >> >> On 30 Dec 2016, at 20:23, O. Hartmann wrote: >>> >>> Recent update of CURRENT to 2310850 fails with buildworld error: &g

Re: gptzfsboot grew a lot after skein support was added; need knob to control bloat

> On 27. jaan 2017, at 1:40, Ngie Cooper (yaneurabeya) > wrote: > > Hi, > I tried upgrading one of my workstations and unfortunately the > freebsd-boot partition is too small (I follow manpage directions, exactly, > and those seem to be too small as of 10.3-RELEASE timeframe), and I don

Re: gptzfsboot grew a lot after skein support was added; need knob to control bloat

> On 27. jaan 2017, at 19:30, Allan Jude wrote: > > On 2017-01-27 12:05, Warner Losh wrote: >> On Fri, Jan 27, 2017 at 12:34 AM, Toomas Soome > <mailto:tso...@me.com>> wrote: >>> >>>> On 27. jaan 2017, at 1:40, Ngie Cooper (yaneurabeya) >>

Re: gptzfsboot grew a lot after skein support was added; need knob to control bloat

> On 27. jaan 2017, at 22:16, Ngie Cooper wrote: > > >> On Jan 27, 2017, at 09:05, Warner Losh wrote: > > ... > >> I'm curious why you can't find the space for a bigger partition? >> Almost all drives these days are partitioned with a little wasted >> space, and that wasted space should be m

Re: gptzfsboot grew a lot after skein support was added; need knob to control bloat

> On 28. jaan 2017, at 18:56, Warner Losh wrote: > >> >> >> at $JOB we are just testing a script that expands the root zfs partition on >> in-field appliances by shaving a bit off swap and cannibalising a small data >> partition we don't really use. I see we only left 64K for the boot part. >>

review: loader: disk/part api needs to use uint64_t offsets

Hi! I would like to have some eyes on https://reviews.freebsd.org/D8710 :) thanks, toomas ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send

review: Implement disk_ioctl() to support DIOCGSECTORSIZE and DIOCGMEDIASIZE.

Hi! Looking for more eyes on: https://reviews.freebsd.org/D8594 thanks, toomas ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to

Re: gptzfsboot trouble

> On 7. veebr 2017, at 18:08, Thomas Sparrevohn > wrote: > > Hi all > > > > Last week I decided to upgrade my FreeBSD installation - it's been a while > (September 16 was last time). Unfortunately CURRENT does not boot and cash > in a weird way. Both 11-RELEASE and 12 CURRENT boot loader se

Re: gptzfsboot trouble

> On 8. veebr 2017, at 14:26, Ronald Klop wrote: > > On Tue, 07 Feb 2017 17:08:44 +0100, Thomas Sparrevohn > wrote: > >> Hi all >> >> >> Last week I decided to upgrade my FreeBSD installation - it's been a while >> (September 16 was last time). Unfortunately CURRENT does not boot and cash >

Re: gptzfsboot trouble

> On 8. veebr 2017, at 14:51, Ronald Klop wrote: > > On Wed, 08 Feb 2017 13:40:25 +0100, Thomas Sparrevohn > wrote: > >> >> The bug in the bugzilla could be related - what is weird is I have been >> running this setup for years without issues - which I guess just shows how >> good ye'ol Fr

Re: Crochet build for Pi3 fails to boot on r313441 (and later), works on r313109

> On 9. veebr 2017, at 16:36, Karl Denninger wrote: > > > On 2/8/2017 16:18, Karl Denninger wrote: >> r313441 blows up on the Pi3 in /boot/loader.efi with: >> >> FreeBSD/arm64 EFI loader, Revision 1.1 >> (Tue Feb 7 15:15:52 CST 2017 free...@newfs.denninger.net) >> Failed to start image provid

Re: Crochet build for Pi3 fails to boot on r313441 (and later), works on r313109

> On 9. veebr 2017, at 17:05, Karl Denninger wrote: > > > On 2/9/2017 08:58, Toomas Soome wrote: >>> On 9. veebr 2017, at 16:36, Karl Denninger >>> <mailto:k...@denninger.net> wrote: >>> >>> >>> On 2/8/2017 16:18, Karl Dennin

Re: Crochet build for Pi3 fails to boot on r313441 (and later), works on r313109

> On 9. veebr 2017, at 23:39, Oleksandr Tymoshenko wrote: > > Toomas Soome (tso...@me.com) wrote: >> >>> On 9. veebr 2017, at 17:05, Karl Denninger wrote: >>> >>> >>> On 2/9/2017 08:58, Toomas Soome wrote: >>>>> On 9. veebr

Re: Crochet build for Pi3 fails to boot on r313441 (and later), works on r313109

> On 10. veebr 2017, at 0:10, Oleksandr Tymoshenko wrote: > > Toomas Soome (tso...@me.com) wrote: >> >>> On 9. veebr 2017, at 23:39, Oleksandr Tymoshenko wrote: >>> >>> Toomas Soome (tso...@me.com) wrote: >>>> >>>>> On 9.

Re: Crochet build for Pi3 fails to boot on r313441 (and later), works on r313109

>> >> From reading U-Boot sources (lib/efi_loader/efi_disk.c) it looks like >> names are in the form of typeN:M, where type is interface type, >> N is disk id and M is partition id. So 3 disks in my setup >> may be mmc0, mmc0:1, mmc0:2. >> >> -- >> gonzo > > Okay, so in case of arm or MEDIA_F

Re: two recent snapshot installer problems

> On 7. märts 2017, at 21:05, Michael W. Lucas > wrote: > > Hi, > > I want to open a bug report on this, but have no idea how to gather > useful info. > > Attempting to install > FreeBSD-12.0-CURRENT-amd64-20170301-r314495-memstick.img onto an > eight-drive iX system. This machine previously

Re: input/output error @boot

> On 9. märts 2017, at 8:00, Dexuan Cui wrote: > > Hi Roberto, > Thanks for sending me your memmap and this is a temporary workaround > patch for you: > https://github.com/dcui/freebsd/commit/0edd1db55fbbb56352d6024250e4ae7dd8ad31e3.patch > > I put the memmap info here for people who're intere

Re: input/output error @boot

> On 9. märts 2017, at 15:03, Dexuan Cui wrote: > >> From: owner-freebsd-curr...@freebsd.org [mailto:owner-freebsd- >> curr...@freebsd.org] On Behalf Of Toomas Soome >> >> IMO there are multiple issues around this problem and workaround. >> >> First

NFSv2 boot & OLD_NFSV2

Hi! The current boot code is building NFSv3, with preprocessor conditional OLD_NFSV2. Should NFSv2 code still be kept around or can we burn it? rgds, toomas ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd

Re: NFSv2 boot & OLD_NFSV2

> On 20. märts 2017, at 23:53, Rick Macklem wrote: > > Baptiste Daroussin wrote: >> On Mon, Mar 20, 2017 at 08:22:12PM +0200, Toomas Soome wrote: >>> Hi! >>> >>> The current boot code is building NFSv3, with preprocessor conditional >>> OLD_N

Re: Are textmode consoles/terminals still supported?

> On 20. märts 2017, at 23:58, Chris H wrote: > > I'm attempting to get a video card that DTRT on FreeBSD. > I started with the graphics provided by an AMD A6-7470K, > only to discover it's not yet supported. So I forked out > for a recent nvidia card, and build/installed a new > world/kernel. >

Re: NFSv2 boot & OLD_NFSV2

> On 21. märts 2017, at 10:13, Baptiste Daroussin wrote: > > On Tue, Mar 21, 2017 at 09:58:21AM +0200, Daniel Braniss wrote: >> >>> On 20 Mar 2017, at 23:55, Toomas Soome wrote: >>> >>>> >>>> On 20. märts 2017, at 23:53, Rick Macklem

Re: NFSv2 boot & OLD_NFSV2

> On 21. märts 2017, at 10:50, Daniel Braniss wrote: > > >> On 21 Mar 2017, at 10:13, Baptiste Daroussin > <mailto:b...@freebsd.org>> wrote: >> >> On Tue, Mar 21, 2017 at 09:58:21AM +0200, Daniel Braniss wrote: >>> >>>> On 20 Mar 20

Re: NFSv2 boot & OLD_NFSV2

d got some stupid cold meanwhile:D rgds, toomas > ________ > From: Toomas Soome mailto:tso...@me.com>> > Sent: Tuesday, March 21, 2017 5:04:59 AM > To: Daniel Braniss > Cc: Baptiste Daroussin; Rick Macklem; FreeBSD Current > Subject: Re: NFSv2 bo

D10203: loader: zfs reader should check all labels

… thanks, toomas > Begin forwarded message: > > From: "tsoome (Toomas Soome)" > Subject: [Differential] D10203: loader: zfs reader should check all labels > Date: 30. märts 2017 18:39.44 GMT+3 > To: tso...@me.com > Reply-To: d10203+574+d76c8a36ba3c3...@reviews.freeb

Re: problem with ls, not show a correct list

> On 7. apr 2017, at 11:29, Andrey Chernov wrote: > >> Hi Allan, the ls show all files without case match >> >> ls [a-z]* >> >> show all files beginning with a and A like this [aA-zZ]* > > No, last "Z" is not included. > This is to define set of chars: { a, A-z, Z } ? A-z of course does n

Re: r316677:EFI boot failure: Can't load kernel

> On 10. apr 2017, at 15:58, Hartmann, O. wrote: > > After today's update to r316677, some UEFI boxes (Fujitsu Celsius M740 > XEON) reject to boot properly. They die immediately after > loading /boot/loader.efi and jump into loader prompt: > > [...] > \ > can't load 'kernel' > > > I had to in

Re: r316677:EFI boot failure: Can't load kernel

> On 10. apr 2017, at 21:04, O. Hartmann wrote: > > Am Mon, 10 Apr 2017 16:14:21 +0300 > Toomas Soome schrieb: > >>> On 10. apr 2017, at 15:58, Hartmann, O. wrote: >>> >>> After today's update to r316677, some UEFI boxes (Fujitsu Celsius M

Re: r316677:EFI boot failure: Can't load kernel

> On 11. apr 2017, at 17:42, Masachika ISHIZUKA wrote: > >> replaced /boot/loader with /boot/loader.old (which was from end of >> March) >> >> copied /boot/loader.efi from the r315864 snapshot USB image >> into /boot/loader.efi of the broken systems. >> >> Aprt from the fact that I don't know

Re: r316677:EFI boot failure: Can't load kernel

> On 12. apr 2017, at 22:48, Chris H wrote: > > On Tue, 11 Apr 2017 23:42:52 +0900 (JST) Masachika ISHIZUKA > mailto:i...@amail.plala.or.jp>> wrote > >>> replaced /boot/loader with /boot/loader.old (which was from end of >>> March) >>> >>> copied /boot/loader.efi from the r315864 snapshot USB

Re: r316677:EFI boot failure: Can't load kernel

> On 12. apr 2017, at 22:48, Chris H wrote: > > On Tue, 11 Apr 2017 23:42:52 +0900 (JST) Masachika ISHIZUKA > mailto:i...@amail.plala.or.jp>> wrote > >>> replaced /boot/loader with /boot/loader.old (which was from end of >>> March) >>> >>> copied /boot/loader.efi from the r315864 snapshot USB

https://reviews.freebsd.org/D10232

Hi! The network code rework still needs good people to test out the work, especially the non-x86 platforms:) the url is still: https://reviews.freebsd.org/D10232 Once it checks out, we can go for next phase and get some boost for network loading. thanks, toomas __

Re: old snapshot install images?

> On 3. mai 2017, at 19:52, Ngie Cooper wrote: > > >> On May 3, 2017, at 09:41, Michael W. Lucas wrote: >> >>> On Wed, May 03, 2017 at 09:37:04AM -0700, Ngie Cooper (yaneurabeya) wrote: >>> Ok. I was curious because there has been a period of time when 512b/sector >>> disks have been broken

Re: old snapshot install images?

> On 3. mai 2017, at 21:06, Michael W. Lucas wrote: > > On Wed, May 03, 2017 at 08:03:21PM +0300, Toomas Soome wrote: >> There was many issues fixed step by step and some fixes for particular >> problem did reveal next one (at least in some systems), and indeed, it can &

  1   2   3   >