> pcmcia/express3? card to > see if they do anything fun :) The kernel supports this, so that should work! Ha, you've dated yourself if that old Ethernet/Wifi card is inside one of your drawers :))by bodhi - Debian
BTW, please change the thread title to "Debian on Checkpoint L-50".by bodhi - Debian
Quoteworks a treat - boots Openwrt & Debian. kwboot was successful also i tested it with debian... havent tried with Openwrt. i see no reason why it wont boot openwrt - i will try tomorrow when i have more time. Cool! Quoteonly thing of note was this that popped up to me in the boot sequence [ 0.257231][ T1] No ATAGs? Which i *think* is obsolete as we are using device-treesby bodhi - Debian
Dual boot Debian on USB and OpenWrt on flash Power up, interrupt serial console countdown and, setenv bootdev usb setenv device '0:1' setenv dtb_file '/boot/dts/kirkwood-l-50.dtb' setenv load_uimage_addr 0x800000 setenv load_uimage 'echo loading uImage ...; ext2load $bootdev $device $load_uimage_addr /boot/uImage' setenv load_initrd_addr 0x1100000 setenby bodhi - Debian
Everything looks great! We should do these to complete. 1. Dump the NAND u-boot and env images for rescue purpose mkdir -p /boot/u-boot # or whever you like to save them cd /boot/u-boot nanddump --noecc --omitoob -f mtd0.u-boot-openwrt /dev/mtd0 nanddump --noecc --omitoob -f mtd1.bootldr-env-openwrt /dev/mtd1 2. UART booting with the u-boot image Copy the backup image to theby bodhi - Debian
Kernel 6.2.8-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
It is optional. The new u-boot has not been released yet. But others have tried OK. Installation instruction: QuoteE. U-Boot 2022.04-tld-1 for M300 (Optional) After the box is running to your satisfaction. Consider installing new u-boot. See new u-boot installation and binary here You don't have to, since stock u-boot works OK. The advantage with the new u-boot is that it isby bodhi - Debian
> root@x:~# mkfs.ext3 /dev/sdb This was wrong. It should be the 1st partition, not the whole disk. mkfs.ext3 /dev/sdb1 > root@x:~# e2label /dev/sdb rootfs This was also incorrect. Should be: e2label /dev/sdb1 rootfs > root@x:~# mount /dev/sdb /mnt Ditto, mount /dev/sdb1 /mnt So on .... > Marvell>> boot > (Re)start USB... > USB: scanniby bodhi - Debian
Gravelrash, > ooooops - i did a save env in the uboot before i > read your post about > "Nooooooooo!!! not yet on the > saveenv" ah well at least when it > rebooted it came back into debian anyways No harm done :) with OpenWrt installation, it is pretty safe to do saveenv. Just my boards hacking habit is that I always try to have a rescue path, i.e. kwboot, befby bodhi - Debian
Gravelrash, > Not to worry for now.... back to the focus on > getting the device up and running first :) i will > do a reboot and save env then post the full log Before saving envs, we should back up the mtds in Debian. And also try kwboot with OpenWrt u-boot.by bodhi - Debian
Now we need to see if the envs can be seen in Debian and modified. I expect to see this in the bootargs. mtdparts=orion_nand:0xc0000@0x0(u-boot)ro,0x40000@0xc0000(bootldr-env),0x7900000@0x100000(ubi),0x800000@0x7a00000(kernel-2),0x7100000@0x8200000(rootfs-2),0x7900000@0xf300000(default_sw),0x1800000@0x16c00000(logs),0x100000@0x18400000(preset_cfg),0x100000@0x18500000(adsl),-@0x18600000(stby bodhi - Debian
Gravelrash, > E: The repository 'http://deb.debian.org > bullseye-security Release' does not have a Release > file. Adjust your apt sources. Looks like it's the security repo change in bullseye is needed. Here is mine: cat /etc/apt/sources.list deb http://ftp.us.debian.org/debian bullseye main contrib non-free deb-src http://ftp.us.debian.org/debian bullseyeby bodhi - Debian
Gravelrash, > I tip my hat to the developers over at Openwrt for > the outstanding work on the uboot and to you Mr > Bodhi for the out of the box - this just loads > debain release... Awesome :) looks like everything is working. But please do post the entire serial console log (from u-boot banner until the Debian login prompt). Attach the log if you'd like.by bodhi - Debian
mrc333777, > i cant get a created usb to boot up, i followed > the instructions properly i think. > can someone make a couple usb images of already > working bootable usb sticks for me to toy around > with? The instruction is concise. So you might have missed some details. Recreate the USB rootfs, and copy /paste everything you've done on the Linux terminal, and postby bodhi - Debian
> As i found in > https://forum.doozan.com/read.php?3,35709,54099#msg-54099 > and everywhere else i was searching for kernel > entry point related to stg-212/medion, it should > be fine with > Load Address: 60008000 > Entry Point: 60008000 Correct. Those are image load and entry point address for all OXNAS boards. What I mentioned above is the addresss that we use iby bodhi - Rescue System
You'd only need to SSH in the board has serial module converter which connects to serial port of other board (that you want to debug).by bodhi - Debian
:) Right! I missed that bootargs. Should be: setenv bootcmd 'usb start; run set_bootargs; run bootcmd_exec; reset'by bodhi - Debian
My bad. I had a typo! missing the closing quote. setenv load_dtb 'echo loading DTB $dtb_file ...; ext2load $bootdev $device $load_dtb_addr $dtb_file'by bodhi - Debian
1. Create the USB rootfs using Debian-5.13.6-kirkwood-tld-1-rootfs-bodhi.tar.bz2. https://forum.doozan.com/read.php?2,12096 Since this is a new u-boot 2020.04, skip Step 4 (this step is for stock u-boot only). 2. Attach the USB rootfs to the USB port in the front (or back if preferred). Power up, interrupt serial console and, setenv bootdev usb setenv device '0:1' setenvby bodhi - Debian
OK so after you've installed the new kernel. Down load the new DTB file and copy it to /boot/dts. The DTS file is also attached, for reference.by bodhi - Debian
> > /dev/null: Warning (unique_unit_address): > /soc/internal-regs/timer@20300: duplicate > unit-address (also used in node > /soc/internal-regs/watchdog@20300) > > > This one is bad. We should fix it. Actually it is OK. That's how it was coded in the armada-370-xp.dtsi.by bodhi - Debian
Drew, Please post in the other thread only. https://forum.doozan.com/read.php?2,134373by bodhi - Debian
QuoteWikiDevi Serial: yes, RJ-45 console, (115200 8N1) Intesresting! so where is this RJ-45 connector?by bodhi - Debian
> DTS was submitted to mainline > kernel. > You can also find high res photos of it I > submitted at > WikiDevi. Thanks Ray!by bodhi - Debian
Cool :) Power up or reboot. Interrupt serial console countdown and printenv help And please post the entire serial console boot log.by bodhi - Debian
Billy, You had a typo. These are kernel files 6.2.7-kirkwood-tld-1 after you extract the tarball. -rw-r--r-- 1 root root 195246 21 mars 23:31 config-6.2.7-kirkwood-tld-1 -rw-r--r-- 1 root root 39528022 24 mars 09:15 linux-6.2.7-kirkwood-tld-1-bodhi.tar.bz2 -rw-r--r-- 1 root root 165133 22 mars 22:31 linux-6.2.7-kirkwood-tld-1.patch -rw-r--r-- 1 root root 1382400 22 mars 03:46by bodhi - Debian
QuoteOn the older container /bin is NOT a symlink, and probably explains why the files appeared to double up. I think that probably mess up somehow. It is probably still an issue to be resolved in this "/usr merge" QuoteEdit: But how? All I can think of are there's other symlinks under the conatiners /bin/ that may point to a larger number of files than are on the remote host,by bodhi - Debian
Gravelrash Wrote: ------------------------------------------------------- > do you recomend i go ahead and install openwrt > now?? Yes! from the info page, look like they have a new u-boot. So once I can find the DTS in their tree, that would make it easier to get it booting Debian.by bodhi - Debian
> The rsync copy went as expected, nothing unusual, > but when I checked the folder size taken up by the > container, it was huge, about 2x what it is on the > remote machine. I've vaguely remember seeing the > 2x increase happen before and it is only on the > machine that has the issue with systemd failing. The fact that the container is 2x its source on the remoteby bodhi - Debian