[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Sarge on an IBM T20



I've just picked up a magazine with a copy of Sarge (DVD) on the cover.
Since I don't have the bandwidth to get it directly, I thought this
would be great, and started to install.

I've had Woody on the T20 for quite a while (along with Vector,
Mandrake, OS/2 and Win98), but my Woody install had suffered some
damage due to the partitioning software in Mandrake, so I decided to
start from scratch.

First problem I had was the installer. When it attempted to install
Grub, the machine locked up. I have seen this problem with grub-install
in the past, so I decided I'd let it install Lilo and clean up later.
However, when I picked the Lilo option from the installer, it came up
with a long and (to me) fairly meaningless path as to where it was
going to install. And failed. I tried again, using /dev/hda1. But from
this point on, it simply went back to the menu, with the install grub
entry preselected.

After more fiddling around, I was able to boot the base system from my
existing grub installation (never used an initrd before, so I had no
idea of the syntax needed to get it to boot). Having done that, I tooke
the simplest option to get packages installed, intending to fine tune
things afterwards with dselect.

The install hit errors on wwoffle, since the machine is not connected
to anything at present, and has a winmodem which needs to be added
after install. I had some difficulty seeing just what the errors were,
but the main one seemed ot be wwoffle waiting for a connection. 

When X started, I got the opening dialogue from KDE, it started to load
and never did anything else - got as far as 'initialising services' and
sat therre. I killed the xserver and tried Gnome, which complained
about lack of a network connection. said it would not be fully
functional(?), did I want to load it anyway. When I said yes, it put up
the Gnome splash screen and got no further. 

I've now tried multiple installations, but I'm really no forther
forward. And I have not been able to find the errors which are causing
it go die so completely. Console seems to work fine, but I've not been
able to get any more than an emergency xterm to work under X.

Can anyone tell me where to look to locate the error which is causing
this? Or has anyone seen similar problems? Any help would be most
appreciated... I'm using the 2.4 kernel, since I need it for the
winmodem drivers and the Savage xserver module.

paul.

-- 
paulm@waitrose.com
Marwick Computer Services - Chipping Norton, Oxfordshire, UK
OS/2, LAN and general Computer Consultants



Reply to: