Installed nginx, because is needs less ram and cpu as apache. PHP seems to work (phpinfo) After setting up php-fusion it's not possible to stay logged in. When clicking something I'm getting logged out. The config files looks correnct, the cache directory is also available and accessable I'll check with other PHP applications but I think the behaviour will be the same (cby pengu - Debian
this makes sense. kernel 4.4 will be the next LTS one The only thing which is fixes in 4.3 kernels is the ext4 problem which occures on my NAS devices with kernels newer than 4.2.1. And perhaps this also fixes some issues with WD Green HDDs on some firmware versions (00J).by pengu - Debian
for me, it's working with stock and newer U-Boot.by pengu - Debian
this is also not fully correct. I've seen some Pogo E02 labeled as Pogo Pro (both labeled "P24" on bottom) and this is the Kirkwood version without S-ATA Only the V3 (pogoplug BIZ. labeled as pogoplug PRO on bottom ) has S-ATAby pengu - Debian
@ingmar_k could be that ther is something messed up in kernel 4.3. The given message persists in stable kernel 4.3 but I found no solution yet. I haven't testet this on my goflex net so far. marvell_cesa 24913 0 des_generic 16866 1 marvell_cesa mv_cesa 11324 0 but it get's loaded you can test this (now dtb files included) but I tby pengu - Debian
I'm using kernel 4.3.0-rc7 now and later let's see what's going on with the final 4.3.0. as seen with 4.3-rc1 I'm seeing this: [ 17.602771] MV-CESA:Could not register sha1 driver [ 17.620416] MV-CESA:Could not register hmac-sha1 driver and the S-ATA settings were not used from previous config so has to be reset.by pengu - Debian
I have the same box and ethernet is working fine. You don't have to set the MAC adress via /etc/network/interfaces, it's taken from the U-Boot env correctly. Perhaps it could be a cable/switch/router issue?by pengu - Debian
Sorry that I haven't worked on it yet but it seems the same issue as on another box I have (iomega StoreCenter ix2-dl) Perheps is's solved here when it could be solved on this box. pengu Wrote: ------------------------------------------------------- > because of a second WD Red I can put two Toshiba > 2,5 '' HDDs in this box. > But I noticed that the poweby pengu - Debian
news news :-) the one minute stall at boot isn't related to NAND. I've built all NAND related stuff as module and its still stalling for one minute after initialing the watchdog. I've seen something on the NSA310 when the ethernet port needs more time to come up (DHCP and stuff). One solution is to let udev not create the 70-persistant-net.rules file. When this file isnby pengu - Debian
after upgrading from Debian Wheezy to Debian Jessie, I'm running systemd. Perhaps I should switch to sysvinit?by pengu - Debian
a view weeks ago I owned a Pogo v3. All seems working fine: - updating U-Boot - installing Debian 3.17 rootfs - updating to kernel 4.1 - upgrading to Debian Jessie I've recognized the following: On Debien Jessie, the LED doesn't go off. There is also something in the log shows that the second core doesn't gets off (only on Debian Jessie). So I decided to test it agby pengu - Debian
I'm using kernel 4.2.1 on all my devices without problems. I decided to test newer kernels (4.2.2 / 4.2.3 ) but now the trouble starts. First I noticed that I couldn't get files read from my samba share via mobile phone (es file manager) no error message, just no files or directories are visible. Same on my pc. Accessing the files via ssh on the box(es) sometimes work, sometimesby pengu - Debian
this doesn't work because this device has only 32 mb flash. whatever I do with the mtdparts it stalls at boot for some time because the flash can't accessed corectly. I'll see later with another ix2-200 (with correct mtdparts) Now I also have the ix2-dl which has similar issues with NAND access on debian. but this is another thing and because of other problems I'll openby pengu - Debian
http://pastebin.com/raw.php?i=rLi4GDaZ new try with up-to-date kernel (4.2.1-kirkwood-rm-1) and blacklisted r8169 module mostly the same read/write rates.. sorry that I'm still using SMB file transfer .. I'm more or less out of timeby pengu - Debian
bodhi Wrote: ------------------------------------------------------- > I think you have network problem, check your > cable, switch,... this doesn't occur on the NSA325v2 and perhaps NSA310s but it could caused by the same problen as mentioned earlyer (another thread, pn) ATM I don't think so because the mentioned things (massive packet loss, reset problem of the atherosby pengu - Debian
I'll check this .. following situation now: file transfer seems to hang sometimes but resumes after a while. In bad situations, the modification fixing the dhcp issue seems to help mv643xx_eth_port mv643xx_eth_port.0 eth0: tx timeout mv643xx_eth_port mv643xx_eth_port.0 eth0: link down mv643xx_eth: Set the PHY back to auto-negotiation modeby pengu - Debian
shure .. the two 2,5'' HDDs were up fine. The transmit timeout problem seens to occour while copying small filesby pengu - Debian
because of a second WD Red I can put two Toshiba 2,5 '' HDDs in this box. But I noticed that the power off issue still remains. I'm trying now the newest kernel + NSA320s dtb .. let's see... Edit same as before :-( [ 1316.847951] ------------[ cut here ]------------ [ 1316.852563] WARNING: CPU: 0 PID: 3764 at drivers/power/reset/gpio-poweroff.c:45 SyS_reboot+0x14c/by pengu - Debian
bodhi Wrote: > It's in your bootlog :) > > mtdparts=nand_mtd:0x100000@0(uboot)ro,0x20000@0xA0 > 000(uboot_env),0x300000@0x900000(kernel),0x1400000 > @0) > I get a kernel panic wich this because of an unexpected character "("by pengu - Debian
I'll do so. As I sead, this doesn't solve the problem of reading / writing to the flash in debian. Edit I couldn't find the right mtdparts line, so I try to get this from my next ix2-200 but I don't know when it will arrive.by pengu - Debian
I said that there could be something hosed ... If I add the kernel partition I cannot start because of an unexpectat character (kernel panic) for me, it's enough to have the 2 partitions and get the U-Boot env readable / writableby pengu - Debian
bodhi Wrote: ------------------------------------------------------- > > /etc/fw_env.config should be like this: > > > > > > /dev/mtd1 0 0x20000 > > > > > > This looks wrong: > > > [ 2.144241] 0x0000000a0000-0x0000000c0000 : > "uboot_env" > could be but why? I don't see anything in "mtdparts&quoby pengu - Debian
yes ;-) [ 0.000000] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootfstype=ext4 mtdparts=orion_nand:0x100000@0(uboot)ro,0x20000@0xA0000(uboot_env) ... ... [ 1.873362] nand: device found, Manufacturer ID: 0xad, Chip ID: 0x75 [ 1.879794] nand: Hynix NAND 32MiB 3,3V 8-bit [ 1.884195] nand: 32 MiB, SLC, erase size: 16 KiB, page size: 512, OOB size: 16 [ 1.891by pengu - Debian
thanks bodhi if I set this or not, no nand partitions were recognizedby pengu - Debian
you don't have to update to newer U-Boot. for this to work, you need to enbed the DTB es seen in chapter 4bby pengu - Debian
there are two versions of this box: - the "dl" (diskless) version which hast many in common with the ZyXEL NSA325(v2) - the "ix2-200" which comes with two HDDs (Raid 1) which can compared with the iConnect. First let's have a look at the default U-Boot env: (perhaps I've messed something up it was late and minicom is sometimes strange) http://pastebin.com/by pengu - Debian
JohnnyUSA Wrote: ------------------------------------------------------- > > [ 14.495495] __nand_correct_data: > uncorrectable ECC error > [ 14.500828] __nand_correct_data: uncorrectable > ECC error > [ 22.805560] __nand_correct_data: > uncorrectable ECC error > [ 22.810897] __nand_correct_data: uncorrectable > ECC error > [ 22.831596] blk_updby pengu - Debian
I got the "old one" ix2-200 with 1,0 GHz CPU. Debian is running fine, but I think there is something wrong with the DTB. The box has only one LAN port but the kernel recognizes two. [ 0.000000] Linux version 4.2.0-kirkwood-tld-1 (root@tldDebian) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 PREEMPT Mon Aug 31 23:12:00 PDT 2015 [ 0.000000] CPU: Feroceon 88FR131 [56251311] revby pengu - Off-Topic
thanks bodhi, but you have to make shure that the "r8169" isn't built into the kernel build it as module as I have done it so you can simply blacklist it if necessary when both modules are enabled, the r8169 is preferedby pengu - Debian