Re: Nvidia Driver Turned Off?

2023-06-30 Thread Tim via users
On Sat, 2023-07-01 at 11:32 +1000, Stephen Morris wrote:
> Does this mean that these drivers are replaced and accessed on the fly 
> but the associated kernel modules do not become active until after a reboot?

That's generally the case.  Various library updates can only be used
after ones in memory are purged, and a reboot can be the only way to
achieve that.

For certain module updates, they're not even a binary install.  They're
compiled on your computer.  For thinks like akmods, that was somewhere
in the boot-up process.  I think some things, now, compile somewhere in
the shutdown process before a reboot.  Either way, there's a delay you
need to wait for, and interrupting it causes some chaos.  Made all the
more harder by there being little indication on-screen what's going on,
and some people will hard reset in the middle of things thinking the
computer has crashed.

> If that is the case, and that mismatch is causing the browser html 5 
> game to think hardware acceleration is not available, how does anything 
> that requires hardware acceleration to function properly ever work after 
> an update?

That is a problem that just about requires a reboot.
 
-- 
 
uname -rsvp
Linux 3.10.0-1160.92.1.el7.x86_64 #1 SMP Tue Jun 20 11:48:01 UTC 2023 x86_64
 
Boilerplate:  All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.
 
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Nvidia Driver Turned Off?

2023-06-30 Thread Stephen Morris



On 28/6/23 20:33, francis.montag...@inria.fr wrote:

Hi.

On Wed, 28 Jun 2023 18:45:51 +1000 Stephen Morris wrote:


On 26/6/23 20:17, Barry wrote:

Maybe there is user mode code that was upgraded that caused the issue?

Thanks Barry, that could have been the case but I'm not aware of any
component like that, but that doesn't mean there isn't.

As I said, in 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/6C74V5VVPE4EX5MESHTJCIPPYX5V43J4/

   During the upgrade, the Xorg nvidia drivers may have been updated. Example:

   /usr/lib64/xorg/modules/drivers/nvidia_drv.so
   /usr/lib64/xorg/modules/extensions/libglxserver_nvidia.so

This is user mode code yes.
Does this mean that these drivers are replaced and accessed on the fly 
but the associated kernel modules do not become active until after a reboot?
If that is the case, and that mismatch is causing the browser html 5 
game to think hardware acceleration is not available, how does anything 
that requires hardware acceleration to function properly ever work after 
an update?


regards,
Steve







OpenPGP_0x594338B1DE179AB2.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Restarting video driver to turn on external vga port

2023-06-30 Thread Tim via users
On Fri, 2023-06-30 at 13:26 -0400, Robert Moskowitz wrote:
> And what is EDID?  And would that come through the KVM?

It's the monitor identifying itself to the video card.  With very old
VGA monitors that could have been just one or two spare pins in the
plug grounded, indicating a certain video mode to be used (and that
sort of thing might only be noticed by a few graphics cards).  With
much more modern hardware, it's serial data transmitted from the
monitor.  The monitor literally identifies itself, and lists its
supported video modes.  Your graphics system would then look through
the table of supported modes for the monitor (scan rates and dot
clocks), likewise for the graphics card, and automatically select the
best mode that both can do.

Some KVMs can tell all their remote PCs what the attached monitor tells
it about itself.  Other's will simply provide some dummy info to get
the PC to give it a video signal.  Then you just have to hope things
work.  If you had a KVM which specifies that it only supports one or
two graphics modes, I'd suspect it's one of those that ignores your
monitors EDID.

Other users who've had problems with their monitors providing incorrect
information to their graphics card have found ways to shoehorn in their
own custom data to override it.  Going from memory, I think Tom Horsley
on this list was one of them.

The same thing (faking your own custom EDID) could help with monitors
with failing EDID circuitry, or broken VGA cable wiring.

-- 
 
NB:  All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the list.
 
The following system info data is generated fresh for each post:
 
uname -rsvp
Linux 6.2.15-100.fc36.x86_64 #1 SMP PREEMPT_DYNAMIC Thu May 11 16:51:53
UTC 2023 x86_64
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Restarting video driver to turn on external vga port

2023-06-30 Thread Robert Moskowitz



