Your message dated Thu, 30 May 2013 17:02:51 +0200
with message-id
<ca+7wusyjww0ekwh2ezswwpzta+3_pmih2-rauqm-c4pgqtq...@mail.gmail.com>
and subject line
has caused the Debian Bug report #707783,
regarding FATAL: Error inserting bbswitch
(/lib/modules/3.2.0-0.bpo.4-amd64/updates/dkms/bbswitch.ko): No such device
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
707783: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707783
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bbswitch-dkms
Version: 0.6-2
Severity: normal
I cannot seem to modprobe the bbswitch kernel module:
$ sudo modprobe -v bbswitch
insmod /lib/modules/3.2.0-0.bpo.4-amd64/updates/dkms/bbswitch.ko
FATAL: Error inserting bbswitch
(/lib/modules/3.2.0-0.bpo.4-amd64/updates/dkms/bbswitch.ko): No such device
System is:
$ lspci -vnn | grep '\''[030[02]\]'
00:02.0 VGA compatible controller [0300]: Intel Corporation Sandy Bridge
Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA
controller])
01:00.0 VGA compatible controller [0300]: nVidia Corporation Device [10de:0df5]
(rev a1) (prog-if 00 [VGA controller])
$ sudo modinfo nvidia
filename: /lib/modules/3.2.0-0.bpo.4-amd64/updates/dkms/nvidia.ko
alias: char-major-195-*
version: 295.59
supported: external
license: NVIDIA
alias: pci:v000010DEd00000E00sv*sd*bc04sc80i00*
alias: pci:v000010DEd00000AA3sv*sd*bc0Bsc40i00*
alias: pci:v000010DEd*sv*sd*bc03sc02i00*
alias: pci:v000010DEd*sv*sd*bc03sc00i00*
depends: i2c-core
vermagic: 3.2.0-0.bpo.4-amd64 SMP mod_unload modversions
parm: NVreg_EnableVia4x:int
parm: NVreg_EnableALiAGP:int
parm: NVreg_ReqAGPRate:int
parm: NVreg_EnableAGPSBA:int
parm: NVreg_EnableAGPFW:int
parm: NVreg_Mobile:int
parm: NVreg_ResmanDebugLevel:int
parm: NVreg_RmLogonRC:int
parm: NVreg_ModifyDeviceFiles:int
parm: NVreg_DeviceFileUID:int
parm: NVreg_DeviceFileGID:int
parm: NVreg_DeviceFileMode:int
parm: NVreg_RemapLimit:int
parm: NVreg_UpdateMemoryTypes:int
parm: NVreg_InitializeSystemMemoryAllocations:int
parm: NVreg_UseVBios:int
parm: NVreg_RMEdgeIntrCheck:int
parm: NVreg_UsePageAttributeTable:int
parm: NVreg_EnableMSI:int
parm: NVreg_MapRegistersEarly:int
parm: NVreg_RegisterForACPIEvents:int
parm: NVreg_RegistryDwords:charp
parm: NVreg_RmMsg:charp
parm: NVreg_NvAGP:int
thanks
-- System Information:
Debian Release: 6.0.7
APT prefers oldstable-updates
APT policy: (500, 'oldstable-updates'), (500, 'oldstable'), (500, 'stable'),
(200, 'testing'), (100, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-0.bpo.4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages bbswitch-dkms depends on:
ii dkms 2.2.0.2-1~bpo60+1 Dynamic Kernel Module Support Fram
bbswitch-dkms recommends no packages.
Versions of packages bbswitch-dkms suggests:
ii bumblebee 3.2.1-1 NVIDIA Optimus support for Linux
-- no debconf information
--- End Message ---
--- Begin Message ---
reassign 707783 binutils-gold 2.20.1-16
thanks
The bug was actually in gold:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710023#31
Using the default linker solved the issue, I can now happily use bbswitch.
Thanks.
--- End Message ---
