schnapper79

  • Content Count

    13
  • Joined

  • Last visited

  1. It was 15.04... I can try with trusty... Just thought 15.04 was reported 'working'. I know 15.10 isn't working at all, u-boot sources from udoo won't compile wit GCC 5.x...
  2. 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?
  3. Thanks... I've seen your bugfix on git. Its the same i did and it works.
  4. Hello Igor, adding worked like a charm, but i also had to copy a file (/etc/apt/apt.conf) into my rootfs to make the apt-get within the chroot-environment work. It contains the proxy-settings for apt-get. i realized what happens at the beginning of the process (see my last post). Its not the debootstrap, its the installation of host dependencies which fails without further notice. I couldn't install the gpg-key for aptly. after installing aptly manually everything worked fine with the proxy. Additionally i ran into problems with the size of the sdcard-image. I had to set th
  5. hi, starting yesterday the menuconfig (for kernel configuration) seems broken: instead of the menu in the grey box it shows the following inside the gray box. the console settings are UTF8. [(0^[[0;1m^[[37m^[[47mx^[(B^[[0m^[[30m^ x x ^[[3G^[(0^[[0m^[[30m^[[47m^[(0^[[0;1m^[[37m^[[47mx^[(B^[[0m^[[30m^ x x ^[[3G^[(0^[[0m^[[30m^[[47m^[(0^[[0;1m^[[37m^[[47mx^[(B^[[0m^[[30m^ x x ^[[3G^[(0^[[0m^[[30m^[[47m^[(0^[[0;1m^[[37m^[[47mx^[(B^[[0m^[[30m^ x x ^[[3G^[(0^[[0m^[[30m^[[47m^[(0^[[0;1m^[[37m^[[47mx^[(B^[[0m^[[30m^ x x ^[[3G^[(0^[[0m^[[30m^[[47m^[(0^[[0;1m^[[37m^[[4
  6. it happens quite often that the deboostrap-process jumps almost immediatly from 0% to 100%. in this case i get an error when stuff should be compiled in chroot-environment. (eg /bin/sh: 1: arm-linux-gnueabihf-gcc: not found) this also happens on machines without proxy. Any idea? (reboot doesn't help at all, deleting of /source and /output is no help either) florian
  7. thanks.. i'll try using your trusty desktop image with the legacy kernel which seemed to work and gonna compile a new kernel. (I need the SocketCan modules compiled, which actually worked fine with 4.2.1)
  8. Thanks... I managed to build armbian "4.4" from your git sources. I did build the Ubuntu trusty with Kernel 4.2.1 (next) and desktop. Now when starting the X (startx) I get a segmentation fault: root@udoo:~# cat /var/log/Xorg.0.log [ 378.989] X.Org X Server 1.15.1 Release Date: 2014-04-13 [ 378.990] X Protocol Version 11, Revision 0 [ 378.990] Build Operating System: Linux 3.2.0-67-highbank armv7l Ubuntu [ 378.991] Current Operating System: Linux udoo 4.2.1-udoo #1 SMP Tue Sep 29 23:33:34 CEST 2015 armv7l [ 378.991] Kernel command line: root=/dev/mmcblk0p1 rootfstype=ext4 rootw
  9. 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
  10. hello Franky, thanks for your answer. Actually i allready knew that and tested it with the udoobuntu 2 beta and its working fine. My question was: how did that test happen that's mentioned on the github-page of the kernel? was it the udoobuntu with a new kernel? or where was this compilation of chromium from? Debian has no chromium for armhf and i am not sure if the official chromium in ubuntu has the egl drivers.
  11. Hello, I have a problem building the image behind a proxy (company proxy). Is there any way to get my proxy configuration into the chroot - environment?
  12. 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
  13. if you need to use chroot for whatever and have an image-file with only one partition: 1) (sudo) fdisk -l /path/to/image.img this will tell you the blocksize (usually 512 byte) and the startblock (lets say 2048) 2) (sudo) mount /path/to/image.img -o offset=$((512 * 2048)) /path/to/mount ((yey, there are the 512 and 2048 again...) 3) now you can follow your mentioned guide again... (copy the qemu-arm-static, mount -o bind the dev, sys and proc and so on....) But just for curiosity: Why you need chroot when getting a complete image?