On 6/30/23 13:13, George N. White III wrote:
On Fri, Jun 30, 2023 at 1:19 PM Robert Moskowitz  
wrote:


I just rebooted after applying new updates.  In the past, this got
the external video going.  Not this time.


VGA suggests an old monitor, so try to verify that it didn't fail by 
connecting to another system or playing
with configuration options until it works.  No point wasting time on a 
dead or dying monitor that is worth less

than the cost of proper disposal.


Actually the bottleneck is my KVM which only supports VGA.  The monitor 
works fine when I switch the kvm to another system.





"|xrandr --query"may have some useful info.|


# xrandr --query
-bash: xrandr: command not found



|
|
Check "inxi -Fzx" for missing graphics hardware.


# inxi -Fzx
-bash: inxi: command not found


  There should be details in "sudo journalctl -b N"
(sudo gives details that are not included when run as regular user).   
Look at a boot that worked for lines
related to the external monitor and compare with what is in the latest 
boot.


That may take for ever.  what file do I grep to look for dates when it 
worked?  I booted the system Monday after a kernel install and the video 
worked fine then.




One thing to watch is EDID -- some older monitors have bad data that 
newer drivers reject.


And what is EDID?  And would that come through the KVM?

thanks



--
George N. White III


___
users mailing list --users@lists.fedoraproject.org
To unsubscribe send an email tousers-le...@lists.fedoraproject.org
Fedora Code of 
Conduct:https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines
List 
Archives:https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report 
it:https://pagure.io/fedora-infrastructure/new_issue
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Restarting video driver to turn on external vga port

2023-06-30 Thread George N. White III
On Fri, Jun 30, 2023 at 1:19 PM Robert Moskowitz 
wrote:

> I just rebooted after applying new updates.  In the past, this got the
> external video going.  Not this time.
>

VGA suggests an old monitor, so try to verify that it didn't fail by
connecting to another system or playing
with configuration options until it works.  No point wasting time on a dead
or dying monitor that is worth less
than the cost of proper disposal.

"xrandr --query" may have some useful info.

Check "inxi -Fzx" for missing graphics hardware.  There should be details
in "sudo journalctl -b N"
(sudo gives details that are not included when run as regular user).   Look
at a boot that worked for lines
related to the external monitor and compare with what is in the latest boot.

One thing to watch is EDID -- some older monitors have bad data that newer
drivers reject.

-- 
George N. White III
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


help with QEMM

2023-06-30 Thread Robert Moskowitz
I have an old Fedora 21 image that I use for one old program I like.  It 
did not survive the migration to F38 and I was given the following to 
get it working:


virsh create /home/rgm/Documents/f21-qemm.xml

This works, as long as qemm is not running.  But it does not survive 
system boots.  Something about this being a transient domain?


So with each system boot, where everything nicely restarts, I have to 
shut down qemm, run the above, and restart qemm.


How can I make this a permanent domain?

thanks

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Restarting video driver to turn on external vga port

2023-06-30 Thread Robert Moskowitz
I just rebooted after applying new updates.  In the past, this got the 
external video going.  Not this time.


help?

On 6/30/23 08:34, Robert Moskowitz wrote:



On 6/30/23 07:44, George N. White III wrote:
On Fri, Jun 30, 2023 at 6:56 AM Robert Moskowitz 
 wrote:


I have a Lenovo x140e running F38.

The video driver is normally the Radeon, but some time ago here I
was
told to change the amdgpu driver but

lspci -nnk | grep -iE "VGA|DISPLAY" -A3
00:01.0 VGA compatible controller [0300]: Advanced Micro Devices,
Inc.
[AMD/ATI] Kabini [Radeon HD 8330] [1002:9832]
     Subsystem: Lenovo Device [17aa:2219]
     Kernel driver in use: amdgpu
     Kernel modules: radeon, amdgpu

But sometimes after a few suspend/unsuspend when remote and no
external
VGA, this system forgets about the external monitor.


By "remote" do you mean using the laptop away from the VGA monitor or
logging in from another (remote) system?  If you are reconnecting the
VGA after using the laptop in another location, I assume the laptop
is in some "suspend" mode.  When using the VGA monitor do you also
use the laptop display or is the laptop closed?


