V570 hangs during boot up - message "please wait"

I just got a new V570 Lenovo IdeaPad laptop on Sunday. It was working fine until Monday. I tried to start it up and it paused at the Please Wait screen. I didn't know what to do so I held the power button until it shut down. I then left it for a bit and it started up fine. Now, this has happened again and I am guessing it is not good. How can I fix it?
Solved!
Go to Solution.

UPDATE - OFFICIAL LENOVO SOLUTION
Please follow the link above to the Lenovo support site - this tip covers a software hang condition / please wait message caused by an interaction with the fingerprint reader and veriface software which may develop under certain conditions on V470/V570 and B470/B570 systems.
who knows - you may have fixed it (DMB stack in CMOS). edit: removed suggestion about safe start since it didn't work..
The removing the battery and the power cord is similar to what we had to do with desktop mobos - unplug it , wait 10 seconds, press power-on a few times to bleed the power off the PSU, and then plug it in and start up - it takes power off the BIOS and causes it to re-create the DMB stack the next time you boot. DMB = info about each device .
I also advise you to get current with MS updates (not necessarily all the optional ones!).
IdeaPad V570-1066A9U, Built 5-22-2011, BIOS 44CN36WW(2011-08-04)
Win7 Pro x64 clean install. Sammy 840 Pro 128GB SSD. Fast! Used nice hardware manual to re-grease CPU and remove tiny bit of lint.

Similar Messages

K8N Neo 2 Platinum -- Hanging during boot --RESOLVED--

Heres the problem...
My system will hang during boot at anytime, from bios initalization to full windows boot (No BSOD ever and where the pc hangs in the boot proccess is totally random). And the only way to get past the hang is do a soft reset. I have to restart my system up to 3 times before I get a good boot, but once the pc is up and running, it stay running till I shut it down. (no hangs)
Now if I shut it down after the system has been running for a while, the pc will restart normally without any hangs. The hangs only occur after the pc has been down for a time.
I have reseated all the connectors, the memory (even tried different slots), add-in cards, cpu.
I have a clean install of Windows XP Pro (hard drives have been repartitioned and reformatted as NTFS)
All fans are spinning up fine, all temps are within norm, power supply voltages are within norm.
No phsysical signs of bad caps on the system board.
I ran ran Memtest86 for 18 hours striaght with no errors.
Ran CPU stress test with no problems.
No IRQ,DMA,etc conflicts found.
Windows records no errors during a freeze and I have checked for unwanted services/proccess as well.
I have tried min install to no avail.
Bois is retaining its settings (so bios battery is good)
I do not over clock anything. Bios is set to discover all important setting automaticly. (Bios setting are the same now as they were 6 months ago)
I am down to a possible cold solder joint on the system board?
This problem started to occur about a month ago.
If someone has seen this exact problem and has a resolution, well I would appreciate it if you passed along your knowladge
I am down to my last option of RMAing my system board. No. I have not replaced any components due to the fact I don't have extras lieing around nor can I spend the money just to troubleshoot :(
Specs..
Athlon 64 3500+
2 gig (pqi TURBO 1GB 184-Pin DDR SDRAM DDR 400 (PC 3200) Unbuffered System Memory Model PQI3200-1024SB) Ran in Dual config
Geforce 6800 (BFG 6800 GT oc)
Creative X-Fi XtremeMusic
Antec NeoPower 480
2 WD 36gig SATA Raptors in raid 0 (system partition)
2 WD 120gig IDE in raid 0 (data partition)
Windows XP Pro
all drivers and bios are manufacture ref and up-to-date.
Ok I won't go into all the details of why I missed this but it turns out the northbridge heatsink fan had stopped spinning and thus the hangs during boot due to overheating (hhmmm, when I step back and look at this the symptoms point right to overheating).
This also expains why after several attempts at booting up, once the pc was up it would run like a champ. The chip would of course overheat and cause random freezes. Now due to the placement of the chip and the design of the heatsink once there was enough airflow over the heatsink the chip would remain cool enough to prevent further freezing of the system.
What helped to facilitate this is that I have a ducted fan system installed in the bottom of my case which directs a substantal amount of fresh air to the pci slots, the chip set and the AGI slot as well.
So what have we learned class?
1. check the obvious
2. do a complete physical inspection of your system
3. KISS -- keep it simple stupid

