If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Announcement
Collapse
No announcement yet.
Announcement
Collapse
No announcement yet.
Bodhi Linux with Enlightenment desktop RFS working on mk908
The Enlightenment desktop is very resource efficient, so maybe the perfect desktop for this stick. Check it out if you feel like it, by following the excellent guides available on how to boot from SD.
The Enlightenment desktop is very resource efficient, so maybe the perfect desktop for this stick. Check it out if you feel like it, by following the excellent guides available on how to boot from SD.
cheers,
Lars
Hi there and thanks for sharing your experience.
I am interested what kernel are you using?
I also have an mk908v1 but it appears to be have been widely neglected by the rk linux developers.
The only working kernel for me is mmm123's 1.1.1
Cheers
Then I put the fb modules I compiled myself in this ramdisk and put both kernel and ramdisk in recovery.img
That was all, feel free to ask for links to the tools and commands if needed (I'm on OSX though, but the tools should work on linux too).
good luck!
Hey and thanks for your quick reply!
I see that you are using 3.0.72 sources, would you mind sharing your experience, does it offer any practical advantage over 3.0.36?
Also, I did try playing with building a kernel (at least managed to have a 720p working which is great for my poor eye sight, but never got to the stage of compiling ap6210 and rkwifi modules from sources. Somehow"
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- modules
and
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- modules_install
do not produce these two modules whatever source and config combination I tried (of course I have them enabled as by replacing "=yes" with "=m".
In my case and with my very limited knowledge this is the only way to keep playng, since, as a total amateur my absolute maximum would be to have modules inserted into mmm123's initrd, edit "init" script to insmod them, and then produce cpio for makebootimg). Any ideas?
I see that you are using 3.0.72 sources, would you mind sharing your experience, does it offer any practical advantage over 3.0.36?
I don't think there are any practical advantages, I remember omegamoon writing he moved to 72 to provide a common source for all of us to base future development on.
Also, I did try playing with building a kernel (at least managed to have a 720p working which is great for my poor eye sight, but never got to the stage of compiling ap6210 and rkwifi modules from sources. Somehow"
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- modules
and
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- modules_install
do not produce these two modules whatever source and config combination I tried (of course I have them enabled as by replacing "=yes" with "=m".
In my case and with my very limited knowledge this is the only way to keep playng, since, as a total amateur my absolute maximum would be to have modules inserted into mmm123's initrd, edit "init" script to insmod them, and then produce cpio for makebootimg). Any ideas?
I still have to work on wifi, my plan of attack is to first try this (precompiled modules):
although I'm a bit worried I'll get version mismatch errors.
In the future I'll also go to compiling them myself, I'll keep you posted how that works (could take a while though).
I don't think there are any practical advantages, I remember omegamoon writing he moved to 72 to provide a common source for all of us to base future development on.
I still have to work on wifi, my plan of attack is to first try this (precompiled modules):
although I'm a bit worried I'll get version mismatch errors.
In the future I'll also go to compiling them myself, I'll keep you posted how that works (could take a while though).
I did not open mine yet, but I ordered it quite recently so I'm guessing v3.
Which kernel sources are you using?
How is the recovery by Sin Huang working for you?
Hi Lars and thanks for your thorough reply!
It must be v.3, mine is almost 6 months old, in the meantime, v2 was released (with external antena), then v3. It seems they all have slightly different boards, v3 in particular, judging at least by android forums discussion.
I am using Alok's sources to keep compatibility with mmm123 config, as it was the one he recommended, and this kernel is the only one I use without any major issues (without the wifi though). Tried other sources too in order to figure out how to produce 6210 module, no success as yet. In the meantime, I use my own debootstrapped Precise with unity (which won't run on later ubuntu releases without hw accelaration anyway). And of course, Roline USB lan adapter takes care of the rest.
And yes, I did come across the rkwifi.ko link you provided, it was used by someone on v.1 board, but haven't tried inserting it into my recovery kernel (I believe it is an android module?)
Will try Sin Huang's recovery and let you know how it went on, but it is not going to be quite informative to you as, v3 is a different hardware.
And most interesting of all, did some google search on ap6210, it does not appear anywhere under Broadcom products, but seems to be related (derived) from its bcm4330 hardware. At least that is my understanding at this stage
Will keep you posted too.
Regards, Goran
Great!
I tried it, but I only got a command line premote, start enlightenment fail.I only need to run linux ,so I install a working Picuntu in my mk908 v3 from this link http://www.freaktab.com/showthread.p...l=1#post103556, and put bodhi linux in sd card, copy modules from the working picuntu in tu sd_card/lib/modules .
It's good that the number of linux distribution ported to be run on our ARM devices is growing. But according Bodhi official news they drop official ARMHF support:
Bodhi drops official ARMHF support
October 24th 2013
Effective immediately Bodhi is dropping official support for ARM devices. What does this mean?
We will no longer be advertising an ARMHF download link on our front page Updates to ARM images will be infrequent/not at all The ARM repo will be slow to receive package updates
The primary reason for this change is that maintaining ARM images is alot of work for very little return. Keeping one ARM image up to date is more work than maintaining all three of our desktop disc images. Every ARM image is used far less than any one of our desktop releases, so it just isn't worth the investment. A secondary reason for this is the closed source nature of ARM hardware. It is near impossible to get ARM hardware fully functional under a normal Linux distribution in a reasonable amount of time. Often by the time we get all the kinks worked out the hardware is so old it isn't truly useful any longer. We will continue to maintain an ARM discussion forum here. Users are free to ask questions about the existing images we have there (or post their own). I do hope to try and maintain ARMHF packages for E17 in our repo for Debian Wheezy moving forward still - but these updates will come slower than the desktop repos get updates.
Sorry if someone could consider my post as offtopic but let me share my experience in searching desktop linux distro for my ARM-based device (Minix Neo x7).
There are some deb-based linux distro (e.g. picuntu) what are running pretty good. But I prefer rpm-based one since I am much more experienced with such ones. On all my x86* CPU desktop PC and laptops I use OpenSUSE. I could run it (OpenSUSE 13.1) on my arm device too but I had been disappointed soon because of poor set of desktop packages provided (firefox, thunderbird, LibreOffice are still not available for ARM arch). So I continued my search and re-discovered ALT linux distro (some years ago I had tried it already but was not fully satisfied). There is Simply Linux branch for ALT linux distro which has ARM v7 arch support and provides a pretty good set of packages for desktop including ones I mentioned above. Simply linux supports Cubox (Marvell Armada 510 CPU based) "out-of-the-box". It was pretty easy to run it on Minix Neo x7 based on RK3188. Although Simply Linux rootfs provided for Cubox is focused on XFCE I had no problem to switched to LXDE (there is Enlightenment DE available as well).
If someone is interested in I can share my quick howto on running Simply linux with LXDE on Minix Neo x7.
Great!
I tried it, but I only got a command line premote, start enlightenment fail.I only need to run linux ,so I install a working Picuntu in my mk908 v3 from this link http://www.freaktab.com/showthread.p...l=1#post103556, and put bodhi linux in sd card, copy modules from the working picuntu in tu sd_card/lib/modules .
How can I make it work? Thanks
What kernel are you using? Can you try it with the recovery from post #3?
I did not touch the root fs at all. I remember reading somewhere that you have to copy all the files as root to preserve permissions (but I'm not even sure if I did that), maybe you can try that?
It's good that the number of linux distribution ported to be run on our ARM devices is growing. But according Bodhi official news they drop official ARMHF support:
Sadly that is true. But maybe if it becomes popular on those android sticks they will have a large enough user base on armhf and consider supporting it again?
Hey, im not sure why you guys dont have wifi. i compiled a kernel for the v1 board and wifi works fine. Only thing is i forgot to remove paranoid android network from the config so you have to add your user to inet and net_raw groups
What kernel are you using? Can you try it with the recovery from post #3?
I did not touch the root fs at all. I remember reading somewhere that you have to copy all the files as root to preserve permissions (but I'm not even sure if I did that), maybe you can try that?
Thanks, I tried that recovery and it work! And I also use the riwifi.ko module from picuntu for mk908 v3, work too.But I have trouble with running qt software.
Anyway, thanks again.
Hey, im not sure why you guys dont have wifi. i compiled a kernel for the v1 board and wifi works fine. Only thing is i forgot to remove paranoid android network from the config so you have to add your user to inet and net_raw groups
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.
By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.
Comment