Announcing Fedora 19 ARM remix for Allwinner SOCs release 1, now with A20 support

[Hans de Goede]

Hi All,

I'm very happy to announce the first release (r1) of my Fedora 19 ARM
remix images for Allwinner A10, A10s, A13 and A20 based devices. This
release is based on the official Fedora 19 Final for ARM images,
with u-boot and kernel(s) from the linux-sunxi project:
http://linux-sunxi.org/

Besides all the goodies from Fedora-19, this release also contains
the following new items on the Allwinner / sunxi front:

-Support for the new dual core A20 soc (tested with cubieboard2),
this is based on forward porting the core machine code + various
drivers from allwinners 3.3 kernel source dump to the sunxi-3.4
sources. The following has been ported / is supported:
-uarts
-mmc controllers
-ehci and ohci usb controllers (usb controllers 1 and 2, controller
0 is an otg controller and is not supported yet.
-video output block (hdmi, vga, lcd, composite out)
-i2c controllers
-axp pmic including cpu voltage scaling
-rtc
-sound: analog in/out, hdmi audio, spdif out (spdif untested)
-ethernet controller (emac)
-sata controller
Note any functional blocks in the SOC which are not explictly
listed as supported above are not supported atm
-Support for a couple of new boards (38 boards in total now)

You can download it here:
http://scotland.proximity.on.ca/contrib-images/hansg/Fedora-19-a10-armhfp-r1.img.xz

sha1sum: a179afafd77c26c7022392d2fa72e3fd221dd33a

It is important to read the README, the image standard comes without
u-boot pre-loaded since u-boot is board specific. The image includes
a user-friendly simple script to install the right u-boot for
your board, but if you simply xzcat the image to an sdcard, and then
boot your device with the sdcard, things will *not* work.

See the README for a list of currently supported boards.

Known Issues:
-Many boards don't have an rtc (A10 and A20 have a builtin one),
or at least no battery backup for it, resulting in the date
+ time being wrong.
-If the date is of by more then a couple of months, "yum update"
won't work because certificate validation fails for the https
connection yum tries to make. So if yum fails to get its repodata
first check (and fix) your date
-The regular (host not otg) usb-port on A10s based boards can be a
bit quirky. It is best to plug in a hub even when using only one
device, otherwise the device may not be recognized. If this happens,
after adding a hub, often a power-cycle is needed too.
-The wifi chip on the Auxtek-T004 hdmi-stick is unsupported atm

Enjoy,

Hans


And to make sure everyone reads the README, let me print it here
in full:

Fedora 19 ARM for Allwinner A10, A10s, A13 and A20 devices README
-----------------------------------------------------------------

Quickstart guide
----------------

1) Insert an sdcard, note any data on the card will be destroyed!
2) Make sure the card is not mounted, run "mount" and if the card shows
up in the output umount its partitions
3) Write the img file to the card, ie as root do:
xzcat Fedora-19-a10-armhfp-r1.img.xz > /dev/mmcblk0
sync
4) The card is not yet ready for use! Since the A10 u-boot is board
specific, the image comes without any uboot install, follow the next
steps to install the right u-boot for your board
5) Remove the card, and re-insert it. The uboot partition should get
automatically mounted, if not mount it manually,
6) As root (or through sudo) run: <uboot-part-mount>/select-board.sh, ie:
sudo /run/media/hans/uboot/select-board.sh

If you've dialog installed the select-board.sh script will prompt for
your board. If you don't have dialog installed, it will print the list
of supported boards. Lookup your board and re-run the script with the
shortname for your board as argument, ie:
sudo /run/media/hans/uboot/select-board.sh mk802
7) umount the uboot and rootfs partitions, ie:
umount /run/media/hans/uboot
umount /run/media/hans/rootfs
8) Your sdcard is now ready for use
9) *Before* powering up your A10 device connect it to an hdmi or dvi monitor
10) When first booting from the sdcard inserted Fedora will automatically
reboot once, this is part of the process to resize the root partition to
fill the entire sdcard and is normal behavior.
11) After the automatic reboot Fedora will start with the initial-setup wizard:
11a) Configure networking, note:
* If you've an A10 board with wired ethernet and you want to use dhcp
you don't need to do anything.
* If you've an A20 board, your ethernet will have a random mac-address,
so if you want to configure a static ip-address and want it to stick
across reboots, go to the ethernet-tab, select the mac-address field
and delete its contents, so that the static ip address you're
configuring does not get tied to the random mac-address.
11b) Setup the time zone
11c) Set a root password
11d) Create a user
12) Log in as the just created user
13) Enjoy Fedora on your A10 device


Supported Devices:
------------------

Fedora 19 ARM for Allwinner A10 has been tested with the following devices:
* A13-OLinuXino-MICRO (Olimex)
* Auxtek T003 hdmi tv stick
* Auxtek T004 hdmi tv stick
* BA10 TV Box
* Cubieboard development board 1024 MB RAM
* Cubieboard2 (A20) development board
* Gooseberry development board
* Mele A1000G/A2000G 1024 MB RAM
* Mini-X 1024 MB RAM
* mk802 (with female mini hdmi) 512 MB RAM
* mk802 with A10s (s with a circle around it on the barcode label)
* mk802ii (with male normal hdmi) 1024 MB RAM
* r7 hdmi tv stick
* UHost U1A hdmi tv stick
* Wobo i5 TV Box

Fedora 19 ARM should also work on the following devices:
* A10 tablet sold under various names (whitelabel)
* A13 tablet sold under various names (whitelabel)
* A10s-OLinuXino-MICRO (Olimex)
* A13-OLinuXino (Olimex)
* A20-OLinuXino-MICRO (Olimex)
* Coby MID7042 tablet
* Coby MID8042 tablet
* Coby MID9742 tablet
* Cubieboard development board 512 MB RAM
* DNS AirTab M82 tablet
* EOMA68 A10 CPU card
* H6 netbook
* Hackberry development board
* Hyundai a7hd tablet
* iNet-97F Rev.2 (and clones) tablet
* Mele A1000/A2000 512 MB RAM
* Mele A3700
* Mini-X 512 MB RAM
* mk802 (with female mini hdmi) 1024 MB RAM
* pcDuino development board
* Point of View ProTab 2 IPS 9" tablet
* Point of View ProTab 2 IPS tablet with 3g
* XZPAD700 7" tablet

Configuring the display output
------------------------------

Multiple video outputs at the same time are not supported. By default
hdmi output with EDID is used for all devices, except for tablets/netbooks
where the default output is the lcd.

The default hdmi output with EDID will get the native resolution of your
TV / monitor and use that. Note that in order for this to work your TV /
monitor must be connected *and turned on*, before booting your device.

The output resolution can be configured with the disp.screen0_output_mode
kernel cmdline value, which can be found in the extrargs part of uEnv.txt in
the uboot partition. The default uEnv.txt contains the following value:
disp.screen0_output_mode=EDID:1280x720p60

This means try to use EDID and if no valid EDID info is found fallback to
1280x720p60.

The used output can be changed by adding disp.screen0_output_type=X to the
extraargs in uEnv.txt. With X being one of: 0:none; 1:lcd; 2:tv; 3:hdmi; 4:vga

Some per display type notes:
-lcd outputs: Hardcoded to the native mode, disp.screen0_output_mode is ignored
-tv: For the cvbs output disp.screen0_output_mode must be set to one of the
following: pal, pal-svideo, ntsc, ntsc-svideo, pal-m, pal-m-svideo, pal-nc,
pal-nc-svideo. Note the -svideo variants should only be used on boards with
an svideo connector, for composite out use the regular variants, ie:
disp.screen0_output_type=2 disp.screen0_output_mode=pal
-hdmi: To override the EDID detected mode, drop the "EDID:" from the
disp.screen0_output_mode value and set it to the desired mode, ie:
disp.screen0_output_type=3 disp.screen0_output_mode=1360x768p60
-vga: Does not support EDID, "EDID:" must be removed from the
disp.screen0_output_mode value otherwise it will be ignored. interlaced
progressive and refreshrate settings specified are ignored, each resolution
has hardcoded values for these. Example usage:
disp.screen0_output_type=4 disp.screen0_output_mode=1024x768


