restricted-manager 0.23 doesn't recognise my laptop's nvidia card.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
restricted-manager (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: restricted-manager
I have a compaq v3000z with an nvidia 6150 [C51] video card that restricted-modules doesn't seem to think is an nvidia card. Info about my card:
$ lspci -nvv -s 00:05.0
00:05.0 0300: 10de:0244 (rev a2) (prog-if 00 [VGA])
Subsystem: 103c:30b5
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Interrupt: pin A routed to IRQ 21
Region 0: Memory at c2000000 (32-bit, non-prefetchable) [size=16M]
Region 1: Memory at d0000000 (64-bit, prefetchable) [size=256M]
Region 3: Memory at c1000000 (64-bit, non-prefetchable) [size=16M]
[virtual] Expansion ROM at 50000000 [disabled] [size=128K]
$ cat /sys/devices/
pci:v000010DEd0
but searching for the first part of that string in the *.restricted file proves fruitless:
$ cat /var/cache/
$
Looking at /var/cache/
$ modinfo nvidia | grep alias:
alias: char-major-195-*
alias: pci:v000010DEd*
alias: pci:v000010DEd*
$
$ dpkg --list "*restricted*"
ii linux-restrict 2.6.20.5-15.20 Non-free Linux 2.6.20 modules on x86/x86_64
ii linux-restrict 2.6.20.5-16.28 Non-free Linux 2.6.20 modules on x86/x86_64
ii linux-restrict 2.6.22.1-6.8 Non-free Linux 2.6.22 modules on x86/x86_64
ii linux-restrict 2.6.22.2-7.2 Non-free Linux 2.6.22 modules on x86/x86_64
ii linux-restrict 2.6.22.2-8.4 Non-free Linux 2.6.22 modules on x86/x86_64
ii linux-restrict 2.6.22.2-8.4 Non-free Linux 2.6.22 modules helper script
ii linux-restrict 2.6.22.8.8 Restricted Linux modules for generic kernels
ii restricted-man 0.23 manage non-free hardware drivers
ii ubuntu-restric 9 Commonly used restricted packages
Not sure who controls the *.restricted file, so I'm filing under rstricted-manager for now. Please move to linux-restricte
(This sounds like a "duplicate" of Bug 93209 )