Hey chessplayer, It's your instruction after all. So if you feel that what it should be then keep it. But the whole point about seeing the envs is a bit counterproductive at Step 5. You cannot really change them, and the new envs setup in Step 1 is applicable to u-boot only. OpenWrt does not use them at all. If one looks at the mtdparts env and comparing that with output of cat /prby bodhi - Rescue System
I guess I was not very clear in my post. I suggested that the text in blue should be moved to Step 7. And delete the text in red. We know the envs are not useable yet. And there is no way to adjust mtdparts. So everything about the envs should be discussed in Step 7. What remain in Step 5 is a sanilty check. Quote5. Log in to OpenWrt Find the IP address of your box and ssh into it (usby bodhi - Rescue System
chessplayer, >. I have implemented your suggestions > and hope that we are now good to go searching for > a solution. I don't see the updates in the 1st post ? > Is there a command to show the contents of a file using ubifs<something>? My naive try ubifscat did not do the job ... I don't think there is cat command for ubifs in u-boot. Usually you wouldby bodhi - Rescue System
OK, that's all I have for now!by bodhi - Rescue System
Now in step 7, you would talk about setting up the envs. And mention that it is not writeable. Quote7. Boot from NAND and log in to OpenWrt ....... generate or modify /etc/fw_env.config Check whether the file /etc/fw_env.config has the following contents (which is easily calculated from the above MTD layout in comparison to bodhi's): /dev/mtd1 0xc0000 0x20000 0x20000 If notby bodhi - Rescue System
Quote 6. Install to NAND Finally, we can perform a sysupgrade of OpenWrt/LEDE either using the LUCI WIF (Web Interface) or the command line. < text about removing all USB drives here> Since we are already logged in via ssh, I only describe the latter option, while the former may be found, e.g., in step 4.b of Jörg's original post for the Kirkwoods. We must do: opkg updateby bodhi - Rescue System
chessplayer, I'm reading the instruction in the 1st post. As I go, I will make a different post for each suggestion. I think realy we don't want even mention the issue about envs not writable here. As long as the ubi partition appears correctly in OpenWrt layout, the installation will proceed OK. And then when you talk about fw_env.config later, you would elaborate. Quote5. Loby bodhi - Rescue System
rsavera, > Do you have any issues with daisy chaining > switches? Cost quickly goes up with 48 port > switches but 24's and 16's are really inexpensive. I don't have any issue with daisy chaining switches at all. They are low cost unmanaged switches Now that we are discussing network, there is an inherent issue with wireless bridges that I've seen and not bby bodhi - Off-Topic
> Should i adjust load_dtb_addr to 0x2c00000 ? You could do that now. > Are there any other "hardcoded" values, that need > to be adjusted for successful boot in near future > versions of linux kernel? These 3 load addresses: load_dtb_addr=0x2c00000 # might need to be adjusted load_initrd_addr=0x1100000 # might need to be adjusted load_uimage_addr=0x800000by bodhi - Debian
Quotebodhi And please create a new thread for any installation problem or question. Last post moved here: https://forum.doozan.com/read.php?2,132765by bodhi - Debian
Thanks guys! Those are very nice 6" cables. If you're like me I stack 3 ethernet switches (so short cables are nice to have).by bodhi - Off-Topic
chessplayer, > But, what do you mean by 'confirmation'? How would > I test, whether this is necessary? You did confirm that. > nand erase.part data > usb reset; fatload usb 0 0x60500000 uImage; bootm 0x60500000 > (the nand.erase should be on the data-partion with > this mtdparts-definition, shouldn't it? Yes. Note that Kirkwood or OXNAS NAND,by bodhi - Rescue System
> So, the nand.erase was necessary also to realize > that what we thought we saw before were really > artefacts ... Yes, that seems to be the case. Because I don't think you would want sysupgrade to format NAND partition at all (it would wipe out current user setting). It only update the existing partition using ubifs. And with NAND you always need to erase the sectors beforby bodhi - Rescue System
> Newegg used to have them. Free after rebate. The shortest Ethernet cable I can find on ebay is 0.2m (about 8"). 3 USD each.by bodhi - Off-Topic
chessplayer Wrote: ------------------------------------------------------- > So, I did all of these again and got the same > results as above: > > setenv mtdparts > 'mtdparts=41000000.nand:0x100000@0x0(u-boot),-@0x100000(ubi)' > setenv partition 'nand0,0' > ubi part ubi > ubi info > ubi info layout > > > Then, I got (which seemby bodhi - Rescue System
ubifsls / ubifsls /etc And so on.....by bodhi - Rescue System
Hi chessplayer, No need to reinstall u-boot. You've missed a recommended step in the installation. Joerg have mentioned this (now that I reread his post and tried it myself on the NSA310S). Quote # bootenvs for Pogo E02 based on uboot.2016.05-tld-1.environment: setenv mtdparts 'mtdparts=orion_nand:0x100000@0x0(u-boot),-@0x100000(ubi)' setenv partition 'nand0,0&by bodhi - Rescue System
Hi chessplayer, I've not been able to boot up my Pogo V3 yet. But I've looked at my old notes. Wow 5,6 years ago :) I created a Kirkwood rescue system but never release it. ubi part ubi ubi info ubi info layout If you see the volume rootfs_data from the layout, try mounting it. It seems to be OpenWrt standard naming convetion used also in Kirkwood boards. ubifsmount uby bodhi - Rescue System
rsavera, Nicely done! Did you make those short Ethernet cable, or bought it somewhere?by bodhi - Off-Topic
Cool! Also, you can use fake-hwclock package instead.by bodhi - Debian
> > Is this SSD formatted Ext3 or Ext4? > > Both are formatted Ext4. Next time it comes up and > fails, i'll try to get a console running to > capture the issue for clarity's sake. I hope you did a "finalize" ( (no lazy_init) when you created this Ext4 rootfs.by bodhi - Debian
rsavera, > Am I missing something obvious here? I feel like I > am. Nothing obviously wrong. What Debian version are you at? cat /etc/debian_version If it is too old, try upgrading Debian first.by bodhi - Debian
sudos, > Something to report... Even with adjusted envs to > take care of the larger-than-11MB initramfs with > 5.18.6, whenever I'm doing an update that requires > the rewrite of uInitrd as outlined in the kernel > thread, the M300 always wants to just not-boot > afterwards. This also happened previously on older > kernels as well, but only past 5.15. > &by bodhi - Debian
> I guess these kirkwood boxes uses 3.3v i/o, so you > can just use a raspberry pi's serial port and > connect them directly. No ca-42 cable needed. IIRC, the rasPi has the Prolific PL3xxx chip built in. The Mirabox also has it.by bodhi - Debian
chessplayer, I beleive all GF Home can be kwboot'ed (Some GF Net cannot). Haha, ninja'ed by David.by bodhi - Debian
FYI, I've tried reinstalling OpenWrt today on my NSA310S and having quite a bit of problem. Perhaps something has changed in sysupgrade process. Update: This image works https://downloads.openwrt.org/releases/22.03.0-rc6/targets/kirkwood/generic/openwrt-22.03.0-rc6-kirkwood-zyxel_nsa310s-squashfs-sysupgrade.binby bodhi - Rescue System
Nirmal, > Do you think it's possible to repair this via JTag > or UART ? Nobody has reported this issue. But for this Pogo V4, it is almost unbrickable. You need to run kwboot to boot it over UART and see the behavior. See here for an example booting with kwboot: https://forum.doozan.com/read.php?3,51739,51919#msg-51919 And pay attention to the power supply. QuoteTrby bodhi - uBoot
BTW, The work around is you can do this on your USB drives that don't have uEnv.txt. Assuming ithe other USB drive is mounted at /media/sdb1 mkdir media/sdb1/boot cd /media/sdb1/boot And then copy the uEnv.xt over to this drive.by bodhi - uBoot
chessplayer, > I just wanted to report an issue I just had on a > Pogo E02 concerning uEnv.txt. I wanted to use the > file to use systemd and it worked about three or > four times. However, since what I am testing is to > have the box act as a file server in the Windows > network with automount of the non-boot attached > devices, I have more than one USB drive attachby bodhi - uBoot
At the moment, you can only read the fan speed on those boxes, but not controlling it (it is automatically adjusted by hardware). Nobdy has found an i2c command to controlling the fan. Wiki thread: QuoteSensors & Fan & WOL OWFSPlug : 1-Wire File System + Motion Detection Software in a NAND Package OWFS & Motion Detection (external link) How to control GPIO in Linux usersby bodhi - Debian