Quantcast
Channel: Armbian news
Viewing all 486 articles
Browse latest View live

Cubox-I 4 with Legacy an Mainline Kernel is not booting by using PARTUUID or UUID in boot.cmd

$
0
0

Hello,

 

i was using my cubox-i 4 pro since two years now. Last time (last week) i have used a armbian legacy debian version from whatever, after my hdd corrupted (i have a backup) i tried to setup the system again with a new ssd and the newer version of armbian but i have a few problems.

 

First i flashed the mainline 4.9.7 dd-image on my sd card with rufus. That one is not booting. I can see in a seriel session that the uboot is starting after the line booting the kernel nothing happens any more. In my router i can not see any ip from dhcp is given out to the system and it does not do anything more.

 

After that i have tried the legacy 3.14.79 what when i flashed it to the sd card did boot. After that i tried to insert the partuuid of my sd card because i want to use it with my ssd over esata and two more usb hdd as sw-raid1 where i do not want to have any problems in booting situations. I have tried to to exchange the variable in boot.cmd defaultly declared with "/dev/mmcblk0p01" with "PARTUUID={PUUID}" what did not do the job. The system wasn't anymore booting with this setting. After that i tried using the uuid of the mmc by declaring the variable in the boot.cmd wit "UUID={UUID}" (all the time i wrote the ids which i wrote here in brackets natively in the string, with double checking if i had some spelling mistakes). I did as well all the time recompile the boot.cmd with the defined line at the end of the boot.cmd.

 

After trying to exchange the content of the variable i tried to exchange the variable in the bootargs string natively with the content of the two version of the variable definition what as well did not do the job to boot my cubox.

 

So now i'm asking, what am i doing wrong? I'm just searching for a solution to us the uuid or the partuuid of a hdd or sdd to boot my system so in the future no conflicts at boot appears with the further usage of more hdd's connected via usb to the box.

 

Hopefully my description is understable and some one can help me.

 

Regards

Geuni


H3 SPI with DMA using kernel 4.10.0

$
0
0

Using the dev build of Armbian for the OrangePi One, does the SPI driver in the mainline kernel support DMA?

According to the mainline status page the work on SPI is done, and DMA has been supported since 4.2

 

I have enabled the spi interface in the device tree and my driver initialises properly with the master.  But in my kernel driver I attempt to allocate some memory with dma_alloc_coherent and it fails.  The driver works fine with the legacy kernel and with alternative hardware (raspberry pi). 

 

Is there some additional configuration needed or does anyone have any pointers to information on this that I look at?

Failure trying to install opejdk 8 headless

$
0
0

On my banana I get the following error:
 

sudo apt-get install openjdk-8-jre-headless

 

Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 openjdk-8-jre-headless : Breaks: ca-certificates-java (< 20160321~) but 20140324 is to be installed
E: Unable to correct problems, you have held broken packages.

openjdk-7-jre-headless is installed without any problem

 

Ch340 (USB/UART) on Armbian

$
0
0

Hi,

Have Arduino (microcontroller) clone with CH340 USB/UART (USB serial port). Does armbian support it? 

 

 

 

regards

Peter

OrangePi Plus/plus2 kernel 4.10

$
0
0

Hi,

 

Following the guide https://docs.armbian.com/Developer-Guide_Build-Preparation/  I compiled a kernel 4.10 and I get:

 

[*]  Only appears one CPU.

                          CPU1, CPU2, CPU3 show disabled as lshw result.   Anybody know how to enable the other cores?

 

[*] In kernel config I enabled staging drivers for sun8i crypto engine. It seems that 

                          after loading the module,  cat /proc/crypto does't appears to be using the crypto engine. 

                          openssl speed seems to be the same than legacy kernel.

                          In dtb I can see that there is some stuff about crypto with status: disabled

                          Anyone can help in getting the crypto engine enabled?

 

 

 

