>
> -----Original Message-----
> From: "Rik Osborne" <[EMAIL PROTECTED]>
> Date: Mon, 20 Sep 1999 18:24:48 -0700
> To: [EMAIL PROTECTED]
> Subject: RedHat 6.0 upgrade difficulties
>> RedHat Linux 6.0 (Hedwig)
>> Kernel 2.0.36 on an i586
>>
>> Now wait a minute... shouldn't that say "Kernel 2.2.5"?
> While you may have wiped your partitions clean, your MBR is still booting
> your old kernel. You'll have to run /sbin/lilo
> You might also edit lilo.conf to make sure your new kernel is the default
> one loaded. That should fix things ;o)
> Mike
Did all that, problem solved, as far as booting goes. From the LILO prompt I
was able to get into bash and run linuxconf, where I figured out how to
disable eth0 at boot time. (Under RH 5.2, I had the eth0 interface
configured to come up at boot. After upgrading to RH 6.0 the whole boot
process would hang at "bringing up interface eth0"). Once that was done, I
was able to boot normally and get to the login screen where I now see:
RedHat Linux 6.0 (Hedwig)
Kernel 2.2.5-22 on an i586
So far, so good. Sadly, I STILL cannot get X to work! Walking through the
various screens in Xconfigurator, I make all my selections identical to what
I selected under RH 5.2. No joy. No matter what choices I make,
Xconfigurator tells me either "There is a problem with your X
configuration..." or "There was an error executing the X server in a probing
mode..."
Here's what I don't understand - why won't the settings that worked
perfectly under RH 5.2 work under 6.0? At the very least, shouldn't "Generic
monitor" work? My monitor is some cheap 14" thing with the name "Shamrock"
on the front, obviously not specifically mentioned in the monitor list. My
system was built for me by a friend, using mostly used components, and I
don't have manuals for most of the components. So I've tried damn near every
monitor listed that's obviously a 14" monitor. The one that works
consistently under 5.2 is "Hyundai DeluxScan 14S" - but not under 6.0.
I'm nearly at the end of my rope with this. I'm beginning to suspect a bug
in either Xconfigurator or the S3 server, but as I'm not a programmer I
wouldn't know where to start trying to track this down.
--
Rik Osborne
<[EMAIL PROTECTED]>
http://www.phase42.net
