GD65: black screen after 4.4ghz with i5 2500k

Hi, I have a problem with my MSI P67A GD65. My cpu is an i5 2500k. I tried to overclock it but if I go over 4.4ghz, despite very high vcore (1.39) does not start windows. The strange thing is that it don't go in BSOD, but the screen stays black or windows crashes a few seconds after the start of the boot process. They said me on an Italian forum (I'm Italian) which is strange, with that vcore windows should start or at least should give me BSOD, no black screen. Can you help me? Thanyou very much
CPU Intel i5 2500k 3.3ghz @ 4.4ghz
Motherboard model MSI P67A GD65 Bios v. 1.70
Memory G.Skill Ripjaws-X 2x2gb 1600mhz cl7 1.5v
Video card Radeon HD 6850 1gb gddr5
Hard drive(s) Samsung Spinpoint F3 7200rpm 16mb
Western Digital Caviar Green 5200rpm 32mb
Any other peripheral cards and devices
Operating system and version Windows 7 Ultimate 64 bit
Power Supply Unit brand and output in watts and DC output (amps) Corsair TX 650w

I would start with updating your BIOS to the latest BETA BIOS Version (v1.8b11) which can be found here: https://forum-en.msi.com/index.php?topic=144655.msg1081923#msg1081923
Set all clock settings back to default before attempting a BIOS Update. >>Use the MSI HQ Forum USB flasher<<
Then retest with the latest version.
Quote
The strange thing is that it don't go in BSOD, but the screen stays black or windows crashes a few seconds after the start of the boot process. They said me on an Italian forum (I'm Italian) which is strange, with that vcore windows should start or at least should give me BSOD, no black screen.
Sorry, but that is basically nonsense. When the overclock settings are unstable, all kind of things can potentially happen: BSODs, freezes, black screen, reboots etc. There is no rule that when a certain VCore is applied the only "right" response would be a BSOD.

Similar Messages

MOVED: GD65: black screen after 4.4ghz with i5 2500k

This topic has been moved to Overclockers & Modding Corner.
https://forum-en.msi.com/index.php?topic=145776.0

I would start with updating your BIOS to the latest BETA BIOS Version (v1.8b11) which can be found here: https://forum-en.msi.com/index.php?topic=144655.msg1081923#msg1081923
Set all clock settings back to default before attempting a BIOS Update. >>Use the MSI HQ Forum USB flasher<<
Then retest with the latest version.
Quote
The strange thing is that it don't go in BSOD, but the screen stays black or windows crashes a few seconds after the start of the boot process. They said me on an Italian forum (I'm Italian) which is strange, with that vcore windows should start or at least should give me BSOD, no black screen.
Sorry, but that is basically nonsense. When the overclock settings are unstable, all kind of things can potentially happen: BSODs, freezes, black screen, reboots etc. There is no rule that when a certain VCore is applied the only "right" response would be a BSOD.

Black Screen after log in with Mountain Lion

For 6 times, in 8 attempts, my retina macbook pro fails to boot up. All goes black after I enter my user password and I have to press the power bottom for 3 sec to restart. It sounds like a system error, and for sure didn't happen before I installed mountain lion, should I attempt to do a fresh install? Or run any tests?
Any advice appreciated.

Hey guys...
Just posted this potential solution over in the forum Clinton mentioned. Not sure if it's a proper fix, but it seemed to work for me.
Cheers...
Had my first experience with this just now. Shut down the MBPr for it's longest off time since getting it last week (about 6 hrs) and logged in to the BSOD.
My go-to solution on any other MacBook has always been the PRAM reset.
Restart your machine. Hold down CMD+OPT+P+R before the gray screen shows up (harder now than on the older, slower machines). Keep holding it down until the startup sound plays 2 or 3 times. Then release the keys and let it boot up normally.
No idea why this works. Don't have any clue what PRAM even is or what it would have to do with all this - but it worked for me. At least this time. Maybe it won't the next!
Hope it helps you all...
http://support.apple.com/kb/HT1379?viewlocale=en_US&locale=en_US

