Created attachment 316025 [details] emerge --info I am running with an ati card using the xf86-drivers (it's an onboard chip and not much fancy graphics needed on this machine). I was running xen-sources 2.6.34 (we're talking about Dom0). After I finally upgraded to 3.2.12 (and then to 3.3.8 where the problem persists) when I try to start X I get the following message in Xorg.0.log: [ 2623.310] (EE) XKB: Could not invoke xkbcomp [ 2623.310] (EE) XKB: Couldn't compile keymap [ 2623.310] (EE) XKB: Failed to load keymap. Loading default keymap instead. [ 2623.351] (EE) XKB: Could not invoke xkbcomp [ 2623.351] (EE) XKB: Couldn't compile keymap [ 2623.351] XKB: Failed to compile keymap [ 2623.351] Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config. [ 2623.351] Fatal server error: Using strace I found that the clone systemcall to start xkbcomp fails with ENOMEM: 20706 rt_sigaction(SIGALRM, {SIG_IGN, [], SA_RESTORER, 0x7f1694cc4260}, {0x567cc 0, [ALRM], SA_RESTORER, 0x7f1694cc4260}, 8) = 0 20706 clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD , child_tidptr=0x7f1695965b50) = -1 ENOMEM (Cannot allocate memory) There is plenty of memory in the system. When this happens dmesg also shows me: [ 908.073657] X:28283 map pfn expected mapping type write-back for fd1f0000-fd200000, got uncached-minus [ 908.192643] X:28283 freeing invalid memtype fd1f0000-fd200000
Created attachment 316027 [details] Full X.log
Consider me lazy: what is your video card in terms of 'lspci -k' and its mesa model (that is r300, r500, etc). Also, attach your kernel config - seems you'll need to adjust your kernel line.
01:05.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RS880 [Radeon HD 4250] Subsystem: ASRock Incorporation Device 9715 Kernel modules: fglrx The .config will be in a separate attachment
Created attachment 316061 [details] .config from the kernel
(In reply to comment #2) > Consider me lazy: what is your video card in terms of 'lspci -k' and its > mesa model (that is r300, r500, etc). > Also, attach your kernel config - seems you'll need to adjust your kernel > line. disable intel_iommu on the commandline or iommu=0 for the xen commandline?
@comment 3: fglrx and xf86-video-radeon *can't* work together - pick one. If you pick open: CONFIG_FRAMEBUFFER_CONSOLE=y # CONFIG_FB_VESA is not set # CONFIG_FB_UVESA is not set # CONFIG_FB_RADEON is not set sorry, know nothing about xen but your config could use a tweak or two, i.e. CONFIG_IDE has been discouraged for quite awhile (you *seem* to have correct CONFIG_ATA options selected, you just need to make some of them builtin - basically same ones that were in CONFIG_IDE -- recheck though). But basically, this seems to not be a bug, just a support question.
In case of open driver, CONFIG_DRM_RADEON and CONFIG_DRM_RADEON_KMS=y config options are *usually* strongly suggested, but I'm not sure whether xen can interfere here.
(In reply to comment #6) > @comment 3: > fglrx and xf86-video-radeon *can't* work together - pick one. > If you pick open: > CONFIG_FRAMEBUFFER_CONSOLE=y > # CONFIG_FB_VESA is not set > # CONFIG_FB_UVESA is not set > # CONFIG_FB_RADEON is not set > > sorry, know nothing about xen > > but your config could use a tweak or two, i.e. CONFIG_IDE has been > discouraged for quite awhile (you *seem* to have correct CONFIG_ATA options > selected, you just need to make some of them builtin - basically same ones > that were in CONFIG_IDE -- recheck though). > > But basically, this seems to not be a bug, just a support question. I know that and I tried both. fglrx leads to kernel freezes but I keep it in to try newer versions for the moment if i use fglrx (and eselect opengl ati) x does not start with other error messages.
(In reply to comment #7) > In case of open driver, CONFIG_DRM_RADEON and CONFIG_DRM_RADEON_KMS=y config > options are *usually* strongly suggested, but I'm not sure whether xen can > interfere here. Well I tried that, but can't get to the menu entries in make menuconfig. Maybe because of xen?
As I decided to be lazy here, I leave up to you finding me a couple pages describing what is xen (unless you'll move this problem to its proper place - forum). As for Radeons on standard desktop: for those two DRM options you obviously need to set CONFIG_DRM first (you're using menuconfig, right ?). I'm not sure (kinda doubt) if radeon module can be still loaded after fglrx was. For a reason, framebuffer console needs to be builtin. KMS with open driver will definite *not* work if any of the mentioned FB options are set. Just to make sure: we're talking about how to make KMS open driver work for you, not fglrx, right ?
(In reply to comment #10) > As I decided to be lazy here, I leave up to you finding me a couple pages > describing what is xen (unless you'll move this problem to its proper place > - forum). OK XEN the hypervisor You might have heard of it... simply put I run in a VM but DOM0 is the master VM with some special treats. > > As for Radeons on standard desktop: for those two DRM options you obviously > need to set CONFIG_DRM first (you're using menuconfig, right ?). I can set this only to module (guessing I need something else built in?) Yes I am using make menuconfig. > > I'm not sure (kinda doubt) if radeon module can be still loaded after fglrx > was. > For a reason, framebuffer console needs to be builtin. > KMS with open driver will definite *not* work if any of the mentioned FB > options are set. > > Just to make sure: we're talking about how to make KMS open driver work for > you, not fglrx, right ? Yes we are. However: I didn't have CONFIG_DRM set in the 2.6.34 kernel I used before and there it worked. Was there some hard change in the behaveiour towards 3.2?
Sorry, that part about hypervisor still doesn't ring a bell (yes, I could check wikipedia, no, I don't feel like it). Lets make one thing straight - without CONFIG_DRM, I'm not sure *if* xserver could work. Even then it would be at best something like mesa software rendering, if even that.
OK, correction: perhaps with fglrx it would work (haven't used that one in awhile), but that blob did many things in its own way.
(In reply to comment #12) > Sorry, that part about hypervisor still doesn't ring a bell (yes, I could > check wikipedia, no, I don't feel like it). > > Lets make one thing straight - without CONFIG_DRM, I'm not sure *if* xserver > could work. Even then it would be at best something like mesa software > rendering, if even that. For Xen try www.xen.org. Point is: It worked in 2.6.34 without CONFIG_DRM I reenabled it but need to wait until tomorrow until I reboot. I don't necessarily nee 3D Accelleration I would be happy if X would start at all.
OK I did not need to reboot... modprobe radeon -> all is well case closed
(In reply to comment #15) > OK I did not need to reboot... > > modprobe radeon -> all is well case closed However: [157793.908] (II) RADEON(0): GPU accel disabled or not working, using shadowfb for KMS In dmesg I see a stream of: [159347.740128] i2c i2c-1: master_xfer[0] W, addr=0x50, len=1 [159347.740130] i2c i2c-1: master_xfer[1] R, addr=0x50, len=8 [159347.741997] i2c i2c-1: NAK from device addr 0x50 msg #0