USB controller caveats
----------------------
The OTG USB controller in host mode only supports a limited number of
devices, plugging in a hub + mouse + keyboard typically will make either
the mouse or keyboard not work. This is a hardware limitation which we
will likely not be able to work around.

On tv-sticks and top-set boxes, simply avoid the otg connector, instead
use a hub in a regular host usb connector. Note on the mini-x the otg / host
marking is not always correct. If things don't work try using the OTG
connector instead!

On tablets and the gooseberry unfortunately only the otg connector is
available. One solution there is using a single usb-device which is
both a keyboard and a mouse at the same time. IE the receiver for logitech
wireless desktop sets.


Supported hardware components / features:
-----------------------------------------

Fedora 19 ARM for Allwinner A10 supports the following components:
* CPU + PMU + RAM
* Serial ports
* MMC cards
* Internal NAND storage (*)
* Framebuffer on lcd / vga / hdmi / composite video
* Sound both analog out and over hdmi
* OTG USB controller (*)
* Both standard USB host controllers
* Wifi
* Wired Ethernet
* SATA
* IR (untested at this time) (*)

*) Not supported on A20, the A20 support in the Fedora 19 A10 images is new,
and as such the driver code for these has not been forward-ported from the
Allwinner source dump to the sunxi-3.4 kernel the Fedora 19 A10 images use yet.


Unsupported hardware components:
--------------------------------

The following components require various proprietary blobs to be used, and
as such are not supported in the Fedora images. The kernel drivers for them
are present (usually as modules) (*), so if you add the necessary blobs you
might get these to work:
* Mali 400 GPU
* Cedar hardware video & audio decoding and encoding engine
* G2D 2d engine

*) Except for the A20


Differences from stock Fedora
-----------------------------
* Since the A10 is not a very powerful soc some services which are enabled by
default on Fedora are disabled in the image, see build-image.sh for a list.
* No plymouth: we log to a serial console for debugging so no pretty splash.
Also we don't use an initrd, so removing the console=ttyS0,115200 from
the extraargs in uEnv.txt will give plymouth, but so late it hardly matters.


Rebuilding the Fedora 19 ARM for Allwinner A10 disk image
---------------------------------------------------------

Building the Fedora 19 ARM for Allwinner A10 disk image consists of 2 steps
1) Building a uboot.tar.gz and rootfs.tar.gz "overlays", this is done
bu the build-boot-root-sh script
2) Combining uboot.tar.gz and rootfs.tar.gz with an official Fedora 19 arm img,
this combining is done by the build-image.sh script
The a10 image you downloaded is based on Fedora-XFCE-armhfp-19-1-sda.raw

These scripts are hosted here:
https://github.com/jwrdegoede/sunxi-fedora-scripts.git

A copy of the exact versions of these scripts used to build this Fedora A10
image can be found in the scripts directory of the uboot partition, the
kernel config used during the build can be found here too.

If you want to exactly reproduce this image it is important to use the
scripts from the scripts dir of the uboot partition, as the scripts contain
GIT tags used during the build to checkout the exact versions to build.

The pre-conditions these scripts expect to be met, and the exact usage of
them is documented in comments in the top of each script.

[Davide]

I've not yet had a chance to try out 19 r1 but I had a chance to try out 18 R2 on my AL-A13-RT713 based Tablet and I found the following problems:

1) After having done the postconfig stuff and user creation I cannot login into the device (ither X or text login) ... I think I get authenticated but then something crashes and I get chucked out

and prompted for login   again. I had a stripped down 18 r2 to fit inside a 512Mb uSD and that did not present the login issue so I'm sure it's something that it's trying to do after authentication.

2) I can't get the touchscreen to work and need usb mouse and keyboard to do anything on my tablet when running custom distribution.

Anyone have any idea how to address these 2 issues ?

Regards

David

---

Da: Hans de Goede <hdeg...@redhat.com>
A: linux...@googlegroups.com; Fedora ARM <a...@lists.fedoraproject.org>; Development discussions related to Fedora <de...@lists.fedoraproject.org>
Inviato: Venerdì 19 Luglio 2013 0:12
Oggetto: [linux-sunxi] Announcing Fedora 19 ARM remix for Allwinner SOCs release 1, now with A20 support

-- You received this message because you are subscribed to the Google Groups "linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsub...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Matson Hall]

wonderful!

2013/7/19 Davide <loui...@yahoo.it>

To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi...@googlegroups.com.

[Oliver Schinagl]

On 19-07-13 14:14, Davide wrote:

I've not yet had a chance to try out 19 r1 but I had a chance to try out 18 R2 on my AL-A13-RT713 based Tablet and I found the following problems:

1) After having done the postconfig stuff and user creation I cannot login into the device (ither X or text login) ... I think I get authenticated but then something crashes and I get chucked out

and prompted for login   again. I had a stripped down 18 r2 to fit inside a 512Mb uSD and that did not present the login issue so I'm sure it's something that it's trying to do after authentication.

How did you make that fit, you need atlaest 2.5 gigabyte I think. So if you put it on 512 mb uSD disk, i'm sure you are loosing files.

2) I can't get the touchscreen to work and need usb mouse and keyboard to do anything on my tablet when running custom distribution.

Firstly, you should really try 19 r1 before asking.
Secondly, touchscreen is far out of scope, but it's quite likely that your touchscreen doesn't have kernel support. If your lucky, there where sources in some allwinner code dump. If so, you can try to port that to our current 3.4. If your unlucky, there was only a GPL violating binary blob. No luck then. You can try writing one, asking the manufacturer for datasheet/driver.

To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi...@googlegroups.com.

[Davide]

Sorry ... I cant's manage that indentation without making a mess (yahoo mail isn't helping)  :(

Yep I stripped down all X stuff, unnecessary modules, yum cache and various other stuff that was not necessary for a non graphical environment. I just wanted to check out basic functionality before using kernel, modules and uboot to start a slackware ARM userland.

I will try 19 r1 ... but I thought my report would be interesting if there's any will to maintain the previous release. If that's not the case then forget my report ... I'll be back as soon as I manage to try  19 r1.

Concerning the touch .... the flect cable is glued with something like white silicon sealant and hides whatever electronic components it's directly connected to.

How can I investigate what sort of bus my touch is connected to ?

Regards

David

-----

[Oliver Schinagl]

On 20-07-13 08:44, Davide wrote:

Sorry ... I cant's manage that indentation without making a mess (yahoo mail isn't helping)  :(

Yep I stripped down all X stuff, unnecessary modules, yum cache and various other stuff that was not necessary for a non graphical environment. I just wanted to check out basic functionality before using kernel, modules and uboot to start a slackware ARM userland.

OOhhhhh, ok then it's quite possible yeah. And a nice starting point + learning point.

I will try 19 r1 ... but I thought my report would be interesting if there's any will to maintain the previous release. If that's not the case then forget my report ... I'll be back as soon as I manage to try  19 r1.

I don't know hansg's intentions, but, Fedora 18 will be supported by fedora as usual I suppose. The important bits for us are the kernel, kernel-modules and u-boot. Those are the same on Fedora 18 and 19 (or can be) and can be updated to whatever we have in our git at any time :)

Concerning the touch .... the flect cable is glued with something like white silicon sealant and hides whatever electronic components it's directly connected to.

