I had no basis to determine whether the installation was still running. Without the display, I could not determine such, as you could only assume that your PC had crashed. In either case, rebooting with ACPI=off or nomodeset will, in fact, complete the DVD installation, and produce a bootable OS. This OS will NOT be able to use the native, full mode of your display.
Yes. That is the critical part of the workaround(s) found here - The “Black Screen” on Boot … a Surprise !. The lid closure/reopen alone, properly timed, may avoid the full workaround with workspace switching.
In regard to earlier posts, have you attempted the liveCD test ? This will determine whether your graphics adaptor/display are properly recognized.
As to another earlier post, rest assured that you do have a Clarkdale processor. Unless your reseller has a secret arrangement with Intel, HP and others, a Sandy Bridge is not hiding under the covers.
Ok thank you.
So My program for the W.E is :
try the 11.3 live CD to see if it is not an install issue as SeanMc98 suggested
try the 11.4 live CD to see if the latest drivers support well my hardware
If it works, try to update kernel and graphic packages.
LiveCD 11.3 64b: boot starts, then screen get white and computer no longer responds
LiveCD 11.4 64b: boot starts, then screen get white and computer no longer responds
Update 11.3 with kernel 2.37 : same behaviour, reboot and OK with NOMODESET boot option
Update 11.3 with kernel 2.36 (stable) : same behaviour, reboot and OK with NOMODESET boot option
Update all Xorg packages with the 2.36 kernel : same behaviour, reboot and OK with NOMODESET boot option. (interesting, it does mean you can update 11.3 safely)
I put here the Xorg log when the computer crashes SUSE Paste
You can see, that I have X11 server 1.9, Intel driver 2.13, …
This is very troubling. When you boot the liveCD(s), can you describe exactly what is displayed (splash screen, menu screen, etc), the option(s) you selected on the screens displayed, and when the “white screen” appears ?
By “no longer responds”, are you referring to the keyboard ?
If a liveCD will not boot to the live desktop, you may have a variant of one or more problems. After reading your post, I booted an 11.3 liveCD (Gnome), burned 2010.09.26, and a 11.4 MS4 liveCD (Gnome), burned 2010.11.26. Both successfully displayed a correct desktop, and an operational platform.
Once the installation has completed, you can always update with nomodeset (or Failsafe). The nomodeset I had previously referenced was during the actual install (the boot during the actual install).
As I pointed out in several posts, Xorg is NOT the initial problem. The “black screen” (or blank screen) occurs early in the boot procedure, prior to X initialization.
As to your experience of “white screen”, I can not say whether an HP uses backlighting and/or backlights an empty display. I have seen “white screen” during a liveCD, usually the result of a bad liveCD.
Then the splash screen becomes slowly (and nicely) white.
As the screen is white, it is hard to say if the computer is still alive or crash. Mouse or keyboard have no effect.
This happens with every configurations I tried : LiveCD 11.3, liveCD 11.4, 11.3 updated with new kernel and Xorg packages, Ubuntu 10.10.
The only way to have the system working is to boot with the option NOMODESET (or ACPI=off with kernel 2.6.34, delivered with standard 11.3), which results to a very poor resolution, probably because the intel driver is not used.
As I pointed out in several posts, Xorg is NOT the initial problem. The “black screen” (or blank screen) occurs early in the boot procedure, prior to X initialization.
After all these experiments, I think you may be right, that the problems doesn’t comes from the graphics and Xorg, and is linked to something else. MAybe I should start a new thread “Splash screen becomes white at boot” ?
(Not trying to be tedious) The “splash screen” referring to the “Welcome/Bienvenue” etc. display ?
And you never see the liveCD menu ? (Options like “Installation”, “Boot from Hard Disk”, etc. ?
Booting the liveCDs (11.3 or 11.4) does not invoke GRUB. Can you use a camera and capture the screens that you see in 1) a "normal’ boot, and 2) booting liveCD ?
Sadly, this is true. You usually get the VESA driver (1024 x 768, or poorer). The only upside is that it usually works. I do wonder why “ACPI=off” is required with the OOTB 11.3. When I used “ACPI=off”, the display worked, but wireless was nowhere to be seen. “ACPI=off” disables a host of hardware detections, while nomodeset has a narrower focus.
Hold on the new thread until we are certain that it is a new problem.
From what I read, I think it is the same issue; (and its hardware is very close from mine)
There are some differences probably because it is a laptop with an arrandale , whereas I have clarkdale (or Sandybridge) and a desktop, for which no workaroung is possible.
Let’s try the following:
Boot to Runlevel 3. (This will create a /var/log/boot.msg file, which later will be /var/log/boot.omsg).
Re-boot with nomodeset. This will get you to a working environment.
Post the /var/log/boot.omsg file here. (This will show the boot log of a successful kernel initialization from the “Runlevel 3” boot).
The “hard part” : Repeat step 1, with a NORMAL boot.
If this boot FAILS (white screen), repeat steps 2 & 3, now showing a FAILURE.
If this boot is successful (you get a login screen), login and post /var/log/boot.msg, showing a SUCCESS.
I appreciate the time and effort you are expending. All will be worthwhile.
Are you sure of your steps? for instance at stage 4, do you really mean “repeat step 1” ? if yes (run level 3) I will never get a login screen…
I think that I need NOMODESET even to boot in runlevel3 -> To be confirmed.
I understand your puzzlement. Let’s try the following (revised):
Boot to Runlevel 3. (This will create a /var/log/boot.msg file, which later will be /var/log/boot.omsg).
Re-boot with nomodeset. This will get you to a working environment.
Post the /var/log/boot.omsg file here. (This will show the boot log of a successful kernel initialization from the “Runlevel 3” boot).
The “hard part” : Do a NORMAL boot. (No modeset or ACPI=off).
If this boot FAILS (white screen), repeat step 2. Post the /var/log/boot.omsg here, now showing a normal boot FAILURE.
If this boot is successful (you get a login screen), login and post /var/log/boot.msg, showing a normal boot SUCCESS.
The rationale for the above is to find exactly what is happening during kernel initialization. If you can get to Runlevel 3 without nomodeset, then the white screen failure is in X. Otherwise, we will get a boot log showing what is happening when your screen goes white.
This log is as predicted. The kernel is using the VESA fb driver.
This show exactly the same problem I )personally) experience, and is reported elsewhere. In a nutshell,
#
<6> 4.562819] [drm] Cannot find any crtc or sizes - going 1024x768
#
<7> 4.571039] checking generic (d0000000 1ff0000) vs hw (d0000000 10000000)
#
<3> 4.571041] fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic driver
#
<4> 4.571061] Console: switching to colour dummy device 80x25
#
<4> 4.571481] Console: switching to colour frame buffer device 128x48
#
<6> 4.584445] bootsplash: scaling image from 1280x1024 to 1024x768
#
<6> 4.712365] bootsplash: scaling image from 1280x1024 to 1024x768
#
<6> 4.746824] bootsplash: scaling image from 1280x1024 to 1024x768
#
<6> 4.875147] bootsplash: scaling image from 1280x1024 to 1024x768
#
<6> 4.896943] fb0: inteldrmfb frame buffer device
#
<6> 4.896945] drm: registered panic notifier
The switch during kernel initialization to the “inteldrmfb” (the Intel frame buffer driver) fails. Why, I have some ideas but no solutions. I do have a circumvention (aka “workaround”), as described elsewhere.
Try the following:
Do a normal boot
As soon as the screen changes to white, close the lid, count 1,2 and re-open the lid.
Post back the findings.
One odd entry in the failing boot.msg log has me puzzled. The failing boot.msg log shows that it determined that your native display mode is 1024 x 768. It should show a native display geometry (aka “modeline”) of 1920 x 1080. This fact is indicative of a DVD-install where the intermediate boot (following the “countdown”) returned a (blank, black, white or empty) screen. A reboot at that point, restarting with either nomodeset or failsafe mode, will install oS, but the result will not boot to native size, nor will the workaround(s) function.
I know your problems and I read carefully the workaround you established.
However, It can’t work in my case because I have a desktop and no lid to close! Only a power button.
An other weird thing is that you mention that the LiveCD always works, which is not true for me. The computer fails with full install or live CD…
I’m under the impression that even with blank screen the boot completes, and linux runs under. Can you confirm?
I don’t know what to try now. I have this last two ideas :
-Try Fedora
-Try SUse 11.2 (no KMS) with updated kernel and X11
What do you think of that? Where can I find a 11.2 version?
Small update with all my activities since january the 12th, to solve my black screen at boot :
1/Fedora 14
-> No improvement, it looks like the problem is a linux issue and not a distro issue
2/update graphics package to :
the Linux 2.6.37 kernel,
Mesa 7.10,
the latest libdrm,
and the xf86-video-intel 2.14.0
-> No improvement, still black screen at boot
3/build a kernel from the edp-fixes-2 branch of the git folder *git://git.kernel.org/pub/scm/linux/kernel/git/jbarnes/drm-intel.git *described in the threadBug 29278.
-> No improvements, still black screen
4/build a kernel from the drm-intel-next branch of the git folder git://git.kernel.org/pub/scm/linux/kernel/git/ickle/drm-intel described in the threadBug 29278.
-> No improvements, still black screen
5/Install the linux kernel 2.6.38-rc1 from the source of kernel.org
-> No improvement, still black screen at boot, even NOMODESET doesn’t enable a working system.
So it looks like there is no solution to have linux working on the HP All in One 200, and I have no hope for the future as it is a very particular issue linked to my hardware, and not a general i3 core issue!