Is this your ram:
Quote
Part Number: PQI3200-1024SB
Quality Control: Comprehensively and rigorously tested
Package: 1024MB single pack
Organization: 128M x 64-bit
CAS Latency: 3-4-4-8
Test Voltage: 2.6 V
PCB Board: 8 Layers PCB
Heat Spreader: Mirrored Black Copper
Speed: DDR 400 MHz (PC3200)
Type: 184-pin DDR SDRAM
Error Checking: Non-ECC
Registered/Unbuffered: Unbuffered
Warranty: Lifetime
This is a quote from MSI web site:
Quote
Main Memory
• Supports dual channel DDR 266/333/400, using four 184-pin DDR DIMMs.
• Supports the memory size up to 4GB
• Supports 2.5v DDR SDRAM DIMM
Due to the High Performance Memory design, motherboards or system configurations may or may not operate smoothly at the JEDEC (Joint Electron Device Engineering Council) standard settings (BIOS Default on the motherboard) such as DDR voltage, memory speeds and memory timing. Please confirm and adjust your memory setting in the BIOS accordingly for better system stability.
Example: Kingston HyperX DDR500 PC4000 operates at 2.65V, 3-4-4-8, CL=3.
For more information about specification of high performance memory modules, please check with your Memory Manufactures for more details.
Manually adjust your ram voltage to 2.65 volts and then manually adjust your ram timings to 3-4-4-8-2T.
If that does not work then do as Richard suggested and strip down to a bar-bone system, this is CPU+fan, 1 stick of ram (try other stick and different slots as one may be bad), graphic card and PS-2 keyboard, if it boots fine without any problems then add one device at a time until you find the problem.
Post back results as there are more things one can try but lets start with the simple stuff and work up.

My ipod 60gb classic is showing as fully charged until I connect it to my pc when it comes up with the error message, 'please wait very low battery' and the little wheel goes round and nothing happens, can anyone explain why this is and what i can do?

My ipod 60gb classic is showing as fully charged until I connect it to my pc when it comes up with the error message, 'please wait very low battery' and the little wheel goes round and nothing happens, can anyone explain why this is and what i can do?

I have worked my way through the assistant and nothing works. I have tried connecting in disc mode but although the screen on the ipod is showing that the device is charged and that it is in disc mode as soon as I connect it to the computer it comes up with the error message 'please wait very low battery' and stays like that until I disconnect when it appears to be OK again. I have tried on both pc and mac.
BTW the ipod is an ipod video not classic if that makes any difference.
Thanks

Sharepoint 2003 Message please wait while setup upgrades your sharepoint sites. This may take a few minutes to a few hours depending on the size of your sites.

Hi All,
We have recently installed Service Pack 4 In SharePoint 2003 I,e SPS 2.0 , we ran the stsadm upgrade command from the Command Prompt , since 5 days the upgrading the sites windows showing and does it completes or not or is there some thing wrong ?.
Environment:
SharePoint 2003 Service Pack 3
SharePoint 2003 Message :
Please wait while setup upgrades your sharepoint sites. This may take a few minutes to a few hours depending on the size of your sites.
We have applied in development box it was completed in 8 hours , but when we do the same in production it was never coming back since 5 days. Not sure what happening
Thanks in Advance
Ravishankar Maduri MCTS,MCPD,MCP

how large are your site collections and content databases?
sounds to me like you're WELL past the recommendations, which could certainly cause such an impact.
Scott Brickey
MCTS, MCPD, MCITP
www.sbrickey.com
Strategic Data Systems - for all your SharePoint needs

Each time I have a message ''please wait while windows configures iTunes''.

when i start my itunes each time i have a message ''please wait while windows configures iTunes''. i recently Upgrad to 9.0.2. i already uninstall and install.
pls help me.
thank you in advance .

when i start my itunes each time i have a message ''please wait while windows configures iTunes''.
The iTunes desktop shortcut is an "advertised shortcut". When you click it, the first thing it does is check the iTunes.msi and determines (against the installation database in there) whether or not there's any files and registry entries and whatnot for iTunes missing on your PC. If it finds something missing, it'll do a repair install of iTunes, which is the "configures" message you're seeing.
As to why it's always doing it in your case, and fixing it ... we'd better first work out if there's real damage to the iTunes stuff on the PC or if the shortcut/itunes.msi/registry machinery is just a bit confused.
Apart from the "configures" message you're getting every time you launch iTunes, is it working okay? Are you able to sync, play music, use the Store and so forth without any trouble? Or are you getting other problems as well?

