Re: Is Fedora Linux protected against the Meltdown and Spectre security flaws?

[Paul Allen Newell]

On 02/19/2018 06:04 AM, Ed Greshko wrote:

On 02/19/18 21:51, Ranjan Maitra wrote:

What do these mean, and what is the needed mitigation, if any?


Basically, it means that everything that can currently be done to lessen the 
chances
of a security breach is being done.

Otherwise you may see something like...

Mitigation: Full generic retpoline - vulnerable module loaded



Ed:

In earlier email in this thread, you stated:

   Yes.  As long as you don't have kernel modules which were built with
   a non-patched gcc.

   ls /sys/devices/system/cpu/vulnerabilities/*

   cat /sys/devices/system/cpu/vulnerabilities/*

This file is new to me ... do you happen to know about when it was 
introduced and if there is any documentation on it (I couldn't find 
anything but I feel I was grasping in the dark as I must be missing 
something).


From what I can tell in this thread, this is a good new addition

Best,
Paul

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Dual screen

[Ed Greshko]

On 02/20/18 09:25, Ed Greshko wrote:
>  If I can only find the mini-HDMI cable that would connect
> to my laptop.  I have never used a TV as a monitor so I don't know how well 
> suited
> they are for this purpose.


I found my HDMI cable.  The TV is a 48 inch model.  It just so happens that its
preferred resolution is the same as my 11 inch laptop screen at 1920x1080.  The 
fonts
on my laptop are very crisp and clear.  On the TV, not so much when viewed 
close up. 
Better when viewed from a distance but still not as good as a monitor.

However, I think I may have found your problem.

Looking at the specs for your TV/monitor we find that the screen size is 23.5" 
with a
pixel density of 66ppi at the native resolution. In searching for articles on 
using
TV as monitor they recommend a display with no less than 80dpi.  I could not 
find the
specs on my TV's display.  It is about 3 years old.

Now compare that with my Asus monitors.  They are 25" displays with a pixel 
density
of 117ppi at their native resolution of 2560x1440

(I think PPD, pixel per degree, may be a better measure but that seems harder t 
come
by or calculate)

Everything is sharp and clear on my Asus monitors.

I think you have HW which is never going to be satisfactory as a monitor.  
Probably
others with better understanding of display technology have their opinion.

-- 
A motto of mine is: When in doubt, try it out



signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Dual screen

[Ed Greshko]

On 02/20/18 09:25, Ed Greshko wrote:
> would not concentrate


would NOW concentrate

-- 
A motto of mine is: When in doubt, try it out



signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Dual screen

[Ed Greshko]

On 02/20/18 04:14, Patrick Dupre wrote:
> Now I am running 1368x768
> I do not think that it is what I wanted.


As I've said before, that is the resolution your monitor is designed to provide 
the
best performance.

I would not concentrate on picking the best looking fonts.  I have a Samsung TV 
that
I could hook up to HDMI.  If I can only find the mini-HDMI cable that would 
connect
to my laptop.  I have never used a TV as a monitor so I don't know how well 
suited
they are for this purpose.

I have 2 ASUS monitors that operate at 2560x1440 and the fonts are crisp and 
clear.

-- 
A motto of mine is: When in doubt, try it out



signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Nvidia Module Tainting Kernel

[Ed Greshko]

On 02/20/18 04:41, Stephen Morris wrote:
>    I'm using the nvidia drivers from negativo17. I have the nvidia source 
> module
> registered with dkms and it seems to be being compiled when I get a new 
> kernel, if
> that is the case what do I need to do to resolve the following messages shown 
> by
> "dmesg"?
>
>
> [   14.934074] nvidia: loading out-of-tree module taints kernel.
> [   14.934086] nvidia: module license 'NVIDIA' taints kernel.
> [   14.934087] Disabling lock debugging due to kernel taint
> [   14.943865] nvidia: module verification failed: signature and/or required 
> key
> missing - tainting kernel 


When you load a proprietary module into the kernel it becomes tainted.  There 
is no
way to "fix" it.  It is like replacing the battery in your iPhone with a 
battery you
bought on the street corner.  You have voided the warranty.

-- 
A motto of mine is: When in doubt, try it out



signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Dual screen

[Wolfgang Pfeiffer]

On Sat, 17 Feb 2018 22:25:19 +0100
"Patrick Dupre"  wrote:

> Hello,
>  
> The Hardware of the PC does not let me access to any monitor configuration.
> It seems that every thing is automatic (It is a recent Asus Motherboard).
>  
> The new monitor says that it is running with a resolution 1920x1080@60Hz.
> I guess that it may be correct if I check on the pictures, but the bizarre 
> thing is that
> the characters are just difficult to read, like if there is a lack of 
> resolution.
> I can switch to 1366x768.

Oops -  just saw the resolution I recommended later on seems to
have worked from the beginning ...

I missed that. Sorry
-- 
Wolfgang Pfeiffer
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Dual screen

[Patrick Dupre]

> On Mon, 19 Feb 2018 21:14:22 +0100
> "Patrick Dupre"  wrote:
> 
> > > 
> > > Two things you need to know. Read careful:
> > > 
> > > -- 0:
> > > You probably have a file like
> > > 
> > > ~/.config/monitors.xml 
> > > 
> > > in your home dir - or wherever. Find it. Read it: It might be that this 
> > > file keeps setting your monitor(s?) to wrong settings/resolutions, 
> > > if these values in that file do not correspond with the actual
> > > capabilities of your monitor(s) ...  
> > 
> > cat .config/monitors.xml
> > 
> >   
> > no
> > 
> >   SAM
> >   SyncMaster
> >   HVYL606149
> >   1600
> >   1200
> >   60
> >   0
> >   0
> >   normal
> >   no
> >   no
> >   yes
> >   no
> >   no
> > 
> > 
> >   SAM
> >   SAMSUNG
> >   0x
> >   1920
> >   1080
> 
> Last two lines seem to be wrong. But your xrandr command seems to have
> ignored them. Good, AFAICS  ... ;)
> 
> >   59.940200805664062
> >   1600
> >   0
> >   normal
> >   no
> >   no
> >   no
> >   no
> >   no
> > 
> >   
> > 
> > 
> > 
> > 
> > > If in doubt: move the file away for a while - don't delete it. Then
> > > connect the external monitor.
> > > 
> > > -- 1:
> > > On many (?) computers there's something like a built-in (?) key combo: 
> > >  - Seems to work both on Linux and Windows.
> > > 
> > > If you have that on your computer, you might be able to change your
> > > monitor settings (external, and, IIRC, also the internal ones) with
> > > that combo: While this can be extremely convenient to attach
> > > monitors you can end up all monitors turning into black screens. In
> > > that case: press the combo again. If that does not help anymore I see
> > > four options to save you:  
> > 
> > I can switch to 1024x768 and back to 1366x768
> 
> And the fonts, and the rest, look nice at these resolutions?

Not really. The display is larger, it's all.


> 
> > 
> > Thank.
> 
> You're welcome! 
> -- 
> Wolfgang Pfeiffer
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> 
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Nvidia Module Tainting Kernel

[Stephen Morris]

Hi,

    I'm using the nvidia drivers from negativo17. I have the nvidia 
source module registered with dkms and it seems to be being compiled 
when I get a new kernel, if that is the case what do I need to do to 
resolve the following messages shown by "dmesg"?



[   14.934074] nvidia: loading out-of-tree module taints kernel.
[   14.934086] nvidia: module license 'NVIDIA' taints kernel.
[   14.934087] Disabling lock debugging due to kernel taint
[   14.943865] nvidia: module verification failed: signature and/or 
required key missing - tainting kernel



regards,

Steve

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Dual screen

[Wolfgang Pfeiffer]

On Mon, 19 Feb 2018 21:14:22 +0100
"Patrick Dupre"  wrote:

> > 
> > Two things you need to know. Read careful:
> > 
> > -- 0:
> > You probably have a file like
> > 
> > ~/.config/monitors.xml 
> > 
> > in your home dir - or wherever. Find it. Read it: It might be that this 
> > file keeps setting your monitor(s?) to wrong settings/resolutions, 
> > if these values in that file do not correspond with the actual
> > capabilities of your monitor(s) ...  
> 
> cat .config/monitors.xml
> 
>   
> no
> 
>   SAM
>   SyncMaster
>   HVYL606149
>   1600
>   1200
>   60
>   0
>   0
>   normal
>   no
>   no
>   yes
>   no
>   no
> 
> 
>   SAM
>   SAMSUNG
>   0x
>   1920
>   1080

Last two lines seem to be wrong. But your xrandr command seems to have
ignored them. Good, AFAICS  ... ;)

>   59.940200805664062
>   1600
>   0
>   normal
>   no
>   no
>   no
>   no
>   no
> 
>   
> 
> 
> 
> 
> > If in doubt: move the file away for a while - don't delete it. Then
> > connect the external monitor.
> > 
> > -- 1:
> > On many (?) computers there's something like a built-in (?) key combo: 
> >  - Seems to work both on Linux and Windows.
> > 
> > If you have that on your computer, you might be able to change your
> > monitor settings (external, and, IIRC, also the internal ones) with
> > that combo: While this can be extremely convenient to attach
> > monitors you can end up all monitors turning into black screens. In
> > that case: press the combo again. If that does not help anymore I see
> > four options to save you:  
> 
> I can switch to 1024x768 and back to 1366x768

And the fonts, and the rest, look nice at these resolutions?

> 
> Thank.

You're welcome! 
-- 
Wolfgang Pfeiffer
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Hardware errors

[Stephen Morris]

On 19/2/18 3:29 pm, Tim wrote:

Allegedly, on or about 19 February 2018, Stephen Morris sent:

Just following on from this, is my setup strange when I have never
found boot.log to be empty and on my system it currently has
mountains of entries?

Oops.  The machine I'm working on now does have a boot.log, my prior
ones didn't.

It doesn't have the entire boot log though (everything that you see as
the machine fires up).  It starts logging part way through.  The
various kernel messages are not there.  Many of the service ok/fail
starts are in there.

If I type in the "dmesg" command, that often starts off with the kind
of info I see as the machine boots up (pre boot.log file contents), and
ends with current kernel messages (such as info about recently plugged
in USB devices).

I appear to have a working /var/log/messages file, but don't recall
doing anything to wrest that back from the modern binary journal that's
supposed to replace it.


I don't have a /var/log/messages file, and the one file that used to be 
present and has disappeared some time ago is /var/log/syslog, which used 
to have more information in it than /var/log/boot.log.



regards,

Steve

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Dual screen

[Patrick Dupre]

I a a bit confused.

>
> On Mon, 19 Feb 2018 10:23:27 +0100
> "Patrick Dupre"  wrote:
> 
> 
> > Screen 0: minimum 320 x 200, current 3520 x 1200, maximum 8192 x 8192
> > HDMI-1 connected 1920x1080+1600+0 (normal left inverted right x axis y 
> > axis) 609mm x 347mm
> >1366x768  59.79 +
> >1920x1080 60.00*   50.0059.9430.0025.0024.00
> > 29.9723.98  
> 
> As Ed already pointed out: the asterisk (*) in the line above means your
> external monitor is set to  1920x1080, while its actual capabilities 
> can nicely handle only 1366x768. You can see that in the line before
> with the plus (+) sign in it. That's why - probably - your fonts on this
> monitor don't look as crisp as you want them. 
> 
> man xrandr  
> 
> >1920x1080i60.0050.0059.94  
> >1280x720  60.0050.0059.94  
> >1024x768  75.0370.0760.00  
> >832x624   74.55  
> >800x600   72.1975.0060.32  
> >720x576   50.00  
> >720x576i  50.00  
> >720x480   60.0059.94  
> >720x480i  60.0059.94  
> >640x480   75.0072.8166.6760.0059.94  
> >720x400   70.08  
> >1920x1080_60.00  59.96  
> > DP-1 connected primary 1600x1200+0+0 (normal left inverted right x axis y 
> > axis) 408mm x 306mm
> 
> > 
> > I run
> >  xrandr --newmode "1920x1080_60.00"  173.00  1920 2048 2248 2576  1080 1083 
> > 1088 1120 -hsync +vsync
> 
> No. You changed the order of the commands. Quote of the BZ page:
> 
> ---
> 
> $ cvt 1360 768 
> # 1360x768 59.80 Hz (CVT) hsync: 47.72 kHz; pclk: 84.75 MHz
> Modeline "1360x768_60.00"   84.75  1360 1432 1568 1776  768 771 781 798
> -hsync +vsync
> 
> [copy/paste the resulting 'Modeline' from above into the next command:]
> 
> $ xrandr --newmode "1360x768_60.00"   84.75  1360 1432 1568 1776  768
> 771 781 798 -hsync +vsync $ xrandr --addmode HDMI-1 1360x768_60.00
> $ xrandr --output HDMI-1 --mode 1360x768_60.00
> 
> --
> 
> So you run first
> 
> $ cvt 1366x768
 cvt 1366 768
# 1368x768 59.88 Hz (CVT) hsync: 47.79 kHz; pclk: 85.25 MHz
Modeline "1368x768_60.00"   85.25  1368 1440 1576 1784  768 771 781 798 -hsync 
+vsync


> 
> because this is max what your external monitor can handle, according to
> xrandr ...
> 
> then 
> copy/paste the resulting 'Modeline' from the first command  into the next
> command. See quote above:
> 
> $ xrandr --newmode .
xrandr --newmode "1368x768_60.00" 85.25  1368 1440 1576 1784  768 771 781 798 
-hsync +vsync
> $ xrandr --addmode .
 xrandr --addmode HDMI-1 1368x768_60.00
> $ xrandr --output HDMI-1 
xrandr --output HDMI-1 --mode 1368x768_60.00

Now I am running 1368x768
I do not think that it is what I wanted.

> 
> > cvt 1920 1080
> > xrandr --addmode HDMI-1 1920x1080_60.00
> > xrandr --output HDMI-1 --mode 1920x1080_60.00
> > 
> > The monitor responds that it switched to 1920 x 1080
> 
> Because you told the poor fellow to do exactly that ... :)
> 
> > 
> > 
> > I do not see any improvement.
> 
> Still astonished? ... ;)
> 
> > DP-1 is the old (but sharp monitor)
> > HDMI-1 is the new (but not sharp monitor)
> 
> Good to know ...
> 
> Two things you need to know. Read careful:
> 
> -- 0:
> You probably have a file like
> 
> ~/.config/monitors.xml 
> 
> in your home dir - or wherever. Find it. Read it: It might be that this 
> file keeps setting your monitor(s?) to wrong settings/resolutions, 
> if these values in that file do not correspond with the actual
> capabilities of your monitor(s) ...

cat .config/monitors.xml

  
no

  SAM
  SyncMaster
  HVYL606149
  1600
  1200
  60
  0
  0
  normal
  no
  no
  yes
  no
  no


  SAM
  SAMSUNG
  0x
  1920
  1080
  59.940200805664062
  1600
  0
  normal
  no
  no
  no
  no
  no

  




> If in doubt: move the file away for a while - don't delete it. Then
> connect the external monitor.
> 
> -- 1:
> On many (?) computers there's something like a built-in (?) key combo: 
>  - Seems to work both on Linux and Windows.
> 
> If you have that on your computer, you might be able to change your
> monitor settings (external, and, IIRC, also the internal ones) with
> that combo: While this can be extremely convenient to attach
> monitors you can end up all monitors turning into black screens. In
> that case: press the combo again. If that does not help anymore I see
> four options to save you:

I can switch to 1024x768 and back to 1366x768

Did I made progresses? I am not sure

Thank.

> -- ssh (good).
> -- sysrq keys (works often).
> -- Off button of your computer (bad).
> -- Throwing both your computer and your monitor against the next
> available walls (Don't do that).
> 
> -- 
> Wolfgang Pfeiffer
> ___
> users mailing list 

Re: how to (re-?)construct grub menu?

[Stephen Morris]

On 20/2/18 3:51 am, Tom H wrote:

On Wed, Feb 14, 2018 at 4:51 PM, Stephen Morris
 wrote:

On 14/2/18 8:18 pm, Tom H wrote:

On Mon, Feb 12, 2018 at 4:28 PM, Stephen Morris
 wrote:

Thanks Tom. My statement was from having seen other threads on this
list saying to not run grub2-install on an efi system because it
wasn't needed.

You're welcome.

Chris M has said that grub2-install shouldn't be used on an EFI
system. Maybe it does the wrong thing when you don't specify
"--target=...-efi" because the default is "--target=i386-pc".

It could be. As I understand it the default functionality updates the
mbr on the specified device, and from what I've read in other threads,
I thought they said that to get the grub menu displayed at boot you
don't update the mbr on an efi system any more, all that is necessary
is to just run grub2-mkconfig.

I'd be surprised if "grub-install" defaults to "--target=i386-pc" on
EFI if you don't include "--target=x86_64-efi" n the command. Maybe;
but I'd expect grub to detect that it's running on an EFI system...
I suspect grub is detecting which architecture is in use. In my 
/boot/efi/EFI/BOOT the only .efi entries in there other than 
fallback.efi are x86_64 versions. Also in /boot/efi/EFI/fedora fwupdate 
has made what I assume are its 32-bit and 64-bit .efi files executable 
and grubx64.efi is also executable. Also /boot/efi/EFI/fedora/grubenv 
seems to have its only line, being a saved_entry line, updated every 
time the machine is booted to reflect the version of the kernel last 
booted from. This surprises me, as I have never installed Win 10, Fedora 
27 or Ubuntu 17.10 in efi format, hence as far as I am aware I'm not 
using efi even though the motherboard I am using now doesn't appear to 
have any means to explicitly turn efi off, other than the SecureBoot 
option, which my previous motherboard that did have the capability of 
explicitly disabling efi didn't have, also I have SecureBoot disabled in 
the bios.


I think that I now remember Chris M's objection. It's that the EFI
executable that "grub-install" drops onto the ESP isn't signed, which
is problematic on SB systems. Ubuntu's "grub-install" has a
"--uefi-secure-boot" option to install a signed EFI executable (I
_assume_ that "/usr/lib/grub/x86_64-efi-signed/grubx64.efi.signed" is
copied to the ESP) but Fedora's grub doesn't have either of these so
Chris must be right for the SB case.


I thought that with SB all your drivers etc had to be signed to be able 
to boot from a SecureBoot system, and as such Fedora were using 
Microsoft certificates, whereas Ubuntu was going down the path of self 
signing. Given what you said around the /usrlib/grub/x86_64-efi-signed 
directory, which doesn't exist on my system, and if I understood you 
correctly doesn't exist in fedora anyway, where are fedora's 
certificates, and, if I enable SecureBoot in my bios do I have to also 
load the default certificates that the bios offers?



regards,

Steve


___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: how to (re-?)construct grub menu?

[Tom H]

On Wed, Feb 14, 2018 at 4:51 PM, Stephen Morris
 wrote:
> On 14/2/18 8:18 pm, Tom H wrote:
>> On Mon, Feb 12, 2018 at 4:28 PM, Stephen Morris
>>  wrote:
>>>
>>> Thanks Tom. My statement was from having seen other threads on this
>>> list saying to not run grub2-install on an efi system because it
>>> wasn't needed.
>>
>> You're welcome.
>>
>> Chris M has said that grub2-install shouldn't be used on an EFI
>> system. Maybe it does the wrong thing when you don't specify
>> "--target=...-efi" because the default is "--target=i386-pc".
>
> It could be. As I understand it the default functionality updates the
> mbr on the specified device, and from what I've read in other threads,
> I thought they said that to get the grub menu displayed at boot you
> don't update the mbr on an efi system any more, all that is necessary
> is to just run grub2-mkconfig.

I'd be surprised if "grub-install" defaults to "--target=i386-pc" on
EFI if you don't include "--target=x86_64-efi" n the command. Maybe;
but I'd expect grub to detect that it's running on an EFI system...

I think that I now remember Chris M's objection. It's that the EFI
executable that "grub-install" drops onto the ESP isn't signed, which
is problematic on SB systems. Ubuntu's "grub-install" has a
"--uefi-secure-boot" option to install a signed EFI executable (I
_assume_ that "/usr/lib/grub/x86_64-efi-signed/grubx64.efi.signed" is
copied to the ESP) but Fedora's grub doesn't have either of these so
Chris must be right for the SB case.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Dual screen

[Wolfgang Pfeiffer]

On Mon, 19 Feb 2018 10:23:27 +0100
"Patrick Dupre"  wrote:


> Screen 0: minimum 320 x 200, current 3520 x 1200, maximum 8192 x 8192
> HDMI-1 connected 1920x1080+1600+0 (normal left inverted right x axis y axis) 
> 609mm x 347mm
>1366x768  59.79 +
>1920x1080 60.00*   50.0059.9430.0025.0024.0029.97  
>   23.98  

As Ed already pointed out: the asterisk (*) in the line above means your
external monitor is set to  1920x1080, while its actual capabilities 
can nicely handle only 1366x768. You can see that in the line before
with the plus (+) sign in it. That's why - probably - your fonts on this
monitor don't look as crisp as you want them. 

man xrandr  

>1920x1080i60.0050.0059.94  
>1280x720  60.0050.0059.94  
>1024x768  75.0370.0760.00  
>832x624   74.55  
>800x600   72.1975.0060.32  
>720x576   50.00  
>720x576i  50.00  
>720x480   60.0059.94  
>720x480i  60.0059.94  
>640x480   75.0072.8166.6760.0059.94  
>720x400   70.08  
>1920x1080_60.00  59.96  
> DP-1 connected primary 1600x1200+0+0 (normal left inverted right x axis y 
> axis) 408mm x 306mm

> 
> I run
>  xrandr --newmode "1920x1080_60.00"  173.00  1920 2048 2248 2576  1080 1083 
> 1088 1120 -hsync +vsync

No. You changed the order of the commands. Quote of the BZ page:

---

$ cvt 1360 768 
# 1360x768 59.80 Hz (CVT) hsync: 47.72 kHz; pclk: 84.75 MHz
Modeline "1360x768_60.00"   84.75  1360 1432 1568 1776  768 771 781 798
-hsync +vsync

[copy/paste the resulting 'Modeline' from above into the next command:]

$ xrandr --newmode "1360x768_60.00"   84.75  1360 1432 1568 1776  768
771 781 798 -hsync +vsync $ xrandr --addmode HDMI-1 1360x768_60.00
$ xrandr --output HDMI-1 --mode 1360x768_60.00

--

So you run first

$ cvt 1366x768

because this is max what your external monitor can handle, according to
xrandr ...

then 
copy/paste the resulting 'Modeline' from the first command  into the next
command. See quote above:

$ xrandr --newmode .
$ xrandr --addmode .
$ xrandr --output HDMI-1 

> cvt 1920 1080
> xrandr --addmode HDMI-1 1920x1080_60.00
> xrandr --output HDMI-1 --mode 1920x1080_60.00
> 
> The monitor responds that it switched to 1920 x 1080

Because you told the poor fellow to do exactly that ... :)

> 
> 
> I do not see any improvement.

Still astonished? ... ;)

> DP-1 is the old (but sharp monitor)
> HDMI-1 is the new (but not sharp monitor)

Good to know ...

Two things you need to know. Read careful:

-- 0:
You probably have a file like

~/.config/monitors.xml 

in your home dir - or wherever. Find it. Read it: It might be that this 
file keeps setting your monitor(s?) to wrong settings/resolutions, 
if these values in that file do not correspond with the actual
capabilities of your monitor(s) ...

If in doubt: move the file away for a while - don't delete it. Then
connect the external monitor.

-- 1:
On many (?) computers there's something like a built-in (?) key combo: 
 - Seems to work both on Linux and Windows.

If you have that on your computer, you might be able to change your
monitor settings (external, and, IIRC, also the internal ones) with
that combo: While this can be extremely convenient to attach
monitors you can end up all monitors turning into black screens. In
that case: press the combo again. If that does not help anymore I see
four options to save you:

-- ssh (good).
-- sysrq keys (works often).
-- Off button of your computer (bad).
-- Throwing both your computer and your monitor against the next
available walls (Don't do that).

-- 
Wolfgang Pfeiffer
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Is Fedora Linux protected against the Meltdown and Spectre security flaws?

[Ranjan Maitra]

On Mon, 19 Feb 2018 22:04:41 +0800 Ed Greshko  wrote:

> On 02/19/18 21:51, Ranjan Maitra wrote:
> > What do these mean, and what is the needed mitigation, if any?
> 
> 
> Basically, it means that everything that can currently be done to lessen the 
> chances
> of a security breach is being done.
> 
> Otherwise you may see something like...
> 
> Mitigation: Full generic retpoline - vulnerable module loaded
> 

I see, so I guess that I am missing the additional words that would be 
concerning then:


$ cat /sys/devices/system/cpu/vulnerabilities/*
Mitigation: PTI
Mitigation: __user pointer sanitization
Mitigation: Full generic retpoline


Thanks!

Ranjan


> -- 
> A motto of mine is: When in doubt, try it out
> 


-- 
Important Notice: This mailbox is ignored: e-mails are set to be deleted on 
receipt. Please respond to the mailing list if appropriate. For those needing 
to send personal or professional e-mail, please use appropriate addresses.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Is Fedora Linux protected against the Meltdown and Spectre security flaws?

[Ed Greshko]

On 02/19/18 21:51, Ranjan Maitra wrote:
> What do these mean, and what is the needed mitigation, if any?


Basically, it means that everything that can currently be done to lessen the 
chances
of a security breach is being done.

Otherwise you may see something like...

Mitigation: Full generic retpoline - vulnerable module loaded

-- 
A motto of mine is: When in doubt, try it out



signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Hardware Errors

[Anne Wilson]

On 17/02/2018 17:49, Patrick O'Callaghan wrote:
> On Sat, 2018-02-17 at 17:33 +, Anne Wilson wrote:
>> On 17/02/2018, Patrick O'Callaghan wrote:
>>> Try 'journalctl -k -b' to see kernel
>>> messages since the most recent boot
>>
>> (Fabricated quote, as I never received your message in TBird.  Sorted
>> now, I think.)
>>
>> Hi, Patrick.  Tried that, resulting:
>>
>> mce: [Hardware Error]: CPU 0: M
>> mce: [Hardware Error]: TSC 0 AD
>> mce: [Hardware Error]: PROCESSO
>>
>> It's hard to be sure whether anything is not working correctly.  I am
>> having problems getting my mind back into linux mode. As you say, much
>> has changed in recent years, apart from my increasing lapses of memory.
> 
> MCE is a Machine Check Error, with is Intel-speak for a hardware error
> of some kind. See 'man mcelog'. It does look 'prima facie' like there
> may be a problem with your machine, but I'm not knowledgeable enough to
> tell you what it is.
> 
> However see 
> https://forums.fedoraforum.org/showthread.php?314118-MCE-hardware-errors-on-boot-on-new-machine
> wherein similar problems have been cured by updating the firmware.
> 
Might have to - but that's not a job to be taken lightly.  I'll wait for
a time with a clear head :-)

Anne
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Is Fedora Linux protected against the Meltdown and Spectre security flaws?

[Ranjan Maitra]

Mine are stock Fedora kernels, updated to the latest.

On Mon, 19 Feb 2018 21:44:09 +0800 Ed Greshko  wrote:

> On 02/19/18 20:14, Turritopsis Dohrnii Teo En Ming wrote:
> > What are the patches that I can download and install to be protected
> > against the Meltdown and Spectre security vulnerabilities?
> 
> (Resend to List, oops)
> 
> Yes.  As long as you don't have kernel modules which were built with a 
> non-patched gcc.
> 
> ls /sys/devices/system/cpu/vulnerabilities/*

I get:

sys/devices/system/cpu/vulnerabilities/meltdown
/sys/devices/system/cpu/vulnerabilities/spectre_v1
/sys/devices/system/cpu/vulnerabilities/spectre_v2



> cat /sys/devices/system/cpu/vulnerabilities/*


I get:

Mitigation: PTI
Mitigation: __user pointer sanitization
Mitigation: Full generic retpoline

What do these mean, and what is the needed mitigation, if any?

Many thanks and best wishes,
Ranjan
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Is Fedora Linux protected against the Meltdown and Spectre security flaws?

[Ed Greshko]

On 02/19/18 20:14, Turritopsis Dohrnii Teo En Ming wrote:
> What are the patches that I can download and install to be protected
> against the Meltdown and Spectre security vulnerabilities?

(Resend to List, oops)

Yes.  As long as you don't have kernel modules which were built with a 
non-patched gcc.

ls /sys/devices/system/cpu/vulnerabilities/*

cat /sys/devices/system/cpu/vulnerabilities/*



-- 
A motto of mine is: When in doubt, try it out



signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Is Fedora Linux protected against the Meltdown and Spectre security flaws?

[Turritopsis Dohrnii Teo En Ming]

What are the patches that I can download and install to be protected
against the Meltdown and Spectre security vulnerabilities?

===BEGIN SIGNATURE===

Turritopsis Dohrnii Teo En Ming's Academic Qualifications as at 30 Oct 2017

[1] https://tdtemcerts.wordpress.com/

[2] http://tdtemcerts.blogspot.sg/

[3] https://www.scribd.com/user/270125049/Teo-En-Ming

===END SIGNATURE===
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Dual screen

[Ed Greshko]

On 02/19/18 17:05, Patrick Dupre wrote:
>> I suspect that the high-res computer screen copies somehow its
>> own resolution to the lower res TV. That's why I asked in another
>> message for the xrandr output for all three monitors, including the one
>> for the built-in computer monitor. 

I didn't write that.  Wolfgang did.

> What do you mean by 3 monitors, including the one for the built-in computer 
> monitor?
> I have only 2 monitors.
>
>

In any event, your Samsung monitor is set to run at 1920x1080 while its native
resolution is 1366x768.

Use xrandr to set it to 1366x768 and verify that it is set to that.  Again, 
running a
LED or LCD monitor at a resolution other than their "native" resolution results 
in a
less than ideal user experience when it comes to text.


-- 
A motto of mine is: When in doubt, try it out



signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Dual screen

[Patrick Dupre]

> "Patrick Dupre"  wrote:
> 
> > >
> > > On Sun, 18 Feb 2018 11:43:35 +0100
> > > "Patrick Dupre"  wrote:
> > >   
> > > > > Subject: Re: Dual screen
> > > > >
> > > > > Allegedly, on or about 17 February 2018, stan sent:
> > > > > > Using monitors with different resolutions and dot pitches
> > > > > > at the same time must play havoc with font selection.
> > > > > 
> > > > > Modern monitors (LCDs, etc), only work at one resolution, their
> > > > > native ones.  If you don't drive the pixels with a 1:1 ratio of
> > > > > graphics generation to actual display resolution, you get a
> > > > > smudge.  Monitors should, automatically, get the right
> > > > > resolution, because they tell the computer what theirs is.
> > > > > Though some lie, or have broken data, or if you connect through
> > > > > some KVMs, that data isn't passed through.
> > > > > 
> > > > > You can have two vastly different monitors, the only noticeable
> > > > > difference should be the size of the fonts (and graphics) on one
> > > > > monitor versus the other, *IF* you're using font sizing based
> > > > > on the number of pixels (which tends to be the case).  But if
> > > > > you use point sizing, then 12 point text on one device should
> > > > > look the same as 12 point text on the other, points are an
> > > > > *absolute* size (in the same way as a 2 cm box should appear as
> > > > > 2 cm box, no matter what the display).
> > > > > 
> > > > > Display cloning/mirroring, is a problem, because you're trying
> > > > > to generate the same data on two different medium.  Independent
> > > > > dual screen, should be fine (that's what I was describing
> > > > > above).
> > > > > 
> > > > > You can play with scaling, to magnify one display, and the
> > > > > graphics rendering should neatly handle the magnification
> > > > > (render it bigger, using more dots).  But if you lie to the
> > > > > renderer about the display resolution, to get that effect,
> > > > > you're likely to get poor resolution results (render it bigger,
> > > > > stretching the dots).  Linux is sadly lacking in letting you
> > > > > easily pick font and graphics sizing.
> > > > > 
> > > > > Font rendering can be odd, thanks to smoothing or sharpening.
> > > > > For text, I prefer the idea of a font engine that generates
> > > > > text properly for the actual screen resolution.  You notice in
> > > > > terminals the different between fonts which only ever use whole
> > > > > pixels, versus the ones that put in half contrast pixels trying
> > > > > to smooth the edges, particularly on small text.  For
> > > > > terminals, try picking a font that's specifically intended for
> > > > > terminals.
> > > > 
> > > > By default, I use
> > > > Window Titles: Cantarell Bold 11
> > > > Interface: Cantarell Regular 11
> > > > Documents: Sans Regular 11
> > > > Minispace: Monospace Regular 11
> > > > Hinting: Slight (I did not see any difference and switching to
> > > > full) Antialiasing: Grayscale
> > > > Scaling factor: 1
> > > >   
> > > > > Font rendering is a bastard to control.  X, or Wayland, may
> > > > > have its own rules for general screen rendering of text.  Your
> > > > > web browser may have its own independent scheme.  The same
> > > > > probably applies for mail clients using the same engines as
> > > > > browsers (Firefox, Thunderbird, etc).
> > > > > 
> > > > > And how are you connecting them?  DVI or HDMI ought to be sharp
> > > > > and clear, with a 1:1 matching of generated graphics to display
> > > > > pixels. VGA has analogue signal which will often smear, as the
> > > > > pixel clock in the graphics card is not the same as pixel
> > > > > clocking in the monitor. 
> > > > I tried several things but without real success.
> > > > 
> > > > The motherboard has 2 ports, one VGA and one DVI.
> > > > The "old" monitor (1600x1200) is connected to the VGA and the
> > > > fonts are sharpe. The new monitor (LED/TV, 1920x1080) is HDMI and
> > > > it is connected to the DVI port by a cable (DVI -> HDMI).  
> > > 
> > > For the monitor that doesn't give you the nice results you want, try
> > > to let software do the job. So get a tool like both cvs and
> > > xrandr, if you don't have them already installed, and try the
> > > instructions on the page below for the monitor that does not work.
> > > 
> > > Please note that this hopefully might work both for mini-DPI and
> > > HDMI connections. 
> > > 
> > > Please note also that this might not work on wayland: try X11 if you
> > > can ...
> > > 
> > > https://bugzilla.redhat.com/show_bug.cgi?id=1470845#c15
> > >   
> > 
> > xrandr
> > Screen 0: minimum 320 x 200, current 3520 x 1200, maximum 8192 x 8192
> > HDMI-1 connected 1920x1080+1600+0 (normal left inverted right x axis
> > y axis) 609mm x 347mm
> 
> what's this? your new TV screen? As I mention below: I miss your built
> in computer screen.
> 
> Scroll down, please
> 
> >1366x768  59.79 +
> >1920x1080 60.00

Re: Dual screen

[Patrick Dupre]

> On Mon, 19 Feb 2018 08:43:12 +0800
> Ed Greshko  wrote:
> 
> > On 02/19/18 08:21, Patrick Dupre wrote:
> > >> Is your poorly performing monitor is connected to HDMI?  
> > > Yes  
> > >>> xrandr
> > >>> Screen 0: minimum 320 x 200, current 3520 x 1200, maximum 8192 x
> > >>> 8192 HDMI-1 connected 1920x1080+1600+0 (normal left inverted
> > >>> right x axis y axis) 609mm x 347mm 1366x768  59.79 +
> > >>>1920x1080 60.0050.0059.94*   30.0025.00
> > >>> 24.0029.9723.98  
> > >> I ask since I see an oddity in the above.  What is the model of
> > >> the monitor connected?  
> > > HDMI-1 connected 1920x1080+1600+0 (normal left inverted right x
> > > axis y axis) 609mm x 347mm 1366x768  59.79 +
> > >1920x1080 60.00*   50.0059.9430.0025.00
> > > 24.0029.9723.98  
> > >
> > > Hence, it is running in 1920x1080
> > >
> > > It is a T24E310EW Samsung
> > >  
> > Well, the specs for that monitor are at 
> > https://uk.hardware.info/product/321689/samsung-t24e310ew/specifications
> > and other places. 
> > 
> > They list the resolution at 1366x768 and you have it set to
> > 1920x1080.  Using an LCD monitor at anything other than its native
> > resolution is sure to give substandard results.
> 
> I suspect that the high-res computer screen copies somehow its
> own resolution to the lower res TV. That's why I asked in another
> message for the xrandr output for all three monitors, including the one
> for the built-in computer monitor. 

What do you mean by 3 monitors, including the one for the built-in computer 
monitor?
I have only 2 monitors.


> But it might be possible to force via xrandr some sane resolution to
> an attached monitor.
> 
> So far I'm confident we'll catch that horse ... :)
> 
> Early in the morning here - I think I'll sleep now
> -- 
> Wolfgang Pfeiffer
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org