3rd Dapper Drake Install Log
From Admin-SIG
The second attempt at install broke too. Perhaps it was the LVM switch, but I think all problems trace to the GDM lock-ups. I was unable to shutdown cleanly, AT ALL. I think GDM doing things was the problem.
Without clean shut-downs, scripts were unable to
save state properly.
On re-boot I lost things like networking, etc.
Networking would work with a /etc/init.d/networking restart.
But this is a symptom of something more problematic.
Another irritation was that the portmapper would work. pmap_dump and pmap_save would freeze too. This made autofs problematic. I decided to re-install, instead of debug. This could be a lengthy process.
On the 3rd install, I choose the safe-graphics option, and got 1600x1200 resolution. It also automagicly mounted my LVM volumes that I had set up at the previous install.
I added some user accounts, mostly just in case I messed up my main account.
I then did :
| Table of contents |
X-Server upgrade
sudo apt-get update sudo apt-get install linux-restricted-modules-$(uname -r) sudo apt-get install xorg-driver-fglrx sudo aticonfig --initial sudo aticonfig --overlay-type=Xv
to get the proper ATI fglrx X-server running. Lets see if this is the culprit. Reboot and see if GDM still works.
AHA! There's the culprit! System locks up on logout now!
After a cold-boot, I tried again. I changed all driver sections to "fglrx", then I tried
sudo dpkg-reconfigure xserver-xorg
I can't remember all the settings I hit, but I answered questions as best I could. Left things blank where I didn't know what they were talking about, now I can logout, and GDM seems to work.
--Aaron 09:28, 12 Sep 2006 (MDT)
Later, when installing Google Earth, It failed.
In /etc/X11/xorg.conf Device section listed Driver as "ati".
I did some messing about, but I think the only important thing was to change
this to "fglrx".
After a reboot, Google Earth worked, hence I think I got the
3D-accel driver working for the ATI Radeon chip on my motherboard.
--Aaron 22:52, 12 Sep 2006 (MDT)
It was suggested that the fglrx driver I have is buggy.
> fglrxinfo display: :0.0 screen: 0 OpenGL vendor string: ATI Technologies Inc. OpenGL renderer string: RADEON XPRESS 200 Series Generic OpenGL version string: 2.0.5814 (8.25.18) > > glxgears -printfps 4698 frames in 5.0 seconds = 939.460 FPS 4763 frames in 5.0 seconds = 952.417 FPS
Kilz on the Ubuntu forum suggested trying a later driver: http://wiki.cchtml.com/index.php/Ubuntu_Dapper_Installation_Guide#Method_2:_Generating.2FInstalling_Ubuntu_packages_for_the_8.28.8_drivers_in_Ubuntu_Dapper_Manually
After this, I get:
> fglrxinfo display: :0.0 screen: 0 OpenGL vendor string: ATI Technologies Inc. OpenGL renderer string: RADEON XPRESS Series Generic OpenGL version string: 2.0.6011 (8.28.8) > > glxgears -printfps 412 frames in 5.0 seconds = 82.301 FPS 414 frames in 5.0 seconds = 82.798 FPS 509 frames in 5.0 seconds = 101.717 FPS
Ick. Others reported this. However, they were also stable. I'll try it. Google earth seems sick though. High cpu. nothing happens.
After making this change to /etc/X11/xorg.conf:
< Option "UseFBDev" "false" < Option "VideoOverlay" "on" < Option "OpenGLOverlay" "off" --- > Option "UseFBDev" "true" > # Option "VideoOverlay" "on" > # Option "OpenGLOverlay" "off"
I got:
> glxgears -printfps 612 frames in 5.0 seconds = 122.324 FPS 613 frames in 5.0 seconds = 122.580 FPS
Which is some improvement. At least the system did not crash on logout this time. Google Earth still seems to be stuck in a continual loop at the splash screen.
--Aaron 09:31, 14 Sep 2006 (MDT)
OK. tried again. Switched over to older fglrx driver. I now have:
> fglrxinfo display: :0.0 screen: 0 OpenGL vendor string: ATI Technologies Inc. OpenGL renderer string: RADEON XPRESS 200 Series Generic OpenGL version string: 2.0.5879 (8.26.18) > > glxgears -printfps 4638 frames in 5.0 seconds = 927.417 FPS 4761 frames in 5.0 seconds = 952.155 FPS
And google earth seems to work! Will report on log-out and shutdown after I have had a chance to test them.
aargh. On re-boot, fglrx seems to be failing. no 3d-accel. no visual. no fglrxinfo. Here is part of /var/log/Xorg.0.log:
(II) LoadModule: "fglrx"
(II) Loading /usr/lib/xorg/modules/drivers/fglrx_drv.so
(II) Module fglrx: vendor="FireGL - ATI Technologies Inc."
compiled for 6.8.99.8, module version = 8.26.18
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 0.7
...
(II) LoadModule: "drm"
(II) Reloading /usr/lib/xorg/modules/linux/libdrm.so
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: Open failed
[drm] failed to load kernel module "fglrx"
(WW) fglrx(0): Failed to open DRM connection
...
(II) Module fb: vendor="X.Org Foundation"
compiled for 7.0.0, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.2
...
(II) Module ramdac: vendor="X.Org Foundation"
compiled for 7.0.0, module version = 0.1.0
ABI class: X.Org Video Driver, version 0.8
(==) fglrx(0): NoAccel = NO
...
(II) fglrx(0): driver needs X.org 6.8.x.y with x.y >= 99.8
(II) fglrx(0): detected X.org 7.0.0.0
(II) Loading extension ATIFGLRXDRI
(II) fglrx(0): doing DRIScreenInit
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: Open failed
[drm] failed to load kernel module "fglrx"
(II) fglrx(0): [drm] drmOpen failed
(EE) fglrx(0): DRIScreenInit failed!
(WW) fglrx(0): ***********************************************
(WW) fglrx(0): * DRI initialization failed! *
(WW) fglrx(0): * (maybe driver kernel module missing or bad) *
(WW) fglrx(0): * 2D acceleraton available (MMIO) *
(WW) fglrx(0): * no 3D acceleration available *
(WW) fglrx(0): ********************************************* *
...
(II) fglrx(0): Acceleration enabled
(II) fglrx(0): Direct rendering disabled
...
--Aaron 13:32, 11 Oct 2006 (MDT)
oops... earlier kernel seems to work:
earwig:~> fglrxinfo display: :0.0 screen: 0 OpenGL vendor string: ATI Technologies Inc. OpenGL renderer string: RADEON XPRESS 200 Series Generic OpenGL version string: 2.0.5879 (8.26.18) > earwig:~> glxgears -printfps 4372 frames in 5.0 seconds = 874.246 FPS 4695 frames in 5.0 seconds = 935.862 FPS 4725 frames in 5.0 seconds = 944.976 FPS > earwig:~> uname -a Linux earwig 2.6.15-26-amd64-generic #1 SMP PREEMPT Fri Sep 8 19:55:50 UTC 2006 x86_64 GNU/Linux
Automatix
I fillowed the update-by-apt instructions, launch Automatix, and quit. This time I hit cancel on that closing menu, which keeps the Autimatix sources.list, which is all I really want.
Now I can
apt-cache search apt-get install apt-get source apt-get remove dpkg-reconfigure
as I am used to, with a rich set of avaulable packages.
I won't do the large install this time, since I'm still not absolutely sure that the system is stable this time.
I installed some of my favorite tools, low risk:
apt-get install tcsh rxvt mrxvt jove
Window Managers
Now lets try the tricky stuff... See if we can get my favorite window managers running with GDM...
apt-get install sawfish enlightenment
Seems to be working. It still does not support GNOME with sawfish, I may hack that later. Enlightenment is good enough for me.
Automounter
The main indicator of sickness on the 2nd install was when the automounter didn't work (time out, 2+ minutes to mount a NFS share)
apt-get install portmap autofs
Follow the NFS directions, and automounter is working cleanly.
--Aaron 10:33, 12 Sep 2006 (MDT)
gdm
AARGH!!!! Everything was fine, then, suddenly, for no appreciable reason, it started locking up on log-out again. Perhas there is something about Ubuntu that once you have a lock-up, the un-clean shutdown causes MORE mess, and things get bad.
Here are the (last few) things I tried when I got the machine NOT to lock on logout, or commanding shutdown.
The gdm log, /var/log/gdm/:0.log showed two odd
warning/error messages.
One was that the file /etc/X11/xserver/SecurityPolicy was missing.
Strangely enough, I found a file by this name in /usr/share/doc
which had some comments in int about being from Xorg.
So I created the /etc/X11/xserver directory, and copied this file there.
The next odd thing was a mess o warnings about not having a /dev/wacom.
Apparently, wacom is a type of tablet.
I don't have one.
So I deleted all references to any type of wacom InputDevice
and deleted references to stylus, cursor and eraser
in the ServerLayout section.
I thought this worked for a bit.
I'm pretty sure I logged out once sucessfully.
But that was from a boot where gdm failed.
I fixed xorg.conf, started gdm, and was able to log out.
However, after a reboot, when gdm starts in the init scripts, things broke again.
--Aaron 11:02, 13 Sep 2006 (MDT)
I have uninstalled gdm, and gotten similar lockups, so it may not be a gdm issue.
I believe that in the past, I did a kill -TERM to the
X server, and the system locked.
Just now, I was able to kill -9 the X server, and it
just logged me out and returned to the gdm login page.
I wonder if that gives anybody a hint about the problem.
More Miscillaneous Tools
Before my next reboot to test the robustness of autofs, install more miscellaneous tools.
apt-get install encfs openssh-server nmap traceroute
Tested that sshd is working, so I can try to recover from future freezes by a remote login, if necessary...
reboot...
Blender
Had been running for a while, and I wanted to try Blender. It don't work. Text on buttons does not display right. It dies when I hit some (unknown) buttons, and leaves zombies. I re-build from source... same problems.