[*]  wifi: The iface wlan0 doesn't exists in kernel 4.10. but after compiling 

                        git clone https://github.com/jwrdegoede/rtl8189ES_linux.gitfrom from http://linux-sunxi.org/Wifi

                        the wlan0 appears and I am able to scan wifi... but there is a error when trying to associate with WPA-PSK CCMP 

                        so no wireless connection.

                        Anyone can point how to make it work?

 

 

Greetings

                        

 

 

 

 

 

 

CVE-2017-6074: DCCP double-free vulnerability (local root)

$
0
0

For anyone stumbling accross CVE-2017-6074 and thinking about whether Armbian installations are affected or not: we're most probably not since CONFIG_IP_DCCP is enabled as module only on some kernels:

root@armbian:/var/git/Armbian/lib/config/kernel # grep 'CONFIG_IP_DCCP=' *
linux-cubox-default.config:CONFIG_IP_DCCP=m
linux-cubox-dev.config:CONFIG_IP_DCCP=m
linux-mvebu-default.config:CONFIG_IP_DCCP=m
linux-mvebu-next.config:CONFIG_IP_DCCP=m
linux-sun8i-dev.config:CONFIG_IP_DCCP=m
linux-sunxi-dev.config:CONFIG_IP_DCCP=m
linux-sunxi-next.config:CONFIG_IP_DCCP=m
root@armbian:/var/git/Armbian/lib/config/kernel #

Details about this local root exploit: http://seclists.org/oss-sec/2017/q1/471

USB-touchscreen doesn't work with Cubietruck 3.4.113.

$
0
0

USB-touchscreen doesn't work with Cubietruck 3.4.113.

The touchscreen well works with versions 4.9.xxx, but doesn't work with 3.4.xxx.
I connected the monitor 1920*1080 and a touchscreen to Cubietruck.
Cubietruck smartly works in video browse mode, but the mouse and the keypad aren't always convenient for control.
Especially at night, too loud clicks. 
I pasted a touchscreen on the monitor.
It works with versions 4.xxx, but video doesn't work. And with versions 3.xxx on the contrary.
What I should make that the touchscreen worked with version 3.4.113?

how to disable verbose ?

$
0
0

in the documentation is written :

How to toogle verbose boot?

touch /boot/.force-verbose # enable

You need to reboot to conduct changes.

rm /boot/.force-verbose # disable

but I am returned :

rm: cannot remove ‘/boot/.force-verbose’: No such file or directory

 

I tried to change verbosity in boot.cmd but with no success

Can you help please ?

Thanks


Camera problem: /dev/video0 not present

SMALLEST rootfs for Orange Pi Zero to fit in 2MB NOR-FLASH on board

$
0
0

Hello,

 

My project does not allow me to use SD card to boot and run my application. I can use SD card as drive to save my data.

 

Is there any alternative way to do so ?

 

Has anyone built a micro rootfs for O-Pi-ZERO NOR Flash ?

 

Does anyone have an idea of the MINIMUM SIZE that is required to do so, if 2MB is too less ?

 

Thanks

Nbird.

 

 

SPI slave

$
0
0

Hi!

I want to write SPI slave custom driver for H3. For this I need to cut off existing SPI Master driver. I did this during configuring Armbian 3.4.112 in image build process. But then I make apt update/upgrade and apt installs new image 3.4.113 with SPI master driver enabled. How could I prevent this?  

One usb keyboard for tty1 and ttyS0.

$
0
0
Good day or night. Help me please. I have armbian. And there are - systemd. I do not know how to set up my usb keyboard to make it work with two displays at once. With tty1 and ttyS0 at the same time. To become a clone tty1 -> ttyS0. Tell me, how do I configure it?

Pine64 board water cooling, off the wall

How to enable pwm in orange pi zero?

$
0
0

I could not found pwm folder in the "/sys/class".

so, how to enable pwm in orange pi zero?

USB Devices on 5.25 doesn't work well

$
0
0
Hello I have a little problem with the usb devices, i use usb camera and if u plug the power supply to the OPI Lite board (5.25) it recognize the camera but it doesn't work well (stream with like 8-10 fps), after a software reboot, the device go to other Bus and the camera work fine with 15-30 fps stream.
 
Before reboot, exact on first power of the board:
 
Bus 006 Device 002: ID 058f:3822 Alcor Micro Corp.
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter
 
 
 
After reboot:
 
Bus 003 Device 002: ID 058f:3822 Alcor Micro Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter
 
 
I try to remove and after that load again uvcvideo driver, but nothing happened, i tried some scripts to restart the usb ports but the result was 0, only if i unplug and plug the camera again or reboot solve the problem. Also i tried with different power supplies and nothing changed. Currently we use chargers from the Orange Pi manufacture so this is the best power supply i guess.
 
 
Any ideas how can i configure the camera to be on Bus 3 and tha wifi dongle to be on Bus 2 or some other solution to the problem?

 


H3/NanoPI Neo stock build failed

$
0
0

Hello,

 

While trying to build full Devian Jessy image for NanoPi Neo at stock x86_64 Ubuntu 16.04 using latest https://github.com/igorpecovnik/libgit , got this:

 

...

[ o.k. ] Compiling default kernel [ 3.4.113 ]
[ o.k. ] Compiler version [ arm-linux-gnueabihf-gcc 5.4.0 ]
[ o.k. ] Using kernel config file [ lib/config/kernel/linux-sun8i-default.config ]
  HOSTCC  scripts/basic/fixdep
  HOSTCC  scripts/kconfig/conf.o
  SHIPPED scripts/kconfig/zconf.tab.c
  SHIPPED scripts/kconfig/zconf.hash.c
  SHIPPED scripts/kconfig/zconf.lex.c
  HOSTCC  scripts/kconfig/zconf.tab.o
  HOSTLD  scripts/kconfig/conf
scripts/kconfig/conf --silentoldconfig Kconfig
drivers/net/wireless/bcmdhd/Kconfig:56:warning: defaults for choice values not supported
 
 Armbian building script, http://www.armbian.com| Author: Igor Pecovnik
 ──────────────────────────────────────────────────────────────────────────────────────────────────────
  ┌────────────────────────────────────────────────────────────────────────────────────────────────┐
  │ Compiling kernel...                                                                            │  
  │────────────────────────────────────────────────────────────────────────────────────────────────│  
  │   CC [M]  net/netfilter/ipvs/ip_vs_wrr.o                                                       │  
  │   CC [M]  net/netfilter/ipvs/ip_vs_lc.o                                                        │  
  │   CC [M]  net/netfilter/ipvs/ip_vs_wlc.o                                                       │  
  │   CC [M]  net/netfilter/ipvs/ip_vs_lblc.o                                                      │  
  │   CC [M]  net/netfilter/ipvs/ip_vs_lblcr.o                                                     │  
  │   CC [M]  net/netfilter/ipvs/ip_vs_dh.o                                                        │  
  │   CC [M]  net/netfilter/ipvs/ip_vs_sh.o                                                        │  
  │   CC [M]  net/netfilter/ipvs/ip_vs_sed.o                                                       │  
  │   CC [M]  net/netfilter/ipset/ip_set_list_set.o                                                │  
  │   CC [M]  net/netfilter/ipvs/ip_vs_nq.o                                                        │  
  │   LD [M]  net/netfilter/ipset/ip_set.o                                                         │  
  │   CC [M]  net/netfilter/ipvs/ip_vs_ftp.o                                                       │  
  │   CC [M]  net/netfilter/ipvs/ip_vs_pe_sip.o                                                    │  
  │   LD [M]  net/netfilter/ipvs/ip_vs.o                                                           │  
  │   LD [M]  net/netfilter/nf_conntrack.o                                                         │  
  │   LD      net/netfilter/netfilter.o                                                            │  
  │   LD      net/netfilter/built-in.o                                                             │  
  │   LD      net/built-in.o                                                                       │  
  
    
 
 
[ error ] ERROR in function compile_kernel [ common.sh:249 ]
[ error ] Kernel was not built [ @host ]
[ o.k. ] Process terminated 
....
 
 
The full kernel compile error is covered by dialog output so no way (!?) to see it. The question is : how to compile the image without this stupid ncurses dialog - just using plain tty with normal error output ?
 
TIA, Rus
 

Update to 4.9.12-cubox

$
0
0

Hi there,

 

on my Cubox i4 pro there was an update from 4.9.7-cubox to 4.9.12-cubox. It took quite a while, and there were a couple of messages:

dpkg: warning: unable to delete old directory '/usr/src/linux-headers-4.9.7-cubox/scripts/genksyms': Directory not empty
dpkg: warning: unable to delete old directory '/usr/src/linux-headers-4.9.7-cubox/scripts/mod': Directory not empty
dpkg: warning: unable to delete old directory '/usr/src/linux-headers-4.9.7-cubox/scripts/kconfig': Directory not empty
dpkg: warning: unable to delete old directory '/usr/src/linux-headers-4.9.7-cubox/scripts/basic': Directory not empty
dpkg: warning: unable to delete old directory '/usr/src/linux-headers-4.9.7-cubox/scripts/dtc': Directory not empty
dpkg: warning: unable to delete old directory '/usr/src/linux-headers-4.9.7-cubox/scripts': Directory not empty
dpkg: warning: unable to delete old directory '/usr/src/linux-headers-4.9.7-cubox/arch/arm/include/generated': Directory not empty
dpkg: warning: unable to delete old directory '/usr/src/linux-headers-4.9.7-cubox/arch/arm/include': Directory not empty
dpkg: warning: unable to delete old directory '/usr/src/linux-headers-4.9.7-cubox/arch/arm': Directory not empty
dpkg: warning: unable to delete old directory '/usr/src/linux-headers-4.9.7-cubox/arch': Directory not empty
dpkg: warning: unable to delete old directory '/usr/src/linux-headers-4.9.7-cubox': Directory not empty
dpkg: warning: unable to delete old directory '/usr/src/linux-headers-4.9.7-cubox/scripts/genksyms': Directory not empty
dpkg: warning: unable to delete old directory '/usr/src/linux-headers-4.9.7-cubox/scripts/mod': Directory not empty
dpkg: warning: unable to delete old directory '/usr/src/linux-headers-4.9.7-cubox/scripts/kconfig': Directory not empty
dpkg: warning: unable to delete old directory '/usr/src/linux-headers-4.9.7-cubox/scripts/basic': Directory not empty
dpkg: warning: unable to delete old directory '/usr/src/linux-headers-4.9.7-cubox/scripts/dtc': Directory not empty
dpkg: warning: unable to delete old directory '/usr/src/linux-headers-4.9.7-cubox/scripts': Directory not empty
dpkg: warning: unable to delete old directory '/usr/src/linux-headers-4.9.7-cubox/arch/arm/include/generated': Directory not empty
dpkg: warning: unable to delete old directory '/usr/src/linux-headers-4.9.7-cubox/arch/arm/include': Directory not empty
dpkg: warning: unable to delete old directory '/usr/src/linux-headers-4.9.7-cubox/arch/arm': Directory not empty
dpkg: warning: unable to delete old directory '/usr/src/linux-headers-4.9.7-cubox/arch': Directory not empty
dpkg: warning: unable to delete old directory '/usr/src/linux-headers-4.9.7-cubox': Directory not empty

Is there anything wrong, and, if not, can I  do anything to get rid of those directories (if necessary).

 

Thanks in advance,

 

Christoph

Orange Pi Zero - Failed to start Load Kernel Modules.

$
0
0