M5400 - Black screen after updating BIOS

As the title says, I've got this unwanted black screen after updating BIOS with update utility from here http://support.lenovo.com/us/en/downloads/ds037429
What I've tried :
- power / battery out, pressing power button several times for short / long and longer time
- BIOS battery out for about half an hour
- wincrisis with USB bootable stick and BIOS extracted from BIOS update utility from support.lenovo
- different combinations of keys such as : FN + B / F / R +/- win key
What should I do next except finding a hammer ?

Hey,
I am having the same problem, I was updating my bios.. followed all directions which is necessary to update them.
And then when it was almost ready it said "Bios update is not responding" so I waited... and waited because I did not want to abort it but then Vista aborted it for me.
Well at first it did not seem to be a problem but then I noticed that I could not click anything (was still in windows @ that time did not reboot yet) then I wanted to reboot but nothing worked.. Pressing off button for a time to shut down did not work.. So eventually power was out. And it shut down.
So I hooked it up again but nothing happened. Pressing the "on" button made it start.. The DVD-drive loaded for a second but... that is it just a black screen :S
Going to bring it back to the shop tomorrow.
Suxors

Lenovo G560 - Issue with won't boot and black screen after HDD upgrade

Lenovo G560 - Issue with won't boot and black screen after HDD upgrade.
What happen: My laptop was working fine, no blue screen issue, no funny business at all. I bought a new SSD Intel 120 GB and thought it would be a good idea to replace the HDD. I shutdown and disconnected the power adapter, waited a couple of minutes and removed the battery. I opened up the back case and replaced the HDD. And put all the screws back and put the battery back in.
Problem: The very first time I turned the power on, nothing happens besides a black screen. I pressed the dvd drive it works and opens up and closes. I waited for about 30 mins and still has blac screen. When I mean black screen, no bios menu, no logo, just a black screen with the fan sound on.
I have tried these:
1. Unplugged everything - battery, adapter, and pressed the power on button for about 60 seconds, nothing, the laptop turns on with the LED display on for both on and battery LED's. But nothing but black screen, no sound of windows loading just the fan and black screen.
2. I tried putting back my old 2.5" and nothing but black screen.
Thoughts and suggestions?
Solved!
Go to Solution.

Hi Autoexit173,
Welcome to Lenovo Community!
As per the query we understood that you are facing issue with system not booting in your Lenovo G560 laptop.
As you have mentioned that the system not booting, please try to remove the RAM and turn on the system and check if you can hear any beep sound. Also try to clean the RAM slots and check for the issue.
Click here for the steps to remove the RAM and refer page number 40.
Hope this helps. Do post back if issue persists!
Best regards,
Ashwin.S
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
Follow @LenovoForums on Twitter!

Black screen after login while on battery with graphics switching enabled

Getting a black screen after entering my password while logging into my account while on battery with graphics switching enabled. Everything is up and running, I just can't see it.
I can log into the guest account on battery
I can log into my account while plugged into power
I can log into my account on battery if graphics switching is disabled
I believe something that is starting up in my account is causing the system to switch from integrated to discrete graphics on login, and that switch isn't working correctly on battery power.
As a work around for now, I can run with graphics switching disabled, but I'd like to solve this so I get longer battery life.
MacBook Pro Retina 15"
Mountain Lion
All updates applied

