[MOOT] UEFI USB Install (from 201306 image) - blank screen during boot

I am trying to install Arch Linux on a Lenovo ThinkPad T431s.
I created a bootable UEFI USB disk image following the instructions on the wiki.
https://wiki.archlinux.org/index.php/UE … B_from_ISO
Attempting to boot from this image I get to a screen that looks like:
Arch Linux archiso x86_64 UEFI USB
UEFI Shell x86_64 v1
UEFI Shell x86_64 v2
After selecting the first option, I get a blank screen.
This appears to be the same (or very similar) to the following issues:
[1] https://bbs.archlinux.org/viewtopic.php?id=151599
[2] https://bbs.archlinux.org/viewtopic.php?id=158530
As suggested by
https://wiki.archlinux.org/index.php/Beginners'_Guide#Preparation
I tried appending a number of things to the initrd line
nomodeset
video=SVIDEO-1:d
i915.modeset=0
with no success (the blank screen was exactly the same).
Some posts in thread [2] indicated that booting in legacy bios mode worked. I created a new disk image (again following the wiki instructions: https://wiki.archlinux.org/index.php/US … ion_Media) and was able to confirm that I could successfully boot from this other image after switching into legacy mode.
In thread [1], there was the suggestion to go into a UEFI shell and try a command like
Shell > fs0:
FS0:\ > cd \arch\boot\x86_64
FS0:\arch\boot\x86_64\ > vmlinuz archisobasedir=arch archisolabel=ARCH_201306 initrd=\arch\boot\x86_64\archiso.img
which I did. After pressing enter nothing happened (the screen did not go blank, all the text remained, no messages appeared).
Eventually in that same thread, a workaround was suggested in this post. I have not tried this because I was unable to understand what exactly was being done, both because of the terse nature of the post and the fact that the referenced article is not in a language which I read (and google translate did not make it clear enough). I was unable to evaluate whether that was a sensible thing to do.
Now, finally, the questions
Firstly, does anyone have any suggestions about how to solve or troubleshoot my blank screen issue?
If not, does anyone have an opinion about which of the workarounds (switching into legacy mode or the one that I don't quite understand yet) would be better? I am not planning to dual boot the system, so I do not need to use UEFI to be win8 friendly, etc.
Last edited by wesphys (2013-06-07 14:36:28)

Auric wrote:
Neri, did you get any further with this? I just got my own Thinkpad Yoga and am facing the same problems. Everything works fine in legacy Boot but the screen stays black on UEFI boot regardless of the known workarounds.
might it help to first install using legacy boot and later on convert to UEFI?
Not really with Arch directly anyways. What you can do is:
1. Use Fedora 20 USB to boot the sucker up
2. Use Archlinux-bootstrap install (download expand etc)
3. Use refind as the bootmanager seems to solve the dual boot issues
ATM i'm fighting a mkinitcpio segfault. But that is after the installation was basically successful. It would be nice if we can find a way to fix the install medium ...
EDIT:
All sorted out. Unfortunately you'll have to bypass the Archlinux Install medium and resort to the fedora 20 installer. I used the XFCE4
version for a smaller download.
Here are the basic steps for a Dual-Boot setup:
In windows (Disk Management) truncate your C: Drive. I ended up making basically what will became /dev/sda4 smaller and didn't not
touch any partition or free space before that. Here's the final Layout:
/dev/sda:
empty space
1. recovery partition
2. ESP
3. reserved
4. windows
5. Linux Root
6. Linux home
7. Swap
The installation happened from within Fedora Live using an Archlinux Boot strap image according to the Wiki for installing from an
existing Linux and the Wiki Installation Guide. I mounted /dev/sda2 (aka. the existing ESP partition) as /boot and installed refind
according to the wiki. Please note, when you install Arch through the archlinux bootstrap method make sure you pacman -S archlinux-keyring
in the bootstrap chroot first before you run the pacstrap command - it will accelerate the process tremendously!
Last edited by neri (2014-01-02 21:40:31)

Similar Messages

Blank Screen During Boot

after my latest upgrade I restarted and now the screen goes blank around the point the font changes and it finishes saying kvm disabled by bios. It then goes black and stays black. I've seen an answer posted here: https://bbs.archlinux.org/viewtopic.php?id=86357 in one of the comments. But it's been months since I did any linuxing. So I need some help. How do I mount my root and boot partitions while booted to live media (usb)? I know which is which in lsblk. My next question is what do I then do to chroot into it? I'm guessing mount /dev/sda1 /mnt/root ? Then chroot to it.
Assistance would be much appreciated. Once I get there I can start trying to change some options with mkinitcpip.conf and in Radeon.conf as I have a Radeon card. The changes are listed in wiki here: https://wiki.archlinux.org/index.php/ATI#Disable_KMS but I seem to be having trouble turning modest=0 on while on live media. If someone could assist it would help a lot as my windows box died (of course) and this is my only pc at the moment. I heard this may fix my issue of someone else has another fix please share. Radeon card, 64bit, manufacutrd by HP as HP compaq elite. Has ran arch over a year fine so far and love it compared to other distros
Thanks for the help in advance I feel like a noob I used to be able to do this stuff in my sleep but I've been stuck on a windows server and infrastructure at work for a while now.
Cheers fellow archers.

Sorry was typing on an iPhone. I'll try switching to a new TTY when I get home from work. The screen is powered on, it displays the DVI connection icon in the corner showing it does have a conneciton, everything is just black. I'm booting straight to X. I managed to get in on a live usb, and mount my root home and usr directories. But after doing so I can't seem to get chroot to cooperate. As I recall I just do chroot /mnt/root_mount_point and that should be it yes? Should I use the special arch chroot or regular? I know you use arch chroot when installing but I'm not doing so.
Assuming I finally get chrooted in, I'm hoping modeset = 0 works. From the post I referenced, doing modeset = 0 in radeon.conf after creating /etc/modprobe.d/radeon.conf and doing mkinitcpio -p kernel26 after making changes to /etc/mkinitcpio.conf Not sure what changes to make exactly, but I guess I'll reread the wiki over and over till I get it. I hope this fixes the issue as it did for the other person.
I have a specific quesiton about mkinitcpio -p kernel26... is that the right argument? Should I use kernel26 or is it specific to the machine? I see in the wiki mkinitcpio -p linux. Which is the correct command?
My last update was yesterday. Before that it had been about a month. And I hadn't restarted in about a week or two.
Does this seem correct? Will it fix my issues?
Thanks

Blank Screen during boot Win XP Pro

When i boot my computer (specs below) the Corecell logo comes up for a few seconds, the the screen will go blank for most of the rest of the boot. it'll go about 45 seconds with a blank screen, then finally the windows XP logo will come on the screen, then a few seconds later, the windows desktop appears. Also seems that the first 30 seconds or so of this blank screen, the hard drive LED isn't showing activity, then finally it'll kick in and the Windows XP logo shows up shortly after.
no big deal really, just wondering why i get this blank screen. We have tons of Win XP pro machines at my job, and none of them boot with this blank screen. I have seen other Win XP machines do this here and there, any ideas why?
- Kip
(just wanted to clarify what i mean by "blank". i mean black screen. video signal is being fed to the screen, just nothing but the black.)

My God! You're running XP!! Have you upgraded from 2000? Do you have any autostart program connected to an instant messaging or SQL server?
http://forums1.itrc.hp.com/service/forums/questionanswer.do?admit=716493758+1080242655589+28353475&threadId=204094
http://support.microsoft.com/default.aspx?scid=kb;en-us;248353

Blank screen during boot, missing video on tty console

I have black screen when booting from docking station where is DVI video output. On laptop itself and over VGA is OK.
Tried modify GRUB2:
GRUB_CMDLINE_LINUX_DEFAULT=“quiet”
for
GRUB_CMDLINE_LINUX_DEFAULT=“i915.modeset=1”
but still the same and can't get video after switch to tty (ctrl+alt+F1) as well
I compare with Debian where tty works fine
found in folder: /etc/modprobe.d/i915-kms.conf
where is:
options i915 modeset=1
in Arch missing this file, any idea what to check?

Mr.Elendig wrote:
https://wiki.archlinux.org/index.php/In … modules.22
This says ati but can in some cases happen on intel with docking stations too:
https://wiki.archlinux.org/index.php/At … rks_in_KMS
The most likely problem is the former though. It tries to use both outputs, and the vga uses a much lower res than the dvi, and therefor your monitor goes black because it doesn't like the video mode.
Thank you for answer.
I modified Grub line for adding one more module parameters fbcon=map:1:
GRUB_CMDLINE_LINUX_DEFAULT="quiet acpi_osi=Linux fbcon=map:1"
and updated grub:
grub-mkconfig -o /boot/grub/grub.cfg
but now after showing Grub table with available systems just frozen video, still I'm able to typing from keyboard to push system forward (encryption password)
I reverse to previous settings.

[Dell E5510] Blank screen during and after boot

Hello,
I performed system update some time ago (2 or 3 weeks) and left my computer unused. Today I tried to power on it and I was very surprised, because I didn't see anything on screen during boot and after it. I rebooted computer in fallback mode (I also added "i915.modeset=0" to kernel init args), and I saw command line. Then I updated whole system and rebooted it again - no luck again blank screen during boot and after.
I rebooted it one more time, but with default kernel (I disabled KMS again via GRUB command line) and I saw systemd output during boot. I teems, that all services were started successfully, because all messages were prefixed with "OK". Then I cloud only use command line, because Gnome 3 was not running under seventh console.
Any idea what is going one here?

Hi there Sudarshan21,
I would recommend taking a look at the troubleshooting steps found in the article below.
Mac OS X: Gray screen appears during startup
http://support.apple.com/kb/ts2570
-Griff W.

Satellite A85-s107 - blank screen on boot up using battery power

Satellite A85-s107 blank screen on boot up using battery power
When I boot up A85-s107 in battery power, it is getting booted up in the background, but my screen is blank.
After that if I connect it to AC power and switch off/on the laptop power button, the display comes back to life.
There is no problem when I boot up when connected to AC power.
Battery is fully charged and computer will run off battery if I remove AC after boootup
Any suggestions?
Ps:
also notice that when I remove AC and then reconnect I have to start the computer twice as it doesnt boot the 1st time?

hi nick34_99,
sounds to me like a bad charging electronic...
i got this issue on my sat3000 too, but only when battery is not fully charged...
start the unit with a dos-disc (freedos has an cd image) and let the battery run "dry"...
after that boot without battery (ac-adapter connected of course) and log on.
after that shut down insert battery and try with batt only....
this trick has done magic on my machine...

Blank screen during calls/alarms after updating to...

Hello. I really need your advice. The problem is that I have blank screen during all calls and alarms and worst thing is that menu and shutdown keys isn't working idher. I can't do anything when I have a call or when I want to shut down alarm clock. Everything worked fine with Symbian Belle but this **bleep** started after I updated it to Belle. So what should I do in this case. Any advices? Thak you
Solved!
Go to Solution.

Hi ausrius517,
Sorry to hear you are having a problem with your device.
Have you tried performing the following resets to see if it will solve your issue:
Soft Reset - this will not delete and data off your device.
Enter *#7780# into your phone's keypad and when prompted, enter 12345 (default code)
If there are not too much data on your device and you have made a backup, you can go for the hard reset option below.
Hard Reset - this will wipe all data off your device, so a backup is recommeded before doing this.
Enter *#7370# into your phone's keypad and when prompted, enter 12345 (default code)
Regards,
haZey
If you find this post helpful, a click upon the white star at bottom would always be appreciated.
If it also solves your problem, clicking ACCEPT AS SOLUTION below it will benefit other users!

WDS Capture Image Blank Screen with Cursor

Hey everyone, happy Friday and Happy Sysadmin Day!
Not super happy for myself unfortunately! I'm having a problem with a Capture Image in WDS. I have a Sysprepped Dell 6440 running Windows 7 x64.I've created a Capture Image in WDS from a boot image with drivers injected and without drivers injected, but every time I boot from PXE, it gets to the windows loading screen, and then it just shows a blank screen with a cursor.I'm using Microsoft's OpenLicense ISO as a base for the boot.wimI can't find any solution that works. I've tried mounting and unmounting the WIM, restarting WDS, etc. This is getting really frustrating as I'm so close to having these images ready.The blank screen won't do anything, won't open a cmd with Shift+
F10 or anything. I've also tried booting on a different machine and it does the same thing.Any suggestions are...
This topic first appeared in the Spiceworks Community

HI @Moonrod ,
Welcome to the HP Forums!
It is a super place to find answers and information!
For you to have the best experience in the HP forum I would like to direct your attention to the HP Forums Guide Learn How to Post and More
I grasp you were unable to do a refresh you PC as you received the message that the drive was locked.
Please refer to my post Re: Can't refresh or reset windows 8.1 because drive is locked
Here is a link from the windowsclub.com that may also be informative.
Fix: The drive where Windows is installed is locked.
Best of Luck!
Sparkles1
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the bottom right to say “Thanks” for helping!

New Install - startx results in blank screen with mouse cursor

I installed Arch on my desktop last week with no issues, so I wanted to install it on an old THinkpad R31. Everything with the installation went smooth, but when I try to 'startx' all I get is a blank screen with a mouse cursor that I can move around. I've installed xorg-xinit, xorg-twm, xorg-xclock, and xterm.
I'm not getting any significant errors in the logs, or even the terminal I issue 'startx' in.
I'm not sure what the problem could be...
Here is my output from 'startx'
X.Org X Server 1.13.0
Release Date: 2012-09-05
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.6.0-1-ARCH i686
Current Operating System: Linux x_00294-ibc 3.5.6-1-ARCH #1 SMP PREEMPT Sun Oct 7 19:33:50 CEST 2012 i686
Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=ec6a9a60-8d8c-4de0-960b-9e2a044d0ca5 ro quiet
Build Date: 05 October 2012 02:01:30PM
Current version of pixman: 0.26.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sat Oct 13 09:26:12 2012
(==) Using config directory: "/etc/X11/xorg.conf.d"
Initializing built-in extension Generic Event Extension
Initializing built-in extension SHAPE
Initializing built-in extension MIT-SHM
Initializing built-in extension XInputExtension
Initializing built-in extension XTEST
Initializing built-in extension BIG-REQUESTS
Initializing built-in extension SYNC
Initializing built-in extension XKEYBOARD
Initializing built-in extension XC-MISC
Initializing built-in extension SECURITY
Initializing built-in extension XINERAMA
Initializing built-in extension XFIXES
Initializing built-in extension RENDER
Initializing built-in extension RANDR
Initializing built-in extension COMPOSITE
Initializing built-in extension DAMAGE
Initializing built-in extension MIT-SCREEN-SAVER
Initializing built-in extension DOUBLE-BUFFER
Initializing built-in extension RECORD
Initializing built-in extension DPMS
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension XFree86-VidModeExtension
Initializing built-in extension XFree86-DGA
Initializing built-in extension XFree86-DRI
Initializing built-in extension DRI2
Loading extension GLX
xinit: connection to X server lost
waiting for X server to shut down XIO: fatal IO error 0 (Success) on X server ":0"
after 554 requests (554 known processed) with 0 events remaining.
xterm: fatal IO error 11 (Resource temporarily unavailable) or KillClient on X server ":0"
xterm: fatal IO error 11 (Resource temporarily unavailable) or KillClient on X server ":0"
xterm: fatal IO error 11 (Resource temporarily unavailable) or KillClient on X server ":0"
Server terminated successfully (0). Closing log file.
xinit: unexpected signal 2
And my Xorg.0.log
[ 4955.478]
X.Org X Server 1.13.0
Release Date: 2012-09-05
[ 4955.479] X Protocol Version 11, Revision 0
[ 4955.479] Build Operating System: Linux 3.6.0-1-ARCH i686
[ 4955.479] Current Operating System: Linux x_00294-ibc 3.5.6-1-ARCH #1 SMP PREEMPT Sun Oct 7 19:33:50 CEST 2012 i686
[ 4955.479] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=ec6a9a60-8d8c-4de0-960b-9e2a044d0ca5 ro quiet
[ 4955.479] Build Date: 05 October 2012 02:01:30PM
[ 4955.479]
[ 4955.479] Current version of pixman: 0.26.2
[ 4955.479] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 4955.479] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 4955.480] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Oct 13 09:26:12 2012
[ 4955.480] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 4955.480] (==) No Layout section. Using the first Screen section.
[ 4955.480] (==) No screen section available. Using defaults.
[ 4955.480] (**) |-->Screen "Default Screen Section" (0)
[ 4955.480] (**) | |-->Monitor "<default monitor>"
[ 4955.481] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 4955.481] (==) Automatically adding devices
[ 4955.481] (==) Automatically enabling devices
[ 4955.481] (==) Automatically adding GPU devices
[ 4955.481] (WW) The directory "/usr/share/fonts/TTF/" does not exist.
[ 4955.481] Entry deleted from font path.
[ 4955.481] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 4955.481] Entry deleted from font path.
[ 4955.481] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 4955.481] Entry deleted from font path.
[ 4955.481] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 4955.481] Entry deleted from font path.
[ 4955.481] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 4955.481] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 4955.481] Entry deleted from font path.
[ 4955.481] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 4955.481] (==) FontPath set to:
/usr/share/fonts/misc/
[ 4955.481] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 4955.481] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 4955.481] (II) Loader magic: 0x825a620
[ 4955.482] (II) Module ABI versions:
[ 4955.482] X.Org ANSI C Emulation: 0.4
[ 4955.482] X.Org Video Driver: 13.0
[ 4955.482] X.Org XInput driver : 18.0
[ 4955.482] X.Org Server Extension : 7.0
[ 4955.484] (II) config/udev: Adding drm device (/dev/dri/card0)
[ 4955.486] (--) PCI:*(0:0:2:0) 8086:3577:1014:0505 rev 4, Mem @ 0x98000000/134217728, 0x90100000/524288
[ 4955.486] (--) PCI: (0:0:2:1) 8086:3577:1014:0505 rev 0, Mem @ 0x88000000/134217728, 0x80200000/524288
[ 4955.486] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 4955.486] Initializing built-in extension Generic Event Extension
[ 4955.486] Initializing built-in extension SHAPE
[ 4955.486] Initializing built-in extension MIT-SHM
[ 4955.486] Initializing built-in extension XInputExtension
[ 4955.486] Initializing built-in extension XTEST
[ 4955.486] Initializing built-in extension BIG-REQUESTS
[ 4955.486] Initializing built-in extension SYNC
[ 4955.487] Initializing built-in extension XKEYBOARD
[ 4955.487] Initializing built-in extension XC-MISC
[ 4955.487] Initializing built-in extension SECURITY
[ 4955.487] Initializing built-in extension XINERAMA
[ 4955.487] Initializing built-in extension XFIXES
[ 4955.487] Initializing built-in extension RENDER
[ 4955.487] Initializing built-in extension RANDR
[ 4955.487] Initializing built-in extension COMPOSITE
[ 4955.487] Initializing built-in extension DAMAGE
[ 4955.487] Initializing built-in extension MIT-SCREEN-SAVER
[ 4955.487] Initializing built-in extension DOUBLE-BUFFER
[ 4955.487] Initializing built-in extension RECORD
[ 4955.487] Initializing built-in extension DPMS
[ 4955.487] Initializing built-in extension X-Resource
[ 4955.487] Initializing built-in extension XVideo
[ 4955.487] Initializing built-in extension XVideo-MotionCompensation
[ 4955.487] Initializing built-in extension XFree86-VidModeExtension
[ 4955.487] Initializing built-in extension XFree86-DGA
[ 4955.487] Initializing built-in extension XFree86-DRI
[ 4955.487] Initializing built-in extension DRI2
[ 4955.487] (II) LoadModule: "glx"
[ 4955.488] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 4955.489] (II) Module glx: vendor="X.Org Foundation"
[ 4955.489] compiled for 1.13.0, module version = 1.0.0
[ 4955.489] ABI class: X.Org Server Extension, version 7.0
[ 4955.489] (==) AIGLX enabled
[ 4955.489] Loading extension GLX
[ 4955.489] (==) Matched intel as autoconfigured driver 0
[ 4955.489] (==) Matched intel as autoconfigured driver 1
[ 4955.489] (==) Matched vesa as autoconfigured driver 2
[ 4955.489] (==) Matched modesetting as autoconfigured driver 3
[ 4955.489] (==) Matched fbdev as autoconfigured driver 4
[ 4955.489] (==) Assigned the driver to the xf86ConfigLayout
[ 4955.489] (II) LoadModule: "intel"
[ 4955.490] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[ 4955.491] (II) Module intel: vendor="X.Org Foundation"
[ 4955.491] compiled for 1.13.0, module version = 2.20.9
[ 4955.491] Module class: X.Org Video Driver
[ 4955.491] ABI class: X.Org Video Driver, version 13.0
[ 4955.491] (II) LoadModule: "vesa"
[ 4955.491] (WW) Warning, couldn't open module vesa
[ 4955.491] (II) UnloadModule: "vesa"
[ 4955.492] (II) Unloading vesa
[ 4955.492] (EE) Failed to load module "vesa" (module does not exist, 0)
[ 4955.492] (II) LoadModule: "modesetting"
[ 4955.492] (WW) Warning, couldn't open module modesetting
[ 4955.492] (II) UnloadModule: "modesetting"
[ 4955.492] (II) Unloading modesetting
[ 4955.492] (EE) Failed to load module "modesetting" (module does not exist, 0)
[ 4955.493] (II) LoadModule: "fbdev"
[ 4955.493] (WW) Warning, couldn't open module fbdev
[ 4955.493] (II) UnloadModule: "fbdev"
[ 4955.493] (II) Unloading fbdev
[ 4955.493] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 4955.493] (II) intel: Driver for Intel 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, B43, Clarkdale, Arrandale,
Sandybridge Desktop (GT1), Sandybridge Desktop (GT2),
Sandybridge Desktop (GT2+), Sandybridge Mobile (GT1),
Sandybridge Mobile (GT2), Sandybridge Mobile (GT2+),
Sandybridge Server, Ivybridge Mobile (GT1), Ivybridge Mobile (GT2),
Ivybridge Desktop (GT1), Ivybridge Desktop (GT2), Ivybridge Server,
Ivybridge Server (GT2), Haswell Desktop (GT1), Haswell Desktop (GT2),
Haswell Desktop (GT2+), Haswell Mobile (GT1), Haswell Mobile (GT2),
Haswell Mobile (GT2+), Haswell Server (GT1), Haswell Server (GT2),
Haswell Server (GT2+), Haswell SDV Desktop (GT1),
Haswell SDV Desktop (GT2), Haswell SDV Desktop (GT2+),
Haswell SDV Mobile (GT1), Haswell SDV Mobile (GT2),
Haswell SDV Mobile (GT2+), Haswell SDV Server (GT1),
Haswell SDV Server (GT2), Haswell SDV Server (GT2+),
Haswell ULT Desktop (GT1), Haswell ULT Desktop (GT2),
Haswell ULT Desktop (GT2+), Haswell ULT Mobile (GT1),
Haswell ULT Mobile (GT2), Haswell ULT Mobile (GT2+),
Haswell ULT Server (GT1), Haswell ULT Server (GT2),
Haswell ULT Server (GT2+), Haswell CRW Desktop (GT1),
Haswell CRW Desktop (GT2), Haswell CRW Desktop (GT2+),
Haswell CRW Mobile (GT1), Haswell CRW Mobile (GT2),
Haswell CRW Mobile (GT2+), Haswell CRW Server (GT1),
Haswell CRW Server (GT2), Haswell CRW Server (GT2+),
ValleyView PO board
[ 4955.496] (--) using VT number 7
[ 4955.508] (II) intel(0): using device path '/dev/dri/card0'
[ 4955.509] (II) intel(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 4955.509] (==) intel(0): Depth 24, (--) framebuffer bpp 32
[ 4955.509] (==) intel(0): RGB weight 888
[ 4955.509] (==) intel(0): Default visual is TrueColor
[ 4955.509] (--) intel(0): Integrated Graphics Chipset: Intel(R) i830M
[ 4955.509] (**) intel(0): Relaxed fencing disabled
[ 4955.509] (**) intel(0): Wait on SwapBuffers? enabled
[ 4955.509] (**) intel(0): Triple buffering? enabled
[ 4955.509] (**) intel(0): Framebuffer tiled
[ 4955.510] (**) intel(0): Pixmaps tiled
[ 4955.510] (**) intel(0): 3D buffers tiled
[ 4955.510] (**) intel(0): SwapBuffers wait enabled
[ 4955.510] (==) intel(0): video overlay key set to 0x101fe
[ 4955.593] (II) intel(0): Output VGA1 has no monitor section
[ 4955.593] (II) intel(0): Output LVDS1 has no monitor section
[ 4955.594] (--) intel(0): found backlight control interface /sys/class/backlight/thinkpad_screen
[ 4955.676] (II) intel(0): EDID for output VGA1
[ 4955.677] (II) intel(0): Printing probed modes for output VGA1
[ 4955.677] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 4955.677] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 4955.677] (II) intel(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
[ 4955.677] (II) intel(0): Modeline "848x480"x60.0 33.75 848 864 976 1088 480 486 494 517 +hsync +vsync (31.0 kHz e)
[ 4955.677] (II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 489 492 525 -hsync -vsync (31.5 kHz e)
[ 4955.677] (II) intel(0): EDID for output LVDS1
[ 4955.677] (II) intel(0): Not using default mode "320x240" (doublescan mode not supported)
[ 4955.677] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported)
[ 4955.677] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported)
[ 4955.677] (II) intel(0): Not using default mode "512x384" (doublescan mode not supported)
[ 4955.678] (II) intel(0): Not using default mode "640x480" (doublescan mode not supported)
[ 4955.678] (II) intel(0): Not using default mode "640x512" (doublescan mode not supported)
[ 4955.678] (II) intel(0): Not using default mode "800x600" (doublescan mode not supported)
[ 4955.678] (II) intel(0): Not using default mode "896x672" (doublescan mode not supported)
[ 4955.678] (II) intel(0): Not using default mode "928x696" (doublescan mode not supported)
[ 4955.678] (II) intel(0): Not using default mode "960x720" (doublescan mode not supported)
[ 4955.678] (II) intel(0): Not using default mode "700x525" (doublescan mode not supported)
[ 4955.678] (II) intel(0): Printing probed modes for output LVDS1
[ 4955.678] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 +hsync +vsync (48.4 kHz P)
[ 4955.678] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz d)
[ 4955.678] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz d)
[ 4955.678] (II) intel(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz d)
[ 4955.678] (II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz d)
[ 4955.678] (II) intel(0): Output VGA1 connected
[ 4955.678] (II) intel(0): Output LVDS1 connected
[ 4955.678] (II) intel(0): Using exact sizes for initial modes
[ 4955.678] (II) intel(0): Output VGA1 using initial mode 1024x768
[ 4955.678] (II) intel(0): Output LVDS1 using initial mode 1024x768
[ 4955.678] (II) intel(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 4955.678] (II) intel(0): Kernel page flipping support detected, enabling
[ 4955.678] (==) intel(0): DPI set to (96, 96)
[ 4955.678] (II) Loading sub module "fb"
[ 4955.678] (II) LoadModule: "fb"
[ 4955.679] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 4955.679] (II) Module fb: vendor="X.Org Foundation"
[ 4955.679] compiled for 1.13.0, module version = 1.0.0
[ 4955.679] ABI class: X.Org ANSI C Emulation, version 0.4
[ 4955.679] (II) Loading sub module "dri2"
[ 4955.679] (II) LoadModule: "dri2"
[ 4955.680] (II) Module "dri2" already built-in
[ 4955.680] (==) Depth 24 pixmap format is 32 bpp
[ 4955.680] (II) intel(0): [DRI2] Setup complete
[ 4955.680] (II) intel(0): [DRI2] DRI driver: i915
[ 4955.680] (II) intel(0): Allocated new frame buffer 1024x768 stride 4096, tiled
[ 4955.680] (II) UXA(0): Driver registered support for the following operations:
[ 4955.680] (II) solid
[ 4955.680] (II) copy
[ 4955.680] (II) composite (RENDER acceleration)
[ 4955.680] (II) put_image
[ 4955.680] (II) get_image
[ 4955.680] (==) intel(0): Backing store disabled
[ 4955.680] (==) intel(0): Silken mouse enabled
[ 4955.681] (II) intel(0): Initializing HW Cursor
[ 4955.681] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 4955.684] (==) intel(0): DPMS enabled
[ 4955.684] (==) intel(0): Intel XvMC decoder disabled
[ 4955.684] (II) intel(0): Set up overlay video
[ 4955.684] (II) intel(0): direct rendering: DRI2 Enabled
[ 4955.684] (==) intel(0): hotplug detection: "enabled"
[ 4955.983] (--) RandR disabled
[ 4956.021] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 4956.021] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 4956.021] (II) AIGLX: enabled GLX_ARB_create_context
[ 4956.021] (II) AIGLX: enabled GLX_ARB_create_context_profile
[ 4956.021] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
[ 4956.021] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
[ 4956.021] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[ 4956.021] (II) AIGLX: Loaded and initialized i915
[ 4956.022] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 4956.023] (II) intel(0): Setting screen physical size to 270 x 203
[ 4956.124] (II) config/udev: Adding input device Power Button (/dev/input/event4)
[ 4956.124] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 4956.124] (II) LoadModule: "evdev"
[ 4956.124] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 4956.125] (II) Module evdev: vendor="X.Org Foundation"
[ 4956.125] compiled for 1.13.0, module version = 2.7.3
[ 4956.125] Module class: X.Org XInput Driver
[ 4956.125] ABI class: X.Org XInput driver, version 18.0
[ 4956.125] (II) Using input driver 'evdev' for 'Power Button'
[ 4956.125] (**) Power Button: always reports core events
[ 4956.125] (**) evdev: Power Button: Device: "/dev/input/event4"
[ 4956.126] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 4956.126] (--) evdev: Power Button: Found keys
[ 4956.126] (II) evdev: Power Button: Configuring as keyboard
[ 4956.126] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4/event4"
[ 4956.126] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 4956.126] (**) Option "xkb_rules" "evdev"
[ 4956.126] (**) Option "xkb_model" "evdev"
[ 4956.126] (**) Option "xkb_layout" "us"
[ 4956.197] (II) config/udev: Adding input device Video Bus (/dev/input/event2)
[ 4956.198] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 4956.198] (II) Using input driver 'evdev' for 'Video Bus'
[ 4956.198] (**) Video Bus: always reports core events
[ 4956.198] (**) evdev: Video Bus: Device: "/dev/input/event2"
[ 4956.198] (--) evdev: Video Bus: Vendor 0 Product 0x6
[ 4956.198] (--) evdev: Video Bus: Found keys
[ 4956.198] (II) evdev: Video Bus: Configuring as keyboard
[ 4956.198] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A03:00/LNXVIDEO:00/input/input2/event2"
[ 4956.198] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
[ 4956.198] (**) Option "xkb_rules" "evdev"
[ 4956.198] (**) Option "xkb_model" "evdev"
[ 4956.198] (**) Option "xkb_layout" "us"
[ 4956.200] (II) config/udev: Adding input device Lid Switch (/dev/input/event3)
[ 4956.200] (II) No input driver specified, ignoring this device.
[ 4956.200] (II) This device may have been added with another device file.
[ 4956.201] (II) config/udev: Adding input device Sleep Button (/dev/input/event1)
[ 4956.201] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
[ 4956.201] (II) Using input driver 'evdev' for 'Sleep Button'
[ 4956.202] (**) Sleep Button: always reports core events
[ 4956.202] (**) evdev: Sleep Button: Device: "/dev/input/event1"
[ 4956.202] (--) evdev: Sleep Button: Vendor 0 Product 0x3
[ 4956.202] (--) evdev: Sleep Button: Found keys
[ 4956.202] (II) evdev: Sleep Button: Configuring as keyboard
[ 4956.202] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input1/event1"
[ 4956.202] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 8)
[ 4956.202] (**) Option "xkb_rules" "evdev"
[ 4956.202] (**) Option "xkb_model" "evdev"
[ 4956.202] (**) Option "xkb_layout" "us"
[ 4956.204] (II) config/udev: Adding drm device (/dev/dri/card0)
[ 4956.205] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 4956.205] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 4956.205] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[ 4956.205] (**) AT Translated Set 2 keyboard: always reports core events
[ 4956.205] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[ 4956.205] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[ 4956.205] (--) evdev: AT Translated Set 2 keyboard: Found keys
[ 4956.205] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[ 4956.205] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[ 4956.205] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 9)
[ 4956.205] (**) Option "xkb_rules" "evdev"
[ 4956.206] (**) Option "xkb_model" "evdev"
[ 4956.206] (**) Option "xkb_layout" "us"
[ 4956.208] (II) config/udev: Adding input device TPPS/2 IBM TrackPoint (/dev/input/event6)
[ 4956.208] (**) TPPS/2 IBM TrackPoint: Applying InputClass "evdev pointer catchall"
[ 4956.208] (II) Using input driver 'evdev' for 'TPPS/2 IBM TrackPoint'
[ 4956.208] (**) TPPS/2 IBM TrackPoint: always reports core events
[ 4956.208] (**) evdev: TPPS/2 IBM TrackPoint: Device: "/dev/input/event6"
[ 4956.208] (--) evdev: TPPS/2 IBM TrackPoint: Vendor 0x2 Product 0xa
[ 4956.208] (--) evdev: TPPS/2 IBM TrackPoint: Found 3 mouse buttons
[ 4956.208] (--) evdev: TPPS/2 IBM TrackPoint: Found relative axes
[ 4956.208] (--) evdev: TPPS/2 IBM TrackPoint: Found x and y relative axes
[ 4956.208] (II) evdev: TPPS/2 IBM TrackPoint: Configuring as mouse
[ 4956.208] (**) evdev: TPPS/2 IBM TrackPoint: YAxisMapping: buttons 4 and 5
[ 4956.208] (**) evdev: TPPS/2 IBM TrackPoint: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 4956.208] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input6/event6"
[ 4956.208] (II) XINPUT: Adding extended input device "TPPS/2 IBM TrackPoint" (type: MOUSE, id 10)
[ 4956.209] (II) evdev: TPPS/2 IBM TrackPoint: initialized for relative axes.
[ 4956.209] (**) TPPS/2 IBM TrackPoint: (accel) keeping acceleration scheme 1
[ 4956.209] (**) TPPS/2 IBM TrackPoint: (accel) acceleration profile 0
[ 4956.209] (**) TPPS/2 IBM TrackPoint: (accel) acceleration factor: 2.000
[ 4956.209] (**) TPPS/2 IBM TrackPoint: (accel) acceleration threshold: 4
[ 4956.210] (II) config/udev: Adding input device TPPS/2 IBM TrackPoint (/dev/input/mouse0)
[ 4956.210] (II) No input driver specified, ignoring this device.
[ 4956.210] (II) This device may have been added with another device file.
[ 4956.211] (II) config/udev: Adding input device PC Speaker (/dev/input/event5)
[ 4956.211] (II) No input driver specified, ignoring this device.
[ 4956.211] (II) This device may have been added with another device file.
[ 4956.213] (II) config/udev: Adding input device ThinkPad Extra Buttons (/dev/input/event7)
[ 4956.213] (**) ThinkPad Extra Buttons: Applying InputClass "evdev keyboard catchall"
[ 4956.213] (II) Using input driver 'evdev' for 'ThinkPad Extra Buttons'
[ 4956.213] (**) ThinkPad Extra Buttons: always reports core events
[ 4956.213] (**) evdev: ThinkPad Extra Buttons: Device: "/dev/input/event7"
[ 4956.214] (--) evdev: ThinkPad Extra Buttons: Vendor 0x1014 Product 0x5054
[ 4956.214] (--) evdev: ThinkPad Extra Buttons: Found keys
[ 4956.214] (II) evdev: ThinkPad Extra Buttons: Configuring as keyboard
[ 4956.214] (**) Option "config_info" "udev:/sys/devices/platform/thinkpad_acpi/input/input7/event7"
[ 4956.214] (II) XINPUT: Adding extended input device "ThinkPad Extra Buttons" (type: KEYBOARD, id 11)
[ 4956.214] (**) Option "xkb_rules" "evdev"
[ 4956.214] (**) Option "xkb_model" "evdev"
[ 4956.214] (**) Option "xkb_layout" "us"
[ 4960.630] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 4964.186] (II) evdev: ThinkPad Extra Buttons: Close
[ 4964.189] (II) UnloadModule: "evdev"
[ 4964.189] (II) evdev: TPPS/2 IBM TrackPoint: Close
[ 4964.189] (II) UnloadModule: "evdev"
[ 4964.189] (II) evdev: AT Translated Set 2 keyboard: Close
[ 4964.189] (II) UnloadModule: "evdev"
[ 4964.189] (II) evdev: Sleep Button: Close
[ 4964.189] (II) UnloadModule: "evdev"
[ 4964.189] (II) evdev: Video Bus: Close
[ 4964.190] (II) UnloadModule: "evdev"
[ 4964.190] (II) evdev: Power Button: Close
[ 4964.190] (II) UnloadModule: "evdev"
[ 4964.192] Server terminated successfully (0). Closing log file.

karol wrote:
Leonid.I wrote:@0x001A4:
To run twm, you need to install xorg-twm from [extra] (I am not sure if it installs by default). Do you have xterm installed?
According to his first post he has both xorg-twm and xterm installed.
I do indeed.
I went ahead and installed LXDE anyways, just to see what would happen. Exact same thing, it looks like everything is about to load but only the mouse cursor shows up. My Xorg.0.log is the same, so I won't post it again.
I do get an error in the console about the openbox menu.xml file missing but I doubt that's related.
X.Org X Server 1.13.0
Release Date: 2012-09-05
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.6.0-1-ARCH i686
Current Operating System: Linux x_00294-ibc 3.5.6-1-ARCH #1 SMP PREEMPT Sun Oct 7 19:33:50 CEST 2012 i686
Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=ec6a9a60-8d8c-4de0-960b-9e2a044d0ca5 ro quiet
Build Date: 05 October 2012 02:01:30PM
Current version of pixman: 0.26.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Oct 15 18:12:28 2012
(==) Using config directory: "/etc/X11/xorg.conf.d"
Initializing built-in extension Generic Event Extension
Initializing built-in extension SHAPE
Initializing built-in extension MIT-SHM
Initializing built-in extension XInputExtension
Initializing built-in extension XTEST
Initializing built-in extension BIG-REQUESTS
Initializing built-in extension SYNC
Initializing built-in extension XKEYBOARD
Initializing built-in extension XC-MISC
Initializing built-in extension SECURITY
Initializing built-in extension XINERAMA
Initializing built-in extension XFIXES
Initializing built-in extension RENDER
Initializing built-in extension RANDR
Initializing built-in extension COMPOSITE
Initializing built-in extension DAMAGE
Initializing built-in extension MIT-SCREEN-SAVER
Initializing built-in extension DOUBLE-BUFFER
Initializing built-in extension RECORD
Initializing built-in extension DPMS
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension XFree86-VidModeExtension
Initializing built-in extension XFree86-DGA
Initializing built-in extension XFree86-DRI
Initializing built-in extension DRI2
Loading extension GLX
Openbox-Message: Unable to find a valid menu file "/usr/share/lxde/openbox/menu.xml"
xinit: connection to X server lost
waiting for X server to shut down pcmanfm: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
after 2326 requests (2323 known processed) with 0 events remaining.
Server terminated successfully (0). Closing log file.
xinit: unexpected signal 2
.xinitrc for my user
exec ck-launch-session startlxde
Very wierd.

