> But then it has its own bugs, which will be much easier to track down in
kvm.
Ok, wait that my information makes useful
El mar, 17 ago 2021 a las 20:03, Samuel Thibault ()
escribió:
> Almudena Garcia, le mar. 17 août 2021 19:49:11 +0200, a ecrit:
> > Ok, then I will regret to compatibility mode
Almudena Garcia, le mar. 17 août 2021 19:49:11 +0200, a ecrit:
> Ok, then I will regret to compatibility mode. I was interested to check if the
> new SATA AHCI driver is able to work in a real machine
Well, apparently it does work indeed.
But then it has its own bugs, which will be much easier to
Ok, then I will regret to compatibility mode. I was interested to check if
the new SATA AHCI driver is able to work in a real machine
Thanks for your help
El mar, 17 ago 2021 a las 19:38, Samuel Thibault ()
escribió:
> Almudena Garcia, le mar. 17 août 2021 19:19:34 +0200, a ecrit:
> > In rescue
Almudena Garcia, le mar. 17 août 2021 19:19:34 +0200, a ecrit:
> In rescue mode, I tried to reinstall GRUB in /dev/wd0s1, but It seems that
> GRUB
> don't find the disk.
Yes, confusingly grub always calls disks hd0, hd1, etc, whether it is
AHCI, IDE, SCSI or whatever.
> Although the rescue mode
Almudena Garcia, le mar. 17 août 2021 18:49:07 +0200, a ecrit:
> Ok, the change of naming to /dev/sd0s1 in fstab failed. The boot continues
> using the device /dev/hd0s1
That will be solved by an update-grub call.
But again, it's completely useless to look at this, as long as sd0 is
not actually
On Tue, Aug 17, 2021 at 7:44 PM Almudena Garcia
wrote:
> But, in fstab, the drives are registered as /dev/hd0s1 (root partition in
> harddisk), and /dev/hd2 (cdron drive).
> I can try to change them to sdX naming, but is a bit risky
fstab only comes into play later in the boot process (certainly
Almudena Garcia, le mar. 17 août 2021 18:43:38 +0200, a ecrit:
> But, in fstab, the drives are registered as /dev/hd0s1 (root partition in
> harddisk), and /dev/hd2 (cdron drive).
Yes, because that was how it was during the debian installer. Think the
BIOS compatibility/AHCI switch as "I unplug th
Ok, the change of naming to /dev/sd0s1 in fstab failed. The boot continues
using the device /dev/hd0s1
El mar, 17 ago 2021 a las 18:43, Almudena Garcia (<
liberamenso10...@gmail.com>) escribió:
> But, in fstab, the drives are registered as /dev/hd0s1 (root partition in
> harddisk), and /dev/hd2 (
But, in fstab, the drives are registered as /dev/hd0s1 (root partition in
harddisk), and /dev/hd2 (cdron drive).
I can try to change them to sdX naming, but is a bit risky
El mar, 17 ago 2021 a las 18:33, Samuel Thibault ()
escribió:
> Almudena Garcia, le mar. 17 août 2021 18:26:24 +0200, a ecrit
Almudena Garcia, le mar. 17 août 2021 18:26:24 +0200, a ecrit:
> Really, there are not any sd0 device, I think.
Really, in AHCI mode, yes, it is to be sd0, not hd0.
hd0 is only in IDE mode.
> But the SATA driver search this sdX device
The SATA driver doesn't search for sdX, it *provides* sdX. W
Really, there are not any sd0 device, I think. The harddisk is hd0.
But the SATA driver search this sdX device
El mar, 17 ago 2021 a las 18:20, Samuel Thibault ()
escribió:
> Almudena Garcia, le mar. 17 août 2021 18:02:49 +0200, a ecrit:
> > I tried, but not boot.
>
> Well that was expected since
Almudena Garcia, le mar. 17 août 2021 18:02:49 +0200, a ecrit:
> I tried, but not boot.
Well that was expected since it's the same kernel as in the debian
installer.
> I attach some images
> ahci: 00:1f.2: Port 0 communication not established. TODO: power on device
> sd0: timeout waiting for re
Almudena Garcia, le mar. 17 août 2021 16:02:55 +0200, a ecrit:
> The installation in compatibily mode works correctly, the fail in with the
> installation in AHCI mode, which fails after partition step
Now that you have it installed in compatibily mode, could you try to
boot it in AHCI mode, to se
The installation in compatibily mode works correctly, the fail in with the
installation in AHCI mode, which fails after partition step
El mar, 17 ago 2021 a las 16:01, Almudena Garcia (<
liberamenso10...@gmail.com>) escribió:
> > You need to select "AHCI" in bios - not "Compatibility"!
> I did it
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
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
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
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
> 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
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
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
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-
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
>
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
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
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
> 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
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
28 matches
Mail list logo