I had the same issue and managed to reslove it.
Shut down your machine.
Power it back on while holding the 'shift' key (left or right, doesn't matter)
You will see a greay progress bar go across the screen while you boot in to 'safe boot'
Once booted, login, and go to Energy Saver and turn on 'Automatic Graphics Switching'.
Reboot back in to normal mode, and you should be able to log back in and see again.
I did this without being plugged into AC power.
Hope it helps!
Cheers!

Sun Rays with VDI 3.1 - Black screen after periods of inactivity

Running VDI 3.1 with bundled versions of SRSS on three servers in a cluster running Solaris 10 with VSphere as a desktop provider - also using meta-kiosk with all smartcards configured to run "VDA" script when inserted, DTUs require registered cards.
Bit of a strange issue that is unfortunately not always reproducible:
After what seems a random period after having removed a smartcard from a DTU (if still logged into a Windows session, or after disconnecting it) sometimes as short as 20mins, sometimes only after overnight, upon reinserting the card, the VDI login screen does not always appear immediately (as should happen), but instead a black screen with a moveable mouse pointer is shown. This persists for almost exactly 2 minutes whenever it happens, then the VDI screen appears. If you manually kill the session from the admin web-interface and power-cycle the Sun Ray, it will pop up immediately as expected.
At times, the VDI screen does simply appear immediately as expected, at others this 2-minute black screen first...
You can often force the behaviour on a working VDI login screen by choosing "More options - Quit" - this will often trigger the black screen/2 minute delay. At other times quitting in this manner does not reproduce the error and the VDI login screen appears immediately.
I've researched this for a couple of weeks, and a lot of bugs mentioning "black screens" pointed towards problems with uttsc-bin - I've already applied the patch here: http://sunsolve.sun.com/search/document.do?assetkey=1-21-143215-03-1 to no avail.
I assume that it possibly is nothing to do with the Windows connector, since it's really the VDI login screen that is not appearing in a timely manner and Windows logins/sessions always start/resume immediately after logging in from the VDI screen.
Can anyone offer any help?

Never figured out what was causing this, but an upgrade to VDI 3.2 has fixed it (for now at least!)

Black Screen after computer boots to Win XP With NX6600 VTD 256

My son recently purchased a new computer and gave his old one to me to salvage what I wanted.Since he just a few months ago purchased my NX6600 VTD 256 from me I naturally salvaged that first. I tried to install the NX6600 in my other son's computer without success. First the particulars:
MSI 845 Pro2 Mobo, 512 mb 133 Mhz Ram, 1.7 Ghz Intel CPU, Aopen AO350 12A PNF power supply, 350 watts with 18 amps on the 12 volt rail.
I did a fresh install of winXP on a freshly formatted HDD. Installed service pack 2, the latest intel drivers, and 5 different versions of the driver packages including ver 77.77 all with the same results.
After the computer boots I am intermittantly faced with a black screen after the WinXP logo disappears. This sometimes happens 3 times in a row before I get a working screen. After a good boot the NX6600 benchmarks good with very good marks!
I am at this point strongly suspecting the power supply is not up to the task, even though the specs for the NX6600 recommend a 350 watt power supply. Before I start removing all the hardware from the computer except for the NX 6600 to see if I have a hardware conflict, I doubt this because with the NX6600 installed without drivers I get a good boot every time.
I'm open for suggestions.

Thanks for the reply boss killer.
I tried what you suggested with a CRS power supply 300 watts with 15 amps on the 12 volt rail.
with the exact same results.
I then put the crs powersupply back into #1 son's old case reinstalled the nx6600 and gave it a go
Particulars for the old computer ECS K7VTA3 ver. 1 Mobo with 512 Mb DDR, nx6600VTD256 vid card and the CRS Power supply 300 watts with 15 amps on the 12 volt rail , and win XP pro service pack 2.
Funny the card works great without any problems with this setup! And the powersupply is 50 watts less and only 15 amps as compared to the other with 18!
I then pulled all the hardware out of #2's computer and tried it with only the memory, cpu, and NX6600 connected.
I had to boot 5 times before I had a working screen.
Now I'm thinking that there is somthing amiss with the NX6600 and the MSI 845 Pro2 ???
I'm thinking that I would be better off installing the K7VTA3 in #2 son's computer with the NX6600, since this works fine. When I did a benchmark with this setup it outperformed the *45 Pro 2 NX6600 combination By 300 points 2600 as compared to 2300 aqua mark points.
Isn't this fun?

[SOLVED] Black screen after GRUB

Hello everyone
I was setting up a machine with E17 and was trying various DM's since none seemed to work. After attempting to use LightDM, I get a black screen after GRUB. I was trying to read the various logs at /var/log/ but I cannot understand them properly. I tried reinstalling entrance and LightDM with no luck. I even tried editing grub's entry appending '1' or 's' and still no dice. Any help would be appreciated.
Last edited by Linoman (2014-01-20 09:22:33)

Hi tnx for both answers.
I missed something important in Xorg.log. As you can see, fbdev and modesetting aren't loading as usual. I didn't check grub stuff, I don't think it's related, since loading in level 3 (text mode) I get a black screen but I can login as root and turn off the computer blindlessly.
[ 2.969] (II) LoadModule: "modesetting"
[ 2.969] (WW) Warning, couldn't open module modesetting
[ 2.969] (II) UnloadModule: "modesetting"
[ 2.969] (II) Unloading modesetting
[ 2.970] (EE) Failed to load module "modesetting" (module does not exist, 0)
[ 2.970] (II) LoadModule: "fbdev"
[ 2.970] (WW) Warning, couldn't open module fbdev
[ 2.970] (II) UnloadModule: "fbdev"
[ 2.970] (II) Unloading fbdev
[ 2.970] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 2.970] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
GM45, 4 Series, G45/G43, Q45/Q43, G41, B43, HD Graphics,
HD Graphics 2000, HD Graphics 3000, HD Graphics 2500,
HD Graphics 4000, HD Graphics P4000, HD Graphics 4600,
HD Graphics 5000, HD Graphics P4600/P4700, Iris(TM) Graphics 5100,
HD Graphics 4400, HD Graphics 4200, Iris(TM) Pro Graphics 5200
[ 2.970] (II) VESA: driver for VESA chipsets: vesa
[ 2.970] (++) using VT number 7
[ 2.974] (WW) Falling back to old probe method for vesa
javex wrote:Post the content of the following files:
Also does disabling LightDM again help resolve the issue, i.e. can you get it to work without LightDM?
No, I can't get it to work changing DM's. I'm not sure if I pacman -Syu before changing DM's another time. Maybe it wasn't LightDM's fault afterall.
Spider.007 wrote:Additionally; try booting without the 'quiet' entry that is in the kernel line by default; and disable https://wiki.archlinux.org/index.php/Ke … de_Setting too
Thanks for pointing out that. I didn't knew I had it on.
Last edited by Linoman (2014-01-11 21:34:08)

