Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - none

#1
Hi,

this happened to me here, I would like to know if is just me.

I am building 26.7.7 again for post PHP issue images, so this happened here:


[20261022135603] ===> License PHP301 accepted by the user
===>   php85-zlib-8.5.12 depends on file: /usr/local/sbin/pkg - not found
[20261022135603] ===> License BSD2CLAUSE accepted by the user
[20261022135603] => 65e6bddc5ffb3edb71e240f7bbaf58fb00b7002e.patch doesn't seem to exist in /usr/ports/distfiles.
[20261022135603] => Attempting to fetch https://github.com/opnsense/pkg/commit/65e6bddc5ffb3edb71e240f7bbaf58fb00b7002e.patch
fetch: https://github.com/opnsense/pkg/commit/65e6bddc5ffb3edb71e240f7bbaf58fb00b7002e.patch: size mismatch: expected 2827, actual 2831
[20261022135604] => Attempting to fetch http://distcache.FreeBSD.org/ports-distfiles/65e6bddc5ffb3edb71e240f7bbaf58fb00b7002e.patch
fetch: http://distcache.FreeBSD.org/ports-distfiles/65e6bddc5ffb3edb71e240f7bbaf58fb00b7002e.patch: Not Found
[20261022135605] => Couldn't fetch it - please try to retrieve this
[20261022135605] => port manually into /usr/ports/distfiles and try again.
*** Error code 1

Stop.
make[1]: stopped making "install" in /usr/ports/opnsense/pkg
*** Error code 1

Stop.
make: stopped making "install" in /usr/ports/archivers/php85-zlib
[20261022135608] ===> Cleaning for pkg-2.8.4_1
[20261022135609] ===> Cleaning for php85-zlib-8.5.12
[20261022135613] ===> License BSD3CLAUSE accepted by the user
===>   snappy-1.3.1 depends on file: /usr/local/sbin/pkg - not found
[20261022135613] ===> License BSD2CLAUSE accepted by the user
[20261022135613] => 65e6bddc5ffb3edb71e240f7bbaf58fb00b7002e.patch doesn't seem to exist in /usr/ports/distfiles.
[20261022135613] => Attempting to fetch https://github.com/opnsense/pkg/commit/65e6bddc5ffb3edb71e240f7bbaf58fb00b7002e.patch
fetch: https://github.com/opnsense/pkg/commit/65e6bddc5ffb3edb71e240f7bbaf58fb00b7002e.patch: size mismatch: expected 2827, actual 2831
[20261022135613] => Attempting to fetch http://distcache.FreeBSD.org/ports-distfiles/65e6bddc5ffb3edb71e240f7bbaf58fb00b7002e.patch
fetch: http://distcache.FreeBSD.org/ports-distfiles/65e6bddc5ffb3edb71e240f7bbaf58fb00b7002e.patch: Not Found
[20261022135614] => Couldn't fetch it - please try to retrieve this
[20261022135614] => port manually into /usr/ports/distfiles and try again.
*** Error code 1

Stop.

and

[20261022141943] ===> License BSD2CLAUSE accepted by the user
[20261022141943] => 6a8c6d4bfc5fef41a055952ab2f6fd5e8c6348cb.patch doesn't seem to exist in /usr/ports/distfiles.
[20261022141943] => Attempting to fetch https://github.com/opnsense/pkg/commit/6a8c6d4bfc5fef41a055952ab2f6fd5e8c6348cb.patch
fetch: https://github.com/opnsense/pkg/commit/6a8c6d4bfc5fef41a055952ab2f6fd5e8c6348cb.patch: size mismatch: expected 3036, actual 3038
[20261022141944] => Attempting to fetch http://distcache.FreeBSD.org/ports-distfiles/6a8c6d4bfc5fef41a055952ab2f6fd5e8c6348cb.patch
fetch: http://distcache.FreeBSD.org/ports-distfiles/6a8c6d4bfc5fef41a055952ab2f6fd5e8c6348cb.patch: Not Found
[20261022141945] => Couldn't fetch it - please try to retrieve this
[20261022141945] => port manually into /usr/ports/distfiles and try again.

I then downloaded manually the patches and updated the distinfo data as well. The ports build now runs as usual here.

Thanks,

none
#2
Hi,

The ports build for 26.7.7 fails just on this package:

>>> ERROR: The build encountered fatal issues!
>>> Aborted sysinfo-1.0.4_1 via sysutils/sysinfo
*** Error code 1

And the reason was:

===>  License BSD2CLAUSE accepted by the user
===>   sysinfo-1.0.4_1 depends on file: /usr/local/sbin/pkg - found
=> sysinfo-1.0.4.tar.gz doesn't seem to exist in /usr/ports/distfiles.
=> Attempting to fetch https://codeberg.org/BSDforge/sysinfo/archive/1.0.4.tar.gz?dummy=/sysinfo-1.0.4.tar.gz
fetch: https://codeberg.org/BSDforge/sysinfo/archive/1.0.4.tar.gz?dummy=/sysinfo-1.0.4.tar.gz: size mismatch: expected 15618, actual 15546
=> Attempting to fetch http://distcache.FreeBSD.org/ports-distfiles/sysinfo-1.0.4.tar.gz
fetch: http://distcache.FreeBSD.org/ports-distfiles/sysinfo-1.0.4.tar.gz: size mismatch: expected 15618, actual 15546
=> Couldn't fetch it - please try to retrieve this
=> port manually into /usr/ports/distfiles and try again.
*** Error code 1

Stop.
make[1]: stopped making "/usr/ports/sysutils/sysinfo/work/.stage_done.sysinfo._usr_local" in /usr/ports/sysutils/sysinfo
*** Error code 1

Stop.
make: stopped making "all" in /usr/ports/sysutils/sysinfo

I downloaded the tar and the file size was changed. I then found the update on freshports:


TIMESTAMP = 1791702801
SHA256 (sysinfo-1.0.4.tar.gz) = 4e6f7cd237822521813cfb0dde0d4213cba0d4c9ed266f8edce7a1def85c9d32
SIZE (sysinfo-1.0.4.tar.gz) = 15546

