Ubuntu
ndiswrapper package

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

Bug #1274829 reported by Cscaorg on 2014-01-31

This bug report is a duplicate of: Bug #1090196: ndiswrapper-dkms 1.57-1ubuntu1: ndiswrapper kernel module failed to build [Cannot find kernel build files in ... Please give the path to kernel build directory with the KBUILD=<path> argument to make]. Edit Remove

This bug affects 1 person

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

Bug Description

Wish i could be of more assistance. using realtek rtl8180u i think, not sure if this matters.

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: ndiswrapper-dkms 1.57-1ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-35.50~precise1-generic 3.8.13.13
Uname: Linux 3.8.0-35-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
DKMSKernelVersion: 3.8.0-35-generic
Date: Fri Jan 31 03:41:20 2014
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.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

Cscaorg (cscaorg) wrote on 2014-01-31:

DKMSBuildLog.txt Edit (298 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (826 bytes, text/plain; charset="utf-8")
DuplicateSignature.txt Edit (270 bytes, text/plain; charset="utf-8")

Apport retracing service (apport) on 2014-01-31

tags:

removed: need-duplicate-check

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2014-02-03:

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 1090196, 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.