Audioniek Images: general info

[Audioniek]

Instructions

Fortis - Flash

Pertains to the following receivers:

• hs8200 (atevio7500)
• hs7119
• hs7429
• hs7819

Do the following:

• Download the correct .zip-file for your receiver;
• Unpack it. You will get two files. One is the customary Fortis .ird file, the other is an .md5 checksum file with which you can verify the integrity of the .ird file;
• Place the .ird file in the root directory of a FAT32 formatted USB stick. The file should be the only file in that directory;
• Switch off the receiver with the switch on the back;
• Insert the prepared USB stick in an USB port of the receiver;
• Press and hold the CH+ or arrow up key on the front panel of the receiver;
• While pressing the front panel key, switch the receiver back on with the switch on the back;
• Release the key when flashing has started.

When you see Er.0x10:
The .ird file provided always has the resellerID of the Octagon version of the particular Fortis model. It is part of the file name of the .ird file. When you see Er.0x10 in the display, the resellerID in the receivers' boot loader and that of the .ird file do not match.
In this case you can do one of two things. The first and recommended way is to change the resellerID of the .ird file in question using a reseller changer programme, of which several are circulating the net. You should find that the only change required are the third and fourth digits of the resellerID. If other changes are necessary, the flash file is NOT suitable for your receiver.
The second way out of this problem is reflashing the bootloader with one that holds the same resellerID as the .ird file. This approach is NOT recommended, as you will brick your receiver in case something goes wrong.

The flash file provided should work with any boot loader that is capable of running an original Fortis factory firmware.

Fortis - USB

Variant 1; pertains to the following receivers:

• fs9000, also fs9200 (fortis_hdbox)
• hs9510 (octagon1008)
• hs8200 (atevio7500)

The image is supplied as a .tar.gz archive that needs further handling before it can be run. The receiver must be equipped with a modified boot loader that can start the file uImage off an USB stick, for example TDT Maxiboot or iBoot. See the instructions elsewhere on the forum on how to proceed.

Variant 2; pertains to the following receivers:

• all hs7XXX

The image is supplied as two files: uImage and rootfs.img that are obtained after unpacking the .zip file. Place both files on a FAT32 formatted USB stick, in the root directory. The stick should not hold any other files.

To run the image, the original Fortis bootloader must be upgraded to a version with the last digit 6 or 7 and USB boot should be on (power up with channel down/arrow down depressed). See elsewhere in the forum to find it, and how to install and set it.

Spark & Spark7162 (flash)

Unpack the .zip file directly onto a FAT32 formatted USB stick that is empty. The result should be a directory /enigma2 holding the following files:

• e2jffs2.img
• e2jffs2.img.md5
• uImage
• uImage.md5

The stick can be used to flash the image in the receiver in the customary way (power on with OK on the frontpanel depressed). See elsewhere in the forum for detailed instructions. Please note that on spark7162 models only the USB port on the rear can be used.

Topfield TF77X0HDPVR (in flash (kernel) and on internal hard disk (the rest))

Case 1: receiver already runs Enigma2
Unpack the .zip file on an empty FAT32 formatted USB stick. The stick will contain 7 files, 3 .md5 checksum files and four others.
Switch the receiver off and insert the prepared USB stick in the USB port on the front. Switch the receiver on. It should now boot from the stick and the installation process can be followed on the front panel display. The last step is 1 FSCK. Power the receiver off and remove the USB stick. After repowering it should boot from its hard disk and run the image.
The file Enigma_Installer.ini on the stick has been prepared so that an attempt is made to save the settings and channel list already in use.

Case 2: receiver still runs Topfield firmware
Unpack the .zip file on an empty FAT32 formatted USB stick. The stick will contain seven files, three .md5 checksum files and four others.
Leave the stick in the PC and open the file Enigma_Installer.ini that is on it with a Linux compatible text editor. Change the following lines in the section [parameter]:

• partition=0 to partition=1
• createmini: to your preference (in most cases the provided value 0 will do fine)
• keepsettings=1 to keepsettings=0
• keepbootargs=1 to keepbootargs=0
• format=0 to format=1

