* Darshaka Pathirana <bts@bts.grml.org> [20090527 18:04]:

> > Do you have something like "Device config" in your BIOS settings?
> > Is it set to "Setup by OS" or to "All Devices"? If so could you please try
> > switching that? (Please do a cold boot, not a normal reboot then.)

> Jup. There is a "Device config" BIOS setting and it was set to "Setup
> by OS". I switched that did a cold bool and tried your given boot
> option. No luck.

Alright.

> > Does booting using 'failsafe' or 'grml pnpacpi=off' or 'grml
> > pnpbios=off' change anything?

> * failsafe - failed
> * grml pnacpi=off - nope
> * grml pnpbios=off - nada

> BUT: guess what! By using the 'failsafe' bootoption I saw the message
> "Probing EDD (edd=off to disable)" for the first time. So I tried
> 'grml edd=off' and voila, booted promptly!

Great :)

> I searched the net a bit to get a cluewhat's this EDD is all about and
> why it delays the boot process on my notebook (escpecially because
> the CONFIG_EDD_OFF=m seems to be set in the grml kernel since ages and
> I did not have problem before grml 1.0-5 - but I need to double check
> that again) but found only uncomplete/unclear information (so far).

> Maybe you have clue...

Check out http://en.wikipedia.org/wiki/INT_13

I'll close this bugreport now as the issues seems to be fixed for
you.

regards,
-mika-

On 05/19/2009 06:18 PM, Michael Prokop wrote:
> 
> Do you have something like "Device config" in your BIOS settings?
> Is it set to "Setup by OS" or to "All Devices"? If so could you please try
> switching that? (Please do a cold boot, not a normal reboot then.)

Jup. There is a "Device config" BIOS setting and it was set to "Setup
by OS". I switched that did a cold bool and tried your given boot
option. No luck.

> Does booting using 'failsafe' or 'grml pnpacpi=off' or 'grml
> pnpbios=off' change anything?

* failsafe - failed
* grml pnacpi=off - nope
* grml pnpbios=off - nada

BUT: guess what! By using the 'failsafe' bootoption I saw the message
"Probing EDD (edd=off to disable)" for the first time. So I tried
'grml edd=off' and voila, booted promptly!

I searched the net a bit to get a cluewhat's this EDD is all about and
why it delays the boot process on my notebook (escpecially because
the CONFIG_EDD_OFF=m seems to be set in the grml kernel since ages and
I did not have problem before grml 1.0-5 - but I need to double check
that again) but found only uncomplete/unclear information (so far).

Maybe you have clue...

Greetings,
 - Darsha

* Darshaka Pathirana <bts@bts.grml.org> [20090519 18:08]:

> >> To say it again: the delay happens before the (fb-)grml-logo is
> >> poped up. (And arises after the initrd is loaded.)
> >> I am sorry, I do not think I can not explain it any better.

> > Yeah, so can you please provide dmesg output? :)

> Here we go...(new info*.tar.bz2 by grml-090313).

Thx!

Do you have something like "Device config" in your BIOS settings?
Is it set to "Setup by OS" or to "All Devices"? If so could you please try
switching that? (Please do a cold boot, not a normal reboot then.)

Does booting using 'failsafe' or 'grml pnpacpi=off' or 'grml
pnpbios=off' change anything?

regards,
-mika-

On 05/01/2009 09:31 AM, Michael Prokop wrote:
> Michael Prokop <mika@grml.org> added the comment:
> 
>> To say it again: the delay happens before the (fb-)grml-logo is
>> poped up. (And arises after the initrd is loaded.)
>> I am sorry, I do not think I can not explain it any better.
> 
> Yeah, so can you please provide dmesg output? :)

Here we go...(new info*.tar.bz2 by grml-090313).

Greetings & thanks for your help,
 - Darsha

* Darshaka Pathirana <bts@bts.grml.org> [20090430 16:52]:

> > The "modprobe: FATAL:" isn't a real problem, see
> > http://bts.grml.org/grml/issue639

> > Though I still don't see the stage where your problem arrives.
> > Can you please provide dmesg output of the booted system?

> Well, if you were able to see where the problem arises out of the
> screenshot I *really* would be amazed. The simple reason is: it can
> not be seen. I just hoped the errors/warnings which can be seen on
> my screenshot do indicate the problem I have *before* the messages
> are shown.

