Hey, so I tried to understand what is causing exectly the kernel panic. What I think is the core of the Problem: void __iomem *port_base; void __iomem *sgdma_base; Here you get with max_ports=2 an array of 2. And thow I have to write an Array and only a number. So I tried to change this ata@45900000 { compatible = "plxtech,nas782x-sata"; /* port sgdma core */by Peacemaker - Debian
I already tried this and then I get a kernel panic. (posted it earlyer). Maybe I had the wrong syntax in the dts(i), but I don't even see how the driver read the dts and switches between ports like the vendors driver. So there might be more to do. I guess this driver is written for single sata, as the SATA_OXNAS_MAX_PORTS is hardcoded and not readed from dts. But I'm happy aboutby Peacemaker - Debian
Big thanks to both of you. I'll see what I can do. But I have first to undersand how the driver works (old and new) to patch the second pord in. But this is the first time I try something like this. And your right with this vendor's sata, I've not beliefed how many warnings( used init's instad of pointers...) and errors there are to fix :-/by Peacemaker - Debian
Am I understanding you right: The 2 port option has to be integreated in the sata_oxnas driver, and not only activated? As I have absolutly no idea how to do this as the structure from the old driver is totaly diffrent to the newer one. If it's right, maybe - for me - it is easyer to integrade the vendors sata driver in the new kernel.by Peacemaker - Debian
Okay, I see what you mean. But how can I use 2. ports on one PHY? I see here nothing in the driver code nor I have any Idea how to insert the second correctly into the dts.by Peacemaker - Debian
WarheadsSE Wrote: ------------------------------------------------------- > It would probably be est to get the sata@ so that > it doesn't think there are actually 2 entries, but > that you can specify nr-ports 2, and it uses the > second port @ +0x10000 I tried yesterday something like that - maybe I did it wrong - and adaped the syntax for the krikwood 2 port devices.by Peacemaker - Debian
Thanks to both of you. I tried to add to dts: sata@45910000 { status = "okay"; }; dtsi: sata@45910000 { compatible = "plxtech,nas782x-sata"; /* port sgdma core */ reg = <0x45910000 0x100>, <0x459B0010 0x10>, <0x459E0000 0x2000>, /* phy descriptors (optional) */ <0x44900000 0x0C>, <0x50000000 0x1000>; intby Peacemaker - Debian
-bodhi, Thanks for your input :-) I know and I allready have a pogoE02 but I liked the opinon of a dualcore and 2sata's and to all of it the KD20 had just a nice price ( 40€) . Back to topic: I have already looked at these lines but have only a vage Idea what to extract from the gpl sources. Somehow I have the feeling that the whole sata driver in Kref's repo is hardcodeby Peacemaker - Debian
Year, I thought maybe, I can set up first booting: up everything direct from HDD, so there is no need modify the nand. But that I get this is harder than expected. The new kernel (Kref's) is running, but I need both SATA. I tried to patch in the vendor-sata driver, but its linked many other files, so not quite easy. And with the new Sata driver direct from Kref's repo I don'by Peacemaker - Debian
Yes, I booted the stage1 und uboot from the HDD, and then I can't activated & boot from Sata/HDDby Peacemaker - Debian
The disk is not spinning up, but it is running anywhy as I boot from the disk. QuoteMy immediate thought is that your recompiled uboot doesn't have the necessary options to enable the power lines? Somethink like this is are my thoughts as well, as I got within the compiling with only sata boot enable an error: /u-boot-vendor/u-boot-256M/u-boot/board/oxnas/ox820.c:178: undefined refereby Peacemaker - Debian
Are there more envs the the normal Bootargs? If I interupt the boot process and try to set up: RStage-1 Bootloader 2014-09.24-14:52:42 Attempting to set PLLA to 875MHz ... plla_ctrl0 : 0x0000020A plla_ctrl1 : 0x00348000 plla_ctrl2 : 0x0068008B plla_ctrl3 : 0x000000F8 PLLA Set Setup memory, testing Reading disk 00 Sector : 0x0000009A Hdr len: 0x00027E98 Hdr CRC: 0xby Peacemaker - Debian
I tested a bit the old U-Boot: I got it working booting stage1 + uboot dirct from hdd, but the uboot don't init the hdd, to load kernel & initrd from hdd. Maybe someone has an idea what I forgot, within the compiling.by Peacemaker - Debian
Bodhi, do you really think this will work? The nas320 is a krikwood divice and not like the kd20 a oxnas? I think I'll just use for the first time the Vendor stage1+uboot. As the new U-Boot need's a lot of changes as well (and I'm not realy good in modifying kernel/uboot jet) , but I see this would be a better choice.by Peacemaker - Debian
@WarheadsSE So I got now all the sources from Shuttle: http://data.shuttle.eu/~upload/omninas/KD20_20121127.zip Okay, do you think it is better to use the "new" uboot with the vendors settings. Or modifiy the "old" Vendor U boot ?by Peacemaker - Debian
Ok, now I see what you mean.by Peacemaker - Debian
Nope, allready tried this and not working :-(by Peacemaker - Debian
Thanks for your help, but: QuoteSo did you compile either mine or kref's u-boot? if you did, try to regenerate your Linux-2.6.32.fake+ uImage with tools/mkimage from that u-boot build. This error usually caused by a badly generated uImage (file system was not sync properly, nfs timeout, mismatched checksum,…). If you don't have 2013.10 u-boot mkimage, I'll post the binary here.by Peacemaker - Debian
Okay, maybe someone has an idea what is wrong here, this this kernel boot perfect with vendors uboot, but with bodhi's or kref's Uboot I got this: OX820 # ide reset Reset IDE: Bus 0: OK Device 0: Model: SAMSUNG HD204UI Firm: 1AQ10001 Ser#: S2H7J9CB207281 Type: Hard Disk Supports 48-bit addressing Capacity: 1907729.0 MB = 1863.0 GB (-38by Peacemaker - Debian
I' see. I just meant, just flash or boot your SPL and your U-Boot, it don't work out of the box. So I need to do some changes to the U-Boot, as set Ram to 256, maybe fix the ethernet. And somehow I can't load my patched 2.6.31 Kernel & Initrdby Peacemaker - Debian
Thx for this, but oob it is not working :-|, and only working without ethernet :-(by Peacemaker - Debian
So, I tried to set up on the KD20 a proper small NAS/Homeserver based on Debian. As it is the same SoC as the PogoPro / Classic i thougt it would be much easyer :-), so this thread is more to get maybe some more people with this device, and some progress to get everything working. So far what I have done so far is: Set up a Wheezy_Rootfs, initrd, with a patched vendors Kernel, and bootby Peacemaker - Debian
Hello, I'm running Debian on Pogoplug E02, and planned to set up an VDR server. I bought a Logilink DVB-T stick, with an AS102 Chip and nieher get in running on E02 with 3.14.0-kirkwood-tld-2 . Niehter on my Debian based Media Center amd64 with 3.13 Kernel. At my Notebook (Ubuntu) and PC (Arch), I pluged the stick in, installed the firmware and it worked. There the module dvb-as102by Peacemaker - Debian