Posted: Sat 09 Dec 2017, 08:25
Duplicate post.
READ-ONLY Archive
https://oldforum.puppylinux.com/
If this is what you meant:jake29 wrote:Yes, I noted those parameters are present. But in my last quote, the suggestion is that additional parameters are also required.
Those parameters are kernel parameters that you need to add to your bootloader, the same place where you specify your savefile= and waitdev= parameters (if you use them). They aren't kernel configurations.since kernel 4.13, adding the amdgpu.si_support=1 radeon.si_support=0 or amdgpu.cik_support=1 radeon.cik_support=0 kernel parameter is required. Otherwise, AMDGPU will not start and you will end up with either radeon being used instead or the display being frozen during the boot.
Noted.My card is "Southern Islands" (SI).
Thanks for the clarification. I have not used Boot Options before, but will do some reading on the topic.jamesbond wrote:If this is what you meant:jake29 wrote:Yes, I noted those parameters are present. But in my last quote, the suggestion is that additional parameters are also required.Those parameters are kernel parameters that you need to add to your bootloader, the same place where you specify your savefile= and waitdev= parameters (if you use them). They aren't kernel configurations.since kernel 4.13, adding the amdgpu.si_support=1 radeon.si_support=0 or amdgpu.cik_support=1 radeon.cik_support=0 kernel parameter is required. Otherwise, AMDGPU will not start and you will end up with either radeon being used instead or the display being frozen during the boot.
I appreciate you for trying. You are right in that only a small number of people would benefit / or even have interest in it.kirk wrote:Jake29,
I looked at this: https://wiki.archlinux.org/index.php/Vulkan which says besides the mesa drivers compiled for vulkan, you also need vulcan loader package https://github.com/KhronosGroup/Vulkan- ... tionLayers. I've tried to compile it, but it requires Python3. So I made a python3 package, but now it needs more modules to build. Sorry, I'm giving up for now, it's still an experimental replacement for opengl that only works for some cards.
Code: Select all
echo "These are all of the drives found in your PC:"
INFODRIVES="$(probedisk -m | sed -e 's%/dev/%%')"
The update-firefox script, which is found in the control panel or from "Menu - Internet - Firefox Browser" if you haven't installed firefox before, will install gtk3, apulse, and configure firefox sound to work. I just tried it with a clean savefile and it installed Firefox-57,0,2, sound on youtube works.I compiled pulseaudio-11.1.tar and json-c-0.12.1.tar (from BLFS) then
installed Firefox-57.02 from the control panel.
When Firefox was installing it install GTK3,
Sound works at news sites and youtube now.
Actually that seems to happen if the file you're right-clicking on is positioned near the bottom of the screen. That must be a "feature" of the new ROX . I'll see if the other guys have noticed this and maybe we can figure out when the bug was introduced.I've found a visual bug that occurs when right-clicking on a zip file with long filename. The more characters it has, the larger the space.
I guess I was lucky I didn't break it, anyway, I've been running this for over 5 hours and it's working well.kirk wrote:The update-firefox script, which is found in the control panel or from "Menu - Internet - Firefox Browser" if you haven't installed firefox before, will install gtk3, apulse, and configure firefox sound to work. I just tried it with a clean savefile and it installed Firefox-57,0,2, sound on youtube works.I compiled pulseaudio-11.1.tar and json-c-0.12.1.tar (from BLFS) then
installed Firefox-57.02 from the control panel.
When Firefox was installing it install GTK3,
Sound works at news sites and youtube now.
If you have already installed firefox by some other means and sound is not working, you may have to delete /home/spot/.mozilla and /home/spot/.cache/mozilla. But maybe not, I haven't test that.
I see the same thing happen for years with certain Wine apps (maybe all of them) and with Tor Browser (Firefox-based). It's not something introduced in this beta.Billtoo wrote:I also installed Google-Chrome on the new install and it doesn't show any odd value in task manager.
It seems that there's something not right with Firefox-57.0.2
https://en.wikipedia.org/wiki/LLVM#FeaturesGraphics code within the OpenGL stack can be left in intermediate representation, and then compiled when run on the target machine. On systems with high-end graphics processing units (GPUs), the resulting code remains quite thin, passing the instructions on to the GPU with minimal changes. On systems with low-end GPUs, LLVM will compile optional procedures that run on the local central processing unit (CPU) that emulate instructions that the GPU cannot run internally. LLVM improved performance on low-end machines using Intel GMA chipsets.
We run VLC as root. And yes, you can grant VLC network access. The problem with having user spot run it is that people tend to use a media player to open things on network dives and flash drives and so on. So a restricted user becomes a bigger inconvenience than it is a security risk. At least that's the thinking.I watched a DVD movie with VLC and it runs as root, should it be run as spot?
That actually seems like a kernel bug. But it is just VM allocation, not real memory.The VM-Size in both my Compaq-Presario and Acer installs show a value
in the TB in task manager when running Firefox-57.0.2, not right away but after a short
period of time.
That's good news. Do you notice any improvement with the vulkan drivers? I did make a 64bit mesa vulkan package too, but by that time you had already done it. I did have to patch them for missing linux/memfd.h, so I don't know what consequences that has. I might add the two mesa-vulkan packages to the repo.The 'vulcan loader package' kirk mentioned does not appeared to be required if using the AMDGPU driver.
It's required to build the mesa radeon/amd drivers. So unfortunately we have to have it. The unfortunate part is the size, and it just keeps getting bigger. EDIT: I should also mention we compile llvm static, so you won't see it in the base.sfs.Edit: LLVM seems to be something that would benefit all users and worth keeping up to date.
probedisk2 -m works for me.don570 wrote: Check to see if 'probedisk -m' works in fatdog 720
This is the first time I have started using the AMDGPU Driver - so that change alone I feel is making a noticeable performance difference in 3D graphics / Games. I was able to get almost 100fps in Serious Sam 3, which is great.kirk wrote:That's good news. Do you notice any improvement with the vulkan drivers? I did make a 64bit mesa vulkan package too, but by that time you had already done it. I did have to patch them for missing linux/memfd.h, so I don't know what consequences that has. I might add the two mesa-vulkan packages to the repo.The 'vulcan loader package' kirk mentioned does not appeared to be required if using the AMDGPU driver.
It's required to build the mesa radeon/amd drivers. So unfortunately we have to have it. The unfortunate part is the size, and it just keeps getting bigger. EDIT: I should also mention we compile llvm static, so you won't see it in the base.sfs.Edit: LLVM seems to be something that would benefit all users and worth keeping up to date.
Good news for a savvy individual pushing the boundaries, but deeply worrying for a deliberately compact distro like this? The dog may be fat, but wasn't this originally intended as a reference to 64bit with added functionality. Games are always going to be better on a console. Maybe the dog needs to diet a little...I was able to get almost 100fps in Serious Sam 3
With all due respect Sage, I think you are over-reacting. All I have done here is enabled drivers that are for the most part, already included. And I only advocated having Vulkan support as an optional extra for those that can benefit from it.Sage wrote:Good news for a savvy individual pushing the boundaries, but deeply worrying for a deliberately compact distro like this? The dog may be fat, but wasn't this originally intended as a reference to 64bit with added functionality. Games are always going to be better on a console. Maybe the dog needs to diet a little...I was able to get almost 100fps in Serious Sam 3