Debian on AK Systems Thin client rev 1.3 September 12, 2024 02:51AM |
Registered: 8 weeks ago Posts: 7 |
Loading file "/boot/uImage" from usb device 0:1 (usbda1) ** File not found /boot/uImage Loading file "/boot/uInitrd" from usb device 0:1 (usbda1) ** File not found /boot/uInitrd Wrong Image Format for bootm command ERROR: can't get kernel image!
Re: Debian on AK Systems Thin client rev 1.3 September 12, 2024 10:05AM |
Admin Registered: 13 years ago Posts: 18,994 |
Quote
I tried to update the u-boot and Debian firmware based on these instructions:
1. Linux Kernel 6.9.6 Kirkwood package and Debian rootfs (Updated 01 Nov 2023:)
2. Boot Kirkwood rootfs with stock u-boot
Quote
I do not have a device on which Linux is installed, so to do all the manipulations for the USB-FLASH, I used an emulator via VirtualBox. However, it seems to me that this was a bad idea, and also the fact that I apparently do not understand at all how the firmware works, thereby I got an eternal reboot.
Re: Debian on AK Systems Thin client rev 1.3 September 12, 2024 09:52PM |
Registered: 8 weeks ago Posts: 7 |
Quote
If you have kept the log of what you did in
creating the rootfs (1), and also the u-boot
booting (2), including all setenvs commands,
please post them here.
Quote
Using VirtualBox is OK. But make sure you use
command line to partition (fdisk) and format
(mkfs.ext3) the USB drive. Don't use the GUI. And
while you are creating the rootfs using tar
command and so on, you must be root user.
Re: Debian on AK Systems Thin client rev 1.3 September 12, 2024 11:33PM |
Admin Registered: 13 years ago Posts: 18,994 |
Loading file "/boot/uImage" from usb device 0:1 (usbda1) ** File not found /boot/uImage Loading file "/boot/uInitrd" from usb device 0:1 (usbda1) ** File not found /boot/uInitrd
usb start usb part usb info ext2ls usb 0:1 /boot
Re: Debian on AK Systems Thin client rev 1.3 September 13, 2024 12:39AM |
Registered: 8 weeks ago Posts: 7 |
Quote
Power up with serial console connected, interrup
u-boot at countdown, and
usb start usb part usb info ext2ls usb 0:1 /boot
U-Boot 2011.06 (Jan 03 2013 - 16:19:06) Promwad-ThinClient SoC: Kirkwood 88F6282_?? RevID 0x01 DRAM: 1 GiB NAND: 1024 MiB In: serial Out: serial Err: serial Net: egiga0, egiga1 88E1121 Initialized on egiga0, devadr 1 88E1121 Initialized on egiga1, devadr 0 Hit any key to stop autoboot: 0 Marvell>> usb start (Re)start USB... USB: Register 10011 NbrPorts 1 USB EHCI 1.00 scanning bus for devices... 3 USB Device(s) found scanning bus for storage devices... EHCI timed out on TD - token=0x248d80 EHCI timed out on TD - token=0x80008d80 1 Storage Device(s) found Marvell>> usb part Partition Map for USB device 0 -- Partition Type: DOS Partition Start Sector Num Sectors Type 1 2048 60626944 83 Marvell>> usb info 1: Hub, USB Revision 2.0 - u-boot EHCI Host Controller - Class: Hub - PacketSize: 64 Configurations: 1 - Vendor: 0x0000 Product 0x0000 Version 1.0 Configuration: 1 - Interfaces: 1 Self Powered 0mA Interface: 0 - Alternate Setting 0, Endpoints: 1 - Class Hub - Endpoint 1 In Interrupt MaxPacket 8 Interval 255ms 2: Hub, USB Revision 2.0 - Class: Hub - PacketSize: 64 Configurations: 1 - Vendor: 0x0000 Product 0x0000 Version 0.0 Configuration: 1 - Interfaces: 1 Bus Powered Remote Wakeup 0mA Interface: 0 - Alternate Setting 0, Endpoints: 1 - Class Hub - Endpoint 1 In Interrupt MaxPacket 1 Interval 12ms 3: Mass Storage, USB Revision 2.0 - USB DISK 2.0 070002E50D84E703 - Class: (from Interface) Mass Storage - PacketSize: 64 Configurations: 1 - Vendor: 0x13fe Product 0x4300 Version 1.0 Configuration: 1 - Interfaces: 1 Bus Powered 200mA Interface: 0 - Alternate Setting 0, Endpoints: 2 - Class Mass Storage, Transp. SCSI, Bulk only - Endpoint 1 In Bulk MaxPacket 512 - Endpoint 2 Out Bulk MaxPacket 512 Marvell>> ext2ls usb 0:1 /boot Marvell>> reboot Unknown command 'reboot' - try 'help' Marvell>> <INTERRUPT> Marvell>> boot NAND read: device 0 offset 0x100000, size 0x400000 4194304 bytes read: OK ## Booting kernel from Legacy Image at 06400000 ... Image Name: Linux-2.6.39.2 Created: 2013-01-03 13:10:40 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2826604 Bytes = 2.7 MiB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. Debian GNU/Linux 6.0 thin_client ttyS0 thin_client login:
Re: Debian on AK Systems Thin client rev 1.3 September 13, 2024 04:05AM |
Admin Registered: 13 years ago Posts: 18,994 |
Re: Debian on AK Systems Thin client rev 1.3 September 13, 2024 07:30PM |
Registered: 9 years ago Posts: 461 |
Re: Debian on AK Systems Thin client rev 1.3 September 13, 2024 10:44PM |
Registered: 8 weeks ago Posts: 7 |
Quote
Perhaps reach out to PromWad to see if they are willing to
provide the U-Boot source code for the device.
Re: Debian on AK Systems Thin client rev 1.3 September 13, 2024 10:50PM |
Registered: 8 weeks ago Posts: 7 |
Quote
This is a common error with old stock u-boot. Try
recreating the USB rootfs using a different USB
thumb drive. Sandisk is among the best brand to
use for rootfs.
Quote
Please keep the log of what you did, and also keep
the entire serial boot log.
Re: Debian on AK Systems Thin client rev 1.3 September 13, 2024 11:41PM |
Admin Registered: 13 years ago Posts: 18,994 |
Re: Debian on AK Systems Thin client rev 1.3 September 13, 2024 11:48PM |
Registered: 8 weeks ago Posts: 7 |
Quote
No. u-boot is the boot loader. You are not writing
the u-boot commands to the Debian rootfs. In the
instruction
Re: Debian on AK Systems Thin client rev 1.3 September 14, 2024 12:06AM |
Admin Registered: 13 years ago Posts: 18,994 |
>Quote
No. u-boot is the boot loader. You are not
> writing
> the u-boot commands to the Debian rootfs. In the
> instruction
Re: Debian on AK Systems Thin client rev 1.3 September 14, 2024 01:49AM |
Registered: 8 weeks ago Posts: 7 |