dear list,
After a few months of running Arch, I am now fine tuning everything (or at least trying).
I discovered this error message in *kernel.log* file.
NVRM: Your system is not currently configured to drive a VGA console NVRM: on the primary VGA device. The NVIDIA Linux graphics driver NVRM: requires the use of a text-mode VGA console. Use of other console NVRM: drivers including, but not limited to, vesafb, may result in NVRM: corruption and stability problems, and is not supported.
Googling let me to many forum posts about this issue with Nvidia card and driver, but I couldn't find any clear answer.
I have tried all the cited tricks in my *grub* file: -add *vga=0*, or *vga=795* (1208x1024), or *video=visa:off vga=normal* -*GRUB_GFXPAYLOAD_LINUX=console*, *GRUB_GFXPAYLOAD_LINUX=text*, *GRUB_GFXPAYLOAD_LINUX=keep*
and whatever else I couldn't remember, but nothing changed about this message.
As far as I understand, Nvidia does NOT support vesa framebuffer, but only vga. Fine. My system is NOT using VGA console. Fine.
But how do I need ton configure my *grub* file ?
Here are the concerned line from my file :
*GRUB_CMDLINE_LINUX="" GRUB_TERMINAL_INPUT=console GRUB_TERMINAL_OUTPUT=console GRUB_GFXMODE=1280x1024 GRUB_GFXPAYLOAD_LINUX=1280x1024*
Please help as keeping running X like this is not recommanded.
TY.
On 06/26/2012 12:31 PM, Arno Gaboury wrote:
dear list,
After a few months of running Arch, I am now fine tuning everything (or at least trying).
I discovered this error message in *kernel.log* file.
NVRM: Your system is not currently configured to drive a VGA console NVRM: on the primary VGA device. The NVIDIA Linux graphics driver NVRM: requires the use of a text-mode VGA console. Use of other console NVRM: drivers including, but not limited to, vesafb, may result in NVRM: corruption and stability problems, and is not supported.
Googling let me to many forum posts about this issue with Nvidia card and driver, but I couldn't find any clear answer.
I have tried all the cited tricks in my *grub* file: -add *vga=0*, or *vga=795* (1208x1024), or *video=visa:off vga=normal* -*GRUB_GFXPAYLOAD_LINUX=console*, *GRUB_GFXPAYLOAD_LINUX=text*, *GRUB_GFXPAYLOAD_LINUX=keep*
and whatever else I couldn't remember, but nothing changed about this message.
As far as I understand, Nvidia does NOT support vesa framebuffer, but only vga. Fine. My system is NOT using VGA console. Fine.
But how do I need ton configure my *grub* file ?
Here are the concerned line from my file :
*GRUB_CMDLINE_LINUX="" GRUB_TERMINAL_INPUT=console GRUB_TERMINAL_OUTPUT=console GRUB_GFXMODE=1280x1024 GRUB_GFXPAYLOAD_LINUX=1280x1024*
Please help as keeping running X like this is not recommanded.
TY.
Putting GRUB_GFXPAYLOAD_LINUX=text in my default grub, then running a new grub.cfg. Reboot and the message went away, though in the console the text is huge. I have seen no actual "fix" for this and have read that Nvidia is not even sure how or why it broke.
The only other difference is I have GRUB_GFXMODE=1280x1024x32 in mine, but with running text this setting is not used, at least that is my understanding.
On 06/26/2012 09:42 PM, Don deJuan wrote:
On 06/26/2012 12:31 PM, Arno Gaboury wrote:
dear list,
After a few months of running Arch, I am now fine tuning everything (or at least trying).
I discovered this error message in *kernel.log* file.
NVRM: Your system is not currently configured to drive a VGA console NVRM: on the primary VGA device. The NVIDIA Linux graphics driver NVRM: requires the use of a text-mode VGA console. Use of other console NVRM: drivers including, but not limited to, vesafb, may result in NVRM: corruption and stability problems, and is not supported.
Googling let me to many forum posts about this issue with Nvidia card and driver, but I couldn't find any clear answer.
I have tried all the cited tricks in my *grub* file: -add *vga=0*, or *vga=795* (1208x1024), or *video=visa:off vga=normal* -*GRUB_GFXPAYLOAD_LINUX=console*, *GRUB_GFXPAYLOAD_LINUX=text*, *GRUB_GFXPAYLOAD_LINUX=keep*
and whatever else I couldn't remember, but nothing changed about this message.
As far as I understand, Nvidia does NOT support vesa framebuffer, but only vga. Fine. My system is NOT using VGA console. Fine.
But how do I need ton configure my *grub* file ?
Here are the concerned line from my file :
*GRUB_CMDLINE_LINUX="" GRUB_TERMINAL_INPUT=console GRUB_TERMINAL_OUTPUT=console GRUB_GFXMODE=1280x1024 GRUB_GFXPAYLOAD_LINUX=1280x1024*
Please help as keeping running X like this is not recommanded.
TY.
Putting GRUB_GFXPAYLOAD_LINUX=text in my default grub, then running a new grub.cfg. Reboot and the message went away, though in the console the text is huge. I have seen no actual "fix" for this and have read that Nvidia is not even sure how or why it broke.
The only other difference is I have GRUB_GFXMODE=1280x1024x32 in mine, but with running text this setting is not used, at least that is my understanding.
I already tried this too, and yes, you are right. Message has gone, but boot resolution is low. I think I will stick to it until better is found, as I think best is to avoid this message and have low res when booting. Sound more safe. And you are right, difficult to find a clean answer, even from Nvidia.
Putting GRUB_GFXPAYLOAD_LINUX=text in my default grub, then running a new grub.cfg. Reboot and the message went away, though in the console the text is huge. I have seen no actual "fix" for this and have read that Nvidia is not even sure how or why it broke.
If it wasn't huge before then you were either running nouveau or vesa framebuffer on the console and Nvidia in the desktop. This warning is likely due to the fact that running a framebuffer and Nvidia used to crash linux. It can probably? be ignored now.
p.s. video=1600x1200@85 is usually used for nouveau enabled via mkinitcpio
and vga=ask will scan and give a menu of possible vesa modes.
On 06/26/2012 01:19 PM, Kevin Chadwick wrote:
Putting GRUB_GFXPAYLOAD_LINUX=text in my default grub, then running a new grub.cfg. Reboot and the message went away, though in the console the text is huge. I have seen no actual "fix" for this and have read that Nvidia is not even sure how or why it broke.
If it wasn't huge before then you were either running nouveau or vesa framebuffer on the console and Nvidia in the desktop. This warning is likely due to the fact that running a framebuffer and Nvidia used to crash linux. It can probably? be ignored now.
p.s. video=1600x1200@85 is usually used for nouveau enabled via mkinitcpio
and vga=ask will scan and give a menu of possible vesa modes.
I do not touch nouveau drivers. Never even installed them on this box. It is because of having to give GRUB_GFXPAYLOAD_LINUX=text flag, to get rid of the error. That is why the console looses its normal resolution. This is supposedly the way to work around the error and broken VESA.
On 06/26/12 at 09:19pm, Kevin Chadwick wrote:
If it wasn't huge before then you were either running nouveau or vesa framebuffer on the console and Nvidia in the desktop. This warning is likely due to the fact that running a framebuffer and Nvidia used to crash linux. It can probably? be ignored now.
FWIW, the latest nVidia have broken my (and many others') suspend, forcing me to vga=0 and very low console resolution. So things are noticeably worse as of late.
M
On 06/26/2012 09:42 PM, Don deJuan wrote:
On 06/26/2012 12:31 PM, Arno Gaboury wrote:
dear list,
After a few months of running Arch, I am now fine tuning everything (or at least trying).
I discovered this error message in *kernel.log* file.
NVRM: Your system is not currently configured to drive a VGA console NVRM: on the primary VGA device. The NVIDIA Linux graphics driver NVRM: requires the use of a text-mode VGA console. Use of other console NVRM: drivers including, but not limited to, vesafb, may result in NVRM: corruption and stability problems, and is not supported.
Googling let me to many forum posts about this issue with Nvidia card and driver, but I couldn't find any clear answer.
I have tried all the cited tricks in my *grub* file: -add *vga=0*, or *vga=795* (1208x1024), or *video=visa:off vga=normal* -*GRUB_GFXPAYLOAD_LINUX=console*, *GRUB_GFXPAYLOAD_LINUX=text*, *GRUB_GFXPAYLOAD_LINUX=keep*
and whatever else I couldn't remember, but nothing changed about this message.
As far as I understand, Nvidia does NOT support vesa framebuffer, but only vga. Fine. My system is NOT using VGA console. Fine.
But how do I need ton configure my *grub* file ?
Here are the concerned line from my file :
*GRUB_CMDLINE_LINUX="" GRUB_TERMINAL_INPUT=console GRUB_TERMINAL_OUTPUT=console GRUB_GFXMODE=1280x1024 GRUB_GFXPAYLOAD_LINUX=1280x1024*
Please help as keeping running X like this is not recommanded.
TY.
Putting GRUB_GFXPAYLOAD_LINUX=text in my default grub, then running a new grub.cfg. Reboot and the message went away, though in the console the text is huge. I have seen no actual "fix" for this and have read that Nvidia is not even sure how or why it broke.
The only other difference is I have GRUB_GFXMODE=1280x1024x32 in mine, but with running text this setting is not used, at least that is my understanding.
After lots of reading, especially *Nvidia* official readme, it seems this card SUPPORTS indded *Vesafb*. So I think this error message has nothing to do here, and I will keep my *grub* file as it was first.
After lots of reading, especially *Nvidia* official readme, it seems this card SUPPORTS indded *Vesafb*. So I think this error message has nothing to do here, and I will keep my *grub* file as it was first.
Vesafb is a standard that all cards are meant to support since decades. Running both full blown and vesafb at the same time may cause an issue, I don't know. Nouveau is a kind of hybrid and closer to the features of the nvidia driver but runs in KMS meaning you can close of the dangerous I/O nvidia requires. Running nouveau and nvidia at the same time certainly had issues in the past but I believe they are fixed now.
In any case I wouldn't worry about it until you get corruption as you already have a good resolution console and fast graphical desktop.
If you switch to the console a lot you may want nouveau on both as it switches instantly but may slow down fullscreen flash. Atleast it should switch instantly, some distros like fedora seem to have fscked that up. Maybe they have more 3d nouveau features enabled than default, but I doubt it, anyone know.
Maybe they have more 3d nouveau features enabled than default, but I doubt it, anyone know.
There's a second stage nouveau Xorg driver. It may be that? Anyone use that and not have a delay switching to console?
After lots of reading, especially *Nvidia* official readme, it seems this card SUPPORTS indded *Vesafb*. So I think this error message has nothing to do here, and I will keep my *grub* file as it was first.
Vesafb is a standard that all cards are meant to support since decades. Running both full blown and vesafb at the same time may cause an issue, I don't know. Nouveau is a kind of hybrid and closer to the features of the nvidia driver but runs in KMS meaning you can close of the dangerous I/O nvidia requires. Running nouveau and nvidia at the same time certainly had issues in the past.
FWIW, the latest nVidia have broken my (and many others') suspend, forcing me to vga=0 and very low console resolution. So things are noticeably worse as of late.
*snip* but I believe they are fixed now. *snip*
In any case I wouldn't worry about it until you get corruption as you already have a good resolution console and fast graphical desktop.
If you switch to the console a lot you may want nouveau on both as it switches instantly but may slow down fullscreen flash. Atleast it should switch instantly, some distros like fedora seem to have fscked that up. Maybe they have more 3d nouveau features enabled than default, but I doubt it, anyone know.
On 06/27/2012 04:11 AM, Kevin Chadwick wrote:
After lots of reading, especially *Nvidia* official readme, it seems this card SUPPORTS indded *Vesafb*. So I think this error message has nothing to do here, and I will keep my *grub* file as it was first.
Vesafb is a standard that all cards are meant to support since decades. Running both full blown and vesafb at the same time may cause an issue, I don't know. Nouveau is a kind of hybrid and closer to the features of the nvidia driver but runs in KMS meaning you can close of the dangerous I/O nvidia requires. Running nouveau and nvidia at the same time certainly had issues in the past.
FWIW, the latest nVidia have broken my (and many others') suspend, forcing me to vga=0 and very low console resolution. So things are noticeably worse as of late.
*snip* but I believe they are fixed now. *snip*
In any case I wouldn't worry about it until you get corruption as you already have a good resolution console and fast graphical desktop.
If you switch to the console a lot you may want nouveau on both as it switches instantly but may slow down fullscreen flash. Atleast it should switch instantly, some distros like fedora seem to have fscked that up. Maybe they have more 3d nouveau features enabled than default, but I doubt it, anyone know.
As I stated VESA is broken currently in Nvidia. Even IF your card is supported like mine, VESA will be broken. Nvidia states they do not know why it broke and how. Also they are not sure how to get it working again. You can find all the info in other threads and on the nvidia website. There is no fix, only workarounds.
Arno Gaboury <arnaud.gaboury <at> gmail.com> writes:
After lots of reading, especially *Nvidia* official readme, it seems this card SUPPORTS indded *Vesafb*. So I think this error message has nothing to do here, and I will keep my *grub* file as it was first.
No, it supports the vesa standard. All cards do. But that's completely different from vesafb, a linux driver. When you use vesafb and the nvidia driver together, you effectively have two drivers poking at the card at the same time. That problems can arise from that makes full sense.
You can keep using vesafb. After all, the message is just that - a message - and not an error. It's just that if something breaks, you get to keep the pieces.
On 06/27/2012 06:55 AM, Uroš Vampl wrote:
Arno Gaboury <arnaud.gaboury <at> gmail.com> writes:
After lots of reading, especially *Nvidia* official readme, it seems this card SUPPORTS indded *Vesafb*. So I think this error message has nothing to do here, and I will keep my *grub* file as it was first.
No, it supports the vesa standard. All cards do. But that's completely different from vesafb, a linux driver. When you use vesafb and the nvidia driver together, you effectively have two drivers poking at the card at the same time. That problems can arise from that makes full sense.
You can keep using vesafb. After all, the message is just that - a message - and not an error. It's just that if something breaks, you get to keep the pieces.
Actually no Nvidia never supported VESA, it just happened to work.
http://www.nvnews.net/vbulletin/showpost.php?p=2561806&postcount=39
On 06/27/2012 04:18 PM, Don deJuan wrote:
On 06/27/2012 06:55 AM, Uroš Vampl wrote:
Arno Gaboury <arnaud.gaboury <at> gmail.com> writes:
After lots of reading, especially *Nvidia* official readme, it seems this card SUPPORTS indded *Vesafb*. So I think this error message has nothing to do here, and I will keep my *grub* file as it was first.
No, it supports the vesa standard. All cards do. But that's completely different from vesafb, a linux driver. When you use vesafb and the nvidia driver together, you effectively have two drivers poking at the card at the same time. That problems can arise from that makes full sense.
You can keep using vesafb. After all, the message is just that - a message - and not an error. It's just that if something breaks, you get to keep the pieces.
Actually no Nvidia never supported VESA, it just happened to work.
http://www.nvnews.net/vbulletin/showpost.php?p=2561806&postcount=39
Are you so sure?
http://us.download.nvidia.com/XFree86/Linux-x86/173.14.09/README/chapter-19....:
First sentence: *The NVIDIA Accelerated Linux Graphics Driver supports all standard VGA and VESA modes*
On 06/27/2012 07:42 AM, Arno Gaboury wrote:
On 06/27/2012 04:18 PM, Don deJuan wrote:
On 06/27/2012 06:55 AM, Uroš Vampl wrote:
Arno Gaboury <arnaud.gaboury <at> gmail.com> writes:
After lots of reading, especially *Nvidia* official readme, it seems this card SUPPORTS indded *Vesafb*. So I think this error message has nothing to do here, and I will keep my *grub* file as it was first.
No, it supports the vesa standard. All cards do. But that's completely different from vesafb, a linux driver. When you use vesafb and the nvidia driver together, you effectively have two drivers poking at the card at the same time. That problems can arise from that makes full sense.
You can keep using vesafb. After all, the message is just that - a message - and not an error. It's just that if something breaks, you get to keep the pieces.
Actually no Nvidia never supported VESA, it just happened to work.
http://www.nvnews.net/vbulletin/showpost.php?p=2561806&postcount=39
Are you so sure?
http://us.download.nvidia.com/XFree86/Linux-x86/173.14.09/README/chapter-19....:
First sentence: *The NVIDIA Accelerated Linux Graphics Driver supports all standard VGA and VESA modes*
Well the link I sent was from an Nvidia employee posting about these issues, so yes I am sure. Also why are you pointing to a readme for the legacy version?
It has been stated by Nvidia themselves in other places as well, that VESA just "happened" to work, was not "officially" supported. So take that as you will, but from what I have read and heard from Nvidia this is the case, even googling reveals the same information going all the way back to around 2003. But no point in arguing the semantics about this, I feel the information I found and gotten from Nvidia directly is more than sufficient, your choice if you want to listen to me and other Nvidia employees posting on this issue. You can easily get the same info regardless of what their README states. Or if you have any buddies in the Linux department at nvidia, shoot them an email and you will get the same response from them, it just happened to work.
On 06/27/2012 05:00 PM, Don deJuan wrote:
On 06/27/2012 07:42 AM, Arno Gaboury wrote:
On 06/27/2012 04:18 PM, Don deJuan wrote:
On 06/27/2012 06:55 AM, Uroš Vampl wrote:
Arno Gaboury <arnaud.gaboury <at> gmail.com> writes:
After lots of reading, especially *Nvidia* official readme, it seems this card SUPPORTS indded *Vesafb*. So I think this error message has nothing to do here, and I will keep my *grub* file as it was first.
No, it supports the vesa standard. All cards do. But that's completely different from vesafb, a linux driver. When you use vesafb and the nvidia driver together, you effectively have two drivers poking at the card at the same time. That problems can arise from that makes full sense.
You can keep using vesafb. After all, the message is just that - a message - and not an error. It's just that if something breaks, you get to keep the pieces.
Actually no Nvidia never supported VESA, it just happened to work.
http://www.nvnews.net/vbulletin/showpost.php?p=2561806&postcount=39
Are you so sure?
http://us.download.nvidia.com/XFree86/Linux-x86/173.14.09/README/chapter-19....:
First sentence: *The NVIDIA Accelerated Linux Graphics Driver supports all standard VGA and VESA modes*
Well the link I sent was from an Nvidia employee posting about these issues, so yes I am sure. Also why are you pointing to a readme for the legacy version?
It has been stated by Nvidia themselves in other places as well, that VESA just "happened" to work, was not "officially" supported. So take that as you will, but from what I have read and heard from Nvidia this is the case, even googling reveals the same information going all the way back to around 2003. But no point in arguing the semantics about this, I feel the information I found and gotten from Nvidia directly is more than sufficient, your choice if you want to listen to me and other Nvidia employees posting on this issue. You can easily get the same info regardless of what their README states. Or if you have any buddies in the Linux department at nvidia, shoot them an email and you will get the same response from them, it just happened to work.
So to sum up this thread, I am left with 3 options with a Nvidia card: -uninstall Nvidia driver and install Nouveau -run Nvidia in VGA mode with a low resolution console mode at boot (couldn't find any trick to het an higher resolution, and I tried alomost all I found) -stick with the VESA mode and this error message .
Am I correct?
On 06/27/2012 08:07 AM, Arno Gaboury wrote:
On 06/27/2012 05:00 PM, Don deJuan wrote:
On 06/27/2012 07:42 AM, Arno Gaboury wrote:
On 06/27/2012 04:18 PM, Don deJuan wrote:
On 06/27/2012 06:55 AM, Uroš Vampl wrote:
Arno Gaboury <arnaud.gaboury <at> gmail.com> writes:
After lots of reading, especially *Nvidia* official readme, it seems this card SUPPORTS indded *Vesafb*. So I think this error message has nothing to do here, and I will keep my *grub* file as it was first.
No, it supports the vesa standard. All cards do. But that's completely different from vesafb, a linux driver. When you use vesafb and the nvidia driver together, you effectively have two drivers poking at the card at the same time. That problems can arise from that makes full sense.
You can keep using vesafb. After all, the message is just that - a message - and not an error. It's just that if something breaks, you get to keep the pieces.
Actually no Nvidia never supported VESA, it just happened to work.
http://www.nvnews.net/vbulletin/showpost.php?p=2561806&postcount=39
Are you so sure?
http://us.download.nvidia.com/XFree86/Linux-x86/173.14.09/README/chapter-19....:
First sentence: *The NVIDIA Accelerated Linux Graphics Driver supports all standard VGA and VESA modes*
Well the link I sent was from an Nvidia employee posting about these issues, so yes I am sure. Also why are you pointing to a readme for the legacy version?
It has been stated by Nvidia themselves in other places as well, that VESA just "happened" to work, was not "officially" supported. So take that as you will, but from what I have read and heard from Nvidia this is the case, even googling reveals the same information going all the way back to around 2003. But no point in arguing the semantics about this, I feel the information I found and gotten from Nvidia directly is more than sufficient, your choice if you want to listen to me and other Nvidia employees posting on this issue. You can easily get the same info regardless of what their README states. Or if you have any buddies in the Linux department at nvidia, shoot them an email and you will get the same response from them, it just happened to work.
So to sum up this thread, I am left with 3 options with a Nvidia card: -uninstall Nvidia driver and install Nouveau -run Nvidia in VGA mode with a low resolution console mode at boot (couldn't find any trick to het an higher resolution, and I tried alomost all I found) -stick with the VESA mode and this error message .
Am I correct?
You could also use the xf86-video-nv driver, but yes those are my understandings of this issue as well.
Le 27 juin 2012 à 17:07 CEST, Arno Gaboury a écrit :
So to sum up this thread, I am left with 3 options with a Nvidia card: -uninstall Nvidia driver and install Nouveau -run Nvidia in VGA mode with a low resolution console mode at boot (couldn't find any trick to het an higher resolution, and I tried alomost all I found) -stick with the VESA mode and this error message .
Am I correct?
On my laptop, before switching to nouveau, I used uvesafb together with the nvidia driver without any issue (1680x1050 console, yay!). You may want to give it a try. https://wiki.archlinux.org/index.php/Uvesafb
Regards,
On 06/27/2012 07:55 PM, Thomas Jost wrote:
Le 27 juin 2012 à 17:07 CEST, Arno Gaboury a écrit :
So to sum up this thread, I am left with 3 options with a Nvidia card: -uninstall Nvidia driver and install Nouveau -run Nvidia in VGA mode with a low resolution console mode at boot (couldn't find any trick to het an higher resolution, and I tried alomost all I found) -stick with the VESA mode and this error message .
Am I correct?
On my laptop, before switching to nouveau, I used uvesafb together with the nvidia driver without any issue (1680x1050 console, yay!). You may want to give it a try. https://wiki.archlinux.org/index.php/Uvesafb
Regards,
I was in fact going this way yesterady, when I finally gave up after hours and hours of reading and testing. I will give a try.
Arno Gaboury <arnaud.gaboury <at> gmail.com> writes:
Actually no Nvidia never supported VESA, it just happened to work.
http://www.nvnews.net/vbulletin/showpost.php?p=2561806&postcount=39
Are you so sure?
http://us.download.nvidia.com/XFree86/Linux-x86/173.14.09/README/chapter-19....:
First sentence: *The NVIDIA Accelerated Linux Graphics Driver supports all standard VGA and VESA modes*
Wow, you guys are now mixing up *three* things!
Like I said, one thing is the vesa standard, and the other is a linux driver called vesafb. These are not one and the same! Now you've added a third thing into the mix - vesa modes. They are modes defined by the standard.
On 06/27/2012 08:18 AM, Uroš Vampl wrote:
Arno Gaboury <arnaud.gaboury <at> gmail.com> writes:
Actually no Nvidia never supported VESA, it just happened to work.
http://www.nvnews.net/vbulletin/showpost.php?p=2561806&postcount=39
Are you so sure?
http://us.download.nvidia.com/XFree86/Linux-x86/173.14.09/README/chapter-19....:
First sentence: *The NVIDIA Accelerated Linux Graphics Driver supports all standard VGA and VESA modes*
Wow, you guys are now mixing up *three* things!
Like I said, one thing is the vesa standard, and the other is a linux driver called vesafb. These are not one and the same! Now you've added a third thing into the mix - vesa modes. They are modes defined by the standard.
I do not see what I have mixed up, I never said anything about vesafb, only the VESA standard, also I have not talked about defining any modes, only another driver option to use instead of the proprietary.
I think you're the one "mixing" up what we have written.
Don deJuan <donjuansjiz <at> gmail.com> writes:
I do not see what I have mixed up, I never said anything about vesafb, only the VESA standard, also I have not talked about defining any modes, only another driver option to use instead of the proprietary.
I think you're the one "mixing" up what we have written.
Nope, it's definitely you. I say Nvidia cards supports the vesa standard, and you say "they never did" pointing to a forum post about *vesafb*. See you mix-up now? You though that forum post is about vesa, but it's not, it's about vesafb.
On 06/27/2012 08:26 AM, Uroš Vampl wrote:
Don deJuan <donjuansjiz <at> gmail.com> writes:
I do not see what I have mixed up, I never said anything about vesafb, only the VESA standard, also I have not talked about defining any modes, only another driver option to use instead of the proprietary.
I think you're the one "mixing" up what we have written.
Nope, it's definitely you. I say Nvidia cards supports the vesa standard, and you say "they never did" pointing to a forum post about *vesafb*. See you mix-up now? You though that forum post is about vesa, but it's not, it's about vesafb.
lol ok
####Sent from my Galaxy S2 running Cyanogenmod 9#### Come and chat on Googletalk On Jun 27, 2012 5:22 PM, "Don deJuan" donjuansjiz@gmail.com wrote:
On 06/27/2012 08:18 AM, Uroš Vampl wrote:
Arno Gaboury <arnaud.gaboury <at> gmail.com> writes:
Actually no Nvidia never supported VESA, it just happened to work.
http://www.nvnews.net/vbulletin/showpost.php?p=2561806&postcount=39
Are you so sure?
http://us.download.nvidia.com/XFree86/Linux-x86/173.14.09/README/chapter-19.... :
First sentence: *The NVIDIA Accelerated Linux Graphics Driver supports all standard VGA and VESA modes*
Wow, you guys are now mixing up *three* things!
Like I said, one thing is the vesa standard, and the other is a linux
driver
called vesafb. These are not one and the same! Now you've added a third
thing
into the mix - vesa modes. They are modes defined by the standard.
I do not see what I have mixed up, I never said anything about vesafb,
only the VESA standard, also I have not talked about defining any modes, only another driver option to use instead of the proprietary.
I think you're the one "mixing" up what we have written.
I am the one who used the word "mode" when I wanted to talk about Framebuffer. My words were not precise enough, as I fully understand what a mode is. I shall learn to be more precise.
No, it supports the vesa standard. All cards do. But that's completely different from vesafb, a linux driver.
Your right and you cleared up the confusion somewhbut that's a little unfair. I believe all cards MUST support VESA. The vesafb driver isn't supported directly but it uses the VESA standard as do many embedded drivers so it is supported indirectly. They certainly don't support running both but then on the 172 driver mentioned they don't support the recent xorg servers new abi either.
If I was the OP I wouldn't waste time if there's is no problem beyond a log from a closed source driver unless uvesafb offers benefits as that won't be supported either as it's not Nvidia's code is it?
####Sent from my Galaxy S2 running Cyanogenmod 9#### Come and chat on Googletalk On Jun 29, 2012 1:16 AM, "Kevin Chadwick" ma1l1ists@yahoo.co.uk wrote:
No, it supports the vesa standard. All cards do. But that's completely
different
from vesafb, a linux driver.
Your right and you cleared up the confusion somewhbut that's a little unfair. I believe all cards MUST support VESA. The vesafb driver isn't supported directly but it uses the VESA standard as do many embedded drivers so it is supported indirectly. They certainly don't support running both but then on the 172 driver mentioned they don't support the recent xorg servers new abi either.
If I was the OP I wouldn't waste time if there's is no problem beyond a log from a closed source driver unless uvesafb offers benefits as that won't be supported either as it's not Nvidia's code is it?
I am the OP and I agree with your opinion, thus I decided to ignore the Kernel error message. As there is NO decisive answer, neither an universally recognized setup, this is the way I decided to run my X server with my Nvidia graphic card and driver. My system MAY be instable thought, but I endorse the risk. Switching to Nouveau would be best indeed, but not at its current stage. ___________________________________________
Why not do something good every day and install BOINC. ________________________________________________________
On Jun 29, 2012 2:12 AM, "arnaud gaboury" arnaud.gaboury@gmail.com wrote:
Switching to Nouveau would be best indeed, but not at its current stage.
Why? Do you have problems running it? I [unfortunately] have several systems with nvidia cards, of varying age/caliber, all running nouveau with 3D-ness enabled in X ... no significant issues for probably 1-2 yrs or so (and just gave a successful presentation on vpython 3 days ago).
Not to suggest it's without issue, but its worth trying periodically.
arch-general@lists.archlinux.org