Re: [gentoo-user] AMDGPU KMS Problems

2017-07-13 Thread jdm
On Thu, 13 Jul 2017 23:29:39 +0100
jdm  wrote:

> On Thu, 13 Jul 2017 03:12:49 -0400
> P Levine  wrote:
> 
> > On Wed, Jul 12, 2017 at 5:34 PM, jdm  wrote:  
> > > Any thouhgts much appreciated.
> > 
> > I tried helping to diagnose a similar problem for a user on Reddit
> > recently, blackscreen/freeze with AMDGPU on boot. After trying
> > everything else he switched the PCI slot the card was in and it
> > booted up fine.  He then switched the card back to the original PCI
> > slot and it still booted up fine.  It seemed to be some weird kind
> > of hardware/bios hiccup.  If you've tried everything else, it
> > wouldn't hurt to fumble around with the graphics card just to see
> > if it makes a difference.
> >   
> 
> Well, well, well.
> 
> Bizarre. took out my old radeon r9 280 card and put the RX480 amdgpu 
> back in and rebooted to a kernel which I had configured for amdgpu 
> and booted with no issues, not needing modeset and xorg working fine
> and dandy.
> 
> Never seen anything like this before. Bring back the days when you had
> a primary and secondary hard drives on a serial bus. Far easier when
> you have to configure your own IRQs.
> 
> Thanks for the advice.
> 
> John. 
> 
> 
To prove that reseating the graphics has sorted the issue I have tried
a few other distros and had no problems. 

John



Re: [gentoo-user] Re: Don't miss the 1 500 000 000 Unix second!

2017-07-13 Thread wabe
wabe  wrote:

> Nikos Chantziaras  wrote:
> 
> > On 13/07/17 21:15, Kent Fredric wrote:  
> > > On Thu, 13 Jul 2017 16:01:42 +0300
> > > Andrew Savchenko  wrote:
> > > >> I'd like to remind you that
> > >>$ date -d @15
> > >> is drawing close!
> > >>
> > >> Don't miss the moment :)
> > > >   watch -n 1 'echo $(( 15 -  $( date +"%s") ))'
> > > > Enjoy.
> > 
> > watch -n 1 'date -d@$((15 - $(date +"%s"))) -u +%H:%M:%S'
> > 
> > Enjoy even more :-)
> >   
> 
> What a big coincidence. I read this threat about half a minute before 

Sorry. Of course I meant "thread" and not "threat". ;-)

--
Regards
wabe



Re: [gentoo-user] Re: Don't miss the 1 500 000 000 Unix second!

2017-07-13 Thread wabe
Nikos Chantziaras  wrote:

> On 13/07/17 21:15, Kent Fredric wrote:
> > On Thu, 13 Jul 2017 16:01:42 +0300
> > Andrew Savchenko  wrote:  
> > >> I'd like to remind you that  
> >>$ date -d @15
> >> is drawing close!
> >>
> >> Don't miss the moment :)
> > >   watch -n 1 'echo $(( 15 -  $( date +"%s") ))'
> > > Enjoy.  
> 
> watch -n 1 'date -d@$((15 - $(date +"%s"))) -u +%H:%M:%S'
> 
> Enjoy even more :-)
> 

What a big coincidence. I read this threat about half a minute before 
03:40 UTC and quickly entered the command you posted into a terminal 
window, only 6 seconds before the "magic moment" occurs. :-)

--
Regards
wabe



Re: [gentoo-user] Don't miss the 1 500 000 000 Unix second!

2017-07-13 Thread R0b0t1
On Thu, Jul 13, 2017 at 8:01 AM, Andrew Savchenko  wrote:
> Hi all!
>
> I'd like to remind you that
>   $ date -d @15
> is drawing close!
>
> Don't miss the moment :)

Here it is!



Re: [gentoo-user] Re: Wayland - too early to try?