Photoshop elements 11 freezes when I try to back up the catalogue. i get a message "Please wait while Elements Organizer prepares for backup". what do i do?

Photoshop elements 11 freezes when I try to back up the catalogue. i get a message "Please wait while Elements Organizer prepares for backup". what do i do?

Thank you for responding. Nothing actually worked! After reading the posts online, I called Apple. They indicated they have seen problems with some software after their upgrades. The technician was able to fix the problem on my computer remotely, but I have no clue what he did! But, it was definitely related to their recent upgrade to my computer.

Ultra 5 Hangs During Boot

My Ultra 5 hangs during boot at the following point....
setting default ipv4 interface......
I have tried resetting my router, unplugging the network cable, and nothing seems to work.
John

jmorrissey3, is this a system that just suddenly stopped working, or is this a "new" system (it's not like Ultra 5s are really new) that you're trying to bring up?
If this is a new system for you to tinker with, you should just go ahead and reinstall the operating system. This will blow everything away, of course, but it's good experience if you've never done it before and it will guarantee that the system is clean.
If the data on there must be retained, you can boot from CD-ROM, mount the / partition, and look at some of the configuration files to try to isolate the problem. I would agree that it either is set up for DHCP and there is no DHCP server or there is an invalid NFS mount that is trying to take place.

P205-s6237 Hangs during boot to recovery after replace HDD

I replaced a bad HDD and the machine hangs during boot to the recovery disk. it gets past the inspecting screen and then hangs when the VISTA dots appear. the dots continue to scroll left to right but nothing ever happens. Any ideads on getting it past this point?

I replaced a bad HDD and the machine hangs during boot to the recovery disk. it gets past the inspecting screen and then hangs when the VISTA dots appear. the dots continue to scroll left to right but nothing ever happens. Any ideads on getting it past this point?

Hangs during boot after upgrading to Kernel 2.6.39

I have just installed Arch on a new computer. It works fine until I upgrade to Kernel 2.6.39. After that it hangs on boot.
The end of /var/log/everything.log is posted below.
Jul 26 23:52:06 localhost kernel: [ 6.036766] [drm] nouveau 0000:04:00.0: Parsing VBIOS init table at offset 0x85F3
Jul 26 23:52:06 localhost kernel: [ 6.129046] adt7475 1-002e: ADT7473 device, revision 1
Jul 26 23:52:06 localhost kernel: [ 6.138997] [drm] nouveau 0000:04:00.0: Detected monitoring device: adt7473
Jul 26 23:52:06 localhost kernel: [ 6.139000] [drm] nouveau 0000:04:00.0: 1 available performance level(s)
Jul 26 23:52:06 localhost kernel: [ 6.139002] [drm] nouveau 0000:04:00.0: 0: memory 405MHz core 270MHz shader 540MHz
Jul 26 23:52:06 localhost kernel: [ 6.139233] [TTM] Zone kernel: Available graphics memory: 12371030 kiB.
Jul 26 23:52:06 localhost kernel: [ 6.139236] [TTM] Zone dma32: Available graphics memory: 2097152 kiB.
Jul 26 23:52:06 localhost kernel: [ 6.139238] [TTM] Initializing pool allocator.
Jul 26 23:52:06 localhost kernel: [ 6.139252] [drm] nouveau 0000:04:00.0: Detected 5376MiB VRAM
Jul 26 23:52:06 localhost kernel: [ 6.139260] mtrr: type mismatch for d0000000,8000000 old: write-back new: write-combining
Jul 26 23:52:06 localhost kernel: [ 6.150626] [drm] nouveau 0000:04:00.0: 512 MiB GART (aperture)
Jul 26 23:52:06 localhost kernel: [ 6.152371] [drm] nouveau 0000:04:00.0: failed to load fuc409d
Jul 26 23:52:06 localhost kernel: [ 6.176193] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
Jul 26 23:52:06 localhost kernel: [ 6.176195] [drm] No driver support for vblank timestamp query.
Jul 26 23:52:06 localhost kernel: [ 6.228800] No connectors reported connected with modes
Jul 26 23:52:06 localhost kernel: [ 6.228802] [drm] Cannot find any crtc or sizes - going 1024x768
Jul 26 23:52:06 localhost kernel: [ 6.231002] [drm] nouveau 0000:04:00.0: allocated 1024x768 fb: 0x8020000, bo ffff880608d97800
Jul 26 23:52:06 localhost kernel: [ 6.233786] Console: switching to colour frame buffer device 128x48
Jul 26 23:52:06 localhost kernel: [ 6.235094] fb0: nouveaufb frame buffer device
Jul 26 23:52:06 localhost kernel: [ 6.235094] drm: registered panic notifier
Jul 26 23:52:06 localhost kernel: [ 6.235098] [drm] Initialized nouveau 0.0.16 20090420 for 0000:04:00.0 on minor 0
Jul 26 23:52:06 localhost kernel: [ 6.255449] HDA Intel 0000:04:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
Jul 26 23:52:06 localhost kernel: [ 6.255451] hda_intel: Disable MSI for Nvidia chipset
Jul 26 23:52:06 localhost kernel: [ 6.255599] HDA Intel 0000:04:00.1: setting latency timer to 64
Jul 26 23:52:06 localhost kernel: [ 7.663482] EXT4-fs (sda3): re-mounted. Opts: (null)
Jul 26 23:52:06 localhost kernel: [ 7.807508] EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: (null)
Jul 26 23:52:06 localhost kernel: [ 7.851401] Adding 265068k swap on /dev/sda2. Priority:-1 extents:1 across:265068k
Jul 26 23:52:06 localhost kernel: [ 8.569682] r8169 0000:08:00.0: eth0: link down
Jul 26 23:52:06 localhost kernel: [ 8.569687] r8169 0000:08:00.0: eth0: link down
Jul 26 23:52:06 localhost dhcpcd[747]: eth0: waiting for carrier
Jul 26 23:52:08 localhost dhcpcd[747]: eth0: carrier acquired
Jul 26 23:52:08 localhost kernel: [ 10.301736] r8169 0000:08:00.0: eth0: link up
Jul 26 23:52:08 localhost dhcpcd[747]: eth0: broadcasting for a lease
Jul 26 23:52:12 localhost dhcpcd[747]: eth0: offered 131.181.53.42 from 131.181.127.32
Jul 26 23:52:13 localhost dhcpcd[747]: eth0: acknowledged 131.181.53.42 from 131.181.59.48
Jul 26 23:52:13 localhost dhcpcd[747]: eth0: checking for 131.181.53.42
Jul 26 23:52:18 localhost dhcpcd[747]: eth0: leased 131.181.53.42 for 43200 seconds
Jul 26 23:52:18 localhost dhcpcd[747]: forked to background, child pid 774
Jul 26 23:52:18 localhost crond[823]: /usr/sbin/crond 4.5 dillon's cron daemon, started with loglevel info
Jul 26 23:53:01 localhost crond[823]: FILE /etc/cron.d/prune-cronstamps USER root PID 835 job prune-cronstamps
Jul 26 23:53:01 localhost crond[823]: FILE /var/spool/cron/root USER root PID 836 job sys-hourly
Jul 26 23:53:01 localhost crond[823]: FILE /var/spool/cron/root USER root PID 837 job sys-daily
Jul 26 23:53:01 localhost crond[823]: FILE /var/spool/cron/root USER root PID 838 job sys-weekly
Any help fixing this would be greatly appreciated.

I have been trying to isolate the problem a little further. I re-installed (with just the base and sudo) and after upgrading pacman rebooted and it worked without fail. Then I installed libusb and libusb-compat which where required when I tried to upgrade just the kernel using
pacman -S kernel26
which initially failed because of the missing dependencies libusb and libusb-compat. I then re-booted and that worked without a problem.
I then upgraded to Kernel 2.6.39 using the above command and then it hung on rebooting. I saved the logs at each stage.
The additional logs in errors.log in the reboot that failed are as follows.
ul 26 16:28:39 O313 kernel: [ 5.120698] [drm] nouveau 0000:04:00.0: Pointer to BIT loadval table invalid
Jul 26 16:28:39 O313 kernel: [ 5.360508] [drm] nouveau 0000:04:00.0: failed to load fuc409d
Jul 26 16:28:39 O313 kernel: [ 5.808016] sd 20:0:0:0: [sdb] Assuming drive cache: write through
Jul 26 16:28:39 O313 kernel: [ 5.809960] sd 20:0:0:0: [sdb] Assuming drive cache: write through
Jul 26 16:28:39 O313 kernel: [ 5.812116] sd 20:0:0:0: [sdb] Assuming drive cache: write through
Jul 26 16:28:35 O313 udevd[369]: error: runtime directory '/run/udev' not writable, for now falling back to '/dev/.udev'
The end of kernel.log is as follows:
Sat Jul 9 14:57:41 CEST 2011
Jul 26 16:28:39 O313 kernel: [ 0.000000] Command line: root=/dev/disk/by-uuid/e4733c60-3e54-4001-a83e-415b690dfcb0 ro
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-provided physical RAM map:
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 0000000000100000 - 00000000cfed0000 (usable)
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000cfed0000 - 00000000cfed1000 (ACPI NVS)
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000cfed1000 - 00000000cfee0000 (ACPI data)
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000cfee0000 - 00000000cff00000 (reserved)
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000f0000000 - 00000000f4000000 (reserved)
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 0000000100000000 - 0000000630000000 (usable)
Jul 26 16:28:39 O313 kernel: [ 0.000000] NX (Execute Disable) protection: active
Jul 26 16:28:39 O313 kernel: [ 0.000000] DMI 2.4 present.
Jul 26 16:28:39 O313 kernel: [ 0.000000] DMI: Gigabyte Technology Co., Ltd. X58A-UD5/X58A-UD5, BIOS FD 02/01/2011
Jul 26 16:28:39 O313 kernel: [ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
Jul 26 16:28:39 O313 kernel: [ 0.000000] e820 remove range: 00000000000a0000 - 0000000000100000 (usable)
Jul 26 16:28:39 O313 kernel: [ 0.000000] No AGP bridge found
Jul 26 16:28:39 O313 kernel: [ 0.000000] last_pfn = 0x630000 max_arch_pfn = 0x400000000
And this is the end of daemon.log
Jul 26 16:27:49 O313 init: Switching to runlevel: 6
Jul 26 16:27:50 O313 dhcpcd: received SIGTERM, stopping
Jul 26 16:27:50 O313 dhcpcd: eth0: removing interface
Jul 26 16:28:39 O313 2.352592] udevd[87]: starting version 171
Jul 26 16:28:39 O313 4.531007] udevd[370]: starting version 171
Jul 26 16:28:39 O313 dhcpcd: version 5.2.2 starting
Jul 26 16:28:39 O313 dhcpcd: eth0: waiting for carrier
Jul 26 16:28:35 O313 udevd[369]: error: runtime directory '/run/udev' not writable, for now falling back to '/dev/.udev'
Jul 26 16:28:39 O313 init: Entering runlevel: 3
Please let me know if any further information would be useful in tracking down this problem. Also ignore any timings in my initial post they were incorrect.
Last edited by TheStatsMan (2011-07-26 07:40:48)

