В Sat, 10 Jan 2015 06:57:25 +0100 adrian15 <[email protected]> пишет:
> I have just found out that I am supposed to run nativedisk command with > modules as arguments. > It has default list of modules to load if no argument is provided. > Well, this is not working very well. At least it's not consistent. > > Please tell me if I should file bugs for: > > * i.e. the "alloc magic is broken" if you try to "nativedisk usbms" > after having done "nativedisk ahci" AND having run ls. Any "alloc magic is broken" is a bug, but before you report it you should compile current upstream GIT version and reproduce it there. Otherwise you should report it to your Linux distribution bug tracker. > * ahci module load aborting virtualbox virtual machine when it's found > as the second argument of nativedisk and possibily after pata. > There is already bug report about it. I tentatively think this is rather a bug in vritual box; but of course if anyone could debug it and come out with explanation what grub does that VB does not like it would be great. > Or if we should not bother at all because I'm not using these commands > as I'm supposed to. > > Thank you. > > # Test 1 > > grub> nativedisk pata > error: no device connected. > error: no device connected. > error: no device connected. > grub> nativedisk ahci > grub> nativedisk usbms > grub> nativedisk ohci > grub> nativedisk uhci > grub> nativedisk ehci > grub> > > # Test 2 (Identical to Test 1 but adding ls commands) > > grub> nativedisk pata > error: no device connected. > error: no device connected. > error: no device connected. > grub> ls > (ata2) (ata2,apple4) (ata2,apple3) (ata2,apple2) (ata2,apple1) > (ata2,gpt3) (ata2,gpt2) (ata2,gpt1) > grub> nativedisk ahci > grub> ls > (ahci0) (ata2) (ata2,apple4) (ata2,apple3) (ata2,apple2) (ata2,apple1) > (ata2,gpt3) (ata2,gpt2) (ata2,gpt1) > grub> nativedisk usbms > alloc magic is broken at 0x7feb8110: 4896602 > Aborted. Press any key to exit. > (Grub is hang). > > # Test 3 > > grub> nativedisk pata ahci > (Virtualbox aborts. You can see Virtualbox log just below). > 00:06:19.698740 AHCI#0P0: Canceled read at offset 0 (32768 bytes left) > returned rc=VINF_SUCCESS > 00:06:20.483363 AHCI#0P0: Canceled write at offset 0 (512 bytes left) > returned rc=VINF_SUCCESS > > # Test 4 (These are the default modules when you run nativedisk without > an argument) > > grub> nativedisk pata ahci usbms ohci uhci ehci > (Virtualbox aborts. You can see Virtualbox log just below). > 00:00:30.868114 AHCI#0P0: Canceled read at offset 0 (32768 bytes left) > returned rc=VINF_SUCCESS > 00:00:31.596667 AHCI#0P0: Canceled write at offset 0 (512 bytes left) > returned rc=VINF_SUCCESS > > I'm using Virtualbox 4.3.20 r96996. > > El 10/01/15 a las 06:24, adrian15 escribió: > > El 10/01/15 a las 06:14, adrian15 escribió: > >> But why every command at grub shell (even: echo $grub_prefix) after > >> running: "insmod ohci" always says: > >> > >> error: disk `hd96' not found. > >>> grub2 has command "nativedisk" that will try to switch from platform > >>> firmware driver (BIOS) to native hardware disk drivers. This may give > >>> you back your disks, but under different names. Note that some commands > >>> will not function, e.g. there is no way to chainload something unless > >>> using BIOS. > >> nativedisk in my virtualbox test also gives me: > >> > >> error: disk `hd96' not found. > > > > Just wanted to make this a bit more clear, and maybe arising another bug. > > > > If I run: > > nativedisk > > after running: > > insmod ohci > > I get: > > error: disk `hd96' not found. > > > > If I just run as the first command (after going to shell from a menu): > > > > nativedisk > > > > the virtual machine aborts with this related virtualbox log (I have > > removed the parts that happened before nativedisk was run). > > I'm using Virtualbox 4.3.20 r96996. > > > > > > adrian15 > _______________________________________________ Help-grub mailing list [email protected] https://lists.gnu.org/mailman/listinfo/help-grub