[Solved]Black screen after "waiting for udev uevents to be processed"

Hello friends,
Starting from late Dec., my laptop goes black screen after "waiting for udev uevents to be processed", after updating kernel to 2.26.32.*. The strange thing is that even the screen is black, the keyboard is working. For example, I can turn on/off the status lights of capslock and others. I guess something might be wrong with udev uevents configuration with regard to the latest kernel. I've noticed that in the new kernel, there are two drivers for intel integrated graphics. My laptop has a 855G, which is supposed to be functional by both drivers, at least according to the kernel description. Maybe because the udev is configured to use the second driver (for newer graphic chips), rather than the first driver, which caused the problem?
Regards,
Wen
Last edited by Wen (2010-01-28 13:14:28)

Have a look here: http://bbs.archlinux.org/viewtopic.php? … 70#p695670

Black Screen After Windows 8 64-bit Upgrade (Clean Install) on TouchSmart IQ508A (IQ500 series)

Hi there,
Just installed Windows 8 and am getting a black screen after booting up like many others. I currently have disabled the graphics driver and this has solved the black screen issue but I can no longer use my web cam for Skype (although web cam works for W8 Camera App oddly).
To date I have tried the following:
Loading up the latest Nvidia drivers from the Nvidia website
Attempting to use the drivers for Windows 7 both in compatability mode and normally. I unzipped SP44488 to get this working
I know many others are having this problem so I really would like someone from HP to respond and state whether a Windows 8 display driver for the Nvidia GE Force 9300M GS is being developed.
I ran the compatability wizard prior to the clean install and it came up with no issues so I am very disappointed I am having these problems.
I've found out that HP have a customised version of the above card so that explains why the Nvidia drivers dont work so I believe HP is therefore obligated to provide a driver.
If anyone else is having similar issues please respond as this will hopefully lead to more action.
cheers
Steve

I'm in the same boat. On my IQ804, the Nvidia GE Force 9300M GS card crashes when I use NVidia's latest Windows 8 driver and Microsoft's LIVE UPDATE drivers. I have to resort to the Standard VGA driver in order for the pc not to crash into a black screen.
I read on another forum you can try installing a July 2012 version of the driver from NVidia and that should solve the problem. I tried it once. Using the July 2012 version, the screen would stay on longer, but eventually it crashes into a black screen...but definitely more usable than the latest from NVidia and Microsoft.
I too have heard that HP used a customized version of the graphics card and that's why neither HP nor NVidia's drivers work.
I also tried installing the Nvidia GE Force 9300M GS drivers for Windows 7 that I downloaded from the HP website. It didn't work either. It actually failed to install altogether, saying my system is incompatible.
As is, the pc works fine. But videos and games that require motion is noticably choppy.
Any help from HP??

Black Screen after logging in locally to Windows 7 that previously had an open RDP session.

Here is what happens. I leave my home computer on (running Windows 7 Ultimate) and sometimes I will remote to it from another location (work, friends house, or wherever). When I return home, I will go to login, the screen then goes blank (no mouse cursor
or anything). I have to do a cold boot to get back into Windows. This only happens if I ever RDP into it sometimes during the day. It seems random. I've tried logging off the RDP session, just closing it without logging off, nothing seems to be the answer
in that regard. It seems very random at times. I'll go a week and I can come home and it will login fine with no problems. Then the next week it starts giving me the black screen after I come home and login locally. I've seen several black screen issues here,
but usually they are getting it before logon. Anyone have a clue what might be causing this?

Hello,
The Windows Desktop Perfmon and Diagnostic tools forum is to discuss performance monitor (perfmon), resource monitor (resmon), and task manager, focusing on HOW-TO, Errors/Problems, and usage scenarios.
As the question is off topic here, I am moving it to the
Where is the Forum... forum.
Karl
When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer.
My Blog: Unlock PowerShell
My Book: Windows PowerShell 2.0 Bible
My E-mail: -join ('6F6C646B61726C40686F746D61696C2E636F6D'-split'(?<=\G.{2})'|%{if($_){[char][int]"0x$_"}})

WINDOWS 8 BLACK SCREEN AFTER LOGIN PROBLEM

Please help me i have a problem with my computer it goes black screen after i login
my desktop is hp pavilion a5055d my os is windows 8 i dont know what the problem
i have a ati radeon xpress 1100 for videocard ..
I tried to restart many times.

Hi,
Did this issue occur before?
Try to logon with Safe Mode to see if the same issue occurs.
Furthermore, you can try to update BIOS for your machine?
You can refer these article to update BIOS if your machine cannot boot:
http://www.ehow.com/how_7356859_update-bios-windows-won_t-boot.html
http://www.wikihow.com/Fix-a-PC-Which-Won't-Boot
Hope that helps.
Leo Huang
TechNet Community Support

Black Screen After Upgrading to Windows 8

Hi
I'm experiencing a black screen after upgrading a Dell N5050 B890 to Windows 8.
Tried to refresh the installation but the problem persited. re-installed the Windows 8, the machine logged in successfully but the problem arose again after reboot.
Urgent assistance needed