New Image from edited Image on Screen

hi,
i want to make an image on screen then edit it and after that save the resulting edited image and display it saperately???
do anyone have any idea that after editing how will i save the new image i get....
thanks

http://forum.java.sun.com/thread.jspa?threadID=762729&messageID=4509503
problem solved :)

Blank screen & no booting after running BIOS update on Satellite A200-1AE

Here is my problem with my A200-1AE (PSAECE) Notebook:
I downloaded the latest BIOS update from the Toshiba download drivers library to install Win XP since finally the drivers are realized. (Note the update clearly stated to run ONLY if you want to install XP on you NB).
So I unzipped the file and after hitting the .exe file it started updating the BIOS on its own without me giving the liberty to do so. Half way the N/B froze for about 20 minutes and as I didnt know what else to do so I reset it.
Result? The NB does NOT boot. I press the power button, the Hard Drive icon flashes 2-3 times as well as the DVD drive, I get a blank screen and the power cord & power button icons constantly on. I removed the battery and the power cord for 48 hours hoping it will reset the BIOS on its own to no avail.
The BIOS battery is under the touchpad which means I have to disassemble the whole laptop and I am not ready to do so. I dont know if on the motherboard there are BIOS reset jumpers and I need someones help as to what I should do. I am starting to think that things where MUCH easier back to when I just had a desktop PC.
THERE must be something I can do other that taking it to the service center and pay half the value of the laptop in repairs.... PLS HELP Im desperate....

