http://qa.mandrakesoft.com/show_bug.cgi?id=5948
------- Additional Comments From [EMAIL PROTECTED] 2003-30-09 11:21 ------- I can confirm this bug report. I'm seeing the same error message on my IBM T22. If I use the savage driver from Tim Roberts site it works fine. The same bug has been reported and resolved in debian. See; http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=182831 -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------- Reminder: ------- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: The driver 'savage_drv.o' in XFree86-server-4.3-23mdk doesn't work in my machine. The screen flashes, and it looks like the video is out of sync. With an LCD monitor that checks the signal more thoroughly, the message 'Out of Range' or 'Illegal mode' is displayed. There is an error in the XFree86.0.log file: (EE) SAVAGE(0): Failed to fetch any BIOS modes. Disabling BIOS. This prevents the driver from using any of the preset modes. I've downloaded the a copy of the binary driver from http://www.probo.com/timr/savage40.html, and it works. I've downloaded the source code XFree86-4.3-23mdk.src.rpm, and discovered that the files in savage-1.1.27t.tar are identical to the ones on Tim Roberts web site (savage-1.1.27t.zip). I've build the XFree86 release using the files from the cooker site, and the 1.1.27t Savage driver source that's in XFree86-4.3-23mdk.src.rpm, it works. The problem might be that the Imakefile in the Savage driver source is incorrect, and the XFree86 build doesn't halt if there are errors, at least in the driver compiles/links. The location of the vbe includes should be $(XF86SRC)/vbe not -I$(XF86OSSRC)/vbe. So line 45 of xc/programs/Xserver/hw/xfree86/drivers/savage/Imakefile should be -I$(EXTINCSRC) -I$(XF86SRC)/vbe -I$(XF86SRC)/shadowfb Probably when generating a release for Cooker, the "WORLDOPTS = -k" in xc/Makefile should be commented out, so errors in the build can be readily found. There are bug reports of this problem for earlier releases (2523, 3482).
