corrupt bootsplash image appears to be known plymouth bug #571567
--
S3 ProSavageDDR K4M266 hard locks on X init when DRI is enabled
https://bugs.launchpad.net/bugs/336311
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-savage in
some additional information:
fresh install from the Kubuntu 10.04 desktop CD did it, only the
bootsplash image appears to be displayed with 8 colors (similar to
attachment).
starting (not installing) Kubuntu from the same CD got me a "hanging"
system again.
** Attachment added: "Kubuntu plymouth
appears to be solved for Lucid for the system mentioned 2009-07-13 -
great work, thanx to the team!
btw, would someone from the team mind telling us out in the wild what
the problem was about?
--
S3 ProSavageDDR K4M266 hard locks on X init when DRI is enabled
https://bugs.launchpad.net/bugs/3363
@Tormod Volden:
current status: System as mentioned in #7 and following, "startx" from
recovery mode, system locked with black screen, hard reset
r...@beta:~# file /var/log/Xorg.0.log
/var/log/Xorg.0.log: empty
--
S3 ProSavageDDR K4M266 hard locks on X init when DRI is enabled
https://bugs.la
confirming behaviour described 2009-07-13 with Karmic
--
S3 ProSavageDDR K4M266 hard locks on X init when DRI is enabled
https://bugs.launchpad.net/bugs/336311
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-savage in ubuntu.
___
** Attachment added: "Xorg.0.log on Hardy (kdm graphic mode)"
http://launchpadlibrarian.net/28980120/Xorg.0.log
--
S3 ProSavageDDR K4M266 hard locks on X init when DRI is enabled
https://bugs.launchpad.net/bugs/336311
You received this bug notification because you are a member of Ubuntu-X,
wh
** Attachment added: "lspci -vvnn on Hardy (kdm graphic mode)"
http://launchpadlibrarian.net/28980100/lspci-vvnn
--
S3 ProSavageDDR K4M266 hard locks on X init when DRI is enabled
https://bugs.launchpad.net/bugs/336311
You received this bug notification because you are a member of Ubuntu-X,
w
** Attachment added: "Xorg.0.log on Jaunty (recovery mode) after failed start
with kdm"
http://launchpadlibrarian.net/28979792/Xorg.0.log
--
S3 ProSavageDDR K4M266 hard locks on X init when DRI is enabled
https://bugs.launchpad.net/bugs/336311
You received this bug notification because you a
** Attachment added: "lspci -vvnn on Jaunty (recovery mode)"
http://launchpadlibrarian.net/28979495/lspci-vvnn
--
S3 ProSavageDDR K4M266 hard locks on X init when DRI is enabled
https://bugs.launchpad.net/bugs/336311
You received this bug notification because you are a member of Ubuntu-X,
whi
** Attachment added: "lshal output on hardy"
http://launchpadlibrarian.net/28978470/lshal
--
S3 ProSavageDDR K4M266 hard locks on X init when DRI is enabled
https://bugs.launchpad.net/bugs/336311
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to x
Don't now if it's the same bug, but an at least very similar behaviour
struck me with an FSC Amilo M 6300, 166 MHz Celeron, 1 GB RAM, 86C380
ProSavageDDR K4M266 after clean install of Jaunty (Kubuntu or Xubuntu
from alternate CD): hard lock on X startup, xorg.conf is empty, lshal
yells
error: dbus
11 matches
Mail list logo
