Hi Florian, Michal Answers in your message.
> It's really cool that you are working on that. What tools are you using > to create the live CD? I use a custom python script shared with another ubuntu project, with a xml description file. > About your specific issue, the explanation is quite simple actually. You > are trying out the resulting ISO in a virtual machine (namely > VirtualBox) which does not provide 3D acceleration. Since 0.3.4 Elisa > detects that kind of situation and refuses to start because the end > result would be simply unusable. I have also the same behaviour if i boot directly from a fresh burnt CD. > You can bypass that safety checks by > using the option '--skip-benchmark'. > I will try first with that option but it is just for test, a reliable solution is to make working dri. > The splash screen is really shown as soon as possible _when_ the > benchmark is not run. Otherwise the benchmark which might take up some > time is run first and then the splashscreen is displayed. Maybe we > should invert that. The code about that is all in > elisa-core/elisa/core/elisa_boot.py if you want to have a look. I will have a look a that. But i think it would be nice to invert in that case. Does the splashscreen require absolutely 3D hardware acceleration or any 3D stuff ? > > > > > - Is it possible to add mesa or opengl packages i don't know of all that > deals > > with 3D that Elisa needs as dependencies on the elisa-extras package ? > because > > we need 3D acceleration and by default, no corresponding packages are > installed. > > > > It's a typical issue on Ubuntu live CD. It boils down to if you have > intel hardware you have 3D hardware acceleration by default. If you > have nVidia, you have no 3D acceleration. If you are lucky and have the > right ATI model you might have decent 3D acceleration. Therefore in many > cases you need to install the proprietary drivers from ATI or nVidia. > Problem is that it's not trivial to have them all installed by default > on a live CD. In your case I guess you have an ATI which is why you have > installed fglrx by default. But that's not enough, you have to do what > "Restricted Manager" does which is tweak the /etc/X11/xorg.conf to tell > X.org to use the fglrx driver. In Hardy "Restricted Manager" is called > 'jockey'. You should definitely have a look at the code (it's Python). No i have on my laptop an intel chipset. but i thought that installing the most common drivers, it would work for anybody. One surprising thing is that on my laptop, i don't have any customized xorg.conf, it doesn't contains any section dealing with drivers like dri. But anyway, i will try to make a generic one and put it on the cd. I will tell you back how it works...or not ! ;) Thank you very much. Denis. -- Windows c'est comme un Tamagoshi... Même quand tu t'en occupes il meurt. => Linux User #354241 ! => Ubuntu User #14794 !
