[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#655219: marked as done (win32-loader: GNU/Hurd graphical installer doesn't boot when setup by win32-loader)

Your message dated Sun, 1 Jun 2025 23:54:15 +0200
with message-id <[🔎] 20250601235415.2b85e5e3b9940a630f4959d2@mailbox.org>
and subject line Re: #655219 win32-loader: GNU/Hurd graphical installer doesn't boot when setup by win32-loader
has caused the Debian Bug report #655219,
regarding win32-loader: GNU/Hurd graphical installer doesn't boot when setup by win32-loader
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
655219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655219
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
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

--- End Message ---
--- Begin Message --- 
win32-loader is no longer in use in the installer.

Closing this bug


-- 
Holger Wansing <hwansing@mailbox.org>
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

--- End Message ---
Reply to: