On 02/11/10 07:07 PM, Chuck Cox wrote: > John Martin wrote: >> On your system booted with b132 with the first desktop >> session active, please run: >> >> $ echo "vgatext_silent/X" | pfexec mdb -k >> >> Also, since you can ssh into the system, please run the same >> command after X fails to start correctly after the first logout. > > > With X up and working properly: > > vgatext_silent: > vgatext_silent: 3000000 >
That should be an impossible value, it should be 0 or 1. If I ssh into my W2100z even without the NVIDIA driver loaded, I see: rugrat at goober9:~$ echo "vgatext_silent/X" | pfexec mdb -k vgatext_silent: vgatext_silent: 1 rugrat at goober9:~$ On a Quadro NVS 280, I see the thin bar at the top of corrupted pixels. So what I believe is happening is the process (or kernel thread) that is responsible for taking down the progress bar before X starts fails to do so. With the nv X driver, all we would get is visible pixel corruption. With the NVIDIA driver, the progress bar update could corrupt instructions in framebuffer memory. On the W1100z/2100z systems, we should probably permanently disable graphical boot until we understand why the progress bar stays runnings.
