ds351, > It kills > me that I can't double check that command now I know the feeling :) > anyway with the redone USB drive, I'm able to > connect to the pogo plug and see that it's now > running Debian! Congrats!by bodhi - Debian
ds351, What you should have done is to look at the sticky threads in thee Debian sub-forum. There you will find the Wiki thread https://forum.doozan.com/read.php?2,23630 QuoteKirkwood plugs Basic steps to install Debian and new u-boot on Kirkwood boxes Boot Kirkwood rootfs with stock u-boot Latest Linux Kirkwood kernel and rootfs Latest Kirkwood u-boots > ... > loadiby bodhi - Debian
mrc333777, > so can this be fixed the way you all do your fancy > repairs? This is a hard one to do "fancy repairs" :) The NAND flash (which is where the system is) is bad. The saving grace is it's an ARM box and run u-boot. So you would need to find the FW first (backup or installation image). And in u-boot console, you would erase NAND, hoping that all the bad blocksby bodhi - uBoot
slushendale, The latest kwboot binary is here: https://forum.doozan.com/read.php?3,27280 You need to find stock u-boot for this WRT1900ACS v2 box. And run kwboot with it to unbrick. What is the booting behavior now? when you connect serial console, and power up, do you see any output?by bodhi - uBoot
ahlaklisuvari, > DTB appended, got it. I assume it is done with > something similiar with those mkimage commands? I > think I've done it too. I've appended the dtb to > vmlinuz and turned it into a uImage in the end. > Just curious, why not zImage though? Because this > marvell's u-boot has bootz command too. Usually whatever (bootm or bootz) the stockby bodhi - uBoot
karool, > QuoteRobin > Creating 6 MTD partitions on "spi0.0": > [ 4.975138] 0x000000000000-0x0000000f0000 : > "RedBoot" > [ 4.981369] 0x0000000f0000-0x0000003c0000 : > "zImage" > [ 4.987545] 0x0000003c0000-0x0000007d0000 : > "rd.gz" > [ 4.993555] 0x0000007d0000-0x0000007e0000 : > "vendor" >by bodhi - uBoot
ahlaklisuvari, > I don't think MTD is a problem here, I simply > don't touch MTD. But on HDD. The installer run > just fine, with that caiman.dtb file. Even > recognized the ethernet. After the installer, it > won't boot now. > Did I create kernel images just > the wrong way? The kernel image seems OK. That was done in these commands for the insby bodhi - uBoot
kiro, > I don't think 5 MB of RAM reserved for > Transmission will anyhow slows the system down? Right! I don't think Transmision has any problem running in this box. I ran it on the GoFlex Net for a few years, and that Kirkwood box has only 128MB RAM and same CPU as this Pogo E02. I have not run Transmission in the last few years so I don't know if there is new bugby bodhi - Debian
Hi Trond, QuoteI strongly believe the cause of the lagging system clock must be inside the SOC since apparently time is lagging as soon as the kernel starts its internal timer (see https://forum.doozan.com/read.php?2,133814,133889#msg-133889 above). I recalled I looked at the DTS for the clock source. But, yes it's worth a look again.by bodhi - Debian
In anycase, I think it (https://wiki.debian.org/InstallingDebianOn/Linksys/WRT1200AC) might not be an appropriate instruction for your box. QuoteInvoke /usr/sbin/flash-kernel, it should overwrite /dev/mtd4 with Debian kernel and /dev/mtd5 with Debian initrd. The above step might corrupt your stock FW.by bodhi - uBoot
ahlaklisuvari, Why use chatgpt? apparently it gave you a wrong instruction. If you run the installer as instructed at Debian site https://wiki.debian.org/InstallingDebianOn/Linksys/WRT1200AC, then you need to do everything according to the instruction on that site. QuoteOne thing is I didn’t do flash-kernel related stuff, because the E-MMC inside is borked totally, or I couldn’t seeby bodhi - uBoot
Hi Trond, Note that the oscillator g762 here is for PWM Fan Controller.by bodhi - Debian
It might not be related. But another significant difference is the RN102/104 use PCIe SATA controller chip 88SE9170. The Mirabox does not have SATA, the PCIe bus is used for USB3 controller. https://wikidevi.wi-cat.ru/Netgear_ReadyNAS_RN104 https://wikidevi.wi-cat.ru/GlobalScale_MiraBox_V5by bodhi - Debian
Hi Trond, > IIRC, the SOC in Mirabox is a stripped down > version of the one in RN 102/104, so the > oscillators are the same. If the DTSs are > different, Mirabox seems to have the right one. > Yes? There is no oscilator defined in the Mirabox DTS.by bodhi - Debian
Hi Trond, The significant difference between the Mirabox and this RN 102/104 is: the oscillator. armada-370-netgear-rn104.dts g762: g762@3e { compatible = "gmt,g762"; reg = <0x3e>; clocks = <&g762_clk>; /* input clock */by bodhi - Debian
Jungle, > I'm just using systemd-timesyncd now, which is > keeping the clock up to date. Yeah, please let use know after you setup the clock sync. Trond might have solved this buffer overrun issue indirectly with this workaround.by bodhi - Debian
Scarface, > Begin: Mounting root file system ... Begin: > Running /scripts/local-top ... done. > Begin: Running /scripts/local-premount ... done. > Begin: Will now check root file system ... fsck > from util-linux 2.38.1 > fsck: error 2 (No such file or directory) while > executing fsck.ext2 for /dev/sda1 > fsck exited with status code 8 > done. > Warningby bodhi - Debian
Jungle, This problem was reported for this RN104 box (in the kernel ML) about 5-6 years ago. But I did not see any specific patch submitted afterward, so not sure if people have fixed the root cause. Perhaps you should run your box with a cron job to adjust the system clock, like Trond did in the installation thread. I think it will potentially help in timer-related tasks.by bodhi - Debian
Scarface, > At this time I went to check any good tutorial how > to install Debian including on this Forum. > Here I found a link to good tutorial: > https://minaret.biz/tips/ix2/index.html, > but if I understood well it's for ix2 (not > ix2-200) device, and this are different > devices, correct? So this tutorial is not suitable > for me? Most info are goby bodhi - Debian
Jungle, The good new is Trond did not see network buffer overun on his box. See this recent post the installation thread. > > Pause parameters for eth0: > Autonegotiate: on > RX: off > TX: off > RX negotiated: on > TX negotiated: on > Looks like the default is not fully flow control. Try: ethtool -A eth0 autoneg on rx on tx on eby bodhi - Debian
Hi Trond, > QuoteHave you seen this problem that Jugle is > seeing with networkk receive buffer > overrun? > > No, I have not: Good to hear that! > > tme@rn102:~$ uptime > 19:45:39 up 5 days, 5:10, 2 users, load > average: 0.00, 0.00, 0.00 > tme@rn102:~$ dmesg | grep overrun > tme@rn102:~$ > > > IIRC, RN104 has two ethenet ports,by bodhi - Debian
And does your Gbit network set up for jumbo frame?by bodhi - Debian
Hi Trond, Have you seen this problem that Jugle is seeing with networkk receive buffer overrun? https://forum.doozan.com/read.php?2,137625,137696#msg-137696by bodhi - Debian
Jungle, Make sure you are running the 6.5.7 kernel. Reboot, login and don't turn off flow control. Just leave the defaut whatever it is. And get the current settings ifconfig -a ethtool eth0 (you should mask out the MAC addresses from ifconfig output). ====== I'm still looking for the datasheet for this chip 88e1318.by bodhi - Debian
Jungle, Get the status to see if there are errors in RX and TX. ifconfig -a ==== Try these to see if it helps 1. Turn off flow control ethtool -A eth0 autoneg off rx off tx off 2. Swap your network cable with a different one. ===== We don't have network buffer management in the DTS for this box. I'm not sure why, perhaps this network chip (88e1318) does not hby bodhi - Debian
Billy, > I tried with the same usb to ttl but with a > raspberry pi like. No errors, nothing come up. Then your converter is faulty. If you buy cheap converter from eBay, like I usually do, sometime you'll get a bad one.by bodhi - Debian
Jungle, You're seeing the same problem as Trond did on the RN102 with kernel 6.8.7. I did mark it as broken QuoteUpdated 21 May 2024: Kernel linux-6.8.7-mvebu-370xp-tld-1-bodhi.tar.bz2 package has been uploaded. New/Updated in this release: - General kernel upgrade. - Warning: this kernel version is broken on the Netgear RN102 and 104. Please stay with previous kernelby bodhi - Debian
Billy, > Maybe my usb to ttl is faulty ? Not sure. If you can, try connecting to a different board (such as rPi).by bodhi - Debian
frankusb, Very nice tutorial! Thanks for you contribution. I'll add this to the Wiki thread.by bodhi - Debian