Join us and the lead editor of IRL, Mozilla's multi-award-winning podcast, for a behind-the-scenes look at the pod and to contribute your ideas for the next season, themed: "AI and ME." Mark your calendar and join our Community Call on Wednesday, Aug 7, 17:00–17:45 UTC. See you there!

Avatar for Username

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

Dieses Thema wurde archiviert. Bitte stellen Sie eine neue Frage, wenn Sie Hilfe benötigen.

Firefox "blacks out" when using switchable graphics

  • 2 Antworten
  • 9 haben dieses Problem
  • 3 Aufrufe
  • Letzte Antwort von dahlner

dahlner
dahlner
more options

Hi,

I have a HP laptop HP Pavilion dv6-6008eo, it has graphic cards: - AMD Radeon HD 6490M (1 GB DDR5) - Mobile Intel(R) HD Graphics When I switch between these, which I do when I plug in/out the charge in order to save battery life, firefox blacks out.

Regards Anders

Hi, I have a HP laptop HP Pavilion dv6-6008eo, it has graphic cards: - AMD Radeon HD 6490M (1 GB DDR5) - Mobile Intel(R) HD Graphics When I switch between these, which I do when I plug in/out the charge in order to save battery life, firefox blacks out. Regards Anders

Alle Antworten (2)

Ted_H
Ted_H
more options

I had the same problem with the HP Pavilion dm4 I started using this week.

I couldn't find any way to stop it from happening within apps. But I found that if you stop it from switching to the power saving adapter (See: http://h30434.www3.hp.com/t5/Notebook-Display-and-Video/I-wish-to-disable-Switchable-Graphics-on-a-DV7-4030ed/td-p/344302) that it stops.

Obviously this impacts your life on battery. But it's a fair tradeoff rather than losing the ability to use any open FF windows. At least until someone can declare a real solution.

dahlner
dahlner Fragesteller
more options

@Ted_H Thanks for the link, I think however that this is a FF-bug to and hopefully there is someone there who can solve the issue! :)

There must be many people out there having our problem!