Bug#451074: xserver-xorg-video-savage: X fails to start locking system after upgrade
severity 451074 important
thank you
Joseph Neal wrote:
> Package: xserver-xorg-video-savage
> Version: 1:2.1.3-4
> Severity: critical
> Justification: breaks unrelated software
>
No it doesn't break unrelated software :)
> X fails to start following today's upgrade. A hard reset is required to restore any kind of functionality. I used
> 'dpkg-reconfigure xserver-xorg" to get a fresh xorg.conf which failed to make a difference.
>
Did you just upgrade xserver-xorg-video-savage? or anything else?
The previous package (1:2.1.3-3) is available from
http://snapshot.debian.net/archive/2007/09/17/debian/pool/main/x/xserver-xorg-video-savage/
If downgrading only this one fixes the problem, then it would be good to
find out which exact commit broke things in the savage driver. Can you
do a git-bisect with the upstream git repository?
If not, could you at least try building the previous 2.1.3-3 with the
following patch applied:
http://git.debian.org/?p=pkg-xorg/driver/xserver-xorg-video-savage.git;a=commitdiff_plain;h=846a69f70d189c486448df269a512b8d42fab0c2;hp=53a2088c5590bb96ce9a7ad30d908c7ea1d54027
> Section "Device"
> Identifier "S3 Inc. VT8375 [ProSavage8 KM266/KL266]"
> Driver "savage"
> BusID "PCI:1:0:0"
> Option "UseFBDev" "true"
> EndSection
>
Do you really need useFBDev?
Brice
Reply to: