Hi,
El 5/8/21 a les 1:26, Samuel Thibault ha escrit:
Is it not possible to avoid having to call memory_object_proxy_valid?
maybe better fix device_map into supporting non-zero offset,
I think it'd be a better solution to move the call to
memory_object_proxy_valid() and the start value overwr
Joan Lledó, le lun. 16 août 2021 10:53:47 +0200, a ecrit:
> El 5/8/21 a les 1:26, Samuel Thibault ha escrit:
>
> > Is it not possible to avoid having to call memory_object_proxy_valid?
> > maybe better fix device_map into supporting non-zero offset,
>
> I think it'd be a better solution to move t
Hello,
Almudena Garcia, le dim. 15 août 2021 02:04:38 +0200, a ecrit:
> Tonight I'm trying to install Debian GNU/Hurd 2021 in a Thinkpad T410,
> configuring SATA disk in AHCI mode,
Is it really in AHCI mode?
> The installer loads, but in partitioning step, after format the partitions, I
> found
> Is it really in AHCI mode?
Yes, I enabled AHCI SATA mode in the BIOS
> This is talking about wd0, i.e. the rumpdisk device, i.e. gnumach
> didn't detect the AHCI card. That's not expected, we need to know what
> is actually showing up exactly in lspci, to be sure that the card is
> showing up r
On Mon, Aug 16, 2021 at 9:17 PM Samuel Thibault wrote:
> > > I'd rather see a
> > > hurd-specific libpciaccess function to get the pager.
> >
> > That's better, but we'd have to add that function in both hurd_pci.c and
> > x86_pci.c. I don't like the idea of adding Hurd specific code to x86_module
And another lspci from the installer in AHCI mode
El lun, 16 ago 2021 a las 21:17, Almudena Garcia (<
liberamenso10...@gmail.com>) escribió:
> Another lspci from Manjaro Linux in live mode, enabling AHCI in BIOS
>
>
>
>
>
> El lun, 16 ago 2021 a las 21:11, Almudena Garcia (<
> liberamenso10...@gm
Sergey Bugaev, le lun. 16 août 2021 21:59:47 +0300, a ecrit:
> On Mon, Aug 16, 2021 at 9:17 PM Samuel Thibault
> wrote:
> > > > I'd rather see a
> > > > hurd-specific libpciaccess function to get the pager.
> > >
> > > That's better, but we'd have to add that function in both hurd_pci.c and
> > >
Almudena Garcia, le lun. 16 août 2021 20:52:07 +0200, a ecrit:
> After install Debian GNU/Hurd in "compatibility" mode in a Thinkpad T410, I've
> found many getty errors which avoid the access to the tty.
>
> It seems any errors in the paths generation, which generates a bad path for
> the
> tty
> It rather looks to me like it's the Hurd console which cannot start for
some reason, and that's where you want to investigate.
What do I have to search? I only have access via Rescue Mode
El lun, 16 ago 2021 a las 21:30, Samuel Thibault ()
escribió:
> Almudena Garcia, le lun. 16 août 2021 20:52
It's lspci -n that we need, to be able to know exactly what this is.
Otherwise it's about randomly grepping in pci.ids to divine what that
could actually be.
Samuel
Almudena Garcia, le lun. 16 août 2021 20:47:02 +0200, a ecrit:
> > Alternatively you could try to reboot to have the partition re-read. But
> > still it's not expected that partition re-read doesn't work, it is
> > implemented and works in my tests. As usual, actual error messages are
> > what you
lspci -n results
El lun, 16 ago 2021 a las 21:36, Samuel Thibault ()
escribió:
> It's lspci -n that we need, to be able to know exactly what this is.
> Otherwise it's about randomly grepping in pci.ids to divine what that
> could actually be.
>
> Samuel
>
The installer detects the size correctly
El lun, 16 ago 2021 a las 21:38, Samuel Thibault ()
escribió:
> Almudena Garcia, le lun. 16 août 2021 20:47:02 +0200, a ecrit:
> > > Alternatively you could try to reboot to have the partition re-read.
> But
> > > still it's not expected that partition re-
Almudena Garcia, le lun. 16 août 2021 21:41:17 +0200, a ecrit:
> The installer detects the size correctly
That doesn't mean that drivers can actually write that far.
Samuel
Almudena Garcia, le lun. 16 août 2021 21:32:38 +0200, a ecrit:
> > It rather looks to me like it's the Hurd console which cannot start for some
> reason, and that's where you want to investigate.
> What do I have to search? I only have access via Rescue Mode
You can disable the hurd console from /
Almudena Garcia, le lun. 16 août 2021 21:40:13 +0200, a ecrit:
> lspci -n results
And with -v ?
Note that I'm wondering about the so-called AHCI mode, not the
IDE-compatible mode which shows an IDE interface that, as you have
experienced, gnumach is fine with.
Samuel
> And with -v ?
Check attached image
El lun, 16 ago 2021 a las 22:03, Samuel Thibault ()
escribió:
> Almudena Garcia, le lun. 16 août 2021 21:40:13 +0200, a ecrit:
> > lspci -n results
>
> And with -v ?
>
> Note that I'm wondering about the so-called AHCI mode, not the
> IDE-compatible mode which
On Mon, Aug 16, 2021 at 10:28 PM Samuel Thibault
wrote:
> Sergey Bugaev, le lun. 16 août 2021 21:59:47 +0300, a ecrit:
> > IMO the proper way to get mremap () is vm_remap ()
>
> But that doesn't answer Joan's need for getting a memory object, to be
> able to put a proxy memory object on top of it
I'm fine with using proxies if that happens to be optimized.
But I'm sad seeing FIXME, XXX, etc. in various places that people don't
take the time to implement, and they work around them.
This week-end, I at last managed to get rid of the horrible rmh
kludge in glibc that hurt us several times, a
Almudena Garcia, le lun. 16 août 2021 22:19:15 +0200, a ecrit:
> > And with -v ?
> Check attached image
Ok, so it does say that it provides the AHCI interface. I don't
know why gnumach doesn't pick it up then, investigation is needed
with actually gnumach messages, possibly adding more printfs in
On Mon, Aug 16, 2021 at 11:43 PM Samuel Thibault
wrote:
> Here, possibly proxies can indeed work properly. But please do look at
> what Joan's situation is to make sure it does.
I don't think I understand enough about the situation. It would help
if you or Joan were to kindly give me some more co
Ok. Tomorrow I will repeat the test in a T60 or similar model, older than
this, which probably use 32-bit busses.
I will report the results
El lun, 16 ago 2021 a las 22:45, Samuel Thibault ()
escribió:
> Almudena Garcia, le lun. 16 août 2021 22:19:15 +0200, a ecrit:
> > > And with -v ?
> > Check
Sergey Bugaev, le mar. 17 août 2021 00:07:29 +0300, a ecrit:
> On Mon, Aug 16, 2021 at 11:43 PM Samuel Thibault
> wrote:
> > Here, possibly proxies can indeed work properly. But please do look at
> > what Joan's situation is to make sure it does.
>
> I don't think I understand enough about the si
Almudena Garcia, le lun. 16 août 2021 23:05:59 +0200, a ecrit:
> Ok. Tomorrow I will repeat the test in a T60 or similar model, older than
> this,
> which probably use 32-bit busses.
I don't think that's the problem.
And we want to fix the problem anyway.
Samuel
On Tue, Aug 17, 2021 at 12:10 AM Samuel Thibault
wrote:
> Yes, and we want to implement nesting: providing a sub-hurd with a
> partial view of the PCI space.
Interesting. But I still don't think I understand what the problem you
are running into.
boot(1) already emulates Mach devices; it would i
Hi,
While it's relatively easy to create an account on the Hurd wiki[1] and
to edit it, everything is in http.
So at the account creation and during the login, the password is most
probably transmitted in clear.
Would it be possible to fix that?
References:
---
[1]http://darnassus.sceen
Sergey Bugaev, le mar. 17 août 2021 00:30:34 +0300, a ecrit:
> On Tue, Aug 17, 2021 at 12:10 AM Samuel Thibault
> wrote:
> > Yes, and we want to implement nesting: providing a sub-hurd with a
> > partial view of the PCI space.
>
> Interesting. But I still don't think I understand what the problem
After change to mach console, I report that the getty error is not the
cause of the keyboard lock.
The getty errors continues appearing, but I can using the keyboard in the
tty.
Now I have to find the cause of the lock: I've disable the kbd repeater (in
other times, this was the cause) and re-enab
Almudena Garcia, le mar. 17 août 2021 00:01:21 +0200, a ecrit:
> After change to mach console, I report that the getty error is not the cause
> of
> the keyboard lock.
> The getty errors continues appearing, but I can using the keyboard in the tty.
That doesn't mean that getty is not an underlyin
> dpkg-reconfigure hurd
It shows many errors
*pruebas@debian:~$ sudo dpkg-reconfigure hurd*
*[sudo] password for pruebas: Setting up translators: /hurd/exec
/hurd/proxy-defpager /hurd/pflocal (+link) inet (+link) inet6 (+link)
/hurd/pci-arbiter /hurd/acpi /hurd/shutdown /hurd/password cr
ups, wait to translate
*pruebas@debian:~$ sudo dpkg-reconfigure hurdSetting up translators:
/hurd/exec /hurd/proxy-defpager /hurd/pflocal (+link) inet (+link) inet6
(+link) /hurd/pci-arbiter /hurd/acpi /hurd/shutdown /hurd/password
crash-kill crash-suspend crash-dump-core crash.Creating d
Almudena Garcia, le mar. 17 août 2021 00:52:15 +0200, a ecrit:
> ups, wait to translate
>
> pruebas@debian:~$ sudo dpkg-reconfigure hurd
> Setting up translators: /hurd/exec /hurd/proxy-defpager /hurd/pflocal (+link)
> inet (+link) inet6 (+link) /hurd/pci-arbiter /hurd/acpi /hurd/shutdown /hurd/
>
After a `apt upgrade`, the problems seems fixed
The upgraded packages are
* apt apt-utils cpio libapt-pkg6.0 libatspi2.0-0 libc-bin libc-l10n
libc0.3 libdw1 libedit2 libelf1 libepoxy0 libgdk-pixbuf-2.0-0
libgdk-pixbuf2.0-common libglib2.0-0 libidn2-0 locales*
El mar, 17 ago 2021 a las 0:56
Hi Almu,
You need to select "AHCI" in bios - not "Compatibility"!
"lspci -nn" on my w520 with coreboot shows:
00:1f.2 SATA controller [0106]: Intel Corporation 6 Series/C200 Series Chipset
Family 6 port Mobile SATA AHCI Controller [8086:1c03] (rev 05)
I think the compatibility mode makes it ap
34 matches
Mail list logo