Right

> To say it again: the delay happens before the (fb-)grml-logo is
> poped up. (And arises after the initrd is loaded.)
> I am sorry, I do not think I can not explain it any better.

Yeah, so can you please provide dmesg output? :)

regards,
-mika-

On 29.04.2009 16:12, Michael Prokop wrote:
> * Darshaka Pathirana <bts@bts.grml.org> [20090428 18:16]:
>> Michael Prokop wrote:
>> 
>>> The long delay happens at "searching for grml...", right?
> 
>> No. As stated in msg1710 the delay happens after blanking the screen
>> after the last dot of the initrd-loading process and before seeing the
>> grml-logo. Bug I get some warning after that. I've attached (dirty)
>> a screenshot.
> 
> The "modprobe: FATAL:" isn't a real problem, see
> http://bts.grml.org/grml/issue639
> 
> Though I still don't see the stage where your problem arrives.
> Can you please provide dmesg output of the booted system?

Well, if you were able to see where the problem arises out of the
screenshot I *really* would be amazed. The simple reason is: it can
not be seen. I just hoped the errors/warnings which can be seen on
my screenshot do indicate the problem I have *before* the messages
are shown.

To say it again: the delay happens before the (fb-)grml-logo is
poped up. (And arises after the initrd is loaded.)
I am sorry, I do not think I can not explain it any better.

Greetings and thanks for your help,
 - Darsha

* Darshaka Pathirana <bts@bts.grml.org> [20090428 18:16]:

> > When booting grml you'll see something like "Mounting live system on
> > /dev/sd0" -> try booting with "grml bootfrom=/dev/sd0", assuming
> > that /dev/sd0 is the device. :)

> Ok. My system shows "/dev/scd0". I tried that and there was no
> difference.

ok

> > The long delay happens at "searching for grml...", right?

> No. As stated in msg1710 the delay happens after blanking the screen
> after the last dot of the initrd-loading process and before seeing the
> grml-logo. Bug I get some warning after that. I've attached (dirty)
> a screenshot.

The "modprobe: FATAL:" isn't a real problem, see
http://bts.grml.org/grml/issue639

Though I still don't see the stage where your problem arrives.
Can you please provide dmesg output of the booted system?

regards,
-mika-

On 04/23/2009 07:48 PM, Michael Prokop wrote:
> * Darshaka Pathirana <bts@bts.grml.org> [20090423 19:31]:
> 
>> Ok. I was able to test the a daily build (2009-04-02) on my notebook.
> 
> Great, thanks.

Oh. I did a mistake in labeling my CD. The daily build is dated with
(20)090319.

>> And again: booting took exactly 67 secconds!
>>
>> I also booted Ubuntu 9.04 beta - alternate which did not show such a
>> delay.
> 
> Ok
> 
>> That said I did not test the bootfrom=... bootoption and honestly have
>> no clue how to use it. Do I have to guess the device where I would
>> like to start from?
> 
> When booting grml you'll see something like "Mounting live system on
> /dev/sd0" -> try booting with "grml bootfrom=/dev/sd0", assuming
> that /dev/sd0 is the device. :)

Ok. My system shows "/dev/scd0". I tried that and there was no
difference.

> The long delay happens at "searching for grml...", right?

No. As stated in msg1710 the delay happens after blanking the screen
after the last dot of the initrd-loading process and before seeing the
grml-logo. Bug I get some warning after that. I've attached (dirty)
a screenshot.

Greetings,
- Darsha

* Darshaka Pathirana <bts@bts.grml.org> [20090423 19:31]:

> Ok. I was able to test the a daily build (2009-04-02) on my notebook.

Great, thanks.

> And again: booting took exactly 67 secconds!
> I also booted Ubuntu 9.04 beta - alternate which did not show such a
> delay.

Ok

> That said I did not test the bootfrom=... bootoption and honestly have
> no clue how to use it. Do I have to guess the device where I would
> like to start from?

When booting grml you'll see something like "Mounting live system on
/dev/sd0" -> try booting with "grml bootfrom=/dev/sd0", assuming
that /dev/sd0 is the device. :)

The long delay happens at "searching for grml...", right?

regards,
-mika-

On 02/12/2009 02:25 PM, Michael Prokop wrote:
> 
> The bootfrom=... bootoption should help you regarding this issue. Just give it 
> a try using a current stable version or daily snapshot booting with "grml 
> bootfrom=/dev/ice" where /dev/ice is the device you are booting from.

Ok. I was able to test the a daily build (2009-04-02) on my notebook.
And again: booting took exactly 67 secconds!
I also booted Ubuntu 9.04 beta - alternate which did not show such a
delay.

That said I did not test the bootfrom=... bootoption and honestly have
no clue how to use it. Do I have to guess the device where I would
like to start from?

Greetings,
 - Darsha

On 02/12/2009 02:25 PM, Michael Prokop wrote:
> 
> The bootfrom=... bootoption should help you regarding this issue. Just give it 
> a try using a current stable version or daily snapshot booting with "grml 
> bootfrom=/dev/ice" where /dev/ice is the device you are booting from.

Sorry! I missed this post somehow. I will try to test a daily build as
soon as possible!

Greetings,
  - Darsha

Hi Darsha!

The bootfrom=... bootoption should help you regarding this issue. Just give it 
a try using a current stable version or daily snapshot booting with "grml 
bootfrom=/dev/ice" where /dev/ice is the device you are booting from.

regards,
-mika-

Hi Mika,

Yes, I had the same speculation and went into checking it and here is my result..

I've booted grml-1.1 and grml-2008.11 and tell you what... they both finally
booted up on my Toshiba Portege M100!
But - and thats interesting - it took
exactly 67(!) seconds from blanking the screen (after the last loading dot of
the initrd) to the grml-bootlogo at the start of the booting processon every
boot with the CD.

Altough I /believe/ I waited atleast 67 seconds in the tests last year I can
not say for sure. I also did a BIOS-Firmware-update in the meanwhile to fix my
corrupt CPU-Microcode so the conditions of the problem may have changed
significantly...

The bottom line is that the main problem changed to "boot up takes ages" but
does not fail anymore so we either can change the title or close this issue.
That said І surely would like to see this fixed but can also live with it.

Thanks for your assistance and help!

Greetings,
 - Darsha

Darsha, do you think this one might be related to http://bts.grml.org/grml/
issue569? Both notebooks are from Toshiba, maybe a BIOS issue on Toshiba?

regards,
-mika-

Good question :-/ I'm working on a new stable version of grml, let's either 
debug this together as soon as we are both in front of the box or otherwise 
let's wait until kernel 2.6.24 and new grml snapshots are available (I expect 
to happen that in january '08).

Sorry, running out of ideas currently, please keep me up2date.

thx && regards,
-mika-

Hi Mika!

Thank you for providing the new snapshot. But unfortunately it still does not
work! What else can I do to help you?

Greetings,
 - Darsha

Hi Darsha!

The cdrom bootoption very probably does not work as expected due to the new 
booting layout.

Do you have any chance to test booting with a current snapshot like:
http://daily.grml.org/grml-medium_sid_20071126.iso
?

regards,
-mika-

Hi Mika!

Just wanted to test the "cdrom"-bootoption as described in issue72 and
http://grml.org/files/release-1.0/grml-cheatcodes.txt.

grml-1.0-3 reports /dev/hdc whereas Ubuntu 7.10 (Kernel: 2.6.22) shows me
/dev/scd0. I've tried both as "cdrom"-option but the behavior did not change.

I am not sure if that was the right thing to look due lack of specific knowledge
of the (cdrom-)bootprocedure.

If you can tell me where or what to look at I'll be glad to give you more
details. Hope this issue can be solved as this problem is serious (at least for
me). Thanks!

Greetings,
 - Darsha

Hi Darsha!

Hm, maybe a kernel 2.6.22 vs. 2.6.23 issue? I'm just working on a new kernel 
build, as soon as I've a new ISO I'll inform you.

thx && regards,
-mika-

Hi,

grml 1.0-5 and 1.1-rc1 fails to boot on my toshiba portege m100. Bootloader is
shown and working, kernel and initrd is also being loaded but screen keeps blank
after that and cdrom spins down.

Bootoptions "debug" and "nofb" did not change anything. Something must have been
changed sind 1.0-3 where booting works flawlessly. I've attached the
"grml-hwinfo"-File (with grml 1.0-3) to provide more infos.

I just saw issue72. Maybe there can be a workaround with the "cdrom"-bootoption
if so I'll report back here.

Greetings,
 - Darsha