PDA

View Full Version : mmcblk1p1



EnoSat
16-07-23, 18:21
1, I noticed this listing in debug when installing 6.4


Freeing unused kernel image (initmem) memory: 2048K
Run /sbin/init as init process
mmc0: error -84 whilst initialising SDIO card

INIT: version 3.04 booting

Starting fake hwclock: loading system time.
Fri Jun 30 22:57:36 UTC 2023
FAT-fs (mmcblk1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
BusyBox v1.36.0 () multi-call binary.

The receiver probably doesn't mind, because it starts up normally. But I would still like to know if this error can be fixed.

2, At startup, I also noticed a probably incorrect interpolation of the grep command, will be displayed 8 times in a row
[CODE]
Usage: grep [-HhnlLoqvsrRiwFE] [-m N] [-A|B|C N] { PATTERN | -e PATTERN... | -f FILE... } [FILE]...

Search for PATTERN in FILEs (or stdin)

-HAdd 'filename:' prefix
-hDo not add 'filename:' prefix
-nAdd 'line_no:' prefix
-lShow only names of files that match
-LShow only names of files that don't match
-cShow only count of matching lines
-oShow only the matching part of line
-qQuiet. Return 0 if PATTERN is found, 1 otherwise
-vSelect non-matching lines
-sSuppress open and read errors
-rRecurse
-RRecurse and dereference symlinks
-iIgnore case
-wMatch whole words only
-xMatch whole lines only
-FPATTERN is a literal (not regexp)
-EPATTERN is an extended regexp
-m NMatch up to N times per file
-A NPrint N lines of trailing context
-B NPrint N lines of leading context
-C NSame as '-A N -B N'
-e PTRNPattern to match
-f FILERead pattern from file
BusyBox v1.36.0 () multi-call binary.
[CODE]

3, Is it possible to use the new FW (https://github.com/availink/dvb-frontends-availink/releases) 1.8.29209 for av6261 instead of the old 1.8.27679 ?

twol
16-07-23, 19:58
1, I noticed this listing in debug when installing 6.4


Freeing unused kernel image (initmem) memory: 2048K
Run /sbin/init as init process
mmc0: error -84 whilst initialising SDIO card

INIT: version 3.04 booting

Starting fake hwclock: loading system time.
Fri Jun 30 22:57:36 UTC 2023
FAT-fs (mmcblk1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
BusyBox v1.36.0 () multi-call binary.

The receiver probably doesn't mind, because it starts up normally. But I would still like to know if this error can be fixed.

2, At startup, I also noticed a probably incorrect interpolation of the grep command, will be displayed 8 times in a row
[CODE]
Usage: grep [-HhnlLoqvsrRiwFE] [-m N] [-A|B|C N] { PATTERN | -e PATTERN... | -f FILE... } [FILE]...

Search for PATTERN in FILEs (or stdin)

-HAdd 'filename:' prefix
-hDo not add 'filename:' prefix
-nAdd 'line_no:' prefix
-lShow only names of files that match
-LShow only names of files that don't match
-cShow only count of matching lines
-oShow only the matching part of line
-qQuiet. Return 0 if PATTERN is found, 1 otherwise
-vSelect non-matching lines
-sSuppress open and read errors
-rRecurse
-RRecurse and dereference symlinks
-iIgnore case
-wMatch whole words only
-xMatch whole lines only
-FPATTERN is a literal (not regexp)
-EPATTERN is an extended regexp
-m NMatch up to N times per file
-A NPrint N lines of trailing context
-B NPrint N lines of leading context
-C NSame as '-A N -B N'
-e PTRNPattern to match
-f FILERead pattern from file
BusyBox v1.36.0 () multi-call binary.
[CODE]

3, Is it possible to use the new FW (https://github.com/availink/dvb-frontends-availink/releases) 1.8.29209 for av6261 instead of the old 1.8.27679 ?

I think mmcblk1p1 is the boot volume, so I would leave it alone - you often see this type of message with the eMMC Partitions.
Regarding firmware, it may depend on the kernel and other manufacturer provided interfces, so again if they have not provided an update to the OE-A then I would leave.
Have you seen an issue with the tuners?

EnoSat
16-07-23, 20:03
New firmware tested on these DVB-S2X (http://enosat.euweb.cz/DVB-S2X.html) transponders

twol
16-07-23, 20:05
New firmware tested on these DVB-S2X (http://enosat.euweb.cz/DVB-S2X.html) transponders

"……… and did it make any difference?

birdman
17-07-23, 01:22
1, I noticed this listing in debug when installing 6.4


Freeing unused kernel image (initmem) memory: 2048K
Run /sbin/init as init process
mmc0: error -84 whilst initialising SDIO cardError code 84 is "Illegal byte sequence".
so it's not impossible that it is related to:


FAT-fs (mmcblk1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.