@ksuszka, Pardon me if I missed what you have posted about this topic. Have you figured out if we can install Linux on this box without using the wloader GUI to select booting from USB? or is it the only way? ======= Speaking about display, I've found what need to be done in the kernel to start enable video. I'll need to build a new kernel for this.by bodhi - Debian
We are also facing another EOL issue with a possible removal of armel architecture in Debian 13. Basically, if that happens we can continue upgrading Kirkwood kernel, but all Kirkwood boxes are stuck in Debian 12 :( Hopefully another distro will still support armel. What has kept armel in Debian 12 is the rPi, thanks rPI :) I hope that specific rPI board will continue to ship for a longer timeby bodhi - Debian
> Yes, the goal was to extend nodes already declared > in armada-38x.dtsi instead of re-declaring them to > avoid warning messages during the dtb compilation. Yes I saw that you have: &uart0 { status = "okay"; }; &uart1 { status = "okay"; }; Shouldn't the pinctl info are specified in these 2 nodes? or were they already speby bodhi - Debian
> Just a quick note about the LAN LED behavior while > I have this in mind. > > As I previously mentioned, the LAN led doesn't > exhibit the expected behavior once the eth0 link > is up. I inspected many things, including the > Marvell PHY driver "/drivers/net/phy/marvell.c". > It seems that its default config is to use the > LED[0] as the 1000Mby bodhi - Debian
Cool! It works very well for the first try. Now let's run some tests and make it boot with the script (from the tarball). Boot with stock u-boot, login to Debian, cp -a boot.scr /boot/ sync Run kwboot again with the new u-boot, and reboot (or shutdown and power up) the box. Interrupt u-boot count down, dm tree scsi reset scsi part usb reset usb info ping <router IP addby bodhi - Debian
@Andreas Heyer, > Hi bodhi, > > thank you again for your work. I upgraded to your > new kernel release 5.4.268 and the seg faults went > away. > > I saw the last when installing the kernel > deb-package. After a reboot, since February > postponed Debian updates went smooth through. The > new kernel seems to do the job and I suppose the > deselectionby bodhi - Debian
@Koen, > It looks like OpenWrt is dropping oxnas after the > upstream community has discontinued support. Is > this the end of the road for oxnas? > > https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=6ca830559865f994db8732a9d06f452e36d5b490 We are at 5.4.x here. So it will be tracked to 5.4 LTS until Dec, 2025. Yes, it will be the end of the road for OXNAS on Dby bodhi - Debian
All, I'm looking for the Git(Hub) URL (I think it is OpenWrt staging) of Lubomir Rintel (the MMP3 Arch maintainer and author of this Ariel DTS). I want to see if the DTS has been updated by Lubomir. Thanks!by bodhi - Debian
@Robin, In the DS216 DTS, is there a reason why you did not use the same definition as the DS116 DTS regarding the serial nodes? internal-regs { i2c@11000 { pinctrl-names = "default"; pinctrl-0 = <&i2c0_pins>; status = "okay"; clock-frequency = <100000>; eeprom@57 { compatible = "atmel,24c64"; reg =by bodhi - Debian
We are testing the new Synology DS216 u-boot here: https://forum.doozan.com/read.php?2,137280,137377#msg-137377by bodhi - uBoot
Hi Robin, Please try kwboot this initial version for the DS216 u-boot. But don't flash it yet. If all goes well, you can boot with the current envs. However, I have not finalized the default envs yet, so it will be posted later. Download at Dropbox uboot.2024.04-tld-1.ds216.bodhi.tar md5: a226ad573b3981d0f84bd42635b419b4 sha256: 712f71d706bdd397c5f1412e1a86a21cf012c2020f82df37by bodhi - Debian
> that is most like due to the fact that both my > units came without wifi modules. As I gathered > from images of the inside of various versions of > those terminals from the internet there is no wifi > builtin on the main board but it is provided in > some units by an extension card. See this picture: > wyse > 3020 with wifi adapter. My units don't have >by bodhi - Debian
@ksuszka et al, Please try: modprobe rt2800usb dmesg ifconfig -aby bodhi - Debian
@ksuszka, > Here is the boot log for reference I did not see Wifi in the log. Perhaps I need to do more configuration for it. UPDATE: It seems already configured RT2800USB_RT35XX [=y] QuoteWI1 module IF: USB (nonby bodhi - Debian
> @bodhi yes, I've installed it on the usb stick and it seems to be booting just fine. Great job! Cool! Thanks!by bodhi - Debian
@ksuszka, Please try the new kernel 6.8.7-mvebu-tld-1: https://forum.doozan.com/read.php?2,32146by bodhi - Debian
Please try the new kernel 6.8.7-mvebu-tld-1: https://forum.doozan.com/read.php?2,32146by bodhi - Debian
Kernel 6.8.7-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
> Those GPIOs turn their respective SATA bays > properly under the stock u-boot. However, even > though both drives are powered, only drives in the > Disk 2 bay will be detected by u-boot and thus be > bootable. Have you tried to check and see if these are on? 39 GPIO1 7 INPUT LOW HDD 1 present. 40 GPIO1 8 INPUTby bodhi - Debian
Kernel linux-6.8.7-kirkwood-tld-1 package has been uploaded. See 1st post for download link. And please create a new thread for any installation problem or question.by bodhi - Debian
> I'm currently preparing a complete guide that I > will post here in a few days. There are few other > minor quirks > I didn't mention previously that I will sum up in > it, such as the fact that the stock u-boot only > detects drives in the DISK 2 bay, even with an > appropriate config. 26 GPIO0 26 OUTPUT HIGH HDD1 power enable.by bodhi - Debian
@primuspaul, > Is there a comprehensive guide, step 1 to end, on > how to install a Linux distribution on a 3020? No we don't, atm. This is where you should start reading: https://forum.doozan.com/read.php?2,134563,137251#msg-137251by bodhi - Debian
> Will this work? > https://www.ebay.com/itm/355519965973 That looks OK, it's the right chip. But as with any cheap serial converter module from eBay, you'd have to try to know for sure. If it does not work, see in the Wiki thread: Quote Unbricking with Serial Console & JTAG console How to unbrick your box using serial console with kwboot .... Serial Port connby bodhi - Debian
@Robin, > It just works > > I followed your procedure with the stock kwboot of > my debian 12 PC and it worked fine. I had to keep > the power button pressed until kwboot stated > loading. Any other way to power on the NAS ended > up in a normal boot, ignoring kwboot. Cool! that's a quirk worth knowing, will save people time trying to run kwboot. I'mby bodhi - Debian
Kwboot with stock mtd0 1. Dumping mtds dd if=/dev/mtd0 of=mtd0.ds216 bs=1024k conv=sync dd if=/dev/mtd1 of=mtd1.ds216 bs=7040k conv=sync dd if=/dev/mtd2 of=mtd2.ds216 bs=64k conv=sync dd if=/dev/mtd3 of=mtd3.ds216 bs=64k conv=sync 2. kwboot - Here is an example of running kwboot. - Download the latest kwboot here. Eventhough the kwboot comes with your Linux host distro is adequatby bodhi - Debian
> It works perfectly. > We can check if kwboot works indeed. But as I have > the required tools to dump or flash the SPI NOR in > place, it's not that risky for me to edit things > to oblivion. Cool! Let's dump the mtds first to back it up and use for kwboot.by bodhi - Debian
Looks like you are using a wrong tutorial. This is what we are using here: https://linux-mmp.docs.kernel.org/dell-wyse-3020.html And in this thread, this is the post you should start from: https://forum.doozan.com/read.php?2,137328,137330#msg-137330by bodhi - Debian
u-boot envs in Linux. Power up, interrupt u-boot countdown and, setenv mtdparts 'mtdparts=spi0.0:1m(u-boot),7040k(kernel),64k(u-boot-env),-(data)' Boot into Debian and - Check the mtd layout cat /proc/mtd - modify /etc/fw_env.config cat /etc/fw_env.config # MTD device name Device offset Env. size Flash sector size Number of sectors # DS216 /dev/mtd2 0x000by bodhi - Debian
Severuspiton99, > I tried but when i tried to get to kwboot nothing > happens. What could It be? There are a few reasons. It could be that your serial connection is wrong (which is not the case here because you've used serial console before), or the kwboot version you are using is old and cannot handshake with this box BootROM successfully. Post what is the u-boot image (wheby bodhi - Debian
@Robin, > Just a quick message to say that I dug a bit into > the DS214 DTS and found several issues. The most > important one probably being the RAM set to 1GB > instead of 512MB. While it's good to fix that RAM size, what's in the DTS should not impact how the kernel determines the RAM size. The RAM size is determined by u-boot and the kernel use that info, and igby bodhi - Debian