Hi Darsha,

our current kernel builds use CONFIG_EDD_OFF=y nowadays. I'm closing this 
bugreport therefore as the issue shouldn't be present with the (soon upcoming) 
next stable release. Thanks for your time and investigations!

regards,
-mika-

I'm thinking about setting CONFIG_EDD_OFF=y which will disable edd by default 
(but will stay configurable through the cmdline via edd={on|skipmbr|off}).

Please stay tuned for our next kernel update.

regards,
-mika-

* Darshaka Pathirana <bts@bts.grml.org> [20090809 13:24]:
> On 08/07/2009 01:25 PM, Michael Prokop wrote:

> > failsafe is an alias for:

> > vga=normal boot=live noautoconfig atapicd noapic noacpi acpi=off nomodules 
> > nofirewire noudev nousb nohotplug noapm nopcmcia nosmp maxcpu
> > s=0 noscsi noagp nodma ide=nodma noswap nofstab nosound nogpm nosyslog nodhcp 
> > nocpu nodisc nomodem xmodule=vesa noraid nolvm noresume selinux=0 edd=off

> > Could you please try to find out which option is relevant for your system?
> > (Try binary search to speed up testing.)

> After sending my previous post I did a last quick test and guess
> what: first try, first hit! ;) -> "edd=off" did the trick (again).

> So similar to issue348 "edd=off" makes the machine boot but before
> closing this (again) I have to ask where this problem comes from.

> Again: Ubuntu and gparted had no difficulties with booting their
> Live-CDs so the question is if this is a (vanilla-)kernel problem
> (and there is a upstream-bts-entry somewhere) or if this is
> grml-specific.

> IMHO using a bootoption to get the system running should be
> considered broken and we should keep this open until it is
> //really// solved. Don't you think so too?

Sounds reasonable.

Thanks for investigating. I'll check out kernel part.

regards,
-mika-

Hi Mika!

You've been faster than I have been...

On 08/07/2009 01:25 PM, Michael Prokop wrote:
> 
> failsafe is an alias for:
> 
> vga=normal boot=live noautoconfig atapicd noapic noacpi acpi=off nomodules 
> nofirewire noudev nousb nohotplug noapm nopcmcia nosmp maxcpu
> s=0 noscsi noagp nodma ide=nodma noswap nofstab nosound nogpm nosyslog nodhcp 
> nocpu nodisc nomodem xmodule=vesa noraid nolvm noresume selinux=0 edd=off
> 
> Could you please try to find out which option is relevant for your system?
> (Try binary search to speed up testing.)

After sending my previous post I did a last quick test and guess
what: first try, first hit! ;) -> "edd=off" did the trick (again).

So similar to issue348 "edd=off" makes the machine boot but before
closing this (again) I have to ask where this problem comes from.

Again: Ubuntu and gparted had no difficulties with booting their
Live-CDs so the question is if this is a (vanilla-)kernel problem
(and there is a upstream-bts-entry somewhere) or if this is
grml-specific.

IMHO using a bootoption to get the system running should be
considered broken and we should keep this open until it is
//really// solved. Don't you think so too?

Greetings,
 - Darsha

Hi Darsha,

failsafe is an alias for:

vga=normal boot=live noautoconfig atapicd noapic noacpi acpi=off nomodules 
nofirewire noudev nousb nohotplug noapm nopcmcia nosmp maxcpu
s=0 noscsi noagp nodma ide=nodma noswap nofstab nosound nogpm nosyslog nodhcp 
nocpu nodisc nomodem xmodule=vesa noraid nolvm noresume selinux=0 edd=off

Could you please try to find out which option is relevant for your system?
(Try binary search to speed up testing.)

thx && regards,
-mika-

Hi Mika!

I currently have access to the notebook (sooner than expected / but only with
limited time). Unfortunatly the result stays the same as described in msg1665
with the only difference that I now use grml-2009.05.

This time I also tried "failsafe" which made the system boot. I've attached the
grml-hwinfo. I hope this helps to solve this issue.

Greetings,
 - Darsha

Hi Mika!

I currently have access to the notebook (sooner than expected / but only with
limited time). Unfortunatly the result stays the same as described in msg1665
with the only difference that I now use grml-2009.05.

This time I also tried "failsafe" which made the system boot. I've attached the
grml-hwinfo. I hope this helps to solve this.

Greetings,
 - Darsha

Ok, thanks!

Hi Mika!

On 05.08.2009 04:01, Michael Prokop wrote:
> 
> Any news regarding this issue? I'd like to see this bugreport solved. :)

