Re: [gentoo-user] can't start X as user

[Jack]

On 6/13/23 20:21, Philip Webb wrote:

My new machine has no problem with graphics using System Rescue etc
nor using 'startx' as root with Gentoo, but it refuses to start as user.

I've had a series of errors :

   parse_vt_settings : can't open /dev/tty0 (permission denied)

after adding my user to 'tty input' in 'group' :

   can't open virtual console 7 : permission denied

after adding 'elogind' to 'default' runlevel & starting it :

   xf86EnableIO : failed to enable I/O ports -03ff
(operation not permitted)

yes, my user is in the 'video' group & 'xorg-server' has  USE="elogind" .

In my current machine, there is a  /dev/fb0  with permission  660 .
but there is no such device in the new machine.

I've looked at several "solved" cases of the same error messages,
but they don't seem to help my problem.

Can anyone offer possible solutions ?


what does "ll /dev/tty*" show?  I see lots of them, including 0, 
although I can't say which are relevant.  It does seem odd if you don't 
have any.  Have you compared kernel config on the machine that works and 
the one that doesn't?


what does /var/log/Xorg.0.log show?  It's likely to be more voluminous 
than output to console.


what's in ~/.xinitrc?  I don't actually suspect anything there, but it 
might be relevant.


In my case, X is started on the same virtual console it is invoked from, 
but I don't remember where the change from always using 7 shows up in 
any config file.  However, that does suggest some permission error MIGHT 
be relevant (but no guarantees.)

[gentoo-user] can't start X as user

[Philip Webb]

My new machine has no problem with graphics using System Rescue etc
nor using 'startx' as root with Gentoo, but it refuses to start as user.

I've had a series of errors :

  parse_vt_settings : can't open /dev/tty0 (permission denied)

after adding my user to 'tty input' in 'group' :

  can't open virtual console 7 : permission denied

after adding 'elogind' to 'default' runlevel & starting it :

  xf86EnableIO : failed to enable I/O ports -03ff
   (operation not permitted)

yes, my user is in the 'video' group & 'xorg-server' has  USE="elogind" .

In my current machine, there is a  /dev/fb0  with permission  660 .
but there is no such device in the new machine.

I've looked at several "solved" cases of the same error messages,
but they don't seem to help my problem.

Can anyone offer possible solutions ?

-- 
,,
SUPPORT ___//___,   Philip Webb
ELECTRIC   /] [] [] [] [] []|   Cities Centre, University of Toronto
TRANSIT`-O--O---'   purslowatchassdotutorontodotca

Re: [gentoo-user] some help with wayland

[Jack]

On 2023.06.13 04:52, Michael wrote:

On Tuesday, 13 June 2023 01:01:43 BST Wol wrote:
> On 10/06/2023 09:44, Michael wrote:
Without sddm, you can run the startplasma-wayland stanza from a  
console, do your thing, logout and the console would have captured  
various logs - just as startx does.

>
Does that actually work now? Last I tried I ended up looking for the  
docu, and found that it said that was a bad idea and not guaranteed  
to work. Certainly on my system, it just hung with, iirc, no logs  
whatsoever.

>
> Once I enabled sddm.service, it worked fine ...
>
> Cheers,
> Wol

It works here with Radeon graphics and Intel graphics (no Nvidia to  
try):


dbus-run-session startplasma-wayland

What works less satisfactorily or not at all on this laptop, is  
Ctrl+Alt+F2 or some other console and then returning to F1.  The  
wayland desktop rendering is corrupted with horizontal tearing and  
flickering on the monitor.  I can't see any menus to restart/logout.   
Sadly Ctrl+Alt+Backspace has no effect on it. If/when it locks  
completely the magic SysRq key combo does not work either.
Well, switching consoles was working for me for a while, but is now  
broken as described.  However, typing Alt-F2 and then logout, then  
hitting Enter, seems to end the session, apparently cleanly (or cleanly  
enough?).  I first tried "kwin_wayland --replace" but without success.   
I'm not certain if it needs some other parameter to be fully  
successful, as on at least one try, the screen went totally black for a  
bit, then the mouse pointer reappeared, but nothing else.


Due to muscle memory, dropping in a console is a regular occurrence  
with me, so I only launch wayland with sddm.  Sessions started with  
sddm can be recovered, if I first return to F7 where sddm is running,  
then to F8 where the wayland session is.

RE: [gentoo-user] Re: Can't upgrade portage or update/install ebuilds

[Laurence Perkins]

>From: Mitch D. futurehyp...@gmail.com
>Sent: Tuesday, June 13, 2023 9:36 AM
>To: gentoo-user@lists.gentoo.org
>Subject: Re: [gentoo-user] Re: Can't upgrade portage or update/install ebuilds
>
>On Tue, Jun 13, 2023 at 10:38 AM Grant Edwards 
>grant.b.edwa...@gmail.com wrote:
>On 2023-06-12, Wol antli...@youngman.org.uk 
>wrote:
>> On 09/06/2023 21:16, Grant Edwards wrote:
>>> On 2023-06-09, Daniel Pielmeier bil...@gentoo.org 
>>> wrote:
>>>
 If it is only about gemato then temporary disable the rsync-verify flag
 which pulls it in.

 # USE="-rsync-verify" emerge sys-apps/portage
>>>
>>> The problem I ran into is that you never know how many issues there
>>> are standing in the way of upgrading. The one time I decided to muscle
>>> my way through updating an "obsolete" Gentoo install, [...]
>>>
>>> You do learn alot about how portage/emerge works...
>>>
>> Learning that is a good idea maybe :-)
>>
>> But last time I had a well-out-of-date system, it was a long and
>> messy process ...
>>
>> What I did was, every time portage said "giving up" or "conflict found"
>> or whatever, I just took a note of as many of the packages I could
>> remember that portage said it could emerge, and then manually updated
>> them "emerge --update --one-shot".
>>
>> And any conflicts, if I dared, I simply deleted then "emerge -C --one-shot".
>
>IIRC, at one point Python was one of those problems, and I stupidly
>removed Python before realizing what that meant...
>
>Hilarity ensued.
>
>Removing/skipping as many of the non-essential "big" packages and
>their dependancies and getting the base system updated is indeed the
>best way to go.
>
>I second this approach. When rescuing a Gentoo system, my first step would be 
>to deselect any and every non-critical package from @world, then try to get 
>@system updated through any means necessary. In the past, I've removed 
>packages instead of deselecting them, but I've had cases where depclean 
>refused to do anything because there were already dependency problems, and 
>sometimes it's hard to know what's safe to unmerge with "-C".
>
I have noticed that doing a --unmerge on virtual/* clears away whole sections 
of conflicts in a lot of cases.

Doing the same on dev-perl/* is a decent trick too if it's snarled enough that 
perl-cleaner runs into conflicts.  But sometimes perl dependencies aren't 
correctly spelled out, so you may have to reinstall some of it by hand in some 
cases.

And you'd be surprised how many “hard” dependency version requirements are 
“softer” than expected.  Using the "ebuild" tool to force it to "just do what 
it's told" and install the new version, and then "emerge -e @world" at the end 
of it all to clean up any mess uses a lot of machine time, but it can save a 
lot of human time.

LMP

Re: [gentoo-user] Re: Can't upgrade portage or update/install ebuilds

[Mitch D.]

On Tue, Jun 13, 2023 at 10:38 AM Grant Edwards 
wrote:

> On 2023-06-12, Wol  wrote:
> > On 09/06/2023 21:16, Grant Edwards wrote:
> >> On 2023-06-09, Daniel Pielmeier  wrote:
> >>
> >>> If it is only about gemato then temporary disable the rsync-verify flag
> >>> which pulls it in.
> >>>
> >>> # USE="-rsync-verify" emerge sys-apps/portage
> >>
> >> The problem I ran into is that you never know how many issues there
> >> are standing in the way of upgrading. The one time I decided to muscle
> >> my way through updating an "obsolete" Gentoo install, [...]
> >>
> >> You do learn alot about how portage/emerge works...
> >>
> > Learning that is a good idea maybe :-)
> >
> > But last time I had a well-out-of-date system, it was a long and
> > messy process ...
> >
> > What I did was, every time portage said "giving up" or "conflict found"
> > or whatever, I just took a note of as many of the packages I could
> > remember that portage said it could emerge, and then manually updated
> > them "emerge --update --one-shot".
> >
> > And any conflicts, if I dared, I simply deleted then "emerge -C
> --one-shot".
>
> IIRC, at one point Python was one of those problems, and I stupidly
> removed Python before realizing what that meant...
>
> Hilarity ensued.
>
> Removing/skipping as many of the non-essential "big" packages and
> their dependancies and getting the base system updated is indeed the
> best way to go.


I second this approach. When rescuing a Gentoo system, my first step would
be to deselect any and every non-critical package from @world, then try to
get @system updated through any means necessary. In the past, I've removed
packages instead of deselecting them, but I've had cases where depclean
refused to do anything because there were already dependency problems, and
sometimes it's hard to know what's safe to unmerge with "-C".

[gentoo-user] Re: Can't upgrade portage or update/install ebuilds

[Grant Edwards]

On 2023-06-12, Wol  wrote:
> On 09/06/2023 21:16, Grant Edwards wrote:
>> On 2023-06-09, Daniel Pielmeier  wrote:
>> 
>>> If it is only about gemato then temporary disable the rsync-verify flag
>>> which pulls it in.
>>>
>>> # USE="-rsync-verify" emerge sys-apps/portage
>> 
>> The problem I ran into is that you never know how many issues there
>> are standing in the way of upgrading. The one time I decided to muscle
>> my way through updating an "obsolete" Gentoo install, [...]
>> 
>> You do learn alot about how portage/emerge works...
>> 
> Learning that is a good idea maybe :-)
>
> But last time I had a well-out-of-date system, it was a long and
> messy process ...
>
> What I did was, every time portage said "giving up" or "conflict found" 
> or whatever, I just took a note of as many of the packages I could 
> remember that portage said it could emerge, and then manually updated 
> them "emerge --update --one-shot".
>
> And any conflicts, if I dared, I simply deleted then "emerge -C --one-shot".

IIRC, at one point Python was one of those problems, and I stupidly
removed Python before realizing what that meant...

Hilarity ensued.

Removing/skipping as many of the non-essential "big" packages and
their dependancies and getting the base system updated is indeed the
best way to go.

[gentoo-user] Re: trying to get sd card reader to work

[Nuno Silva]

On 2023-06-13, Wols Lists wrote:

> On 13/06/2023 03:01, John Blinka wrote:
>> Good to know it all works, but if you're sticking a new card in an old
>> reader, they may not be compatible.
>>
>>
>> Don’t know what constitutes new/old, but these are <1 year old
>> cards. Satisfied with empiric evidence that it all works. Have
>> written mp3 files to this card and played them via Arduino/attached
>> mp3 board. Sufficient for my purposes. Amazed that it all works!
>> (Pushing beyond my comfort level with card reader/Arduino/mp3
>> board/wiring all this stuff together.)
>
> Basically, just a little bit of history ...
>
> When these cards came out, they were true SD. With a max capacity of
> 4GB (4GB cards are actually rare as hens teeth ...)
>
> As 2GB became cheap and common, the technology transitioned to SDHC,
> so your 4GB card is almost certainly SDHC, and will not work in a true
> SD reader (like my 2009-era satnav).
>
> That had a limit of - iirc - 32GB, and as that became common the
> technology transitioned to SDXC. This is where my knowledge becomes
> rather hazy...
>
> But anyways, everywhere the card is newer than the reader, you have
> the possibility of problems. It rarely happens, but I've been bitten
> twice trying to upgrade the chips in cameras ...
>
> Cheers,
> Wol


Curiously, I've just recently bought a bigger capacity card (32GB I
think?), µSDHC, with an "SD adapter", and I learned that the
(multi-slot) USB dongle I've been using does not support µSDHC (only
µSD, apparently?)... but does support SDHC!

-- 
Nuno Silva

Re: [gentoo-user] some help with wayland

[Michael]

On Tuesday, 13 June 2023 01:01:43 BST Wol wrote:
> On 10/06/2023 09:44, Michael wrote:
> > Without sddm, you can run the startplasma-wayland stanza from a console,
> > do
> > your thing, logout and the console would have captured various logs - just
> > as startx does.
> 
> Does that actually work now? Last I tried I ended up looking for the
> docu, and found that it said that was a bad idea and not guaranteed to
> work. Certainly on my system, it just hung with, iirc, no logs whatsoever.
> 
> Once I enabled sddm.service, it worked fine ...
> 
> Cheers,
> Wol

It works here with Radeon graphics and Intel graphics (no Nvidia to try):

dbus-run-session startplasma-wayland

What works less satisfactorily or not at all on this laptop, is Ctrl+Alt+F2 or 
some other console and then returning to F1.  The wayland desktop rendering is 
corrupted with horizontal tearing and flickering on the monitor.  I can't see 
any menus to restart/logout.  Sadly Ctrl+Alt+Backspace has no effect on it.  
If/when it locks completely the magic SysRq key combo does not work either.

Due to muscle memory, dropping in a console is a regular occurrence with me, 
so I only launch wayland with sddm.  Sessions started with sddm can be 
recovered, if I first return to F7 where sddm is running, then to F8 where the 
wayland session is.

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

Re: [gentoo-user] trying to get sd card reader to work

[Wols Lists]

On 13/06/2023 03:01, John Blinka wrote:

Good to know it all works, but if you're sticking a new card in an old
reader, they may not be compatible.


Don’t know what constitutes new/old, but these are <1 year old cards. 
Satisfied with empiric evidence that it all works. Have written mp3 
files to this card and played them via Arduino/attached mp3 board. 
Sufficient for my purposes. Amazed that it all works! (Pushing beyond my 
comfort level with card reader/Arduino/mp3 board/wiring all this stuff 
together.)


Basically, just a little bit of history ...

When these cards came out, they were true SD. With a max capacity of 4GB 
(4GB cards are actually rare as hens teeth ...)


As 2GB became cheap and common, the technology transitioned to SDHC, so 
your 4GB card is almost certainly SDHC, and will not work in a true SD 
reader (like my 2009-era satnav).


That had a limit of - iirc - 32GB, and as that became common the 
technology transitioned to SDXC. This is where my knowledge becomes 
rather hazy...


But anyways, everywhere the card is newer than the reader, you have the 
possibility of problems. It rarely happens, but I've been bitten twice 
trying to upgrade the chips in cameras ...


Cheers,
Wol