During compilation of customized distribution (using buildroot v. 11.2018) I have problem with libmount library (the problem appeared after I had included efl package in buildroot menuconfig - *Target packages -> Graphic lib... -> efl* ). I have additionaly installed package libmount-dev with no results. checking for getxattr in -lc... yes checking sys/xattr.h usability... yes checking sys/xattr.h presence... yes checking for sys/xattr.h... yes checking for XATTR_NOFOLLOW... no checking for LIBMOUNT... no configure: error: *** Could not find libmount How to include this library to obtain succesful compilation?

I use buildroot to compile a custom sedutil. I can compile and boot from a usb drive from all my computers except one, my Thinkpad T16 gen3. It gets stuck at:

Loading bzImage... ok
Loading rootfs.cpio.xz... ok

## syslinux.cfg

default DTA
prompt 0
noescape 1
label DTA
    kernel bzImage
    append debug loglevel=9 nosmp libata.allow_tpm=1 usbcore.autosuspend=-1 usbcore.old-scheme-first=1
    initrd rootfs.cpio.xz

I already tried to add debug loglevel=9 but nothing, something seems wrong with the laptop. I know it isn't a problem of compilation since it works perfectly on the other computers. I'd like to get what's wrong, which material or what can affect the initrd process. I couldn't find anything. Since there is literally no other print, I believe the kernel doesn't boot.

I'm trying to configure QT 5 through buildroot and some options are not available with the message requires an OpenGL-capable backend. I'm using buildroot 2013.08-rc1 but the same message comes up with 2013.05. I'm targeting x86_64 core2 platform and I can't find any options to select OpenGL backend (or OpenGL anything actually). How can I enable OpenGL backend in buildroot?

I'm creating an embedded system using Buildroot. Currently, my Buildroot configuration ensures the rootfs is remounted as read/write during startup. However I would like to remove this feature and keep my rootfs as read-only. I have a few questions regarding this: ---------- How do I change a user's password? This would require changing /etc/passwd & /etc/shadow. How do I change the timezone? This would require changing /etc/localtime. How do I create ssh keys for sshd? ssh-keygen creates the keys in /etc/ssh/ According to the Filesystem Hierarchy Standard, a Linux system is required to function with a read-only /etc/ directory, but it seems I'm finding a distinct loss of functionality as described above. ---------- Secondly, after specifying that the rootfs is to remain read-only in my Buildroot configuration, it elects to mount /var/ as a tmpfs (in RAM, so it is writable) But, this is volatile, how can I ensure runtime files (which I need to save) aren't lost on reboot or unexpected power-loss? I'm using UBIFS, in my embedded system. Am I required to create a read/write UBI volume which I use as persistent storage? Is this the standard in embedded systems? ---------- And finally, should I re-evaluate my idea to use a read-only rootfs at all? Given I am using UBI, and as wear-levelling is implemented across all the UBI volumes (the exist on the same device, of course), will I receive any benefit in making my rootfs read-only?

I just moved an old buildroot folder from an old VM to a newer one to consolidate. I thought that simply moving the folder, along with any dependent folders, and making the appropriate path/name changes would be all that is required to get it up and running in the new VM. Unfortunately, this appears to not be the case as I am greeted with the following error upon attempting to build in this new VM: # # configuration written to /home/mirion/mirion/buildroot-2013.05/.config # /usr/bin/make -j5 HOSTCC="/usr/bin/gcc" HOSTCXX="/usr/bin/g++" silentoldconfig make: Entering directory '/home/mirion/mirion/buildroot-2013.05' BR2_DEFCONFIG='' KCONFIG_AUTOCONFIG=/home/mirion/mirion/buildroot-2013.05/output/build/buildroot-config/auto.conf KCONFIG_AUTOHEADER=/home/mirion/mirion/buildroot-2013.05/output/build/buildroot-config/autoconf.h KCONFIG_TRISTATE=/home/mirion/mirion/buildroot-2013.05/output/build/buildroot-config/tristate.config BUILDROOT_CONFIG=/home/mirion/mirion/buildroot-2013.05/.config /home/mirion/mirion/buildroot-2013.05/output/build/buildroot-config/conf --silentoldconfig Config.in *** Error during update of the configuration. Makefile:692: recipe for target 'silentoldconfig' failed make: *** [silentoldconfig] Error 1 make: Leaving directory '/home/mirion/mirion/buildroot-2013.05' Makefile:396: recipe for target '/home/mirion/mirion/buildroot-2013.05/output/build/buildroot-config/auto.conf' failed make: *** [/home/mirion/mirion/buildroot-2013.05/output/build/buildroot-config/auto.conf] Error 2 mv: cannot stat 'output/images/rootfs.ubi': No such file or directory Are there any ideas as to what I can do to resolve this? I did some poking around on google but could not find anything conclusive. EDIT: Original VM was running Lubuntu 12.04, the new VM is running Ubuntu 17.10. Thanks.

