#1169 closed bug (fixed)
The screen NeoMagic on a Dell Latitude CPi A366 (NeoMagic 256AV) are all messed up
Reported by: | modeenf | Owned by: | axeld |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | Drivers/Graphics/NeoMagic | Version: | R1/pre-alpha1 |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | x86 |
Description
I can't see anything so I can't install or on otherways get you an image.. will try to get a picture.
Tha laptop http://laptop.hug-nordic.org/laptop.php?id=21
The same problems exist on Dell Latitude C840 but here exist another problem as well but this are another bug report.
Attachments (2)
Change History (18)
comment:1 by , 18 years ago
Component: | Drivers/Graphics/nVidia → Drivers/Graphics |
---|
comment:3 by , 18 years ago
Component: | Drivers/Graphics → Drivers/Graphics/NeoMagic |
---|
Can you provide the exact vendor/device IDs of your graphics chip?
comment:5 by , 18 years ago
If I look at the Dell doc. It's a NeoMagic 2200(0x0005,/*MagicMedia 256AV (NM2200) 0x45*/)
It does work with BeOSMax v4b1. But I can't find nm.driver but perhaps it's the nv.driver..
the latest Zeta hade the same problem (Zeta 1.0 - 1.5). Zeta Neo don't have this problem. the ddriver are from 2004-10-07 (YYYY-MM-DD) (again nv.driver)
comment:6 by , 18 years ago
ok have looked at the jame file so nm.xxx should be there.
Have tested version 0.11 from bebits and that worked with BeOSMax v4 b1 (hade no nm.driver that I could find)
will test the driver from build factory.. (can it be rune in BeOS?)
comment:7 by , 18 years ago
Have now tested the lates (2007-04-22) nm.driver from http://factory.haiku-os.org/
the syslog says "KERN 'app_server'[24]:System add-on /boot/config/add-ons/kernel/drivers/bin/nm.driver linking against kernel.so"
And I have no problem
comment:8 by , 18 years ago
What I can see the big thing happend in Revision 16033.
Revision 9998 should be the one at bebits (the driver at bebits ar from 2004-11-18)
comment:9 by , 17 years ago
This can be closed as I don't have the hardware and don't intend to update this :(
But it can be reopend if some one find's the bug again ;)
comment:10 by , 17 years ago
Not sure if this is the same issue or not, but I just got Haiku installed onto a Thinkpad 570E, but can only get it to boot if I use space bar and pick "Fail Safe Video Mode". I did that and got in and ran listdev > listdev.txt, I then rebooted into BeOS Max and grabbed the listdev.txt file and am attaching that to this report. It appears to use a NeoMagic graphics chip, details in the listdev.txt file. I'm guessing it might just be missing PCI ID info?
by , 17 years ago
Attachment: | Thinkpad-570E-listdev.txt added |
---|
comment:11 by , 17 years ago
So I got in with fail-safe mode and set up the screen as 1024x768 24bit and rebooted. Picture of the screen after reboot is attached. Seems all of the colors are messed up now. But hey it's accelerated now. ;) When using the fail safe mode the colors are normal, but video is vesa and unaccelerated.
by , 17 years ago
Attachment: | Thinkpad-570-bad-colors.jpg added |
---|
follow-up: 13 comment:12 by , 17 years ago
On the Thinkpad 570E, I just tried setting the resolution to 1024x768 and colors to 32768 and that seems to work. I've got normal colors now. But it's still an issue that it picks a default that gives bad color.
Device details from listdev output: device Display controller (VGA compatible controller, VGA) [3|0|0] vendor 10c8: Neomagic Corporation device 0005: NM2200 [MagicGraph 256AV]
comment:13 by , 17 years ago
Replying to scottmc:
On the Thinkpad 570E, I just tried setting the resolution to 1024x768 and colors to 32768 and that seems to work. I've got normal colors now. But it's still an issue that it picks a default that gives bad color.
Device details from listdev output: device Display controller (VGA compatible controller, VGA) [3|0|0] vendor 10c8: Neomagic Corporation device 0005: NM2200 [MagicGraph 256AV]
Can the defaults for this device be set so that it is set for 16 bit color and 1024x768 @ 60Hz? That way on first boot up users will have correct. Right now the first boot up of a freshly installed image is what is shown in the attached screenshot. It's hard to see in the screenshot but the test is nearly unreadable, but if you know where things are you can find the screen app and fix it for now.
follow-up: 16 comment:14 by , 17 years ago
Running hrev24868 on the old IBM Thinkpad 570E and it no longer has the weird colors on first startup. Seeing that modeenf no longer has hardware to test on, and the 570E is working ok not, this ticket can be closed.
comment:16 by , 17 years ago
Replying to scottmc:
Running hrev24868 on the old IBM Thinkpad 570E and it no longer has the weird colors on first startup. Seeing that modeenf no longer has hardware to test on, and the 570E is working ok not, this ticket can be closed.
Same here, and now I even have '32 Bits/Pixel 16 Million Colors' maximum, as opposed to the '16 Bits/Pixel 65536 Colors' a while ago on my 570...for which I'd like to thank whoever responsible!
Hm this wasn't a good bug description..
I'm trying to install Haiku from a bootable CD and all of this work, hitting space and use safe mode don't work. (don't know if it should work)
Insted of a desktop I see a black screen with some color on it (in stripes).
Will try to make a foto of it..