If you like BoxMatrix then please contribute Supportdata, Supportdata2, Firmware and/or Hardware (get in touch).
My metamonk@yahoo.com is not reachable by me since years. Please use hippie2000@webnmail.de instead.
Property:config (procfs)
| BoxMatrix >> System >> config (procfs) | @ BoxMatrix - IRC-Chat - Translate: de es fr it nl pl |
| News | Selectors | Models | Accessories | Components | Environment | Config | Commands | System | Webif | Software | Develop | Lexicon | Community | Project | Media |
| Devices | Filesystems | Partitions | Sockets | Netlink | Pipes | Interfaces | Bridges | Ports | Events | Sources | Sinks | AVMIPC | Processes | Watchdogs | Memory | Slab | Vmalloc | ProcFS | SysFS | Research |
 |
Name-Collision - multiple objects in this wiki use the name config!
|
Procfs-Object
| Procfs-Object: | config (procfs) - type Dirlink, File | Wiki | Freetz | IPPF | whmf | AVM | Web |
| Location: | System >> Proc-Filesystem - Origin: AVM | ||||||
| Path: | /proc/avm/benchmark, /proc/sys/urlader | ||||||
| Properties: | Firmware: 5.20 - 7.58 - Kernel (perm): 2.6.28.10 (rw), 2.6.39.4 (rw), 4.1.38 (l), 4.1.52 (l), 4.4.271 (l), 4.4.60 (l), 4.9.250 (rw) | ||||||
| Function: | Puma: API to blobs stored in Bootloader. MemBench: Benchmark config. | ||||||
Goto: Puma - MemBench - Dependencies - Model-Matrix - Help Supportdata2 - SMW-Browser
Details
This is an "in-section" name collision covering 2 completely different objects: - (this will be splitted one day)
Puma
config is an API to blobs stored in the Bootloader on Puma models, located at /proc/sys/urlader/config.
It is enabled if CONFIG_ARCH_PUMA5, CONFIG_MACH_PUMA6 or CONFIG_ARCH_GEN3 is enabled.
When reading from it it lists all blobs which are stored. 6490 fw 7.29 example:
# cat /proc/sys/urlader/config WLAN DECT WLAN2 ZERTIFIKATE DOCSIS
Writing the name of the blob and a destination filename to it makes it copy the blob:
Inspired by docsiscertdefaults of a 6490 fw 7.29:
# echo ZERTIFIKATE /var/tmp/urladercerts.tar.gz > /proc/sys/urlader/config # gunzip -d < /var/tmp/urladercerts.tar.gz | tar tv -rw-rw-r-- 0/0 635 2016-04-15 15:20:02 cm_key_prv.bin -rw-rw-r-- 0/0 775 2016-04-15 15:20:02 cm_cert.cer -rw-r----- 0/0 1013 2016-04-15 14:56:17 mfg_cert.cer -rw-r----- 0/0 294 2016-04-15 14:56:17 mfg_key_pub.bin
Let's peek DOCSIS the same way:
# echo DOCSIS /var/tmp/docsis.tar.gz > /proc/sys/urlader/config # gunzip -d < /var/tmp/docsis.tar.gz | tar tv drwxr-xr-x root/root 0 1970-01-01 01:01:58 DownstreamCal/ -rwxr-xr-x root/root 592 1970-01-01 01:01:58 DownstreamCal/MxL267 drwxr-xr-x root/root 0 1970-01-01 01:02:02 UpstreamCal/ -rwxr-xr-x root/root 242 1970-01-01 01:02:03 UpstreamCal/usNewFreqTableFile -rwxr-xr-x root/root 386 1970-01-01 01:02:03 UpstreamCal/usTablesFile -rwxr-xr-x root/root 12 1970-01-01 01:02:03 UpstreamCal/usParametersFile
Extracting WLAN, DECT and WLAN2 work the same way but they are plain binary calibration data.
MemBench
config is the configuration folder of the MemBench Benchmark suite.
It is a symlink located at /proc/avm/benchmark/config which points into the sysfs. 7530 fw 7.39 example:
root@fritz0:/var/mod/root# ls -l /proc/avm/benchmark/config lrwxrwxrwx 1 root root 31 Jan 1 17:40 /proc/avm/benchmark/config -> /sys/kernel/debug/avm-membench/ root@fritz0:/var/mod/root# ls -l /sys/kernel/debug/avm-membench/ -r--r--r-- 1 root root 0 Jan 1 01:00 counter -rw------- 1 root root 0 Jan 1 01:00 loops -rw------- 1 root root 0 Jan 1 01:00 membench_bus_clock -rw------- 1 root root 0 Jan 1 01:00 membench_cpu_clock -rw------- 1 root root 0 Jan 1 01:00 mess_laenge
Most values are hexadecimal:
file value decimal comment ----------------------------------------------------------------------------------- counter 0x2da47da06c5c 50184505551964 Result loops 1 1 Measure-Time Loops membench_bus_clock 0x40164000 1075200000 RAM-Clock membench_cpu_clock 0x2a51bd80 710000000 CPU-Clock mess_laenge 0x000000002a51bd80 710000000 Measure-Time CPU cycles
This is the Benchmark which has been run before:
root@fritz0:/var/mod/root# cat /proc/avm/benchmark/do_read_pipe
AVM-RAM-Benchmark
=============================================
IRQs: off (alle Tests mit deaktivierten IRQs)
CPU-Clock: 710000000
RAM-Clock: 1075200000 (eff. Datentaktrate)
BUS-Breite (Word=): 16 Bit
Measure-Time: 1 * 1.0s
-- Results --
=============================================================================
type | total read | loops | DDR-Ticks | 16Bit |
| in kByte | | /16Bit | Worte/s | kByte/s
=============================================================================
read | 1579008 | 1 | 1.329 | 808452096 | 1579008
| | | | |
Burstartiges Lesen aus dem RAM unter Nutzung von load multiple.
-----------------------------------------------------------------------------
Dependencies
Daily updated index of all dependencies of this object. Last update: GMT.
A ** in the Mod column marks info from Supportdata2 probes, which will always stay incomplete.
A - in the Mod column marks manual research, the Firmware then shows where the Object occurs, not the Relation.
| Relation | Typ | Object | Mod | Firmware | Info | Origin |
|---|---|---|---|---|---|---|
| 0 dependencies for this object | ||||||
Model-Matrix
Daily updated index of the presence, path and size of this object for each model. Last update: 2024-04-16 04:22 GMT.
Showing all models using this object. Click any column header (click-wait-click) to sort the list by the respective data.
The (main/scrpn/boot/arm/prx/atom) label in the Model column shows which CPU is meant for models with multiple Linux instances.
Note that this list comes from Supportdata2 probes, which can have arbitrary settings and come from different firmware versions.
It doesn't say much if a model is not listed here. It may be a missing supportdata2 file or just a disabled feature.
| Model | Firmware | Path | Kernel (perm) |
|---|---|---|---|
| FRITZ!Box 4060 | 7.30 - 7.39 | /proc/avm/benchmark | 4.4.271 (l), 4.4.60 (l) |
| FRITZ!Box 5590 Fiber (arm) | 7.29 | /proc/avm/benchmark | 4.4.60 (l) |
| FRITZ!Box 6360 Cable | 5.20 | /proc/sys/urlader | 2.6.28.10 (rw) |
| FRITZ!Box 6430 Cable (arm) | 7.29 | /proc/sys/urlader | 2.6.39.4 (rw) |
| FRITZ!Box 6430 Cable (atom) | 7.29 | /proc/sys/urlader | 2.6.39.4 (rw) |
| FRITZ!Box 6490 Cable (arm) | 7.29 - 7.39 | /proc/sys/urlader | 2.6.39.4 (rw) |
| FRITZ!Box 6490 Cable (atom) | 7.29 - 7.39 | /proc/sys/urlader | 2.6.39.4 (rw) |
| FRITZ!Box 6660 Cable (atom) | 7.29 | /proc/sys/urlader | 4.9.250 (rw) |
| FRITZ!Box 6850 LTE | 7.39 | /proc/avm/benchmark | 4.4.60 (l) |
| FRITZ!Box 6850 5G | 7.39 | /proc/avm/benchmark | 4.4.60 (l) |
| FRITZ!Box 7510 | 7.30 | /proc/avm/benchmark | 4.4.60 (l) |
| FRITZ!Box 7520 | 7.29 - 7.50 | /proc/avm/benchmark | 4.4.271 (l), 4.4.60 (l) |
| FRITZ!Box 7520 v2 | 7.31 | /proc/avm/benchmark | 4.4.60 (l) |
| FRITZ!Box 7530 | 7.39 | /proc/avm/benchmark | 4.4.271 (l) |
| FRITZ!Box 7530 AX | 7.31 | /proc/avm/benchmark | 4.1.52 (l) |
| FRITZ!Box 7581 | 7.17 | /proc/avm/benchmark | 4.1.38 (l) |
| FRITZ!Smart Gateway | 7.57 - 7.58 | /proc/avm/benchmark | 4.4.271 (l) |
| FRITZ!Repeater 1200 AX | 7.30 - 7.39 | /proc/avm/benchmark | 4.4.60 (l) |
| FRITZ!Repeater 6000 | 7.29 - 7.39 | /proc/avm/benchmark | 4.4.60 (l) |
| 19 models use this object | |||
Help Supportdata2
The data in this article is incomplete since it was manually collected using the Supportdata2 project.
Unlike the Supportdata-Probes which have been collected for years Supportdata2 is brand new and only has a few probes.
If you have access to a shell then please help to extend the Supportdata2 collection to improve this data.
It's easy and it's done in minutes. Please send created data as an Email attachment to the address listed here. Thanks!
