5 февраля 2017 г. 3:54:49 CET, Bob Pasken <[email protected]> пишет:
>I have a Dell T605 with the motherboard ATI-ES1000 and an Nvidia nv-290
>
>PCI-e card. Under windows and Linux I can run the system off the Nvidia
>
>card, by shutting the system off, plugging the monitor into the Nvidia
>card and booting. All is well. I do the same thing with the OpenIndiana
>
>Hipster and the system boots, gets to the point where it starts X11 and
>
>then reboots. Nothing other than the usual boot messages appear in
>/var/adm/messages and nothing in the xsession logs. Any ideas?
>
>Cheers
>RWP
>
>_______________________________________________
>openindiana-discuss mailing list
>[email protected]
>https://openindiana.org/mailman/listinfo/openindiana-discuss
I fought with a similar situation (intel + nvidia) yesterday, but to no avail
so far. Guys here told me that the dual setup is known as Optimus and does not
work so far, and suggested to turn it off in bios - to see if the system would
start with one remaining card.
Unfortunately that is not an option for me (corporate laptop, blocked bios) so
I fiddled with xorg.conf and vesa driver and BusID "0:2:0" settings and got to
a point where X11 apparently starts (screen goes blank with no blinking
cursor), but no image appears on the LCD either. Maybe it tries to route to an
output where no monitor is attached, but I can't prove or disprove it without
an extra monitor by looking at logs (wonder if I can make XOrg logs more
detailed and useful). Without a specific BusID value, or with different drivers
(intel, nvidia, nv directly) or without xorg.conf, the GDM startup apparently
fails to find a Device so it can not provide a Screen (as seen in logs) and
just sits there with blank text mode console with a lonely cursor in the corner.
Apparently, I can blindly log in - logs get MATE messages then etc. But
otherwise it is useless.
I am puzzled by your system rebooting - for me it just blocks the display and
text console (including no VT switching) by starting a gdm without output
capabilities. It was up to me to kill gdm or initiate a power-button reboot
(graceful).
What helped in this lockpicking was :
* 'svcadm disable gdm' by default - so system stays in text login prompt.
* a .bashrc function, or a script, to do
trygdm() {
svcadm enable -t gdm
sleep 20
svcadm dissble gdm
less /var/log/XOrg.0.log
}
- this allowed me to kill gdm after predefined time and regain the text console
without reboot
* for practical use, this is combined with my init-script for dualboot support
(out there someplace on my github), so when the partition boots as a virtualbox
guest from another OS, it substitutes the vbox xorg config and does a
conditional 'svcadm enable -t gdm' to spin up gui late in the boot-up
(conditions block gdm from starting if it failed earlier, so text console lives
on at a later boot-up).
Hope this helps you figure it out and helps us both get further in the native
OI setup ;)
My other blocker is intel 8260 wifi which no driver seems to recognize...
Jim
--
Typos courtesy of K-9 Mail on my Samsung Android
_______________________________________________
openindiana-discuss mailing list
[email protected]
https://openindiana.org/mailman/listinfo/openindiana-discuss
