Just a little background I have a sony vaio VPCZ119X laptop and have been struggling to get all components working under linux especially the intel graphics.
I saw that once I upgraded to the latest available kernel release which currently is 2.6.37 rc7. The intel graphics is working, but sometimes when I boot I get a blank/black screen but seems to be lit up. All other functions seem working so for example I am able to login etc just that I dont see anything on the screen.
I have tried the following so far to identify the issue or isolate it:
Switching to the console screens has no effect, still the black / blank screen.
Restarting the system does not always immediately get the screen working, sometimes it takes a couple of reboots before the screen is available
I have a switchable graphics with nVidia I never get this problem when I use the nvidia driver
I have tried closing the lid etc as suggested in the below post without any change in output, will try further as there are other options available as well The “Black Screen” on Boot … a Surprise !
I see one difference between both the Xorg log files but I am not able to reason out why this happens hence I will just supply the files here and try not to theorize.
Sure
The only difference I could see using KDiff was from line 393. In the xorg.0.log.old (not working) it starts closing out modules while I don’t see in the Xorg.0.log (working) here it just lists the same screen frequency information multiple times.
This is what baffles me because the difference I am seeing seems more like the effect that must be caused elsewhere in the log, it is possible that I might have missed another difference in the log let me keep checking that.
According to the Xorg.0.log, you have the Arrandale chipset. I can’t see any “significant” difference between the two Xorg.0.log files. Did you modify any of the section/files (e.g. monitor) in /etc/X11/xorg.conf.d directory?
What packages did you update for the change to 2.6.37 rc7 kernel?
The various forum threads investigating problems/bugs with the intel driver support for Arrandale chipset suggest that just upgrading the kernel is probaly not enough. You are using intel driver 2.12.0 with xorg-server 1.8.0 as supplied with 11.3, where with a much newer kernel such as 2.6.37-rc7 (hopefully with latest upstream patches for your chipset), you may need to upgrade xorg-xserver (to 1.9.x) to get bug fixes since 1.8.0, and also upgrade to the latest 2.13.0 intel driver to get better Arrandale support. It may be worth downloading and testing a liveCD of 11.4 Milestone 5 to accomplish that.
According to the Xorg.0.log, you have the Arrandale chipset. I can’t see any “significant” difference between the two Xorg.0.log files. Did you modify any of the section/files (e.g. monitor) in /etc/X11/xorg.conf.d directory?
I don’t remember changing any of the files, but please do let me know if there is a specific file information that you might want to have a look at. For me the most baffling this is that sometimes the X system shows up fine and sometimes it does not without any changes (or perceivable changes as something must be different humidity, time of the day etc ).
What packages did you update for the change to 2.6.37 rc7 kernel?
When I updated the kernel using the repository, it updated the following packages
kernel-default
kernel-default-base
kernel-default-devel
kernel-devel
kernel-firmware
kernel-source
preload
preload-kmp-default
It may be worth downloading and testing a liveCD of 11.4 Milestone 5 to accomplish that.
Good suggestion let me try that, I remember trying with milestone 2/3 which had the kernel as 2.6.36 and I couldn’t get the X working but let me try the milestone 5 and see how it goes.
Thanks for all the suggestions and the time you are spending on this.
Ok. If the correct display resolution is being automatically configured for your laptop, best not to change the default files in xorg.conf.d directory.
It’s difficult to test complex software for those intermittent problems such as the one you appear to be experiencing. In this case, we have kernel and kernel modules, DRI/DRM modules and drivers, Xorg and the “intel” driver. Combine that with various new intel processor h/w configurations using Arrandale chipsets with integrated GMA HD (Graphics Media Accelerator), on different laptop manufacturers, and you have a complex scenario.
When I updated the kernel using the repository, it updated the following packages…
Thanks for package list, it looks fine.
Thanks for all the suggestions and the time you are spending on this.
Unfortunately bad news to report, I get the same issue even with the live cd, sometimes I get the X display fine in other cases again the same black or blank screen.
I am trying to see is there is no other log that gets written which might give us some idea on what is happening here, also I seem to have a hypothesis that if I wait for a while during the boot process I get the proper display, let me try that a little further and post an update here.
Having only tested and verified the liveCD in an Intel Integrated Graphics (only) environment, I cannot say whether it should work with switchable graphics. There should be three (3) scenarios for the liveCD testing:
Intel Graphics only
Nvidia Graphics only
both adaptors enabled
This is/should be selectable in the BIOS setup (switchable graphics). (I personally do not know how/if the liveCD might handle the Nvidia graphics).
The boot.msg and boot.omsg logs are of value, as the problem with the Intel Integrated Graphics occurs early in the boot process, before X is initialized. You might test the lid closure technique by closing and reopening the lid as soon as the screen goes black/blank. If you wait until the login screen, you must use the workspace switch technique.
As to advanced levels of Xorg, I have found that the newer (2.13.0+) Intel drivers have no incremental or enhanced effect on the black screen at boot, although there is effect once the login is processed. You might consider booting to Runlevel 3. Should you get a black/blank screen, the lid closure/reopen alone should restore your display. At this point, you could run the “X -configure” and post the contents of xorg.conf.new in SUSE Paste.
Thanks for feedback. You could test @SeanMc98’s suggestions, that may mean updating kernel, drm, xorg and intel driver to his current levels (?). You will probably need repos from Factory and/or OBS. These days, there are several choices, so perhaps SeanMc98 can enlighten us on that here?
Or stick with 11.4 milestone’s, but I wouldn’t install them unless you have a separate m/c or testing partion (need to be comfortable with multibooting and grub issues). Although, using the liveCD may not be a thorough enough test.
In the original post, the OP noted that the running kernel was (the latest) 2.6.37-rc7. It appears that either additional repo’s have been added, or kernel 2.6.37-rc7 was compiled/installed. Further, in the same post, the OP indicated that no problems occurred with the Nvidia driver. (NOTE: I would absolutely love to have an alternate GA!!!).
If the Nvidia driver works without problem(s), is there a compelling reason to pursue the Intel Integrated Graphics ? I am not being critical, rather if the OP has a working openSUSE 11.3 environment, I would suggest waiting (I have come to loathe that word!) until the kernel/Xorg issues are sorted.
That being said, to pursue the Intel GMA, we need to complete a baseline. We already have the Xorg.0.log(s) for the Sony VAIO. I would like to see the output of
uname -a
lspci -v
zypper lr -d
as well as the earlier requested boot.msg/boot.omsg logs. I would like the test of the liveCD boot, which I still use when any kernel/Xorg update goes “wonky” as 2.6.37-rc8 did!
I got the impression that @pavibhai had read most of your recent postings about your testing. I posted having seen another post about 2.6.37 (i.e. not RC) having been released recently. That could be worth a go e.g. if/when it reaches a milestone liveCD.
If the Nvidia driver works without problem(s), is there a compelling reason to pursue the Intel Integrated Graphics ? I am not being critical, rather if the OP has a working openSUSE 11.3 environment, I would suggest waiting (I have come to loathe that word!) until the kernel/Xorg issues are sorted.
If nvidia is satisfactory, and if it were me, I would wait for 11.4 and/or kernel/drm/xorg/driver to get sorted.
I would like the test of the liveCD boot, which I still use when any kernel/Xorg update goes “wonky” as 2.6.37-rc8 did!
What liveCD are you referring to?
I was referring to post #8 here, concerning the liveCD boot with the three(3) BIOS-selectable graphics configurations. If possible, the 11.3 and 11.4 MS5 liveCDs.
Firstly apologies for the delay in the response and appreciate the time everyone is spending on this one.
To be honest at this point in time the primary reason is the curiosity as to how this is possible that something works sometimes and not the others. Additionally when I travel I get around 10hrs battery backup with Intel while with nVidia I barely get 3.5hrs.
uname -a
Linux linux-0a2q.site 2.6.37-rc8-default #1 SMP 2010-12-30 00:50:58 +0100 x86_64 x86_64 x86_64 GNU/Linux
lspci -v
00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 02)
Subsystem: Sony Corporation Device 905a
Flags: bus master, fast devsel, latency 0
Capabilities: [e0] Vendor Specific Information: Len=0c <?>
Kernel driver in use: agpgart-intel
00:01.0 PCI bridge: Intel Corporation Core Processor PCI Express x16 Root Port (rev 02) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 00006000-00006fff
Memory behind bridge: d0000000-d10fffff
Prefetchable memory behind bridge: 00000000a0000000-00000000b1ffffff
Capabilities: [88] Subsystem: Sony Corporation Device 905a
Capabilities: [80] Power Management version 3
Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit-
Capabilities: [a0] Express Root Port (Slot+), MSI 00
Capabilities: [100] Virtual Channel
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02) (prog-if 00 [VGA controller])
Subsystem: Sony Corporation Device 905a
Flags: bus master, fast devsel, latency 0, IRQ 44
Memory at d1400000 (64-bit, non-prefetchable) [size=4]
Memory at c0000000 (64-bit, prefetchable) [size=256]
I/O ports at 7078 [size=8]
Expansion ROM at <unassigned> [disabled]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
Capabilities: [a4] PCI Advanced Features
Kernel driver in use: i915
00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06)
Subsystem: Sony Corporation Device 905a
Flags: bus master, fast devsel, latency 0, IRQ 5
Memory at d7828100 (64-bit, non-prefetchable) [size=16]
Capabilities: [50] Power Management version 3
Capabilities: [8c] MSI: Enable- Count=1/1 Maskable- 64bit+
00:19.0 Ethernet controller: Intel Corporation 82577LC Gigabit Network Connection (rev 05)
Subsystem: Sony Corporation Device 905a
Flags: bus master, fast devsel, latency 0, IRQ 41
Memory at d7800000 (32-bit, non-prefetchable) [size=128]
Memory at d7825000 (32-bit, non-prefetchable) [size=4]
I/O ports at 7040 [size=32]
Capabilities: [c8] Power Management version 2
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [e0] PCI Advanced Features
Kernel driver in use: e1000e
00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05) (prog-if 20 [EHCI])
Subsystem: Sony Corporation Device 905a
Flags: bus master, medium devsel, latency 0, IRQ 23
Memory at d7827c00 (32-bit, non-prefetchable) [size=1]
Capabilities: [50] Power Management version 2
Capabilities: [58] Debug port: BAR=1 offset=00a0
Capabilities: [98] PCI Advanced Features
Kernel driver in use: ehci_hcd
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05)
Subsystem: Sony Corporation Device 905a
Flags: bus master, fast devsel, latency 0, IRQ 42
Memory at d7820000 (64-bit, non-prefetchable) [size=16]
Capabilities: [50] Power Management version 2
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [100] Virtual Channel
Capabilities: [130] Root Complex Link
Kernel driver in use: HDA Intel
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 05) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
I/O behind bridge: 00005000-00005fff
Memory behind bridge: d6800000-d77fffff
Prefetchable memory behind bridge: 00000000d1800000-00000000d27fffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: Sony Corporation Device 905a
Capabilities: [a0] Power Management version 2
00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 05) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
I/O behind bridge: 00004000-00004fff
Memory behind bridge: d5800000-d67fffff
Prefetchable memory behind bridge: 00000000d2800000-00000000d37fffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: Sony Corporation Device 905a
Capabilities: [a0] Power Management version 2
00:1c.2 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 3 (rev 05) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=04, subordinate=0b, sec-latency=0
I/O behind bridge: 00003000-00003fff
Memory behind bridge: d4800000-d57fffff
Prefetchable memory behind bridge: 00000000d3800000-00000000d47fffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: Sony Corporation Device 905a
Capabilities: [a0] Power Management version 2
00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05) (prog-if 20 [EHCI])
Subsystem: Sony Corporation Device 905a
Flags: bus master, medium devsel, latency 0, IRQ 20
Memory at d7827800 (32-bit, non-prefetchable) [size=1]
Capabilities: [50] Power Management version 2
Capabilities: [58] Debug port: BAR=1 offset=00a0
Capabilities: [98] PCI Advanced Features
Kernel driver in use: ehci_hcd
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a5) (prog-if 01 [Subtractive decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=0c, subordinate=0c, sec-latency=32
Capabilities: [50] Subsystem: Sony Corporation Device 905a
00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller (rev 05)
Subsystem: Sony Corporation Device 905a
Flags: bus master, medium devsel, latency 0
Capabilities: [e0] Vendor Specific Information: Len=10 <?>
00:1f.2 RAID bus controller: Intel Corporation Mobile 82801 SATA RAID Controller (rev 05)
Subsystem: Sony Corporation Device 905a
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 40
I/O ports at 7068 [size=8]
I/O ports at 7084 [size=4]
I/O ports at 7060 [size=8]
I/O ports at 7080 [size=4]
I/O ports at 7020 [size=32]
Memory at d7827000 (32-bit, non-prefetchable) [size=2]
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [70] Power Management version 3
Capabilities: [a8] SATA HBA v1.0
Capabilities: [b0] PCI Advanced Features
Kernel driver in use: ahci
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 05)
Subsystem: Sony Corporation Device 905a
Flags: medium devsel, IRQ 22
Memory at d7828000 (64-bit, non-prefetchable) [size=256]
I/O ports at 7000 [size=32]
00:1f.6 Signal processing controller: Intel Corporation 5 Series/3400 Series Chipset Thermal Subsystem (rev 05)
Subsystem: Sony Corporation Device 905a
Flags: bus master, fast devsel, latency 0, IRQ 22
Memory at d7824000 (64-bit, non-prefetchable) [size=4]
Capabilities: [50] Power Management version 3
Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
01:00.0 VGA compatible controller: nVidia Corporation GT216 [GeForce GT 330M] (rev a2) (prog-if 00 [VGA controller])
Subsystem: Sony Corporation Device 905a
Flags: fast devsel, IRQ 5
Memory at d0000000 (32-bit, non-prefetchable) [disabled] [size=16]
Memory at a0000000 (64-bit, prefetchable) [disabled] [size=256]
Memory at b0000000 (64-bit, prefetchable) [disabled] [size=32]
I/O ports at 6000 [disabled] [size=128]
Expansion ROM at d1080000 [disabled] [size=512]
Capabilities: [60] Power Management version 3
Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [78] Express Endpoint, MSI 00
Capabilities: [b4] Vendor Specific Information: Len=14 <?>
Capabilities: [100] Virtual Channel
Capabilities: [128] Power Budgeting <?>
Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?>
01:00.1 Audio device: nVidia Corporation High Definition Audio Controller (rev a1)
Subsystem: Sony Corporation Device 905a
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at d1000000 (32-bit, non-prefetchable) [size=16]
Capabilities: [60] Power Management version 3
Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [78] Express Endpoint, MSI 00
Kernel driver in use: HDA Intel
02:00.0 Network controller: Intel Corporation Centrino Advanced-N 6200 (rev 35)
Subsystem: Intel Corporation Centrino Advanced-N 6200 2x2 AGN
Flags: bus master, fast devsel, latency 0, IRQ 43
Memory at d6800000 (64-bit, non-prefetchable) [size=8]
Capabilities: [c8] Power Management version 3
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [e0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number 00-23-14-ff-ff-40-b4-90
Kernel driver in use: iwlagn
03:00.0 SD Host controller: Ricoh Co Ltd Device e822
Subsystem: Sony Corporation Device 905a
Flags: bus master, fast devsel, latency 0, IRQ 17
Memory at d5800a00 (32-bit, non-prefetchable) [size=256]
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [78] Power Management version 3
Capabilities: [80] Express Endpoint, MSI 00
Capabilities: [100] Virtual Channel
Capabilities: [800] Advanced Error Reporting
Kernel driver in use: sdhci-pci
03:00.1 System peripheral: Ricoh Co Ltd Device e230
Subsystem: Sony Corporation Device 905a
Flags: bus master, fast devsel, latency 0, IRQ 10
Memory at d5800900 (32-bit, non-prefetchable) [size=256]
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [78] Power Management version 3
Capabilities: [80] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
03:00.4 SD Host controller: Ricoh Co Ltd Device e822
Subsystem: Sony Corporation Device 905a
Flags: bus master, fast devsel, latency 0, IRQ 19
Memory at d5800800 (32-bit, non-prefetchable) [size=256]
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [78] Power Management version 3
Capabilities: [80] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Kernel driver in use: sdhci-pci
3f:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 02)
Subsystem: Sony Corporation Device 905a
Flags: bus master, fast devsel, latency 0
3f:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 02)
Subsystem: Sony Corporation Device 905a
Flags: bus master, fast devsel, latency 0
3f:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 02)
Subsystem: Sony Corporation Device 905a
Flags: bus master, fast devsel, latency 0
3f:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 02)
Subsystem: Sony Corporation Device 905a
Flags: bus master, fast devsel, latency 0
3f:02.2 Host bridge: Intel Corporation Core Processor Reserved (rev 02)
Subsystem: Sony Corporation Device 905a
Flags: bus master, fast devsel, latency 0
3f:02.3 Host bridge: Intel Corporation Core Processor Reserved (rev 02)
Subsystem: Sony Corporation Device 905a
Flags: bus master, fast devsel, latency 0
zypper output in a subsequent post as this went too long.[/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size]
That’s a lot of repos to manage, and refresh at startup or when opening Yast. Enabling both Videolan and Packman repos can lead to conflicts when adding/updating multimedia packages. We usually advise to disable Videolan repo after getting libdvdcss, since Packman provides the rest.
@pavibhai: Thanks for the postings. Several things came to my attention: Your kernel is 2.6.37-rc8. This kernel was problematic for me, although others here experienced no problems. (The problem area is found in your boot.msg at lines 602 - 605). The kernel date for -rc8 was 2010.12.30, corresponding to your original post. What kernel were you running prior to posting, and were you experiencing the original described problems ?
I was going to suggest backing this kernel out, however, the 2.6.37 kernel was released and seems to have corrected the -rc8 problems. Rather than have you compile a kernel, it appears that the Kernel/HEAD repos have been updated to kernel 2.6.37-31.1.
After looking at your boot logs, it appeared tht you were experiencing the problem (intermittent blank screen at boot) while running on battery power. If this is true, could you duplicate the testing running on AC power ? One possible (and probable) cause of this problem lies in power management, and I was able to partially replicate your problem. Booting my Intel Graphics laptop on battery did NOT respond to the lid closure/reopen workaround. Your failing boot.msg indicated some out-of-the-norm messages on the “Lid switch”.
Suggestions:
Test on AC power PRIOR to any kernel changes.
Update the kernel to the 2.6.37-31.1 kernel from your defined repos.
Test with AC and battery.
As for potential changes to the Intel drivers, Xorg, drm, etc., I would delay any such change for now. Lets see if we can get to a consistent, almost-but-not-quite working system first.
Good point that you raise, let me recollect my history with kernel versions here, I think I first started with rc3 and if my memory serves correct I have not see the graphics / X display issue there only the sound card was not working.
I think maybe with the subsequent rc4 onwards I have had this X display issue and is still present with rc8, the initial posts were with rc7.
rc7 however corrected the sound card issue and sound is working again since then.
Is there a chance to revert back to rc3 just to be sure?
I was going to suggest backing this kernel out, however, the 2.6.37 kernel was released and seems to have corrected the -rc8 problems. Rather than have you compile a kernel, it appears that the Kernel/HEAD repos have been updated to kernel 2.6.37-31.1.
I have tried upgrading the kernel, but I find updates to only these packages
kernel-default
kernel-default-base
I am assuming this is sufficient.
Suggestions:
Test on AC power PRIOR to any kernel changes.
Update the kernel to the 2.6.37-31.1 kernel from your defined repos.
Test with AC and battery.
I am surprised that you see that the logs report on battery power, I was connected to the power supply all the time. I was trying to notice or time the failures since yesterday, I am not sure if I can conclusively state this yet, but if I slow down the boot process like wait (could be any issue with warming up or so?) for a while on the grub screen or later I have seen that the X always loads properly, if the kernel update still does not fix the issue I will try to time this further to get more accurate results.
I will keep my fingers crossed on the kernel update lets see.
I have upgraded the kernel but I don’t see any difference in the problem. Sometimes I get X and sometimes I don’t I further went ahead to check that this behavior does not change whether I am connected to the power supply or not.
Still studying your boot and Xorg logs, and I have a few questions and requests:
When you state “Sometimes I get X and sometimes I don’t”, what exactly are you describing ? Are you referrring to the Gnome or KDE or ?? Login screen ? Are you set up for autologin ?
When you get the black/blank screen, do you do a hard (i.e.: power off/on) reboot ? Is there any pattern to successful/unsuccessful boots based on powering off or length of time the PC is off ?
When you get the black/blank screen, have you tried the following:
1. *ctrl+alt+F2*,
2. Close the lid, reopen the lid, and note anything on the display,
3. *ctrl+alt+F1*, and note the contents of the display.
(You may need to do a
4. *ctrl+alt+F7* at the end of sequence ?
I am not familiar with your BIOS. Is there an option to disable the Nvidia graphics prior to boot ?
Can you post the contents of /boot/grub/menu.lst ?
kdesu kwrite /boot/grub/menu.lst
- or -
gnomesu gedit /boot/grub/menu.lst
Can you boot to Runlevel 3 (given the unpredictable likelihood of successful boot, this may take more that one attempt) ? At Runlevel 3, login with your normal ID, then su and run X -configure. Post any error messages here.
