Coreboot and SeaBIOS

[inaxeon]

Guys. If you want to be handy while I have some time off, do some googling for me.

The hang you're all whinging about is caused by a driver called "msisadrv.sys"

The only information I've been able to dredge up on it so far is from a WinHEC powerpoint presentation which states:

* Contains routines to manage an ISA bridge
* Allows exporting an interrupt translator interface from the HAL
* Required to support PS/2 keyboards and mice

That isn't enough for me to narrow down the problem. I need to know more. Anything is useful!

Dan has already dug up some killer useful info on the i8042 problem. Let's have some more of it!

[danfoshizzle]

Will go google-fu on this tomorrow!

[inaxeon]

Aside from the question of 'what is it' - The other thing I was thinking, is there some way to stop it loading? registry hack? if so, and that makes it more reliable, that'd be an interesting observation.

[pete]

Here's the patched ntdetect.com. Here its booting a bunch of colors. But it never stops booting. I went to putting a working copy of XP on a USB to ZIF drive.

[mickchip]

msisadrv.sys all I have found

•Msisadrv.sys is a PE style file.
•This program does not appear to be internally referenced by any other file.
•The file msisadrv.sys is a device driver. It is included as part of the standard Windows file set from Microsoft. The driver is loaded as part of the Boot Bus Extender group. Depending on the hardware and installation type it may not be active.

Changes in Windows Vista and Windows Server 2008
Windows Vista and Windows Server 2008 continue to provide isapnp.sys, but this driver is not loaded by default. As a first step toward completely removing legacy ISAPnP support, Windows Vista and Windows Server 2008 moved reduced support for ISA devices into the driver msisadrv.sys. This driver preserves only minimal functionality and does not provide ISAPnP enumeration and resource assignment support. Msisadrv.sys contains routines to manage an ISA bridge, such as exporting an interrupt translator interface from the HAL, and is required to support legacy devices still prevalent in the platform, such as PS/2 input devices. Windows Vista and Windows Server 2008 will load msisadrv.sys on a PCI-to-ISA bridge device by default. For legacy devices where the platform firmware provides hardware enumeration and resource assignment support, msisadrv.sys will provide the necessary support and these devices will work without issue

[Mevi]

The hang you're all whinging about is caused by a driver called "msisadrv.sys"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\msisadrv]

On my W7 laptop, there is a entry in the registry: "Start"=dword:00000000

I think a value to disable this service would be: "Start"=dword:00000004

I'm away from home right now, so I have no way to test this on a Joggler

All the valid entries for the "start" are:

0 Boot
1 System
2 Automatic
3 Manual
4 Disabled

[mickchip]

That seems to have worked on mine, only tested once upto now
doing this while decorating.
Spoke to soon, second boot didn't work.
Won't boot at all again, another reinstall.

[inaxeon]

That seems to have worked on mine, only tested once upto now
doing this while decorating.
Spoke to soon, second boot didn't work.
Won't boot at all again, another reinstall.

Interesting. I'll try tweaking my registry with the debugger attached and see if its still that holding the system up.

It ain't fixed till you've booted it 50 times without a hang.

The device it's attached to (Under Device manager, System devices, "PCI standard ISA bridge") I notice doesn't have a disable option, so the registry setting Mevi posted will likely be ignored.

Certainly more stuff to look into...

[danfoshizzle]

Well, windows 8 works , sound only through headphone jack, shut down and start up works,metro apps dont work, screen resolution too low, but seems to run a little better than 7, this is on the 0,4 bios, could not get the bios to update via F7.

Ok, cannot get the video driver to install, Inaxeons posted IEGD will not install in windows 8, going to go back to windows 7 as windows 8 runs well but is a little useless without video drivers.

Even a reboot worked on windows 8, just needs some work on drivers, will try Windows 7.

Question for Inaxeon, How would I go about adding windows 8 support to the IEGD driver?

EDIT: Head hurts, staying on win 8 for now, here some pictures!







Ignore the date, forgot to change it lol

[inaxeon]

I can't customise or make any changes to operating system support. Only hardware.

I've never seen any mention of Windows 8 for any IEGD kit. I can imagine that once Intel releases official support, GMA500 support will have long since been dropped (It's already gone in the latest version).

Apparently Win 8 supports the same driver frameworks as Win 7, so it should be able to work, if you can get it to load. Can you describe the exact reason why it wont install?

[danfoshizzle]

INF install fails due to the operating system not being supported, but have been using it with the basic display adaptor driver and its been ok, and yeah after searching around seems as though the only hope would be a gma 500 driver, which from my testing only results on BSOD, (was the same on windows xp before coreboot) Currently trying other poulsbo devices drivers, not had any luck yet though.

[inaxeon]

Well, windows 8 works , sound only through headphone jack

That stuff isn't hard to fix. You're just going to have to learn how the driver's configuration scripts work - and understand exactly how the Joggler's hardware is hooked up. Or am I going to have to do that

[danfoshizzle]

No no, joggler has always been a learning device for me only know what I know now because of it lol

[inaxeon]

and yeah after searching around seems as though the only hope would be a gma 500 driver

It's a complicated story but - The GMA500 driver will never work with the BIOSes I've been providing, or indeed on the Joggler at all - as it stands. Its design doesn't really lend its self to running 'laptop style' GMA drivers.

I know what it would take to get it working, but as a bunch of home brew tinkerers, I don't think we'll be able to get the needed resources from Intel.

If it's just bitching about the INF, you might be able to add some entries in there in Win 8 format, and point it at the same driver files. Shouldn't be too hard.

[danfoshizzle]

Now looking up how to add windows 8 installation to the inf, I knew gma500 was a bitch from when we were starting out with windows xp, always corrupted the installs, but thought I might aswell try them just for tryings sake lol

[danfoshizzle]

Just reinstalling windows 8 now to try my edited inf file, Added NTx86.6.2 support

[Mevi]

Dan, did you natively install w8 on the Joggler or did you install on virtual box first? I installed w8 rtm on virtual box a few nights ago, but was away at a friend's so not able to image my hdd until maybe later tonight. You're already way ahead of me changing the gma500 inf to support 6.2... Just a coincidence I recently stumbleupon a how-to for just this kind of driver support issue we've run into. Good work.

[Mevi]

As for the screen resolution, does the gma500 support screen scaling?

[mickchip]

The gma500 does support higher resolutions but not with the driver we have.
I installed win8 using nt6 fast installer, so its like a native install, it's been the
easiest OS to install for me.

[Mevi]

Windows 8 up and running here too. Working from USB HDD pretty much perfect aside from driver & screen resolution problems.