Wolfenstein: The New Order message "please wait while downloadable content is being validated"

When starting Wolfenstein:The New Order, the game goes through all the publisher/developer title screens and goes briefly to the standard loading screen then the screen goes totally black. If I press a button on the controller, the game shows the "Loading profile" prompt with the spinning circle. Soon after the message is replaced with "Please wait while downloadable content is being validated". Here is where the game just hangs forever. I have left it on this screen for over an hour and nothing happens. I contacted Bethesda support and they sent me here saying it is a PSN issue. I have already tried uninstalling and deleting all save games, etc. but the problem persists even on a non-patched game. This started happening on Sunday and I have already played the game through once and was on second playthrough and this is the first time I have encountered the problem. Greetings!Thank you for contacting Bethesda Technical Support.
The issue you are experiencing may be related to PSN and/or Internet connectivity. Please make sure that you were signed into PSN and online when trying to run the game as it needs to validate the downloadable content. If for some reason this issue persists you will need to contact Sony support for your PS4 as the validation process is ran by them on their end and not an issue we can investigate.Warm Regards,
The Bethesda Technical Support Team. From what I can tell, I am signed in to PSN since I can access the store and see my trophies and friends online. When I signed out and signed back in, I did get a message about not being able to reconnect but it did eventually. I have done extensive searches on the web and I don't see anyone else having this issue.