2017-07-13 Thread Mick
On Thursday 13 Jul 2017 21:58:10 Mart Raudsepp wrote:
> Ühel kenal päeval, K, 12.07.2017 kell 09:33, kirjutas Mick:
> > On Tuesday 11 Jul 2017 23:14:16 Mick wrote:
> > > On Wednesday 12 Jul 2017 01:10:00 Mart Raudsepp wrote:
> > > > > I copied /usr/share/xsessions/enlightenment.desktop to
> > > > > /usr/share/wayland-
> > > > > sessions/ and tried to select it in LightDM.  Unfortunately
> > > > > LightDM
> > > > > returns me
> > > > > back to the login page.  I don't know if this is a result of
> > > > > LightDM
> > > > > not being
> > > > > compatible with Wayland and friends, or if I need to install
> > > > > some
> > > > > other
> > > > > package in addition to what has been emerged already.
> > > > 
> > > > The desktop manager needs to be using wayland to be able to
> > > > launch
> > > > wayland desktop sessions. LightDM is not such a desktop manager
> > > > to my
> > > > knowledge and you won't be able to launch any wayland sessions
> > > > with it.
> > > > 
> > > > Mart
> > > 
> > > Thanks Mart, what other DM or means do I have to launch
> > > enlightenment with
> > > wayland?  I'm guessing the time honoured startx from a console
> > > won't cut it.
> > 
> > Oh dear!  I noticed this:
> > 
> > https://git.enlightenment.org/core/enlightenment.git/tree/README.wayl
> > and
> > 
> > which states that efl *must* be built with --enable-systemd
> > option.  I am 
> > running openrc ... so I don't know if the above just requires this as
> > a build 
> > time dependency, or is needs systemd to be running.  Anyway, from
> > that write 
> > up and the Known Issues at the bottom it seems Wayland is not ready
> > for prime 
> > time yet.
> 
> That README.wayland looks rather outdated. There are issues mentioned
> in the end that have been fixed since mid-2016 with xorg-server
> releases out since then with the fixes (Xwayland comes from xorg-
> server[wayland]).

Yes, this is encouraging and things are moving fast in e_git code.


> Regarding systemd, wayland sessions usually require logind seat
> interfaces. If you want to stick with OpenRC, you might need to look
> into elogind then, which is now in Gentoo and integrated for some
> Plasma wayland usages, but EFL stuff might need some ebuild changes too
> to use that instead of systemd provided logind.
> 
> 
> Mart

It'll take a dev interested in getting EFL to get this to run on openrc or 
with elogind.  I'll keep an eye out for developments in this area.  The 
direction of travel appears to be towards Wayland, but the ETA is of course 
unknown.

Interestingly, selecting Plasma to run with Wayland won't launch either.  It 
drops me back into the LoginDM screen.
-- 
Regards,
Mick

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


Re: [gentoo-user] AMDGPU KMS Problems

2017-07-13 Thread jdm
On Thu, 13 Jul 2017 03:12:49 -0400
P Levine  wrote:

> On Wed, Jul 12, 2017 at 5:34 PM, jdm  wrote:
> > Any thouhgts much appreciated.  
> 
> I tried helping to diagnose a similar problem for a user on Reddit
> recently, blackscreen/freeze with AMDGPU on boot. After trying
> everything else he switched the PCI slot the card was in and it booted
> up fine.  He then switched the card back to the original PCI slot and
> it still booted up fine.  It seemed to be some weird kind of
> hardware/bios hiccup.  If you've tried everything else, it wouldn't
> hurt to fumble around with the graphics card just to see if it makes a
> difference.
> 

Well, well, well.

Bizarre. took out my old radeon r9 280 card and put the RX480 amdgpu 
back in and rebooted to a kernel which I had configured for amdgpu 
and booted with no issues, not needing modeset and xorg working fine
and dandy.

Never seen anything like this before. Bring back the days when you had
a primary and secondary hard drives on a serial bus. Far easier when
you have to configure your own IRQs.

Thanks for the advice.

John. 




[gentoo-user] Re: Don't miss the 1 500 000 000 Unix second!

2017-07-13 Thread Nikos Chantziaras

On 13/07/17 21:15, Kent Fredric wrote:

On Thu, 13 Jul 2017 16:01:42 +0300
Andrew Savchenko  wrote:


I'd like to remind you that
   $ date -d @15
is drawing close!

Don't miss the moment :)


  watch -n 1 'echo $(( 15 -  $( date +"%s") ))'

Enjoy.


watch -n 1 'date -d@$((15 - $(date +"%s"))) -u +%H:%M:%S'

Enjoy even more :-)




Re: [gentoo-user] GPU closed source libraries

2017-07-13 Thread Mart Raudsepp
Ühel kenal päeval, N, 13.07.2017 kell 16:41, kirjutas Francisco Ares:
> Hi, All.
> 
> I'm trying to get Gentoo and xorg in an Odroid XU4 (hardkernel.com).
> 
> Most things are done, but there are a few glitches. I'm using the
> open source xf86-video-armsoc, which does not provide GPU
> acceleration.
> 
> So, for instance, dev-qt/qtgui with USE="gles2" (just an example), it
> will pull media-libs/mesa for 3d acceleration, although the
> proprietary library (Mali drivers) would do so.
> 
> How would I avoid emerging media-libs/mesa in this example?

