![]() |
|
|
#1 | |
|
Registered User
Join Date: Mar 2006
Posts: 260
|
Ok time I also report a problem
![]() Using the 100.14.09 drivers I can no longer change to another VT while the nvidia driver is loaded. Pressing ctrl+alt+f1 etc while on X results in black screen and the monitors entering standby mode. I can switch back to X just fine though. Also in shutdown after X is killed I see nothing, again screens are black and they enter standby mode. This doesn't happen with 9755 drivers or beta 100x drivers. This doesn't change if I remove any boot option, totally new to these drivers. Please find attached the bug report. |
|
|
|
|
|
|
#2 |
|
Registered User
Join Date: Aug 2006
Posts: 66
|
Strange. I had this problem with previous beta drivers, 100.14.09 solved it for me.
|
|
|
|
| Sponsored Links - Guests Only | ||
|
|
|
|
#3 | |
|
Registered User
Join Date: May 2007
Posts: 56
|
Quote:
|
|
|
|
|
|
|
#4 | |
|
Registered User
Join Date: Mar 2006
Posts: 260
|
Quote:
Guess what fixed it for you broke it for me ![]() Hope when they solve it for me doesn't break it for you again ![]() |
|
|
|
|
|
|
#5 |
|
NVIDIA Corporation
Join Date: Aug 2002
Posts: 3,541
|
@gbil: there's a known regression with VESA console interaction that was introduced between 100.14.06 and 100.14.09; if you're using a VESA console, I'd recommend using a standard VGA one for now. This should work better again in future drivers, though only VGA is presently fully supported.
|
|
|
|
|
|
#6 | |
|
Registered User
Join Date: Mar 2006
Posts: 260
|
Quote:
|
|
|
|
|
|
|
#7 |
|
Registered User
Join Date: Feb 2007
Posts: 9
|
I have this problem as well, the suggested solution means again huge letters in the console
Please fix this. |
|
|
|
|
|
#8 | |
|
Registered User
Join Date: Feb 2006
Posts: 1
|
Quote:
I had exactly the same problem. In my case it appears with nvidia drivers 9xxxx but it is still present with 100.14.09 drivers: the virtual consoles are there but there is not video signal sent to the screen, and you can switch between X and virtual consoles without problem (and there is no problem accessing virtual consoles using the nv driver, the problem only appears when using nvidia driver). (I have it with Ubuntu 7.04 and with Kubuntu 7.04 (same machine)) I solved it modifying my boot options, adding "vga=792". Now my /boot/grub/menu.lst has the following line: Code:
kernel /boot/vmlinuz-2.6.20-16-generic root=UUID=9924d035-b141-4e2b-922 a-013cf2c1cddd ro quiet splash vga=792 Linux framebuffer super mini howto) Now I can access my virtual consoles even when I am using the nvidia driver under Ubuntu 7.04. I hope this helps you. Regards |
|
|
|
|
|
|
#9 |
|
Registered User
Join Date: Aug 2006
Posts: 66
|
To those of you with working FB-consoles: Are any of you using tvout or running multiple screens?
I am, and this is the result: http://fredrik.obra.se/corruption.jpg ![]() |
|
|
|
|
|
#10 |
|
Registered User
Join Date: Mar 2006
Posts: 260
|
My console switching problem solved with 100.14.11 drivers.
|
|
|
|
|
|
#11 |
|
Registered User
Join Date: Jun 2007
Posts: 10
|
The problem remains even after upgrade to 100.14.11. I log into KDE, run another session, switch back, switch to the new session - and all I can do is to press the RESET button
![]() |
|
|
|
|
|
#12 | |
|
Registered User
Join Date: Mar 2006
Posts: 260
|
Quote:
|
|
|
|
|
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
|
|