Save the file on the stick. If you use a Windows environment, make sure the file is saved with Linux compatible line endings.

Installing the image is a two step process. First power the receiver down and up again, so the Topfield firmware starts. Insert the prepared USB stick in the USB port on the front. Press MENU on the remote control. Select Installation in the main menu and press OK on the remote control. Select USB Firmware Upgrade in the Installation menu (you have to scroll down to see it) and press OK on the remote control. Select the file Enigma_Installer.tfd from the list and press OK on the remote control. Confirm the 'Are you sure' question by selecting Yes and pressing OK on the remote control. When the receivers' display shows a blinking text END, switch the receiver off leaving the USB stick connected.
The second step is started by powering the receiver back on with the USB stick still inserted. It should now boot from the stick and the installation process can be followed on the front panel display. The last step is 1 FSCK and it may take a few minutes to reach depending on the size of the internal hard disk. Power the receiver off and remove the USB stick. After repowering it should boot from its hard disk and run the image.
Caution: after all this your Topfield recordings are lost because the internal hard disk has been repartitioned.

Kathrein UFS912 - flash

Unpack the .zip file on an empty FAT32 formatted USB stick. After unpacking the root directory of the stick will have one directory /kathrein, with two subdirectories in it.
If the receiver is still running the factory firmware, perform the following steps on the PC with the USB stick still attached in order to change the bootargs:

1. Rename the folder /kathrein/ufs912 to /katrein/ufs912_img"
2. Rename the folder /kathrein/ufs912_Bargs to /kathrein/ufs912"

Switch the receiver off using the mains switch on the back and insert the USB stick into its front USB port. To start changing the bootargs, press and hold the key TV/RADIO on the front panel and switch the receiver on using the mains switch. Release the TV/RADIO key when the display shows EMERGENCY BOOT. Changing the bootargs will now begin and is completed when the display shows UPDATE SUCCESS!

Switch the receiver off using the mains switch and remove the USB stick. Perform the following steps on a PC:

1. Rename the folder /kathrein/ufs912 to /katrein/ufs912_Bargs
2. Rename the folder /kathrein/ufs912_img to /kathrein/ufs912

NOTE: Changing the bootargs needs to be done only once.

Flashing the image is done as follows. Switch the receiver off using the mains switch on the back and connect the USB stick to its front USB port. To start the flashing process, press and hold the key TV/RADIO on the front panel and switch the receiver on using the mains switch. Release the TV/RADIO key when the display shows EMERGENCY BOOT. Flashing the image will now begin and is completed when the receiver reboots.

Kathrein UFS913 - flash

Unpack the .zip file on an empty FAT32 formatted USB stick. After unpacking the root directory of the stick will have one directory /kathrein, with one subdirectory ufs913 in it.

Flashing the image is done as follows. Switch the receiver off using the mains switch on the back and connect the USB stick to its front USB port. To start the flashing process, press and hold the key TV/RADIO on the front panel and switch the receiver on using the mains switch. Release the TV/RADIO key when the display shows EMERGENCY BOOT. Flashing the image will now begin and is completed when the receiver reboots for the final time (the flash process also does a reboot half way).

Kathrein UFS922 - flash

Unpack the .zip file on an empty FAT32 formatted USB stick. After unpacking the root directory of the stick will have one directory /kathrein, with one subdirectory ufs922 in it. In the root directory, you will find three files:

• Image_Installer.ini -> The contents of this file controls the installation: first time or update;
• rootfs.tar.gz -> The rootfs in an archive, that will be written to the internal hard disk;
• uImage -> The extra kernel that will perform the installation; will be flashed in NOR flash.

Case 1: receiver already runs Enigma2, from another source
As a first step, convert the receiver back to running Kathrein firmware, then proceed with Case 3.
Instructions and files to restore the receiver to Kathrein firmware are posted here in posting #2.
CAUTION: Your recordings, channel list and other information will be lost.

