Re: [gentoo-user] Re: KDE6 and Pipewire control change

[Dale]

Dale wrote:
> Dale wrote:
>> Mark Knecht wrote:
>>>
>>>
>>> On Wed, Jul 3, 2024 at 6:33 AM Dale >> > wrote:
>>> 
>>> > Actually, it does.  Thing is, it doesn't show the HDMI as a option in
>>> > the list.  I bet the reason it doesn't show up under applications like
>>> > it did before is because it only sees the main speakers as a
>>> option.  No
>>> > need showing options when there is none.  So, I need to figure out how
>>> > to make it see HDMI as a option as well as main speakers.  Then
>>> maybe it
>>> > will show up under applications again.  I'd be back in business then.
>>> >
>>> > Something to work on when I get back from town.  Today is shot day.
>>> > :/   And grocery shopping.  Gotta eat.
>>>
>>> Audio over HDMI is not a requirement of the HDMI spec, it's an
>>> option.
>>>
>>> You might want to look at the specs for your card to see if NVidia 
>>> included it in the chipset. Graphics adapters intended for use in
>>> Bloomberg Stations might not include it.
>>>
>>> Typically
>>>
>>> lspci | grep Audio
>>>
>>> should tell you something.
>>>
>>> Good luck,
>>> Mark
>>
>>
>> Well, until the recent KDE upgrade, it worked.  I just had a easy way
>> to do it.  So I know the hardware is capable of it.  I just need to
>> figure out the software issue.  Since it doesn't see it now, I need
>> to figure out why it isn't being seen and fix it.  I may just need to
>> configure something.  Having it done in pipewire tho sure was handy. 
>> I hope that feature isn't gone for some reason.  As it is, I have to
>> manually tell Smplayer to send the audio to the HDMI port in
>> Preferences.  It works but I have to disable that to have sound on my
>> main speakers.  Thing is, on rare occasion I want to play a video on
>> the TV with mpv.  Doing it with pipewire made even it easy to
>> switch.  I just click on it, select for it to go to HDMI, done.  The
>> next time I play something with mpv, it goes back to the default. 
>> Really nifty. 
>>
>> Given the recent upgrade, I may just try logging out and back in. 
>> Maybe it just didn't pick it up last time.  It's not likely but
>> possible.  One can hope.  :-D
>>
>> Neighbor is sick.  Gotta go mow about 4 acres of grass.  Poor thing. 
>> He has issues.  :/  It's already 90F. 
>>
>> Dale
>>
>> :-)  :-) 
>
>
> Someone wrote me off list.  They not subscribed but read my post
> somehow.  Anyway, they recommended installing pavucontrol-qt and using
> the Pro Audio setting.  That package was already installed.  I'd never
> used Pro Audio before, didn't know what it was so didn't know it was a
> usable option.  However, when I selected it, all my options came
> back.  I got my three little horizontal lines back.  One of the
> options is HDMI again. 
>
> So, that's working again.  I hope this might help someone else who
> runs into this problem.  I won't be surprised tho if the original
> option comes back after I log out and back in again.  Weirder things
> have happened.  ;-)
>
> Thanks to all. 
>
> Dale
>
> :-)  :-) 


Oh, forgot to mention, I enabled that option in KDE System Settings
under Sound.  For me, it was at the top.  Could vary tho. 

Also, the monitor I bought dropped in price.  I ordered a second one. 
Should be here before to long.  My current 27" monitor will become the
monitor that moves from whatever system I need to use.  I plan to check
the power supply again in the LG but may retire it, just use it on that
rare occasion I need something simple but don't rely on it. 

Dale

:-)  :-) 

Re: [gentoo-user] Re: KDE6 and Pipewire control change

[Dale]

