It should be relatively easy to load the OpenWrt image into ram and boot the nas. You can then do a 'sysupgrade' to install it in the onboard nand flash. Loading the image in ram can be done either via tftp or an usb drive depending on the available commands in uboot. So can you type 'help' or '?' at the uboot prompt to show what commands are available?by Koen - uBoot
Hi, I bought a pogoplug pro on ebay recently and decided to install OpenWrt on it. I played around with it for a bit but quickly realised that the current release of OpenWrt does not expose the internal sata port and I also had problems using different wifi cards in the pcie slot. So I decided to look into updating uboot to bohdi's version as released on the forum here to be able to run Dby Koen - uBoot
Hi TC, I think the problem will be related to the file permissions on /share/sdb1. You have probably mounted the drive as root user and other users will not be able to write data to this location. I guess you will need to use chmod to change permissions on this directory. I normally run 'chmod -R 777' on the directory and that will change the permissions of the folder plus all subfolby Koen - uBoot
I've got a NSA325 V1 and would like to be able to control the fan to reduce the noise. It runs OpenWrt and the disks are spun down most of the time so it should not need much cooling. I've already put some rubber rings around each screw between the fan and the housing to try to reduce the transmission of the vibrations to the case. I recently bought a second hand Netgear readynas duo v2by Koen - uBoot
Thanks for the info about cutter.re to inspect the binary from stock firmware. I'll give that a try to see if I can find out more about fan control. Koenby Koen - uBoot
When I run i2cdetect it gives the following output: root@debian:~# i2cdetect -y 0x0 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- 0a -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- --by Koen - Debian
Hi all, I think the name of the script has been a 'red herring'. The data sheet shows the ADT7463 has 24 pins and I have inspected the board and I can see only 1 chip with 24 pins. The 24 pin chip on the board is not an ADT7463 but has the following label: Holtek HT66F30. The data sheet of that microcontroller can be found here: https://datasheet.lcsc.com/szlcsc/Holtek-Semicon-HTby Koen - Debian
Hi Bodhi, thanks for the info. I may have a look at writing a script once I've got some more spare time. Koenby Koen - Debian
I changed the i2c section in the kirkwood-nsa325.dtb to the following below (pure guess work based on some similar dts files so this is probably incorrect!). Now the lm85 module gets loaded on boot and sensor-detect does say there is a adt7463 sensor. However pwmconfig does not change the fan rpm and fancontrol does not work. i2c@11000 { compatible = "marvell,mv64xxx-i2c";by Koen - Debian
The end of the script above calls the binary /sbin/fanctrld. I guess it is not possible to just copy this over since it is compiled for a much older system? When I run 'strings fanctrl' this is the output: strings fanctrld /lib/ld-linux.so.3 __gmon_start__ libc.so.6 exit readdir sprintf fopen strncmp closedir fork abort strtol fgets strlen __errno_location chdby Koen - Debian
Hi, I've got a NSA325 and it is currently running OpenWrt with the option to boot Debian from an USB stick. Both OpenWrt and Debian do not seem to have the ability to adjust the fan speed on the NSA325 at the moment. Based on the findings by 030theo in the NSA326 thread I decided to inspect the stock firmware to see if I could find something. Running binwalk on the stock firmware doesby Koen - Debian
OpenWrt on kirkwood devices uses the UBI file system which according to this website can't be used on USB sticks. http://www.linux-mtd.infradead.org/doc/ubi.html#L_rednote On the WD my book live NAS the OpenWrt system is written to an ext4 partition on the hard drive since it doesn't have flash memory. So it is possible to install and run from an ext4 partition but I'm not suby Koen - uBoot
You probably ran out of space since all the packages you installed while running the combined initramfs-uImage end up being installed in your RAM. So by the time you want to run sysupgrade there is not enough space left to download the required files. The idea of the combined initramfs-uImage is that it provides a way to install the normal full system to nand. Once that has been done you can reboby Koen - Rescue System
The combined initramfs-uImage is a minimal openwrt system that can be run from memory (RAM). To install openwrt to the internal memory / nand you will need to follow the instructions to do a sysupgrade from command line. The general procedure is described here: https://openwrt.org/docs/guide-user/installation/sysupgrade.cli You will have to adjust these instructions based on the system you want tby Koen - Rescue System
I'm not sure if related but over the Xmas holiday I installed OpenWrt 18.06.1 on a Shuttle KD20 and ran into the same issue. The device didn't reboot from command line and required the power cable to be removed before it could boot again. I assumed that it was an OpenWrt issue but it looks like it is a general kernel issue. Koenby Koen - Debian
> Yes, Ext3 and Ext2 use the same driver in stock > Marvell uboot. This Iomega EZ uboot is practically > same as other Kirwood boxes uboot. Thanks for the additional info. I'll prepare an etx3 rootfs on the new Sandisk USB stick when it arrives.by Koen - Debian
OK thanks. I can't connect using openvpn anymore so I guess it must have died completely in the mean time. I tried to setup a ext3 rootfs originally but couldn't get it to work. I'm not sure if ext3 booting is supported in stock uboot. I'll order a proper Sandisk USB stick instead of this unbranded one and redo the setup when I visit them next week. Koenby Koen - Debian
I can't use sudo but su still works. Unfortunately fsck gives a segmentation fault. Are there any other options to check and fix the filesystem? root@debian:/# fsck.ext2 /dev/sdb1 Segmentation faultby Koen - Debian
Hi, I've got a Iomega EZ running Debian at my parents house for doing local backups of their phones and tablets. I just logged in to check everything is still running OK and it seems the USB drive with the rootfs is dying. I can't use sudo to run apt-get update and there seem to be file system issues. dmesg shows the following output: [2163755.377304] EXT2-fs (sdb1): error: ext2by Koen - Debian
During the Christmas holiday I was doing some IT support for the family and I ended up with a couple of android phones. The phones are quite old and no longer supported by the manufacturer or custom roms so pretty much worthless. The hardware is probably more powerful than the standard kirkwood board so could be an interesting project to run linux on. A quick google shows that there are quite a fby Koen - Off-Topic
Inside there is both a 4 pin and a 6 pin header. The 4 pin is the UART connection. With the power button towards you and the DVI connection away from you the connections are as follows: GND, TX, RX, VCC (from left to right).by Koen - Debian
Hi bodhi, I tried that but got confused since the mtd definition in Debian is different than in stock. And even the mtd definition in stock is numbered differently than the order they appear on the chip. So I ended up bricking the device and had to switch to flashing the chip using my raspberry pi. Luckily there was a stock dmesg in the original thread which helped me work out the order of theby Koen - Debian
When I connect a screen, mouse and keyboard it shows the device booting into the stock OS so re-flashing the chip with the original uboot etc. has been successful. Unfortunately the ethernet connection doesn't work so that indicates that there is a hardware problem with my device. Thanks everyone for the advice and contributions. Regards, Koenby Koen - Debian
I've used to following section of the original stock dmesg output to put together the different mtd files in the correct order (using my backup of uboot and the env combined with the other files supplied by fortis91). I've used cat to merge all the files together and added an empty file to the end to match the size of the 1M chip. I've then used flashrom on my raspberry pi to flashby Koen - Debian
Thanks a lot. I may have some time this weekend to return my box to stock to see if this is a hardware problem. Koenby Koen - Debian
No not yet. I've been quite busy with work and other stuff recently so haven't got around to do more testing. I still think it is a hardware problem but the only way to test that assumption is to go back to stock. I haven't got a backup of all the original mtd partitions so would need someone else to upload their copy / backup to be able to test this. Koenby Koen - Debian
I've dug out the router supplied by my ISP and connected it to the hp t5325 using a different cable. I get the exact same results. The router shows a 100 Mbps connection on the lan1 port but the device does not show up in the list of connected clients. Sending a ping does not work and there is no working connection. So the only thing left to test is going back to stock and check if it is a hby Koen - Debian
Hi bodhi, this is the same as yours: T5325> mii info PHY 0x08: OUI = 0x5043, Model = 0x22, Rev = 0x00, 100baseT, FDX And here the dump of 0 - 5. Looks similar but there are some differences in dump 5 as highlighted further down this post. T5325> mii dump 8 0 0.by Koen - Debian
Hi bodhi, the number on the chip says macronix MX25L1606E which corresponds with the current kernel dmesg. However you are correct that the stock kernel detects it differently. Koen stock: [ 27.165642] m25p80 spi0.0: mx25l1605d (2048 Kbytes) current: [ 1.830166] m25p80 spi0.0: found mx25l1606e, expected sst25vf080bby Koen - Debian
Hi bodhi, when I run the ping test this is the output: T5325> ping 192.168.1.1 Using egiga0 device ARP Retry count exceeded; starting again ping failed; host 192.168.1.1 is not alive T5325> and the dhcp boot test results in this: T5325> dhcp BOOTP broadcast 1 BOOTP broadcast 2 BOOTP broadcast 3 BOOTP broadcast 4 BOOTP broadcast 5 BOOTP broadcast 6 BOOTP brby Koen - Debian