Re: 64bit startup

2023-05-27 Thread Samuel Thibault
If people want to play with it, I have updated the image on https://people.debian.org/~sthibault/hurd-i386/initrd-amd64.img.gz of course, since the second stage of debootstrap doesn't work yet, nothing is configured, so you have to configure everything by hand to get almost anything to work. It

Re: 64bit startup

2023-05-27 Thread Samuel Thibault
Samuel Thibault, le dim. 28 mai 2023 02:30:25 +0200, a ecrit: > BTW, good news: it seems that netdde seems to be starting :D > > pci_irq_enable: dev 0x3d1008 > pci_irq_enable: irq 11, pin 1 > <6>e1000 :00:04.0: PCI INT A -> GSI 11 -> IRQ 11 > MEM: name: e1000, start: feba, len: 131072 >

Re: 64bit startup

2023-05-27 Thread Samuel Thibault
Samuel Thibault, le dim. 28 mai 2023 03:37:01 +0200, a ecrit: > Samuel Thibault, le dim. 28 mai 2023 03:34:50 +0200, a ecrit: > > # fdisk -l /dev/wd0 > > Disk /dev/wd0: 81 MiB, 84934656 bytes, 165888 sectors > > Units: sectors of 1 * 512 = 512 bytes > > Sector size (logical/physical): 512 bytes /

Re: 64bit startup

2023-05-27 Thread Samuel Thibault
Samuel Thibault, le dim. 28 mai 2023 03:34:50 +0200, a ecrit: > # fdisk -l /dev/wd0 > Disk /dev/wd0: 81 MiB, 84934656 bytes, 165888 sectors > Units: sectors of 1 * 512 = 512 bytes > Sector size (logical/physical): 512 bytes / 512 bytes > I/O size (minimum/optimal): 512 bytes / 512 bytes >

Re: 64bit startup

2023-05-27 Thread Samuel Thibault
And rumpdisk as well :) [ 2.9500050] wd3 at atabus5 drive 0 [ 2.9500050] wd3: [ 2.9500050] wd3: drive supports 16-sector PIO transfers, LBA48 addressing [ 2.9500050] wd3: 50001 MB, 101589 cyl, 16 head, 63 sec, 512 bytes/sect x 102402048 sectors [ 2.9600050] wd3: drive supports PIO

Re: 64bit startup

2023-05-27 Thread Samuel Thibault
BTW, good news: it seems that netdde seems to be starting :D pci_irq_enable: dev 0x3d1008 pci_irq_enable: irq 11, pin 1 <6>e1000 :00:04.0: PCI INT A -> GSI 11 -> IRQ 11 MEM: name: e1000, start: feba, len: 131072 IO: name: e1000, start: c040, len: 64 ioremap: phys: feba <-> virt:

Re: 64bit startup

2023-05-27 Thread Samuel Thibault
Samuel Thibault, le sam. 27 mai 2023 12:16:50 +0200, a ecrit: > > > BTW, it seems the control-alt-d kdb shortcut is not working? > > > > I didn't enable kdb in my gnumach build. I never learned how to use it. > > You really should, it's terribly useful to inspect tasks etc. > > show all tasks >

Re: 64bit startup

2023-05-27 Thread Samuel Thibault
Sergey Bugaev, le ven. 26 mai 2023 17:31:40 +0300, a ecrit: > (maybe you could teach me how to fetch and load separate debuginfo > into gdb?) BTW it's as simple as symbol-file ./usr/lib/debug/.build-id/3e/a2af77859e5cfd5c1b726d81f135bfbfb3d1f0.debug (the build id is visible in the `file

Re: 64bit startup

2023-05-27 Thread Samuel Thibault
Samuel Thibault, le sam. 27 mai 2023 23:13:40 +0200, a ecrit: > Samuel Thibault, le sam. 27 mai 2023 13:40:58 +0200, a ecrit: > > start ext2fs: Hurd server bootstrap: ext2fs[device:rd0] exec startup proc > > auth. > > /usr/libexec/console-run: /dev/console: Read-only file system > > > > task

Re: 64bit startup

