• NOTICE: If you are reading this, you are hitting our new server. We expect there to be some bugs - please let us know if you come across anything, THANKS!

Screwed again by Intel.



Condobloke

Well-Known Member
So, here we go again.

I received an update for Micro Code on the 15th of this month.

I have no idea if it is related to this drama.



and at this late hour I am too tired to really care. It is past my snooze time

Tomorrow will be soon enough.
 

poorguy

Well-Known Member
And some days.... I am very happy to be running old junk here. :eek::D

Old AMD junk. :cool::D
Me too.

Get a rope.
Find an old scrub oak tree.
And Hang-em High.
 

poorguy

Well-Known Member
CPU: Intel Core2 Duo E7500 (Jan. 18, 2009)

Run this command in terminal.
cat /sys/devices/system/cpu/vulnerabilities/mds

My output.
[email protected]:~$ cat /sys/devices/system/cpu/vulnerabilities/mds
Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled
 

Condobloke

Well-Known Member

poorguy

Well-Known Member

Condobloke

Well-Known Member
Ran it several times.....same response

I have no idea

Doesnt worry me
 

lekkerlinux

Active Member
And some days.... I am very happy to be running old junk here. :eek::D

Old AMD junk. :cool::D
Have been running AMD Athlon from 2001 to 2013, then AMD A 10 from 2013 on. I had to replace the previous PC because the fan on the motherboard stopped working.

My graphics card is also AMD Radeon.

AMD stuff seems to run very nicely with the open source Linux graphics driver, Intel and NVIDIA seems to give more trouble.
 

poorguy

Well-Known Member
AMD stuff seems to run very nicely with the open source Linux graphics driver, Intel and NVIDIA seems to give more trouble.
I've never had any problems with AMD / ATI hardware or Intel hardware running Linux the open source drivers work well.

Nvidia graphics cards and Nvidia integrated graphics adapters have been somewhat problematic for me sometimes running Linux.

Back in 2014 Linux users were able to get proprietary Nvidia graphics drivers from "Additional Drivers" section of Linux and that doesn't seem to be available with the new Linux distros. :mad:

Nouveau open source driver doesn't always work well with some Nvidia graphics adapters discrete or integrated. :mad:
 

lekkerlinux

Active Member
Back in 2014 Linux users were able to get proprietary Nvidia graphics drivers from "Additional Drivers" section of Linux and that doesn't seem to be available with the new Linux distros. :mad:
I think I tried the proprietary ATI driver last year, just like you said under "Additional Drivers" and it changed my screen resolution to 5000 x 5000. Everything was really small but crystal clear. I just changed back to the open source driver because the other one would not let me change the resolution at all.

I have a bit of a problem now, would you care to look at that in Power save in Budgie in the Desktop section, please?
 

poorguy

Well-Known Member
I have a bit of a problem now, would you care to look at that in Power save in Budgie in the Desktop section, please?
Start a new thread so that we stay within the forum rules and guidelines.
 

wizardfromoz

Super Moderator
Staff member
Gold Supporter
Regarding #5 through #8

Brian is running Linux Mint 18.3 'Sylvia' Cinnamon, which, surprise, surprise I have one of also.

Kernel is likely 4.15.0-48 and under that environment, there is no mds in

/sys/devices/system/cpu/vulnerabilities - but there are files for Meltdown Spectre and l1tf

I have just run updates which included a kernel upgrade to 4.15.0-50 and it is here that the support for md5 appears.




Changelog includes, in part the following

linux (4.15.0-50.54) bionic; urgency=medium

* CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130
- Documentation/l1tf: Fix small spelling typo
- x86/cpu: Sanitize FAM6_ATOM naming
- kvm: x86: Report STIBP on GET_SUPPORTED_CPUID
- locking/atomics, asm-generic: Move some macros from <linux/bitops.h> to a
new <linux/bits.h> file
- tools include: Adopt linux/bits.h
- x86/msr-index: Cleanup bit defines
- x86/speculation: Consolidate CPU whitelists
- x86/speculation/mds: Add basic bug infrastructure for MDS
- x86/speculation/mds: Add BUG_MSBDS_ONLY
- x86/kvm: Expose X86_FEATURE_MD_CLEAR to guests
- x86/speculation/mds: Add mds_clear_cpu_buffers()
- x86/speculation/mds: Clear CPU buffers on exit to user
- x86/kvm/vmx: Add MDS protection when L1D Flush is not active
- x86/speculation/mds: Conditionally clear CPU buffers on idle entry
- x86/speculation/mds: Add mitigation control for MDS
- x86/speculation/mds: Add sysfs reporting for MDS
- x86/speculation/mds: Add mitigation mode VMWERV
- Documentation: Move L1TF to separate directory
- Documentation: Add MDS vulnerability documentation
- x86/speculation/mds: Add mds=full,nosmt cmdline option
- x86/speculation: Move arch_smt_update() call to after mitigation decisions
- x86/speculation/mds: Add SMT warning message
- x86/speculation/mds: Fix comment
- x86/speculation/mds: Print SMT vulnerable on MSBDS with mitigations off
- x86/speculation/mds: Add 'mitigations=' support for MDS