How can I investigate what sort of bus my touch is connected to ?

i2c is my bet. But you can always boot stock android and see with lsmod which modules are loaded and with dmesg to see which ones are probed. And finally,the fex file should contain some touchscreen parameters as to how various touch screens are configured.

[Michal Suchanek]

Hello,

thanks for your work on 3.4 kernel.

I was able to build a kernel for both a10 and a20 based on your a20
patched source.

I tried building it a few times and the result of those attempts are
some build fix patches:
https://github.com/hramrach/linux-sunxi/commits/nand-3.4

This is work in progress and some of the patches are not very nice.
Especially core.c needs some merging from sun7i into sunxi.

Consider reviewing and importing some into r2. Some may not be
required anymore because they were for an older kernel version.

Thanks

Michal

[Hans de Goede]

Hi,

On 07/24/2013 11:17 AM, Michal Suchanek wrote:
> Hello,
>
> thanks for your work on 3.4 kernel.

You're welcome, and likewise thank you for your work :)

> I was able to build a kernel for both a10 and a20 based on your a20
> patched source.
>
> I tried building it a few times and the result of those attempts are
> some build fix patches:
> https://github.com/hramrach/linux-sunxi/commits/nand-3.4

I've rebased my tree onto the latest linux-sunxi/stage/sunxi-3.4
(which adds a much needed reboot fix from hno), and then cherry
picked your patches into my tree.

I skipped the def_config patch, before adding it to my tree I would
like to see a better commit message, including some sort of rationale
for the changes, as well as similar changes to the sun5i defconfig
to keep the various defconfigs more or less in sync.

I've also not taken the nand patch, since I believe the proper way
to get nand support on the a20 is to add support to the existing
sunxi-nand code, unless the a20 has a completely different controller
(I've not looked yet). With the dma_compat.h stuff I've written and
used in the sound and emac code, adding support to the existing
sunxi-nand code should be doable.

> This is work in progress and some of the patches are not very nice.
> Especially core.c needs some merging from sun7i into sunxi.

Agreed, I've just pushed a set of commits on top of the ones I
cherry picked from you which fully merge core.c, and I've also started
working towards merging the timer code, doing some much needed
cleanups of the sun4i/sun5i timer code as part of this.

You can find my work on this here:
https://github.com/jwrdegoede/linux-sunxi/commits/sunxi-3.4

I expect to finish the timer merging work tomorrow, and then I'll
be merging in various patches posted by others, since my tree
also more or less serves as a patch collection tree for amery.

Regards,

Hans

[Davide]

I made an image builder for Slackware ARM based on the work done for the Fedora 19 r1 (big thanks to all those who contributed to the fedora image for Allwinner soc), but instead of making changes to the image itself I build an image with just what's required for your chosen target.Also the image size is user definable (so long as you choose to make it big enough to hold your cosen root image.
Some of the stuff I do is slackware specific but most of it is reusable, alternatively any other distro specific stuff can be fixed before unmounting the loop devices and writing to target block device.
If anyone likes it feel free to reuse it : http://ftp.slackware.org.uk/slackwarearm/people/louigi600/

Regards
David

[Michal Suchanek]

On 28 July 2013 00:29, Hans de Goede <hdeg...@redhat.com> wrote:
> Hi,
>
>
> On 07/24/2013 11:17 AM, Michal Suchanek wrote:
>>
>> Hello,
>>
>> thanks for your work on 3.4 kernel.
>
>
> You're welcome, and likewise thank you for your work :)
>
>
>> I was able to build a kernel for both a10 and a20 based on your a20
>> patched source.
>>
>> I tried building it a few times and the result of those attempts are
>> some build fix patches:
>> https://github.com/hramrach/linux-sunxi/commits/nand-3.4
>
>
> I've rebased my tree onto the latest linux-sunxi/stage/sunxi-3.4
> (which adds a much needed reboot fix from hno), and then cherry
> picked your patches into my tree.

Cherry picking is nice but I specifically put some of the build fixes
after the commits that break build so that the branch does not have
like 70 commits that don't build.

>
> I skipped the def_config patch, before adding it to my tree I would
> like to see a better commit message, including some sort of rationale
> for the changes, as well as similar changes to the sun5i defconfig
> to keep the various defconfigs more or less in sync.

The rationale for adding sun7i defconfig is to have one. I would not
push the sun4i changes either.

>
> I've also not taken the nand patch, since I believe the proper way

Did not get it working anyway.

Thanks

Michal.

[Hans de Goede]

Hi,

On 07/28/2013 11:33 AM, Michal Suchanek wrote:
> On 28 July 2013 00:29, Hans de Goede <hdeg...@redhat.com> wrote:
>> Hi,
>>
>>
>> On 07/24/2013 11:17 AM, Michal Suchanek wrote:
>>>
>>> Hello,
>>>
>>> thanks for your work on 3.4 kernel.
>>
>>
>> You're welcome, and likewise thank you for your work :)
>>
>>
>>> I was able to build a kernel for both a10 and a20 based on your a20
>>> patched source.
>>>
>>> I tried building it a few times and the result of those attempts are
>>> some build fix patches:
>>> https://github.com/hramrach/linux-sunxi/commits/nand-3.4
>>
>>
>> I've rebased my tree onto the latest linux-sunxi/stage/sunxi-3.4
>> (which adds a much needed reboot fix from hno), and then cherry
>> picked your patches into my tree.
>
> Cherry picking is nice but I specifically put some of the build fixes
> after the commits that break build so that the branch does not have
> like 70 commits that don't build.

Ok, I needed todo a forced push anyways, so I've moved the one build-fix
from your tree which is out of order compared to mine (the debug-macro one)
to the front. The other out of order patch (the one renaming all the irqs),
I've left were I put it yesterday as that one has conflicts with a bunch of
other patches.

I've also completed the merge of the core and timer code
to plat-sunxi, as always you can grab it all here:
https://github.com/jwrdegoede/linux-sunxi/commits/sunxi-3.4

>
>>
>> I skipped the def_config patch, before adding it to my tree I would
>> like to see a better commit message, including some sort of rationale
>> for the changes, as well as similar changes to the sun5i defconfig
>> to keep the various defconfigs more or less in sync.
>
> The rationale for adding sun7i defconfig is to have one. I would not
> push the sun4i changes either.

Ah, ok, can you do a separate patch for this, and how does your defconfig
compare to this one ? :
https://github.com/wingrime/linux-sunxi/commit/6cb58a859057e59b76a6699c3e48afb0831700f6

>
>>
>> I've also not taken the nand patch, since I believe the proper way
>
> Did not get it working anyway.

Note that the cubieboard repo:
https://github.com/cubieboard2/linux-sunxi/commits/hans-sunxi-3.4

Has some wip on this.

Regards,

Hans

[Michal Suchanek]

On 28 July 2013 13:19, Hans de Goede <hdeg...@redhat.com> wrote:
>
> On 07/28/2013 11:33 AM, Michal Suchanek wrote:
>>
>> On 28 July 2013 00:29, Hans de Goede <hdeg...@redhat.com> wrote:
>>>
>>> On 07/24/2013 11:17 AM, Michal Suchanek wrote:
>>>>

>>> I've rebased my tree onto the latest linux-sunxi/stage/sunxi-3.4
>>> (which adds a much needed reboot fix from hno), and then cherry
>>> picked your patches into my tree.
>>
>>
>> Cherry picking is nice but I specifically put some of the build fixes
>> after the commits that break build so that the branch does not have
>> like 70 commits that don't build.
>
>
> Ok, I needed todo a forced push anyways, so I've moved the one build-fix
> from your tree which is out of order compared to mine (the debug-macro one)
> to the front. The other out of order patch (the one renaming all the irqs),
> I've left were I put it yesterday as that one has conflicts with a bunch of
> other patches.

Yes, it does conflict. There are some patches that rename irqs a few
at a time together with other changes. Still you need irqs merged so
that you can enable PLAT_SUNXI which enables sunxi configs like
selecting the debug uart.

>
> I've also completed the merge of the core and timer code
> to plat-sunxi, as always you can grab it all here:
> https://github.com/jwrdegoede/linux-sunxi/commits/sunxi-3.4

nice :)

