blcr-dkms 0.8.2-10: blcr kernel module failed to build
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
blcr (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
$ uname -a
Linux sleepless 2.6.38-13-generic #56~lucid1-Ubuntu SMP Tue Feb 14 03:18:12 UTC 2012 x86_64 GNU/Linux
$ cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 20
model : 2
model name : AMD E-450 APU with Radeon(tm) HD Graphics
stepping : 0
cpu MHz : 825.000
cache size : 512 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 6
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf pni monitor ssse3 cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch ibs skinit wdt arat npt lbrv svm_lock nrip_save pausefilter
bogomips : 3292.97
TLB size : 1024 4K pages
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management: ts ttp tm stc 100mhzsteps hwpstate
...
$ lsb_release -rd
Description: Ubuntu 10.04.4 LTS
Release: 10.04
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: blcr-dkms 0.8.2-10
ProcVersionSign
Uname: Linux 2.6.38-13-generic x86_64
NonfreeKernelMo
Architecture: amd64
DKMSKernelVersion: 2.6.38-13-generic
Date: Thu Mar 8 03:34:26 2012
InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release amd64 (20110720.1)
PackageArchitec
PackageVersion: 0.8.2-10
SourcePackage: blcr
Title: blcr-dkms 0.8.2-10: blcr kernel module failed to build
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 852682, 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.