So the support is now there, but an MDS file has yet to be generated.

https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html

... explains more about MDS.

Wizard
 

wizardfromoz

Super Moderator
Staff member
Gold Supporter
My MDS file appeared today (with a change of the calendar responsible, I suspect ala a cron-style process), in Sylvia, running kernel 4.15.0-50

My Serena 18.1 'Cinnamon' (which coincidentally I installed to help another Member) I have run 2 upgrades on, starting with kernel 4.4.0-53, then to 4.4.0-146, and finally to 4.4.0-148.

It was with this last update that the /vulnerabilities folder is generated, and that in turn will ultimately generate the MDS file.

Not sure why Tom deleted his previous Post but as I recall his

uname -r

resulted in 4.4.0-148, a match.

It was not just /vulnerabilities which was generated with the kernel upgrade, there were 2 other folders, /intel_pstate and /smt, and you'll note that SMT was referenced in the file on MDS Tom provided earlier.

In Serena, I was able to dial back the kernels from the grub menu, too and watch the various components disappear, from view at least, they were obviously still on the hard drive.

Hope that helps, out for the night
 

poorguy

Well-Known Member
Not sure why Tom deleted his previous Post but as I recall his

uname -r

resulted in 4.4.0-148, a match.

It was not just /vulnerabilities which was generated with the kernel upgrade, there were 2 other folders, /intel_pstate and /smt, and you'll note that SMT was referenced in the file on MDS Tom provided earlier.
This is what I posted and I discovered the difference / found my answer and didn't see any need for my post which is why I removed it.

Linux Mint 18 Xfce 64 bit.

Code:
[email protected] ~ $ cat /sys/devices/system/cpu/vulnerabilities/mds
Not affected
[email protected] ~ $
Code:
[email protected] ~ $ uname -r
4.4.0-148-generic
[email protected] ~ $
Code:
[email protected] ~ $ inxi -Fxz
System:    Host: hp-pavilion Kernel: 4.4.0-148-generic x86_64 (64 bit gcc: 5.4.0)
           Desktop: Xfce 4.12.3 (Gtk 2.24.28) Distro: Linux Mint 18 Sarah
Machine:   System: HP-Pavilion product: GN556AA-ABA a6200n
           Mobo: ECS model: Nettle2 v: 1.0 Bios: Phoenix v: 5.12 date: 06/11/2007
CPU:       Dual core AMD Athlon 64 X2 5600+ (-MCP-) cache: 2048 KB flags: (lm nx sse sse2 sse3 svm) bmips: 4018
           clock speeds: max: 2800 MHz 1: 1000 MHz 2: 1000 MHz
Graphics:  Card: NVIDIA C61 [GeForce 6150SE nForce 430] bus-ID: 00:0d.0
           Display Server: X.Org 1.18.4 drivers: nvidia (unloaded: fbdev,vesa,nouveau)
           Resolution: [email protected]
           GLX Renderer: GeForce 6150SE nForce 430/integrated/SSE2
           GLX Version: 2.1.2 NVIDIA 304.135 Direct Rendering: Yes
Audio:     Card NVIDIA MCP61 High Definition Audio driver: snd_hda_intel bus-ID: 00:05.0
           Sound: Advanced Linux Sound Architecture v: k4.4.0-148-generic
Network:   Card: NVIDIA MCP61 Ethernet driver: forcedeth port: ec00 bus-ID: 00:07.0
           IF: enp0s7 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:    HDD Total Size: 82.3GB (16.3% used) ID-1: /dev/sda model: Hitachi_HDS72168 size: 82.3GB
Partition: ID-1: / size: 70G used: 7.0G (11%) fs: ext4 dev: /dev/sda1
           ID-2: swap-1 size: 6.31GB used: 0.00GB (0%) fs: swap dev: /dev/sda5
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 40.0C mobo: N/A gpu: 0.0:
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 179 Uptime: 26 min Memory: 700.1/5840.8MB Init: systemd runlevel: 5 Gcc sys: 5.4.0
           Client: Shell (bash 4.3.481) inxi: 2.2.35
[email protected] ~ $
 

poorguy

Well-Known Member
And some days.... I am very happy to be running old junk here. :eek::D

Old AMD junk. :cool::D
Yep me to. :)

I'm thinking about taking all of my Intel products out to the farm and blasting them full of holes with my 357 magnum. :p:D
 

wizardfromoz

Super Moderator
Staff member
Gold Supporter
I discovered the difference / found my answer
Did that shed any light, was it similar to/different from what I mentioned above?

I'm thinking about taking all of my Intel products out to the farm and blasting them full of holes with my 357 magnum. :p:D
Can you save a bullet or two for me? No, for my Intel, not me
 

poorguy

Well-Known Member
This is the output from the terminal command.
cat /sys/devices/system/cpu/vulnerabilities/mds

[email protected] ~ $ cat /sys/devices/system/cpu/vulnerabilities/mds
Not affected


The other outputs are inxi -Fxz and uname -r just for explanation purposes.
 
Last edited:

poorguy

Well-Known Member
Last edited:

Members online


Latest posts

Top