Debian 10 with kernel 3.8.13

[Jørgen Sirum]

Hi,

Trying to install old kernel 3.8.13 on the newest Debian 10 IOT image from beagleboard.org. (Want to have Python 3.7. But all my configuration of GPIO, UART (with RS485) is based on the old capemanager)

Used "sudo apt-get install linux-image-3.8.13-bone86" and then commented out the

"enable_uboot_overlays=1" in /boot/uEnv.txt and added the UUID of disk in same file.

But when rebooting it fails:

U-Boot 2019.04-00002-g07d5700e21 (Mar 06 2020 - 11:24:55 -0600), Build: jenkins-github_Bootloader-Builder-137

CPU  : AM335X-GP rev 2.1
I2C:   ready
DRAM:  512 MiB
No match for driver 'omap_hsmmc'
No match for driver 'omap_hsmmc'
Some drivers were not found
Reset Source: Power-on reset has occurred.
RTC 32KCLK Source: External.
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
Loading Environment from EXT4... Card did not respond to voltage select!
Board: BeagleBone Black
<ethaddr> not set. Validating first E-fuse MAC
BeagleBone Black:
Model: Element14 BeagleBone Black Industrial:
Timed out in wait_for_event: status=0000
Check if pads/pull-ups of bus are properly configured
BeagleBone: cape eeprom: i2c_probe: 0x54:
Timed out in wait_for_event: status=0000
Check if pads/pull-ups of bus are properly configured
BeagleBone: cape eeprom: i2c_probe: 0x55:
Timed out in wait_for_event: status=0000
Check if pads/pull-ups of bus are properly configured
BeagleBone: cape eeprom: i2c_probe: 0x56:
Timed out in wait_for_event: status=0000
Check if pads/pull-ups of bus are properly configured
BeagleBone: cape eeprom: i2c_probe: 0x57:
Net:   eth0: MII MODE
cpsw, usb_ether
Press SPACE to abort autoboot in 0 seconds
board_name=[A335BNLT] ...
board_rev=[EIA0] ...
Card did not respond to voltage select!
Card did not respond to voltage select!
Card did not respond to voltage select!
gpio: pin 56 (gpio 56) value is 0
gpio: pin 55 (gpio 55) value is 0
gpio: pin 54 (gpio 54) value is 0
gpio: pin 53 (gpio 53) value is 1
Card did not respond to voltage select!
Card did not respond to voltage select!
switch to partitions #0, OK
mmc1(part 0) is current device
Scanning mmc 1:1...
gpio: pin 56 (gpio 56) value is 0
gpio: pin 55 (gpio 55) value is 0
gpio: pin 54 (gpio 54) value is 0
gpio: pin 53 (gpio 53) value is 1
switch to partitions #0, OK
mmc1(part 0) is current device
gpio: pin 54 (gpio 54) value is 1
Checking for: /uEnv.txt ...
Checking for: /boot.scr ...
Checking for: /boot/boot.scr ...
Checking for: /boot/uEnv.txt ...
gpio: pin 55 (gpio 55) value is 1
2040 bytes read in 16 ms (124 KiB/s)
Loaded environment from /boot/uEnv.txt
Checking if uname_r is set in /boot/uEnv.txt...
gpio: pin 56 (gpio 56) value is 1
Running uname_boot ...
loading /boot/vmlinuz-3.8.13-bone86 ...
5600072 bytes read in 373 ms (14.3 MiB/s)
debug: [enable_uboot_overlays=] ...
loading /boot/dtbs/3.8.13-bone86/am335x-boneblack.dtb ...
26118 bytes read in 22 ms (1.1 MiB/s)
uboot_overlays: add [enable_uboot_overlays=1] to /boot/uEnv.txt to enable...
loading /boot/initrd.img-3.8.13-bone86 ...
5929307 bytes read in 395 ms (14.3 MiB/s)
debug: [console=ttyO0,115200n8 root=UUID=cf89a5ea-9bc4-4b40-acf9-2084d7c396be ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 lpj=1990656 rng_core.default_quality=100 quiet] ...
debug: [bootz 0x82000000 0x88080000:5a795b 0x88000000] ...
## Flattened Device Tree blob at 88000000
   Booting using the fdt blob at 0x88000000
   Loading Ramdisk to 8fa58000, end 8ffff95b ... OK
   Loading Device Tree to 8fa4e000, end 8fa57605 ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.549291] omap2_mbox_probe: platform not supported
