Mailinglist Archive: opensuse (3261 mails)

[b stephen harding <big-lime@xxxxxxxx>]

On Monday 23 April 2001 22:51, you wrote:
> crrey wrote:
> > Yep. make config, make dep, make clean, make bzImage (or bzlilo), make
> > modules, make modules_install, make install, a few cp commands, run lilo,
> > and viola!  And RPM's, thought those were supposed to take care of that
> > stuff. At least vendor specific rpms into the same vendor specific
> > distro/version.  But, heck what do I know, I'm a newbie!
>
> A blind make config or whatever your are doing will not get you a
> working kernel. Just try to get one of those mobos with VIA chipset to
> work and you are for a sad reality.
>
> There is more to updating kernel RPMs that installing them, it's all
> documented in the Suse web site and posted here by me.
>
> What did you do and what error messages did you get?

Not sure what you are talking about.  I've got one of those VIA Mobo's and 
I've just finished doing a kernel compile of 2.4.2 with success and you 
can't get much more of a novice then me.

I'm running:
AMD K6III 450
256Mb ram
DFI Mobo with Via chipset
Promise Ultra66 IDE Controller
HDD 20.00 Fujitsu Picobird
HDD 27.2 IBM Deskstar
Sblive
Geforce 2 MX

This was not my first kernel compile though, maybe me 20th (not all 
successful).

Honestly I'm not sure what some of you are complaining about with the support 
thing.  Seems clear to me what SuSE covers in there support agreement.  If 
you want to upgrade to something not supplied in the orginal package that is 
your responsibility.

All my dealings with SuSE support have been satisfactory in the replies and 
fixes.  They could have been a bit more timely though.  LOL, the list most 
times provides the solutions first.  Well most times anyways, when my posts 
don't get ignored. :-)