2023-05-27 Thread Samuel Thibault
Samuel Thibault, le sam. 27 mai 2023 13:40:58 +0200, a ecrit: > Disabling the protector indeed helped a lot :) Packages are getting > rebuilt (with debugging information, this time...), but I could already > build some debian initrd image: > >

Re: 64bit startup

2023-05-27 Thread Samuel Thibault
Samuel Thibault, le sam. 27 mai 2023 12:16:50 +0200, a ecrit: > Sergey Bugaev, le ven. 26 mai 2023 17:31:40 +0300, a ecrit: > > On Fri, May 26, 2023 at 2:15 PM Samuel Thibault > > wrote: > > > It does load, but stays stuck when starting ext2fs: > > > > > >start ext2fs: > > > > Yes, I can

Re: 64bit startup

2023-05-27 Thread Samuel Thibault
Samuel Thibault, le sam. 27 mai 2023 12:16:50 +0200, a ecrit: > Sergey Bugaev, le ven. 26 mai 2023 17:31:40 +0300, a ecrit: > > On Fri, May 26, 2023 at 2:15 PM Samuel Thibault > > wrote: > > > It does load, but stays stuck when starting ext2fs: > > > > > >start ext2fs: > > > > Yes, I can

Re: 64bit startup

2023-05-27 Thread Samuel Thibault
Sergey Bugaev, le ven. 26 mai 2023 17:31:40 +0300, a ecrit: > On Fri, May 26, 2023 at 2:15 PM Samuel Thibault > wrote: > > It does load, but stays stuck when starting ext2fs: > > > >start ext2fs: > > Yes, I can reproduce this with your build of ext2fs.static > > Unfortunately there are no

Re: libdiskfs assertion failed

2023-05-27 Thread Samuel Thibault
Joshua Branson, le ven. 26 mai 2023 11:02:44 -0400, a ecrit: > Samuel Thibault writes: > > Joshua Branson, le jeu. 25 mai 2023 22:32:24 -0400, a ecrit: > >> So I updated my T43 to the bleeding edge Debian in real hardware, which > >> come on that is pretty cool! The update process was pretty

Most recent commit in incubater/dde_net breaks cross build

2023-05-27 Thread Janneke Nieuwenhuizen
Hi, This commit https://git.savannah.gnu.org/cgit/hurd/incubator.git/commit/?id=be828e44b332ccfeef6f687d69b5d74b2a16323d more specificly, this bit --8<---cut here---start->8--- diff --git a/main.c b/main.c index ec764056a..26ad4f1dd 100644 --- a/main.c

Re: [PATCH glibc] Stop checking if MiG supports retcode.

2023-05-27 Thread Guy-Fleury Iteriteka
On May 27, 2023 8:42:27 AM GMT+02:00, "Flávio Cruz" wrote: >On Fri, May 26, 2023 at 9:42 AM Guy-Fleury Iteriteka >wrote: > >> On May 26, 2023 2:00:00 PM GMT+02:00, "Flávio Cruz" >> wrote: >> >Hi Sergey >> > >> >On Fri, May 19, 2023 at 4:02 AM Sergey Bugaev wrote: >> > >> >> Hi, >> >> >> >> On

Re: [PATCH glibc] Stop checking if MiG supports retcode.

2023-05-27 Thread Flávio Cruz
On Fri, May 26, 2023 at 9:42 AM Guy-Fleury Iteriteka wrote: > On May 26, 2023 2:00:00 PM GMT+02:00, "Flávio Cruz" > wrote: > >Hi Sergey > > > >On Fri, May 19, 2023 at 4:02 AM Sergey Bugaev wrote: > > > >> Hi, > >> > >> On Fri, May 19, 2023 at 9:43 AM Flávio Cruz > wrote: > >> > I have made

Re: [PATCH glibc] Stop checking if MiG supports retcode.

2023-05-27 Thread Flávio Cruz
On Fri, May 26, 2023 at 10:43 AM Sergey Bugaev wrote: > On Fri, May 26, 2023 at 3:00 PM Flávio Cruz wrote: > > Hi Sergey > > Hi, > > > Thanks for the instructions. I was able to make it work and pushed my > changes to Github. > > That's awesome news -- thank you! > > (Well, I figured as much