FatdogArm Alpha [CLOSED]
But I already have a Mele1000A and I do not see it much available anymore with all the extra (computer like goodies VGA etc ) being dropped in later versions.
BTW this is being typed on a MeLe 1000A, have not even turned on my other computers in days! It took the wall plug for my Apple iPhone charger so the Mele is doing double duty as a charger!
Strange that it does not see the iPhone as a USB file like standard puppylinux (I do not recall trying the iPhone with regular FD64, so may not be a bug per-say)
Im looking for an cheap usable tablet for the one switch project effort.
BTW this is being typed on a MeLe 1000A, have not even turned on my other computers in days! It took the wall plug for my Apple iPhone charger so the Mele is doing double duty as a charger!
Strange that it does not see the iPhone as a USB file like standard puppylinux (I do not recall trying the iPhone with regular FD64, so may not be a bug per-say)
Im looking for an cheap usable tablet for the one switch project effort.
Starhawk, unfortunately, 01micko is right
Compared to the ARM world, x86 world suddenly looks very homogenous. PAE or non-PAE discussions suddenly feels like kid's talk.
ARM world is very different from x86. In ARM world, every ARM device is different - it has different CPUs (with different capabilities which can't even be probed by software), different chip features (which can't be probed by software), different peripherals (which can't be probed by software) ... in x86 world, every laptop or desktop may be different but *almost all* of them have PCI busses and these features can be probed by software - thus enabling auto-configuration. There is no such thing on ARM
Case in point - a few posts earlier Ted Dog asked how to access his SATA disk and I said, load the sw_ahci_platform module. But FD-Arm already comes with udev, and udev is supposed to automatically load modules when a particular is detected, right? Right? Yes --- except that udev on ARM can't probe that the platform has SATA support to begin with thus it must be loaded manually.
Thus every single device will need work. FD-Arm is currently configured for Mele A1000 but it will definitely needs re-configuration for Mele M5. Have you seen this link: Adopting FatdogArm?
How about others? Look here: Official Fedora Arm 19 release notes and here: Fedora Arm 19 remixes. As you can see, almost every other ARM platform gets its own distribution ... Same story with Debian too.
Coming nearer to home, Mavrothal is currently adapting FD-Arm for OLPC. No, not for OLPC, for XO laptop. No, not for XO laptop, it is for XO-4 laptop. When done, he will probably come out with a specific image for XO-4 laptop. This makes it easier for people to get the image, dd it into a USB stick and boots it up on XO-4. But someone has to prepare for it. And so that it is noted, the image for XO-4 will not work on XO-1.75 although both are ARM platforms and both are using Marvell CPU (different model though). It is that specific. (I will be the one working on XO-1.75 laptop). 01micko did the same for Pandora - without his work FD-Arm *will not boot* on it. He may release his own adapted version of FD-Arm sooner or later.
To conclude: the only sure fire way to get FD-Arm (or any other ARM distro out there) to work on a specific ARM device is to get someone to test, adapt and package FD-ARM for that device. Only then you can just get a downloadable image with a few easy steps to follow (dd to SD card, etc).
If not, then one must take the path less travelled. I can be your guide and tell you pointers and perhaps some generic steps, but since I do not own the specific device you have in mind I will not be able to tell you exactly the steps to do or why certain things won't or can't work (well, this is true in Fatdog64 too); but before we even being the path, as Micko pointed out above, one must be equipped with certain skills which can be learned along the way. The only consolation I can offer is that the journey will be fun (if you like that sort of fun ).
====
@Ted Dog,
From the spec, the Onda looks like it uses standard A10, so that's quite identical to what Mele A1000. The only thing to worry about is the "script.bin", the touchscreen driver, and the wireless driver.
@Starhawk,
The T004 is based on A10s (which is sun5i, not sun4i like A10), so it will require a different boot loader, a different kernel, and its "script.bin". It's a stick so we can forget about the touchscreen, but still beware of the wireless driver.
----
To know what driver is being used for these devices, install Android "Terminal" app, launch it, and from there do "ls /sys/modules". You will get an indication of all the drivers being used. If looking for touchscreen, do "cat /proc/bus/input/devices" and peruse it.
To copy the script.bin, look at here: http://linux-sunxi.org/Submitting_Boards, the easiest is the second from the bottom ("script.bin from nanda mount"), but it requires that your device is rooted (only root can mount /dev/block/nanda for good reasons). If it is not rooted you must use other (much more) convoluted way, unfortunately.
And without the right script.bin, the chance that FD-Arm will work on the device is approximately zero.
----
@Starhawk, no I'm not advocating you to get Mele A1000. It is an old device, as Ted Dog pointed out it may not even be avalable anymore; nor do I want to tell you to get anything outside your purchasing power.
But I do hope you understand the issues - whatever device you choose, it's going to be complicated (and devices like CX-01 multiply the complications by many times to the point that it isn't worth it anymore).
cheers!
Compared to the ARM world, x86 world suddenly looks very homogenous. PAE or non-PAE discussions suddenly feels like kid's talk.
ARM world is very different from x86. In ARM world, every ARM device is different - it has different CPUs (with different capabilities which can't even be probed by software), different chip features (which can't be probed by software), different peripherals (which can't be probed by software) ... in x86 world, every laptop or desktop may be different but *almost all* of them have PCI busses and these features can be probed by software - thus enabling auto-configuration. There is no such thing on ARM
Case in point - a few posts earlier Ted Dog asked how to access his SATA disk and I said, load the sw_ahci_platform module. But FD-Arm already comes with udev, and udev is supposed to automatically load modules when a particular is detected, right? Right? Yes --- except that udev on ARM can't probe that the platform has SATA support to begin with thus it must be loaded manually.
Thus every single device will need work. FD-Arm is currently configured for Mele A1000 but it will definitely needs re-configuration for Mele M5. Have you seen this link: Adopting FatdogArm?
How about others? Look here: Official Fedora Arm 19 release notes and here: Fedora Arm 19 remixes. As you can see, almost every other ARM platform gets its own distribution ... Same story with Debian too.
Coming nearer to home, Mavrothal is currently adapting FD-Arm for OLPC. No, not for OLPC, for XO laptop. No, not for XO laptop, it is for XO-4 laptop. When done, he will probably come out with a specific image for XO-4 laptop. This makes it easier for people to get the image, dd it into a USB stick and boots it up on XO-4. But someone has to prepare for it. And so that it is noted, the image for XO-4 will not work on XO-1.75 although both are ARM platforms and both are using Marvell CPU (different model though). It is that specific. (I will be the one working on XO-1.75 laptop). 01micko did the same for Pandora - without his work FD-Arm *will not boot* on it. He may release his own adapted version of FD-Arm sooner or later.
To conclude: the only sure fire way to get FD-Arm (or any other ARM distro out there) to work on a specific ARM device is to get someone to test, adapt and package FD-ARM for that device. Only then you can just get a downloadable image with a few easy steps to follow (dd to SD card, etc).
If not, then one must take the path less travelled. I can be your guide and tell you pointers and perhaps some generic steps, but since I do not own the specific device you have in mind I will not be able to tell you exactly the steps to do or why certain things won't or can't work (well, this is true in Fatdog64 too); but before we even being the path, as Micko pointed out above, one must be equipped with certain skills which can be learned along the way. The only consolation I can offer is that the journey will be fun (if you like that sort of fun ).
====
@Ted Dog,
From the spec, the Onda looks like it uses standard A10, so that's quite identical to what Mele A1000. The only thing to worry about is the "script.bin", the touchscreen driver, and the wireless driver.
@Starhawk,
The T004 is based on A10s (which is sun5i, not sun4i like A10), so it will require a different boot loader, a different kernel, and its "script.bin". It's a stick so we can forget about the touchscreen, but still beware of the wireless driver.
----
To know what driver is being used for these devices, install Android "Terminal" app, launch it, and from there do "ls /sys/modules". You will get an indication of all the drivers being used. If looking for touchscreen, do "cat /proc/bus/input/devices" and peruse it.
To copy the script.bin, look at here: http://linux-sunxi.org/Submitting_Boards, the easiest is the second from the bottom ("script.bin from nanda mount"), but it requires that your device is rooted (only root can mount /dev/block/nanda for good reasons). If it is not rooted you must use other (much more) convoluted way, unfortunately.
And without the right script.bin, the chance that FD-Arm will work on the device is approximately zero.
----
@Starhawk, no I'm not advocating you to get Mele A1000. It is an old device, as Ted Dog pointed out it may not even be avalable anymore; nor do I want to tell you to get anything outside your purchasing power.
But I do hope you understand the issues - whatever device you choose, it's going to be complicated (and devices like CX-01 multiply the complications by many times to the point that it isn't worth it anymore).
cheers!
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
The BeagleBone Black is like the device you stated for the same general price range, and is designed from the ground up as a hacker playground, while I like the price points for cheap china crap,especially hackabl3 ones, they come with a host of nagging problems that can't be solved without lot effort, and a technical friend that speak Chinese.
http://beagleboard.org/
It's from Texas so there may still be a language problem, for you foreigners Doesn't affect me... I just wish I could pick one up in person.
http://beagleboard.org/
It's from Texas so there may still be a language problem, for you foreigners Doesn't affect me... I just wish I could pick one up in person.
5V 2A wall warts are available in more unlikely places, My mele1000A has one and my older PSP wall wort, and PSP car charger runs MeLe, a old USB powered HUB wall wart, wireless Access Point, and antique 100/10T based router, (+/- reversed) Solar battery charger, rechargeable adapter that PROVEN to charge iPhones that includes different tips [This is best as a pass-thro, and can be had cheaply]
Could a swore that I saw the IT BBB included power, MiniHDMI and usb cable, check around there are MANY suppliers, three I've done business with before (for decades)
Could a swore that I saw the IT BBB included power, MiniHDMI and usb cable, check around there are MANY suppliers, three I've done business with before (for decades)
Check this out, its really close to MeLe and offers the same ports and slightly newer Alwinner A13
http://www.mouser.com/new/olimex/olimex-A13olinuxino/
did not see price so....
http://www.mouser.com/new/olimex/olimex-A13olinuxino/
did not see price so....
Here's the product page with price.
http://www.mouser.com/ProductDetail/Oli ... f8G7WT37Q7
Just under $80.
http://www.mouser.com/ProductDetail/Oli ... f8G7WT37Q7
Just under $80.
Speeding up ARM compilation - Fatdog64 and FatdogArm building together:
http://jamesbond3142.no-ip.org/wiki/wik ... singDistcc.
http://jamesbond3142.no-ip.org/wiki/wik ... singDistcc.
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
Great find just think what more than one host would do to speedup ARM development.jamesbond wrote:Speeding up ARM compilation - Fatdog64 and FatdogArm building together:
http://jamesbond3142.no-ip.org/wiki/wik ... singDistcc.
Well that depends ... http://jamesbond3142.no-ip.org/blog/?viewDetailed=00054Ted Dog wrote:Great find just think what more than one host would do to speedup ARM development.
You can definitely use more than one host, I've tried that too. And it works.
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
Seems like a complex way of solving the out of RAM issue, but go for it, that QEMU method would be useful for many other people and sort of like Aboriginal
For me I'd find a old sata hardrive and configure a FAT swap partition to solve that.
I had a picked up a seagate hybrid drive for use with my MeLe1000 last year, but it's sitting in a old Windows Vista machine storing files to large to backup without splitting into BluRay disks.
Ordered a new pack of BluRays discs, and will clear (backup) some other harddrives from storage, and free that drive for its original use.
For me I'd find a old sata hardrive and configure a FAT swap partition to solve that.
I had a picked up a seagate hybrid drive for use with my MeLe1000 last year, but it's sitting in a old Windows Vista machine storing files to large to backup without splitting into BluRay disks.
Ordered a new pack of BluRays discs, and will clear (backup) some other harddrives from storage, and free that drive for its original use.
Ted, the problem isn't want of or lack of swap space; I've already configured a large swap partition on external USB disk. The problem is VM trashing (wikipedia link) which you can only address by adding more memory, or in this, case by getting one of these or these (scroll down, then check right-most column). Unfortunately they are out of my budget for nowTed Dog wrote: For me I'd find a old sata hardrive and configure a FAT swap partition to solve that.
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
I'm just wondering why my connection is flakey (wireless on the Pandora) when I connect from the kernel commandline string. Most of the time it doesn't connect at all, with the as mentioned earlier "disassociated" (reason 1) message after it was authenticated. Then when it does connect it only stays up a few minutes and then dies.
I made a simple script with the same commands that are in system-init script for wireless, using udhcpc, and it seems to work fine, as long as I kill wpa_supplicant before hand. It's been up a few hours now.
No big deal, just a bit perplexing, for me at least.
I made a simple script with the same commands that are in system-init script for wireless, using udhcpc, and it seems to work fine, as long as I kill wpa_supplicant before hand. It's been up a few hours now.
No big deal, just a bit perplexing, for me at least.
Puppy Linux Blog - contact me for access
Is the wlan0 a module, or do you built it in to the kernel? Either way, sometimes the driver needs more time to initialise (3 seconds of waitdev may not be enough). When you lost the connection does dmesg say anything about it?01micko wrote:I'm just wondering why my connection is flakey (wireless on the Pandora) when I connect from the kernel commandline string. Most of the time it doesn't connect at all, with the as mentioned earlier "disassociated" (reason 1) message after it was authenticated. Then when it does connect it only stays up a few minutes and then dies.
Also - if it is certain kind of atheros, you may want to disable hardware encryption ...
Alpha2 will feature barebone wireless configuration thanks to Mav's pointer to tinycore's wifi.sh scriptI made a simple script with the same commands that are in system-init script for wireless, using udhcpc, and it seems to work fine, as long as I kill wpa_supplicant before hand. It's been up a few hours now.
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
retrovol-arm
I can not get the volume panel applet to work in fd-arm, so i compiled retrovo 0.8 and works fine.
Here it is.
Here it is.
- Attachments
-
- retrovol-0.8_armv7hl.pet
- volume panel applet, compiled for atmv7 with hard FPU
- (115.93 KiB) Downloaded 537 times
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==
mavrothal,
I made this insanely simple volume control with the raspberry pi in mind a few months back. Doesn't work on Pandora as alsamixer reports no adjustments
Anyway, take a look if you want here.
----------------------
The error in dmesg I get is that it is all good, associated, then deauthenticated (reason=1) , and this can happen when I try it from my script too. So, it's like I said crappy driver/firmware I believe.
I made this insanely simple volume control with the raspberry pi in mind a few months back. Doesn't work on Pandora as alsamixer reports no adjustments
Anyway, take a look if you want here.
----------------------
It's a module and I have waitdev=5, but that seems not the problem, I'm sure the device is ready, it's probably crappy code (either driver or firmware.. it is broadcom after all ).jamesbond wrote:Is the wlan0 a module, or do you built it in to the kernel? Either way, sometimes the driver needs more time to initialise (3 seconds of waitdev may not be enough). When you lost the connection does dmesg say anything about it?
The error in dmesg I get is that it is all good, associated, then deauthenticated (reason=1) , and this can happen when I try it from my script too. So, it's like I said crappy driver/firmware I believe.
Puppy Linux Blog - contact me for access
Works fine01micko wrote: Anyway, take a look if you want here.
It needs better icons, and 10 more lines of code to update icons with "master" level (a la xo-battery monitor).
Though I can see jamesbond already compiled retrovol-08 for a2
BTW have you removed /etc/astate.conf from your build. Iy may cause trouble.
Edit: "funny" spelling
Last edited by mavrothal on Tue 10 Sep 2013, 15:38, edited 1 time in total.
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==