Re: old snapshot install images?

> On 3. mai 2017, at 21:23, Michael W. Lucas wrote: > > On Wed, May 03, 2017 at 09:11:05PM +0300, Toomas Soome wrote: >> >>> On 3. mai 2017, at 21:06, Michael W. Lucas >>> wrote: >>> >>> On Wed, May 03, 2017 at 08:03:21PM +0300, Toomas So

Re: old snapshot install images?

> On 3. mai 2017, at 21:53, Toomas Soome wrote: > > >> On 3. mai 2017, at 21:23, Michael W. Lucas > <mailto:mwlu...@michaelwlucas.com>> wrote: >> >> On Wed, May 03, 2017 at 09:11:05PM +0300, Toomas Soome wrote: >>> >>>>

Re: old snapshot install images?

just for an update: apparently this was buggy BIOS and the BIOS update did fix it. The curious fact was that the gptzfsboot INT13 calls were failing, while pmbr INT13 calls were doing OK also the usb stick boot had no apparent problems. rgds, toomas > On 3. mai 2017, at 21:53, Toomas So

Re: bootcode capable of booting both UFS and ZFS?

> On 5. mai 2017, at 22:07, Julian Elischer wrote: > > Subject says it all really, is this an option at this time? > > we'd like to try boot the main zfs root partition and then fall back to a > small UFS based recovery partition.. is that possible? > > I know we could use grub but I'd prefer

loader: network code update

hi! After pushing the network code update, there is review up: https://reviews.freebsd.org/D10631 For testing it, you would also like to increase the read sizes like: tftp.blksize=“8196” nfs.read_size=“4096" for nfs, the 4k is currently max value, we probably would like to rise the allowed ma

Re: bootcode capable of booting both UFS and ZFS? (Amazon/ec2)

> On 7. mai 2017, at 13:18, Julian Elischer wrote: > > On 7/5/17 1:45 pm, Warner Losh wrote: >> On Sat, May 6, 2017 at 10:03 PM, Julian Elischer wrote: >>> On 6/5/17 4:01 am, Toomas Soome wrote: >>>> >>>>> On 5. mai 2017, at 22:07, Juli

Re: zfsloader and compiler options/version?

> On 4. juuni 2017, at 15:28, Alexander Leidinger > wrote: > > Hi, > > I have a zfsloader which hangs directly after "Booting". First I attributed > it to maybe a bug in meta-mode/ccache + ino64 (easy assumption without > knowing if ino64 is involved in zfsloader), but after ccache -C, remov

Re: Boot CURRENT without efi

> On 5. juuni 2017, at 20:31, Andy Neustadter wrote: > > Hi: > > I have an older HP desktop that does not support USB boot or UEFI. Is > it possible to use this machine with 12-current using GPT? Any help > or pointers to info would be greatly appreciated. Thanks in advance. GPT does not re

about history:)

hi! there is an question about the tty line (canonical) mode — the internal implementation is using 2k buffer, but the related (public) constants are claiming buffer size about 255 chars. Why it is so - any hints about the background there? #define MAX_CANON 255 /* max bytes

Re: [SOLVED] [memstick install] auto-zfs error

> On 10. juuli 2017, at 21:24, Boris Samorodov wrote: > > 10.07.2017 21:05, Allan Jude пишет: >> On 2017-07-09 14:40, Boris Samorodov wrote: >>> 08.07.2017 18:56, Boris Samorodov пишет: Hi All, I tied to install a new FreeBSD-amd-12 system from official USB installation mems

Re: [SOLVED] [memstick install] auto-zfs error

> On 10. juuli 2017, at 22:53, Boris Samorodov wrote: > > 10.07.2017 22:21, Toomas Soome пишет: >> >>> On 10. juuli 2017, at 21:24, Boris Samorodov wrote: >>> >>> 10.07.2017 21:05, Allan Jude пишет: >>>> On 2017-07-09 14:40, Boris Sa

Re: Buildworld failure in sys/boot/efi/loader/main.c if WITHOUT_ZFS is defined

Got it fixed in: r323428 | tsoome | 2017-09-11 10:38:53 +0300 (E, 11 sept 2017) | 7 lines r323389 breaks the kernel build when WITHOUT_ZFS is defined in src.conf Need to add #ifdef EFI_ZFS_BOOT guard into efi/loader/main.c PR: 15 Reported by:Sylvain Garrigues sorry about i

Re: loader.efi module path vs kernel directory

Also, instead of manual load, you may want to use enable-module. Sent from my iPhone > On 20. Oct 2022, at 13:08, Emmanuel Vadot wrote: > > On Thu, 20 Oct 2022 13:03:26 +0300 > Andriy Gapon wrote: > >> >> I recently needed to recover a system by manually preloading a driver. >> To a bit of