I'm trying to run the [uvc-gadget](https://gitlab.freedesktop.org/camera/uvc-gadget) application and I'm running into "No cameras were identified on the system" error from libcamera on my **Raspberry Pi Zero 2 W** using buildroot and am hoping someone can spot what I'm missing. Here’s all the stuff I’ve already tried: --- ## **Hardware & Software** - **Board:** Raspberry Pi Zero 2 W Rev 1.0 - **Camera:** Camera Module 3, IMX708 module - **OS:** Custom Buildroot rootfs (64-bit, aarch64) - **Kernel:** Raspberry Pi Foundation kernel (cd231d47) - **libcamera:** Built and installed via Buildroot (0.5.0, mainline, not raspberrypi version) --- ## **Symptoms** - libcamera-apps is not installed. Should not be needed for my application, I think. - /dev/video0 exists, but it's the UVC gadget, not the camera - /dev/media* and /dev/video* for the camera do **not** appear --- ## **What Works** - **Same hardware and camera module work perfectly with Raspberry Pi OS Lite (64-bit)** - The camera shows up as expected in /dev/media* and /dev/video* on Raspberry Pi OS --- ## **Kernel and Firmware Setup** - **Kernel source:** [raspberrypi/linux](https://github.com/raspberrypi/linux) - **Kernel commit:** (tried multiple, including the latest as of 2025-05-18) - **Defconfig:** bcm2711_defconfig (as per official RPi docs for 64-bit) - **DTB:** bcm2710-rpi-zero-2-w.dtb - **Overlays:** Using official overlays, e.g., imx708.dtbo - **config.txt:**

start_x=1
    gpu_mem=128
    camera_auto_detect=1
	
	# For USB gadget mode
	dtoverlay=dwc2,dr_mode=otg

- All kernel, DTB, and overlay build dates match and are from the same build. --- ## **Kernel Config Checks** I've confirmed the following kernel options are enabled (=y not =m): - CONFIG_MEDIA_CONTROLLER - CONFIG_MEDIA_SUPPORT - CONFIG_MEDIA_PLATFORM_SUPPORT - CONFIG_MEDIA_CAMERA_SUPPORT - CONFIG_V4L2_FWNODE - CONFIG_VIDEO_BCM2835_UNICAM - CONFIG_VIDEO_IMX708 - CONFIG_V4L2_SUBDEV_API - CONFIG_I2C_CHARDEV I disabled CONFIG_VIDEO_BCM2835_UNICAM_LEGACY --- ## **Troubleshooting Steps Taken** 1. **Tested hardware and camera with Raspberry Pi OS – works perfectly.** 2. **Checked DTB and overlays:** - Confirmed /mnt/bcm2710-rpi-zero-2-w.dtb and /mnt/overlays/imx708.dtbo match kernel build date. - strings on DTB shows correct nodes (linux,cma, etc.). 3. **Checked dmesg:** - No probe errors, but also **no evidence of Unicam/Cam sensor driver binding**. 4. **/proc/device-tree/model** confirms: Raspberry Pi Zero 2 W Rev 1.0 5. **Verified kernel version:** Linux buildroot 6.12.20-v8 #3 SMP PREEMPT ... aarch64 GNU/Linux 6. **Confirmed udev (+eudev option) is running under BusyBox init system to create device nodes.** 7. **No /dev/media* or /dev/video* nodes for camera after boot.** --- ## **Things I've Ruled Out** - **Hardware issue:** Camera and cables work with Pi OS - **DTB/overlay mismatch:** All files are from same build - **libcamera-apps dependency:** On Pi OS works with and without libcamera-apps present. --- ## **Questions** - What else could be preventing the Unicam or camera sensor drivers from probing or binding to the hardware? - Could there be a kernel config or missing firmware file issue? - Does anyone have a working kernel .config for a 64-bit Buildroot + Pi camera setup on Zero 2 W? - Are there any other debugging steps or logs I should collect to pinpoint the issue? --- **Any help or suggestions would be greatly appreciated! If you need logs, let me know what to post.** Thanks!

I'm trying to compile a [Buildroot](https://bellard.org/tinyemu/buildroot-riscv-2018-10-20.tar.gz) image using a preconfigured builtin _defconfig file... More specific the riscv64_xwin_defconfig which is a simple setup for a riscv64 image with Xorg builtin. Since it's a rather old build i'm doing this inside a Fedora 23 Docker container which has gcc version 5.3.1, i don't think this is a problem since i can successfully build the non-Xwin riscv64 defconfig just fine The problem resides when the Makefile tries to build the specific package "eudev-3.2" Here is the config.log:

configure:3158: $? = 1
configure:3178: checking whether the C compiler works
configure:3200: /home/buildroot-riscv-2018-10-20/output/host/usr/bin/riscv64-buildroot-linux-gnu-gcc -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64  -Os  -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64  conftest.c -lrt >&5
/home/buildroot-riscv-2018-10-20/output/host/usr/lib/gcc/riscv64-buildroot-linux-gnu/7.3.0/../../../../riscv64-buildroot-linux-gnu/bin/ld: warning: libpthread.so.0, needed by /home/buildroot-riscv-2018-10-20/output/host/usr/riscv64-buildroot-linux-gnu/sysroot/usr/lib64/lp64d/librt.so, not found (try using -rpath or -rpath-link)
/home/buildroot-riscv-2018-10-20/output/host/usr/riscv64-buildroot-linux-gnu/sysroot/usr/lib64/lp64d/librt.so: undefined reference to `__pthread_barrier_wait@GLIBC_PRIVATE'
/home/buildroot-riscv-2018-10-20/output/host/usr/riscv64-buildroot-linux-gnu/sysroot/usr/lib64/lp64d/librt.so: undefined reference to `pthread_attr_setstacksize@GLIBC_2.27'
/home/buildroot-riscv-2018-10-20/output/host/usr/riscv64-buildroot-linux-gnu/sysroot/usr/lib64/lp64d/librt.so: undefined reference to `__pthread_barrier_init@GLIBC_PRIVATE'
/home/buildroot-riscv-2018-10-20/output/host/usr/riscv64-buildroot-linux-gnu/sysroot/usr/lib64/lp64d/librt.so: undefined reference to `__pthread_unwind@GLIBC_PRIVATE'
/home/buildroot-riscv-2018-10-20/output/host/usr/riscv64-buildroot-linux-gnu/sysroot/usr/lib64/lp64d/librt.so: undefined reference to `pthread_create@GLIBC_2.27'
/home/buildroot-riscv-2018-10-20/output/host/usr/riscv64-buildroot-linux-gnu/sysroot/usr/lib64/lp64d/librt.so: undefined reference to `pthread_sigmask@GLIBC_2.27'
/home/buildroot-riscv-2018-10-20/output/host/usr/riscv64-buildroot-linux-gnu/sysroot/usr/lib64/lp64d/librt.so: undefined reference to `pthread_once@GLIBC_2.27'
/home/buildroot-riscv-2018-10-20/output/host/usr/riscv64-buildroot-linux-gnu/sysroot/usr/lib64/lp64d/librt.so: undefined reference to `__shm_directory@GLIBC_PRIVATE'
/home/buildroot-riscv-2018-10-20/output/host/usr/riscv64-buildroot-linux-gnu/sysroot/usr/lib64/lp64d/librt.so: undefined reference to `pthread_detach@GLIBC_2.27'
/home/buildroot-riscv-2018-10-20/output/host/usr/riscv64-buildroot-linux-gnu/sysroot/usr/lib64/lp64d/librt.so: undefined reference to `pthread_cancel@GLIBC_2.27'
/home/buildroot-riscv-2018-10-20/output/host/usr/riscv64-buildroot-linux-gnu/sysroot/usr/lib64/lp64d/librt.so: undefined reference to `__pthread_get_minstack@GLIBC_PRIVATE'
collect2: error: ld returned 1 exit status

I'm working on an embedded device with an arm cortex A9. The kernel version is 4.16.0 and is generated by buildroot 2018.05. The storage memory is an mmc with several partition. U-boot reads the uImage in one partition and starts the kernel. The filesystem is included in the kernel image and is loaded at startup in an initramfs (config : BR2_TARGET_ROOTFS_INITRAMFS). I want to use an overlayfs to use a folder (in the mmc) as a 'user' filesystem, mounted onto /. I already tried succesfully to overlay /etc with a directory named /data/etc by adding these lines to the /etc/fstab : /dev/mmcblk0p1 /data auto defaults 1 2 overlay /etc overlay x-systemd.requires=/data,lowerdir=/etc,upperdir=/data/etc,workdir=/data/work/etc 0 0 This is working, but the overlay is mounted after systemd has already launch its sevices. So the network configuration for example is the one in the uImage and not the one in my user filesystem. I'd like to mount the overlay before lauching systemd, just after / is mounted. I have understood that at startup, the system creates a first memory space in ram and then extracts the cpio image in it. Then / is mounted there and the system launches the first program : systemd:/sbin/init with the PID 1. Is my understanding right ? I have read lots of article and Q&A website but I still do not understand where I have to make the changes to perform my overlay at boot time. What are the files that contains the mount / operation ?

I've used a given board configuration to reconfigure it for my individual board. My board has a CS4270 sound device of Cirrus Logic. My uImage is booting successfully on my target hardware, but an alsactl init always shows me no sound card. I loaded as many sound modules as I can, e.g. modprobe snd-soc-cs4270. But I have the feeling there is one module missing because the [alsa-project website](http://www.alsa-project.org/main/index.php/Matrix:Module-cs4270) shows a specific module named snd-cs4270. Can I get this module installed by buildroot or do I have to download and integrate it into my target hardware on my own? I've followed [this question](https://unix.stackexchange.com/questions/59497/alsa-asoc-how-to-correctly-load-devices-drivers) and ended up with the question, if I must implement the sound device in the board file in linux/linux-kernel/arch//mach-/.c. But this can't give me a snd-cs4270module. Has anyone an idea which way I shall go to get this thing done?

I'd like to load some additional modules at boot. This works fine from the command line: modprobe -a i2c-dev modprobe -a snd-soc-pcm512x modprobe -a snd-soc-wm8804 But I want this done at boot. I've tried creating /etc/modules, /etc/modprobe.conf and /etc/modprobe.d/i2c-dev.conf, etc. with the module name in there, but no luck. I'm using a buildroot-2017-08, which I believes uses kmod, with a BusyBox init. I can just create an init.d script, but I think there's a specific location that should contain the list of modules to load.

I am running a custom linux distribution on a custom board running on an ATSAMA5D29. I am managed to get the sound to work on the demo board, but when running it on custom hardware I get the error: # speaker-test speaker-test 1.2.11 Playback device is default Stream parameters are 48000Hz, S16_LE, 1 channels Using 16 octaves of pink noise ALSA lib dlmisc.c:226:(snd_dlsym_verify) unable to verify version for symbol _snd_pcm_empty_open ALSA lib dlmisc.c:348:(snd_dlobj_cache_get0) symbol _snd_pcm_empty_open is not defined inside [builtin] Playback open error: -6,No such device or address This happens even when running on the loopback card. Here's the list of devices (exactly the same output as the functioning demo board) # aplay -l **** List of PLAYBACK Hardware Devices **** card 0: Loopback [Loopback], device 0: Loopback PCM [Loopback PCM] Subdevices: 8/8 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 Subdevice #3: subdevice #3 Subdevice #4: subdevice #4 Subdevice #5: subdevice #5 Subdevice #6: subdevice #6 Subdevice #7: subdevice #7 card 0: Loopback [Loopback], device 1: Loopback PCM [Loopback PCM] Subdevices: 8/8 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 Subdevice #3: subdevice #3 Subdevice #4: subdevice #4 Subdevice #5: subdevice #5 Subdevice #6: subdevice #6 Subdevice #7: subdevice #7 card 1: CLASSD [CLASSD], device 0: CLASSD PCM snd-soc-dummy-dai-0 [CLASSD PCM snd-soc-dummy-dai-0] Subdevices: 1/1 Subdevice #0: subdevice #0 # aplay -L null Discard all samples (playback) or generate zero samples (capture) default:CARD=Loopback Loopback, Loopback PCM Default Audio Device sysdefault:CARD=Loopback Loopback, Loopback PCM Default Audio Device front:CARD=Loopback,DEV=0 Loopback, Loopback PCM Front output / input surround21:CARD=Loopback,DEV=0 Loopback, Loopback PCM 2.1 Surround output to Front and Subwoofer speakers surround40:CARD=Loopback,DEV=0 Loopback, Loopback PCM 4.0 Surround output to Front and Rear speakers surround41:CARD=Loopback,DEV=0 Loopback, Loopback PCM 4.1 Surround output to Front, Rear and Subwoofer speakers surround50:CARD=Loopback,DEV=0 Loopback, Loopback PCM 5.0 Surround output to Front, Center and Rear speakers surround51:CARD=Loopback,DEV=0 Loopback, Loopback PCM 5.1 Surround output to Front, Center, Rear and Subwoofer speakers surround71:CARD=Loopback,DEV=0 Loopback, Loopback PCM 7.1 Surround output to Front, Center, Side, Rear and Woofer speakers default:CARD=CLASSD CLASSD, CLASSD PCM snd-soc-dummy-dai-0 Default Audio Device sysdefault:CARD=CLASSD CLASSD, CLASSD PCM snd-soc-dummy-dai-0 Default Audio Device The dmesg output may give some hints: # dmesg | grep classd device: 'fc048000.classd': device_add bus: 'platform': add device fc048000.classd PM: Adding info for platform:fc048000.classd platform fc048000.classd: Not linking /ahb/apb/clock-controller@f0014000 - might never become dev /ahb/apb/classd@fc048000 Dropping the fwnode link to /ahb/apb/clock-controller@f0014000 platform fc048000.classd: Not linking /ahb/apb/interrupt-controller@fc020000 - might never become dev /ahb/apb/classd@fc048000 Dropping the fwnode link to /ahb/apb/interrupt-controller@fc020000 /ahb/apb/classd@fc048000 Linked as a fwnode consumer to /ahb/apb/pinctrl@fc038000 /ahb/apb/classd@fc048000 Dropping the fwnode link to /ahb/apb/pinctrl@fc038000/classd_default_pfets /ahb/apb/classd@fc048000 Dropping the fwnode link to /ahb/apb/pinctrl@fc038000/classd_default_nfets device: 'platform:fc038000.pinctrl--platform:fc048000.classd': device_add devices_kset: Moving fc048000.classd to end of list PM: Moving platform:fc048000.classd to end of list platform fc048000.classd: Linked as a consumer to fc038000.pinctrl /ahb/apb/classd@fc048000 Dropping the fwnode link to /ahb/apb/pinctrl@fc038000 bus: 'platform': add driver atmel-classd bus: 'platform': __driver_probe_device: matched device fc048000.classd with driver atmel-classd bus: 'platform': really_probe: probing driver atmel-classd with device fc048000.classd atmel-classd fc048000.classd: no init pinctrl state atmel-classd fc048000.classd: no sleep pinctrl state atmel-classd fc048000.classd: no idle pinctrl state atmel-classd fc048000.classd: PWM modulation type is Differential, non-overlapping is enabled driver: 'atmel-classd': driver_bound: bound to device 'fc048000.classd' bus: 'platform': really_probe: bound device fc048000.classd to driver atmel-classd There is more information in sysfs and debugfs but none of it differed from the functioning board that I could tell. The relevant kernel configs are: CONFIG_SND=y CONFIG_SND_TIMER=y CONFIG_SND_PCM=y CONFIG_SND_DMAENGINE_PCM=y CONFIG_SND_PCM_TIMER=y CONFIG_SND_SUPPORT_OLD_API=y CONFIG_SND_PROC_FS=y CONFIG_SND_VERBOSE_PROCFS=y CONFIG_SND_VERBOSE_PRINTK=y CONFIG_SND_CTL_FAST_LOOKUP=y CONFIG_SND_DEBUG=y CONFIG_SND_DEBUG_VERBOSE=y CONFIG_SND_DRIVERS=y CONFIG_SND_HDA_PREALLOC_SIZE=64 CONFIG_SND_ARM=y CONFIG_SND_SPI=y CONFIG_SND_SOC=y CONFIG_SND_SOC_GENERIC_DMAENGINE_PCM=y CONFIG_SND_ATMEL_SOC=y CONFIG_SND_ATMEL_SOC_CLASSD=y If anyone has any ideas or other debug information I should provide please let me know.

I am trying to use tw9990 connected to a ATSAMA5D29 to play a camera feed. I have a custom board where the digital data lines are going to the ISC lines of the processor. I have an embedded linux distro made in Buildroot based off the microchip kernel. I am seeing the TW9910 module come up and talk to the TW9990 chip successfully, but I don't see any /dev/video. I added a small patch to the microchip-isc driver's probe() function which printed "probing" with printk, but I'm not seeing it in dmesg. An interesting, but confusing part of dmesg: # dmesg | grep isc device class 'misc': registering /ahb/apb/isc@f0008000 Linked as a fwnode consumer to /ahb/apb/pinctrl@fc038000 /ahb/apb/isc@f0008000 Dropping the fwnode link to /ahb/apb/pinctrl@fc038000/isc_base /ahb/apb/isc@f0008000 Dropping the fwnode link to /ahb/apb/pinctrl@fc038000/isc_data_8bit device: 'platform:fc038000.pinctrl--platform:f0008000.isc': device_add devices_kset: Moving f0008000.isc to end of list PM: Moving platform:f0008000.isc to end of list platform f0008000.isc: Linked as a consumer to fc038000.pinctrl /ahb/apb/isc@f0008000 Dropping the fwnode link to /ahb/apb/pinctrl@fc038000 bus: 'platform': add driver microchip-sama5d2-isc /ahb/apb/i2c@f8028000/tw9990@44: Relaxing link with /ahb/apb/isc@f0008000 /ahb/apb/isc@f0008000: Relaxing link with /ahb/apb/i2c@f8028000/tw9990@44 platform f0008000.isc: Fixed dependency cycle(s) with /ahb/apb/i2c@f8028000/tw9990@44 device: 'i2c:0-0044--platform:f0008000.isc': device_add platform f0008000.isc: Linked as a sync state only consumer to 0-0044 /ahb/apb/isc@f0008000 Dropping the fwnode link to /ahb/apb/i2c@f8028000/tw9990@44 /ahb/apb/i2c@f8028000/tw9990@44: Relaxing link with /ahb/apb/isc@f0008000 i2c 0-0044: Fixed dependency cycle(s) with /ahb/apb/isc@f0008000 device: 'platform:f0008000.isc--i2c:0-0044': device_add i2c 0-0044: Linked as a sync state only consumer to f0008000.isc /ahb/apb/i2c@f8028000/tw9990@44 Dropping the fwnode link to /ahb/apb/isc@f0008000 at91_i2c f8028000.i2c: Dropping the link to f0008000.isc device: 'platform:f0008000.isc--platform:f8028000.i2c': device_unregister tw9910 0-0044: Dropping the link to f0008000.isc device: 'platform:f0008000.isc--i2c:0-0044': device_unregister The device_register and between isc and i2c may be part of the problem, but I don't know why that's happening. The full dmesg is here and the kernel configuration is here .

I use busybox (and buildroot). How to use status? For example dd if=disk.img of=/dev/sda bs=4M conv=fsync status=progress

I recently took on a project to create a Linux image with basic hardware support for the NanoPi Neo SOM. This is my first experience working with embedded Linux, as my background has primarily been in developing hardware for microcontrollers. For this task, I am utilizing Buildroot. While the output image works well, I have encountered an issue: I cannot find SPI support in the ***/dev/ directory***, which I believe is crucial for my application. However, I do see some SPI-related files located in other parts of the system, such as ***/sys/bus/***, ***/sys/class/***, and ***/lib/modules/6.10.9/kernel/drivers/***. While calling **make linux-menuconfig** command and searching for SPI configuration this is what I found: Symbol: SPI_SPIDEV [=y] │ Type : tristate │ Defined at drivers/spi/Kconfig:1222 │ Prompt: User mode SPI device driver support │ Depends on: SPI [=y] && SPI_MASTER [=y] │ Location: │ -> Device Drivers │ -> SPI support (SPI [=y]) │ (1) -> User mode SPI device driver support (SPI_SPIDEV [=y]) This is what I found in **./buildroot/output/target/boot/sun8i-h3-nanopi-neo.dtb**: pinctrl@1c20800 { spi0-pins { pins = "PC0\0PC1\0PC2\0PC3"; function = "spi0"; phandle = ; }; spi1-pins { pins = "PA15\0PA16\0PA14\0PA13"; function = "spi1"; phandle = ; }; }; soc { spi@1c68000 { compatible = "allwinner,sun8i-h3-spi"; reg = ; interrupts = ; clocks = ; clock-names = "ahb\0mod"; dmas = ; dma-names = "rx\0tx"; pinctrl-names = "default"; pinctrl-0 = ; resets = ; status = "disabled"; #address-cells = ; #size-cells = ; phandle = ; }; spi@1c69000 { compatible = "allwinner,sun8i-h3-spi"; reg = ; interrupts = ; clocks = ; clock-names = "ahb\0mod"; dmas = ; dma-names = "rx\0tx"; pinctrl-names = "default"; pinctrl-0 = ; resets = ; status = "disabled"; #address-cells = ; #size-cells = ; phandle = ; }; }; __symbols__ { spi0_pins = "/soc/pinctrl@1c20800/spi0-pins"; spi1_pins = "/soc/pinctrl@1c20800/spi1-pins"; spi0 = "/soc/spi@1c68000"; spi1 = "/soc/spi@1c69000"; }; I changed status from **"disabled"** to **"okay"** but it did not help. Does anyone have insights into why this might be happening or suggestions for resolving this issue? Thank you!

I would like to merge configuration from Makefile, for this I've updated external.mk and introduced this:

# Custom target to merge multiple defconfig files
.PHONY: merge
merge:
	@if [ -z "$(filter %_defconfig,$(MAKECMDGOALS))" ]; then \
		echo "No defconfig files provided. Usage: make merge a_defconfig b_defconfig ..."; \
		exit 1; \
	fi
	@echo "Merging configuration files: $(filter %_defconfig,$(MAKECMDGOALS))"

# Prevent Make from treating the defconfig files as targets
$(filter %_defconfig,$(MAKECMDGOALS)):
	@:

unfortunately, it doesn't work:

$ make merge a_defconfig b_defconfig
make: *** No rule to make target 'merge'.  Stop.
make: *** [Makefile:83: _all] Error 2

If I don't pass any target parameters it reasonably reports missing configs:

make merge 
No defconfig files provided. Usage: make merge a_defconfig b_defconfig ...
make: *** [/tmp/buildroot/external.mk:17: merge] Error 1
make: *** [Makefile:82: _all] Error 2

What am I doing wrong?

If I do: git clone git://git.buildroot.net/buildroot cd buildroot git checkout 2016.05 make qemu_x86_defconfig make BR2_JLEVEL=2 qemu-system-x86_64 -M pc -kernel output/images/bzImage -drive file=output/images/rootfs.ext2,if=virtio,format=raw -append root=/dev/vda -net nic,model=virtio -net user I have to type root into QEMU before I can use the shell. How to configure buildroot to skip that and login directly? Tested on Ubuntu 16.04.

In order to test the root file system i need to run QEMU with created disk image as root file system, the QEMU accepts -kernel which can be used for specifying kernel directly without deploying it inside root file system, however i need similar feature for root file system to specify path of extracted root file system instead of creating a disk image and use it with -hda or -usbdisk options. is it possible at all with QEMU alone?! Or with third-party tools (like virtual disk image emulator) My goal is to test a tar archive of root file system without creating disk image

I am using buildroot to generate a custom linux image. I have the **bluez** packages installed, which allows me to connect to another device via bluetooth using the bluetoothctl command. However, when I use the **bt-obex** command to share a file

bt-obex -p  file

, I get the error

Couldn't connect to DBus session bus: Cannot autolaunch D-Bus without X11 $DISPLAY

. I guess bt-obex doesn't use any GUI, so I don't understand the error. Can bt-obex be used to work without GUI? Or do you now other way to share files via Bluetooth using the command line? Thank you.

I try to build the Linux kernel with Buildroot using Docker. I've created a simple Docker image: FROM debian:7 MAINTAINER OrangeTux RUN apt-get update && \ apt-get install -y \ build-essential \ bash \ bc \ binutils \ build-essential \ bzip2 \ cpio \ g++ \ gcc \ git \ gzip \ make \ libncurses5-dev \ patch \ perl \ python \ rsync \ sed \ tar \ unzip \ wget WORKDIR /root RUN git clone git://git.buildroot.net/buildroot WORKDIR /root/buildroot CMD ["/bin/bash"] I want to keep dl/ andoutput/build/ when container stops, so I don't have to download and compile all dependencies every time. I also want the build products on my host. Therefore I start container like this: `$ docker run -ti -v $(pwd)/dl:/root/buildroot/dl -v \ $(pwd)/output/build:/root/buildroot/output/build -v \ $(pwd)/output/images:/root/buildroot/output/images orangetux/buildroot` I'm able to run make menuconfig which builds the configuration for Buildroot. I've made a few modifications to the defaults. Here's the output of make savedefconfig: BR2_arm=y BR2_LINUX_KERNEL=y BR2_LINUX_KERNEL_DEFCONFIG="at91_dt" The next step is to build linux-menuconfig. This action failed and I've no clue what is going wrong: $ make linux-menuconfig /usr/bin/make -j1 HOSTCC="/usr/bin/gcc" HOSTCXX="/usr/bin/g++" silentoldconfig make: Entering directory `/root/buildroot' BR2_DEFCONFIG='' KCONFIG_AUTOCONFIG=/root/buildroot/output/build/buildroot-config/auto.conf KCONFIG_AUTOHEADER=/root/buildroot/output/build/buildroot-config/autoconf.h KCONFIG_TRISTATE=/root/buildroot/output/build/buildroot-config/tristate.config BR2_CONFIG=/root/buildroot/.config BR2_EXTERNAL=support/dummy-external SKIP_LEGACY= /root/buildroot/output/build/buildroot-config/conf --silentoldconfig Config.in *** Error during update of the configuration. make: *** [silentoldconfig] Error 1 make: Leaving directory `/root/buildroot' make: *** [/root/buildroot/output/build/buildroot-config/auto.conf] Error 2 The file /root/buildroot/output/build/buildroot-config/auto.conf doesn't exists. Why does the file not exists and how can I build linux-menuconfig?

