March 28, 2020, 05:00:26 pm


Have you visited the Allwinner Chipset wiki? -

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - rgmhtt

It is much more than a MBR of 512 bytes,  The uboot is equivalent to an i386 BIOS.  The Cubietruck one I have here  for 10/26/17 is 545.6KB.  So your dd is much larger than moving a MBR.

I use the cheapest, smallest mSD card I can get for this purpose, and just dd the more.

I just uploaded the 10/26/17 Cubietruck uboot:

You can try that in place of the Cubie2 I have in my guide.

BTW, on Fedora/Centos, you install uboot-tools and there there is a directory (somewhere) with ALL the current various board uboots...
Another thought.

Your distro may be using the original Cubie uboot, not the independent sunxi uboot.  You would know this if your WiFi and Bluetooth work.  These were never 'cracked' by the open community.  The original uboot does not know how to switch to the sata, and a kernel that works with the original uboot would not know how to interact with the open sunxi uboot.  You would have to check the sunxi uboot site for Linaro support, or the Linaro web site.

Again, I use only Fedora and Centos.  In fact I am one of the armv7hl testers for these distros.

There are clear instructions on the Fedora arm site and Centos about this.  Plus I have it on my website:

I currently do not have a separate CubieTruck uboot on my site, but I can put one there for you.  When you boot up, what uboot version is reported to the console?

Allwinner A20 uboot for some time has 'know' that if there are no partitions on the mSD card, to look for sata or usb (though I have not tried usb for a long time).  I don't think they goot the nrand partitions working for booting...

It is all in the uboot.  see what my console looks like booting a Cubie2:

U-Boot SPL 2016.09.01 (Oct 19 2016 - 13:46:44)
DRAM: 1024 MiB
CPU: 912000000Hz, AXI/AHB/APB: 3/2/2
Trying to boot from MMC1

U-Boot 2016.09.01 (Oct 19 2016 - 13:46:44 +0000) Allwinner Technology

CPU:   Allwinner A20 (SUN7I)
Model: Cubietech Cubieboard2
I2C:   ready
DRAM:  1 GiB
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
SCSI:  Target spinup took 0 ms.
AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
flags: ncq stag pm led clo only pmp pio slum part ccc apst
Net:   eth0: ethernet@01c50000
starting USB...
USB0:   USB EHCI 1.00
USB1:   USB OHCI 1.0
USB2:   USB EHCI 1.00
USB3:   USB OHCI 1.0
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 2 for devices... 1 USB Device(s) found
Hit any key to stop autoboot:  2  1  0
switch to partitions #0, OK
mmc0 is current device
** Invalid partition 1 **
scanning bus for devices...
  Device 0: (0:0) Vendor: ATA Prod.: WDC WD3200BPVT-8 Rev: 01.0
            Type: Hard Disk
            Capacity: 305245.3 MB = 298.0 GB (625142448 x 512)
Found 1 device(s).

Device 0: (0:0) Vendor: ATA Prod.: WDC WD3200BPVT-8 Rev: 01.0
            Type: Hard Disk
            Capacity: 305245.3 MB = 298.0 GB (625142448 x 512)
... is now current device
Scanning scsi 0:1...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf

Deutsch / Re: openssl Problme
November 25, 2017, 07:54:06 pm
You probably have a self-signed certificate.  Browsers today treat this as an error condition that the user has to accept the 'risk' of using a self-signed cert.  After all, Mal could make a cert with the same content (other than the keys) as yours and trick your users into accepting it.

Thus you need to provide your users with YOUR keyid so they can store your certificate with confidence.  Or have control over the network such that they cannot be connected to anything but your NAS.  If you store the cert, you only go through this warning once.  Per user.

Or buy a cert.

If you are interested, I have published an Internet Draft on building an ECDSA PKI.  This does not directly fix your challenge, but if you have multiple servers for your users, they only need to accept your root cert then they will auto accept all certs signed in that PKI.

My draft can be found at:

I do have to rev it, as one grad student using it for his thesis for his PKI found a typo in one of the chmod commands...

Plus I want to add support for 802.1AR iDevID CSRs.

Note this is only for ECDSA certificates.  I try not to use RSA certs anymore, and EDDSA certs are in the next release (1.1.1).

Hope this helps
Deutsch / Re: openssl Problme
November 24, 2017, 09:01:13 am
I work a lot with OpenSSL (1.1.0), but on Fedora/Centos and ONLY in English.

If you provide your question and screen capture in English I may be able to help.

I really wish I could deal with German, but I am dyslexic a highly mono-linguistic.
I only have Cubietrucks and I use Fedora/Centos.


I suspect you have a uboot with Linaro.  Put JUST the uboot on the mSD; NO PARTITIONS.

Put all your OS partitions  on the SATA drive.

Boot and see what happens.

I worked with the uboot developer for Allwinner CPUs some years ago getting this working, and I use it all the time.  The key point is ONLY uboot on the mSD card.

Unlikely.  On INTEL, brightness is a BIOS function and the BIOS intercepting special keys.

armv7, as such does not have BIOS.  This type of control would have to be in UBOOT and the video driver.  So it will depend, in large measure, with the OS distro you are using.

I know there have been discussions here in the past about 'bare metal programming'.

So I suggest you do some searching here and see what you find.

Also look at the sunxi uboot work for Cubies and see how that work is.  That is where much of the raw driver work is that then makes it available to theLinux kernels.

I run Fedora and Centos.  I ask on the Fedora and Centos lists (both the regular and their specific ARM lists).

You are using Debian.  I would hope you have some connection already to those lists, if you are talking about dealing with systemd.  Ah systemd.  one of the services that so many Linux users love to complain about.

But then they want VM support...

Lots of things had to change to better support VMs.
You can get more information with:

systemctl -l status

Or look in the appropriate log files.

I really can't help in detail with debian as I am Centos/Fedora...

But there I use systemd and systemctl fairly regularly.

What version of Nextcloud are you using?  Their site says that v11 works with php 5.4, but prefers 5.5 for security and performance updates and works best with php 7.  V 12 only lists php 5.6+

We are working up a php7 build for Centos7 from the CLS srpm.

What kind of drive do you have on your Cubietruck?  I have an 240GB SSD available for starters.  Have you followed the simple technique to boot off sata with Fedora/Centos?  (only have uboot on mSD, no partitions at all, all partitions on sata)?
Look at Nextcloud over Owncloud.

Don't know if anyone has gotten it working on RPi; and I work with Centos on Cubies.  Challenge there is Nextcloud wants php 7; and that will take a bit as Redhat is still back at php 5.4!  But there are ways....

So OK for Owncloud.  Look at Nextcloud.

Now that is strange!  I use Fedora/Centos, and don't know how cubier works or if it has SELinux.

First quick test is check for SELinux and put it in permissive mode and try again.  If it works, you have to work with your SELinux policies.

If SELinux is NOT the barrier, then you need to look at your ftp.conf file (whatever your distro uses) and see how it is listening on the interfaces and if there are any operation rules per interface.

Definitely strange.  I vote for SELinux...
And thus you are locked into the uboot Cubie provides and MAYB E if you dig around you will find the logo file to replace.  More likely it is embedded somewhere and completely unchangeable.

You make your selection and you work with the consequences.
Which OS are you using?  Follow the general instructions for that OS skype install.  As I use Fedora, I follow what I would do on a Fedora-x64 system.