Mylivecd, iso can't read libpng

[Yankee]

Hello,

Made an iso with the 33.7 kernel, took twice as long, all the updates are current, etc..

The iso boots off a flashdrive made with unetbootin and stops in the middle of
completing the boot.   Says it cannot read libpng.  Libpng3 is current.   No problems
were noticed during the iso creation.

Am I using the wrong kernel ?


THX.

[Neal ManBear]

Unless something else is wrong, the system should continue to the login after the libpng read error.

[Yankee]

Hi,

Would I get an error message if I'm out of memory ?    The iso I made several
weeks ago was 760MB and it worked OK.  Installed as well to a portable hard drive.
This current one is 965MB and it is stalling during boot.   System req'd RAM plus
LiveCD req'd RAM is possibly over my 1 GB of RAM with this larger iso.   
The livecd.sqfs is 948MB.

If RAM isn't  a  problem I'll make another iso using gzip and see how it does.

THX.
   

[Neal ManBear]

Is the libpng read error the only error you see?

I've booted a 4GB ISO on a system with 1GB RAM. Not problems with doing so.

[Yankee]

Is the libpng read error the only error you see?

I've booted a 4GB ISO on a system with 1GB RAM. Not problems with doing so.

The light blue screen appears and waits or stops.  When I hit escape it says libpng error: read error.
If I hit escape again it just repeats the error message and eventually the light blue screen reappears.
I've waited over 5 minutes with the light blue screen and without other activity messages on escape.

Later today I'll wait 15 or 20 minutes and see how it does.

THX.

[AS]

Hi,

what filesystem is on USB flash ? If I remember correctly some problems is related to ext4 partition.

AS

[Yankee]

Hi,

what filesystem is on USB flash ? If I remember correctly some problems is related to ext4 partition.

AS

It's a Windows created Fat32 which the Unetbootin on PCL installs quite well to.
At least it has so far.

[Neal ManBear]

You should hit the <Esc> key as soon as the graphic screen appears during the boot process. Watch for any error messages. Post any such accurately.

As an alternative, and in my opinion, better way to create a liveUSB, use PCLinuxOS LiveUSB Creator and use the ext3 formatting. As AS says, ext4 is known to have issues. I'd definitely avoid using any MS filesystem, like fat32.

To repeat, the libpng read error will not stop the boot process. It is a "null" error that will only be seen just before the login screen.

[AS]

Hi,

what filesystem is on USB flash ? If I remember correctly some problems is related to ext4 partition.

AS

It's a Windows created Fat32 which the Unetbootin on PCL installs quite well to.
At least it has so far.

... CONFIRMED: even FAT32 is not recognized from grub ...
http://www.pclinuxos.com/forum/index.php/topic,76452.msg743195.html#msg743195

[Yankee]

You should hit the <Esc> key as soon as the graphic screen appears during the boot process. Watch for any error messages. Post any such accurately.

I see what you're saying.   Would you wait longer than 20 minutes for this to boot ?   I did.
When working it says "Plymouth Start" before the blue screen, then I hit escape, it says "libpng error: read error",
then it says "Setting up union filesystem".    Then it finishes boot, all this in less than a minute or so.

When this current iso boots it stops at "libpng error: read error".   I don't think I should wait longer than
20 minutes.

I made the LiveCD with PCLLiveUSBCreator also using ext3.   The white bar moved to the right and
stopped.   I hit escape and saw a blinking cursor and no messages.  Waited 5 minutes no result.

One other question.   What is the default compression with the 33.7 kernel.  Choosing gzip might
use the same one.   If I do this iso over I'll try a different compression.

THX for your response(s)

[Neal ManBear]

You should hit the <Esc> key as soon as the graphic screen appears during the boot process. Watch for any error messages. Post any such accurately.

I see what you're saying.   Would you wait longer than 20 minutes for this to boot ?

   

I would wait on a first boot for hardware detection and etc to complete for as long as needed. Some older, less 'zippy' hardware may take longer.
The first boot process occurs each time you boot a live media.

I did.
When working it says "Plymouth Start" before the blue screen, then I hit escape, it says "libpng error: read error",
then it says "Setting up union filesystem".    Then it finishes boot, all this in less than a minute or so.

After the grub screen, boot starts. When you see the plymouth boot graphic is the time to type the <Esc> key. This switches you to a textual display of the boot process. There will be lines of text on the left and either an [OK] or a [Failed] on the right.

The libpng read error is a "null" event. That is, it does not have any effect on the booting of your system.

If nothing occurs between the starting of plymouth and the libpng read error, then booting has not occured. When you say, "it finishes boot," you are saying you logged into the desktop. Is this what you mean?

When this current iso boots it stops at "libpng error: read error".   I don't think I should wait longer than
20 minutes.

I would not wait 20 minutes at that point.

I made the LiveCD with PCLLiveUSBCreator also using ext3.   The white bar moved to the right and
stopped.   I hit escape and saw a blinking cursor and no messages.  Waited 5 minutes no result.

  Instead of waiting on the bar, try typing the <Esc> key and check the boot text. That is where you will see any failed messages. These messages are the important ones. The libpng message is of no importance.

One other question.   What is the default compression with the 33.7 kernel.  Choosing gzip might
use the same one.   If I do this iso over I'll try a different compression.

THX for your response(s)

The default compression for mylivecd is xz. The option to use a different compression is available, if you want to use it.

[Yankee]

After the grub screen, boot starts. When you see the plymouth boot graphic is the time to type the <Esc> key. This switches you to a textual display of the boot process. There will be lines of text on the left and either an [OK] or a [Failed] on the right.

The libpng read error is a "null" event. That is, it does not have any effect on the booting of your system.

If nothing occurs between the starting of plymouth and the libpng read error, then booting has not occured. When you say, "it finishes boot," you are saying you logged into the desktop. Is this what you mean?

Yes, I was successful with the smaller iso.   It said "Setting up union filesystem" after the blue screen
and then quickly went to the desktop after login, etc..   The larger iso is the problem.   It's on a
PCLinuxUSBCreator flash drive now.   I'll try it again, but it never says "Setting up union file system".
I'll wait 30 minutes for it to do something, hopefully lights will flash on the drive so I can see it working.

THX.

[Yankee]

Hi Neal,

http://www.pclinuxos.com/forum/index.php/topic,89932.0.html

The above thread identifies a problem with mylivecd and ProjectM files.
I think you would concur.

My small iso which works did not have ProjectM files in it, but the larger
iso does (Clementine specifically).

Next time I'm on Google I'll write the developer a bug message about unmatched
parentheses in preset file names.   He has a Google Newsgroup account.

Thanks for your help, greatly appreciated.