> Now the above I've wrote between your edits, so > now I assume my questions answered ^_^J Cool :) glad you got the answer you need! There is better way to ensure the load addresses are OK. But that will be for another day in the future when I will release new u-boot version.by bodhi - Debian
Dźwiedziu , Use 5.17.4-kirkwood-tld-1, interrupt serial console at count down > Hit any key to stop autoboot: And then set the load address of load_dtb_addr to 0x2c00000 and boot. setenv load_dtb_addr 0x2c00000 boot ========= I've just recall I already wrote this on the u-boot installation thread: QuoteB. Load addresses for large systems This u-boot was releby bodhi - Debian
> [ 8.598956][ T1] VFS: Cannot open root > device "(null)" or unknown-block(0,0): error -6 > [ 8.680507][ T1] (driver?) > [ 8.688519][ T1] Kernel panic - not syncing: > VFS: Unable to mount root fs on > unknown-block(0,0) This error is just either the root device in the bootargs is wrong, or the USB rootfs partition does not have label rby bodhi - Debian
> I know in the E02 the kirkwood is bare, as > it is in the Pogo v4 as well. in the E02 just add > a heatsink that fits, and in the v4, you need to > get crafty to figure a way to take up the air gap > between the SoC and the steel weight on the bottom > of the casing. That provides ample thermal mass to > keep the 800MHz part cool enough to not > fall over on itselby bodhi - Debian
> Why not. the point here is that at every kernel > update the mess inceases :) Yup :) But the kernel files must be in /boot for certain things to work, such as Debian version upgrade. So keep 2 versions and uninstall the rest. Example to uninstall a kernel version (any version except the one running). List them root@tldDebian:/boot# dpkg -l | grep linux-image ii linux-imagby bodhi - Debian
miazza, Each box has a different LEDs skeme so if the questions are about NSA325, it should not be asked here (will be consfusing to go back and forth). Should be in this thread https://forum.doozan.com/read.php?2,32460,32467#msg-32467 You will see the examples about using esekeyd to control button. And how to set up the script to shoutdown.by bodhi - Debian
You could also create a folder and move them there cd /boot mkdir -p kernel mv -i linux-image-*.deb *.tar *.bz2 ./kernelby bodhi - Debian
miazza, > Thank you. I supposed it was like that but I > wanted to be sure. Yes, instruction to remove is there as a precaution when people install the kernel from a mainline rootfs. delete: > linux-dtb-5.17.4-kirkwood-tld-1.tar > linux-5.17.4-kirkwood-tld-1-bodhi.tar.bz2 But keep everything else, those are kernel files, in case you have to recreate the uImage and uInby bodhi - Debian
Dźwiedziu, > Only > unset all the env variables and semi-manually set > them to the defaults, taken from > https://forum.doozan.com/read.php?3,12381 -> > uboot.2016.05-tld-1.environment.bodhi.tar. That's not a recommended approach. When you think the envs are all messed up, you can use the uEnv.txt to reload all default envs. See here: https://forum.doozan.cby bodhi - Debian
macsneil, > I've tried the fix for the blue LED indicator > activity trigger and it works but I can't seem to > make it persistent across reboots. > /sys/class/leds/status:blue:activity_led/trigger > defaults back to heartbeat from none after > reboot. Did you add this to your /etc/rc.local (place it at the end before "exit 0"): echo none >by bodhi - Debian
sudos, Very nice mod! > Hopefully this little infopost finds someone else > well as the Armada chips are pretty much the only > SoCs in the kirkwood family I can find to have a > working thermal sensor that can be probed. The > others might have it but I've never seen a device > yet aside from this example where it has been made > visible and working. Theby bodhi - Debian
> card from another pc to bring it back to live, it > used to be my main gamer but I built it in 2014 so > it is pretty much obsolete and I figured since I > refuse to part with it I may as well use it for > something useful. I see. Hard to part with something like that. I would keep it too. I have a box of floppy disks somewhere in the closet, in among them my first 8086 deby bodhi - Debian
echowarrior108, > Operating System: Debian GNU/Linux 11 > KDE Plasma Version: 5.20.5 > KDE Frameworks Version: 5.78.0 > Qt Version: 5.15.2 > Kernel Version: 5.10.0-13-amd64 > OS Type: 64-bit > Processors: 6 × AMD Phenom(tm) II X6 1100T > Processor > Memory: 15.6 GiB of RAM > Graphics Processor: NVC1 All that horsepower for a mail server? wow! Sell itby bodhi - Debian
Kernel 5.17.4-mvebu-tld-1 package has been uploaded. See 1st post for download link. Please create a new thread for any installation problem or questions.by bodhi - Debian
Thanks Ray!by bodhi - Debian
IIRC, OpenWrt already has a switchroot instruction.by bodhi - Rescue System
> And why would you want? You could > simply use Debian. +1 Distro serves different purposes. Use Debian as a NAS, use OpenWrt as a router.by bodhi - Rescue System
renojim Wrote: ------------------------------------------------------- > Sorry, I missed that. I should have known there > was a reason. :-) NP :) I don't like them much myself. Also, about this topic, Dropbox policy is not Linux's friendly. If anybody knows Gdrive or OneDrive provide download statistics, please let me know.by bodhi - Debian
habibie, > Am I understood you are saying uboot has been > ported to replace a PC boot ROM now? I sure would > like to get information like this so I can start > playing around with it on my old i386 PCs. No, sudos meant new u-boot for the Dell Kace M300. There is no u-boot for Intel PC.by bodhi - Debian
> I gotta be honest, I've never understood the need > for a shortening service. These aren't tweets or > text messages limited to a certain length. :-) As I've mentioned, I use bitly to record the download count. Dropbox does not provide download count. If I see not too many people are intertested in a certain image, then it's something with low priority on myby bodhi - Debian
I've updated the u-boot installation post to include Dropbox links for everything. Looks like I will have to stop using bitly from now on. I need to find a better shortening service.by bodhi - Debian
Sorry, I was not aware that you are still having trouble downloading the u-boot image!by bodhi - Debian
Kernel linux-5.17.4-kirkwood-tld-1 package has been uploaded. See 1st post for download link. And please create a new thread for any installation problem or questions.by bodhi - Debian
pm4888, What you did was creating a Debian debootstrap rootfs. But you also need to install a kernel to run it. There are several more steps to be done before you can use this debootstrap rootfs. That was the reason I created a basic rootfs and provided it for general consumption. =========== There are 3 differerent paths to get this box running. 1. Download my basic rootfs and ruby bodhi - Debian
pm4888, You could just create the rootfs Debian-5.13.6-kirkwood-tld-1-rootfs-bodhi.tar.bz2 and use it.by bodhi - Debian
QuoteIndeed can I make a live tar as for your post without having any problem during the tar process ? What Mijzelf show above should work fine. That tar command will exclude everything, only the rootfs is archived (things such as user's /home will be excluded). You can even use cp to copy the live rootfs, but you'd need to make sure to prepare a few things before running the cp coby bodhi - Debian
> Normally with debootstrap to prepare a disk and a > boot loader it's good to go to setup a system. > However I dont know how to approach these devices > especially when kernel needs to be customized and > dts files are involved. E.g. what it takes to > prepare a debian11 system? With the Pogo E02 you can use the Debian debootstrap rootfs. You just need to tweak thby bodhi - Debian
pm4888, My new u-boot supports Ext4. So you can use Ext4 rootfs. But you do need to finalize the rootfs formatting right away. > I didn't give "finalized" much thought and use > "sync" before reboot, because of ext4 and the > journal/cache. Sync does not do anything to an Ext4 file system during lazy_init. > the uboot files at least the one forby bodhi - Debian
OK. Try: fw_setenv curr_bootfrom 2 fw_setenv next_bootfrom 1 fw_setenv change_boot_part 1 If you alternatively modify the curr_bootfrom and next_bootfrom a few times (2 to 1 and 1 to 2) and still no boot, then I think you will need to connect serial console. There might be some different behavior that we cannot see without serial console.by bodhi - Debian
Markeli, Make sure that you were root when you extract the tarball into the USB drive. su - If you did that, then try this, 1. Plug in the USB rootfs to the front USB port. 2. In stock OS, set this env fw_setenv change_boot_part 1 fw_printenv and reboot. If it still boot stock OS, log in and set it again fw_setenv change_boot_part 1 fw_printenv and reboot. If that iby bodhi - Debian