|
OpenBSD General Other questions regarding OpenBSD which do not fit in any of the categories below. |
|
Thread Tools | Display Modes |
|
|||
Xorg hangs on startup on 5.6+ with Intel HD 4400
Does anyone else experience this issue?
I've mailed the info on a possible bug to the OpenBSDs 'misc' list several days ago, but since there was not a single reply yet, I assume it might be quite rare. Since I cannot post links on this forum just yet, here is an excerpt from my aforementioned report: Quote:
|
|
|||
Your account has been enabled to post URL's. Simply use [url] & [/url] tags to bracket links.
|
|
|||
Yeah, I didn't have any expertise/experience to offer either except, are you sure the keyboard is unresponsive? Did you try switching virtual terminals with Ctl+Alt+F1? X runs on VT 5 (I think, on most platforms). F2 - F4 should get you to a login prompt.
Tim. |
|
|||
It looks like you have a dual Intel/NVidia GPU.
In 5.5 were you using the intel video driver or vesa? Do you have the option to disable NVidia in the BIOS? KMS requires libdrm. What happens if you disable inteldrm as described here? Last edited by shep; 24th January 2015 at 04:21 AM. |
|
|||
Quote:
Quote:
5.5 boots automatically with inteldrm/framebuffer console enabled. X starts self-configured, using 'intel' driver. Disabling inteldrm did help. X started normally. So this is the culprit I suppose? Perhaps some code change to it from 5.5 broke things in this case? Last edited by luciderous; 24th January 2015 at 08:41 AM. |
|
|||
Here are some subtle differences I've noticed between 5.5 and 5.7-snapshot dmesg/Xorg logs.
dmesg 5.5: Code:
... vga1 at pci0 dev 2 function 0 "Intel HD Graphics" rev 0x09 intagp0 at vga1 agp0 at intagp0: aperture at 0xc0000000, size 0x10000000 inteldrm0 at vga1 drm0 at inteldrm0 ... vendor "NVIDIA", unknown product 0x0fe4 (class display subclass 3D, rev 0xa1) at pci4 dev 0 function 0 not configured ... Code:
... vga1 at pci0 dev 2 function 0 "Intel HD Graphics" rev 0x09 intagp at vga1 not configured inteldrm0 at vga1 drm0 at inteldrm0 drm: Memory usable by graphics device = 2048M ... 1:0:0: mem address conflict 0xfff80000/0x80000 vendor "NVIDIA", unknown product 0x0fe4 (class display subclass 3D, rev 0xa1) at pci4 dev 0 function 0 not configured ... Code:
... [ 210.889] (--) PCI:*(0:0:2:0) 8086:0a16:1025:079b rev 9, Mem @ 0xb3000000/4194304, 0xc0000000/268435456, I/O @ 0x00005000/64 [ 210.889] (--) PCI: (0:1:0:0) 10de:0fe4:1025:079b rev 161, Mem @ 0xb2000000/16777216, 0xa0000000/268435456, 0xb0000000/33554432, I/O @ 0x00003000/128, BIOS @ 0x????????/524288 [ 210.890] Initializing built-in extension Generic Event Extension [ 210.890] Initializing built-in extension SHAPE [ 210.890] Initializing built-in extension MIT-SHM [ 210.890] Initializing built-in extension XInputExtension [ 210.890] Initializing built-in extension XTEST [ 210.890] Initializing built-in extension BIG-REQUESTS [ 210.890] Initializing built-in extension SYNC [ 210.890] Initializing built-in extension XKEYBOARD [ 210.890] Initializing built-in extension XC-MISC [ 210.890] Initializing built-in extension SECURITY [ 210.890] Initializing built-in extension XINERAMA [ 210.890] Initializing built-in extension XFIXES [ 210.890] Initializing built-in extension RENDER [ 210.890] Initializing built-in extension RANDR [ 210.890] Initializing built-in extension COMPOSITE [ 210.890] Initializing built-in extension DAMAGE [ 210.890] Initializing built-in extension MIT-SCREEN-SAVER [ 210.890] Initializing built-in extension DOUBLE-BUFFER [ 210.890] Initializing built-in extension RECORD [ 210.890] Initializing built-in extension DPMS [ 210.890] Initializing built-in extension X-Resource [ 210.890] Initializing built-in extension XVideo [ 210.890] Initializing built-in extension XVideo-MotionCompensation [ 210.890] Initializing built-in extension XFree86-VidModeExtension [ 210.890] Initializing built-in extension XFree86-DGA [ 210.890] Initializing built-in extension XFree86-DRI [ 210.890] Initializing built-in extension DRI2 [ 210.890] (II) LoadModule: "glx" ... [ 210.910] Loading extension GLX ... [ 210.973] (==) intel(0): Backing store disabled ... [ 211.191] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer [ 211.191] (II) AIGLX: enabled GLX_INTEL_swap_event [ 211.191] (II) AIGLX: enabled GLX_ARB_create_context [ 211.191] (II) AIGLX: enabled GLX_ARB_create_context_profile [ 211.191] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile [ 211.191] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control [ 211.191] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects [ 211.193] (II) AIGLX: Loaded and initialized i965 ... Code:
... [ 254.999] (--) PCI:*(0:0:2:0) 8086:0a16:1025:079b rev 9, Mem @ 0xb3000000/4194304, 0xc0000000/268435456, I/O @ 0x00005000/64 [ 254.999] (--) PCI: (0:1:0:0) 10de:0fe4:1025:079b rev 161, Mem @ 0xb2000000/16777216, 0xa0000000/268435456, 0xb0000000/33554432, I/O @ 0x00003000/128 [ 254.999] (II) LoadModule: "glx" ... [ 255.145] (==) intel(0): Backing store enabled ... [ 255.327] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer [ 255.327] (II) AIGLX: enabled GLX_ARB_create_context [ 255.327] (II) AIGLX: enabled GLX_ARB_create_context_profile [ 255.327] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile [ 255.327] (II) AIGLX: enabled GLX_INTEL_swap_event [ 255.327] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control [ 255.327] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB [ 255.327] (II) AIGLX: enabled GLX_ARB_fbconfig_float [ 255.327] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects [ 255.328] (II) AIGLX: Loaded and initialized i965 ... |
|
|||
There is a BIOS update for your machine that deals with hybrid graphics. My initial search did not find many details though.
Quote:
I wonder if the memory address conflict is due the Nvidia driver reserving that memory space? If the Nvidia driver could be disabled in the bios it is possible that that the memory could be freed up. It would be something to consider when purchasing a hybrid graphics laptop for OpenBSD use. The last thought is if adjusting the usable memory for the intel driver affects anything? |
|
|||
Quote:
Quote:
Quote:
I'm inclined to believe that this is the best lead right now. It seems that it might be wise to bring this issue to the attention of the one responsible for the relevant code change, namely kettenis@. Do you have any idea if he frequents this forum? Or perhaps I should try finding him through the official lists? |
|
|||
Quote:
You want bugs@ in this case. Good luck! |
|
|||
Re: adjusting memory allocation for intel video. I have several systems with onboard video and all have the option to adjust video memory in the bios. This may not do anything with the memory space issue you are having but it costs nothing to try. This HP web page talks about video memory allocation.
I also saw in the FreeBSD forums that there is early work for hybrid Nvidia/Intel cards |
|
|||
Quote:
What would be most ideal would be a port of nouveau. |
|
|||
Unfortunately, the BIOS in my Acer laptop is simplistic at best. There are no options for advanced features, namely those dealing with video cards and memory allocation whatsoever. Quite a shame, really. Thanks for the tip anyway.
|
|
|||
Quote:
Code:
Developer's Lists These lists are for technical discussions of aspects of OpenBSD. They are NOT for beginning or average users, they are not for problem reporting (unless you are including a good fix), and they are not for installation problems. If you have any question about if a message should be posted to any of these lists, almost invariably, it should not be. Use misc, above, instead. Please do not cross post to multiple lists. |
|
|||
There currently is another user with a problem with inteldrm(4) in bugs-openbsd. If you are subscribed to the list you may be able to input on the issue.
|
|
|||
Hi,
I am new with OpenBSD and have the same problem (ver 5.6). with the intel or vesa driver (Lenovo G710) I have intel hd4600 (nvidia is disabled in the bios) I cannot run x11 (black screen) laptop is accessible from the network I tried to do as described above 1. disable tty C1-5 (/etc/ttys ; turn off ) 2. disable inteldrm (config -e /bsd ; disable inteldrm) ; doesn't save after reboot I am still reading openbsd documantation but really want the x to work before doing that :-) i probably doing it wrong because I'm not yet familiar with how this are done in openbsd can someone explain please (for dummies) ? Thanks Last edited by ramib; 10th February 2015 at 05:37 AM. |
|
|||
As I already posted above - this seems to be a bug, not a configuration issue.
Unfortunately, the developers ignored my report - they seem not to care about this issue at the moment. Therefore I had to switch to DragonFlyBSD for now - at least it works for me. Perhaps you should try it as well. |
|
||||
@luciderous: I don't think feeling hard done by and moving to DragonFly BSD is going to resolve the problem. Your bug was likely ignored because it was posted to misc as explained above.
If you had a radeon GPU, you'd probably be complaining about radeondrm on DragonFly... You say that the nvidia discrete graphics is disabled in BIOS setup, yet dmesg reports it...? |
|
|||
Quote:
Did I say it was disabled in BIOS setup? Perhaps you should re-read my bug report more thoroughly. |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Tweaking Xorg For Intel Graphics On OpenBSD 5.3 To Fix HD Screen Tearing | BenHur | OpenBSD Packages and Ports | 0 | 15th August 2013 07:51 AM |
"Intel Packet of Death" not Intel's problem | J65nko | News | 0 | 11th February 2013 07:26 PM |
xorg.conf doesn't exist & I want to keep record of my working Xorg setting | daemonfowl | OpenBSD General | 14 | 28th August 2012 01:13 AM |
xserver hangs with intel driver on 4.8 | rjtp | OpenBSD General | 6 | 1st December 2010 12:48 AM |
Xorg hangs on exit | gpatrick | OpenBSD General | 7 | 27th November 2009 09:24 PM |