[Fwd: Re: [ale] SuSE 81 review, kinda...]

[Ray Knight]

Need to remember to respond from the correct account.



-- BEGIN included message

To: ale at ale.org
Subject: Re: [ale] SuSE 81 review, kinda...
From: Ray Knight <audilvr at speakeasy.org>
To: ale at ale.org
Date: 23 Jan 2003 19:21:11 -0500
In-Reply-To: <3E300E96.9070409 at 3times25.net>
References: <3E300E96.9070409 at 3times25.net>

On Thu, 2003-01-23 at 10:47, Geoffrey wrote:
> I've got to say, I've been playing with SuSE 8.1 lately.  It is quite 
> sweet.  I picked up the Personal version and installed it on 5 machines. 
>   I've since picked up the Professional and am currently installing it 
> on another.  So far it's been pretty flawless.  Two problems I have run 
> into:
> 
> 1. When installing on a box with an older trident card, I could never 
> get X to work.  This happened with Mandrake 9.0 as well.  Doing a bit of 
> research, I found a link off the XFree86 site referencing another driver 
> and noting that xfree 4.2 has problems with some trident chipsets.  That 
> driver works like a charm on two different trident cards I previously 
> could not get working.
> 
> 2.  When installing on a box with an S3 trio3d card, SuSE 8.1 Personal 
> set the driver to "Vesa".  I don't know if that was intentional but 
> again, reviewing the XFree docs, they say that chip requires the S3virge 
> driver. Once I made this change, that box is working like a charm.
> 
> Waiting to see if my IEEE-1394 (firewire) card is recognized. ;)
> 
> -- 
> Until later: Geoffrey		esoteric at 3times25.net
> 
> The latest, most widespread virus?  Microsoft end user agreement.
> Think about it...
> 
I bought SuSE 8.1 Professional this past weekend to update a system
running 8.0.  It originally had SuSE 7.1 and was updated to 7.3 and then
8.0   The 8.0 to 8.1 update failed with numerous (>80) rpms failing to
install.  The log doesn't give any details, just says failed, followed
by a blank line.  So I tried doing a fresh install, just saving my /home
directory which has it's own partition.  Still have rpms that fail to
install with no details in the log.  So I think perhaps my CDROM drive
is announcing imminent failure.  Tried 2 other CDROM drives with
identical results.  Trying to install some of the failed rpms from the
command line results in:  Segmentation fault.  I ran the memory tester
overnight with no failures.  Anyone have a clue what I should try next? 
Do I perhaps have defective CDROM disks?

Ray



-- END included message