Re: [gentoo-user] AMDGPU KMS Problems

[Rich Freeman]

On Wed, Jul 12, 2017 at 5:34 PM, jdm  wrote:
>
> I checked the config of the kernel (inc firmware) and could not find
> an issue. I then tried arch/fedora/ubuntu and all froze at boot and then
> worked with nomodeset.

Ok, this is pointing to a likely hardware issue IMO - I gotta imagine
that one of those distros would have noticed the RX 480 not working -
it is hardly an obscure card.

>
> 1) Is this likely to be a kernel issue (amdgpu drm)?

Probably not, imo.  However, I would try booting using a mainline
kernel (4.12 right now) just to confirm.  Any distro would be fine -
but try it on the bleeding edge kernel on one of them.

> 2) Could this be a firmware issue (amd)?

Maybe, but probably not.  You might want to check if your motherboard
has any published issues.  I'd think that amd would be pushing their
motherboard partners to support their cards.

> 3) Could this be a motherboard/processor issue?
> 4) Can you think of any ways round this so I can use the RX 480 gpu

I suspect it is some kind of motherboard-GPU issue.  Maybe it is
firmware - I'd search for that.  Some kind of power issue could also
be the problem.  Maybe your board has issues supplying enough power (I
understand the RX 480 draws quite a bit through the PCI slot), or
maybe the new motherboard+CPU+RX480 combo is stressing your power
supply (either overall, or on one of the rails).  Granted, if your old
card was also a radeon it probably was also a power hog.

Those are just the things I'd probably poke at - somebody else might
have other ideas.  Hopefully you'll get it working - I doubt I'll need
an RX 480 but I probably will move to Ryzen sometime soon now that it
is starting to mature on linux (though I wouldn't mind seeing it
supported in a longterm kernel first, especially since I'm using btrfs
and zfs on this box).

-- 
Rich

Re: [gentoo-user] Re: grub error I've never seen in many installs

[Hinnerk van Bruinehsen]

On Wed, Jul 12, 2017 at 05:57:58PM -0400, Harry Putnam wrote:
> Arve Barsnes  writes:
> 
> > On 10 July 2017 at 22:06, Harry Putnam  wrote:
> >
> >>  grub-install /dev/sda Installing for i386-pc platform.
> >> grub-install: error: cannot find a GRUB drive for /dev/sda1.  Check
> >> your device.map.
> >>
> >> Where might I find `device.map'... it isn't part of grub2.  At least
> >> grep doesn't find it with `qlist grub'
> >>
> >
> > As far as I understand it, grub2 will dynamically create the device.map
> > when it needs it, so it doesn't actually exist as a file. On my grub legacy
> > system it is installed as /boot/grub/device.map, with the only contents
> > being "(hd0)   /dev/sda".
> >
> > How you would feed grub this information *before* it is installed I'm not
> > sure, but maybe look into the USE=device-mapper flag, maybe it installs the
> > grub-mkdevicemap executable.
> 
> Yeah, I tried that before posting.. setting USE=device-mapper then
> reinstalled grub2... same result as without the flag.  Same error
> message.
> 
> I've always .. on many installs (over time) and mostly into a vbox vm,
> created a disk, then when booting the install media I carve it up with
> fdisk.
> /dev/sda1=boot
> /dev/sda2=swap
> /dev/sda3=home
> /dev/sda4=/
> 
> Has something changed regarding using that kind of technique?
> 
> I can't figure out why grub would be looking for a GRUB drive on
> /dev/sda1 as the error says:
> 
>   grub-install: error: cannot find a GRUB drive for /dev/sda1


Did you mount /boot from inside the chroot environment? IIRC I got a
similar failure when mounting /boot from outside the chroot...

[gentoo-user] Re: grub error I've never seen in many installs

[Harry Putnam]

Arve Barsnes  writes:

> On 10 July 2017 at 22:06, Harry Putnam  wrote:
>
>>  grub-install /dev/sda Installing for i386-pc platform.
>> grub-install: error: cannot find a GRUB drive for /dev/sda1.  Check
>> your device.map.
>>
>> Where might I find `device.map'... it isn't part of grub2.  At least
>> grep doesn't find it with `qlist grub'
>>
>
> As far as I understand it, grub2 will dynamically create the device.map
> when it needs it, so it doesn't actually exist as a file. On my grub legacy
> system it is installed as /boot/grub/device.map, with the only contents
> being "(hd0)   /dev/sda".
>
> How you would feed grub this information *before* it is installed I'm not
> sure, but maybe look into the USE=device-mapper flag, maybe it installs the
> grub-mkdevicemap executable.

Yeah, I tried that before posting.. setting USE=device-mapper then
reinstalled grub2... same result as without the flag.  Same error
message.

I've always .. on many installs (over time) and mostly into a vbox vm,
created a disk, then when booting the install media I carve it up with
fdisk.
/dev/sda1=boot
/dev/sda2=swap
/dev/sda3=home
/dev/sda4=/

Has something changed regarding using that kind of technique?

I can't figure out why grub would be looking for a GRUB drive on
/dev/sda1 as the error says:

  grub-install: error: cannot find a GRUB drive for /dev/sda1

[gentoo-user] AMDGPU KMS Problems

[jdm]

Hi All,

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.

At the weekend I upgraded my PC from a AMD 970 chipset to a x370
chipset (fx8300 to ryzen 1700x).

