Also please check if you have an option to add a pci function(BDF) as boot
device, if so, please add the BDF and change the boot order to point to
newly added boot device as first boot device.
Thanks
Neeraj
On Wed, Mar 12, 2014 at 6:42 PM, Neeraj Ladkani wrote:
> >> I think, that's no the reas
>> I think, that's no the reason not to register the driver (entrypoint
code). Block IO installs in the START section (not in entrypoint) of my
driver.
Since your device pci config will report it as storage adapter( before even
finding out optom rom details) , it can be assumed that this adapter w
> 11.03.2014, 20:34, "Igor Sharovar" :
> Is your driver present in a list of PCI devices if you run "pci" Shell
> command?
> Igor Sharovar
Not driver, but my device present in a "pci" list.
In drivers list after "drivers" command my driver not present.
But after "loadpcirom" - my driver present
Is your driver present in a list of PCI devices if you run "pci" Shell
command?
Igor Sharovar
On Tue, Mar 11, 2014 at 7:46 AM, Neeraj Ladkani wrote:
> Can you try disabling SATA/RAID and other on board storage controllers ?
> there might be a possibility that BIOS finds block IO protocol produc
Can you try disabling SATA/RAID and other on board storage controllers ?
there might be a possibility that BIOS finds block IO protocol produced by
primary storage controller and skips loading your adapter's oprom (I am
assuming your adapter is a storage adapter) since this is a desktop board
Neer
: Onipchuk Vladimir [mailto:v-onipc...@yandex.ru]
Sent: Tuesday, March 11, 2014 4:43 PM
To: Bill Paul; edk2-devel@lists.sourceforge.net
Subject: Re: [edk2] PCI OpROM driver
Ok, I'm finally realized, that my driver doesn't start on the DH67BL (
http://www.intel.com/content/www/us/en/motherboar
Ok, I'm finally realized, that my driver doesn't start on the DH67BL (
http://www.intel.com/content/www/us/en/motherboards/desktop-motherboards/desktop-board-dh67bl.html
)
My experiments:
1) This code at the Entrypoint:
> [...]
>
> UINTN msgSize;
> CHAR16 msg[] = L"Hello, is this thi
Of all the gin joints in all the towns in all the world, Neeraj Ladkani had to
walk into mine at 00:16:26 on Friday 07 March 2014 and say:
> very basic input... sometime on specific platforms, PCIe oprom execution is
> disabled by default , please check in UEFI Setup -> PCI device->
> ->Option Ro
On Mar 6, 2014, at 11:55 PM, Onipchuk Vladimir wrote:
>
>
> My DEBUG prints uses .
In the edk2 there is not a 1 to 1 mapping between a Library Class and a Library
Instance.
The driver includes a generic include, , that is the public
interface of the library class. Then the INF file list t
very basic input... sometime on specific platforms, PCIe oprom execution is
disabled by default , please check in UEFI Setup -> PCI device->
->Option Rom Execution might be disabled.
Thanks
Neeraj
On Fri, Mar 7, 2014 at 1:25 PM, Onipchuk Vladimir wrote:
>
>
> My DEBUG prints uses .
> Even i
My DEBUG prints uses .
Even if all DEBUG prints turned off, "dh" command (UEFI shell) must print all
device handles with registered protocols.
But even driver binding and component name protocols (installed in entrypoint
of my driver) not displayed.
After "loadpcirom" this protocols displayed
On Mar 6, 2014, at 5:57 AM, Onipchuk Vladimir wrote:
> My DEBUG print samples:
>
> DEBUG ((EFI_D_INFO, "SUPPORTED!\n"));
>
EFI_D_INFO could be turned off on this platform.
> or
>
> if (EFI_ERROR (Status)) {
> DEBUG((EFI_D_ERROR,"Install BLOCK_IO protocol error - %x\n",Status));
> goto ON_
My DEBUG print samples:
DEBUG ((EFI_D_INFO, "SUPPORTED!\n"));
or
if (EFI_ERROR (Status)) {
DEBUG((EFI_D_ERROR,"Install BLOCK_IO protocol error - %x\n",Status));
goto ON_ERROR;
}
Using Print() function in driver causes boot process freezing.
06.03.2014, 17:38, "Andrew Fish" :
> On Mar 6,
On Mar 6, 2014, at 3:27 AM, Onipchuk Vladimir wrote:
> Neeraj,
>
> oh no, I mean checking on the non-problematic platform (DG41TX in my case).
> On the problematic platform, I can't even print debug message at the start of
> my code. So I think, my driver not executing at the platform initial
Neeraj,
oh no, I mean checking on the non-problematic platform (DG41TX in my case).
On the problematic platform, I can't even print debug message at the start of
my code. So I think, my driver not executing at the platform initialization
stage.
"dh" command results (from the UEFI shell) has no
Onipchuk,
How do you say "protocol checking completed successfully" during system
boot, if you were able to print the return value, it means your driver was
executing... first please confirm if your driver is not at all executing or
it failing to produce desired protocol ?
Thanks
Neeraj
On Thu
Thanks Igor and Neeraj for your answers.
Device ID passed in EfiRom = Device ID in the PCI config space.
Protocols checking completed successfully.
Maybe platform skips option ROMs?
Or platform must check all OpRom drivers (and execute entrypoints) ?
06.03.2014, 00:04, "Igor Sharovar" :
> Anot
Another problem could be that you not correctly report Device ID in efirom
utility. Some UEFI BIOS implementation don't care about Device ID, reported
in a OptionalRom image, but some does. You should check what you report
when execute efirom.
Igor Sharovar
On Wed, Mar 5, 2014 at 5:54 AM, Neeraj
if you are trying to locate a specific protocol from your driver, it might
not installed during boot process so it doesn't work, but when you execute
it from shell the consumed protocol might already been loaded by some other
driver so it works.
please check the protocol you are trying to locate
Hi All,
I have problems with the my PCI OpRom device driver on some platforms.
Driver executing successfully on the old DG41TX motherboard, but on the DH67BL
and on the some new HP motherboards driver does not loading from OpRom on the
PCIe card (probably, even entrypoint does not executing).
B
Hi All,
I have problems with the my PCI OpRom device driver on some platforms.Driver executing successfully on the old DG41TX motherboard, but on the DH67BL and on the some new HP motherboards driver does not loading from OpRom on the PCIe card (probably, even entrypoint does not executing).Boot p
21 matches
Mail list logo
