he bodhi. i'm using zram on all my small ram devices to "enlarge" RAM before using slow swap. Have you tought about updating the rootfs with the zram option by default? its just adding this script to startup: ZRAM on Debianby Sash - Debian
sorry u r right! my fault...used wrong dtb ... root@debian:~# lspci -vvv 00:01.0 PCI bridge: Marvell Technology Group Ltd. 88F6281 ARM SoC (rev 02) (prog-if 00 ) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latenby Sash - Debian
this is k4.8 maybe there is a problem with the dtb....its detected as "OF: fdt:Machine model: Seagate GoFlex Net" but i installed the ix4-200d.dtb from your link...maybe there is the problem located... Starting kernel ... Uncompressing Linux... done, booting the kernel. [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 4.8.0-kirkwood-tld-1 (root@by Sash - Debian
this is k4.6 root@debian:~# dmesg [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 4.6.0-kirkwood-tld-1 (root@tldDebian) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 PREEMPT Wed May 18 03:54:14 PDT 2016 [ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f [ 0.000000] CPU: VIVT data cache, VIVT instruction cache [ 0.000000] Maby Sash - Debian
hi so 1st tried the k4.6 dtb with k4.8, but no 2nd sata chip not any lspci output. then downgraded to k4.6 with also no sata and pci output. also i see no eth interfaces with k4.6 and k4.6 dtb!by Sash - Debian
ok, will do when i get home in the evening.by Sash - Debian
yep there seems to be a problem with the bus, else there should be an output when calling lspci, right!? i have posted the dmesg above.by Sash - Debian
hmmm makes sense. installed pciutils but there is no output on probing the bus...? any suggestions?by Sash - Debian
yes console is attached. ide is not installed...which package is this or in which is it included? the stock system works well with all 4 drives. btw its a bit different in the handling though. the uboot indentifies drive 3 and 4 an tries to boot thy system from a md raid1 located on these 2 drives. the drives 1 and 2 are activated via kernel while booting. atm with your fdt only driveby Sash - Debian
bodhi Wrote: ------------------------------------------------------- > Sash, > > I'm really not worrying about upstream until > before I retire from this forum :) ok, i see *g* > > I don't think the magic number number error has > anything to do with arcNumber/machid. Usually, > when you try to boot stock OS on NAND, its u-boot > does a checksby Sash - Debian
check! btw debian testing doesnt contain the ix4 fdt up to now. so debian (especially the kernel) doesnt know anything about the the device right now. are you pushing this info upstream or someone else? bbtw. do you know a working machid/arc# so that de clean debian install can be tested? the currect debian kernel errors with bad magic number. thx sash p.s. sorry for the last postby Sash - Debian
he guys! i'm facing a little problem with my box. i guess other have the same problem but nobody recognized it so far. i uses the latest rootfs and the 4-8 kernel. running fine so far, but is see the 2 of the 4 sata ports missing. as is can see the port isnt loaded. is this missing from the fdt file?by Sash - Debian
just FYI: i also have uploaded the differen versions of the Iomega ix4-200d U-boot to this topic: klickby Sash - uBoot
ok so this units (cloud/non cloud) use direct env access. root@ix4-200d-BO0J8W:/# fw_printenv bootdelay=1 baudrate=115200 loads_echo=0 rootpath=/mnt/ARM_FS/ CASset=min MALLOC_len=1 ethprime=egiga0 bootargs_root=root=/dev/nfs rw bootargs_end=:::DB88FXX81:eth0:none image_name=uImage console=console=ttyS0,115200 mtdparts=nand_mtd:0xa0000@0x0(uboot),0x00010000@0x000a0000(param),32by Sash - Debian
bodhi Wrote: ------------------------------------------------------- > However, to make it a functional u-boot, we need > u-boot tools in Debian to print/set u-boot envs. > We'll need to find blparam binary in stock OS. > > If you could, connect with serial console and boot > to stock OS. The blparam binary should be > somewhere in stock rootfs. If you could, sby Sash - Debian
just for the record. these are the 2 different iomega storcenter ix4-200d uboot versions the different revisions of the unit was delivered with. i can also provide a wholeflash backup of the cloud und noncloud version on request if there is any demand.....by Sash - Debian