I re-installed Gentoo but the first time I started the boot iso the
screen froze, so I tried the nomodeset option and booted ok and
installed as per usual. 

After rebooting to new install the screen froze again and the only way
to get it to boot was using kernel option nomodeset. This then gave me
another problem as it could not startx (no screens found).

I checked the config of the kernel (inc firmware) and could not find
an issue. I then tried arch/fedora/ubuntu and all froze at boot and then
worked with nomodeset.

I have now gone back to using an old graphics card which uses radeon
and have no problems starting xorg-server.

1) Is this likeley to be a kernel issue (amdgpu drm)?
2) Could this be a firmware issue (amd)?
3) Could this be a motherboard/processor issue?
4) Can you think of any ways round this so I can use the RX 480 gpu

Any thouhgts much appreciated.

John

[gentoo-user] emerge problem after sync today

[Danny YUE]

Hi all,

I encountered a problem after `emerge --sync` today.

When I ran `emerge -auDNU @world`, it told me something strange
following the list of upgradable software:

Would you like to merge these packages? [Yes/No] 
>>> Verifying ebuild manifests
!!! A file is not listed in the Manifest: 
'/usr/portage/app-arch/unrar/unrar-5.4.5.ebuild'
!!! A file is not listed in the Manifest: 
'/usr/portage/sys-apps/less/less-494.ebuild'
!!! A file is not listed in the Manifest: 
'/usr/portage/dev-python/sip/sip-4..ebuild'
!!! A file is not listed in the Manifest: 
'/usr/portage/dev-python/pillow/pillow-4.2.1.ebuild'
!!! A file is not listed in the Manifest: 
'/usr/portage/dev-python/sphinx/sphinx-1.3.1-r2.ebuild'
!!! A file is not listed in the Manifest: 
'/usr/portage/www-servers/nginx/nginx-1.13.0.ebuild'
!!! A file is not listed in the Manifest: 
'/usr/portage/app-text/podofo/podofo-0.9.6_pre20170508-r1.ebuild'
!!! A file is not listed in the Manifest: 
'/usr/portage/dev-lang/vala/vala-0.32.1.ebuild'
!!! A file is not listed in the Manifest: 
'/usr/portage/sys-libs/db/db-4.8.30-r2.ebuild'
!!! A file is not listed in the Manifest: 
'/usr/portage/sys-libs/db/db-4.8.30-r2.ebuild'
!!! A file is not listed in the Manifest: 
'/usr/portage/net-dns/bind-tools/bind-tools-9.11.0_p3.ebuild'
!!! A file is not listed in the Manifest: 
'/usr/portage/dev-lang/php/php-5.6.30.ebuild'
!!! A file is not listed in the Manifest: 
'/usr/portage/app-admin/apache-tools/apache-tools-2.4.25.ebuild'
!!! A file is not listed in the Manifest: 
'/usr/portage/app-text/dos2unix/dos2unix-7.3.5.ebuild'
!!! A file is not listed in the Manifest: 
'/usr/portage/media-libs/harfbuzz/harfbuzz-1.4.6-r1.ebuild'
!!! A file is not listed in the Manifest: 
'/usr/portage/dev-cpp/gtkmm/gtkmm-2.24.5.ebuild'
!!! A file is not listed in the Manifest: 
'/usr/portage/app-text/calibre/calibre-3.1.1-r2.ebuild'
!!! A file is not listed in the Manifest: 
'/usr/portage/gnome-base/gnome-keyring/gnome-keyring-3.20.1.ebuild'

Then I checked unrar ebuild directory. I found that Manifest file is
empty.

The problem did not disappear after I purged /usr/portage and redo
`emerge --sync`. So I suspect this is an error in the upstream
repository.


This is really strange. Any idea?


Danny

[gentoo-user] Re: march to cross-compile ASUS laptop

[Andrés Becerra Sandoval]

​Thank you R0b0t1, Peter and Hinnerk!


-- 
  Andrés Becerra Sandoval

Re: [gentoo-user] march to cross-compile ASUS laptop

[Hinnerk van Bruinehsen]

On Tue, Jul 11, 2017 at 06:06:26PM -0500, Andrés Becerra Sandoval wrote:
>Hello,
> 
>I want to use a build host to create packages for a L402N Asus laptop.
> 
>% grep -m1 -A3 "vendor_id" /proc/cpuinfo
>vendor_id   : GenuineIntel
>cpu family  : 6
>model   : 92
>model name  : Intel(R) Celeron(R) CPU N3350 @ 1.10GHz
> 
>intel has this specs:
>
> [1]http://ark.intel.com/products/95598/Intel-Celeron-Processor-N3350-2M-Cache-up-to-2_4-GHz
> 
>and, in the following website:
> 
> [2]https://en.wikichip.org/wiki/intel/celeron/n3350
> 
>​It says that the microarchitecture is apollo-lake.
> 
>What would be the proper marc​h configuration for this box?
> 

Hi,

if you have Gentoo already installed on the box, make sure that you
configured the same compiler version as on the build host (gcc-config)
and then run:
gcc -### -march=native -E /usr/include/stdlib.h 2>&1 | grep
"/usr/libexec/gcc/.*cc1"

Everything after "-march=..." should be what your gcc version would use
when using march=native on the laptop.

WKR Hinnerk

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

[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.wayland

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.
-- 
Regards,
Mick

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