2016-09-09, 21:21
It won't - this is kernel level.
(2016-09-09, 17:46)Milhouse Wrote:(2016-09-09, 08:33)alxtr1bal Wrote:(2016-09-09, 07:51)fritsch Wrote: @alxtr1bal: Include [pkg] patch: xf86-video-amdgpu: Latest commits (6a1ba04) adding Polaris 10 & 11 support (xf86-video-amdgpu) <- such commits are highly relevant for you.
Next time, please gather logfiles. Xorg.0.log and dmesg | pastebinit
With these we can file bugs at bugs.freedesktop.org so that this gets fixed. It won't happen magically.
Ok, last update not working :
Xorg log : http://sprunge.us/VcJK
dmesg : http://sprunge.us/XcBW
here's what i did to install :
First , installed the 7.90.005, with the processor GPU as primary.
Then , put the latest update in /Updates, change the primary video card as the RX 460, and boot.
Update is going ok, reboot, and then the Xorg won't start.
Not sure if this is the right way...
Thanks for the logs. It looks like the "ATI Radeon" driver is being loaded and not the updated "amdgpu" driver. Not sure how easy it is to work around that. Do you have two GPUs in your system, a Kaveri and Polaris? Can you disable the Kaveri?
(2016-09-09, 21:30)alxtr1bal Wrote:(2016-09-09, 17:46)Milhouse Wrote:(2016-09-09, 08:33)alxtr1bal Wrote: Ok, last update not working :
Xorg log : http://sprunge.us/VcJK
dmesg : http://sprunge.us/XcBW
here's what i did to install :
First , installed the 7.90.005, with the processor GPU as primary.
Then , put the latest update in /Updates, change the primary video card as the RX 460, and boot.
Update is going ok, reboot, and then the Xorg won't start.
Not sure if this is the right way...
Thanks for the logs. It looks like the "ATI Radeon" driver is being loaded and not the updated "amdgpu" driver. Not sure how easy it is to work around that. Do you have two GPUs in your system, a Kaveri and Polaris? Can you disable the Kaveri?
For those logs , the Kaveri (AMD A10 GPU) was disabled in the BIOS.
Question is : how can i do fresh install of LE with the new drivers ?
Because what i did is i had an installed LE with Kaveri enabled, updated to #0908, then installed this new RX 460 card and disabled the Kaveri in the bios. Then Xorg does not start... So may be it's because i did not install with this card enabled at the first time ... but this is not possible.
(2016-09-09, 20:07)Superbert Wrote: You are the only one to find this out, what happend between the last version that was ok and the follwing where power on is broken.
(2016-09-09, 21:04)lrusak Wrote: Not sure,
@MilhouseVH you might want to try just updating xf86-video-amdgpu to master and see if that works.
(2016-09-09, 21:30)alxtr1bal Wrote: Question is : how can i do fresh install of LE with the new drivers ?
Because what i did is i had an installed LE with Kaveri enabled, updated to #0908, then installed this new RX 460 card and disabled the Kaveri in the bios. Then Xorg does not start... So may be it's because i did not install with this card enabled at the first time ... but this is not possible.
(2016-09-09, 20:07)Superbert Wrote:(2016-09-08, 14:42)Milhouse Wrote:(2016-09-08, 13:45)Hanxi Wrote: Hi,This is likely an issue between your BIOS and the more recent kernels - see if you have any BIOS updates available. Unfortunately there's little that anyone can do about this kind of issue, as it's likely to be a hardware specific issue (ie. buggy BIOS).
I had updated my Zotac Zbox ci321 nano from libreelec v7.02 to libreelec v7.90.005 and now I have issues to wake up the device via IR-remote. The Power.Off-button and all others works fine, only Power.On works no more. With v7.02 there was no problems.
Then I tested the milhous-rls and found out, that the releases up to 'LibreELEC-Generic.x86_64-8.0-Milhouse-20160421040821-#0420-gfee76be' works with rc-power.on, later releases up to the current version #907 not.
Is there any chance for a fix?
Same problem here, same ZBox. Bios is up to date.
@Milhouse:
You are the only one to find this out, what happend between the last version that was ok and the follwing where power on is broken.
Maybe in this stadium, there are not so many users, who tried the alpha versions, but when its final and there is this this IR wake up issue, there will be many more.
Please help us
(2016-09-09, 22:24)3000 Wrote: is it normal I still have high CPU usage with the latest builds?
(2016-09-09, 22:35)Hanxi Wrote: I mean, it can't be the BIOS.
I make a UEFI dual-boot system. first I install libreelec, then Win10 with rEFind bootmanager. Basically, the whole works, but after libreelec start and shutdown, the rc-button Power.On don't work. On the other hand, when I starts Win10 and shutdown, Power.On works flawlessly, until I boot libreelec again... like a flip-flop.
There must be an error in the current kernel, because with windows there is no issue.
(2016-09-09, 22:42)Milhouse Wrote:(2016-09-09, 22:35)Hanxi Wrote: I mean, it can't be the BIOS.
I make a UEFI dual-boot system. first I install libreelec, then Win10 with rEFind bootmanager. Basically, the whole works, but after libreelec start and shutdown, the rc-button Power.On don't work. On the other hand, when I starts Win10 and shutdown, Power.On works flawlessly, until I boot libreelec again... like a flip-flop.
There must be an error in the current kernel, because with windows there is no issue.
Test with #0509 and #0509x.
(2016-09-09, 22:12)Milhouse Wrote: To confirm if it is the kernel change, you can try builds #0509 (4.6.0-rc7) then #0509x (4.4.7) - the only difference between these two builds is the kernel. If resume DOES NOT work with #0509, but DOES work with #0509x, then we know it's the kernel change that is responsible.
(2016-09-10, 00:14)tinzarian Wrote: No shit, Sherlock.It's been confirmed that it is a kernel issue months ago. But with the huge benefits the new kernels bring it just makes sense to ignore this and use any new kernel that's available.
(2016-09-10, 00:14)tinzarian Wrote:(2016-09-09, 22:12)Milhouse Wrote: To confirm if it is the kernel change, you can try builds #0509 (4.6.0-rc7) then #0509x (4.4.7) - the only difference between these two builds is the kernel. If resume DOES NOT work with #0509, but DOES work with #0509x, then we know it's the kernel change that is responsible.
No shit, Sherlock.It's been confirmed that it is a kernel issue months ago. But with the huge benefits the new kernels bring it just makes sense to ignore this and use any new kernel that's available.
(2016-09-10, 00:54)Brian B Wrote: What huge benefits or are you being facetious?