The module overrides are in place since 7.10. Closing the bug.
** Changed in: linux-restricted-modules-2.6.22 (Ubuntu)
Sourcepackagename: linux-restricted-modules-2.6.20 =>
linux-restricted-modules-2.6.22
Status: In Progress => Fix Released
--
Please ship proper modaliases for nvidia, fg
Very interesting perhaps:
[EMAIL PROTECTED]:~$ gksudo "restricted-manager -l"
X Error: BadDevice, invalid or uninitialized input device 167
Major opcode: 144
Minor opcode: 3
Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 167
Major opcode
I have an nVidia GeForce FX 5200 and have the same problem with feisty.
[EMAIL PROTECTED]:~$ sudo -H lspci -vvn
Password:
00:00.0 0600: 1106:3205
Subsystem: 1043:80f9
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap+
Same Here on a GeForce GO 6600
The results of lspci -n | grep 0300 is:
01:00.0 0300: 10de:0148 (rev a2)
--
Please ship proper modaliases for nvidia, fglrx & co
https://bugs.launchpad.net/bugs/93209
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug cont
I have a similar issue on Feisty AMD64. When the nvidia-glx package is
installed and activated, restricted drivers manager is aware of it. When
it is not installed, it does not detect that I have a Nvidia card that
can use binary drivers.
lspci lists my card as:
VGA compatible controller: nVidia C
I have a similar issue on Feisty AMD64. When the nvidia-glx package is
installed and activated, restricted drivers manager is aware of it. When
it is not installed, it does not detect that I have a Nvidia card that
can use binary drivers.
lspci lists my card as:
VGA compatible controller: nVidia C
New l-r-m does ship modaliases which restricted-manager can use. Thanks,
Ben!
However, this bug should be kept open for Feisty+1, where the package
should be changed to actually override the modaliases, so that they work
not just with restricted-manager. Removing the milestone for that.
** Change
Same here,
lspci -n | grep 300
00:05.0 0300: 10de:0247 (rev a2)
--
Please ship proper modaliases for nvidia, fglrx & co
https://bugs.launchpad.net/bugs/93209
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
Same for me GeForce4 (NV17) MX440
The results of lspci -n | grep 0300 is:
01:00.0 0300: 10de:0181 (rev a2)
Anders
--
Please ship proper modaliases for nvidia, fglrx & co
https://bugs.launchpad.net/bugs/93209
You received this bug notification because you are a member of Ubuntu
Bugs, which is th
Same for my GeForce FX Go5600:
01:00.0 0300: 10de:031a (rev a1)
Thanks!
--
Please ship proper modaliases for nvidia, fglrx & co
https://bugs.launchpad.net/bugs/93209
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
I'm running restricted-manager 0.18 and it seems that my Nvidia Go 6600
isn't showing up either.
The results of lspci -n | grep 0300 is:
01:00.0 0300: 10de:0146 (rev a2)
Matt
--
Please ship proper modaliases for nvidia, fglrx & co
https://bugs.launchpad.net/bugs/93209
You received this bug not
This affects a lot of people, bumping severity. Ben, can this patch be
applied for Feisty? Otherwise I have to write a per-architecture
solution in restricted-manager, which is pretty ugly.
** Changed in: linux-restricted-modules-2.6.20 (Ubuntu)
Importance: Medium => High
--
Please ship prope
** Changed in: linux-restricted-modules-2.6.20 (Ubuntu)
Target: None => ubuntu-7.04
--
Please ship proper modaliases for nvidia, fglrx & co
https://bugs.launchpad.net/bugs/93209
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Loic,
I am writing this from yesterday 3/30 daily build cd for feisty but when i try
to open restricted-manager it says "no restricted drivers needed" or something
very similar to that. Off of my HD install restricted-manger opens because i
have vmware modules installed... and the nvidia card i
I also have the same chipset (geforce4 go 440) on a Dell Inspiron 8200,
and it's detected by restricted-manager who proposes nvidia-legacy (only
7xxx, that has a bug on my system, but that's another bug report).
Could you check by booting a recent daily desktop live CD if the problem
still exist f
i have a geforce4 go 440... would you like dev ids from my card as well?
updated restricted-manager to 0.17 today to no avail... still no nvidia in
manager , and issuing it it xorg.cobf x refuses to start: no screens found
when i first installed the beta restricted-manager worked and correct
** Summary changed:
- Fails to detect Nvidia 3D driver
+ Please ship proper modaliases for nvidia, fglrx & co
--
Please ship proper modaliases for nvidia, fglrx & co
https://launchpad.net/bugs/93209
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listi
17 matches
Mail list logo
