[opensuse-factory] splashy vs bootsplash
I'd like to ask if there are any plans to drop bootsplash for 11.2 as the bootsplash.org site itself recommends moving over to splashy. thanks -- Jakub Steiner <jimmac@gmail.com> http://jimmac.musichall.cz -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sat, Jun 13, 2009 at 4:13 AM, Jakub Steiner<jimmac@gmail.com> wrote:
I'd like to ask if there are any plans to drop bootsplash for 11.2 as the bootsplash.org site itself recommends moving over to splashy.
Fedora and Ubuntu seems to have moved to "Plymouth" it supports animated boot splash. It would be nice to use that for 11.2. Cheers -J -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Saturday 13 June 2009 06:45:05 Jigish Gohil wrote:
On Sat, Jun 13, 2009 at 4:13 AM, Jakub Steiner<jimmac@gmail.com> wrote:
I'd like to ask if there are any plans to drop bootsplash for 11.2 as the bootsplash.org site itself recommends moving over to splashy.
Fedora and Ubuntu seems to have moved to "Plymouth" it supports animated boot splash.
It would be nice to use that for 11.2. I'm not aware of anyone working on it though.
splashy supports animated boot splashs too - we use it for suspend. Staying with bootsplash sounds wrong, but then again it's the cheapest solution for now. Someone needs to do a test with both available solutions and then we need to judge. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sat, Jun 13, 2009 at 12:56 PM, Stephan Kulow<coolo@novell.com> wrote:
On Saturday 13 June 2009 06:45:05 Jigish Gohil wrote:
On Sat, Jun 13, 2009 at 4:13 AM, Jakub Steiner<jimmac@gmail.com> wrote:
I'd like to ask if there are any plans to drop bootsplash for 11.2 as the bootsplash.org site itself recommends moving over to splashy.
Fedora and Ubuntu seems to have moved to "Plymouth" it supports animated boot splash.
It would be nice to use that for 11.2. I'm not aware of anyone working on it though.
development seems to be active: http://cgit.freedesktop.org/plymouth/log/ I also saw it in moblin project repo.
splashy supports animated boot splashs too - we use it for suspend. Staying with bootsplash sounds wrong, but then again it's the cheapest solution for now.
Someone needs to do a test with both available solutions and then we need to judge.
Yes, but it seems plymouth needs bit more work before we can test: http://sidux.com/PNphpBB2-viewtopic-t-15145.html Ciao -J -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Saturday 13 June 2009 08:34:48 Jigish Gohil wrote:
On Sat, Jun 13, 2009 at 12:56 PM, Stephan Kulow<coolo@novell.com> wrote:
On Saturday 13 June 2009 06:45:05 Jigish Gohil wrote:
On Sat, Jun 13, 2009 at 4:13 AM, Jakub Steiner<jimmac@gmail.com> wrote:
I'd like to ask if there are any plans to drop bootsplash for 11.2 as the bootsplash.org site itself recommends moving over to splashy.
Fedora and Ubuntu seems to have moved to "Plymouth" it supports animated boot splash.
It would be nice to use that for 11.2.
I'm not aware of anyone working on it though.
development seems to be active: http://cgit.freedesktop.org/plymouth/log/
I meant working on replacing bootsplash Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
-----Original Message----- From: jigish.gohil@gmail.com [mailto:jigish.gohil@gmail.com] On Behalf Of Jigish Gohil Sent: Saturday, June 13, 2009 8:35 AM To: Stephan Kulow Cc: opensuse-factory@opensuse.org Subject: Re: [opensuse-factory] splashy vs bootsplash
On Sat, Jun 13, 2009 at 12:56 PM, Stephan Kulow<coolo@novell.com> wrote:
On Saturday 13 June 2009 06:45:05 Jigish Gohil wrote:
On Sat, Jun 13, 2009 at 4:13 AM, Jakub Steiner<jimmac@gmail.com> wrote:
I'd like to ask if there are any plans to drop bootsplash for 11.2 as the bootsplash.org site itself recommends moving over to splashy.
Fedora and Ubuntu seems to have moved to "Plymouth" it supports animated boot splash.
It's not true. Ubuntu is going to stick to USplash and not to use Plymouth in future releases.
Just to make you feel sure and make me feel better.
-- Best regards, Jakub 'Livio' Rusinek http://jakubrusinek.pl/
Mandriva 2010 is going to use Plymouth. http://blog.mandriva.com/2009/06/21/mandriva-linux-2010-alpha-1-and-2010-spe cifications/ -- S pozdravom / Best regards, Rasto -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Mon, 2009-06-22 at 10:58 +0200, Rastislav Krupanský wrote:
-----Original Message----- From: jigish.gohil@gmail.com [mailto:jigish.gohil@gmail.com] On Behalf Of Jigish Gohil Sent: Saturday, June 13, 2009 8:35 AM To: Stephan Kulow Cc: opensuse-factory@opensuse.org Subject: Re: [opensuse-factory] splashy vs bootsplash
On Sat, Jun 13, 2009 at 12:56 PM, Stephan Kulow<coolo@novell.com> wrote:
On Saturday 13 June 2009 06:45:05 Jigish Gohil wrote:
On Sat, Jun 13, 2009 at 4:13 AM, Jakub Steiner<jimmac@gmail.com> wrote:
I'd like to ask if there are any plans to drop bootsplash for 11.2 as the bootsplash.org site itself recommends moving over to splashy.
Fedora and Ubuntu seems to have moved to "Plymouth" it supports animated boot splash.
It's not true. Ubuntu is going to stick to USplash and not to use Plymouth in future releases.
Just to make you feel sure and make me feel better.
-- Best regards, Jakub 'Livio' Rusinek http://jakubrusinek.pl/
Mandriva 2010 is going to use Plymouth. http://blog.mandriva.com/2009/06/21/mandriva-linux-2010-alpha-1-and-2010-spe cifications/ Rasto
Sad to admit this as I like openSUSE, but among the list of features that openSUSE users would like to see on next releases, I bet is a better, nicer and cleaner session-manager/pre-login screen. I am not so skilled on this matter, but for example, latest Ubuntu 9.04, which I have installed as guest machine onto my oS 11.1, looks a lot much better than openSUSE! -- Marco <amdturion> SuSE Linux 11.2 Kernel 2.6.30.6-default GNOME 2.26.2 VirtualBox
On 2009/06/26 23:31 (GMT-0300) Marco Calistri composed:
Sad to admit this as I like openSUSE, but among the list of features that openSUSE users would like to see on next releases, I bet is a better, nicer and cleaner session-manager/pre-login screen.
*buntu splashes have usually annoyed me highly, as usually more trouble to eradicate than on other distros. I really don't care what system is used for bootsplash, as long as it's easy to get permanently rid of. It would be nice to have an installer option to have it not installed in the first place. -- "Cast but a glance at riches, and they are gone, for they will surely sprout wings and fly off to the sky like an eagle." Proverbs 23:5 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
2009/6/13 Stephan Kulow <coolo@novell.com>:
On Saturday 13 June 2009 06:45:05 Jigish Gohil wrote:
On Sat, Jun 13, 2009 at 4:13 AM, Jakub Steiner<jimmac@gmail.com> wrote:
I'd like to ask if there are any plans to drop bootsplash for 11.2 as the bootsplash.org site itself recommends moving over to splashy.
Fedora and Ubuntu seems to have moved to "Plymouth" it supports animated boot splash.
It would be nice to use that for 11.2. I'm not aware of anyone working on it though.
splashy supports animated boot splashs too - we use it for suspend. Staying with bootsplash sounds wrong, but then again it's the cheapest solution for now.
Someone needs to do a test with both available solutions and then we need to judge.
Can users/volunteers do it? What is needed to test and how? -- S pozdravom / Best regards, Rasto -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Saturday 13 June 2009 09:40:16 Rastislav Krupanský wrote:
Someone needs to do a test with both available solutions and then we need to judge.
Can users/volunteers do it? What is needed to test and how?
As I'm not aware of anyone working on it, I'm not aware of anything to test - other than testing how to replace bootsplash with splashy and/or plymouth. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sat, 2009-06-13 at 19:12 +0200, Stephan Kulow wrote:
On Saturday 13 June 2009 09:40:16 Rastislav Krupanský wrote:
Someone needs to do a test with both available solutions and then we need to judge.
Can users/volunteers do it? What is needed to test and how?
As I'm not aware of anyone working on it, I'm not aware of anything to test - other than testing how to replace bootsplash with splashy and/or plymouth.
Johannes Engel (CC) already did some initial work and tests with splashy in regard to regular booting. I remember him having problems with parallel booting because the bootsplash interaction is hard coded in /sbin/startpar. Attaching his /etc/rc.splash which worked (at that time) with RUN_PARALLEL=no for reference if someone wants to pick up his work. Regards, Holger
Am Mittwoch 24 Juni 2009 schrieb Holger Macht:
On Sat, 2009-06-13 at 19:12 +0200, Stephan Kulow wrote:
On Saturday 13 June 2009 09:40:16 Rastislav Krupanský wrote:
Someone needs to do a test with both available solutions and then we need to judge.
Can users/volunteers do it? What is needed to test and how?
As I'm not aware of anyone working on it, I'm not aware of anything to test - other than testing how to replace bootsplash with splashy and/or plymouth.
Johannes Engel (CC) already did some initial work and tests with splashy in regard to regular booting. I remember him having problems with parallel booting because the bootsplash interaction is hard coded in /sbin/startpar. Attaching his /etc/rc.splash which worked (at that time) with RUN_PARALLEL=no for reference if someone wants to pick up his work.
OK, I looked into this yesterday and there are some problems: - plymouth is out as it requires DRM and while fedora has tons of drm patches in their kernel I don't see us going there - perhaps 11.3 if everything needed settled in Xorg and kernel. - bootsplash works, but is limiting the artists and is only used for booting, not for suspend. And it has no support for e.g. error boxes and password queries - splashy is from what my experiments easy to fix, it has support for not so useful effects (you can emulate them in bootsplash using mng anims, but you need a tool to create these), displaying errors in truetype fonts and getting password queries. suspend & resume already use it, so we have some experience with it - and a package ready. The problems I faced with splashy are: it flickers one more often than bootsplash as the kernel will setup the framebuffer and detect hardware and _then_ splashy comes up to paint over it. With bootsplash the kernel will display an initial graphic and _then_ the userspace will take over showing a progress bar. And I didn't yet experiment to see how we can go from initrd to booting, but that should be possible - splashy has chroot support. Now I wonder if we can leave the bootsplash kernel patch in and use it only to display the initial graphic. My experiments were with a vanilla kernel. Oppinions? Volunteers? :) Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Thu, Jul 30, 2009 at 09:39:20AM +0200, Stephan Kulow wrote:
Am Mittwoch 24 Juni 2009 schrieb Holger Macht:
On Sat, 2009-06-13 at 19:12 +0200, Stephan Kulow wrote:
On Saturday 13 June 2009 09:40:16 Rastislav Krupanský wrote:
Someone needs to do a test with both available solutions and then we need to judge.
Can users/volunteers do it? What is needed to test and how?
As I'm not aware of anyone working on it, I'm not aware of anything to test - other than testing how to replace bootsplash with splashy and/or plymouth.
Johannes Engel (CC) already did some initial work and tests with splashy in regard to regular booting. I remember him having problems with parallel booting because the bootsplash interaction is hard coded in /sbin/startpar. Attaching his /etc/rc.splash which worked (at that time) with RUN_PARALLEL=no for reference if someone wants to pick up his work.
OK, I looked into this yesterday and there are some problems:
- plymouth is out as it requires DRM and while fedora has tons of drm patches in their kernel I don't see us going there - perhaps 11.3 if everything needed settled in Xorg and kernel. - bootsplash works, but is limiting the artists and is only used for booting, not for suspend. And it has no support for e.g. error boxes and password queries - splashy is from what my experiments easy to fix, it has support for not so useful effects (you can emulate them in bootsplash using mng anims, but you need a tool to create these), displaying errors in truetype fonts and getting password queries. suspend & resume already use it, so we have some experience with it - and a package ready.
The problems I faced with splashy are: it flickers one more often than bootsplash as the kernel will setup the framebuffer and detect hardware and _then_ splashy comes up to paint over it. With bootsplash the kernel will display an initial graphic and _then_ the userspace will take over showing a progress bar. And I didn't yet experiment to see how we can go from initrd to booting, but that should be possible - splashy has chroot support.
Now I wonder if we can leave the bootsplash kernel patch in and use it only to display the initial graphic. My experiments were with a vanilla kernel. Oppinions? Volunteers? :)
If that's all you want, they why not use what we are doing in the Moblin images, which is no kernel patch, and just the framebuffer in userspace? Much simpler and faster, and no kernel changes needed. thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Am Donnerstag 30 Juli 2009 schrieb Greg KH:
If that's all you want, they why not use what we are doing in the Moblin images, which is no kernel patch, and just the framebuffer in userspace? Much simpler and faster, and no kernel changes needed.
splashy _is_ framebuffer in userspace. But the flicker comes from the initrd setting up the framebuffer and the kernel blubbering before - but "quiet" makes that less of a problem. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Thu, Jul 30, 2009 at 05:38:11PM +0200, Stephan Kulow wrote:
Am Donnerstag 30 Juli 2009 schrieb Greg KH:
If that's all you want, they why not use what we are doing in the Moblin images, which is no kernel patch, and just the framebuffer in userspace? Much simpler and faster, and no kernel changes needed.
splashy _is_ framebuffer in userspace. But the flicker comes from the initrd setting up the framebuffer and the kernel blubbering before - but "quiet" makes that less of a problem.
Yes, on Moblin we got rid of the flicker. Well, I hope so, it keeps coming back, and people keep stomping on the bugs. But it is possible to do. thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Thu, 30 Jul 2009, Stephan Kulow wrote:
Am Donnerstag 30 Juli 2009 schrieb Greg KH:
If that's all you want, they why not use what we are doing in the Moblin images, which is no kernel patch, and just the framebuffer in userspace? Much simpler and faster, and no kernel changes needed.
splashy _is_ framebuffer in userspace. But the flicker comes from the initrd setting up the framebuffer and the kernel blubbering before - but "quiet" makes that less of a problem.
Well, with a kernel that skips mode setting I got it flicker free until init starts. The bootloader already can set a mode and load an image. Steffen -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Stephan Kulow wrote:
OK, I looked into this yesterday and there are some problems:
- plymouth is out as it requires DRM and while fedora has tons of drm patches in their kernel I don't see us going there - perhaps 11.3 if everything needed settled in Xorg and kernel. As far as I can see for intel chips the required work is already in kernel and X.Org and settled. For radeon chips upto and including r600(?) the respective work is in the staging area of the kernel (correct me please if that is wrong, Greg).
- bootsplash works, but is limiting the artists and is only used for booting, not for suspend. And it has no support for e.g. error boxes and password queries - splashy is from what my experiments easy to fix, it has support for not so useful effects (you can emulate them in bootsplash using mng anims, but you need a tool to create these), displaying errors in truetype fonts and getting password queries. suspend & resume already use it, so we have some experience with it - and a package ready.
I agree with you. However, splashy needs an fb console. Thus my question would be, if we can use the fb device created by the KMS drivers for the devices mentioned above. That would guarantee a smooth transition without flickering to the X.Org display. For other devices the VGA fb console should do the trick.
The problems I faced with splashy are: it flickers one more often than bootsplash as the kernel will setup the framebuffer and detect hardware and _then_ splashy comes up to paint over it. With bootsplash the kernel will display an initial graphic and _then_ the userspace will take over showing a progress bar. And I didn't yet experiment to see how we can go from initrd to booting, but that should be possible - splashy has chroot support.
Can we keep the kernel quiet until fb console is set up? That would get rid of this problem.
Now I wonder if we can leave the bootsplash kernel patch in and use it only to display the initial graphic. My experiments were with a vanilla kernel. Oppinions? Volunteers? :)
To be honest I would try to get rid of that ASAP in favor of the suggestion above. Cheers, Johannes P.S.: Please only use the email address jcnengel@googlemail.com and not wasabgeben@googlemail.com, since the second one is not my personal address. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Am Freitag 31 Juli 2009 schrieb Johannes Engel:
I agree with you. However, splashy needs an fb console. Thus my question would be, if we can use the fb device created by the KMS drivers for the devices mentioned above. That would guarantee a smooth transition without flickering to the X.Org display. For other devices the VGA fb console should do the trick.
I'm not aware of any plans to make KMS default - and my own experience with the 965GM don't really hint we should change that ;(
The problems I faced with splashy are: it flickers one more often than bootsplash as the kernel will setup the framebuffer and detect hardware and _then_ splashy comes up to paint over it. With bootsplash the kernel will display an initial graphic and _then_ the userspace will take over showing a progress bar. And I didn't yet experiment to see how we can go from initrd to booting, but that should be possible - splashy has chroot support.
Can we keep the kernel quiet until fb console is set up? That would get rid of this problem.
Actually "quiet" is the default already, but you still some kind of flicker when my laptop goes from whatever mode grub uses into a black 1024x786x16 and then into blue splashy. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Fri, Jul 31, 2009 at 12:59:24PM +0200, Stephan Kulow wrote:
Am Freitag 31 Juli 2009 schrieb Johannes Engel:
I agree with you. However, splashy needs an fb console. Thus my question would be, if we can use the fb device created by the KMS drivers for the devices mentioned above. That would guarantee a smooth transition without flickering to the X.Org display. For other devices the VGA fb console should do the trick.
I'm not aware of any plans to make KMS default - and my own experience with the 965GM don't really hint we should change that ;(
It's the default on Moblin, which is using the 2.6.30 kernel right now :) thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Am Freitag 31 Juli 2009 schrieb Greg KH:
On Fri, Jul 31, 2009 at 12:59:24PM +0200, Stephan Kulow wrote:
Am Freitag 31 Juli 2009 schrieb Johannes Engel:
I agree with you. However, splashy needs an fb console. Thus my question would be, if we can use the fb device created by the KMS drivers for the devices mentioned above. That would guarantee a smooth transition without flickering to the X.Org display. For other devices the VGA fb console should do the trick.
I'm not aware of any plans to make KMS default - and my own experience with the 965GM don't really hint we should change that ;(
It's the default on Moblin, which is using the 2.6.30 kernel right now
:)
It might work fine for hardware supported by moblin Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Am Freitag, 31. Juli 2009 12:59:24 schrieb Stephan Kulow:
Am Freitag 31 Juli 2009 schrieb Johannes Engel:
I agree with you. However, splashy needs an fb console. Thus my question would be, if we can use the fb device created by the KMS drivers for the devices mentioned above. That would guarantee a smooth transition without flickering to the X.Org display. For other devices the VGA fb console should do the trick.
I'm not aware of any plans to make KMS default - and my own experience with the 965GM don't really hint we should change that ;(
I hope I can override this locally and activate KMS? cya, Karsten -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Fri, Jul 31, 2009 at 06:00:40PM +0200, Karsten König wrote:
Am Freitag, 31. Juli 2009 12:59:24 schrieb Stephan Kulow:
Am Freitag 31 Juli 2009 schrieb Johannes Engel:
I agree with you. However, splashy needs an fb console. Thus my question would be, if we can use the fb device created by the KMS drivers for the devices mentioned above. That would guarantee a smooth transition without flickering to the X.Org display. For other devices the VGA fb console should do the trick.
I'm not aware of any plans to make KMS default - and my own experience with the 965GM don't really hint we should change that ;(
I hope I can override this locally and activate KMS?
The module parameter to the 915 driver will allow you to do this. thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Am Freitag 31 Juli 2009 schrieb Karsten König:
Am Freitag, 31. Juli 2009 12:59:24 schrieb Stephan Kulow:
Am Freitag 31 Juli 2009 schrieb Johannes Engel:
I agree with you. However, splashy needs an fb console. Thus my question would be, if we can use the fb device created by the KMS drivers for the devices mentioned above. That would guarantee a smooth transition without flickering to the X.Org display. For other devices the VGA fb console should do the trick.
I'm not aware of any plans to make KMS default - and my own experience with the 965GM don't really hint we should change that ;(
I hope I can override this locally and activate KMS?
You can boot with i915.modeset=1 Greeings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Heya Am Montag, 3. August 2009 10:52:53 schrieb Stephan Kulow:
I hope I can override this locally and activate KMS?
You can boot with i915.modeset=1
Unknown kernel option when starting on 11.2 =( ###Don't change this comment - YaST2 identifier: Original name: linux### title openSUSE 11.2 root (hd0,6) kernel /boot/vmlinuz-2.6.31-rc6-3-default root=/dev/disk/by-id/ata- WDC_WD2500BEVS-08VAT1_WD-WXEX08CC0365-part7 resume=/dev/disk/by-id/ata- WDC_WD2500BEVS-08VAT1_WD-WXEX08CC0365-part2 splash=silent quiet showopts i915.modeset=1 initrd /boot/initrd-2.6.31-rc6-3-default Karsten -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Am Sonntag 23 August 2009 schrieb Karsten König:
Heya
Am Montag, 3. August 2009 10:52:53 schrieb Stephan Kulow:
I hope I can override this locally and activate KMS?
You can boot with i915.modeset=1
Unknown kernel option when starting on 11.2 =(
It says that, because it's a modprobe option. Don't worry :) Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Mon, Aug 24, 2009 at 02:00:27PM +0200, Stephan Kulow wrote:
Am Sonntag 23 August 2009 schrieb Karsten K\366nig:
Heya
Am Montag, 3. August 2009 10:52:53 schrieb Stephan Kulow:
I hope I can override this locally and activate KMS?
You can boot with i915.modeset=1
Unknown kernel option when starting on 11.2 =(
It says that, because it's a modprobe option. Don't worry :)
To be a bit more precise: The situation with kms is rather unsatisfying (this is not an opensuse problem but a design-problem with Linux module handling). Here's the receipt for the generation of unhappy users: 1 If you want to add a module parameter for a specific module, you can do so at kernel boot time. In that case, it has the format <modulename>.<parameter>. 2 If you specify an invalid, i.e. non-existant parameter name, the module will not load. 3 Make KMS a compile time option with a parameter name that only exists if the KMS option has been compiled in. Now someone needs the option to disable KMS and adds that line to the kernel boot options. In case your kernel has been compiled with KMS, things go as expected. If, for whatever reason, you change to a kernel that has KMS disabled, the module will *always* fail to load at all. Fantastic design. Ciao Joerg -- Joerg Mayer <jmayer@loplof.de> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Fri, Jul 31, 2009 at 11:49:19AM +0100, Johannes Engel wrote:
Stephan Kulow wrote:
OK, I looked into this yesterday and there are some problems:
- plymouth is out as it requires DRM and while fedora has tons of drm patches in their kernel I don't see us going there - perhaps 11.3 if everything needed settled in Xorg and kernel. As far as I can see for intel chips the required work is already in kernel and X.Org and settled. For radeon chips upto and including r600(?) the respective work is in the staging area of the kernel (correct me please if that is wrong, Greg).
Well, it's not really in the staging area, but it is covered by the CONFIG_STAGING option, if that means anything or not. But it's not "settled" by any means, a big update just went into the kernel 2 days ago, which is quite late on this release cycle.
- bootsplash works, but is limiting the artists and is only used for booting, not for suspend. And it has no support for e.g. error boxes and password queries - splashy is from what my experiments easy to fix, it has support for not so useful effects (you can emulate them in bootsplash using mng anims, but you need a tool to create these), displaying errors in truetype fonts and getting password queries. suspend & resume already use it, so we have some experience with it - and a package ready.
I agree with you. However, splashy needs an fb console. Thus my question would be, if we can use the fb device created by the KMS drivers for the devices mentioned above. That would guarantee a smooth transition without flickering to the X.Org display. For other devices the VGA fb console should do the trick.
The problems I faced with splashy are: it flickers one more often than bootsplash as the kernel will setup the framebuffer and detect hardware and _then_ splashy comes up to paint over it. With bootsplash the kernel will display an initial graphic and _then_ the userspace will take over showing a progress bar. And I didn't yet experiment to see how we can go from initrd to booting, but that should be possible - splashy has chroot support.
Can we keep the kernel quiet until fb console is set up? That would get rid of this problem.
Yes, that's easy to do, we do it for moblin. Just add "quiet" to the boot command line. thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Le samedi 13 juin 2009, à 10:15 +0530, Jigish Gohil a écrit :
On Sat, Jun 13, 2009 at 4:13 AM, Jakub Steiner<jimmac@gmail.com> wrote:
I'd like to ask if there are any plans to drop bootsplash for 11.2 as the bootsplash.org site itself recommends moving over to splashy.
Fedora and Ubuntu seems to have moved to "Plymouth" it supports animated boot splash.
If people test plymouth on openSUSE, please add notes on https://features.opensuse.org/305493 where this feature is tracked :-) Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Le samedi 13 juin 2009, à 10:15 +0530, Jigish Gohil a écrit :
On Sat, Jun 13, 2009 at 4:13 AM, Jakub Steiner<jimmac@gmail.com> wrote:
I'd like to ask if there are any plans to drop bootsplash for 11.2 as the bootsplash.org site itself recommends moving over to splashy.
Fedora and Ubuntu seems to have moved to "Plymouth" it supports animated boot splash.
It's not true. Ubuntu is going to stick to USplash and not to use Plymouth in future releases. Just to make you feel sure and make me feel better. -- Best regards, Jakub 'Livio' Rusinek http://jakubrusinek.pl/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Dňa Sat, 13 Jun 2009 20:37:49 +0200 Vincent Untz <vuntz@opensuse.org> napísal(a):
Le samedi 13 juin 2009, à 10:15 +0530, Jigish Gohil a écrit :
On Sat, Jun 13, 2009 at 4:13 AM, Jakub Steiner<jimmac@gmail.com> wrote:
I'd like to ask if there are any plans to drop bootsplash for 11.2 as the bootsplash.org site itself recommends moving over to splashy.
Fedora and Ubuntu seems to have moved to "Plymouth" it supports animated boot splash.
If people test plymouth on openSUSE, please add notes on https://features.opensuse.org/305493 where this feature is tracked :-)
Vincent
Some packages available for openSUSE Factory. http://download.opensuse.org/repositories/home:/etrash:/plymouth/openSUSE_Fa... -- S pozdravom / Best regards, Rasto -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
2009/7/20 Rastislav Krupanský <rastislav.krupansky@gmail.com>:
Dňa Sat, 13 Jun 2009 20:37:49 +0200 Vincent Untz <vuntz@opensuse.org> napísal(a):
If people test plymouth on openSUSE, please add notes on https://features.opensuse.org/305493 where this feature is tracked :-)
Some packages available for openSUSE Factory.
http://download.opensuse.org/repositories/home:/etrash:/plymouth/openSUSE_Fa...
Those packages are very experimental. Not sure if they will work at all. Haven't had time to try them myself. Vacation you know. But now I'm back and will try to give them some more time and love. Warm Regards, Claes Backstrom (a.k.a etrash) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Am Samstag 13 Juni 2009 schrieb Jakub Steiner:
I'd like to ask if there are any plans to drop bootsplash for 11.2 as the bootsplash.org site itself recommends moving over to splashy.
OK, I give up on splashy. It just doesn't work too well, so I guess 11.2 will be bootsplash and I'm glad I can finally answer your question :) Perhaps 11.3 is plymouth then :) Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (15)
-
Claes Backstrom -
Felix Miata -
Greg KH -
Holger Macht -
Jakub 'Livio' Rusinek -
Jakub Steiner -
Jigish Gohil -
Joerg Mayer -
Johannes Engel -
Karsten König -
Marco Calistri -
Rastislav Krupanský -
Steffen Winterfeldt -
Stephan Kulow -
Vincent Untz