Bug#378081: Cannot read V_BIOS memory allocation error -- resolved
This is working for me in the current version (1.1.1-9). I'm a very happy camper again. signature.asc Description: Digital signature
Bug#378081: Cannot read V_BIOS memory allocation error
I have a feeling that bug 377549 is a cousin to this one. #377549: libint10 hangs while POSTing my ATI Rage 128 Pro video card in dual-head configuration http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=377549
Bug#378081: Cannot read V_BIOS memory allocation error
My attempts to munge it into the current source (without knowledge of C) didn't result in a successful start. Do you still have a working source tree you can diff against? Unfortunately this looks suspiciously like a feature reversion rather than an actual bugfix. But I guess it can tide me over until the sysfs interface for this get sorted out. Assuming I can get that patch working, that is. signature.asc Description: Digital signature
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]
Bug#378081: Cannot read V_BIOS memory allocation error
Package: xserver-xorg-core Version: 1.0.2-9 My six-card x.org configuration started failing and/or crashing during the xserver initialization with memory allocation errors on the 6.9 release and hasn't been fixed so far as I've found yet. Requesting insufficient memory window!: start: 0xd000 end: 0xdbff size 0xd88a Requesting insufficient memory window!: start: 0xdc00 end: 0xe3ff size 0xd88a (EE) R128(3): Cannot read V_BIOS Only the AGP card seems to work with the 7.0 release. The individual logs for all cards and each card, along with a lot of diagnostic information, are available (for size reasons) at http://neuroblastoma.omgwallhack.org/home/jrayhawk/xorgbugreport/ The 6.8 log is a Gentoo compile of x.org made for reference which works much the same way (as far as I can see) as Debian's 6.8 releases did. Gentoo's 6.9/7.0 packages exhibit the same broken behavior as seen here. I can provide any further information if requested. I am willing to give a trustworthy interested party root access to the machine. Just provide a SSH key and I can get that set up. signature.asc Description: Digital signature
