RE: [gentoo-user] (Not Solved for me) anyone tried amdgpu (kernel module)
> From: michaelkintz...@gmail.com > To: gentoo-user@lists.gentoo.org > Subject: Re: [gentoo-user] (Not Solved for me) anyone tried amdgpu (kernel > module) > Date: Tue, 22 Dec 2015 23:02:12 + > > On Tuesday 22 Dec 2015 21:30:48 Alexander Kapshuk wrote: > > On Tue, Dec 22, 2015 at 9:39 PM, Mick wrote: > > > On Sunday 20 Dec 2015 20:29:28 Alexander Kapshuk wrote: > > > > On Sun, Dec 20, 2015 at 9:04 PM, Mick wrote: > > > > > This is not working for me on a Kaveri system. > > > > > > > > > > The wiki page suggests these firmware blobs: > > > > > > > > > > radeon/kaveri_ce.bin radeon/kaveri_me.bin radeon/kaveri_mec2.bin > > > > > radeon/kaveri_mec.bin radeon/kaveri_pfp.bin radeon/kaveri_rlc.bin > > > > > radeon/kaveri_sdma1.bin radeon/kaveri_sdma.bin radeon/kaveri_uvd.bin > > > > > radeon/kaveri_vce.bin > > > > > > > > > > Unfortunately, radeon/kaveri_sdma1.bin does not seen to be available > > > > > > when > > > > > > > > I use sys-kernel/linux-firmware: > > > > > > > > > > find /lib/firmware/radeon/ -iname KAVERI*sdma* > > > > > /lib/firmware/radeon/kaveri_sdma.bin > > > > > /lib/firmware/radeon/KAVERI_sdma.bin > > > > > > > > > > > > > > > I installed sys-firmware/amdgpu-ucode, but KAVERI is not found there > > > > > either: > > > > > > > > > > find /lib/firmware/amdgpu/ -iname *sdma* > > > > > /lib/firmware/amdgpu/carrizo_sdma.bin > > > > > /lib/firmware/amdgpu/carrizo_sdma1.bin > > > > > /lib/firmware/amdgpu/fiji_sdma.bin > > > > > /lib/firmware/amdgpu/fiji_sdma1.bin > > > > > /lib/firmware/amdgpu/tonga_sdma.bin > > > > > /lib/firmware/amdgpu/tonga_sdma1.bin > > > > > /lib/firmware/amdgpu/topaz_sdma.bin > > > > > /lib/firmware/amdgpu/topaz_sdma1.bin > > > > > > > > > > > > > > > Building the recommended blobs fails like so: > > > > > > > > > > # make && make modules_install && make firmware_install > > > > > > > > > > CHK include/config/kernel.release > > > > > CHK include/generated/uapi/linux/version.h > > > > > CHK include/generated/utsrelease.h > > > > > CHK include/generated/bounds.h > > > > > CHK include/generated/asm-offsets.h > > > > > CALLscripts/checksyscalls.sh > > > > > CHK include/generated/compile.h > > > > > > > > > > kernel/Makefile:135: *** No X.509 certificates found *** > > > > > make[1]: *** No rule to make target > > > > > '/lib/firmware//radeon/kaveri_sdma1.bin', > > > > > needed by 'firmware/radeon/kaveri_sdma1.bin.gen.o'. Stop. > > > > > Makefile:947: recipe for target 'firmware' failed > > > > > make: *** [firmware] Error 2 > > > > > > > > That's interesting. 'kaveri_sdma1.bin' is found in the > > > > 'sys-firmware/amdgpu-ucode' package. See below. > > > > % pwd > > > > radeon_ucode/kaveri > > > > > > I don't seem to have such a directory, or the files therein. Where am I > > > supposed to look? > > > > > > This is what emerge -uaDv sys-firmware/amdgpu-ucode installed on my PC: > > > >>> Installing (1 of 1) sys-firmware/amdgpu-ucode-20150803::gentoo > > > > > > * checking 44 files for package collisions > > > > > > >>> Merging sys-firmware/amdgpu-ucode-20150803 to / > > > > > > --- /lib/ > > > --- /lib/firmware/ > > > --- /lib/firmware/amdgpu/ > > > > > > >>> /lib/firmware/amdgpu/carrizo_ce.bin > > > >>> /lib/firmware/amdgpu/carrizo_me.bin > > > >>> /lib/firmware/amdgpu/carrizo_mec.bin > > > >>> /lib/firmware/amdgpu/carrizo_mec2.bin > > > >>> /lib/firmware/amdgpu/carrizo_pfp.bin > > > >>> /lib/firmware/amdgpu/carrizo_rlc.bin > > > >>> /lib/firmware/amdgpu/carrizo_sdma.bin > > > >>> /lib/firmware/amdgpu/carrizo_sdma1.bin > > > >>> /lib/firmware/amdgpu/carrizo_uvd.bin > > > >>> /lib/firmware/amdgpu/carrizo_vce.bin > > > >>> /lib/firmware/amdgpu/fiji_ce.bin > > > >>> /lib/firmware/amdgpu/fiji_mc.bin > > > >>> /lib/firmware/amdgpu/fiji_me.bin > > > >>> /lib/firmware/amdgpu/fiji_mec.bin > > > >>> /lib/firmware/amdgpu/fiji_mec2.bin > > > >>> /lib/firmware/amdgpu/fiji_pfp.bin > > > >>> /lib/firmware/amdgpu/fiji_rlc.bin > > > >>> /lib/firmware/amdgpu/fiji_sdma.bin > > > >>> /lib/firmware/amdgpu/fiji_sdma1.bin > > > >>> /lib/firmware/amdgpu/fiji_smc.bin > > > >>> /lib/firmware/amdgpu/fiji_uvd.bin > > > >>> /lib/firmware/amdgpu/fiji_vce.bin > > > >>> /lib/firmware/amdgpu/tonga_ce.bin > > > >>> /lib/firmware/amdgpu/tonga_mc.bin > > > >>> /lib/firmware/amdgpu/tonga_me.bin > > > >>> /lib/firmware/amdgpu/tonga_mec.bin > > > >>> /lib/firmware/amdgpu/tonga_mec2.bin > > > >>> /lib/firmware/amdgpu/tonga_pfp.bin > > > >>> /lib/firmware/amdgpu/tonga_rlc.bin > > > >>> /lib/firmware/amdgpu/tonga_sdma.bin > > > >>> /lib/firmware/amdgpu/tonga_sdma1.bin > > > >>> /lib/firmware/amdgpu/tonga_smc.bin > > > >>> /lib/firmware/amdgpu/tonga_uvd.bin > > > >>> /lib/firmware/amdgpu/tonga_vce.bin > > > >>> /lib/firmware/amdgpu/topaz_ce.bin > > > >>> /lib/firmware/amdgpu/topaz_mc.bin > > > >>> /lib/firmware/amdgpu/topaz_me.bin > > > >>> /lib/firmware/amdgpu/topaz_mec.bin > > > >>> /lib/firmware/amdgpu/topaz_mec2.bin > > > >>> /lib/firmware/a
Re: [gentoo-user] Re: Problem with openrc-0.18.4 and ifplugd
On Tuesday 22 Dec 2015 23:32:40 Neil Bothwick wrote: > On Tue, 22 Dec 2015 15:15:57 +, Mick wrote: > > > As far as I understood, you now start ifplugd using the associated > > > net.* init script. Openrc will detect that ifplugd is installed and > > > then wait until a cable is plugged, plus starting an instance > > > listening on the device. > > > > No, this is not how ifplugd worked, for as long as I can remember. I > > never started the interface, or had to start ifplugd by an init.d > > script or manually. > > It may not be how you used it, but that is how ifplugd (or netplug) is > supposed to be used with openrc. It detects whether ifplugd or netplug is > installed when the interface is started up and starts it up to monitor > the interface using the correct options. It's been that way fr a lot of > years and was documented, I think in the comments in the net.* scripts. > > Your approach may have worked in the past but it was unsupported, now it > appears that it doesn't work. Thank you Neil, I just tried netplug and indeed behaves the same as ifplugd - one has to start the interface before netplug will configure a connection. Interestingly, there is a difference between netplug and ifplugd. ifplugd when started by hand, will initialise and configure a NIC. netplug will not. It requires that the interface has been enabled before it does anything. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
