October 18, 2019, 01:19:30 pm

News:

Have you visited the Allwinner Chipset wiki? - http://linux-sunxi.org/


Buster, Xenial and Bionic - updated 6.7.2019

Started by slovenia, December 24, 2013, 03:23:11 pm

Previous topic - Next topic

soundcheck

Just found this in LMS 7.8 buildme.sh


# Supported OSes:
#
# Linux (Perl 5.8.8, 5.10.0, 5.12.4, 5.14.1, 5.16.3)


I guess I need to downgrade perl??  Any ideas how to do it?

castalla

Quote from: soundcheck on June 13, 2014, 10:25:47 am
Just found this in LMS 7.8 buildme.sh


# Supported OSes:
#
# Linux (Perl 5.8.8, 5.10.0, 5.12.4, 5.14.1, 5.16.3)


I guess I need to downgrade perl??  Any ideas how to do it?


You might get some help on http://forums.slimdevices.com/index.php

david88

After a number of updates, I realized I have about 800MB of old kernels on my CT. Is it safe to just delete the old directories?

3.4.75-igorpecovnik.com+
3.4.75-sun7i+
3.4.79-sun7i+
3.4.91-sun7i+ (this one is in use now based on uname)

slovenia

Quote from: david88 on June 13, 2014, 08:24:17 pm
After a number of updates, I realized I have about 800MB of old kernels on my CT. Is it safe to just delete the old directories?

3.4.75-igorpecovnik.com+
3.4.75-sun7i+
3.4.79-sun7i+
3.4.91-sun7i+ (this one is in use now based on uname)


Sure - remove inactive kernel files under /boot and inactive modules under /lib/modules
Debian and Ubuntu images with kernel 3.4.110, 4.3.3, 4.4
http://www.armbian.com

soundcheck

@castalla

Last comment about my LMS subject


Regarding "EASY". What's your setup? Are you actually running slovenias image?

Wheezy comes with Perl 5.14 and Jessie with 5.18. And LMS <=7.9.0 just supports <= 5.14 on ARM.

The ways out:
* Either I use Wheezy, but that gets me back to rather crappy (for ARM)  gcc 4.6, or
* I manage to downgrade to Perl 5.14 on my Jessie image, or
* I manage to get an LMS with Perl 5.18 support for ARM.

Thx

BASKA

Hi everyone!  :)
Tell me please, who knows.
How can you make an update separately only the kernel?
At the moment I have installed and configured for my needs - CTDebian 2.0.
I can only update the kernel? If yes - please tell me how to do it.
Thank you in advance.

castalla

Quote from: soundcheck on June 14, 2014, 04:25:20 am
@castalla

Last comment about my LMS subject


Regarding "EASY". What's your setup? Are you actually running slovenias image?

Wheezy comes with Perl 5.14 and Jessie with 5.18. And LMS <=7.9.0 just supports <= 5.14 on ARM.

The ways out:
* Either I use Wheezy, but that gets me back to rather crappy (for ARM)  gcc 4.6, or
* I manage to downgrade to Perl 5.14 on my Jessie image, or
* I manage to get an LMS with Perl 5.18 support for ARM.

Thx


Yes ... using the 2.0 version.  Works without any issues.

soundcheck

Quote from: BASKA on June 14, 2014, 01:48:28 pm
Hi everyone!  :)
Tell me please, who knows.
How can you make an update separately only the kernel?
At the moment I have installed and configured for my needs - CTDebian 2.0.
I can only update the kernel? If yes - please tell me how to do it.
Thank you in advance.


That's pretty easy. ;)  (If you know how)

If you ran slovenia's built script successfully, you'll have the base environment settings done.
The kernel sources can then be found under $DEST/Cubie/linux-sunxi

You then just configure the  new/updated/patched kernel, you compile it, and then you copy the uimage/modules/firmware over to the CT. (Have a look at the slovenia build script first and then
search in the forum)

Good luck.


soundcheck

Hi slovenia.


Two little improvement proposals.

You might update the default /etc/network/interfaces to introduce an option for static IP.

Enclosed my setup:


/etc/network/interfaces
# interfaces(5) file used by ifup(8) and ifdown(8)

auto lo
iface lo inet loopback

###DHCP setting#################################################################
#######################
auto eth0
allow-hotplug eth0
iface eth0 inet dhcp

###STATIC IP setting############################################################
#######################
#auto eth0
#allow-hotplug eth0
#iface eth0 inet static
#address 192.168.X.YY
#netmask 255.255.255.0
#network 192.168.X.0
#broadcast 192.168.X.255
#gateway 192.168.X.1

###WLAN setting#################################################################
#######################
#auto wlan0
#allow-hotplug wlan0
#iface wlan0 inet dhcp
#    wpa-ssid SSID
#    wpa-psk xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
# to generate proper encrypted key: wpa_passphrase yourSSID yourpassword




Beside that you could add "nfs-common" to the base image.

Cheers

cubiezomb



soundcheck

@castalla

To confirm:

Just installed the logitechmediaserver 7.9.0.-beta on a Wheezy image.

On the Wheezy image, with perl 5.14 in place it as easy as you suggested.

Thx

DEVIL


slovenia

Quote from: DEVIL on June 18, 2014, 05:58:19 am
V2.1 with Kernel 3.4.93 ---> kernel headers are broken!


How do you mean broken? They looks o.k. to me but It's true that I haven't done anything with them. I only created them in the compile process. Compilation was completed without any errors.
Debian and Ubuntu images with kernel 3.4.110, 4.3.3, 4.4
http://www.armbian.com

playassoff

Hello everyone,

I have problem with Sunxi-IR module. Of course I'm using this image, current version 2.1.

My hardware.conf:

root@cubie:/etc/lirc# cat hardware.conf

#Chosen Remote Control
REMOTE="Custom"
REMOTE_MODULES="sunxi_lirc"
REMOTE_DRIVER="default"
# REMOTE_DEVICE=""
REMOTE_DEVICE="/dev/lirc1"
REMOTE_SOCKET="/dev/lircd"
#REMOTE_SOCKET="/var/run/lirc/lircd"

REMOTE_LIRCD_CONF="/etc/lirc/lircd.conf"
REMOTE_LIRCD_ARGS=""

#Chosen IR Transmitter
TRANSMITTER="Custom"
TRANSMITTER_MODULES="lirc_gpio"
TRANSMITTER_DRIVER="default"
TRANSMITTER_DEVICE="/dev/lirc0"
TRANSMITTER_SOCKET="/dev/lircd"
TRANSMITTER_LIRCD_CONF="/etc/lirc/lircd.conf"
TRANSMITTER_LIRCD_ARGS=""

#Enable lircd
START_LIRCD="true"

#Don't start lircmd even if there seems to be a good config file
#START_LIRCMD="false"

#Try to load appropriate kernel modules
LOAD_MODULES="true"

# Default configuration files for your hardware if any
LIRCMD_CONF=""

FORCE_NONINTERACTIVE_RECONFIGURATION="false"
START_LIRCMD="true"


0. First of all I'm trying to check if sunxi-ir is working.

root@cubie:/etc/lirc# service lirc stop

root@cubie:/etc/lirc# cat /dev/lirc1 | hexdump
0000000 22aa 0100 1194 0000 022b 0100 0215 0000
0000010 0215 0100 0215 0000 022b 0100 0215 0000
0000040 0215 0100 022a 0000 0215 0100 066a 0000
0000050 022b 0100 067f 0000 0215 0100 067f 0000
0000060 0215 0100 067f 0000 01d5 0100 06bf 0000
0000070 0215 0100 067f 0000 022b 0100 066a 0000
..and so on

and
root@cubie:/etc/lirc# mode2 -d /dev/lirc1
pulse 8938
space 4436
pulse 533
space 533
pulse 555
space 533
...and so on


It looks that everything is OK.

1. I tried to record pilot config. And this is result:

root@cubie:/etc/lirc# irrecord -d /dev/lirc0 --disable-namespace test.conf
Press RETURN now to start recording.
................................................................................
Found gap: 16275
Please keep on pressing buttons like described above.
................................................................................
Space/pulse encoded remote control found.
Signal length is 67.
No header data.
Found trail pulse: 543
Found repeat code: 8919 2223
Found repeat gap: 16275
Signals are space encoded.
Signal length is 33
Now enter the names for the buttons.

Please enter the name for the next button (press <ENTER> to finish recording)
POWER

Now hold down button "POWER".
Something went wrong. Please try again. (9 retries left)
Something went wrong. Please try again. (8 retries left)
Something went wrong. Please try again. (7 retries left)
Something went wrong. Please try again. (6 retries left)
Something went wrong. Please try again. (5 retries left)
Something went wrong. Please try again. (4 retries left)
Something went wrong. Please try again. (3 retries left)
Something went wrong. Please try again. (2 retries left)
Something went wrong. Please try again. (1 retries left)
Something went wrong.
Try using the -f option.


With -f option or without --disable-namespace result is always the same. I have no idea what I'm doing wrong. Hardware.conf is not configured correctly?

Here is generated test.conf:
root@cubie:/etc/lirc# cat test.conf

# Please make this file available to others
# by sending it to <lirc@bartelmus.de>
#
# this config file was automatically generated
# using lirc-0.9.0-pre1(default) on Wed Jun 18 18:07:27 2014
#
# contributed by
#
# brand:                       test.conf
# model no. of remote control:
# devices being controlled by this remote:
#

begin remote

  name  test.conf
  bits           33
  flags SPACE_ENC
  eps            30
  aeps          100

  one           537  1658
  zero          537   540
  ptrail        543
  repeat       8919  2223
  gap          16275
  repeat_gap   16275
  toggle_bit_mask 0x0

      begin codes
      end codes

end remote