I mean I was out from town with my notebook and no external monitor 
connected.  And I suspended before I left, and then multiple times 
while away I resumed and suspended and so forth.




Is there someway to force the video driver to wake up and see the
attached vga monitor?


First, is your system fully updated including vendor firmware (so 
others will be using

the same software versions)?


It was as of Tuesday before leaving.



Are you using F38 Workstation and Gnome?   I have a desktop that has a
monitor and a TV that is usually turned off.   When first booted the 
login

shows on the TV, so I use Settings/Displays to make the monitor the
main display.   The system never suspends, but logging out and back in
some I sometimes have to connect the TV to get the login prompt.


I use the everything network install to install workstation and Xfce.  
Should have said Xfce, as it impacts what you say below.





Have you tried Settings/Displays to detect the VGA monitor?


Both from  and from the app pull down to get into 
Settings/Display.  The external monitor is just not listed.


BTW, it is often the case with this system that the external monitor 
is not listed, but just gets turned on, which is plain weird.



   Is the
system suspended or awake when VGA is connected, and is the monitor
on or off when making the connection?  A workaround may be a simple
change to your usual routine.


Before suspending to travel, I unplug everything (power, vga, usb 
kybd/mouse) then suspend.  Once home I connect everything and then 
open the notebook.



Normally udev should handle events like
connecting an external monitor.   If you have a way to ssh into the 
laptop

you could use "udevadm monitor" to see what happens when connecting the
monitor with the laptop lid closed.


I always work at my desk with the notebook open so I have the internal 
mirroring to the external.


and

# udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

now nothing in the terminal window.  Like this is hung?  Or not 
expected to return back to the prompt?




Example for Xorg:



How is this suppose to work:

|KERNEL=="card1", SUBSYSTEM=="drm", ENV{DISPLAY}=":0", 
ENV{XAUTHORITY}="/home/vllblvck/.Xauthority", 
RUN+="/usr/bin/setup-ext-display.sh" Is KERNEL a variable or is there 
some udev file I am suppose to set up? No, at least recent, experience 
with udev stuff.. |





--
George N. White III


___
users mailing list --users@lists.fedoraproject.org
To unsubscribe send an email tousers-le...@lists.fedoraproject.org
Fedora Code of 
Conduct:https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines
List 
Archives:https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report 
it:https://pagure.io/fedora-infrastructure/new_issue



___
users mailing list --users@lists.fedoraproject.org
To unsubscribe send an email tousers-le...@lists.fedoraproject.org
Fedora Code of 
Conduct:https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines
List 
Archives:https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report 
it:https://pagure.io/fedora-infrastructure/new_issue
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduc

Re: SOLUTION: Re: journal / systemd colours ?

2023-06-30 Thread stan via users
On Fri, 30 Jun 2023 14:46:38 +0100
Barry Scott  wrote:

> > On 30 Jun 2023, at 14:15, stan via users
> >  wrote:

> > This is correct.  After I posted this, I found that it is
> > impossible to actually set the colors in journalctl because they
> > are hard coded as escape sequences when the data is written into
> > the journal.  What I had done is remove the R option to less, which
> > turns off such escape sequences.  In my case, the less options I
> > set for color then seems to highlight the ESC in light red, so I
> > know which lines journalctl wants to highlight, but not their
> > status.  That isn't optimal, but the horrible dark blue on black
> > background is gone, so I can live with it.  
> 
> I would be nice to be able to configure the colours used. Would need
> a PR against systemd I expect to get this changed.
> 
> One hack would be to edit the output and replace the escape sequence
> for the poor colour to use a replacement using sed I guess.
> 
> For example change the blue to red.
> 
> SYSTEMD_COLORS=16 journalctl  | sed 's/\x1b\[0;34m/\x1b\[0;31m/g' |
> more
> 
> I use more not less and notice that less does not show the coloured
> output.
> 
> Barry

Thanks, this worked for me with both more and less, and the red is much
more palatable. I think the default for less is not to have --use-color
set, so that is probably why it didn't work for you.  I set it on login.

This could be put as a function in .bashrc so that invoking something
like jrctl would run it automatically.  I'm not sure how that would
work for the OP who wanted to use cat though.

I tried 
$ SYSTEMD_COLORS=16 journalctl -r  | sed 's/\x1b\[0;34m/\x1b\[0;31m/g' | cat -
and it worked to send the output colored correctly to stdout, but there
was no paging, it just was a continuous stream.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: FreeIPA on Fedora and dnf system-upgrade

2023-06-30 Thread Ian Pilcher

On 6/29/23 18:40, Samuel Sieb wrote:

On 6/29/23 13:32, Ian Pilcher wrote:

I am currently running FreeIPA on CentOS 7, and I am considering moving
it to Fedora.

On RHEL and derivatives, in-place upgrades are not supported.  It is
necessary to provision a new server, running the new OS version, add it
as a FreeIPA replica, and then decommission the old system.

How does this work on Fedora?  Will I be able to use dnf system-upgrade,
or will I find myself having to use the process described above?


How did you manage to send the exact same email 3 times?


Honestly, I have no idea.  Somehow Thunderbird and GMail combined to do
that.  Hopefully it was a one-time issue.

On Fedora, you can use system-upgrade.  I have multiple freeipa VMs 
(different sites) that have been upgrading for years, probably even from 
before system-upgrade was a thing.


Perfect.  Thank you!

(And sorry about the duplicate emails.)

--

Google  Where SkyNet meets Idiocracy

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: SOLUTION: Re: journal / systemd colours ?

2023-06-30 Thread Barry Scott


> On 30 Jun 2023, at 14:15, stan via users  
> wrote:
> 
> On Thu, 29 Jun 2023 17:44:01 +0200
> lejeczek via users  > wrote:
> 
>> On 28/06/2023 20:26, stan via users wrote:
>>> Operator error.  Exporting the wrong name because of a cut and
>>> paste. Once I fixed that, definitely works to change colors in
>>> journalctl output, will have to tune it to get what I want.
>>> I put this in my .bashrc so everything is set on login.
>>> SYSTEMD_PAGER=less
>>> export SYSTEMD_PAGER
>>> SYSTEMD_LESS="[list of less options]"
>>> export SYSTEMD_LESS
>>> ___  
>> Not exactly, I'd not think of it as _the_ solution - (I much 
> 
> This is correct.  After I posted this, I found that it is impossible to
> actually set the colors in journalctl because they are hard coded as
> escape sequences when the data is written into the journal.  What I had
> done is remove the R option to less, which turns off such escape
> sequences.  In my case, the less options I set for color then seems to
> highlight the ESC in light red, so I know which lines journalctl wants
> to highlight, but not their status.  That isn't optimal, but the
> horrible dark blue on black background is gone, so I can live with it.

I would be nice to be able to configure the colours used. Would need a PR 
against systemd I expect to get this changed.

One hack would be to edit the output and replace the escape sequence for the 
poor colour to use a replacement using sed I guess.

For example change the blue to red.

SYSTEMD_COLORS=16 journalctl  | sed 's/\x1b\[0;34m/\x1b\[0;31m/g' | more

I use more not less and notice that less does not show the coloured output.

Barry


> 
>> prefer to up&down pages via actual mechanical scrolling) - 
>> as I use, always I've had, SYSTEMD_PAGER=cat so...
>> 
>> man page for 'journalctl' has a shor section:
>> When outputting to a tty, lines are colored according to 
>> priority: lines of level ERROR and higher are colored red;
>>lines of level NOTICE and higher are highlighted; 
>> lines of level DEBUG are colored lighter grey; other lines are
>>displayed normally.
>> 
>> would be nice to be able to customize those & if 'systemd' 
>> delegates declaration of that 'highlighting' colour then 
>> these below do not do it:
>> a) terminal-colors.d - perhaps systemd/journal ignores it 
>> altogether
>> b) gnome-terminal has config for 'Highlight colour'
>> 
>> It would be great/the best to have that functionality 
>> internal to systemd/journal - thus, if authors/devel might 
>> read here - please think of this conversation's subject as 
>> possible future addition/enhancement to the software.
> 
> Yes, this would be the solution.  Unless there is some setting in
> systemd already that allows for changing the colors, they are set by
> systemd when it writes things into the journal, probably based on what
> the application requests when it reports the error.
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new_issue

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: SOLUTION: Re: journal / systemd colours ?

