> Remove the splashimage, foreground and background lines.
> And remove the ",console=graphics" option on the
> kernel$ line,
>
> Before all the opensolaris boot entries there should
> be another "splashimage /boot/grub/splash.xpm.gz"
> line that should be removed.
>
> With all this removed grub and the kernel should boot
> in text mode.
>    
Cool :-)

Now I found the irritating error which was the same thing as I 
experienced in Belenix a while back:

The error is like so: Mobile 4 chipset present, activating quirks

Setting RWBF forcefully

Invalid Bios RMRR: Disabling Intel IOMMU

No wonder I was complaining about poor HD performance!!! Gosh if only I 
had text boot before I would've already holla'd about this issue already 
as for the first time I experienced this on the 21st of Jan 2010 with 
Belenix 0.8 Beta upon my first successful install of the system,
- Just searched my archives and a similar issue can be found on the 
Belenix forum under a post entitled: /Belenix 0.8 Beta successfully 
installed but bugs with Intel series 4 chipset/

This is also probably contributing to the fact that I cannot bring the 
system down into single user mode properly, as if it's a bios issue then 
the display certainly is getting effected!!! - by invalid GPU switches 
most likely has mentioned my system's a hybrid of dedicated and dynamic 
memory.

This is all really bad news as it means that I am unable to perform the 
upgrade to build 133 unless someone has a patch for my system that get's 
rid of this error and allows me access to the single user console mode.

I desperately need to update my NIC driver to the yge Yukon driver as my 
current driver is for Solaris10 which has a problem when running more 
then 2 zones on the system meaning global and an extra zone. This cannot 
be done without the installation of snv_133 and so the wheel turns and I 
am stuck :-(

Regards,

Kaya
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://mail.opensolaris.org/pipermail/laptop-discuss/attachments/20100228/1da964b0/attachment.html>

Reply via email to