[    0.703890] tps65217-bl tps65217-bl: failed to find backlight node
[    0.703981] tps65217-bl tps65217-bl: DT parse failed.
[    1.741053] omap_i2c 4819c000.i2c: controller timed out
[    2.752783] omap_i2c 4819c000.i2c: controller timed out
[    2.764472] bone-capemgr bone_capemgr.9: slot #0: No cape found
[    3.770344] omap_i2c 4819c000.i2c: controller timed out
[    4.782197] omap_i2c 4819c000.i2c: controller timed out
[    4.795720] bone-capemgr bone_capemgr.9: slot #1: No cape found
[    5.801593] omap_i2c 4819c000.i2c: controller timed out
[    6.813328] omap_i2c 4819c000.i2c: controller timed out
[    6.825015] bone-capemgr bone_capemgr.9: slot #2: No cape found
[    7.831013] omap_i2c 4819c000.i2c: controller timed out
[    8.842625] omap_i2c 4819c000.i2c: controller timed out
[    8.854313] bone-capemgr bone_capemgr.9: slot #3: No cape found
[    8.869901] bone-capemgr bone_capemgr.9: slot #6: BB-BONELT-HDMIN conflict P8.45 (#5:BB-BONELT-HDMI)
[    8.879889] bone-capemgr bone_capemgr.9: slot #6: Failed verification
[    8.886894] bone-capemgr bone_capemgr.9: loader: failed to load slot-6 BB-BONELT-HDMIN:00A0 (prio 2)
[    8.903673] omap_hsmmc mmc.5: of_parse_phandle_with_args of 'reset' failed
[    8.965901] pinctrl-single 44e10800.pinmux: pin 44e10854 already requested by 44e10800.pinmux; cannot claim for gpio-leds.8
[    8.978052] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status -22
[    8.985611] pinctrl-single 44e10800.pinmux: could not request pin 21 on device pinctrl-single
rootfs: clean, 88135/236176 files, 537660/943104 blocks
[   11.699389] EXT4-fs (mmcblk0p1): error loading journal
mount: Invalid argument
Failed to mount /dev/mmcblk0p1 as root file system.

Anybody knows how to fix this issue?

[Robert Nelson]

On Fri, Jan 15, 2021 at 11:40 AM Jørgen Sirum <jorgen...@gmail.com> wrote:
>
> Hi,
> Trying to install old kernel 3.8.13 on the newest Debian 10 IOT image from beagleboard.org. (Want to have Python 3.7. But all my configuration of GPIO, UART (with RS485) is based on the old capemanager)
> Used "sudo apt-get install linux-image-3.8.13-bone86" and then commented out the
> "enable_uboot_overlays=1" in /boot/uEnv.txt and added the UUID of disk in same file.

Oh I forget where 3.8.13 physically broke in Buster/Sid/etc..

This 'might' be a systemd 'feature' why it doesn't work (aka 3.8.13
too old..), but please disable "quiet" in /boot/uEnv.txt and retry
booting and let's see what it does..

Regards,

--
Robert Nelson
https://rcn-ee.com/

[Jørgen Sirum]

Hi,

New boot log

...
Loading, please wait...
Starting version 241
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems
done.
Begin: Will now check root file system ... fsck from util-linux 2.33.1
[/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1
rootfs: clean, 88128/236176 files, 537444/943104 blocks
done.
[    5.735837] JBD2: Unrecognised features on journal
[    5.741070] EXT4-fs (mmcblk0p1): error loading journal

mount: Invalid argument
Failed to mount /dev/mmcblk0p1 as root file system.

(initramfs)

Seems like features '64bit' , 'metadata_csum' and 'uninit_bg' has been added to filesystem compared to my old system

Booted from SD card and removed 64bit with 'resize2fs -s /dev/mmcblk1p1'. Removed the two others with 'tune2fs -O ^uninit_bg /dev/mmcblk1p1'

That did not help. So removed 'has_journal' and it booted!

But is it wise to remove 'has_journal' ?

And maybe I didnt need to remove the other stuff

br

Jørgen