I'm trying to flash my DZ60RGB V2 keyboard on Arch Linux. I installed qmk package setup qmk_toolbox using qmk setup command. In the process it warned me about missing udev rules which I added when setting up ⚠ Missing or outdated udev rules for 'atmel-dfu' boards. Run 'sudo cp /home/s1n7ax/qmk_firmware/util/udev/50-qmk.rules /etc/udev/rules.d/'. ⚠ Missing or outdated udev rules for 'kiibohd' boards. Run 'sudo cp /home/s1n7ax/qmk_firmware/util/udev/50-qmk.rules /etc/udev/rules.d/'. ⚠ Missing or outdated udev rules for 'stm32' boards. Run 'sudo cp /home/s1n7ax/qmk_firmware/util/udev/50-qmk.rules /etc/udev/rules.d/'. ⚠ Missing or outdated udev rules for 'bootloadhid' boards. Run 'sudo cp /home/s1n7ax/qmk_firmware/util/udev/50-qmk.rules /etc/udev/rules.d/'. ⚠ Missing or outdated udev rules for 'usbasploader' boards. Run 'sudo cp /home/s1n7ax/qmk_firmware/util/udev/50-qmk.rules /etc/udev/rules.d/'. ⚠ Missing or outdated udev rules for 'massdrop' boards. Run 'sudo cp /home/s1n7ax/qmk_firmware/util/udev/50-qmk.rules /etc/udev/rules.d/'. ⚠ Missing or outdated udev rules for 'caterina' boards. Run 'sudo cp /home/s1n7ax/qmk_firmware/util/udev/50-qmk.rules /etc/udev/rules.d/'. After that compiled default keymap successfully and flashed while in the Bootloader mode. $ qmk compile -kb dztech/dz60rgb/v2 -km default $ qmk flash -kb dztech/dz60rgb/v2 -km default QMK Firmware 0.13.34 Making dztech/dz60rgb/v2 with keymap default and target flash avr-gcc (GCC) 11.2.0 Copyright (C) 2021 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Size before: text data bss dec hex filename 0 26626 0 26626 6802 .build/dztech_dz60rgb_v2_default.hex Copying dztech_dz60rgb_v2_default.hex to qmk_firmware folder [OK] Checking file size of dztech_dz60rgb_v2_default.hex [OK] * The firmware size is fine - 26626/28672 (92%, 2046 bytes free) Bootloader not found. Trying again every 0.5s (Ctrl+C to cancel).....^Cmake[1] : *** [tmk_core/avr.mk:331: flash] Interrupt I also tried to erase through dfu-programmer which failed again. $ dfu-programmer atmega32u4 erase dfu-programmer: no device present. I tried using sudo but the result was the same. I tried the same thing on Ubuntu 21.04 which result in the same error. How ever via identifies the keyboard as DZ60RGB V2 and I can make key changes fine. Edit: lsusb identifies the keyboard as followr Bus 001 Device 010: ID 445a:1121 DZTECH DZ60RGB When it is connected in Bootloader mode, the device is is shown as follows. Bus 001 Device 011: ID 03eb:2045 Atmel Corp. LUFA Mass Storage Demo Application