Sorry for the delay!
> 
> I'm marking this bugreport with "needs-progress" for now, if I don't 
> have any feedback within the next 4 weeks I'll consider closing this bugreport.

Please close it as soon as you need to do it. It's harder to get
access to this notebook than expected. If necessary I will reopen
this task when getting any further information.

Thanks for your assistance!

Greetings,
 - Darsha

Hi Darsha!

Any news regarding this issue? I'd like to see this bugreport solved. :)

I'm marking this bugreport with "needs-progress" for now, if I don't 
have any feedback within the next 4 weeks I'll consider closing this bugreport.

Thanks!

regards,
-mika-

Hi!

issue348 gives me hope that we have a similar problem here.
Unfortunatly it's harder to get access to this notebook again than
expected.  I'll try again this week and let you know.

Greetings,
 - Darsha

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

> I am sorry! I was not able to test it on the notebook in the week
> after easter.
> I am im Hannover (@Robocup) this week and so will //probably// be able to
> try it next week. As you tagged this as a release-stopper I will try to
> do my best to get it done as soon as possible.

That's just fine :)

> When do plan to release?

We're working on a devel-release which will become a rc version
then. The stable release is planned for may.

Have fun @ Robocup! :)

regards,
-mika-

Hi Mika!

I am sorry! I was not able to test it on the notebook in the week
after easter.
I am im Hannover (@Robocup) this week and so will //probably// be able to
try it next week. As you tagged this as a release-stopper I will try to
do my best to get it done as soon as possible.

When do plan to release?

Greetings,
 - Darsha

Hi Darsha!

Any news from your side?

thx && regards,
-mika-

* Darshaka Pathirana <bts@bts.grml.org> [20090401 10:44]:
> On 03/31/2009 11:58 PM, Michael Prokop wrote:

> > Hi Darsha, any chance that you could test one of the recent daily
> > ISOs (see daily.grml.org) to see whether your issue is really fixed?
> > Thanks!

> I'll try a daily ISO as soon as possible (most probably today).
> Unfortunatly I do not think I will not have access to the R600 (and
> therefor will not  be able to test the boot process) before
> the week after easter.

> I'll keep you updated.

That's just fine. Thanks!

regards,
-mika-

Hi Mika!

On 03/31/2009 11:58 PM, Michael Prokop wrote:
> 
> Hi Darsha, any chance that you could test one of the recent daily
> ISOs (see daily.grml.org) to see whether your issue is really fixed?
> Thanks!

I'll try a daily ISO as soon as possible (most probably today).
Unfortunatly I do not think I will not have access to the R600 (and
therefor will not  be able to test the boot process) before
the week after easter.

I'll keep you updated.

Greetings,
 - Darsha

Hi Darsha, any chance that you could test one of the recent daily ISOs (see 
daily.grml.org) to see whether your issue is really fixed? Thanks!

regards,
-mika-

Michael Prokop <mika@grml.org> has uploaded a package that may fix your bug.
Please test the package and inform the maintainer whether
version 0.9.8 of grml-live works as intended or not.

Thank you

The changelog is attached below

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Thu, 12 Feb 2009 14:20:39 +0100
Source: grml-live
Binary: grml-live
Architecture: source all
Version: 0.9.8
Distribution: unstable
Urgency: low
Maintainer: Michael Prokop <mika@grml.org>
Changed-By: Michael Prokop <mika@grml.org>
Description: 
 grml-live  - build system for creating a grml (based) live-cd
