Saturday, November 04, 2006

Ubuntu - Installation

I installed Ubuntu 6.10 on the old computer yesterday. Pentium III 667Mhz, 128 RAM with a 3dfx Voodoo graphic card and Soundblaster-I-forgot-the-model sound card. Dual-boot with Windows by the way. I encountered the paradise of problems - GDM, gnome and X server. I did this, did that, got nowhere, created new problems and the list goes on. So I reinstalled Ubuntu again today. And here goes the log:

1. No problems during installation. I had to use the text-mode installation method using the alternate-iso-cd because the other live-desktop-whatever-it-is-called-i386 iso needs 192 MB RAM.

2. Rebooted after installation. Arrived at login screen of gdm. Entered username and password. Gnome started. Halfway-through the startup, the login screen appeared again. Entered username and password. Gnome started, this time without a problem. But why do THREE Nautilus windows have to be started??

3. Update package manager popped up a screen with 2 new updates; imagemagick (I think) and something else. Updates completed without problem.

4. Checked .xsession-errors. Had to edit xorg.conf to:
a. remove all entries which had anything to do with wacom, stylus, cursor and can't-remember (something to do with tablet pc)
b. edit the Font paths in which 'X11' and 'fonts' were in reversed position

5. Checked all the other log files: Xorg.0.log, dmesg, faillog, ... no apparent errors.

6. Ran gdmsetup. Made sure 'Accessible login' was not enabled. Read somewhere that enabling this can cause some kind of errors.

7. Edited startup programs. Later saw some error messages which said that the autostart file cannot be edited. Have to check to see if ~/.config/autostart is under root.

8. Rebooted again. Say hello to 'PROBLEMS'.

7. Login screen keeps on appearing after I have entered username and password for Gnome Session.

8. Nautilus and nothing else pop up after logging into Gnome Failsave. Couldn't even find a way to bring up a terminal. I think I got an error message about Gnome Settings Daemon and dbus.

9. Login into Terminal Failsave successful but there was no detectable error messages.

10. Decided to call it a night.


No comments: