hifn 795x module doesn't exist on a 32bit system

[Koen Hendrix]

kernel 3.5.0-19-generic #30-Ubuntu SMP

LSB Version: core-2.0-ia32:core-2.0-noarch:core-3.0-ia32:core-3.0-noarch:core-3.1-ia32:core-3.1-noarch:core-3.2-ia32:core-3.2-noarch:core-4.0-ia32:core-4.0-noarch
Distributor ID: Ubuntu
Description: Ubuntu 12.10
Release: 12.10
Codename: quantal

my Hifn 7955 crypto accelerator doesn't get used anymore. it's a PCI-card; dmesg doesn't report it, lspci says it's still there:

02:08.0 Co-processor: Hifn Inc. 7955 Security Processor
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 32, Cache Line Size: 32 bytes
 Interrupt: pin A routed to IRQ 7
 Region 0: Memory at f412a000 (32-bit, non-prefetchable) [size=4K]
 Region 1: Memory at f4128000 (32-bit, non-prefetchable) [size=8K]
 Region 2: Memory at f4120000 (32-bit, non-prefetchable) [size=32K]

in the past, there was the hifn_795x.ko module; that module gave problems on 64bit systems. anyway, on a 32bit system, it seems the module doesn't get compiled anymore...

ref. bug #692999 from december 2010

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: linux-image-3.5.0-19-generic 3.5.0-19.30
ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7
Uname: Linux 3.5.0-19-generic i686
ApportVersion: 2.6.1-0ubuntu7
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: koen 1548 F.... xfce4-volumed
                      koen 1567 F.... pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Date: Fri Nov 30 17:07:13 2012
HibernationDevice: RESUME=UUID=4b501d2f-1fab-47fc-b093-542d5612b69f
InstallationDate: Installed on 2012-11-29 (0 days ago)
InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.1)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: Shuttle Inc SB77V10
MarkForUpload: True
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-19-generic root=UUID=e840ce01-edcc-4089-a997-df724413a49b ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-19-generic N/A
 linux-backports-modules-3.5.0-19-generic N/A
 linux-firmware 1.95
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/07/2005
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: FB77V10
dmi.board.vendor: Shuttle Inc
dmi.chassis.type: 3
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd09/07/2005:svnShuttleInc:pnSB77V10:pvr:rvnShuttleInc:rnFB77V10:rvr:cvn:ct3:cvr:
dmi.product.name: SB77V10
dmi.sys.vendor: Shuttle Inc

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

The options for this device were removed from the kernel config file in Quantal and also in Raring. The options exist in Precise:

CONFIG_CRYPTO_DEV_HIFN_795X=m
CONFIG_CRYPTO_DEV_HIFN_795X_RNG=y

We may be able to re-enable them.

[Joseph Salisbury (jsalisbury)]

I built a Raring test kernel with these options enabled. The kernel can be downloaded from:

http://people.canonical.com/~jsalisbury/lp1085115/

Can you test that kernel and report back if it fixes the bug? Note that you will need to install both the linux-image and linux-image-extra packages.

[Koen Hendrix (koen-hendrix)]

thanks for the build! alas...

$ cat /var/log/dpkg.log|grep "status installed"
2012-12-01 11:16:21 status installed linux-image-3.7.0-4-generic:i386 3.7.0-4.12~lp1085115v1
2012-12-01 11:29:08 status installed linux-headers-3.7.0-4:all 3.7.0-4.12~lp1085115v1
2012-12-01 11:33:14 status installed linux-image-extra-3.7.0-4-generic:i386 3.7.0-4.12~lp1085115v1
2012-12-01 11:37:36 status installed linux-image-extra-3.7.0-4-generic:i386 3.7.0-4.12~lp1085115v1
2012-12-01 11:38:11 status installed linux-headers-3.7.0-4-generic:i386 3.7.0-4.12~lp1085115v1
(image-extra was installed twice, due to software center's slow gui)

$ grep -E 'Crypto|crypto|Hifn|hifn' /var/log/boot.log
(nothing)

$ sudo dmesg>dmesg.log && grep -E 'Crypto|crypto|Hifn|hifn' dmesg.log
(nothing)

$ sudo lspci|grep Hifn
02:08.0 Co-processor: Hifn Inc. 7955 Security Processor

$ ls /lib/modules/3.7.0-4-generic/kernel/drivers/crypto/
total 48
drwxr-xr-x 2 root root 4096 Dec 1 11:36 .
drwxr-xr-x 70 root root 4096 Dec 1 11:32 ..
-rw-r--r-- 1 root root 10876 Nov 30 22:31 geode-aes.ko
-rw-r--r-- 1 root root 11668 Nov 30 22:31 padlock-aes.ko
-rw-r--r-- 1 root root 12748 Nov 30 22:31 padlock-sha.ko

$ sudo find /lib/modules/3.7.0-4-generic/ -type f -follow -name '*795x*'
(nothing)

$ sudo find /lib/modules/3.7.0-4-generic/ -type f -follow -name '*hifn*'
(nothing)

anything else i can try?

[Koen Hendrix (koen-hendrix)]

i forgot:

$ sudo uname -a
Linux iugo 3.7.0-4-generic #12~lp1085115v1 SMP Fri Nov 30 20:57:19 UTC 2012 i686 i686 i686 GNU/Linux

i did boot the new kernel.

[Joseph Salisbury (jsalisbury)]

hifn_795x has a dependency on HIGHMEM64G not being set. This config option allows you to have a 32-bit processor and more than 4G's of RAM. In Precise, this is the main difference between the PAE and Non-PAE kernels.

In Quantal the i386 non-pae flavor has been eliminated. The generic-pae flavor has become the generic flavor, and thus HIGHMEM64G=y which then has a trickle down affect of preventing hifn_795x from being enabled.

We cannot disable HIGHMEM64G, thus hifn_795x won't be enabled due to it's dependency chain of !ARCH_DMA_ADDR_T_64BIT.

[penalvch (penalvch)]

As per https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1085115/comments/7 -> Won't Fix for Trusty.

Joseph Salisbury, it appears there are at least two separate issues here:
1) The Hifn 7955 crypto accelerator doesn't have PAE/amd64 driver support. As I'm not sure, ould you know the maintainer for this?

2) if Koen Hendrix wanted to utilize a non-PAE/amd64 kernel in a Quantal+ release, wouldn't all that needs to occur is just adjust the appropriate config flags and rebuild the kernel via https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel ?