Show all posts by user
Discuss all things Debian on your device
Re: JFFS2 filesystem support for Pogoplug V3 - 2 months ago
Thank you! I will wait till the next releaseby schnee - Debian
Re: JFFS2 filesystem support for Pogoplug V3 - 2 months ago
Sorry if i was not clear. I am trying to do the same as I did with the Pogo V4, describer here: https://forum.doozan.com/read.php?2,132241 The problem is when I try to mount the NAND as JFFS2 filesystem example mount -t jffs2 /dev/mtdblock1 I get the error that it is unknown file system. I am not sure how to add the support to the device.by schnee - Debian
JFFS2 filesystem support for Pogoplug V3 - 2 months ago
Hello, I am trying to utilize the onboard FLASh on the Pogoplug V3 board to load the kernel from it. I tried it with the latest kernel (5.4.224) and also with previous ones, but it seems that JFFS2 file system support it missing. root@pogo:~/ ls -l /lib/modules/$(uname -r)/kernel/fs total 64 drwxr-xr-x 16 root root 4096 Nov 20 19:30 . drwxr-xr-x 11 root root 4096 Nov 20 19:31 .. drwxby schnee - Debian
Re: No mtd block devices under Linux Kernel 5.17.4 Kirkwood - 7 months ago
I guess i should read the release notes next time more carefully.... I just read the red USB warning I added the module to /etc/initramfs-tools/modules, then regenerated the initrd file: cd boot update-initramfs -u mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-5.17.4-kirkwood-tld-1 -d initrd.img-5.17.4-kirkwood-tld-1 uInitrd Now everything works fiby schnee - Debian
No mtd block devices under Linux Kernel 5.17.4 Kirkwood - 7 months ago
Hi, Yesterday I upgraded one of my Pogo V4 box to the latest 5.17.4 kernel. When i tried to mount the mtd block devices i received an error, that it does not exists. Looking into the dev list they are indeed missing: root@server:~# uname -r 5.17.4-kirkwood-tld-1 root@server:~# ls /dev/m* /dev/mem /dev/mtd0 /dev/mtd0ro /dev/mtd1 /dev/mtd1ro When i downgrade the kernel to 5.15.5 eby schnee - Debian
Pogoplug V4: Boot Kernel from NAND - 8 months ago
I made a setup to boot my Pogoplug V4 kernel from NAND. The reason was that i wanted to attache a SATA multiplier, but when it is attached the Pogoplug cannot boot from it. It has to use either USB or SD card for the boot, which i don't like. This setup allowed me to boot from SATA with the multiplier attached. WARNING !!!! This is a destructive change! It will overwrite the content ofby schnee - Debian
Re: Pogoplug v3 PIP and PIP3 segementation fault - 11 months ago
Thanks for the suggestions echowarrior108 nad bodhi. Upgrading to Debian 11 resolved the issue: root@server:~# pip3 Usage: pip3 <command> Commands: install Install packages. download Download packages. uninstall Uninstall packages. freeze Output installed packages in requirements formby schnee - Debian
Re: Pogoplug v3 PIP and PIP3 segementation fault - 11 months ago
Thanks for the update. It seems that you are on a different Debian verison (bullseye<>buster). here are the same commands and results from my box: root@schtorrent:~# cat /etc/debian_version 10.11 root@server:~# uname -r 5.4.179-oxnas-tld-1 root@server:~# python3 --version Python 3.7.3 root@server:~# apt install python3-pip Reading package lists... Done Building dependency treeby schnee - Debian
Re: Pogoplug v3 PIP and PIP3 segementation fault - 11 months ago
bodhi Wrote: ------------------------------------------------------- > Hi Schnee, > > > Yes, i installed it with apt install > pip3 > > > I tried to search for this package and it is not > in Debian repo. Wondering if you have a different > repo added to your /etc/apt/sources.list ? > > https://packages.debian.org/search?suite=all&arch=any&amby schnee - Debian
Re: Pogoplug v3 PIP and PIP3 segementation fault - 11 months ago
bodhi Wrote: ------------------------------------------------------- > Schnee, > > How did you install PIP3? was it from Debian repo? Yes, i installed it with apt install python3-pip I installed flexget while the box was running a 4.x.x kernel Edit: corrected apt command pip3 -> python3-pipby schnee - Debian
Pogoplug v3 (oxnas) OpenBSD SSH server starts slowly (solution) - 11 months ago
HI, after a long time i did a clean install for one of he Pogo V3. I used Debian-4.14.180-oxnas-tld-1-rootfs-bodhi.tar.bz2 (17 May 2020). When i rebooted i realized that the SSH server takes very long time to start (4+ minutes): [....] Starting OpenBSD Secure Shell server: sshd[ 267.217536][ C0] crng init done After searching the net i found https://daniel-lange.com/archives/152-Opensby schnee - Debian
Re: Pogoplug v3 PIP and PIP3 segementation fault - 11 months ago
Thanks Bodhi! Unfortunatelly it did not help: root@schnee:~# pip3 Segmentation fault root@schnee:~# flexget Segmentation fault Here is the trace with the same error [ 248.669091] 8<--- cut here --- [ 248.672839] Unhandled fault: page domain fault (0x81b) at 0xb6efe000 [ 248.679854] pgd = 6eeb95c9 [ 248.683238] *pgd=669b4831, *pte=622c955f, *ppte=622c9c7e [ 248.690178by schnee - Debian
Re: Pogoplug v3 PIP and PIP3 segementation fault - 11 months ago
Thanks, will check with the next kernel. Meanwhile just to confirm goind back to 4.x.x kernel solves the issueby schnee - Debian
Re: Pogoplug v3 PIP and PIP3 segementation fault - 11 months ago
So i just built a new system from scratch (latest rootfs), still have the error with the new kernel and the dump is still the same. [13425.208517] 8<--- cut here --- [13425.212267] Unhandled fault: page domain fault (0x81b) at 0xb6f98000 [13425.219279] pgd = 7ee1738c [13425.222663] *pgd=67b6f831, *pte=62c0a55f, *ppte=62c0ac7e [13425.229601] Internal error: : 81b [#11] PREEMPT SMP ARMby schnee - Debian
Re: Pogoplug v3 PIP and PIP3 segementation fault - 1 year ago
Finally i found the SATA boot disk creating script. Here is a link https://mega.nz/file/YRVhzQBa#jnu1JbxtMf8JStWZ0_m70AudAjfUSi-fLqhmWyxGIhQby schnee - Debian
Re: Pogoplug v3 PIP and PIP3 segementation fault - 1 year ago
I did some test on another box and it seems to be kernel related. I moved to 5.4.101 and i started the get the segmentation faults. Upgraded to debian 10 and it did not help. oot@schcamus:~# cat /etc/debian_version 10.9 root@schcamus:~# pip Segmentation fault root@schcamus:~# uname -r 5.4.101-oxnas-tld-1 root@schcamus:~# Going back to kernel 4.14.198 fixes the issue root@schcamusby schnee - Debian
Pogoplug v3 PIP and PIP3 segementation fault - 1 year ago
Hi, I have the latest kernel running on my Pogoplug V3 box. I tried both pip and pip3, but both generates segfault. root@scht:~# uname -r 5.4.101-oxnas-tld-1 root@sch:~# cat /etc/debian_version 9.13 root@sch:~# pip3 Segmentation fault root@sch:~# python --version Python 3.5.3 Here is the segmentation fault trace from the logs: [ 373.945011] 8<--- cut here --- [ 373.948761by schnee - Debian
Re: Ethernet problem with Linux Kernel 4.14.176 Oxnas (OX820) Pogo V3 - 2 years ago
bodhi, thank you for the quick fix. It works perfectly on my box.by schnee - Debian
Re: Ethernet problem with Linux Kernel 4.14.176 Oxnas (OX820) Pogo V3 - 2 years ago
I looked at the man page and was unable to find the network option you are using (but could be wrong). Do you see anything in dmesg?by schnee - Debian
Re: Ethernet problem with Linux Kernel 4.14.176 Oxnas (OX820) Pogo V3 - 2 years ago
bluzfanmr1 , this is how i added and it works fine: auto lo eth0 iface lo inet loopback iface eth0 inet dhcp hwaddress ether 52:3b:20:XX:XX:XXby schnee - Debian
Re: Ethernet problem with Linux Kernel 4.14.176 Oxnas (OX820) Pogo V3 - 2 years ago
bodhi, i checked bdinfo in uboot and the MAC address is the same what is in the env variables ethaddr 52:3b:20:9c:11:51 If i remove the ethaddr variable and reboot the board the MAC address remains empty. Unfortunately i got this board without the case and with modified firmware with the above MAC. i have no idea how to recover the Cloud Engine assigned MAC address. Anyway, i think iby schnee - Debian
Re: Ethernet problem with Linux Kernel 4.14.176 Oxnas (OX820) Pogo V3 - 2 years ago
Thanks bodhi! I do remember changing the ethaddr variable during the installation ~1 year ago, but i could be wrong. Anyway i don't have the case with the sticker so i have no idea what was the original MAC for this box. Is there any way to figure it out? With the 4.4.X kernel version this MAC address worked fine. You mentioned that you may have to fix this in DTS, so i feel that curreby schnee - Debian
Ethernet problem with Linux Kernel 4.14.176 Oxnas (OX820) Pogo V3 - 2 years ago
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
Re: New uBoot for PogoPlug V3 question - 3 years ago
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
Re: New uBoot for PogoPlug V3 question - 3 years ago
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
New uBoot for PogoPlug V3 question - 3 years ago
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
Re: Tutorial of native sata boot for pogoplug pro - 3 years ago
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
Re: Tutorial of native sata boot for pogoplug pro - 3 years ago
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
Re: Tutorial of native sata boot for pogoplug pro - 3 years ago
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
Re: USB Automount does not work on Boot (Pogoplug Pro) - 3 years ago
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