Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
trouble configuring kernel settings for a Xeon E3-1200
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware
View previous topic :: View next topic  
Author Message
visionlogic
n00b
n00b


Joined: 04 Nov 2017
Posts: 8

PostPosted: Mon Nov 06, 2017 4:37 am    Post subject: trouble configuring kernel settings for a Xeon E3-1200 Reply with quote

Hi Everyone,
Earlier this weekend, I was having some trouble with the graphics on my system. After startx, the image displays darkly tinted red.

I initially thought this was a problem with the driver, because I was getting an error in dmesg:

Code:

[    31.715] (EE) AIGLX error: dlopen of /usr/lib64/dri/radeonsi_dri.so failed (/usr/lib64/dri/radeonsi_dri.so: cannot open shared object file: No such file or directory)


Some folks on another thread were kind enough to help me sort through that error and get the amdgpu drivers working according to the xorg log. Unfortunately, this didn't solve the issue of the dark red tint, which is why I am opening a new thread.

I have a feeling there is probably something wrong with my kernel configuration, but I have gone through lspci -v and built in kernel support for the hardware I find therein.

The only other error I find in dmesg is:

Code:

[    1.098678] [Firmware Bug]: ACPI(GFX0) defines _DOD but not _DOS
[    1.098699] ACPI: Video Device [GFX0] (multi-head: yes  rom: yes  post: no)
[    1.099946] acpi device:02: registered as cooling_device0
[    1.099971] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:01/LNXVIDEO:00/input/input3
[    1.100239] ACPI Error: [\_PR_.CPU0._CST] Namespace lookup failure, AE_NOT_FOUND (20170119/psargs-363)
[    1.100257] ACPI Error: Method parse/execution failed [\_PR.CPU1._CST] (Node ffff88084e891230), AE_NOT_FOUND (20170119/psparse-543)


It seems like it has something to do with the video device, but I don't know where this error comes from or how to fix it.

Here is some relevant info:

dmesg:
https://paste.pound-python.org/raw/JlCvlSmky2I5ppbK1e8K/

kernel config:
https://paste.pound-python.org/raw/Y4B2d4sy88zubvvqzscd/

lspci -v
https://paste.pound-python.org/raw/sWNEFHsvQeKXE0AHiiQY/

xorg log
https://paste.pound-python.org/raw/3eiZ3Pw7edyIStG7HRk7/

Thanks in advance for any help! :D I hope that a resolution of this problem might be helpful to somebody else having the same issue.


Last edited by visionlogic on Tue Nov 07, 2017 5:49 am; edited 1 time in total
Back to top
View user's profile Send private message
theotherjoe
Guru
Guru


Joined: 22 Nov 2003
Posts: 368

PostPosted: Mon Nov 06, 2017 5:31 pm    Post subject: Reply with quote

visionlogic,

I dont have any experience with apple hardware and its special features.
Maybe the first steps to narrow down the problems could be to try different
kernel versions. I probably would start with latest 4.9 and 4.13 versions and
see where that gets you. both versions are available under real time sources,
but I would probably begin with vanilla or gentoo sources.
Back to top
View user's profile Send private message
Roman_Gruber
Advocate
Advocate


Joined: 03 Oct 2006
Posts: 3806
Location: Austro Bavaria

PostPosted: Mon Nov 06, 2017 11:24 pm    Post subject: Reply with quote

Does your screen works with sysrescue-cd?

Any reason why you are using such dated kernel => Linux 4.11.12-rt-rt14 x86_64 Gentoo

AFAIK, just my humble opinion, new hardware requires latest ~ kernel. And you are also using quite new hardware, the amd gpu is heavily patched afaik in the kernel, so I would try latest kernel, latest mesa and other related packages for such hardware.

Not sure where the difference is on x86 based apple computers vs native x86 computers
Back to top
View user's profile Send private message
Marlo
Veteran
Veteran


Joined: 26 Jul 2003
Posts: 1414

PostPosted: Tue Nov 07, 2017 1:10 am    Post subject: Reply with quote

Hello visionlogic,
I think your thread heading is not quite right. The important problem is not (now) the screen, but the kernel configuration for a Xeon E3-1200 in an apple. Consider whether it can be formulated more precisely to the problem.
As a starting point, https://wiki.gentoo.org/wiki/Kernel/Gentoo_Kernel_Configuration_Guide is highly recommended. And use the latest gentoo-sources, these are supported here in the forum.

And if there are any difficulties, your precise questions are better answered.

greetings
Ma
_________________
Thank you for your attention, interest and support.
------------------------------------------------------------------
http://radio.garden/
Back to top
View user's profile Send private message
visionlogic
n00b
n00b


Joined: 04 Nov 2017
Posts: 8

PostPosted: Tue Nov 07, 2017 5:48 am    Post subject: trouble configuring correct kernel settings for a Xeon E3-12 Reply with quote

I suppose my trouble is that I'm not sure where else I can go to investigate this problem other than the logs and files I posted originally. I have gone through lspci -v and looked up every item in the kernel driver database: https://cateee.net/lkddb/ , found the associated drivers, and built them into the kernel. I originally did this for all of the items that did not have a "kernel driver in use: ___" section, but then went through again tonight for each and every one.

Although most everything I found in this database was accounted for in my configuration, I did find that this setting was not selected https://cateee.net/lkddb/web-lkddb/EDAC_IE31200.html However, this doesn't seem related to this problem and building it in did not fix my situation.

Originally, I thought the problem had to have something to do with the graphics drivers because of the effect on the display. I still think the problem falls under the category of "display problem" because of the dark red tint on the display. The screen is unusable in this state. The only d messages that seem like errors I have posted below. After looking online for hours, I cant seem to find a solution for my particular case or an indication of what the cause might be. Whenever I search for these errors online, all I can find are bug reports for systems and problems that don't seem similar.

The reason I am using a realtime kernel is because the goal for this system is an audio processing rig. The version I am using actually seems to be quite recent. A non RT kernel is not an option for this use case. I actually know that this kernel version should work because I initially had it working with genkernel.
Everything broke when I tried to build in support for amdgpu. Configuring the kernel from scratch was an attempt to solve the problems I encountered. I have another Gentoo system where I configured the kernel from scratch, and thought that having less superfluous options built in would help me isolate the issue.

Marlo, you are right: the title of this post should be something like: "trouble configuring correct kernel settings for a Xeon E3-1200 in an apple" I will update it as such.

Code:

[    1.069773] pnp: PnP ACPI init
[    1.069862] system 00:00: [mem 0xfed00000-0xfed03fff] has been reserved
[    1.069865] system 00:00: Plug and Play ACPI device, IDs PNP0103 PNP0c01 (active)
[    1.069885] system 00:01: [io  0xffff] has been reserved
[    1.069887] system 00:01: [io  0x1800-0x187f] has been reserved
[    1.069890] system 00:01: [io  0x0800-0x087f] has been reserved
[    1.069892] system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
[    1.069900] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
[    1.070229] system 00:03: [mem 0xfed1c000-0xfed1ffff] has been reserved
[    1.070231] system 00:03: [mem 0xfed10000-0xfed17fff] has been reserved
[    1.070233] system 00:03: [mem 0xfed18000-0xfed18fff] has been reserved
[    1.070235] system 00:03: [mem 0xfed19000-0xfed19fff] has been reserved
[    1.070237] system 00:03: [mem 0xe0000000-0xefffffff] could not be reserved
[    1.070239] system 00:03: [mem 0xfed20000-0xfed3ffff] has been reserved
[    1.070241] system 00:03: [mem 0xfed90000-0xfed93fff] has been reserved
[    1.070242] system 00:03: [mem 0xfed45000-0xfed8ffff] has been reserved
[    1.070244] system 00:03: [mem 0xff000000-0xffffffff] could not be reserved
[    1.070246] system 00:03: [mem 0xfee00000-0xfeefffff] has been reserved
[    1.070249] system 00:03: Plug and Play ACPI device, IDs PNP0c02 (active)
[    1.070269] system 00:04: [mem 0x20000000-0x201fffff] could not be reserved
[    1.070271] system 00:04: [mem 0x40000000-0x401fffff] could not be reserved
[    1.070274] system 00:04: Plug and Play ACPI device, IDs PNP0c01 (active)
[    1.070321] pnp: PnP ACPI: found 5 devices
[    1.071428] pci 0000:01:00.0: assigning 55 device properties
[    1.076069] pci 0000:07:00.0: assigning 7 device properties
[    1.076104] pci 0000:00:1b.0: assigning 4 device properties
[    1.076109] apple-properties: device path parse error -19 at 0x14:
[    1.076114] apple-properties: 00000000: 52 00 00 00 01 00 00 00 02 01 0c 00 d0 41 03 0a  R............A..
[    1.076119] apple-properties: 00000010: 00 00 00 00 01 01 06 00 00 02 7f ff 04 00 2c 00  ..............,.
[    1.076123] apple-properties: 00000020: 00 00 41 00 41 00 50 00 4c 00 2c 00 69 00 67 00  ..A.A.P.L.,.i.g.
[    1.076128] apple-properties: 00000030: 2d 00 70 00 6c 00 61 00 74 00 66 00 6f 00 72 00  -.p.l.a.t.f.o.r.
[    1.076137] apple-properties: 00000040: 6d 00 2d 00 69 00 64 00 00 00 08 00 00 00 0b 00  m.-.i.d.........
[    1.076140] apple-properties: 00000050: 12 04                                            ..
[    1.080667] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
[    1.080676] pci 0000:02:00.0: can't claim BAR 6 [mem 0xfffe0000-0xffffffff pref]: no compatible bridge window
[    1.080707] pci 0000:06:00.0: bridge window [io  0x1000-0x0fff] to [bus 07] add_size 1000
[    1.080708] pci 0000:06:00.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 07] add_size 200000 add_align 100000
[    1.080723] pci 0000:06:04.0: bridge window [io  0x1000-0x0fff] to [bus 39] add_size 1000
[    1.080724] pci 0000:06:04.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 39] add_size 200000 add_align 100000
[    1.080725] pci 0000:06:04.0: bridge window [mem 0x00100000-0x000fffff] to [bus 39] add_size 200000 add_align 100000
[    1.080739] pci 0000:06:06.0: bridge window [io  0x1000-0x0fff] to [bus 6b] add_size 1000
[    1.080740] pci 0000:06:06.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 6b] add_size 200000 add_align 100000
[    1.080741] pci 0000:06:06.0: bridge window [mem 0x00100000-0x000fffff] to [bus 6b] add_size 200000 add_align 100000
[    1.080754] pci 0000:00:01.0: PCI bridge to [bus 01]
[    1.080756] pci 0000:00:01.0:   bridge window [io  0x3000-0x3fff]
[    1.080759] pci 0000:00:01.0:   bridge window [mem 0xb0900000-0xb09fffff]
[    1.080762] pci 0000:00:01.0:   bridge window [mem 0x90000000-0xa01fffff 64bit pref]
[    1.080767] pci 0000:02:00.0: BAR 6: assigned [mem 0xb0820000-0xb083ffff pref]
[    1.080770] pci 0000:00:1c.0: PCI bridge to [bus 02]
[    1.080773] pci 0000:00:1c.0:   bridge window [io  0x2000-0x2fff]
[    1.080778] pci 0000:00:1c.0:   bridge window [mem 0xb0800000-0xb08fffff]
[    1.080784] pci 0000:00:1c.2: PCI bridge to [bus 03]
[    1.080789] pci 0000:00:1c.2:   bridge window [mem 0xb0400000-0xb06fffff]
[    1.080796] pci 0000:00:1c.3: PCI bridge to [bus 04]
[    1.080802] pci 0000:00:1c.3:   bridge window [mem 0xb0700000-0xb07fffff 64bit pref]
[    1.080810] pci 0000:06:00.0: BAR 9: no space for [mem size 0x00200000 64bit pref]
[    1.080813] pci 0000:06:00.0: BAR 9: failed to assign [mem size 0x00200000 64bit pref]
[    1.080815] pci 0000:06:04.0: BAR 8: no space for [mem size 0x00200000]
[    1.080817] pci 0000:06:04.0: BAR 8: failed to assign [mem size 0x00200000]
[    1.080819] pci 0000:06:04.0: BAR 9: no space for [mem size 0x00200000 64bit pref]
[    1.080822] pci 0000:06:04.0: BAR 9: failed to assign [mem size 0x00200000 64bit pref]
[    1.080824] pci 0000:06:06.0: BAR 8: no space for [mem size 0x00200000]
[    1.080826] pci 0000:06:06.0: BAR 8: failed to assign [mem size 0x00200000]
[    1.080828] pci 0000:06:06.0: BAR 9: no space for [mem size 0x00200000 64bit pref]
[    1.080831] pci 0000:06:06.0: BAR 9: failed to assign [mem size 0x00200000 64bit pref]
[    1.080834] pci 0000:06:00.0: BAR 7: no space for [io  size 0x1000]
[    1.080835] pci 0000:06:00.0: BAR 7: failed to assign [io  size 0x1000]
[    1.080837] pci 0000:06:04.0: BAR 7: no space for [io  size 0x1000]
[    1.080839] pci 0000:06:04.0: BAR 7: failed to assign [io  size 0x1000]
[    1.080840] pci 0000:06:06.0: BAR 7: no space for [io  size 0x1000]
[    1.080842] pci 0000:06:06.0: BAR 7: failed to assign [io  size 0x1000]
[    1.080844] pci 0000:06:06.0: BAR 8: no space for [mem size 0x00200000]
[    1.080846] pci 0000:06:06.0: BAR 8: failed to assign [mem size 0x00200000]
[    1.080849] pci 0000:06:06.0: BAR 9: no space for [mem size 0x00200000 64bit pref]
[    1.080851] pci 0000:06:06.0: BAR 9: failed to assign [mem size 0x00200000 64bit pref]
[    1.080854] pci 0000:06:06.0: BAR 7: no space for [io  size 0x1000]
[    1.080855] pci 0000:06:06.0: BAR 7: failed to assign [io  size 0x1000]
[    1.080857] pci 0000:06:04.0: BAR 8: no space for [mem size 0x00200000]
[    1.080859] pci 0000:06:04.0: BAR 8: failed to assign [mem size 0x00200000]
[    1.080861] pci 0000:06:04.0: BAR 9: no space for [mem size 0x00200000 64bit pref]
[    1.080864] pci 0000:06:04.0: BAR 9: failed to assign [mem size 0x00200000 64bit pref]
[    1.080866] pci 0000:06:04.0: BAR 7: no space for [io  size 0x1000]
[    1.080868] pci 0000:06:04.0: BAR 7: failed to assign [io  size 0x1000]
[    1.080870] pci 0000:06:00.0: BAR 9: no space for [mem size 0x00200000 64bit pref]
[    1.080873] pci 0000:06:00.0: BAR 9: failed to assign [mem size 0x00200000 64bit pref]
[    1.080875] pci 0000:06:00.0: BAR 7: no space for [io  size 0x1000]
[    1.080877] pci 0000:06:00.0: BAR 7: failed to assign [io  size 0x1000]



