Jens Bauer

You can set the register values from within u-boot directly if you've a serial connection and stop autoboot: https://groups.google.com/d/msg/linux-sunxi/Y_Zh5juEJG4/egjJojeTgS8J
 
(but I've no clue why he just tried 0x006, 0x406, 0x806 and 0xc06 and how this should 'translate' to 0, 1, 2 and 3? If we're speaking about 3 bits then 8 -- 0 to 7 -- different values should be possible?)

It's a temporary error, long story short - GPG key for aptly repository expired, and now dependencies installation will fail on Ubuntu Trusty.
 
 
 
Please try Ubuntu Wily (or Xenial) as your build host in VM.
 
Edit: new key added to build script, so this should be fixed shortly.

Ubuntu 15.10 works perfectly, thanks.
 
 
I compile the kernel and making an image (i will test it this afternoon), i add some drivers, and delete drivers from IR and Audio.
 
The only problem is that i cant see the HDMI drivers ( or options ) only LCD options.

Dear Jens Bauer,
 
from you all instructables here above when you start to tell me I may try to see if the given shell could contact the modem/router at the IP address 192.168.1.1 I regret to tell you that :
1) I explained I got an unknown shell that appears with only those two character "=>".
2) when I tried a simple ping to the modem/router at 192.168.1.1 here is what I got :
=> ping 192.168.1.1
ethernet@01c50000 Waiting for PHY auto negotiation to complete ......... TIMEOUT !
ethernet@01c50000: No link.
ping failed; host 192.168.1.1 is not alive
=>
 
Then I tested with 127.0.0.1 and I got exactly the same error except it talked about 127.0.0.1
 
As I saw a command line called version (when I launched the help command line to see all the available commands) I got :
U-Boot 2016.01-armbian-sun7i (Feb 10 2016 - 20:22:20 +0100) Allwinner Technology
arm-linux-gnuabihf-gcc (Ununtu/Linaro 4.8.2-16ubuntu4) 4.8.2
GNU ld (GNU Binutils for Ubuntu) 2.24
 
Then it let me believe I am still in the U-Boot and not further in the ARMBian (Jessie Legacy) operating system.
This was why I talked about an unknown shell kind.
 
So what could I do now to go further ?
 
Sincerely thanks ;-)

Dear Jens Bauer and others,
 
you right with the bad speed used in putty that generate bad caracters (white and black pixels).
By using it at the good speed 115200 it gave me a comprehensive text (part of it here below).
 
I used the last here above recommended static IP setup where I forced the static 192.168.2.1.
 
After having display a lot of systemm informations it gave :
ethernet@01c50000 Waiting for PHY auto negociation to complete ........ TIMEOUT!
ethernet@01c50000: No link.
missing environment variable: pxeuuid
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/01-03-c9-03-42-36-97
ethernet@01c50000 Waiting for PHY auto negociation to complete ........ TIMEOUT!

Then it continued with Retrieving file: pxelinux.cfg/00000000
from eight zeros to only one zero : Retrieving file: pxe.cfg/0
Always with TIMEOUT!

Then it tried with : Retrieving file:
pxelinux.cfg/default-arm-sunxi
pxelinux.cfg/deafult-arm
pxelinux.cfg/default

Then after still telling :
ethernet@01c50000: No link.
Config file not found
ethernet@01c50000 Waiting for PHY auto negociation to complete ........ TIMEOUT!
ethernet@01c50000: No link.

it just returned a prompt like this :
=>

and typing help gave me a lot of command

Internet could be contact (like now) but always the same situation :
modem/router keep the gateway default IP Address 192.168.1.1
the laptop got the IP Address 192.168.1.3

But I can not know if Lamobo R1 got an IP ADDRESS because nothing could be returned by pinging the 192.168.1.3 or even the 192.168.1.4
As the laptop got a 192.168.1.x IP I know trying to ping the /etc/network/interfaces forced IP Address could not work but I tested to be able to confirm you that it  did not work too (I know this is normal).

Then I was not able to try a SSH connexion. And I did not find any command line in the give shell => to try knowing it IP Address

What could I still try to help you understand what happends and be able to go further with this Jessie ;-)
 
Thank you all of you for your precious time and your help.

Dont understand very well your question but i supposed that if i remove from kernel this devices, the board will be more eficcient, true? and the kernel will run more faster, true? or i am totaly wronge?

And why don't you start removing the few thousand other drivers from the kernel for hardware that is not even present on your board before? What do you fear?

doesnt make that much of a difference and its possible to blacklist modules from loading.

