Sorting out oxnas upgrade issues -- Guidance please

[wxtofly]

I've been having nothing but frustration as Arch has evolved but Arch for oxnas has
remained with the WarheadSE kernel 2.6.31.6_SMP_820.

Aside from the move of modules from /lib to usr/lib which was only a minor headache,
the changes surrounding bootup have led to completely inconsistent documentation as some has the old ways and others have the new ways and none tell what the issues might be for the hybrid oxnas system.

If there is no stable kernel that supports systemd, why is systemd in the ArchLinuxARM-oxnas-latest.tar.gz ?

Is there some mechanism to track exactly what is happening at boot / init, to see which parts are being invoked?

Does anyone understand the nuances and differences well enough to make guidelines for the hybridized rootfs?

Any such guidance would be greatly appreciated.

TJ wxtofly

[WarheadsSE]

Because systemd contains udev. You like having devices work, and kernel modules load, right?

[wxtofly]

@WarheadSE

Yes of course, but what is the deal with systemd, new kernels and oxnas 8020?

I finally got my kirkwood device working with peripherals when I upgraded to a 3.2 kernel. Since I can't do that with oxnas 8020, I'm still struggling to try to find the magic spells that will actually turn on and run my Raylink 3070 wireless device on a WPA secure network.

Unfortunately, udev is covered by Clark's third law for me as it seems is wireless connectivity.

TJ

[chat1410]

Per this response:

$this->bbcode_second_pass_quote('WarheadsSE', 'I')t's a matter of I have done work, but I am limited in what I actually know about the underlying hardware, even with the NDA. PLX is not interested in updating the kernel, and actually have sold the unit that produced the hardware family and wrote the kernel!

My efforts along with others have resulted in kernels that are supportive of systemd, however, they are NOT stable kernels, and have as-yet-untraced faults that cannot be deemed "acceptable". Right now, efforts are underway to get uboot partition & usb support all the way to 2013.01-rc's. We've yet to get USB working fully, and we've got a few issues with the sata read (yay! nasty hack by PLX). The reason this is important is it will remove the need to have the kernel in NAND, which is one of the many things I despise about the way the system support stands as it is now.

[WarheadsSE]

That's fairly close chat1410.

The major hiccup is the version of the kernel as it stands does not support the necessary CGROUPS and journal needs. Moving to a much newer kernel provide that, but getting PLX's horrible "the hardware is fine, fix it in software" hacks working in newer code is infuriatingly painful.

[wxtofly]

Thank you both for the responses and the hard work you do. I am thinking that the oxnas platform for me will just remain one that I use wired. As you have developed it so far, I can do one of my projects with it fine and I will plan to use other platforms for my other projects.

If this board is an orphan of the manufacturer, then it probably isn't worth much more effort.

My biggest frustration comes not from the board and software, but from difficulties knowing which bits and pieces of advice on the forums should work and not knowing why if they don't.

Again, thanks for all your hard work and my apologies if I seemed to be whining too much.
TJ

[sethjvm]

$this->bbcode_second_pass_quote('wxtofly', 'I')f this board is an orphan of the manufacturer, then it probably isn't worth much more effort.

[godfather007]

Hi,

is there a quick "step-up" how to get the pogo-plug (oxnas 820) running with kernel 3.1 (ie WarHeadsSE repo)?

I've bought 2 of the pinky ones (for a USB DAC, squeezelite for LogitechMediaServer) and only 1 is running the debian image for it.

I would love to see the less valued one (the oxnas) to fulfill this task.


I've found that WarheadsSE has created a git repo. Is it hard to make this run on it?

I think there are a lot of vortexbox-users that would love to have this oxnas working only for that.


Thanks,

Martijn