Code:

[    1.103952] [Firmware Bug]: ACPI(GFX0) defines _DOD but not _DOS
[    1.103974] ACPI: Video Device [GFX0] (multi-head: yes  rom: yes  post: no)
[    1.105217] acpi device:02: registered as cooling_device0
[    1.105245] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:01/LNXVIDEO:00/input/input3
[    1.105531] ACPI Error: [\_PR_.CPU0._CST] Namespace lookup failure, AE_NOT_FOUND (20170119/psargs-363)
[    1.105551] ACPI Error: Method parse/execution failed [\_PR.CPU1._CST] (Node ffff88084adc3028), AE_NOT_FOUND (20170119/psparse-543)
[    1.105592] ACPI Error: [\_PR_.CPU0._CST] Namespace lookup failure, AE_NOT_FOUND (20170119/psargs-363)
[    1.105612] ACPI Error: Method parse/execution failed [\_PR.CPU2._CST] (Node ffff88084adc3050), AE_NOT_FOUND (20170119/psparse-543)
[    1.105663] ACPI Error: [\_PR_.CPU0._CST] Namespace lookup failure, AE_NOT_FOUND (20170119/psargs-363)
[    1.105682] ACPI Error: Method parse/execution failed [\_PR.CPU3._CST] (Node ffff88084adc3078), AE_NOT_FOUND (20170119/psparse-543)
[    1.105733] ACPI Error: [\_PR_.CPU0._CST] Namespace lookup failure, AE_NOT_FOUND (20170119/psargs-363)
[    1.105753] ACPI Error: Method parse/execution failed [\_PR.CPU4._CST] (Node ffff88084adc30a0), AE_NOT_FOUND (20170119/psparse-543)
[    1.105803] ACPI Error: [\_PR_.CPU0._CST] Namespace lookup failure, AE_NOT_FOUND (20170119/psargs-363)
[    1.105823] ACPI Error: Method parse/execution failed [\_PR.CPU5._CST] (Node ffff88084adc30c8), AE_NOT_FOUND (20170119/psparse-543)
[    1.105873] ACPI Error: [\_PR_.CPU0._CST] Namespace lookup failure, AE_NOT_FOUND (20170119/psargs-363)
[    1.105892] ACPI Error: Method parse/execution failed [\_PR.CPU6._CST] (Node ffff88084adc30f0), AE_NOT_FOUND (20170119/psparse-543)
[    1.105941] ACPI Error: [\_PR_.CPU0._CST] Namespace lookup failure, AE_NOT_FOUND (20170119/psargs-363)
[    1.105961] ACPI Error: Method parse/execution failed [\_PR.CPU7._CST] (Node ffff88084adc3118), AE_NOT_FOUND (20170119/psparse-543)
[    1.106071] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    1.106335] Non-volatile memory driver v1.3
[    1.106357] Linux agpgart interface v0.103


Code:

[    0.672152] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[    0.672235] ACPI Error: Needed type [Reference], found [Integer] ffff88084a402e58 (20170119/exresop-103)
[    0.672240] ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20170119/dswexec-461)
[    0.672244] ACPI Error: Method parse/execution failed [\_PR.CPU0._PDC] (Node ffff88084e8d21e0), AE_AML_OPERAND_TYPE (20170119/psparse-543)
[    0.672360] ACPI: Dynamic OEM Table Load:
[    0.672366] ACPI: SSDT 0xFFFF88084B348000 00067C (v01 PmRef  ApIst    00003000 INTL 20100915)
[    0.672551] ACPI: Dynamic OEM Table Load:
[    0.672557] ACPI: SSDT 0xFFFF88084B310000 000119 (v01 PmRef  ApCst    00003000 INTL 20100915)
[    0.673245] ACPI : EC: EC stopped
[    0.673247] ACPI : EC: EC started
[    0.673249] ACPI : EC: interrupt blocked
[    0.673364] ACPI: \_SB_.PCI0.LPCB.EC__: Used as first EC
[    0.673366] ACPI: \_SB_.PCI0.LPCB.EC__: GPE=0x17, EC_CMD/EC_SC=0x66, EC_DATA=0x62
[    0.673368] ACPI: \_SB_.PCI0.LPCB.EC__: Used as boot DSDT EC to handle transactions
[    0.673371] ACPI: Interpreter enabled
[    0.673382] ACPI: (supports S0 S3 S4 S5)
[    0.673384] ACPI: Using IOAPIC for interrupt routing
[    0.673401] PCI: MMCONFIG for domain 0000 [bus 00-9b] at [mem 0xe0000000-0xe9bfffff] (base 0xe0000000)
[    0.673633] PCI: MMCONFIG at [mem 0xe0000000-0xe9bfffff] reserved in ACPI motherboard resources
[    0.673643] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Back to top
View user's profile Send private message
visionlogic
n00b
n00b


Joined: 04 Nov 2017
Posts: 8

PostPosted: Tue Nov 07, 2017 6:10 am    Post subject: Reply with quote

Also, Roman_Gruber --yes, the screen works with SRCD. It also worked before, back when I was using genkernel and not using the amdgpu driver. I could go back to this configuration, but I'd rather have a kernel minimally configured for my system and use the drivers meant for my hardware. Plus, there were other problems with the configuration I had before.

My fear is that it is not a matter of failing to enable a setting, but instead that it is a matter of some setting I have enabled causing this broken functionality. Although I am not quite sure how to diagnose the situation other than looking for problems at boot and in dmesg (and the xorg log, which seems clean. The boot log is also clean).

My current kernel configuration is:
https://paste.pound-python.org/raw/4eu5bRJ0nOQwMZYOMOux/
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum