[SOLVED] Using slackware 3.2 kernel package from current on 13.37

Phorize · 02-06-2012, 03:09 AM

Hi can't see any obvious reason why doing the above would cause any issues if the hardware on the machine was known to run well with the 3.2 kernel-what do we think?

willysr · 02-06-2012, 03:21 AM

AFAIK, the 3.2 kernel was built against different toolchain used in 13.37, so it caused some incompatibilities between these two systems..

If you would like to use 3.2 in 13.37, i guess it's better to use the config file from -Current to compile your own kernel that are based on 13.37

Phorize · 02-06-2012, 03:47 AM

Quote:

Originally Posted by willysr

AFAIK, the 3.2 kernel was built against different toolchain used in 13.37, so it caused some incompatibilities between these two systems..

If you would like to use 3.2 in 13.37, i guess it's better to use the config file from -Current to compile your own kernel that are based on 13.37

Thanks, I do what you suggest.

Petri Kaukasoina · 02-06-2012, 03:55 AM

Quote:

Originally Posted by kristizz

Hi can't see any obvious reason why doing the above would cause any issues if the hardware on the machine was known to run well with the 3.2 kernel-what do we think?

It will be ok. (Unless you need to install an nvidia proprietary driver. It could complain that the gcc version is wrong.)

But lilo will give this error:

Code:

Fatal: Setup length exceeds 31 maximum; kernel setup will overwrite boot loader

It's because the kernel has grown so large. You can fix it by installing a fixed lilo from slackware-current, too.

Phorize · 02-06-2012, 04:01 AM

Quote:

Originally Posted by Petri Kaukasoina

It will be ok. (Unless you need to install an nvidia proprietary driver. It could complain that the gcc version is wrong.)

But lilo will give this error:

Code:

Fatal: Setup length exceeds 31 maximum; kernel setup will overwrite boot loader

It's because the kernel has grown so large. You can fix it by installing a fixed lilo from slackware-current, too.

Thanks. I think that adding large-memory to lilo.conf would also address that.