As far as I remeber the 325 fan has only two wires so I don't think it can be controlled in RPM. I think the only way is to change the supply voltage via its controller board as a function of the internal temperature.by miazza - Debian
Every time I write something on this forum I learn something. Thank you !by miazza - Debian
bodhi Wrote: ------------------------------------------------------- > You could also create a folder and move them > there > > > cd /boot > mkdir -p kernel > mv -i linux-image-*.deb *.tar *.bz2 ./kernel > Why not. the point here is that at every kernel update the mess inceases :)by miazza - Debian
Thank you. I supposed it was like that but I wanted to be sure. Everything went smooth. In the boot folder now I have a mess of files: config-5.17.4-kirkwood-tld-1 linux-5.17.4-kirkwood-tld-1.patch uEnv.txt zImage-5.13.6-kirkwood-tld-1 .. dts linux-dtb-5.17.4-kirby miazza - Debian
By default in rootfs the function to shutdown when pressing the power button is present (I did not do anything and this feature is present since the beginning). I tried to find out where this is coming and I found the button-switch.sh that is ecactly this script. However I cannot manage to have the halt or the reboot (I tried different timing for the pressing but it always shutdown and never rby miazza - Debian
I'm trying to update my kernel following the instructions Updated 27 Apr 2022. At the point 3 I get the error that flash-kernel is not installed: root@debian:/boot# apt-get remove flash-kernel Reading package lists... Done Building dependency tree... Done Reading state information... Done Package 'flash-kernel' is not installed, so not removed 0 upgraded, 0 newly instaby miazza - Debian
Thank you to all. I tried both and they both have worked fine. miazzaby miazza - Debian
I've seen you anwer too late, I forgot to tick the e-mail for reply :) Yes, of course I need to manually mount sata-rootfs before to tar. I'm doing it right now and it seems to work... tar process running and bz2 file is growing in the destination. Indeed can I make a live tar as for your post without having any problem during the tar process ?by miazza - Debian
Hollo everyody. I have read all the wiky for the back-up but I have not found a wicky for a Backup rootfs using tar command from SATA to USB without dismounting the HD (there is a similar one for cloning but I would prefer a tar file). Before to make the wrong thing I would like to ask if this will work: 1) boot as normal with last u-boot from SATA rootfs 2) change rootfs LABEL to SATA_roby miazza - Debian
My net console seems to be no properly working. I've sent the following: fw_setenv serverip 192.168.1.19 (my pi fixe IP) fw_setenv ipaddr 192.168.1.200 (free IP in the dhcp) I sent the command: nc -l -u -p 6666 I made a reboot and I only get the following: root@Raspberrypy-4:/home/pi# nc -l -u -p 6666 U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:42:03 -0700) ZyXEL NSA325by miazza - uBoot
bodhi Wrote: ------------------------------------------------------- > miazza, > > As I mentioned, > > > If you had installed u-boot to NAND, you would not have this problem. > > I think it is time to flash it for real. Just make sure you save the stock mtd0 as instructed, so you can restore back to stock when and if you > > decide to do that.. Yes ,by miazza - Debian
Hello bodhi, I have tried to modify uEnv.txt as from you suggested: root@debian:~# cat /boot/uEnv.txt devices=ide usb disks=0 1 2 3 4 5 6 7 ethaddr=EC:43:F6:40:84:91 custom_params=init=/bin/systemd load_dtb_addr=0x2c00000 But it seems u-boot still looks only at USB for loading uEnv.txt loading envs from usb 0 ... ** Bad device usb 0 ** Here the full boot log: U-Boot 20by miazza - Debian
And finally I found the trick: It seems that the u-boot is not automatically loading the uEnv.txt from the IDE drive. I made: setenv set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts init=/bin/systemd' and now systemd is back working as well as all the other stuff. Now the question is why uEnv.txt is not loaded automaticcally from u-boby miazza - Debian
Thank you bodhi... also for your patience :) Now I have no access to the NAS (I'll be away few days for Easer). I will apply all your advise when come back. The tricky point is the systemd initialization. For the USB rootfs I relied in the uEnv.txt that is loaded during UART Boot : custom_params=init=/bin/systemd The same uEnv. txt is saved in the SATA rootfs (it is a back-upby miazza - Debian
bodhi Wrote: ------------------------------------------------------- > =============== > > This rootfs is a very small rootfs, with only > necessary packages installed. It's a learning > vehicle for beginners, and a minimal rootfs for > advanced users to configure as they like. It is > not a full and heavy system like Ubuntu. If you > don't like gettinby miazza - Debian
Hello bodhi, when booting from USB rootf is perfectly working with systemd installed according to intruction from the forum and everything works smooth, buttons, led, samba , systemd. See attached log. U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:42:03 -0700) ZyXEL NSA325 2-Bay Power Media Server SoC: Kirkwood 88F6282_A1 DRAM: 512 MiB WARNING: Caches not enabled NAND: 128 MiB *** Warninby miazza - Debian
This is the full log: pi@Raspberrypy-4:~ $ sudo su root@Raspberrypy-4:/home/pi# kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2017.07-tld-1.nsa325.mtd0.kwb -p Sending boot message. Please reboot the target...| Sending boot image... 0 % [......................................................................] 1 % [......................................................................]by miazza - Debian
I made a system back-up with the tar procedure of the USB rootfs and installed it in the first partition of the SATA HD in bay 2. SATA HD is made of two partitions: . 1 ext3 15 G for the rootf - 2 ext 3 52 G for data storage I restored the tar in partition 1 above and I labelled it as rootf- I unplugged the usb rootfs I rebooted in UART mode System started as expected but several probleby miazza - Debian
This is what happened: root@debian:~# e2fsck /dev/md0 e2fsck 1.46.2 (28-Feb-2021) /dev/md0 has been mounted 291 times without being checked, check forced. Pass 1: Checking inodes, blocks, and sizes Inode 78121674 extent tree (at level 1) could be shorter. Optimize<y>? yes Inode 78122555 extent tree (at level 1) could be shorter. Optimize<y>? yes Inode 78122582 extent treeby miazza - Debian
It seems that the MAC is correct now: ifconfig -a eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.104 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::ee43:f6ff:fe40:8491 prefixlen 64 scopeid 0x20<link> ether ec:xx:xx:xx:xx:xx txqueuelen 1000 (Ethernet) RX packets 298 bytes 33624 (32.8 KiB) RX eby miazza - uBoot
habibie Wrote: ------------------------------------------------------- > Do you see the above last line with a warning? It > recommends you to manually clean your partition > table (that may already be dirty). Just run > e2fsck device where the device is the > partition. Do a man e2fsck to find out more > information what this utility can do. For me, I > just usuallyby miazza - Debian
Dear Mijzelf : THANK YOU. I lost two nights without asking and trying myself :)by miazza - Debian
Mijzelf Wrote: ------------------------------------------------------- > Quote > loop0 > ext4 1.0 > 304a4dce-e926-4081-a5f7-a308c5d320cf 1.2T > 34% /srv/nsa32 > sda > |-sda1 > | ext2 1.0 > 0f1b4806-89db-4c26-8eae-ab98b5a023a9 > `-sda2 > linux_ 1.2 NSA325:0 > > 20f70310-7a8f-ddcd-bby miazza - Debian
YES. BEFORE root@debian:/etc/network# lsblk -f NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUN TPOINT sda |-sda1 | ext2 1.0 0f1b4806-89db-4c26-8eae-ab98b5a023a9 `-sda2 linux_ 1.2 NSA325:0 20f70310-7a8fby miazza - Debian
Thanks bodhi. How shoul it like interfeces ? Right now I have: auto lo eth0 iface lo inet loopback iface eth0 inet dhcp hwaddress ether xx:xx:xx:xx:xx:xx This does not work and reports the same error as before.by miazza - uBoot
bodhi Wrote: ------------------------------------------------------- > > > > Warning: egiga0 MAC addresses don't match: > > Address in SROM is ec:43:f6:40:84:91 > > Address in environment is xx:xx:xx:xx:xx:xx > > > > Try setting it at u-boot prompt > > > setenv ethaddr xx:xx:xx:xx:xx:xx > U-Boot 2017.07-tld-1 (Sep 05by miazza - uBoot
In UART boot the default MAC Address is automatically set. I have created a uEnv.txt file for setting the right one but I get: Warning: egiga0 MAC addresses don't match: Address in SROM is ec:43:f6:40:84:91 Address in environment is xx:xx:xx:xx:xx:xx How can I fix this in UART boot ?by miazza - uBoot
Hi, today I'm fighting with samba :) The first point is indeed to mount my HDD that was already mounted with the stock system. After some study I found this command to work: mount -o rw,loop,offset=$((2048*512)) /dev/sda2 /srv/nsa325/ The point is that in no way I could manage to automount it at the system boot. I tried to put the command in rc.local but is does not work Iby miazza - Debian
Hello bodhi. Finally everything seems working well. Now the IP address is assigned (there was a cable non well attached to the 10/100 switch). I made swap file and full system upgrade. For the time being I'm still with UART Boot until I get a stable configuration. Now a few questions: 1) The push button is not working for the switch-off ; is there any trick to configure it ? 2) Iby miazza - Debian
Yes. Thank you bodhi, I realized the mitake and did the job correctly. Now booting correctly :) Only issue is now that DHCP is not found ... may be the MAC address is not set ? root@Raspberrypy-4:/home/pi# kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2017.07- tld-1.nsa325.mtd0.kwb -pby miazza - Debian