Show all posts by user
Discussions that don't fit anywhere else
Re: Debian on Netgear RN102 - Yesterday
whitepawn, Change nandwrite to explicitly specify --noecc nandwrite --noecc /dev/mtd0 u-boot-rn102-nandwithdtbmtd0.kwbby bodhi - Debian
Re: RN104 bricked - Yesterday
K20, Ah. I see. These binaries are old so I forgot that the options have changed. Here is the revised commands. nandump commands are the same ./nanddump --noecc --omitoob -f mtd0.u-boot.rn104 /dev/mtd0 ./nanddump --noecc --omitoob -f mtd1.u-boot-env.rn104 /dev/mtd1 ./nanddump --noecc --omitoob -f mtd2.uImage.rn104 /dev/mtd2 ./nanddump --noecc --omitoob -f mtd3.minirootfs.rn104 /dev/by bodhi - uBoot
Re: RN104 bricked - Yesterday
K20, It's been a while so I don't remember the nanddump and nandwrite version. The old NAND utility has slightly different syntax. So in stock OS, ./nanddump --help ./nandwrite --help And ====== Also, since you can log in stock OS with the HDD rootfs, why not let stock OS reinstall the FW for you? there must be a way to do that.by bodhi - uBoot
Re: PogoHole project - stuck on oxnas boot only - help - Yesterday
[ 4.757184] usb 1-1: new high-speed USB device number 2 using oxnas-ehci At this point the USB stick was not detected further. What we should see is somethign like this (idVendor and idProduct numbers are specific to a USB brand and model). [ 4.597393] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608 So, - What type of USB drive is it? brand, model, capacity. - Wasby bodhi - uBoot
Re: Debian on Netgear RN102 - Yesterday
whitepawn, root@Neutron:/media# dd if=/dev/mtd0 of=/media/mtd0afterwrite.kwb 4096+0 records in 4096+0 records out 2097152 bytes (2.1 MB, 2.0 MiB) copied, 26.2412 s, 79.9 kB/s root@Neutron:/media# diff u-boot-rn102-nandwithdtbmtd0.kwb mtd0afterwrite.kwb Binary files u-boot-rn102-nandwithdtbmtd0.kwb and mtd0afterwrite.kwb differ That flashing was not good. Look at the nandwrite commandby bodhi - Debian
Re: RN104 bricked - 2 days ago
K20, > NAS OS doesn't have "nanddump" "nandwrite " or > "nand" Download the bin pack that I uploaded: https://forum.doozan.com/read.php?3,27280 Extract it to a folder somehwere in your good box. Let say it is in /media. And when you execute each command, it must be executed as the binary is in the current folder (replace this in the commnandsby bodhi - uBoot
Re: RN104 bricked - 2 days ago
K20, QuoteCan anyone please help me to written default FW image to nand via ubifs ? I just did above.by bodhi - uBoot
Re: SoftBank nears deal to sell Arm Holdings to Nvidia for more than $40 billion - WSJ - 2 days ago
> LOL! Are they saying he isn't merely a "get off my > lawn" kind of guy but a "get off my Linux > International Headquarters lawn" kind of guy? LOL Can't blame him. Imagine someone is just not get on your lawn, but also camping and sh*t on your lawn :))by bodhi - Off-Topic
Re: Debian on Netgear RN102 - 2 days ago
whitepawn, I forgot one step in verifying the nandwrite. Make it 2MB even: dd if=u-boot-rn102-nandwithdtbmtd0.bin of=u-boot-rn102-nandwithdtbmtd0.kwb bs=2048k conv=sync So no padding is needed in writing: nandwrite /dev/mtd0 u-boot-rn102-nandwithdtbmtd0.kwb And verify. It should show the 2 binaries are identical: dd if=/dev/mtd0 of=/media/mtd0afterwrite.kwb diff u-boot-rn102-nby bodhi - Debian
Re: Need help in restoring u-boot for Netgear Stora MS2110 - 2 days ago
Trond, Everything is in the patch file. See the release thread. Quotehttps://forum.doozan.com/read.php?2,12096 Updated 23 Aug 2020: Kernel linux-5.8.3-kirkwood-tld-1 package has been uploaded. The following features were added/updated: - BFQ IO Scheduler is now the default in the kernel. This is an improvement in making the system more responsive when under memory stress (Note: usby bodhi - uBoot
Re: RN104 bricked - 2 days ago
K20, Congrats! Now you have unbricked the box, and can log in stock OS. 0: u-boot 0x000000180000 0x000000000000 0 1: u-boot-env 0x000000020000 0x000000180000 0 2: uImage 0x000000600000 0x000000200000 0 3: minirootfs 0x000000400000 0x000000800000 0 4: ubifs 0x000007400000 0x000000c00000 0 And you did restore pby bodhi - uBoot
Re: Debian on Netgear RN102 - 2 days ago
whitepawn, Remove the env mtd. setenv mtdparts 'mtdparts=pxa3xx_nand-0:0x200000@0(u-boot),-(ubifs)' Flash: nandwrite -p /dev/mtd0 u-boot-rn102-nandwithdtbmtd0.bin Verify: dd if=/dev/mtd0 of=/media/mtd0afterwrite.bin diff u-boot-rn102-nandwithdtbmtd0.bin mtd0afterwrite.bin And reboot. If the header checksum is bad again, check how the u-boot image was created duby bodhi - Debian
Re: Debian on Netgear RN102 - 3 days ago
whitepawn, Quote1. I think i have figured it out by changing partition sizes on mtd0 and mtd1 but i am not sure if it is the right way to do it.According to here it must be a multiple of the block-size of the flash chip OK, so comparing the 2 definitions. Keep in mind that the erase block size for this NAND is 2M (0x00200000). Old: dev: size erasesize name mtd0: 00180000 00200by bodhi - Debian
Re: Pogoplug V4 - uBoot with Debian - 3 days ago
Nirmal, > > Now the device is simply blinking and not booting > from the sd card. (both devices). I even tried > with the native adapter which came with the > device. No difference. > > My query is, does using a different 12V adpater > will damage the device ethernet or does it > corrupted the uboot inside the NAND ? Not likely that will corrupt anythingby bodhi - uBoot
Re: Need help in restoring u-boot for Netgear Stora MS2110 - 3 days ago
Trond, > Winter is coming, and then I will try to figure > out a robust way to install a recent Linux kernel > and bodhi's root file system on Stora without a > serial console, since the serial console part may > be too technical for some owners. I don't know if > it's possible, though. It is quite easy. I have released new 2017.07 u-boot for the Stoby bodhi - uBoot
Re: RN104 bricked - 3 days ago
K20, Try what tme suggested above about "Tech Support" mode. If you still cannot recover then the next step is to reflash your box using a good set of mtds back up. Because your NAND mtds were erased. You need to reflash all 5 mtds. device nand0 <armada-nand>, # parts = 5 #: name size offset mask_flags 0: u-boot 0x000000180000 0x000000000000 0by bodhi - uBoot
Re: PogoHole project - stuck on oxnas boot only - help - 3 days ago
myhobby, > I'm currently stuck on booting after (I think) > successfully installing the latest OXNAS820 on a > Pogo-B03. I have created an USB stick according > the guidelines with the label "rootfs" and ext3 > filesystem. On the USB stick I untarred > Debian-4.14.180-oxnas-tld-1-rootfs-bodhi.tar.bz2 > and when checking the USB stick, I do find all theby bodhi - uBoot
Re: compile kernel, integrate sata driver, detected but no sda,why? - 3 days ago
youxiaojie, > and to tell you a good news spl 2015.10 is ok, I > am testing and polishing. Cool! will keep that in mind. I don't have any plan to upgrade u-boot for this device for (the current version could be the last, since we don't have a lot of OXNAS users).by bodhi - Debian
Re: compile kernel, integrate sata driver, detected but no sda,why? - 3 days ago
youxiaojie, > 1.I just feel strange that why there is no sda > appear, what I did is try to compile kernel to > include oxnas disk driver so that I can mount > harddisk as root and boot from it.for now harddisk > recognized but sda not appear. could you give me > some viewpoint? On top of my head, I can't think of any reason. But do check these SATA config optioby bodhi - Debian
Re: compile kernel, integrate sata driver, detected but no sda,why? - 3 days ago
youxiaojie, > I compile kernel of new openwrt 5.4 for pogo > plug, Which pogoplug? the Pogo V3 OXNAS or the Pogo E02 Kirkwood? > your kenel and rootfs missing b43 wireless driver > realtek net phy driver, so I compiled from openwrt > integrate sata diver ,no sda appear, so which > driver I miss? You could have requested that the b43 Wifi be included, and I'lby bodhi - Debian
Re: Debian on Netgear RN102 - 4 days ago
whitepawn, > It complains about error correction system, how > can i fix this? It is ony a warning, it is OK ignore it. To make it perfect, iirc somewhere in the DTS must be modified for this chip. The DTS currently being used works for all MVEBU boxes stock NAND chips. > But when i used nandwrite to test if i can write > mtd1 it says permission denied: Looks like thereby bodhi - Debian
Re: Debian on Netgear RN102 - 4 days ago
whitepawn, I will be back. You need to get some sleep:)by bodhi - Debian
Re: RN104 bricked - 4 days ago
K20, Looks like the recovery is working. So now you just need to upgrade FW. Usually the recovery FW enable you to log in and interact with the box so you can upgrade FW using their official procedure. I don't think you need to do it manually. Find the stock FW upgrade procedure at Netgear website and follow that. I wanted to see the envs listing to determine if the USB recovery prby bodhi - uBoot
Re: Debian on Netgear RN102 - 4 days ago
whitepawn, > NAND: (ID 0x642c) 8192 MiB [ 4.957071][ T1] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0x64 [ 4.963573][ T1] nand: Micron MT29F64G08CBABAWP [ 4.969041][ T1] nand: 8192 MiB, MLC, erase size: 2048 KiB, page size: 8192, OOB size: 744 Neutron Linux version 5.8.5-mvebu-370xp-tld-1 (root@tldDebianVM) (arm-linux-gnueabihf-gcc (Ubuntu/Linaro 7.5.0-3by bodhi - Debian
Re: RN104 bricked - 4 days ago
K20, > I have manage to write the uboot to the Nand and > now am currently able to boot from nand every time > I power on Congrats! it is unbricked. Ok so now there are few things to do. 1. At serial console prompt get the listing of the envs (NAND is empty, so the envs are from internal envs) printenv And please post the output here. 2. Search Netgear website to seby bodhi - uBoot
Re: Debian on Netgear RN102 - 4 days ago
QuoteIf you are using isolated power bricks or using plugs without earth (which always connects GND) GND must be connected. If your PC and Nas power brick connects same outlet with earthing you don't need to connect GND because it is connected Via earthing internally so you won't need to connect extra ground. Yes. And it does not hurt to connect GND in either cases and keep it simpleby bodhi - Debian
Re: Debian on Netgear RN102 - 4 days ago
whitepawn, > Also board itself has 4 pinheader internally but i > havent tested yet. That's the J7 header, the 2nd UART port. So you have UART0 and UART1.by bodhi - Debian
Re: RN10400 - 4 days ago
AkkJaa, I asked other guys in the RN102 thread. Here is the answer: https://forum.doozan.com/read.php?2,106589,107669#msg-107669by bodhi - uBoot
Re: Debian on Netgear RN102 - 4 days ago
All, Could you guys describe how you connect serial console. Where is the header and what is the pinouts? It is for AkkJaa in this thread: https://forum.doozan.com/read.php?3,106724,107619#msg-107619 Seems like the RN102 and RN104 have the same board.by bodhi - Debian
Re: Debian on Netgear RN102 - 4 days ago
whitepawn, Look for ./board/mv_ebu/common/mv_hal/nfc/mvNfc.c Regarding USB 3.0, yes, it is the PCI bus. Trond, QuoteI imagine the right way to proceed is to extract the ReadyNAS specific patches from the Marvell u-boot version v2011.12, and modify these patches so they can be applied seamlessly to a recent main stream u-boot implementation. What are the candidates for the "reby bodhi - Debian