[SOLVED] Download previous versions of 32 bit kernel

TarFile · 03-17-2019, 10:54 AM

Since 4.19.29 is no longer able to build the Legacy GPU version (304.xx series): 304.137. Is there some where to download the previous kernels to find the last one that will work.

I have one 32 bit PC that I use for assorted archival tasks and the latest kernels don't support Nvidia Legacy drivers anymore.

ponce · 03-17-2019, 11:05 AM

Hi TarFile,

I'm not sure what's happening there (can you post the errors somewhere like pastebin.com?), but FYI I just built nvidia-legacy304-kernel-304.137_4.19.29_smp-x86-1ponce.txz on the latest slackware-current, using the repository linked here.

orbea · 03-17-2019, 11:15 AM

Quote:

Originally Posted by TarFile

Since 4.19.29 is no longer able to build the Legacy GPU version (304.xx series): 304.137. Is there some where to download the previous kernels to find the last one that will work.

I have one 32 bit PC that I use for assorted archival tasks and the latest kernels don't support Nvidia Legacy drivers anymore.

What GPU do you have? Have you considered trying nouveau? They may support legacy nivida cards better than the legacy nvidia drivers do and depending on your use case it may work fine.

TarFile · 03-17-2019, 12:11 PM

Well the Nouveau driver lets X start but Firefox won't work.

I think it's a 7500GT.

orbea · 03-17-2019, 12:56 PM

If you start firefox from a terminal what does it print? It would be surprising for firefox to not work with nouveau. The nvidia drivers overwrite various system libraries so is it possible it failed because of missing libraries from a removed nvidia driver?

cwizardone · 03-17-2019, 01:10 PM

When you removed the Nvidia driver it gives you the option to restore any files it changed.

orbea · 03-17-2019, 01:12 PM

Quote:

Originally Posted by cwizardone

When you removed the Nvidia driver it gives you the option to restore any files it changed.

It would not be the first time someone has messed this up.

rkfb · 03-17-2019, 01:39 PM

Quote:

Originally Posted by TarFile

Well the Nouveau driver lets X start but Firefox won't work.

I think it's a 7500GT.

Code:

lspci | grep NVIDIA

as root may help.

TarFile · 03-17-2019, 01:41 PM

orbea it just dies no message.

Ponce how exactly did you download and build from the current slackbuilds repo. I have never really understood how you are supposed to use that. I usually just grab the slackbuild there and whatever else I need and get the source then run the slackbuild.

I tried to use sbopkg set to use current but it gets the wrong 304.131 not the 304.137.

Do I need to clone or download it to use it correctly?

jmccue · 03-17-2019, 01:46 PM

TarFilem

I feel your pain, 304 is 'dead' as far as Nvidia is concerned,like you nouveau had issues on my machine. I ended up getting cheap non-nvidia card, if you are on a desktop that may be an option.

But sometime after Feb 1, someone posted a patch to get the 304 package working, I tried without any luck finding it. Maybe you will have will have better luck

TarFile · 03-17-2019, 01:54 PM

Well as I said this box is for legacy archival use mostly. It is the only box I have left that can use a 5 1/4 floppy drive. I have quite a few really old games on those old disks and am in the middle of trying to get them all on USB drives and working in DosBox among other things. I guess even Linux is about ready to give up on 32 bit

Still a lot of Steam games require 32 bit compatibility to run. Of course most of them seem to use DosBox these days

jmccue · 03-17-2019, 02:03 PM

Quote:

Originally Posted by TarFile

I guess even Linux is about ready to give up on 32 bit

One would think so, but there was a recent article in LWN stating there is a lot of work on the kernel and glib to get it ready for 2038, so that tells me 32bit Linux is still here for quite a while.

Anyway, for your issue, how about doing a complete reset on Firefox (ie: delete your current profile and create a new one) along with clearing out all cookies/cache/etc. Remember to backup you bookmarks.

Nille_kungen · 03-17-2019, 02:17 PM

Quote:

Originally Posted by TarFile

orbea it just dies no message.

Ponce how exactly did you download and build from the current slackbuilds repo. I have never really understood how you are supposed to use that. I usually just grab the slackbuild there and whatever else I need and get the source then run the slackbuild.

I tried to use sbopkg set to use current but it gets the wrong 304.131 not the 304.137.

Do I need to clone or download it to use it correctly?

I'm not sure he used SBo he might have used his own SlackBuilds that is linked in the first post if you followed the link he posted.
If you look at the tag of the package name he posted you will see the ponce tag.

ponce · 03-17-2019, 02:26 PM

Quote:

Originally Posted by TarFile

Ponce how exactly did you download and build from the current slackbuilds repo. I have never really understood how you are supposed to use that. I usually just grab the slackbuild there and whatever else I need and get the source then run the slackbuild.

I tried to use sbopkg set to use current but it gets the wrong 304.131 not the 304.137.

Do I need to clone or download it to use it correctly?

if you look at the first post of the topic I linked you it contains a link to instructions on how to use it with sbopkg: be extra careful about the sync procedure described there, I think the reason why you get an older version is because you are not syncing the repository correctly.

you can also clone it using "git clone" (also that is explained).

if you prefer you can also navigate and download single files, but IMHO could be a little painful if you have to do it often

http://cgit.ponce.cc/slackbuilds/tre...gacy304-kernel

TarFile · 03-17-2019, 03:29 PM

Ponce, you were correct about syncing the repository. I did follow the instructions the first time but something went amiss for some reason. Trying a rebuild right now.