Re: i386/amd64 image generated trough mkimage stuck on primary bootsrap at boot

2022-07-17 Thread br0nko
On Wednesday, July 13th, 2022 at 6:39 PM, br0nko wrote: > I confirm that the image is bootable with your patch, thank you !!! As you > said already, it lack the resize capability, which make the image somehow > useless since it run out of space at first boot. I did try "resize_root=YES" > in

Re: i386/amd64 image generated trough mkimage stuck on primary bootsrap at boot

2022-07-13 Thread br0nko
--- Original Message --- On Sunday, July 10th, 2022 at 10:47 AM, RVP wrote: > Right. After ~10 hours of doing `build.sh release' I have a patch. However, > I'm not at all certain that this script is meant to be used on the x86 arch. > because: a) It only seems to be used by the evbarm

Re: i386/amd64 image generated trough mkimage stuck on primary bootsrap at boot

2022-07-11 Thread RVP
On Sun, 10 Jul 2022, Izumi Tsutsui wrote: IIRC libsa/sa/ufs.c requires large heapsize to read blocksize, from ffs, so sometimes it fails to load on blocksize=65536 fs. (but I'm nots sure 64KB blocksize is valied on FFS because newfs(8) man page just says 4KB-32KB for it) On Mon, 11 Jul 2022,

Re: i386/amd64 image generated trough mkimage stuck on primary bootsrap at boot

2022-07-10 Thread Michael van Elst
m...@eterna.com.au (matthew green) writes: >FWIW, i've been using 64K block *and frag size FFS for over >a decade without any problem, on a file system that almost >always has extremely large files on it. >so, this should be fixed in the manual i guess. The manual just lists the default values

re: i386/amd64 image generated trough mkimage stuck on primary bootsrap at boot

2022-07-10 Thread matthew green
> (but I'm nots sure 64KB blocksize is valied on FFS because > newfs(8) man page just says 4KB-32KB for it) FWIW, i've been using 64K block *and frag size FFS for over a decade without any problem, on a file system that almost always has extremely large files on it. so, this should be fixed in

Re: i386/amd64 image generated trough mkimage stuck on primary bootsrap at boot

2022-07-10 Thread Izumi Tsutsui
mlelstv@ wrote: > r...@sdf.org (RVP) writes: > > >@@ -255,7 +255,7 @@ > > echo ${bar} Populating ffs filesystem ${bar} > > ${MAKEFS} -rx ${endian} -N ${release}/etc -t ffs \ > > -O ${ffsoffset} \ > >--o d=4096,f=8192,b=65536 -b $((${extra}))m \ > >+-o

Re: i386/amd64 image generated trough mkimage stuck on primary bootsrap at boot

2022-07-10 Thread Michael van Elst
r...@sdf.org (RVP) writes: >@@ -255,7 +255,7 @@ > echo ${bar} Populating ffs filesystem ${bar} > ${MAKEFS} -rx ${endian} -N ${release}/etc -t ffs \ > -O ${ffsoffset} \ >- -o d=4096,f=8192,b=65536 -b $((${extra}))m \ >+ -o d=8192,f=2048,b=16384 -b

Re: i386/amd64 image generated trough mkimage stuck on primary bootsrap at boot

2022-07-10 Thread RVP
On Thu, 7 Jul 2022, br0nko wrote: I wanted to resurrect an old i386 alix box, and I did follow the guide to create a custom image trough mkimage (https://www.netbsd.org/docs/guide/en/chap-inst-media.html#chap-inst-media-creating-live-images). I did first try on amd64 so that I can first test on

Re: i386/amd64 image generated trough mkimage stuck on primary bootsrap at boot

2022-07-08 Thread Lloyd Parkes
On 8/07/22 21:01, RVP wrote: On Fri, 8 Jul 2022, br0nko wrote: 8 partitions: #    size    offset fstype [fsize bsize cpg/sgs] a:   2369473    63 4.2BSD  0 0 0  # (Cyl. 0*-   1156) c:   2312129    63 unused  0 0    # (Cyl. 0*-  

Re: i386/amd64 image generated trough mkimage stuck on primary bootsrap at boot

2022-07-08 Thread Lloyd Parkes
On 8/07/22 19:57, br0nko wrote: On Thursday, July 7th, 2022 at 11:25 PM, Mike Pumford wrote: On 07/07/2022 15:40, br0nko wrote: Hi, 0: NetBSD (sysid 169) start 63, size 1568384 (766 MB, Cyls 0/1/1-97/160/62), Active beg: cylinder 0, head 1, sector 1 end: cylinder 97, head 160, sector

Re: i386/amd64 image generated trough mkimage stuck on primary bootsrap at boot

2022-07-08 Thread RVP
On Fri, 8 Jul 2022, br0nko wrote: 8 partitions: #sizeoffset fstype [fsize bsize cpg/sgs] a: 236947363 4.2BSD 0 0 0 # (Cyl. 0*- 1156) c: 231212963 unused 0 0# (Cyl. 0*- 1128) d: 2369536 0

Re: i386/amd64 image generated trough mkimage stuck on primary bootsrap at boot

2022-07-08 Thread br0nko
On Friday, July 8th, 2022 at 12:31 AM, RVP wrote: > On Thu, 7 Jul 2022, br0nko wrote: > > > bash-5.1# vndconfig vnd0 /home/phil/alix-netbsd.9.2.img > > bash-5.1# fdisk -vv /dev/rvnd0 > > installboot -v -o timeout=5 /dev/rsd0a /usr/mdec/bootxx_ffsv1 > > > Is rsd0a where you copied /usr/mdec/boot,

Re: i386/amd64 image generated trough mkimage stuck on primary bootsrap at boot

2022-07-08 Thread br0nko
On Thursday, July 7th, 2022 at 11:25 PM, Mike Pumford wrote: > On 07/07/2022 15:40, br0nko wrote: > > > Hi, > > > > 0: NetBSD (sysid 169) > > start 63, size 1568384 (766 MB, Cyls 0/1/1-97/160/62), Active > > beg: cylinder 0, head 1, sector 1 > > end: cylinder 97, head 160, sector 62 > >

Re: i386/amd64 image generated trough mkimage stuck on primary bootsrap at boot

2022-07-07 Thread RVP
On Thu, 7 Jul 2022, br0nko wrote: bash-5.1# vndconfig vnd0 /home/phil/alix-netbsd.9.2.img bash-5.1# fdisk -vv /dev/rvnd0 installboot -v -o timeout=5 /dev/rsd0a /usr/mdec/bootxx_ffsv1 Is rsd0a where you copied /usr/mdec/boot, and dies rsd0a start at the same sector as rsd0c (the NetBSD

Re: i386/amd64 image generated trough mkimage stuck on primary bootsrap at boot

2022-07-07 Thread Mike Pumford
On 07/07/2022 15:40, br0nko wrote: Hi, 0: NetBSD (sysid 169) start 63, size 1568384 (766 MB, Cyls 0/1/1-97/160/62), Active beg: cylinder0, head 1, sector 1 end: cylinder 97, head 160, sector 62 Information from PBR: Not bootable: All bytes

i386/amd64 image generated trough mkimage stuck on primary bootsrap at boot

2022-07-07 Thread br0nko
Hi, I wanted to resurrect an old i386 alix box, and I did follow the guide to create a custom image trough mkimage (https://www.netbsd.org/docs/guide/en/chap-inst-media.html#chap-inst-media-creating-live-images). I did first try on amd64 so that I can first test on my laptop. Build was