[fedora-arm] Testing CMA=64M on low memory devices (BeagleBones)

2014-08-15 Thread Nicolas Chauvet
Hi, I would request beaglebones users (either Black or white) to do some tests about a possible cma=64M to be set on kernel cmdline: # sed -i 's/^ABC_BASEARGS="\(.*\)"/ABC_BASEARGS="\1 cma=64M\"/' /etc/sysconfig/arm-boot-config # a-b-c # reboot By default cma is set to 16 and is not enought for

Re: [fedora-arm] Testing CMA=64M on low memory devices (BeagleBones)

2014-08-15 Thread Peter Robinson
On Fri, Aug 15, 2014 at 5:40 PM, Nicolas Chauvet wrote: > Hi, > > I would request beaglebones users (either Black or white) to do some tests > about a possible > cma=64M to be set on kernel cmdline: > > # sed -i 's/^ABC_BASEARGS="\(.*\)"/ABC_BASEARGS="\1 cma=64M\"/' > /etc/sysconfig/arm-boot-confi

[fedora-arm] Touchscreen support for Cubieboard?

2014-08-15 Thread Robert Moskowitz
A 3.5" TFT (800x480) with touchscreen control to your Cubieboard1 or Cubieboard2 http://www.cubieforums.com/index.php/topic,2910.0.html I see touchscreen support in 3.16 for the A10 listed. ___ arm mailing list arm@lists.fedoraproject.org https://ad

Re: [fedora-arm] Touchscreen support for Cubieboard?

2014-08-15 Thread Peter Robinson
On Fri, Aug 15, 2014 at 7:04 PM, Robert Moskowitz wrote: > A 3.5" TFT (800x480) with touchscreen control to your Cubieboard1 or > Cubieboard2 > > http://www.cubieforums.com/index.php/topic,2910.0.html > > I see touchscreen support in 3.16 for the A10 listed. Given we don't have display support I'

Re: [fedora-arm] Touchscreen support for Cubieboard?

2014-08-15 Thread Robert Moskowitz
On 08/15/2014 02:20 PM, Peter Robinson wrote: On Fri, Aug 15, 2014 at 7:04 PM, Robert Moskowitz wrote: A 3.5" TFT (800x480) with touchscreen control to your Cubieboard1 or Cubieboard2 http://www.cubieforums.com/index.php/topic,2910.0.html I see touchscreen support in 3.16 for the A10 listed.

[fedora-arm] Fedora-Xfce-armhfp-21-20140815-sda.raw.xz problems with sshd

2014-08-15 Thread Robert Moskowitz
My cubieboard2 does not have an rtc, so at boot time the clock is at the epoche start. Once the network is up, then NTP sets the clock. So I tried connecting to SSH after the install and got: Read from socket failed: Connection reset by peer systemctl status sshd.service, said something about

[fedora-arm] Setting date/time on firstboot - Re: Fedora-Xfce-armhfp-21-20140815-sda.raw.xz problems with sshd

2014-08-15 Thread Robert Moskowitz
I would suspect that a number of armv7 boards lack an RTC, and an old date will be bad for a lot of processes beyound just SSH key generation. So on first boot (and maybe any boot), check the system time. If it is ZERO, then read some file that has the last boot date and update with that. Th

[fedora-arm] arm rawhide report: 20140816 changes

2014-08-15 Thread arm Fedora Rawhide Report
Broken deps for aarch64 -- [APLpy] APLpy-0.9.8-5.fc21.noarch requires pywcs [ATpy] ATpy-0.9.7-5.fc21.noarch requires python-astropy python3-ATpy-0.9.7-5.fc21.noarch requires python3-astropy [OpenLP] OpenLP-2.0.5