Linux Kernel 3.4.2 ready for testing - With new bootsplah

[UrUtusUbU]

hello
last stable kernel of linux for everybody.

changes:
---Kernel---
the kernel was patched with aufs3 and bootsplash-3.1.6,
no errors and 16 warnings,
some news modules and drivers,
some personal beginner errors fixeds.

---Initrd.xz---
only updated drivers Net of initrd with its corresponding ones and inlay the bootsplash.

---Bootsplash---
only configured for verbose mode with window effect and a new cool image.

now the bootsplash look like this:


1024x780 here:
http://img256.imageshack.us/img256/4109/033h.png

---Download---
All necessary (vmlinuz, initrd.xz, 000-kernel.xzm and md5checksums) are compresed in one file, you must download, decompress, and you can see the folders boot and porteus,
copy the two folder, paste in your usb or .... and say yes to rewrite, and reboot system.

download link:
http://www.mediafire.com/?0ej9bb3sw4obve1

I hope comments

bye.

[Hamza]

I would love to get this startup screen for next release.

[UrUtusUbU]

I believe that imageshack darkens a little the images, working it turns out to be clearer, at least in my monitor.

Posted after 6 hours 23 seconds:
Re: Linux Kernel 3.4.2 ready for testing - With new bootsplah
lol,
the kernel 3.4.3 was released today,
and imageshack was bloked the 1024x780 image,
lol.

[fanthom]

I would love to get this startup screen for next release.

i have played with bootsplash in slax-remix times to finally drop it completely in about v07 or v08 release.
reason: bootsplash is not compatible with KMS drivers (opensource intel, radeon and nouveau) and gets destroyed when udev loads drm driver (which is pretty early).
it could work for fglrx and binary nvidia but with a boot time around 10 seconds (to Xorg) I see no point for that.

i have nothing against keeping it as an option for people who wants bootsplash in "Community effort" section.
please remember that kernels with config different than official wont be supported by me so any troubles caused by it must be reported to the person who releases the kernel.

[Hamza]

bootsplash is not compatible with KMS drivers (opensource intel, radeon and nouveau) and gets destroyed when udev loads drm driver (which is pretty early).
it could work for fglrx and binary nvidia but with a boot time around 10 seconds (to Xorg) I see no point for that.

It's difficult to say No, but if that makes slower my Porteus, I'm finally against this idea. If I had understood, that will also detroyes some GPU drivers ?

[beny]

it is a choice,and it is enough a disclaimer to user,you know what you doing,no warranty,and if something goes wrong put back the original modules inside.

[Hamza]

@beny,

I'm agree with you but here the subject is to includes it as default boot screen and fanthom let us know that may affects the boot time and also GPU drivers.

[wread]

If 3.4.3 is already released without startsplash, why stick to 3.4.2, when the startsplash could mean trouble with some drivers?

[Hamza]

@wread,

I'm not sure, but I think, It's again a story of patch compatibility.

[UrUtusUbU]

i have played with bootsplash in slax-remix times to finally drop it completely in about v07 or v08 release.
reason: bootsplash is not compatible with KMS drivers (opensource intel, radeon and nouveau) and gets destroyed when udev loads drm driver (which is pretty early).
it could work for fglrx and binary nvidia but with a boot time around 10 seconds (to Xorg) I see no point for that.

that's why it goes out when it changes the resolution? is when load udev.
sometimes i have not time to see the bootsplash when the screen changes the resolution, also it depends in that you plot. i need 10 seconds more
the only problem for me is the crc32 of initrd.xz when patch the bootsplash, but if you do not touch it it is not a problem.

i have nothing against keeping it as an option for people who wants bootsplash in "Community effort" section.
please remember that kernels with config different than official wont be supported by me so any troubles caused by it must be reported to the person who releases the kernel.

the config of this kernel is the same of porteus 1.2 rc2,
i write

Code: Select all

modprobe configs && zcat /proc/config.gz > .config

