Michael Prokop wrote...

Please test the ISOs and everything you usually use and report back so we can complete the stable release soon.

Errr, folks ... I did "kvm -cdrom $IMAGE" for both

grml32-small_2014.10-rc1.iso grml64-full_2014.10-rc1.iso

and simply chose the first entry from the boot menu - to find them failing while looking for the root file system, dropping me into the rescue shell. Something's terribly wrong here.

Testing grml32small on an ol' VIA C3 board, using toram/fetch

- Still the "module dm-raid45 not found in modules.dep", appearently harmless. - New: There's a long time without activity (approximately 40 seconds) after "Creating /dev/mdadm/mdadm.conf ...". Not a bug but somewhat confusing.

Aside, a feature request: Appearently fetch=http://... retrieves the squashfs using curl, the copies it around using rsync. Was it possible to download it right to the final place and save a step?

Testing grml64-full_2014.10-rc1.iso on a recent Intel Atom board showed no unexpected behaviour.

Christoph

Hi,

On Thu, Oct 09, 2014 at 11:40:46AM +0200, Michael Prokop wrote:

Please test the ISOs and everything you usually use and report back so we can complete the stable release soon.

Since the WWAN modem for my Thinkpad X240 arrived today, this was a good occassion to boot the new grml RC on real modern hardware. I boot it via /boot/grml/*.iso and grml-rescueboot(*).

Here's what I noticed:

General and working fine:

* X and the mouse work well, despite the annoying clickpad with no more real mouse keys.

* WLAN seems to work fine, too.

* acpi found and properly displayed both batteries

Slightly confusing, possibly bugs:

* Boot menu without background image or similar, just black background.

* But as soon as I select any submenu, a blue-ish background (same color as my grub background, but without the white Debian swirl) without any text pops up for a facture of a second and then the background goes black again and the submenu is displayed.

* Independent of what I boot (grml to RAM, MirBSD, X, default), the blue-ish background reappears, shows the first few kernel output lines and stays until the font is switched.

* If I boot grml to RAM, X or MirBSD I initially get an grub error "error: null src bitmap in grub_video_bitmap_create_scaled before "Loading kernel" plus "Press any key to continue...". This does not happen with the default boot entry.

* It seems to make no latency difference if I press enter at that prompt or just wait.

* Ctrl-Alt-Backspace does not kill X (neither with "Boot into X" nor with default boot and then pressing "x")

* MirBSD has an option "Chain to GNU GRUB for booting into grml.org again", but if I choose that I get a "boot>" prompt and the message "Switching to GRUB again is deactivated in loopback.cfg" -- maybe caused by the fact that I used grml-rescueboot?

* If I type "reboot" on MirBSD's "boot>" prompt, it says "Rebooting..." and "exit" and then does nothing. Had to power off the device to get anywhere else.

* If I boot MirBSD, it shows the following error message before showing the prompt the first time:

1) "uid 0 on /: file system full" (kernel message blue on white) 2) "/: write failed: file system is full" 3) "cp: /tmp/tftpboot/boot: No space left on device"

(*) Booting it via grub-imageboot from the same device just made a beep and then a light-/dark-grey striped screen, then after a few seconds a white-yellow striped screen, then the Grml ASCII art logo, then repeating messages saying "modprobe: module luks not found in modules.dep" (maybe related to the fact that the machine's root file system is encrypted) and finally falling into the initramfs with the message "unable to find a medium containing a live file system and a final message "modprobe: module ehci-orion not found in modules.dep".

HTH.

Kind regards, Axel