Re: Last night's dist-upgrade broke Gnome-AA session :-(

x 1019 > (**) RADEON(0): DPMS enabled > (II) RADEON(0): Reinitializing Xvideo subsystems > (II) RADEON(0): Rage Theatre setting standard 0x > (II) RADEON(0): X context handle = 0x0001 > (II) RADEON(0): [drm] installed DRM signal handler > (II) RADEON(0): [DRI] installation complete > (II) RADEON(0): [drm] Added 32 65536 byte vertex/indirect buffers > (II) RADEON(0): [drm] Mapped 32 vertex/indirect buffers > (II) RADEON(0): Direct rendering enabled > PEXExtensionInit: Couldn't open default PEX font file Roman_M > ^^^ > (II) RADEON(0): Shutting down Xvideo subsystems > (II) RADEON(0): Rage Theatre setting standard 0x > > > -- > "They that would give up essential liberty for temporary safety deserve > neither liberty nor safety." > -- Benjamin Franklin > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > Two things here jump out at me, one may not be related to your problem, one is. First, it appears that your sync and refresh rates for your monitor are incorrect. I may be mistaken, this could be settings for color depths not in use. I paste the relevant section here: > (II) RADEON(0): Not using default mode "640x350" (vrefresh out of range) > (II) RADEON(0): Not using default mode "640x400" (vrefresh out of range) > (II) RADEON(0): Not using default mode "720x400" (vrefresh out of range) > (II) RADEON(0): Not using default mode "640x480" (vrefresh out of range) > (II) RADEON(0): Not using default mode "800x600" (vrefresh out of range) > (II) RADEON(0): Not using default mode "1024x768" (vrefresh out of range) > (II) RADEON(0): Not using default mode "1024x768" (vrefresh out of range) > (II) RADEON(0): Not using default mode "1280x960" (hsync out of range) > (II) RADEON(0): Not using default mode "1280x1024" (hsync out of range) > (II) RADEON(0): Not using default mode "1600x1200" (hsync out of range) > (II) RADEON(0): Not using default mode "1600x1200" (hsync out of range) > (II) RADEON(0): Not using default mode "1600x1200" (hsync out of range) > (II) RADEON(0): Not using default mode "1600x1200" (hsync out of range) > (II) RADEON(0): Not using default mode "1792x1344" (hsync out of range) > (II) RADEON(0): Not using default mode "1792x1344" (hsync out of range) > (II) RADEON(0): Not using default mode "1856x1392" (hsync out of range) > (II) RADEON(0): Not using default mode "1856x1392" (hsync out of range) > (II) RADEON(0): Not using default mode "1920x1440" (hsync out of range) > (II) RADEON(0): Not using default mode "1920x1440" (hsync out of range) > (II) RADEON(0): Not using default mode "1400x1050" (hsync out of range) Secondly, the following appears several times in the log: > PEXExtensionInit: Couldn't open default PEX font file Roman_M > ^^^ My hunch is that this is your problem. Unfortunately, I have no idea how to fix it, but maybe this can be of some use. Good Luck! Allen Linkenhoker -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Unable to print when using Debian 3.0

a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > I would humbly suggest that you switch back to your original kernel, and install CUPS. Afterward, browse to http://localhost:631. Login as root, and give it a try! The interface is fairly self-explanatory. Good luck! L. Allen Linkenhoker a.k.a. DirtCop -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: sysadmin won't allow linux - PLEASE HELP

at could happen! Allen Linkenhoker From: Matthew Garman <[EMAIL PROTECTED]> To: Debian User's List Subject: Re: sysadmin won't allow linux - PLEASE HELP Message-id: <[EMAIL PROTECTED]> Content-type: text/plain; charset=us-ascii Content-disposition: inline MIME-Version: 1.0 On W

Re: OT Ram upgrade options

t your board is running Pentium II/III/Celeron. They are not as picky about RAM as Athlon boards. On some AMD-based boards, getting the good RAM is essential, as these systems can have problems with slight timing mismatches between sticks, and between what the board expects. Good luck, hope this hel