Package: win32-loader Version: 0.7.4.3 Severity: important Tags: d-i upstream help
Hi, while testing win32-loader for its 0.7.4.3 upload, I noticed that the GNU/Hurd graphical installer doesn't boot anymore with the current win32-loader configuration. The files it installs are the following: http://people.debian.org/~sthibault/hurd-i386/installer/cdimage/current/gtk/gnumach.gz http://people.debian.org/~sthibault/hurd-i386/installer/cdimage/current/gtk/ext2fs.static http://people.debian.org/~sthibault/hurd-i386/installer/cdimage/current/gtk/initrd.gz http://people.debian.org/~sthibault/hurd-i386/installer/cdimage/current/gtk/ld.so.1 Win32-loader then puts them all in C:\win32-loader and configures a Grub with the attached grub.cfg. Now, at boot, it fails with messages approximately (crappy smartphone camera, sorry) saying: > no more room for vm_map_find_entry in 74002294 > no more room for kmem_alloc in 74002294 then > 3 bootmodules > panic: 1 of 3 boot script commands could not be parsed at Can anyone from debian-hurd@l.d.o give me a hint thereabout ? Cheers, OdyX
multiboot /win32-loader/gnumach.gz root=gunzip:device:rd0 priority=low -- module --nounzip /win32-loader/initrd.gz initrd '$(ramdisk-create)' module /win32-loader/ext2fs.static ext2fs \ --multiboot-command-line='${kernel-command-line}' \ --host-priv-port='${host-port}' \ --device-master-port='${device-port}' \ --exec-server-task='${exec-task}' -T typed '${root}' \ '$(task-create)' '$(task-resume)' module /win32-loader/ld.so.1 exec /hurd/exec '$(exec-task=task-create)' boot