Ubuntu
ndiswrapper package

ndiswrapper-dkms 1.57-1ubuntu1: ndiswrapper kernel module failed to build

Bug #1103629 reported by Samuel Webb on 2013-01-23

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 1 person

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

Bug Description

My system won't shutdown ever, it crashes on every restart/shutdown. I have tried re-installing Xubuntu 12.10 but same thing happens.

Thanks

sam webb

ProblemType: Package
DistroRelease: Ubuntu 12.10
Package: ndiswrapper-dkms 1.57-1ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2
Uname: Linux 3.5.0-22-generic i686
ApportVersion: 2.6.1-0ubuntu9
Architecture: i386
DKMSKernelVersion: 3.5.0-17-generic
Date: Wed Jan 23 07:58:34 2013
InstallationDate: Installed on 2013-01-23 (0 days ago)
InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.1)
MarkForUpload: True
PackageArchitecture: all
PackageVersion: 1.57-1ubuntu1
SourcePackage: ndiswrapper
Title: ndiswrapper-dkms 1.57-1ubuntu1: ndiswrapper kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Samuel Webb (flashsamuk) wrote on 2013-01-23:

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

Apport retracing service (apport) on 2013-01-23

tags:

removed: need-duplicate-check

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2013-01-24:

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.