I am having the same exact problem. I got this game from gamefly last week and it did it. I told gamefly they sent me an entirely different game and it still is hanging up at the validating dlc screen, a wheel just continues to spin and nothing happens. My interent is fine and I am connected to PSN as I too can see that my friends are onine.

Multiple cPCI Graphics cards - System Hangs during Boot

We have 2 Kontron dual output CP332 cPCI graphics cards to install into a NI PXI rack in order to give us 4 graphics outputs.
When one card is installed it acts as the Primary graphics card and it is required to disable to NI on-board graphics card in order for this to boot and function correctley.
If a 2nd Kontron CP322 card is added the system will hang during WinXP boot, as it switches from VGA to SVGA mode.
Disabling the 2nd card via device manager allows the system to boot.
Re-enabling the 2nd card once booted, then configuring with the ATI driver application allows the 4 graphics output to work as expected.
If the system is re-powered it will once again hang during WinXp booting.
Is there anything that can be configured on the NI Embedded PC (BIOS) to prevent this ?
Is there anything in windows that can be set to prevent this ?
Can we control the windows device manager from labview in order to enable/disable the 2nd card after power-on and before shutdown.
many thanks

Hi Scott,
I have some more information for you regarding your issue. We have tested the Kontron CP332 with the PXI-8196.
However when we tested the setup, we had 3 monitors working, the on-board graphics and the dual output from the card.
Until we get the on-board graphics working with a single CP332 I don't think we will get bot CP332's working.
So these are the steps to get on-board graphics working with a single Kontron card the steps come from talking to our PXI Product Support Engineer:
"The first thing you need to make sure is that you are using the
driver for Windows XP, and not the one for Windows 2000. Here's a link
to the driver download page:
http://us.kontron.com/index.php?searchword=cp+332&id=363
Notice that the first two driver downloads look just the same, but if
you hover over them and look at the url, you'll notice that the first
one is for Windows 2000 (w2k), and the second one is for Windows XP
(wxp). So, just make sure you are using the second one. The PSE did
mention that she was initially using the Win 2k driver, and was having
some issues with it hanging and all. Here's the information she sent me
about how she was able to get things working:
"Here is the info. My controller has BIOS version 1.3 but have him try this first before updating the BIOS.
The Kontron Board is the CP 332. I was able to get all three monitors working with the PXI-8196.
Configuration steps:
1) Insert both the controller and the kontron board in the chassis.
Note: When the computer is starting it will give you the Windows boot
up screen on the DVI 1 on the Kontron board and then give you the login
screen on the monitor connected to the 8196 so make sure you still have
a monitor connected to the controller.
2) Cancel the NI installation wizard if it comes up.
3)
Unzip the drivers and run the setup.exe file. Make sure you install
both the ATI display driver and the ATI Control Panel. (Check the zip
name to make sure you have the xp version of the driver)
4) After
restart go to the Display Properties and under the Settings tab you
should have monitors 1 and 2 on Mobility Radeon 9000 (Kontron CP-332)."
If you don't have BIOS version 1.20 or higher, please upgrade to BIOS version 1.30, if you need to upgrade the BIOS please make sure you fully understand the readme file. Then follow the steps above to enable triple output on the graphics cards.
When you have this working please try adding the second Kontron card.
Regards
JamesC
NIUK and Ireland

