On Wed, Apr 18, 2012 at 06:17:21PM +0200, Bruno Friedmann wrote:

On Wednesday 18 April 2012 09.53:23 Raymond Wooninck wrote:

...

Hi Michael,

On Wednesday, April 18, 2012, Michael Chang wrote:

...

* Graphical boot menu:

Current plan is

1. list of all modes and use highest (from fbresolution or vbemode output) as default, for selection in options dialog 2. use background image (instead of grub2's theme), default to the path of opensuse background .. need to decide the path and the art work, or could we reuse any Polymouth image, Raymond ?

The background image use, should be coming from the openSUSE artwork. This was the case with the Grub/Splashy combination and should be followed through with Grub2/Splashy or Grub2/Plymouth. What I found is that Grub2 will automatically resize the image if it is not fitting.

As I've tested a lot the combination of grub2/plymouth on a full / encrypted with luks, what I can said is you need a new copy of the background in /boot otherwise grub2 has no way to display it

I've tried to symlink in plymouth themes the image located in /boot/grub2 (where I put it manually) but this seems not the work. The background is located in the initrd.

Having multiple time the background is bad for disk space (who care) but also then the video card has to reload several times the same images ...

Any thoughts on this ?

How about this? We create a grub2 subpackage, grub2-gfxterm and put background image in this package. We install it to /boot/grub2 folder. This seems to solve the problem but the drawback is that not link to Plymouth themes. Or the other way round, a Plymouth theme package installs this background image to /boot/grub2 and edits /etc/defaulf/grub:GRUB_BACKGROUND to make the settings effective. Regards, Michael

...

-- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch

openSUSE Member & Ambassador GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Wed, Apr 18, 2012 at 05:15:05PM -0400, Brian K. White wrote:

On 4/18/2012 3:53 AM, Raymond Wooninck wrote:

...

Hi Michael,

On Wednesday, April 18, 2012, Michael Chang wrote:

...

* Graphical boot menu:

Current plan is

1. list of all modes and use highest (from fbresolution or vbemode output) as default, for selection in options dialog 2. use background image (instead of grub2's theme), default to the path of opensuse background .. need to decide the path and the art work, or could we reuse any Polymouth image, Raymond ?

The background image use, should be coming from the openSUSE artwork. This was the case with the Grub/Splashy combination and should be followed through with Grub2/Splashy or Grub2/Plymouth. What I found is that Grub2 will automatically resize the image if it is not fitting.

...

For 1, the concern for me is that fbresoltuin make yast2 bootloader to depend on splash package and vbemode may not detect some special native mode (but we can reuse vgamode in yast for detecting the modes).

I think that the better way is to extract the fbresolution program (it is only a single file from the splash package and compile it inside the grub2 package. You could then create a separate package (e.g. grub2-graphical) that contains this program and executes the necessary steps to get a graphical Grub2 screen.

Regards

Raymond

Might want to apply a tiny patch to get rid of the hard coded black border around gfxterm:

https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/567226 Comment 12 https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/567226/comments/12

It's most noticeable when you tried to take the pains to make the same background, perfectly sized and full native resolution, from grub to splash to xdm to desktop, only it's not perfectly possible because grub eats a 10 pixel border on all 4 sides.

Thanks for patch. I'll give it a try. The black border is unnecessary and, like you suggested, bad for user if they want more seamless booting experience. Thanks, Michael

(no SR from me because I'm not using grub2 nor any graphical booting nor desktops on any suse boxes at the moment and I don't want to SR anything I didn't actually do and use. I did do it on an ubuntu system from upstream sources though.)

-- bkw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Thu, 2012-04-19 at 09:52 +0800, Michael Chang wrote:

The question is how do I/we contact the artwork people?

Easy, just send a mail to opensuse-artwork@opensuse.org -- Marcel Kühlhorn freenode: tux93 Have a lot of fun!

On Thu, Apr 19, 2012 at 06:52:36AM +0200, Marcel Kühlhorn wrote:

On Thu, 2012-04-19 at 09:52 +0800, Michael Chang wrote:

...

The question is how do I/we contact the artwork people?

Easy, just send a mail to opensuse-artwork@opensuse.org

Thanks. Good to know. :-) Regards, Michael

-- Marcel Kühlhorn freenode: tux93

Have a lot of fun!

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Thu, Apr 19, 2012 at 07:27:52AM +0200, Bruno Friedmann wrote:

On Thursday 19 April 2012 09.52:08 Michael Chang wrote:

...

On Wed, Apr 18, 2012 at 09:53:23AM +0200, Raymond Wooninck wrote:

...

Hi Michael,

On Wednesday, April 18, 2012, Michael Chang wrote:

...

* Graphical boot menu:

Current plan is

1. list of all modes and use highest (from fbresolution or vbemode output) as default, for selection in options dialog 2. use background image (instead of grub2's theme), default to the path of opensuse background .. need to decide the path and the art work, or could we reuse any Polymouth image, Raymond ?

The background image use, should be coming from the openSUSE artwork. This was the case with the Grub/Splashy combination and should be followed through with Grub2/Splashy or Grub2/Plymouth. What I found is that Grub2 will automatically resize the image if it is not fitting.

Yes. I agree with you that the background images has to be designed to be part of Plymouth nation. This would make boot experience better. The question is how do I/we contact the artwork people?

The resizing to fit entire screen is good to me, or do you think it has any problem?

...

...

For 1, the concern for me is that fbresoltuin make yast2 bootloader to depend on splash package and vbemode may not detect some special native mode (but we can reuse vgamode in yast for detecting the modes).

I think that the better way is to extract the fbresolution program (it is only a single file from the splash package and compile it inside the grub2 package. You could then create a separate package (e.g. grub2-graphical) that contains this program and executes the necessary steps to get a graphical Grub2 screen.

The fbresolution would not be executed in package install scripts, it would be executed by yast bootloader for getting the resolution then asking perl bootloader to write the settings. This resolution, together with other available vbe modes, would be listed in Grub'2 option dialog for selection.

And yes, we may still need a separate package for holding Grub2 graphics artwork and any stuff related with it. :)

Thanks, Michael

...

Regards

Raymond

On the gitorious repo opensuse-art there the basics of the new wallpaper and background. They made it with different kind of ratio for the different kind of screen 16:10, 16:9, 5:4, 4:3

using the high resolution, and with the result of fbresolution, pick the right ratio image name it background and go.

Artist last saturday, promise that I will have final artwork for saturday, but we could already use what exist.

I am cloning the repo .. thanks a lot. With the materials I think now I'm ready to go. Regards, Michael

-- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch

openSUSE Member & Ambassador GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Thu, Apr 19, 2012 at 09:42:35AM +0100, Alin M Elena wrote:

Hi Michael,

I have been playing with grub2-efi... first I run on a macbook pro 7,1, opensuse-factory, plymouth and systemd... in addition nvidia propetary driver I installed grub2-efi in the apple boot/efi partition... the prescribed way... generated my .efi file and then generated a nice grub.cfg file with the -mkconfig tool....

rebooted the machine, no magic needed, a new entry in the refit menu was there. I have boot into it... got the grub2 screen then I choose the opensuse boot... I got the plymouth screen and everything loaded correctly until the X.... There I got a black screen... I checked the xorg log (added in attach) and it showed me x crashed due to missing screens..

Any ideas?

Seems like nvidia driver's problem .. [ 49.373] (EE) NVIDIA(0): Failed to initialize the display subsystem for the NVIDIA [ 49.373] (EE) NVIDIA(0): graphics device! [ 49.373] (EE) NVIDIA(0): Failed to get supported display device(s) [ 49.373] (EE) NVIDIA(0): Failed to initialize dac HAL You can try running nvidia util (nvidia-xconfig?) to generate the config but I doubt that it would still fail. I am not xorg expert and my knowledge for uefi is weak so please consider my comments as JFYI .. :) It's possible that you disable pc bios emulation mode and runs in pure efi mode. The vbios interface for pc bios is no longer available and driver must use EFI defined protocol to communicate with uEFI firmware. This is completely new path for driver and might horribly broken due to it's not well tested .. Does nvidia driver ever work before in this environment? Regards, Michael

regards, Alin

-- Without Questions there are no Answers! ______________________________________________________________________ Alin Marin ELENA Advanced Molecular Simulation Research Laboratory School of Physics, University College Dublin ---- Ardionsamblú Móilíneach Saotharlann Taighde Scoil na Fisice, An Coláiste Ollscoile, Baile Átha Cliath

----------------------------------------------------------------------------------- http://alin.elenaworld.net ______________________________________________________________________

-- Michael Chang Software Engineer Rm. B, 26F, No.216, Tun Hwa S. Rd., Sec.2 Taipei 106, Taiwan, R.O.C +886223760030 mchang@suse.com SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Mon, 23 Apr 2012 18:28:41 -0400 "Brian K. White" wrote:

On 4/19/2012 1:27 AM, Bruno Friedmann wrote:

...

On Thursday 19 April 2012 09.52:08 Michael Chang wrote:

...

On Wed, Apr 18, 2012 at 09:53:23AM +0200, Raymond Wooninck wrote:

...

Hi Michael,

On Wednesday, April 18, 2012, Michael Chang wrote:

...

* Graphical boot menu:

Current plan is

1. list of all modes and use highest (from fbresolution or vbemode output) as default, for selection in options dialog 2. use background image (instead of grub2's theme), default to the path of opensuse background .. need to decide the path and the art work, or could we reuse any Polymouth image, Raymond ?

The background image use, should be coming from the openSUSE artwork. This was the case with the Grub/Splashy combination and should be followed through with Grub2/Splashy or Grub2/Plymouth. What I found is that Grub2 will automatically resize the image if it is not fitting.

Yes. I agree with you that the background images has to be designed to be part of Plymouth nation. This would make boot experience better. The question is how do I/we contact the artwork people?

The resizing to fit entire screen is good to me, or do you think it has any problem?

...

...

For 1, the concern for me is that fbresoltuin make yast2 bootloader to depend on splash package and vbemode may not detect some special native mode (but we can reuse vgamode in yast for detecting the modes).

I think that the better way is to extract the fbresolution program (it is only a single file from the splash package and compile it inside the grub2 package. You could then create a separate package (e.g. grub2-graphical) that contains this program and executes the necessary steps to get a graphical Grub2 screen.

The fbresolution would not be executed in package install scripts, it would be executed by yast bootloader for getting the resolution then asking perl bootloader to write the settings. This resolution, together with other available vbe modes, would be listed in Grub'2 option dialog for selection.

And yes, we may still need a separate package for holding Grub2 graphics artwork and any stuff related with it. :)

Thanks, Michael

...

Regards

Raymond

On the gitorious repo opensuse-art there the basics of the new wallpaper and background. They made it with different kind of ratio for the different kind of screen 16:10, 16:9, 5:4, 4:3

using the high resolution, and with the result of fbresolution, pick the right ratio image name it background and go.

Artist last saturday, promise that I will have final artwork for saturday, but we could already use what exist.

Add 2:1 to that long list of possible ratios. Vaio P is 1600x800

I seem to remember a packaging of gdm (I think it was gdm) on ubuntu a while back that just included a single huge image that was simply centered with no scaling and was always larger than most screens and the excess was just not displayed off the edge of the screen. That way there was no scaling or distorting no matter what the users unpredictable screen shape was, and only one image to include, albeit a large one and couldn't have image features that mattered near the edges or they'd get chopped off.

Maybe the way to go is to use something that generates an image on the spot. Include a few small images and render them like html all relative the the available screen which can't be predicted ahead of time. A la lightdm webkit-greeter.

To me this is all gross to put into initrd anyways but what the hell in for a penny in for a pound. Do it or don't do it (try to put graphics into the boot process, especially when you can no longer assure access to the disk thanks to other wonderful decisions) but if you're going to do it, do it. If you're going to make people swallow the requirements of working graphics at all, then don't worry about ram and storage and network bandwidth. Put everything in there necessary to make it good. Put the entire /usr core OS in there.

It won't work for a lot of people but what you're already doing already doesn't work for a lot of people and you don't care, so what's the problem?

/usr entirely in initrd and entirely in ram thereafter, and not easily/casually modified except by system/package updates, has it's advantages. It could become the new default way all modern distros run the OS and we did it first.

If /usr is moved to RAM, some users with small amounts of RAM (especially older systems) may have problems. How do you account for those? Tom -- Tom Taylor - retired penguin AMD Phenom II x4 955 -- 4GB RAM -- 2x1.5TB sata3 openSUSE 12.1x86_64 openSUSE 12.2x86_64 KDE 4.6.00, FF 7.0 KDE 4.7.2, FF 10.0 claws-mail 3.8.0 registered linux user 263467 linxt-At-comcast-DoT-net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Mon, Apr 23, 2012 at 12:29:34PM +0200, Bruno Friedmann wrote:

On Wednesday 18 April 2012 14.37:24 Michael Chang wrote:

...

TODOs

* Graphical boot menu:

Current plan is

1. list of all modes and use highest (from fbresolution or vbemode output) as default, for selection in options dialog 2. use background image (instead of grub2's theme), default to the path of opensuse background .. need to decide the path and the art work, or could we reuse any Polymouth image, Raymond ?

For 1, the concern for me is that fbresoltuin make yast2 bootloader to depend on splash package and vbemode may not detect some special native mode (but we can reuse vgamode in yast for detecting the modes).

Michael,

New artwork will available soon in factory.

I made some reflexion this week-end and also wait the feedback about getting png as default format for default wallpaper

If we move to this format then plymouth and grub2 will be able to pick those.

Now we have to select the best ratio image 4:3,5:4,16:9,16:10 so extending or shrinking the image will keep a nice aspect ...

Thanks a lot for heading up this. To get those new arts I need to git-pull the arts git repo or they will be packaged ?

My idea would be to create a simple way to select which image to take from an array of resolution and picking the right one according to fbresolution output I believe we should do it with bash as the most low level tools available at install time? Any ideas or comments?

I think we did need to have helper scripts for handling these, and these scripts should packaged together with the images, perhaps a subpackage of grub2 and name grub2-gfxterm-backgrounds .. We can name these images files to follow a template and create them under /boot/grub2/background//-.(png|jpg) /boot/grub2/background/Polymouth/default-1024x768.png /boot/grub2/background/Polymouth/default-800x600.png .. .. /boot/grub2/background/openSUSE/default-1024x768.png /boot/grub2/background/openSUSE/default-800x600.png And the helper scripts should help in listing and getting appropriate backgrounds for us .. $ grub2-background --list-all Polymouth openSUSE $ grub2-background --get Polymouth --res `fbresolution` /boot/grub2/background/openSUSE/1024x768.png PS. output mose close aspect ratio image per the input res Maybe better approach would be see if any free desktop specs we can follow, but I'm not familiar with that to be honest.

In the next few days, I will try to trick one factory install here, and see if plymouth is able to work with a linked png (but I'm pretty sure we will have to patch mkinitrd to copy not the link but the link destination)

ps : for grub2 unfortunately, the selected image has to be copied in /boot otherwise luks / will not allow grub2 to use it. I believe it's too complicated and less errors proof to try to do that only if / is encrypted, cause /usr can also be separate and encrypted too. So better to have only one rules

Yes. I agree put the images in /boot for all the circumstances, as these images has to be accessed in pre-os stage, the best place for them would be /boot.

ps2 : If you need the artwork png for test for grub2 and plymouth you can pick a demo here http://dl.dropbox.com/u/13333867/openSUSE/default-1280x1024.png http://dl.dropbox.com/u/13333867/openSUSE/default-1600x1200.png http://dl.dropbox.com/u/13333867/openSUSE/default-1920x1080.png http://dl.dropbox.com/u/13333867/openSUSE/default-1920x1200.png

Thanks .. I downloaded these pictures. :)

ps3 : Once we know what we want for plymouth branding and grub2 branding, then we will add them to gitorious/art repository and also modify the Base:System:opensuse-branding package

The set-able options for gfxterm would have to be divided into three parts 1. toggle on/off gfxconsole checkbox 2. resolution combo box, list all available res, default to native 3. background combo box, list all availbe backgrounds, defalut to "Polymouth". Item 3 should be what we are discussing now, and would be great to know the proposing here is make sense to go and I (or any one volunteer) could start to work on that. Thanks, Michael

-- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch

openSUSE Member & Ambassador GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Tue, Apr 24, 2012 at 09:43:59PM +0200, Bruno Friedmann wrote:

On Tuesday 24 April 2012 12.53:04 Michael Chang wrote:

...

On Mon, Apr 23, 2012 at 12:29:34PM +0200, Bruno Friedmann wrote:

...

On Wednesday 18 April 2012 14.37:24 Michael Chang wrote:

...

TODOs

* Graphical boot menu:

Current plan is

1. list of all modes and use highest (from fbresolution or vbemode output) as default, for selection in options dialog 2. use background image (instead of grub2's theme), default to the path of opensuse background .. need to decide the path and the art work, or could we reuse any Polymouth image, Raymond ?

For 1, the concern for me is that fbresoltuin make yast2 bootloader to depend on splash package and vbemode may not detect some special native mode (but we can reuse vgamode in yast for detecting the modes).

Michael,

New artwork will available soon in factory.

I made some reflexion this week-end and also wait the feedback about getting png as default format for default wallpaper

If we move to this format then plymouth and grub2 will be able to pick those.

Now we have to select the best ratio image 4:3,5:4,16:9,16:10 so extending or shrinking the image will keep a nice aspect ...

Thanks a lot for heading up this. To get those new arts I need to git-pull the arts git repo or they will be packaged ?

...

My idea would be to create a simple way to select which image to take from an array of resolution and picking the right one according to fbresolution output I believe we should do it with bash as the most low level tools available at install time? Any ideas or comments?

I think we did need to have helper scripts for handling these, and these scripts should packaged together with the images, perhaps a subpackage of grub2 and name grub2-gfxterm-backgrounds ..

We can name these images files to follow a template and create them under /boot/grub2/background//-.(png|jpg)

/boot/grub2/background/Polymouth/default-1024x768.png /boot/grub2/background/Polymouth/default-800x600.png .. .. /boot/grub2/background/openSUSE/default-1024x768.png /boot/grub2/background/openSUSE/default-800x600.png

And the helper scripts should help in listing and getting appropriate backgrounds for us ..

$ grub2-background --list-all Polymouth openSUSE $ grub2-background --get Polymouth --res `fbresolution` /boot/grub2/background/openSUSE/1024x768.png

PS. output mose close aspect ratio image per the input res

Maybe better approach would be see if any free desktop specs we can follow, but I'm not familiar with that to be honest.

...

In the next few days, I will try to trick one factory install here, and see if plymouth is able to work with a linked png (but I'm pretty sure we will have to patch mkinitrd to copy not the link but the link destination)

ps : for grub2 unfortunately, the selected image has to be copied in /boot otherwise luks / will not allow grub2 to use it. I believe it's too complicated and less errors proof to try to do that only if / is encrypted, cause /usr can also be separate and encrypted too. So better to have only one rules

Yes. I agree put the images in /boot for all the circumstances, as these images has to be accessed in pre-os stage, the best place for them would be /boot.

...

ps2 : If you need the artwork png for test for grub2 and plymouth you can pick a demo here http://dl.dropbox.com/u/13333867/openSUSE/default-1280x1024.png http://dl.dropbox.com/u/13333867/openSUSE/default-1600x1200.png http://dl.dropbox.com/u/13333867/openSUSE/default-1920x1080.png http://dl.dropbox.com/u/13333867/openSUSE/default-1920x1200.png

Thanks .. I downloaded these pictures. :)

...

ps3 : Once we know what we want for plymouth branding and grub2 branding, then we will add them to gitorious/art repository and also modify the Base:System:opensuse-branding package

The set-able options for gfxterm would have to be divided into three parts

1. toggle on/off gfxconsole checkbox 2. resolution combo box, list all available res, default to native 3. background combo box, list all availbe backgrounds, defalut to "Polymouth".

Item 3 should be what we are discussing now, and would be great to know the proposing here is make sense to go and I (or any one volunteer) could start to work on that.

Thanks, Michael

You give me some nice clue, With what is actually existing in -art repository I think there's something possible the way you describe.

Just on point, grub2 is able to resize background normally so to limit the place used in /boot I would release one picture by ratio type and use symlink to the different resolution ...

Don't bother to create links for different resolution (I believe it would be tedious work as we know how many current display supports). Just name the pictures with associcated ratio is fine, let the script to calc and pick the most feasible one for resolution. :)

Also I think the default will be branding-openSUSE (to stay in line with the rest of the branding) plymouth getting a proper openSUSE-branding based on the default wallpaper (which then has to be migrated to png see my other mails)

Yes. In branding-openSUSE is better and makes scence. I use grub2 subpackage is for example and in case no one could help in branding package (I prefer branding package as well). However a grub2 subpackage could be good place for upstream's themes (starfield). We might have not enough time working on openSUSE grub2 theme but would be great to have this upstream one in our distro.

So what I can propose, is trying to build the directory layout, put the stuff in it and then start to check how it behave with your own development ...

Yes. Please let me know what's the layout looks like. I'd expect that's like what we discussed so far. That is they'll be put under /boot/grub2/backgrounds folder and named by aspect ratio. If so that would be no big problem for me as far as I can see.

In parallel, I will start preparing grub2 in the gitorious -art repository and adjust script there to have it build with the rest of the branding ...

Sound good for you?

Yes. Btw I've also started working on gfx menu support on yast. Let's see. :). Thanks, Michael

-- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch

openSUSE Member & Ambassador GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org