Mainline Debian on Iomega ix4-300d
Posted by Koen
|
Re: Mainline Debian on Iomega ix4-300d December 17, 2022 05:09PM |
Admin Registered: 13 years ago Posts: 18,542 |
RaumZeit,
> 1. I get random segmentation faults when I run
> `update-initramfs`. Only about one out of three
> attempts runs through without problems. Also
> sometimes I get `illegal instruction` reports when
> I update some software using `apt`. I really have
> no clue what is going on here, is there something
> wrong with the kernel config or maybe I have some
> faulty RAM blocks? Any help is appreciated.
Since you are running mainline Debian rootfs created by the installer, I'm not sure what's the problem. Sounds like you have a bad rootfs. Later, after you booted my released kernel 6.0.7, you might want to try the new rootfs Debian-5.13.8-mvebu-tld-1-rootfs-bodhi.tar.bz2 also.
> 2. I tried updating to kernel 6.0.7 using your
> (@bodhi) instructions taken from here:
> https://forum.doozan.com/read.php?2,32146
At serial console,
Please post the serial console log here.
I might ask for more follow up info later.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> 1. I get random segmentation faults when I run
> `update-initramfs`. Only about one out of three
> attempts runs through without problems. Also
> sometimes I get `illegal instruction` reports when
> I update some software using `apt`. I really have
> no clue what is going on here, is there something
> wrong with the kernel config or maybe I have some
> faulty RAM blocks? Any help is appreciated.
Since you are running mainline Debian rootfs created by the installer, I'm not sure what's the problem. Sounds like you have a bad rootfs. Later, after you booted my released kernel 6.0.7, you might want to try the new rootfs Debian-5.13.8-mvebu-tld-1-rootfs-bodhi.tar.bz2 also.
> 2. I tried updating to kernel 6.0.7 using your
> (@bodhi) instructions taken from here:
> https://forum.doozan.com/read.php?2,32146
Quote
data abort
pc : [<0117de7c>] lr : [<0117b83c>]
sp : 0167bb40 ip : 0000001c fp : 0167625c
r10: 0117a610 r9 : 0117b088 r8 : 01676260
r7 : 00000bdc r6 : 0167a750 r5 : 00000055 r4 : 0118117e
r3 : 00000bdc r2 : fed12000 r1 : f1012000 r0 : 00000055
Flags: nzCv IRQs off FIQs off Mode SVC_32
Resetting CPU ...
At serial console,
bdinfo map
Please post the serial console log here.
I might ask for more follow up info later.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Mainline Debian on Iomega ix4-300d December 18, 2022 04:33AM |
Registered: 1 year ago Posts: 4 |
bdinfo:
map:
arch_number = 0x00000BDC env_t = 0x00000000 boot_params = 0x00000100 DRAM bank = 0x00000000 -> start = 0x00000000 -> size = 0x20000000 DRAM bank = 0x00000001 -> start = 0x00000000 -> size = 0x00000000 DRAM bank = 0x00000002 -> start = 0x00000000 -> size = 0x00000000 DRAM bank = 0x00000003 -> start = 0x00000000 -> size = 0x00000000 ethaddr = 00:D0:B8:2A:3D:DF ip_addr = 192.168.1.2 baudrate = 115200 bps
map:
CPU Interface ------------- SDRAM_CS0 ....base 00000000, size 512MB SDRAM_CS1 ....disable SDRAM_CS2 ....disable SDRAM_CS3 ....disable DEVICE_CS0 ....no such DEVICE_CS1 ....no such DEVICE_CS2 ....no such DEVICE_CS3 ....no such PEX0_MEM ....base c0000000, size 64MB PEX0_IO ....base f1100000, size 1MB PEX1_MEM ....no such PEX1_IO ....no such PEX2_MEM ....base cc000000, size 64MB PEX2_IO ....no such PEX3_MEM ....base e0000000, size 64MB PEX3_IO ....no such PEX4_MEM ....base ca000000, size 32MB PEX4_IO ....no such PEX5_MEM ....no such PEX5_IO ....no such PEX6_MEM ....base e4000000, size 64MB PEX6_IO ....no such PEX7_MEM ....no such PEX7_IO ....no such PEX8_MEM ....base e8000000, size 64MB PEX8_IO ....no such PEX9_MEM ....base ec000000, size 64MB PEX9_IO ....no such INTER_REGS ....base d0000000, size 1MB DMA_UART ....no such SPI_CS0 ....base f4000000, size 8MB SPI_CS1 ....no such SPI_CS2 ....no such SPI_CS3 ....no such SPI_CS4 ....no such SPI_CS5 ....no such SPI_CS6 ....no such SPI_CS7 ....no such BOOT_ROM_CS ....base f8000000, size 1MB DEV_BOOTCS ....base fd000000, size 16MB PMU_SCRATCHPAD ....no such CRYPT1_ENG ....base c8010000, size 64KB CRYPT2_ENG ....no such PNC_BM ....no such AHB To MBUS Bridge: ------------------- win0 - PEX0_MEM base c0000000, ....size 64MB win1 - PEX0_IO base f1100000, ....size 1MB win2 - PEX2_MEM base cc000000, ....size 64MB win3 - PEX3_MEM base e0000000, ....size 64MB win4 - PEX4_MEM base ca000000, ....size 32MB win5 - PEX6_MEM base e4000000, ....size 64MB win6 - PEX8_MEM base e8000000, ....size 64MB win7 - PEX9_MEM base ec000000, ....size 64MB win8 - SPI_CS0 base f4000000, ....size 8MB win9 - DEV_BOOTCS base fd000000, ....size 16MB win10 - CRYPT1_ENG base c8010000, ....size 64KB win11 - disable win12 - disable win13 - BOOT_ROM_CS base f8000000, ....size 1MB win14 - disable win15 - disable win16 - disable win17 - disable win18 - disable win19 - disable win20 - INTER_REGS base d0000000, ....size 1MB PEX0: ----- Pex Bars Internal Regs Bar0.... base d0000000, size 1MB DRAM Bar1............. base 00000000, size 512MB Devices Bar2.......... disable Pex Decode Windows win0 - SDRAM_CS0 base 00000000, ....size 512MB win1 - disable win2 - disable win3 - disable win4 - disable win5 - disable default win - SDRAM_CS0 Expansion ROM - SDRAM_CS0 PEX4: ----- Pex Bars Internal Regs Bar0.... base d0000000, size 1MB DRAM Bar1............. base 00000000, size 512MB Devices Bar2.......... disable Pex Decode Windows win0 - SDRAM_CS0 base 00000000, ....size 512MB win1 - disable win2 - disable win3 - disable win4 - disable win5 - disable default win - SDRAM_CS0 Expansion ROM - SDRAM_CS0 USB 0: ---- win0 - SDRAM_CS0 base 00000000, ....size 512MB win1 - PEX0_MEM base c0000000, ....size 64MB win2 - disable win3 - disable win4 - mvUsbWinRead (dev=0): ERR. Invalid winNum 4 win5 - mvUsbWinRead (dev=0): ERR. Invalid winNum 5 win6 - mvUsbWinRead (dev=0): ERR. Invalid winNum 6 win7 - mvUsbWinRead (dev=0): ERR. Invalid winNum 7 win8 - mvUsbWinRead (dev=0): ERR. Invalid winNum 8 win9 - mvUsbWinRead (dev=0): ERR. Invalid winNum 9 win10 - mvUsbWinRead (dev=0): ERR. Invalid winNum 10 win11 - mvUsbWinRead (dev=0): ERR. Invalid winNum 11 win12 - mvUsbWinRead (dev=0): ERR. Invalid winNum 12 win13 - mvUsbWinRead (dev=0): ERR. Invalid winNum 13 win14 - mvUsbWinRead (dev=0): ERR. Invalid winNum 14 win15 - mvUsbWinRead (dev=0): ERR. Invalid winNum 15 USB 1: ---- win0 - SDRAM_CS0 base 00000000, ....size 512MB win1 - PEX0_MEM base c0000000, ....size 64MB win2 - disable win3 - disable win4 - mvUsbWinRead (dev=1): ERR. Invalid winNum 4 win5 - mvUsbWinRead (dev=1): ERR. Invalid winNum 5 win6 - mvUsbWinRead (dev=1): ERR. Invalid winNum 6 win7 - mvUsbWinRead (dev=1): ERR. Invalid winNum 7 win8 - mvUsbWinRead (dev=1): ERR. Invalid winNum 8 win9 - mvUsbWinRead (dev=1): ERR. Invalid winNum 9 win10 - mvUsbWinRead (dev=1): ERR. Invalid winNum 10 win11 - mvUsbWinRead (dev=1): ERR. Invalid winNum 11 win12 - mvUsbWinRead (dev=1): ERR. Invalid winNum 12 win13 - mvUsbWinRead (dev=1): ERR. Invalid winNum 13 win14 - mvUsbWinRead (dev=1): ERR. Invalid winNum 14 win15 - mvUsbWinRead (dev=1): ERR. Invalid winNum 15 USB 2: ---- win0 - SDRAM_CS0 base 00000000, ....size 512MB win1 - PEX0_MEM base c0000000, ....size 64MB win2 - disable win3 - disable win4 - mvUsbWinRead (dev=2): ERR. Invalid winNum 4 win5 - mvUsbWinRead (dev=2): ERR. Invalid winNum 5 win6 - mvUsbWinRead (dev=2): ERR. Invalid winNum 6 win7 - mvUsbWinRead (dev=2): ERR. Invalid winNum 7 win8 - mvUsbWinRead (dev=2): ERR. Invalid winNum 8 win9 - mvUsbWinRead (dev=2): ERR. Invalid winNum 9 win10 - mvUsbWinRead (dev=2): ERR. Invalid winNum 10 win11 - mvUsbWinRead (dev=2): ERR. Invalid winNum 11 win12 - mvUsbWinRead (dev=2): ERR. Invalid winNum 12 win13 - mvUsbWinRead (dev=2): ERR. Invalid winNum 13 win14 - mvUsbWinRead (dev=2): ERR. Invalid winNum 14 win15 - mvUsbWinRead (dev=2): ERR. Invalid winNum 15 ETH 0: ---- win0 - SDRAM_CS0 base 00000000, ....size 512MB win1 - disable win2 - disable win3 - disable win4 - disable win5 - disable win6 - mvNetaWinGet: ERR. Invalid winNum 6 win7 - mvNetaWinGet: ERR. Invalid winNum 7 win8 - mvNetaWinGet: ERR. Invalid winNum 8 win9 - mvNetaWinGet: ERR. Invalid winNum 9 win10 - mvNetaWinGet: ERR. Invalid winNum 10 win11 - mvNetaWinGet: ERR. Invalid winNum 11 win12 - mvNetaWinGet: ERR. Invalid winNum 12 win13 - mvNetaWinGet: ERR. Invalid winNum 13 win14 - mvNetaWinGet: ERR. Invalid winNum 14 win15 - mvNetaWinGet: ERR. Invalid winNum 15 ETH 1: ---- win0 - SDRAM_CS0 base 00000000, ....size 512MB win1 - disable win2 - disable win3 - disable win4 - disable win5 - disable win6 - mvNetaWinGet: ERR. Invalid winNum 6 win7 - mvNetaWinGet: ERR. Invalid winNum 7 win8 - mvNetaWinGet: ERR. Invalid winNum 8 win9 - mvNetaWinGet: ERR. Invalid winNum 9 win10 - mvNetaWinGet: ERR. Invalid winNum 10 win11 - mvNetaWinGet: ERR. Invalid winNum 11 win12 - mvNetaWinGet: ERR. Invalid winNum 12 win13 - mvNetaWinGet: ERR. Invalid winNum 13 win14 - mvNetaWinGet: ERR. Invalid winNum 14 win15 - mvNetaWinGet: ERR. Invalid winNum 15 XOR 0: ---- win0 - PEX0_MEM base c0000000, ....size 64MB win1 - PEX2_MEM base cc000000, ....size 64MB win2 - PEX3_MEM base e0000000, ....size 64MB win3 - PEX8_MEM base e8000000, ....size 64MB win4 - PEX9_MEM base ec000000, ....size 64MB win5 - SDRAM_CS0 base 00000000, ....size 512MB win6 - disable win7 - disable win8 - win9 - win10 - win11 - win12 - win13 - win14 - win15 - XOR 1: ---- win0 - PEX0_MEM base c0000000, ....size 64MB win1 - PEX2_MEM base cc000000, ....size 64MB win2 - PEX3_MEM base e0000000, ....size 64MB win3 - PEX8_MEM base e8000000, ....size 64MB win4 - PEX9_MEM base ec000000, ....size 64MB win5 - SDRAM_CS0 base 00000000, ....size 512MB win6 - disable win7 - disable win8 - win9 - win10 - win11 - win12 - win13 - win14 - win15 - XOR 2: ---- win0 - PEX0_MEM base c0000000, ....size 64MB win1 - PEX2_MEM base cc000000, ....size 64MB win2 - PEX3_MEM base e0000000, ....size 64MB win3 - PEX8_MEM base e8000000, ....size 64MB win4 - PEX9_MEM base ec000000, ....size 64MB win5 - SDRAM_CS0 base 00000000, ....size 512MB win6 - disable win7 - disable win8 - win9 - win10 - win11 - win12 - win13 - win14 - win15 - XOR 3: ---- win0 - PEX0_MEM base c0000000, ....size 64MB win1 - PEX2_MEM base cc000000, ....size 64MB win2 - PEX3_MEM base e0000000, ....size 64MB win3 - PEX8_MEM base e8000000, ....size 64MB win4 - PEX9_MEM base ec000000, ....size 64MB win5 - SDRAM_CS0 base 00000000, ....size 512MB win6 - disable win7 - disable win8 - win9 - win10 - win11 - win12 - win13 - win14 - win15 - Sata 0: ---- win0 - SDRAM_CS0 base 00000000, ....size 256MB win1 - SDRAM_CS1 base 10000000, ....size 256MB win2 - SDRAM_CS2 base 20000000, ....size 256MB win3 - SDRAM_CS3 base 30000000, ....size 256MB win4 - mvSataWinRead (dev=0): ERR. Invalid winNum 4 win5 - mvSataWinRead (dev=0): ERR. Invalid winNum 5 win6 - mvSataWinRead (dev=0): ERR. Invalid winNum 6 win7 - mvSataWinRead (dev=0): ERR. Invalid winNum 7 win8 - mvSataWinRead (dev=0): ERR. Invalid winNum 8 win9 - mvSataWinRead (dev=0): ERR. Invalid winNum 9 win10 - mvSataWinRead (dev=0): ERR. Invalid winNum 10 win11 - mvSataWinRead (dev=0): ERR. Invalid winNum 11 win12 - mvSataWinRead (dev=0): ERR. Invalid winNum 12 win13 - mvSataWinRead (dev=0): ERR. Invalid winNum 13 win14 - mvSataWinRead (dev=0): ERR. Invalid winNum 14 win15 - mvSataWinRead (dev=0): ERR. Invalid winNum 15 Sata 1: ---- win0 - SDRAM_CS0 base 00000000, ....size 256MB win1 - SDRAM_CS1 base 10000000, ....size 256MB win2 - SDRAM_CS2 base 20000000, ....size 256MB win3 - SDRAM_CS3 base 30000000, ....size 256MB win4 - mvSataWinRead (dev=1): ERR. Invalid winNum 4 win5 - mvSataWinRead (dev=1): ERR. Invalid winNum 5 win6 - mvSataWinRead (dev=1): ERR. Invalid winNum 6 win7 - mvSataWinRead (dev=1): ERR. Invalid winNum 7 win8 - mvSataWinRead (dev=1): ERR. Invalid winNum 8 win9 - mvSataWinRead (dev=1): ERR. Invalid winNum 9 win10 - mvSataWinRead (dev=1): ERR. Invalid winNum 10 win11 - mvSataWinRead (dev=1): ERR. Invalid winNum 11 win12 - mvSataWinRead (dev=1): ERR. Invalid winNum 12 win13 - mvSataWinRead (dev=1): ERR. Invalid winNum 13 win14 - mvSataWinRead (dev=1): ERR. Invalid winNum 14 win15 - mvSataWinRead (dev=1): ERR. Invalid winNum 15
|
Re: Mainline Debian on Iomega ix4-300d December 18, 2022 04:38PM |
Admin Registered: 13 years ago Posts: 18,542 |
RaumZeit,
The info looks good. There should be no address conflict in booting.
But since you are booting with stock u-boot, and it's quite old and sensitive to load addresses. Try booting at the same addresses that Koen used.
If that still has problem, then adjust the uImage and uInitrd addresses as followed:
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
The info looks good. There should be no address conflict in booting.
But since you are booting with stock u-boot, and it's quite old and sensitive to load addresses. Try booting at the same addresses that Koen used.
setenv bootdebian "printenv; ide reset; ext2load ide 2:1 0x40000 uImage; ext2load ide 2:1 0x2000000 uInitrd; setenv bootargs $console $mtdparts root=LABEL=rootfs rw rootdelay=10; bootm 0x40000 0x2000000"
If that still has problem, then adjust the uImage and uInitrd addresses as followed:
uImage load and boot address: 0x800000 uInitrd load and boot address: 0x2100000
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Mainline Debian on Iomega ix4-300d December 19, 2022 02:12PM |
Registered: 5 years ago Posts: 180 |
Hi RaumZeit,
everything looked OK after the install but I did get similar error messages when installing software using apt after a while. I often had to run apt a few times before it would succeed. I'm not sure what caused it but it made me a bit worried about the data on the nas so I've moved the drives to another nas for now. I've not used the ix4 300d since but can boot it up to provide a dmesg log if anybody is interested to have a look.
Koen
everything looked OK after the install but I did get similar error messages when installing software using apt after a while. I often had to run apt a few times before it would succeed. I'm not sure what caused it but it made me a bit worried about the data on the nas so I've moved the drives to another nas for now. I've not used the ix4 300d since but can boot it up to provide a dmesg log if anybody is interested to have a look.
Koen
|
Re: Mainline Debian on Iomega ix4-300d December 21, 2022 03:16AM |
Registered: 1 year ago Posts: 4 |
|
Re: Mainline Debian on Iomega ix4-300d December 21, 2022 03:20AM |
Registered: 1 year ago Posts: 4 |
Thanks for getting back to me, Koen!
the bad news that you also experience these issues is somehow good news to me. Maybe it's really just a kernel config problem. I also sometimes suspect that the box runs out of memory quickly. Anyhow, I think no further dmesg output is required at this stage. I'll see how things develop with Bodhis new 6.0.7 kernel, if I get it running.
Btw., apart from the segmentation faults during install of software it is running stable so far. I use it as NFS server and have a software raid running. No further problems so far. But its only running for a few days now.
Best,
RaumZeit
the bad news that you also experience these issues is somehow good news to me. Maybe it's really just a kernel config problem. I also sometimes suspect that the box runs out of memory quickly. Anyhow, I think no further dmesg output is required at this stage. I'll see how things develop with Bodhis new 6.0.7 kernel, if I get it running.
Btw., apart from the segmentation faults during install of software it is running stable so far. I use it as NFS server and have a software raid running. No further problems so far. But its only running for a few days now.
Best,
RaumZeit
|
bramm
Re: Mainline Debian on Iomega ix4-300d January 31, 2023 04:49AM |
|
Re: Mainline Debian on Iomega ix4-300d February 28, 2023 06:32PM |
Registered: 1 year ago Posts: 2 |
I'm trying to fix the bootloader on my IX4-300D. I accidentally ran
I able able to get back into U-Boot using kwboot:
From the U-Boot console, I was able to restore the NAND partitions (except rootfs, because it's so large) by transferring them with TFTP and writing them with 'nand write'. However, the system still will not boot on its own. The serial console outputs the following:
Does anyone know how to restore the bootloader on this device?
nand erasefrom the U-Boot console, without any parameters, which erases the whole flash. Fortunately, I had backed up the MTD partitions from Linux using dd.
I able able to get back into U-Boot using kwboot:
kwboot -t -B 115200 /dev/ttyUSB0 -b mtd0ro -pFrom here, I can load Linux over TFTP and boot and it works fine.
From the U-Boot console, I was able to restore the NAND partitions (except rootfs, because it's so large) by transferring them with TFTP and writing them with 'nand write'. However, the system still will not boot on its own. The serial console outputs the following:
BootROM 1.15 Booting from NAND flash DDR3 Training Sequence - Ver 2.3.4 DDR3 Training Sequence - Ended Successfully BootROM: Image checksum verification FAILED BootROM: Bad header at offset 00020000 BootROM: Bad header at offset 00040000 BootROM: Bad header at offset 00060000 BootROM: Bad header at offset 00080000 [...] BootROM: Bad header at offset 03FE0000
Does anyone know how to restore the bootloader on this device?
|
Re: Mainline Debian on Iomega ix4-300d February 28, 2023 09:08PM |
Admin Registered: 13 years ago Posts: 18,542 |
Perhaps Koen will come around and help.
In the mean time, did you use command similar to this to back up mtd0 to the file mtd0ro?
What is the size of mtd0ro?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
In the mean time, did you use command similar to this to back up mtd0 to the file mtd0ro?
nanddump --noecc --omitoob -f mtd0 /dev/mtd0
What is the size of mtd0ro?
ls -l mtd0ro ls -lh mtd0roIs this 896K?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Mainline Debian on Iomega ix4-300d February 28, 2023 09:12PM |
Admin Registered: 13 years ago Posts: 18,542 |
Also see if you can use Koen's mtds backup in this post.
https://forum.doozan.com/read.php?2,131833,133002#msg-133002
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
https://forum.doozan.com/read.php?2,131833,133002#msg-133002
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Mainline Debian on Iomega ix4-300d February 28, 2023 10:36PM |
Registered: 1 year ago Posts: 2 |
I used dd.Quote
bodhi
In the mean time, did you use command similar to this to back up mtd0 to the file mtd0ro?
Yup, it's 917504 bytes.Quote
bodhi
Is this 896K?
That fixed it! Booting now without kwboot. My mtd0 backup must've been corrupted somehow, but it still worked well enough for kwboot. Weird.Quote
bodhi
Also see if you can use Koen's mtds backup in this post.
Thanks!
|
Re: Mainline Debian on Iomega ix4-300d February 28, 2023 10:50PM |
Admin Registered: 13 years ago Posts: 18,542 |
> That fixed it! Booting now without kwboot. My mtd0
> backup must've been corrupted somehow, but it
> still worked well enough for kwboot. Weird.
Cool!
BTW, dd is not recommended for something like this. nanddump is the right tool.
kwboot actually fix th eheader up before sending, and the BootROM only cares to see the UART byte in the header.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 02/28/2023 10:53PM by bodhi.
> backup must've been corrupted somehow, but it
> still worked well enough for kwboot. Weird.
Cool!
BTW, dd is not recommended for something like this. nanddump is the right tool.
kwboot actually fix th eheader up before sending, and the BootROM only cares to see the UART byte in the header.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 02/28/2023 10:53PM by bodhi.
|
Rom
Re: Mainline Debian on Iomega ix4-300d May 13, 2023 07:37AM |
Hey,
Trying to install any firmware on the IX-300D using the usb port but it always shows "TFTP and USB boot fail".
I don't have Linux and when I tried to combine the image files using CMD as described in the README file in one of the links it didn't find the specified file or didn't recognize it as a command.
Is there a simple way I can get the Nas running with a formatted HDD?
Thanks
Trying to install any firmware on the IX-300D using the usb port but it always shows "TFTP and USB boot fail".
I don't have Linux and when I tried to combine the image files using CMD as described in the README file in one of the links it didn't find the specified file or didn't recognize it as a command.
Is there a simple way I can get the Nas running with a formatted HDD?
Thanks
|
Re: Mainline Debian on Iomega ix4-300d May 13, 2023 02:57PM |
Admin Registered: 13 years ago Posts: 18,542 |
Rom,
You need another Linux box and connect serial console.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
You need another Linux box and connect serial console.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
alf45tar
Re: Mainline Debian on Iomega ix4-300d August 25, 2023 11:13AM |
Thanks for the very helpful information you provided to the community.
I am preparing a step-by-step tutorial to revamp a Lenovo Iomega ix4-300d NAS installing the last version of Debian and potentially any recent software.
Is it not yet finished but the working in progress is available here https://github.com/alf45tar/ix4-300d.
Regards
ald45tar
I am preparing a step-by-step tutorial to revamp a Lenovo Iomega ix4-300d NAS installing the last version of Debian and potentially any recent software.
Is it not yet finished but the working in progress is available here https://github.com/alf45tar/ix4-300d.
Regards
ald45tar
|
Re: Mainline Debian on Iomega ix4-300d August 25, 2023 01:01PM |
Admin Registered: 13 years ago Posts: 18,542 |
ald45tar,
Thanks for sharing!
I took a quick look. Great info! please let us know when you're done so I can add to the Wiki thread here.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Thanks for sharing!
Quote
Is it not yet finished but the working in progress is available here https://github.com/alf45tar/ix4-300d.
I took a quick look. Great info! please let us know when you're done so I can add to the Wiki thread here.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Mainline Debian on Iomega ix4-300d August 28, 2023 02:50PM |
Registered: 5 years ago Posts: 252 |
alf45tar,
Great work! I may need to dust off my ix4-200d and see if I can adapt some of it to work with that device.
Could you post the dmesg output from this device on the 6.1 kernel? I'm curious to compare how the PCIe initialization looks compared to one of my devices.
I ran into a rather nasty issue affecting the PCIe SATA on the Buffalo TS3400D which I believe uses the same SoC and is generally very similar. It turned out that in uboot somewhere the PCI-ID for the port was being overwritten with the SoC ID which became a problem when the Linux Kernel actually started validating that ID starting with 5.18 or so.
If you didn't run into that issue that likely proves it was a buffalo issue rather than something with Marvell or their SDK.... it's always something.
Is the u-boot source for this device available? It might help me fill in some gaps left by Buffalo not publishing theirs.
Great work! I may need to dust off my ix4-200d and see if I can adapt some of it to work with that device.
Could you post the dmesg output from this device on the 6.1 kernel? I'm curious to compare how the PCIe initialization looks compared to one of my devices.
I ran into a rather nasty issue affecting the PCIe SATA on the Buffalo TS3400D which I believe uses the same SoC and is generally very similar. It turned out that in uboot somewhere the PCI-ID for the port was being overwritten with the SoC ID which became a problem when the Linux Kernel actually started validating that ID starting with 5.18 or so.
If you didn't run into that issue that likely proves it was a buffalo issue rather than something with Marvell or their SDK.... it's always something.
Is the u-boot source for this device available? It might help me fill in some gaps left by Buffalo not publishing theirs.
|
Re: Mainline Debian on Iomega ix4-300d August 28, 2023 04:05PM |
Admin Registered: 13 years ago Posts: 18,542 |
1000001101000,
> I ran into a rather nasty issue affecting the PCIe
> SATA on the Buffalo TS3400D which I believe uses
> the same SoC and is generally very similar. It
> turned out that in uboot somewhere the PCI-ID for
> the port was being overwritten with the SoC ID
> which became a problem when the Linux Kernel
> actually started validating that ID starting with
> 5.18 or so.
I don't know what this stock u-boot might do. But usually thing happens the other way around: U-Boot reads the SoC ID from the PCIe. That's how it has been for a long time in mainline u-boot. There were also recent works to clean up that code.
> If you didn't run into that issue that likely
> proves it was a buffalo issue rather than
> something with Marvell or their SDK.... it's
> always something.
Could be just the Buffalo issue, I have not come across any other Armada SoC-based NAS that has this problem in the kernel 5.18+.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> I ran into a rather nasty issue affecting the PCIe
> SATA on the Buffalo TS3400D which I believe uses
> the same SoC and is generally very similar. It
> turned out that in uboot somewhere the PCI-ID for
> the port was being overwritten with the SoC ID
> which became a problem when the Linux Kernel
> actually started validating that ID starting with
> 5.18 or so.
I don't know what this stock u-boot might do. But usually thing happens the other way around: U-Boot reads the SoC ID from the PCIe. That's how it has been for a long time in mainline u-boot. There were also recent works to clean up that code.
> If you didn't run into that issue that likely
> proves it was a buffalo issue rather than
> something with Marvell or their SDK.... it's
> always something.
Could be just the Buffalo issue, I have not come across any other Armada SoC-based NAS that has this problem in the kernel 5.18+.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Mainline Debian on Iomega ix4-300d August 29, 2023 02:09PM |
Registered: 5 years ago Posts: 252 |
I seem to be missing some of the details in my notes but they were re-writing the PCI id from 11ab:7846 which matches the functional spec to something like 0001:7823 presumably either but accident or to help them separate the mv78230 and mv7840 which set that value the same. It went unnoticed for a long time since the kernel never used to do anything with that value for the mvebu pci driver until recently.
it's always something.
it's always something.
|
Re: Mainline Debian on Iomega ix4-300d August 29, 2023 03:18PM |
Admin Registered: 13 years ago Posts: 18,542 |
> I seem to be missing some of the details in my
> notes but they were re-writing the PCI id from
> 11ab:7846 which matches the functional spec to
> something like 0001:7823 presumably either but
> accident or to help them separate the mv78230 and
> mv7840 which set that value the same.
> It went
> unnoticed for a long time since the kernel never
> used to do anything with that value for the mvebu
> pci driver until recently.
>
> it's always something.
I think you're refering to this commit:
https://github.com/torvalds/linux/commit/e3e13c9135da969cfe1666a9f24e76b589d5652b
So currently in kernel 6.4.11, lspci will give 11ab:
This problem could be solved in u-boot. IIRC, to populate that to correct value before booting the kernel, we might be able to poke the location with a memory write (mw command).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> notes but they were re-writing the PCI id from
> 11ab:7846 which matches the functional spec to
> something like 0001:7823 presumably either but
> accident or to help them separate the mv78230 and
> mv7840 which set that value the same.
> It went
> unnoticed for a long time since the kernel never
> used to do anything with that value for the mvebu
> pci driver until recently.
>
> it's always something.
I think you're refering to this commit:
https://github.com/torvalds/linux/commit/e3e13c9135da969cfe1666a9f24e76b589d5652b
So currently in kernel 6.4.11, lspci will give 11ab:
root@tldDebian6:~# lspci -v 00:01.0 PCI bridge: Marvell Technology Group Ltd. Device 6282 (rev 01) (prog-if 00 [Normal decode]) Subsystem: Marvell Technology Group Ltd. Device 11ab Device tree node: /sys/firmware/devicetree/base/mbus@f1000000/pcie@82000000/pcie@1,0 Flags: fast devsel Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: [disabled] [32-bit] Memory behind bridge: [disabled] [32-bit] Capabilities: [40] Subsystem: Marvell Technology Group Ltd. Device 11ab Capabilities: [60] Express Root Port (Slot+), MSI 00 Capabilities: [100] Advanced Error ReportingAs it should be.
This problem could be solved in u-boot. IIRC, to populate that to correct value before booting the kernel, we might be able to poke the location with a memory write (mw command).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Mainline Debian on Iomega ix4-300d August 30, 2023 08:59AM |
Registered: 5 years ago Posts: 252 |
That's the one! It look me an embarrassingly log time to narrow that down for various reasons.Quote
I think you're referring to this commit:
https://github.com/torvalds/linux/commit/e3e13c9135da969cfe1666a9f24e76b589d5652b
Quote
This problem could be solved in u-boot. IIRC, to populate that to correct value before booting the kernel, we might be able to poke the location with a memory write (mw command).
For the Buffalo stuff I've started using a small second stage "shim" after u-boot to handle relocating the initrd when needed and to make this type of tweak before the kernel starts. This lets me continue to avoid messing with the stock u-boot since a lot of these devices don't have an accessible serial console or u-boot source.
Sorry for hijacking the thread!
|
alf45tar
Re: Mainline Debian on Iomega ix4-300d September 08, 2023 11:15AM |
|
Re: Mainline Debian on Iomega ix4-300d September 08, 2023 01:35PM |
Admin Registered: 13 years ago Posts: 18,542 |
alf45tar,
Looks like it should work (all the ingredients are there in mainline kernel). Have you checked your dmesg? Please post
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Looks like it should work (all the ingredients are there in mainline kernel). Have you checked your dmesg? Please post
dmesg
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
alf45tar
Re: Mainline Debian on Iomega ix4-300d September 08, 2023 04:42PM |
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 6.1.0-11-armmp-lpae (debian-kernel@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP Debian 6.1.38-4 (2023-08-08)
[ 0.000000] CPU: ARMv7 Processor [562f5842] revision 2 (ARMv7), cr=30c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
[ 0.000000] OF: fdt: Machine model: Lenovo Iomega ix4-300d
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] efi: UEFI not found.
[ 0.000000] cma: Reserved 16 MiB at 0x000000001f000000
[ 0.000000] Zone ranges:
[ 0.000000] DMA [mem 0x0000000000000000-0x000000001fffffff]
[ 0.000000] Normal empty
[ 0.000000] HighMem empty
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x0000000000000000-0x000000001fffffff]
[ 0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x000000001fffffff]
[ 0.000000] percpu: Embedded 18 pages/cpu s41684 r8192 d23852 u73728
[ 0.000000] pcpu-alloc: s41684 r8192 d23852 u73728 alloc=18*4096
[ 0.000000] pcpu-alloc: [0] 0 [0] 1
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 129920
[ 0.000000] Kernel command line: console=ttyS0,115200 mtdparts=armada-nand:0xe0000@0x0(uboot),0x20000@0xe0000(env),0x20000@0x100000(env2),0x400000@0x120000(zImage),0x400000@0x520000(initrd),0x3F200000@0xE00000(boot),0x40000000@0x0(flash) root=LABEL=rootfs rw rootdelay=5
[ 0.000000] Unknown kernel command line parameters "mtdparts=armada-nand:0xe0000@0x0(uboot),0x20000@0xe0000(env),0x20000@0x100000(env2),0x400000@0x120000(zImage),0x400000@0x520000(initrd),0x3F200000@0xE00000(boot),0x40000000@0x0(flash)", will be passed to user space.
[ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes, linear)
[ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes, linear)
[ 0.000000] mem auto-init: stack:all(zero), heap alloc:on, heap free:off
[ 0.000000] Memory: 457788K/524288K available (12288K kernel code, 1710K rwdata, 3588K rodata, 2048K init, 384K bss, 50116K reserved, 16384K cma-reserved, 0K highmem)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[ 0.000000] ftrace: allocating 39699 entries in 117 pages
[ 0.000000] ftrace: allocated 117 pages with 5 groups
[ 0.000000] trace event string verifier disabled
[ 0.000000] rcu: Hierarchical RCU implementation.
[ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=2.
[ 0.000000] Rude variant of Tasks RCU enabled.
[ 0.000000] Tracing variant of Tasks RCU enabled.
[ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
[ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[ 0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[ 0.000000] L2C: DT/platform modifies aux control register: 0x1a696b10 -> 0x1a696b12
[ 0.000000] Aurora cache controller enabled, 16 ways, 1024 kB
[ 0.000000] Aurora: CACHE_ID 0x00000100, AUX_CTRL 0x1a696b12
[ 0.000000] rcu: srcu_init: Setting srcu_struct sizes based on contention.
[ 0.000000] Switching to timer-based delay loop, resolution 40ns
[ 0.000001] sched_clock: 32 bits at 25MHz, resolution 40ns, wraps every 85899345900ns
[ 0.000012] clocksource: armada_370_xp_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 76450417870 ns
[ 0.001180] Console: colour dummy device 80x30
[ 0.001217] Calibrating delay loop (skipped), value calculated using timer frequency.. 50.00 BogoMIPS (lpj=100000)
[ 0.001230] CPU: Testing write buffer coherency: ok
[ 0.001265] pid_max: default: 32768 minimum: 301
[ 0.001626] LSM: Security Framework initializing
[ 0.001733] landlock: Up and running.
[ 0.001736] Yama: disabled by default; enable with sysctl kernel.yama.*
[ 0.001911] AppArmor: AppArmor initialized
[ 0.001920] TOMOYO Linux initialized
[ 0.001947] LSM support for eBPF active
[ 0.002146] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[ 0.002158] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[ 0.003483] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.004436] cblist_init_generic: Setting adjustable number of callback queues.
[ 0.004444] cblist_init_generic: Setting shift to 1 and lim to 1.
[ 0.004549] cblist_init_generic: Setting shift to 1 and lim to 1.
[ 0.004695] Setting up static identity map for 0x400000 - 0x4000ac
[ 0.004995] mvebu-soc-id: MVEBU SoC ID=0x7823, Rev=0x1
[ 0.005082] mvebu-pmsu: Initializing Power Management Service Unit
[ 0.005246] rcu: Hierarchical SRCU implementation.
[ 0.005250] rcu: Max phase no-delay instances is 1000.
[ 0.006577] EFI services will not be available.
[ 0.006906] smp: Bringing up secondary CPUs ...
[ 0.007507] Booting CPU 1
[ 0.007745] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[ 0.011813] smp: Brought up 1 node, 2 CPUs
[ 0.011822] SMP: Total of 2 processors activated (100.00 BogoMIPS).
[ 0.011829] CPU: All CPU(s) started in SVC mode.
[ 0.012557] devtmpfs: initialized
[ 0.016672] VFP support v0.3: implementor 56 architecture 2 part 20 variant 9 rev 6
[ 0.016904] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[ 0.016931] futex hash table entries: 512 (order: 3, 32768 bytes, linear)
[ 0.017931] pinctrl core: initialized pinctrl subsystem
[ 0.018632] DMI not present or invalid.
[ 0.019222] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[ 0.020720] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.021417] audit: initializing netlink subsys (disabled)
[ 0.021680] audit: type=2000 audit(0.020:1): state=initialized audit_enabled=0 res=1
[ 0.022554] thermal_sys: Registered thermal governor 'fair_share'
[ 0.022561] thermal_sys: Registered thermal governor 'bang_bang'
[ 0.022566] thermal_sys: Registered thermal governor 'step_wise'
[ 0.022570] thermal_sys: Registered thermal governor 'user_space'
[ 0.022573] thermal_sys: Registered thermal governor 'power_allocator'
[ 0.022796] No ATAGs?
[ 0.022828] hw-breakpoint: Debug register access (0xee003e17) caused undefined instruction on CPU 0
[ 0.022836] hw-breakpoint: CPU 0 failed to disable vector catch
[ 0.022865] hw-breakpoint: Debug register access (0xee003e17) caused undefined instruction on CPU 1
[ 0.023763] Serial: AMBA PL011 UART driver
[ 0.039413] kprobes: kprobe jump-optimization is enabled. All kprobes are optimized if possible.
[ 0.044507] HugeTLB: registered 2.00 MiB page size, pre-allocated 0 pages
[ 0.044515] HugeTLB: 0 KiB vmemmap can be freed for a 2.00 MiB page
[ 0.047763] iommu: Default domain type: Translated
[ 0.047770] iommu: DMA domain TLB invalidation policy: strict mode
[ 0.049602] NetLabel: Initializing
[ 0.049608] NetLabel: domain hash size = 128
[ 0.049612] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO
[ 0.049673] NetLabel: unlabeled traffic allowed by default
[ 0.049866] vgaarb: loaded
[ 0.060385] clocksource: Switched to clocksource armada_370_xp_clocksource
[ 0.124522] VFS: Disk quotas dquot_6.6.0
[ 0.124626] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 0.125389] AppArmor: AppArmor Filesystem Enabled
[ 0.135571] NET: Registered PF_INET protocol family
[ 0.135784] IP idents hash table entries: 8192 (order: 4, 65536 bytes, linear)
[ 0.137128] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes, linear)
[ 0.137227] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
[ 0.137257] TCP established hash table entries: 4096 (order: 2, 16384 bytes, linear)
[ 0.137301] TCP bind hash table entries: 4096 (order: 4, 65536 bytes, linear)
[ 0.137356] TCP: Hash tables configured (established 4096 bind 4096)
[ 0.137586] MPTCP token hash table entries: 512 (order: 1, 8192 bytes, linear)
[ 0.137656] UDP hash table entries: 256 (order: 1, 8192 bytes, linear)
[ 0.137676] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes, linear)
[ 0.137862] NET: Registered PF_UNIX/PF_LOCAL protocol family
[ 0.137891] NET: Registered PF_XDP protocol family
[ 0.137902] PCI: CLS 0 bytes, default 64
[ 0.138350] Trying to unpack rootfs image as initramfs...
[ 0.138381] hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
[ 0.141087] Initialise system trusted keyrings
[ 0.141174] Key type blacklist registered
[ 0.141429] workingset: timestamp_bits=14 max_order=17 bucket_order=3
[ 0.148772] zbud: loaded
[ 0.152591] integrity: Platform Keyring initialized
[ 0.152634] integrity: Machine keyring initialized
[ 0.152644] Key type asymmetric registered
[ 0.152651] Asymmetric key parser 'x509' registered
[ 1.947948] Freeing initrd memory: 24288K
[ 1.976553] alg: self-tests for CTR-KDF (hmac(sha256)) passed
[ 1.976770] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250)
[ 1.976952] io scheduler mq-deadline registered
[ 1.983649] armada-xp-pinctrl d0018000.pin-ctrl: registered pinctrl driver
[ 1.985711] debugfs: Directory 'd0018100.gpio' with parent 'regmap' already present!
[ 1.986420] debugfs: Directory 'd0018140.gpio' with parent 'regmap' already present!
[ 1.987278] mvebu-pcie soc:pcie@82000000: host bridge /soc/pcie@82000000 ranges:
[ 1.987316] mvebu-pcie soc:pcie@82000000: MEM 0x00d0040000..0x00d0041fff -> 0x0000040000
[ 1.987341] mvebu-pcie soc:pcie@82000000: MEM 0x00d0044000..0x00d0045fff -> 0x0000044000
[ 1.987363] mvebu-pcie soc:pcie@82000000: MEM 0x00d0048000..0x00d0049fff -> 0x0000048000
[ 1.987383] mvebu-pcie soc:pcie@82000000: MEM 0x00d004c000..0x00d004dfff -> 0x000004c000
[ 1.987404] mvebu-pcie soc:pcie@82000000: MEM 0x00d0080000..0x00d0081fff -> 0x0000080000
[ 1.987425] mvebu-pcie soc:pcie@82000000: MEM 0xffffffffffffffff..0x00fffffffe -> 0x0100000000
[ 1.987444] mvebu-pcie soc:pcie@82000000: IO 0xffffffffffffffff..0x00fffffffe -> 0x0100000000
[ 1.987464] mvebu-pcie soc:pcie@82000000: MEM 0xffffffffffffffff..0x00fffffffe -> 0x0200000000
[ 1.987483] mvebu-pcie soc:pcie@82000000: IO 0xffffffffffffffff..0x00fffffffe -> 0x0200000000
[ 1.987502] mvebu-pcie soc:pcie@82000000: MEM 0xffffffffffffffff..0x00fffffffe -> 0x0300000000
[ 1.987522] mvebu-pcie soc:pcie@82000000: IO 0xffffffffffffffff..0x00fffffffe -> 0x0300000000
[ 1.987541] mvebu-pcie soc:pcie@82000000: MEM 0xffffffffffffffff..0x00fffffffe -> 0x0400000000
[ 1.987560] mvebu-pcie soc:pcie@82000000: IO 0xffffffffffffffff..0x00fffffffe -> 0x0400000000
[ 1.987579] mvebu-pcie soc:pcie@82000000: MEM 0xffffffffffffffff..0x00fffffffe -> 0x0500000000
[ 1.987593] mvebu-pcie soc:pcie@82000000: IO 0xffffffffffffffff..0x00fffffffe -> 0x0500000000
[ 1.987999] mvebu-pcie soc:pcie@82000000: PCI host bridge to bus 0000:00
[ 1.988009] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 1.988021] pci_bus 0000:00: root bus resource [mem 0xd0040000-0xd0041fff] (bus address [0x00040000-0x00041fff])
[ 1.988031] pci_bus 0000:00: root bus resource [mem 0xd0044000-0xd0045fff] (bus address [0x00044000-0x00045fff])
[ 1.988040] pci_bus 0000:00: root bus resource [mem 0xd0048000-0xd0049fff] (bus address [0x00048000-0x00049fff])
[ 1.988049] pci_bus 0000:00: root bus resource [mem 0xd004c000-0xd004dfff] (bus address [0x0004c000-0x0004dfff])
[ 1.988058] pci_bus 0000:00: root bus resource [mem 0xd0080000-0xd0081fff] (bus address [0x00080000-0x00081fff])
[ 1.988065] pci_bus 0000:00: root bus resource [mem 0xf8000000-0xffdfffff]
[ 1.988073] pci_bus 0000:00: root bus resource [io 0x1000-0xeffff]
[ 1.988166] pci 0000:00:01.0: [11ab:7823] type 01 class 0x060400
[ 1.988606] pci 0000:00:05.0: [11ab:7823] type 01 class 0x060400
[ 1.989567] PCI: bus0: Fast back to back transfers disabled
[ 1.989577] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 1.989591] pci 0000:00:05.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 2.015365] pci 0000:01:00.0: [11ab:7042] type 00 class 0x010000
[ 2.015398] pci 0000:01:00.0: reg 0x10: [mem 0x40000000-0x400fffff 64bit]
[ 2.015415] pci 0000:01:00.0: reg 0x18: [io 0xf1100000-0xf11000ff]
[ 2.015592] pci 0000:01:00.0: 2.000 Gb/s available PCIe bandwidth, limited by 2.5 GT/s PCIe x1 link at 0000:00:01.0 (capable of 8.000 Gb/s with 2.5 GT/s PCIe x4 link)
[ 2.015776] pci 0000:01:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force'
[ 2.015804] PCI: bus1: Fast back to back transfers disabled
[ 2.015812] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[ 2.015966] pci 0000:02:00.0: [1033:0194] type 00 class 0x0c0330
[ 2.015995] pci 0000:02:00.0: reg 0x10: [mem 0x4a000000-0x4a001fff 64bit]
[ 2.016121] pci 0000:02:00.0: PME# supported from D0 D3hot
[ 2.028440] PCI: bus2: Fast back to back transfers disabled
[ 2.028450] pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to 02
[ 2.028487] pci 0000:00:01.0: BAR 8: assigned [mem 0xf8000000-0xf80fffff]
[ 2.028502] pci 0000:00:05.0: BAR 8: assigned [mem 0xf8100000-0xf81fffff]
[ 2.028512] pci 0000:00:01.0: BAR 7: assigned [io 0x10000-0x10fff]
[ 2.028525] pci 0000:01:00.0: BAR 0: assigned [mem 0xf8000000-0xf80fffff 64bit]
[ 2.028543] pci 0000:01:00.0: BAR 2: assigned [io 0x10000-0x100ff]
[ 2.028554] pci 0000:00:01.0: PCI bridge to [bus 01]
[ 2.028562] pci 0000:00:01.0: bridge window [io 0x10000-0x10fff]
[ 2.028579] pci 0000:00:01.0: bridge window [mem 0xf8000000-0xf80fffff]
[ 2.028601] pci 0000:02:00.0: BAR 0: assigned [mem 0xf8100000-0xf8101fff 64bit]
[ 2.028616] pci 0000:00:05.0: PCI bridge to [bus 02]
[ 2.028625] pci 0000:00:05.0: bridge window [mem 0xf8100000-0xf81fffff]
[ 2.028703] pcieport 0000:00:01.0: enabling device (0140 -> 0143)
[ 2.028783] pcieport 0000:00:05.0: enabling device (0140 -> 0142)
[ 2.032611] mv_xor d0060900.xor: Marvell shared XOR driver
[ 2.061442] mv_xor d0060900.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[ 2.061717] mv_xor d00f0900.xor: Marvell shared XOR driver
[ 2.093437] mv_xor d00f0900.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[ 2.096269] Serial: 8250/16550 driver, 5 ports, IRQ sharing enabled
[ 2.098498] printk: console [ttyS0] disabled
[ 2.118668] d0012000.serial: ttyS0 at MMIO 0xd0012000 (irq = 37, base_baud = 15625000) is a 16550A
[ 3.417078] printk: console [ttyS0] enabled
[ 3.422115] Serial: AMBA driver
[ 3.426182] STM32 USART driver initialized
[ 3.433032] mousedev: PS/2 mouse device common for all mice
[ 3.439904] rtc-mv d0010300.rtc: registered as rtc0
[ 3.444868] rtc-mv d0010300.rtc: setting system clock to 2023-09-08T21:37:32 UTC (1694209052)
[ 3.558257] ledtrig-cpu: registered to indicate activity on CPUs
[ 3.566434] NET: Registered PF_INET6 protocol family
[ 3.598403] Segment Routing with IPv6
[ 3.602197] In-situ OAM (IOAM) with IPv6
[ 3.606254] mip6: Mobile IPv6
[ 3.609296] NET: Registered PF_PACKET protocol family
[ 3.614530] mpls_gso: MPLS GSO support
[ 3.618426] ThumbEE CPU extension supported.
[ 3.622736] Registering SWP/SWPB emulation handler
[ 3.628008] registered taskstats version 1
[ 3.632192] Loading compiled-in X.509 certificates
[ 4.541803] Loaded X.509 cert 'Debian Secure Boot CA: 6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1'
[ 4.550636] Loaded X.509 cert 'Debian Secure Boot Signer 2022 - linux: 14011249c2675ea8e5148542202005810584b25f'
[ 4.561789] zswap: loaded using pool lzo/zbud
[ 4.566920] Key type .fscrypt registered
[ 4.570887] Key type fscrypt-provisioning registered
[ 4.602027] Key type encrypted registered
[ 4.606105] AppArmor: AppArmor sha1 policy hashing enabled
[ 4.611654] ima: No TPM chip found, activating TPM-bypass!
[ 4.617203] ima: Allocated hash algorithm: sha256
[ 4.621967] ima: No architecture policies found
[ 4.626601] evm: Initialising EVM extended attributes:
[ 4.631769] evm: security.selinux
[ 4.635104] evm: security.SMACK64 (disabled)
[ 4.639394] evm: security.SMACK64EXEC (disabled)
[ 4.644033] evm: security.SMACK64TRANSMUTE (disabled)
[ 4.649107] evm: security.SMACK64MMAP (disabled)
[ 4.653751] evm: security.apparmor
[ 4.657180] evm: security.ima
[ 4.660158] evm: security.capability
[ 4.663752] evm: HMAC attrs: 0x1
[ 5.776199] input: gpio-keys as /devices/platform/gpio-keys/input/input0
[ 5.792471] Freeing unused kernel image (initmem) memory: 2048K
[ 5.810371] Checked W+X mappings: passed, no W+X pages found
[ 5.816087] Run /init as init process
[ 5.819777] with arguments:
[ 5.819785] /init
[ 5.819791] with environment:
[ 5.819796] HOME=/
[ 5.819801] TERM=linux
[ 5.819807] mtdparts=armada-nand:0xe0000@0x0(uboot),0x20000@0xe0000(env),0x20000@0x100000(env2),0x400000@0x120000(zImage),0x400000@0x520000(initrd),0x3F200000@0xE00000(boot),0x40000000@0x0(flash)
[ 6.484328] mv64xxx_i2c d0011000.i2c: can't get pinctrl, bus recovery not supported
[ 6.552760] rtc-pcf8563 0-0051: registered as rtc1
[ 6.608160] usbcore: registered new interface driver usbfs
[ 6.608327] mvneta d0070000.ethernet eth0: Using random mac address 0a:38:62:83:df:0f
[ 6.649707] SCSI subsystem initialized
[ 6.655340] mvneta d0074000.ethernet eth1: Using random mac address 0a:ef:f9:a8:67:48
[ 6.699126] usbcore: registered new interface driver hub
[ 6.703935] libata version 3.00 loaded.
[ 6.736366] hrtimer: interrupt took 11998800 ns
[ 6.737814] usbcore: registered new device driver usb
[ 6.767103] orion-ehci d0050000.usb: EHCI Host Controller
[ 6.777533] orion-ehci d0050000.usb: new USB bus registered, assigned bus number 1
[ 6.778353] sata_mv 0000:01:00.0: version 1.28
[ 6.786660] orion-ehci d0050000.usb: irq 46, io mem 0xd0050000
[ 6.819194] xhci_hcd 0000:02:00.0: xHCI Host Controller
[ 6.847104] orion-ehci d0050000.usb: USB 2.0 started, EHCI 1.00
[ 6.849079] xhci_hcd 0000:02:00.0: new USB bus registered, assigned bus number 2
[ 6.853781] sata_mv 0000:01:00.0: Gen-IIE 32 slots 4 ports SCSI mode IRQ via INTx
[ 6.860717] xhci_hcd 0000:02:00.0: hcc params 0x014042cb hci version 0x96 quirks 0x0000000000000004
[ 6.872464] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.01
[ 6.877936] xhci_hcd 0000:02:00.0: xHCI Host Controller
[ 6.885478] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 6.885488] usb usb1: Product: EHCI Host Controller
[ 6.902878] usb usb1: Manufacturer: Linux 6.1.0-11-armmp-lpae ehci_hcd
[ 6.909444] usb usb1: SerialNumber: d0050000.usb
[ 6.948318] scsi host0: sata_mv
[ 6.952439] scsi host1: sata_mv
[ 6.956265] hub 1-0:1.0: USB hub found
[ 6.960234] hub 1-0:1.0: 1 port detected
[ 6.986448] orion-ehci d0051000.usb: EHCI Host Controller
[ 6.987373] xhci_hcd 0000:02:00.0: new USB bus registered, assigned bus number 3
[ 6.991905] orion-ehci d0051000.usb: new USB bus registered, assigned bus number 4
[ 6.999440] scsi host2: sata_mv
[ 7.016434] xhci_hcd 0000:02:00.0: Host supports USB 3.0 SuperSpeed
[ 7.016514] orion-ehci d0051000.usb: irq 52, io mem 0xd0051000
[ 7.022933] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.01
[ 7.041236] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 7.048505] usb usb2: Product: xHCI Host Controller
[ 7.048827] scsi host3: sata_mv
[ 7.053413] usb usb2: Manufacturer: Linux 6.1.0-11-armmp-lpae xhci-hcd
[ 7.053420] usb usb2: SerialNumber: 0000:02:00.0
[ 7.056606] orion-ehci d0051000.usb: USB 2.0 started, EHCI 1.00
[ 7.065275] hub 2-0:1.0: USB hub found
[ 7.068063] ata1: SATA max UDMA/133 mmio m1048576@0xf8000000 port 0xf8022000 irq 47
[ 7.074082] hub 2-0:1.0: 2 ports detected
[ 7.077494] ata2: SATA max UDMA/133 mmio m1048576@0xf8000000 port 0xf8024000 irq 47
[ 7.077503] ata3: SATA max UDMA/133 mmio m1048576@0xf8000000 port 0xf8026000 irq 47
[ 7.086335] usb usb3: We don't know the algorithms for LPM for this host, disabling LPM.
[ 7.089224] ata4: SATA max UDMA/133 mmio m1048576@0xf8000000 port 0xf8028000 irq 47
[ 7.120782] usb usb3: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.01
[ 7.129105] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 7.136375] usb usb3: Product: xHCI Host Controller
[ 7.141282] usb usb3: Manufacturer: Linux 6.1.0-11-armmp-lpae xhci-hcd
[ 7.147842] usb usb3: SerialNumber: 0000:02:00.0
[ 7.153050] hub 3-0:1.0: USB hub found
[ 7.156876] hub 3-0:1.0: 2 ports detected
[ 7.161781] usb usb4: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.01
[ 7.170114] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 7.177381] usb usb4: Product: EHCI Host Controller
[ 7.182290] usb usb4: Manufacturer: Linux 6.1.0-11-armmp-lpae ehci_hcd
[ 7.188852] usb usb4: SerialNumber: d0051000.usb
[ 7.194039] hub 4-0:1.0: USB hub found
[ 7.197861] hub 4-0:1.0: 1 port detected
[ 7.352420] usb 2-1: new high-speed USB device number 2 using xhci_hcd
[ 7.456395] usb 4-1: new full-speed USB device number 2 using orion-ehci
[ 7.513789] usb 2-1: New USB device found, idVendor=1737, idProduct=0073, bcdDevice= 2.00
[ 7.522021] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 7.529195] usb 2-1: Product: RTL8187B_WLAN_Adapter
[ 7.534116] usb 2-1: Manufacturer: Manufacturer_Realtek
[ 7.539375] usb 2-1: SerialNumber: 00e04c000001
[ 7.584454] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 7.595422] ata1.00: ATA-8: HGST HTS725032A7E630, GHBOA560, max UDMA/133
[ 7.602187] ata1.00: 625142448 sectors, multi 16: LBA48 NCQ (depth 31/32)
[ 7.615995] ata1.00: configured for UDMA/133
[ 7.620658] scsi 0:0:0:0: Direct-Access ATA HGST HTS725032A7 A560 PQ: 0 ANSI: 5
[ 7.634496] usb 4-1: New USB device found, idVendor=8086, idProduct=0808, bcdDevice= 1.00
[ 7.642730] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 7.649902] usb 4-1: Product: USB PnP Sound Device
[ 7.654725] usb 4-1: Manufacturer: C-Media Electronics Inc.
[ 8.100418] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 8.111371] ata2.00: ATA-10: WDC WD5000AZLX-75K2TA0, 01.01A01, max UDMA/133
[ 8.118383] ata2.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
[ 8.128004] ata2.00: configured for UDMA/133
[ 8.132602] scsi 1:0:0:0: Direct-Access ATA WDC WD5000AZLX-7 1A01 PQ: 0 ANSI: 5
[ 8.612419] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 8.640448] ata3.00: ATA-8: WDC WD5000AAKS-00A7B0, 01.03B01, max UDMA/133
[ 8.647284] ata3.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[ 8.661007] ata3.00: configured for UDMA/133
[ 8.665586] scsi 2:0:0:0: Direct-Access ATA WDC WD5000AAKS-0 3B01 PQ: 0 ANSI: 5
[ 8.990898] ata4: SATA link down (SStatus 0 SControl 300)
[ 9.137034] hid: raw HID events driver (C) Jiri Kosina
[ 9.171436] usbcore: registered new interface driver usbhid
[ 9.177079] usbhid: USB HID core driver
[ 9.182182] sd 0:0:0:0: [sda] 625142448 512-byte logical blocks: (320 GB/298 GiB)
[ 9.189764] sd 0:0:0:0: [sda] 4096-byte physical blocks
[ 9.193092] sd 2:0:0:0: [sdc] 976773168 512-byte logical blocks: (500 GB/466 GiB)
[ 9.216884] sd 0:0:0:0: [sda] Write Protect is off
[ 9.217155] sd 1:0:0:0: [sdb] 976773168 512-byte logical blocks: (500 GB/466 GiB)
[ 9.221758] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 9.229230] sd 1:0:0:0: [sdb] 4096-byte physical blocks
[ 9.229291] sd 2:0:0:0: [sdc] Write Protect is off
[ 9.234618] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 9.239320] sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[ 9.239434] sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 9.248557] sd 0:0:0:0: [sda] Preferred minimum I/O size 4096 bytes
[ 9.257538] sd 1:0:0:0: [sdb] Write Protect is off
[ 9.277116] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[ 9.277257] sd 2:0:0:0: [sdc] Preferred minimum I/O size 512 bytes
[ 9.285523] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 9.294821] sd 1:0:0:0: [sdb] Preferred minimum I/O size 4096 bytes
[ 9.309604] sd 2:0:0:0: [sdc] Attached SCSI disk
[ 9.615718] sda: sda1 sda2 sda3 < sda5 >
[ 9.620637] sd 0:0:0:0: [sda] Attached SCSI disk
[ 9.739028] sd 1:0:0:0: [sdb] Attached SCSI disk
[ 9.753723] input: C-Media Electronics Inc. USB PnP Sound Device as /devices/platform/soc/soc:internal-regs/d0051000.usb/usb4/4-1/4-1:1.3/0003:8086:0808.0001/input/input1
[ 9.848652] hid-generic 0003:8086:0808.0001: input,hidraw0: USB HID v1.00 Device [C-Media Electronics Inc. USB PnP Sound Device] on usb-d0051000.usb-1/input3
[ 10.532432] raid6: int32x8 gen() 411 MB/s
[ 10.604396] raid6: int32x4 gen() 471 MB/s
[ 10.676383] raid6: int32x2 gen() 595 MB/s
[ 10.748378] raid6: int32x1 gen() 541 MB/s
[ 10.752684] raid6: using algorithm int32x2 gen() 595 MB/s
[ 10.824392] raid6: .... xor() 259 MB/s, rmw enabled
[ 10.829301] raid6: using intx1 recovery algorithm
[ 10.835245] xor: measuring software checksum speed
[ 10.848903] arm4regs : 1117 MB/sec
[ 10.861769] 8regs : 1161 MB/sec
[ 10.874602] 32regs : 1168 MB/sec
[ 10.878988] xor: using function: 32regs (1168 MB/sec)
[ 10.888896] async_tx: api initialized (async)
[ 16.414433] Btrfs loaded, crc32c=crc32c-generic, zoned=yes, fsverity=yes
[ 16.663932] BTRFS: device fsid bd9b4047-5599-4f64-b90d-119b70bcf29d devid 2 transid 395 /dev/sdc scanned by btrfs (174)
[ 16.676087] BTRFS: device fsid bd9b4047-5599-4f64-b90d-119b70bcf29d devid 1 transid 395 /dev/sdb scanned by btrfs (174)
[ 16.753780] PM: Image not found (code -22)
[ 17.487989] EXT4-fs (sda2): mounted filesystem with ordered data mode. Quota mode: none.
[ 17.842145] Not activating Mandatory Access Control as /sbin/tomoyo-init does not exist.
[ 18.201174] random: crng init done
[ 18.922187] systemd[1]: Inserted module 'autofs4'
[ 19.131638] systemd[1]: systemd 252.12-1~deb12u1 running in system mode (+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -BPF_FRAMEWORK -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified)
[ 19.164484] systemd[1]: Detected architecture arm.
[ 19.210211] systemd[1]: Hostname set to <lenovo>.
[ 23.992638] systemd[1]: Queued start job for default target graphical.target.
[ 24.026324] systemd[1]: Created slice system-getty.slice - Slice /system/getty.
[ 24.055227] systemd[1]: Created slice system-modprobe.slice - Slice /system/modprobe.
[ 24.083195] systemd[1]: Created slice system-serial\x2dgetty.slice - Slice /system/serial-getty.
[ 24.111144] systemd[1]: Created slice system-systemd\x2dfsck.slice - Slice /system/systemd-fsck.
[ 24.138070] systemd[1]: Created slice user.slice - User and Session Slice.
[ 24.160904] systemd[1]: Started systemd-ask-password-console.path - Dispatch Password Requests to Console Directory Watch.
[ 24.188855] systemd[1]: Started systemd-ask-password-wall.path - Forward Password Requests to Wall Directory Watch.
[ 24.217600] systemd[1]: Set up automount proc-sys-fs-binfmt_misc.automount - Arbitrary Executable File Formats File System Automount Point.
[ 24.249025] systemd[1]: Reached target cryptsetup.target - Local Encrypted Volumes.
[ 24.272773] systemd[1]: Reached target integritysetup.target - Local Integrity Protected Volumes.
[ 24.300951] systemd[1]: Reached target nss-lookup.target - Host and Network Name Lookups.
[ 24.324567] systemd[1]: Reached target paths.target - Path Units.
[ 24.344873] systemd[1]: Reached target slices.target - Slice Units.
[ 24.368849] systemd[1]: Reached target veritysetup.target - Local Verity Protected Volumes.
[ 24.434179] systemd[1]: Listening on rpcbind.socket - RPCbind Server Activation Socket.
[ 24.461389] systemd[1]: Listening on systemd-fsckd.socket - fsck to fsckd communication Socket.
[ 24.488900] systemd[1]: Listening on systemd-initctl.socket - initctl Compatibility Named Pipe.
[ 24.517879] systemd[1]: Listening on systemd-journald-audit.socket - Journal Audit Socket.
[ 24.545255] systemd[1]: Listening on systemd-journald-dev-log.socket - Journal Socket (/dev/log).
[ 24.573335] systemd[1]: Listening on systemd-journald.socket - Journal Socket.
[ 24.621490] systemd[1]: Listening on systemd-udevd-control.socket - udev Control Socket.
[ 24.649167] systemd[1]: Listening on systemd-udevd-kernel.socket - udev Kernel Socket.
[ 24.696738] systemd[1]: Mounting dev-hugepages.mount - Huge Pages File System...
[ 24.725528] systemd[1]: Mounting dev-mqueue.mount - POSIX Message Queue File System...
[ 24.772782] systemd[1]: Mounting proc-fs-nfsd.mount - NFSD configuration filesystem...
[ 24.802242] systemd[1]: Mounting sys-kernel-debug.mount - Kernel Debug File System...
[ 24.833601] systemd[1]: Mounting sys-kernel-tracing.mount - Kernel Trace File System...
[ 24.860950] systemd[1]: auth-rpcgss-module.service - Kernel Module supporting RPCSEC_GSS was skipped because of an unmet condition check (ConditionPathExists=/etc/krb5.keytab).
[ 24.933801] RPC: Registered named UNIX socket transport module.
[ 24.939784] RPC: Registered udp transport module.
[ 24.941204] systemd[1]: Starting keyboard-setup.service - Set the console keyboard layout...
[ 24.944529] RPC: Registered tcp transport module.
[ 24.944534] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 25.004995] systemd[1]: Starting kmod-static-nodes.service - Create List of Static Device Nodes...
[ 25.061156] systemd[1]: Starting modprobe@configfs.service - Load Kernel Module configfs...
[ 25.109874] systemd[1]: Starting modprobe@dm_mod.service - Load Kernel Module dm_mod...
[ 25.133238] systemd[1]: Starting modprobe@drm.service - Load Kernel Module drm...
[ 25.175333] systemd[1]: Starting modprobe@efi_pstore.service - Load Kernel Module efi_pstore...
[ 25.278861] systemd[1]: Starting modprobe@fuse.service - Load Kernel Module fuse...
[ 25.311855] systemd[1]: Starting modprobe@loop.service - Load Kernel Module loop...
[ 25.379998] systemd[1]: systemd-fsck-root.service - File System Check on Root Device was skipped because of an unmet condition check (ConditionPathExists=!/run/initramfs/fsck-root).
[ 25.383245] fuse: init (API version 7.37)
[ 25.407032] device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.
[ 25.420585] device-mapper: uevent: version 1.0.3
[ 25.446274] device-mapper: ioctl: 4.47.0-ioctl (2022-07-28) initialised: dm-devel@redhat.com
[ 25.455650] systemd[1]: Starting systemd-journald.service - Journal Service...
[ 25.469455] loop: module loaded
[ 25.572926] systemd[1]: Starting systemd-modules-load.service - Load Kernel Modules...
[ 25.616052] systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems...
[ 25.681688] systemd[1]: Starting systemd-udev-trigger.service - Coldplug All udev Devices...
[ 25.730570] systemd[1]: Mounted dev-hugepages.mount - Huge Pages File System.
[ 25.756419] EXT4-fs (sda2): re-mounted. Quota mode: none.
[ 25.757357] systemd[1]: Mounted dev-mqueue.mount - POSIX Message Queue File System.
[ 25.815711] systemd[1]: Mounted proc-fs-nfsd.mount - NFSD configuration filesystem.
[ 25.853269] systemd[1]: Mounted sys-kernel-debug.mount - Kernel Debug File System.
[ 25.905251] systemd[1]: Mounted sys-kernel-tracing.mount - Kernel Trace File System.
[ 25.929850] adt7475 0-002e: ADT7473 device, revision 0
[ 25.935065] adt7475 0-002e: Optional features: fan4 pwm2
[ 25.936864] systemd[1]: Finished kmod-static-nodes.service - Create List of Static Device Nodes.
[ 26.050727] systemd[1]: modprobe@configfs.service: Deactivated successfully.
[ 26.071065] hwmon hwmon2: temp1_input not attached to any thermal zone
[ 26.077572] systemd[1]: Finished modprobe@configfs.service - Load Kernel Module configfs.
[ 26.087835] hwmon hwmon3: temp1_input not attached to any thermal zone
[ 26.104079] hwmon hwmon4: temp1_input not attached to any thermal zone
[ 26.118440] systemd[1]: modprobe@dm_mod.service: Deactivated successfully.
[ 26.126905] systemd[1]: Finished modprobe@dm_mod.service - Load Kernel Module dm_mod.
[ 26.174783] Asymmetric key parser 'pkcs8' registered
[ 26.194712] systemd[1]: modprobe@drm.service: Deactivated successfully.
[ 26.226952] systemd[1]: Finished modprobe@drm.service - Load Kernel Module drm.
[ 26.254431] systemd[1]: modprobe@efi_pstore.service: Deactivated successfully.
[ 26.269635] systemd[1]: Finished modprobe@efi_pstore.service - Load Kernel Module efi_pstore.
[ 26.310325] systemd[1]: Finished keyboard-setup.service - Set the console keyboard layout.
[ 26.342307] systemd[1]: modprobe@fuse.service: Deactivated successfully.
[ 26.357535] systemd[1]: Finished modprobe@fuse.service - Load Kernel Module fuse.
[ 26.389222] systemd[1]: Started systemd-journald.service - Journal Service.
[ 26.671506] systemd-journald[257]: Received client request to flush runtime journal.
[ 28.344618] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 28.355794] /var/lib/snapd/snaps/pyradio_676.snap: Can't open blockdev
[ 28.363205] /var/lib/snapd/snaps/core18_2795.snap: Can't open blockdev
[ 28.371997] /var/lib/snapd/snaps/snapd_20101.snap: Can't open blockdev
[ 31.489939] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 31.504629] sd 1:0:0:0: Attached scsi generic sg1 type 0
[ 31.527153] sd 2:0:0:0: Attached scsi generic sg2 type 0
[ 32.566409] debugfs: Directory 'cpu1' with parent 'opp' already present!
[ 32.896480] at24 0-0050: supply vcc not found, using dummy regulator
[ 32.924459] at24 0-0050: 8192 byte 24c64 EEPROM, writable, 1 bytes/write
[ 32.931835] orion_wdt: Initial timeout 171 sec
[ 33.121176] nand: device found, Manufacturer ID: 0xec, Chip ID: 0xd3
[ 33.127677] nand: Samsung NAND 1GiB 3,3V 8-bit
[ 33.132179] nand: 1024 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[ 33.139908] marvell-nfc d00d0000.nand-controller: No minimum ECC strength, using 1b/512B
[ 33.195947] mc: Linux media interface: v0.10
[ 33.294175] Bad block table found at page 524224, version 0x01
[ 33.308566] Bad block table found at page 524160, version 0x01
[ 33.405722] nand_read_bbt: bad block at 0x000003c60000
[ 33.488998] usbcore: registered new interface driver snd-usb-audio
[ 33.624901] 6 fixed-partitions partitions found on MTD device pxa3xx_nand-0
[ 33.631940] Creating 6 MTD partitions on "pxa3xx_nand-0":
[ 33.696434] 0x000000000000-0x0000000e0000 : "u-boot"
[ 33.725737] 0x0000000e0000-0x000000100000 : "u-boot-env"
[ 33.773746] 0x000000100000-0x000000120000 : "u-boot-env2"
[ 33.817241] 0x000000120000-0x000000520000 : "zImage"
[ 33.869646] 0x000000520000-0x000000920000 : "initrd"
[ 33.908632] 0x000000e00000-0x000040000000 : "boot"
[ 34.041951] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 34.078384] cfg80211: Loaded X.509 cert 'benh@debian.org: 577e021cb980e0e820821ba7b54b4961b8b4fadf'
[ 34.147880] cfg80211: Loaded X.509 cert 'romain.perier@gmail.com: 3abbc6ec146e09d1b6016ab9d6cf71dd233f0328'
[ 34.194538] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[ 34.237748] BTRFS info (device sdb): using crc32c (crc32c-generic) checksum algorithm
[ 34.245719] BTRFS info (device sdb): using free space tree
[ 34.285903] platform regulatory.0: firmware: direct-loading firmware regulatory.db
[ 34.356803] platform regulatory.0: firmware: direct-loading firmware regulatory.db.p7s
[ 35.097524] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[ 35.099092] ieee80211 phy0: hwaddr 00:22:6b:da:ea:cb, RTL8187BvE V0 + rtl8225z2, rfkill mask 2
[ 35.117458] marvell-cesa d0090000.crypto: CESA device successfully registered
[ 35.201244] rtl8187: Customer ID is 0x00
[ 35.216744] rtl8187: wireless switch is on
[ 35.222063] usbcore: registered new interface driver rtl8187
[ 35.631275] rtl8187 2-1:1.0 wlx00226bdaeacb: renamed from wlan0
[ 35.852508] Adding 489468k swap on /dev/sda5. Priority:-2 extents:1 across:489468k FS
[ 36.327476] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem
[ 36.385641] EXT4-fs (sda1): mounted filesystem without journal. Quota mode: none.
[ 36.936105] audit: type=1400 audit(1694209085.984:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=541 comm="apparmor_parser"
[ 36.952996] audit: type=1400 audit(1694209085.984:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=541 comm="apparmor_parser"
[ 36.969003] audit: type=1400 audit(1694209085.984:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lsb_release" pid=540 comm="apparmor_parser"
[ 37.102179] audit: type=1400 audit(1694209086.152:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=545 comm="apparmor_parser"
[ 37.118150] audit: type=1400 audit(1694209086.152:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=545 comm="apparmor_parser"
[ 37.133174] audit: type=1400 audit(1694209086.152:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_groff" pid=545 comm="apparmor_parser"
[ 37.216422] audit: type=1400 audit(1694209086.264:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=544 comm="apparmor_parser"
[ 37.235440] audit: type=1400 audit(1694209086.264:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-helper" pid=544 comm="apparmor_parser"
[ 37.270915] audit: type=1400 audit(1694209086.264:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=544 comm="apparmor_parser"
[ 37.288858] audit: type=1400 audit(1694209086.264:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/{,usr/}sbin/dhclient" pid=544 comm="apparmor_parser"
[ 39.352605] NET: Registered PF_ALG protocol family
[ 40.047342] alg: No test for hmac(md4) (hmac(md4-generic))
[ 40.478090] mvneta d0070000.ethernet eth0: PHY [d0072004.mdio-mii:00] driver [Marvell 88E1318S] (irq=POLL)
[ 40.489019] mvneta d0070000.ethernet eth0: configuring for phy/rgmii-id link mode
[ 40.498612] bond0: (slave eth0): Enslaving as an active interface with a down link
[ 40.529999] cryptd: max_cpu_qlen set to 1000
[ 40.587386] mvneta d0074000.ethernet eth1: PHY [d0072004.mdio-mii:01] driver [Marvell 88E1318S] (irq=POLL)
[ 40.611511] mvneta d0074000.ethernet eth1: configuring for phy/rgmii-id link mode
[ 40.621629] bond0: (slave eth1): Enslaving as an active interface with a down link
[ 50.099465] NFSD: Using nfsdcld client tracking operations.
[ 50.105117] NFSD: no clients to reclaim, skipping NFSv4 grace period (net f0000000)
[ 50.257873] wlx00226bdaeacb: authenticate with a4:2b:b0:b9:14:84
[ 50.595795] NET: Registered PF_QIPCRTR protocol family
[ 50.756925] wlx00226bdaeacb: send auth to a4:2b:b0:b9:14:84 (try 1/3)
[ 50.767718] wlx00226bdaeacb: authenticated
[ 50.780532] wlx00226bdaeacb: associate with a4:2b:b0:b9:14:84 (try 1/3)
[ 50.811054] wlx00226bdaeacb: RX AssocResp from a4:2b:b0:b9:14:84 (capab=0x1011 status=0 aid=4)
[ 50.852792] wlx00226bdaeacb: associated
[ 50.900861] IPv6: ADDRCONF(NETDEV_CHANGE): wlx00226bdaeacb: link becomes ready
|
Re: Mainline Debian on Iomega ix4-300d September 08, 2023 10:49PM |
Admin Registered: 13 years ago Posts: 18,542 |
alf45tar,
I did not see anything strange in dmesg.
FWIW, my Marvell Armada 385 boxes (with kernel linux-6.4.11-mvebu-tld-1) and Marvel Kirwood boxes (with kernel linux-6.4.11-kirkwood-tld-1) are showing /sys/class/leds/ content in both Debian 11 and 12.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
I did not see anything strange in dmesg.
FWIW, my Marvell Armada 385 boxes (with kernel linux-6.4.11-mvebu-tld-1) and Marvel Kirwood boxes (with kernel linux-6.4.11-kirkwood-tld-1) are showing /sys/class/leds/ content in both Debian 11 and 12.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Mainline Debian on Iomega ix4-300d September 08, 2023 11:04PM |
Admin Registered: 13 years ago Posts: 18,542 |
Do you have serial console? It might show some errors that we cannot see in dmesg.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Mainline Debian on Iomega ix4-300d September 09, 2023 12:13AM |
Registered: 9 years ago Posts: 442 |
alf45tar,
Where did you get the kernel you are booting? It appears to be an actual Debian built kernel, not one that bodhi supplied on this forum. Debian does not officially support the Lenovo device, so they may not have included necessary drivers when building their kernel. You should try using the kernel supplied by bodhi.
Ray
Where did you get the kernel you are booting? It appears to be an actual Debian built kernel, not one that bodhi supplied on this forum. Debian does not officially support the Lenovo device, so they may not have included necessary drivers when building their kernel. You should try using the kernel supplied by bodhi.
Ray
|
Re: Mainline Debian on Iomega ix4-300d September 09, 2023 12:45AM |
Admin Registered: 13 years ago Posts: 18,542 |
All,
> Where did you get the kernel you are booting? It
> appears to be an actual Debian built kernel, not
> one that bodhi supplied on this forum. Debian
> does not officially support the Lenovo device, so
> they may not have included necessary drivers when
> building their kernel. You should try using the
> kernel supplied by bodhi.
>
> Ray
Ray is probably right! I think the most likely explanation is that the mainline Debian kernel config lacks some Marvell MVEBU specifics.
To prove the theory, It does not hurt to install kernel linux-6.4.11-mvebu-tld-1 and see if the /sys/class/leds got populated.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 09/09/2023 12:59AM by bodhi.
> Where did you get the kernel you are booting? It
> appears to be an actual Debian built kernel, not
> one that bodhi supplied on this forum. Debian
> does not officially support the Lenovo device, so
> they may not have included necessary drivers when
> building their kernel. You should try using the
> kernel supplied by bodhi.
>
> Ray
Ray is probably right! I think the most likely explanation is that the mainline Debian kernel config lacks some Marvell MVEBU specifics.
To prove the theory, It does not hurt to install kernel linux-6.4.11-mvebu-tld-1 and see if the /sys/class/leds got populated.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 09/09/2023 12:59AM by bodhi.
|
alf45tar
Re: Mainline Debian on Iomega ix4-300d September 09, 2023 06:21AM |
|
alf45tar
Re: Mainline Debian on Iomega ix4-300d September 09, 2023 11:10AM |
1. Installed mainline Debian 11 -> no leds
2. Installed bodhi kernel on mainline Debian 11 -> no leds
bodhi kernel has no new armada-xp-lenovo-ix4-300d.dtb. I used the mainline one.
2. Installed bodhi kernel on mainline Debian 11 -> no leds
root@lenovo:~# cat /proc/version Linux version 6.4.11-mvebu-tld-1 (root@tldDebian) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT Sun Aug 20 03:17:26 PDT 2023
bodhi kernel has no new armada-xp-lenovo-ix4-300d.dtb. I used the mainline one.