Arch Live CD x64 hanging during boot at "triggering uevents"

Hello!
I recently was recommended Arch by a friend, and after I followed the 'Newbies Guide' and burning a live CD to install Arch with, it appears to hang during Live CD boot at "installing uevents."
I am trying to install Arch as a dual boot on a late 2008 MacBook Pro which is currently running x64 Windows 7. I have plenty of HD space (100gb free and 100gb unallocated to install Arch onto).
Here is a picture:
http://i.imgur.com/Y8P41nf.jpg
I get the same error weather I try to install x64 or i686 (I think that's what it's called). Is there any reason for this?
Thank you!
-- mod edit: read the Forum Etiquette and only post thumbnails http://wiki.archlinux.org/index.php/For … s_and_Code --
(Sorry, missed that. My bad!)
Last edited by RalphORama (2013-09-07 03:09:13)

frank604 wrote:
You can try nomodeset. Seems to be a failure in loading a driver for your hardware. To read more on similar issues, there's a few posts with more info and suggestions by googling it.
Google result: http://lmgtfy.com/?q=halt+at+triggering+uevent
Results:
https://bbs.archlinux.org/viewtopic.php?id=151259
https://bbs.archlinux.org/viewtopic.php?id=140426
Thanks! I tried googling it myself but got mostly answers that didn't work. I'll try this!

