Thanks Carsten! I also plan (in 1-2 months) to have a raspberrypi as a semi-personal/semi-work server. I plan to use Gentoo and E. Thanks for sharing this.
On Thu, 1 Aug 2019 at 02:04, Carsten Haitzler <ras...@rasterman.com> wrote: > > On Thu, 1 Aug 2019 09:40:25 +1000 Daniel Kasak <d.j.kasak...@gmail.com> said: > > > On Tue, Jul 30, 2019 at 9:26 PM Carsten Haitzler <ras...@rasterman.com> > > wrote: > > > > > On Tue, 30 Jul 2019 09:38:02 +1000 Daniel Kasak <d.j.kasak...@gmail.com> > > > said: > > > > > > > On Mon, Jul 29, 2019 at 8:36 PM Carsten Haitzler <ras...@rasterman.com> > > > > wrote: > > > > > > > > > > > > > > https://www.enlightenment.org/_media/arch-linux-e-pi-setup.jpg > > > > > > > > > > This is a first cut at a pre-built Arch Linux disk image for the > > > > > Raspberry Pi with Enlightenment, EFL, Terminology and Rage all > > > > > installed from git (as AUR packages). > > > > > > > > > > > > > Awwwww nice :) My home server is a Cubox i4pro ( ARMv7-based ) which is > > > > currently running Gentoo ... but you can imagine the effort required to > > > > keep it up to date. I'll give this a spin and maybe contribute some > > > > Cubox-specific stuff. > > > > > > you might find that a challenge as i made this specifically for the pi - > > > it > > > relies on disk partitioning for the pi (fat /boot with /boot/config.txt > > > specifically for the pi bootloader) and a pi kernel and at least 1 or 2 > > > pkgs > > > specifically for the pi. :) you'd be better off starting from the alarm > > > tarball > > > and then applying the same customization i did. i actually have scripted > > > the > > > entire build so it's automated for me by now, but it does rely on my > > > personal > > > machine with arch on it and all the right dependencies installed to work > > > :) i > > > can share my scripts with you... :) > > > > > > > I see. OK I'll do some preparation work first. The last time I installed on > > this box, I remember the boot loader setup invoking tears :) This is a > > semi-personal/semi-work server too, so I don't want to be offline for *too* > > long. Has the boot loader stuff become slightly less cryptic these days? > > on arm server platforms - yes. it's uefi and you can boot it like any pc - > same > thing just with an arm architecture. can boot off thumbdrives/cd iso images > etc. ... but for these boards.... nope. every SoC maker will do their own > thing > so nothing will have changed for the pi or for you actually. :) that's why i'm > just warning you... it'll be less "simple" than you think. the rpi is > probably > right now the best documented and supported board+chip in this realm. uefi arm > systems are a whole new kettle of fish :) > > > Thanks for the offer of sharing your scripts. I'd love to see what you've > > got. I've just switched my laptop from Gentoo to Arch ( largely because of > > the ongoing issues I've had getting E+Wayland+EGL working on it ... and > > yes, this has fixed things ). It would be great to have the Cubox running > > on an Arch-based distro as well. > > oh. so getting over to arch from gentoo improved things for you? excellent. > i'm > often baffled by people having issues. i sit on arch and i have precious few > of > them :) well nowhere near what other people seem to have. :) > > not sure which cubox you have but: > > https://archlinuxarm.org/platforms/armv7/marvell/cubox > https://archlinuxarm.org/platforms/armv7/freescale/cubox-i > > i had assumed it was the latter with the imx6 and thus needing etnaviv mesa > driver support (and kernel too) which does exist these days. i've never tried > it though. > > > how is the etnaviv driver state for wayland/kms/drm/gles purposes? you may > > > want > > > to check into that first to look for blockers on the imx.6. > > > > > > > It was in a pretty immature state when I installed. I was able to bring up > > E+Wayland+EGL, but the whole thing was pretty unstable. Running in software > > mode was pretty slow. I ended up not having a monitor connected anyway, and > > making a mental note to check on things "regularly". There's been a lot of > > work on the etnaviv stack for the Librem 5 phone. I was hoping that > > improved things significantly for the imx.6. It was a minefield of > > competing drivers and out-of-date documentation last time :) > > i have heard that it has improved... but... i have never checked, so my take > would be - first just do raw arch on your cubox and get it up, build the aur > pkgs for efl-git and enlightenment-git etc. and ... see how it goes. do > whatever mesa/kernel driver wrestling there so you get a lay of the land first > by hand. then once you know just what is needed to make this work (what > bootloader bits are needed to pass the right parameters to get a fairly quiet > boot with kms/drm working etc.)... then it's time to look at the automation > thing i did... :) as raspberry pi's all work off micro-sd card by default > (some > can boot off usb storage now... but i have chosen to do the "only micro sd > card > media" path as it's simple and universal), then it's simple to just dd the img > file onto the sd card and get on with it. flashing emmc or even raw nand is a > whole new universe... (with emmc being far simpler generally than raw nand...) > > > -- > ------------- Codito, ergo sum - "I code, therefore I am" -------------- > Carsten Haitzler - ras...@rasterman.com > > > > _______________________________________________ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- _______________________________________ Raffaele Spinelli, Ph.D. Web: www.rafspiny.eu _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
