Ubuntu
ndiswrapper package

ndiswrapper-dkms failed to build and crashes to load on kernel 3.5.0-18 ubuntu 12.04

Bug #1074826 reported by Inox on 2012-11-04

This bug report is a duplicate of: Bug #1023645: ndiswrapper-dkms 1.57-1ubuntu1: ndiswrapper kernel module failed to build [error: ‘struct kernel_stat’ has no member named ‘cpustat’]. Edit Remove

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	ndiswrapper (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

After upgrade to 3.5.0-18 from 3.2.0-* kernel branch ndiswrapper stopped working.

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: ndiswrapper-dkms 1.57-1ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-18.29~precise1-generic 3.5.7
Uname: Linux 3.5.0-18-generic i686
ApportVersion: 2.0.1-0ubuntu14
Architecture: i386
DKMSKernelVersion: 3.5.0-18-generic
Date: Sun Nov 4 01:13:13 2012
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
PackageArchitecture: all
PackageVersion: 1.57-1ubuntu1
SourcePackage: ndiswrapper
Title: ndiswrapper-dkms 1.57-1ubuntu1: ndiswrapper kernel module failed to build
UpgradeStatus: Upgraded to precise on 2012-05-08 (179 days ago)

Tags:

Revision history for this message

Inox (inox) wrote on 2012-11-04:

DKMSBuildLog.txt Edit (1.7 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (820 bytes, text/plain; charset="utf-8")
DuplicateSignature.txt Edit (1.7 KiB, text/plain; charset="utf-8")

Apport retracing service (apport) on 2012-11-04

tags:

removed: need-duplicate-check

Revision history for this message

Launchpad Janitor (janitor) wrote on 2012-11-07:

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ndiswrapper (Ubuntu):
status:	New → Confirmed

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2012-11-08:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1023645, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.