Linux Kernel 6.8.7 Kirkwood upgrade, cannot login anymore into device

Quote

B. Load addresses for large systems
Set the env permanently to give another 16MB to load uInitrd (i.e. allow for initrd that is up to 27 MB in size).

Quote

fw_setenv load_dtb_addr 0x2c00000

Quote

rescue:~# uname -a
Linux rescue 3.3.2-kirkwide #1 Mon Oct 29 17:52:07 CDT 2012 armv5tel GNU/Linux

Quote

arcNumber=3542
bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; run bootcmd_rescue
bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load_initrd_addr; fi; else if run load_dtb; then bootm $load_uimage_addr - $load_dtb_addr; else bootm $load_uimage_addr; fi; fi
bootcmd_pogo=run bootcmd_rescue
bootcmd_rescue=run set_bootargs_rescue; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootdelay=10
bootdev=usb
device=0:1
devices=usb ide mmc
disks=0 1 2 3
dtb_file=/boot/dts/kirkwood-pogo_e02.dtb
ethact=egiga0
ethaddr=XXXXXXXXXXXXXXXXX
if_netconsole=ping $serverip
ipaddr=XXXXXXXXXXXXXXXXX
led_error=orange blinking
led_exit=green off
led_init=green blinking
load_dtb=echo loading DTB $dtb_file ...; load $bootdev $device $load_dtb_addr $dtb_file
load_dtb_addr=0x2c00000
load_initrd=echo loading uInitrd ...; load $bootdev $device $load_initrd_addr /boot/uInitrd
load_initrd_addr=0x1100000
load_uimage=echo loading uImage ...; load $bootdev $device $load_uimage_addr /boot/uImage
load_uimage_addr=0x800000
machid=dd6
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
partition=nand0,2
preboot=run preboot_nc
preboot_nc=setenv nc_ready 0; for pingstat in 1 2 3 4 5; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then run start_netconsole; fi
rescue_installed=1
scan_disk=echo running scan_disk ...; scan_done=0; setenv scan_usb "usb start"; setenv scan_ide "ide reset"; setenv scan_mmc "mmc rescan"; for dev in $devices; do if test $scan_done -eq 0; then echo Scan device $dev; run scan_$dev; for disknum in $disks; do if test $scan_done -eq 0; then echo device $dev $disknum:1; if load $dev $disknum:1 $load_uimage_addr /boot/uImage 1; then scan_done=1; echo Found bootable drive on $dev $disknum; setenv device $disknum:1; setenv bootdev $dev; fi; fi; done; fi; done
serverip=XXXXXXXXXXXXXXXXX
set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params
set_bootargs_rescue=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=serial
stdin=serial
stdout=serial
uenv_addr=0x810000
uenv_import=echo importing envs ...; env import -t $uenv_addr $filesize
uenv_init_devices=setenv init_usb "usb start"; setenv init_ide "ide reset"; setenv init_mmc "mmc rescan"; for devtype in $devices; do run init_$devtype; done;
uenv_load=run uenv_init_devices; setenv uenv_loaded 0; for devtype in $devices; do for disknum in 0; do run uenv_read_disk; done; done;
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; fi
uenv_read_disk=if test $devtype -eq mmc; then if $devtype part; then run uenv_read; fi; else if $devtype part $disknum; then run uenv_read; fi; fi
usb_ready_retry=15

Quote

\Netcat>nc -l -u -p 6666

U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:13:18 -0700)
Pogo E02
gcc (Debian 6.3.0-18) 6.3.0 20170516
GNU ld (GNU Binutils for Debian) 2.28
Hit any key to stop autoboot: 0
starting USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
scanning usb for storage devices...
Use USB retry period from the environment: 15 second(s)
1 Storage Device(s) found
Unknown command 'ide' - try 'help'
Unknown command 'mmc' - try 'help'

Partition Map for USB device 0 -- Partition Type: DOS

Part Start Sector Num Sectors UUID Type
1 2048 10235904 fcf2fcf2-01 07 Boot
2 10237952 4192965 fcf2fcf2-02 07
3 14432256 1985964032 fcf2fcf2-03 07

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0
loading envs from usb 0 ...
** File not found /boot/uEnv.txt **
Unknown command 'ide' - try 'help'
Unknown command 'mmc' - try 'help'
running scan_disk ...
Scan device usb
device usb 0:1
1 bytes read in 661 ms (0 Bytes/s)
Found bootable drive on usb 0
loading uImage ...
6179248 bytes read in 857 ms (6.9 MiB/s)
loading uInitrd ...
12102926 bytes read in 953 ms (12.1 MiB/s)
loading DTB /boot/dts/kirkwood-pogo_e02.dtb ...
10322 bytes read in 2076 ms (3.9 KiB/s)
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-6.8.7-kirkwood-tld-1
Created: 2024-05-04 16:29:08 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 6179184 Bytes = 5.9 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
Image Name: initramfs-6.8.7-kirkwood-tld-1
Created: 2024-05-04 16:29:13 UTC
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 12102862 Bytes = 11.5 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 02c00000
Booting using the fdt blob at 0x2c00000


Starting kernel ...

Quote

Netcat>nc -l -u -p 6666

U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:13:18 -0700)
Pogo E02

setenv load_dtb_addr 0x1c00000
setenv load_initrd_addr 0x2100000 
setenv load_uimage_addr 0x800000

boot

fw_printenv

fw_setenv load_dtb_addr '0x1c00000'
fw_setenv load_initrd_addr '0x2100000'
fw_setenv load_uimage_addr '0x800000'

Quote

Note 7. Ethernet Naming Issue (Optional):

In Debian 12.4, the ethernet "Predictable Names" scheme is enabled. So the ethernet device assigned is no longer "eth0", but is "end0". This "predictable naming" scheme broke a lot of existing applications that still relying on "eth0" is the network device name. It does not affect this Kirkwood rootfs (due to some setup I had in the past).

However, if after a future Debian upgrade of this rootfs, the network is no longer eth0, then this is the way to bring it back.

cat /etc/network/interfaces
rename /end0=eth0
auto lo eth0
iface lo inet loopback
iface eth0 inet dhcp
Beware of software apps, such as OMV, that do not respect users' configuration and so wiping out this change during its installation! I'd suggest to make a backup of this file, so you can compare that with any new /etc/network/interfaces after installing OMV, and restore the rename command.

There are also many other ways to force the eth0 name. However, it is more cumbersome to do than just watching out for this file being changed by OMV or other major apps installation. Also, other methods might not survive a future Debian upgrade :)

Quote

fw_setenv load_dtb_addr '0x1c00000'
fw_setenv load_initrd_addr '0x2100000'
fw_setenv load_uimage_addr '0x800000'

Quote

Updated 18 Apr 2024:

Kernel linux-6.8.7-kirkwood-tld-1 package has been uploaded. The following features were added/updated:

- General kernel upgrade.

./configure -disable-dbus  -enable-lowmem  -without-qt4 -sysconfdir=/etc

mkfs.ext4  -L rootfs -E lazy_itable_init=0  -O 64bit /dev/sdc1

# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# /dev/root      /               ext3    noatime,errors=remount-ro 0 1
tmpfs          /tmp            tmpfs   defaults          0       0

LABEL=rootfs    /               ext4    noatime,errors=remount-ro 0 1
/dev/sda3 /mnt/hdd ntfs-3g defaults,big_writes 0 0
/dev/sda2	 none	  swap	   defaults	  0 0

Quote

[ OK ] Mounted /tmp.
[ 34.952347][ T312] /dev/sda3: Can't open blockdev
[FAILED] Failed to mount /mnt/hdd.
See 'systemctl status mnt-hdd.mount' for details.
[DEPEND] Dependency failed for Local File Systems.
[ OK ] Stopped Dispatch Password …ts to Console Directory Watch.
[ OK ] Stopped Forward Password R…uests to Wall Directory Watch.
[ OK ] Reached target Timers.
Starting Raise network interfaces...
Starting Preprocess NFS configuration...
[ OK ] Reached target Login Prompts.
[ OK ] Reached target Sockets.
[ OK ] Started Emergency Shell.
[ OK ] Reached target Emergency Mode.
Starting Create Volatile Files and Directories...
[ OK ] Finished Preprocess NFS configuration.
Starting NFSv4 ID-name mapping service...
[ OK ] Reached target NFS client services.
[ OK ] Started NFSv4 ID-name mapping service.
[ OK ] Finished Create Volatile Files and Directories.
Starting RPC bind portmap service...
Starting Update UTMP about System Boot/Shutdown...
[ OK ] Started RPC bind portmap service.
[ OK ] Finished Update UTMP about System Boot/Shutdown.
[ OK ] Reached target RPC Port Mapper.
Starting Update UTMP about System Runlevel Changes...
[ OK ] Finished Update UTMP about System Runlevel Changes.
[ 39.509640][ C0] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control disabled
You are in emergency mode. After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" or "exit"
to boot into default mode.
Give root password for maintenance
(or press Control-D to continue): [ 44.460771][ T446] NFSD: Unable to initialize client recovery tracking! (-110)
[ 44.468149][ T446] NFSD: starting 90-second grace period (net f0000000)


