On Jun 29, 2012 2:12 AM, "arnaud gaboury" 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 ...
Sent from my Galaxy S2 running Cyanogenmod 9 Come and chat on
Googletalk
On Jun 29, 2012 1:16 AM, "Kevin Chadwick" 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
> 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
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 an
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,
Sent from my Galaxy S2 running Cyanogenmod 9 Come and chat on
Googletalk
On Jun 27, 2012 5:22 PM, "Don deJuan" wrote:
>
> On 06/27/2012 08:18 AM, Uroš Vampl wrote:
>>
>> Arno Gaboury gmail.com> writes:
>
>
>
Actually no Nvidia never supported VESA, it just happened to wor
On 06/27/2012 08:26 AM, Uroš Vampl wrote:
Don deJuan 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 t
Don deJuan 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 w
On 06/27/2012 08:18 AM, Uroš Vampl wrote:
Arno Gaboury 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/READ
Arno Gaboury 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.html:
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 gmail.com> writes:
After lots of reading, especially *Nvidia* o
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 gmail.com> writes:
After lots of reading, especially *Nvidia* official readme, it seems
this card SUPPORTS i
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 gmail.com> writes:
After lots of reading, especially *Nvidia* official readme, it seems
this card SUPPORTS indded *Vesafb*. So I think this error messa
On 06/27/2012 04:18 PM, Don deJuan wrote:
On 06/27/2012 06:55 AM, Uroš Vampl wrote:
Arno Gaboury 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
On 06/27/2012 06:55 AM, Uroš Vampl wrote:
Arno Gaboury 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 supp
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 me
Arno Gaboury 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.
> 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?
--
Why not do somethi
> 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 bot
> 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 bot
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
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 ign
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
> 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 the
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
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
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
27 matches
Mail list logo