This problem is solved...
I guess the problem is concerned with the display module controller in the BIOS which is having a slight compatibility issue with windows 8.
This issue is solved by updating the BIOS of your Laptop/PC to the latest version. You can download the latest BIOS from the website of the Laptop company/Motherboard Company.
But for updating the BIOS, you have to start your computer/Laptop for at least one time in Normal Mode. So here are the steps to do so...
1) Boot the Laptop/PC.
2) After the boot screen (The Circle Animation & Windows 8 logo), you will be presented by the lovely & awesome blank screen.
3) Wait for 1 minute so that drivers load into the memory.
4) Press the Power button of your laptop/PC for only a moment (Just Press and release it quickly. Don't hold. We don't want to shut down).
5) This will force the laptop/PC to go into Sleep mode.
6) When the laptop/PC goes in sleep, the laptop fan & other sounds will stop.
7) After 4-5 seconds, press the power button again & release it quickly.
8) Voilllaa!!! The laptop/PC starts & you are presented with the lock screen. Now..... Login! What are you waiting for! :P
This is not the permanent solution. It just lets you start you Laptop/PC.
After updating the BIOS, I strongly suggest that you must download the latest graphics driver for your Computer/Laptop to avoid any further issues.

[Solved] Amilo XI 2550 - Black screen after fresh install

Dear archlinux users,
I have been reading the archlinux wiki and forums since I started using arch several years ago. It was always possible to solve the problems I ran into by consulting these webpages, therefore a big thanks to the community for the provided help.
Two weeks ago I installed arch on a Fujitsu Siemens Amilo XI 2550. The first problem I ran into was that booting the live-cd resulted in a black screen and I could not even start with installing arch. This problem was solved with the kernel parameter 'nomodeset'.
The first boot of the freshly installed arch also resulted in a black screen after the GRUB menu which was perfectly displayed. After some searching (here and here and ...) I plugged in an external monitor and it showed the login screen. I then installed KDE because I thaught the problem might not show up with X and KDE running. After the login to KDE I realized that the brightness of the laptop display is nearly black but not totally. It seems as if the brightness is at a very low level, but brightness cannot be controlled with the Fn+F8 or Fn+F9 commands. But I see a OSD that indicates that the controls are used but without effect. So at the moment it is only possible to work on the laptop with another display connected to it.
Maybe of use:
ls /sys/class/backlight/
acpi_video0
radeon_bl0
less /sys/class/backlight/acpi_video0/bl_power
0
less /sys/class/backlight/acpi_video0/actual_brightness
7
less /sys/class/backlight/acpi_video0/brightness
7
less /sys/class/backlight/acpi_video0/max_brightness
7
less /sys/class/backlight/radeon_bl0/bl_power
0
less /sys/class/backlight/radeon_bl0/actual_brightness
255
less /sys/class/backlight/radeon_bl0/brightness
255
less /sys/class/backlight/radeon_bl0/max_brightness
255
dmesg | grep drm
[ 0.736559] [drm] Initialized drm 1.1.0 20060810
[ 0.743608] [drm] radeon kernel modesetting enabled.
[ 0.743678] fb: switching to radeondrmfb from VESA VGA
[ 0.744054] [drm] initializing kernel modesetting (RV630 0x1002:0x9583 0x1734:0x1107).
[ 0.744065] [drm] register mmio base: 0xCFEF0000
[ 0.744067] [drm] register mmio size: 65536
[ 0.744172] [drm] Detected VRAM RAM=256M, BAR=256M
[ 0.744174] [drm] RAM width 128bits DDR
[ 0.744257] [drm] radeon: 256M of VRAM memory ready
[ 0.744259] [drm] radeon: 512M of GTT memory ready.
[ 0.744275] [drm] Loading RV630 Microcode
[ 0.744345] [drm] Internal thermal controller without fan control
[ 0.744386] [drm] radeon: power management initialized
[ 0.744389] [drm] GART: num cpu pages 131072, num gpu pages 131072
[ 0.762830] [drm] PCIE GART of 512M enabled (table at 0x0000000000040000).
[ 0.762873] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 0.762874] [drm] Driver supports precise vblank timestamp query.
[ 0.762937] [drm] radeon: irq initialized.
[ 0.794780] [drm] ring test on 0 succeeded in 1 usecs
[ 0.795253] [drm] ib test on ring 0 succeeded in 0 usecs
[ 0.795942] [drm] radeon atom DIG backlight initialized
[ 0.795945] [drm] Radeon Display Connectors
[ 0.795947] [drm] Connector 0:
[ 0.795948] [drm] LVDS-1
[ 0.795950] [drm] DDC: 0xac0 0xac0 0xac4 0xac4 0xac8 0xac8 0xacc 0xacc
[ 0.795951] [drm] Encoders:
[ 0.795952] [drm] LCD1: INTERNAL_LVTM1
[ 0.795953] [drm] Connector 1:
[ 0.795954] [drm] DIN-1
[ 0.795955] [drm] Encoders:
[ 0.795956] [drm] TV1: INTERNAL_KLDSCP_DAC2
[ 0.795957] [drm] Connector 2:
[ 0.795958] [drm] HDMI-A-1
[ 0.795960] [drm] HPD1
[ 0.795961] [drm] DDC: 0x7e50 0x7e50 0x7e54 0x7e54 0x7e58 0x7e58 0x7e5c 0x7e5c
[ 0.795963] [drm] Encoders:
[ 0.795964] [drm] DFP1: INTERNAL_KLDSCP_TMDS1
[ 0.795965] [drm] Connector 3:
[ 0.795966] [drm] VGA-1
[ 0.795968] [drm] DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c
[ 0.795969] [drm] Encoders:
[ 0.795970] [drm] CRT1: INTERNAL_KLDSCP_DAC1
[ 1.278449] [drm] fb mappable at 0xD0141000
[ 1.278451] [drm] vram apper at 0xD0000000
[ 1.278453] [drm] size 9216000
[ 1.278454] [drm] fb depth is 24
[ 1.278455] [drm] pitch is 7680
[ 1.278527] fbcon: radeondrmfb (fb0) is primary device
[ 1.726069] radeon 0000:01:00.0: fb0: radeondrmfb frame buffer device
[ 1.770030] [drm] Initialized radeon 2.39.0 20080528 for 0000:01:00.0 on minor 0
Until now and amongst others I tried the following things.
Using kernel parameters
video.use_native_backlight=1
video.use_native_backlight=0
acpi_osi=linux
acpi_backlight=vendor
and others I just cannot remember.
Masking backlight
systemctl mask systemd-backlight@backlight:acpi_video0.service
systemctl mask systemd-backlight@backlight:radeon_bl0.service
Setting bl_power
echo 1 > /sys/class/backlight/acpi_video0/bl_power
echo 1 > /sys/class/backlight/radeon_bl0/bl_power
Nothing of the above was improving the situation.
Your help on the problem would be highly appreciated.
Best regards
mgs
Last edited by mgs (2014-10-27 10:15:11)

Hello Trilby,
thanks for the reply.
Trilby wrote:If nomodeset worked with the installation medium, why haven't you tried that for the same problem on your installed system?
The kernel parameter 'nomodeset' results in a working display but without X support, due to the fact that with 'nomodeset' there is no KMS support and therefore no X. But nevertheless I tried it and as expected X did not start.
Trilby wrote:Could you also post information about your graphics card and what drivers you've installed.
The graphics card is a Radeon HD 2700 and according to the above dmesg log it is recognized as RV 630. The radeon module is loaded via /etc/mkinitcpio.conf and xf86-video-ati (1:7.5.0-1) is installed.
I hope the provided information is what you asked for, thanks for your help.
Best regards
mgs

GD65: black screen after 4.4ghz with i5 2500k

Similar Messages

Maybe you are looking for