Hi there,
first of all: a notebook is not a desktop and such mobile computer does not have jumpers like a deskop computer. They surely have something to delete the BIOS but I am not so sure IF resetting the BIOS could help you.
I guess you will have to send your machine to a service center for repair because in such cases you will have no other option. Do you have still warranty on this machine?
Greets

GT70 2OC Bios update went bad, blank screen on boot

Hi,
I want to update my laptop's bios, model being MSI GT70 2OC - 065US. When I went to MSI driver download site, there were two different bios files for download.
Version 517 for UEFI None RAID SKU and version 717 for UEFI RAID0 SKU. My Laptop has one hard disk and other sata slot for hdd is empty. I am confused whether which BIOS file should I use for my laptop. Please help.
Thanks.
UPDATE
I tried to update BIOS using version 517 file. I was following procedure given in pdf manual. I followed every step as per manual. Laptop asked permission to reboot as suggested in manual. But after reboot only blank screen is appearing and only fan is working, no other activity is there.
Kindly help.

Quote from: ajaymore2909 on 12-January-15, 02:26:50
Hi,
I want to update my laptop's bios, model being MSI GT70 2OC - 065US. When I went to MSI driver download site, there were two different bios files for download.
Version 517 for UEFI None RAID SKU and version 717 for UEFI RAID0 SKU. My Laptop has one hard disk and other sata slot for hdd is empty. I am confused whether which BIOS file should I use for my laptop. Please help.
Thanks.
UPDATE
I tried to update BIOS using version 517 file. I was following procedure given in pdf manual. I followed every step as per manual. Laptop asked permission to reboot as suggested in manual. But after reboot only blank screen is appearing and only fan is working, no other activity is there.
Kindly help.
Power on/off your laptop. If the laptop does the same then you have to send it back for RMA.