On a Buildroot environment for RPi 3 B+ I have this connection file: # cat /etc/NetworkManager/system-connections/mark.nmconnection [connection] id=mark uuid=0f285419-2238-4b94-ad48-577a1a5f3765 type=wifi interface-name=wlan0 timestamp=295 autoconnect=true [wifi] mode=infrastructure ssid=mark [wifi-security] key-mgmt=wpa-psk psk=mypassword [ipv4] dns=192.168.2.1;8.8.8.8; method=auto [ipv6] addr-gen-mode=default method=disabled There are issues: the first is on the console when the connection is up I read: > IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready but I've disabled the ipv6 protocol! The second one and more important is the autoconnect behavior. Here I read the default value is true but without this option in my file it *never* connects automatically. I always need to issue: # nmcli con up mark Instead, adding autoconnect=true leads to an odd behavior. *Some times* it automatically connects, others does not. The access-point is close and always active. In fact, when it does not connect automatically issuing the above command leads to an immediate connection. I inspected the logs (/var/logs/messages). When it does not connect, the last messages are: Jan 1 00:00:08 mark daemon.info NetworkManager: [8.9299] NetworkManager (version 1.42.0) is starting... (boot:a02ac8dc-0c02-4a96-a3f4-2615029efee6) Jan 1 00:00:08 mark daemon.info NetworkManager: [8.9302] Read config: /etc/NetworkManager/NetworkManager.conf Jan 1 00:00:08 mark daemon.info NetworkManager: [8.9521] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager" Jan 1 00:00:09 mark daemon.info NetworkManager: [9.0134] manager[0x55bd54ed10]: monitoring kernel firmware directory '/lib/firmware'. Jan 1 00:00:09 mark daemon.info NetworkManager: [9.0322] hostname: hostname: couldn't get property from hostnamed Jan 1 00:00:09 mark daemon.info NetworkManager: [9.0338] hostname: static hostname changed from (none) to "mark" Jan 1 00:00:09 mark daemon.info NetworkManager: [9.0374] dns-mgr: init: dns=default,systemd-resolved rc-manager=file Jan 1 00:00:09 mark daemon.info NetworkManager: [9.0419] rfkill0: found Wi-Fi radio killswitch (at /sys/devices/platform/soc/3f300000.mmcnr/mmc_host/mmc1/mmc1:0001/mmc1:0001:1/ieee80211/phy0/rfkill0) (driver brcmfmac) Jan 1 00:00:09 mark daemon.info NetworkManager: [9.0431] manager[0x55bd54ed10]: rfkill: Wi-Fi hardware radio set enabled Jan 1 00:00:09 mark daemon.info NetworkManager: [9.0433] manager[0x55bd54ed10]: rfkill: WWAN hardware radio set enabled Jan 1 00:00:09 mark daemon.info NetworkManager: [9.0619] Loaded device plugin: NMAtmManager (/usr/lib/NetworkManager/1.42.0/libnm-device-plugin-adsl.so) Jan 1 00:00:09 mark daemon.info NetworkManager: [9.0727] Loaded device plugin: NMWifiFactory (/usr/lib/NetworkManager/1.42.0/libnm-device-plugin-wifi.so) Jan 1 00:00:09 mark daemon.info NetworkManager: [9.0734] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file Jan 1 00:00:09 mark daemon.info NetworkManager: [9.0741] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file Jan 1 00:00:09 mark daemon.info NetworkManager: [9.0745] manager: Networking is enabled by state file Jan 1 00:00:09 mark daemon.info dbus-daemon: [system] Activating service name='org.freedesktop.nm_dispatcher' requested by ':1.0' (uid=0 pid=267 comm="/usr/sbin/NetworkManager") (using servicehelper) Jan 1 00:00:09 mark daemon.warn NetworkManager: [9.0871] settings: could not load plugin 'ifupdown' from file '/usr/lib/NetworkManager/1.42.0/libnm-settings-plugin-ifupdown.so': No such file or directory Jan 1 00:00:09 mark daemon.info NetworkManager: [9.0875] settings: Loaded settings plugin: keyfile (internal) Jan 1 00:00:09 mark daemon.info NetworkManager: [9.1254] dhcp: init: Using DHCP client 'internal' Jan 1 00:00:09 mark daemon.info NetworkManager: [9.1284] manager: (lo): new Loopback device (/org/freedesktop/NetworkManager/Devices/1) Jan 1 00:00:09 mark daemon.info NetworkManager: [9.1404] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2) Jan 1 00:00:09 mark daemon.info NetworkManager: [9.1519] settings: (eth0): created default wired connection 'Wired connection 1' Jan 1 00:00:09 mark daemon.info NetworkManager: [9.1523] device (eth0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Jan 1 00:00:09 mark daemon.info dbus-daemon: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Jan 1 00:00:09 mark daemon.info NetworkManager: [9.2498] device (wlan0): driver supports Access Point (AP) mode Jan 1 00:00:09 mark daemon.info NetworkManager: [9.2572] manager: (wlan0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/3) Jan 1 00:00:09 mark daemon.info NetworkManager: [9.2602] device (wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Jan 1 00:00:09 mark kern.info kernel: [ 9.291489] NET: Registered protocol family 10 Jan 1 00:00:09 mark kern.info kernel: [ 9.301271] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled Jan 1 00:00:09 mark kern.info kernel: [ 9.320675] Segment Routing with IPv6 Jan 1 00:00:09 mark daemon.info NetworkManager: [9.8872] device (wlan0): set-hw-addr: set MAC address to 92:89:66:51:06:EF (scanning) Jan 1 00:00:09 mark kern.info kernel: [ 9.891675] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled Jan 1 00:00:09 mark daemon.info dbus-daemon: [system] Activating service name='fi.w1.wpa_supplicant1' requested by ':1.0' (uid=0 pid=267 comm="/usr/sbin/NetworkManager") (using servicehelper) Jan 1 00:00:09 mark daemon.info NetworkManager: [9.9390] device (lo): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external') Jan 1 00:00:09 mark daemon.info NetworkManager: [9.9444] device (lo): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external') Jan 1 00:00:09 mark daemon.info NetworkManager: [9.9511] device (lo): Activation: starting connection 'lo' (14489a2d-6709-4e4f-b28b-e924fcb0bc95) Jan 1 00:00:09 mark daemon.info NetworkManager: [9.9519] device (lo): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external') Jan 1 00:00:09 mark daemon.info NetworkManager: [9.9545] device (lo): state change: prepare -> config (reason 'none', sys-iface-state: 'external') Jan 1 00:00:09 mark daemon.info NetworkManager: [9.9566] device (lo): state change: config -> ip-config (reason 'none', sys-iface-state: 'external') Jan 1 00:00:09 mark daemon.info NetworkManager: [9.9587] device (lo): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external') Jan 1 00:00:09 mark daemon.info NetworkManager: [9.9766] device (lo): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external') Jan 1 00:00:09 mark daemon.info NetworkManager: [9.9784] device (lo): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external') Jan 1 00:00:09 mark daemon.info NetworkManager: [9.9833] device (lo): Activation: successful, device activated. Jan 1 00:00:10 mark daemon.info dbus-daemon: [system] Successfully activated service 'fi.w1.wpa_supplicant1' Jan 1 00:00:10 mark daemon.info NetworkManager: [10.4979] device (wlan0): supplicant interface state: internal-starting -> disconnected Jan 1 00:00:10 mark daemon.info NetworkManager: [10.4987] Wi-Fi P2P device controlled by interface wlan0 created Jan 1 00:00:10 mark daemon.info NetworkManager: [10.5021] manager: (p2p-dev-wlan0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/4) Jan 1 00:00:10 mark daemon.info NetworkManager: [10.5043] device (p2p-dev-wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Jan 1 00:00:10 mark daemon.info NetworkManager: [10.5083] device (wlan0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed') Jan 1 00:00:10 mark daemon.info NetworkManager: [10.5159] device (p2p-dev-wlan0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed') Jan 1 00:00:10 mark auth.info sshd: Server listening on 0.0.0.0 port 22. Jan 1 00:00:10 mark auth.info sshd: Server listening on :: port 22. Jan 1 00:00:13 mark daemon.info : starting pid 484, tty '/dev/console': '/sbin/getty -L console 0 vt100 ' Jan 1 00:00:13 mark daemon.info : starting pid 485, tty '/dev/tty1': '-/bin/sh' Jan 1 00:00:15 mark daemon.info NetworkManager: [15.1762] manager: startup complete Instead, when it works fine, after the startup complete it goes ahead with: Jan 1 00:00:20 mark daemon.info NetworkManager: [20.9056] policy: auto-activating connection 'mark' (0f285419-2238-4b94-ad48-577a1a5f3765) Jan 1 00:00:20 mark daemon.info NetworkManager: [20.9093] device (wlan0): Activation: starting connection 'mark' (0f285419-2238-4b94-ad48-577a1a5f3765) Jan 1 00:00:20 mark daemon.info NetworkManager: [20.9100] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Jan 1 00:00:20 mark daemon.info NetworkManager: [20.9124] manager: NetworkManager state is now CONNECTING Jan ... Is there something wrong in my connection file?