Well, part of my problems is that the SCSI card drivers and sound card
drivers are not part of the standard linux-mandrake distribution, so I had
to download drivers to work with Mandrake 7.2 out of the box. When I tried
to use the source or binaries from the 2.2.17 based drivers, they didn't
work under 2.4, so at the least I need to recompile them or download new
sources.
One thing that I did notice, was that some of the options that I expected to
be turned "on" by default were turned "off" this time (The last kernel I
compiled was 2.2.16). Things like the VFAT support. make sure you go
through whatever configuration tool you use carefully for differences.
Thanks,
-Kevin
----- Original Message -----
From: "Michael, Steve" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, January 12, 2001 11:20 AM
Subject: RE: [newbie] 2.4 Kernel
> Not to bash the 2.4 upgrade, but it didn't sound like it went all that
well
> for you. I don't think a newbie could have done what you have done, that
> is, without some serious help. Hopefully the upgrades will get better
over
> time.
>
> -----Original Message-----
> From: Kevin Tambascio [mailto:[EMAIL PROTECTED]]
> Sent: Friday, January 12, 2001 9:37 AM
> To: [EMAIL PROTECTED]
> Subject: [newbie] 2.4 Kernel
>
>
> Hi,
>
> Have any of your tried the 2.4 kernel yet? I tried to install and compile
> it last night, and had some success. I was able to reboot into the new
> kernel, but I had some error messages about loading FAT partitions, turned
> out I hadn't built in the VFAT into the kernel or module. I couldn't get
my
> USB scanner (EPSON Perfection 610) working right away, I have to figure
out
> what is happening. I was able to get my scanner working sometimes with
> 2.2.17. My SCSI card needs a new driver (Tekram 315), and I need to d/l a
> 2.4 based Vortex 1 driver. My Ethernet card was not immediately working.
I
> had to reselect in DrakConf that I needed the Tulip driver. After that,
an
> insmod tulip, ifup eth was all I needed to get it working. Other than
those
> things, KDE came up OK, and nothing else unusual was apparent.
>
> Would any other users care to share their experience so far?
>
> -Kevin
>
>
