Search the Community

Showing results for tags 'udoo'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Community
    • Announcements
    • Feature Requests
  • Using Armbian
    • Beginners
    • Advanced users - Development
  • Upcoming Hardware (WIP)
    • Tech News
    • Khadas VIM4
    • Radxa Zero 2
    • Odroid M1
  • Supported boards
    • Board does not start
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Unsupported (CSC/EOL/TVB) / Other
    • TV boxes
    • Off-topic
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Old bug tracker - read only
    • Old bug tracker - read only
  • TV Boxes's General Chat
  • TV Boxes's Reviews/Tutorials
  • TV Boxes's FAQ
  • TV Boxes's TV Boxes running Armbian
  • TV Boxes's Rockchip CPU Boxes
  • TV Boxes's Amlogic CPU Boxes
  • TV Boxes's Allwinner CPU Boxes
  • Android's Forums
  • Gaming on ARM's Reviews
  • Gaming on ARM's Issues

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Matrix


Mastodon


IRC


Website URL


XMPP


Skype


Github


Location


Interests

Found 23 results

  1. Hello, I deployed the latest image "Armbian Buster mainline based kernel 5.8.y" and after initial setup, I cannot activate the analog sound card. What I did: The "Hardware" section in "Settings" section of armbian-config was missing, so I installed the following packages: "linux-dtb-current-sunxi/buster 20.11.0-trunk.28 armhf Linux DTB, version 5.9.5-sunxi, linux-dtb-dev-sunxi/buster 20.11.0-trunk.28 armhf Linux DTB, version 5.10.0-rc2-sunxi" and after that changed: /boot/armbianEnv.txt by adding overlay_prefix: "sun8i-h3". This was the only way I could make armbian-config to correctly display the "Hardware" device tree. I tried to put: imx6q, imx6q-quad, imx6q-quad-hdmi (also copied all imx6q-udoo.dtb) to /boot/dtb, since after installinx *sunxi packages, the sunxi became the default dtb folder. The only way to make it properly display the HW menu was with "sun8i-h3". With "imx6q-udoo" it displayed this error: "Loading error: expected at least 6 tokens for --checklist, have 4. use --help to list options. submodule ..." I tried to enable "analog audio" with "sun8i-h3" (since only with this option I could properly see the Hardware section) but of course it didn't worked, and this is normal since there are different boards with different Device Tree Overlays. The question is what should I do, in order to have the properly DT for my board (Udoo Quad)? I decompiled the DTB file but I didn't see any VT1613 or analog audio in there... Please help me with some clues. Thanks a lot! Cristi
  2. I'm trying to upgrade from Armbian 5.32 (Xenial Next/4.4.76) and was hoping to enable 1 wire again on my Udoo. For that build, I had to add one wire modules to the kernel config, then edit the imx6qdl-udoo.dtsi to set the onewire status to okay (from disabled). In the dtsi, after udoo_ard: udoo_ard_manager it had: onewire@0 { /* example for pin 08 */ compatible = "w1-gpio"; pinctrl-names = "default"; pinctrl-0 = <&w1_gpio_pins>; status = "disabled"; /* "okay" to enable */ gpios = <&gpio1 21 0>; }; and in iomuxc, there was a section (in external_hog: hoggrp-2, MX6QDL_PAD_SD1_DAT3__GPIO1_IO21 0x80000000 // pin 08): w1_gpio_pins: w1-gpio@0 { fsl,pins = < MX6QDL_PAD_SD1_DAT3__GPIO1_IO21 0x80000000 /* example for pin 08 */ >; }; I tried adding the following to /boot/armbianEnv.txt overlays=w1-gpio param_w1_pin=21 param_w1_pin_int_pullup=0 with no luck. Do I need to modify the dtsi and rebuild, or is there an overlay that will add one wire? (the current dtsi has no entries for one wire)
  3. I downloaded Armbian for a Udoo Quad from https://dl.armbian.com/udoo/Focal_current_desktop. uname -a reports: Linux udoo 5.6.18-imx6 #20.05.4 SMP Mon Jun 15 00:30:23 CEST 2020 armv7l armv7l armv7l GNU/Linux However in https://docs.armbian.com/Hardware_Freescale-imx6/ I read: "Udoo Quad Kernel 3.14.x and 4.4.x with some hardware support, headers and some firmware included", which suggests that the image should have a 3.14 or 4.4 kernel. In /var/log/Xorg.0.log I read: [ 21.345] (II) AIGLX: Screen 0 is not DRI2 capable [ 23.279] (II) IGLX: Loaded and initialized swrast [ 23.279] (II) GLX: Initialized DRISWRAST GL provider for screen 0 LIBGL_DEBUG=verbose glxgears -info says: libGL: screen 0 does not appear to be DRI2 capable libGL: Can't open configuration file /etc/drirc: No such file or directory. libGL: Can't open configuration file /home/pi/.drirc: No such file or directory. libGL: Can't open configuration file /etc/drirc: No such file or directory. libGL: Can't open configuration file /home/pi/.drirc: No such file or directory. GL_RENDERER = llvmpipe (LLVM 9.0.1, 128 bits) GL_VERSION = 3.1 Mesa 20.0.4 GL_VENDOR = VMware, Inc. suggesting that there is no hardware acceleration. Is there any way to get hardware acceleration on a Udoo Quad with Armbian
  4. UDOO Quad Hello. Armbian bionic desktop mainline based kernel 5.4, USB ports do not work, wifi module is not visible. Everything works correctly on Stretch. Do not tell me where to look for the reason?
  5. Its been a while since I built a UDOO image (need another kernel module), when I ran compile.sh, it pulled new source and told me to clone a new build directory. In the process of cloning, however with UDOO being EOS, is it still possible to build the legacy kernel/image with current sources?
  6. Hi I have no /dev/dvb on my UDOO Quad. I'm trying to get MythTV or tvheadend working on my UDOO Quad with Armbian Jessie with kernal 4.4.102 glen@udoo:~$ uname -a Linux udoo 4.4.102-udoo #2 SMP Fri Nov 24 18:49:01 CET 2017 armv7l GNU/Linux I thought that dvb drivers were included in version 3.19 of the kernel and up? Anyway I copied dvb-usb-af9015.fw to /lib/firmware and rebooted. But nothing shows up under /dev/dvb/ I would expect there to be adapter0 and adapter1 Here is my lsusb: glen@udoo:~$ lsusb Bus 001 Device 004: ID 13d3:3226 IMC Networks DigitalNow TinyTwin DVB-T Receiver Bus 001 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub and my dmesg: [ 8904.731820] usb 1-1.2: USB disconnect, device number 3 [ 9150.501583] usb 1-1.1: new high-speed USB device number 4 using ci_hdrc [ 9150.616876] usb 1-1.1: New USB device found, idVendor=13d3, idProduct=3226 [ 9150.616899] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 9150.616915] usb 1-1.1: Product: DVB-T 2 [ 9150.616928] usb 1-1.1: Manufacturer: Afatech [ 9150.616940] usb 1-1.1: SerialNumber: 010101010600001 [ 9150.630673] input: Afatech DVB-T 2 as /devices/soc0/soc/2100000.aips-bus/2184200.usb/ci_hdrc.1/usb1/1-1/1-1.1/1-1.1:1.1/0003:13D3:3226.0002/input/input1 [ 9150.682765] hid-generic 0003:13D3:3226.0002: input: USB HID v1.01 Keyboard [Afatech DVB-T 2] on usb-ci_hdrc.1-1.1/input1
  7. I upgrade Jessie to Stretch and installed (from armbian stretch) linux-image-dev-udoo linux-headers-dev-udoo linux-dtb-dev-udoo linux-u-boot-udoo-dev Unfortunately the kernel is not booting any more from sata: U-Boot SPL 2015.10-armbian (Nov 22 2017 - 17:21:35) U-Boot 2015.10-armbian (Nov 22 2017 - 17:21:35 +0100) CPU: Freescale i.MX6Q rev1.2 at 792 MHz Reset cause: POR Board: UDOO Quad DRAM: 1 GiB MMC: FSL_SDHC: 0 No panel detected: default to HDMI Display: HDMI (1280x720) In: serial Out: serial Err: serial Net: using phy at 6 FEC [PRIME] Hit any key to stop autoboot: 0 ** Bad device size - sata 0 ** AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl SATA mode flags: ncq stag pm led clo only pmp pio slum part SATA Device Info: S/N: B645560128 Product model number: TS256GSSD370 Firmware version: 20140516 Capacity: 500118192 sectors Booting from sata ... 37690 bytes read in 391 ms (93.8 KiB/s) 7120160 bytes read in 164 ms (41.4 MiB/s) Kernel image @ 0x12000000 [ 0x000000 - 0x6ca520 ] ## Flattened Device Tree blob at 18000000 Booting using the fdt blob at 0x18000000 Using Device Tree in place at 18000000, end 1800c339 Starting kernel ... Booting Linux on physical CPU 0x0 Linux version 4.14.0-udoo (root@armbian) (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.4)) #18 SMP Wed Nov 23:35 CET 2017 CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c5387d CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache OF: fdt: Machine model: Udoo i.MX6 Quad Board Memory policy: Data cache writealloc cma: Reserved 256 MiB at 0x40000000 random: fast init done percpu: Embedded 17 pages/cpu @af61a000 s40396 r8192 d21044 u69632 Built 1 zonelists, mobility grouping on. Total pages: 259840 Kernel command line: console=ttymxc1,115200 root=/dev/sda1 rootwait rw fbmem=24M video=mxcfb0:dev=hdmi,1920x1080M@60,bpp=32 PID hash table entries: 4096 (order: 2, 16384 bytes) Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Memory: 759876K/1048576K available (10240K kernel code, 744K rwdata, 2340K rodata, 1024K init, 456K bss, 26556K reserved, 262ma-reserved, 0K highmem) Virtual kernel memory layout: vector : 0xffff0000 - 0xffff1000 ( 4 kB) fixmap : 0xffc00000 - 0xfff00000 (3072 kB) vmalloc : 0xc0800000 - 0xff800000 (1008 MB) lowmem : 0x80000000 - 0xc0000000 (1024 MB) pkmap : 0x7fe00000 - 0x80000000 ( 2 MB) modules : 0x7f000000 - 0x7fe00000 ( 14 MB) .text : 0x80008000 - 0x80b00000 (11232 kB) .init : 0x80e00000 - 0x80f00000 (1024 kB) .data : 0x80f00000 - 0x80fba2fc ( 745 kB) .bss : 0x80fc4e74 - 0x8103723c ( 457 kB) SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 Hierarchical RCU implementation. NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16 L2C-310 errata 752271 769419 enabled L2C-310 enabling early BRESP for Cortex-A9 L2C-310 full line of zeros enabled for Cortex-A9 L2C-310 ID prefetch enabled, offset 16 lines L2C-310 dynamic clock gating enabled, standby mode enabled L2C-310 cache controller enabled, 16 ways, 1024 kB L2C-310: CACHE_ID 0x410000c7, AUX_CTRL 0x76470001 Switching to timer-based delay loop, resolution 333ns sched_clock: 32 bits at 3000kHz, resolution 333ns, wraps every 715827882841ns clocksource: mxc_timer1: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 637086815595 ns Console: colour dummy device 80x30 Calibrating delay loop (skipped), value calculated using timer frequency.. 6.00 BogoMIPS (lpj=30000) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 2048 (order: 1, 8192 bytes) Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes) CPU: Testing write buffer coherency: ok CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 Setting up static identity map for 0x10100000 - 0x10100060 Hierarchical SRCU implementation. smp: Bringing up secondary CPUs ... CPU1: thread -1, cpu 1, socket 0, mpidr 80000001 CPU2: thread -1, cpu 2, socket 0, mpidr 80000002 CPU3: thread -1, cpu 3, socket 0, mpidr 80000003 smp: Brought up 1 node, 4 CPUs SMP: Total of 4 processors activated (24.00 BogoMIPS). CPU: All CPU(s) started in SVC mode. devtmpfs: initialized VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4 clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns futex hash table entries: 1024 (order: 4, 65536 bytes) xor: measuring software checksum speed arm4regs : 1221.200 MB/sec 8regs : 951.200 MB/sec 32regs : 987.200 MB/sec neon : 894.400 MB/sec xor: using function: arm4regs (1221.200 MB/sec) pinctrl core: initialized pinctrl subsystem NET: Registered protocol family 16 DMA: preallocated 2048 KiB pool for atomic coherent allocations cpuidle: using governor ladder cpuidle: using governor menu CPU identified as i.MX6Q, silicon rev 1.2 vdd1p1: supplied by regulator-dummy vdd3p0: supplied by regulator-dummy vdd2p5: supplied by regulator-dummy vddarm: supplied by regulator-dummy vddpu: supplied by regulator-dummy vddsoc: supplied by regulator-dummy hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers. hw-breakpoint: maximum watchpoint size is 4 bytes. imx6q-pinctrl 20e0000.iomuxc: no fsl,pins and pins property in node /soc/aips-bus@02000000/iomuxc@020e0000/imx6q-udoo/pwm4grp imx6q-pinctrl 20e0000.iomuxc: no fsl,pins and pins property in node /soc/aips-bus@02000000/iomuxc@020e0000/imx6q-udoo/pwm3grp imx6q-pinctrl 20e0000.iomuxc: initialized IMX pinctrl driver raid6: int32x1 gen() 106 MB/s raid6: int32x1 xor() 151 MB/s raid6: int32x2 gen() 165 MB/s raid6: int32x2 xor() 171 MB/s raid6: int32x4 gen() 181 MB/s raid6: int32x4 xor() 166 MB/s raid6: int32x8 gen() 205 MB/s raid6: int32x8 xor() 152 MB/s raid6: neonx1 gen() 616 MB/s raid6: neonx1 xor() 572 MB/s raid6: neonx2 gen() 658 MB/s raid6: neonx2 xor() 666 MB/s raid6: neonx4 gen() 678 MB/s raid6: neonx4 xor() 700 MB/s raid6: neonx8 gen() 560 MB/s raid6: neonx8 xor() 532 MB/s raid6: using algorithm neonx4 gen() 678 MB/s raid6: .... xor() 700 MB/s, rmw enabled raid6: using neon recovery algorithm mxs-dma 110000.dma-apbh: initialized SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb usb_phy_generic 2000000.aips-bus:usbphy_nop1: 2000000.aips-bus:usbphy_nop1 supply vcc not found, using dummy regulator usb_phy_generic 2000000.aips-bus:usbphy_nop2: 2000000.aips-bus:usbphy_nop2 supply vcc not found, using dummy regulator i2c i2c-0: IMX I2C adapter registered i2c i2c-0: can't use DMA, using PIO instead. i2c i2c-1: IMX I2C adapter registered i2c i2c-1: can't use DMA, using PIO instead. i2c i2c-2: IMX I2C adapter registered i2c i2c-2: can't use DMA, using PIO instead. media: Linux media interface: v0.10 Linux video capture interface: v2.00 pps_core: LinuxPPS API ver. 1 registered pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it> PTP clock support registered Advanced Linux Sound Architecture Driver Initialized. clocksource: Switched to clocksource mxc_timer1 VFS: Disk quotas dquot_6.6.0 VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) FS-Cache: Loaded CacheFiles: Loaded NET: Registered protocol family 2 TCP established hash table entries: 8192 (order: 3, 32768 bytes) TCP bind hash table entries: 8192 (order: 4, 65536 bytes) TCP: Hash tables configured (established 8192 bind 8192) UDP hash table entries: 512 (order: 2, 16384 bytes) UDP-Lite hash table entries: 512 (order: 2, 16384 bytes) NET: Registered protocol family 1 RPC: Registered named UNIX socket transport module. RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. hw perfevents: no interrupt-affinity property for /soc/pmu, guessing. hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available Initialise system trusted keyrings workingset: timestamp_bits=14 max_order=18 bucket_order=4 zbud: loaded FS-Cache: Netfs 'nfs' registered for caching NFS: Registering the id_resolver key type Key type id_resolver registered Key type id_legacy registered nfs4filelayout_init: NFSv4 File Layout Driver Registering... fuse init (API version 7.26) Key type asymmetric registered Block layer SCSI generic (bsg) driver version 0.4 loaded (major 247) io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) io scheduler mq-deadline registered io scheduler kyber registered imx-weim 21b8000.weim: Driver registered. imx-sdma 20ec000.sdma: Direct firmware load for imx/sdma/sdma-imx6q.bin failed with error -2 imx-sdma 20ec000.sdma: external firmware not found, using ROM firmware 21e8000.serial: ttymxc1 at MMIO 0x21e8000 (irq = 70, base_baud = 5000000) is a IMX console [ttymxc1] enabled 21f0000.serial: ttymxc3 at MMIO 0x21f0000 (irq = 71, base_baud = 5000000) is a IMX brd: module loaded loop: module loaded ahci-imx 2200000.sata: fsl,transmit-level-mV not specified, using 00000024 ahci-imx 2200000.sata: fsl,transmit-boost-mdB not specified, using 00000480 ahci-imx 2200000.sata: fsl,transmit-atten-16ths not specified, using 00002000 ahci-imx 2200000.sata: fsl,receive-eq-mdB not specified, using 05000000 ahci-imx 2200000.sata: SSS flag set, parallel bus scan disabled ahci-imx 2200000.sata: AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl platform mode ahci-imx 2200000.sata: flags: ncq sntf stag pm led clo only pmp pio slum part ccc apst scsi host0: ahci-imx ata1: SATA max UDMA/133 mmio [mem 0x02200000-0x02203fff] port 0x100 irq 81 Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011) libphy: Fixed MDIO Bus: probed tun: Universal TUN/TAP device driver, 1.6 fec 2188000.ethernet: 2188000.ethernet supply phy not found, using dummy regulator pps pps0: new PPS source ptp0 libphy: fec_enet_mii_bus: probed fec 2188000.ethernet eth0: registered PHC device 0 ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver ehci-mxc: Freescale On-Chip EHCI Host driver usbcore: registered new interface driver usb-storage Has anybody an idea? I tried also booting 4.4 kernel. Same result.... Is this an u-boot issue? Thanks. kind regards Claus
  8. I finally got my Udoo Dual up and running with Mainline 4.4 Xenial Next and I was wondering how I go about getting the arduino environment back on to it. I downloaded the arm version from arduino and it sees the correct serial port but how do I access it within arduino. I updated the board package to include the Udoo boards but when I hit upload, it says bossac tools are unavailable for my board? What do I need to do to fix this? Sent from my iPad using Tapatalk
  9. I've loaded Armbian onto my Udoo Dual and am having issues getting it past starting the kernel. I really like this OS on my other sbc's and have had no issues before this. I'm mostly a Linux noob with an elementary grasp of compiling the kernel. I have had this problem for about a week and am finally asking the pro's on how to fix this. Any help would GREATLY appreciated. Below is what I get from the U-Boot startup. Thanks! U-Boot SPL 2015.10-armbian (Jun 13 2017 - 15:51:16) U-Boot 2015.10-armbian (Jun 13 2017 - 15:51:16 +0200) CPU: Freescale i.MX6DL rev1.1 at 792 MHz Reset cause: POR Board: UDOO DualLite DRAM: 1 GiB MMC: FSL_SDHC: 0 *** Warning - bad CRC, using default environment auto-detected panel HDMI Display: HDMI (1280x720) In: serial Out: serial Err: serial Net: using phy at 6 FEC [PRIME] Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc Found U-Boot script /boot.scr ** File not found /boot.scr ** ** Unrecognized filesystem type ** Found U-Boot script /boot/boot.scr 1757 bytes read in 99 ms (16.6 KiB/s) Running bootscript from mmc ... ## Executing script at 12000000 Booting from SD ** File not found /boot/armbianEnv.txt ** ** Unrecognized filesystem type ** 4765629 bytes read in 363 ms (12.5 MiB/s) 6234592 bytes read in 440 ms (13.5 MiB/s) 0 bytes read in 70 ms (0 Bytes/s) 37690 bytes read in 393 ms (92.8 KiB/s) Kernel image @ 0x12000000 [ 0x000000 - 0x5f21e0 ] ## Loading init Ramdisk from Legacy Image at 14800000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 4765565 Bytes = 4.5 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 18000000 Booting using the fdt blob at 0x18000000 Using Device Tree in place at 18000000, end 1800c339 Starting kernel ...
  10. Hey All - So I decided to upgrade my Udoo from 4.5 (Debian Jessia, kernel 3.14.28) to the latest 5.25 Xenial. I gave next (4.4.46) a try, and it seemed to work awesome, however it seems like no one wants 1wire (still - it only takes up 1 gpio!). I built custom kernels enabling 1wire in the kernel and updated (or for default adding) 1wire to be enabiled in the imx6qdl-udoo.dtsi, however after I install the kernels, it just sits indefinitely at the red Armbian logo on boot. On 4.4.46, i was able to just install all the debs via dpkg -i *.deb On 3.14.56, I had to use dpkg --force-all -i *.deb Any ideas on what I'm doing wrong? Its been a while, so I'm sure a bunch has changed, but adding 1wire in the kernel shouldn't cause a freeze
  11. I migrated my system from Wheezy from udoo.org which installed long ago to Armbian Jessie. The main stuff is working and i also manged to boot the new kernel (u-boot config). When i do apt-get upgrade the system always want to upgrade the initrd file. I get the following error messages: update-initramfs: Generating /boot/initrd.img-4.4.51-udoo Warning: root device rootfs does not exist Press Ctrl-C to abort build, or Enter to continue Warning: /sbin/fsck.rootfs doesn't exist, can't install to initramfs, ignoring. update-initramfs: Converting to u-boot format Unsupported platform. run-parts: /etc/initramfs/post-update.d//flash-kernel exited with return code 1 Does anybody has an idea why is says Unsupported platform?
  12. Hi i have an udoo quad and i downloaded your os (ubuntu jessie desktop Kernel 4.0.8). At first congratulation for your work and big thanks to share it After the flash of the sd card (used win32diskimager because imagewriter don't work for me), i can started my card. Ethernet, wifi, browser ... works fine ! Now, that it didn't work is sata disk or usb disk. When i plug it on the card nothing appear. If i go to /media i saw nothing. Do you know how to resolve this ? Otherwise, i would like to compile Qt5.5 but i need the header for openGL librairie to do it. Is it possible to have it (i saw nothing on /usr/include) ? Last think, do you plan to make a try with the new desktop lxqt ?
  13. Anyone get ArduinoIDE working on armbian for the Udoo quad? When I try to upload a sketch, i see a java exception for bossac - no such file or directory (when i try to run bossac -h, same error) Edit - the error above was for Udoo's 1.5.8 version. I tried 1.5.4, and now I get errors trying to create GPIO0 and GPIO117 (direction & value).
  14. Just upgraded to the new Jessie image 4.4.1. Is there any concern with this bad CRC warning? Do I need to update the u-boot.img? If so, how. U-Boot SPL 2013.10-rc4 (Feb 03 2016 - 16:37:42) Boot Device: SD1 spl: error reading image u-boot.img, err - -1 Load image from RAW... U-Boot 2013.10-rc4 (Feb 03 2016 - 16:37:42) CPU: Freescale i.MX6Q rev1.5 at 792 MHz Reset cause: POR Board: MX6-CuBox-i DRAM: 2 GiB MMC: FSL_SDHC: 0 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: FEC [PRIME] Hit any key to stop autoboot: 0 mmc0 is current device ** File not found /boot.scr ** ** File not found /uEnv.txt ** ** File not found /zImage ** ** File not found /uImage ** 563 bytes read in 131 ms (3.9 KiB/s) Running bootscript from mmc ... ## Executing script at 10800000 33996 bytes read in 252 ms (130.9 KiB/s) 4325272 bytes read in 342 ms (12.1 MiB/s) Kernel image @ 0x10800000 [ 0x000000 - 0x41ff98 ] ## Flattened Device Tree blob at 18000000 Booting using the fdt blob at 0x18000000 Using Device Tree in place at 18000000, end 1800b4cb Starting kernel ... Uncompressing Linux... done, booting the kernel. Debian GNU/Linux 8 cubox-i ttymxc0 cubox-i login
  15. I have debian installed on my hummingboard pro. When I execute nand-sata-install script it looks like it works. It asks me to reboot but then issuing a df -h or mount does not show that I have a 32gb drive mounted on /. Is there something else I have to do after I run this script? Thanks! ril3y
  16. hi... i have some trouble compiling a new image with the latest kernel (4.2) for udoo quad. i get an error during make drivers/pci/access.c:493:16: error: redefinition of 'pci_vpd_f0_write' static ssize_t pci_vpd_f0_write(struct pci_dev *dev, loff_t pos, size_t count, Any idea? solutions?
  17. Finally got an UDOO quad Trusty image built. How do I get it out of the virtual environment? Shared folder?
  18. hey, is there anyone who successfully compile armbian kernel with can support for uddo quad board ? (i also preffer compiled iptables module) here is my working patch with yocto project version dora http://pastebin.com/BF2SeWHa
  19. I was trying to plug my Arduino uno into my Udoo quad but it does not appear to be assigned to a serial port, which i believe should appear as ttyACM*. when searching the kernel github page i see these relults https://github.com/patrykk/linux-udoo/search?utf8=%E2%9C%93&q=ACM. Is it possible to get these devices supported in your next kernel release?
  20. Using Armbian_4.4_Udoo_Debian_jessie_3.14.28 - Wicd doesn't detect any networks (/etc/network/interfaces has wlan0 commented out). If i setup /etc/network/interfaces and edit /etc/hostapd.conf and /etc/init.d/hostapd, I can get the udoo to authenticate to my wireless network, but I can't ping/resolve/browse anything but google.com Using CLI images - I can't get my network card to auth at all. Any idea what happened - a few months ago wifi was working perfectly. Also - is there anyway to modify the startup job to raise network interfaces to have a time limit? Occasionally boot will go indefinitely.
  21. got this message during build (during installation of additional packages: bridge-utils): [ error ] Installation failed initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind not found. dpkg: error processing package libpam-systemd:armhf (--configure): subprocess installed post-installation script returned error exit status 100 Processing triggers for libc-bin (2.19-0ubuntu6) ... Processing triggers for sgml-base (1.26+nmu4ubuntu1) ... Processing triggers for ureadahead (0.100.0-16) ... Errors were encountered while processing: libpam-systemd:armhf E: Sub-process /usr/bin/dpkg returned an error code (1) root@d9c64ede3eb0:/armbian# any idea?
  22. Hello Igor, thanks for your work. On your Github-page for Kernel 4.2.0 you say you tested this kernel with chromium egl. Which was your setup? (Did you build your own chromium? which distro did you use?.....) regards Florian
  23. I was trying to install the udoo kernel but got stuck with this error: root@udoo:/tmp/4.0.8# ls -la total 32968 drwxr-xr-x 2 root root 4096 Jul 29 14:21 . drwxrwxrwx 5 root root 4096 Jul 29 14:21 .. -rw-r--r-- 1 root root 16875520 Jul 13 11:30 4.0.8-udoo-next.tar -rw-r--r-- 1 root root 11204 Jul 13 11:30 linux-dtb-4.0.8-udoo_1.8_armhf.db -rw-r--r-- 1 root root 49792 Jul 13 11:30 linux-firmware-image-4.0.8-udoo_b -rw-r--r-- 1 root root 6844194 Jul 13 11:30 linux-headers-4.0.8-udoo_1.8_armb -rw-r--r-- 1 root root 9096354 Jul 13 11:30 linux-image-4.0.8-udoo_1.8_armhfb -rw-r--r-- 1 root root 769836 Jul 13 11:30 linux-libc-dev_1.8_armhf.deb -rw-r--r-- 1 root root 97604 Jul 13 11:30 linux-u-boot-4.0.8-udoo_1.8_armhb root@udoo:/tmp/4.0.8# dpkg -i linux-image-4.0.8-udoo_1.8_armhf.deb dpkg: error processing archive linux-image-4.0.8-udoo_1.8_armhf.deb (--install): package architecture (armhf) does not match system (armel) Errors were encountered while processing: linux-image-4.0.8-udoo_1.8_armhf.deb Am I using the right package for udoo quad? Alf