![]() When Xorg starts with the intel driver, it randomly crashes. But maybe you could get the Ubuntu maintainers to upgrade the xserver-xorg-video-intel package to 2.30 (I think 2.2.9* would also work) in the hardy heron release? I don't know if that would work on a Ubuntu system. Īnd it turns out that there was a similar bug reported at Xorg, only occurring with the Intel 965 chipset, and only with versions 2.1.1 and 2.2.1 of xserver-xorg-video-intel.īut I think (knock wood) that it got fixed when I downloaded the latest xserver-xorg-video-intel package - 2.3.0 - from Debian experimental. It was a complete hard freeze : no keyboard shortcuts worked, and I had to shut off the computer using the on-off button. When I upgraded xserver-xorg-video-intel to 2.1.1 (in Debian unstable), my computer would hang at boot-up, just when X was starting. I was using Sidux (which is mostly Debian unstable). I have (at my office) a Dell Optiplex, with an Intel 965q chipset. But maybe you could get the Ubuntu maintainers to upgrade the xserver- xorg-video- intel package to 2.30 (I think 2.2.9* would also work) in the hardy heron release? Īnd it turns out that there was a similar bug reported at Xorg, only occurring with the Intel 965 chipset, and only with versions 2.1.1 and 2.2.1 of xserver- xorg-video- intel.Ĭhanging the driver in "nf" from "intel" to "vesa" stopped the problem, but the screen resolution didn't look that great.īut I think (knock wood) that it got fixed when I downloaded the latest xserver- xorg-video- intel package - 2.3.0 - from Debian experimental. When I upgraded xserver- xorg-video- intel to 2.1.1 (in Debian unstable), my computer would hang at boot-up, just when X was starting. I'm not an ubuntu user, but I seem to have had a similar problem. The log file from this session is attached. Is it possible that this bug is related to "crtc 0" on the ATI 圆00 (M24)? Xrandr -output DVI-0 -crtc 0 -output VGA-0 -crtc 1Īt this point, my desktop is properly displayed on VGA-0 while DVI-0 displays "2: Digital Input Cannot Display This Video Mode". The "working" monitor shifts from DVI-0 to VGA-0 when I issue the following command: On startup the DVI-0 monitor functions as expected while the VGA-0 monitor displays "1: Analog Input Cannot Display This Video Mode". I have a striped down configuration nf with two identical Dell FP1905 monitors connected through a docking station, one via VGA-0 and the other via DVI-0. Previously this worked with the ati driver and it still functions when I change over to the "fglrx" driver (which rules out bad hardware). I'm experiencing problems with dual-head setup and xrandr 1.2 on a recent upgrade to Ubuntu 7.10 on my Dell Latitude D810 laptop with docking station. It appears that this bug could be more closely related to my issue. ![]() However, "mek" referenced me to this bug as well. I already tried running "sudo apt-get update & sudo-apt-get dist-upgrade" in hopes that this would fix or finish the upgrade and/or installing of the security update, but this didn't fix the problem.I posted the following to bug #132716. I believe this error is due to the symbolic link that is used to identify the "libXfont.so.1" file, but I don't know how to fix this problem. ![]() Xauth: timeout in locking authority file get the same message when I try "sudo startx". ![]() Xinit: unable to connect to X server: Connection refused usr/bin/X: error while loading shared libraries: libXfont.so.1: cannot open shared object file: No such file or directory Xauth: timeout in locking authority file /home/user/.Xauthority When I log in and try "startx" I get the following: startx It starts up into command line mode (without GUI) and asks for my username and password. I followed some guides and ran the following commands: ls /dev/sd*Īfter running those commands and rebooting, my Linux system was back up and running again however, not quite like it was before. I let it update while I was at work and when I returned I found a black screen stating, "No init found" and "mount: mounting /dev/mapper/ubuntu-root on /root failed: Invalid argument". I had Ubuntu 14.04 running perfectly on my system and then it underwent a recommended security update. ![]()
0 Comments
Leave a Reply. |