AndreaCipcino, > setenv mainlineLinux yes > USB starts no problem, but STOCK OS hangs up at > "booting the kernel" . > I have foun that the problem is the environment > variable "mainlineLinux yes" if I do not set this > variable then stock OS starts as normal. >Is this > variable necessary for USB rootfs booting and > operation ?by bodhi - uBoot
AndreaCipcino, My notes in the release. QuoteUpdated 01 Nov 2023: Basic Debian bookworm Kirkwood rootfs for most Kirwood plugs: - tarball size: 250MB - install size: 714MB - The init system used in this rootfs is sysvinit . To boot with systemd, see Notes below. - Installed packages: nano, avahi, ntp, busybox-syslogd (log to RAM), htop, isc-dhcp-client, dialog, bzip2, nfs servby bodhi - Debian
AndreaCipcino, > I have managed to run a rootfs of Debian 12 + OMV7 > on this old NAS. Everything works except hard disk > presence LEDs. Which kernel are you running on this ReadyNAS duo V2? If you are running my regularly released kernel here, then yes that's how it behaves. When you access the HDD, it will flash to show activities.by bodhi - Debian
Anderson, > I think it is really best to use rootfs on > the USB. That's what I said. The kernel is already installed in the USB rootfs. You would load the uImage and uInitrd from the rootfs /boot. And you would update it regularly when I release a new one. And you woud update to the latest Debian. So it is secured if you use it facing the internet. > On my 'EX2 Ultrby bodhi - Debian
Anderson, I've been running 4 NAS boxes with USB rootfs (Sandisk brand) for more than 10 years now. A couple years ago, I had to replace one of the internal HDDs, but the USB rootfs are still the same drives.by bodhi - Debian
Bob, > the Pogo 4 devices to Sandisk 32GB cards designed > for dashcams and surveillance cams. I am guessing > they have inbuilt sector write balancing and other > safeguards to prevent premature failure. I'd hope they have sophisticate write balancing. What you can also do is to over provision, i.e. leave about 2 to 4 GB unallocated. Those unallocated sectors will be uby bodhi - Debian
achlebek, Sorry, it has been many years since I see stock boot log, no idea what happended there.by bodhi - Debian
achlebek, > Thank you bodhi. > Is there an SSH way to blindly make it boot > kernel-2? Yes. But it is always riskier when you don't have serial console. Because you cannot see any problem booting up after you've made the change. Let see if your stock OS has these set up. SSH into stock OS and cat /etc/fw_env.config fw_printenv > I never tinkered with seby bodhi - Debian
achlebek, > Hi, there seem to be here some extremely > proficient users so let me ask a question before I > try to Debian my after-warranty Zyxel NAS326: Yes, do install Debian. Stock OS should be used only as a fallback/rescue system when you have problem and need to fix Debian rootfs. > > It reverts to defaults on every reboot/power. I > attach full dmesg but theby bodhi - Debian
Hi Trond, Thanks! so that theory about TCLK is proven not to be. BTW, I looked at the GPL code Quote[ 0.000000] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=pxa3xx_nand-0:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),0x600000@0x200000(uImage),0x400000@0x800000(minirootfs),-(ubifs) earlyprintk=serial mtdparts=pxa3xx_nand-0:0x180000@0(u-boot),0x200by bodhi - Debian
Here is the test kernel linux-6.9.6-mvebu-370xp-tld-3.x. This kernel is the same as the released kernel linux-6.9.6-mvebu-370xp-tld-2, but with some more debug loggings during boot. Download at Dropbox linux-6.9.6-mvebu-370xp-tld-3.x-bodhi.tar.bz2 md5sum linux-6.9.6-mvebu-370xp-tld-3.x-bodhi.tar.bz2 d680f87fa4aab42522614fc5943b641e linux-6.9.6-mvebu-370xp-tld-3.x-bodhi.tar.bz2 sby bodhi - Debian
Hi Trond, > On RN102 (warm start): > > Marvell>> md.l 0xd0018230 1 > d0018230: 0012b395 .... > Marvell>> md.l 0xd0018234 1 > d0018234: 00000000 .... > > Ok. So we can see BIT 20 was set to 200 Mhz (001 2b395), same as the Mirabox. I will post a test kernel so we can see in Linux if the SAR register content is the same as in u-boot. The Miby bodhi - Debian
Hi Trond, The correct addresses to dump SAR. On Mirabox Marvell>> md.l 0xd0018230 1 d0018230: 0012b397 .... Marvell>> md.l 0xd0018234 1 d0018234: 00000000 .... At 0xd0018230, Bit 20 == 1 indicates 200Mhz.by bodhi - Debian
Hi Trond, Thanks for the test! Unfortunately, I forgot to add the register base to the SAR offset :)) So I need to come back with a correct address. It should be either 0xd0000000 or 0xf1000000. In this old u-boot I think it is 0xd0000000. BTW, bit 20 is the TCLK indicator.by bodhi - Debian
bodhi Wrote: > > Currently, I cannot manage the leds event in > the > > dts/dtb file correctly listed in the > > /sys/class/leds folder. > > Boot back to sysvinit and check the > /sys/class/leds again to see if they are > populated. Nevermind. I've found that the current kernel 6.9.6 does not have the LED control for this box. While other Kirwooby bodhi - Debian
mdg69, > I was not albe to connect serial console to run > the test you asked. That will make it harder for me to help. > This version allow to manual control the fan but > it seems to me the kernel miss the coretemp module > to check the cpu temp. I would like to create a > script that control the fan rpm in conjunction > with the cpu and HDD temp (drivetemp mby bodhi - Debian
mdg69, > I am triyng to get control of the leds on a lacie > 2big NAS with no luck. > My /sys/class/leds folder is always empty. > Any suggestion? That's because you are using the GF Home DTB. The LED definitions are different. > > Do you know if the Kernel has gpio-leds support or > there is a specific module to be loaded with > modprobe? > Thby bodhi - Debian
> After following your instructions, I was able to > make U-Boot load `uImage` and `uInitrd` from the > HDD, on the `/dev/sda1/` partition formatted in > ext3 (ext4 doesn't work). > > But I remembered the reason for not being able to > use HDDs larger than 2TB: they are in 'GPT' and > not 'MBR'... > > Thus, U-Boot does not read disby bodhi - Debian
> Yes, I am seeing the whole bootlog on a simple > connection without using kwboot. At least that's a > step in the right direction. > > > As for kwboot, the behavior is like the u-boot > > image was not a good one. Perhaps you should go > > ahead and boot into Debian, and then dump stock > > mtd0, and use it for kwboot. > > I'll seeby bodhi - Debian
dhargens, > xmodem: Connection timed out > > > You'll note that at the end the connection dropped > for some reason - which also won't work. I tried > both kwboots (rc3 & static) and neither worked for > me. I think that's normal. The connection timeout indicates that kwboot is still trying to handshake. If you run picocom/minicom then youby bodhi - Debian
Anderson, > Marvell>> scsi reset > > > > Reset SCSI > > AHCI init for unit0 > > Tarby bodhi - Debian
I forget if this box u-boot can see the HDDs. With at least one HDD in the slots. Power up, interrupt u-boot countdown and, help scsi resetby bodhi - Debian
Hi all, Please cold start (after shutdown for about 30 minutes) your RN102 or RN104. Interrupt u-boot at count down and dump SAR register md.l 0x18230 1 md.l 0x18234 1by bodhi - Debian
Thanks Trond!by bodhi - Debian
dhargens, > RJ-45 Console port. Here's the pins I'm using: > 3 - TXD > 4+5 - GND > 6 - RXD It looks right to me. > [*] I'm using minicom for my serial connection > program, set at 115200 8N1 Also OK. > [*] I've swapped Rx & Tx - one way it's silent, > the other way it's gibberish. > With this wiring setup I applyby bodhi - Debian
dhargens, This box uses RJ45 connector. It's a standdard Cisco one. See previous post. https://forum.doozan.com/read.php?2,134340,134421#msg-134421by bodhi - Debian
> I changed sda1 to sdb1, because rootfs usb is > sdb1 That's expected. The rootfs USB drive could be assigned any driver letter, depending on how many SATA drives and USB drives are attched. To make it resilient, the bootargs should be: setenv set_bootargs_debian 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs $(mtdparts) earlyprintk=serial init=/bin/system'by bodhi - Debian
Anderson, Power up, interrupt u-boot at count down and, setenv usbActive 0 setenv set_bootargs_debian 'setenv bootargs console=ttyS0,115200 root=/dev/sda1 $(mtdparts) earlyprintk=serial init=/bin/systemd' setenv bootcmd 'run set_bootargs_debian; run boot_debian_usb1; run boot_debian_usb2; run boot_debian_usb3; run boot_debian_usb4; reset' And then bootby bodhi - Debian
Anderson, > Now, I want to move the uImage and uInitrd to the > NAND. OK. > I successfully transferred the uImage, which is > 5MB, to the flash. > However, the uInitrd doesn't fit in the standard > partition because it's also 5MB and the file > doesn't fit (I tried to reduce it with this > tutorial > (https://forum.doozan.com/read.php?2,13by bodhi - Debian
Hi Ray, Did you find u-boot source any where in the website https://kb.netgear.com/2649/NETGEAR-Open-Source-Code-for-Programmers-GPL?by bodhi - Debian