xorg screen corruption with intel video

[Bruno Damour]

Hello,

I'm trying to upgrade my laptop (Thinkpad X201) from snv151a to solaris 11.0.
After a successful uprgade (so it seems) I'm running into a problem with the intel video.
I had first to set console=force-text in grub, which solves the problem with framebuffer console freezing the screen (and the boot) with garbage (vertical colored lines).
So I can boot.
Unfortunately the X server also displays only this same (or similar) garbage. It doesn't freeze the machine though.
I tried to use Option "Tiling" "false" as per solaris 11-EA release notes, but no effect.
Tried also to use VESA driver, no change. I check from Xorg.0.log that the server is actually loading vesa.
I tried to disable modules. No effect.

Any ideas ? it is in deed strange that corruption occurs with both intel and vesa drivers, or ?

Bruno

[Bruno Damour]

Thank you very much !
You will find two logs and corresponding xorg.conf :
- one (laptop) uses the intel driver
- the second (vesa) the vesa driver.
Both were generated by starting X manually after disabling gdm:
X :0 -config /etc/X11/xorg.conf.(vesa|laptop)
Both got the same result : vertical colored lines
Please do not hesitate to ask me for further info
Bruno

Can you please send me your /var/log/Xorg.0.log file?
thanks
Niveditha

Post by Bruno Damour
Hello,
I'm trying to upgrade my laptop (Thinkpad X201) from snv151a to solaris 11.0.
After a successful uprgade (so it seems) I'm running into a problem with the intel video.
I had first to set console=force-text in grub, which solves the
problem with framebuffer console freezing the screen (and the boot)
with garbage (vertical colored lines).
So I can boot.
Unfortunately the X server also displays only this same (or similar)
garbage. It doesn't freeze the machine though.
I tried to use Option "Tiling" "false" as per solaris 11-EA release notes, but no effect.
Tried also to use VESA driver, no change. I check from Xorg.0.log
that the server is actually loading vesa.
I tried to disable modules. No effect.
Any ideas ? it is in deed strange that corruption occurs with both
intel and vesa drivers, or ?
Bruno
_______________________________________________
opensolaris-discuss mailing list

[Bruno Damour]

Hello,
I upgraded some time ago from solaris 11 express to solaris 11.0.
I have a gcc/gnu installation built from sources in a zone.
I've discovered that trying now to compile doesn't work any longer.
Typically, configure fails with a message seaming to guess that I'm
trying to cross compile without providing a --host option.
I sort of guess this is related to solaris 11 now beeing 64bit only ?
Doesn anyone know how I could recover a working gcc (apart from
installing the ips provided gcc which is gcc-4.5.2 and recompiling my
gcc 4.6.2) ?
Thanks for any hint
Bruno

Example from config.log

configure:5900: checking whether the C compiler works
configure:5922: gcc -I/usr/local/include -L/opt/local/lib
-R/opt/local/lib conftest.c >&5
configure:5926: $? = 0
configure:5975: result: yes
configure:5978: checking for C compiler default output file name
configure:5980: result: a.out
configure:5986: checking for suffix of executables
configure:5993: gcc -o conftest -I/usr/local/include -L/opt/local/lib
-R/opt/local/lib conftest.c >&5
configure:5997: $? = 0
configure:6019: result:
configure:6041: checking whether we are cross compiling
configure:6049: gcc -o conftest -I/usr/local/include -L/opt/local/lib
-R/opt/local/lib conftest.c >&5
conftest.c:17:19: fatal error: stdio.h: No such file or directory
compilation terminated.
configure:6053: $? = 1
configure:6060: ./conftest
./configure[6062]: eval[1]: ./conftest: not found [No such file or
directory]
configure:6064: $? = 127
configure:6071: error: in `/root/data/R-2.14.0':
configure:6073: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.

[Ali Bahrami]

Post by Bruno Damour
Hello,
I upgraded some time ago from solaris 11 express to solaris 11.0.
I have a gcc/gnu installation built from sources in a zone.
I've discovered that trying now to compile doesn't work any longer.
Typically, configure fails with a message seaming to guess that I'm trying to cross compile without providing a --host option.
I sort of guess this is related to solaris 11 now beeing 64bit only ?
Doesn anyone know how I could recover a working gcc (apart from installing the ips provided gcc which is gcc-4.5.2 and recompiling my gcc 4.6.2) ?
Thanks for any hint
Bruno

...

Post by Bruno Damour
configure:6049: gcc -o conftest -I/usr/local/include -L/opt/local/lib -R/opt/local/lib conftest.c >&5
conftest.c:17:19: fatal error: stdio.h: No such file or directory

This has nothing to do with "Solaris being 64-bit only".
All that means is that there's no longer a 32-bit kernel.
Most people haven't run the 32-bit kernel for years, as x86
hardware has been able to support 64-bits for a long time.
Rest assured that S11's ability to run 32-bit code in natively
in userland is still there.

It's been ages since I built gcc, but I think that the messages about
cross compiling are just part of the process it goes through. Had the
test compile worked, it would likely have determined that it wasn't
building a cross compiler.

I think the error message about not finding stdio.h is likely at
the root of things. Have you installed the system header files?

# pkg search -r /usr/include/stdio.h
# INDEX ACTION VALUE PACKAGE
# path file usr/include/stdio.h pkg:/system/***@0.5.11-0.175.0.0.0.2.1

# pkg install system/header

- Ali

[Bruno Damour]

Post by Ali Bahrami
I think the error message about not finding stdio.h is likely at
the root of things. Have you installed the system header files?
# pkg search -r /usr/include/stdio.h
# INDEX ACTION VALUE PACKAGE
# path file usr/include/stdio.h
# pkg install system/header

OMG, you are right, I had to reinstall the zone, because it wouldn't
upgrade, and I forgot to re-install system/header...
Thank you so much
Bruno

[Bruno Damour]

Hello Niveditha,
Thank you so much for your answer.
I'll experiment along the lines you give and report back later on
tonight or tomorrow.
I'll try to get access from a ssh console to trace and pstack the Xorg
process.
I'll sure get you a no Xorg xconf. I should of coure have tried it
first, but I had the same problem when booting with the liveUSB so I
suspect it will not yield result, maybe the logs...
I will also try to tweak the BIOS
Bruno

HI Bruno,
From the log file, looks like X started ok. Can you do a pstack of
the Xorg pid? Also what happens when you don't use a xorg.conf at
all? I would like to see that log file as well.
I know there are some lenovo laptops that hang with VT-d enabled. Can
you try disabling that in the BIOS, although I suspect that is not the
problem you are having.
Thanks
Niveditha

[Bruno Damour]

Well you gave me the good hint.
Everything works fine if I disable the VT-D option in the BIOS.
Thanks a lot
Bruno

Post by Bruno Damour
Hello Niveditha,
Thank you so much for your answer.
I'll experiment along the lines you give and report back later on
tonight or tomorrow.
I'll try to get access from a ssh console to trace and pstack the Xorg
process.
I'll sure get you a no Xorg xconf. I should of coure have tried it
first, but I had the same problem when booting with the liveUSB so I
suspect it will not yield result, maybe the logs...
I will also try to tweak the BIOS
Bruno

HI Bruno,
From the log file, looks like X started ok. Can you do a pstack of
the Xorg pid? Also what happens when you don't use a xorg.conf at
all? I would like to see that log file as well.
I know there are some lenovo laptops that hang with VT-d enabled.
Can you try disabling that in the BIOS, although I suspect that is
not the problem you are having.
Thanks
Niveditha