I've installed Debian Buster on a "ReadyNAS 102" via u-boot / serial console. I was following this tutorial . But, replaced used different links to download current the Debian installer and Device Tree Blob: * http://ftp.debian.org/debian/dists/buster/main/installer-armhf/current/images/device-tree/armada-370-netgear-rn102.dtb * http://ftp.debian.org/debian/dists/buster/main/installer-armhf/current/images/netboot/initrd.gz * http://ftp.debian.org/debian/dists/buster/main/installer-armhf/current/images/netboot/vmlinuz Installation worked fine, except for the installation of grub (which is known to fail according to the tutorial). Instead you've to manually install/configure the flash-kernel package. I also had to manually call "mtdpart" to create the uImage and minirootfs partitions to finally be able to successfully run "update-initramfs": # mtdpart add /dev/mtd0 uImage 0x200000 0x600000 # mtdpart add /dev/mtd0 minirootfs 0x800000 0x1000000 # update-initramfs -u So far so good. I got the kernel booting, but after booting I've some preconfigured "mtd partitions", which seem to originate from the kernel device tree: ~# cat /proc/mtd dev: size erasesize name mtd0: 00180000 00020000 "u-boot" mtd1: 00020000 00020000 "u-boot-env" mtd2: 00600000 00020000 "uImage" mtd3: 00400000 00020000 "minirootfs" mtd4: 07400000 00020000 "ubifs" The problem with this is: "minirootfs" is too small (only 4 MB) for the generated initramfs: # update-initramfs -u -k 4.19.0-6-armmp update-initramfs: Generating /boot/initrd.img-4.19.0-6-armmp Using DTB: armada-370-netgear-rn102.dtb Installing /usr/lib/linux-image-4.19.0-6-armmp/armada-370-netgear-rn102.dtb into /boot/dtbs/4.19.0-6-armmp/./armada-370-netgear-rn102.dtb Taking backup of armada-370-netgear-rn102.dtb. Installing new armada-370-netgear-rn102.dtb. Installing /usr/lib/linux-image-4.19.0-6-armmp/armada-370-netgear-rn102.dtb into /boot/dtbs/4.19.0-6-armmp/./armada-370-netgear-rn102.dtb Taking backup of armada-370-netgear-rn102.dtb. Installing new armada-370-netgear-rn102.dtb. flash-kernel: installing version 4.19.0-6-armmp The initial ramdisk is too large. This is often due to the unnecessary inclusion of all kernel modules in the image. To fix this set MODULES=dep in one or both /etc/initramfs-tools/conf.d/driver-policy (if it exists) and /etc/initramfs-tools/initramfs.conf and then run 'update-initramfs -u -k 4.19.0-6-armmp' Not enough space for initrd in MTD 'minirootfs' (need 4971360 but is actually 4194304). run-parts: /etc/initramfs/post-update.d//flash-kernel exited with return code 1 The new /dev/mtd0 to /dev/mtd4 devices can not be removed, edited or recreated by mtdpart. I also tried to set the mtdparts kernel parameter (which needs to be 'cmdlinepart.mtdparts' due to a bug in buster; I've tried 'mtdparts=' too): # cat /proc/cmdline console=ttyS0,115200 cmdlinepart.mtdparts=armada-nand:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),(uImage),0x1000000@0x800000(minirootfs),-(ubi) The mtd partitions seem to be defined in the *.dtb file that comes with the kernel: The following message appears in "dmesg" speaking about "5 fixed-partions". [ 18.310935] 5 fixed-partitions partitions found on MTD device pxa3xx_nand-0 [ 18.318030] Creating 5 MTD partitions on "pxa3xx_nand-0": root@ReadyNAS102:~# dmesg | grep 'MTD' -A 3 [ 18.310935] 5 fixed-partitions partitions found on MTD device pxa3xx_nand-0 [ 18.318030] Creating 5 MTD partitions on "pxa3xx_nand-0": (...some other lines...) [ 18.443214] 0x000000000000-0x000000180000 : "u-boot" [ 18.497255] 0x000000180000-0x0000001a0000 : "u-boot-env" [ 18.543756] 0x000000200000-0x000000800000 : "uImage" [ 18.601234] 0x000000800000-0x000000c00000 : "minirootfs" [ 18.661169] 0x000000c00000-0x000008000000 : "ubifs" I tried to edit the *.dtb file that comes with the kernel (/boot/dtbs/4.19.0-6-armmp/armada-370-netgear-rn102.dts) by using the dtc tool: # dtc -I dtb -O dts armada-370-netgear-rn102.dtb > armada-370-netgear-rn102.dts # editing the *.dts file # dtc -I dts -O dtb armada-370-netgear-rn102.dts > armada-370-netgear-rn102.dtb I changed the *.dts file as following: nand-controller@d0000 { compatible = "marvell,armada370-nand-controller"; reg = ; #address-cells = ; #size-cells = ; interrupts = ; clocks = ; status = "okay"; nand@0 { reg = ; label = "pxa3xx_nand-0"; nand-rb = ; marvell,nand-keep-config; nand-on-flash-bbt; nand-ecc-strength = ; nand-ecc-step-size = ; partitions { compatible = "fixed-partitions"; #address-cells = ; #size-cells = ; partition@0 { label = "u-boot"; reg = ; read-only; }; partition@180000 { label = "u-boot-env"; reg = ; read-only; }; partition@200000 { label = "uImage"; reg = ; }; partition@800000 { label = "minirootfs"; reg = ; }; partition@c00000 { label = "ubifs"; reg = ; }; }; }; }; Especially, I changed "reg = ;" to "reg = ;" for partition@800000: partition@800000 { label = "minirootfs"; reg = ; }; There's enough space before the "ubifs" partition and I don't use it anyways. But, after a reboot the kernel still tells me about the old settings. How can I fix that? I could probably manually install "vmlinuz + *.dtb" to the NAND via uboot. But, that would be gone as soon as the next kernel update is installed. I would prefer the kernel to interpret the "mtdparts" command line parameter. Any ideas? EDIT #1: --- I now (ab)use the partition "ubifs" instead of "minirootfs" for the initramfs. This works, but I would like to know if there is a more clean solution. Of course, I also had to change my "bootcmd" at u-boot to load/use data from this partition instead: setenv bootcmd 'nand read 0x2000000 0x200000 0x600000; nand read 0x3000000 0xc00000 0x800000; bootm 0x2000000 0x3000000' saveenv reset

linux newbie here. I'm currently working on google coral SOM with baseboard. (mendal linux) i made some programs for the my job, and I want to put my programs, bash files and setup to other board as well, so the board are ready to be deployed in one single install. my baseboard allow boot from SD card. option 1: install default mendel OS (using coral start guide), and apply my custom setup, and put my program files. its very tedious since my custom board does not fully support what regular dev board does and it stops booting, so I need to do extra work in order to make it successfully installed. and of course I need to setup, and transfer my files. option 2: copy current board's os image with dd, and use program like balenaEtcher to flash to SD card. and from the other board, boot from SD card to install. this is what i tried to do, but it does not work. os install just don't seem to proceed. is there a way to do it?

After 9 years of use, this 4GB SATADOM finally broke and wiped itself to the extent that the underlying Linux partitions are no longer visible. While the device will show up as /dev/sdb, even testdisk cannot detect partitions. When choosing an Intel/PC partition, I get the errors: Partition sector doesn't have the endmark 0xAA55 When choosing EFI partition, I get the error: Bad GPT partition, invalid signature. Trying alternate GPT Bad GPT partition, invalid signature. Is there a way to recover any of the files, or preferably even mount it properly after fixing the superblock issues? Ideally I would like to extract a PostgreSQL databse. At the moment I made a backup with ddrescue, which detected 0 read errors, curiously enough. MTBF: 4 million hours Flash endurance: 100,000 program-erase cycles I suspect the flash endurance has perhaps been compromised - the warranty is curiously only for 5 years.

