I think Beryl is definitely not involved. I have never have Beryl started automatically. I always begin with a Metacity desktop and start Beryl manually from "System Tools->Beryl Manager". Anyway, for the test I explicitly set the desktop manager to Matacity in Beryl Manager and then rebooted using the 'nv' driver and kernel 2.6.20-16.28. It made no difference. I got the black screen exactly as before.
After a successful boot with 2.6.20-15 Xorg.0.log seems the same, with the following lines added at the end:
(II) Configured Mouse: ps2EnableDataReporting: succeeded
Could not init font path element /usr/X11R6/lib/X11/fonts/misc, removing from list!
Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list!
Could not init font path element /usr/X11R6/lib/X11/fonts/Type1, removing from list!
In the syslog, the message "apm: disabled - APM is not SMP safe" is followed by the start of the Bluetooth daemon. Since I don't use Bluetooth, I tried to uninstall the package bluez-utils, because other people were reporting network problems. But that also made no difference.
I think Beryl is definitely not involved. I have never have Beryl started automatically. I always begin with a Metacity desktop and start Beryl manually from "System Tools->Beryl Manager". Anyway, for the test I explicitly set the desktop manager to Matacity in Beryl Manager and then rebooted using the 'nv' driver and kernel 2.6.20-16.28. It made no difference. I got the black screen exactly as before.
After a successful boot with 2.6.20-15 Xorg.0.log seems the same, with the following lines added at the end: porting: succeeded lib/X11/ fonts/misc, removing from list! fonts/X11/ cyrillic, removing from list! lib/X11/ fonts/Type1, removing from list!
(II) Configured Mouse: ps2EnableDataRe
Could not init font path element /usr/X11R6/
Could not init font path element /usr/share/
Could not init font path element /usr/X11R6/
In the syslog, the message "apm: disabled - APM is not SMP safe" is followed by the start of the Bluetooth daemon. Since I don't use Bluetooth, I tried to uninstall the package bluez-utils, because other people were reporting network problems. But that also made no difference.