Can't boot after changing swappiness to 512

[Dominik]

Hi,

 

so without knowing what the swappiness actually is I changed the value from 100 to 512.

Since then, I can't boot my Banana Pi M2 Zero.

Shortly after that, I remembered again: swappiness is the percentage of how often to use swap and not the maximum amount of storage.

 

Can I repair it inside uboot?

Can I plug the sd card into my PC and edit the files there?

 

Here is the log from the serial console. It's stuck forever after the last line.

 

..............................................................
U-Boot SPL 2020.10-armbian (Nov 23 2020 - 15:48:18 +0100)
DRAM: 512 MiB
Trying to boot from MMC1


U-Boot 2020.10-armbian (Nov 23 2020 - 15:48:18 +0100) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: Banana Pi BPI-M2-Zero
DRAM:  512 MiB
MMC:   mmc@1c0f000: 0, mmc@1c10000: 1
Loading Environment from FAT... Unable to use mmc 0:1... In:    serial@1c28000
Out:   serial@1c28000
Err:   serial@1c28000
Net:   No ethernet found.
starting USB...
No working controllers found
Autoboot in 1 seconds, press <Space> to stop
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3967 bytes read in 4 ms (967.8 KiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
262 bytes read in 3 ms (85 KiB/s)
11504321 bytes read in 963 ms (11.4 MiB/s)
7793968 bytes read in 652 ms (11.4 MiB/s)
Found mainline kernel configuration
33363 bytes read in 12 ms (2.7 MiB/s)
788 bytes read in 11 ms (69.3 KiB/s)
Applying kernel provided DT overlay sun8i-h3-spi-spidev.dtbo
502 bytes read in 10 ms (48.8 KiB/s)
Applying kernel provided DT overlay sun8i-h3-uart1.dtbo
502 bytes read in 11 ms (43.9 KiB/s)
Applying kernel provided DT overlay sun8i-h3-uart3.dtbo
4185 bytes read in 11 ms (371.1 KiB/s)
Applying kernel provided DT fixup script (sun8i-h3-fixup.scr)
## Executing script at 45000000
## Loading init Ramdisk from Legacy Image at 43300000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    11504257 Bytes = 11 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 43000000
   Booting using the fdt blob at 0x43000000
   Loading Ramdisk to 49507000, end 49fffa81 ... OK
   Loading Device Tree to 49496000, end 49506fff ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

 

Thanks

Board: Not on the list

[SteeMan]

Moved post to Allwinner unmaintained forum as this board is not supported.

[CryBaby]

2 hours ago, Dominik said:

Can I plug the sd card into my PC and edit the files there?

This will be the easiest approach, provided you have linux on your PC. If you don't then you could make another working sd card, boot your SBC with that and plug in the broken one using an adapter. Then you mount the broken card and undo whatever you did to break it.

 

None of this is specific to a particular board.

[Dominik]

On 7/22/2022 at 11:28 PM, CryBaby said:

This will be the easiest approach, provided you have linux on your PC. If you don't then you could make another working sd card, boot your SBC with that and plug in the broken one using an adapter. Then you mount the broken card and undo whatever you did to break it.

 

None of this is specific to a particular board.

Thanks. I installed a Linux VM and changed the file. It still doesn't work. 

So either something else is the problem (I probably messed something else up) or the original file is on the emmc which I can't access?

Anyways, I'm backing up my files and reinstalling armbian.