Bug#378081: Cannot read V_BIOS memory allocation error
MZ == Milan Zamazal [EMAIL PROTECTED] writes: MZ I don't know yet how stable the solution is but the X server at MZ least starts and seems to work on the first glance, including 3D MZ acceleration, on my secondary graphics card and the Cannot read MZ V_BIOS error message is gone. When an X server is running and I start another one on the other graphics card, input devices (keyboard and mouse) of the first X server stop working. I guess it has nothing to do with the patch, but it's a bug anyway. Regards, Milan Zamazal -- http://www.zamazal.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#378081: Cannot read V_BIOS memory allocation error
MZ == Milan Zamazal [EMAIL PROTECTED] writes: MZ When an X server is running and I start another one on the other MZ graphics card, ... and the same VT (with -sharevts) ... MZ input devices (keyboard and mouse) of the first X server stop MZ working. Actually the X server freezes completely. Regards, Milan Zamazal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#378081: Cannot read V_BIOS memory allocation error
I had the same problem. I've finally solved it (I hope) by applying the patch https://bugzilla.novell.com/attachment.cgi?id=86821 from https://bugzilla.novell.com/show_bug.cgi?id=171453x=0y=0 to xserver-xorg-core_1.0.2-9 (it required some manual adjustments). I don't know yet how stable the solution is but the X server at least starts and seems to work on the first glance, including 3D acceleration, on my secondary graphics card and the Cannot read V_BIOS error message is gone. My Linux kernel version is 2.6.17-3. Regards, Milan Zamazal -- http://www.zamazal.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
75dpi, 100dpi, misc -- which one?
[Please CC me.] In the `intlfonts' package I maintain, there is a lot of fonts, without being classified by their dpi. So I'd like to know how can I find out the resolution of an X11 font? I guess the resolution is defined by the SIZE parameter in the BDF file. Is it right? If so, then I have another question. There is a lot of various numbers there, including 72, 75, 80, 100, and 150. Where should the fonts with the resolution different of 75 and 100 go to? (`misc' is defined as the place for character-cell fonts, cursor fonts, and other low-resolution fonts by Debian Policy, so it doesn't look to me like the right place generally.) Thanks, Milan Zamazal -- Why waste keystrokes when you can waste CPU cycles instead? Karl Fogel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
75dpi, 100dpi, misc -- which one?
[Please CC me.] In the `intlfonts' package I maintain, there is a lot of fonts, without being classified by their dpi. So I'd like to know how can I find out the resolution of an X11 font? I guess the resolution is defined by the SIZE parameter in the BDF file. Is it right? If so, then I have another question. There is a lot of various numbers there, including 72, 75, 80, 100, and 150. Where should the fonts with the resolution different of 75 and 100 go to? (`misc' is defined as the place for character-cell fonts, cursor fonts, and other low-resolution fonts by Debian Policy, so it doesn't look to me like the right place generally.) Thanks, Milan Zamazal -- Why waste keystrokes when you can waste CPU cycles instead? Karl Fogel
