Jürgen Keil wrote:
What happens when you boot from CD#1, and append
-m milestone=none -v
to the GRUB boot command line? That shouln't start
half of the the above processes, and runs a shell instead (=
"System Maintenance Mode"). Do you still get console text corruption in
this mode?
Yes.
The five lines leading up to it are:
Configuring devices. (I'm asuming that if I'm
seeing this, the kernel is booted)
Yes, the kernel is booted and runs the "devfsadm" user level
command, to probe for the hardware installed in the machine.
It surprises me a bit that is runs devfsadm. Did you
use "-m milestone=none" in this test? With build 22,
devfsadm is *not* run when I boot the kernel with
-m milestone=none.
I thought I had but I think I made a mistake and just did -v. It turns
out that if I boot with -m milestone=none, the text does not get corrupt.
pseudo-device: devinfo0
devinfo0 is /pseudo/[EMAIL PROTECTED]
xsvc0 at root
xsvc0 is /xsvc
After that I get one line of garbled text
Well, xsvc is a device driver used by the X11 server to
get access to the video card's video memory.
xsvc could be a candidate for being responsible for the
text console corruption.
Is there still text console corruption when you don't allow
the kernel to use the xsvc kernel module, by booting with
... -B install_media=cdrom,disable-xsvc=true -m milestone=none -v
or
... -B install_media=cdrom,disable-xsvc=true -v
The first option does not corrupt the text but the second option does
which leads me to believe that booting with xsvc disabled does not fix
the problem, hence it's not the problem.
_______________________________________________
opensolaris-help mailing list
[email protected]
