Search the Community

Showing results for tags 'mainline'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Announcements & first aid
    • Announcements
    • Board doesn't start
  • Community forums
    • Common issues
    • Peer to peer technical support
    • Feature Requests
    • TV boxes
    • General chit chat
  • Bug tracker
    • Allwinner A20
    • Allwinner H2 & H3
    • Allwinner H5 & A64
    • Armada A388, A3700
    • Amlogic S905(x)
    • NXP (Freescale)
    • Rockchip 3288 & 3328
    • Other supported boards
  • Development
    • Allwinner H6
    • Rockchip 3399
    • Development

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 851 results

  1. The notes here, talk about a beta image that has hardware acceleration enabled for the pine64. Unfortunately, the link is no longer valid. Anyone have a link to images I can use with the pine64 that have hardware (2d primarily) that i can use?
  2. Hi. Is there no support for btrfs in the latest armbian-ubuntu-xenial for Pine64s? Linux pine54 3.10.104-pine64 #2 SMP PREEMPT Thu Feb 23 22:26:21 CET 2017 aarch64 aarch64 aarch64 GNU/Linux root@pine54:~# mkfs.btrfs /dev/sda1 btrfs-progs v4.4 See for more information. failed to open /dev/btrfs-control skipping device registration: No such file or directory Label: (null) UUID: d8362fb9-1b9c-4d92-8222-6745f842efcf Node size: 16384 Sector size: 4096 Filesystem size: 7.04GiB Block group profiles: Data: single 8.00MiB Metadata: DUP 368.62MiB System: DUP 12.00MiB SSD detected: no Incompat features: extref, skinny-metadata Number of devices: 1 Devices: ID SIZE PATH 1 7.04GiB /dev/sda1 root@pine54:~# mount /dev/sda1 /opt/ mount: unknown filesystem type 'btrfs' root@pine54:~# modprobe btrfs modprobe: FATAL: Module btrfs not found in directory /lib/modules/3.10.104-pine64
  3. Hi everyone, I was doing speed tests on the XR819 and started looking at the driver code. My this looks very similar to the cw1200 driver already in mainline Linux. I started modifying the cw1200 driver to try and get it to work with the XR819. Apart from someone renaming functions and adding a bunch of important junk for XR819, the drivers are quite similar. I've modified the cw1200 driver up to the point that it's loading the boot_cw1x60.bin ( boot_xr819.bin ) file, but for some reason the bootloader is returning an error instead of success. I don't think it's possible to diagnose this without the datasheet from ST. Clearly this exists, because people were able to write the cw1200 driver for mainline. Does anyone have a clue where I might find the datasheet for the CW1100? I also haven't been able to find the firmware files from ST for this chip. They don't exist in the linux-firmware tree! Here's my progress thus far: Try to load cw1200_wlan_sdio first time. Timeout waiting for bootloader to respond (I think XR819 has the same bug, no?) Unload the module and load it again: Here's my diff to the mainline driver.
  4. I suggest relevant discussion continues in this thread. I also urge mods to move relavant posts from here. What is Pinebook ?
  5. I am a bit lost how to create a bootable micro SD card with Armbian version for Pine64 board... I've downloaded Armbian_5.20_Pine64_Debian_jessie_3.10.102.7z file from Armbian site, extracted it using 7Zip on my Windows 7 machine and got following 6 files: armbian.txt armbian.txt.asc Armbian_5.25_Pine64_Debian_jessie_default_3.10.104.img Armbian_5.25_Pine64_Debian_jessie_default_3.10.104.img.asc sha256sum.sha AS I understiid, the *.img file is the disk image itself. However writing it to the SD card (using Etcher, as recommended, as well as Win32DiskImager that I've always used to write Pine64 images, then also tried with Rufus) renders the card ureadable, with a partition of 1.3GB, about the size of the IMG file.... The Getting Started page on Armbian Documentation describes how to check the SD card, but nothing about how to actually write the image to it. Several places also mention writing the RAW image using Etcher - where to find that RAW image? I'm very eager to try and compare the Armbian with other OSes running on Pine64, but it is so frustrating not being able even to boot up : -( Please, anyone can help?..
  6. Found an interesting way to keep the Pine64 cool.
  7. Hi everybody. Does anybody know how can i add the mali driver listed below to the latest Armbian image? Any suggestion would highly appreciated.
  8. If someone is interested i have compiled some TSLIB deb packages for the Pine64 Touch Screen to work without evdev driver or any other service behind. Advantages: * Easy to install (if you know how to edit xorg.conf) * No service needed * No calibration needed Disadvantages: * works on X11 only Information and deb packages: Hope it can be useful.
  9. I like the idea, but having an all winner chip kills it, I'd love tkaisers
  10. Hi, Not sure if this is me being stupid or a general problem with the 4.10 kernel: As there are now Mainline 4.10.0-next-20170125 images available from the main Pine64 download page, I tried flashing a spare card to start working on the touchscreen. Neither of the Server images based in 4.10 will boot on my board (no Ethernet activity so I can't ssh in). I also tried updating a working 3.10.104 / 5.25 installation with the dev. 4.x kernel, using the guide: Finally tried with a cross compiled kernel, built using the developer guide: All with same result: Board apparently doesn't boot, with no Ethernet activity. HAve I misunderstood something major, or is there a problem? BR. Marius
  11. Hello I installed today image version: Armbian_5.24.170129 (CLI version) Image starting fine but after some time i'm unable to login via ssh and hdmi showing something like this: Any ideas? Its on sandisk card class 10.. (brand new ) but kingston (used for 1,5 y)card also class 10 warking fine,
  12. Hi all, there is an issue with SPI on a Banana Pro (A20). I am on mainline kernel 4.5.5 now, but the problem already occurred on 3.4.109. SPI transfers are way to slow for my application, independently from the SPI clock. Investigating the SPI signals it turned out that there is an enormous delay between CS going active (low) and the transmission starting. The delay is in the magnitude of 10...20 usec which is a large multiple of the pure transmission time, so increasing the SPI clock does not solve the problem. The connected device is an SPI TFT display, so I have to send a large number of SPI words of 2 bytes each, where CS must toggle after each word (required by the target device). Consequently, the transmission of a large amount of data takes about several hundred times longer than required. I am not a driver expert, but I have looked into the source code of spi_sun4i.c which is the low level driver used for the A20 as far as I know. Here it seems, that the CS signal is under software control, i.e. it is handled as a normal GPIO. CS must be set/cleared by an explicit function call. I wonder, if this is the reason for the large delay. I found a quick-and-dirty workaround, where somebody configured the SPI controller directly via /dev/mem (i.e. bypassing kernel driver) and kept CS under hardware control, so the delay between CS and start of transmission is only some hundred nanoseconds. Now I am thinking of a modification of the SPI low level driver to keep CS under hardware control as well. However, I am not sure if this is a solution to my problem. Does anybody have a similar experience or a better idea than kernel modification? Any comments are welcome :-) Thanks
  13. Hi, I was unable to get static MAC address working on my Pine64. I have the kernel boot argument, console=ttyS0,115200 root=/dev/mmcblk0p1 rootwait rootfstype=ext4 panic=10 consoleblank=0 enforcing=0 loglevel=1 mac_addr=3a:bd:50:94:8b:06 But still, the from dmesg, [ 12.954581] sun8i-emac 1c30000.ethernet: device MAC address slot 0 aa:90:02:81:eb:e9 In the interfaces file, auto eth0 iface eth0 inet dhcp hwaddress ether 3a:bd:50:94:8b:06 But this caused error in ifup and system start up (networking cannot start since ifup failed with device in use) Although ifup failed, eth0 is visible in ifconfig, which means something else had already brought it up. Any ideas?
  14. I tried to get armbian running on my new pine64. Therefore I downloaded the latest two 7z-files for debian and ubuntu. But neither of them does an auto-resize nor does the first boot took more than 30sec - contrary to the documentation. I'm using the SD cards delivered with the pine64 (16GB). In a related post I've found there has been "update-rc filesystem defaults" to (re-)trigger the process (or update.rc). Neither nor I've found. How can I get the distribution created in the correct way on the SD card?
  15. Hey Igor and fellow Armbian forum members! I have worked with Armbian on my OPi PC and used the rtl8192cu-fixed github replacement driver, and recently just edited /etc/modules to include 8192cu(btw apt-get upgrade breaks this). However on my Pine64, dmesg says: rtlwifi/rtl8192cufw.bin isn't available. I have tried manually placing the Debian .bin file into the proper /lib but haven't been able to get the wlan0 to show up under iwconfig(yea I have already enabled it in /etc/network/interfaces. lsusb and lsmod both show some entries for 8912cu. Thanks for any insight, and let's hope we can fix this so that people can use their wifi adapters soon .
  16. Hi, When will soon be ready for the Armbian Pine A64 Desktop Debian? Can I now install Debian xfce on the Armbian Pine A64 Server? and how? Thank you
  17. Hi, I seem to be unable to create a working image for my Orange Pi PC+ with a 4.x kernel (I want to use Docker). I had a working 4.7.3 install but a recent (this week) apt-get upgrade installed a 4.8.x kernel (and probably a u-boot) after which my Opi PC+ will not boot anymore (my home-router shows the opi for a short time but it disappears before I can do a ssh to the Opi PC+). None of the images I have or create with a 4.x kernel seem to want to work. Only the 3.4.112 images that I download will work. Since I fried my uart0 and I haven't been able to use uart1 I have not been able to debug this. So I was hoping someone has a working image with a 4.x kernel (preferably debian-jessie server) for a Opi PC+ that they would be willing to share.
  18. Hi, not sure if this problem is related to Armbian, but in my case it occurs only on an Armian system. I have mainline kernel (4.7.x) running on a Banana Pro. wlan is configured as access point and works without any problems. eth0 is configured as client with static IP. The Banana is running 24/7, but the ethernet port is used only sporadically. The switch where eth0 is connected to is powered down most time. The problem is that eth0 forgets its IP configuration after a while, ifconfig then reports no IP address for eth0. I have to login via wlan and then ifdown/ifup eth0, then it works again. After a couple of hours (I dont know exactly how long), the IP is lost again. What is going wrong here?
  19. Hi, All ARM 64 get support plate. Spec: If it is like the 3.10 series kernel,?!?
  20. I am having the exact same hw configuration as described here. I am using latest (stable) mainline kernel 4.0.5, SPI is enabled in DTB like this: spi0: spi@01c05000 { pinctrl-names = "default"; pinctrl-0 = <&spi0_pins_a>; status = "okay"; spi0_0 { #address-cells = <1>; #size-cells = <0>; compatible = "spidev"; reg = <0>; spi-max-frequency = <50000000>; }; }; I am loading the driver like this and the displays back light goes on - so far is o.k. modprobe fbtft_device name=adafruit22a rotate=90 speed=4800000 fps=30 gpios=reset:272,led:226,dc:245 busnum=32766 This way, with different GPIOS numbers and without busnum parameter works perfectly well on kernel 3.4.x Kernel output when loading the driver on 4.0.5 [27880.540870] fbtft: module is from the staging directory, the quality is unknown, you have been warned. [27880.549004] fbtft_device: module is from the staging directory, the quality is unknown, you have been warned. [27880.551333] fbtft_device: SPI devices registered: [27880.551386] fbtft_device: spidev spi32766.0 50000kHz 8 bits mode=0x00 [27880.551406] fbtft_device: 'fb' Platform devices registered: [27880.551570] fbtft_device: Deleting spi32766.0 [27880.553696] fbtft_device: GPIOS used by 'adafruit22a': [27880.553735] fbtft_device: 'reset' = GPIO272 [27880.553756] fbtft_device: 'led' = GPIO226 [27880.553775] fbtft_device: 'dc' = GPIO245 [27880.553793] fbtft_device: SPI devices registered: [27880.553820] fbtft_device: fb_ili9340 spi32766.0 4800kHz 8 bits mode=0x00 [27880.575688] fb_ili9340: module is from the staging directory, the quality is unknown, you have been warned. [27880.819789] fb_ili9340 spi32766.0: SPI transfer failed: -22 [27880.819830] spi_master spi32766: failed to transfer one message from queue [27880.819850] fb_ili9340 spi32766.0: fbtft_update_display: write_vmem failed to update display buffer [27880.821093] graphics fb1: fb_ili9340 frame buffer, 320x240, 150 KiB video memory, 4 KiB DMA buffer memory, fps=33, spi32766.0 at 4 MHz When I write some picture to the display I got this: [28727.125092] fb_ili9340 spi32766.0: SPI transfer failed: -22 [28727.125141] spi_master spi32766: failed to transfer one message from queue [28727.125162] fb_ili9340 spi32766.0: fbtft_update_display: write_vmem failed to update display buffer [28727.154895] fb_ili9340 spi32766.0: SPI transfer failed: -22 [28727.154937] spi_master spi32766: failed to transfer one message from queue [28727.154957] fb_ili9340 spi32766.0: fbtft_update_display: write_vmem failed to update display buffer I haven't done the famous spi_test.c test and I also doesn't have any equipment to debug further. Is there any stupid thing that I am doing wrong or is this simply not done yet? Anyone got further on this?
  21. Hi, Pine 64's delivery is in full swing and thousands of people are receiving/received their Pine64 boards (Mine is scheduled for May). One of the survey shows that majority of the people have chosen to install linux on their boards. Many people are struggling to find a good image for their boards and current some what stable image is based on already end of life 3.10 kernel and there is promising development by sunxi. I am sure that thousands will get benefited if they get Armbian for Pine64. So How about Armbian for Pine 64? Regards, -- Avinash
  22. Hi! I'm testing the image for cubieboard (A10 SOC) onto my MK 802 II and the legacy kernel is working fine (USB, OGT, WIFI, HDMI...) I just have changed the script.bin I'm reading some documentation about the device trees and I don't understand how you compile the vanilla kernel. Sorry if is a stupid questions but my board has his own .dts (sun4i-a10-mk802ii.dts), how you get a common vanilla kernel valid for all the configurations without using one specific .dts for each board? Probably I'm missing something very basic for ARM kernels, but this is my 1º aproach.
  23. Hello Igor, I am starting exploring your nice "lib" tools for mainline/lamobo/trusty and end with this error message. the host is trusty / amd64 / quad cores / 8 GB RAM unsure if /bin/mktemp refers to loopback device or host /tmp lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk x Installing Armbian on the top of Ubuntu trusty base system ... x x x x build-essential x x x x lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk x x x 0% x x x mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj x mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj [ error ] Installation failed Setting up cmake-data ( ... Setting up cmake ( ... Processing triggers for libc-bin (2.19-0ubuntu6) ... Processing triggers for ca-certificates (20141019ubuntu0.14.04.1) ... /bin/mktemp: failed to create file via template '/tmp/user/0/ca-certificates.crt.tmp.XXXXXX': No such file or directory dpkg: error processing package ca-certificates (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: ca-certificates E: Sub-process /usr/bin/dpkg returned an error code (1) FYI gr@gr /run $ df -h Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur /dev/sda1 115G 63G 47G 58% / none 4,0K 0 4,0K 0% /sys/fs/cgroup udev 3,9G 4,0K 3,9G 1% /dev none 1,0G 8,0K 1,0G 1% /tmp tmpfs 799M 1,1M 798M 1% /run none 5,0M 0 5,0M 0% /run/lock none 3,9G 0 3,9G 0% /run/shm none 100M 0 100M 0% /run/user ramlog-tmpfs 2,0G 706M 1,3G 36% /var/log /dev/sda2 991M 105M 820M 12% /boot /dev/sdb6 210G 141G 59G 71% /home2 /dev/sdc1 1,8T 533G 1,2T 31% /home4 /dev/mapper/sdd1 1,8T 93M 1,7T 1% /home5 /dev/loop0p1 3,8G 526M 3,1G 15% /home/gr/armbian/output/cache/sdcard chdev 3,9G 4,0K 3,9G 1% /home/gr/armbian/output/cache/sdcard/dev regards, Guillaume
  24. Hi Igor, Hi Buddies, with the new changes of *.sh files because of "2>&1" you cannot figure out the compilation errors -- or if any staling questions like patching file tools/include/tools/be_byteshift.h patching file tools/include/tools/le_byteshift.h dpkg-deb: building package `linux-firmware-image-next-sunxi' in `../linux-firmware-image-next-sunxi_4.6_armhf.deb'. gzip: ./debian/dtbtmp/usr/share/doc/linux-dtb-next-sunxi/changelog.Debian.gz already exists; do you wish to overwrite (y or n)? so I have tried and would suggest the following changes in (or anything better for bash conditional piping) #make $CTHREADS ARCH=arm CROSS_COMPILE="$CCACHE arm-linux-gnueabihf-" zImage modules 2>&1 | dialog --backtitle "$backtitle" --progressbox "Compiling kernel $CCACHE ..." 20 80 MKE="make $CTHREADS ARCH=arm CROSS_COMPILE=\"$CCACHE arm-linux-gnueabihf-\" zImage modules" [[ $DEBUGKBUILD = "" ]] && MKE="${MKE} 2>&1 | dialog --backtitle \"$backtitle\" --progressbox \"Compiling kernel $CCACHE ...\" 20 80" eval $MKE #make $CTHREADS ARCH=arm CROSS_COMPILE="$CCACHE arm-linux-gnueabihf-" dtbs 2>&1 | dialog --backtitle "$backtitle" --progressbox "Compiling DTB $CCACHE ..." 20 80 MKE="make $CTHREADS ARCH=arm CROSS_COMPILE=\"$CCACHE arm-linux-gnueabihf-\" dtbs" [[ $DEBUGKBUILD = "" ]] && MKE="${MKE} 2>&1 | dialog --backtitle \"$backtitle\" --progressbox \"Compiling DTB $CCACHE ...\" 20 80" eval $MKE #make -j1 $KERNEL_PACKING KDEB_PKGVERSION=$REVISION LOCALVERSION="-"$LINUXFAMILY KBUILD_DEBARCH=armhf ARCH=arm DEBFULLNAME="$MAINTAINER" \ #DEBEMAIL="$MAINTAINERMAIL" CROSS_COMPILE="$CCACHE arm-linux-gnueabihf-" 2>&1 | dialog --backtitle "$backtitle" --progressbox "Packing kernel $CCACHE ..." 20 80 MKE="\ make -j1 $KERNEL_PACKING KDEB_PKGVERSION=$REVISION LOCALVERSION=\"-\"$LINUXFAMILY KBUILD_DEBARCH=armhf ARCH=arm DEBFULLNAME=\"$MAINTAINER\" \ DEBEMAIL=\"$MAINTAINERMAIL\" CROSS_COMPILE=\"$CCACHE arm-linux-gnueabihf-\"\ " [[ $DEBUGKBUILD = "" ]] && MKE="${MKE} 2>&1 | dialog --backtitle \"$backtitle\" --progressbox \"Packing kernel $CCACHE ...\" 20 80" eval $MKE including in DEBUGKBUILD="yes" # if "yes" then remove dialog for debug else "" for nice dialog style Cheers, Mr Poor 12.34 €
  25. Hello Igor, greatings everyone, I have realized the "build" link is missing to the /usr/src/linux-headers-x.x.x-sunxi Ubuntu Trusty (x86/amd64 kernel) provides such a link I was building a small kernel module from source (frandom-dkms) on my labomo-r1 gr@bpi:/lib/modules/4.2.3-sunxi$ ll total 1260 drwxr-xr-x 4 root root 4096 Oct 13 18:34 ./ drwxr-xr-x 3 root root 4096 Oct 13 15:20 ../ lrwxrwxrwx 1 root root 34 Oct 13 14:23 build -> /usr/src/linux-headers-4.2.3-sunxi/ drwxr-xr-x 9 root root 4096 Oct 13 15:20 kernel/ -rw-r--r-- 1 root root 360156 Oct 13 18:34 modules.alias -rw-r--r-- 1 root root 367304 Oct 13 18:34 modules.alias.bin -rw-r--r-- 1 root root 14935 Oct 11 14:12 modules.builtin -rw-r--r-- 1 root root 17813 Oct 13 18:34 modules.builtin.bin -rw-r--r-- 1 root root 82602 Oct 13 18:34 modules.dep -rw-r--r-- 1 root root 128280 Oct 13 18:34 modules.dep.bin -rw-r--r-- 1 root root 128 Oct 13 18:34 modules.devname -rw-r--r-- 1 root root 40034 Oct 11 14:12 modules.order -rw-r--r-- 1 root root 131 Oct 13 18:34 modules.softdep -rw-r--r-- 1 root root 103401 Oct 13 18:34 modules.symbols -rw-r--r-- 1 root root 131685 Oct 13 18:34 modules.symbols.bin drwxr-xr-x 3 root root 4096 Oct 13 18:34 updates/ without the link: gr@bpi:~/frandom/frandom-master$ ls CHANGELOG debian description-pak etc frandom.c INSTALL Makefile README usr gr@bpi:~/frandom/frandom-master$ make make -C /lib/modules/4.2.3-sunxi/build SUBDIRS=/home/gr/frandom/frandom-master modules make: *** /lib/modules/4.2.3-sunxi/build: No such file or directory. Stop. make: *** [default] Error 2 with the link: gr@bpi:~/frandom/frandom-master$ make make -C /lib/modules/4.2.3-sunxi/build SUBDIRS=/home/gr/frandom/frandom-master modules make[1]: Entering directory `/home2/src/linux-headers-4.2.3-sunxi' test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \ echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it."; \ echo >&2 ; \ /bin/false) mkdir -p /home/gr/frandom/frandom-master/.tmp_versions ; rm -f /home/gr/frandom/frandom-master/.tmp_versions/* make -f ./scripts/ obj=/home/gr/frandom/frandom-master gcc -Wp,-MD,/home/gr/frandom/frandom-master/.frandom.o.d -nostdinc -isystem /usr/lib/gcc/arm-linux-gnueabihf/4.8/include -I./arch/arm/include -Iarch/arm/include/generated/uapi -Iarch/arm/include/generated -Iinclude -I./arch/arm/include/uapi -Iarch/arm/include/generated/uapi -I./include/uapi -Iinclude/generated/uapi -include ./include/linux/kconfig.h -D__KERNEL__ -mlittle-endian -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -std=gnu89 -fno-dwarf2-cfi-asm -mabi=aapcs-linux -mno-thumb-interwork -mfpu=vfp -funwind-tables -marm -D__LINUX_ARM_ARCH__=7 -march=armv7-a -msoft-float -Uarm -fno-delete-null-pointer-checks -O2 --param=allow-store-data-races=0 -Wframe-larger-than=1024 -fno-stack-protector -Wno-unused-but-set-variable -fomit-frame-pointer -fno-var-tracking-assignments -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fconserve-stack -Werror=implicit-int -Werror=strict-prototypes -DCC_HAVE_ASM_GOTO -DMODULE -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(frandom)" -D"KBUILD_MODNAME=KBUILD_STR(frandom)" -c -o /home/gr/frandom/frandom-master/frandom.o /home/gr/frandom/frandom-master/frandom.c (cat /dev/null; echo kernel//home/gr/frandom/frandom-master/frandom.ko;) > /home/gr/frandom/frandom-master/modules.order make -f ./scripts/Makefile.modpost find /home/gr/frandom/frandom-master/.tmp_versions -name '*.mod' | xargs -r grep -h '\.ko$' | sort -u | sed 's/\.ko$/.o/' | scripts/mod/modpost -i ./Module.symvers -I /home/gr/frandom/frandom-master/Module.symvers -o /home/gr/frandom/frandom-master/Module.symvers -S -w -s -T - gcc -Wp,-MD,/home/gr/frandom/frandom-master/.frandom.mod.o.d -nostdinc -isystem /usr/lib/gcc/arm-linux-gnueabihf/4.8/include -I./arch/arm/include -Iarch/arm/include/generated/uapi -Iarch/arm/include/generated -Iinclude -I./arch/arm/include/uapi -Iarch/arm/include/generated/uapi -I./include/uapi -Iinclude/generated/uapi -include ./include/linux/kconfig.h -D__KERNEL__ -mlittle-endian -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -std=gnu89 -fno-dwarf2-cfi-asm -mabi=aapcs-linux -mno-thumb-interwork -mfpu=vfp -funwind-tables -marm -D__LINUX_ARM_ARCH__=7 -march=armv7-a -msoft-float -Uarm -fno-delete-null-pointer-checks -O2 --param=allow-store-data-races=0 -Wframe-larger-than=1024 -fno-stack-protector -Wno-unused-but-set-variable -fomit-frame-pointer -fno-var-tracking-assignments -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fconserve-stack -Werror=implicit-int -Werror=strict-prototypes -DCC_HAVE_ASM_GOTO -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(frandom.mod)" -D"KBUILD_MODNAME=KBUILD_STR(frandom)" -DMODULE -c -o /home/gr/frandom/frandom-master/frandom.mod.o /home/gr/frandom/frandom-master/frandom.mod.c ld -EL -r -T ./scripts/ --build-id -o /home/gr/frandom/frandom-master/frandom.ko /home/gr/frandom/frandom-master/frandom.o /home/gr/frandom/frandom-master/frandom.mod.o make[1]: Leaving directory `/home2/src/linux-headers-4.2.3-sunxi' gr@bpi:~/frandom/frandom-master$ ls CHANGELOG description-pak frandom.c frandom.mod.c frandom.o Makefile Module.symvers usr debian etc frandom.ko frandom.mod.o INSTALL modules.order README thanks! Guillaume