Orange Pi Zero shows error 

        [FAILED] Failed to start Load Kernel Modules.
        See 'systemctl status systemd-modules-load.service' for details.
opizero.png
 
More details
 
opizero1.png
 
How to fix this error?

UART on Orange Pi Zero

$
0
0

I was unable to get UART working on my Orange Pi Zero. Note, that I am not trying to use UART to access the terminal, I need to use the UART port to say connect to an arduino, etc. 

 

 Here is the output of some commands that I thought may be helpful. 

uname -a
Linux orangepizero 4.10.0-sun8i #14 SMP Fri Feb 24 03:02:58 CET 2017 armv7l armv7l armv7l GNU/Linux
dmesg | grep TTY

[    0.000000] Kernel command line: root=UUID=b5fc390b-23ef-47a8-83fb-0fd94a3d2dcc rootwait rootfstype=ext4 console=tty1 console=ttyS0,115200 cgroup_enable=memory swapaccount=1 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 panic=10 consoleblank=0 enforcing=0 loglevel=1 ubootpart=8b708352-01 ubootsource=mmc   sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_fb_mem_reserve=16
[    0.001005] console [tty1] enabled
[    4.126456] console [ttyS0] disabled
[    4.146689] 1c28000.serial: ttyS0 at MMIO 0x1c28000 (irq = 37, base_baud = 1500000) is a U6_16550A
[    4.146761] console [ttyS0] enabled
 
Here's how I tested communication with UART. I wired up the pins (RX <--> TX) as per the pinout at http://linux-sunxi.org/Xunlong_Orange_Pi_Zero#Locating_the_UARTI would then do, 
screen /dev/ttyS[12] 57600
[screen is terminating]

Any help is appreciated. Thanks!

 

[Odroid C2] filesystem corrupted after boot from emmc

$
0
0

I created a new image for my Odroid C2 with the most current version of Armbian 5.26. Configuration was pretty much standard, except BOOTSIZE=0 and ROOTFS_TYPE=ext4. The image works fine, if dumped to a sdcard. When dumping it to an emmc card, the system boots up, but 'find / > /dev/null' leads to a filesystem error:

 

[   52.799920] EXT4-fs error (device mmcblk0p1): htree_dirblock_to_tree:913: inode #41001: block 12032: comm find: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=8213, rec_len=4097, name_len=0
[   52.812862] EXT4-fs (mmcblk0p1): Remounting filesystem read-only

 

Behavior is deterministic - I tried with two different boards and two different emmc cards. I also checked, that the filesystem is initially ok on the emmc.

 

I tracked the problem down to the Amlogic mmc driver in linux kernel 3.14.y. During kernel boot, the function aml_sd_emmc_execute_tuning in drivers/amlogic/mmc/aml_sd_emmc.c is invoked. pdata->need_cali == 1 and aml_sd_emmc_execute_tuning_index is called. At the end, this function writes to the emmc: mmc_write_internal(mmc->card, record_blk, 1, write_buf).

The first two bytes of the written data are 0x2015, 0x1001 - which perfectly corresponds to the inode and rec_len from the error message above.

The position where the data is written at is calculated in emmc_partitions.c (function get_reserve_partition_off) and depends on several constants. The position evaluates to block #98304, which is somewhere in the root partition of the disk. Since in my image, this block is used by a directory inode, the filesystem gets corrupted.

 

On an image with a 64MB boot partition and an ext4 root partition, the write operation goes to the boot partition. It does not seem to have a negative impact on the consistency of the filesystem - at least not in my case.

 

I could imagine different solutions of the problem:

(1) set OFFSET=64 -> write operation will go to the unused space before boot / root partition

(2) change constants in linux kernel -> write operation will go to a different block on emmc (i cannot guess potential side effects of this)

(3) change partition layout on emmc by changing calculation in debootstrap-ng.sh

 

 

Best regards,

Michael

Viewing all 486 articles
Browse latest View live