Re: loader.efi module path vs kernel directory

present (defined in /boot/lua/cli.lua). I am also pretty sure, Kyle did add those when 13 was current, lua version was missing those, Forth version had them first:) rgds, toomas > On 20. Oct 2022, at 13:27, Andriy Gapon wrote: > > On 20/10/2022 13:20, Toomas Soome wrote: >> Also, in

Re: loader.efi module path vs kernel directory

Whoops, meant cli.lua(8), of course. > On 20. Oct 2022, at 13:58, Toomas Soome wrote: > > > the problem with ‘?’ command is that it only does list commands written in C, > it does not list scripted commands. cli_lua(8) should list lua specific ones. > And at least my sta

Re: Why doesn't the EFI boot loader want to display the graphical orb logo in its boot menu on an Asus Prime 7590-P motherboard?

> On 12. May 2023, at 00:11, Oleg Lelchuk wrote: > > Guys, there is something that I find puzzling. Why doesn't the EFI boot > loader want to display the graphical orb logo in its boot menu on an Asus > Prime 7590-P motherboard? Is there something quirky about this particular > motherboard

Re: Why doesn't the EFI boot loader want to display the graphical orb logo in its boot menu on an Asus Prime 7590-P motherboard?

/dtb;/boot/dtb/overlays" > nextboot_conf="/boot/nextboot.conf" > ram_blacklist_name="/boot/blacklist.txt" > > The efivar command shows me: > > efivar --device-path 8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut > efivar: fetching 8be4df61-93ca-11d2-aa0d-00e098032b8c-

Re: Why doesn't the EFI boot loader want to display the graphical orb logo in its boot menu on an Asus Prime 7590-P motherboard?

le (see show console on loader prompt). rgds, toomas > > On Thu, May 11, 2023 at 6:06 PM Toomas Soome <mailto:tso...@me.com>> wrote: >> >> >>> On 12. May 2023, at 00:57, Oleg Lelchuk >> <mailto:oleglelc...@gmail.com>> wrote: >>> >&

Re: Why doesn't the EFI boot loader want to display the graphical orb logo in its boot menu on an Asus Prime 7590-P motherboard?

re update from system vendor, that may fix the missing ConOut. rgds, toomas > > On Fri, May 12, 2023, 1:06 AM Emmanuel Vadot <mailto:m...@bidouilliste.com>> wrote: >> On Fri, 12 May 2023 00:20:47 +0300 >> Toomas Soome mailto:tso...@me.com>> wrote: >> &g

Re: Why doesn't the EFI boot loader want to display the graphical orb logo in its boot menu on an Asus Prime 7590-P motherboard?

bit of time. rgds, toomas > On Fri, May 12, 2023, 6:55 AM Toomas Soome <mailto:tso...@me.com>> wrote: >> >> >>> On 12. May 2023, at 13:41, Oleg Lelchuk >> <mailto:oleglelc...@gmail.com>> wrote: >>> >>> There is only one moni

Re: Why doesn't the EFI boot loader want to display the graphical orb logo in its boot menu on an Asus Prime 7590-P motherboard?

> On 15. May 2023, at 15:22, Oleg Lelchuk wrote: > > Adding screen.font="16×32" to loader.conf fixed that tiny issue mentioned in > the previous email message... I find it a bit surprising that I only had to > make one tiny change to the source code of stand to make the graphical logo > appe

Re: WITH_BEARSSL: -8112 bytes available

> On 1. Jun 2023, at 11:30, Gary Jennejohn wrote: > > On Wed, 31 May 2023 14:41:23 -0600 > Warner Losh mailto:i...@bsdimp.com>> wrote: > >> On Wed, May 31, 2023 at 1:30?PM Gary Jennejohn wrote: >> >>> On Wed, 31 May 2023 12:15:12 -0600 >>> Warner Losh wrote: >>> >>> [SNIP irrelevant text]

Re: CURRRENT snapshot won't boot due missing ZFS feature

Re: how to set vfs.zfs.arc.max in 15-current ?

> On 13. Oct 2023, at 09:35, void wrote: > > On Fri, Oct 13, 2023 at 08:12:47AM +0200, Juraj Lutter wrote: > >> Set also vfs.zfs.arc.min to some value higher than zero. > > aha! that worked!!! :D > > root@beer:/root# sysctl vfs.zfs.arc.min=1073741824 > vfs.zfs.arc.min: 0 -> 1073741824 > roo

Re: symlink to /boot/loader.efi

> On 22. Dec 2023, at 11:09, Mark Millard wrote: > > Tomoaki AOKI wrote on > Date: Thu, 21 Dec 2023 23:21:00 UTC : > >> On Thu, 21 Dec 2023 14:22:14 +0100 >> Dimitry Andric wrote: >> >>> Yeah, my procedure is the same as yours: I first copy >>> /boot/efi/efi/freebsd/loader.efi to /boot/ef

Re: symlink to /boot/loader.efi

> On 22. Dec 2023, at 11:54, Mark Millard wrote: > > On Dec 22, 2023, at 01:36, Toomas Soome wrote: >> >> >> >>> On 22. Dec 2023, at 11:09, Mark Millard wrote: >>> >>> Tomoaki AOKI wrote on >>> Date: Thu, 21 Dec 2

Re: symlink to /boot/loader.efi

> On 22. Dec 2023, at 16:07, Konstantin Belousov wrote: > > On Fri, Dec 22, 2023 at 11:36:24AM +0200, Toomas Soome wrote: >> >> >>> On 22. Dec 2023, at 11:09, Mark Millard wrote: >>> >>> Tomoaki AOKI wrote on >>> Date: Thu, 21 Dec 2

Re: Removing fdisk and bsdlabel (legacy partition tools)

> On 26. Jan 2024, at 18:02, Rodney W. Grimes > wrote: > > -- Start of PGP signed section. >> Am 2024-01-25 18:49, schrieb Rodney W. Grimes: On Thu, Jan 25, 2024, 9:11?AM Ed Maste wrote: > On Thu, 25 Jan 2024 at 11:00, Rodney W. Grimes > wrote: >> >>> These will

Re: Removing fdisk and bsdlabel (legacy partition tools)

> On 26. Jan 2024, at 18:21, Rodney W. Grimes > wrote: > >> >> >>> On 26. Jan 2024, at 18:02, Rodney W. Grimes >>> wrote: >>> >>> -- Start of PGP signed section. Am 2024-01-25 18:49, schrieb Rodney W. Grimes: >> On Thu, Jan 25, 2024, 9:11?AM Ed Maste wrote: >> >>> On Th

Re: setting the console to serial by defailt seems to not work

> On 31. Jul 2024, at 15:01, void wrote: > > On Tue, Jul 30, 2024 at 08:55:22PM +0200, Dag-Erling Smørgrav wrote: >> void writes: >>> The arm64 device is headless and i connect to it via serial. >>> I noticed the beastie menu come up with the option Video for >>> console. Cycled it to Serial,

Re: Cannot install FreeBSD 12.0 on HP Compaq DC5850

> On 29 Sep 2017, at 09:35, Tommi Pernila wrote: > > Hi Elena, > > Thanks for the details. > I'm also forwarding this to the Current mailing list as it has more devs > following. > Two things to test - check for bios update and UEFI boot (with decure boot disabled). Also make sure any non-

Re: Cannot install FreeBSD 12.0 on HP Compaq DC5850

> On 30 Sep 2017, at 19:29, Elena Mihailescu > wrote: > >> Two things to test - check for bios update and UEFI boot (with decure boot >> disabled). Also make sure any non-essential devices are disconnected - this >> hung smells like it is getting stuck on disk device probing, and one case I

Re: Booting native 4K SSD disk from FreeBSD ?

> On 4 Oct 2017, at 00:18, Hans Petter Selasky wrote: > > Hi, > > I accidentially ordered a Sata SSD disk which diskinfo reports a sector-size > 4K instead of 512 bytes. Trying to get it to boot under FreeBSD appeared > impossible. Then I started looking into the boot0,1,2 and loader and the

Re: system stuck on bios splash after reboot only

> On 1 Nov 2017, at 19:37, far...@t-online.de wrote: > >Firstly, I couldn't find an answer for this specific problem, so I >apologize when this is a common problem. > >Recently I installed FreeBSD again on a new laptop (Thinkpad T470 >20HES2SF00). On my desktop, the OS runs with

Re: Booting native 4K SSD disk from FreeBSD ?

With r325310, the UEFI boot with CURRENT should be ok with >512B sectors. The BIOS part is still work in the process. rgds, toomas > On 4 Oct 2017, at 19:32, Allan Jude wrote: > > On 2017-10-04 05:27, Thomas Mueller wrote: >> from Allan Jude: >> Anyone has any recommendations or experi

Re: what happened to src/sys/boot?

> On 2 Dec 2017, at 15:42, Daniel Braniss wrote: > > Hi, > it seems to have disappeared. > it got moved to src/stand rgds, toomas ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe

Re: GPTZFSBOOT in Current r326622 has problems

> On 9 Dec 2017, at 19:56, Warner Losh wrote: > > On Sat, Dec 9, 2017 at 7:12 AM, Thomas Laus wrote: > >> On 12/08/17 22:06, Warner Losh wrote: >>> >>> Clean build? >>> >> It was a clean build. I performed a rm -rf /usr/obj/* before starting >> the buildworld after cvs updating to r326720.

Re: ZFS i/o error in recent 12.0

> On 20 Mar 2018, at 09:50, Markus Wild wrote: > > Hi there, > >> I've been encountered suddenly death in ZFS full volume >> machine(r330434) about 10 days after installation[1]: >> >> ZFS: i/o error - all block copies unavailable >> ZFS: can't read MOS of pool zroot >> gptzfsboot: failed to

Re: Call for Testing: UEFI Changes

> On 22 Mar 2018, at 12:13, Jakob Alvermark wrote: > > Hi! > > > Just updated to r331345. > > Two problems: > > 1. boot/efi.4th is added to /usr/src/ObsoleteFiles.inc but still included in > loader.rc. Loader fails to load it and subsequently fails to load modules. > Reinstalling efi.4th

Re: Boot failure: panic: No heap setup

> On 29 Mar 2018, at 01:06, Stefan Esser wrote: > > Am 28.03.18 um 22:28 schrieb Warner Losh: >>> Hmmm, the code references point into the boot loader code - I had >>> expected that there is a problem in the kernel, not the boot loader. >>> [1] https://svnweb.freebsd.org/base/head/st

Re: Boot failure: panic: No heap setup

> On 30 Mar 2018, at 18:03, Stefan Esser wrote: > > Am 29.03.18 um 07:15 schrieb Toomas Soome: >> >> >>> On 29 Mar 2018, at 01:06, Stefan Esser wrote: >>> >>> Am 28.03.18 um 22:28 schrieb Warner Losh: >>>>> Hmmm, the code re

Re: Odd ZFS boot module issue on r332158

> On 10 Apr 2018, at 15:27, Andrew Gallatin wrote: > > On 04/09/18 23:33, Allan Jude wrote: >> On 2018-04-09 19:11, Andrew Gallatin wrote: >>> I updated my main amd64 workstation to r332158 from something much >>> earlier (mid Jan). >>> >>> Upon reboot, all seemed well. However, I later reali

Re: anyone running with ngroups increased from 16?

> On 16 Apr 2018, at 15:12, Rick Macklem wrote: > > Julian Elischer wrote: >> On 16/4/18 6:37 pm, Julian Elischer wrote: >>> Windows users seem to have an almost unlimited number of groups and >>> soem places seem to use them a LOT. >>> This gives Posix systems problems with deciding how to han

Re: Odd ZFS boot module issue on r332158

> On 1 May 2018, at 17:34, Andrew Gallatin wrote: > > On 04/10/18 16:51, Andriy Gapon wrote: >> On 10/04/2018 22:48, Andrew Gallatin wrote: >>> On 04/10/18 11:25, Andriy Gapon wrote: On 10/04/2018 15:27, Andrew Gallatin wrote: > Is there something like tools/diag/prtblknos for ZFS? >>>

Re: UEFI equivalent of boot.config? (Was: Re: [RFC] Deprecation and removal of the drm2 driver)

> On 23 May 2018, at 13:29, sth...@nethelp.no wrote: > > Hijacking a thread here, > >> Turns out, you can't install FreeBSD using a USB stick image because the >> BIOS only support MBR. No idea why MBR support was dropped for the USB >> images. >> >> In the end I had to find a CD burner, and

Re: Current @ r335314 not bootable with Geli and ZFS

> On 19 Jun 2018, at 21:51, Thomas Laus wrote: > > On 06/19/18 14:22, Thomas Laus wrote: >> On 06/19/18 12:09, Allan Jude wrote: >>> >>> We tested all of the changes with the setup in tools/boot/rootgen.sh, it >>> will be interesting to figure out what went wrong with your setup, and >>> add i

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

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

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

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

> 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

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

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

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

> 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: 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: 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: 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: 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: Panic in gptzfsboot?

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

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: r351900 broke UEFI boot on VMware VMs

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

Re: current does not boot on vmware fusion 11

> 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

about loader & console

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: what 3rd party boot mgr is required to boot multiple freebsd versions?

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

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

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 3

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

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

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

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 m

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

> 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: Geli encryption issue on r362779

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

Re: Geli encryption issue on r362779

> 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&revision=362431 >> >> The majority of the code is now shared with loader (li

Re: Geli encryption issue on r362779

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

Re: Geli encryption issue on r362779

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

Re: Boot failure on refreshed Dell Precision 7550

> 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: Boot failure on refreshed Dell Precision 7550

> 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: Geli encryption issue on r362779

> 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: OpenZFS support merged

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

Re: OpenZFS support merged

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

<    1   2   3   >