New answers tagged

-1

I found most effective sudo usb-creator-gtk Your question: sync does no do the magic, it just flushes the buffers. As mentioned by GAD3R cp <file> <device> is equivalent to dd.


0

You aren't passing any bootargs to the kernel, and since you're bypassing the logic to have a regular Linux distribution provide that for you, you need to pass in something that says where the console is, to Linux, so it will print out messages, as well as your root device.


0

The short answer is no. but the barebox community is working on it to bring barebox to cortex m devices too. I suggest you to use u-boot for now because it supports many cortex m socs (m3, m4 and m7). you can easily port barebox for any cortex m mcu. you can use u-boot drivers to port them to barebox. you must have a deep knowledge about linux/u-boot driver ...


0

I solved it. The right command is: fs0:> Kubuntu.efi root=/dev/nvme0n1p5 The solution found in: Linux-kernel ---> ~/Documentation/admin-guide/efi-stub.rst Thank you very much for your help.


0

One way would be to add the boot options to the UEFI boot variables in NVRAM, using the -@ option of the efibootmgr command: echo "root=/dev/nvme0n1pX" | efibootmgr -c -d /dev/nvme0n1 -L "Kubuntu with kernel UEFI stub" -l \\EFI\\ubuntu.efi -@ - ... where /dev/nvme0n1pX is the NVME device partition containing your actual root filesystem, ...


0

Well like I said before, I tried to delete the kde neon boot option and his partition and redownload the file, reflash my usb drive and reinstall it and it worked, i think it was because of corrupted file so they were bugs but all is fix now !


Top 50 recent answers are included