Hello, I will need to redo the update, I foolishly decided to remove the BE for b133 as it was using significant space on my system which is fairly tight for HD space (OK, not too tight, but sufficiently that a few GB of stuff which is unusable is undesirable).
Sorry in my original message I was typing the file name from memory, what you said sounded correct /var/log/Xorg.0.log. Shall I let the b133 BE only boot once (I would expect then you would have a correct boot in Xorg.0.log.old and the incorrect boot in Xorg.0.log). Also if it helps, what I remember happening is that the laptop backlight goes out once comes back on with what I think is a completely black screen and then stops, normal booting in b129 turns the backlight off and on a second time and then GDM appears. OK, I am about to start the update now, back when its done. Michael Whapples On 03/03/2010 11:10 AM, Martin Bochnig wrote: > Hello Michael! > > We can get you through this. > The Xorg output goes to the log file > > /var/log/Xorg.0.log > > The previous log - file gets reamed to > > /var/log/Xorg.0.log.old > > Please attach these 2 files from when your scenario happened. > Then we can help you. > > p.s. I have added the xwin-discuss at opensolaris.org alias to the CC: > field, as this list is more relevant. > > > > Regards, > Martin > > > On Wed, Mar 3, 2010 at 11:07 AM, Michael Whapples<mwhapples at aim.com> > wrote: > >> Hello, >> Firstly I will outline my situation so you know what I can manage. I am a >> blind user of opensolaris (blind to the extent I can only make out >> approximate light level from the computer screen but little in any detail, >> eg. I can see the difference of a black screen just before GDM is started, >> the standard gnome background and when gnome has applications open, I cannot >> read any of the text independently, I use orca in that department). >> >> In recent build of opensolaris (b130 onwards, this includes b133) I noticed >> that X never seems to load, to me the screen appears black (NOTE: I may not >> be detecting text error messages). Now I was aware of problems with intel >> graphics and yes the computer I am talking about is a laptop with intel >> graphics (not quite sure on the intel graphics card model, the laptop is a >> dell inspiron 510m). Now mostly my looking at dev builds has been on LiveCDs >> but I realised that if I installed I could create boot environments and look >> at the logs from a working BE. So I installed b129 and updated in a separate >> BE. Now when I mount the b133 BE and look at /var/log/xorg.log >> (capitalisation not guaranteed, I used tab completion when opening the file >> so I know it exists) I only find the xorg release information and nothing >> more. This compares to quite a lot of output in the b129 log which has many >> messages explaining what its doing. >> >> Does this sound like it may be the intel graphics issue? Is there any other >> way I can get the output to try and be more specific about what the problem >> is (why I stated at the beginning my situation)? >> >> Michael Whapples >> _______________________________________________ >> indiana-discuss mailing list >> indiana-discuss at opensolaris.org >> http://mail.opensolaris.org/mailman/listinfo/indiana-discuss >> >>