I have a file.img file which was obtained by running dd if=/dev/sda of=file.img. This was done on a device with two partitions, /dev/sda1 and /dev/sda2. In order to flash a new device with the same image, I'm booting an Alpine Linux using network boot, copy the file.img from the network and run the dd if=file.img of=/dev/sda. This is competed successfully and if I reboot, the device boots up properly. The issue is that I want to add some files to the new device. Naturally, I thought I'll just mount the /dev/sda2 (that's the device I want to add stuff to) and add stuff there. Well, not that simple: /dev/sda2 is missing - sometimes. After the dd command runs, sometimes - without a pattern observed - the partitions are missing. Checking the disk using fdisk -l /dev/sda shows both partitions there. Running partprobe /dev/sda; dmesg always shows (dmesg command outputs this) sda: sda1 sda2 so the partitions are there and they're being recognized. Still, they don't appear under /dev/. The funny part is that running partprobe /dev/sda sometimes fixes the issue, other times it doesn't. With all this madness, rebooting the device will ALWAYS boot correctly. If anyone has any idea what I could try, I'd greatly appreciate the ideas. Thank you. P.S.: I also tried to run partx -uv /dev/sda. That tells me:

partition: none  disk: /dev/sda, lower: 0, upper: 0
/dev/sda: partition table type 'dos' detected
/dev/sda: partition #1 added
/dev/sda: partition #2 added

But the partitions still can't be found under /dev/sdaX

Is there a Linux command that makes the screen blink for a fraction of a second? Possibly on all virtual desktops? I would use it to get a visual feedback to signal the end of a build, something like: $ make; blink I already tried with the beep command, to get an audio feedback, but on my system it produces no sound.

I am having difficulty logging into my Linux Lite desktop, because it randomly decided to enforce a password. To fix this issue, I created a bootable USB. My first attempt was to access the BIOS and set USB as the highest priority. While, I can access the main menu, I can't move the cursor around or see any effect as I press enter. 2nd attempt was to access the command line and set the root to the USB. Unfortunately, I am unable to figure out which (...) To use for the root. Yes, I already tried (hd0,gpt1) and (hd0,gpt2). I also unplugged it to see if it vanishes. That did not work, either. How may I find the right command to finally boot from the flash stick?

I have a Smartbuy 16Gb USB 2.0 flash drive (whith new memory controler) that is not recognized in any Linux system, but on Windows it recognized and worked fine. When I connect it to the PC on Linux system, nothing happens. In dmesg appears this lines: [ 2454.940289] usb 2-1.3: new high-speed USB device number 9 using ehci-pci [ 2455.051632] usb 2-1.3: New USB device found, idVendor=13fe, idProduct=4300 [ 2455.051636] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 2455.051639] usb 2-1.3: Product: USB DISK 2.0 [ 2455.051641] usb 2-1.3: Manufacturer: [ 2455.051643] usb 2-1.3: SerialNumber: 9000883E242B3934 [ 2455.051971] usb-storage 2-1.3:1.0: USB Mass Storage device detected [ 2455.052148] scsi host4: usb-storage 2-1.3:1.0 [ 2456.640210] usb 2-1.3: reset high-speed USB device number 9 using ehci-pci [ 2456.844280] usb 2-1.3: reset high-speed USB device number 9 using ehci-pci [ 2457.048278] usb 2-1.3: reset high-speed USB device number 9 using ehci-pci [ 2457.252279] usb 2-1.3: reset high-speed USB device number 9 using ehci-pci In lsusb: Bus 002 Device 007: ID 13fe:4300 Kingston Technology Company Inc. fdisk -l and parted -l not return recognizing the USB device or partitions. This solution: https://superuser.com/a/1107319 and reformat on Windows to fat32, didn't work.

I have this IP camera that I bought that's really pretty shady (it streams all the videos to some S3 bucket and forces me to use their software), but I'm pretty sure it runs embedded linux and I'm hoping I can just reinstall a fresh build. I'm a heavy linux user but I'm totally new to this level of modding. To start, the camera has a Ingenic T31 chip, which appears to be a MIPS processor. You can see from this photo there is some other chip below it, but it doesn't have any labels or anything. It's right next to the wireless antenna so make that's the radio controller? Second, in the attached board, there are 4 holes that look like they might be fit for a USB adaptor. I have seen people solder ports into those, but I'm not sure if there is a way to connect without solder. (I'm terrible with solder). Finally, there is also a micro SD card slot on the reverse side of that second board. Aside from figuring out HOW to flash it, I also need to find the correct build of linux to install and run the camera. I'm planning to use this with HomeAssistant. I know there is probably a lot of info out there I can find on my own, but maybe I'm not searching for the right buzzwords. I'd be happy just to be pointed in the right direction.

Many gui tools such as rufus use up the entire drive when flashing an iso. I have a 64gb usb and flashing a single linux installer iso less than 4gb feels like a waste of space. Are there any packages/commands that can create dualbootable usbs?

A couple of weeks ago I bought a "2Tb" thumb drive of uncertain origin, with the intention of using this as intermediate storage when rebuilding a system (three releases forwards of Debian). Can anybody suggest an efficient way of verifying the actual size of this, i.e. that it actually has "2Tb" of Flash rather than a single "500Mb" device repeating in the storage space? I'd like to emphasise that I am fully aware of the liberties that manufacturers have long taken when stating capacities, and that my "2Tb" drive will be likely to have a maximum real capacity of something like 1.75Tib. It was originally formatted with unpartitioned exFAT, and while my usual test program would write more than 1Tb of test data to it it invariably glitched at some random point before getting to the read pass which would verify that the block numbers were actually retained. While that could point to flakiness in the drive's microcontroller, the problem might equally be in the comparatively new exFAT support on Linux. I am able to use gparted to partition and reformat as ext4 or ext2 without error. Tring to manually run mke2fs with -cc options for a r/w block test is taking about 80 hours per 1% of the drive. In addition, I've not seen explicit verification that it has the two separate passes which would be needed to verify size unambiguously. I've not yet tried running my own test program, which I trust on smaller media (10s of Gb scale) on this device formatted as ext2. In cases where my test program was being applied to a block device rather than to a file, I could possibly improve efficiency by adding a --sparse option which only wrote the block number in e.g. a 4K block. This probably wouldn't help if the target was a test file, since (a) the OS might not allocate space for unwritten areas in sparse files and (b) there would be so many layers of translation involved that it would be virtually impossibly to hit the Flash device block boundaries. Any suggestions would be appreciated.

Actually i am working with NOR flash. I am getting confused about block read and write from NOR flash. - From my understand block read and write means writing and reading complete sector of the flash. Is it correct? Please anyone help to clarify my doubt.

I have tried to follow the steps recommended in https://linuxconfig.org/enable-adobe-flash-for-firefox-on-ubuntu-20-04-focal-fossa-linux But when I enter **sudo apt install flashplugin-installer** into my shell, it tells me **the package flushplugin-installer could not be found**. REMARK: I know flash is an old software virtually no one uses anymore, but I need it in order to view content embedded in newspaper articles that were published ten years ago.

I've been searching for many days now and I still cannot get flash on Opera Browser for my Linux Debian 10 Chromebook. Can someone please help me? I've tried methods with Terminal but most of the methods I've used are outdated due to flash player site being 'End Of Life' no longer letting me download plugins!

since the end of flash we are unable to run flash content in any of our computers not even in web browsers, is there a way to keep running flash content on linux web browsers such as chrome, chrommium or firefox?

I am software engineer with no embedded development experience and have been handed a board (Qualcomm® Snapdragon™) with 1: an image (Automotive Grade Linux: Halibut release) 2: flashing instructions I need to flash a new image to the board However, I am having great difficulty trying to figure out how to get this to work. The instructions I have (which are not from Qualcomm) say that DIP switches 1&2 must be turned on in order to flash. When I turn DIP switches 1&2 on, the board does not boot an OS, but QFIL does NOT detect it like it is supposed to: By contrast, when DIP switches 1&2 are OFF, the board DOES boot the OS, but QFIL detects the device as it is NOT supposed to do.: Do I have bad hardware or am I missing something?

I am using a Linux-based switch and it has created many logs due to some known bugs. The problem is that the log files even exceed the physical flash size. I would like to ask what happened to the flash in this state? I tried to download the log file to the windows platform and read it. The actual size and content are normal. The typical content is as follows：

Jan  3 00:00:02 SWITCH : mac-address 000e.c6c1.3a03 vid 1 move from interface eth0/7 to interface eth0/5
Jan  3 00:00:02 SWITCH : mac-address 000e.c6c1.3a03 vid 1 move from interface eth0/5 to interface eth0/7
Jan  3 00:00:02 SWITCH : mac-address 000e.c6c1.3a03 vid 1 move from interface eth0/7 to interface eth0/5
Jan  3 00:00:03 SWITCH : mac-address 000e.c6c1.3a03 vid 1 move from interface eth0/5 to interface eth0/7
Jan  3 00:00:03 SWITCH : mac-address 000e.c6c1.3a03 vid 1 move from interface eth0/7 to interface eth0/5

