Af 1bot.dk | 25.12.2019 02:56

Installation af lm-sensors 3.6.0

Forums

Brødtekst

Hej linuxin-brugere

Jeg har gevaldige problemmer mht at få informationer ud af min ryzen 3900x kørene på "asus prime x370-pro" motherboardet, gennem installation af lm-sensors 3.5.0 der ik vil annerkende tredie generation af ryzen cpu'en selvom sensors-detect fortæller mig hvilken cpu jeg kører med.

Når jeg kører sensors-detect ifm installation af lm-sensors 3.5.0 fortæller programmet mig bare af der er ingen cpu'er genkendt selvom 17h amd-cpu-genration er skrevet ind i version 3.5.0, er gen-2 af ryzen cpuen (tredie genration af ryzen cpu'en) nyere end version 3.5.0 og jeg har ligesom set at lm-sensors bliver brugt ifm gkrellm, conky mfl programmer.

Dette link fortæller at:

sensors-detect: Add detection of AMD Family 17h, models 30h, 70h (samt AMD Family 15h og 16h model 30h power sensors) er tilføjet versionen 3.6.0 og gennem min søgen på google, af hjælp til at installere lm-sensors 3.6.0 på i første omgang på debian 10 finder jeg ingen hjælp via tråde til hvordan jeg installere lm-sensors. Jeg har installeret compileren gcc via link og at læse infofilerne på github-siden mht lm-sensors, få jeg ik meget hjælp til at få installeret programmet.

Og så spørger jeg på mine grædene knæ om der ik er nogen der har prøvet at hente lm-sensors 3.6.0 fra github-siden link for at installere seneste version af programmet på linuxsystemet.

Men denne klagesang fra mig gælder ligeså meget installation fra github-sider eller compile kommende programmer der ik er i managerne (apt mfl) og ligeså meget pga nyere versioner af programmerne.

Jeg håber ovenstående beskrivelse giver mening og at jeg ik gentager mig selv for mange gange, da jeg prøver at være så konkret at det ik kan misforstås og jeg kan forstå at lm-sensors 3.5.0 ligesom er den generale version der kan hentes (installeres) via apt-manageren ifm debian, mxlinux og ubuntu.

/allan

Log in to post comments

Kommentarer50

Har du

Har du læst

https://github.com/lm-sensors/lm-sensors/blob/master/INSTALL

Jeg har forøvrigt lm-sensors 3.6.0 i synaptic.

Der ser også ud til at være debian pakker klar.

https://packages.debian.org/sid/amd64/lm-sensors/download

Når lm-sensors, er installeret, kan du køre -

# sudo sensors-detect --auto

Og se resultatet med

$ sensors coretemp-isa-0000 Adapter: ISA adapter Core 0: +33.0°C (high = +105.0°C, crit = +105.0°C) Core 1: +31.0°C (high = +105.0°C, crit = +105.0°C) acpitz-acpi-0 Adapter: ACPI interface temp1: +35.0°C (crit = +127.0°C) temp2: +33.0°C (crit = +100.0°C) thinkpad-isa-0000 Adapter: ISA adapter fan1: 1895 RPM temp1: +35.0°C temp2: +35.0°C temp3: +31.0°C temp4: N/A temp5: +50.0°C temp6: N/A temp7: +21.0°C temp8: N/A temp9: +34.0°C temp10: +38.0°C temp11: +35.0°C temp12: N/A temp13: N/A temp14: N/A temp15: N/A temp16: N/A

Her på en gammel T500.

Log in to post comments

svar på osjensen's indlæg

Hej osjensen

Dit første LINK er det jeg ik kan forstrå, for der bliver blot ref til en kommando "make install" som når jeg i mit home directory og danner mappen "lm-sensors" og skriver kommandoen "sudo make install" kommer følgende svar (1).

Dit andet hint mht "synaptic package manager" (synaptic) viser kun "1:3.5.0-3" og altså ik version 3.6.0.

Dit tredie LINK viser links til

ftp.dk.debian.org/debian, da jeg klikker på den danske ftp i europa, som giver mig en deb-fil til den ustabile version af debian, men jeg må indrøme jeg har ik prøvet at installere via deb endsige tænkt på det (og tak for den ide) giver følgende svar med kommandoen "sudo apt install lm-sensors_3.6.0-2_amd64.deb" (2) og jeg har prøvet forskellige varianter ved hjælp af linket men det hjalp heller ik.

JEG ER HÅBENBART MEGET TUNGNEM !!!

/allan

PS: Jeg har først set din tillægskommando "sudo sensors-detect --auto" efter jeg har prøvet de tre hint, men eftersom jeg ik har fået installeret lm-sensors endnu kan jeg ik bruge denne kommando endnu.

(1)

allan@debian:~/lm-sensors$ sudo make install [sudo] password for allan: gcc -M -MG -DETCDIR="\"/etc\"" -I. -Wall -O2 -Wstrict-prototypes -Wshadow -Wpointer-arith -Wcast-qual -Wcast-align -Wwrite-strings -Wnested-externs -Winline -W -Wmissing-prototypes -Wundef prog/dump/superio.c | \ sed -e 's@^$.*$\.o:@prog/dump/superio.rd prog/dump/superio.ro: Makefile '`dirname prog/dump/superio.rd`/Module.mk' @' > prog/dump/superio.rd gcc -M -MG -DETCDIR="\"/etc\"" -I. -Wall -O2 -Wstrict-prototypes -Wshadow -Wpointer-arith -Wcast-qual -Wcast-align -Wwrite-strings -Wnested-externs -Winline -W -Wmissing-prototypes -Wundef prog/dump/isaset.c | \ sed -e 's@^$.*$\.o:@prog/dump/isaset.rd prog/dump/isaset.ro: Makefile '`dirname prog/dump/isaset.rd`/Module.mk' @' > prog/dump/isaset.rd gcc -M -MG -DETCDIR="\"/etc\"" -I. -Wall -O2 -Wstrict-prototypes -Wshadow -Wpointer-arith -Wcast-qual -Wcast-align -Wwrite-strings -Wnested-externs -Winline -W -Wmissing-prototypes -Wundef prog/dump/isadump.c | \ sed -e 's@^$.*$\.o:@prog/dump/isadump.rd prog/dump/isadump.ro: Makefile '`dirname prog/dump/isadump.rd`/Module.mk' @' > prog/dump/isadump.rd gcc -M -MG -DETCDIR="\"/etc\"" -I. -Wall -O2 -Wstrict-prototypes -Wshadow -Wpointer-arith -Wcast-qual -Wcast-align -Wwrite-strings -Wnested-externs -Winline -W -Wmissing-prototypes -Wundef prog/dump/util.c | \ sed -e 's@^$.*$\.o:@prog/dump/util.rd prog/dump/util.ro: Makefile '`dirname prog/dump/util.rd`/Module.mk' @' > prog/dump/util.rd gcc -M -MG -DETCDIR="\"/etc\"" -I. -Wall -O2 -Wstrict-prototypes -Wshadow -Wpointer-arith -Wcast-qual -Wcast-align -Wwrite-strings -Wnested-externs -Winline -W -Wmissing-prototypes -Wundef prog/sensors/chips.c | \ sed -e 's@^$.*$\.o:@prog/sensors/chips.rd prog/sensors/chips.ro: Makefile '`dirname prog/sensors/chips.rd`/Module.mk' @' > prog/sensors/chips.rd gcc -M -MG -DETCDIR="\"/etc\"" -I. -Wall -O2 -Wstrict-prototypes -Wshadow -Wpointer-arith -Wcast-qual -Wcast-align -Wwrite-strings -Wnested-externs -Winline -W -Wmissing-prototypes -Wundef prog/sensors/main.c | \ sed -e 's@^$.*$\.o:@prog/sensors/main.rd prog/sensors/main.ro: Makefile '`dirname prog/sensors/main.rd`/Module.mk' @' > prog/sensors/main.rd Please install bison, then run "make clean" and try again Makefile:175: lib/conf-lex.ad: No such file or directory make: *** [Makefile:270: lib/conf-parse.c] Error 1

(2)

allan@debian:~$ ls deb-files Documents hello it87 Music Public Videos Desktop Downloads hello.c lm-sensors Pictures Templates allan@debian:~$ cd deb-files/ allan@debian:~/deb-files$ ls lm-sensors_3.6.0-2_amd64.deb allan@debian:~/deb-files$ sudo apt install lm-sensors_3.6.0-2_amd64.deb [sudo] password for allan: E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? allan@debian:~/deb-files$ sudo dpkg -i lm-sensors_3.6.0-2_amd64.deb dpkg: error: dpkg frontend lock is locked by another process allan@debian:~/deb-files$ sudo dpkg -i /home/allan/deb-files/lm-sensors_3.6.0-2_amd64.deb dpkg: error: dpkg frontend lock is locked by another process allan@debian:~/deb-files$ sudo dpkg -i /home/allan/deb-files/lm-sensors_3.6.0-2_amd64.deb&&sudo apt-get install -f dpkg: error: dpkg frontend lock is locked by another process allan@debian:~/deb-files$ sudo apt install lm-sensors_3.6.0-2_amd64.deb E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?

Log in to post comments

Fra en MX 19 livecd

dpkg: error: dpkg frontend lock is locked by another process

Du har sikkert synaptic kørende i baggrunden.

Luk synaptic eller genstart maskinen, og start på en frisk.

Fra en MX livecd:

*******************************************************

root@mx1:/home/demo/Downloads# apt install ./lm-sensors_3.6.0-2_amd64.deb

Reading package lists... Done

Building dependency tree

Reading state information... Done

Note, selecting 'lm-sensors' instead of './lm-sensors_3.6.0-2_amd64.deb'

Suggested packages:

fancontrol i2c-tools

The following NEW packages will be installed:

lm-sensors

0 upgraded, 1 newly installed, 0 to remove and 132 not upgraded.

After this operation, 414 kB of additional disk space will be used.

Get:1 /home/demo/Downloads/lm-sensors_3.6.0-2_amd64.deb lm-sensors amd64 1:3.6.0-2 [115 kB]

Selecting previously unselected package lm-sensors.

(Reading database ... 273192 files and directories currently installed.)

Preparing to unpack .../lm-sensors_3.6.0-2_amd64.deb ...

Unpacking lm-sensors (1:3.6.0-2) ...

Setting up lm-sensors (1:3.6.0-2) ...

Processing triggers for man-db (2.8.5-2) ...

Processing triggers for systemd (1:241-5+mx19+2) ...

root@mx1:/home/demo/Downloads#

root@mx1:/home/demo/Downloads# sensors-detect --auto

# sensors-detect version 3.6.0

# System: LENOVO 2089WBT [ThinkPad T500] (laptop)

# Kernel: 4.19.0-6-amd64 x86_64

# Processor: Intel(R) Core(TM)2 Duo CPU P8400 @ 2.26GHz (6/23/10)

Running in automatic mode, default answers to all questions

are assumed.

Some south bridges, CPUs or memory controllers contain embedded sensors.

Do you want to scan for them? This is totally safe. (YES/no):

Module cpuid loaded successfully.

Silicon Integrated Systems SIS5595... No

VIA VT82C686 Integrated Sensors... No

VIA VT8231 Integrated Sensors... No

AMD K8 thermal sensors... No

AMD Family 10h thermal sensors... No

AMD Family 11h thermal sensors... No

AMD Family 12h and 14h thermal sensors... No

AMD Family 15h thermal sensors... No

AMD Family 16h thermal sensors... No

AMD Family 17h thermal sensors... No

AMD Family 15h power sensors... No

AMD Family 16h power sensors... No

Hygon Family 18h thermal sensors... No

Intel digital thermal sensor... Success!

(driver `coretemp')

Intel AMB FB-DIMM thermal sensor... No

Intel 5500/5520/X58 thermal sensor... No

VIA C7 thermal sensor... No

VIA Nano thermal sensor... No

-- osv.--

root@mx1:/home/demo/Downloads# sensors

coretemp-isa-0000

Adapter: ISA adapter

Core 0: +38.0°C (high = +105.0°C, crit = +105.0°C)

Core 1: +34.0°C (high = +105.0°C, crit = +105.0°C)

acpitz-acpi-0

Adapter: ACPI interface

temp1: +38.0°C (crit = +127.0°C)

temp2: +38.0°C (crit = +100.0°C)

thinkpad-isa-0000

Adapter: ISA adapter

fan1: 1906 RPM

temp1: +38.0°C

temp2: +38.0°C

temp3: +33.0°C

temp4: N/A

temp5: +50.0°C

temp6: N/A

temp7: +28.0°C

temp8: N/A

temp9: +38.0°C

temp10: +41.0°C

temp11: +38.0°C

temp12: N/A

temp13: N/A

temp14: N/A

temp15: N/A

temp16: N/A

root@mx1:/home/demo/Downloads#

***********************************************

Alt virker, som det skal.

En hurtig alternativ test, kan gøres med en openbox mini cd.

https://www.pclinuxos.com/forum/index.php/topic,151038.0.html

lm-sensors 3.6.0 er instaleret på isoen.

Log in to post comments

Hej osjensenSÅ LYKKES DET

Hej osjensen

SÅ LYKKES DET MHT AT INSTALLERE DEB-FILEN OG TAK FOR DIN HJÆLP!!

Men jeg følger ik jeg er kommet meget tættere på mht temperaturaen i ryzen 3900x cpu'en. For iflg (note 1) finder kommandoen "sudo sensors-detect --auto" godt nok cpu'en, men når jeg skriver kommandoen "sensors" eller "watch sensors" (note 2) viser lm-sensors kun gpu temperaturen, og du kan se i (note 3) versionen for lm-sensors.

Jeg har fået installeret psensor, men det hjælper ik meget på temperaturen for cpu'en, og jeg har prøvet at installere it87.c med kommandoen "gcc it87.c -o install" fra github-siden med LINKet uden et brugbart resultat. I min google-søgn har jeg fundet LINKet der gav kommandoen "sudo dmidecode > sensors.txt" (note 4) og ref til github-siden hvor it87 er. Og en anden side LINKet hvor vedkommende skriver at it87.c skal installeres, men ik hvordan it87 bliver installeret (og det er generelt på nettet at info-teksten til at få installeret et code-program er mangelfuldt skrevet, men det er nok fordi læseren/brugeren ved hvordan code-programmere skal installeres og jeg ik forstå dem!!).

/allan

1)

allan@debian:~$ sudo sensors-detect --auto [sudo] password for allan: # sensors-detect version 3.6.0 # Board: ASUSTeK COMPUTER INC. PRIME X370-PRO # Kernel: 4.19.0-6-amd64 x86_64 # Processor: AMD Ryzen 9 3900X 12-Core Processor (23/113/0) Running in automatic mode, default answers to all questions are assumed. Some south bridges, CPUs or memory controllers contain embedded sensors. Do you want to scan for them? This is totally safe. (YES/no): Module cpuid loaded successfully. Silicon Integrated Systems SIS5595... No VIA VT82C686 Integrated Sensors... No VIA VT8231 Integrated Sensors... No AMD K8 thermal sensors... No AMD Family 10h thermal sensors... No AMD Family 11h thermal sensors... No AMD Family 12h and 14h thermal sensors... No AMD Family 15h thermal sensors... No AMD Family 16h thermal sensors... No AMD Family 17h thermal sensors... Success! (driver `k10temp') AMD Family 15h power sensors... No AMD Family 16h power sensors... No Hygon Family 18h thermal sensors... No Intel digital thermal sensor... No Intel AMB FB-DIMM thermal sensor... No Intel 5500/5520/X58 thermal sensor... No VIA C7 thermal sensor... No VIA Nano thermal sensor... No Some Super I/O chips contain embedded sensors. We have to write to standard I/O ports to probe them. This is usually safe. Do you want to scan for Super I/O sensors? (YES/no): Probing for Super-I/O at 0x2e/0x2f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... Yes Found `ITE IT8665E Super IO Sensors' Success! (address 0x290, driver `to-be-written') Probing for Super-I/O at 0x4e/0x4f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... No Some systems (mainly servers) implement IPMI, a set of common interfaces through which system health data may be retrieved, amongst other things. We first try to get the information from SMBIOS. If we don't find it there, we have to read from arbitrary I/O ports to probe for such interfaces. This is normally safe. Do you want to scan for IPMI interfaces? (YES/no): Probing for `IPMI BMC KCS' at 0xca0... No Probing for `IPMI BMC SMIC' at 0xca8... No Some hardware monitoring chips are accessible through the ISA I/O ports. We have to write to arbitrary I/O ports to probe them. This is usually safe though. Yes, you do have ISA I/O ports even if you do not have any ISA slots! Do you want to scan the ISA I/O ports? (yes/NO): Lastly, we can probe the I2C/SMBus adapters for connected hardware monitoring devices. This is the most risky part, and while it works reasonably well on most systems, it has been reported to cause trouble on some systems. Do you want to probe the I2C/SMBus adapters now? (YES/no): Using driver `i2c-piix4' for device 0000:00:14.0: AMD KERNCZ SMBus Module i2c-dev loaded successfully. Next adapter: SMBus PIIX4 adapter port 0 at 0b00 (i2c-0) Do you want to scan it? (YES/no/selectively): Client found at address 0x50 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... Yes (confidence 8, not a hardware monitoring chip) Probing for `EDID EEPROM'... No Client found at address 0x51 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... Yes (confidence 8, not a hardware monitoring chip) Client found at address 0x52 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... Yes (confidence 8, not a hardware monitoring chip) Client found at address 0x53 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... Yes (confidence 8, not a hardware monitoring chip) Next adapter: SMBus PIIX4 adapter port 2 at 0b00 (i2c-1) Do you want to scan it? (YES/no/selectively): Next adapter: SMBus PIIX4 adapter port 3 at 0b00 (i2c-2) Do you want to scan it? (YES/no/selectively): Next adapter: SMBus PIIX4 adapter port 4 at 0b00 (i2c-3) Do you want to scan it? (YES/no/selectively): Next adapter: nvkm-0000:0a:00.0-bus-0000 (i2c-4) Do you want to scan it? (yes/NO/selectively): Next adapter: nvkm-0000:0a:00.0-bus-0001 (i2c-5) Do you want to scan it? (yes/NO/selectively): Next adapter: nvkm-0000:0a:00.0-bus-0002 (i2c-6) Do you want to scan it? (yes/NO/selectively): Next adapter: nvkm-0000:0a:00.0-bus-0005 (i2c-7) Do you want to scan it? (yes/NO/selectively): Next adapter: nvkm-0000:0a:00.0-bus-0006 (i2c-8) Do you want to scan it? (yes/NO/selectively): Next adapter: nvkm-0000:0a:00.0-bus-0007 (i2c-9) Do you want to scan it? (yes/NO/selectively): Next adapter: nvkm-0000:0a:00.0-bus-0008 (i2c-10) Do you want to scan it? (yes/NO/selectively): Next adapter: nvkm-0000:0a:00.0-bus-0009 (i2c-11) Do you want to scan it? (yes/NO/selectively): Next adapter: nvkm-0000:0a:00.0-aux-000a (i2c-12) Do you want to scan it? (yes/NO/selectively): Next adapter: nvkm-0000:0a:00.0-aux-000b (i2c-13) Do you want to scan it? (yes/NO/selectively): Next adapter: nvkm-0000:0a:00.0-aux-000c (i2c-14) Do you want to scan it? (yes/NO/selectively): Next adapter: nvkm-0000:0a:00.0-aux-000d (i2c-15) Do you want to scan it? (yes/NO/selectively): Now follows a summary of the probes I have just done. Driver `to-be-written': * ISA bus, address 0x290 Chip `ITE IT8665E Super IO Sensors' (confidence: 9) Driver `k10temp': * Chip `AMD Family 17h thermal sensors' (confidence: 9) Note: there is no driver for ITE IT8665E Super IO Sensors yet. Check https://hwmon.wiki.kernel.org/device_support_status for updates. To load everything that is needed, add this to /etc/modules: #----cut here---- # Chip drivers k10temp #----cut here---- If you have some drivers built into your kernel, the list above will contain too many modules. Skip the appropriate ones! Do you want to add these lines automatically to /etc/modules? (yes/NO) Unloading i2c-dev... OK Unloading cpuid... OK

2)

allan@debian:~$ sensors nouveau-pci-0a00 Adapter: PCI adapter GPU core: 912.00 mV (min = +0.80 V, max = +1.19 V) temp1: +46.0°C (high = +95.0°C, hyst = +3.0°C) (crit = +105.0°C, hyst = +5.0°C) (emerg = +135.0°C, hyst = +5.0°C) asus-isa-0000 Adapter: ISA adapter cpu_fan: 0 RPM

3)

allan@debian:~$ sensors -v sensors version 3.6.0 with libsensors version 3.5.0

4)

# dmidecode 3.2 Getting SMBIOS data from sysfs. SMBIOS 3.1.1 present. Table at 0x000E6B60. Handle 0x0000, DMI type 0, 26 bytes BIOS Information Vendor: American Megatrends Inc. Version: 5220 Release Date: 09/12/2019 Address: 0xF0000 Runtime Size: 64 kB ROM Size: 16 MB Characteristics: PCI is supported APM is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported BIOS ROM is socketed EDD is supported 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported BIOS boot specification is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 5.13 Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: System manufacturer Product Name: System Product Name Version: System Version Serial Number: System Serial Number UUID: dbee9940-05f2-11e9-8e4d-049226da0509 Wake-up Type: Power Switch SKU Number: SKU Family: To be filled by O.E.M. Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: ASUSTeK COMPUTER INC. Product Name: PRIME X370-PRO Version: Rev X.0x Serial Number: 181242061800950 Asset Tag: Default string Features: Board is a hosting board Board is replaceable Location In Chassis: Default string Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 Handle 0x0003, DMI type 3, 22 bytes Chassis Information Manufacturer: Default string Type: Desktop Lock: Not Present Version: Default string Serial Number: Default string Asset Tag: Default string Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: None OEM Information: 0x00000000 Height: Unspecified Number Of Power Cords: 1 Contained Elements: 0 SKU Number: Default string Handle 0x0004, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: PS/2 Keyboard/Mouse Internal Connector Type: None External Reference Designator: PS/2 Keyboard/Mouse External Connector Type: PS/2 Port Type: Keyboard Port Handle 0x0005, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: USB3_910 Internal Connector Type: None External Reference Designator: USB3_910 External Connector Type: Access Bus (USB) Port Type: USB Handle 0x0006, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: DP Internal Connector Type: None External Reference Designator: DP port External Connector Type: Other Port Type: Video Port Handle 0x0007, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: HDMI Internal Connector Type: None External Reference Designator: HDMI port External Connector Type: Other Port Type: Video Port Handle 0x0008, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: USB3_C7 Internal Connector Type: None External Reference Designator: USB3_C7 External Connector Type: Access Bus (USB) Port Type: USB Handle 0x0009, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: USB3_5 Internal Connector Type: None External Reference Designator: USB3_5 External Connector Type: Access Bus (USB) Port Type: USB Handle 0x000A, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: USB3.1_E12 Internal Connector Type: None External Reference Designator: USB3.1_E12 External Connector Type: Access Bus (USB) Port Type: USB Handle 0x000B, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: USB3_34 Internal Connector Type: None External Reference Designator: USB3_34 External Connector Type: Access Bus (USB) Port Type: USB Handle 0x000C, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: LAN Internal Connector Type: None External Reference Designator: LAN External Connector Type: RJ-45 Port Type: Network Port Handle 0x000D, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: AUDIO Internal Connector Type: None External Reference Designator: AUDIO External Connector Type: Other Port Type: Audio Port Handle 0x000E, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: SATA6G_1 Internal Connector Type: SAS/SATA Plug Receptacle External Reference Designator: Not Specified External Connector Type: None Port Type: SATA Handle 0x000F, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: SATA6G_2 Internal Connector Type: SAS/SATA Plug Receptacle External Reference Designator: Not Specified External Connector Type: None Port Type: SATA Handle 0x0010, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: SATA6G_3 Internal Connector Type: SAS/SATA Plug Receptacle External Reference Designator: Not Specified External Connector Type: None Port Type: SATA Handle 0x0011, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: SATA6G_4 Internal Connector Type: SAS/SATA Plug Receptacle External Reference Designator: Not Specified External Connector Type: None Port Type: SATA Handle 0x0012, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: SATA6G_5 Internal Connector Type: SAS/SATA Plug Receptacle External Reference Designator: Not Specified External Connector Type: None Port Type: SATA Handle 0x0013, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: SATA6G_6 Internal Connector Type: SAS/SATA Plug Receptacle External Reference Designator: Not Specified External Connector Type: None Port Type: SATA Handle 0x0014, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: SATA6G_7 Internal Connector Type: SAS/SATA Plug Receptacle External Reference Designator: Not Specified External Connector Type: None Port Type: SATA Handle 0x0015, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: SATA6G_8 Internal Connector Type: SAS/SATA Plug Receptacle External Reference Designator: Not Specified External Connector Type: None Port Type: SATA Handle 0x0016, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: M.2 Internal Connector Type: SAS/SATA Plug Receptacle External Reference Designator: Not Specified External Connector Type: None Port Type: SATA Handle 0x0017, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: USB_12 Internal Connector Type: Access Bus (USB) External Reference Designator: Not Specified External Connector Type: None Port Type: USB Handle 0x0018, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: USB_34 Internal Connector Type: Access Bus (USB) External Reference Designator: Not Specified External Connector Type: None Port Type: USB Handle 0x0019, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: USB3_12 Internal Connector Type: Access Bus (USB) External Reference Designator: Not Specified External Connector Type: None Port Type: USB Handle 0x001A, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: USB3.1_C1 Internal Connector Type: Access Bus (USB) External Reference Designator: Not Specified External Connector Type: None Port Type: USB Handle 0x001B, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: CPU_FAN Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x001C, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: CPU_OPT Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x001D, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: CHA_FAN1 Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x001E, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: AIO_PUMP Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x001F, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: CHA_FAN2 Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x0020, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: W_PUMP+ Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x0021, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: COM Internal Connector Type: DB-9 male External Reference Designator: Not Specified External Connector Type: None Port Type: Serial Port 16550A Compatible Handle 0x0022, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: AAFP Internal Connector Type: Mini Jack (headphones) External Reference Designator: Not Specified External Connector Type: None Port Type: Audio Port Handle 0x0023, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: PANEL Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x0024, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: TPM Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x0025, DMI type 10, 6 bytes On Board Device Information Type: Video Status: Enabled Description: To Be Filled By O.E.M. Handle 0x0026, DMI type 11, 5 bytes OEM Strings String 1: Default string String 2: Default string String 3: COKE String 4: Default string String 5: FFFFFFFFFFFFF String 6: FFFFFFFFFFFFF String 7: FFFFFFFFFFFFF String 8: Default string Handle 0x0027, DMI type 12, 5 bytes System Configuration Options Option 1: SMI:00B29C05 Option 2: DSN: . Option 3: DSN: . Option 4: DSN: . Handle 0x0028, DMI type 32, 20 bytes System Boot Information Status: No errors detected Handle 0x0029, DMI type 34, 11 bytes Management Device Description: ITE IT8665E Type: Other Address: 0x00000295 Address Type: I/O Port Handle 0x002A, DMI type 41, 11 bytes Onboard Device Reference Designation: Onboard IGD Type: Video Status: Enabled Type Instance: 1 Bus Address: 0000:00:02.0 Handle 0x002B, DMI type 18, 23 bytes 32-bit Memory Error Information Type: OK Granularity: Unknown Operation: Unknown Vendor Syndrome: Unknown Memory Array Address: Unknown Device Address: Unknown Resolution: Unknown Handle 0x002C, DMI type 16, 23 bytes Physical Memory Array Location: System Board Or Motherboard Use: System Memory Error Correction Type: None Maximum Capacity: 128 GB Error Information Handle: 0x002B Number Of Devices: 4 Handle 0x002D, DMI type 19, 31 bytes Memory Array Mapped Address Starting Address: 0x00000000000 Ending Address: 0x000DFFFFFFF Range Size: 3584 MB Physical Array Handle: 0x002C Partition Width: 4 Handle 0x002E, DMI type 19, 31 bytes Memory Array Mapped Address Starting Address: 0x00100000000 Ending Address: 0x0101FFFFFFF Range Size: 61952 MB Physical Array Handle: 0x002C Partition Width: 4 Handle 0x002F, DMI type 7, 19 bytes Cache Information Socket Designation: L1 - Cache Configuration: Enabled, Not Socketed, Level 1 Operational Mode: Write Back Location: Internal Installed Size: 768 kB Maximum Size: 768 kB Supported SRAM Types: Pipeline Burst Installed SRAM Type: Pipeline Burst Speed: 1 ns Error Correction Type: Multi-bit ECC System Type: Unified Associativity: 8-way Set-associative Handle 0x0030, DMI type 7, 19 bytes Cache Information Socket Designation: L2 - Cache Configuration: Enabled, Not Socketed, Level 2 Operational Mode: Write Back Location: Internal Installed Size: 6144 kB Maximum Size: 6144 kB Supported SRAM Types: Pipeline Burst Installed SRAM Type: Pipeline Burst Speed: 1 ns Error Correction Type: Multi-bit ECC System Type: Unified Associativity: 8-way Set-associative Handle 0x0031, DMI type 7, 19 bytes Cache Information Socket Designation: L3 - Cache Configuration: Enabled, Not Socketed, Level 3 Operational Mode: Write Back Location: Internal Installed Size: 65536 kB Maximum Size: 65536 kB Supported SRAM Types: Pipeline Burst Installed SRAM Type: Pipeline Burst Speed: 1 ns Error Correction Type: Multi-bit ECC System Type: Unified Associativity: 16-way Set-associative Handle 0x0032, DMI type 4, 48 bytes Processor Information Socket Designation: AM4 Type: Central Processor Family: Zen Manufacturer: Advanced Micro Devices, Inc. ID: 10 0F 87 00 FF FB 8B 17 Signature: Family 23, Model 113, Stepping 0 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) DE (Debugging extension) PSE (Page size extension) TSC (Time stamp counter) MSR (Model specific registers) PAE (Physical address extension) MCE (Machine check exception) CX8 (CMPXCHG8 instruction supported) APIC (On-chip APIC hardware supported) SEP (Fast system call) MTRR (Memory type range registers) PGE (Page global enable) MCA (Machine check architecture) CMOV (Conditional move instruction supported) PAT (Page attribute table) PSE-36 (36-bit page size extension) CLFSH (CLFLUSH instruction supported) MMX (MMX technology supported) FXSR (FXSAVE and FXSTOR instructions supported) SSE (Streaming SIMD extensions) SSE2 (Streaming SIMD extensions 2) HTT (Multi-threading) Version: AMD Ryzen 9 3900X 12-Core Processor Voltage: 1.1 V External Clock: 100 MHz Max Speed: 4650 MHz Current Speed: 3800 MHz Status: Populated, Enabled Upgrade: Socket AM4 L1 Cache Handle: 0x002F L2 Cache Handle: 0x0030 L3 Cache Handle: 0x0031 Serial Number: Unknown Asset Tag: Unknown Part Number: Unknown Core Count: 12 Core Enabled: 12 Thread Count: 24 Characteristics: 64-bit capable Multi-Core Hardware Thread Execute Protection Enhanced Virtualization Power/Performance Control Handle 0x0033, DMI type 18, 23 bytes 32-bit Memory Error Information Type: OK Granularity: Unknown Operation: Unknown Vendor Syndrome: Unknown Memory Array Address: Unknown Device Address: Unknown Resolution: Unknown Handle 0x0034, DMI type 17, 40 bytes Memory Device Array Handle: 0x002C Error Information Handle: 0x0033 Total Width: 64 bits Data Width: 64 bits Size: 16384 MB Form Factor: DIMM Set: None Locator: DIMM_A1 Bank Locator: BANK 0 Type: DDR4 Type Detail: Synchronous Unbuffered (Unregistered) Speed: 2666 MT/s Manufacturer: Kingston Serial Number: F01CF4EC Asset Tag: Not Specified Part Number: KHX2666C16/16G Rank: 2 Configured Memory Speed: 2666 MT/s Minimum Voltage: 1.2 V Maximum Voltage: 1.2 V Configured Voltage: 1.2 V Handle 0x0035, DMI type 20, 35 bytes Memory Device Mapped Address Starting Address: 0x00000000000 Ending Address: 0x00FFFFFFFFF Range Size: 64 GB Physical Device Handle: 0x0034 Memory Array Mapped Address Handle: 0x002E Partition Row Position: Unknown Interleave Position: Unknown Interleaved Data Depth: Unknown Handle 0x0036, DMI type 18, 23 bytes 32-bit Memory Error Information Type: OK Granularity: Unknown Operation: Unknown Vendor Syndrome: Unknown Memory Array Address: Unknown Device Address: Unknown Resolution: Unknown Handle 0x0037, DMI type 17, 40 bytes Memory Device Array Handle: 0x002C Error Information Handle: 0x0036 Total Width: 64 bits Data Width: 64 bits Size: 16384 MB Form Factor: DIMM Set: None Locator: DIMM_A2 Bank Locator: BANK 1 Type: DDR4 Type Detail: Synchronous Unbuffered (Unregistered) Speed: 2666 MT/s Manufacturer: Kingston Serial Number: EE1CF6EC Asset Tag: Not Specified Part Number: KHX2666C16/16G Rank: 2 Configured Memory Speed: 2666 MT/s Minimum Voltage: 1.2 V Maximum Voltage: 1.2 V Configured Voltage: 1.2 V Handle 0x0038, DMI type 20, 35 bytes Memory Device Mapped Address Starting Address: 0x00000000000 Ending Address: 0x00FFFFFFFFF Range Size: 64 GB Physical Device Handle: 0x0037 Memory Array Mapped Address Handle: 0x002E Partition Row Position: Unknown Interleave Position: Unknown Interleaved Data Depth: Unknown Handle 0x0039, DMI type 18, 23 bytes 32-bit Memory Error Information Type: OK Granularity: Unknown Operation: Unknown Vendor Syndrome: Unknown Memory Array Address: Unknown Device Address: Unknown Resolution: Unknown Handle 0x003A, DMI type 17, 40 bytes Memory Device Array Handle: 0x002C Error Information Handle: 0x0039 Total Width: 64 bits Data Width: 64 bits Size: 16384 MB Form Factor: DIMM Set: None Locator: DIMM_B1 Bank Locator: BANK 2 Type: DDR4 Type Detail: Synchronous Unbuffered (Unregistered) Speed: 2666 MT/s Manufacturer: Kingston Serial Number: EC1CF3EC Asset Tag: Not Specified Part Number: KHX2666C16/16G Rank: 2 Configured Memory Speed: 2666 MT/s Minimum Voltage: 1.2 V Maximum Voltage: 1.2 V Configured Voltage: 1.2 V Handle 0x003B, DMI type 20, 35 bytes Memory Device Mapped Address Starting Address: 0x00000000000 Ending Address: 0x00FFFFFFFFF Range Size: 64 GB Physical Device Handle: 0x003A Memory Array Mapped Address Handle: 0x002E Partition Row Position: Unknown Interleave Position: Unknown Interleaved Data Depth: Unknown Handle 0x003C, DMI type 18, 23 bytes 32-bit Memory Error Information Type: OK Granularity: Unknown Operation: Unknown Vendor Syndrome: Unknown Memory Array Address: Unknown Device Address: Unknown Resolution: Unknown Handle 0x003D, DMI type 17, 40 bytes Memory Device Array Handle: 0x002C Error Information Handle: 0x003C Total Width: 64 bits Data Width: 64 bits Size: 16384 MB Form Factor: DIMM Set: None Locator: DIMM_B2 Bank Locator: BANK 3 Type: DDR4 Type Detail: Synchronous Unbuffered (Unregistered) Speed: 2666 MT/s Manufacturer: Kingston Serial Number: E71C87EC Asset Tag: Not Specified Part Number: KHX2666C16/16G Rank: 2 Configured Memory Speed: 2666 MT/s Minimum Voltage: 1.2 V Maximum Voltage: 1.2 V Configured Voltage: 1.2 V Handle 0x003E, DMI type 20, 35 bytes Memory Device Mapped Address Starting Address: 0x00000000000 Ending Address: 0x00FFFFFFFFF Range Size: 64 GB Physical Device Handle: 0x003D Memory Array Mapped Address Handle: 0x002E Partition Row Position: Unknown Interleave Position: Unknown Interleaved Data Depth: Unknown Handle 0x003F, DMI type 13, 22 bytes BIOS Language Information Language Description Format: Long Installable Languages: 9 en|US|iso8859-1 fr|FR|iso8859-1 zh|TW|unicode ja|JP|unicode de|DE|iso8859-1 es|ES|iso8859-1 ru|RU|iso8859-5 ko|KR|unicode Currently Installed Language: en|US|iso8859-1 Handle 0x0040, DMI type 9, 17 bytes System Slot Information Designation: PCIEX16_1 Type: x16 PCI Express Current Usage: In Use Length: Long ID: 0 Characteristics: 3.3 V is provided Opening is shared PME signal is supported Bus Address: 0000:00:03.1 Handle 0x0041, DMI type 9, 17 bytes System Slot Information Designation: PCIEX16_2 Type: x8 PCI Express Current Usage: Available Length: Long ID: 1 Characteristics: 3.3 V is provided Opening is shared PME signal is supported Bus Address: 0000:00:1f.7 Handle 0x0042, DMI type 9, 17 bytes System Slot Information Designation: PCIEX16_3 Type: x4 PCI Express Current Usage: Available Length: Long ID: 2 Characteristics: 3.3 V is provided Opening is shared PME signal is supported Bus Address: 0000:00:1f.7 Handle 0x0043, DMI type 9, 17 bytes System Slot Information Designation: PCIEX1_1 Type: x1 PCI Express Current Usage: Available Length: Short ID: 3 Characteristics: 3.3 V is provided Opening is shared PME signal is supported Bus Address: 0000:00:1f.7 Handle 0x0044, DMI type 9, 17 bytes System Slot Information Designation: PCIEX1_2 Type: x1 PCI Express Current Usage: Available Length: Short ID: 4 Characteristics: 3.3 V is provided Opening is shared PME signal is supported Bus Address: 0000:00:1f.7 Handle 0x0045, DMI type 9, 17 bytes System Slot Information Designation: PCIEX1_3 Type: x1 PCI Express Current Usage: Available Length: Short ID: 5 Characteristics: 3.3 V is provided Opening is shared PME signal is supported Bus Address: 0000:00:1f.7 Handle 0x0046, DMI type 127, 4 bytes End Of Table

Log in to post comments

AMD Family 17h thermal

AMD Family 17h thermal sensors... Success!

(driver `k10temp')

Som jeg ser det, skal du have en hel ny kerne 5.4

for at få en k10temp driver, der virker

https://www.phoronix.com/scan.php?page=news_item&px=Linux-5.4-Hwmon-Zen…

Log in to post comments

Hej osjensen
Ved du hvordan

Hej osjensen

Ved du hvordan jeg får en update af kernel'en på debian 10.2 (debian 10.2 kører kernel 4.19) og er det overhoved muligt??

Jeg vil ik lyde for dum, men står det i dit link*??

/allan

* jeg håber ik du misforstår min fustration eller hjælpeløshed.

Log in to post comments

#6Der nævnes om kerne 5.4

#6

Der nævnes om kerne 5.4 at der er tilføjet- " k10temp: Add support for AMD family 17h, model 70h CPUs", og det må vel betyde, at det ikke har virket tidligere?

Se evt. om k10temp er indlæst med -

lsmod | grep k10temp

Da jeg ikke ejer noget med Amd, kan jeg ikke komme det nærmere, selv om jeg lige har installeret sidste nye kerne -

$ uname -r 5.4.6-pclos1

Hvad der er muligt på Debian, er der andre, der har mere erfaring med.

Nb.

På sådan en "super maskine", vil det ikke tage mere end 15 min. at installere en pclinuxos64-openbox-mini-2019.12.iso, i Virtual Box

og måske udlæse temperaturen.

Log in to post comments

Nb.På sådan en "super

#7: Nb.

På sådan en "super maskine", vil det ikke tage mere end 15 min. at installere en pclinuxos64-openbox-mini-2019.12.iso, i Virtual Box

og måske udlæse temperaturen.

Virtuelle guest maskiner er ikke hardware installerede og kan derfor ikke læse hardwarens temperatur sensore, så den går ikke. De skal vises fra host.

k10temp er nogle gange refereret som temp1 i fx GkrellM på AMD processore, også på gamle computere og ældre kerner som 4.15

Eksempel fra en oldsag (gammel HP ProBook - AMD - Linux Mint 19.2 64bit), hvor der ingen virtuelle PC programmer er installeret:

administrator@ProBook:~$ sensors

k10temp-pci-00c3

Adapter: PCI adapter

temp1: +41.2°C (high = +70.0°C)

(crit = +100.0°C, hyst = +99.0°C)

acpitz-virtual-0

Adapter: Virtual device

temp1: +41.0°C (crit = +128.0°C)

temp2: +0.0°C (crit = +128.0°C)

temp3: +32.0°C (crit = +128.0°C)

temp4: +38.0°C (crit = +128.0°C)

temp5: +20.0°C (crit = +128.0°C)

radeon-pci-0008

Adapter: PCI adapter

temp1: +42.0°C (crit = +120.0°C, hyst = +90.0°C)

For en ordens skyld på samme maskine:

lsmod | grep k10temp

k10temp 16384 0

Log in to post comments

Virtuelle guest maskiner er

Virtuelle guest maskiner er ikke hardware installerede og kan derfor ikke læse hardwarens temperatur sensore, så den går ikke. De skal vises fra host.

Det har du desværre ret i, frogmaster.

Der er ingen "katte-lem" indbygget.

Log in to post comments

Kernel 5.4.6

Hej Frogmaster og osjensen

Jeg har prøvet "lsmod | greb k10temp" (note 1) som giver intet brugbart resultat og selvom jeg bytter b ud med p giver maskinen mig stadig intet svar. Og tilbage til opdateringen af kernel fra 4.19.0-6-amd64 (kørene i debian 10) til 5.4.6 LINK.

Jeg har fundet LINKet, men jeg ved ik om "linux-5.4.6.tar.xz"-filen jeg har hentet ned er til 64bit, for jeg får godt nok mange fejlmeddelser, for "-amd64" ref til 64bit.

Tænker lidt på at jeg nok bliver nød til at lave en reinstallation af debian 10, for jeg har nok klokket for meget rundt i det. Jeg har i (note 2) gengivet hvad jeg har fået af svar i terminalen på de kommandoer som jeg har fået i LINKet.

Men det der lidt af en øjenåbner for øjeblikket er de muligheder der ligger i gcc eller linux, som der ik var i m$Windows. Jeg skal bare lære at mestre det!

/allan

PS: Jeg prøver mig virkelig frem for øjeblikket og skulle nok lade være, men jeg vil så gerne have den temperatur fra cpu'en (for øjeblikket kører jeg på "gnome-system-monitor" der viser cpu-belastningen der oversat ref til varmen i cpu'en.

1)

allan@debian:~$ lsmod | greb k10temp bash: greb: command not found allan@debian:~$ lsmod | grep k10temp allan@debian:~$ uname -r 4.19.0-6-amd64

2)

allan@debian:~$ cp -v /boot/config-$(uname -r) .config '/boot/config-4.19.0-6-amd64' -> '.config/config-4.19.0-6-amd64' allan@debian:~$ cd linux-5.4.6/ allan@debian:~/linux-5.4.6$ make gconfig HOSTCC scripts/basic/fixdep * * 'make gconfig' requires 'pkg-config'. Please install it. * make[1]: *** [scripts/kconfig/Makefile:208: scripts/kconfig/gconf-cfg] Error 1 make: *** [Makefile:567: gconfig] Error 2 allan@debian:~/linux-5.4.6$ make menuconfig * * Unable to find the ncurses package. * Install ncurses (ncurses-devel or libncurses-dev * depending on your distribution). * make[1]: *** [scripts/kconfig/Makefile:208: scripts/kconfig/mconf-cfg] Error 1 make: *** [Makefile:567: menuconfig] Error 2 allan@debian:~/linux-5.4.6$ gcc --version gcc (Debian 8.3.0-6) 8.3.0 Copyright (C) 2018 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. allan@debian:~/linux-5.4.6$ make -j $(nproc) *** *** Configuration file ".config" not found! *** *** Please run some configurator (e.g. "make oldconfig" or *** "make menuconfig" or "make xconfig"). *** make: *** [Makefile:669: .config] Error 1 allan@debian:~/linux-5.4.6$ make pkg-config make[1]: *** No rule to make target 'pkg-config'. Stop. make: *** [Makefile:567: pkg-config] Error 2 allan@debian:~/linux-5.4.6$ sudo make pkg-config [sudo] password for allan: make[1]: *** No rule to make target 'pkg-config'. Stop. make: *** [Makefile:567: pkg-config] Error 2 allan@debian:~/linux-5.4.6$ make xconfig HOSTCC scripts/kconfig/images.o HOSTCC scripts/kconfig/confdata.o HOSTCC scripts/kconfig/expr.o LEX scripts/kconfig/lexer.lex.c /bin/sh: 1: flex: not found make[1]: *** [scripts/Makefile.host:9: scripts/kconfig/lexer.lex.c] Error 127 make: *** [Makefile:567: xconfig] Error 2 allan@debian:~/linux-5.4.6$ cd.. bash: cd..: command not found allan@debian:~/linux-5.4.6$ cd .. allan@debian:~$ make pkg-config make: *** No rule to make target 'pkg-config'. Stop. allan@debian:~$ make menuconfig make: *** No rule to make target 'menuconfig'. Stop. allan@debian:~$ cd linux-5.4.6/ allan@debian:~/linux-5.4.6$ make -j $(nproc) *** *** Configuration file ".config" not found! *** *** Please run some configurator (e.g. "make oldconfig" or *** "make menuconfig" or "make xconfig"). *** make: *** [Makefile:669: .config] Error 1 allan@debian:~/linux-5.4.6$ cp -v /boot/config-$(uname -r) .config '/boot/config-4.19.0-6-amd64' -> '.config' allan@debian:~/linux-5.4.6$ make menuconfig * * Unable to find the ncurses package. * Install ncurses (ncurses-devel or libncurses-dev * depending on your distribution). * make[1]: *** [scripts/kconfig/Makefile:208: scripts/kconfig/mconf-cfg] Error 1 make: *** [Makefile:567: menuconfig] Error 2 allan@debian:~/linux-5.4.6$ make -j $(nproc) HOSTCC scripts/kconfig/conf.o LEX scripts/kconfig/lexer.lex.c /bin/sh: 1: flex: not found YACC scripts/kconfig/parser.tab.[ch] make[2]: *** [scripts/Makefile.host:9: scripts/kconfig/lexer.lex.c] Error 127 /bin/sh: 1: bison: not found make[2]: *** Waiting for unfinished jobs.... make[2]: *** [scripts/Makefile.host:17: scripts/kconfig/parser.tab.h] Error 127 HOSTCC scripts/kconfig/preprocess.o make[1]: *** [Makefile:567: syncconfig] Error 2 make: *** [Makefile:678: include/config/auto.conf.cmd] Error 2 allan@debian:~/linux-5.4.6$ make LEX scripts/kconfig/lexer.lex.c /bin/sh: 1: flex: not found make[2]: *** [scripts/Makefile.host:9: scripts/kconfig/lexer.lex.c] Error 127 make[1]: *** [Makefile:567: syncconfig] Error 2 Makefile:660: include/config/auto.conf.cmd: No such file or directory make: *** [Makefile:678: include/config/auto.conf.cmd] Error 2 allan@debian:~/linux-5.4.6$ sudo make modules_install [sudo] password for allan: ERROR: Kernel configuration is invalid. include/generated/autoconf.h or include/config/auto.conf are missing. Run 'make oldconfig && make prepare' on kernel src to fix it. Makefile:613: include/config/auto.conf: No such file or directory make: *** [Makefile:686: include/config/auto.conf] Error 1 allan@debian:~/linux-5.4.6$ sudo make install ERROR: Kernel configuration is invalid. include/generated/autoconf.h or include/config/auto.conf are missing. Run 'make oldconfig && make prepare' on kernel src to fix it. Makefile:613: include/config/auto.conf: No such file or directory make: *** [Makefile:686: include/config/auto.conf] Error 1 allan@debian:~/linux-5.4.6$ uname -r 4.19.0-6-amd64 allan@debian:~/linux-5.4.6$ sudo update-initramfs -c -k $(uname -r) update-initramfs: Generating /boot/initrd.img-4.19.0-6-amd64 W: Possible missing firmware /lib/firmware/nvidia/gp100/gr/sw_method_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp100/gr/sw_bundle_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp100/gr/sw_nonctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp100/gr/sw_ctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp100/gr/gpccs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp100/gr/gpccs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp100/gr/gpccs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp100/gr/gpccs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp100/gr/fecs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp100/gr/fecs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp100/gr/fecs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp100/gr/fecs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp100/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp100/acr/ucode_load.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp100/acr/bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/sw_method_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/sw_bundle_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/sw_nonctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/sw_ctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/gpccs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/gpccs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/gpccs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/gpccs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/fecs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/fecs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/fecs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/fecs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm206/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm206/acr/ucode_load.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm206/acr/bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm204/gr/sw_method_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm204/gr/sw_bundle_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm204/gr/sw_nonctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm204/gr/sw_ctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm204/gr/gpccs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm204/gr/gpccs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm204/gr/gpccs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm204/gr/gpccs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm204/gr/fecs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm204/gr/fecs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm204/gr/fecs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm204/gr/fecs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm204/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm204/acr/ucode_load.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm204/acr/bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm200/gr/sw_method_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm200/gr/sw_bundle_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm200/gr/sw_nonctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm200/gr/sw_ctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm200/gr/gpccs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm200/gr/gpccs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm200/gr/gpccs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm200/gr/gpccs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm200/gr/fecs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm200/gr/fecs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm200/gr/fecs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm200/gr/fecs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm200/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm200/acr/ucode_load.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm200/acr/bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/sec2/sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/sec2/image.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/sec2/desc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/nvdec/scrubber.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/sw_method_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/sw_bundle_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/sw_nonctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/sw_ctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/gpccs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/gpccs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/gpccs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/gpccs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/fecs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/fecs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/fecs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/fecs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/acr/ucode_load.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/acr/unload_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/acr/bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/sec2/sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/sec2/image.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/sec2/desc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/nvdec/scrubber.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/gr/sw_method_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/gr/sw_bundle_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/gr/sw_nonctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/gr/sw_ctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/gr/gpccs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/gr/gpccs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/gr/gpccs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/gr/gpccs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/gr/fecs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/gr/fecs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/gr/fecs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/gr/fecs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/acr/ucode_load.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/acr/unload_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/acr/bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp104/sec2/sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp104/sec2/image.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp104/sec2/desc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp104/nvdec/scrubber.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp104/gr/sw_method_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp104/gr/sw_bundle_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp104/gr/sw_nonctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp104/gr/sw_ctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp104/gr/gpccs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp104/gr/gpccs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp104/gr/gpccs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp104/gr/gpccs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp104/gr/fecs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp104/gr/fecs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp104/gr/fecs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp104/gr/fecs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp104/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp104/acr/ucode_load.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp104/acr/unload_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp104/acr/bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp102/sec2/sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp102/sec2/image.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp102/sec2/desc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp102/nvdec/scrubber.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp102/gr/sw_method_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp102/gr/sw_bundle_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp102/gr/sw_nonctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp102/gr/sw_ctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp102/gr/gpccs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp102/gr/gpccs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp102/gr/gpccs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp102/gr/gpccs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp102/gr/fecs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp102/gr/fecs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp102/gr/fecs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp102/gr/fecs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp102/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp102/acr/ucode_load.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp102/acr/unload_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp102/acr/bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/image.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/desc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/nvdec/scrubber.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_method_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_bundle_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_nonctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_ctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/ucode_load.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/unload_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/sec2/sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/sec2/image.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/sec2/desc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/nvdec/scrubber.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/gr/sw_method_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/gr/sw_bundle_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/gr/sw_nonctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/gr/sw_ctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/gr/gpccs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/gr/gpccs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/gr/gpccs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/gr/gpccs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/gr/fecs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/gr/fecs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/gr/fecs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/gr/fecs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/acr/ucode_load.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/acr/unload_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/acr/bl.bin for module nouveau allan@debian:~/linux-5.4.6$ uname -r 4.19.0-6-amd64 allan@debian:~/linux-5.4.6$ reboot bash: reboot: command not found allan@debian:~/linux-5.4.6$ sudo reboot allan@debian:~$ uname -mrs Linux 4.19.0-6-amd64 x86_64 allan@debian:~$

Log in to post comments

Tænker lidt på at jeg

#10: Tænker lidt på at jeg nok bliver nød til at lave en reinstallation af debian 10, for jeg har nok klokket for meget rundt i det.

Det er muligt, kender det godt, men jeg vil alligevel gentage at du formentligt bruger for megen tid på visningen af de sensorer. Så vigtigt er det altså ikke.

Det vigtige er at hardwarens termostater slukker maskinen hvis den overophedes.

Sker det, så er der noget helt andet, og meget mere alvorligt i vejen, som gentaget, OS problemer med drivere til hardwaren eller installation af kørende inkompatible tjenester (baggrundsprogrammer) eller forgrundsprogrammer.

Oplever du overophedning?

Log in to post comments

Modelering ifb gcc

Hej Frogmaster

Jeg har lavet en tilføjelse til #10 som jeg gengiver herunder.

#10: Men det der lidt af en øjenåbner for øjeblikket er de muligheder der ligger i gcc eller linux, som der ik var i m$Windows. Jeg skal bare lære at mestre det!

Men du har nok ret mht overophedning af maskinen.

/allan

Log in to post comments

#10Bare for at runde af

#10

Bare for at runde af -

k10temp er ikke indlæst -

så du meddelelsen tidligere

To load everything that is needed, add this to /etc/modules:

#----cut here----

# Chip drivers

k10temp

#----cut here----

Som root indlæs k10temp med -

# modprobe k10temp # lsmod | grep k10temp

så ser du sikkert

k10temp 16384 0

Prøv så igen

sensors-detect --auto

og

sensors

Ser du nu -

temp1 temperatur

eller flere

Core X temp. angivet.

Log in to post comments

Hvis ikke maskinen bliver

Hvis ikke maskinen bliver overophedet, så er sensore-visning irrelevant i henhold i funktionalitet. Det er pointen.

Noget andet kan være at nye OS, på ny hardware, skal have ny opdateret software for at kunne vise fx temperaturen. Sådan har det altid været.

Visning af temperaturen og termostaters maskine-nedlukning er to forskellige ting.

Igen, hvis maskinen føles kølig når du rører på den, så er den formentlig okay ...

Log in to post comments

Jeg tolker det som, at bot1

Jeg tolker det som, at 1bot øver sig, dygtiggør sig og prøver sig frem, - som han selv siger, "lidt af en øjenåbner for øjeblikket er de muligheder der ligger i gcc eller linux, som der ik var i m$Windows. Jeg skal bare lære at mestre det!"

Det tolker jeg som, at han øver sig og er overvældet over mulighederne og friheden ved Linux, og er nysgerrig og gerne vil lære en hel masse om det, - og så skal man jo starte et sted, hvorved det så er lm-sensors han har kastet sin opmærksomhed på, også selvom maskinen slet ikke bliver for varm. For så er det en øvelse i sig selv, at lære conky og lm-sensors og senere andre programmer, og funktioner og dele af Linux, at kende, for så til sidst, at mestre det så godt, at han får fuld kontrol og bliver dygtig til det.

Jeg har selv været der, så jeg kan relatere til det, at ville kaste min opmærksomhed på en funktionalitet, eller et stykke software, som egentlig ikke tjener mig andet formål, end at lære noget nyt.

Log in to post comments

Hej OracleJMT
TAK FOR DE

Hej OracleJMT

TAK FOR DE PÆNE ORD!!

/allan

Log in to post comments

Velbekomme, og forsinket

Velbekomme, og forsinket glædelig jul. :-)

Log in to post comments

Hej igen OracleJMT
Tak og i

Hej igen OracleJMT

Tak og i lige måde, og god nytår som jo er meget snart.

/allan

Log in to post comments

Tak i lige måde, Allan. Jeg

Tak i lige måde, Allan. Jeg følger tråden her, så du spørger bare, så vil vi hjælpe dig videre efter bedste evne. :-)

Log in to post comments

GENNEMBRUDET!!

Hej igen herinde

Jeg har her idag lavet en google-søgning på "upgrade linux kernel amd64 on debian buster" LINKet til søgningen og fundet en kort youtube-video omkring opgrading af kernel'en i debian buster.

Her er youtubeLINKet til videoen på 1min32sek og den opgrader kernel'en fra 4.19.0-6-amd64 til 5.3.0-0.bpo.2-amd64.

Følgende kommando fra videoen er (og se min note 1):

This video will show you how to easily upgrade your Linux Kernel on Debian 10 Buster. Commands used in this video: uname -r sudo nano /etc/apt/sources.list - Add this line: "deb http://deb.debian.org/debian buster-backports main" sudo apt update sudo apt -t buster-backports install linux-image-amd64 sudo reboot

Jeg har så kørt en "sudo sensors-detect --auto" (se note 2) derefter og derefter kommandoen "sensors" og "watch sensors" (se note 3), og selvom det ik er en kernel 5.4, men en 5.3 er cpu-temperaturen fanget, som kan ses i note 3 vha "Tdie og Tctl".

Jeg er ik klar over om 5.3.0-0.bpo.2-amd64 er til den ustabile debian (SID), men det er der måske nogen der kan fortælle mig??

Summa summa rum er i hvert tilfælde at jeg har fået cpu-temperaturen i lm-sensors og derved også gengivet i psensor og igen i de fleste temperaturprogrammer som eks gkrellm, conky mfl. Og det takket være jer, men det nager mig stadig lidt at jeg ik er kommet op på en kernel 5.4.6.

TAK FOR HJÆLPEN!!

note 1)

allan@debian:~$ uname -r 4.19.0-6-amd64 allan@debian:~$ sudo nano /etc/apt/sources.list [sudo] password for allan: allan@debian:~$ sudo apt update Get:1 http://security.debian.org/debian-security buster/updates InRelease [65,4 kB] Get:2 http://security.debian.org/debian-security buster/updates/main Sources [96,5 kB] Get:3 http://security.debian.org/debian-security buster/updates/main amd64 Packages [167 kB] Get:4 http://security.debian.org/debian-security buster/updates/main Translation-en [87,2 kB] Hit:5 http://deb.debian.org/debian buster InRelease Get:6 http://deb.debian.org/debian buster-updates InRelease [49,3 kB] Get:7 http://deb.debian.org/debian buster-backports InRelease [46,7 kB] Get:8 http://deb.debian.org/debian buster-backports/main amd64 Packages [158 kB] Get:9 http://deb.debian.org/debian buster-backports/main Translation-en [133 kB] Fetched 804 kB in 2s (382 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. allan@debian:~$ sudo apt -t buster-backports install linux-image-amd64 Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: linux-image-5.3.0-0.bpo.2-amd64 Suggested packages: linux-doc-5.3 debian-kernel-handbook The following NEW packages will be installed: linux-image-5.3.0-0.bpo.2-amd64 The following packages will be upgraded: linux-image-amd64 1 upgraded, 1 newly installed, 0 to remove and 90 not upgraded. Need to get 48,9 MB of archives. After this operation, 276 MB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://deb.debian.org/debian buster-backports/main amd64 linux-image-5.3.0-0.bpo.2-amd64 amd64 5.3.9-2~bpo10+1 [48,9 MB] Get:2 http://deb.debian.org/debian buster-backports/main amd64 linux-image-amd64 amd64 5.3.9-2~bpo10+1 [1.448 B] Fetched 48,9 MB in 23s (2.114 kB/s) Reading changelogs... Done Selecting previously unselected package linux-image-5.3.0-0.bpo.2-amd64. (Reading database ... 106779 files and directories currently installed.) Preparing to unpack .../linux-image-5.3.0-0.bpo.2-amd64_5.3.9-2~bpo10+1_amd64.deb ... Unpacking linux-image-5.3.0-0.bpo.2-amd64 (5.3.9-2~bpo10+1) ... Preparing to unpack .../linux-image-amd64_5.3.9-2~bpo10+1_amd64.deb ... Unpacking linux-image-amd64 (5.3.9-2~bpo10+1) over (4.19+105+deb10u1) ... Setting up linux-image-5.3.0-0.bpo.2-amd64 (5.3.9-2~bpo10+1) ... I: /vmlinuz is now a symlink to boot/vmlinuz-5.3.0-0.bpo.2-amd64 I: /initrd.img is now a symlink to boot/initrd.img-5.3.0-0.bpo.2-amd64 /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-5.3.0-0.bpo.2-amd64 W: Possible missing firmware /lib/firmware/nvidia/gp100/gr/sw_method_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp100/gr/sw_bundle_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp100/gr/sw_nonctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp100/gr/sw_ctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp100/gr/gpccs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp100/gr/gpccs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp100/gr/gpccs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp100/gr/gpccs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp100/gr/fecs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp100/gr/fecs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp100/gr/fecs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp100/gr/fecs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp100/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp100/acr/ucode_load.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp100/acr/bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/sw_method_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/sw_bundle_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/sw_nonctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/sw_ctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/gpccs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/gpccs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/gpccs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/gpccs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/fecs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/fecs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/fecs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/fecs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm206/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm206/acr/ucode_load.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm206/acr/bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm204/gr/sw_method_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm204/gr/sw_bundle_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm204/gr/sw_nonctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm204/gr/sw_ctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm204/gr/gpccs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm204/gr/gpccs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm204/gr/gpccs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm204/gr/gpccs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm204/gr/fecs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm204/gr/fecs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm204/gr/fecs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm204/gr/fecs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm204/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm204/acr/ucode_load.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm204/acr/bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm200/gr/sw_method_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm200/gr/sw_bundle_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm200/gr/sw_nonctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm200/gr/sw_ctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm200/gr/gpccs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm200/gr/gpccs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm200/gr/gpccs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm200/gr/gpccs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm200/gr/fecs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm200/gr/fecs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm200/gr/fecs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm200/gr/fecs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm200/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm200/acr/ucode_load.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm200/acr/bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/sec2/sig-1.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/sec2/image-1.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/sec2/desc-1.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/sec2/sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/sec2/image.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/sec2/desc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/nvdec/scrubber.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/sw_method_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/sw_bundle_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/sw_nonctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/sw_ctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/gpccs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/gpccs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/gpccs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/gpccs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/fecs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/fecs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/fecs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/gr/fecs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/acr/ucode_load.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/acr/unload_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp107/acr/bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/sec2/sig-1.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/sec2/image-1.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/sec2/desc-1.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/sec2/sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/sec2/image.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/sec2/desc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/nvdec/scrubber.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/gr/sw_method_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/gr/sw_bundle_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/gr/sw_nonctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/gr/sw_ctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/gr/gpccs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/gr/gpccs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/gr/gpccs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/gr/gpccs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/gr/fecs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/gr/fecs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/gr/fecs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/gr/fecs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/acr/ucode_load.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/acr/unload_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp106/acr/bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp104/sec2/sig-1.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp104/sec2/image-1.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp104/sec2/desc-1.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp104/sec2/sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp104/sec2/image.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp104/sec2/desc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp104/nvdec/scrubber.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp104/gr/sw_method_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp104/gr/sw_bundle_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp104/gr/sw_nonctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp104/gr/sw_ctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp104/gr/gpccs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp104/gr/gpccs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp104/gr/gpccs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp104/gr/gpccs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp104/gr/fecs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp104/gr/fecs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp104/gr/fecs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp104/gr/fecs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp104/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp104/acr/ucode_load.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp104/acr/unload_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp104/acr/bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp102/sec2/sig-1.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp102/sec2/image-1.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp102/sec2/desc-1.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp102/sec2/sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp102/sec2/image.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp102/sec2/desc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp102/nvdec/scrubber.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp102/gr/sw_method_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp102/gr/sw_bundle_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp102/gr/sw_nonctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp102/gr/sw_ctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp102/gr/gpccs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp102/gr/gpccs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp102/gr/gpccs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp102/gr/gpccs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp102/gr/fecs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp102/gr/fecs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp102/gr/fecs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp102/gr/fecs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp102/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp102/acr/ucode_load.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp102/acr/unload_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp102/acr/bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/image.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/sec2/desc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/nvdec/scrubber.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_method_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_bundle_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_nonctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/sw_ctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/gpccs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/gr/fecs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/ucode_load.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/unload_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/sec2/sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/sec2/image.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/sec2/desc.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/nvdec/scrubber.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/gr/sw_method_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/gr/sw_bundle_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/gr/sw_nonctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/gr/sw_ctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/gr/gpccs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/gr/gpccs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/gr/gpccs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/gr/gpccs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/gr/fecs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/gr/fecs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/gr/fecs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/gr/fecs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/acr/ucode_load.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/acr/unload_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gp108/acr/bl.bin for module nouveau /etc/kernel/postinst.d/zz-update-grub: Generating grub configuration file ... Found background image: /usr/share/images/desktop-base/desktop-grub.png Found linux image: /boot/vmlinuz-5.3.0-0.bpo.2-amd64 Found initrd image: /boot/initrd.img-5.3.0-0.bpo.2-amd64 Found linux image: /boot/vmlinuz-4.19.0-6-amd64 Found initrd image: /boot/initrd.img-4.19.0-6-amd64 Adding boot menu entry for EFI firmware configuration done Setting up linux-image-amd64 (5.3.9-2~bpo10+1) ... allan@debian:~$ sudo reboot allan@debian:~$ uname -r 5.3.0-0.bpo.2-amd64

note 2)

allan@debian:~$ sudo sensors-detect --auto [sudo] password for allan: # sensors-detect version 3.6.0 # Board: ASUSTeK COMPUTER INC. PRIME X370-PRO # Kernel: 5.3.0-0.bpo.2-amd64 x86_64 # Processor: AMD Ryzen 9 3900X 12-Core Processor (23/113/0) Running in automatic mode, default answers to all questions are assumed. Some south bridges, CPUs or memory controllers contain embedded sensors. Do you want to scan for them? This is totally safe. (YES/no): Module cpuid loaded successfully. Silicon Integrated Systems SIS5595... No VIA VT82C686 Integrated Sensors... No VIA VT8231 Integrated Sensors... No AMD K8 thermal sensors... No AMD Family 10h thermal sensors... No AMD Family 11h thermal sensors... No AMD Family 12h and 14h thermal sensors... No AMD Family 15h thermal sensors... No AMD Family 16h thermal sensors... No AMD Family 17h thermal sensors... Success! (driver `k10temp') AMD Family 15h power sensors... No AMD Family 16h power sensors... No Hygon Family 18h thermal sensors... No Intel digital thermal sensor... No Intel AMB FB-DIMM thermal sensor... No Intel 5500/5520/X58 thermal sensor... No VIA C7 thermal sensor... No VIA Nano thermal sensor... No Some Super I/O chips contain embedded sensors. We have to write to standard I/O ports to probe them. This is usually safe. Do you want to scan for Super I/O sensors? (YES/no): Probing for Super-I/O at 0x2e/0x2f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... Yes Found `ITE IT8665E Super IO Sensors' Success! (address 0x290, driver `to-be-written') Probing for Super-I/O at 0x4e/0x4f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... No Some systems (mainly servers) implement IPMI, a set of common interfaces through which system health data may be retrieved, amongst other things. We first try to get the information from SMBIOS. If we don't find it there, we have to read from arbitrary I/O ports to probe for such interfaces. This is normally safe. Do you want to scan for IPMI interfaces? (YES/no): Probing for `IPMI BMC KCS' at 0xca0... No Probing for `IPMI BMC SMIC' at 0xca8... No Some hardware monitoring chips are accessible through the ISA I/O ports. We have to write to arbitrary I/O ports to probe them. This is usually safe though. Yes, you do have ISA I/O ports even if you do not have any ISA slots! Do you want to scan the ISA I/O ports? (yes/NO): Lastly, we can probe the I2C/SMBus adapters for connected hardware monitoring devices. This is the most risky part, and while it works reasonably well on most systems, it has been reported to cause trouble on some systems. Do you want to probe the I2C/SMBus adapters now? (YES/no): Using driver `i2c-piix4' for device 0000:00:14.0: AMD KERNCZ SMBus Module i2c-dev loaded successfully. Next adapter: SMBus PIIX4 adapter port 0 at 0b00 (i2c-0) Do you want to scan it? (YES/no/selectively): Client found at address 0x50 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... Yes (confidence 8, not a hardware monitoring chip) Probing for `EDID EEPROM'... No Client found at address 0x51 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... Yes (confidence 8, not a hardware monitoring chip) Client found at address 0x52 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... Yes (confidence 8, not a hardware monitoring chip) Client found at address 0x53 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... Yes (confidence 8, not a hardware monitoring chip) Next adapter: SMBus PIIX4 adapter port 2 at 0b00 (i2c-1) Do you want to scan it? (YES/no/selectively): Next adapter: SMBus PIIX4 adapter port 3 at 0b00 (i2c-2) Do you want to scan it? (YES/no/selectively): Next adapter: SMBus PIIX4 adapter port 4 at 0b00 (i2c-3) Do you want to scan it? (YES/no/selectively): Next adapter: nvkm-0000:0a:00.0-bus-0000 (i2c-4) Do you want to scan it? (yes/NO/selectively): Next adapter: nvkm-0000:0a:00.0-bus-0001 (i2c-5) Do you want to scan it? (yes/NO/selectively): Next adapter: nvkm-0000:0a:00.0-bus-0002 (i2c-6) Do you want to scan it? (yes/NO/selectively): Next adapter: nvkm-0000:0a:00.0-bus-0005 (i2c-7) Do you want to scan it? (yes/NO/selectively): Next adapter: nvkm-0000:0a:00.0-bus-0006 (i2c-8) Do you want to scan it? (yes/NO/selectively): Next adapter: nvkm-0000:0a:00.0-bus-0007 (i2c-9) Do you want to scan it? (yes/NO/selectively): Next adapter: nvkm-0000:0a:00.0-bus-0008 (i2c-10) Do you want to scan it? (yes/NO/selectively): Next adapter: nvkm-0000:0a:00.0-bus-0009 (i2c-11) Do you want to scan it? (yes/NO/selectively): Next adapter: nvkm-0000:0a:00.0-aux-000a (i2c-12) Do you want to scan it? (yes/NO/selectively): Next adapter: nvkm-0000:0a:00.0-aux-000b (i2c-13) Do you want to scan it? (yes/NO/selectively): Next adapter: nvkm-0000:0a:00.0-aux-000c (i2c-14) Do you want to scan it? (yes/NO/selectively): Next adapter: nvkm-0000:0a:00.0-aux-000d (i2c-15) Do you want to scan it? (yes/NO/selectively): Now follows a summary of the probes I have just done. Driver `k10temp' (autoloaded): * Chip `AMD Family 17h thermal sensors' (confidence: 9) Driver `to-be-written': * ISA bus, address 0x290 Chip `ITE IT8665E Super IO Sensors' (confidence: 9) Note: there is no driver for ITE IT8665E Super IO Sensors yet. Check https://hwmon.wiki.kernel.org/device_support_status for updates. No modules to load, skipping modules configuration. Unloading i2c-dev... OK Unloading cpuid... OK

note 3)

allan@debian:~$ sensors asus-isa-0000 Adapter: ISA adapter cpu_fan: 0 RPM nouveau-pci-0a00 Adapter: PCI adapter GPU core: 912.00 mV (min = +0.80 V, max = +1.19 V) temp1: +41.0°C (high = +95.0°C, hyst = +3.0°C) (crit = +105.0°C, hyst = +5.0°C) (emerg = +135.0°C, hyst = +5.0°C) k10temp-pci-00c3 Adapter: PCI adapter Tdie: +24.2°C (high = +70.0°C) Tctl: +24.2°C

Log in to post comments

Hej igen igen.
I

Hej igen igen.

I forlængelse af min note 3 i #20, undre mig lidt at Tdie og Tctl er ens, burde de ik være forskellige??

/allan

Log in to post comments

Du kan også bare bruge

Du kan også bare bruge Fedora Xfce, som jeg gør. Der får du altid de nyeste pakker. Den er mere stabil end Debian Unstable, men skal opgraderes til et nyt versionsnummer hvert halve år. Ellers er der løbende opdateringer til de seneste pakker imellem de halvårlige versioner.

Log in to post comments

Hej OracleJMTDet vil jeg

Hej OracleJMT

Det vil jeg godt lige tænke over det mht Fedora xfce.

Hvad ved du om mxLinux??

/allan

Log in to post comments

Det vil jeg godt lige

Det vil jeg godt lige tænke over det mht Fedora xfce.Hvad ved du om mxLinux??

At det er Debian Stable med sysvinit i stedet for systemd, og lidt hjælpeværktøjer og en nem grafisk installer og en special-tilpasset Xfce.

Log in to post comments

Hej OracleJMT
Jeg ved at

Hej OracleJMT

Jeg ved at fodora havde problemer mht ryzen tredie generation (det var omkring relase sommeren 2019) og noget jeg kom til at tænke på efter at jeg havde skrevet mit sit indlæg #23.

/allan

Log in to post comments

Ja, men Fedora 31 benytter

Ja, men Fedora 31 benytter kernel 5.3, og om lidt kernel 5.4, når den kommer ud (pakker bliver løbende opdateret) så den skulle være god nok nu i forhold til understøttelse af lm-sensors for din hardware.

Log in to post comments

Hej AllanDu kunne jo også

Hej Allan

Du kunne jo også overveje openSUSE, der ved du jo at det virker med en Zen2 cpu, og de gamle kerner får jo backported opdateringer og rettelser.

Mit bundkort har også nyre chipset B450, så hvis du vil prøve forskellige vil jeg forslå openSUSE Leap med kde.

Log in to post comments

en lille opdatering...

Hej igen

Min ryzen3900x (psensor) siger Tdie&Tctl er min 25cDegrees og max 52c, så det passer nok meget godt når Frogmaster (indlæg #11) siger jeg spilder min tid med at få temp-data fra cpu'en.

Jeg har læst mig til at debian fraråder folk at opdatere sin kernel fra kernel.org pga manglende opdateringer ifm egne compilering af kernel og så har jeg ik kommet frem til en succefuldt kernel-opdatering fra kernel.org endnu, selvom jeg har fuldt instrukserne vha LINKet og installeret debian10 på virtuelbox. Jeg har også prøvet at finde nogle youtube-videoer omkring emnet, men det har heller ik hjulpet. Den eneste video som har hjulpet er LINKet som jeg tidligere har ref til (indlæg #20) og jeg ved ik om "5.3.0-0.bpo.2-amd" er en "sid" (ustabil) opdatering, men den virker mht at se cpu-temperaturen via psensor.

Jeg er ik helt afklaret endnu mht hvilke OS jeg skal kører på hovedmaskinen, om det bliver debian, PClinuxOS eller arch. Men efter at bedømme på distrowatch.com er det enten arch eller PClinuxOS pga kernel'en (men det virker fint nok på nuvæende tidspunkt mht debian og kernel 5.3.0-0.bpo-2).

Jeg har lidt svært ved at forstår hvorfor cpu-temperaturen skal splittes op i Tdie og Tctl (min og max er blot dobbelt i psensor, så Tdie og Tctl er ens), når det er samme tal, men det kan I måske hjælpe med??

/allan ;o))

Log in to post comments

Eller Fedora eller Opensuse

Eller Fedora eller Opensuse tumbleweed. Der får du også seneste kerne altid.

Jeg anbefaler Fedora, da den har været meget stabil og professionel på det seneste selvom det får seneste pakker altid.

Log in to post comments

Hej OracleJMTJa den glemte

Hej OracleJMT

Ja den glemte jeg i forvirringen, men den bygger jo på redhat (hvad jeg har set og hørt på youtube), og opensuse har jeg aldrig haft fidus til (selvom jeg startede med suse omkring 90erne før man kunne hente iso-filer på nettet).

Har du noget med freeBSD at gøre??

/allan

Log in to post comments

Hvad er der i vejen med, at

Hvad er der i vejen med, at den er bygget på Red Hat?

Ja, jeg bruger også FreeBSD på en af mine maskiner (som IKKE er Linux)

Hvorfor har du ikke haft fidus til OpenSUSE? Der er så meget du ikke begrunder :-)

Log in to post comments

Hej OracleJMT
Har du nogle

Hej OracleJMT

Har du nogle gode installationsguids til freeBSD??

Kan freeBSD godt kører på amd (ryzen mfl) samt uefi??

Og nej jeg har intet imod at fedora bygge på redhat

/allan

Log in to post comments

Jeg hjælper ikke med

Jeg hjælper ikke med FreeBSD. :-) Nej, FreeBSD har meget begrænset hardwaresupport.

Prøv Fedora. Den er god. Den kan jeg anbefale dig, især nu hvor du siger, at du har brug for seneste kerne. Det er en professionel distribution understøttet af Red Hat. Meget seriøs og mere brugervenlig, end de fleste tror.

Vælg Xfce-versionen.

Log in to post comments

Hvorfor har du ikke

#31: Hvorfor har du ikke haft fidus til OpenSUSE? Der er så meget du ikke begrunder :-)

Så ik dette spørgsmål før nu. Og jeg har nok mere helt mit hoved til debian og opfatet suse som propritær software ligesom redhat.

Jeg har så prøvet kræfter med arch (et par måneder i 2018) med succes, men blev lidt træt af alle de opdateringer der er pga rolling-release (jeg har set på youtube at der kan komme op til tre opdateringer på en dag, men det er først her fornylig at jeg har set at man ik skal opdatere hvert øjeblik, som de fleste nybegyndere gør og jeg også gjorde!!).

/allan

PS: Du spørger bare, hvis der er nogen tvivl omkring hvad jeg skriver, og jeg har selv lagt mærke til at jeg glemmer centrale ord.

Log in to post comments

Prøv Fedora. Den er

#33: Prøv Fedora. Den er god.

JEG TAKKER FOR ANBEFALINGEN, OG VIL PRØVE DEN I VIRTUALBOX.

#33: Jeg hjælper ikke med FreeBSD. :-)

æv, for det er ellers svært stof at forstå, når jeg ser videoer mht freeBSD.

/allan

Log in to post comments

Hvad får du ud af, at

Hvad får du ud af, at prøve den i virtualbox, da er det jo ikke på din rigtige hardware, og derved kan du ikke teste hvordan det kører på din rigtige hardware? :)

Log in to post comments

ja, du har en pointe, men

ja, du har en pointe, men ville se den i aktion og være lidt forberedt før jeg installer den så ik det kommer væltene.

Har du nogen ide om en_dk.utf-8 kan vælges i installationen eller skal det tilpasse i terminalen??

Log in to post comments

Ja, du vælger bare det bare

Ja, du vælger bare det bare i installationen.

Desuden adskiller Fedora Xfce sig kun fra Xubuntu ved, at det er bruger RPM-pakkesystemet i stedet for APT, og er baseret på Red Hat i stedet for Ubuntu/Debian og bruger et andet installationsprogram i live-usb'en; anaconda i stedet for ubiquity.

Ellers er det stadig bare Linux plus GNU plus Xfce.

Log in to post comments

Min ryzen3900x

#28: Min ryzen3900x (psensor) siger Tdie&Tctl er min 25cDegrees og max 52c, så det passer nok meget godt når Frogmaster (indlæg #11) siger jeg spilder min tid med at få temp-data fra cpu'en.

Før eller siden bliver support til visning af temperatur sensore til ryzen CPU implementeret i samtlige LTS Linux.

Indtil da, så er det bare at læne sig tilbage eller bruge sin tid på noget andet, vel og mærke, så længe maskinen ikke overophedes. Så enkelt er det bare.

Log in to post comments

Hej FrogmasterMen

Hej Frogmaster

Men problemmet handlede i ligeså stort omfang om opdatering af kernel'en i debian og hvordan jeg får et github-program til at virke eller viseversa.

Kernel'en i debian kunne jeg ik få til at virke selvom jeg fulgte beskrivelsen LINKet (indlæg #28), og jeg havde installeret gcc compileren.

Men problemmet er ligeså relevant, når jeg sidder med LINKet til siden og gerne vil installere filerne, når en fyr på LINKet til siden kun skriver at filerne bare skal installeres (endsige ifm programmet "conky").

SÅ PROBLEMMET HANDLER OM MEGET ANDET END TEMPERATUR-DATA AF CPU'EN, MEN TAK FOR DIT SVAR I INDLÆG #39!!

/allan

Log in to post comments

Hvis jeg må hjælpe 1bot

Hvis jeg må hjælpe 1bot lidt med at forklare, så kan det have en fordel, at have et system, der er bleeding edge, - eller rolling. Det er der mange der foretrækker, fordi de gerne vil have nye programmer og kernel løbende.

Jeg tror 1bot gerne vil have bedre understøttelse af hans nye hardware, og det klarer Fedora, PCLinuxOS eller Arch bedre, end Debian Stable eller Ubuntu LTS/Mint.

Log in to post comments

Udvikling af mig selv ifm linux

#41: Jeg tror 1bot gerne vil have bedre understøttelse af hans nye hardware, og det klarer Fedora, PCLinuxOS eller Arch bedre, end Debian Stable eller Ubuntu LTS/Mint.

Tak for de fine ord og rigtigheden i det!!

/allan

Log in to post comments

Jeg synes vi skal hjælpe

Jeg synes vi skal hjælpe hinanden. Jeg kan huske da jeg var helt amatør med computere i 00'erne, - da turde jeg ikke engang skrive på et forum.

Så da jeg startede på Linux i 2011 havde jeg meget IT erfaring og erfaring med forums allerede, hvilket gjorde, at det ikke var så slemt for mig.

Log in to post comments

Hej OracleJMT
Når jeg

Hej OracleJMT

Når jeg prøver at installere fedora 31 LINK vil iso-filen gerne installere gnome og ik xfce.

Jeg har fundet kommandoen "sudo dnf group install "Xfce Desktop"" på LINKet til siden, og jeg har prøvet instruktion på LINKet til siden samt installere gnome-knappen uden resultat (jeg har også skrevet føromtalte kommando "sudo dnf group install "Xfce Desktop"" og genstartet uden resultat, som gav sort skærm).

/allan

Log in to post comments

Du skal hente Xfce versionen

Du skal hente Xfce versionen af iso'et.

HER

Log in to post comments

Tak, det giver mening.

#45: Tak, det giver mening. /allan

Log in to post comments

Hej igen og i forlængelse

Hej igen og i forlængelse af #46

For jeg har gået ind på hovedsiden LINK og troede at jeg bare kunne hente en iso-fil, hvor man så valgte sit DEmiljø under installationen.

/allan

Log in to post comments

For jeg har gået ind på

For jeg har gået ind på hovedsiden LINK og troede at jeg bare kunne hente en iso-fil, hvor man så valgte sit DEmiljø under installationen.

Nej, Fedora er en rigtig GNOME-distribution, og Red Hat er en af de helt store bidragere til GNOME skrivebordet. Derfor anses Fedora og RHEL for at være en rigtig GNOME distribution af GNU/Linux.

Når det så er sagt, så er diverse spins, Xfce, KDE osv. rigtigt fine erstatninger i Fedora. Man skal bare lige huske, at hente det iso-spin man skal bruge, hvis man vil undgå bøvl.

Det skyldes Fedora's metode, hvor GNOME har hard dependencies på GNOME-pakker fra start. Det ville kræve sin mand, at få det hele fjernet ordentligt, dernæst få systemd til, at opføre sig ordentligt, dernæst få installeret sit skrivebord med de samme pakker, som der er i det pågældende spin, for så at krydse fingre for, at systemet booter i det hele taget, eller at der ikke er blevet taget vigtige afhængigheder med i farten.

Derfor -----> Hent altid specifikt iso-spin fra start.

Log in to post comments

Jeg takker igen mange gange

Jeg takker igen mange gange for jeg har fået OS'et igang og installeret libreoffice, gnome-system-monitor, nautilus og psensor var lidt sværre at få installeret. Man skulle først skrive kommandoen "sudo dnf copr enable angeldm/psensor" LINK for så dernæst skrive kommandoen "sudo dnf install psensor".

/allan;o))

2 stk Jolla C2 sælges	0
Den er go	0
Vil du have et sikrere og mere privat internet? Du skal blot installere Vivaldi-browseren med Proton VPN understøttelse!	0
14. februar = I Love Free Software Day	0
Lokal fil-deling - for de dovne.	0

Det første forumindlæg efter installation af Forum-modulet	8
Test	1
Vanilla OS	12
Nye forum-indlæg viser sig kun 1 gang	1
Vil alle forumindlæg vise sig to gange	1
Hjælp til remote terminal vindue?	3
PCLinuxOS	19
Kan ikke boote på installation	24
80-20 reglen	1
Skærmlys fader ud på min bærbare	8
32 bit distro på max 700mb der stadig understøttes	26
Har vi nogen Linux konsulenter i Slagelse området?	3
Virkelig	7
gnome-software?	3
Archer T2U AC600 Wireless Dual Band USB Adapter	26
En farverig APT 3.0 udgivelse imponerer med sine nye funktioner	2
Unix's fødsel	2
Linux Mint	13
"Intet realistisk alternativ" - mig i r*ven	1
German state moving 30,000 PCs to LibreOffice	6

Hvad kan du med 100% sikkerhed sige, at du har stemt?

Resultater

Installation af lm-sensors 3.6.0

Kommentarer50

Svar søges

Seneste aktivitet