coreboot August 2018

coreboot@coreboot.org

43 participants
110 discussions

Re: [coreboot] Intel ME what is it? And when did this dangerous thing get installed?
by Youness Alaoui 29 Aug '18

29 Aug '18

I think there's a good explanation of it in the FAQ of the libreboot project here : https://libreboot.org/faq.html#intelme If there are more specific questions that you have, ask them and I might be able to answer them! On Wed, Aug 29, 2018 at 2:36 AM Gregg Levine <gregg.drwho8(a)gmail.com> wrote: > > Hello! > Would one of you, or even any of you please take some time out of your > busy schedule and ponder the subject? And of course try to respond > accordingly? > > Bootguard sadly I am familiar with, but the Intel ME product I confess > I understand a portion about it. And not enough to mention here. > ----- > Gregg C Levine gregg.drwho8(a)gmail.com > "This signature fought the Time Wars, time and again." > > -- > coreboot mailing list: coreboot(a)coreboot.org > https://mail.coreboot.org/mailman/listinfo/coreboot

1 0

Intel ME what is it? And when did this dangerous thing get installed?
by Gregg Levine 29 Aug '18

29 Aug '18

Hello! Would one of you, or even any of you please take some time out of your busy schedule and ponder the subject? And of course try to respond accordingly? Bootguard sadly I am familiar with, but the Intel ME product I confess I understand a portion about it. And not enough to mention here. ----- Gregg C Levine gregg.drwho8(a)gmail.com "This signature fought the Time Wars, time and again."

1 0

Re: [coreboot] T450S + Coreboot
by Nico Huber 28 Aug '18

28 Aug '18

Hi Mike, you can be as much biased as you want, and you can express that here. I have no trouble with that. What I don't like is your choice of words. For instance with "Undoubtedly, Intel ME is a backdoor," you imply to know everybody's opinion on the matter. Because I don't think you are the creator himself, this draws a big WTF? into my brain. You can say "In my opinion, Intel ME is a backdoor, ..." but you can't say it's undoubted. I don't only doubt that, IMHO, it is a frontdoor. You also claim that things are well studied which are not. A replay of a proprietary program might be open-source technically, but it doesn't mean that anybody has a clue how it works. So please, if you want to express your *personal* opinion or "knowledge" please always state so. And don't make it look like the general under- standing (especially not when experts disagree). Nico

2 1

Re: [coreboot] Extracting MRC training data
by Angel Pons 28 Aug '18

28 Aug '18

Hello Anthony, As far as I am concerned, this is expected behavior. The longer first boot time is due to the RAM training process, which is needed because the MRC cache (training data) is empty. Once it has been cached, if the RAM configuration does not change on subsequent boots, the MRC cache is reused, which is faster than retraining. If you dump a flash image, then rewrite it, the end result is that the flash contents have not changed. This implies the MRC cache remains unchanged as well. Since the RAM configuration did not change, the MRC cache is still valid thus it is reused. Regarding the extraction of said data, I believe it could be done, but I would not recommend it. Since this data is specific for a system, generating it anew sounds more reasonable than reusing it. > This Email may contain confidential or privileged information for the intended recipient (s). If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system. This footer makes absolutely no sense when you address a mailing list. I wouldn't be surprised if you get less answers because of it. Best regards, Angel Pons

1 0

Re: [coreboot] x86 SMM handler Local APIC assumptions
by Andrew Cooper 28 Aug '18

28 Aug '18