more ops below:

root@SWITCH:/var/log# pwd
/var/log
root@SWITCH:/var/log# ls -lh
total 1.3G
-rw-r----- 1 root adm  265M Jan  1 03:17 all
-rw-r----- 1 root adm  367M Jan  3  1970 all.1
-rw-r--r-- 1 root root    0 Mar 27  2019 btmp
-rw-r--r-- 1 root root  292 Jan  1 00:15 lastlog
-rw-r----- 1 root adm  263M Jan  1 03:13 syslog
-rw-r----- 1 root adm  364M Jan  3  1970 syslog.1
-rw-r--r-- 1 root root  19K Jan  1 00:15 wtmp
...
root@SWITCH:/var/log# du -h *
265M    all
367M    all.1
0       btmp
4.0K    lastlog
263M    syslog
364M    syslog.1
20K     wtmp
...
root@SWITCH:/var/log# df -h
Filesystem      Size  Used Avail Use% Mounted on
rootfs          215M  214M   28K 100% /
ubi0:rootfs     215M  214M   28K 100% /
devtmpfs        124M     0  124M   0% /dev
tmpfs            25M   96K   25M   1% /run
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs            50M  4.0K   50M   1% /run/shm
tmpfs           124M     0  124M   0% /tmp
ubi2:data        12M   44K   12M   1% /data
root@SWITCH:/var/log# mount
ubi0:rootfs on / type ubifs (rw,relatime)
devtmpfs on /dev type devtmpfs (rw,relatime,size=126736k,nr_inodes=31684,mode=755)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=25368k,mode=755)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=50720k)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620)
tmpfs on /tmp type tmpfs (rw,nosuid,noexec,relatime)
ubi2:data on /data type ubifs (rw,relatime)

Linux SWITCH 3.10.70 #1 SMP Fri Jul 10 03:00:57 UTC 2020 armv7l GNU/Linux
rroot@SWITCH:/var/log# ls -lshiA
total 1.3G
9504  29M -rw-r----- 1 root root  29M Jan  1 00:39 .all.swp
9438 265M -rw-r----- 1 root adm  265M Jan  1 08:17 all
9406 367M -rw-r----- 1 root adm  367M Jan  3  1970 all.1
 902    0 -rw-r--r-- 1 root root    0 Mar 27  2019 btmp
9422 4.0K -rw-r--r-- 1 root root  292 Jan  1 00:15 lastlog
9439 263M -rw-r----- 1 root adm  263M Jan  1 03:13 syslog
9407 364M -rw-r----- 1 root adm  364M Jan  3  1970 syslog.1
 901  20K -rw-r--r-- 1 root root  19K Jan  1 00:15 wtmp

I am very confused, hope to find some help here, thanks!

I have switched to Emacs as my editor and when using multiple windows in the terminal I want the cursor to flash in the current window. I have run the (blink-cursor-mode t) command and nothing happens. I have also tried a few commands to get the cursor to flash in the terminal and nothing happens.

I have a DOS based HDD utility called spinrite. I want to create a bootable flash drive with the freedos OS and once created copy into the drive the executable utility. I tried using gparted to partition the drive, formated it as Fat32 and set the Boot flag. once done I cannot see how to install the OS and add the executable. I have an image file of Freedos, if I try making the flash drive with it then it's not bootable. Any help is greatly appreciated.

If for example I clear the contents of my SD card with command dd *if=/dev/zero of=/dev/sdX* , I'm guessing this completely wipes (sets to zero) every single content on the card? partitions, file system, data etc. Now what I can't understand is, when I will plug this device into a computer again afterwards, Linux or Windows, I am able to write to it again. How does the OS know what type of device this is if everything is wiped? There are different types of flash memory and I'm guessing they need specific drivers to write to them depending on what type, so how does the OS know what type? Can it be that there is a small part of the flash memory which was not overwritten which contains data explaining what type of memory it is?