Lumia 800 constant blank screen during calls

hi guys,
I have a nokia lumia 800,
when im on a call the screen stays blank so i cant access any of the in call options? i dont have a screen protector on the phone, i have run the diagnostics app and the the proximity sensor is responding fine!!! so it leads me to think its a software issue? is this a common problem or am i doing something wrong?
hope you can help.
daniel

The screen gets turned off during a phone call when the proximity sensor is covered. This is done to avoid accidental touch screen actions when you are in a call.
If the screen gets turned off immediately when dialing a number or receiving a call, check that your phone does not have any object which may cause detection. There are various non-Nokia original screen protectors sold in the market which cover the proximity sensor causing blank screen issues during calls.
You can take the following steps to check the issue. If the screen keeps turned off, the protector may not be of the right size and will block the sensor on the upper part of the front side. Then either remove the protector or cut off the plastic from the blocking area.
Make or receive a call with the phone.
Once the phone is in a call place your hand 1cm above the screen and display will turn off.
Remove your hand and display shall turn back on.
Repeat the test steps 1,2,3 for 3 times to verify the proximity sensor function.
If i have helped at all a click on the white star below would be nice thanks.
Now using the Lumia 1520

Blank Screen during 3D Games ??

Hi, I am a newbie here. Hope to get used to it here ^_^
So...... Yoroshiku!
Straight to my problem.
I seems to encounter this problem below.
My screen will goes to sleep mode or blank screen whenever I tried to play games such as WarCraft III, Battle Realms and other 3D games.
Can someone pelase advise ?
Below is my system info:
MEC PSU: 3.3V/14A, 5V/27A, 12V/15A, Peak Load =380W
MSI K7N2 Delta (Nvidia nForce2 Chipset Based) with:
   AGP8X
   Dual DDR400
   10/100 LAN Ethernet
   5.1 Channel Audio
   Real 128bit Memory Bus
