Bug 978973

Why not add a video drop-down list? Since vga is deprecated, the video option is the new replacement.

Josef, please check....

I have added video=1280x1024 to kernel options to bring back the boot splash.
Then I typed mkinitrd && reboot to add it to initrd.

The "video=" option should be passed on to plymouth during the boot process so that we see a bootsplash.
I'm wondering if another bug report for plymouth should be reported.

Any thoughts?

(In reply to Roman Bysh from comment #0)
> Tumbleweed
> 
> Removing the very useful vga selection

Please explain what you mean. I tested bootloader module on current TW and it still offers "Console Resolution" selection which is translated in grub2

gfxmode=800x600
gfxpayload=keep

This should be entirely equivalent to using vga=800x600 (sorry, forgot hex for it) on kernel command line. If not, the first suspect here is grub2. Please give as much details as possible, including architecture and platform (BIOS, EFI) and your grub.cfg.

> now breaks plymouth as it now shows
> three question marks.

This probably means plymouth is started in text mode. Please show dmesg after boot for both cases, with and without vga= on kernel command line.

> We've been using it for years why the sudden change?
> 

As long as grub2 is the only supported bootloader, using grub2 native means to configure resolution sounds logical.

> It seems to work fine with the nouveau driver but when I install an Nvidia
> blob
> I get three question marks.
> 

Sorry, but that is absolutely unintelligible. Works "what"? YaST2 bootloader module adds vga= kernel parameter when you are using nouveau?

> Plymouth requires a ie. vga=795 so that it can show the boot splash.

You are confused. Plymouth does *not* require it. Plymouth can also show splash in text mode. This is buggy as you see and has to be reported separately. To show graphical splash kernel has to start with frame buffer console. That apparently does not happen in your case, and we need to understand why. It works on all my VMs BTW so it is not something generally broken.

Let's try to understand the root cause before demanding perpetual workaround.

(In reply to Roman Bysh from comment #4)
> I'm wondering if another bug report for plymouth should be reported.
> 

Three question marks is a bug in console initialization in text mode; there was already bug report but I am not sure what outcome is. In any case, this is something between plymouth, systemd and dracut and completely unrelated to yast.

Three question marks on the boot screen might not look pretty, but it's certainly not a MAJOR bug.

Andrei

The update removed my vga settings from grub.cfg. Not good. I am use an Nvidia card. The driver is 340.96 x86_64. 

For me console resolution controls the resolution of the grub2 menu graphics and the fonts.

Now that vga= is deprecated we have switched to video=1180x1024 by adding it to the kernel options and running mkinitrd.

The bootsplash is back.

The community would have appreciated a heads up on the Factory ml that it was being removed. Since we provide help on the forum we would like to be prepared.

Follow Up

Our desktops use an ASUS P5Q with a Q6600 CPU with 8GB of RAM.
I have 1TB drive for my primary drive. The 2nd and 3rd drives are 500 GB.

Created attachment 676424 [details]
Revised grub.cfg

This is a revised grub.cfg file so that it works with Plymouth.
Removing the video=1280x1024 breaks Plymouth so that it shows three question marks. This is with the Nvidia driver installed.

(In reply to Roman Bysh from comment #9)
> Created attachment 676424 [details]
> Revised grub.cfg
> 
> This is a revised grub.cfg file so that it works with Plymouth.

This contains

set gfxmode=1280x800
set gfxpayload=keep

and you override it with video=1280x1024. Why you are using different modes?

You still did not show any evidence that using vga=1280x800 works (while your initial claim is that removing this option causes your problem). And I still do not see dmesg in working and non-working cases for comparison. I'm afraid knowing hard drive size of your system is of little help in this case.

I am using the different setting video=1280x1024 to reduce the font size when I switch to ctrl+alt+F1. The fonts are *HUGE* if I use 1280x800.

My monitor is an Acer x203 with a resolution 1680x1050.
Look console mode 1280x800 makes the grub2 menu appear on the screen just right. If I increase the console mode setting to 1280x1024 then the height of the menu gets smaller.

vga=795 = video=1280x1024

I've been using this configuration for years. Since openSUSE 10x.

(In reply to Roman Bysh from comment #11)
> 
> I've been using this configuration for years. Since openSUSE 10x.

I tested on 13.2 and I do not see any difference with TW. In 13.2 YaST Bootloader offers Console Resolution menu and it translates into grub2 gfxmode and gfxpayload. No vga= option is ever added to kernel command line. So I'm afraid I'm completely lost what exact behavior change you mean. Could you try to explain it once more. Thank you.

Follow Up

Looks like something got corrupt when I updated. Today I did fresh installation using ext4 and I am no longer adding "video=" to the kernel options.
Everything looks good today. 
The console fonts look correct.

Perhaps in the past before Plymouth I had to add the vga=795 so I kept using it.
Please close this bug report.

Follow Up

After removing the vga and video entries from the kernel options dmesg shows:

NVRM: Your system is not currently configured to drive a VGA console
[   22.189972] NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
[   22.189974] NVRM: requires the use of a text-mode VGA console. Use of other console
[   22.189977] NVRM: drivers including, but not limited to, vesafb, may result in
[   22.189979] NVRM: corruption and stability problems, and is not supported.

Created attachment 676961 [details]
dmesg

My dmesg

(In reply to Roman Bysh from comment #15)
> My dmesg

Where is dmesg with vga= and/or video= options?

When they were removed I got the message posted in comment #14

As I commented the decision was made stop using vga= and video= option.

Everything is working including the boot splash without them being added to my kernel options.


Can you please close the bug report?

New test provides good results

I no longer have any vga= entries in openSUSE 13.2 and Tumbleweed.
Both openSUSE 13.2 and Tumbleweed are on separate drives.

Test 1
I set my sata cables so that 13.2 is primary with Tumbleweed on the second drive.
The desktop is powered up and Tumbleweed is selected from the 13.2 grub2 menu.
I see a flashing cursor in the top left corner of the screen during the boot process and is followed by the boot splash with the three question marks.

The desktop is then shutdown and rebooted. This time I select 13.2. The boot process appears normal with the correct resolution and no flashing cursor.
  
Test 2
I reversed the sata cables so that my 2nd drive with Tumbleweed is the primary and openSUSE 13.2 is the second drive.
The desktop is powered up and Tumbleweed is selected from the Tumbleweed grub2 menu. This time Tumbleweed boot process looks normal with the correct resolution.

When I shutdown, reboot and select 13.2 from the Tumbleweed menu the flashing cursor appears in the top left corner and I have HUGE letters for the console prompt when I press ctrl+alt+F1.

When I add vga=795 to the kernel options whatever openSUSE distro is on the second drive no longer shows the flashing cursor in the the left window and three question marks.

(In reply to Roman Bysh from comment #18)
...
> The desktop is powered up and Tumbleweed is selected from the 13.2 grub2
> menu.
> I see a flashing cursor in the top left corner of the screen during the boot
> process and is followed by the boot splash with the three question marks.
> 
...
> 
> When I shutdown, reboot and select 13.2 from the Tumbleweed menu the
> flashing cursor appears in the top left corner and I have HUGE letters for
> the console prompt when I press ctrl+alt+F1.
> 


Yes, gfxpayload was not set for Linux entries generated from os-prober scan. Please try grub2 from

http://download.opensuse.org/repositories/home:/arvidjaar:/bnc:/978973/openSUSE_Tumbleweed/

It contains patch to do it. If you want, you may try the same package on 13.2 as well

http://download.opensuse.org/repositories/home:/arvidjaar:/bnc:/978973/openSUSE_13.2/

Created attachment 677119 [details]
screenshot of yast2 boot loader error message pop up

I'm getting the same message on openSUSE 13.2 and Tumbleweed.

When I run grub2-mkconfig I get the following output with an error.

grub2-mkconfig -o /boot/grub2/grub.cfg
Generating grub configuration file ...
Found theme: /boot/grub2/themes/openSUSE/theme.txt
Found linux image: /boot/vmlinuz-3.16.7-35-desktop
Found initrd image: /boot/initrd-3.16.7-35-desktop
Found linux image: /boot/vmlinuz-3.16.7-32-desktop
Found initrd image: /boot/initrd-3.16.7-32-desktop
  WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it!
  No volume groups found
/etc/grub.d/30_os-prober: line 256: syntax error near unexpected token `fi'

These error messages appear after I updated grub2.

Created attachment 677122 [details]
new grub.cfg

I've uploaded the new grub.cfg

Created attachment 677123 [details]
30_os_prober

This the newest 30_os_prober that is broken.

Created attachment 677135 [details]
y2logs

I've included the y2logs for Yast for you to review.

(In reply to Roman Bysh from comment #21)
> /etc/grub.d/30_os-prober: line 256: syntax error near unexpected token `fi'

Sorry, I updated patch; it may take some time until TW version is rebuilt.

Roman - I am not much happy to have injected another topic into this bug, next time please open new one, so one bug one topic. Thanks

Andrei,

Is there a fix for openSUSE 13.2?

Josef,

Agreed.

Andrei,

I installed the patched grub2 in openSUSE 13.2. It did not work. The problem is that /etc/default/grub is missing GRUB_GFXPAYLOAD_LINUX=

I added it to the grub file so that it appears as:

GRUB_GFXMODE=1680x1050
GRUB_GFXPAYLOAD_LINUX=1680x1050

Ran grub2-mkconfig -o /boot/grub2/grub.cfg

Now it is working.

I reset the settings to the default:

GRUB_GFXMODE=1280x800
GRUB_GFXPAYLOAD_LINUX=1280x800

Ran grub2-mkconfig and it's still working. I would strongly recommend that you
add 

GRUB_GFXMODE=1280x800
GRUB_GFXPAYLOAD_LINUX=1280x800

as the default. This should be added to the Yast installer so that it will work out of the box in future versions.

Andrei,

I've testing the Grub2 fix for openSUSE 13.2 and Tumbleweed. They only work by adding:

GRUB_GFXPAYLOAD_LINUX="1280x800

Can you add a patch to /etc/default/grub so that it is ready without having to manually add it after updating Grub2?

Grub2 should be ready for download or update for openSUSE 13.2 and Tumbleweed.

Missed a quotation mark

GRUB_GFXPAYLOAD_LINUX="1280x800"

Andrei,

I found the correct setting from:

GRUB_GFXMODE=1680x1050
GRUB_GFXPAYLOAD_LINUX=1680x1050

to:

GRUB_GFXMODE=1680x1050
GRUB_GFXPAYLOAD_LINUX=keep


I believe this is the correct setting to use in future default settings of /etc/default/grub settings.

IMPORTANT

Andrei,

Please consider adding a patch so that it adds an extra line:

GRUB_GFXPAYLOAD_LINUX=keep

to /etc/default/grub

This line will appear as shown below:

GRUB_GFXMODE=1680x1050
GRUB_GFXPAYLOAD_LINUX=keep

After a lot off testing this fixes the bug. This can be repackaged and made available as an update for openSUSE 13.2 and Tumbleweed.

Andrei,

I've just noticed this problem with openSUSE 42.2 Alpha 3.

Can you please apply this patch to the new 64-bit Grub2?
This has been outstanding for some time.

Update Please

Andrei,

Can you please apply your os-prober patch to Grub2 to Factory and then Tumbleweed repository?

It's still working. We can close this report.

Andrei,

Please confirm that you are closing this bug report.

Marking this bug as resolved. It has been fixed.

I still see the three question marks on Tumbleweed and only occasionally the plymouth boot screen is shown. It seems non-deterministic though.

Add the line GRUB_GFXPAYLOAD_LINUX=keep

to /etc/default/grub

This line will appear as shown below:

GRUB_GFXMODE=1280x800
GRUB_GFXPAYLOAD_LINUX=keep

Then type grub2-mkconfig -o /boot/grub2/grub.cfg

Reboot

I was trying these in the past ever since I found this bug report but then and now it does not help.

On an additional note in case this is relevant (although I don't think so): I'm using an lvm-encrypted btrfs root partition, a separate btrfs boot partition and UEFI

Add this repo to Yast

http://download.opensuse.org/repositories/home:/arvidjaar:/bnc:/978973/openSUSE_Tumbleweed

Use the "change vendor" option to switch and update the grub2* packages.

Reboot.

Unfortunately, this doesn't help either (as in the past) and I still have the password prompt in text mode and the three question marks. I'm using the latest 375.26 NVidia blob but this behaviour did not change over the past x driver versions.

Also, when looking at the OBS project, it seems to be outdated to some extend compared to the repo it is based on.

Michael

You left out the following in the latest version of os-prober 1.74:


if [ "x$GRUB_GFXPAYLOAD_LINUX" != x ]; then
	      if [ "x$GRUB_GFXPAYLOAD_LINUX" != xtext ]; then
		echo "	load_video"
	      fi
	      echo "	set gfxpayload=$GRUB_GFXPAYLOAD_LINUX"
	    fi

During the boot process of Tumbleweed Plymouth shows three tiny green squares.

So using "GRUB_GFXPAYLOAD_LINUX=keep" in /etc/default/grub no longer enables Plymouth graphics.

I have Tumbleweed installed on another drive.

I had to reopen this bug report. If Tumbleweed is installed on my 3rd drive the Tumbleweed logo has disappeared again.

I've had this problem myself for many months, and still do with the latest packages: Instead of the correct images showing, the boot time splash screen is always a gray background with three green ??? symbols in the center-lower part of the screen.

Note however that this is not a Nvidia exclusive problem as I think some have suggested! I have a Radeon card which runs on the RadeonSI architecture, and get this issue never the less.

When I boot to runlevel 3 or press CTRL+ALT+F1 the fonts are very large About a centimeter or more in height.

Update

Grub2 2.00 is still broken in Tumbleweed.

It seems your boot splash can only be rendered correctly with graphic mode 1280x800 which cannot not be the case for others, so I think the setting cannot be applied globally.

For missing gfypayload settings in os-prober, I suggest to open a new bug as it's a separate problem.
Thanks.

I apologize for not coming back earlier. I tested booting in text mode and linux framebuffer driver gets loaded and linux switches to framebuffer console. So contrary to my assumption it is not necessary to have framebuffer active when linux kernel is loaded. 

Also every now and then I (and other users) get the same text mode splash even for regular boot, with gfxpayload and vide setup.

So it really sounds like the root cause is somewhere else.

(In reply to Andrei Borzenkov from comment #52)
> I apologize for not coming back earlier. I tested booting in text mode and
> linux framebuffer driver gets loaded and linux switches to framebuffer
> console. So contrary to my assumption it is not necessary to have
> framebuffer active when linux kernel is loaded. 
> 
> Also every now and then I (and other users) get the same text mode splash
> even for regular boot, with gfxpayload and vide setup.
> 
> So it really sounds like the root cause is somewhere else.

I keep GFXMODE lower as it also controls the resolution of the grub2 menu.

It appears that the command "GRUB_GFXPAYLOAD_LINUX=keep" is broken. Can you still access a lower version of grub2 from 2016?

We should install them and see of there is any difference. Do you have 1.99?

Can the problem in Tumbleweed exist with newer kernels introduced this year?

The GFXPAYLOAD in Grub2 worked ever since you introduced a patched version in 
May - June 2016.

When I switched to your Grub2 2.0 they no longer worked in 2017.

Michael

Can the problem exist with dracut? 

I would like to test an older version from 2016 and compare with a very new one.

I didn't do any in-depth testing, but just confirming that the broken splash screen still exists for me in latest Tumbleweed, and has in fact never been fixed for at least an year. Once again, I do not use a Nvidia card, mine is a RadeonSI / GCN 1.0.

I have however noticed a VERY strange side effect, which I never actually reported and took me a while to figure out: If my system doesn't cleanly shut down (eg: a GPU lockup causes me to force restart), the splash screen will show correctly! However, if I do a normal and clean shutdown or restart of the system, I get the gray background with three green ??? symbols. Any thoughts on this?

That is very strange. The plymouth image is stored in the initrd file. Perhaps memory got freed up from you graphics card.

I would recommend testing an older dracut file with a newer.

I forgot to add this link from another bug report.

Ref: https://bugzilla.opensuse.org/show_bug.cgi?id=1011474

(In reply to Roman Bysh from comment #55)
> Michael
> 
> Can the problem exist with dracut? 

Maybe. What about the kernel kms driver (of specific vga adapter) ? As far as I know plymouth renders via kms backend though I am pretty rust to tell as it may not be the case.

And when it comes to kms drivers, usually vga= and gfxpayload has nothing to do with them. Both bootloader parameters are meant to be effective for 'firmware' based mode setting before kms takes place and takes position of it.

I am testing Leap 42.3 and the problem has returned about not being able to read BTRFS partition on another drive.

Grub menu on Leap 42.3 shows Tumbleweed as unknown Linux distribution.

Michael

I wonder if Fedora is experiencing the same problem? Can you contact them?

Michael

I updated Leap 42.3 Beta today to the latest release. Plymouth is now working during the boot process. And, I have it installed on another drive.

Follow Up

Looks like it hasn't been fixed. I have it installed on another drive.
Plymouth shows three little squares.

Hi Roman,

Sorry but I really think Plymouth problem (displays three little squares) is not related to removed vga kernel option here, or even not nouveau specific.

And from me the culprit could be everything else, name it in Plymouth itself, kernel, dracut or even combination of them, that could all affect result of rendering. I think a separate bug report is more appropriate as it's quite complicated to understand what really happened ..

It's much more complex as the kernel has changed this year compared the kernels of 2016.
I see a patch has been provided for Leap 42.2. 

Can that patch be provided for 42.3 for me to test? I have 42.3 installed on my 4th drive.

Guys,

Have you spoken with Fedora or Ray Stroda (Plymouth maintainer)? They may have some ideas on what the problem can be.

Michael,

Did you provide a patch for 42.2? I can see the Plymouth bootsplash during the boot process.

Update Please

What is the status of Plymouth and getting to work in Tumbleweed. It is working in Leap 42.3 yet when Tumbleweed is installed on my 2nd drive, all I see is a black screen during the boot process.

Is this an issue with dracut and grub2 or both? 

Leap 42.3 is installed on my first drive and I can see Plymouth during the boot process.

Update December 30, 2017

Plymouth shows three small square when Leap 15 is installed on a second drive.
Tumbleweed shows black during the boot process when it is running on another drive other than the first drive.

Update

I'm running Leap 14 Build 124.1 on my second drive and I'm still getting the three little squares. What's the news update?

(In reply to Roman Bysh from comment #71)
> I'm still getting the three little squares.

Could be https://bugs.freedesktop.org/show_bug.cgi?id=105141. If you boot with plymouth.debug=stream:/run/plymouth.trace and check /run/plymouth.ttrace after boot do you see messages about not initialized skipped devices?

Just confirming that I still have this problem in latest Tumbleweed, after I forgot how many years now. It only happens if I do a normal reboot / shutdown... if I power off my computer while it's running and boot it back up, I see the normal splash screen but only that once. Again I don't have a Nvidia card as the title suggests, mine is RadeonSI.

Try installing it on another drive and see what the results are. 
I would debug your installation. Please review comment #72.

Just a heads up in case this is relevant: Yesterday I was finally able to switch from the old "radeon" driver to the newer "amdgpu" driver on my RadeonSI card. This can be done by booting the system with the following parameters:

radeon.si_support=0 amdgpu.si_support=1

The splash screen bug no longer happens when using this driver. The gray background and green ??? are gone, I always see the themed boot screen.

So this may either be a driver specific issue, either certain drivers take certain steps differently which causes the screen to load differently as well. For instance I also see the console more often during the booting process, so it may very well be the later case.

I have run a plymouth debug and there are a number of errors.

Created attachment 761558 [details]
plymouth.trace

Comment on attachment 761558 [details]
plymouth.trace

See:

[./plugin.c:1017]                                  query_device:Could not get card resources
[ply-renderer.c:250]                      ply_renderer_open_plugin:could not query rendering device for plugin /usr/lib64/plymouth/renderers/drm.so
[./plugin.c:768]                                  close_device:closing device
[./plugin.c:722]                                unload_backend:unloading backend
[./plugin.c:633]                               destroy_backend:destroying renderer backend for device /dev/dri/card0
[ply-renderer.c:287]                             ply_renderer_open:could not find suitable rendering plugin

There appears to be a bug in ./plugin.c as it could not get card resources.

Update Please

Are you able to fix this bug in time for the GA release of Leap 15?

This has been broken and fixed some time in May of 2016. Yet, openSUSE Leap 42.3 works when running on the first SATA drive. There is still a problem when selecting to boot an installation from the grub2 menu a root partition on a second drive. The three little green squares shows up during the boot process.

It was fixed then it broke again in the last quarter of 2016.

(In reply to Michael Chang from comment #64)
> Hi Roman,
> 
> Sorry but I really think Plymouth problem (displays three little squares) is
> not related to removed vga kernel option here, or even not nouveau specific.
> 
> And from me the culprit could be everything else, name it in Plymouth
> itself, kernel, dracut or even combination of them, that could all affect
> result of rendering. I think a separate bug report is more appropriate as
> it's quite complicated to understand what really happened ..

Michael,

See bug report https://bugzilla.opensuse.org/show_bug.cgi?id=1090451

I'm getting a message from dracut that it is removing the Plymouth module. This right after I installed the NVidia drivers.

@Michael Chang,

It appears that Plymouth 9.3git does not work with Tumbleweed and Leap when NVidia drivers are installed. However, when I downgraded to Plymouth 9.2x it suddenly works with NVidia drivers.

I would recommend that we stick with Plymouth 9.2x for Leap 15.0.

Any thoughts?

(In reply to Roman Bysh from comment #82)
> @Michael Chang,
> 
> It appears that Plymouth 9.3git does not work with Tumbleweed and Leap when
> NVidia drivers are installed. However, when I downgraded to Plymouth 9.2x it
> suddenly works with NVidia drivers.

Is it possible to bisect to know the offending commit ?

> 
> I would recommend that we stick with Plymouth 9.2x for Leap 15.0.
> 
> Any thoughts?

Well. I am not maintainer of Plymouth, I can't speak on behave of them so you should contact them in favor of me. I have added qzhao and set needinfo to him. he is the maintainer/bugowner queried by iosc maintainer SUSE:SLE-15:GA plymouth.

Basically it is not good idea to have Leap 15.0 a separate version to SLE imho, they have to share the same maintenance update channel for any "Core" package ...

(In reply to Michael Chang from comment #83)
> (In reply to Roman Bysh from comment #82)
> > @Michael Chang,
> > 
> > It appears that Plymouth 9.3git does not work with Tumbleweed and Leap when
> > NVidia drivers are installed. However, when I downgraded to Plymouth 9.2x it
> > suddenly works with NVidia drivers.
> 
> Is it possible to bisect to know the offending commit ?
> 
> > 
> > I would recommend that we stick with Plymouth 9.2x for Leap 15.0.
> > 
> > Any thoughts?
> 
> Well. I am not maintainer of Plymouth, I can't speak on behave of them so
> you should contact them in favor of me. I have added qzhao and set needinfo
> to him. he is the maintainer/bugowner queried by iosc maintainer
> SUSE:SLE-15:GA plymouth.

Should I make a new bug report under Plymouth?

> Basically it is not good idea to have Leap 15.0 a separate version to SLE
> imho, they have to share the same maintenance update channel for any "Core"
> package ...

Agreed.

@qzhao

Can you bisect Plymouth 9.3gitx and Plymouth 9.2x to find out which patch is causing Plymouth to go completely black when booting up with Nvidia drivers installed?

I used this repository to fix the problem in TW and Leap. It's basically downgrading Plymouth to 9.2x. 

http://download.opensuse.org/repositories/home:/mrbadguy/openSUSE_Tumbleweed/

I understand that I shouldn't mix repositories because Leap and SLE share the same maintenance channel. Could there be a problem with the frambuffer?

One of the patches from May 2016 to now has created this problem.

I no longer see question marks. I'm seeing three little squares.

Could this be a case of the font map missing from initrd?

Unfortunately,we haven't heard from the maintainer of plymouth. 
Unless openSUSE adds the bootsplash to the kernel I really can't see a future with Plymouth and using the Nvidia drivers.

Do you want to mark this as WONTFIX so that we can move on to other bugs?

(In reply to Roman Bysh from comment #87)

> Do you want to mark this as WONTFIX so that we can move on to other bugs?

We have to move on, certainly. We can't do anything to support proprietary driver like nvidia. I know we had a plan to replace Plymouth with in-kernel rendering, but I don't have the detail.

Thanks for your enthusiasm to the project.

(In reply to Michael Chang from comment #88)
> (In reply to Roman Bysh from comment #87)
> 
> > Do you want to mark this as WONTFIX so that we can move on to other bugs?
> 
> We have to move on, certainly. We can't do anything to support proprietary
> driver like nvidia. I know we had a plan to replace Plymouth with in-kernel
> rendering, but I don't have the detail.
> 
> Thanks for your enthusiasm to the project.

No problem. Am I better off switching to a Radeon card?

(In reply to Roman Bysh from comment #89)
> (In reply to Michael Chang from comment #88)
> > (In reply to Roman Bysh from comment #87)

> No problem. Am I better off switching to a Radeon card?

AMD/ATI does really better work in open source their driver. AFAIK most their driver are in kernel and you don't need the ugly kmp stuff :).