Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi,
As the subject says I'm havin problems to assign RAM to my iGPU/ to utilize this RAM.
First of my hardware:
ASRock FM2A88M Extreme4+
A10-7850k
G.Skill RipjawsX DDR3-2400MHz 8GB (2x 4096)
and Software:
Fedora 20 x86_64
3.14.4-200
Mesa 10.1.3
The game Guacamelee runs with ~5FPS (if nothing else is running) and shows me:
Memory Status:
System Ram : 4269801472
Available System Ram : 4269801472
Used System Ram : 4260757504
Reserved System Ram : 34209792
Video Ram : 0
Available Video Ram : 0
Used Video Ram : 0
Audio Ram : 25165824
Available Audio Ram : 21417032
Used Audio Ram : 3748792
Max Used Audio Ram : 3748792
Total Alloc Count : 26328
It's the same with other games and because of this output I thought it would be a problem with the Video RAM.
When I run it at 2400MHz lspci -v -s 00:01.0 shows me:
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 Graphics] (prog-if 00 [VGA controller])
Subsystem: ASRock Incorporation Device 130f
Flags: bus master, fast devsel, latency 0, IRQ 11
Memory at c0000000 (64-bit, prefetchable) [size=256M]
Memory at d0000000 (64-bit, prefetchable) [size=8M]
I/O ports at f000 [size=256]
Memory at ff700000 (32-bit, non-prefetchable) [size=256K]
Expansion ROM at ff740000 [disabled] [size=128K]
Capabilities: <access denied>
Kernel modules: radeon
Since 2133 are recommend I thought this could be the problem (although others got it to work with 2400MHz) and changed it in the BIOS, but it remains the same.
Even though I have 2048MB assigned to the GPU.
Since I "lost" my RAM (i.e top shows less total memory) when I assigned more to the GPU I'm not sure if that's the problem. So could it be something else why I can barely run any games or do you think I'm at least on the right track?
Hope you can help me and sorry for my english. It's not my mother tongue.
Yes, I have some Kaveri files in /lib/firmware/radeon. But I'm not so sure anymore if it's really just the RAM. I tried Xonotic today and it won't even start, because "Your system currently is not capable of hardware accelerated 3D."
So any idea what it could be, that the GPU get detected but won't work probably? I don't have any other GPU so it can't be that the wrong one is in use. And while the open source drivers are slower it should be at least better than this as Phoronix and others show.
Something seems to be wrong with your driver setup.
Now i dont know what exactly should you get for radeonsi (the driver that is used by your card), but you seem to be running software rendering.
Run this:
Now this isnt right. "radeon kernel modesetting" MUST be enabled, along with dpm for APUs to work right.
Make sure you have "radeon.dpm=1 radeon.modeset=1" in your kernel boot options.
From what i see you need:
-enable kms (Kernel Mode Setting)
-enable dpm (Dynamic Power Management - essential for APU integrated graphics performance with OSS drivers) - this might be enabled, but better make sure it is
-make sure you actually have the corresponding firmware file
Now if you have the /etc/default/grub file, edit it with root (sudo) rights, find the line that begins with GRUB_CMDLINE_LINUX_DEFAULT, make it look like this (if you have other options there, you can keep them too):
Only things I changed from your instructions:
I used "GRUB_CMDLINE_LINUX" because I don't have a "GRUB_CMDLINE_LINUX_DEFAULT" line
I did grub2-mkconfig, which uses settings from /etc/default/grub (don't have update-grub)
Does it have to be at a special place in the line?
Does it have to be at a special place in the line?
No. It can be anywhere.
Maybe you can try this -
Go to tty1, log in, stop your graphic display manger service (whatever that you use), stop any service that might be affceted by forced reboot then:
Then restart the the gdm (lightdm, gdm3, kdm, whatever you have) service, log in.
Then dmesg to see if anything changed.
If the screen goes dark at the first command you can try typing blindly. If stays that way, reboot with either with one press on power button (if it works) or alt+printscreen+reisub (the last part is a key sequence pressed one after another while holding alt+printscreen pressed, reboots the computer but prevents file system errors).
Last edited by gradinaruvasile; 05-31-2014 at 11:12 PM.
I stopped kdm, but got "modprobe: FATAL: Module drm is in use." after the first command. Tried do find xorg and other similiar things to stop them but found nothing helpful. So any idea what else I should stop?
And do you have some examples for services that might be affected by forced reboot? Because my common sense tells me that any of them could be.. NetworkManager, bluetooth,audit?
At the second one I get "modprobe: FATAL: Module debug=1 not found".... but yeah.. No surprise because the argument is missing, right? So skip this step? Then at the third one I get a dark screen. If I try to start kdm again it won't work (saw after the reboot, that it was in fact my last command, so it just didn't work).
At the second one I get "modprobe: FATAL: Module debug=1 not found".... but yeah.. No surprise because the argument is missing, right? So skip this step? Then at the third one I get a dark screen. If I try to start kdm again it won't work (saw after the reboot, that it was in fact my last command, so it just didn't work).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.