Athlon XP 2100+
1x 256Mb DDR PC3200 CL3 184-Pin DIMM
MSI GeForce4 MX400SE-T 64Mb with TV-out
Using on-board soundcard
HDD: Western Digital 80Gb Ata 133-7200 Rpm
Maxtor 40Gb Ata 133-5400 Rpm
Asus 16x max Dvd-rom
Asus CDRW 52x24x52x
Win Xp Prof. SP1

Fredrik Åsenius , You pointed out that he has an nForce based motherboard and then you say install the 4in1 drivers in safe mode.
4in1 driver are only for VIA based chipsets, I am sure you know this.
fatmantaray:
Leave it on 133Mhz and remove both cd drives and 1 hard drive.
See what happens, that should reduce your power consumption.
Just incase you PSU cannot handle it.

Blank screen after boot - After update.

Hello!
I have the following problem with my arch dist:
I recently - and after several weeks without touching it - updated my arch but, after rebooting, the laptop screen went blank just after booting up. Using the fallback boot resulted in the same ... well.. result. This is as much as i can describe since i don´t know how to access a comand line in this context, in order to test/check what´s going on. Anyone can help me?
Thanks

Assuming you are using grub, you can edit /boot/grub/menu.lst when grub is loading, in order to force it to not boot into X. On boot, select your normal arch linux entry from to boot list (don't press enter) and type e to edit the menu.lst Press e again on the kernel line and append this number:
kernel /vmlinuz26 root=/dev/sda3 resume=/dev/sda5 ro 1
Press enter and then you boot it by pressing b. It is the number at the end that defines the run level, in this case 1 (single user). This will allow you to boot into console as root.
Edit: I meant run level 1 (single user)
Last edited by roygbiv (2011-06-24 20:08:01)

[MOOT] UEFI USB Install (from 201306 image) - blank screen during boot

Similar Messages

Maybe you are looking for