grub not detect hdd or usb

hi

when boot grub4dos from hdd and i want to use some file from usb drive grub not detect hd1 as usb what can i do?

(or if i use plpbt to boot from cd and then boot to usb (my pc not support to boot from usb!!) then i have hd0 as usb and not detect hd1 ad hard disk ??)

sorry for bad english!!

What is the problem? Are you using a grub4dos menu to boot something? If so, please give menu lines to us.

no, i use command to boot but when i install grub to hard disk and boot and connect usb masstorage to pc grub not detect the usb

when use find command, only show (hd0,0), (hd0,1), ... and i cant access to usb storage

grub4dos 0.4.5c does not contain any USB controller drivers.

If you boot from USB then BIOS uses its USB drivers and maps the USB drive as hd0.

If you boot from HDD then the BIOS does not map the USB drive at all and so the BIOS does not know of the USB drive.

So when you boot from HDD to grub4dos, there will be no USB devices.

However, grub4dos 0.4.6a has a USB 2.0 driver.

1. Download the latest version of 0.4.6a (2015-02-28) from here

2. Copy the grldr file to your HDD and overwrite the one that is already there

3. Boot to grub4dos from the HDD

4. Connect USB drive to USB 2.0 port

5. In grub4dos command shell type 

find
usb --init
find

If the grub4dos driver works, you should now have an accessible USB drive?

hi

but on vmware error 81. no usb device found, show

Forget vmware do what Steve6375 said in your real machine it has to work with your USB. Unless there is someting wrong with your USB device (try mother board USB ports first).

@Steve6375 : Hi ! I've checked the very latest 0.4.6a binary and peeked inside 

source code (asm.S where the - impressive -  USB stuff resides) : unfortunately,

it still assumes USB disk's sector size = 512 bytes - that is hard coded   :=(

Am i assumming right that you Steve are in contact with Chenall and/or Yaya (I think

Yaya is grub4dos's USB-man...) ?

IFF you are able to contact someone there, would you please ask them the question

about if (and when) they are going to address this problem - i.e. process USB

( and hopefully also other) disks having 4096 bytes per sector !

Support thereof has been badly wanted for several years now !

Thanks in advance ! 

Edited by Ninho, 03 March 2015 - 06:48 PM.

Double-post, sorry - ignore !

Edited by Ninho, 03 March 2015 - 06:46 PM.

Triple trouble- sorry. Ignore !

Edited by Ninho, 03 March 2015 - 06:47 PM.

It has already been requested previously but most (all?) USB BIOSes don't support 4k USB disks, so you can't even boot to grub4dos anyway!

So the answer has been 'don't hold your breath!'

You can log a request here - if you can specify a system/BIOS that supports int13h native 4k sector support...

thanks instant answer !

if you can specify a system/BIOS that supports int13h native 4k sector support..

Uh, no, USB support through BIOS is not what I'm asking here,

if BIOS could do it by itself Grub'4DOS support wouldn't be needed  

:=)

New G4D version 0.4.6a has its own USB-EHCI mass-storage class - doesn't use

the BIOS, the sad fact is at the moment, for some odd reason they have hard-coded

sector sizes to 512 bytes. The hard part is done - USB is hard! - I'm confident

it would not be extremely hard, in comparison, to add the 4K sector case

for them who know their code intimately... 

Then for boot support (chainloading) , it'll be trivial to load a 4K boot sector or MBR 

to memory at absolute 00007C00 and start execution there... 

As another useful application, boot/chainload an OS from another disk

but keeping GRUB4DOS's EHCI driver as the USB BIOS...

You can log a request here...

Aye ! Good, I'll do that !

Edited by Ninho, 03 March 2015 - 07:21 PM.

But how do you boot to grub4dos in the first place?

[q]But how do you boot to grub4dos in the first place?[/q]

Well... from another, supported, disk that can boot the machine up to Grub4DOS, of course... 

So you want to boot from an MBR-bootable 512 byte disk via BIOS int 13h to grub4dos - run the usb --init command to install the USB 2.0 grub4dos driver which can support 4K USB disks and then access those 4K disks from grub4dos? 

I guess that is possible, but the current USB drive is not very good. It only supports USB 2.0 controllers and does not work with as many different controllers as Plop does (though the grub4dos driver is rd/wr and not just read-only like Plop is).

So you want to boot from an MBR-bootable 512 byte disk via BIOS int 13h to grub4dos - run the usb --init command to install the USB 2.0 grub4dos driver which can support 4K USB disks and then access those 4K disks from grub4dos? 

Right!

I guess that is possible, but the current USB drive is not very good. It only supports USB 2.0 controllers and does not work with as many different controllers as Plop does (though the grub4dos driver is rd/wr and not just read-only like Plop is).

Plop's is not an option, at the moment, for 2 reasons : it's read only, and the 'experimental' 4K support doesn't not work

in addition, I think, Elmar lost interest / isn't working at it   :=(

= Grub4DOS " usb -- init " does not detect tje USB-EHCI controller on a machine that has

a VIA USB2 PCI adapter  :=( .

That older Dell machine's native Intel chipset only does UHCI , i.e. USB1.1

Is failure to detect EHCI add-on adapters expected ?

= I posted the previous request (about 4KByte sectors; upthread) to Chenal's Github

a week ago, but no sign of any activity there. Are you sure they check the log ?

I'd need to ping "Yaya" in particular, he's "Mr USB" I think, is there a

way to get his (or Chenal's) attention ? Have an email ?

Edited by Ninho, 13 March 2015 - 04:13 PM.

The USB controller detection is limited and only USB 2.0 adapters.

You can report it as an issue, but list PCI ID (use E2B - Utilities - Show Mass Storage Contoller PCI IDs.)

They do check the issues log daily. But of the request is difficult then they need time to study it. If it is easy to fix they will fix in a day or so.

As I said, the 4K sectors request has already been made previously and they said they don't currently intend to support it.

 The USB controller detection is limited and only USB 2.0 adapters.

Yes i'm aware Grub4dos does USB 2.0 only (EHCI). But i haven't read any indication that it would not

work with add-on PCI USB 2, have there been reports of not detected USB 2.0 ? 

 They do check the issues log daily. 

Alright then, wait'n'see... I'm going to add a log for the undetected VIA add-on board.

Thanks

As I said, the range of controllers that it works with is limited. Older USB 2 controllers may work, but Plop seems to work on some systems that grub4dos USB driver does not. Newer controllers don't seem to be detected. e.g. Haswell Z87.

Today's latest commit by Yaya2007 resolves the issue (#49) ! There's a man !

 Now if only he would look at the more important (in my opinion) issue of 4K-sectors !

Steve, am I right assuming he, Mr. Yaya, is the same person, Yaya Diy,  who gave us an upgraded

"Di1000dd.sys" USB MSD driver for DOS systems ?

I lose the USB keyboard after running usb --init with the new version of grub4dos on my Haswell Z87A - so not such a good bugfix...

I lose the USB keyboard after running usb --init with the new version of grub4dos on my Haswell Z87A - so not such a good bugfix...

Too bad ! Please report the bug there I'm seeing you reported the bug...

Me, don't know, I'm using PS2-port connected keyboards only.

Edited by Ninho, 18 March 2015 - 02:15 PM.