Case 2: receiver already runs Enigma2
Unpack the .zip file on an empty FAT32 formatted USB stick.
The file Image_Installer.ini on the stick has been prepared so that an attempt is made to save the recordings, settings and channel list already in use.

Case 3: receiver still runs Kathrein firmware
Unpack the .zip file on an empty FAT32 formatted USB stick.
Leave the stick in the PC and open the file Image_Installer.ini that is on it with a Linux compatible text editor. Change the following lines in the section [parameter]:

• partition=0 to partition=1
• createmini: to your preference (in most cases the provided value 0 will do fine)
• keepsettings=1 to keepsettings=0
• keepbootargs=1 to keepbootargs=0
• format=0 to format=1

Save the file on the stick. If you use a Windows environment, make sure the file is saved with Linux compatible line endings.
CAUTION: Your recordings, channel list and other information will be lost.

The installation is done as follows (both with original Kathrein firmware or Audioniek's Enigma2 image):

1. Switch off the receiver using the mains switch on the back and insert the prepared USB disk in the front USB port. Press and hold the front panel key RECORD and switch the receiver on. Keep pressing the key until the display shows "[ ]/UP2TE2/OPT". Then release the key and briefly press the front panel key STOP. The installation will now begin. If the parameters format and partition are set to 1 the formatting and partitioning of the hard disk can take several minutes depending on its size. Progress can be observed in the serial log.
2. Halfway the installation, you are asked to press and hold the RECORD key on the front panel again, so keep observing the front panel display. After the restart release the key when the aforementioned text "[ ]/UP2TE2/OPT" appears in the display and briefly press STOP on the front panel.
3. The installation is complete after the third restart, when the image is run for the first time.

Kathrein - USB

The image is supplied as a .tar.gz archive that needs further handling before it can be run. The receiver must be equipped with a modified boot loader that can start the file uImage off an USB stick, for example TDT Maxiboot. See the instructions elsewhere on the forum on how to proceed.

adb_box (nBox BSKA/BSLA/BXZB/BZZB) - flash

The image is supplied as a set of four files:

• kernel.img
• rootfs.img
• update
• update.img

Copy these files to a FAT32 formatted USB stick and insert the stick in the USB port of the receiver. Power the receiver down by removing the DC power plug.
The way flashing is done depends on the boot loader present in the receiver. If the boot loader signs on with nBox, it contains the B4T bootloader. If the sign on is boot or u-boot... it contains the MAGUS or Freebox loader.

Flash - MAGUS/Freebox loader
Press and hold the power key on the front panel and insert the DC power plug. Release the power key when the display shows PROG. Flashing will then begin. When it is finished, the receiver will restart automatically and run the image.

Flash - B4T loader
Press and hold the arrow up key on the front panel and insert the DC power plug. Release the arrow up key when the display begins showing the various boot options. Use arrow up/down to select the option UPDT/Update, then press the front panel OK key. Flashing will then begin. When it is finished, the receiver will restart automatically and run the image.

The image is built for the Freebox/MAGUS memory layout. If the receiver contains the B4T boot loader, use the boot option n-Fb. Setting the boot option is done the same way as invoking flashing.

adb_box (nBox BSKA/BSLA/BXZB/BZZB) - USB

The image is supplied as the customary .tar.gz file. Unpack this on a ext2 formatted USB stick and insert the stick in the USB port of the receiver. To run the image, select the proper boot option in the boot loader beforehand. Using the B4T boot loader is easiest.

CubeRevo (all models) - USB

Before you can run an image off USB, your CubeRevo (ABcom, Vizyon) receiver needs to have its bootargs changed if it is still in factory condition. This is done by flashing a small file holding the bootargs. A proper file can be found on various forums specializing in CubeRevo and similar receivers and has usually a name containing multiboot, the receiver model name and the extension .img. Please note that the file is different for each receiver model, so download the correct one.

Flashing, all models excluding CubeRevo
To start flashing the file, copy it to a FAT32 formatted USB stick, rename it to usb_update.img. Switch the receiver off using the mains switch on the back. Insert the stick in the USB port on the back of the receiver. Press and hold the front panel power key, and switch the receiver back on using the mains switch. Release the front panel when display shows USB UPGRADE or USB (LED models). The file on the USB stick will be flashed and the process is finished when the display shows DONE.

Flashing, CubeRevo models
Flashing on CubeRevo models requires a Windows PC, an extra USB cable between that PC and the CLIENT USB port on the receiver, as well as the program FlashTools.exe V1.02. Store the file to be flashed in a convenient location on the Windows PC. Connect the PC with the CLIENT USB port on the receiver. Switch the receiver off using the mains switch on the back. Press and hold the front panel power key, and switch the receiver back on using the mains switch. Release the front panel when the display shows USB UPGRADE. Windows should now ask for a driver (when you do this the first time) or produce the sound when a USB device is connected. If Windows wants to install a driver, follow the normal driver installation procedure up to the point where Windows wants to know the name/location of the .INF file. Browse to the file VESTAUSB.inf and click for OK. The file is part of the download package containing FlashTools.exe V1.02 and is installed alongside it in C:\Program Files\FlashTools. After driver installation is complete, start the programme FlashTools.exe.
Click on the text USB. Check the status window in the lower half of the programme window. It should report that the receiver is connected.
Click on the button FILE and browse to the .img file to be flashed, then click to select it.
Next click on the button DOWN. The file will be downloaded to the receiver, and flashed. Flashing is complete when the display on the receiver shows DONE and the status window states 'Completed'. Only when this text is there, FlashTools can be closed.
If you find all of this cumbersome, so do I. If you know how to flash a CubeRevo directly off an USB stick, please let me know and I will share it.

Setting the bootargs (all models)
Setting the bootargs is done by pressing and holding a number key on the remote control, while the boot loader is starting and before the text BOOTING is shown. The best way to achieve this is first pressing and holding the remote control key, and then switching on the receiver using the mains switch. The option selected will be flashed in the bootargs without any display feedback, and the boot loader will then try and use that option. In many cases the receiver will not start after first flashing the bootargs (or setting a wrong option like NFS), so you will have to try the various options. In the multiboot files option 1 is often the option for running the software in flash, and 6 the one to use to run Enigma2 off an USB stick. Please be aware that if the receiver has a built-in hard disk, the USB stick will be sdb1, if no hard disk installed it is sda1.

Preparing the USB stick (all models)
The image is supplied as the customary .tar.gz file. Unpack this on a ext2 formatted USB stick and insert the stick in the USB (HOST) port of the receiver. To run the image, select the proper boot option in the boot loader beforehand. The CubeRevo receivers are unfortunately very picky regarding which stick works. Older, low capacity ones usually work best.


Regards,

Audioniek.

[spartak73]

Hallo! Thanks for the work you've done. I installed the USB image for atevio 7500 (.tar.gz), the image booted and working. Image for hs7429 (usb version) is not booted. Log attached ...

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2019.02.15 22:37:23 =~=~=~=~=~=~=~=~=~=~=~=
  FrTs
 '1 (Re)start USB...
Front USB:   scanning bus for devices... 3 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
            system volume information/
 134217728   root.img 
  3727530   uimage 
            $recycle.bin/
            ./
            ../
       12   wpsettings.dat 
       76   indexervolumeguid 

4 file(s), 4 dir(s)

reading uImage
............................................................................................................................................................................................................................................................................................................................................................................
ret=> 3727530
    FrTs
 '1 (Re)start USB...
Front USB:   scanning bus for devices... 3 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
            system volume information/
 134217728   root.img 
  3727530   uimage 
            $recycle.bin/
            ./
            ../
       12   wpsettings.dat 
       76   indexervolumeguid 

4 file(s), 4 dir(s)

reading uImage
............................................................................................................................................................................................................................................................................................................................................................................
ret=> 3727530

hs7429.log

[Audioniek]

HS7429 USB : I will give it a test and if anything changes, I will upload an improved image.

Regards,

Audioniek.

[Schaagi]

Hi Audioniek

Thank you very much for the new image of the UFS 912. I downloaded it immediately and installed the USB image on my receiver.
The VFD display shows the following informations:
- wait for 1 minute
- Load 9
- FW missing
- Load 6
After that nothing happens anymore - there is no picture on the monitor.

I'm looking forward to the next releases.

Best regards
Schaagi

[Audioniek]

Hello Schaagi,

I have been able to reproduce your problem with UFS912_USB and I think I have fixed it. In post #19 is a new link for download.

Regards,

Audioniek.

[Schaagi]

Hi Audioniek

Thank you for the update. Now it works. I will test the image and give you feedback.

Regards Schaagi

[Audioniek]

I have tried to reproduce your problem on the HS7429_USB. What I find strange is that uImage is read completely but that it does not start its built-in rcS:

Front USB:   scanning bus for devices... 3 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
  3727530   uimage -> the size is the same
 134217728   root.img -> size is the same

2 file(s), 0 dir(s)

reading uImage
................................................................................
................................................................................
................................................................................
................................................................................
............................................
ret=> 3727530

 --={ Load Enigma2 from USB }=--  -> I do not see this one in your log, this is the start of the built-in rcS

[init] Wait until /dev/sda exists
[init] ...found, mounting /dev/sda1 -> root.img is found
[init] Check root.img
enigma2: clean, 6030/32768 files, 124204/131072 blocks
[init] Mount root.img
[init] Start Enigma2
INIT: version 2.88 booting -> start of the rcS in the root.img
Fortis HS7429 Enigma2
[rcS] Init frontpanel
[rcS] WAIT 1 minute
[mountvirtfs] Mount /dev in tmpfs
[mountvirtfs] Copying device nodes to /dev
[rcS] Starting automounter
Starting automounter: /media/usb.
[rcS] Starting DEBUG Interface
[mountall] Mounting local filesystems...
mount: mounting LABEL=RECORD on /hdd failed: No such file or directory
Cleaning /tmp /var/run /var/lock.
Hostname: hs7429.
[rcS] Starting telnetd with autologin
[rcS] Init stmfb (LOAD 9)
[rcS] Loading modules
[rcS] Load audio firmware (LOAD 8)
[rcS] Load video firmware (LOAD 7)
[rcS] Init embx (LOAD 6)
[rcS] Init AVS (LOAD 5)
[rcS] Init player 191 (LOAD 4)
[rcS] Init frontend
[rcS] Init CI & cardreader
[rcS] Full feature pti
[rcS] Init player2 (LOAD 3)
[rcS] Init HDMI-CEC
[rcS] Init remote control (LOAD 2)
[evremote2] Model: 'hs7429'
[evremote2] vBoxType: 8 (hs7429)
[evremote2] Input device name: "TDT RC event driver"
[evremote2] Remote selected: Fortis RemoteControl
[evremote2] RemoteControl Map:
             Keyname  Keyword  KeyCode
--------------------------------------
                MENU  -  04  -  139
                 RED  -  4B  -  398
               GREEN  -  4A  -  399
              YELLOW  -  49  -  400
                BLUE  -  48  -  401
                EXIT  -  1C  -  102
                TEXT  -  0D  -  388
                 EPG  -  08  -  365
              REWIND  -  58  -  168
         FASTFORWARD  -  5C  -  208
                PLAY  -  55  -  207
               PAUSE  -  07  -  119
              RECORD  -  56  -  167
                STOP  -  54  -  128
             STANDBY  -  0A  -  116
                MUTE  -  0C  -  113
           CHANNELUP  -  5E  -  104
         CHANNELDOWN  -  5F  -  109
            VOLUMEUP  -  4E  -  115
          VOLUMEDOWN  -  4F  -  114
                INFO  -  06  -  358
                  OK  -  1F  -  352
                  UP  -  00  -  103
               RIGHT  -  02  -  106
                DOWN  -  01  -  108
                LEFT  -  03  -  105
              RECALL  -  09  -  138
                ZOOM  -  53  -  372
             VFORMAT  -  0E  -  371
          RESOLUTION  -  0F  -  375
             TVRADIO  -  1A  -  373
               SLEEP  -  1E  -  409
                OPEN  -  40  -  394
                 FAV  -  41  -  364
               CHECK  -  42  -  353
                UPUP  -  43  -  414
            DOWNDOWN  -  44  -  415
                NEXT  -  4C  -  407
                LAST  -  50  -  412
                 PIP  -  51  -  357
                SWAP  -  52  -  354
                LIST  -  0B  -  370
             0BUTTON  -  10  -   11
             1BUTTON  -  11  -    2
             2BUTTON  -  12  -    3
             3BUTTON  -  13  -    4
             4BUTTON  -  14  -    5
             5BUTTON  -  15  -    6
             6BUTTON  -  16  -    7
             7BUTTON  -  17  -    8
             8BUTTON  -  18  -    9
             9BUTTON  -  19  -   10
--------------------------------------
[evremote2] Frontpanel Map:
             Keyname  Keyword  KeyCode
--------------------------------------
             STANDBY  -  00  -  116
                  OK  -  06  -  352
                MENU  -  05  -  139
            VOLUMEUP  -  03  -  115
          VOLUMEDOWN  -  04  -  114
           CHANNELUP  -  01  -  104
         CHANNELDOWN  -  02  -  109
--------------------------------------
[evremote2] Supports Long KeyPress: yes
[evremote2 fortis] Period = 10, delay = 140
[evremote2] Using period = 10 delay = 140
[showiframe] showSinglePic /boot/bootlogo.mvi
[showiframe] VIDEO_SELECT_SOURCE MEMORY (Success)
[showiframe] VIDEO_PLAY (Success)
[showiframe] VIDEO_CONTINUE: (Success)
[showiframe] VIDEO_CLEAR_BUFFER: (Invalid argument)
Deconfiguring network interfaces... ifdown: interface lo not configured
ifdown: interface eth0 not configured
ifdown: interface eth1 not configured
ifdown: interface wlan0 not configured
done.
[rcS] Starting DHCP
Starting DHCP client: udhcpcudhcpc: started, v1.29.3
udhcpc: sending discover
udhcpc: sending select for 192.168.178.124
udhcpc: lease of 192.168.178.124 obtained, lease time 864000
route: SIOCDELRT: No such process
adding dns 192.168.178.1
.
Setting up IP spoofing protection: rp_filter.
Configuring network interfaces... udhcpc: started, v1.29.3
udhcpc: sending discover
udhcpc: sending select for 192.168.178.124
udhcpc: lease of 192.168.178.124 obtained, lease time 864000
route: SIOCDELRT: No such process
adding dns 192.168.178.1
ip: SIOCGIFFLAGS: No such device
ip: SIOCGIFFLAGS: No such device
done.
[rcS] Init WLAN: None.
[rcS] No inadyn
[rcS] No OpenSSH
[rcS] Set internet time
ntpd: setting time to 2019-02-16 13:54:37.260939 (offset +603636850.492527s)
Current system time: 13:54:37 16-02-2019 (local)
Front panel time set to: 13:54:37 16-02-2019 (local)
Note: /proc/stb/fp/rtc_offset set to: +3600 seconds.
[rcS] Init portmap & ftp (LOAD 1)
Starting portmap daemon....
Starting FTP server: vsftpd.
[rcS] Loading E2
[rcS] Entering e2 main loop
PYTHONPATH: /usr/lib/enigma2/python -> 1st enigma2 message
DVB_API_VERSION 5 DVB_API_VERSION_MINOR 3
ENIGMA_DEBUG_LVL=4
[Avahi] Not running yet, cannot browse for type _e2stream._tcp.
[eInit] + (1) Background File Eraser
[eInit] + (5) Tuxtxt
[eInit] + (8) graphics acceleration manager
STMFB accel interface available

[eInit] + (9) GFBDC

I have found that the USB stick is very, very critical with these bozes; I tried more than ten, only one would work. Maybe you should try another stick?

Regards,

Audioniek.

- - - Aktualisiert - - -

Hello spartak73,

On my testbox I have the same problem, even with the hard disk formatted in ext3. I assumed it was a particular problem of that box, but apparently it is generic. It is not the kernel-config, jfs is enabled because Fortis firmware formats in jfs by default and Fortis recordings are playable by E2:

#
# File systems
#
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
# CONFIG_EXT2_FS_POSIX_ACL is not set
# CONFIG_EXT2_FS_SECURITY is not set
# CONFIG_EXT2_FS_XIP is not set
CONFIG_EXT3_FS=y
# CONFIG_EXT3_DEFAULTS_TO_ORDERED is not set
CONFIG_EXT3_FS_XATTR=y
# CONFIG_EXT3_FS_POSIX_ACL is not set
# CONFIG_EXT3_FS_SECURITY is not set
CONFIG_EXT4_FS=y
CONFIG_EXT4_FS_XATTR=y
# CONFIG_EXT4_FS_POSIX_ACL is not set
# CONFIG_EXT4_FS_SECURITY is not set
# CONFIG_EXT4_DEBUG is not set
CONFIG_JBD=y
CONFIG_JBD2=y
CONFIG_FS_MBCACHE=y
# CONFIG_REISERFS_FS is not set
CONFIG_JFS_FS=y
# CONFIG_JFS_POSIX_ACL is not set
# CONFIG_JFS_SECURITY is not set
# CONFIG_JFS_DEBUG is not set
# CONFIG_JFS_STATISTICS is not set
CONFIG_FS_POSIX_ACL=y

Will investigate further.

Regards,

Audioniek.

[knaq]

The same on my Ufs912. I guess start routine from DuckBA (99% Used from Ufs912 User) is different to the old Maxiboot Tool. Hopefully Audioniek can provide patched .tar.gz Image which fits with the Multiboot DuckBA ( also implemented in MorlyTool)

Update to Ufs912 Flash Image - It works so far - nice to have a new E2 Image since long time ago

[spartak73]

Atevio 7500 USB. I have a problem with mounting the hard drive and usb flash drive. I have a hard drive in the jfs file system. With this file system on other images is mounted. I tried to write to the fstab file, but it does not help. The disk is visible but not mounted ...

[Audioniek]

Atevio 7500 USB. I have a hard drive in the jfs file system. With this file system on other images is mounted. I tried to write to the fstab file, but it does not help.

The kernel configuration is indeed OK. I am using this fstab now and it mounts a Fortis prepared jfs-formatted drive properly:

# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>                                       <dump>  <pass>
#/dev/root      /               auto    defaults,errors=remount-rw,noatime,nodiratime   0       0
proc            /proc           proc    defaults                                        0       0
tmpfs           /tmp            tmpfs   defaults                                        0       0
#
/dev/sda1       /hdd            auto    defaults,noatime,nodiratime                     0       0
#/dev/sda2      none            swap    sw
#/dev/sdb1      /hdd            auto    defaults,noatime,nodiratime                     0       0
#/dev/sdc1      /hdd            auto    defaults,noatime,nodiratime                     0       0
#/dev/sdd1      /hdd            auto    defaults,noatime,nodiratime                     0       0
LABEL=RECORD    /hdd            auto    defaults,errors=remount-ro,noatime,nodiratime   0       0
LABEL=SWAPPART  none            swap    sw

There are two mounts listed for /hdd. The idea is that mount -a processes them in order. Fortis does not label their partitions, so the attempt for /dev/sda1 should succeed in case of a Fortis jfs-formatted drive. The attempt for LABEL=RECORD will fail.
In the other case (LABEL=RECORD is present on /dev/sda1) This first mount will succeed, and second will remount (in this case) the same partition.

Another, more simple solution is label the jfs-partition RECORD.

Hope this works for you.

Regards,

Audioniek.