For a security boundary, the question is "what can an OS potentially do", not "what do we expect it to do". Modification of the APIC_ID register is model specific, but prohibited by the x2APIC spec. I presume that the SMM entry straps disambiguate by the initial APIC ID, which is fixed, but I don't know for sure. Since sending this email, I've come to the conclusion that deriving the stack from the entry strap is probably a safer option than trying to use/parse/modify the APIC. As for x2APIC, any system with >254 cpus needs x2APIC (and Interrupt Remapping) for the OS to be able to perform symmetric interrupt handling, but OSes will turn it on if available, because it has a better programming model (no waiting on status bits), and is easier to virtualise. ~Andrew On 28/08/18 19:37, Lance Zhao wrote: > Without x2apic mode, APIC_ID register will not be moved by OS. Those > address normally had been tagged as reserved and will not be touched. > I believe that x2apic will apply for processors number more than 255, > so majority cases in coreboot didn't touch that area yet. > > > On Tue, Aug 28, 2018 at 7:50 AM Andrew Cooper > <andrew.cooper3(a)citrix.com <mailto:andrew.cooper3@citrix.com>> wrote: > > Hello, > > While looking at some code, I noticed that twice (once in asm, and > again > later in C), the SMM handler assumes that 0xfee00020 is the APIC_ID > reigster in the xAPIC MMIO window. > > This isn't true if the OS has moved the MMIO window, or switched to > x2apic mode (on supporting hardware). > > As a result, it looks like its rather easy to feed a kernel-controlled > value into Coreboot's idea of its Local APIC id, which can either > be the > same on all cores (reuse of the same stack) or wildly out of range > (albeit, at least bounded to 255). > > To fix, I'd expect Coreboot to read MSR_APIC_BASE, and either cope > with > x2apic mode (which is surely easier than switching APIC mode, as > you've > got to cycle through off to switch back to xAPIC mode), or > save/remap/restore the APIC MMIO window. > > Without paging, you can't address an APIC MMIO window above the 4G > boundary. > > Is this something you care about? > > Thanks, > > ~Andrew > > -- > coreboot mailing list: coreboot(a)coreboot.org > <mailto:coreboot@coreboot.org> > https://mail.coreboot.org/mailman/listinfo/coreboot >

1 0

x86 SMM handler Local APIC assumptions
by Andrew Cooper 28 Aug '18

28 Aug '18

Hello, While looking at some code, I noticed that twice (once in asm, and again later in C), the SMM handler assumes that 0xfee00020 is the APIC_ID reigster in the xAPIC MMIO window. This isn't true if the OS has moved the MMIO window, or switched to x2apic mode (on supporting hardware). As a result, it looks like its rather easy to feed a kernel-controlled value into Coreboot's idea of its Local APIC id, which can either be the same on all cores (reuse of the same stack) or wildly out of range (albeit, at least bounded to 255). To fix, I'd expect Coreboot to read MSR_APIC_BASE, and either cope with x2apic mode (which is surely easier than switching APIC mode, as you've got to cycle through off to switch back to xAPIC mode), or save/remap/restore the APIC MMIO window. Without paging, you can't address an APIC MMIO window above the 4G boundary. Is this something you care about? Thanks, ~Andrew

2 1

Re: [coreboot] T450S + Coreboot
by Th3Fanbus . 28 Aug '18

28 Aug '18

Taiidan, > I doubt those guys have the skill to do so but for those who do - you'd > spend tens of thousands in order to have a port for an old machine that > still is stuck with ME and hardware init done entirely by binary blobs. It is not about the skill or money involved in the process, it is about the *possibility* of even running coreboot on said machine, which is most likely zero. > I would save your money and instead buy an ivy/sandybridge thinkpad (can > nerf the ME - but not disable which is impossible) AFAIK, you can still run me_cleaner on a Broadwell laptop. I don't think the ME is the main reason to get a XX20/XX30 Thinkpad over newer models. Mike, > microcode - is optional I assume you refer to microcode *updates*, not the microcode that is hard-coded inside the CPU. Still, I fail to understand why there is so much worry about microcode updates, as if they were going to open a backdoor of some sorts. To me, the only gain of not updating the microcode is in the number of bugs. I do understand temporarily delaying the updates of known unstable microcode versions while awaiting for a fix, though. > as far as I know its impossible to completely replace ME, only to trim > its' firmware as much as possible and hope for the best that it > doesn't have some undocumented "backdoor restore" mechanism that could > restore the original uncut blob under some conditions. Undoubtedly, > Intel ME is a backdoor, e.g. because it contains some antitheft > features which could be used to control your computer remotely: shut > it down, wipe or retrieve data from it, etc This makes me feel I should recall what Nico told you earlier: "please don't spread FUD on this list." Regards, Angel Pons

1 0

Re: [coreboot] coreboot AMD Cards
by kinky_nekoboi 28 Aug '18

28 Aug '18

