Closing this issue as it seem to be resolved, please reopen if you think we 
should investigate further. Thanks!

regards,
-mika-

Thank you ... a broken CD media.  I burned a new one and the delay is gone.  I
should have tried that before bothering you.  Sorry.

I should point out, though, that all the ACPI Error messages still occur.

Thanks,
Fletcher

* Fletcher wrote in grml's BTS on 20091117 / 00:04:

> After 70 seconds I get "  -> Mounted live system on /dev/sr0"

> Lots of error messages in dmesg.  The particular messages between about the 4th
> and 64th seconds in the log were a series of 6 lines repeated about every 6 or 7
> seconds consisting of (only readable text copied):

> Unhandled sense code
> Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
> Sense key : Hardware Error [current]
> Add. Sense: Time out on logical unit
> end_request: I/O error, dev sr0, sector 490552
> Buffer I/O error on device sr0, logical block 61319

Very probably you've either a broken CD medium or a broken CD drive.

regards,
-mika-

Addendum to previous message:

Booted from a USB CD-ROM drive.  Long delay gone.

Does the attached dmesg output shed any light on what I need to do to get the
built-in CD-ROM drive to work without the delay?

Thanks,
Fletcher

70 seconds for just the "Searching for GRML file, this may take a few seconds...".

After 70 seconds I get "  -> Mounted live system on /dev/sr0"

Lots of error messages in dmesg.  The particular messages between about the 4th
and 64th seconds in the log were a series of 6 lines repeated about every 6 or 7
seconds consisting of (only readable text copied):

Unhandled sense code
Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Sense key : Hardware Error [current]
Add. Sense: Time out on logical unit
end_request: I/O error, dev sr0, sector 490552
Buffer I/O error on device sr0, logical block 61319

There were other different error message throughout the dmesg output before and
after the ones above that didn't seem to cause a noticeable delay.

Can I send you a copy of the dmesg output?

I'll try a USB CD-ROM and see if there is a difference.

Thanks,
Fletcher

* Fletcher wrote in grml's BTS on 20091116 / 22:40:

> I'm booting from a CD.

Ok.

> No special bootoptions ... just the default "/boot/grmlmedium/linux26
> /boot/grmlmedium/initrd.gz boot=live apm=power-off vga=791 guiet nomce".

Ok.

> When I added "bootfrom=removable" to the options it actually reduced the time by
> about 1 minute.  It now takes about 70 seconds.

Ok, 70 seconds for just the "Searching for GRML file" or for
complete boot?

> We seem to be headed in the right direction.  Any more things to tweak?

Is anything obvious inside output of dmesg?
Any chance you try booting from USB pen and check whether the
situation is the same there?

regards,
-mika-

I'm booting from a CD.

No special bootoptions ... just the default "/boot/grmlmedium/linux26
/boot/grmlmedium/initrd.gz boot=live apm=power-off vga=791 guiet nomce".

When I added "bootfrom=removable" to the options it actually reduced the time by
about 1 minute.  It now takes about 70 seconds.

We seem to be headed in the right direction.  Any more things to tweak?

Cheers,
Fletcher

Do you use any special bootoptions?
Does booting with 'bootfrom=removable' improve the situation?
From which media (CD/USB/Disk/...) are you booting?

regards,
-mika-

I'm getting a 2+ minute delay during "Searching for GPML file".  Apparently the
earlier fix isn't working for me.  I'm running the 2009-10 release (codename
Hello-Wien) on a Dell Latitude E6400 XFR w/ Core2 Duo CPU @ 2.53GHz and 4GM RAM.

What sort of additional information can I provide to aid in solving this problem?

Thanks,
Fletcher

I'm closing this bugreport because the issue should be fixed. Please feel free 
to reopen the bugreport if you can still explore the problem.

thx && regards,
-mika-

Quoting from #debian-live:

10:06 < CIA-1> daniel * r1b53347 live-initramfs/scripts/ (live live-helpers): 
Ignoring floppy devices for live filesystem as well as live persistency.

On Mon, May 12, 2008 at 05:20:06PM -0000, Michael Prokop wrote:
> Can you please try booting with bootoption "nopersistent"?
> Does this change anything?

No.

Greetings
Marc

-- 
-----------------------------------------------------------------------------
Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany  |  lose things."    Winona Ryder | Fon: *49 621 72739834
Nordisch by Nature |  How to make an American Quilt | Fax: *49 3221 2323190

* Marc 'Zugschlus' Haber <bts@bts.grml.org> [20080512 18:54]:

> On some systems, GRML hangs for minutes on "Searching for GRML file". When 
> watching GRML booting a virtual machine, this shows that GRML tries to access a 
> non-existing floppy.

> In some systems, it is not possible to disable the floppy controller in the 
> BIOS.

> Since GRML is way too large for a floppy anyway, I guess that it is safe to 
> exclude /sys/blog/fd0 from the list that is obtained in find_livefs in 
> scripts/live by echo /sys/block/*.

> There should probably be a boot parameter to re-enable the scan of the floppy 
> drive for the rare case that this is actually needed.

Can you please try booting with bootoption "nopersistent"?
Does this change anything?

regards,
-mika-

On some systems, GRML hangs for minutes on "Searching for GRML file". When 
watching GRML booting a virtual machine, this shows that GRML tries to access a 
non-existing floppy.

In some systems, it is not possible to disable the floppy controller in the 
BIOS.

Since GRML is way too large for a floppy anyway, I guess that it is safe to 
exclude /sys/blog/fd0 from the list that is obtained in find_livefs in 
scripts/live by echo /sys/block/*.

There should probably be a boot parameter to re-enable the scan of the floppy 
drive for the rare case that this is actually needed.

Greetings
Marc