Applying patch 9982 Failed

[inamiitb]

Tried to apply the 9982 patch at https://github.com/thuehn/RegMon/blob/master/RegMon/src/9982-ath9k_RegMon.patch

but that failed with the following error:

Applying ./patches/9982-ath9k_RegMon.patch using plaintext: 
patch: **** Only garbage was found in the patch input.
Patch failed!  Please fix ./patches/9982-ath9k_RegMon.patch!
Makefile:1794: recipe for target '/home/inam/lede/build_dir/target-mips_24kc_musl/linux-ar71xx_mikrotik/backports-4.14-rc2-1/.prepared_83c071a4dce6eb411f0df18e77d19c28_6664517399ebbbc92a37c5bb081b5c53' failed

I have used both methods: compiling only the package and rebuild complete LEDE. Neither patch of ath9k nor of ath5k works. Please suggest.

[denisroeper]

@inamiitb: How do you applied the patch and what are the first lines of the patch (head -n 10 patchfilename)?

[inamiitb]

Oh! I realised my mistake. I was downloading patch file directly from the link on the RegMon main page that was giving the 'garbage' in the patch input. I downloaded it from the Raw button and right now it is working. Regards Inam

[inamiitb]

I ran into another problem, though I had correctly installed patches for RegMon as well as for LuCI app. Now when I am trying to finally flash a new image, I get the following output on sysupgrade:

root@LEDE:/# sysupgrade -v /tmp/*.bin
Image metadata not found
Cannot save config while running from ramdisk.
killall: watchdog: no process killed
Commencing upgrade. All shell sessions will be closed now.
Watchdog handover: fd=3
- watchdog -
killall: telnetd: no process killed
Sending TERM to remaining processes ... dnsmasq ubusd logd netifd odhcpd ntpd 
Sending KILL to remaining processes ... ntpd 
Performing system upgrade...
Unlocking kernel ...
Erasing kernel ...