oldconfig etc etc,
and default in new drivers and modules, this kernel does not have many innovations,

but i do not want that you support this, after everything already slow one day in expiring,
if somebody see some very serious error saying it to me also,
I do it only for trying and learning.

if i do other i must put it in "Community effort" section??? not in development??

Posted after 8 minutes 52 seconds:

If 3.4.3 is already released without startsplash, why stick to 3.4.2, when the startsplash could mean trouble with some drivers?

i dont have problems with drivers, i have 2 ati and 1 intel video cards and no problems,
i use bootsplash every time and all the video section also compiz work fine,
so much drama no?

Posted after 11 minutes 55 seconds:

@wread,

I'm not sure, but I think, It's again a story of patch compatibility.

I do not believe,
the patch and the compilation dont teach any error ,
if it was incompatibility it would not be allowed to install or would give many errors, and it would not teach the bootsplash of course,
i also compiled in porteus the program for patch initrd without problems,
I do not believe that it is a problem of incompatibility.


Re: Linux Kernel 3.4.2 ready for testing - With new bootsplah
I say all this for my experience in 3 different computers without problems in none on the bootsplash, nor the kernel.

Posted after 5 minutes 50 seconds:
Re: Linux Kernel 3.4.2 ready for testing - With new bootsplah
fanthom you can say me how you putting the bootsplash in slax-remix??

[fanthom]

It's difficult to say No, but if that makes slower my Porteus, I'm finally against this idea. If I had understood, that will also detroyes some GPU drivers ?

bootsplash makes booting slower only by about 0.5 second. it does not destroy GPU drivers but rather a VESA framebuffer (used by bootsplash in text mode only) as KMS compatible drivers contains their own and better framebuffer implementation (native resolution, faster scrolling, immediate vt switching, etc...).

that's why it goes out when it changes the resolution? is when load udev.

yes - correct.

the only problem for me is the crc32 of initrd.xz when patch the bootsplash

i can remember that after attaching bootsplash to initrd.xz i was not able to unpack it anymore thus had to provide 'clean' version in porteus repo for those who wanted to attach their own bootsplash or just modify initrd content (another mark against bootsplash).

if i do other i must put it in "Community effort" section??? not in development??

'Development' section is for suggestions of features to be included in official ISO.
'Communitu effort' is for features which for some reasons were rejected/never accepted, but may be useful for some people (like ZEN patched kernel, 32bit kde4, etc...). some projects may start in 'Community section' and then get officially accepted - this happened to XFCE edition.

fanthom you can say me how you putting the bootsplash in slax-remix??

please check Q/A 12 from slax-remix FAQ:
link

[Hamza]

bootsplash makes booting slower only by about 0.5 second. it does not destroy GPU drivers but rather a VESA framebuffer (used by bootsplash in text mode only) as KMS compatible drivers contains their own and better framebuffer implementation (native resolution, faster scrolling, immediate vt switching, etc...).

I understand now. Thanks a lot for explanation

[UrUtusUbU]

it does not destroy GPU drivers but rather a VESA framebuffer

also it depends on the computer or driver, in virtual box it is seen at first and in the end, no framebuffer there.
the problem is not the bootsplash, they are the drivers.

i can remember that after attaching bootsplash to initrd.xz i was not able to unpack it anymore.

yes, this is what happens, but if you dont touch initrd this problem does not exist because the rest work fine,
it does not influence the system.

'Development' section is for suggestions of features to be included in official ISO.
'Communitu effort' is for features which for some reasons were rejected/never accepted, but may be useful for some people (like ZEN patched kernel, 32bit kde4, etc...). some projects may start in 'Community section' and then get officially accepted - this happened to XFCE edition.

ok the next time to Community effort,
I feel alone in community effort section and effort is a word that it tires

fanthom you can say me how you putting the bootsplash in slax-remix??

please check Q/A 12 from slax-remix FAQ:
link

thanks so much, i already looked at it, it is the same way as i do it, with the program splash.

sy