Can't get into BIOS on K7N2G-ILSR 6570G

Yesterday I tried to get into the BIOS like I always had done, by pressing delete on start up. I tried numerous times, and for some reason, no luck. I then posted on techguy.org. Someone told me to get a BIOS flush utility from the MB manufact. I went to the website but couldn't find anything that looked like that. Can someone tell me what to look for, and why this may have happened in the first place.

I have spent the last 2 hrs with this computer. I finally tried a different keyboard after I had cleared CMOS and then it wouldn't let me press either del or F1. I was stuck, so changed keyboards and now everything is fine. I also managed to clean all the components and dust it out good while in there. Thanks for your help. I'm back in business!!

Similar Messages

Can't get into BIOS mode

** i also put this question in O.P. topic, because i think that was the wrong one**
1. Type of computer - HP ENVY dv7-7250nr
2. opporating system- windows 8 64bit
I recently got this computer. It's amazing the only thing that could use a change is the keyboard. I got this as a gaming PC but the function keys can only be accesed when pressing FN. In most computer games the f# keys are your shortcuts. When i go to press mine i have windows changed and the control panal pops up.
So i was looking around and they say you can go into BIOS mode and turn off the hotkeys. Only issue is i can't get into BIOS mode.
I would really appreciate some help on this, i don't want to go out and key a whole-nother keyboard.
Thank you in advance.

Princess.
Turn on the laptop then tap f10.
That should get you into the BIOS.
REO
HP Expert Tester "Now testing HP Pavilion 15t i3-4030U Win8.1, 6GB RAM and 750GB HDD"
Loaner Program”HP Split 13 x2 13r010dx i3-4012Y Win8.1, 4GB RAM and 500GB Hybrid HDD”
Microsoft Registered Refurbisher
Registered Microsoft Partner
Apple Certified Macintosh Technician Certification in progress.

Z68A-GD55 can't get into BIOS anymore

Just built new Z68 computer gradually over 3 days. Then loaded applications and everything worked great for 2 days. Decided it was done and time to change boot priority in BIOS. Couldn’t get into BIOS. Got splash screen but no further.
Found forum message recommending CMOS reset. Tried button, jumper, remove battery methods. Still can’t get into BIOS. Get BIOS Prompt ("...press DELETE"), but nothing after that except flashing cursor top left of screen. Back to barebones; same result. Screen messages before BIOS prompt: 98, 99, A3. Will not boot MS DOS (Win98 version) from USB drive (would before). I’d appreciate any suggestions. Thx.
Key build steps:
• Ran Memtest barebones 48 hrs.
• Added SSD (ACHI) and Installed Windows 7 Pro. SSD was new.
• Added, formatted HDD
• Enabled multi-monitor in BIOS; added Radeon HD6870; 2 monitors on Radeon, none on internal; installed Radeon drivers.
• Enabled Virtu in BIOS, d-mode; Installed Virtu
Not overclocked.

After replacing the PSU with a Corsair TX650M (650w, 3.3v30A, 5v30A, 12V54A), the barebones config could access the BIOS. Installed everything except boot SSD; still OK.
Before letting the computer boot back into Win7, I connected two old 19" LCD monitors (Microtek C997SD). For setup and testing, I had been using a 24" widescreen. But Win7 had never seen anything but the Microteks, which I intend to use with this computer. Tried to enter BIOS to verify settings were still correct for SSD. Got splash screen -- regular BIOS background, but no Icons (Green Power, Utilities, Overclocking, etc.). Computer locks: PS/2 keyboard (incl. Ctrl-Alt-Del) and USB mouse, do nothing.
Connected widescreen, verified BIOS OK. Shut down and reconnected Microteks, attempted boot into Win7, and all was OK. I just can't use a Microtek to access BIOS.
I hope MSI recognizes how valuable the volunteers here are. Your advice solved the problem at least a couple of days earlier than I would have done on my own. Thank you.

MSI 870-G45 - Can't get into BIOS

So, just built myself a new pc.
It posts, and I have some output on the screen upon boot up, like I see that its detecting my sata hd/dvd drive and everything. Like the topic name says, I can't get into the BIOS. When it posts, its detecting my keyboard and everything, but it simply hangs at the post screen and I cannot get into the BIOS at all for whatever reason that is beyond me. I've tried 2 keyboards, one ps/2 and a usb keyboard, nothing on either (the usb is one I went to wal-mart and got today as I guessed the ps/2 wasn't working correctly or whatever).
Tried clearing CMOS (taking out the battery, resetting the jumper and everything). Still got nothing.
Heres a link to a pic of what output I do have. http://img858.imageshack.us/i/img20110313152042.jpg/ (sorry, don't know how to embed pics into a forum board, not that familiar)

Quote from: littlemanx23 on 14-March-11, 13:10:00
I mean, I'm using a usb keyboard. Should I try a PS/2? I mean I've tried clearing the CMOS a handful of times to no avail, nothing. It just simply hangs at that screen and says CMOS settings are wrong.
I thought you said you'd already tried a PS/2 keyboard and it still hangs?

Can't Get Into Bios.

Hello:
After putting together a new system and installing windows I ran MSI's update util. The first thing I updated was the bios. I did a windows flash. It made the recovery disk and flashed the bios. The machine would not boot after this and I followed the recovery process. Now I can't get into the bios. After the first beep when posting I hit and the machine just hangs. I'm really not sure how stable my system is now. After the recovery I ran the update util again and tried to install some Intel Inf files and after copying 90% the machine hung. I was thinking about re-flashing and re-installing windows.
Thanks In Advance,
Steve Dessent.

Can you post the details on your setup - board, video card, power supply, etc.
And can you clarify where you know stand. If I understand this you flashed to a new bios version, were unable to boot, and you restored the old bios, and are able to boot. Have you gone into the bios to make changes since recovering?

Laptop won't boot, can't get into BIOS.

I have a Satellite P55t-A5116, with windows 8.1. The other day I went into the Toshiba password utility and set a user password, and when the machine reboots, nothing happens. No sign in screen, no place to enter the password, nothing. I cannot get into the BIOS, having tried holding down the ESC, F2, F8, and F12 keys. I also tried holding down the Fn key plus the F2, F8, and F12 keys. I have tried to boot with my Toshiba System recovery disc ( that might be a windows 8 disc, I made it when I got the laptop in March), or an Unbuntu disc. Below is a screenshot of what I get when the machine starts. Did the BIOS get corrupted when I entered the password? If I pop out the CMOS battery, will that fix it? Any help and suggestions is much appreciated.
Attachments:
image.jpg ‏966 KB

I'm not sure how setting the password would cause this. You might want to try these suggestions:
What can I do if my Windows 8 laptop won't start?
- Peter

Can't get into BIOS on new Z97M-G43 Mobo

I just received all the components (below) for a new build. When I power the system up, I get a screen with the following:
EFI Shell Version 2.31 [4.633]
Current running mode 1.1.2 Map: Cannot find required map name
Press Esc in 5 seconds to skip startup.nsh, any other key to continue
Regardless of what I do, I cannot get into the BIOS. I have tried clearing the CMOS using the procedures documented here on the forum - both removing the CMOS battery and by using the jumper, both with the power off.
I removed all non-necessary connections - USB, HDD, DVD. The only things connected are power and the front panel power, reset and LED.
When I remove 2 of the 4 memory modules and restart, I get a message saying that the CPU or memory changed and to press F1 to go into setup. When I press F1, I only get a black screen. I also get a black screen if I press DEL repeatedly after turning on the system.
I am using a HDMI connection to my monitor.
What is the magic to get into the BIOS, or does this suggest something is wrong with the Mobo?
Many thanks!

Quote
Regardless of what I do, I cannot get into the BIOS. I have tried clearing the CMOS using the procedures documented here on the forum - both removing the CMOS battery and by using the jumper, both with the power off.
remove power cord from the PSU 1st
then do >>Clear CMOS Guide<< and retest
Quote
MEM: GSkill 4x4gb F3-14900CL9D-8GBXL
also try with 1 memory stick only

MSI GE70 2OE Can't get into bios after update

Hello
I had some problems with the intel turbo boost not working properly so I updated my bios with the new version from 2013-09-03. After this update the intel turbo boost works fine but since I can't access my bios anymore. Does anyone have a solution?
Thanks

Problem solved. It seems that after the update you have less time to press delete to enter the bios.

ThinkPad E330 can't get into BIOS anymore

I tried to install Ubuntu on a Thinkpad E330 that had Windows 8 preinstalled, from a USB key. It was a 32 bits version of Ubuntu, just for a trial. I accessed the EFI bios from W8, shifted to legacy BIOS mode and installed Ubuntu w/o any problem, on a set of separate partitions. Works like a charm (although I would like to shift to 64 bits).
The problem is that I would now like to go back to EFI mode to access W8 and install a 64 bits version of Ubuntu for EFI but I cannot access the BIOS anymore to put it back to EFI mode. Although the screen says "press F1 key to enter BIOS" or "Press Enter to interuupt normal boot process", the F1 Key does not work, the Enter key does no better.
I found plenty of posts of people in a similar situation, that tried to clear CMOS (does not work) and all ultimately point to the user "someotherguy" that apparently saved them. I tried to pm him but he does not react to my private messages.
Is there anybody else that could help me here ?
Thanks
Thomas
Solved!
Go to Solution.

For those who like me could not access their BIOS because they put it in Legacy mode:
I must first thank someotherguy for his help.
After different trials, the success was reached by opening the thinkpad (3 little screws) and the CMOS battery. The reboot gave me access to the BIOS and I shifted it back to UEFI mode and thus regained access to Windows 8 (and therefore to the BIOS again).
I will now proceed with Ubuntu installation...in UEFI mode (as I intended initially but did not do because I has a 32 bit version of ubuntu already on a USB key).
Thomas

Dv9000 series - how to get into BIOS

How can I get into BIOS and how can I re-dedicate graphics memory-use there? (Maybe my other's post was too special...)

Oh, THAT's interesting to learn that chances are high, they either changed the whole mobo, or the system wouldn't run stable with damaged graphics memory...(An ugly one: would it be worth exchanging the mobo and do all that counterfeiting data just for the value of the old mobo???) Here's what I found so far: (I used "SIW System Information for Windows"-tool to get the following data, among a lot of other)- Serial-# matches my serial-# as per the original packaging, paperwork and bottom of the machine- Model 103C_5335KV (another way to denote the model KP964EA/dv9787eg?)- NVIDIA 8600M GS with (only) 256MB DDR2 64bits- dedicated video memory 239MB (251199488)- dedicated system memory 0MB- shared system memory 1279MB (1341353984)- Mobo is a Quanta 30CB 79.2E (no serial-# found/supplied by SIW!) I will check the hardware again by "reading out" data with Fn+Esc and/or CPUZ and GPUZ and report back (as said, I think the info there said KP964EA already - just to make sure)... Just for the guessing or "narrowing the problem down":IF my system was running on 256MB before already (and hp advertised wrong data for my rig) - so no change there - what else might cause my games running roughly now and be a reason for the dropped performance-index in windows?Possible that the graphics chip is able to perform with 256MB only and I would need another version of the 8600M GS which IS able to make use of the 512? (Guess no, as the above info TELLS me that there is only 256MB - and no 512MB - available, right?)CAN that be related to some software or driver?Would/might setting up windows anew (or changing from Vista to 7 for that matter) might bring me back to speed? Anyway, let me tell you that I VERY much appreciate your help on this - I am kind of lost on my own here, and I will try whatever I can to get back my "old" great-performing machine.

Can no longer get into BIOS, always goes to system diagnostics

After changing some settings in BIOS the system won't boot anymore.
But the real problem is that I can not get into the BIOS anymore. When started the system goes straight to System Diagnostics.
When I continue I get the message:
BootDevice Not Found
Please install an operating system on your hard disk.
Hard Disk - (3F0)
When I go to the startup menu and try to enter Boot Device Options(F9) or Bios Setup(F10) it still takes me to System Diagnostics.
The system passes all system diagnostic tests.
I don't understand why I can't get into the BIOS anymore, this should always be possible right? How can I fix this?
Any help is greatly appreciated.

@WB__
‎Thank you for using HP Support Forum. I have brought your issue to the appropriate team within HP. They will likely request information from you in order to look up your case details or product serial number. Please look for a private message from an identified HP contact. Additionally, keep in mind not to publicly post ( serial numbers and case details).
If you are unfamiliar with the Forum's private messaging please click here to learn more.
Thank you,
Omar
I Work for HP

Now RAID BIOS Hangs-Can't get into it!!

Folks - On a new build, the BIOS (v1.6) on my Neo4-F worked fine. I was trying to get Windows to not lose missing nt___ files. I kept deleting arrays and trying new array configs, reloading windows (yes, loading the RAID drivers with F6), but Windows still wouldn't load due to missing dll's. Now when I set the RAID SATA settings in the BIOS, save & exit, on the reload it hangs at the Nvidia RAID ROM BIOS screen "Detecting array..." and won't go any further. So I have to power down, reset the CMOS to get the BIOS back. If I go in and reset the SATA RAID drives, it'll do the same thing, otherwise if I don't set the RAID, it'll go on to load Windows as normal. What happened and how can I get into the RAID BIOS again??? Thanks

Try having just one connected and boot . (do a cmos clear also ) .
You can also leave the drive powered , and just insert/remove the sata cable when system is running .
Just don't plug/unplug the HDs power connector while system is powered on.
Sometimes the raid hangs if the drive order has been reversed (the raid mirror is confused whats drive #1) .So you should also try switching the drives on the connected sata ports .

I can't get to BIOS if internal HD is plugged in

W520 running BIOS version 1.35
If I remove the hard drive, I can get into the BIOS just fine (I am talking about the internal HD, Intel 320). I wanted to change the boot order. However it makes no difference once I reconnect the hard drive, it wants the hard drive password first, won't let me boot from anything else or get to the BIOS, and I've either forgotten it (honestly I never had it set to my knowledge, only had a Supervisor password, but now I am getting prompted for a HD password after Windows froze and I had to force shut down while plugged into Ethernet cable; I think some Wake On LAN settings caused a BIOS bug to occur or something because it changed my boot order and tried to PXE boot... can't understand it, no PXE environment on my LAN, it's just a regular router).
It seems like the BIOS is actually stored on the hard drive? (And since when is BIOS stored on hard drive?!?) Is there any way I can actually get into the BIOS with my hard drive connected? What is going on here?
I'm trying to boot from USB so I can run a disk utility and check the SMART status on the Intel 320 SSD. I believe I'm deal with a BIOS bug even though Lenovo refuses to acknowledge or look into it. All I can think to try is make sure the disk is not faulty.
I've also tried flashing the BIOS but it seems to make no difference... if the hard disk is connected it won't boot from any other media, and if the hard disk isn't connected, it doesn't seem to actually flash the BIOS as the version never changes from 1.35.
Solved!
Go to Solution.

The drive pw is needed at power up, whether you boot into the bios or an os. It is not needed on a restart, assuming it was entered at power up.

How to get into BIOS in Windows 8

my question is this will the same fan control software that was on windows seven 64 bit lenova work with windows 8 and 8.1 just wondering if i have to uninstall before i upgrade or will it be compatable with 8 and 8.1 upgrade hope someone can steer me in the right direction here it would be appreciated-thanks

Hi,
follow the links below:
http://forums.lenovo.com/t5/Windows-8-and-8-1-Knowledge-Base/How-to-get-into-BIOS-in-Windows-8/ta-p/...
http://support.lenovo.com/en_US/detail.page?DocID=HT076607
win8 should be installed on the big HDD.
If you have enough computing skills Win8.1 Update could be installed on the small SSD using the new feature - WimBOOT.
x220 | i5-2520m | Intel ssd 320 series | Gobi 2000 3G GPS | WiFi
x220 | i5-2520m | hdd 320 | Intel msata ssd 310 series | 3G GPS | WiFi
Do it well, worse becomes itself
Русскоязычное Сообщество English Community Deutsche Community Comunidad en Español

Just updated, can't get into X or console [Solved]

So yeah, as the title says.
Can't remember exactly what was updated but there was definitely a kernel update in there. The system boots fine until it goes to start X, then i just get a blank screen. No keyboard working, so i can't get into a console.
Any ideas? Live cd maybe?
Last edited by Mountainjew (2011-06-09 22:37:14)

Ok i think i found the problem...But i dunno why all of a sudden my ATi card wouldn't be picked up, unless it has to do with the new method of blacklisting?
Slim.log
slim: waiting for X server to begin accepting connections
X.Org X Server 1.10.2
Release Date: 2011-05-28
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.38-ARCH x86_64
Current Operating System: Linux arch 2.6.38-ARCH #1 SMP PREEMPT Mon Jun 6 22:49:29 CEST 2011 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz26 root=/dev/disk/by-uuid/b09f0621-97f9-4226-b572-338c215b1d68 ro nomodeset init=/sbin/e4rat-preload
Build Date: 30 May 2011 08:18:15AM
Current version of pixman: 0.22.0
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: Thu Jun 9 22:06:00 2011
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using config directory: "/etc/X11/xorg.conf.d"
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:17:0) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:18:0) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:18:2) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:19:0) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:19:2) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:0) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:1) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:3) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:4) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:5) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:21:0) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:21:1) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:22:0) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:22:2) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@1:0:1) found
Giving up.
slim: unable to connect to X server
Xorg.0.log
[ 16.825]
X.Org X Server 1.10.2
Release Date: 2011-05-28
[ 16.825] X Protocol Version 11, Revision 0
[ 16.825] Build Operating System: Linux 2.6.38-ARCH x86_64
[ 16.825] Current Operating System: Linux arch 2.6.38-ARCH #1 SMP PREEMPT Mon Jun 6 22:49:29 CEST 2011 x86_64
[ 16.825] Kernel command line: BOOT_IMAGE=/boot/vmlinuz26 root=/dev/disk/by-uuid/b09f0621-97f9-4226-b572-338c215b1d68 ro nomodeset init=/sbin/e4rat-preload
[ 16.825] Build Date: 30 May 2011 08:18:15AM
[ 16.825]
[ 16.825] Current version of pixman: 0.22.0
[ 16.825] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 16.825] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 16.825] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Jun 9 22:06:00 2011
[ 16.825] (==) Using config file: "/etc/X11/xorg.conf"
[ 16.825] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 16.832] (==) ServerLayout "aticonfig Layout"
[ 16.832] (**) |-->Screen "aticonfig-Screen[0]-0" (0)
[ 16.832] (**) | |-->Monitor "aticonfig-Monitor[0]-0"
[ 16.832] (**) | |-->Device "aticonfig-Device[0]-0"
[ 16.832] (==) Automatically adding devices
[ 16.832] (==) Automatically enabling devices
[ 16.832] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 16.832] Entry deleted from font path.
[ 16.833] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/Type1/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/75dpi/
[ 16.833] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 16.833] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 16.833] (II) Loader magic: 0x7d3440
[ 16.833] (II) Module ABI versions:
[ 16.833] X.Org ANSI C Emulation: 0.4
[ 16.833] X.Org Video Driver: 10.0
[ 16.833] X.Org XInput driver : 12.2
[ 16.833] X.Org Server Extension : 5.0
[ 16.834] (--) PCI:*(0:1:0:0) 1002:6899:1787:2290 rev 0, Mem @ 0xd0000000/268435456, 0xfe6e0000/131072, I/O @ 0x0000a000/256, BIOS @ 0x????????/131072
[ 16.834] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 16.834] (II) "extmod" will be loaded by default.
[ 16.834] (II) "dbe" will be loaded by default.
[ 16.834] (II) "glx" will be loaded by default.
[ 16.834] (II) "record" will be loaded by default.
[ 16.834] (II) "dri" will be loaded by default.
[ 16.834] (II) "dri2" will be loaded by default.
[ 16.834] (II) LoadModule: "extmod"
[ 16.834] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
[ 16.834] (II) Module extmod: vendor="X.Org Foundation"
[ 16.834] compiled for 1.10.2, module version = 1.0.0
[ 16.834] Module class: X.Org Server Extension
[ 16.834] ABI class: X.Org Server Extension, version 5.0
[ 16.834] (II) Loading extension MIT-SCREEN-SAVER
[ 16.834] (II) Loading extension XFree86-VidModeExtension
[ 16.834] (II) Loading extension XFree86-DGA
[ 16.834] (II) Loading extension DPMS
[ 16.834] (II) Loading extension XVideo
[ 16.834] (II) Loading extension XVideo-MotionCompensation
[ 16.834] (II) Loading extension X-Resource
[ 16.834] (II) LoadModule: "dbe"
[ 16.835] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
[ 16.835] (II) Module dbe: vendor="X.Org Foundation"
[ 16.835] compiled for 1.10.2, module version = 1.0.0
[ 16.835] Module class: X.Org Server Extension
[ 16.835] ABI class: X.Org Server Extension, version 5.0
[ 16.835] (II) Loading extension DOUBLE-BUFFER
[ 16.835] (II) LoadModule: "glx"
[ 16.835] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 16.835] (II) Module glx: vendor="FireGL - ATI Technologies Inc."
[ 16.835] compiled for 6.9.0, module version = 1.0.0
[ 16.835] (II) Loading extension GLX
[ 16.835] (II) LoadModule: "record"
[ 16.835] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
[ 16.835] (II) Module record: vendor="X.Org Foundation"
[ 16.835] compiled for 1.10.2, module version = 1.13.0
[ 16.835] Module class: X.Org Server Extension
[ 16.836] ABI class: X.Org Server Extension, version 5.0
[ 16.836] (II) Loading extension RECORD
[ 16.836] (II) LoadModule: "dri"
[ 16.836] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[ 16.836] (II) Module dri: vendor="X.Org Foundation"
[ 16.836] compiled for 1.10.2, module version = 1.0.0
[ 16.836] ABI class: X.Org Server Extension, version 5.0
[ 16.836] (II) Loading extension XFree86-DRI
[ 16.836] (II) LoadModule: "dri2"
[ 16.836] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 16.836] (II) Module dri2: vendor="X.Org Foundation"
[ 16.836] compiled for 1.10.2, module version = 1.2.0
[ 16.836] ABI class: X.Org Server Extension, version 5.0
[ 16.836] (II) Loading extension DRI2
[ 16.836] (II) LoadModule: "fglrx"
[ 16.846] (II) Loading /usr/lib/xorg/modules/drivers/fglrx_drv.so
[ 16.861] (II) Module fglrx: vendor="FireGL - ATI Technologies Inc."
[ 16.861] compiled for 1.4.99.906, module version = 8.85.6
[ 16.861] Module class: X.Org Video Driver
[ 16.861] (II) Loading sub module "fglrxdrm"
[ 16.861] (II) LoadModule: "fglrxdrm"
[ 16.861] (II) Loading /usr/lib/xorg/modules/linux/libfglrxdrm.so
[ 16.861] (II) Module fglrxdrm: vendor="FireGL - ATI Technologies Inc."
[ 16.861] compiled for 1.4.99.906, module version = 8.85.6
[ 16.861] (II) ATI Proprietary Linux Driver Version Identifier:8.85.6
[ 16.861] (II) ATI Proprietary Linux Driver Release Identifier: 8.85
[ 16.861] (II) ATI Proprietary Linux Driver Build Date: Apr 19 2011 21:30:04
[ 16.861] (++) using VT number 7
[ 16.866] (WW) Falling back to old probe method for fglrx
[ 16.884] (II) Loading PCS database from /etc/ati/amdpcsdb
[ 16.885] (--) Chipset Supported AMD Graphics Processor (0x6899) found
[ 16.885] (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:17:0) found
[ 16.885] (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:18:0) found
[ 16.885] (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:18:2) found
[ 16.885] (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:19:0) found
[ 16.885] (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:19:2) found
[ 16.885] (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:0) found
[ 16.885] (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:1) found
[ 16.885] (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:3) found
[ 16.885] (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:4) found
[ 16.885] (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:5) found
[ 16.885] (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:21:0) found
[ 16.885] (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:21:1) found
[ 16.885] (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:22:0) found
[ 16.885] (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:22:2) found
[ 16.886] (WW) fglrx: No matching Device section for instance (BusID PCI:0@1:0:1) found
[ 16.886] (II) AMD Video driver is running on a device belonging to a group targeted for this release
[ 16.886] (II) AMD Video driver is signed
[ 16.886] (II) Loading /usr/lib/xorg/modules/drivers/fglrx_drv.so
[ 16.886] (II) Loading /usr/lib/xorg/modules/linux/libfglrxdrm.so
[ 16.886] (II) fglrx(0): pEnt->device->identifier=0x23a7500
[ 16.886] (II) fglrx(0): === [xdl_xs110_atiddxPreInit] === begin
[ 16.886] (II) Loading sub module "vgahw"
[ 16.886] (II) LoadModule: "vgahw"
[ 16.886] (II) Loading /usr/lib/xorg/modules/libvgahw.so
[ 16.886] (II) Module vgahw: vendor="X.Org Foundation"
[ 16.886] compiled for 1.10.2, module version = 0.1.0
[ 16.886] ABI class: X.Org Video Driver, version 10.0
[ 16.886] (**) fglrx(0): Depth 24, (--) framebuffer bpp 32
[ 16.886] (II) fglrx(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
[ 16.886] (==) fglrx(0): Default visual is TrueColor
[ 16.886] (**) fglrx(0): Option "DPMS" "true"
[ 16.886] (==) fglrx(0): RGB weight 888
[ 16.887] (II) fglrx(0): Using 8 bits per RGB
[ 16.887] (==) fglrx(0): Buffer Tiling is ON
[ 16.887] (II) Loading sub module "fglrxdrm"
[ 16.887] (II) LoadModule: "fglrxdrm"
[ 16.887] (II) Loading /usr/lib/xorg/modules/linux/libfglrxdrm.so
[ 16.887] (II) Module fglrxdrm: vendor="FireGL - ATI Technologies Inc."
[ 16.887] compiled for 1.4.99.906, module version = 8.85.6
[ 16.888] ukiDynamicMajor: found major device number 252
[ 16.888] ukiDynamicMajor: found major device number 252
[ 16.888] ukiOpenByBusid: Searching for BusID PCI:1:0:0
[ 16.888] ukiOpenDevice: node name is /dev/ati/card0
pacman.log
[2011-06-09 15:07] upgraded udev (171-1 -> 171-2)
[2011-06-09 15:07] upgraded iproute2 (2.6.37-1 -> 2.6.38-3)
[2011-06-09 15:07] warning: /etc/rc.conf installed as /etc/rc.conf.pacnew
[2011-06-09 15:07] Blacklisting of modules is no longer supported in rc.conf,
[2011-06-09 15:07] please add blacklist entries to /etc/modprobe.d/ instead.
[2011-06-09 15:07] upgraded initscripts (2011.05.2-1 -> 2011.06.3-1)
[2011-06-09 15:07] upgraded inputproto (2.0.1-1 -> 2.0.2-1)
[2011-06-09 15:07] >>> Updating module dependencies. Please wait ...
[2011-06-09 15:07] >>> MKINITCPIO SETUP
[2011-06-09 15:07] >>> ----------------
[2011-06-09 15:07] >>> If you use LVM2, Encrypted root or software RAID,
[2011-06-09 15:07] >>> Ensure you enable support in /etc/mkinitcpio.conf .
[2011-06-09 15:07] >>> More information about mkinitcpio setup can be found here:
[2011-06-09 15:07] >>> http://wiki.archlinux.org/index.php/Mkinitcpio
[2011-06-09 15:07]
[2011-06-09 15:07] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2011-06-09 15:07] ==> Building image "default"
[2011-06-09 15:07] ==> Running command: /sbin/mkinitcpio -k 2.6.38-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img
[2011-06-09 15:07] :: Begin build
[2011-06-09 15:07] :: Parsing hook [base]
[2011-06-09 15:07] :: Parsing hook [udev]
[2011-06-09 15:07] :: Parsing hook [v86d]
[2011-06-09 15:07] :: Parsing hook [autodetect]
[2011-06-09 15:07] :: Parsing hook [pata]
[2011-06-09 15:07] :: Parsing hook [scsi]
[2011-06-09 15:07] :: Parsing hook [sata]
[2011-06-09 15:07] :: Parsing hook [filesystems]
[2011-06-09 15:07] :: Generating module dependencies
[2011-06-09 15:07] :: Generating image '/boot/kernel26.img'...SUCCESS
[2011-06-09 15:07] ==> SUCCESS
[2011-06-09 15:07] ==> Building image "fallback"
[2011-06-09 15:07] ==> Running command: /sbin/mkinitcpio -k 2.6.38-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26-fallback.img -S autodetect
[2011-06-09 15:07] :: Begin build
[2011-06-09 15:07] :: Parsing hook [base]
[2011-06-09 15:07] :: Parsing hook [udev]
[2011-06-09 15:07] :: Parsing hook [v86d]
[2011-06-09 15:07] :: Parsing hook [pata]
[2011-06-09 15:07] :: Parsing hook [scsi]
[2011-06-09 15:07] :: Parsing hook [sata]
[2011-06-09 15:07] :: Parsing hook [filesystems]
[2011-06-09 15:07] :: Generating module dependencies
[2011-06-09 15:07] :: Generating image '/boot/kernel26-fallback.img'...SUCCESS
[2011-06-09 15:07] ==> SUCCESS
[2011-06-09 15:07] upgraded kernel26 (2.6.38.7-1 -> 2.6.38.8-1)
[2011-06-09 15:08] upgraded kernel26-headers (2.6.38.7-1 -> 2.6.38.8-1)
[2011-06-09 15:08] upgraded net-tools (1.60-14 -> 1.60-16)
[2011-06-09 15:08] upgraded qt (4.7.3-2 -> 4.7.3-3)
[2011-06-09 15:40] Running '/usr/bin/pacman-color -Syu'
[2011-06-09 15:40] synchronizing package lists
[2011-06-09 15:40] starting full system upgrade
[2011-06-09 15:43] Running '/usr/bin/pacman-color -U bluegriffon-1.1-1-x86_64.pkg.tar.xz'
[2011-06-09 15:43] upgraded bluegriffon (1.0-1 -> 1.1-1)
[2011-06-09 15:43] Running '/usr/bin/pacman-color -U sublime-text-2-v2059-2-x86_64.pkg.tar.xz'
[2011-06-09 15:43] upgraded sublime-text-2 (v2059-1 -> v2059-2)
[2011-06-09 15:47] Running 'pacman -S virtualbox-guest-additions'

Can't get into BIOS on K7N2G-ILSR 6570G

Similar Messages

Maybe you are looking for