Skipping bad block at 0x0   
Skipping bad block at 0x20000   
Skipping bad block at 0x40000   
Skipping bad block at 0x60000   
Skipping bad block at 0x80000   
Skipping bad block at 0xa0000   
Skipping bad block at 0xc0000   
Skipping bad block at 0xe0000   
Skipping bad block at 0x100000   
Skipping bad block at 0x120000   
Skipping bad block at 0x140000   
Skipping bad block at 0x160000   
Skipping bad block at 0x180000   
Skipping bad block at 0x1a0000   
Skipping bad block at 0x1c0000   
Skipping bad block at 0x1e0000   
Skipping bad block at 0x200000   
Skipping bad block at 0x220000   
Skipping bad block at 0x240000   
Skipping bad block at 0x260000   
Skipping bad block at 0x280000   
Skipping bad block at 0x2a0000   
Skipping bad block at 0x2c0000   
Skipping bad block at 0x2e0000   
Skipping bad block at 0x300000   
Skipping bad block at 0x320000   
Skipping bad block at 0x340000   
Skipping bad block at 0x360000   
Skipping bad block at 0x380000   
Skipping bad block at 0x3a0000   Writing data to block 0 at offset 0x0
Bad block at 0, 1 block(s) from 0 will be skipped
Writing data to block 1 at offset 0x20000
Bad block at 20000, 1 block(s) from 20000 will be skipped
Writing data to block 2 at offset 0x40000
Bad block at 40000, 1 block(s) from 40000 will be skipped
Writing data to block 3 at offset 0x60000
Bad block at 60000, 1 block(s) from 60000 will be skipped
Writing data to block 4 at offset 0x80000
Bad block at 80000, 1 block(s) from 80000 will be skipped
Writing data to block 5 at offset 0xa0000
Bad block at a0000, 1 block(s) from a0000 will be skipped
Writing data to block 6 at offset 0xc0000
Bad block at c0000, 1 block(s) from c0000 will be skipped
Writing data to block 7 at offset 0xe0000
Bad block at e0000, 1 block(s) from e0000 will be skipped
Writing data to block 8 at offset 0x100000
Bad block at 100000, 1 block(s) from 100000 will be skipped
Writing data to block 9 at offset 0x120000
Bad block at 120000, 1 block(s) from 120000 will be skipped
Writing data to block 10 at offset 0x140000
Bad block at 140000, 1 block(s) from 140000 will be skipped
Writing data to block 11 at offset 0x160000
Bad block at 160000, 1 block(s) from 160000 will be skipped
Writing data to block 12 at offset 0x180000
Bad block at 180000, 1 block(s) from 180000 will be skipped
Writing data to block 13 at offset 0x1a0000
Bad block at 1a0000, 1 block(s) from 1a0000 will be skipped
Writing data to block 14 at offset 0x1c0000
Bad block at 1c0000, 1 block(s) from 1c0000 will be skipped
Writing data to block 15 at offset 0x1e0000
Bad block at 1e0000, 1 block(s) from 1e0000 will be skipped
Writing data to block 16 at offset 0x200000
Bad block at 200000, 1 block(s) from 200000 will be skipped
Writing data to block 17 at offset 0x220000
Bad block at 220000, 1 block(s) from 220000 will be skipped
Writing data to block 18 at offset 0x240000
Bad block at 240000, 1 block(s) from 240000 will be skipped
Writing data to block 19 at offset 0x260000
Bad block at 260000, 1 block(s) from 260000 will be skipped
Writing data to block 20 at offset 0x280000
Bad block at 280000, 1 block(s) from 280000 will be skipped
Writing data to block 21 at offset 0x2a0000
Bad block at 2a0000, 1 block(s) from 2a0000 will be skipped
Writing data to block 22 at offset 0x2c0000
Bad block at 2c0000, 1 block(s) from 2c0000 will be skipped
Writing data to block 23 at offset 0x2e0000
Bad block at 2e0000, 1 block(s) from 2e0000 will be skipped
Writing data to block 24 at offset 0x300000
Bad block at 300000, 1 block(s) from 300000 will be skipped
Writing data to block 25 at offset 0x320000
Bad block at 320000, 1 block(s) from 320000 will be skipped
Writing data to block 26 at offset 0x340000
Bad block at 340000, 1 block(s) from 340000 will be skipped
Writing data to block 27 at offset 0x360000
Bad block at 360000, 1 block(s) from 360000 will be skipped
Writing data to block 28 at offset 0x380000
Bad block at 380000, 1 block(s) from 380000 will be skipped
Writing data to block 29 at offset 0x3a0000
Bad block at 3a0000, 1 block(s) from 3a0000 will be skWriting data to block 30 at offset 0x3c0000
libmtd: error!: bad eraseblock number 30, mtd5 has 30 eraseblocks
nandwrite: error!: /dev/mtd5: MTD get bad block failed
           error 22 (Invalid argument)
tar: write error: Broken pipe
nandwrite: error!: Data was only partially written due to error
           error 22 (Invalid argument)
removing ubiblock0_1
[  169.431549] block ubiblock0_1: released
Volume ID 0, size 13 LEBs (1650688 bytes, 1.6 MiB), LEB size 126976 bytes (124.0 KiB), dynamic, name "none", alignment 1
Volume ID 1, size 31 LEBs (3936256 bytes, 3.8 MiB), LEB size 126976 bytes (124.0 KiB), dynamic, name "rootfs", alignment 1
Set volume size to 117325824
Volume ID 2, size 924 LEBs (117325824 bytes, 111.9 MiB), LEB size 126976 bytes (124.0 KiB), dynamic, name "rootfs_data", alignment 1
sysupgrade successful
umount: can't unmount /dev: Resource busy
umount: can't unmount /tmp: Resource [  174.419406] reboot: Restarting system

On rebooting, it gives the following error (kernel not found on nand):

RouterBOOT booter 3.10

RouterBoard 433AH

CPU frequency: 680 MHz
  Memory size: 128 MiB
    NAND size: 128 MiB

Press any key within 3 seconds to enter setup...

loading kernel from nand... kernel not found
trying dhcp protocol... OK
resolved mac address 1C:1B:0D:8C:E3:1E
Gateway: 192.168.6.1
transfer started .................................................. transfer ok, time=2.36s
setting up elf image... OK

and then it booots from the ethernet.

Is it that that my board is gone? Or is there a way to remove those so many bad blocks? Regards Inam

[thuehn]

As this seems to be in issue not related to Regmon itself rather than to flash a proper LEDE image ... should we close this issue ?

[inamiitb]

Yes, I also think so. I have flashed on my other board. But some idea on whether it was caused due to, say, debugfs used by Regmon? Regards.

[thuehn]

I do close this issue according to your other message that regmon is now working for you.