Dale wrote:
> Mark Knecht wrote:
>>
>>
>> On Wed, Jul 3, 2024 at 6:33 AM Dale > > wrote:
>> 
>> > Actually, it does.  Thing is, it doesn't show the HDMI as a option in
>> > the list.  I bet the reason it doesn't show up under applications like
>> > it did before is because it only sees the main speakers as a
>> option.  No
>> > need showing options when there is none.  So, I need to figure out how
>> > to make it see HDMI as a option as well as main speakers.  Then
>> maybe it
>> > will show up under applications again.  I'd be back in business then.
>> >
>> > Something to work on when I get back from town.  Today is shot day.
>> > :/   And grocery shopping.  Gotta eat.
>>
>> Audio over HDMI is not a requirement of the HDMI spec, it's an
>> option.
>>
>> You might want to look at the specs for your card to see if NVidia 
>> included it in the chipset. Graphics adapters intended for use in
>> Bloomberg Stations might not include it.
>>
>> Typically
>>
>> lspci | grep Audio
>>
>> should tell you something.
>>
>> Good luck,
>> Mark
>
>
> Well, until the recent KDE upgrade, it worked.  I just had a easy way
> to do it.  So I know the hardware is capable of it.  I just need to
> figure out the software issue.  Since it doesn't see it now, I need to
> figure out why it isn't being seen and fix it.  I may just need to
> configure something.  Having it done in pipewire tho sure was handy. 
> I hope that feature isn't gone for some reason.  As it is, I have to
> manually tell Smplayer to send the audio to the HDMI port in
> Preferences.  It works but I have to disable that to have sound on my
> main speakers.  Thing is, on rare occasion I want to play a video on
> the TV with mpv.  Doing it with pipewire made even it easy to switch. 
> I just click on it, select for it to go to HDMI, done.  The next time
> I play something with mpv, it goes back to the default.  Really nifty. 
>
> Given the recent upgrade, I may just try logging out and back in. 
> Maybe it just didn't pick it up last time.  It's not likely but
> possible.  One can hope.  :-D
>
> Neighbor is sick.  Gotta go mow about 4 acres of grass.  Poor thing. 
> He has issues.  :/  It's already 90F. 
>
> Dale
>
> :-)  :-) 


Someone wrote me off list.  They not subscribed but read my post
somehow.  Anyway, they recommended installing pavucontrol-qt and using
the Pro Audio setting.  That package was already installed.  I'd never
used Pro Audio before, didn't know what it was so didn't know it was a
usable option.  However, when I selected it, all my options came back. 
I got my three little horizontal lines back.  One of the options is HDMI
again. 

So, that's working again.  I hope this might help someone else who runs
into this problem.  I won't be surprised tho if the original option
comes back after I log out and back in again.  Weirder things have
happened.  ;-)

Thanks to all. 

Dale

:-)  :-) 

Re: [gentoo-user] Re: KDE6 and Pipewire control change

[Dale]

Mark Knecht wrote:
>
>
> On Wed, Jul 3, 2024 at 6:33 AM Dale  > wrote:
> 
> > Actually, it does.  Thing is, it doesn't show the HDMI as a option in
> > the list.  I bet the reason it doesn't show up under applications like
> > it did before is because it only sees the main speakers as a option.  No
> > need showing options when there is none.  So, I need to figure out how
> > to make it see HDMI as a option as well as main speakers.  Then maybe it
> > will show up under applications again.  I'd be back in business then.
> >
> > Something to work on when I get back from town.  Today is shot day.
> > :/   And grocery shopping.  Gotta eat.
>
> Audio over HDMI is not a requirement of the HDMI spec, it's an
> option.
>
> You might want to look at the specs for your card to see if NVidia 
> included it in the chipset. Graphics adapters intended for use in
> Bloomberg Stations might not include it.
>
> Typically
>
> lspci | grep Audio
>
> should tell you something.
>
> Good luck,
> Mark


Well, until the recent KDE upgrade, it worked.  I just had a easy way to
do it.  So I know the hardware is capable of it.  I just need to figure
out the software issue.  Since it doesn't see it now, I need to figure
out why it isn't being seen and fix it.  I may just need to configure
something.  Having it done in pipewire tho sure was handy.  I hope that
feature isn't gone for some reason.  As it is, I have to manually tell
Smplayer to send the audio to the HDMI port in Preferences.  It works
but I have to disable that to have sound on my main speakers.  Thing is,
on rare occasion I want to play a video on the TV with mpv.  Doing it
with pipewire made even it easy to switch.  I just click on it, select
for it to go to HDMI, done.  The next time I play something with mpv, it
goes back to the default.  Really nifty. 

Given the recent upgrade, I may just try logging out and back in.  Maybe
it just didn't pick it up last time.  It's not likely but possible.  One
can hope.  :-D

Neighbor is sick.  Gotta go mow about 4 acres of grass.  Poor thing.  He
has issues.  :/  It's already 90F. 

Dale

:-)  :-) 

Re: [gentoo-user] New monitor, new problem. Everything LARGE O_O

[Michael]

On Wednesday, 3 July 2024 10:22:33 BST Dale wrote:

> Another update.  I rebooted several times to make sure whether things
> would be consistent.  Most of the time, it came up as it should.  Some
> times, not so much.  When I had just the new Samsung monitor connected,
> it was consistent.  When I added the old LG, it would not always come up
> like it should.  The biggest thing, the plasma panel would be on the
> wrong monitor. 

If you are adding a second monitor then you need an additional "Monitor" 
section with a different identifier in your xorg.conf for a multi-headed 
setup.  You need to add in the first monitor section:

Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName  "Samsung LS32B30"
HorizSync   30.0 - 84.0
VertRefresh 50.0 - 75.0
Option "PreferredMode" "1920x1080_60.00"
Option "Primary" "true"
Option "DPMS" "true"
EndSection

and then in the second monitor section:

Section "Monitor"
Identifier "Monitor1"
VendorName "Unknown"
ModelName  "LG blah-blah"
Option "PreferredMode" "1920x1080_60.00"
Option "RightOf" "Monitor0"
Option "DPMS" "true"
EndSection

Section "Screen" 
Identifier "Screen0"
Device "Device0"
Monitor"Monitor0"
SubSection "Display"
Depth   24
Virtual 3840 1080 # 1920 + 1920 (3840), 1080 + 0 (1080)
EndSubSection
EndSection

You'll get the correct identifiers and "Modelines", "PreferredMode", 
resolution, refresh rate, etc. values for the above by using 'xrandr -q'.


> I tried using xrandr to set this but it kept changing what monitors was
> connected where which would throw off what monitor got what priority.

Manually instructing xranrd to set up your monitors will not survive between 
reboots unless you store its settings in your xorg.conf.  You need to rerun it 
each time, manually or via a script.  Or, you just set correctly your 
xorg.conf once and then you can forget about it.  ;-)