It needs the standardish khronos GL headers from somewhere, which
proprietary drivers don't ship or mess with them too much for standard
stuff. Typically mesa is a good place to get them. That doesn't mean
it'd use it at runtime when your system is eselected to mali instead.
Have you tried not worry about the dep and just get things compiled
against mesa headers and see if it actually uses mali drivers then
still?



[gentoo-user] GPU closed source libraries

2017-07-13 Thread Francisco Ares
Hi, All.

I'm trying to get Gentoo and xorg in an Odroid XU4 (hardkernel.com).

Most things are done, but there are a few glitches. I'm using the open
source xf86-video-armsoc, which does not provide GPU acceleration.

So, for instance, dev-qt/qtgui with USE="gles2" (just an example), it will
pull media-libs/mesa for 3d acceleration, although the proprietary library
(Mali drivers) would do so.

How would I avoid emerging media-libs/mesa in this example?

Thank you,
Francisco


Re: [gentoo-user] Re: Wayland - too early to try?

2017-07-13 Thread Mart Raudsepp
Ühel kenal päeval, K, 12.07.2017 kell 09:33, kirjutas Mick:
> On Tuesday 11 Jul 2017 23:14:16 Mick wrote:
> > On Wednesday 12 Jul 2017 01:10:00 Mart Raudsepp wrote:
> > > > I copied /usr/share/xsessions/enlightenment.desktop to
> > > > /usr/share/wayland-
> > > > sessions/ and tried to select it in LightDM.  Unfortunately
> > > > LightDM
> > > > returns me
> > > > back to the login page.  I don't know if this is a result of
> > > > LightDM
> > > > not being
> > > > compatible with Wayland and friends, or if I need to install
> > > > some
> > > > other
> > > > package in addition to what has been emerged already.
> > > 
> > > The desktop manager needs to be using wayland to be able to
> > > launch
> > > wayland desktop sessions. LightDM is not such a desktop manager
> > > to my
> > > knowledge and you won't be able to launch any wayland sessions
> > > with it.
> > > 
> > > Mart
> > 
> > Thanks Mart, what other DM or means do I have to launch
> > enlightenment with
> > wayland?  I'm guessing the time honoured startx from a console
> > won't cut it.
> 
> Oh dear!  I noticed this:
> 
> https://git.enlightenment.org/core/enlightenment.git/tree/README.wayl
> and
> 
> which states that efl *must* be built with --enable-systemd
> option.  I am 
> running openrc ... so I don't know if the above just requires this as
> a build 
> time dependency, or is needs systemd to be running.  Anyway, from
> that write 
> up and the Known Issues at the bottom it seems Wayland is not ready
> for prime 
> time yet.

That README.wayland looks rather outdated. There are issues mentioned
in the end that have been fixed since mid-2016 with xorg-server
releases out since then with the fixes (Xwayland comes from xorg-
server[wayland]).

Regarding systemd, wayland sessions usually require logind seat
interfaces. If you want to stick with OpenRC, you might need to look
into elogind then, which is now in Gentoo and integrated for some
Plasma wayland usages, but EFL stuff might need some ebuild changes too
to use that instead of systemd provided logind.


Mart



Re: [gentoo-user] Re: Wayland - too early to try?

2017-07-13 Thread Mart Raudsepp
Ühel kenal päeval, T, 11.07.2017 kell 18:16, kirjutas R0b0t1:
> In any case if you are asking the question that OP did, I would
> suggest Wayland might not be for you. You may not receive any benefit
> from using it unless, for some reason, the differing underlying
> implementation fixes a bug - but I see this as being a bit of a
> stretch, because if you don't go out of your way to run Wayland only
> programs, you will still be running X11 on top of Wayland.

There are no grabs in Wayland, and thus the bug he had, related to
tooltips or context menus, might very well be related to the switch, as
tooltips and context menus are done completely differently.

> Most programs written for Wayland still seem to be at early
> experimental stages, and are things like tiling window managers.

Most programs don't need to be written for Wayland, they just use a
toolkit while avoiding to make their own libX11/XCB/etc calls.
This means most GTK3 programs and Qt programs run natively on wayland
out of the box without doing anything.
Running things needing X11, and thus going through Xwayland, can still
be smoother as well.


Mart



Re: [gentoo-user] Re: Wayland - too early to try?

