Filesysbox 54.8: AROS FORUMS

Filesysbox 54.8

Last updated on 1 month ago

salass00Software Dev

Posted 1 month ago

I just released filesysbox version 54.8 for m68k-amigaos and i388-aros (ABIv0):

https://github.co.../tag/V54.8

This release adds the new FbxDismount command that can be used to cleanly unmount any FUSE based file system. Unlike "Assign DISMOUNT" it will not leave the file system process running in the background. Any outstanding locks/notify requests will be handled by the filesysbox internal lockhandler.

The FbxDismount command has already existed for a while now in the filesysbox source repo but I didn't release it until today because I just managed to fix a bug in the lockhandler that was causing a crash if you were CD:ed to a FUSE file system when it was dismounted and then tried to do something from that shell.

6 users reacted to this post

miker1264, aha, Amiwell79, retrofaza, deadwood, Deremon

amigamiaAdmin

Posted 1 month ago

Nice work! Thank you for sharing.

AMIGASYSTEMDistro Maintainer

Posted 1 month ago

Thanks salass00, ‘filesysbox.library’ version 54.8 works fine, but ‘FbxDismount’ on AROS crashes (Guru).

I compiled 64-bit filesysbox version 54.8, and even with 64-bit AROS, ‘filesysbox.library’ works fine, but ‘FbxDismount’ crashes (Guru).

AROS One All Thread
AROS One Home Site
AROS One Facebook

salass00Software Dev

Posted 1 month ago

@AMIGASYSTEM

Can you try if the latest commit helps with that?

https://github.co...e89e81fb87

AMIGASYSTEMDistro Maintainer

Posted 1 month ago

OK, thank you, now ‘FbxDismount’ 64bit works fine, dismounting is immediate!

I tried mounting and dismounting and everything went well!

Mount SMB2:
FbxDismount SMB2:

AROS One All Thread
AROS One Home Site
AROS One Facebook

salass00Software Dev

Posted 1 month ago

Apparently some minor code changes I made just before release broke the i386-aros build of FbxDismount so I replaced the i386-aros archive yesterday evening with one containing a working FbxDismount command (it is compiled from the same code but with __startup attribute added to the _start() function).

I would like to build releases for x86_64-aros as well and I have a (seemingly) working cross-compiler setup for this already, but I have no way of testing if the produced binaries are working or not. So far all my attempts at trying to boot x86_64-aros in VirtualBox have met with failure. I get to the grub screen just fine but then after that I just get a black screen and nothing seems to happen.

retrofazaDistro Maintainer

Posted 1 month ago

salass00 wrote:

I would like to build releases for x86_64-aros as well and I have a (seemingly) working cross-compiler setup for this already, but I have no way of testing if the produced binaries are working or not. So far all my attempts at trying to boot x86_64-aros in VirtualBox have met with failure. I get to the grub screen just fine but then after that I just get a black screen and nothing seems to happen.

Hmm, maybe you selected “Other/Other unknown” instead of “Other/Other unknown (64-bit)” during installation in VBox?

salass00Software Dev

Posted 1 month ago

No, I did select "Other/Unknown (64-bit)".

deadwoodAROS Dev

Posted 1 month ago

Also try adding debug=serial to grub command line ('e', add and then CTRL+x). This should show some output (and and send the output to COM port if you have it configured in your VM) that can help us discover the issue. I do most of development and testing in VirtualBox 7.1.4.

salass00Software Dev

Posted 1 month ago

#10

Adding debug=serial I get the following output:

Quote

0000000000000000 0x0000000000000000 | 000 | AROS - The AROS Research OS
0000000000000000 0x0000000000000000 | 000 | 64-bit build. Compiled Apr 18 2025
000000177b6c0428 0x0000000000000000 | 000 | ACPI: RSDP 0x00000000000E0000 000024 (v02 VBOX )
000000177e079dbe 0x0000000000000000 | 000 | ACPI: XSDT 0x0000000003FF0030 00003C (v01 VBOX VBOXXSDT 00000001 ASL 00000061)
000000178140f821 0x0000000000000000 | 000 | ACPI: FACP 0x0000000003FF00F0 0000F4 (v04 VBOX VBOXFACP 00000001 ASL 00000061)
000000178428fda8 0x0000000000000000 | 000 | ACPI: DSDT 0x0000000003FF0610 002353 (v02 VBOX VBOXBIOS 00000002 INTL 20230628)
000000178639b000 0x0000000000000000 | 000 | ACPI: FACS 0x0000000003FF0200 000040
00000017873f9e0b 0x0000000000000000 | 000 | ACPI: APIC 0x0000000003FF0240 000054 (v02 VBOX VBOXAPIC 00000001 ASL 00000061)
000000178a102632 0x0000000000000000 | 000 | ACPI: SSDT 0x0000000003FF02A0 00036C (v01 VBOX VBOXCPUT 00000002 INTL 20230628)
[HPET] 0 units total

deadwoodAROS Dev

Posted 1 month ago

#11

Hmm, the bootstrap looks ok. Attached is a config I use - plase try it on your VM.

Alternativelly since you mentioned you already have a cross-compiler, then probably you also have AROS hosted built - you can use that for testing as well. (https://arosnews.github.io/how-to-cross-compile-aros-hosted-wsl/)

You do not have access to view attachments

AMIGASYSTEMDistro Maintainer

Posted 1 month ago

#12

salass00, if you have the opportunity to install VMware Player, it will be much easier. With VMware, you will encounter no difficulties and enjoy better usability.

Regarding VirtualBox, you may need to enable VT-x or AMD-V in the BIOS.

AROS One All Thread
AROS One Home Site
AROS One Facebook

salass00Software Dev

Posted 1 month ago

#13

@deadwood

I tried with your settings (I had to reduce the memory a little and change the name of the serial log file) but it still stops with the same serial output.

While I do have a working hosted AROS install I don't have a working network in it, which means I won't be able to test smb2-handler with it. I have previously attempted to get a working network connection with hosted AROS using guides on the internet, but with no success.

@AMIGASYSTEM

I checked the BIOS settings and while I couldn't find any mention of VT-x or AMD-V I did find a setting for "Virtualization Technology" which was grayed out but listed as enabled. The CPU is an Intel Core 2 Duo 6400 @ 2.13 GHz.

deadwoodAROS Dev

Posted 1 month ago

#14

Hmm, that's very weird. All I can recommend right now is to try either VMWARE or QEMU on your machine. AROS works equally good in all 3 VMs types.

AMIGASYSTEMDistro Maintainer

Posted 1 month ago

#15

salass00, if it helps, I am attaching my AROS 64-bit Hosted Linux startup files. I use VMware. I am not a Linux expert, but I believe they also work on other virtual machines.

I am also attaching a screenshot showing how to configure AROS Network Prefs!

Important: SMB2 requires a static IP address to work on AROS Linux Hosted; it does not work with a computer name!

On native VMware and native PCs, however, SMB2 works perfectly even with a PC name.

AROS One All Thread
AROS One Home Site
AROS One Facebook

1 user reacted to this post

salass00

You do not have access to view attachments

salass00Software Dev

Posted 1 month ago

#16

@AMIGASYSTEM

Using your startup script and network settings I now have hosted AROS connected to aros0 network and I'm able to ping 192.168.166.1 but any IP address outside of the aros0 network seems to be inaccessible still.

This is enough to test smb2-handler though and it seems to be working fine

Edited by salass00 on 05-02-2026 07:00, 1 month ago

1 user reacted to this post

deadwood

salass00Software Dev

Posted 1 month ago

#17

I've now added x86_64-aros binary archives to the latest releases of filesysbox and smb2fs.

1 user reacted to this post

Deremon

AMIGASYSTEMDistro Maintainer

Posted 1 month ago

#18

salass00 wrote:

@salass00 - @AMIGASYSTEM

Using your startup script and network settings I now have hosted AROS connected to aros0 network and I'm able to ping 192.168.166.1 but any IP address outside of the aros0 network seems to be inaccessible still.

This is enough to test smb2-handler though and it seems to be working fine .

I don't quite understand which connection isn't working properly, but here are the results of my tests:

- VMware+Linux-AROS Hosted = You can connect to shared files on your networked PCs, even on a PC other than the one where AROS is installed.

In the attached screenshot, you can see AROS One connecting to the shared folders of Win7, where VMware+Linux-AROS Hosted is installed, but it also accesses the shared folder of Win8, a clean system where neither Linux nor AROS is installed.

- VMware+Linux-AROS Hosted = To connect, you must use a static IP address of the PC that is sharing; the computer name does not work.

- VMware-AROS Native/Virtualized = Can connect to the shared folder of the host PC (Win7) with either a static IP or the PC name.
VMware-AROS Native/Virtualized = Can connect to the shared folder of a networked PC (Win8) only if you use a static IP.

On a Native AROS PC, if I remember correctly, you should be able to connect with both a static IP and a PC name, but I would need to check to confirm.

AROS One All Thread
AROS One Home Site
AROS One Facebook

You do not have access to view attachments

salass00Software Dev

Posted 1 month ago

#19

As I'm already using 64-bit Ubuntu on this machine I saw no reason to use a VM to run linux hosted AROS, so I cut out the middleman. To hopefully make it more clear I can ping the aros0 gateway at 192.168.166.1 and I can ping the host at 192.168.0.x (its static IP address on my router's local network) but I can't ping the router or the static IP of any other machine on the local network.

retrofazaDistro Maintainer

Posted 1 month ago

#20

salass00 wrote:

@salass00 - As I'm already using 64-bit Ubuntu on this machine I saw no reason to use a VM to run linux hosted AROS, so I cut out the middleman. To hopefully make it more clear I can ping the aros0 gateway at 192.168.166.1 and I can ping the host at 192.168.0.x (its static IP address on my router's local network) but I can't ping the router or the static IP of any other machine on the local network.

Have you entered the correct name of your network interface in the script (where you run iptables)?

This tutorial includes a section describing how to connect (in the example script, you need to change "eth0" to your name if it is different).

https://arosnews....osted-wsl/

1 user reacted to this post

salass00

You can view all discussion threads in this forum.
You cannot start a new discussion thread in this forum.
You cannot reply in this discussion thread.
You cannot start on a poll in this forum.
You cannot upload attachments in this forum.
You cannot download attachments in this forum.

Moderator: Administrator, Moderators

Users who participated in discussion: amigamia, deadwood, salass00, AMIGASYSTEM, retrofaza

Search AROSWorld

Filesysbox 54.8