X stopped working on my T41p, and I'm wondering if anybody know if this failure indication of hardware trouble, or if there is some trick to getting the attention of the radeon chip ? I have tried all the usual tricks, holy water, dead chicken, take out batteries for 15 minutes etc. Failing any good ideas for recovery, recommendations for sensible and solid laptops are welcome in private email. Poul-Henning xauth: creating new authority file /home/phk/.serverauth.829 X Window System Version 6.9.0 Release Date: 21 December 2005 X Protocol Version 11, Revision 0, Release 6.9 Build Operating System: FreeBSD 7.0 i386 [ELF] Current Operating System: FreeBSD critter.freebsd.dk 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Tue Jan 2 13:14:38 UTC 2007 root_at_critter.freebsd.dk:/usr/obj/critter/src/sys/TP41P i386 Build Date: 02 January 2007 Before reporting problems, check http://wiki.X.Org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Wed Feb 14 09:06:46 2007 (==) Using config file: "/etc/xorg.conf" [drm] failed to load kernel module "radeon" (EE) RADEON(0): [dri] DRIScreenInit failed. Disabling DRI. (EE) RADEON(0): Idle timed out, resetting engine... (EE) RADEON(0): Idle timed out, resetting engine... (EE) RADEON(0): Idle timed out, resetting engine... [...] -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk_at_FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.Received on Wed Feb 14 2007 - 08:46:57 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:05 UTC