2023-06-30 Thread stan via users
On Thu, 29 Jun 2023 17:44:01 +0200
lejeczek via users  wrote:

> On 28/06/2023 20:26, stan via users wrote:
> > Operator error.  Exporting the wrong name because of a cut and
> > paste. Once I fixed that, definitely works to change colors in
> > journalctl output, will have to tune it to get what I want.
> > I put this in my .bashrc so everything is set on login.
> > SYSTEMD_PAGER=less
> > export SYSTEMD_PAGER
> > SYSTEMD_LESS="[list of less options]"
> > export SYSTEMD_LESS
> > ___  
> Not exactly, I'd not think of it as _the_ solution - (I much 

This is correct.  After I posted this, I found that it is impossible to
actually set the colors in journalctl because they are hard coded as
escape sequences when the data is written into the journal.  What I had
done is remove the R option to less, which turns off such escape
sequences.  In my case, the less options I set for color then seems to
highlight the ESC in light red, so I know which lines journalctl wants
to highlight, but not their status.  That isn't optimal, but the
horrible dark blue on black background is gone, so I can live with it.

> prefer to up&down pages via actual mechanical scrolling) - 
> as I use, always I've had, SYSTEMD_PAGER=cat so...
> 
> man page for 'journalctl' has a shor section:
> When outputting to a tty, lines are colored according to 
> priority: lines of level ERROR and higher are colored red;
>     lines of level NOTICE and higher are highlighted; 
> lines of level DEBUG are colored lighter grey; other lines are
>     displayed normally.
> 
> would be nice to be able to customize those & if 'systemd' 
> delegates declaration of that 'highlighting' colour then 
> these below do not do it:
> a) terminal-colors.d - perhaps systemd/journal ignores it 
> altogether
> b) gnome-terminal has config for 'Highlight colour'
> 
> It would be great/the best to have that functionality 
> internal to systemd/journal - thus, if authors/devel might 
> read here - please think of this conversation's subject as 
> possible future addition/enhancement to the software.

Yes, this would be the solution.  Unless there is some setting in
systemd already that allows for changing the colors, they are set by
systemd when it writes things into the journal, probably based on what
the application requests when it reports the error.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Restarting video driver to turn on external vga port

2023-06-30 Thread Robert Moskowitz



On 6/30/23 07:44, George N. White III wrote:
On Fri, Jun 30, 2023 at 6:56 AM Robert Moskowitz  
wrote:


I have a Lenovo x140e running F38.

The video driver is normally the Radeon, but some time ago here I was
told to change the amdgpu driver but

lspci -nnk | grep -iE "VGA|DISPLAY" -A3
00:01.0 VGA compatible controller [0300]: Advanced Micro Devices,
Inc.
[AMD/ATI] Kabini [Radeon HD 8330] [1002:9832]
     Subsystem: Lenovo Device [17aa:2219]
     Kernel driver in use: amdgpu
     Kernel modules: radeon, amdgpu

But sometimes after a few suspend/unsuspend when remote and no
external
VGA, this system forgets about the external monitor.


By "remote" do you mean using the laptop away from the VGA monitor or
logging in from another (remote) system?  If you are reconnecting the
VGA after using the laptop in another location, I assume the laptop
is in some "suspend" mode.  When using the VGA monitor do you also
use the laptop display or is the laptop closed?


I mean I was out from town with my notebook and no external monitor 
connected.  And I suspended before I left, and then multiple times while 
away I resumed and suspended and so forth.




Is there someway to force the video driver to wake up and see the
attached vga monitor?


First, is your system fully updated including vendor firmware (so 
others will be using

the same software versions)?


It was as of Tuesday before leaving.



Are you using F38 Workstation and Gnome?   I have a desktop that has a
monitor and a TV that is usually turned off.   When first booted the 
login

shows on the TV, so I use Settings/Displays to make the monitor the
main display.   The system never suspends, but logging out and back in
some I sometimes have to connect the TV to get the login prompt.


I use the everything network install to install workstation and Xfce.  
Should have said Xfce, as it impacts what you say below.





Have you tried Settings/Displays to detect the VGA monitor?


Both from  and from the app pull down to get into 
Settings/Display.  The external monitor is just not listed.


BTW, it is often the case with this system that the external monitor is 
not listed, but just gets turned on, which is plain weird.



   Is the
system suspended or awake when VGA is connected, and is the monitor
on or off when making the connection?  A workaround may be a simple
change to your usual routine.


Before suspending to travel, I unplug everything (power, vga, usb 
kybd/mouse) then suspend.  Once home I connect everything and then open 
the notebook.



Normally udev should handle events like
connecting an external monitor.   If you have a way to ssh into the laptop
you could use "udevadm monitor" to see what happens when connecting the
monitor with the laptop lid closed.


I always work at my desk with the notebook open so I have the internal 
mirroring to the external.


and

# udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

now nothing in the terminal window.  Like this is hung?  Or not expected 
to return back to the prompt?




Example for Xorg:



How is this suppose to work:

|KERNEL=="card1", SUBSYSTEM=="drm", ENV{DISPLAY}=":0", 
ENV{XAUTHORITY}="/home/vllblvck/.Xauthority", 
RUN+="/usr/bin/setup-ext-display.sh" Is KERNEL a variable or is there 
some udev file I am suppose to set up? No, at least recent, experience 
with udev stuff.. |






--
George N. White III


___
users mailing list --users@lists.fedoraproject.org
To unsubscribe send an email tousers-le...@lists.fedoraproject.org
Fedora Code of 
Conduct:https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines
List 
Archives:https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report 
it:https://pagure.io/fedora-infrastructure/new_issue
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Restarting video driver to turn on external vga port

2023-06-30 Thread George N. White III
On Fri, Jun 30, 2023 at 6:56 AM Robert Moskowitz 
wrote:

> I have a Lenovo x140e running F38.
>
> The video driver is normally the Radeon, but some time ago here I was
> told to change the amdgpu driver but
>
> lspci -nnk | grep -iE "VGA|DISPLAY" -A3
> 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
> [AMD/ATI] Kabini [Radeon HD 8330] [1002:9832]
>  Subsystem: Lenovo Device [17aa:2219]
>  Kernel driver in use: amdgpu
>  Kernel modules: radeon, amdgpu
>
> But sometimes after a few suspend/unsuspend when remote and no external
> VGA, this system forgets about the external monitor.
>

By "remote" do you mean using the laptop away from the VGA monitor or
logging in from another (remote) system?  If you are reconnecting the
VGA after using the laptop in another location, I assume the laptop
is in some "suspend" mode.  When using the VGA monitor do you also
use the laptop display or is the laptop closed?

>
> Is there someway to force the video driver to wake up and see the
> attached vga monitor?
>

First, is your system fully updated including vendor firmware (so others
will be using
the same software versions)?

Are you using F38 Workstation and Gnome?   I have a desktop that has a
monitor and a TV that is usually turned off.   When first booted the login
shows on the TV, so I use Settings/Displays to make the monitor the
main display.   The system never suspends, but logging out and back in
some I sometimes have to connect the TV to get the login prompt.

Have you tried Settings/Displays to detect the VGA monitor?   Is the
system suspended or awake when VGA is connected, and is the monitor
on or off when making the connection?  A workaround may be a simple
change to your usual routine.  Normally udev should handle events like
connecting an external monitor.   If you have a way to ssh into the laptop
you could use "udevadm monitor" to see what happens when connecting the
monitor with the laptop lid closed.

Example for Xorg:
<
https://unix.stackexchange.com/questions/675024/udev-rule-for-connecting-external-display-not-working
>

-- 
George N. White III
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Restarting video driver to turn on external vga port

2023-06-30 Thread Robert Moskowitz

I have a Lenovo x140e running F38.

The video driver is normally the Radeon, but some time ago here I was 
told to change the amdgpu driver but


lspci -nnk | grep -iE "VGA|DISPLAY" -A3
00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Kabini [Radeon HD 8330] [1002:9832]

    Subsystem: Lenovo Device [17aa:2219]
    Kernel driver in use: amdgpu
    Kernel modules: radeon, amdgpu

But sometimes after a few suspend/unsuspend when remote and no external 
VGA, this system forgets about the external monitor.


Is there someway to force the video driver to wake up and see the 
attached vga monitor?


thanks
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue