-
-
Notifications
You must be signed in to change notification settings - Fork 992
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NTFS, exfat and xfs modules are not compiled in x86-64 arch #2723
Comments
No particular reason. This is because we typically base board specific kernel default configurations of some existing configuration (e.g. from the Raspberry Pi team). I have on my todo to align the kernel configurations a bit more. Essentially move all "generic" kernel modules to the operating system kernel configuration.
I'll consider it. While I rather prefer to not support "wild" usage of HAOS, these modules are upstream and rather low maintenance from HAOS point of view. |
I actually get the idea of not making HAOS more "wild" in order to keep it easier to support and in general. And yeah, there of course is the issue with the discrepancy across arch's configurations. PS |
Personally i compile some of these modules - exfat, ntfs, ntfs3, even fuse - and load them manually, at homeassistant start. but this isn't always working with sambanas addon, depending by addons loading order. |
I was just about to move my XFS 4TB of storage from an old power hungry PC on to my shiny new HAOS box and have stumbled into this issue. +1 vote for adding XFS into the kernel from me :-) |
There hasn't been any activity on this issue recently. To keep our backlog manageable we have to clean old issues, as many of them have already been resolved with the latest updates. |
could you explain a bit more on how to do that please? |
first of all, reading this: https://developers.home-assistant.io/docs/operating-system/getting-started/ then, modifying few config files, as follow:
then run "sudo scripts/enter.sh make generic_x86_64" after compiling, search for "aqc111.ko", "ntfs.ko", etc - don't remember exactly the build path. please nothe that these modules aren't present in modules.dep (as not entire haos will be replaced). not loadable with modprobe. i have a script running after homeassistant finish to load, with required commands - like "/sbin/insmod /mnt/data/supervisor/homeassistant/modules/ntfs.ko". for usb net modules, "/sbin/modprobe usbnet" is required first.. any operation requiring for these modules to be already loaded before the running the script will fail. for sure, all of these modifications coudl be made by HA developers directly in source, but is their decision not to do so. |
@agners could you consider again adding support to these filesystems ? |
added pull request #3516 |
Enable NTFS and exFAT drivers, as they're not in defconfigs of all platforms and may be useful when mounting removable drives. Fixes #2723 Co-authored-by: Jan Čermák <sairon@users.noreply.github.com>
Describe the issue you are experiencing
When launching a SambaNAS addon I can see in the logs
I am using Home Assistant OS in generic x86-64 device (smth like Intel NUC) and according to this comment from add-on repo
dianlight/hassio-addons#160 (comment)
As well as some others dianlight/hassio-addons#160 (comment)
The problem is that x86-64 version of Hassos doesn't have this modules compiled, but what surprises me that some other arch version has. So is there any particular reason for such a discrepancy? Will it be reasonable to compile these modules into the next release version of Hassos x86-64m even if it's not the main idea of the OS, but if aarch64 can have it, why not us?
What operating system image do you use?
generic-x86-64 (Generic UEFI capable x86-64 systems)
What version of Home Assistant Operating System is installed?
Home Assistant OS 10.5
Did you upgrade the Operating System.
Yes
Steps to reproduce the issue
Anything in the Supervisor logs that might be useful for us?
Anything in the Host logs that might be useful for us?
System information
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: