Opened 11 years ago
Closed 6 years ago
#10404 closed bug (fixed)
Intel(R) GMA 950 doesn't work with Intel Extreme driver and with Vesa driver.
Reported by: | walera | Owned by: | kallisti5 |
---|---|---|---|
Priority: | high | Milestone: | R1/beta2 |
Component: | Drivers/Graphics/intel_extreme | Version: | R1/alpha4.1 |
Keywords: | boot-failure | Cc: | |
Blocked By: | Blocking: | ||
Platform: | x86 |
Description
My notebook Quanta SW1 with Intel 82945GM chipset and integrated Intel GMA 950 graphics. I try install different versions of Haiku from Alpha 2 to hrev46656 but by use intel_extreme driver (default loading from installation CD) I see colors noice on LCD screen. If I choice fail-safe video mode (I try all modes) I see black screen only but I hear loading from CD. Resolution of integrated LCD screen is 1280x800. I make my tests with external D-SUB monitor also but result was identical.. I try loading from Zeta 1.21 CD also. Zeta doesn't work in VESA mode also but can work in monochrome B/W mode. I make listdev command under Zeta (see attachment).
Attachments (9)
Change History (25)
by , 11 years ago
Attachment: | ListDev.log added |
---|
by , 11 years ago
Attachment: | colors_noise.JPG added |
---|
follow-up: 2 comment:1 by , 11 years ago
This looks like the intel_extreme driver didn't manage to allocate enough memory for the framebuffer. A syslog would be useful, if you manage to extract it.
comment:2 by , 11 years ago
Replying to pulkomandy:
This looks like the intel_extreme driver didn't manage to allocate enough memory for the framebuffer.
But I see problem in VESA driver also.
A syslog would be useful, if you manage to extract it.
I make bootable USB flash and extract syslogs in two loading modes: default loading (intel_extreme driver) and by loading in VESA mode. See attachment.
follow-up: 5 comment:3 by , 11 years ago
Things look fine on the video driver initialization and mode setting side. However I noticed this:
2263 KERN: add_memory_type_range(5414, 0xc0000000, 0x10000000, 0) 2264 KERN: set MTRRs to: 2265 KERN: mtrr: 0: base: 0xc0000000, size: 0x40000000, type: 0 2266 KERN: remove_memory_type_range(86, 0xc0000000, 0x300000, 1) 2267 KERN: set MTRRs to: 2268 KERN: mtrr: 0: base: 0xc0000000, size: 0x40000000, type: 0 2269 KERN: add_memory_type_range(5414, 0xc0000000, 0x10000000, 1) 2270 KERN: set MTRRs to: 2271 KERN: mtrr: 0: base: 0xcf691000, size: 0x1000, type: 0 2272 KERN: mtrr: 1: base: 0xcf697000, size: 0x1000, type: 0 2273 KERN: mtrr: 2: base: 0xcf698000, size: 0x1000, type: 0 2274 KERN: mtrr: 3: base: 0xd0000000, size: 0x10000000, type: 0 2275 KERN: mtrr: 4: base: 0xe0000000, size: 0x20000000, type: 0 2276 KERN: mtrr: 5: base: 0xc0000000, size: 0x40000000, type: 1 2277 KERN: loaded driver /boot/system/add-ons/kernel/drivers/dev/net/pegasus 2278 KERN: add_memory_type_range(5422, 0x90000, 0x70000, 0) 2279 KERN: set MTRRs to: 2280 KERN: mtrr: 0: base: 0x90000, size: 0x10000, type: 0 2281 KERN: mtrr: 1: base: 0xa0000, size: 0x20000, type: 0 2282 KERN: mtrr: 2: base: 0xc0000, size: 0x40000, type: 0 2283 KERN: mtrr: 3: base: 0xd0000000, size: 0x10000000, type: 0 2284 KERN: mtrr: 4: base: 0xe0000000, size: 0x20000000, type: 0 2285 KERN: mtrr: 5: base: 0xc0000000, size: 0x40000000, type: 1 2286 KERN: update_mtrrs(): Succeeded setting MTRRs after ignoring uncacheable ranges up to size 0x1000. 2287 KERN: remove_memory_type_range(5422, 0x90000, 0x70000, 0) 2288 KERN: set MTRRs to: 2289 KERN: mtrr: 0: base: 0xcf691000, size: 0x1000, type: 0 2290 KERN: mtrr: 1: base: 0xcf697000, size: 0x1000, type: 0 2291 KERN: mtrr: 2: base: 0xcf698000, size: 0x1000, type: 0 2292 KERN: mtrr: 3: base: 0xd0000000, size: 0x10000000, type: 0 2293 KERN: mtrr: 4: base: 0xe0000000, size: 0x20000000, type: 0 2294 KERN: mtrr: 5: base: 0xc0000000, size: 0x40000000, type: 1
There seem to be not enough MTRRs to set the complete memory caching map somewhere during video init, then the problem goes away as a range is unmapped.
Is this a 64-bit machine? I think in 64-bit mode, a better system can be used for setting this, avoiding the limitation. If it isn't, maybe we'll have to fix our MTRR allocation code again.
comment:4 by , 11 years ago
The MTRR code is fine. It can ignore uncacheable ranges, since that property will still be enforced via the PTE flags.
comment:5 by , 11 years ago
Replying to pulkomandy:
Is this a 64-bit machine? I think in 64-bit mode, a better system can be used for setting this, avoiding the limitation. If it isn't, maybe we'll have to fix our MTRR allocation code again.
This machine support 64 bit OS. CPU - Intel® Core™2 Duo Processor T7200, RAM - 4 Gb. Win7 64 bit work on this computer w/o any problems.
I try last x86_64 nightly image but with identical result..
I make new test - remove 2 Gb RAM module. After it Haiku loaded w/o any problems. See new syslog in attachment.
comment:6 by , 11 years ago
Blocking: | 7665 added |
---|
comment:7 by , 8 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:8 by , 7 years ago
There have been a lot of fixes to the Intel video driver in the past 3 years. Could you please retest?
comment:9 by , 6 years ago
Keywords: | boot-failure added |
---|
comment:10 by , 6 years ago
Blocking: | 7665 removed |
---|
by , 6 years ago
Attachment: | listimage_grep_drivers.hey68you.txt added |
---|
color noise and left margin added
by , 6 years ago
Attachment: | IMG-20181016-WA0007.jpg added |
---|
screen-shot color noise and left margin added
comment:11 by , 6 years ago
I'm having similar issue with a left margin added (and right side of screen is out-of-bounds/hidden).
I'm on post R1/beta hrev 52397 Samsung SA300/SA350 24" Intel GMA (i945G)
Please see attachments and screenshot attachment
device Display controller (VGA compatible controller, VGA controller) [3|0|0] vendor 8086: Intel Corporation device 2772: 82945G/GZ Integrated Graphics Controller
comment:12 by , 6 years ago
You seem to have a different problem though? This ticket is about black screen on boot.
comment:13 by , 6 years ago
But I do have the color noise :)
In any case, I think you (on IRC) once pointed me to an different open ticket with a similar issue... please let me know if you can find it and/or should I open a separate new bug?
comment:14 by , 6 years ago
Milestone: | R1 → R1/beta2 |
---|
comment:16 by , 6 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Color noise is indeed a separate ticket, so if there is at least output, this ticket is fixed.
Color noise by use intel_extreme driver