Hi, i just installed the new kernel on my V3 classic box and have some issues with the MAC address. I have the uboot env setup for the MAC address: root@sch~# uname -r 4.14.176-oxnas-tld-1 root@sch:~# fw_printenv ... dtb_file=/boot/dts/ox820-pogoplug-classic.dtb ethact=dwmac.40400000 ethaddr=52:3b:20:9c:XX:XX ... However when it boots the kernel uses a different MAC address:by schnee - Debian
Thanks Bodhi! i tried compiling your u-boot version. It compiles if it set to nand boot (not tested the result yet), but when i try to build it for SATA i end up with error: common/built-in.o: In function `initr_ide': /root/u-boot-oxnas/common/board_r.c:617: undefined reference to `board_start_ide' ld.bfd: BFD (GNU Binutils for Debian) 2.28 assertion fail ../../bfd/elf32-arm.by schnee - uBoot
Thanks Bodhi. I understand that it is considered as rescue mechanism, however i am using it in some cases where i was unable to fix the NAND..... Can you point me to a guide and probably a config example which could help me to start playing around with uboot? Thanksby schnee - uBoot
Hi, i was playing around with the pogoplug V4 in uboot and found the nice sntp (and other) commands to setup time during boot. I tried that on the Pogoplug V3, but the exisiting SATA uboot version does not support these commands. I looked at https://forum.doozan.com/read.php?3,16017,page=1 for creating a new uboot to boot from SATA (not for flashing), but it is not very straight forward forby schnee - uBoot
schnee Wrote: ------------------------------------------------------- > I am trying to follow the instructions from the > 1st post. Prepared everything and now i am ready > to boot. However i get an error: > > U-Boot SPL 2013.10-g3a0f380-dirty (Jul 26 2014 - > 14:31:34) > Boot device: SATA > Attempting to set PLLA to 850 MHz ... > plla_ctrl0 : 0000020a &by schnee - Debian
echowarrior108 Wrote: ------------------------------------------------------- > Just a thought, is it the power supply? Don't think so. I use the same powersupply when attaching it to my desktop and it works fine. Also the SPL is loaded from the disk.by schnee - Debian
I am trying to follow the instructions from the 1st post. Prepared everything and now i am ready to boot. However i get an error: U-Boot SPL 2013.10-g3a0f380-dirty (Jul 26 2014 - 14:31:34) Boot device: SATA Attempting to set PLLA to 850 MHz ... plla_ctrl0 : 0000020a plla_ctrl1 : 00330000 plla_ctrl2 : 0065008b plla_ctrl3 : 000000f1 PLLA Set Bus 0: OK Device 0: ** Fileby schnee - Debian
I looked into the issue and found a few post related to this it on other forums. The root cause is that systemd actually mounts the drives during boot bus private, not visible to other users. To change this behavior an update to the config is needed: Option 1: create a file /etc/systemd/system/systemd-udevd.service with contents .include /usr/lib/systemd/system/systemd-udevd.service Mounby schnee - Debian
bodhi Wrote: ------------------------------------------------------- > Yes. If you use systemd, the automount is > different. Do you have any documentation how different it is, how to make it work with systemd? Or the only way to make it work again to switch back to sysV init? I am not a huge fan of systemd, but it seems to be the future....by schnee - Debian
The 2 drives are the same both on how they are attached to the system (sata to USB converter) and on the file system, one has ext4 (works) other has 1 ext4 and 1 ext2 (both are not working). The difference i found looking in deeper: the working one uses sysV init (-rwxr-xr-x 1 root root 35328 Feb 12 2017 /sbin/init) while the not working one uses systemd (lrwxrwxrwx 1 root root 20 Apr 8 12:by schnee - Debian
I am trying to figure out what is causing the issue that the attached USB drives are not mounted during boot on my Pogoplug Pro. It worked before the debian 9.8 upgrade with the udev rules I am using from https://forum.doozan.com/read.php?2,24139. Some system info: root@sch:/media# cat /etc/debian_version 9.8 root@sch:/media# uname -r 4.4.176-oxnas-tld-1 root@sch:/media# cat /etc/udby schnee - Debian
Thanks. Already installed and works fine!by schnee - Debian
Thanks bodhi. For now i downgraded the kernel and that solved the issue. Waiting for the new release.by schnee - Debian
Hi, i have weird issue since i upgraded my pogoplug to debian 8 from debian 7. The box boots and works fine, however reboot does not work. After issuing the reboot command the box goes down normally but then freezes before the actual reboot and a power-cycle is needed to start booting again. The last messages on the serial: ... systemd-shutdown[1]: Sending SIGKILL to remaining processesby schnee - Debian
coolvi Wrote: ------------------------------------------------------- > All right. :) > > Just in case, I have changed the value of > /proc/sys/vm/swappiness and > /proc/sys/vm/min_free_kbytes on my pogo v3 not to > encounter out of memory. > > Here is my additional settings for > /etc/sysctl.conf: > > # set swappiness (default 60, the more swappineby schnee - Debian
coolvi Wrote: ------------------------------------------------------- > Hi schnee, > > I guess that it seems like an issue related to out > of memory. Can you check out /proc/pagetypeinfo or > /proc/meminfo when you reproduce it ? > If you can't log-in on the console, you'd better > set-up a swap device on your pogo to increase the > amount of availablby schnee - Debian
HI, today my pogo became unresponsive (no replyon pings etc) so i looked at the serial console and i see the following message repeating in every ~second: ICMPv6: ndisc: ndisc_alloc_skb failed to allocate an skb Tried to log in on the console, but it did not work. Any idea what could cause this? (kernel is 4.4.117)by schnee - Debian
echowarrior108, How do you connect the serial cable to the pogoplug? Can you check what you see on the serial if the sata drive is not connected? How do you power the sata drive? Thanksby schnee - Debian
You can take a look at my sata 'installer" from this post: https://forum.doozan.com/read.php?2,16044,23122#msg-23122 I will have it updated to the latest kernel and rootfs soon.by schnee - Debian
I think i found the issue. Compared the initramfs from the working 4.4.79 and from 4.4.89 and found a diff, which relates to disk mounting: -./lib/udev/rules.d/91-media-by-label-auto-mount.rules The 4.4.79 initramfs does not have this line, while the non working 4.4.89 (and 4.4.117) has this line. If i remove the file from /etc/udev/rules.d folder and generate a new initrd.img and create aby schnee - Debian
bodhi, thanks for posting your boot log. As the system works with 4.4.79 but not with 4.4.89 and 4.4.117 i am now trying to find the difference in the bootlog, if it helps to chase down the issue My rootfs data (for the working 4.4.79) root@sch:~# uname -a Linux sch 4.4.117-oxnas-tld-1 #2 SMP PREEMPT Sun Feb 25 01:33:22 PST 2018 armv6l GNU/Linux root@sch:~# cat /etc/debian_version 9.by schnee - Debian
Just tested with the latest 4.4.117 but have the same result as with 4.4.89 IDE device 0: Model: Samsung SSD 840 PRO Series Firm: DXM06B0Q Ser#: S1ATNSAF507409D Type: Hard Disk Supports 48-bit addressing Capacity: 244198.3 MB = 238.4 GB (500118192 x 512) 4124792 bytes read in 560 ms (7 MiB/s) 4595317 bytes read in 626 ms (7 MiB/s) 7075 bytes read in 1by schnee - Debian
bodhi, yes i boot directly from SATA and yes my uImage and uInitrd are correct. I had some time and i downgraded the kernel to 4.4.79, recreated uImage and uInitrd and magic everything works fine. To double check i downloaded the 4.4.89 image again and reinstalled it, generated new uImage and uInitrd files, but the result was sam kernel panic. For reference here is the 4.4.79 boot logby schnee - Debian
bodhi, the USB drive was created for the test.... The initial issue was with my 1TB harddrive. I used the same USB drive, same partition with different filesystems. With fat and ntfs it was booted fine, with ext[2,4] it caused kernel panic on boot.... The system was working fine with the previous rootfs, the problem started after creating the new Debian 9 rootfs.by schnee - Debian
Tryed a few things tonight, but issue is still not solved: - tried booting with systemd instead of init -> sam kernel panic - tried booting with fat, ntfs, ext and ext4 drive (ext4 created with the extra options -O ^64bit) with fat and ntfs drive attached on boot system booted, with ext2 and ext4 it failed. example with fat IDE device 0: Model: Samsung SSD 840 PRO Series Firm: DXM06B0by schnee - Debian
I used you latest rootfs image to create drive. ~$ cat /etc/debian_version 9.3 This is the fstab file: # /etc/fstab: static file system information. # # <file system> <mount point> <type> <options> <dump> <pass> /dev/sda2 / ext4 noatime,errors=remount-ro 0 1 tmpfs /tmp tmpfs defaultsby schnee - Debian
bodhi, i don't think this problem is related to the power. The drive has a external power supply. Also i tried with a standard 8G USB stick. If the stick format was FAT32 than it booted, if the format was ext4 it caused the same issue. As i changed both the kernel and the root filesystem at the same time, i will do some more testing next week: - downgrade the kernel to 4.4.54 and testby schnee - Debian
Hi bodhi, first of all thanks for the latest rootfs and kernel files! I just had time now to start upgrading my systems and i want(ed) to give them a fresh start. I rebuilt my sata disk builder script with the new rootfs and kernel 4.4.89. It works fine and the pogo boots with some warning messages but generally works fine. But when i boot with my USB to SATA device plugged the boot ends up wiby schnee - Debian
Here is a picture with the wire soldered to the pcb. I also used hot glue to fix it to the PCB.by schnee - Debian
So i think i figured it out after some tests. There is an RC circuit connected to the reset pin of the CPU. The RC circuit provides the reset impulse at powerup, making sure that the CPU powers up properly. After power up in holds the pin at ~3.3V (VCC). If the pin is bought down to GND and then released the CPU resets and the box reboots. See pictures for the location of the capacitor (C154)by schnee - Debian