2017-07-13 Thread Mart Raudsepp
Ühel kenal päeval, T, 11.07.2017 kell 23:14, kirjutas Mick:
> On Wednesday 12 Jul 2017 01:10:00 Mart Raudsepp wrote:
> > > I copied /usr/share/xsessions/enlightenment.desktop to
> > > /usr/share/wayland-
> > > sessions/ and tried to select it in LightDM.  Unfortunately
> > > LightDM
> > > returns me 
> > > back to the login page.  I don't know if this is a result of
> > > LightDM
> > > not being 
> > > compatible with Wayland and friends, or if I need to install some
> > > other 
> > > package in addition to what has been emerged already.  
> > 
> > The desktop manager needs to be using wayland to be able to launch
> > wayland desktop sessions. LightDM is not such a desktop manager to
> > my
> > knowledge and you won't be able to launch any wayland sessions with
> > it.
> > 
> > Mart
> 
> Thanks Mart, what other DM or means do I have to launch enlightenment
> with 
> wayland?  I'm guessing the time honoured startx from a console won't
> cut it.

Someone else was trying Sway with LightDM and got it to work. LightDM
wiki page also says it supports Wayland. But maybe our packaging
doesn't, I need to check back with him. Did you check with LightDM as-
is? It ought to show stuff from /usr/share/wayland-sessions/ as choices
(maybe enlightenment doesn't have an entry there?).

Command line launching should be possible, but I don't know the details
to get everything going correctly.


Mart



Re: [gentoo-user] Don't miss the 1 500 000 000 Unix second!

2017-07-13 Thread Kent Fredric
On Thu, 13 Jul 2017 16:01:42 +0300
Andrew Savchenko  wrote:

> Hi all!
> 
> I'd like to remind you that
>   $ date -d @15
> is drawing close!
> 
> Don't miss the moment :)
> 
> Best regards,
> Andrew Savchenko

 watch -n 1 'echo $(( 15 -  $( date +"%s") ))'

Enjoy.


pgp2ET0HBEcp8.pgp
Description: OpenPGP digital signature


Re: [gentoo-user] Don't miss the 1 500 000 000 Unix second!

2017-07-13 Thread Peter Humphrey
On Thursday 13 Jul 2017 16:01:42 Andrew Savchenko wrote:
> Hi all!
> 
> I'd like to remind you that
>   $ date -d @15
> is drawing close!
> 
> Don't miss the moment :)

With any luck, most of us in the UK will be asleep, as it's at 03:40.  :)

-- 
Regards
Peter




Re: [gentoo-user] Don't miss the 1 500 000 000 Unix second!

2017-07-13 Thread R0b0t1
On Thu, Jul 13, 2017 at 8:01 AM, Andrew Savchenko  wrote:
> Hi all!
>
> I'd like to remind you that
>   $ date -d @15
> is drawing close!
>
> Don't miss the moment :)
>

I'll make a wish, like I do at 11:11!



[gentoo-user] Don't miss the 1 500 000 000 Unix second!

2017-07-13 Thread Andrew Savchenko
Hi all!

I'd like to remind you that
  $ date -d @15
is drawing close!

Don't miss the moment :)

Best regards,
Andrew Savchenko


pgpRdAwlWh1Fd.pgp
Description: PGP signature


Re: [gentoo-user] AMDGPU KMS Problems

2017-07-13 Thread Peter Humphrey
On Wednesday 12 Jul 2017 22:34:09 jdm wrote:

> A few months ago I bought a AMD RX 480 GPU and followed the Gentoo
> amdgpu guide and everything ran just fine with excellent graphics
> performance.

I have a Radeon R9 380X (tonga), which may perhaps be similar to your card, 
though with an i7 motherboard. I had to include VIDEO_CARDS="amdgpu 
radeonsi" in make.conf.

--->8

> Any thouhgts much appreciated.

My motherboard can only accept this graphics card in one specific slot 
(actually, a pair of them).

That's all I can come up with. Good luck!

-- 
Regards
Peter




Re: [gentoo-user] AMDGPU KMS Problems

2017-07-13 Thread P Levine
On Wed, Jul 12, 2017 at 5:34 PM, jdm  wrote:
> Any thouhgts much appreciated.

I tried helping to diagnose a similar problem for a user on Reddit
recently, blackscreen/freeze with AMDGPU on boot. After trying
everything else he switched the PCI slot the card was in and it booted
up fine.  He then switched the card back to the original PCI slot and
it still booted up fine.  It seemed to be some weird kind of
hardware/bios hiccup.  If you've tried everything else, it wouldn't
hurt to fumble around with the graphics card just to see if it makes a
difference.