September 18, 2019, 07:34:00 am

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

smotritel89

something which results:

cd /usr/src
git clone -b pat-3.4.79  https://github.com/patrickhwood/linux-sunxi   
cd /linux-sunxi
curl https://raw.githubusercontent.com/igorpecovnik/Cubietruck-Debian/master/config/kernel.config > .config
make prepare
make scripts
make modules


then try to test Compiling "Hello.c":

make -C /lib/modules/3.4.79-sun7i+/build M=/root/test modules
make[1]: Entering directory `/usr/src/linux-sunxi'
  CC [M]  /root/test/hello.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /root/test/hello.mod.o
  LD [M]  /root/test/hello.ko


try

insmod hello.ko

result:

Error: could not insert module hello.ko: Invalid module format
dmesg:  hello: no symbol version for module_layout


How to Fix ?






quickpass

Quote from: slovenia on May 02, 2014, 01:01:05 am

1. I have no experience with Plex Media Server but if it works on RasPI than it is possible to be installed on Cubieboard. My image included. Beware that if you want to run a media center (XBMC or similar) you will have troubles playing HD videos since drivers are not fully developed yet.

2 and 3. You can't flash this image directly to NAND. You have to create SD card, boot and transfer/mirror/rsync the content to NAND. Utility (installer) is included ... workaround (if trouble occurred) is described in first post.


Thanks slovenia for your reply. I plan to use my CT as a headless home server (NAS, Plex Media Server, Cloud, etc.) I don't plan to run any media center or anything like that.

I tried to write this image version 1.9 using ImageWriter with success. My CT boots with no problem. I can ssh to it but can't see anything from my TV (connect via HDMI). I guess this is due to no memory reserve for video? I will try to install Plex Media Server to see if it works and will report back. I am new to Linux so not sure if I can get any luck.

slovenia

QuoteThanks slovenia for your reply. I plan to use my CT as a headless home server (NAS, Plex Media Server, Cloud, etc.) I don't plan to run any media center or anything like that.


This image is designed for such usage.

QuoteI tried to write this image version 1.9 using ImageWriter with success. My CT boots with no problem. I can ssh to it but can't see anything from my TV (connect via HDMI). I guess this is due to no memory reserve for video? I will try to install Plex Media Server to see if it works and will report back. I am new to Linux so not sure if I can get any luck.


Glad to hear that. No, memory reservation does not affect CLI. In this case you probably installed wrong version in term (VGA/HDMI) or I made some bug on the way :) ? You can change this in /boot/uEnv.ct 

Change:
script=/boot/ct-vga.bin
to
script=/boot/ct-hdmi.bin
Debian and Ubuntu images with kernel 3.4.110, 4.3.3, 4.4
http://www.armbian.com

shider

@slovenia
First I wanted to thank You for a great image. It's really fast and stable.

Testing it on cubieboard2 and I discovered problems associated with LEDs. "disable_led.sh" script is prepared exclusively for Cubietruck. Cubieboard2 has only two LEDs: "/sys/class/leds/green:ph20:led1" and "/sys/class/leds/blue:ph21:led2". The script runs on four Cubietruck LEDs and on Cubieboard green still shines.
Generally, the script itself is not needed. A suitable modification can be done in a boot script. Example for Cubieboard2:

[leds_para]
leds_used = 1
leds_num = 2
leds_pin_1 = port:PH20<1><default><default><0>
leds_name_1 = "green:ph20:led1"
leds_default_1 = 0
leds_trigger_1 = "none"
leds_pin_2 = port:PH21<1><default><default><0>
leds_name_2 = "blue:ph21:led2"
leds_default_2 = 0
leds_trigger_2 = "none"


The second problem prevents the use of the blue LED. It is impossible to enable it. I do not know exactly which module is causing it, but after commenting modules: bcmdhd, rfcomm, hidp, lirc_gpio, sunxi_lirc the problem disappeared.
Using Tapatalk

twist

So after using 3 Versions of this image i am very satisfied with it  ;D
Very good work. I hope you will improve it for a long time.

I donated you a very big cup of coffee or tea to keep you awake for working hehe.

Greetings from a half Slovenian ^^
Have a nice summer :)


cgelan

Thank you for the great CT Wheezy  SD card image!
This allows me to use my favourite distribution on my Cubietruck. So far I'm fine, boot OK, install of additional packages OK. Now setting up a headless server.

There are, however three things I'd like to change and couldn't really figure out how to do it.
1) I'd like to have "ttyX" mentioned on my console in the login screen (e.g. "Debian GNU/Linux wheezy hostname ttyX")
2) I'd like to see boot messages on screen while booting. (dmesg is OK but only accessable if boot went through OK))
3) Is there a value between LEDs superbright and totally disabled?
Allright just Q No 3 is really Cubietruck related.

Thank you for your fine work
Eike (from Paraguay)

slovenia

@shider
Thanks for using and for the feedback. 8) I am using "non fex method" because you can play with leds on the fly if you like. They are active during boot which I consider helpful. You can attach one to the drive activity ... search on the forum. I am aware that there are certain differences between CB2 and CT but since I only have Cubietruck I can't test all. The honest subtitle for this image should be: "it should work on CB2 but not tested by author". :-[ I was already thinking to get myself one CB2 for this purpose.

QuoteThe second problem prevents the use of the blue LED.


This is a bit strange.  ??? It would be helpful to find out which module is causing problems.
If you have CB2 then remove wireless module for good anyway ...

@twist
QuoteVery good work. I hope you will improve it for a long time.
I donated you a very big cup of coffee or tea to keep you awake for working hehe.


Tnx. Cheers! ;)

@Eike
1. I don't understand exactly where you want this to be displayed - check those files /etc/issue /etc/motd /root/.bashrc and do some google to get the names for desired variables
2. Edit and change boot parameters in /boot/uEnv.ct or uEnv.cb (for CB2),"console="
3. No, it's digital.
Debian and Ubuntu images with kernel 3.4.110, 4.3.3, 4.4
http://www.armbian.com

jedie

I think there should be somewhere a community driven FAQ for this project.
Such a list with short tips like:

To enable boot output: Edit and change boot parameters in /boot/uEnv.ct or uEnv.cb (for CB2):
-"console=ttyS0,115200"
+"console="

Maybe a good point is: https://github.com/igorpecovnik/Cubietruck-Debian/wiki/FAQ ?

EDIT: I added some more information into the FAQ ;)

jedie

I try now the update to "jessie".

One "Problem" while dist-upgrade: ramlog is a own package and will be removes while updating.
What's about "busybox-syslogd" witch IMHO also write into RAM only.

EDIT: If i have a SATA SSD, then i should change /etc/sysfs.conf and set
block/sda/queue/scheduler from cfq to noop, isn't it?

slovenia

Quote from: jedie on May 05, 2014, 05:55:07 am
I try now the update to "jessie".

One "Problem" while dist-upgrade: ramlog is a own package and will be removes while updating.
What's about "busybox-syslogd" witch IMHO also write into RAM only.


Thanks for adding to FAQ 8). Will add too.

Ramlog package was installed manually. It is for general usage - you can have any/all logs in ram and that's important when you add services.

If you do upgrade to jessy, ramlog fails? What if you install it manually? The package is here.
Debian and Ubuntu images with kernel 3.4.110, 4.3.3, 4.4
http://www.armbian.com

jedie

Quote from: slovenia on May 05, 2014, 06:25:05 am
If you do upgrade to jessy, ramlog fails? What if you install it manually? The package is here.

The dist-upgrade routine will remove the package.
Think i can reinstall it... But why a own package, if busybox-syslogd exists? OK, busybox will be installed, too. But what's are the avertage of the own package?

Btw. One point for the FAQ: How to disable WLAN ???
My old solution was: to add iwconfig wlan0 txpower off to /etc/rc.local
I add this to https://github.com/igorpecovnik/Cubietruck-Debian/wiki/FAQ#disable-wifi
But what's the best solution for this?

slovenia

Quote from: jedie on May 05, 2014, 06:29:57 am
Quote from: slovenia on May 05, 2014, 06:25:05 am
If you do upgrade to jessy, ramlog fails? What if you install it manually? The package is here.

The dist-upgrade routine will remove the package.
Think i can reinstall it... But why a own package, if busybox-syslogd exists? OK, busybox will be installed, too. But what's are the avertage of the own package?

Btw. One point for the FAQ: How to disable WLAN ???
My old solution was: to add iwconfig wlan0 txpower off to /etc/rc.local
But what's the best solution for this?


I see "ramlog" more advanced. It's sad that it's not a part of a distro / developed any more ... it looks like a perfect solution for embedded system logging.

Yes, why not. It's working well. (on and off)

Debian and Ubuntu images with kernel 3.4.110, 4.3.3, 4.4
http://www.armbian.com

jedie

The "load info" is in https://github.com/igorpecovnik/Cubietruck-Debian/blob/master/scripts/bashrc and will be copied with:
# install custom bashrc
cp $SRC/scripts/bashrc $DEST/output/sdcard/root/.bashrc


Why not something like this:
cat Cubietruck-Debian/scripts/bashrc >> /etc/bash.bashrc

So that's its in the global bashrc so that normal logins also display the load info...?

EDIT: OK, i see a "error" in Drive temperature... But the other works for a normal user.

EDIT2: What's about this:
Put the Cubietruck-Debian/scripts/bashrc file somethere in the filesystem and call it e.g. with "source" in /etc/bash.bashrc
So it's callable for the user on prompt, too.

jedie

The problem is a normal user get a error for /usr/sbin/hddtemp /dev/sda I have create a bugfix and refactor the script: https://github.com/igorpecovnik/Cubietruck-Debian/pull/16

jedie

Quote from: jedie on May 05, 2014, 06:29:57 am
Btw. One point for the FAQ: How to disable WLAN ???
My old solution was: to add iwconfig wlan0 txpower off to /etc/rc.local
I add this to https://github.com/igorpecovnik/Cubietruck-Debian/wiki/FAQ#disable-wifi

But there is also a p2p0 device. What is this?

So i have to also add iwconfig p2p0 txpower off for this.

EDIT: See also a thread about a backup script: http://www.cubieforums.com/index.php?topic=2490.0