Hello,
I have just updated to b134 but still get the problem. Baring in mind
the limitations I noted in the first place (I am blind and so depend on
tools such as orca and so either need to use gnome or ssh to access the
system) what can I do to find out more information to help? The next
release version is getting very close and it would be a shame if the
release was totally useless to me (I really need X to run for the system
to be useful to me (orca only gives access to the gnome desktop
environment).
Michael Whapples
On 01/-10/-28163 08:59 PM, Jürgen Keil wrote:
I've a similar problem. My Laptop is an old one :
System Configuration: FUJITSU SIEMENS LIFEBOOK S6120
In Build 129 I can start with the native intel driver, but all builds above
including Build 133 have the same effects as Michael describes.
An open bug with b130+ is defect 14101
http://defect.opensolaris.org/bz/show_bug.cgi?id=14101
Can you try to boot your build 133 BE into single user mode
(kernel$ boot options "-ks"; press SHIFT key to switch from
the boot graphics to text mode) and run
dd if=/dev/agpgart
Does that panic the kernel?
_______________________________________________
indiana-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
