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

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

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

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

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?

> 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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

<    1   2   3