Opened 8 years ago
Closed 8 years ago
#12988 closed bug (fixed)
intel_extreme: Atom N4xx no longer functional
Reported by: | kallisti5 | Owned by: | pulkomandy |
---|---|---|---|
Priority: | normal | Milestone: | Unscheduled |
Component: | Drivers/Graphics | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Attachments (5)
Change History (13)
by , 8 years ago
comment:1 by , 8 years ago
comment:2 by , 8 years ago
A syslog (copy of /var/log/syslog) could be helpful. Preferrably from an up to date version.
comment:3 by , 8 years ago
Alright, I've attaching both a syslog, and a picture of the problematic screen. Sorry for the delay, but Haiku keeps messing up with my FAT partitions when I write to them (to extract the syslog).
The syslog shows some improvements from the old behavior (it seems to properly recognize the native resolution of the LCD panel now). Still same borked screen though :-)
Edit: the tested revision was hrev50904.
comment:4 by , 8 years ago
I've attached the syslog from booting alpha 4.1 from a SD card. Using that version, the video works perfectly.
I've also tried using the kernel driver and accelerant from the alpha 4.1 in an installation of hrev50904 (placing them in the non-packaged directories inside "home").
Strangely enough, the result is exactly the same non working "white screen" as using the latest drivers.
I forgot to get a syslog while using the alpha 4.1 drivers. If anyone thinks it might be useful to have that one, just let me know.
comment:5 by , 8 years ago
Have you blacklisted the original intel driver? That should start the system in VESA mode, or make sure your old driver in non-packaged is used.
comment:6 by , 8 years ago
Yup, I have blacklisted the system intel_extreme driver/accelerant. Boots into VESA (800x600x32). After installing the alpha 4.1 driver/accelerant, the syslog shows that the driver is correctly loaded from the user-mode non-packaged location, but it shows the same "white screen" issue :-/.
I'll try to get a clean syslog from hrev50904, with blacklisted system driver plus the old driver (assuming Haiku does not corrupts again my pendrive while trying to copy the said syslog from that machine).
by , 8 years ago
Attachment: | syslog.hrev50904.alpha4.1-drivers.txt added |
---|
hrev50904 with blacklisted intel_extreme, plus intel_extreme drivers from Alpha4.1
comment:7 by , 8 years ago
comment:8 by , 8 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
FYI, on a Atom N450 based netbook (a clone of Intel Classmate PC) it used to work very well on a pre package-manager nightly (sorry for not being more specific, I've lost track of the revision number).
For me it stopped working when I've installed haiku-nightly-hrev48669-x86_gcc2_hybrid-anyboot.
The symptoms are: the screen (internal LCD) is all white, with some faint lines on the right side of the screen. It seems to try to default to 1366x768 resolution, when the native res is 1024x600.
Trying to use the VGA port with an external 1920x1080 monitor, yields an unusable image: much like the ones we used to get with CRT monitors when the refresh rate was too high.
Forcing a lower resolution (1280x720, for example) seems to work.
All this was on hrev48669.
The unusable white LCD panel is still present on hrev50904. I should try the rest later on.