schnapper79

Members
  • 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 the size to 8000MB as i got "out of space"-messages when installing the pakets into the sdcard image. (even 6000MB were not enough for trusty with desktop).
  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^[[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^[[47mtqqqqqqqqqqqqqqqq x x ^[[3G^[(0^[[0m^[[30m^[[47m^[(0^[[0;1m^[[37m^[[47mx^[(B^[[0m^[[30m^ x mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj any idea?
  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 rootwait console=tty1 video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24,bpp=32 rd.dm=0 rd.luks=0 rd.lvm=0 raid=noautodetect pci=nomsi ahci_imx.hotplug=1 quiet [ 378.993] Build Date: 12 February 2015 02:55:07PM [ 378.993] xorg-server 2:1.15.1-0ubuntu2.7 (For technical support please see http://www.ubuntu.com/support) [ 378.993] Current version of pixman: 0.30.2 [ 378.994] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 378.995] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 378.997] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Sep 30 09:18:42 2015 [ 378.998] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 378.999] (==) No Layout section. Using the first Screen section. [ 378.999] (==) No screen section available. Using defaults. [ 378.999] (**) |-->Screen "Default Screen Section" (0) [ 378.999] (**) | |-->Monitor "<default monitor>" [ 379.000] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 379.000] (==) Automatically adding devices [ 379.000] (==) Automatically enabling devices [ 379.000] (==) Automatically adding GPU devices [ 379.000] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 379.000] Entry deleted from font path. [ 379.000] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist. [ 379.000] Entry deleted from font path. [ 379.000] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist. [ 379.000] Entry deleted from font path. [ 379.000] (WW) The directory "/usr/share/fonts/X11/Type1" does not exist. [ 379.001] Entry deleted from font path. [ 379.001] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist. [ 379.001] Entry deleted from font path. [ 379.001] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist. [ 379.001] Entry deleted from font path. [ 379.001] (==) FontPath set to: /usr/share/fonts/X11/misc, built-ins [ 379.001] (==) ModulePath set to "/usr/lib/arm-linux-gnueabihf/xorg/extra-modules,/usr/lib/xorg/extra-modules,/usr/lib/xorg/modules" [ 379.001] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 379.001] (II) Loader magic: 0x54c06f10 [ 379.001] (II) Module ABI versions: [ 379.001] X.Org ANSI C Emulation: 0.4 [ 379.001] X.Org Video Driver: 15.0 [ 379.001] X.Org XInput driver : 20.0 [ 379.001] X.Org Server Extension : 8.0 [ 379.002] (II) xfree86: Adding drm device (/dev/dri/card0) [ 379.002] (EE) [ 379.002] (EE) Backtrace: [ 379.003] (EE) [ 379.003] (EE) Segmentation fault at address 0x0 [ 379.004] (EE) Fatal server error: [ 379.004] (EE) Caught signal 11 (Segmentation fault). Server aborting[ 379.005] (EE) [ 379.006] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 379.008] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 379.008] (EE) root@udoo:~# Any idea ?
  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-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?
  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?