[Gensplash]Refuse de me mettre une image(resolu)

[Monrake]

Voilà, dans le but de personnaliser un peu plus ma Gentoo, je me suis dit que je pourrais mettre une super image quand mon gentoo boot ou que je travaille sans démarrer X.

Pour ce faire, j'ai installé splashutils qui est supposé faire ça comme un grand garçon. J'ai suivit les how to present pour faire la configuration. J'ai donc créer le lien entre le dossier du thème et j'ai modifié mon lilo.conf comme un grand garçon.

La seule chose qui marche, c'est que j'arrive à faire changer la résolution, j'ai à présenter le boot en 1024*780 mais il ne veut absolument rien savoir pour ce qui est de mettre une image ou le théme par défaut.

Voici mon lilo.conf :

[colito]

bon alors déjà, mais je suppose que tu l'as déjà fait, y'a des docs très bien faites là dessus...
Je te balance ceci que j'ai trouvé sur internet...Je sais plus où je les ai pris, mais merci à leurs auteurs...
ça m'a personnellement débloqué sur le même problème.


HOWTO fbsplash
From Gentoo-Portage Wiki
Table of contents [hide]
1 Introduction1.1 What is gensplash?1.2 What is fbsplash (framebuffer splash)?1.3 What is a frame buffer device?2 Installing fbsplash and splashutils2.1 Patching the kernel2.2 Configuring / compiling the kernel (manually)2.3 Configuring / compiling the kernel (genkernel users)2.4 Emerging splashutils2.5 Installing the kernel3 Making an initramfs image3.1 What is initramfs?3.2 Compiling the initramfs image directly into the kernel3.3 Loading the initramfs image dynamically at boot time3.4 Creating new gensplash themes3.5 Converting bootsplash themes to gensplash themes3.6 Using self-made gensplash themes4 Configuring your bootloader4.1 Kernel options4.2 Grub configuration - example4.3 Lilo configuration - example5 Adding a background to all consoles6 Gensplash on non-Gentoo distributions6.1 Differences6.2 Additional steps6.3 Need a name for point 37 Troubleshooting7.1 Users with /usr on a separate partition7.2 Background image loading in the middle of the boot process8 References
[edit]
Introduction
First I want say thanks to the gentoo-developer Spock (http://dev.gentoo.org/~spock/) for developing gensplash (fbsplash and splashutils) and vesafb-tng. As an alternative to this how-to, you could try Spock's Gensplash-in-5-easy-steps How-to (http://dev.gentoo.org/~spock/projects/gensplash/gensplash-in-5-easy-steps.php).
[edit]
What is gensplash?
Gensplash is a project started by Spock (http://dev.gentoo.org/~spock/) whose aim is to create a set of tools which could "enrich" the Gentoo boot process (displaying messages, animations, progress bars, etc.).
[edit]
What is fbsplash (framebuffer splash)?
Fbsplash is part of the gensplash project. According to fbsplash's documentation, "the framebuffer splash is a kernel feature that allows displaying a background picture on selected consoles and switching the first console to the so-called silent mode, while booting/rebooting/shutting down the system." The fbsplash device is accessed through the /dev/fbsplash device node. For fbsplash to work, a frame buffer device is required.
[edit]
What is a frame buffer device?
The frame buffer device provides an abstraction for the graphics hardware. It represents the frame buffer of some video hardware and allows application software to access the graphics hardware through a well-defined interface, so the software doesn't need to know anything about the low-level (hardware register) stuff. The device is accessed through special device nodes, usually located in the /dev directory, i.e. /dev/fb*.
There are many different frame buffer devices.
1. Some of them are generic frame buffer devices that can be used with various graphics cards:
o vesafb (vesa frame buffer);
o vesafb-tng (vesa frame buffer - the next generation).
2. Some are graphics-card-specific; examples include:
o rivafb (may be used with nvidia cards);
o radeonfb (may be used with ati cards).
Fbsplash should work with any of these frame buffer devices (in fact, it should work with any device that provides 8/15/16/24/32bpp directcolor/pseudocolor modes).
[edit]
Installing fbsplash and splashutils
In the example below the vesafb-tng frame buffer device is used. Also, it is assumed that Gentoo is your distribution of choice.
[edit]
Patching the kernel
First make sure you have the fbsplash and vesafb-tng patches installed into your kernel. The gentoo-dev-sources version 2.6.8-r1 and higher should have these patches already installed. If you don't have these patches, you can get them from Spock's homepage (http://dev.gentoo.org/~spock/) and you can install them following the instructions on his page.
[edit]
Configuring / compiling the kernel (manually)
# cd /usr/src/linux
You may want to make sure that no files from previous compilations are in your kernel directory:
# make mrproper
Now configure your kernel:
# make menuconfig
First include the vesafb-tng frame buffer support in your kernel by choosing the options below (you can skip this step if you already configured a framebuffer driver besides vesa-tng, eg. i810fb):
Device Drivers > Graphics support:
[*] Support for frame buffer devices
<*> VESA VGA graphics support
VESA driver type (vesafb-tng) --->
Then you'll need fbsplash support in your kernel:
Device Drivers > Graphics support > Console display driver support:
<*> Framebuffer Console support
Device Drivers > Graphics support:
[*] Support for the framebuffer splash (NEW)
If you want to load the initramfs image dynamically at boot (please see Making an initramfs image (http://gentoo-wiki.com/HOWTO_fbsplash#Making_an_initramfs_image) chapter on this howto for details) later on, you have to enable the options specified below are selected. If you don't know what to do, enable them anyhow (it won't hurt):
Device Drivers > Block devices:
<*> RAM disk support
(4096) Default RAM disk size (kbytes) (NEW)
[*] Initial RAM disk (initrd) support
After you have configured your kernel, compile it (warning: this step is essential before installing splashutils). 'make' will compile both your kernel image ('make bzImage') and your modules ('make modules'):
# make
[edit]
Configuring / compiling the kernel (genkernel users)
Work in progress...
[edit]
Emerging splashutils
Now it's time to emerge splashutils. The splashutils are the binaries that are used to load the images (and to decode jpeg, png, etc).
Splashutils is now marked as stable on x86, so you can simply emerge it:
# emerge splashutils
Make sure, that /usr/src/linux points to sources with the patch installed.
[edit]
Installing the kernel
Now you have prepared your kernel and prepared your system to show a splash screen, so go ahead and finish up the compilation and installation of your new kernel using
If /boot is on a separate partition, mount it first:
# mount /boot
Then install the modules and the kernel image:
# make modules_install
# make install
[edit]
Making an initramfs image
The above instructions (and the next part of this howto, Configuring your bootloader (http://gentoo-wiki.com/HOWTO_fbsplash#Configuring_your_bootloader)) should be sufficient to get a splash screen after your kernel has booted. However, if you'd like to get your sexy background picture to appear earlier (right after your frame buffer device - vesafb-tng in our case - is initialized), you'll have to use initramfs.
[edit]
What is initramfs?
(Quoting Spock (http://dev.gentoo.org/~spock/)): "Initramfs (initial ramfs) is a chunk of code that unpacks the compressed cpio image midway through the kernel boot process. The files contained within that image are then used to populate the root filesystem. Initramfs is a part of a bigger concept called 'early-userspace'".
Now, in order to use initramfs, an initramfs image has to be created. An initramfs image should contain:
1. the pictures to be displayed as splash screen;
2. the necessary config files;
3. a userspace helper (splash_helper) utility.
The pictures and config files (things mentioned in 1 and 2 above) constitute a gensplash theme.
There are two ways of using the initramfs image:
1. compiling the initramfs image directly into the kernel;
2. loading the initramfs image dynamically at boot time (using the 'initial ram disk' - initrd).
You can choose whichever you like (the second one - using initrd - might seem a bit more convenient).
[edit]
Compiling the initramfs image directly into the kernel
First, delete the present initramfs image:
# rm /usr/src/linux/usr/initramfs_data.cpio.gz
Next, you'll have to create a new initramfs image containing the pictures, configs and the userspace helper. It is very easy using the utility splash_geninitramfs (it was installed when emerging splashutils). It is similar to the 'splash' utility used by bootsplash.
# splash_geninitramfs -v -g /usr/src/linux/usr/initramfs_data.cpio.gz -r 1024x768 emergence
Compiling the initramfs image directly into the kernel has the disadvantage that you'll need to rebuild you kernel (that step is not required when using the second option - initrd):
# cd /usr/src/linux
# touch usr/initramfs_data.cpio.gz
# make bzImage
# mount /boot
# make install
[edit]
Loading the initramfs image dynamically at boot time
This option is almost identical to compiling the initramfs image directly into your kernel. The only difference is that, instead of creating the image inside your kernel (and then compiling it with 'make' and copying the whole kernel to the /boot partition with 'make install'), you create the initramfs image as a stand-alone file (the initrd file). So here you will not have to rebuild your kernel. You will have to, however, specify an additional line in your boot loader config (so that it knows it should load the initrd file). That will be done in the next part of this how-to.
So the only thing you have to do here is use splash_geninitramfs to generate an initrd file (that contains the pictures, configs and the userspace helper):
# mount /boot
# splash_geninitramfs -v -g /boot/fbsplash-emergence-1024x768 -r 1024x768 emergence
As you can see, the file is generated inside the /boot partition (directory).
However, quoting Spock (https://forums.gentoo.org/viewtopic.php?p=1488636#1488636), "you can't append initramfs data to an initrd image". Consequently, this option may not be used by the genkernel users since genkernel creates its own initrd image used during the boot process. Unless you change kernel and initrd line in grub.conf from:
root=/dev/ram0 real_root=/dev/$ROOT
initrd (hd0,0)/boot/initrd
to:
root=/dev/$ROOT
initrd (hd0,0)/boot/fbsplash-emergence-1024x768
[edit]
Creating new gensplash themes
The standard splash image 'emergence' and its config files are located in /etc/splash/emergence.
If you want to create a new gensplash theme (let's call it 'newtheme'), you must:
1. create the theme directory inside /etc/splash:
# mkdir /etc/splash/newtheme
2. create the 'images' directory inside /etc/splash/newtheme:
# mkdir /etc/splash/newtheme/images
and copy the images (png/jpg files) you would like to use to that directory.
3. create the necessary config files. The config files should have an *.cfg extension and must be saved in the root path of your theme (/etc/splash/newtheme). To have an idea how they should look like, have a look at the config files for the default theme ('emergence'):
# ls -l /etc/splash/emergence/
images/
1024x768.cfg
1280x1024.cfg
800x600.cfg
It is particularly important to make sure the 'jpeg=' and 'silentjpeg=' options (in the *.cfg files) point to the correct image paths (inside the /etc/splash/newtheme/images directory). If you don't use jpeg images, change the jpeg options in 'pic=' and 'silentpic='.
For a more in-depth understanding of the fbsplash theme format, please refer to splashutils' documentation:
# less /usr/doc/splashutils-version/theme_format.gz
[edit]
Converting bootsplash themes to gensplash themes
Again, Spock has provided a handy utility called bootsplash2fbsplash (it's a script that comes with splashutils) to make converting bootsplash themes to the gensplash format easy.
Say you have the bootspash theme 'gentoo-highquality' located in /etc/bootsplash. All you have to do is issue the following command (as root):
# bootsplash2fbsplash gentoo-highquality
and the utility will magically create a gensplash-compatible theme inside the /etc/splash directory (/etc/splash/gentoo-highquality) with all the required files.
[edit]
Using self-made gensplash themes
To generate a new image from the theme you've just created (called 'newtheme', using the 1280x1024 resolution), you will have to use (surprise, surprise) splash_geninitramfs.
If you decided to compile the image into the kernel (the first option):
# splash_geninitramfs -v -g /usr/src/linux/usr/initramfs_data.cpio.gz -r 1280x1024 newtheme
# cd /usr/src/linux
# touch usr/initramfs_data.cpio.gz
# make bzImage
# mount /boot
# make install
If you use the initrd file (the second option):
# mount /boot
# splash_geninitramfs -v -g /boot/fbsplash-newtheme-1280x1024 -r 1280x1024 newtheme
Here is what the splash_geninitramfs options mean:
-v tells splash_geninitramfs to go into verbose mode
-g tells splash_geninitramfs to generate the initramfs image file
(/usr/src/linux/usr/initramfs_data.cpio.gz
or /boot/fbsplash-newtheme-1280x1024)
-r tells splash_geninitramfs to use the 1280x1024 resolution
-the 'newtheme' part tells splash_geninitramfs to look in
the /etc/splash/newtheme directory for the .cfg files
To see a description of all splash_geninitramfs' options:
# splash_geninitramfs --help
The last point in this part of the how-to is a useful tip from the splashutils' docs:
If you want to save some memory and you aren't planning to use all
available resolutions, you'd probably want to copy the config file and
the background pics only for the one resolution you use.
Now it's high time you configured your bootloader.
[edit]
Configuring your bootloader
[edit]
Kernel options
Here are the options that have to be included in the grub/lilo configuration files:
1. an option which specifies the frame buffer device is essential. Here is how it can look for the vesafb-tng driver:
video=vesafb:ywrap,mtrr,1024x768-16@85
In the above example, we specify that we would like to use the 1024x768 resolution, 16bpp and a refresh rate of 85Hz. If you use vesafb-tng, you also have to remove the 'vga=' option from your bootloader config file (it is only used by the 'normal' vesafb frame buffer device):
# DO NOT set the 'vga=' option for vesafb-tng (if it is set, remove it):
vga=791
vga=0x517
2. fbsplash requires its own option:
splash=verbose,theme:emergence
First the fbsplash mode is chosen (the 'verbose' mode in the above example). Here's an extract from the fbsplash docs: "The framebuffer splash can work in two modes: verbose and silent. The first one means "console with a background image". The latter one is a concept first introduced in bootsplash. When silent mode is active, the console is switched to a graphic mode and no text is displayed. It's up to the userspace programs to display something (a progress bar for example) on the screen".
The second part of the fbsplash boot loader option allows you to specify which theme should be used (in the above example, it is the default theme 'emergence').
Both the mode and the theme have to be specified for fbsplash to work.
3. if you decided to use an initrd file (see previous chapter - Loading the initramfs image dynamically at boot time (http://gentoo-wiki.com/HOWTO_fbsplash#Loading_the_initramfs_image_dynamically_at_boot_time)), you will need to place an additional option in the boot loader config:
initrd /boot/fbsplash-emergence-1024x768 # Grub
initrd = /boot/fbsplash-emergence-1024x768 # Lilo
In the above example, it is assumed that the name of the initrd file is fbsplash-emergence-1024x768 (and it resides in the /boot partition or directory).
Below are examples for both grub and lilo config files. It is assumed that the custom theme 'newtheme', a resolution of 1280x1024, 32bpp and a refresh rate of 70Hz are used. The specified fbsplash mode is 'silent' and an initrd file is used (hence the additional 'initrd' line).
[edit]
Grub configuration - example
title Gentoo
root (hd0,0)
kernel (hd0,0)/kernel-2.6.8-gentoo-r1 root=/dev/hda3 video=vesafb:ywrap,mtrr,1280x1024-32@70 splash=silent,theme:newtheme
initrd (hd0,0)/fbsplash-newtheme-1280x1024
Replace (hd0,0) with your boot partition (or, if there is no separate boot partition, use the root partition number and prepend /boot to the kernel and initrd paths)
Genkernel users should use something like this for the kernel line (all in one line):
kernel (hd0,0)/kernel-2.6.8-gentoo-r1 init=/linuxrc root=/dev/hda3 video=vesafb:ywrap,mtrr,1280x1024-32@70 splash=silent,theme:newtheme

[edit]
Lilo configuration - example
image=/boot/kernel-2.6.8-gentoo-r1
label = "Gentoo"
root = /dev/hda3
append="video=vesa:ywrap,mtrr,1280x1024-32@70 splash=silent,theme:newtheme"
read-only
initrd = /boot/fbsplash-newtheme-1280x1024
Do not forget to run lilo after you have adjusted the lilo.conf file:
# mount /boot
# lilo -v
After all this work and a reboot you should have a graphical boot.
[edit]
Adding a background to all consoles
If you want all consoles to have a splash screen (the verbose mode pictures) - not only the first one - then edit /etc/conf.d/splash to select the options you would like and then add splash to your default bootlevel:
# rc-update add splash default
If you were using bootsplash, remove it from your runlevels:
# rc-update del bootsplash
[edit]
Gensplash on non-Gentoo distributions
(Jakub) I believe this section should consist of three parts:
Introduction: Gensplash will work on other distributions.
1. What needs to be done in a different way (compared to the steps of this howto) - e.g. inability to use emerge. This should apply to all non-Gentoo distributions.
2. What additional steps need to be taken - e.g. modification of startup scripts. This should also apply to all non-Gentoo distributions.
3. Some distribution-specific deviations from 1 and 2 (should they exist).
[edit]
Differences
1. Patching the kernel - necessary. Won't probably use gentoo-dev-sources (although, of course, possible)
2. Configure/compile kernel - cannot use genkerel.
3. Installing splashutils - no package.keywords, no emerge. By hand. Supply direct download link. Suggestion that switching to Gentoo would be a good idea.
4. Adding the splash screen to all consoles (and removal of bootpslash) - probably depends on the distribution. The Gentoo way won't work (obviously).
[edit]
Additional steps
Modification of startup scripts required to get the progressbar working. Two possible scenarios:
· people were using bootsplash (easier)
· people were not using bootsplash (more difficult)
[edit]
Need a name for point 3
The Debian function mentioned by Spock on forums.gentoo.org.
[edit]
Troubleshooting
[edit]
Users with /usr on a separate partition
If you are using splashutils version 0.9-pre08 or later and have /usr on a separate partition, gensplash should work out of the box (without any modifications). If you, however, use an older version of splashutils and, for some bizarre reason, stubbornly refuse to update it, please use the instructions below.
The program and libraries that splash_util needs to run fbset and display your splash image are kept in /usr/bin and /usr/lib. So if you have these on separate partitions from / (such as a RAID or LVM2 partition), they may not be available (mounted) at the time splash_utils needs them (when using the older version of splashutils), and you won't see your beautiful splash.
The solution? Copy them to somewhere that they are available, as follows (with thanks to aslocum and the Gentoo forums Gensplash-How-to with progressbar!!!!! (https://forums.gentoo.org/viewtopic.php?t=206778&start=200&postdays=0&postorder=asc&highlight=) thread):
# cp /usr/bin/fbset /sbin
# cp /usr/lib/libjpeg.so.62 /lib
# cp /usr/lib/libpng.so.3 /lib
edit the /sbin/splash (nano works fine for this, just type nano -w /sbin/splash) and edit line 31 to read:
res=`/sbin/fbset | grep "^mode" | sed -r 's/mode "([0-9]+x[0-9]+).*/\1/'`
The only difference in this line is to add /sbin/ before fbset. Save and exit, and your splash should display properly.
[edit]
Background image loading in the middle of the boot process
You may (and probably will) find that the background image is loaded with a certain few-seconds-delay even when using an initramfs image. During that time the standard black-and-white 640x480 resolution is used.
Such behaviour is normal. The only workaround (in order to get the background image as early as possible) would be using the vesafb frame buffer device (instead of vesafb-tng). Here's Spock's elaborate answer (https://forums.gentoo.org/viewtopic.php?t=206778) on that issue: "The initramfs is used to populate the root filesystem before the frame-buffer subsystem is initialized, so it's good enough - don't worry about it. As you might have noticed, your PC boots into the text mode, and not the graphics mode. The graphics mode is set up when the framebuffer sub-system is initialized. But before that can happen, other things must be initialized, things that take some time. That's why for a second or two you might be seeing the kernel messages. You might say that with vesafb you didn't have those. And you will be right. But vesafb is an exception, not a rule (it's initialized while the kernel is being loaded) . Every other fb driver, including vesafb-tng, rivafb, radeonfb,... is initialized with the fbdev subsystem".
Suggestions are welcome, if I've made some mistakes please correct them. I hope this How-To will help.
Greetings, RobDin
(Thanks, RobDin, it helped me, and I hope my small additions will help others too. --motub)
(Many modifications - especially (but not only) concerning the frame buffer devices - made by Jakub, I hope the author won't mind)
(Actually I have rewritten many parts of this howto. I'm afraid the original author might not like it but it's too late now. I'm sorry -- Jakub)
(@Jakub - I thought that making adaptions to How-To's is part of the gentoo-wiki way, feel free to make more adaptions. I allready knew that it was incomplete so I should thank you -- RobDin)
(Me (fctk) heavyly modified this howto, too. I hope i didn't messed up something...)
Spanish Versión https://forums.gentoo.org/viewtopic.php?p=1606187
[edit]
References
· Spock's homepage (http://dev.gentoo.org/~spock/)
· Spock's Gensplash-in-5-easy-steps (http://dev.gentoo.org/~spock/projects/gensplash/gensplash-in-5-easy-steps.php)
From Gentoo Forums:
· Gensplash-How-to with progressbar!!!!! (https://forums.gentoo.org/viewtopic.php?t=206778)
Offline documentation:
· Fbsplash's documentation (/usr/src/linux/Documentation/fb/splash.txt).
· Frame buffer documentation (/usr/src/linux/Documentation/fb/framebuffer.txt).
· Splashutils' documentation (/usr/share/doc/splashutils-0.9_pre07/).

HOWTO Gentoo & FBSplash
aus Unixboard, der freien Wissensdatenbank
This document describes how to get fbsplash up-n-running in a fast and painless way.
0) Preparation. Make sure you that you either have your ACCEPT_KEYWORDS set
to ~<your_arch> (eg. ~x86) or that you add:
sys-kernel/gentoo-dev-sources ~x86
media-gfx/splashutils ~x86
to your /etc/portage/package.keywords.
1) Install the latest Gentoo kernel sources:
# emerge gentoo-dev-sources
2) Configure, build and install your kernel:
# cd /usr/src/linux
# make menuconfig
# make
# make install modules_install
3) Install splashutils:
# emerge splashutils
4) Create an initramfs image for fbsplash:
# splash_geninitramfs -v -g /boot/fbsplash-emergence-1024x768 -r 1024x768 emergence
5) Configure your bootloader: (instructions for grub)
# cd /boot/grub
Edit menu.lst, find the entry for your kernel, and put 'splash=silent,theme:emergence'
onto the kernel command line. You should get something like this:
title Gentoo Linux (g-d-s 2.6.8.1)
root (hd0,4)
kernel /boot/gentoo-2.6.8.1 ro root=/dev/hda1 video=vesafb:ywrap,pmipal,1024x768-32@85 splash=silent,theme:emergence
initrd /boot/fbsplash-emergence-1024x768
This is it. Reboot and enjoy fbsplash

Voilà, tu en as deux. Ils sont cependant écrits pour fbsplash, donc si t'as pas un kernel > 2.6.8 ça va pas le faire.

Hésite pas en cas de besoin

[Monrake]

J'ai lu le premier tuto et j'ai fait les verification, mon Kernel a bien les options demandés, je l'avais recompilé expressement pour ça. Le reste de la procédure est celle que j'ai suivit, c'est pour cela que je suis un peu perdu et que je ne comprends pas pourquoi ça ne marche pas

[laharl]

record battu là
_________________
http://linux.laharl.org

[Monrake]

[laharl]

[Monrake]

Bon, je suis entrain de refaire tout le tuto. Des fois que j'aurais fait une erreur en chemin.

[Monrake]

je viens de faire le tuto a moins 4 fois et toujours pas d'évolution. J'ai repassé mon kernel a paigne fin, j'ai verifiter tout les menus, sous menu, etc... comme je l'ai jamais fait. J'ai du desinstaller et reinstallé splashutils au moins 3 fois, rien changé non plus.

J'ai aussi essayé de foutre l'image directement dans le kernel ou en dynamique, change rien, je tourne en rond et sa fait deux heures que sa me les casses graves....

[neor]

salut,

[Dais]

Sauf que normalement, si tu mets verbose, tu as effectivement la console, mais AVEC l'image de fond (la version verbose donc, celle qui a un espace réservé pour l'affichage de la console). Là il n'a rien, juste du noir en fond :p

[Monrake]

[yuk159]

As-tu essayé de remplacer

[Monrake]

[Nemerid]

J'ai personnellement le même problème, je n'ai jamais réussi à faire fonctionner gensplash ! Et je ne compte plus le nombre de fois où j'ai du rebooter mon pc...

[Monrake]

[NiLuJe]

L'initramfs a été généré correctement? Ou compilé en dur dans le kernel? (Je pencherais pour la solution 1, vu qu'il y a un initrd de spécifié dans vos confs)

(Et correspond avec la conf du lilo/grub.conf, evidemment ^^)

[Monrake]

[Monrake]

En faisant des tests de kernel, j'ai remarqué un détail interressant. Quand j'active l'option suivante dans le kernel :

[NiLuJe]

Essaye sans spécifier theme:emergence, a tout hasard. (Il utilise bien le seul/premier theme qu'il trouve / celui spécifié dans la conf splash dans ce cas la, nan? )

Edit : En passant, vesafb ne gère pas le changement de rafraichissment, et donc le paramètre @75. Essaye en utilisant vesafb-tng à la place (Si le patch vesafb-tng a été appliqué au kernel bien sûr, mais en général il va de paire avec le patch gensplash, donc bon ^^).

[Monrake]

Après une 10ene de compilation de mon kernel avec Dais pour tout tester, ça marche. Je n'avais pas vu qu'il fallait spéifier dans le kernel la résolution.