If you really care about performance you have to tweak other settings first. As a starting point: http://linux-sunxi.org/Sunxi_devices_as_NAS#Influence_of_the_chosen_OS_image_on_NAS_performance(follow the links there especially if you have an A10 device since there memory bandwidth might suffer from graphics settings)

Thanks for the answer @Jens, but i think i should recompiled the kernel like this link: http://www.armbian.com/github/
 
But my questión is when i compile what i generate? how can i add that kernel to my system? or how can i make and image from that kernel?

 

Try having a look at the top of /boot/boot.cmd
 
-This is a file, which needs to be compiled (but you have the compiler)
Now, if you make a mistake, you might have to re-write your sd-card, so I will suggest you do the following:
 
1: Take out the SD-card you usually boot from and put it somewhere safe.
2: Get an empty card (a different card).
3: Write Armbian to this card, then boot from it.
4: When you've done the basic setup, CD into /boot.
5: copy boot.cmd to boot.cmd.old and boot.scr to boot.scr.old
6: Edit boot.cmd using your favorite editor. (I like nano myself, as it's very simple and easy to learn)
7: Look in /usr/sbin/nand-sata-install, you'll find a few places where 'boot.scr' is re-built from 'boot.cmd'.
8: Pick the one, which generates the SD-card booter and copy that:
mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr After running the above command, your boot.scr is updated. Try booting from the card and see if it works as expected.
 
My boot.cmd for CubieBoard2 looks like this (note: you can most likely not use mine; use the one that is already written to your SD-card)...
 
 
setenv bootargs "console=tty1 root=/dev/mmcblk0p1 rootwait rootfstype=ext4 cgroup-enable=memory swapaccount=1 sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_no_mali_mem_reserve sunxi_fb_mem_reserve=16 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 panic=10 consoleblank=0 enforcing=0 loglevel=1" -As you see, there are several interesting things to mess with.
What exactly to do to disable things, I do not know, but I'd start by reducing the screen resolution to something small like 640x480@60.
 
I think that other users of this forum will be able to provide a much better answer than mine, but this should give you a place to start.

http://www.ebay.com/itm/6Pin-USB-2-0-to-TTL-UART-Module-Serial-Converter-CP2102-STC-Replace-Ft232-Module-/400565980256?hash=item5d4397cc60
 
+ good quality
+ cheap
+ trusted seller
+ fast delivery

"Good" to hear other have the same problem... after the workaround went fine on my CubieBoard2 I bricked my production system CubieTruck the same way, you described. The workaround trick went fine on the CubieTruck. But after reboot the system does not start anymore:
 red power LED near power jack is lit  network LEDs show some activity  SATA disk stays off  front LEDs stay off  VGA has no signal  no other reaction observable  
I had similar NAND boot problems in the past, so I assumed it is the same case again. The last time it was sufficient to leave the board unpowered for some hours (discharging battery a bit), but this time nothing helped. So I migrated my complete system back to SDCARD, and it is working like before.
 
After thinking a night about the problem, it might be sufficient to manually update all kernel files on NAND1. I did not test that.
Do you have a serial cable to watch the boot output? (I don't have one.)

Workaround: manually remove 
 
dpkg -r linux-jessie-root-cubieboard2
 
and install
 
apt-get install linux-jessie-root-cubieboard2

When doing apt-upgrade to get the latest linux-jessie-root-cubieboard2, it fails with this error message:
# apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded:   linux-jessie-root-cubieboard2 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 3 not fully installed or removed. Need to get 0 B/1.810 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Y (Reading database ... 51863 files and directories currently installed.) Preparing to unpack .../linux-jessie-root-cubieboard2_5.00_armhf.deb ... Unpacking linux-jessie-root-cubieboard2 (5.00) over (4.81) ... dpkg: error processing archive /var/cache/apt/archives/linux-jessie-root-cubieboard2_5.00_armhf.deb (--unpack):  unable to make backup link of `./boot/bin/cubieboard.bin' before installing new version: Operation not permitted dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Processing triggers for systemd (215-17+deb8u3) ... Errors were encountered while processing:  /var/cache/apt/archives/linux-jessie-root-cubieboard2_5.00_armhf.deb E: Sub-process /usr/bin/dpkg returned an error code (1)
When /boot is on NAND it is not possible to link files there, maybe that is the problem?

Hi all again,
 
I need disable this hardware on the kernel of the board because i dont use it:
HDMI Audio IR receiver Camera LCD screen  
For do this i should recompile the kernel? or i can desactivate in the armbian with out recompile?
 
And how i do this? i am very noob with kernels.
 
Best Regards!