iwl4965 wireless driver

[edeplus]

Why is the iwl4965 wireless driver not longer available in the kernel-7.x.x series?

[swissluxtom]

Why is the iwl4965 wireless driver not longer available in the kernel-7.x.x series?

I think there is a newer intel driver, according Google AI:

CONFIG_IWLWIFI is the modern, unified driver architecture for Intel Wireless WiFi Link cards, whereas CONFIG_IWL4965 is a legacy driver specifically built for the older Intel Wireless WiFi Link 4965AGN card.When configuring a modern Linux kernel, CONFIG_IWLWIFI serves as the primary master option for almost all Intel wireless cards, while CONFIG_IWL4965 has largely been deprecated or integrated into legacy sub-options depending on your kernel version

But I don't know if a microcode firmware file is required and included.
+UPDATE+ seems the 4965 chip is not supported by the new driver; but it requires CONFIG_IWLEGACY and CONFIG_IWL4965, which have been removed in latest Porteus config.

[edeplus]

First they come for the i386s, I did not speak out as I was using the Pentiums.
Then they come for the i486s, and I did not speak out as I was using Dual Cores.
Then they come for the legacy drivers, and there is no-one left to speak for me.

New Quote: "Linux cannot runs on everything"

[swissluxtom]

in this case, I think it was removed in Porteus just to keep ISO smaller. Other distros (I think like PorteuX-64 derivate) have it active. In my opinion almost all working drivers should be active in the kernel config for compiling, but then a subset of drivers provided in the default ISO. All other drivers (+microcode-firmware) should be a XZM module to download separately.

[edeplus]

In my opinion almost all working drivers should be active in the kernel config for compiling, but then a subset of drivers provided in the default ISO. All other drivers (+microcode-firmware) should be a XZM module to download separately.

I couldn't agree with you more. I have separated the kernel-7.0.9-porteus into 000-kernel.xzm and 000-firmware.xzm.
They take 25MB and 203MB respectively. Now, if only the portues kernel maintainer would run with the idea.

My point about supporting older hardware is still valid. On one of my machines, PorteuX gives:
"Fatal glibc error: CPU does not support x86-64-v2.

[Ed_P]

On one of my machines, PorteuX gives:
"Fatal glibc error: CPU does not support x86-64-v2.

Try one of these 486, 586 systems: https://mirror.yandex.ru/mirrors/porteus/

In my opinion almost all working drivers should be active in the kernel config for compiling, but then a subset of drivers provided in the default ISO. All other drivers (+microcode-firmware) should be a XZM module to download separately.

I like this idea also.

[edeplus]

Try one of these 486, 586 systems: https://mirror.yandex.ru/mirrors/porteus/

Thanks for the helpful suggestion.

The error "Fatal glibc errorL CPU does not support x86064-v2" simply says that
the glibc is compiled for the x86-64-v2 CPU level.

This is NOT a Porteus issue, but a PorteuX one. The machine in question has a
"Intel(R) Core(TM)2 Duo CPU T8100 @ 2.10GHz" capable of 64 bits. But in the
relentess drive towards modernity, PorteuX has left this CPU behind.

[edeplus]

Other distros (I think like PorteuX-64 derivate) have it active.

Thanks for pointing this out, and I can confirm it. Porteus-V5.1 works fine
with PorteuX kernel-7.2.0 (iwl4965 wireless driver enabled.)