Ubuntu
ndiswrapper package

Unable to use driver for Ralkink RT3090

Bug #1151561 reported by Bryian Meenehan on 2013-03-07

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

sudo modprobe ndiswrapper
WARNING: All config files need .conf: /etc/modprobe.d/blacklist.conf.save, it will be ignored in a future release. FATAL: Module ndiswrapper not found.

ProblemType: Package
DistroRelease: Ubuntu 12.10
Package: ndiswrapper-dkms 1.57-1ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-25.39-generic 3.5.7.4
Uname: Linux 3.5.0-25-generic x86_64
ApportVersion: 2.6.1-0ubuntu10
Architecture: amd64
DKMSKernelVersion: 3.5.0-25-generic
Date: Wed Mar 6 13:49:23 2013
InstallationDate: Installed on 2012-03-30 (341 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MarkForUpload: True
PackageArchitecture: all
PackageVersion: 1.57-1ubuntu1
SourcePackage: ndiswrapper
Title: ndiswrapper-dkms 1.57-1ubuntu1: ndiswrapper kernel module failed to build
UpgradeStatus: Upgraded to quantal on 2013-03-04 (2 days ago)

Tags:

Revision history for this message

Bryian Meenehan (bmeenehan) wrote on 2013-03-07:

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-03-07

tags:

removed: need-duplicate-check

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2013-03-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.