Changes: 
 grml-live (0.9.8) unstable; urgency=low
 .
   * Improve help text of the release option in usage info.
   * Drop fblog from GRML_FULL (obsolete with 2.6 kernels, #427139).
   * Add libcap2-bin to GRML_FULL.
   * Upgrade isolinux.bin to version from syslinux-common 2:3.73+dfsg-1.
     [Testing: issue569]
   * Integrate /etc/grml/fai/config/scripts/GRMLBASE/18-timesetup to
     improve UTC handling. Thanks for the script, Thomas Lehmann!
Checksums-Sha1: 
 63299a20eb0cddb4a4e1a946b5a08abace6ac002 879 grml-live_0.9.8.dsc
 508b68e3ad9625374c2493638d4357ff18aa74ba 2068172 grml-live_0.9.8.tar.gz
 dba83f3099567b46f2002c4bb3e56fffe8df72f3 2074446 grml-live_0.9.8_all.deb
Checksums-Sha256: 
 9e6ddb43ca89946972cec2764dd5bfd1c6bf9667418ed20b4d0ded588945854d 879 grml-live_0.9.8.dsc
 94f8ff8534f52f243bec17b45f0f6013d797d8ddcc6fb9689a3c12aa1eabd252 2068172 grml-live_0.9.8.tar.gz
 a4d94862aeb411ef01a7778e44e1d83a1fcb5c580ea88aca16479ed4001174d2 2074446 grml-live_0.9.8_all.deb
Files: 
 142afe45371300594ac44c9a43b00cfa 879 grml extra grml-live_0.9.8.dsc
 95129d2cde289192e018c34e5a00606a 2068172 grml extra grml-live_0.9.8.tar.gz
 46f9876ee7f0f436209d37f5ee02e6bc 2074446 grml extra grml-live_0.9.8_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iD8DBQFJlJou2N9T+zficugRAv08AJ97Odwc1fimncXNbiHdRrO53MtzdgCfRfI7
mY3yrN6MFdHvnCYQDajxJx0=
=CNYr
-----END PGP SIGNATURE-----

I've just updated isolinux.bin to version 2:3.73+dfsg-1:

  http://git.grml.org/?p=grml-live.git;a=commit;h=c7174a3

Upload of a new grml-live package will happen soon and rebuilds of ISOs will 
follow. Just to keep you informed, I'll ping you again as soon as I've ISOs 
available where this issue should be fixed.

thx && regards,
-mika-

Hi Mika!

After making my tests on issue348 I also tried to boot more patiently. But I am
sorry to say that there were no progress after 180 seconds. So the problem
remains on this (brand new) notebook.

I understand your concerns regarding the syslinux-version in the freeze state
so if we really can pinpoint this problem to syslinux we should provide an
"easy" workaround like remstaring the grml-iso with a different
syslinux-version by a script, a grml-tip or as a wiki-article... 

I am very interested in rebuilding the iso but surely need further reading [1]
as I am not "into it" right now... 

I also just took a look at grml2usb as a possible quick pre-test which states
that I need syslinux installed (quite obvious) but I don't know how to apt-get
a specific (and/or older) version (3.61 to be specific) of syslinux (or any
other program to be more generic) as v3.71 is the current version in
debian/lenny. 

What would you recommend to do?

Greetings,
 - Darsha

[1] is http://tinyurl.com/4gcbvo enough (with different isolinux versions)?

Hi Darsha!

Cool, thanks for investigating! I wasn't aware of the version trick at syslinux 
3.63+. :) I identify the isolinux/syslinux version using strings:

# strings ../grml_cd/boot/isolinux/isolinux.bin | grep ISOLINUX
ISOLINUX 3.61 Debian-2008-02-05

Is there any chance that you rebuild the ISO using a more recent syslinux 
version? (If not please ping me.) I'm afraid of changing the syslinux version 
within the freeze time of the upcoming stable release because we had serious 
problems with more recent isolinux/syslinux versions already. :-/ But I'd like 
to update to a more recent syslinux version shortly after the stable release 
came out.

thx && regards,
-mika-

Hi,

I just checked the syslinux-versions by booting the ISOs in
VirtualBox.

Here are the results:

 * grml 2008.11-rc1 -> syslinux 3.61
 * kubuntu 8.10 alternate -> syslinux 3.63
 * gparted live -> syslinux 3.72

Btw: I had problems to find out the syslinux-version in grml as the
ISOLINUX-versionstring passed so fast and is overlayed by the
bootlogo. syslinux 3.63+ allows me to disable the bootlogo by holding
the left shift-button (which is nice!). Any other way to disable the
logo in the older versions?

I will have access to the Notebook tomorrow or day after tomorrow. If I
can help you with any more infos, please let me know.

Greetings,
 - Darsha

Hi,

grml 2008.11-rc1 (on CD) fails to boot on a Toshiba Portege R600-101[1].

Similar to issue348 bootloader (syslinux) is shown, kernel and
initrd are also beeing loaded but screen keeps blank after that.

Unfortunatly I had no time to debug that problem intensivly but can
tell you that Kubuntu 8.10-alternate (on CD) and gparted Live (on USB)
(built after [2]) were able to boot flawlessly.

I suspect it has something to do with the syslinux-version as I
imagine to have seen different versions on each of this boot-mediums
(whereas grml seemed to use the oldest version).

I don't know if you consinder this one release-critical but really
would to see this issue fixed as I really would be a pitty if I could
not use grml on machines like these... I would be glad to help
wherever I can.

Greetings,
 - Darsha

[1] http://tinyurl.com/5lqfg8
[2] http://gparted.sourceforge.net/liveusb.php