7 p.m.
I've picked up a Mele A1000 set top, which uses the Allwinner A10 CPU.
I don't see a Fedora port for this one yet, so I might take a shot at
it. But first I wanted to ask if anyone else has already started this?
The CPU is a Cortex A8, and there is an Ubuntu port, as well as its
native Android OS.
Steve
5:12 a.m.
On Fri, Aug 3, 2012 at 1:00 AM, Steven A. Falco <safalco(a)optonline.net> wrote:
I've picked up a Mele A1000 set top, which uses the Allwinner A10
CPU.
I don't see a Fedora port for this one yet, so I might take a shot at
it. But first I wanted to ask if anyone else has already started this?
The CPU is a Cortex A8, and there is an Ubuntu port, as well as its
native Android OS.
None of the A10 kernel source code is upstream. It's something I would
like to support at some point in time as there's a lot of cheap and
interesting devices coming out with the chip from Netbook form factor
through to stick PCs. It should be doable as it's only kernel stuff
that's needed and it should run fine with the standard hardfp builds
but your milarge may vary.
Peter
8:23 a.m.
On Fri, Aug 3, 2012 at 7:12 AM, Peter Robinson <pbrobinson(a)gmail.com> wrote:
On Fri, Aug 3, 2012 at 1:00 AM, Steven A. Falco
<safalco(a)optonline.net> wrote:
> I've picked up a Mele A1000 set top, which uses the Allwinner A10 CPU.
> I don't see a Fedora port for this one yet, so I might take a shot at
> it. But first I wanted to ask if anyone else has already started this?
>
> The CPU is a Cortex A8, and there is an Ubuntu port, as well as its
> native Android OS.
None of the A10 kernel source code is upstream. It's something I would
like to support at some point in time as there's a lot of cheap and
interesting devices coming out with the chip from Netbook form factor
through to stick PCs. It should be doable as it's only kernel stuff
that's needed and it should run fine with the standard hardfp builds
but your milarge may vary.
Peter
I have one, if you build the kernel I am able to try it.
--
------------
Itamar Reis Peixoto
msn, google talk: itamar(a)ispbrasil.com.br
+55 11 4063 5033 (FIXO SP)
+55 34 9158 9329 (TIM)
+55 34 8806 3989 (OI)
+55 34 3221 8599 (FIXO MG)
8:37 a.m.
Have tried to get the kernel to build, and I remember these sites were helpful.
https://github.com/amery/linux-allwinner
http://rhombus-tech.net/allwinner_a10/hacking_the_mele_a1000/Building_Deb...
Make sure that cgroups are enabled in your kernel.
Once you have the kernel build you can integrate with the latest userland image.
Somebody on IRC suggested that the Allwinner patches may need
improvement before they could be accepted upstream?
It would be great if that happened, as Fedora only digests upstream kernel.
Otherwise this could be a 3rd party spin like raspi?
-Jon
On Fri, Aug 3, 2012 at 8:23 AM, Itamar Reis Peixoto
<itamar(a)ispbrasil.com.br> wrote:
On Fri, Aug 3, 2012 at 7:12 AM, Peter Robinson
<pbrobinson(a)gmail.com> wrote:
> On Fri, Aug 3, 2012 at 1:00 AM, Steven A. Falco <safalco(a)optonline.net> wrote:
>> I've picked up a Mele A1000 set top, which uses the Allwinner A10 CPU.
>> I don't see a Fedora port for this one yet, so I might take a shot at
>> it. But first I wanted to ask if anyone else has already started this?
>>
>> The CPU is a Cortex A8, and there is an Ubuntu port, as well as its
>> native Android OS.
>
> None of the A10 kernel source code is upstream. It's something I would
> like to support at some point in time as there's a lot of cheap and
> interesting devices coming out with the chip from Netbook form factor
> through to stick PCs. It should be doable as it's only kernel stuff
> that's needed and it should run fine with the standard hardfp builds
> but your milarge may vary.
>
> Peter
I have one, if you build the kernel I am able to try it.
--
------------
Itamar Reis Peixoto
msn, google talk: itamar(a)ispbrasil.com.br
+55 11 4063 5033 (FIXO SP)
+55 34 9158 9329 (TIM)
+55 34 8806 3989 (OI)
+55 34 3221 8599 (FIXO MG)
_______________________________________________
arm mailing list
arm(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/arm
--
-Jon
12:17 p.m.
On 08/03/2012 09:37 AM, Jon wrote:
Have tried to get the kernel to build, and I remember these sites
were helpful.
https://github.com/amery/linux-allwinner
http://rhombus-tech.net/allwinner_a10/hacking_the_mele_a1000/Building_Deb...
Make sure that cgroups are enabled in your kernel.
Once you have the kernel build you can integrate with the latest userland image.
Somebody on IRC suggested that the Allwinner patches may need
improvement before they could be accepted upstream?
It would be great if that happened, as Fedora only digests upstream kernel.
Otherwise this could be a 3rd party spin like raspi?
I'll take a close look at the kernel patches over the next day
or two. I am set up to cross-compile that, so it is mostly a
question of the required settings for Fedora. Is there a minimum
allowed kernel version? As in, nothing older than 3.xxx? I ask
because I tried a 2.6.34.9 kernel with F17 on my Ionics, and got
lots of errors from udev and systemd.
Also, is there a preferred procedure for bootstrapping initramfs?
I assume the best way is to unpack an existing one, replace any
kernel modules, and repack. I don't see a way to run dracut in
a cross-environment (i.e. from an x86).
Steve
-Jon
On Fri, Aug 3, 2012 at 8:23 AM, Itamar Reis Peixoto
<itamar(a)ispbrasil.com.br> wrote:
> On Fri, Aug 3, 2012 at 7:12 AM, Peter Robinson <pbrobinson(a)gmail.com> wrote:
>> On Fri, Aug 3, 2012 at 1:00 AM, Steven A. Falco <safalco(a)optonline.net>
wrote:
>>> I've picked up a Mele A1000 set top, which uses the Allwinner A10 CPU.
>>> I don't see a Fedora port for this one yet, so I might take a shot at
>>> it. But first I wanted to ask if anyone else has already started this?
>>>
>>> The CPU is a Cortex A8, and there is an Ubuntu port, as well as its
>>> native Android OS.
>>
>> None of the A10 kernel source code is upstream. It's something I would
>> like to support at some point in time as there's a lot of cheap and
>> interesting devices coming out with the chip from Netbook form factor
>> through to stick PCs. It should be doable as it's only kernel stuff
>> that's needed and it should run fine with the standard hardfp builds
>> but your milarge may vary.
>>
>> Peter
>
> I have one, if you build the kernel I am able to try it.
>
> --
> ------------
>
> Itamar Reis Peixoto
> msn, google talk: itamar(a)ispbrasil.com.br
> +55 11 4063 5033 (FIXO SP)
> +55 34 9158 9329 (TIM)
> +55 34 8806 3989 (OI)
> +55 34 3221 8599 (FIXO MG)
> _______________________________________________
> arm mailing list
> arm(a)lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/arm
1:14 p.m.
On Sat, Aug 4, 2012 at 2:17 PM, Steven A. Falco <safalco(a)optonline.net> wrote:
On 08/03/2012 09:37 AM, Jon wrote:
> Have tried to get the kernel to build, and I remember these sites were helpful.
>
> https://github.com/amery/linux-allwinner
>
http://rhombus-tech.net/allwinner_a10/hacking_the_mele_a1000/Building_Deb...
>
> Make sure that cgroups are enabled in your kernel.
> Once you have the kernel build you can integrate with the latest userland image.
>
> Somebody on IRC suggested that the Allwinner patches may need
> improvement before they could be accepted upstream?
> It would be great if that happened, as Fedora only digests upstream kernel.
>
> Otherwise this could be a 3rd party spin like raspi?
I'll take a close look at the kernel patches over the next day
or two. I am set up to cross-compile that, so it is mostly a
question of the required settings for Fedora. Is there a minimum
allowed kernel version? As in, nothing older than 3.xxx? I ask
because I tried a 2.6.34.9 kernel with F17 on my Ionics, and got
lots of errors from udev and systemd.
Also, is there a preferred procedure for bootstrapping initramfs?
I assume the best way is to unpack an existing one, replace any
kernel modules, and repack. I don't see a way to run dracut in
a cross-environment (i.e. from an x86).
Steve
I havent tried, but its possible to run fedora arm inside qemu, its
probably slow, but seems to work.
--
------------
Itamar Reis Peixoto
msn, google talk: itamar(a)ispbrasil.com.br
+55 11 4063 5033 (FIXO SP)
+55 34 9158 9329 (TIM)
+55 34 8806 3989 (OI)
+55 34 3221 8599 (FIXO MG)
8:52 p.m.
On 08/03/2012 06:12 AM, Peter Robinson wrote:
On Fri, Aug 3, 2012 at 1:00 AM, Steven A. Falco
<safalco(a)optonline.net> wrote:
> I've picked up a Mele A1000 set top, which uses the Allwinner A10 CPU.
> I don't see a Fedora port for this one yet, so I might take a shot at
> it. But first I wanted to ask if anyone else has already started this?
>
> The CPU is a Cortex A8, and there is an Ubuntu port, as well as its
> native Android OS.
None of the A10 kernel source code is upstream. It's something I would
like to support at some point in time as there's a lot of cheap and
interesting devices coming out with the chip from Netbook form factor
through to stick PCs. It should be doable as it's only kernel stuff
that's needed and it should run fine with the standard hardfp builds
but your milarge may vary.
Peter
Ok - I have Fedora 17 running on the Mele. It is quite a hack, but it
is usable (yum merrily installing the dev tools as we speak).
Here is the recipe:
1) grab and cross-compile a copy of the kernel from:
git://github.com/amery/linux-allwinner.git
(use branch allwinner-v3.0-android-v2 with sun4i_defconfig)
2) grab http://hands.com/~lkcl/mele-ubuntu-lucid.img.lzma and write it
to an SD card (don't forget to decompress it). Afterwards, use
gparted to expand the ext partition to fill the SD card.
3) Mount the various partitions of the SD card on a host machine. On
the fat partition, replace uImage with the one you just built. On
the ext partition, blow everything away, and replace with an untar of:
http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images...
4) Install the modules that go with the kernel you built to the ext
partition (into /lib/modules/3.0.38+).
5) Stick the SD card in the Mele, and it should boot.
One big issue is that the built-in eth0 is not functional. That is true
of the ubuntu build as well. To get around that, I plugged in a USB/ethernet
adapter (and built the kernel module for it). That gave me a usable eth1.
This clearly needs a ton of work to be a proper Fedora installation,
but at least it is a start...
Steve
10:59 p.m.
On Mon, Aug 6, 2012 at 8:52 PM, Steven A. Falco <safalco(a)optonline.net> wrote:
On 08/03/2012 06:12 AM, Peter Robinson wrote:
> On Fri, Aug 3, 2012 at 1:00 AM, Steven A. Falco <safalco(a)optonline.net> wrote:
>> I've picked up a Mele A1000 set top, which uses the Allwinner A10 CPU.
>> I don't see a Fedora port for this one yet, so I might take a shot at
>> it. But first I wanted to ask if anyone else has already started this?
>>
>> The CPU is a Cortex A8, and there is an Ubuntu port, as well as its
>> native Android OS.
>
> None of the A10 kernel source code is upstream. It's something I would
> like to support at some point in time as there's a lot of cheap and
> interesting devices coming out with the chip from Netbook form factor
> through to stick PCs. It should be doable as it's only kernel stuff
> that's needed and it should run fine with the standard hardfp builds
> but your milarge may vary.
>
> Peter
>
Ok - I have Fedora 17 running on the Mele. It is quite a hack, but it
is usable (yum merrily installing the dev tools as we speak).
Here is the recipe:
1) grab and cross-compile a copy of the kernel from:
git://github.com/amery/linux-allwinner.git
(use branch allwinner-v3.0-android-v2 with sun4i_defconfig)
2) grab http://hands.com/~lkcl/mele-ubuntu-lucid.img.lzma and write it
to an SD card (don't forget to decompress it). Afterwards, use
gparted to expand the ext partition to fill the SD card.
3) Mount the various partitions of the SD card on a host machine. On
the fat partition, replace uImage with the one you just built. On
the ext partition, blow everything away, and replace with an untar of:
http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images...
4) Install the modules that go with the kernel you built to the ext
partition (into /lib/modules/3.0.38+).
5) Stick the SD card in the Mele, and it should boot.
One big issue is that the built-in eth0 is not functional. That is true
of the ubuntu build as well. To get around that, I plugged in a USB/ethernet
adapter (and built the kernel module for it). That gave me a usable eth1.
This clearly needs a ton of work to be a proper Fedora installation,
but at least it is a start...
Steve
Sounds like a good start.
We could probably just use the resize script in our image to expand
partition and resize ext on firstboot?
We might also consider making a wiki page for this device, ensure to
mention this is unsupported.
-Jon
11:02 p.m.
On Tue, Aug 7, 2012 at 12:59 AM, Jon <jdisnard(a)gmail.com> wrote:
Sounds like a good start.
We could probably just use the resize script in our image to expand
partition and resize ext on firstboot?
We might also consider making a wiki page for this device, ensure to
mention this is unsupported.
-Jon
Please do that, I got one, its very fast with android, if I replace
android with fedora I can use it as my desktop.
--
------------
Itamar Reis Peixoto
msn, google talk: itamar(a)ispbrasil.com.br
+55 11 4063 5033 (FIXO SP)
+55 34 9158 9329 (TIM)
+55 34 8806 3989 (OI)
+55 34 3221 8599 (FIXO MG)
6:58 a.m.
On 08/07/2012 12:02 AM, Itamar Reis Peixoto wrote:
On Tue, Aug 7, 2012 at 12:59 AM, Jon <jdisnard(a)gmail.com>
wrote:
>
> Sounds like a good start.
>
> We could probably just use the resize script in our image to expand
> partition and resize ext on firstboot?
>
> We might also consider making a wiki page for this device, ensure to
> mention this is unsupported.
>
> -Jon
Please do that, I got one, its very fast with android, if I replace
android with fedora I can use it as my desktop.
If I have access, I'll start working up a page tonight. One thing
about a desktop - I have not tried any graphics yet. It is strictly
an ssh text-mode thing right now, as that is all I need to do my
initial performance measurements. I'm trying to assess the viability
of the chip for an embedded project rather than as a general-purpose
box.
But of course others in the community would be encouraged to look
the graphics side. Once you have it booted, the rest of the code can
follow.
Steve
11:09 a.m.
On 08/06/2012 11:59 PM, Jon wrote:
On Mon, Aug 6, 2012 at 8:52 PM, Steven A. Falco
<safalco(a)optonline.net> wrote:
> On 08/03/2012 06:12 AM, Peter Robinson wrote:
[...]
>
> Ok - I have Fedora 17 running on the Mele. It is quite a hack, but it
> is usable (yum merrily installing the dev tools as we speak).
>
> Here is the recipe:
>
> 1) grab and cross-compile a copy of the kernel from:
> git://github.com/amery/linux-allwinner.git
> (use branch allwinner-v3.0-android-v2 with sun4i_defconfig)
> 2) grab http://hands.com/~lkcl/mele-ubuntu-lucid.img.lzma and write it
> to an SD card (don't forget to decompress it). Afterwards, use
> gparted to expand the ext partition to fill the SD card.
>
> 3) Mount the various partitions of the SD card on a host machine. On
> the fat partition, replace uImage with the one you just built. On
> the ext partition, blow everything away, and replace with an untar of:
>
>
http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images...
>
> 4) Install the modules that go with the kernel you built to the ext
> partition (into /lib/modules/3.0.38+).
>
> 5) Stick the SD card in the Mele, and it should boot.
Alternatively and Cleaner:
1) Download A1000 hardware pack from nightly builds. This is a Kernel
and Uboot pre-built.
http://rhombus-tech.net/allwinner_a10/nightly_build_images/
2) Grab the a1x-media-create.sh Script.
# Needs to be Modified to support Fedora .zx tar archive and /lib
symbolic link. Working on a patch.
3) Download the Fedora Root FS.
4) Run media build script.
5) Stick SD card in the Mele and it will boot.
This removes the dependence on the ubuntu image and automatically makes
the partitions the correct size for the media.
> One big issue is that the built-in eth0 is not functional. That
is true
> of the ubuntu build as well. To get around that, I plugged in a USB/ethernet
> adapter (and built the kernel module for it). That gave me a usable eth1.
I got it to boot on Saturday using the method I outlined. I ran out of
time to verify what did and didn't work.
> This clearly needs a ton of work to be a proper Fedora
installation,
> but at least it is a start...
Yes, certainly getting easier.
Sounds like a good start.
We could probably just use the resize script in our image to expand
partition and resize ext on firstboot?
No need with the creation script from the nightly builds. Otherwise we
could re-purpose the scripts form the Raspberry Pi remix.
We might also consider making a wiki page for this device, ensure to
mention this is unsupported.
Where do you want it?
--
Scott Sullivan
IRC: revident
11:36 a.m.
On Tue, Aug 7, 2012 at 11:09 AM, Scott Sullivan <scott(a)ss.org> wrote:
On 08/06/2012 11:59 PM, Jon wrote:
>
> On Mon, Aug 6, 2012 at 8:52 PM, Steven A. Falco <safalco(a)optonline.net>
> wrote:
>>
>> On 08/03/2012 06:12 AM, Peter Robinson wrote:
[...]
>>
>> Ok - I have Fedora 17 running on the Mele. It is quite a hack, but it
>> is usable (yum merrily installing the dev tools as we speak).
>>
>> Here is the recipe:
>>
>> 1) grab and cross-compile a copy of the kernel from:
>> git://github.com/amery/linux-allwinner.git
>> (use branch allwinner-v3.0-android-v2 with sun4i_defconfig)
>> 2) grab http://hands.com/~lkcl/mele-ubuntu-lucid.img.lzma and write it
>> to an SD card (don't forget to decompress it). Afterwards, use
>> gparted to expand the ext partition to fill the SD card.
>>
>> 3) Mount the various partitions of the SD card on a host machine. On
>> the fat partition, replace uImage with the one you just built. On
>> the ext partition, blow everything away, and replace with an untar
>> of:
>>
>>
>>
http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images...
>>
>> 4) Install the modules that go with the kernel you built to the ext
>> partition (into /lib/modules/3.0.38+).
>>
>> 5) Stick the SD card in the Mele, and it should boot.
Alternatively and Cleaner:
1) Download A1000 hardware pack from nightly builds. This is a Kernel and
Uboot pre-built.
http://rhombus-tech.net/allwinner_a10/nightly_build_images/
2) Grab the a1x-media-create.sh Script.
# Needs to be Modified to support Fedora .zx tar archive and /lib symbolic
link. Working on a patch.
3) Download the Fedora Root FS.
4) Run media build script.
5) Stick SD card in the Mele and it will boot.
This removes the dependence on the ubuntu image and automatically makes the
partitions the correct size for the media.
>> One big issue is that the built-in eth0 is not functional. That is true
>> of the ubuntu build as well. To get around that, I plugged in a
>> USB/ethernet
>> adapter (and built the kernel module for it). That gave me a usable
>> eth1.
I got it to boot on Saturday using the method I outlined. I ran out of time
to verify what did and didn't work.
>> This clearly needs a ton of work to be a proper Fedora installation,
>> but at least it is a start...
Yes, certainly getting easier.
> Sounds like a good start.
>
> We could probably just use the resize script in our image to expand
> partition and resize ext on firstboot?
No need with the creation script from the nightly builds. Otherwise we could
re-purpose the scripts form the Raspberry Pi remix.
That is the script I'm talking about, I believe it is on the Fedora
image you have used.
Look at your systemd units, it should just work on first boot.
> We might also consider making a wiki page for this device, ensure to
> mention this is unsupported.
Where do you want it?
How about here:
http://fedoraproject.org/wiki/Architectures/ARM/AllwinerA10
[does not exist yet]
Presumably these steps will work with the mk802?
I'll attempt to reproduce your results soon, hopefully tonight.
Have you seen this?
[1] https://www.miniand.com/forums/forums/2/topics/42
They have a Fedora image for mk802 (allwinner a10) with a UI.
An opportunity take a look at some prior art, though I don't see any
build steps.
Hopefully we can document the build steps for others to follow on the wiki.
Thanks,
-Jon
8 p.m.
On 08/07/2012 12:09 PM, Scott Sullivan wrote:
>> One big issue is that the built-in eth0 is not functional.
That is true
>> of the ubuntu build as well. To get around that, I plugged in a USB/ethernet
>> adapter (and built the kernel module for it). That gave me a usable eth1.
I got it to boot on Saturday using the method I outlined. I ran out of time to verify
what did and didn't work.
I'll be interested to see if you wind up with a functional eth0. I'd like
to get rid of the USB dongle I'm using.
Steve
10:23 p.m.
On Tue, Aug 7, 2012 at 8:00 PM, Steven A. Falco <safalco(a)optonline.net> wrote:
On 08/07/2012 12:09 PM, Scott Sullivan wrote:
>>> One big issue is that the built-in eth0 is not functional. That is true
>>> of the ubuntu build as well. To get around that, I plugged in a
USB/ethernet
>>> adapter (and built the kernel module for it). That gave me a usable eth1.
>
> I got it to boot on Saturday using the method I outlined. I ran out of time to verify
what did and didn't work.
>
I'll be interested to see if you wind up with a functional eth0. I'd like
to get rid of the USB dongle I'm using.
Steve
FYI - Another Allwinner A10 board
https://www.miniand.com/products/Hackberry%20A10%20Developer%20Board#buy
--
-Jon
11:07 p.m.
On Thu, Aug 2, 2012 at 9:00 PM, Steven A. Falco <safalco(a)optonline.net> wrote:
I've picked up a Mele A1000 set top,
Is the A2000 related to the A1000? anyone tried it? (I´m asking
because I can´t find the A1000 in amazon.com but the A2000 is
available...)
TIA
FC
PS: Apologies Steven if you get this twice, I hit reply on gmail and
ended up sending this just to you off-list, and I guess others would
be interested in the answer wrt A2000. Thanks
11:11 p.m.
On Mon, Aug 6, 2012 at 10:52 PM, Steven A. Falco <safalco(a)optonline.net> wrote:
5) Stick the SD card in the Mele, and it should boot.
You forgot
6) use ´dd´ to write a copy of the resulting sd card to a disk image
file and upload it somewhere (sites.google.com, sourceforge.net?
thinking aloud :) so that everyone interested saves themselves from
doing steps 1-5. ;-)
well. it would be nice. ;)
FC
11:12 p.m.
On Tue, Aug 7, 2012 at 11:07 PM, Fernando Cassia <fcassia(a)gmail.com> wrote:
On Thu, Aug 2, 2012 at 9:00 PM, Steven A. Falco
<safalco(a)optonline.net> wrote:
> I've picked up a Mele A1000 set top,
Is the A2000 related to the A1000? anyone tried it? (I´m asking
because I can´t find the A1000 in amazon.com but the A2000 is
available...)
TIA
FC
PS: Apologies Steven if you get this twice, I hit reply on gmail and
ended up sending this just to you off-list, and I guess others would
be interested in the answer wrt A2000. Thanks
AFAIK the a2000 has more memory.
A good wiki page for the AllWinner is on xmbc website
[1] http://wiki.xbmc.org/index.php?title=Allwinner_A10#Mele_A1000.2FA2000
--
-Jon
11:13 p.m.
On Wed, Aug 8, 2012 at 1:12 AM, Jon <jdisnard(a)gmail.com> wrote:
AFAIK the a2000 has more memory.
A good wiki page for the AllWinner is on xmbc website
[1] http://wiki.xbmc.org/index.php?title=Allwinner_A10#Mele_A1000.2FA2000
Great pointer Jon.
Thanks a bunch.
FC
7:02 a.m.
On 08/08/2012 12:11 AM, Fernando Cassia wrote:
On Mon, Aug 6, 2012 at 10:52 PM, Steven A. Falco
<safalco(a)optonline.net> wrote:
> 5) Stick the SD card in the Mele, and it should boot.
You forgot
6) use ´dd´ to write a copy of the resulting sd card to a disk image
file and upload it somewhere (sites.google.com, sourceforge.net?
thinking aloud :) so that everyone interested saves themselves from
doing steps 1-5. ;-)
well. it would be nice. ;)
The problem is that you will need a USB/ethernet dongle right now, and
that means you have to build your own kernel. So a single image is not
really possible at the moment.
Steve
FC
_______________________________________________
arm mailing list
arm(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/arm
7:45 a.m.
On Wed, Aug 8, 2012 at 9:02 AM, Steven A. Falco <safalco(a)optonline.net> wrote:
The problem is that you will need a USB/ethernet dongle right now,
and
that means you have to build your own kernel. So a single image is not
really possible at the moment.
Steve
OK I see. Thanks.
Let me guess... the Ethernet port in the device is handled by the cpu
(DSP microcode) rather than being based on a real Ethernet controller
on the system board?. Or is there an Ethernet chip in there, just
unsupported by Linux drivers?.
If the former case, then it reminds me of the Neuros OSD...
FC
9:02 a.m.
On 08/08/2012 08:45 AM, Fernando Cassia wrote:
On Wed, Aug 8, 2012 at 9:02 AM, Steven A. Falco
<safalco(a)optonline.net> wrote:
> The problem is that you will need a USB/ethernet dongle right now, and
> that means you have to build your own kernel. So a single image is not
> really possible at the moment.
>
> Steve
OK I see. Thanks.
Let me guess... the Ethernet port in the device is handled by the cpu
(DSP microcode) rather than being based on a real Ethernet controller
on the system board?. Or is there an Ethernet chip in there, just
unsupported by Linux drivers?.
If the former case, then it reminds me of the Neuros OSD...
It uses something called WEMAC which is part of the chip. I have not
attempted to see what is wrong. Might just be a gpio that is not
turned on, or might be something major. Sadly I don't have time to
dig into it.
But since Olimex is looking at building a hacker board with this CPU,
I imagine it will get sorted out by them, if not before...
Steve
FC
_______________________________________________
arm mailing list
arm(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/arm
1:12 p.m.
On 08/07/2012 12:09 PM, Scott Sullivan wrote:
On 08/06/2012 11:59 PM, Jon wrote:
> On Mon, Aug 6, 2012 at 8:52 PM, Steven A. Falco <safalco(a)optonline.net> wrote:
>> On 08/03/2012 06:12 AM, Peter Robinson wrote:
[...]
>>
>> Ok - I have Fedora 17 running on the Mele. It is quite a hack, but it
>> is usable (yum merrily installing the dev tools as we speak).
>>
>> Here is the recipe:
>>
>> 1) grab and cross-compile a copy of the kernel from:
>> git://github.com/amery/linux-allwinner.git
>> (use branch allwinner-v3.0-android-v2 with sun4i_defconfig)
>> 2) grab http://hands.com/~lkcl/mele-ubuntu-lucid.img.lzma and write it
>> to an SD card (don't forget to decompress it). Afterwards, use
>> gparted to expand the ext partition to fill the SD card.
>>
>> 3) Mount the various partitions of the SD card on a host machine. On
>> the fat partition, replace uImage with the one you just built. On
>> the ext partition, blow everything away, and replace with an untar of:
>>
>>
http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images...
>>
>> 4) Install the modules that go with the kernel you built to the ext
>> partition (into /lib/modules/3.0.38+).
>>
>> 5) Stick the SD card in the Mele, and it should boot.
Alternatively and Cleaner:
1) Download A1000 hardware pack from nightly builds. This is a Kernel and Uboot
pre-built.
http://rhombus-tech.net/allwinner_a10/nightly_build_images/
2) Grab the a1x-media-create.sh Script.
# Needs to be Modified to support Fedora .zx tar archive and /lib symbolic link. Working
on a patch.
The following is all that is needed for the .xz stuff. I have
not looked at the /lib part.
--- /home/sfalco/a1x-media-create.sh 2012-08-08 14:10:38.323150167 -0400
+++ ./a1x-media-create.sh 2012-08-08 14:08:26.021655286 -0400
@@ -107,6 +107,8 @@
sudo tar xzf ../$1
elif [ ${fileext} == "7z" ] | [ ${fileext} == "lzma" ]; then
sudo 7z x ../$1
+ elif [ ${fileext} == "xz" ]; then
+ sudo tar xJf ../$1
else
echo "Unknown file extension: ${fileext}"
popd
3) Download the Fedora Root FS.
4) Run media build script.
5) Stick SD card in the Mele and it will boot.
This removes the dependence on the ubuntu image and automatically makes the partitions
the correct size for the media.
>> One big issue is that the built-in eth0 is not functional. That is true
>> of the ubuntu build as well. To get around that, I plugged in a USB/ethernet
>> adapter (and built the kernel module for it). That gave me a usable eth1.
I got it to boot on Saturday using the method I outlined. I ran out of time to verify
what did and didn't work.
>> This clearly needs a ton of work to be a proper Fedora installation,
>> but at least it is a start...
Yes, certainly getting easier.
> Sounds like a good start.
>
> We could probably just use the resize script in our image to expand
> partition and resize ext on firstboot?
No need with the creation script from the nightly builds. Otherwise we could re-purpose
the scripts form the Raspberry Pi remix.
> We might also consider making a wiki page for this device, ensure to
> mention this is unsupported.
Where do you want it?
1:44 p.m.
On 08/07/2012 12:09 PM, Scott Sullivan wrote:
On 08/06/2012 11:59 PM, Jon wrote:
> On Mon, Aug 6, 2012 at 8:52 PM, Steven A. Falco <safalco(a)optonline.net> wrote:
>> On 08/03/2012 06:12 AM, Peter Robinson wrote:
[...]
>>
>> Ok - I have Fedora 17 running on the Mele. It is quite a hack, but it
>> is usable (yum merrily installing the dev tools as we speak).
>>
>> Here is the recipe:
>>
>> 1) grab and cross-compile a copy of the kernel from:
>> git://github.com/amery/linux-allwinner.git
>> (use branch allwinner-v3.0-android-v2 with sun4i_defconfig)
>> 2) grab http://hands.com/~lkcl/mele-ubuntu-lucid.img.lzma and write it
>> to an SD card (don't forget to decompress it). Afterwards, use
>> gparted to expand the ext partition to fill the SD card.
>>
>> 3) Mount the various partitions of the SD card on a host machine. On
>> the fat partition, replace uImage with the one you just built. On
>> the ext partition, blow everything away, and replace with an untar of:
>>
>>
http://download.fedoraproject.org/pub/fedora-secondary/releases/17/Images...
>>
>> 4) Install the modules that go with the kernel you built to the ext
>> partition (into /lib/modules/3.0.38+).
>>
>> 5) Stick the SD card in the Mele, and it should boot.
Alternatively and Cleaner:
1) Download A1000 hardware pack from nightly builds. This is a Kernel and Uboot
pre-built.
http://rhombus-tech.net/allwinner_a10/nightly_build_images/
2) Grab the a1x-media-create.sh Script.
# Needs to be Modified to support Fedora .zx tar archive and /lib symbolic link. Working
on a patch.
Here is a patch that fixes both the xz and symbolic link:
--- /home/sfalco/a1x-media-create.sh 2012-08-08 14:10:38.323150167 -0400
+++ ./a1x-media-create.sh 2012-08-08 14:38:29.609848573 -0400
@@ -107,6 +107,8 @@
sudo tar xzf ../$1
elif [ ${fileext} == "7z" ] | [ ${fileext} == "lzma" ]; then
sudo 7z x ../$1
+ elif [ ${fileext} == "xz" ]; then
+ sudo tar xJf ../$1
else
echo "Unknown file extension: ${fileext}"
popd
@@ -217,6 +219,14 @@
cleanup
fi
echo "Copy hwpack rootfs files"
+ # Fedora uses a softlink for lib. Adjust, if needed.
+ if [ -L mntSDrootfs/lib ]; then
+ # Find where it points. For Fedora, we expect usr/lib.
+ DEST=`/bin/ls -l mntSDrootfs/lib | sed -e 's,.* ,,'`
+ if [ "$DEST" = "usr/lib" ]; then
+ mv hwpack/rootfs/lib hwpack/rootfs/usr
+ fi
+ fi
sudo cp -a hwpack/rootfs/* mntSDrootfs >> ${logfile}
if [ $? -ne 0 ]; then
echo "Failed to copy rootfs hwpack files to SD Card"
3) Download the Fedora Root FS.
4) Run media build script.
5) Stick SD card in the Mele and it will boot.
This removes the dependence on the ubuntu image and automatically makes the partitions
the correct size for the media.
>> One big issue is that the built-in eth0 is not functional. That is true
>> of the ubuntu build as well. To get around that, I plugged in a USB/ethernet
>> adapter (and built the kernel module for it). That gave me a usable eth1.
I got it to boot on Saturday using the method I outlined. I ran out of time to verify
what did and didn't work.
>> This clearly needs a ton of work to be a proper Fedora installation,
>> but at least it is a start...
Yes, certainly getting easier.
> Sounds like a good start.
>
> We could probably just use the resize script in our image to expand
> partition and resize ext on firstboot?
No need with the creation script from the nightly builds. Otherwise we could re-purpose
the scripts form the Raspberry Pi remix.
> We might also consider making a wiki page for this device, ensure to
> mention this is unsupported.
Where do you want it?
2:46 p.m.
On Wed, Aug 8, 2012 at 11:02 AM, Steven A. Falco <safalco(a)optonline.net> wrote:
It uses something called WEMAC which is part of the chip. I have
not
attempted to see what is wrong. Might just be a gpio that is not
turned on, or might be something major. Sadly I don't have time to
dig into it.
I see
https://github.com/amery/linux-allwinner/pull/39
FC
8:14 p.m.
On 08/08/2012 02:44 PM, Steven A. Falco wrote:
On 08/07/2012 12:09 PM, Scott Sullivan wrote:
[...]
> # Needs to be Modified to support Fedora .zx tar archive and /lib
symbolic link. Working on a patch.
Here is a patch that fixes both the xz and symbolic link:
--- /home/sfalco/a1x-media-create.sh 2012-08-08 14:10:38.323150167 -0400
+++ ./a1x-media-create.sh 2012-08-08 14:38:29.609848573 -0400
@@ -107,6 +107,8 @@
sudo tar xzf ../$1
elif [ ${fileext} == "7z" ] | [ ${fileext} == "lzma" ]; then
sudo 7z x ../$1
+ elif [ ${fileext} == "xz" ]; then
+ sudo tar xJf ../$1
else
echo "Unknown file extension: ${fileext}"
popd
@@ -217,6 +219,14 @@
cleanup
fi
echo "Copy hwpack rootfs files"
+ # Fedora uses a softlink for lib. Adjust, if needed.
+ if [ -L mntSDrootfs/lib ]; then
+ # Find where it points. For Fedora, we expect usr/lib.
+ DEST=`/bin/ls -l mntSDrootfs/lib | sed -e 's,.* ,,'`
+ if [ "$DEST" = "usr/lib" ]; then
+ mv hwpack/rootfs/lib hwpack/rootfs/usr
+ fi
+ fi
sudo cp -a hwpack/rootfs/* mntSDrootfs >> ${logfile}
if [ $? -ne 0 ]; then
echo "Failed to copy rootfs hwpack files to SD Card"
Thanks Steven. My time got busy and this got pushed to my back burner,
greatly appreciated.
Have you tired getting this applied to the upstream yet?
--
Scott Sullivan
8:24 p.m.
On 08/08/2012 09:14 PM, Scott Sullivan wrote:
On 08/08/2012 02:44 PM, Steven A. Falco wrote:
> On 08/07/2012 12:09 PM, Scott Sullivan wrote:
[...]
>> # Needs to be Modified to support Fedora .zx tar archive and /lib symbolic link.
Working on a patch.
>
> Here is a patch that fixes both the xz and symbolic link:
>
> --- /home/sfalco/a1x-media-create.sh 2012-08-08 14:10:38.323150167 -0400
> +++ ./a1x-media-create.sh 2012-08-08 14:38:29.609848573 -0400
> @@ -107,6 +107,8 @@
> sudo tar xzf ../$1
> elif [ ${fileext} == "7z" ] | [ ${fileext} == "lzma" ];
then
> sudo 7z x ../$1
> + elif [ ${fileext} == "xz" ]; then
> + sudo tar xJf ../$1
> else
> echo "Unknown file extension: ${fileext}"
> popd
> @@ -217,6 +219,14 @@
> cleanup
> fi
> echo "Copy hwpack rootfs files"
> + # Fedora uses a softlink for lib. Adjust, if needed.
> + if [ -L mntSDrootfs/lib ]; then
> + # Find where it points. For Fedora, we expect usr/lib.
> + DEST=`/bin/ls -l mntSDrootfs/lib | sed -e 's,.* ,,'`
> + if [ "$DEST" = "usr/lib" ]; then
> + mv hwpack/rootfs/lib hwpack/rootfs/usr
> + fi
> + fi
> sudo cp -a hwpack/rootfs/* mntSDrootfs >> ${logfile}
> if [ $? -ne 0 ]; then
> echo "Failed to copy rootfs hwpack files to SD Card"
Thanks Steven. My time got busy and this got pushed to my back burner, greatly
appreciated.
Have you tired getting this applied to the upstream yet?
No, but I have tested it, and it is working very well. It even solves
the wired-ethernet bug that I was having. So I'm happy with it. I'll
look at trying to get it upstream a bit later.
Steve
8:57 p.m.
On 08/08/2012 09:14 PM, Scott Sullivan wrote:
On 08/08/2012 02:44 PM, Steven A. Falco wrote:
> On 08/07/2012 12:09 PM, Scott Sullivan wrote:
[...]
>> # Needs to be Modified to support Fedora .zx tar archive and /lib symbolic link.
Working on a patch.
>
> Here is a patch that fixes both the xz and symbolic link:
>
> --- /home/sfalco/a1x-media-create.sh 2012-08-08 14:10:38.323150167 -0400
> +++ ./a1x-media-create.sh 2012-08-08 14:38:29.609848573 -0400
> @@ -107,6 +107,8 @@
> sudo tar xzf ../$1
> elif [ ${fileext} == "7z" ] | [ ${fileext} == "lzma" ];
then
> sudo 7z x ../$1
> + elif [ ${fileext} == "xz" ]; then
> + sudo tar xJf ../$1
> else
> echo "Unknown file extension: ${fileext}"
> popd
> @@ -217,6 +219,14 @@
> cleanup
> fi
> echo "Copy hwpack rootfs files"
> + # Fedora uses a softlink for lib. Adjust, if needed.
> + if [ -L mntSDrootfs/lib ]; then
> + # Find where it points. For Fedora, we expect usr/lib.
> + DEST=`/bin/ls -l mntSDrootfs/lib | sed -e 's,.* ,,'`
> + if [ "$DEST" = "usr/lib" ]; then
> + mv hwpack/rootfs/lib hwpack/rootfs/usr
> + fi
> + fi
> sudo cp -a hwpack/rootfs/* mntSDrootfs >> ${logfile}
> if [ $? -ne 0 ]; then
> echo "Failed to copy rootfs hwpack files to SD Card"
Thanks Steven. My time got busy and this got pushed to my back burner, greatly
appreciated.
Have you tired getting this applied to the upstream yet?
I created a fork on github, put in my changes, and made a pull
request. My version is here:
git://github.com/stevefalco/a10-tools.git
Please give it a try and feed me any comments.
Steve
10:38 p.m.
On 08/08/2012 09:57 PM, Steven A. Falco wrote:
On 08/08/2012 09:14 PM, Scott Sullivan wrote:
> On 08/08/2012 02:44 PM, Steven A. Falco wrote:
>> On 08/07/2012 12:09 PM, Scott Sullivan wrote:
> [...]
>>> # Needs to be Modified to support Fedora .zx tar archive and /lib symbolic
link. Working on a patch.
>>
>> Here is a patch that fixes both the xz and symbolic link:
>>
>> --- /home/sfalco/a1x-media-create.sh 2012-08-08 14:10:38.323150167 -0400
>> +++ ./a1x-media-create.sh 2012-08-08 14:38:29.609848573 -0400
>> @@ -107,6 +107,8 @@
>> sudo tar xzf ../$1
>> elif [ ${fileext} == "7z" ] | [ ${fileext} == "lzma"
]; then
>> sudo 7z x ../$1
>> + elif [ ${fileext} == "xz" ]; then
>> + sudo tar xJf ../$1
>> else
>> echo "Unknown file extension: ${fileext}"
>> popd
>> @@ -217,6 +219,14 @@
>> cleanup
>> fi
>> echo "Copy hwpack rootfs files"
>> + # Fedora uses a softlink for lib. Adjust, if needed.
>> + if [ -L mntSDrootfs/lib ]; then
>> + # Find where it points. For Fedora, we expect usr/lib.
>> + DEST=`/bin/ls -l mntSDrootfs/lib | sed -e 's,.* ,,'`
>> + if [ "$DEST" = "usr/lib" ]; then
>> + mv hwpack/rootfs/lib hwpack/rootfs/usr
>> + fi
>> + fi
>> sudo cp -a hwpack/rootfs/* mntSDrootfs >> ${logfile}
>> if [ $? -ne 0 ]; then
>> echo "Failed to copy rootfs hwpack files to SD Card"
>
>
> Thanks Steven. My time got busy and this got pushed to my back burner, greatly
appreciated.
>
> Have you tired getting this applied to the upstream yet?
>
I created a fork on github, put in my changes, and made a pull
request. My version is here:
git://github.com/stevefalco/a10-tools.git
Please give it a try and feed me any comments.
Steve
I snagged it and ran up a fresh SD card. It booted as expected and so
far networking is working. Now to just to find some time to get the VGA
working under Fedora.
--
Scott Sullivan
6:55 a.m.
On 08/08/2012 11:38 PM, Scott Sullivan wrote:
On 08/08/2012 09:57 PM, Steven A. Falco wrote:
> On 08/08/2012 09:14 PM, Scott Sullivan wrote:
>> On 08/08/2012 02:44 PM, Steven A. Falco wrote:
>>> On 08/07/2012 12:09 PM, Scott Sullivan wrote:
>> [...]
>>>> # Needs to be Modified to support Fedora .zx tar archive and /lib
symbolic link. Working on a patch.
>>>
>>> Here is a patch that fixes both the xz and symbolic link:
>>>
>>> --- /home/sfalco/a1x-media-create.sh 2012-08-08 14:10:38.323150167 -0400
>>> +++ ./a1x-media-create.sh 2012-08-08 14:38:29.609848573 -0400
>>> @@ -107,6 +107,8 @@
>>> sudo tar xzf ../$1
>>> elif [ ${fileext} == "7z" ] | [ ${fileext} ==
"lzma" ]; then
>>> sudo 7z x ../$1
>>> + elif [ ${fileext} == "xz" ]; then
>>> + sudo tar xJf ../$1
>>> else
>>> echo "Unknown file extension: ${fileext}"
>>> popd
>>> @@ -217,6 +219,14 @@
>>> cleanup
>>> fi
>>> echo "Copy hwpack rootfs files"
>>> + # Fedora uses a softlink for lib. Adjust, if needed.
>>> + if [ -L mntSDrootfs/lib ]; then
>>> + # Find where it points. For Fedora, we expect usr/lib.
>>> + DEST=`/bin/ls -l mntSDrootfs/lib | sed -e 's,.* ,,'`
>>> + if [ "$DEST" = "usr/lib" ]; then
>>> + mv hwpack/rootfs/lib hwpack/rootfs/usr
>>> + fi
>>> + fi
>>> sudo cp -a hwpack/rootfs/* mntSDrootfs >> ${logfile}
>>> if [ $? -ne 0 ]; then
>>> echo "Failed to copy rootfs hwpack files to SD Card"
>>
>>
>> Thanks Steven. My time got busy and this got pushed to my back burner, greatly
appreciated.
>>
>> Have you tired getting this applied to the upstream yet?
>>
>
> I created a fork on github, put in my changes, and made a pull
> request. My version is here:
>
> git://github.com/stevefalco/a10-tools.git
>
> Please give it a try and feed me any comments.
>
> Steve
I snagged it and ran up a fresh SD card. It booted as expected and so far networking is
working. Now to just to find some time to get the VGA working under Fedora.
Thanks for the confirmation. The pull was accepted, so it is now in the
mainline.
Steve
11:11 p.m.
On Thu, Aug 9, 2012 at 8:55 AM, Steven A. Falco <safalco(a)optonline.net> wrote:
I have tested creating images with console / xfce and doesnt work.
the image from website bellow boots fine.
https://www.miniand.com/forums/forums/2/topics/42
I am very impressed with performance of mk802, Its very small and run
very fast for the price, should be a good idea if fedora supports it.
my current desktop machine is very noise, I am thinking about
replacing with a mk802.
I will buy a Hackberry when its come back to stock.
8:03 a.m.
On 08/11/2012 12:11 AM, Itamar Reis Peixoto wrote:
On Thu, Aug 9, 2012 at 8:55 AM, Steven A. Falco
<safalco(a)optonline.net> wrote:
I have tested creating images with console / xfce and doesnt work.
the image from website bellow boots fine.
The nightly hardware packs are configured to use the hardware serial
console as their default out-put. For the mk802 you'll need to open up
the casing and find the pins to see the output.
Currently on my Mele A1000 graphics do not currently work. I suspect
this is just an issue with loading the driver that I haven't had the
time to investigate yet.
https://www.miniand.com/forums/forums/2/topics/42
I am very impressed with performance of mk802, Its very small and run
very fast for the price, should be a good idea if fedora supports it.
Good to hear. I don't have an mk802 to play with, but I'll try using
their image to sort out how they have X configured.
--
Scott Sullivan
4267
days inactive
4277
days old
30 comments
6 participants
participants (6)
-
Fernando Cassia -
itamar -
Jon -
Peter Robinson -
Scott Sullivan -
Steven A. Falco