From c4ad3f73033c7e0511c3e7df961e1232cc503478 Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Wed, 26 Feb 2014 12:32:06 +0100 Subject: IRC. --- faq/sata_disk_drives/discussion.mdwn | 92 +++++++++++++++++++++++++++++++++++- 1 file changed, 91 insertions(+), 1 deletion(-) (limited to 'faq/sata_disk_drives') diff --git a/faq/sata_disk_drives/discussion.mdwn b/faq/sata_disk_drives/discussion.mdwn index d05566b6..0b56f235 100644 --- a/faq/sata_disk_drives/discussion.mdwn +++ b/faq/sata_disk_drives/discussion.mdwn @@ -1,4 +1,4 @@ -[[!meta copyright="Copyright © 2013 Free Software Foundation, Inc."]] +[[!meta copyright="Copyright © 2013, 2014 Free Software Foundation, Inc."]] [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable id="license" text="Permission is granted to copy, distribute and/or modify this @@ -256,3 +256,93 @@ License|/fdl]]."]]"""]] youpi: hm, I think my board has no ahci controller, linux uses the sata_via module to talk to it :/ ah :/ + + +# IRC, freenode, #hurd, 2014-02-05 + + teythoon: i don't completely trust the driver + oh ? + it doesn't work on my laptop, and i had a failure once on a "big" + partition of 128G + hm + my hardware does not implement ahci, but in qemu it works fine + for me + well qemu is the only supported "hardware" + but then my partitions are not that big + braunr: no, it does work on my laptop too + ok + + +# IRC, freenode, #hurd, 2014-02-12 + + youpi: hum, sorry to ask but how do you use qemu to provide sata ? + braunr: there's an important trick: getting it on another IRQ than + the eth0 board :/ + -device ahci,id=ahci1 + for nothing + -device ahci,id=ahci2 + -drive id=root,file=/dev/${HDA}7,cache=writeback,if=none + -device ide-drive,drive=root,bus=ahci2.1 + ok that's close enough to what i have + but + i'm using /dev/sda as the backend + instead of a regular file + sda already containing a regular debian linux system + and grub2 can't boot because it seems to fail reading the + partition table + it works perfectly when accessing it as an ide disk though + youpi: do you see any reason why grub would fail with ahci ? + also, why ahci2._1_ instead of 0 ? + youpi: fyi, the cd installer always booted fine here, both on my + workstation and my laptop, i did about 50 tries on each machine + the graphical mode doesn't seem to work though + youpi: fyi2 the grub related issue i'm having is + https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692249 + I'm using .1 because I have a /boot .0 before the / .1 :) + humm + you have two drives ? + braunr: (cd installer): you mean, even in semi-graphical mode? + one for /boot and the other for / ? + I have 3 actually :) + youpi: no, xorg + ok i se + see + (cd installer) I'm talking about the working ones :) + I know xorg does not boot + ok + so apparently, adding ,boot=on to the -drive parameter did the + trick + k + and now, i have a hurd system running from /dev/sda5 (the real + disk) in qemu + for the pseudo-graphical console, I guess his monitor is too dumb + to be able to display 640x400 + possible + most probably because no OS uses that any more nowadays :/ + (and that won't get better) + so now i can debug ahci on my laptop using that :) + + youpi: is there a known limit to the size of an ahci drive in the + gnumach driver ? + in the driver itself, it's simply lba48 + but the mach interface uses 32bit sector number + thus 2TB limit + that's plenty :) + I have a 2TB drive :) + so it won't be plenty for long + 2TB for your hurd system ? + no, for my backups etc. + i meant plenty for our hurd instances + but there could have been a hurd vm there + and not necesseraly below 2TiB + + hm, the installer doesn't detect existing partitions on an ahci + drive :/ + + +## IRC, freenode, #hurd, 2014-02-13 + + youpi: looks like linux has trouble handling my ahci drive without + ioapic/msi + no wonder gnumach can't either + erf -- cgit v1.2.3