> Finally, I removed the old LG.  It has caused enough grief already.  I
> unhooked the TV cable for my bedroom TV and connected it to the new
> rig.  I then booted.  I installed a package called arandr.  It's a
> sister to xrandr but GUI based.  Makes it very easy to see what is
> what.  On the first boot, the Samsung showed as connected to port 1. 
> The TV showed as port 3 I think.  It seems each port can do two displays
> so it kinda skips.  The first port is actually 0.  Anyway, I used arandr
> to set it up like I wanted.  I saved the file with the command in my
> home directory.  I then moved the command to a file in
> /etc/X11/xinit/xinitrc.d/ as a file.  They are usually started with a
> number in the file name.  Don't forget to add the bash bit on the first
> line if needed and make it executable as well.  Once I did that, the
> displays worked like they should.  So far at least.
> 
> The lesson to be learned is this.  When you have a monitor that is
> having issues and keeps showing as connected to different ports and
> such, you can't use that display to get a reliable configuration that
> will survive a reboot, maybe even a power off and back on.  Another
> thing, using either xrandr or arandr is a nifty feature if set up
> correctly.  Those two make it so a display, or set of displays more
> importantly, work like you want.  The arnadr command since it is a GUI,
> makes it a lot easier to create the xrandr command with the right
> options.  If you use that route tho, make sure all monitors are
> connected and on before starting.  You may can do it without it with
> xrandr but arandr needs the monitor to be on and working.  The other
> thing, putting the setting in /etc/X11/xinit/xinitrc.d/ seems to work
> pretty well.  So far at least. 
> 
> To be honest tho, I wish Nvidia would generate a conf file that contains
> both monitors and I could set it up properly there.  Then when I boot
> up, it reads that file and knows what monitor is what long before DM
> and/or sddm even starts.  It could also keep a monitor powered on even
> while on a console with nothing GUI running.  I kinda wish we could do
> it like we did back in the old days. 
> 
> I also had another thought. When changing the xorg.conf file, I wonder
> if it only reads that file when loading the nvidia drivers but not when
> DM is started/restarted.  I noticed on my system, when I booted but have
> not started DM, the Nvidia drivers were already loaded.  I'm not sure
> when the xorg.conf file is loaded but if it is loaded when the drivers
> load, then that could explain why some changes didn't make any changes
> to the display.  The changes were not seen unless I rebooted which I
> didn't always do.  Maybe someone here knows what order this happens in. 
> It could explain a lot tho. 

I think if you change parameters in the "Device" section for the graphics 
driver in your xorg.conf, you need to rel

Re: [gentoo-user] Re: KDE6 and Pipewire control change

[Mark Knecht]

On Wed, Jul 3, 2024 at 6:33 AM Dale  wrote:

> Actually, it does.  Thing is, it doesn't show the HDMI as a option in
> the list.  I bet the reason it doesn't show up under applications like
> it did before is because it only sees the main speakers as a option.  No
> need showing options when there is none.  So, I need to figure out how
> to make it see HDMI as a option as well as main speakers.  Then maybe it
> will show up under applications again.  I'd be back in business then.
>
> Something to work on when I get back from town.  Today is shot day.
> :/   And grocery shopping.  Gotta eat.

Audio over HDMI is not a requirement of the HDMI spec, it's an
option.

You might want to look at the specs for your card to see if NVidia
included it in the chipset. Graphics adapters intended for use in
Bloomberg Stations might not include it.

Typically

lspci | grep Audio

should tell you something.

Good luck,
Mark

Re: [gentoo-user] world upgrade a mess, need some advise

[Dale]

Michael wrote:
> On Wednesday, 3 July 2024 01:34:12 BST Dale wrote:
>>
>> All I've ever seen is --depclean and preserved rebuild.  I don't recall
>> ever seeing anything else.  If a package fails, then it tacks the log
>> file on the end, sometimes of multiple packages.  To be honest tho, if
>> it fails, most of the time that isn't useful either.  Usually the actual
>> error is way up somewhere.  I've never seen anything about perl, python
>> or that sort of thing before. 
>>
>> It could be that my emerge options are good enough that it doesn't
>> trigger any of those.  When I had to run perl cleaner a while back tho,
>> I wish emerge had gave me a hint that it needed to be run if it couldn't
>> fix it itself.  Then again, it may not have known about it either. 
>>
>> I plan to run it and if it does nothing, at least then I know my system
>> is set up correctly. It's better than not doing it and having weird
>> problems that are hard to figure out the cause of. 
>>
>> Dale
>>
>> :-)  :-) 
> When perl itself is updated emerge let's you know to run perl-cleaner with a 
> message at the end.


Well, it missed it that time I had issues then.  o_O 

Dale

:-)  :-) 

Re: [gentoo-user] Re: KDE6 and Pipewire control change

[Dale]

Nikos Chantziaras wrote:
> On 02/07/2024 15:46, Dale wrote:
>> I can't find the controls I used to have with the new
>> pipewire.
> Does it show up in the "Devices" tab?
>
>
>


Actually, it does.  Thing is, it doesn't show the HDMI as a option in
the list.  I bet the reason it doesn't show up under applications like
it did before is because it only sees the main speakers as a option.  No
need showing options when there is none.  So, I need to figure out how
to make it see HDMI as a option as well as main speakers.  Then maybe it
will show up under applications again.  I'd be back in business then. 

Something to work on when I get back from town.  Today is shot day. 
:/   And grocery shopping.  Gotta eat. 

Dale

:-)  :-) 

[gentoo-user] Re: KDE6 and Pipewire control change

[Nikos Chantziaras]

On 02/07/2024 15:46, Dale wrote:

I can't find the controls I used to have with the new
pipewire.

Does it show up in the "Devices" tab?

Re: [gentoo-user] world upgrade a mess, need some advise

[Michael]

On Wednesday, 3 July 2024 01:34:12 BST Dale wrote:
> Eli Schwartz wrote:
> > On 7/2/24 7:33 PM, Dale wrote:
> >> What I wish, emerge would spit the information out after it completes
> >> instead of putting fairly important info in some log files somewhere for
> >> a person to go dig and find.  It already tells us we should run
> >> --depclean.  Why can't it tell us when we need to run some python tool,
> >> perl or anything else as well that has been triggered.  I've never seen
> >> emerge tell me to run anything but --depclean or preserved rebuild and
> >> to be honest, if a package isn't used, it likely doesn't hurt anything
> >> that it is still installed.  It's just cruft left behind.  Having a
> >> broken python, perl or some other important package should give us a
> >> notice at the end.  That to me would be more important than running
> >> -depclean.  Running preserved rebuild is important tho.
> >> 
> >> One thing about it, if it doesn't need to fix anything, I guess it does
> >> nothing.  Might upset a few electrons while checking is all.  ;-)
> > 
> > ... but it already does exactly this?
> > 
> > When a package emits a warning in the middle of 50 other packages being
> > compiled and installed... portage collects warnings and repeats them at
> > the end for you.
> > 
> > It doesn't matter because the package manager already rebuilds pretty
> > much all perl modules. Running perl-cleaner is advised "in case portage
> > missed something" which probably means "it wasn't part of @world".
> 
> All I've ever seen is --depclean and preserved rebuild.  I don't recall
> ever seeing anything else.  If a package fails, then it tacks the log
> file on the end, sometimes of multiple packages.  To be honest tho, if
> it fails, most of the time that isn't useful either.  Usually the actual
> error is way up somewhere.  I've never seen anything about perl, python
> or that sort of thing before. 
> 
> It could be that my emerge options are good enough that it doesn't
> trigger any of those.  When I had to run perl cleaner a while back tho,
> I wish emerge had gave me a hint that it needed to be run if it couldn't
> fix it itself.  Then again, it may not have known about it either. 
> 
> I plan to run it and if it does nothing, at least then I know my system
> is set up correctly. It's better than not doing it and having weird
> problems that are hard to figure out the cause of. 
> 
> Dale
> 
> :-)  :-) 

When perl itself is updated emerge let's you know to run perl-cleaner with a 
message at the end.

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] New monitor, new problem. Everything LARGE O_O

[Dale]

