Opened 7 years ago
Last modified 2 years ago
#13751 new bug
Intel Atom (ValleyView Mobile) not correctly supported by intel_extreme driver
Reported by: | taos | Owned by: | rudolfc |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | Drivers/Graphics/intel_extreme/valleyview | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
I'm triple-booting my Acer TM B115 netbook. Since most of the time I'm running Archlinux on bare metal and Haiku in VirtualBox, I didn't notice that Haiku's intel_extreme driver started to support my GPU. So, when booting hrev51502 x86_64, I was quite surprised to see a slightly scrambled Desktop - it was shifted to the bottom, showing a big black bar at the top and missing the lower part, the left part was displayed on the right, and the right part on the left:
The last time I booted Haiku on bare metal before I noticed the change, I was still at hrev51206 when framebuffer.accelerant was loaded (I'm booting with EFI).
listdev identifies the GPU as
device Display controller (VGA compatible controller, VGA controller) [3|0|0] vendor 8086: Intel Corporation device 0f31: Atom Processor Z36xxx/Z37xxx Series Graphics & Display
listimage | grep accel displays the used graphics driver as:
1522 0x000000b15387d000 0x000000b153a95000 0 0 /boot/system/add-ons/accelerants/intel_extreme.accelerant TEAM 971 (/bin/grep accel):
And Screen application uses the name "Intel Atom (ValleyView Mobile):
I've attached the syslog file.
Attachments (6)
Change History (26)
by , 7 years ago
Attachment: | screenshot7.png added |
---|
comment:1 by , 7 years ago
patch: | 0 → 1 |
---|
by , 7 years ago
Attachment: | Screenshot7.png added |
---|
Screenshot of Screen application under hrev51502.
comment:2 by , 7 years ago
BTW, just noticed that framebuffer_accelerant was removed in hrev51207, since then, vesa_accelerant should be used for both EFI and BIOS systems as backup driver.
comment:3 by , 7 years ago
Let me know if you need further information or if I can help testing a modified version of the intel_extreme driver and accelerant.
BTW, could someone remove "Has a Patch" from the ticket description and change the component from "- General" to Drivers - Graphics - intel_extreme? Thanks.
comment:4 by , 7 years ago
Component: | - General → Drivers/Graphics/intel_extreme |
---|---|
Owner: | changed from | to
comment:5 by , 7 years ago
patch: | 1 → 0 |
---|
comment:6 by , 6 years ago
Problem still exists in hrev52301 (x86_64). It might be a good idea to remove support for this chipset from intel_extreme for the beta.
comment:8 by , 6 years ago
Milestone: | Unscheduled → R1/beta2 |
---|
comment:10 by , 5 years ago
Component: | Drivers/Graphics/intel_extreme → Drivers/Graphics/intel_extreme/ivybridge |
---|---|
Owner: | changed from | to
comment:11 by , 5 years ago
Please try with hrev53857 or later and provide an updated syslog if it still doesn't work.
comment:12 by , 5 years ago
After updating to hrev53880, I still see the same issue. Syslog is attached.
by , 5 years ago
Attachment: | syslog_hrev53880.txt added |
---|
syslog before and after updating to hrev53880
comment:13 by , 5 years ago
Component: | Drivers/Graphics/intel_extreme/ivybridge → Drivers/Graphics/intel_extreme/haswell |
---|
comment:14 by , 5 years ago
Blocking: | 15885 added |
---|
comment:15 by , 5 years ago
Blocking: | 15885 removed |
---|
In https://review.haiku-os.org/c/haiku/+/2499 I disabled the modern Intel devices in the driver. We just don't support them. This will bring back VESA for you.
I think this at least allows us to move this out of the beta2 milestone. We can revisit it later when we start actually adding support for modern Intel video devices.
comment:16 by , 4 years ago
Milestone: | R1/beta2 → R1/beta3 |
---|
Move tickets that will not be solved in beta2 to beta3.
comment:17 by , 4 years ago
Milestone: | R1/beta3 → R1 |
---|
No one is working on the intel driver at the moment so it seems no progress will be made on these issues for beta3. Remove them from the milestone so we can better see our status.
comment:19 by , 2 years ago
It's still using the Framebuffer Driver according to Screen preferences in hrev56571. Syslog is attached.
comment:20 by , 2 years ago
Component: | Drivers/Graphics/intel_extreme/haswell → Drivers/Graphics/intel_extreme/valleyview |
---|---|
Owner: | changed from | to
Indeed Valleyview isn't supported at the moment.
Screenshot of Screen application under hrev51502.