the output of sudo dmesg | grep invalid is empty.. but as i said i am currently running this board with the stock BIOS/UEFI as it is my main desktop. i have another AMD A8-5500 laying around .. if i can hands on a another testing board i will test this to. as i remembered as i logged in via ssh on the testrun with no graphics output .. the HD7850 was listed in lspci i will update you with more informations when i am able to. Am 28.08.2018 um 16:11 schrieb Mike Banon: > Hi Nekoboi, could you please provide a dmesg kernel log? (after > removing MAC addresses/serial numbers from it) > I wonder if it contains the lines like these below: > amdgpu 0000:04:00.0: Invalid PCI ROM header signature: expecting > 0xaa55, got 0x0000 > [drm:amdgpu_get_bios [amdgpu]] *ERROR* Unable to locate a BIOS ROM > amdgpu 0000:04:00.0: Fatal error during GPU init > ( https://bugs.freedesktop.org/show_bug.cgi?id=101473 ) > > More system info like lspci -v and lspci -tv could be also helpful to > resolve a problem. > Please try to provide as much helpful logs as possible > > Best regards, > Mike Banon > > On Tue, Aug 28, 2018 at 2:29 PM kinky_nekoboi > <kinky_nekoboi(a)bluetardis.de> wrote: >> AFAIK the Hardware init of coreboot is somehow based of the linux kernel ? >> >> As a Deblobed Kernel like in Debian is not able to detect an AMD card >> without Amd microcode.. is Coreboot not able to detect AMD Cards without >> this microcode ? >> >> >> The problem is that i can not get any AMD cards to work with >> coreboot+Seabios on my F2A85M board. >> >> Systeminfo, currently with ASUS UEFI >> >> 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. >> [AMD/ATI] Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP] >> (prog-if 00 [VGA controller]) >> Subsystem: PC Partner Limited / Sapphire Technology Pitcairn PRO >> [Radeon HD 7850 / R7 265 / R9 270 1024SP] >> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- >> Stepping- SERR- FastB2B- DisINTx+ >> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- >> <TAbort- <MAbort- >SERR- <PERR- INTx- >> Latency: 0, Cache Line Size: 64 bytes >> Interrupt: pin A routed to IRQ 43 >> Region 0: Memory at c0000000 (64-bit, prefetchable) [size=256M] >> Region 2: Memory at fea00000 (64-bit, non-prefetchable) [size=256K] >> Region 4: I/O ports at e000 [size=256] >> Expansion ROM at 000c0000 [disabled] [size=128K] >> Capabilities: <access denied> >> Kernel driver in use: amdgpu >> Kernel modules: radeon, amdgpu >> >> >> System: >> Host: thanatos Kernel: 4.17.0-3-amd64 x86_64 bits: 64 compiler: gcc >> v: 7.3.0 Desktop: Cinnamon 3.8.8 dm: lightdm 1.18.3 >> Distro: Debian GNU/Linux buster/sid >> Machine: >> Type: Desktop Mobo: ASUSTeK model: F2A85-M v: Rev X.0x >> serial: <root required> BIOS: American Megatrends v: 6402 date: >> 07/18/2013 >> Memory: >> RAM Report: permissions: Unable to run dmidecode. Are you root? >> PCI Slots: >> Permissions: Unable to run dmidecode. Are you root? >> CPU: >> Topology: Quad Core model: AMD A8-6600K APU with Radeon HD Graphics >> bits: 64 type: MCP arch: Piledriver rev: 1 L2 cache: 2048 KiB >> bogomips: 31355 >> Speed: 1907 MHz min/max: 1900/3900 MHz boost: enabled Core speeds (MHz): >> 1: 1909 2: 1909 3: 1906 4: 1903 >> Flags: 3dnowprefetch abm aes aperfmperf apic arat avx bmi1 clflush cmov >> cmp_legacy constant_tsc cpb cpuid cr8_legacy cx16 cx8 de decodeassists >> extapic extd_apicid f16c flushbyasid fma fma4 fpu fxsr fxsr_opt ht >> hw_pstate ibs lahf_lm lbrv lm lwp mca mce misalignsse mmx mmxext monitor >> msr mtrr nodeid_msr nonstop_tsc nopl npt nrip_save nx osvw pae pat >> pausefilter pclmulqdq pdpe1gb perfctr_core perfctr_nb pfthreshold pge pni >> popcnt pse pse36 rdtscp rep_good sep skinit ssbd sse sse2 sse4_1 sse4_2 >> sse4a ssse3 svm svm_lock syscall tbm tce topoext tsc tsc_scale vmcb_clean >> vme vmmcall wdt xop xsave >> Graphics: >> Card-1: AMD Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP] >> vendor: PC Partner Limited driver: amdgpu v: kernel bus ID: 01:00.0 >> chip ID: 1002:6819 >> Display: x11 server: X.Org 1.20.1 driver: amdgpu,ati >> unloaded: fbdev,modesetting,vesa >> resolution: 1920x1080~60Hz, 1920x1080~60Hz >> OpenGL: renderer: AMD Radeon HD 7800 Series (PITCAIRN DRM 3.25.0 >> 4.17.0-3-amd64 LLVM 6.0.1) >> v: 4.5 Mesa 18.1.6 compat-v: 3.1 direct render: Yes >> Audio: >> Card-1: AMD FCH Azalia vendor: ASUSTeK F2A85-M Series >> driver: snd_hda_intel v: kernel bus ID: 00:14.2 chip ID: 1022:780d >> Card-2: AMD Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series] >> vendor: PC Partner Limited driver: snd_hda_intel v: kernel bus ID: >> 01:00.1 >> chip ID: 1002:aab0 >> Sound Server: ALSA v: k4.17.0-3-amd64 >> Network: >> Card-1: Intel 82571EB Gigabit Ethernet driver: e1000e v: 3.2.6-k >> port: d020 bus ID: 02:00 chip ID: 8086:105e >> IF: enp2s0f0 state: up speed: 1000 Mbps duplex: full >> mac: 00:24:81:7f:47:c0 >> IP v4: 10.0.0.88/24 type: dynamic noprefixroute scope: global >> broadcast: 10.0.0.255 >> IP v6: fe80::224:81ff:fe7f:47c0/64 type: noprefixroute scope: link >> Card-2: Intel 82571EB Gigabit Ethernet driver: e1000e v: 3.2.6-k >> port: d000 bus ID: 02:00.1 chip ID: 8086:105e >> IF: enp2s0f1 state: down mac: 00:24:81:7f:47:c1 >> Card-3: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet >> driver: r8169 v: 2.3LK-NAPI port: c000 bus ID: 05:00 chip ID: 10ec:8168 >> IF: enp5s0 state: down mac: 08:60:6e:da:8e:bb >> IF-ID-1: virbr0 state: down mac: 52:54:00:ee:6e:d1 >> IP v4: 192.168.122.1/24 scope: global broadcast: 192.168.122.255 >> IF-ID-2: virbr0-nic state: down mac: 52:54:00:ee:6e:d1 >> WAN IP: 94.222.186.234 >> Drives: >> Local Storage: total: 1.03 TiB used: 22.00 GiB (2.1%) >> ID-1: /dev/sda vendor: A-Data model: SP900 size: 119.24 GiB >> speed: 6.0 Gb/s serial: 7E2720008327 temp: 32 C scheme: MBR >> ID-2: /dev/sdb vendor: Western Digital model: WD10EZRX-00A8LB0 >> size: 931.51 GiB speed: 6.0 Gb/s serial: WD-WCC1U0278788 rev: 1A01 >> temp: 38 C scheme: GPT >> Message: No Optical or Floppy data was found. >> RAID: >> Message: No RAID data was found. >> Partition: >> ID-1: / size: 109.30 GiB used: 18.91 GiB (17.3%) fs: ext4 dev: /dev/dm-1 >> label: N/A uuid: 5c555be5-d883-4cea-bb77-54c6c8cf487a >> ID-2: /boot size: 235.3 MiB used: 46.7 MiB (19.9%) fs: ext2 dev: >> /dev/sda1 >> label: N/A uuid: d7955e20-0ca7-4dbc-8d27-ef0cfc539dc7 >> ID-3: /media/sdb1_crypt size: 931.06 GiB used: 3.05 GiB (0.3%) fs: xfs >> dev: /dev/dm-3 label: cryptica uuid: 48251097-20b6-4f5a-bfa4-4a614c62a15d >> ID-4: /media/smb/data_lg size: 3.64 TiB used: 2.27 TiB (62.4%) fs: cifs >> remote: //freedom/data_lg label: N/A uuid: N/A >> ID-5: /media/smb/pool size: 3.64 TiB used: 2.27 TiB (62.4%) fs: cifs >> remote: //freedom/pool label: N/A uuid: N/A >> ID-6: swap-1 size: 7.45 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/dm-2 >> label: N/A uuid: bebbd4d3-4597-4ecc-935e-13976c0e0fa3 >> Unmounted: >> ID-1: /dev/dm-0 size: 119.00 GiB fs: <root required> label: N/A uuid: N/A >> ID-2: /dev/sda2 size: 1 KiB fs: <root required> label: N/A uuid: N/A >> ID-3: /dev/sda5 size: 119.00 GiB fs: crypto_luks label: N/A >> uuid: b3becd23-ac52-44b7-a499-f5c1035e8420 >> ID-4: /dev/sdb1 size: 931.51 GiB fs: crypto_luks label: N/A >> uuid: 7b09e039-080a-4c97-baaa-ef5905c6fc9b >> USB: >> Hub: 1:1 usb: 2.0 type: Full speed (or root) hub chip ID: 1d6b:0002 >> Hub: 2:1 usb: 3.0 type: Full speed (or root) hub chip ID: 1d6b:0003 >> Hub: 3:1 usb: 2.0 type: Full speed (or root) hub chip ID: 1d6b:0002 >> Hub: 4:1 usb: 3.0 type: Full speed (or root) hub chip ID: 1d6b:0003 >> Hub: 5:1 usb: 2.0 type: Full speed (or root) hub chip ID: 1d6b:0002 >> Device-1: Lexmark bus ID: 5:4 usb: 2.0 type: Printer chip ID: 043d:0126 >> Hub: 6:1 usb: 2.0 type: Full speed (or root) hub chip ID: 1d6b:0002 >> Hub: 7:1 usb: 1.1 type: Full speed (or root) hub chip ID: 1d6b:0001 >> Device-2: Keyboard bus ID: 7:2 usb: 1.1 type: Keyboard chip ID: 258a:1006 >> Device-3: Logitech M90/M100 Optical Mouse bus ID: 7:3 usb: 2.0 type: >> Mouse >> chip ID: 046d:c05a >> Hub: 8:1 usb: 1.1 type: Full speed (or root) hub chip ID: 1d6b:0001 >> Sensors: >> System Temperatures: cpu: 24.4 C mobo: N/A gpu: amdgpu temp: 46 C >> Fan Speeds (RPM): cpu: 0 gpu: amdgpu fan: 0 >> Repos: >> Active apt repos in: /etc/apt/sources.list >> 1: deb http://ftp.de.debian.org/debian/ buster main contrib non-free >> 2: deb-src http://ftp.de.debian.org/debian/ buster main contrib >> 3: deb http://security.debian.org/debian-security buster/updates main >> contrib non-free >> 4: deb-src http://security.debian.org/debian-security buster/updates >> main contrib >> 5: deb http://ftp.de.debian.org/debian/ buster-updates main contrib >> non-free >> 6: deb-src http://ftp.de.debian.org/debian/ buster-updates main contrib >> Processes: >> CPU top: 5 >> 1: cpu: 7.0% command: firefox-esr pid: 7855 mem: 704.6 MiB (8.8%) >> 2: cpu: 4.3% command: cinnamon pid: 2270 mem: 242.4 MiB (3.0%) >> 3: cpu: 2.8% command: xorg pid: 907 mem: 163.3 MiB (2.0%) >> 4: cpu: 1.4% command: thunderbird pid: 7710 mem: 383.5 MiB (4.8%) >> 5: cpu: 1.0% command: dino-im pid: 7767 mem: 90.5 MiB (1.1%) >> Memory top: 5 >> 1: mem: 704.6 MiB (8.8%) command: firefox-esr pid: 7855 cpu: 7.0% >> 2: mem: 383.5 MiB (4.8%) command: thunderbird pid: 7710 cpu: 1.4% >> 3: mem: 242.4 MiB (3.0%) command: cinnamon pid: 2270 cpu: 4.3% >> 4: mem: 163.3 MiB (2.0%) command: xorg pid: 907 cpu: 2.8% >> 5: mem: 109.5 MiB (1.3%) command: owncloud pid: 2478 cpu: 0.0% >> Info: >> Processes: 223 Uptime: 1h 16m Memory: 7.74 GiB used: 2.15 GiB (27.8%) >> Init: systemd v: 239 runlevel: 5 Compilers: gcc: 8.2.0 alt: 7/8 >> Shell: bash v: 4.4.23 running in: gnome-terminal inxi: 3.0.20 >> lg@thanatos:~$ >> >> >> -- >> coreboot mailing list: coreboot(a)coreboot.org >> https://mail.coreboot.org/mailman/listinfo/coreboot

2 1

Re: [coreboot] T450S + Coreboot
by Nico Huber 28 Aug '18

28 Aug '18

Hi Mike, please don't spread FUD on this list. On 28.08.2018 09:54, Mike Banon wrote: > And even if there weren't any problem with Intel Boot Guard, its not > that easy to add a support for new board (impossible to do it over > weekends, especially for the newcomers). The T450s would probably benefit a lot from the existing support for ThinkPads. But Broadwell really isn't a weekend port (Sandy or Ivy Bridge would be for a ThinkPad) because we have few Broadwell ports and an ugly blob situation. Anyway, chances are close to 100% that the T450s has BootGuard in verification mode. > If I were you I would have > sold these T450S and bought some machine already supported by > coreboot. It could be one of those Intel Thinkpads (although you'll > have to spend time cleaning Intel ME) You don't *have to* spend time cleaning the ME, you *can* spend time with it. It is actually unknown if that lowers or highers security, so there is really no reason to advice to do it (unless you need more flash space for fancy stuff). > or maybe Lenovo G505S quadcore > AMD laptop which doesn't have any Intel ME / AMD PSP backdoors in its' > CPU at all - so no need to clean anything. The G505s requires a lot of other blobs, IIRC: xHCI (optional), AtomBIOS for GFX (which even runs in the OS on the host CPU), maybe more I don't remember. I don't see how that is better (you seemed to want to sell that by only stating absence of blobs, ignoring those it has instead). Nico