Mac Mini keeps hanging during boot

My ~3 year old Mac Mini keeps freezing during booting with the error message "You need to restart your computer. Hold down the Power button...". This happens every time. Booting in safe mode works.
This happened with Mac OS X Tiger but keeps happening even after I have completely reformatted that hard disk and reinstalled Leopard from scratch. There are no external devices connected to the computer besides the monitor and a bluetooth mouse and keyboard.
After reading some discussion forums I have already tried starting into Open Bootware and running "reset-nvram" and "reset-all" but to no avail.

Welcome to Apple Discussions!
What you are suffering is a Kernel Panic, and given you have reformatted your drive and reinstalled MacOS, it would tend to suggest the issue is hardware related - most common culprit being RAM.
http://docs.info.apple.com/article.html?artnum=106227 explains what kernel panics are, and http://www.thexlab.com/faqs/kernelpanics.html and http://www.index-site.com/kernelpanic.html may give some assistance in working through the problem to determine the cause.
The one good thing is that your system appears sufficiently stable to allow you to boot to the Leopard installer and complete a full install. This makes it less likely there is a fundamental issue with the most expensive component of the system, the logic board.

OVM manager 3.0.3.546 locked up with message "Please wait while system is initializing"

Hi ,
I am receiving this message on any actions on OVM manager.
and AdminServer.log with this message
####<Aug 16, 2013 9:26:16 AM EST> <Warning> <com.oracle.ovm.mgr.model.ModelEngine> <serverneame> <AdminServer> <Odof Tcp Client Thread: /127.0.0.1:54321/101> <<anonymous>> <> <0000K24Ij5W5yWNLuIP5iX1I3MCB000002> <1376609176392> <BEA-000000> <Object 'null<500739>' got an unexpected rollback Lifecycle State.DELETING>
As soon as this message occur the discovery process is stopped and OVM manager lock up with the "Please wait while system is initializing" message.
any ideal?

Perform the following procedure to recover the management functionality OVM manager.
> 1) stop ovmm service
> # service ovmm stop
> 2) backup OVM3DB database
> # ovm_upgrade.sh --export --dbuser=ovs --dbpass=<ovspassword> --dbhost=<db host> --dbport=<db port> --dbsid=<sid/schema>
> 2) delete the database OVM3DB
> # ovm_upgrade.sh --deletedb --dbuser=ovs --dbpass=<ovspassword> --dbhost=<db host> --dbport=<db port> --dbsid=<sid/schema>
> 3) Restart ovmm service
> # service ovmm start
> 4) Login into the manager and re-discover your Servers and Repositories.
Back to business

My ipod Video won't switch on and always displays the message, "Please Wait Very Little Battery" despite being plugged into the charger.

Dear Apple Support Communities,
I am writing to inform you I have had my iPod for about 6 years now and it has slowly got to the stage where it no longer turns on. My iPod began freezing every now and then (for a few seconds now) and then this problem escalated to the stage where it began to freeze for days. I am now at the stage where it doesn't switch on at all, in fact everytime I try to switch on my iPod the following message appears on the screen, 'Please Wait, Very Little Battery' despite the fact that the iPod is currently being charged. I haven't used my iPod for months and was wondering if this promblem can be fixed or am I entitled to any upgrades.

Did you try to let it connected to USB for charging for a while before asking it anything. When the battery is deeply drained, it can occur that the iPod displays nothing for half an hour, just charging.
Also, make sure your PC gives sufficient power to the iPod for charging, I let mine once for six hours charging on my work's pc, and it didn't display "charged" message even after the 6H charge.
When an USB device is requiring more power than it can receive from the plug it is in, MacOSX advices it to user, It seems that Windows doesn't.

V570 hangs during boot up - message "please wait"

Similar Messages

Maybe you are looking for