[?2004hroot@pogo:~#  systemctl status mnt-hdd.mount
root@pogo:~# systemctl status mnt-hdd.mount
[?2004l
* mnt-hdd.mount - /mnt/hdd
Loaded: loaded (/etc/fstab; generated)
Active: failed (Result: exit-code) since Sun 2023-06-18 16:56:06 CEST; 56s ago
Where: /mnt/hdd
What: /dev/sda3
Docs: man:fstab(5)
man:systemd-fstab-generator(8)
CPU: 515ms

Jun 18 16:56:04 pogo systemd[1]: Mounting /mnt/hdd...
Jun 18 16:56:05 pogo mount[312]: ntfs-3g-mount: mount failed: Device or resource busy
Jun 18 16:56:06 pogo systemd[1]: mnt-hdd.mount: Mount process exited, code=exited, status=21/n/a
Jun 18 16:56:06 pogo systemd[1]: mnt-hdd.mount: Failed with result 'exit-code'.
Jun 18 16:56:06 pogo systemd[1]: 

Quote

[?2004l
Package: ntfs-3g
Version: 1:2017.3.23AR.3-4+deb11u3
Priority: optional
Section: otherosfs
Maintainer: Laszlo Boszormenyi (GCS) <gcs@debian.org>
Installed-Size: 1418 kB
Depends: libc6 (>= 2.17), libgcrypt20 (>= 1.8.0), libgnutls30 (>= 3.7.0), libntfs-3g883 (= 1:2017.3.23AR.3-4+deb11u3), fuse
Suggests: fdisk
Homepage: http://jp-andre.pagesperso-orange.fr/advanced-ntfs-3g.html
Tag: admin::filesystem, hardware::storage, implemented-in::c,
interface::commandline, interface::shell, role::program, scope::utility
Download-Size: 404 kB
APT-Manual-Installed: yes
APT-Sources: http://deb.debian.org/debian bullseye/main armel Packages
Description: read/write NTFS driver for FUSE
NTFS-3G uses FUSE (Filesystem in Userspace) to provide support for the NTFS
filesystem used by Microsoft Windows.

/dev/sda3 /mnt/hdd ntfs-3g defaults,big_writes 0 0

Windows has checked the file system and found no problems.

Quote

Jun 18 16:56:04
btw, not sure where this date/time from log is coming from (it is both wrong).

Quote

For test purposes commented ntfs line in
/etc/fstab

/dev/sda3 /mnt/hdd ntfs-3g defaults,big_writes 0 0

now system boots fine, debian 11.9, kernel 6.8.7, no "connection refused". via ssh.

root@pogo:~# ntfs-3g /dev/sda3 /mnt/hdd
ntfs-3g-mount: mount failed: Device or resource busy

mount -o noatime,big_writes /dev/sda3 /media/sda3

mount -L $disk_label -o noatime,big_writes /media/$disk_label

Quote

issues with auto-mount of ntfs filesystem using Kernel 6.8
The kernel changed default ntfs driver from FUSE one to ntfs3.
These two are not fully compatible, mainly as far as mount options go. If you have custom mount options in the fstab (or any other application, such as VeraCrypt) they need to be changed.

Symptoms:
Mount fails with: Device or resource busy
DMesg reports: Can't open blockdev

Solution:
Migrate your mount options. For me the changes were:

allow_other → umask=000
default_permissions → [drop]
user_id=1000 → uid=1000
group_id=1000 → gid=1000

Quote

And because Kernel 6.9 will completely remove ntfs-3g 2, it needs adjusting many things to adopt the new modifications.

Quote

Some more happy info
https://forum.manjaro.org/t/unable-to-mount-fat-or-ntfs-drives-after-updating/149354/46
Quote

And because Kernel 6.9 will completely remove ntfs-3g 2, it needs adjusting many things to adopt the new modifications.

# This file blacklists the kirkwood_thermal module on ZyXEL boxes with 6282 SoC

blacklist kirkwood_thermal

blacklist ntfs3