bodhi Wrote: ------------------------------------------------------- > theliquid, > > No idea why! since these are not main line > packages, dont know what to make of this. RPi > rootfs is a prebuilt heavy rootfs so it has many > things installed already. Ok, thanks anyway. Nvm I switched to a RPi v2 for my home server due to 1GB of RAM :)by theliquid - Debian
bodhi Wrote: ------------------------------------------------------- > theliquid, > > >. But with Kernel 4.1 on my > > Pogoplug I get error message like this: PAM > > audit_log_acct_message() failed: Operation not > > permitted. > > Please post the full error text in the log. This is the only error I get; its in auth.log and error.log. I canby theliquid - Debian
Is it possible, that there is something wrong with pam_unix.so module? I'm trying to use /usr/lib/openvpn/openvpn-plugin-auth-pam.so with openvpn. I did this on 2 x86 machines on Ubuntu which worked fine. But with Kernel 4.1 on my Pogoplug I get error message like this: PAM audit_log_acct_message() failed: Operation not permitted. Any clue? Edit: on Raspberry Pi it also works flawleby theliquid - Debian
@bodhi Ok, thanks. I'm looking forward to it. Beside the encryption the kernel works flawlessly.by theliquid - Debian
Thanks a lot! I'll try the new kernel now. Btw how does the ext4 encryption work?by theliquid - Debian
Upgrade to Jessie worked flawlessly; I am on Kernel 4.0 with my PogoV1.by theliquid - Debian
Debian Jessie comes with 3.16 kernel, so 3.17 should be fine, AFAIK I'm currently upgrading my PogoV1 and will report back if everything worked.by theliquid - Debian
Update: 3G seems to work (can't test it more currently): Jan 1 01:00:41 PogoplugV3 dhclient: isc-dhclient-4.2.2 Jan 1 01:00:42 PogoplugV3 dhclient: isc-dhclient-4.2.2 Jan 1 01:03:07 PogoplugV3 pppd[2253]: pppd 2.4.5 started by root, uid 0 Jan 1 01:03:07 PogoplugV3 pppd[2253]: Using interface ppp0 Jan 1 01:03:07 PogoplugV3 pppd[2253]: Connect: ppp0 <--> /dev/ttyUSB0 Jan 1by theliquid - Debian
Thanks, bodhi! I'll try it asap!by theliquid - Debian
Hey bodhi! I just tested the kernel and it's working fine. Huawei modem gets detected normally and wifi also works. But I can't connect with wvdial. It seems ppp_generic module is missing. Aug 27 21:35:56 PogoV3 pppd[7844]: Couldn't open the /dev/ppp device: No such device or address Aug 27 21:35:56 PogoV3 pppd[7844]: Please load the ppp_generic kernel module. Aug 27by theliquid - Debian
bodhi Wrote: ------------------------------------------------------- > Kernel linux-3.16.0-oxnas package was uploaded. > Please see 1st post for download link. Hi bodhi! Sorry I was off for some days, but anyway thanks for the new kernel. I'll try it asap. I have several Huawei modems (E160, E172 etc.), I think it's all the same driver/module. I don't know which itby theliquid - Debian
Update: my 2 devices with bad blocks worked fine. My other PogoV4 has also got a bad block: root@debian:~# dmesg | grep Bad [ 5.131787] Bad eraseblock 80 at 0x000000a00000 Is it safe to flash too? Edit: nvm, I figured it out myself. It was safe to flash, because the bad block is at 10M :)by theliquid - uBoot
bodhi Wrote: ------------------------------------------------------- > @theliquid, > > Nothing to be concerned. From now on, if you get > more bad blocks then yes, keep watch on them. And > your bad blocks are in the stock FW > (kernel/rootfs) area so they do not affect u-boot > (1st 1M). Only later if you want to flash your > kernel and/or rootfs to NAND then thby theliquid - uBoot
This would nice! I'd like to use my Pogoplug V3 as a WiFi / 3G rescue box.by theliquid - Debian
I have bad blocks: Pogoplug V1 dmesg | grep -i 'bad' [ 19.766086] Scanning device for bad blocks [ 19.838307] Bad eraseblock 637 at 0x000004fa0000 [ 20.158075] Bad eraseblock 3589 at 0x00001c0a0000 and on my Pogoplug V4 dmesg | grep -i 'bad' [ 1.897690] Scanning device for bad blocks [ 2.014965] Bad eraseblock 1006 at 0x000007dc0000 Any way to fix tby theliquid - uBoot
bodhi, is it possible to support drivers/kernel modules for wifi and huawei 3g dongles in future versions of this kernel?by theliquid - Debian
Better don't use Owncloud. It's far too ressource hungry. I tried it on my homeserver and it took too much ressources and was too slow. I finally switched to Seafile, which also works properly on the RPi.by theliquid - Debian
Ok, I answered it myself: installed new kernel and it works like a charm. Tun is now supported!by theliquid - Debian
Hi bodhi, thanks for the new kernel build. Is tun device now supported in the kernel?by theliquid - Debian
Ok, thanks. With the label it's working now!by theliquid - Debian
Nvm, I got it working to go past the initial boot. The problem was that Gparted screwed up partitions. I recreated them with fdisk and now it works. But I can't ping the machine. Don't know whats wrong. How can I investigate it? With serial console? Current netconsole output is: U-Boot 2011.12 (Apr 08 2012 - 19:03:41) Cloud Engines-Pogoplug v4/Mobile:MMC version arm-none-linux-by theliquid - Debian
Ok, I'll try to use this label method. I already tried rootfs on SD as ext2, ext3, ext4 and on USB as ext2, ext3, ext4. (I changed the setting in envs everytime) Got always the same result. (with a bit different log output) The strange thing is that the rescue system boots properly. Btw. I have the Pogoplug Mobile.by theliquid - Debian
Hi! I just got my Pogoplug V4 Mobile. And flashing the uboot worked properly. But I can't get it booting the Debian rootfs. I formated it to Ext3 and set the correct env var (usb_rootfstype=ext3). But it doesn't boot. Here is the netconsole ouput: U-Boot 2011.12 (Apr 08 2012 - 19:03:41) Cloud Engines-Pogoplug v4/Mobile:MMC version arm-none-linux-gnueabi-gcc (Sourcery G++ Litby theliquid - Debian
Ok, thanks for the reply. No need to rush. I still have my Pogoplug V1 :)by theliquid - Debian
After hacking around a bit with this kernel I realized that I'm missing compatibility for tun devices. It seems tun.ko is missing. Is there any way to support it?by theliquid - Debian
Thank you for the reply, bodhi! Just to be sure I set usb_rootfstype=ext4 and all worked fine.by theliquid - uBoot
Ok, thanks it worked! When I want to change my rootfs to ext4 (instead of ext2), I just have to chance usb_rootfstype=ext2 to usb_rootfstype=ext4, right? (I already reformatted the usb device to ext4).by theliquid - uBoot
Ok, I'll try it here. I want to upgrade the u-boot on my Pogoplug V1. Which U-Boot I have to use? The Dockstar? My current u-boot from 2012 is made for the Dockstar: U-Boot 2011.12 (Feb 12 2012 - 21:33:07) Seagate FreeAgent DockStar SoC: Kirkwood 88F6281_A0 DRAM: 128 MiB WARNING: Caches not enabled NAND: 512 MiB In: serial Out: serial Err: serial Net: egiga0by theliquid - uBoot
[...] Nvm, I started with flashing the kernel and it works like a charm. Linux 3.14.0-kirkwood-tld-2 #1 PREEMPT Sat Apr 19 02:02:09 PDT 2014 armv5tel GNU/Linuxby theliquid - Debian
Ok, thank you. I'll try it tomorrow. I need to be more careful with this device, because it is very important in my LAN. I'll report back if it worked then.by theliquid - Debian