the changelog for that item is:
*/*: Refresh checksums for on the fly archives on codeberg.org

See https://codeberg.org/Codeberg/Community/issues/2861

Approved by: blanket

Should I wait for any update on the 26.7.7 tag or find a workaround and wait for 26.7.8? :)

thanks,

none
#3
Hello,

for the record, 26.7.6 builds fine.

Thanks,

none
#4
I think I saw pointers that this change would be ARM related, while searching for this error.

Your builds are AMD64 only, right?

I will wait for 26.7.6 and try again.

Thanks for the feedback :)

none
#5
the error:

Quote/usr/src/sys/dev/pci/pci_host_generic_fdt.c:122:2: error: call to undeclared function 'ofw_bus_destroy_iinfo'; ISO C99 and later do not support implicit function declarations [-Werror,-Wimplicit-function-declaration]
  122 |         ofw_bus_destroy_iinfo(&sc->pci_iinfo);
      |         ^
/usr/src/sys/dev/pci/pci_host_generic_fdt.c:122:2: note: did you mean 'ofw_bus_setup_iinfo'?
/usr/src/sys/dev/ofw/ofw_bus_subr.h:88:6: note: 'ofw_bus_setup_iinfo' declared here
   88 | void    ofw_bus_setup_iinfo(phandle_t, struct ofw_bus_iinfo *, int);
      |         ^
1 error generated.
--- pci_host_generic_fdt.o ---
*** [pci_host_generic_fdt.o] Error code 1

make[2]: stopped making "all" in /usr/obj/usr/src/arm64.aarch64/sys/SMP-ARM

#6
Hello,

I build arm images and the 26.7.5 build failed for src. I got to find out the reason was this:

ofw_bus_destroy_iinfo()

that was introduced in this commit:

https://github.com/opnsense/src/commit/ed5b1f4fb4d2f4c8c13004f7fc7560fb8e6b7864

So now there is no 26.7.5 tag and the build fails complaining about this function. I saw that src tagged 26.7.4 doesn't have this call, so I am trying to build 26.7.5 using src tagged 26.7.4. Will be a 26.7.5 tag or should I expect just 26.7.6?

Thanks

none

#7
Hi Franco,

would be a big issue if I build 26.7 using 14.x FreeBSD?

On 26.1 I used to build and it was ok, faster and the build would run without errors. For 26.7 the packages get errors and even github clone fails with timeout. My guess is something about 15.1 and arm boxes, as other amd64 15.1 systems don't show this, and they are on the very same network, ISP, dns server, etc...

I remember using command line to overrule OS version. But my question is if that would hurt the final image binaries.

the errors are:

>>> ERROR: The build encountered fatal issues!
>>> Aborted netdata-2.8.5_7 via net-mgmt/netdata
>>> Aborted telegraf-1.39.1_1 via net-mgmt/telegraf
>>> Aborted opnsense-filterlog-0.10.0 via opnsense/filterlog-go
>>> Aborted ndp-proxy-go-1.0.4 via opnsense/ndp-proxy-go
>>> Aborted crowdsec-1.7.8_1 via security/crowdsec
>>> Aborted tailscale-1.98.9 via security/tailscale
>>> Aborted xray-core-26.3.27_2 via security/xray-core
>>> Aborted node_exporter-1.11.0_3 via sysutils/node_exporter
>>> Aborted nut-2.8.5_1 via sysutils/nut
>>> Aborted caddy-custom-2.11.4.0.0.4.5.13_18 via www/caddy-custom
*** Error code 1

have this also:

pkg-static: Both ABI_FILE and OSVERSION are set, ABI_FILE overrides OSVERSION
# get https://proxy.golang.org/github.com/akavel/rsrc/@v/v0.10.2.mod: Get "https://proxy.golang.org/github.com/akavel/rsrc/@v/v0.10.2.mod": net/http: TLS handshake timeo
ut
# get https://proxy.golang.org/github.com/spf13/cobra/@v/v1.9.1.mod: Get "https://proxy.golang.org/github.com/spf13/cobra/@v/v1.9.1.mod": net/http: TLS handshake timeout
# get https://proxy.golang.org/github.com/inconshreveable/mousetrap/@v/v1.1.0.mod: Get "https://proxy.golang.org/github.com/inconshreveable/mousetrap/@v/v1.1.0.mod": net
/http: TLS handshake timeout
# get https://proxy.golang.org/github.com/spf13/pflag/@v/v1.0.6.info
# get https://proxy.golang.org/github.com/google/shlex/@v/v0.0.0-20191202100458-e7afc7fbc510.info
# get https://proxy.golang.org/github.com/inconshreveable/mousetrap/@v/v1.1.0.info
# get https://proxy.golang.org/github.com/spf13/cobra/@v/v1.9.1.info
# get https://proxy.golang.org/github.com/akavel/rsrc/@v/v0.10.2.info
# get https://proxy.golang.org/github.com/%21masterminds/semver/v3/@v/v3.4.0.info
# get https://proxy.golang.org/github.com/josephspurrier/goversioninfo/@v/v1.5.0.info
# get https://proxy.golang.org/github.com/spf13/pflag/@v/v1.0.6.info: 200 OK (0.299s)
# get https://proxy.golang.org/github.com/google/shlex/@v/v0.0.0-20191202100458-e7afc7fbc510.info: 200 OK (0.299s)
# get https://proxy.golang.org/github.com/inconshreveable/mousetrap/@v/v1.1.0.info: 200 OK (0.300s)
# get https://proxy.golang.org/github.com/akavel/rsrc/@v/v0.10.2.info: 200 OK (0.300s)
# get https://proxy.golang.org/github.com/%21masterminds/semver/v3/@v/v3.4.0.info: 200 OK (0.301s)
# get https://proxy.golang.org/github.com/spf13/cobra/@v/v1.9.1.info: 200 OK (275.998s)
# get https://proxy.golang.org/github.com/josephspurrier/goversioninfo/@v/v1.5.0.info: 200 OK (275.998s)
go: github.com/Masterminds/semver/v3@v3.4.0: Get "https://proxy.golang.org/github.com/%21masterminds/semver/v3/@v/v3.4.0.mod": net/http: TLS handshake timeout
go: github.com/akavel/rsrc@v0.10.2: Get "https://proxy.golang.org/github.com/akavel/rsrc/@v/v0.10.2.mod": net/http: TLS handshake timeout
go: github.com/google/shlex@v0.0.0-20191202100458-e7afc7fbc510: Get "https://proxy.golang.org/github.com/google/shlex/@v/v0.0.0-20191202100458-e7afc7fbc510.mod": net/htt
p: TLS handshake timeout
go: github.com/inconshreveable/mousetrap@v1.1.0: Get "https://proxy.golang.org/github.com/inconshreveable/mousetrap/@v/v1.1.0.mod": net/http: TLS handshake timeout     
go: github.com/josephspurrier/goversioninfo@v1.5.0: Get "https://proxy.golang.org/github.com/josephspurrier/goversioninfo/@v/v1.5.0.mod": net/http: TLS handshake timeout
go: github.com/spf13/cobra@v1.9.1: Get "https://proxy.golang.org/github.com/spf13/cobra/@v/v1.9.1.mod": net/http: TLS handshake timeout
go: github.com/spf13/pflag@v1.0.6: Get "https://proxy.golang.org/github.com/spf13/pflag/@v/v1.0.6.mod": net/http: TLS handshake timeout
*** Error code 1

I will try to test over amd64 here to see if the errors are present too (network errors). I will try to fix a amd64 box over the weekend.

thanks for the help,

none
#8
Thanks for the answer.

My usual build time for it all was about 36h. Now its way more, and the box is the same. I am looking for the reason :)

none
#9
Hi,

I build arm64 images for opnsense and this week I begun building for 26.7 family. Usually ports build takes 20 to 24 hours, but it is now over 3 days and not close to end.

Has the change to FreeBSD 15.1 demanded special config to use all cpu cores? FreeBSD can see all 8 cores:

---<<BOOT>>---
Copyright (c) 1992-2025 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
        The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 15.1-RELEASE releng/15.1-n283562-96841ea08dcf GENERIC arm64
FreeBSD clang version 19.1.7 (https://github.com/llvm/llvm-project.git llvmorg-19.1.7-0-gcd708029e0b2)
VT(efifb): resolution 640x480
real memory  = 16879779840 (16097 MB)
avail memory = 16487489536 (15723 MB)
Starting CPU 1 (100)
Starting CPU 2 (200)
Starting CPU 3 (300)
Starting CPU 4 (400)
Starting CPU 5 (500)
Starting CPU 6 (600)
Starting CPU 7 (700)
FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs

but the ports build uses only one :(

If anyone have any hints on how to change it :)

thanks,

none
#10
Hi,

as 25.7 uses pkg 1.19.5_2, I upgraded the build box to 14.3R and had some trouble updating the packages, every time I got this message:

pkg update
Updating FreeBSD repository catalogue...
pkg: https://pkgmir.geo.freebsd.org/FreeBSD:14:aarch64/quarterly/packagesite.txz: Not Found
Unable to update repository FreeBSD
Updating FreeBSD-kmods repository catalogue...
Fetching packagesite.pkg: 100%   15 KiB  15.4kB/s    00:01   
Processing entries: 100%
FreeBSD-kmods repository update completed. 68 packages processed.
Error updating repositories!
root@rpi5-hd:/usr/ports/ports-mgmt/pkg # pkg info | grep pkg
pkg-1.19.2_5                   Package manager

The environment here is Raspberry Pi 5 8GB arm64 and USB disk and NIC.

I upgraded to last pkg and got it to update packages repo, then I built again 1.19.5_2 and now the same message above shows when I try to update.

Is there any hints on this? Last time I searched I got the idea that I need to run the same pkg version on the build box. If this is not true anymore, would help a lot :)

Thanks,

none
#11
Hi,

I am trying to build ARM64 images for opnsense and now I have to add manually two files after I dd the image to the microSD.

I found a small guide for git on this post, but the images won't have the same files I commit using this commands.

I use the following line to build:

make -C /usr/tools/ VERSION=$TAG_SRC DEVICE=$DEVICE base

Where TAG_SRC on the last build has the value of 25.1.4.

I did:

git tag -f -m "message" 25.1.4

and then on the /usr/core (where my commited files are) I run:

git checkout 25.1.4

and there my files are what I expect them to be.

My knowledge of git is not much, if anyone has any hints here :)

I want to include my fingerprint for the packages and a new /usr/local/etc/rc script for ARM64 gpart resizing.

Thanks in advance :)

none
#12
Hi Franco,

I got to walk a few steps here, here is the result.

I found that the line:

        local IDX=${1##"${DEV}p"}
in /usr/local/etc/rc was returning a value that would make the next "if" always be true:

        if [ "${IDX}" = "${1}" ]; then
                # assume schema ada0a used by nano images
                IDX=1
        fi
This way when disks configured as MBR, as is the case here, would always default to IDX=1 and make it to the next "if":

       if [ -n "${DEV}" -a "${DEV}" != "${1}" -a \
            -n "${IDX}" -a "${IDX}" != "${1}" ]; then
                gpart recover ${DEV}
                gpart resize -i ${IDX} ${DEV}
       fi

issuing gpart resize on a partition that has no place to grow (and not the root one, also). The partitions here are organized like this:

gpart show da11
=>      63  61069249  da11  MBR  (29G)
        63    131009        - free -  (64M)
    131072     65536     1  fat32lba  [active]  (32M)
    196608   6094848     2  freebsd  (2.9G)
   6291456  54777856        - free -  (26G)
Just as the default opnsense scripts build. Running on index 1 would not meet the premise for the growfs step that follows, and then get that message saying it already has the desired size.

For the Nano image that would do fine, as it has only 1 partition, the BSD scheme is written directly on the device, no MBR or GPT is created.

To address this I created a test to know if it is a MBR scheme, and then act accordingly. That way it finds the index for the root file system and the gpart resize step works.

Now I got a message from gpart tellimg me I need to do a commit to the UFS label (my case was ufs/OPNsense. Not doing that would ruin the boot:

mmcsd0 recovering is not needed
GEOM_PART: ufs/OPNsense was automatically resized.
  Use `gpart commit ufs/OPNsense` to save changes or `gpart undo ufs/OPNsense` to revert them.
mmcsd0s2 resized

That step is outside the grow_partition(), and later I found was not welcome on AMD64 Nano image (may be arch related?). I then created another test to run only on MBR schemes.

My skills here are far from yours and the opnsense team. Here is the file I ended with, I hope my humble time here can help anyhow.

My tests here are also limited. Nano images works as is now and keeps working after the modifications. ARM64 images now work in the first boot. I just need to learn how to commit changes to the local repo, so images will have it out-of-the-box either.

Thanks for the help, as usual :)

The dmesg from that part is:

Booting [/boot/kernel/kernel]...               
Using DTB provided by EFI at 0xef03c000.
����#U}�qqC��� ����!����*���mu��������k�饭�9� ���5������j�j�����������)��y��i*���Ovq4�y���,�J�uQ�����4����+��������몋���
                                                                                                                        ���8�q����i*���
                                                                                                                                       +�v����J��:u�Ѩ��V[]����U8��x��y>k�8�ռy�Ѫ��i�d���i�����.�����8;�u�+����+�ꪨ�,���+���ʊ�����ʊ���+��v�����+��)�ź����*�����l�"�)��᪩��0���uW�S�I+��4��{qɩ��J����+���0��9},����e����Q���}����..��Y��0�ټ�.�g�����+�}���*�����(��k��W;�+*���<�ܑ����������y�J�h������"�(����(��J��$��b*��,��٩���9��ը�����3 �����q�WS[�mq=1>Q2ը��.��z����>A�Y�q5��q��W�騤�ɪ�`�ѤY�Q1QA��8��m+�+��,���m�����)������"�������ъ(�#��������r�*�u�u���������f+����U1��*�b���0�������������+���q�t�9���%��Z�ᩴu�]T���ԼQWI�QS����]�8<������2��*�S�*��j�r��������n�*�j�*[TWS�>��<�,����K
                                                                                                                                                                                          �++��Y)����,(�誶��$�+���uNJ�ي+k����;z���J�������;��գ��ű��
    ����Y�?�����՜u������q���������Y8����񱁙�����(�����a����ɛ�Q:��(���������**�ͣ�����f���Q�Z��銊�����9x��+��e.������       ~qq���z��!��**+���$����(��8x�ዧ������}��(���Ț�Z�)���������动���::I�����1::I�Ŋ�:����!::�����*��8
                                                                                                                                                                                                                     ������uhub0: 1 port with 1 removable, self powered
uhub3: 1 port with 1 removable, self powered
uhub2: 2 ports with 2 removable, self powered
uhub5: 2 ports with 2 removable, self powered
Mounting filesystems...
tunefs: soft updates remains unchanged as enabled
uhub1: 1 port with 1 removable, self powered
uhub4: 1 port with 1 removable, self powered
camcontrol: cam_lookup_pass: CAMGETPASSTHRU ioctl failed
cam_lookup_pass: No such file or directory
cam_lookup_pass: either the pass driver isn't in your kernel
cam_lookup_pass: or mmcsd0 doesn't exist
mmcsd0 recovering is not needed
GEOM_PART: ufs/OPNsense was automatically resized.
  Use `gpart commit ufs/OPNsense` to save changes or `gpart undo ufs/OPNsense` to revert them.
mmcsd0s2 resized
super-block backups (for fsck_ffs -b #) at:
 6402432, 7682880, 8963328, 10243776, 11524224, 12804672, 14085120, 15365568,
 16646016, 17926464, 19206912, 20487360, 21767808, 23048256, 24328704,
 25609152, 26889600, 28170048, 29450496, 30730944, 32011392, 33291840,
 34572288, 35852736, 37133184, 38413632, 39694080, 40974528, 42254976,
 43535424, 44815872, 46096320, 47376768, 48657216, 49937664, 51218112,
 52498560, 53779008, 55059456, 56339904, 57620352, 58900800, 60181248
** /dev/ufs/OPNsense
FILE SYSTEM CLEAN; SKIPPING CHECKS
clean, 6831398 free (94 frags, 853913 blocks, 0.0% fragmentation)
Setting hostuuid: 00000000-0000-0000-eb8b-ff6f21811d36.
Setting hostid: 0x5f653895.
>>> Invoking import script 'importer'
Press any key to start the configuration importer: .......
Bootstrapping config.xml...done.


FreeBSD/arm64 (OPNsense.localdomain) (ttyu1)

login: root
Password:
------------------------------------------------
|       Hello, this is OPNsense 25.1           |           :::::::.
|                                              |           :::::::::.
|  Website:     https://opnsense.org/          |        :::        :::
|  Handbook:    https://docs.opnsense.org/     |        :::        :::
|  Forums:      https://forum.opnsense.org/    |        :::        :::
|  Code:        https://github.com/opnsense    |         `:::::::::
|  Reddit:      https://reddit.com/r/opnsense  |           `:::::::
------------------------------------------------

*** OPNsense.localdomain: OPNsense 25.1.3_33 (aarch64) ***

 LAN (re0)       -> v4: 192.168.1.1/24
 WAN (re1)       ->

 HTTPS: sha256 2B 47 72 39 88 B9 32 31 2F 65 59 19 61 F6 85 76
               08 19 F7 E9 39 34 18 F8 97 70 A1 58 50 46 2C 41

  0) Logout                              7) Ping host
  1) Assign interfaces                   8) Shell
  2) Set interface IP address            9) pfTop
  3) Reset the root password            10) Firewall log
  4) Reset to factory defaults          11) Reload all services
  5) Power off system                   12) Update from console
  6) Reboot system                      13) Restore a backup

Enter an option: 8

root@OPNsense:~ # df -h
Filesystem                   Size    Used   Avail Capacity  Mounted on
/dev/ufs/OPNsense             28G    2.0G     24G     8%    /
devfs                        1.0K      0B    1.0K     0%    /dev
/dev/msdosfs/MSDOSBOOT        32M    832K     31M     3%    /boot/msdos
devfs                        1.0K      0B    1.0K     0%    /var/dhcpd/dev
devfs                        1.0K      0B    1.0K     0%    /var/unbound/dev
/usr/local/lib/python3.11     28G    2.0G     24G     8%    /var/unbound/usr/local/lib/python3.11
/lib                          28G    2.0G     24G     8%    /var/unbound/lib
#13
Quote from: franco on April 04, 2025, 02:42:57 PM> so even in the nano image the the resizing is not working?

Says you? Last time I checked it worked, which was 25.1...

No, please don't get me wrong. I misunderstood your post, so I asked to be sure. I thought you were saying that was not working anymore, and now I see I got it wrong.

You said earlier it worked for you on amd64 and as I read it I got confused, as if you had tested again and said was not working anymore. Sorry for the noise :(

I just was trying to get something to compare and have a starting point. And now I have it. Thanks again.

none
#14
Hi Franco,

so even in the nano image the the resizing is not working?

I will fix a pc for testing this and see what I can help.

Thanks again.

none
#15
Hi Franco, can you point me out a case that should work so I can try to look it and reproduce here? What image to test?

I want to know what disk partitioning there should be so the growfs will work.

thanks,

none