Dale wrote:
> Micheal and I had a email or two off list.  This is what I think the
> problem was.  Nvidia and KDE was clashing with each other.  I ended up
> connecting both the new monitor and old LG that gave me so much
> trouble.  I think Nvidia wanted to set the first port as primary but KDE
> wanted to set the 2nd port because I had that monitor connected before
> and it remembered it or something.  I set Nvidia GUI settings to what I
> wanted but it was still making everything HUGE.  I found the settings
> for KDE and actually reversed it.  One reason I wanted to reverse it,
> the plasma panel on the bottom was also on the wrong monitor.  It was on
> port 2, the old LG monitor, and I wanted it on port 1, the new Samsung
> monitor.  That's how I want it when I switch rigs as well.  Anyway, when
> I set it in KDE backwards, the mouse and such got a little weird.  I had
> to figure out how to get from one screen to another.  You may want to do
> that before changing settings.  Once I set it up backwards, I hit
> apply.  I think it had a confirm box for this which is why you need to
> know how to get the mouse pointer from one display to the other.  After
> I did that, I checked Nvidia and it still had the same settings for
> where displays were.  I then went back to the KDE settings and set them
> correctly.  I set Samsung as primary, new monitor, and LG as Right of
> Samsung.  I hit apply.  The screens blinked, plasma moved to the Samsung
> monitor and that HUGE problem went away.  Things are larger but just
> because it is a larger monitor.  Basically, it is as it should be. 
> Oddly, the old LG monitor works pretty well now too.  ROFL
>
> If I had the new monitor and used it from the beginning, it might have
> just worked.  I think KDE remembered it and insisted on making it
> primary instead of what I was telling Nvidia.  Setting it backwards and
> then setting it the correct way forced KDE to rethink the settings. 
> This may be a rare problem to run into but if someone reading this ever
> recycles a system and connects things differently, this may help. 
> Forcing KDE to do something backwards and then setting it to the correct
> way just may force KDE to forget previous info and work like you want it
> too. 
>
> I'm still trying to decide if I want to keep using the splitter or not. 
> I could bypass the splitter and connect directly to a video card port. 
> I'm just not sure why I should rework my cabling tho. 
>
> Thanks to all for the help, Micheal and Mark for sure.  I hope this info
> will help someone else tho.  When one of us beats something into
> submission, we can all learn from it.  It's why I read almost every post
> on this list.  It just might come in handy one day, if I remember what I
> read.  LOL 
>
> Dale
>
> :-)  :-) 
>

Another update.  I rebooted several times to make sure whether things
would be consistent.  Most of the time, it came up as it should.  Some
times, not so much.  When I had just the new Samsung monitor connected,
it was consistent.  When I added the old LG, it would not always come up
like it should.  The biggest thing, the plasma panel would be on the
wrong monitor. 

I tried using xrandr to set this but it kept changing what monitors was
connected where which would throw off what monitor got what priority. 
Finally, I removed the old LG.  It has caused enough grief already.  I
unhooked the TV cable for my bedroom TV and connected it to the new
rig.  I then booted.  I installed a package called arandr.  It's a
sister to xrandr but GUI based.  Makes it very easy to see what is
what.  On the first boot, the Samsung showed as connected to port 1. 
The TV showed as port 3 I think.  It seems each port can do two displays
so it kinda skips.  The first port is actually 0.  Anyway, I used arandr
to set it up like I wanted.  I saved the file with the command in my
home directory.  I then moved the command to a file in
/etc/X11/xinit/xinitrc.d/ as a file.  They are usually started with a
number in the file name.  Don't forget to add the bash bit on the first
line if needed and make it executable as well.  Once I did that, the
displays worked like they should.  So far at least.

The lesson to be learned is this.  When you have a monitor that is
having issues and keeps showing as connected to different ports and
such, you can't use that display to get a reliable configuration that
will survive a reboot, maybe even a power off and back on.  Another
thing, using either xrandr or arandr is a nifty feature if set up
correctly.  Those two make it so a display, or set of displays more
importantly, work like you want.  The arnadr command since it is a GUI,
makes it a lot easier to create the xrandr command with the right
options.  If you use that route tho, make sure all monitors are
connected and on before starting.  You may can do it without it with
xrandr but arandr needs the monitor to be on and working.  The other
thing, putting the setting in /etc/X11/xinit/xinitrc.d/ seem