Jump to content
10 posts in this topic

Recommended Posts

Hi all,

 

after i sucessfully installed iDeneb 1.4, i booted into the system, but i was stuck at a blue screen. not a BSOD but a simple blank blue screen with mouse moving.

 

I become crazy with this, but finally I found that I simply need to set the system into sleep once by pushing the powerbutton, and wake up the system, after this the screen graphics appear and everything work fine (resolution ok, all function enabled). If I try to change resolution I have again the blue screen and I have to make the same operation for the dashboard coming back.

 

I already tried to install all possible driver that I found for HD3850, but I always have the same issue. Now I'm using the EFIStudio_extended solution with MEGALODON driver.

 

Does anyone have a suggetion on how to resolve this issue?

 

Thanks

 

 

my specs:

graphic: ati Sapphire HD 3850 512m

mb: asus m2npv-vm

cpu: amd Athlon 5000+ dual core

monitor: HP w19b connected with DVI cable (with VGA I have the same issue!!!!)

Have you tried the other DVI Port ?

I would shut down , switch moni cable to other port and try again if that helps.

38XX are sometimes an nightmare.

 

Also check if you not forgot to remove any natit.kext / other gpu injectors.

If missed removing, remove and also remove that extensions.mkext.

Have you tried the other DVI Port ?

I would shut down , switch moni cable to other port and try again if that helps.

38XX are sometimes an nightmare.

 

 

Tried, but nothing change.

 

 

Also check if you not forgot to remove any natit.kext / other gpu injectors.

If missed removing, remove and also remove that extensions.mkext.

 

 

I don't have natit.kext and I remove extension.mkext and reboot, but again nothing change! How can I understand if have other gpu injectors that I should remove?

 

One more question: is not possible taht the issue is not related to the Graphic card but to the mobo ACPI bios or to the monitor, or may be to the monitor cable? I'm trying any possible solution, I really do not understand!

 

Thanks.

You can try to set your PCIe as default (first gpu device) if BIOS allows that.

ATI drivers sometimes have problems to see connected devices. NVidia work very different in this case (may have other "voodoos").

 

which OS X of idebeb do you have ?

MegadolonFB needs normally at least 10.5.6.

 

Normally the EFI_STUDIO_EXTENDED (setting to Megadolon) works very well with the ATI3850. I have this card, but its an MSI DDR3.

 

www.rapidshare.com/files/234653525/EFIStudio_EXTENDED.zip

 

 

I know only , ATI_INIT.kext (newest) , natit.kext and nvcush.kext for gpu injectors.

I have iDeneb 1.4, so I have 10.5.6, and I also update to 10.5.7 with the last released Combo Upgrade Kit. PCIe is already set in the bios as default card.

 

But what is really strange is that my card is working perfectly after performing the "stand-by" operation. It only don't show the dashboard on first start-up. I also tried to change the bios card with other version, but I always obtain the same result.

 

Many thanks.

Hard problem.

I woud also check the system.log (with Console) if there any gpu error+warning messages are shown.

 

 

My last hint:

repair permissions and try to boot once with kernel flag -f (load all drivers, recreates kextcache).

 

If that also not works i would change the headline of your tread a bit, because that "sleep/wakeup" workaround maybe know for an special problem and so better hints can come.

LIKE: HD3850 Blue Screen , but after sleep/wakeup all OK?!

I had the same prob with my 3850 installing 3 different builds.

 

Boot the the -x option for safe mode.

 

When in safe mode, install the ATi universal injector/enabler from netkas blog.

 

I'm sure it will work, it did for me.

 

here's the link: http://netkas.org/?p=104

Unfortunately also the 2 last suggestion doesn't solve my problem, always same behavior!!!

 

@OfficerJackMehoff: with which distribution / kernel did your solution work? Which system do you have (Intel or AMD)?

 

 

@mich_de: How should I check the system log? What I should do?

No problem for me if you want to change the headline of the thread, I'll be happy if the workaround can be at least helpfully to other people.

 

And thanks a lot to everybody!!!!

with which distribution / kernel did your solution work? Which system do you have (Intel or AMD)?

 

iPC, the 10.5.6 version. I am using an altered kernel, the voodoo 9.5.0 kernel. No distro would work for me without it. I have a dominantly AMD system, which I consider a stark disadvantage in this situation. If I would have known I could build a mac pro (nearly equivalent) for ~$1200, I definitely would have :)

  • 5 months later...

Same problem here. Specs:

graphics: Gigabyte ATI Radeon 2400XT

mainboard: Asus M2NPV-VM (the same!!!!!)

distro: ideneb 1.3 (10.5.5) updated to 10.5.7

 

Guess which framebuffer I'm using: Megalodon

 

I know another workaround: Start Windows (or a Windows install disk) and then restart. OS X will work perfectly. It won't work with linux, it has to be windows.

×
×
  • Create New...