2 1

coreboot AMD Cards
by kinky_nekoboi 28 Aug '18

28 Aug '18

AFAIK the Hardware init of coreboot is somehow based of the linux kernel ? As a Deblobed Kernel like in Debian is not able to detect an AMD card without Amd microcode.. is Coreboot not able to detect AMD Cards without this microcode ? The problem is that i can not get any AMD cards to work with coreboot+Seabios on my F2A85M board. Systeminfo, currently with ASUS UEFI 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 43 Region 0: Memory at c0000000 (64-bit, prefetchable) [size=256M] Region 2: Memory at fea00000 (64-bit, non-prefetchable) [size=256K] Region 4: I/O ports at e000 [size=256] Expansion ROM at 000c0000 [disabled] [size=128K] Capabilities: <access denied> Kernel driver in use: amdgpu Kernel modules: radeon, amdgpu System: Host: thanatos Kernel: 4.17.0-3-amd64 x86_64 bits: 64 compiler: gcc v: 7.3.0 Desktop: Cinnamon 3.8.8 dm: lightdm 1.18.3 Distro: Debian GNU/Linux buster/sid Machine: Type: Desktop Mobo: ASUSTeK model: F2A85-M v: Rev X.0x serial: <root required> BIOS: American Megatrends v: 6402 date: 07/18/2013 Memory: RAM Report: permissions: Unable to run dmidecode. Are you root? PCI Slots: Permissions: Unable to run dmidecode. Are you root? CPU: Topology: Quad Core model: AMD A8-6600K APU with Radeon HD Graphics bits: 64 type: MCP arch: Piledriver rev: 1 L2 cache: 2048 KiB bogomips: 31355 Speed: 1907 MHz min/max: 1900/3900 MHz boost: enabled Core speeds (MHz): 1: 1909 2: 1909 3: 1906 4: 1903 Flags: 3dnowprefetch abm aes aperfmperf apic arat avx bmi1 clflush cmov cmp_legacy constant_tsc cpb cpuid cr8_legacy cx16 cx8 de decodeassists extapic extd_apicid f16c flushbyasid fma fma4 fpu fxsr fxsr_opt ht hw_pstate ibs lahf_lm lbrv lm lwp mca mce misalignsse mmx mmxext monitor msr mtrr nodeid_msr nonstop_tsc nopl npt nrip_save nx osvw pae pat pausefilter pclmulqdq pdpe1gb perfctr_core perfctr_nb pfthreshold pge pni popcnt pse pse36 rdtscp rep_good sep skinit ssbd sse sse2 sse4_1 sse4_2 sse4a ssse3 svm svm_lock syscall tbm tce topoext tsc tsc_scale vmcb_clean vme vmmcall wdt xop xsave Graphics: Card-1: AMD Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP] vendor: PC Partner Limited driver: amdgpu v: kernel bus ID: 01:00.0 chip ID: 1002:6819 Display: x11 server: X.Org 1.20.1 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz, 1920x1080~60Hz OpenGL: renderer: AMD Radeon HD 7800 Series (PITCAIRN DRM 3.25.0 4.17.0-3-amd64 LLVM 6.0.1) v: 4.5 Mesa 18.1.6 compat-v: 3.1 direct render: Yes Audio: Card-1: AMD FCH Azalia vendor: ASUSTeK F2A85-M Series driver: snd_hda_intel v: kernel bus ID: 00:14.2 chip ID: 1022:780d Card-2: AMD Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series] vendor: PC Partner Limited driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 1002:aab0 Sound Server: ALSA v: k4.17.0-3-amd64 Network: Card-1: Intel 82571EB Gigabit Ethernet driver: e1000e v: 3.2.6-k port: d020 bus ID: 02:00 chip ID: 8086:105e IF: enp2s0f0 state: up speed: 1000 Mbps duplex: full mac: 00:24:81:7f:47:c0 IP v4: 10.0.0.88/24 type: dynamic noprefixroute scope: global broadcast: 10.0.0.255 IP v6: fe80::224:81ff:fe7f:47c0/64 type: noprefixroute scope: link Card-2: Intel 82571EB Gigabit Ethernet driver: e1000e v: 3.2.6-k port: d000 bus ID: 02:00.1 chip ID: 8086:105e IF: enp2s0f1 state: down mac: 00:24:81:7f:47:c1 Card-3: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 v: 2.3LK-NAPI port: c000 bus ID: 05:00 chip ID: 10ec:8168 IF: enp5s0 state: down mac: 08:60:6e:da:8e:bb IF-ID-1: virbr0 state: down mac: 52:54:00:ee:6e:d1 IP v4: 192.168.122.1/24 scope: global broadcast: 192.168.122.255 IF-ID-2: virbr0-nic state: down mac: 52:54:00:ee:6e:d1 WAN IP: 94.222.186.234 Drives: Local Storage: total: 1.03 TiB used: 22.00 GiB (2.1%) ID-1: /dev/sda vendor: A-Data model: SP900 size: 119.24 GiB speed: 6.0 Gb/s serial: 7E2720008327 temp: 32 C scheme: MBR ID-2: /dev/sdb vendor: Western Digital model: WD10EZRX-00A8LB0 size: 931.51 GiB speed: 6.0 Gb/s serial: WD-WCC1U0278788 rev: 1A01 temp: 38 C scheme: GPT Message: No Optical or Floppy data was found. RAID: Message: No RAID data was found. Partition: ID-1: / size: 109.30 GiB used: 18.91 GiB (17.3%) fs: ext4 dev: /dev/dm-1 label: N/A uuid: 5c555be5-d883-4cea-bb77-54c6c8cf487a ID-2: /boot size: 235.3 MiB used: 46.7 MiB (19.9%) fs: ext2 dev: /dev/sda1 label: N/A uuid: d7955e20-0ca7-4dbc-8d27-ef0cfc539dc7 ID-3: /media/sdb1_crypt size: 931.06 GiB used: 3.05 GiB (0.3%) fs: xfs dev: /dev/dm-3 label: cryptica uuid: 48251097-20b6-4f5a-bfa4-4a614c62a15d ID-4: /media/smb/data_lg size: 3.64 TiB used: 2.27 TiB (62.4%) fs: cifs remote: //freedom/data_lg label: N/A uuid: N/A ID-5: /media/smb/pool size: 3.64 TiB used: 2.27 TiB (62.4%) fs: cifs remote: //freedom/pool label: N/A uuid: N/A ID-6: swap-1 size: 7.45 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/dm-2 label: N/A uuid: bebbd4d3-4597-4ecc-935e-13976c0e0fa3 Unmounted: ID-1: /dev/dm-0 size: 119.00 GiB fs: <root required> label: N/A uuid: N/A ID-2: /dev/sda2 size: 1 KiB fs: <root required> label: N/A uuid: N/A ID-3: /dev/sda5 size: 119.00 GiB fs: crypto_luks label: N/A uuid: b3becd23-ac52-44b7-a499-f5c1035e8420 ID-4: /dev/sdb1 size: 931.51 GiB fs: crypto_luks label: N/A uuid: 7b09e039-080a-4c97-baaa-ef5905c6fc9b USB: Hub: 1:1 usb: 2.0 type: Full speed (or root) hub chip ID: 1d6b:0002 Hub: 2:1 usb: 3.0 type: Full speed (or root) hub chip ID: 1d6b:0003 Hub: 3:1 usb: 2.0 type: Full speed (or root) hub chip ID: 1d6b:0002 Hub: 4:1 usb: 3.0 type: Full speed (or root) hub chip ID: 1d6b:0003 Hub: 5:1 usb: 2.0 type: Full speed (or root) hub chip ID: 1d6b:0002 Device-1: Lexmark bus ID: 5:4 usb: 2.0 type: Printer chip ID: 043d:0126 Hub: 6:1 usb: 2.0 type: Full speed (or root) hub chip ID: 1d6b:0002 Hub: 7:1 usb: 1.1 type: Full speed (or root) hub chip ID: 1d6b:0001 Device-2: Keyboard bus ID: 7:2 usb: 1.1 type: Keyboard chip ID: 258a:1006 Device-3: Logitech M90/M100 Optical Mouse bus ID: 7:3 usb: 2.0 type: Mouse chip ID: 046d:c05a Hub: 8:1 usb: 1.1 type: Full speed (or root) hub chip ID: 1d6b:0001 Sensors: System Temperatures: cpu: 24.4 C mobo: N/A gpu: amdgpu temp: 46 C Fan Speeds (RPM): cpu: 0 gpu: amdgpu fan: 0 Repos: Active apt repos in: /etc/apt/sources.list 1: deb http://ftp.de.debian.org/debian/ buster main contrib non-free 2: deb-src http://ftp.de.debian.org/debian/ buster main contrib 3: deb http://security.debian.org/debian-security buster/updates main contrib non-free 4: deb-src http://security.debian.org/debian-security buster/updates main contrib 5: deb http://ftp.de.debian.org/debian/ buster-updates main contrib non-free 6: deb-src http://ftp.de.debian.org/debian/ buster-updates main contrib Processes: CPU top: 5 1: cpu: 7.0% command: firefox-esr pid: 7855 mem: 704.6 MiB (8.8%) 2: cpu: 4.3% command: cinnamon pid: 2270 mem: 242.4 MiB (3.0%) 3: cpu: 2.8% command: xorg pid: 907 mem: 163.3 MiB (2.0%) 4: cpu: 1.4% command: thunderbird pid: 7710 mem: 383.5 MiB (4.8%) 5: cpu: 1.0% command: dino-im pid: 7767 mem: 90.5 MiB (1.1%) Memory top: 5 1: mem: 704.6 MiB (8.8%) command: firefox-esr pid: 7855 cpu: 7.0% 2: mem: 383.5 MiB (4.8%) command: thunderbird pid: 7710 cpu: 1.4% 3: mem: 242.4 MiB (3.0%) command: cinnamon pid: 2270 cpu: 4.3% 4: mem: 163.3 MiB (2.0%) command: xorg pid: 907 cpu: 2.8% 5: mem: 109.5 MiB (1.3%) command: owncloud pid: 2478 cpu: 0.0% Info: Processes: 223 Uptime: 1h 16m Memory: 7.74 GiB used: 2.15 GiB (27.8%) Init: systemd v: 239 runlevel: 5 Compilers: gcc: 8.2.0 alt: 7/8 Shell: bash v: 4.4.23 running in: gnome-terminal inxi: 3.0.20 lg@thanatos:~$

2 1

← Newer
1
2
3
4
5
6
7
...
11
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot August 2018