>
>
>>
>>>
>>> I skipped the def_config patch, before adding it to my tree I would
>>> like to see a better commit message, including some sort of rationale
>>> for the changes, as well as similar changes to the sun5i defconfig
>>> to keep the various defconfigs more or less in sync.
>>
>>
>> The rationale for adding sun7i defconfig is to have one. I would not
>> push the sun4i changes either.
>
>
> Ah, ok, can you do a separate patch for this, and how does your defconfig
> compare to this one ? :
> https://github.com/wingrime/linux-sunxi/commit/6cb58a859057e59b76a6699c3e48afb0831700f6

https://github.com/hramrach/linux-sunxi/commit/710f863d4ccb0f16d684defdb54ae057a2017456

I guess it enables more stuff. For one it enables the sun7i
architecture which does not seem to be enabled in wingrime's config.

Thanks

Michal

[Hans de Goede]

Hi,

On 07/28/2013 02:03 PM, Michal Suchanek wrote:
> On 28 July 2013 13:19, Hans de Goede <hdeg...@redhat.com> wrote:

<snip>

>>> The rationale for adding sun7i defconfig is to have one. I would not
>>> push the sun4i changes either.
>>
>>
>> Ah, ok, can you do a separate patch for this, and how does your defconfig
>> compare to this one ? :
>> https://github.com/wingrime/linux-sunxi/commit/6cb58a859057e59b76a6699c3e48afb0831700f6
>
> https://github.com/hramrach/linux-sunxi/commit/710f863d4ccb0f16d684defdb54ae057a2017456
>
> I guess it enables more stuff. For one it enables the sun7i
> architecture which does not seem to be enabled in wingrime's config.

Thanks, added to my sunxi-3.4 branch.

Regards,

Hans

[haripr...@gmail.com]

hi Hans de Goede , i am following the steps you have mentioned above for the compilation of source code of fedora for A20-OLinuXino-MICRO , will it work properly? (you have specified that it should work for all A20,10 based devicess, but i'm confused)

[elia...@gmail.com]

Op vrijdag 19 juli 2013 00:12:35 UTC+2 schreef Hans de Goede:

> The following has been ported / is supported:
>

> -sound: analog in/out

> Fedora 19 ARM should also work on the following devices:
>

> * A13-OLinuXino (Olimex)
>

Hi, thanks very much for the release!

I've already tested the Fedora 18 remix on my A13-OLinuXino (even with WIFI working!), but I can't get the audio to work:
ALSA reports that no soundcards could be detected.

However using the Debian image of Olimex, I was able to get audio through my headphones and the mic worked also. I looked up the driver, and it appeared to be "sun5i-CODEC". On the rootfs of the Fedora image, I looked into "/lib/modules/<sun5i-kernel>/kernel/sound/soc/", but I only could see a "sun4i" directory, even without a "sun4i-CODEC" counterpart.
I read somewhere else that code of "/sound/soc/sun5i" was merged with "/sound/soc/sun4i", but I tried to modprobe each driver in "/sound/soc/sun4i" without success.

Do I have to recompile the whole kernel, or just compile the "sun5i-CODEC" module, or do I have to do something different to get audio working?
Thank you very much!

P.S.: Do you know whether it is possible to run a synthesiser such as ZynAddSubFX with low latency on such boards (using the onboard soundcard)?

[Oliver Schinagl]

On 08/30/13 19:24, elia...@gmail.com wrote:
> Op vrijdag 19 juli 2013 00:12:35 UTC+2 schreef Hans de Goede:
>> The following has been ported / is supported:
>>
>> -sound: analog in/out
>> Fedora 19 ARM should also work on the following devices:
>>
>> * A13-OLinuXino (Olimex)
>>
>
> Hi, thanks very much for the release!
>
> I've already tested the Fedora 18 remix on my A13-OLinuXino (even with WIFI working!), but I can't get the audio to work:
> ALSA reports that no soundcards could be detected.
>
> However using the Debian image of Olimex, I was able to get audio through my headphones and the mic worked also. I looked up the driver, and it appeared to be "sun5i-CODEC". On the rootfs of the Fedora image, I looked into "/lib/modules/<sun5i-kernel>/kernel/sound/soc/", but I only could see a "sun4i" directory, even without a "sun4i-CODEC" counterpart.
> I read somewhere else that code of "/sound/soc/sun5i" was merged with "/sound/soc/sun4i", but I tried to modprobe each driver in "/sound/soc/sun4i" without success.
>
> Do I have to recompile the whole kernel, or just compile the "sun5i-CODEC" module, or do I have to do something different to get audio working?
> Thank you very much!

Actually the driver is called sunxi these days, so upgradeing the kernel
(from linux-sunxi github stage/sunxi-3.4 and using the config from the
fedora image might be the best idea. Either that or wait for the next
release of Fedora with an updated kernel

>
> P.S.: Do you know whether it is possible to run a synthesiser such as ZynAddSubFX with low latency on such boards (using the onboard soundcard)?
>

I don't know, but I wouldn't hold my hopes up for the audio quality of
these sound chips ...

[Hans de Goede]

Hi,

On 08/30/2013 07:24 PM, elia...@gmail.com wrote:
> Op vrijdag 19 juli 2013 00:12:35 UTC+2 schreef Hans de Goede:
>> The following has been ported / is supported:
>>
>> -sound: analog in/out
>> Fedora 19 ARM should also work on the following devices:
>>
>> * A13-OLinuXino (Olimex)
>>
>
> Hi, thanks very much for the release!
>
> I've already tested the Fedora 18 remix on my A13-OLinuXino (even with WIFI working!), but I can't get the audio to work:
> ALSA reports that no soundcards could be detected.
>
> However using the Debian image of Olimex, I was able to get audio through my headphones and the mic worked also. I looked up the driver, and it appeared to be "sun5i-CODEC". On the rootfs of the Fedora image, I looked into "/lib/modules/<sun5i-kernel>/kernel/sound/soc/", but I only could see a "sun4i" directory, even without a "sun4i-CODEC" counterpart.
> I read somewhere else that code of "/sound/soc/sun5i" was merged with "/sound/soc/sun4i", but I tried to modprobe each driver in "/sound/soc/sun4i" without success.
>
> Do I have to recompile the whole kernel, or just compile the "sun5i-CODEC" module, or do I have to do something different to get audio working?
> Thank you very much!

You're not seeing the sun4i-codec module (which works for sun5i too) because it is build into the kernel.

You should see some audio devices under /dev/snd and /sys/class/sound

While checking things work with Fedora 19 ARM remix for Allwinner SOCs release 1 I did notice that there
is an error in the fex file for the A13-OLinuXino, causing only audio-out to be present, I've just pushed
an updated fex file here:
https://github.com/linux-sunxi/sunxi-boards/blob/master/sys_config/a13/a13-olinuxino.fex

If you save this file, convert it to a script.bin file using the fex2bin utility from here:
https://github.com/linux-sunxi/sunxi-tools

And then overwrite script.bin in the uboot partition of your sdcard with the new one you should
also get a capture device.

Regards,

Hans

[Hans de Goede]

Hi,

On 09/01/2013 02:55 PM, Elias Vanderstuyft wrote:
> Ok, adding only "vconsole.keymap=be-latin1" (not "LANG=nl_NL.UTF-8", this causes kernel panic) after the extraargs field in uEnv.txt, successfully enabled azerty in tty consoles, however X11 is still using qwerty (however once logged in into Xfce, I can set keyboard layout to belgian, so it's not that important to me).
>
> Now, I've got another issue: the LCD display (A13-LCD10TS <https://www.olimex.com/Products/OLinuXino/A13/A13-LCD10TS/open-source-hardware>) I bought for my A13-OLinuXino-WIFI <https://www.olimex.com/Products/OLinuXino/A13/A13-OLinuXino-WIFI/open-source-hardware> doesn't work on Fedora 18 r2 ARM.
>
> Using the debian SD card, it works only if I pick the script.bin file associated with LCD_1024x600 which can be found on http://www.olimex.com/wiki/index.php?title=Configuration_of_hardware_in_the_debian_image#Changing_A13-OLinuxino_settings_to_VGA_.28800x600_or_1024x768.29_or_LCD_.28480x272_or_800x480_or_1024x600.29
>
> by downloading the VGA_LCD_scripts_A13.zip file.
>
> It also contains the corresponding fex file, which I included as attachment.
>
>
> I first tried to copy the [lcd0_para] variables from that file to the fex file you provided in your last mail. Without success, when the power is turned on the lcd blinks one time, and then remains off.
>
> Then I tried to copy the [disp_init] section. Again without success.
>
> Finally I tried to use the (working with debian) script.bin corresponding with script_GPIO_1024x600.fex. Still without success.
>
>
> Do you have some suggestions?

So my 7" LCD panel arrived last Tuesday, and in the mean time I've figured out
the problem. Some lcd settings in the olimex provided fex files are wrong,
and it seems their own kernel is somehow ignoring these.

Specifically they have lcd_pwm_used=0, even though the pwm is used for
the backlight, and lcd_pwm_pol=0, which should be 1 since their backlight
pwm line is active low.

I've attached a fex file which should work with the 10" olimex lcd module
on the olinuxino-a13. Please give it a try and let me know if this works
for you.

Regards,

Hans

[hmand...@gmail.com]

Hi Hans,
i tryed to use your fedora 19 remix on my Olinuxino A20 Rev.D but don't start,
there is only red and green leds power on static (no blink) but i have always hdmi signal off (i verified that script is for hdmi).

I used uSD 16GB 200x (30MB/s) SanDisk class 10.

have you tips ?

[Hans de Goede]

Hi,

On 09/12/2013 04:27 PM, hmand...@gmail.com wrote:
> Hi Hans,
> i tryed to use your fedora 19 remix on my Olinuxino A20 Rev.D but don't start,
> there is only red and green leds power on static (no blink) but i have always hdmi signal off (i verified that script is for hdmi).

Have you tried hooking up the uart to a serial port / usb <-> serial convertor too
see if there are any kernel boot messages?

Various people have been successfully using the image with hdmi out on the Olinuxino A20 Rev.D,
without any issues. How are you powering the board ? Note that the board has an onboard
regulator, so it needs 6V as a minimum input voltage. Also try replacing the sdcard and the
hdmi cable. If that all fails, try another Linux distro, ie olimex's official images,
if that fails too, it could be your board is broken.

Regards,

Hans

[Davide Soldan]

I apologize to everyone, I was totally wrong in my previous post...I've removed the post from the web interface of the group...
I'm testing Hans's fedora 19 on Olinuxino a10s.
Like mentioned before I can boot fedora and login from serial port and all seems to work well. Xorg log is http://pastebin.com/PEZf9eKq
but the screen is black and it doesn't receive any signals...
Maybe dmesg could be useful: http://pastebin.com/w1CNLg4V
The board/sdcard/hdmi cable works well as I can run the base debian distro from olimex with the same components.
Also the various script.bin, uImage ecc should be ok as I checked that were the one's for sun5i.
Any idea about this issue?
Thank you and again sorry for the previous wrong post
Regards
Davide

In data giovedì 19 settembre 2013 06:47:09, davide.sold...@gmail.com ha scritto:
> Hi Hans,
> I'm having a problem testing your fedora 19 remix on Olinuxino a10s.
> The board boot well, and I can login from the serial port, but Xorg crashes with these outputs:
> at boot: http://pastebin.com/PEZf9eKq
> after boot if I login and try startx: http://pastebin.com/HateKEi8
> the board/sdcard/hdmi cable works well as I can run the base debian distro from olimex with the same components.
> Also the various script.bin, uImage ecc should be ok as I checked that were the one's for sun5i.
> Can you help me with this problem?
> Thank you a lot!
> Regards
> Davide

[Hans de Goede]

Hi,

On 09/19/2013 03:47 PM, davide.sold...@gmail.com wrote:
> Hi Hans,
> I'm having a problem testing your fedora 19 remix on Olinuxino a10s.
> The board boot well, and I can login from the serial port, but Xorg crashes with these outputs:
> at boot: http://pastebin.com/PEZf9eKq
> after boot if I login and try startx: http://pastebin.com/HateKEi8
> the board/sdcard/hdmi cable works well as I can run the base debian distro from olimex with the same components.
> Also the various script.bin, uImage ecc should be ok as I checked that were the one's for sun5i.
> Can you help me with this problem?

Yes, there was an error in the fex / script.bin file for the Olinuxino a10s causing it
to not send video to the hdmi output with Fedora 19 ARM remix for Allwinner SOCs release 1.

This is fixed in release 2, but in release 2 I ended up picking a bad u-boot snapshot (and
doing a bad QA job as well), so that one does not boot on sun5i devices at all.

Attached is a good script.bin for the Olinuxino a10s, if you drop this in the u-boot
partition of your sdcard the hdmi out should work.

Regards,

Hans

[deasy]

Mele A1000G support ? Sure ? It's with an A31 right ?
As someone asked on the channel linux-sunxi for linux distro on a1000g(a31) and we have answered there is no distro for it.

[Roman Mamedov]

On Mon, 11 Nov 2013 10:01:05 -0800 (PST)
deasy <ledesillu...@gmail.com> wrote:

> Mele A1000G support ? Sure ? It's with an A31 right ?
> As someone asked on the channel linux-sunxi for linux distro on a1000g(a31)
> and we have answered there is no distro for it.

There was Mele A1000G with A10 and 1GB of RAM:
http://dx.com/p/mele-a1000g-android-4-0-google-tv-player-w-wi-fi-sd-1gb-ram-8gb-rom-vga-black-161823

The A31 one is called "A1000G Quad".
http://www.aliexpress.com/store/product/Quad-Core-Mele-A1000G-Quad-Mini-PC-Android-4-1-TV-Box-Allwinner-ARM-CortexA7-2GB/715968_818962879.html

--
With respect,
Roman

[Hans de Goede]

Hi,

On 11/11/2013 07:56 PM, Roman Mamedov wrote:
> On Mon, 11 Nov 2013 10:01:05 -0800 (PST)
> deasy <ledesillu...@gmail.com> wrote:
>
>> Mele A1000G support ? Sure ? It's with an A31 right ?
>> As someone asked on the channel linux-sunxi for linux distro on a1000g(a31)
>> and we have answered there is no distro for it.
>
> There was Mele A1000G with A10 and 1GB of RAM:
> http://dx.com/p/mele-a1000g-android-4-0-google-tv-player-w-wi-fi-sd-1gb-ram-8gb-rom-vga-black-161823

Right, that is what the A1000G support is for.

> The A31 one is called "A1000G Quad".
> http://www.aliexpress.com/store/product/Quad-Core-Mele-A1000G-Quad-Mini-PC-Android-4-1-TV-Box-Allwinner-ARM-CortexA7-2GB/715968_818962879.html

And not for this one.

Regards,

Hans

[Richard W.M. Jones]

Aren't those two the same thing?

How hackable are either of these boxes?

Rich.

--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW

[Richard W.M. Jones]

On Mon, Nov 11, 2013 at 08:43:48PM +0000, Richard W.M. Jones wrote:
> On Mon, Nov 11, 2013 at 08:11:35PM +0100, Hans de Goede wrote:
> > Hi,
> >
> > On 11/11/2013 07:56 PM, Roman Mamedov wrote:
> > >On Mon, 11 Nov 2013 10:01:05 -0800 (PST)
> > >deasy <ledesillu...@gmail.com> wrote:
> > >
> > >>Mele A1000G support ? Sure ? It's with an A31 right ?
> > >>As someone asked on the channel linux-sunxi for linux distro on a1000g(a31)
> > >>and we have answered there is no distro for it.
> > >
> > >There was Mele A1000G with A10 and 1GB of RAM:
> > >http://dx.com/p/mele-a1000g-android-4-0-google-tv-player-w-wi-fi-sd-1gb-ram-8gb-rom-vga-black-161823
> >
> > Right, that is what the A1000G support is for.
> >
> > >The A31 one is called "A1000G Quad".
> > >http://www.aliexpress.com/store/product/Quad-Core-Mele-A1000G-Quad-Mini-PC-Android-4-1-TV-Box-Allwinner-ARM-CortexA7-2GB/715968_818962879.html
> >
> > And not for this one.
>
> Aren't those two the same thing?

Obviously I see they're not the same.

How hackable is the A31-based box?

[Arokux X]

On Mon, Nov 11, 2013 at 9:44 PM, Richard W.M. Jones <rjo...@redhat.com> wrote:
> On Mon, Nov 11, 2013 at 08:43:48PM +0000, Richard W.M. Jones wrote:
>> On Mon, Nov 11, 2013 at 08:11:35PM +0100, Hans de Goede wrote:
>> > Hi,
>> >
>> > On 11/11/2013 07:56 PM, Roman Mamedov wrote:
>> > >On Mon, 11 Nov 2013 10:01:05 -0800 (PST)
>> > >deasy <ledesillu...@gmail.com> wrote:
>> > >
>> > >>Mele A1000G support ? Sure ? It's with an A31 right ?
>> > >>As someone asked on the channel linux-sunxi for linux distro on a1000g(a31)
>> > >>and we have answered there is no distro for it.
>> > >
>> > >There was Mele A1000G with A10 and 1GB of RAM:
>> > >http://dx.com/p/mele-a1000g-android-4-0-google-tv-player-w-wi-fi-sd-1gb-ram-8gb-rom-vga-black-161823
>> >
>> > Right, that is what the A1000G support is for.
>> >
>> > >The A31 one is called "A1000G Quad".
>> > >http://www.aliexpress.com/store/product/Quad-Core-Mele-A1000G-Quad-Mini-PC-Android-4-1-TV-Box-Allwinner-ARM-CortexA7-2GB/715968_818962879.html
>> >
>> > And not for this one.
>>
>> Aren't those two the same thing?
>
> Obviously I see they're not the same.
>
> How hackable is the A31-based box?

http://linux-sunxi.org/A31#Community_Support

>
> Rich.
>
> --
> Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
> Fedora Windows cross-compiler. Compile Windows programs, test, and
> build Windows installers. Over 100 libraries supported.
> http://fedoraproject.org/wiki/MinGW
>

[Hans de Goede]

Hi,

On 11/11/2013 09:44 PM, Richard W.M. Jones wrote:
> On Mon, Nov 11, 2013 at 08:43:48PM +0000, Richard W.M. Jones wrote:
>> On Mon, Nov 11, 2013 at 08:11:35PM +0100, Hans de Goede wrote:
>>> Hi,
>>>
>>> On 11/11/2013 07:56 PM, Roman Mamedov wrote:
>>>> On Mon, 11 Nov 2013 10:01:05 -0800 (PST)
>>>> deasy <ledesillu...@gmail.com> wrote:
>>>>
>>>>> Mele A1000G support ? Sure ? It's with an A31 right ?
>>>>> As someone asked on the channel linux-sunxi for linux distro on a1000g(a31)
>>>>> and we have answered there is no distro for it.
>>>>
>>>> There was Mele A1000G with A10 and 1GB of RAM:
>>>> http://dx.com/p/mele-a1000g-android-4-0-google-tv-player-w-wi-fi-sd-1gb-ram-8gb-rom-vga-black-161823
>>>
>>> Right, that is what the A1000G support is for.
>>>
>>>> The A31 one is called "A1000G Quad".
>>>> http://www.aliexpress.com/store/product/Quad-Core-Mele-A1000G-Quad-Mini-PC-Android-4-1-TV-Box-Allwinner-ARM-CortexA7-2GB/715968_818962879.html
>>>
>>> And not for this one.
>>
>> Aren't those two the same thing?
>
> Obviously I see they're not the same.
>
> How hackable is the A31-based box?

AFAIK it is similar to other allwinner devices and it is reasonable hack-able,
(ie not locked down, most source code available in the form of android kernels)
but no one really is working on it. AFAIK there is some rudimentary support
in the upstream kernel. Assuming this soc uses the same ip-blocks for mmc and
network as the A10 / A20 it could be that support for it will get better as those
get better support upstream.

Regards,

Hans

[Richard W.M. Jones]

On Tue, Nov 12, 2013 at 08:21:57AM +0100, Hans de Goede wrote:
> AFAIK it is similar to other allwinner devices and it is reasonable
> hack-able, (ie not locked down, most source code available in the
> form of android kernels) but no one really is working on it. AFAIK
> there is some rudimentary support in the upstream kernel. Assuming
> this soc uses the same ip-blocks for mmc and network as the A10 /
> A20 it could be that support for it will get better as those get
> better support upstream.

I ordered one, so I'll let you know how it goes.

Rich.

--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones

virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top

[9ep...@gmail.com]

Hi, I tried this image on my A20 tablet. http://www.tinydeal.com/9-hd-screen-android-422-8gb-a20-dual-core-tablet-pc-w-wifi-p-102831.html .

I tried with cubieboard2 uboot settings.

I got several error messages: (AXP) driver using configuration failed(323)
(AXP)power_start = 0, axp20_ldo2: Failed to create debugfs directory, [mmc_pm]: failed to fetch sdio card configuration!,
disp_clk: Could not find a matching pll-freq for 53900000 pclk
axp20_buck3: incomplete constraints, leaving on
[mmc-err] smc 0 err, cmd 52, RTO
EXT4-fs (mmcblk0p3): couldn't mount as ext3 due to feature incompatibilities
Kernel panic - not syncing: Attempted to kill init exitcode=0x0000000b

Continuously rebooting
Is it bossible to get it working?

Regards
Seppo

[Luc Verhaegen]

Smells like you are using a wrong script.bin for your device.

I do not think that we have general sunxi support for this
tablet. In such a case, you should be working through:

http://linux-sunxi.org/New_Board_howto

The latter 3 bits still need to be filled in, but you can just
send the retrieved information to our ml as well.

Luc Verhaegen.

[afonso bordado]

Hi,first im still a newb to this linux on arm thing, so far i managed to boot and put wifi working, but i need help with the touchscreen, i dont know the make or model, but i belive it to be a goodix one because the driver recognises that there is a goodix panel, but i think it can also be a GSL1680 because i2c-2 there is something on 0x40 wich is where the driver responds. When i insert the goodix_touch.ko module i get an error in the dmesg, i dont know how to interpert this so please help me, i apreciate any help provided, thanks.

dmesg: http://pastebin.com/QPjsWD0w

[SK]

Smells like you are using a wrong script.bin for your device.

I do not think that we have general sunxi support for this
tablet. In such a case, you should be working through:

http://linux-sunxi.org/New_Board_howto

The latter 3 bits still need to be filled in, but you can just
send the retrieved information to our ml as well.

Luc Verhaegen.

 I retrieved information from my tablet using fel via usb.

Regards
Seppo

[Luc Verhaegen]

Did you see Step 2 there at our http://linux-sunxi.org/New_Board_howto
?

Luc Verhaegen.

[SK]

Did you see Step 2 there at our http://linux-sunxi.org/New_Board_howto
?

Luc Verhaegen.

Simple wiki page created: http://linux-sunxi.org/Unknown_SoftwinerEvb

Regards
Seppo

[Luc Verhaegen]

On Sun, Dec 15, 2013 at 11:55:21PM -0800, SK wrote:
>
> Simple wiki page created: http://linux-sunxi.org/Unknown_SoftwinerEvb
>
> Regards
> Seppo

A quick bin2fex later, and a bit of googling revealed this device to be
commonly known as MID-S906.

I have moved the page.

Luc Verhaegen.

[SK]

> I tried with cubieboard2 uboot settings.
>
> I got several error messages: (AXP) driver using configuration failed(323)
> (AXP)power_start = 0, axp20_ldo2: Failed to create debugfs directory, [mmc_pm]: failed to fetch sdio card configuration!,
> disp_clk: Could not find a matching pll-freq for 53900000 pclk
> axp20_buck3: incomplete constraints, leaving on
> [mmc-err] smc 0 err, cmd 52, RTO
> EXT4-fs (mmcblk0p3): couldn't mount as ext3 due to feature incompatibilities
> Kernel panic - not syncing: Attempted to kill init exitcode=0x0000000b
>
> Continuously rebooting
> Is it bossible to get it working?
>
> Regards
> Seppo

Smells like you are using a wrong script.bin for your device.

Luc Verhaegen.

I tried now cubieboard2 uboot and with script.bin retrieved from my tablet, only difference was that picture appear in tablet own display (cubie2 script.bin only via HDMI) and with same errors and rebooting,

Not mounting filesystem > EXT4-fs (mmcblk0p3): couldn't mount as ext3 due to feature incompatibilities.
Is it possible to get partion mounted with editing script.bin only?

Regards
Seppo

[nej...@gmail.com]

DEAR HANS:

I HAVE INSTALLED THE FEDORA 19 REMIX ON MY CHEAP CHINESE TABLETS.
HAVE 2 OF THEM, AND BOTH ARE 7" A13 BASED TABLETS.
THE FEDORA BOOTS FINE, I HAVE THE OTG USB CONNECTED TO MY WIRELESS KEYBOARD/MOUSE AND WORKS HAPPY.

WIFI IS NOT DETECTED, AND I HAVE NO IDEA HOW TO MAKE IT WORK ...

I NEED TO COMUNICATE WITH THE TABLET USING SSH IN ORDER TO UPLOAD MY PROGRAMS AND TO CONFIGURE THE TABLET FOR MY USE.

PLEASE, ANY ASSISTANCE ON THE TOPIC WILL BE VERY APPRECIATED.

I AM NEW IN THE FIELD, SO I BEG YOUR PARDON IF THIS IS A STUPID QUESTION ...

ALL THE BEST !

NELSON

[Ian Daniher]

Nelson,

Emails sent in all caps are generally not good netiquette, as this is approximately the equivalent of shouting.

That said, I just successfully solved a similar problem on similar hardware. There are a few pieces of information to acquire before we're able to help you.

First off, what chipset do the tablets use? Hints to this effect can be found by running the command "lsusb" from in android and noting the vendor and product ID, a pair of hex numbers, possibly like "148f:7601." It is usually the only such pair not containing "1d6b" as the first number. You can also open your tablets and inspect the wifi card directly. Usually it is a small circuit board soldered to the motherboard. If you can read numbers off the small square chip, this also should have this information.

In order to get the wireless to work on my 7" A13 tablet, I also had to extract, decompile, and modify the script.bin / script.fex hardware configuration file to ensure the internal USB port was enabled by default. To do this, you will need a PC with Linux installed and a copy of https://github.com/linux-sunxi/sunxi-tools. With information about your chipset, we will be better able to help you through this process.

Best,

--
Ian Daniher

[Nelson Grodzicki]

Dear Ian:

I apologize for the "noise" in the groups.

Never will happen again, and this is a promise.

By the way, with the external USB Hub, I was able to have my mouse/keyboard working and also a tiny WiFi adaptor working very happy !!

So, I was able to have access to Internet from the XFCE !

Since I am almost a complete ignorant in Linux my opinion may not be valid, but I have to say after playing with Ubuntu, Debian, Puppy, Armstrong and other distributions, this one is by far the BEST distribution I ever tryied.

The modules inside the Tablet are:

Touch Screen (does not work with the Fedora yet)  -- zet6221

WiFi Realtek -- 8188eu

USB-Ethernet controller -- RTL 8150

I think the external WiFi module is the 8192cu but not sure.

Question:

How do I activate the ssh access to the Fedora so I can start working from my Mac ??

Also, I need to start up the Fedora in the console mode and not in Graphic, how do I do that ?

Well, again, thank you a million for your fantastic job !!

Al the best.

Nelson - 

2014/1/8 Ian Daniher <explod...@gmail.com>

[Nelson Grodzicki]

Dear Ian:

Just checked the script.bin for my A13 tablet and usbc1 is =1.

This is the copy of the USB section of my actual tablet using bin2fex utility.

[usbc0]
usb_used = 1
usb_port_type = 2

usb_detect_type = 1
usb_id_gpio = port:PG02<0><1><default><default>
usb_det_vbus_gpio = port:PG01<0><0><default><default>
usb_drv_vbus_gpio = port:PG12<1><0><default><0>
usb_host_init_state = 0


[usbc1]
usb_used = 1
usb_port_type = 1

usb_detect_type = 1
usb_id_gpio =
usb_det_vbus_gpio =

usb_drv_vbus_gpio = port:power203<1><0><default><0>
usb_host_init_state = 0


The external WiFi adaptor works great.
Any clue how to activate the internal WiFi on the tablet ?

It is a Realtek 8188eu (checked visually on the board itself)

Thanks a million.

Nelson

2014/1/8 Nelson Grodzicki <nej...@gmail.com>

[Ian Daniher]

usb_host_init_state should be set to 1. Recompile and replace the script.bin file.

—
From My Tiny Glowing Screen

[Nelson Grodzicki]

Good day Ian:

Chinese tablet is bacaming very rebel.

Still internal WiFi does not want to show up ...

This is the new [usb] section of my script.bin

[usbc0]

usb_used = 1

usb_port_type = 2

usb_detect_type = 1

usb_id_gpio = port:PG02<0><1><default><default>

usb_det_vbus_gpio = port:PG01<0><0><default><default>

usb_drv_vbus_gpio = port:PG12<1><0><default><0>

usb_host_init_state = 0

[usbc1]

usb_used = 1

usb_port_type = 1

usb_detect_type = 0

usb_id_gpio =

usb_det_vbus_gpio =

usb_drv_vbus_gpio = port:power203<1><0><default><0>

usb_host_init_state = 1

Any idea ?

The external adaptor (a nano EDUP USB adaptor) works fantastic ! but I need the internal ....

Thanks a million .

Nelson

2014/1/12 Ian Daniher <explod...@gmail.com>

[nils...@gmail.com]

понедельник, 13 января 2014 г., 17:43:25 UTC+4 пользователь Nelson Grodzicki написал:

> Still internal WiFi does not want to show up ...

what 'dmesg' out after 'modprobe 8188eu' ?

[Nelson Grodzicki]

Hi,

so far this is what I got from dmseg

[10947.177718] sw_usb_enable_hcd: usbc_num = 1

[10947.182129] usbcore: registered new interface driver rtl8188eu

Will see..

Thanks !!!!

2014/1/13 <nils...@gmail.com>

[Nelson Grodzicki]

Just realized that the WiFi adaptor is RTL8188etv which has a different vendor id (0179).

Perhaps I need to modify the .ko driver which is set for RTL8188eu.

How do I do that the easy way ??

Thanks --

Nelson

2014/1/13 Nelson Grodzicki <nej...@gmail.com>

[Patrick Wood]

Use the latest code.  This device was added with this commit: 9cfbbed3b2b098774b04553843d2f4092b8f7fe8 from this patch: https://groups.google.com/forum/#!topic/linux-sunxi/oMmB72S8qzQ

[Nelson Grodzicki]

Thanks, any LINK to download the patch ??

Nelson

2014/1/14 Patrick Wood <patric...@gmail.com>

[Steev Klimaszewski]

On Tue, Jan 14, 2014 at 12:09 PM, Nelson Grodzicki <nej...@gmail.com> wrote:

Thanks, any LINK to download the patch ??

Nelson

Maybe check the github?  

 https://github.com/linux-sunxi/linux-sunxi/commit/9cfbbed3b2b098774b04553843d2f4092b8f7fe8

hint: if you add .patch or .diff to the end of a github url, it will provide the file as a patch or diff.

This e-mail and any attachments are for the sole use of the intended recipients(s) and may be confidential. Use of any Pwnie Express product signifies your agreement to the Rapid Focus Security EULA and is subject to export controls under the U.S. Commerce Department’s Export Administration Regulations (“EAR”).

[Nelson Grodzicki]

I am becaming nuts trying to apply the patch. The reason? I am just another stupid newbie ...

Do you have the new rtl8188.ko compiled for A13 at hand? Or at least, the source code so I can make the module by myself? SORRY, SHAME ON ME !

All the best !!

Nelson

2014/1/14 Steev Klimaszewski <st...@pwnieexpress.com>

--
You received this message because you are subscribed to a topic in the Google Groups "linux-sunxi" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/linux-sunxi/PLgUj-KefKQ/unsubscribe.
To unsubscribe from this group and all of its topics, send an email to linux-sunxi...@googlegroups.com.

[Nelson Grodzicki]

By the way, perhaps someone have the new RTL8188etv.ko module already compiled for A13 available and want to share it with me??

Nelson

2014/1/14 Steev Klimaszewski <st...@pwnieexpress.com>

On Tue, Jan 14, 2014 at 12:09 PM, Nelson Grodzicki <nej...@gmail.com> wrote:

--

[afonso bordado]

im compiling with the new patch right now, it might not work on your kernel, meanwhile have you tried
"echo 0bda 0179 > /sys/bus/usb/drivers/rtl8188eu/new_id" on the old driver?
it used to work for me

[Nelson Grodzicki]

Dear Afonso: IT'S ALIVE !!! As always, the simplest the best. It worked first attempt.

Now I will start to work on my projetct.

I need to deactivate the xfce4 desktop and replace the xfwm4 for the old good OPENBOX and be able to launch a startx session form SSH.

Any suggestions to make a shortcut will be appreciated.

Thank you a million and muito obrigado !

All the best. Nelson.

2014/1/15 afonso bordado <afonso...@gmail.com>

[Nelson Grodzicki]

Dear All: any one knows how to rotate the screen in the 7" A13 chinese tablet running the latest Fedora? fbcon works nice but only for the console, xandr does not work in graphic environment. I am using LXDE with openbox on top of lightdm. Any help will be appreciated.nelson.

2014/1/15 Nelson Grodzicki <nej...@gmail.com>

[SK]

Smells like you are using a wrong script.bin for your device.


Luc Verhaegen.

 

Few days ago i finally got my MID S906 booting to Fedora 19r1
But usb not seem to activated. (no power to keyboard or mouse)

 
  I get access to Fedora initial setup screen but not able to use keyboard or mouse.

   Does it need some sort of script to activate usb after booting?
   Or powered usb hub?

Regards
Seppo

[Olliver Schinagl]

Depends, but generally, no; it should just work; double check your
script.bin's usb0 settings, make sure it's powered. A powered USB hub
helps generally here.
>
> Regards
> Seppo
>
> --
> You received this message because you are subscribed to the Google
> Groups "linux-sunxi" group.
> To unsubscribe from this group and stop receiving emails from it, send

[SK]

perjantai, 24. tammikuuta 2014 12.18.52 UTC+2 Olliver Schinagl kirjoitti:

On 24-01-14 10:18, SK wrote:
>
>
>
>
>
>
>
>
>         Smells like you are using a wrong script.bin for your device.
>
>
>         Luc Verhaegen.
>
>
>
>     Few days ago i finally got my MID S906 booting to Fedora 19r1
>     But usb not seem to activated. (no power to keyboard or mouse)
>
>
>    I get access to Fedora initial setup screen but not able to use
> keyboard or mouse.
>
>     Does it need some sort of script to activate usb after booting?
>     Or powered usb hub?
Depends, but generally, no; it should just work; double check your
script.bin's usb0 settings, make sure it's powered.  A powered USB hub
helps generally here.

My tablet script.bin usb section:
 

[usbc0]
usb_used = 1
usb_port_type = 2
usb_detect_type = 1

usb_id_gpio = port:PH04<0><1><default><default>
usb_det_vbus_gpio = "axp_ctrl"
usb_drv_vbus_gpio = port:PB09<1><0><default><0>
usb_ac_enable_gpio = port:PH05<1><0><default><0>
usb_restrict_gpio = 0
usb_host_init_state = 0
usb_restric_flag = 0
usb_restric_voltage = 3550000
usb_restric_capacity = 5

Regards
Seppo

[Ian Daniher]

Depending upon your kernel and hardware, you may need to configure the port as host-only?

> usb_port_type = 1

> usb_host_init_state = 1

On my A20 board with a similar basic configuration, I have to manually enable the pin used for usb_drv_vbus_gpio to enable the 5v rail.

--

You received this message because you are subscribed to a topic in the Google Groups "linux-sunxi" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/linux-sunxi/PLgUj-KefKQ/unsubscribe.
To unsubscribe from this group and all of its topics, send an email to linux-sunxi...@googlegroups.com.

[SK]

perjantai, 24. tammikuuta 2014 18.30.06 UTC+2 Ian Daniher kirjoitti:

Depending upon your kernel and hardware, you may need to configure the port as host-only?

> usb_port_type = 1

> usb_host_init_state = 1

On my A20 board with a similar basic configuration, I have to manually enable the pin used for usb_drv_vbus_gpio to enable the 5v rail.

Not work with host-only configuration.
Nor with powered usb hub.

How can i enable this usb_drv_vbus_gpio pin?

Regards
Seppo

[Ian Daniher]

Something like pio -m 'PB9<1><2><1><1>' ought to enable the 5v rail for that port, possibly solving your issues.

You'll need to get 'pio' source from https://github.com/linux-sunxi/sunxi-tools/blob/master/pio.c and compile it.

[SK]

Earlier i used fel to retrieve script.bin and boot1.header from tablet.
I do not have serial port set up in my tablet.

Can i use fel-gpio script to manipulate gpio settings when tablet is in fel mode from my laptop?
   "fel-gpio:  A script which used fel to upload fel-pio to the target, and which then can use the pio utility, and manipulate  gpio settings, over fel/usb"

If possible, could you advice this procedure?