Problemas Bios Boot Z5070

Hola. Me compré solo hace dos meses un Z5070 y no lo he usado demasiado intensivamente pero ayer mientras navegaba por internet se bloqueo y tras dar a Ctrl Alt Supr surgió la pantalla azul con la cara triste de Windows 8.1 haciendo referencia a un problema kernel (no recuerdo el resto) y era necesario reiniciar sistema para lo cual guardaría datos para luego enviar informe . Tras un largo rato reiniciándose con algún ruido extraño tuve que apagar porque no hacia nada. A partir de ahí, al iniciar el ordenador se quedaba en la pantalla de lenovo y empezaron a salir las siguientes pantallas
EFI network 0 for IPv4 (68-F7-28-05-70-E0)
EFI network 0 for IPv6 (68-F7-28-05-70-E0)
Default Boot Device Missing or Boot Failed
Insert Recovery Media and hit any key
Then select Boot Manager to choose a new Boot device or to Boot Recovery Media
Tengo fotos de las pantallas que podría enviar si es preciso.
Me gustaría saber qué hacer y si el posible problema lo cubre la garantía. También me gustaría saber si hay alguna solución sin perder los datos de estos últimos días.
Gracias

Así es como comentas seria el primer paso , la idea de cargar los valores por defecto de la BIOS es para ver que en la cargar del orden de dispositivos este en lo correcto, disco duro al inicio.
Si el error es asociado a esto deberá cargar Windows, si carga pero con errores del sistema operativo debes ingresar al recovery con esto verificas también problemas del disco duro, si carga normalmente puedes descartar esto ultimo.
Si carga no utilizarla porque un recovery del sistema elimina todo en C a no ser que no sea de gran importancia o que tengas en C, si necesitas tu información debes acceder a ella por otros medios por ejemplo a través de un sistema Linux en modo Live (no se instala) si el disco duro es el problema y que que el sistema no lo reconoce lo de rescatar la información o aplicar lo antes comentado no servirá, en ese caso debes contactar al centro llamadas Lenovo números al final en mi firma.
Un saludo.

Similar Messages

  • P35Neo2 FIR and problem with booting

    So I have problem with booting my compie. Compie try to boot to the part of start windows, after that in case of switch into graphicis mobo going down and restarting (WinXP SP3). I think, that problem is not in PSU, cos i have 800W XILENCE (+3,3V 28A, +5V 32A, 4x+12V 20A, -12V 0,5A, 5VSB 3A), Board P35 Neo2 FIR, E7200 proc, bios 1.9 (updated). I have 5 disk and use raid function in bios. Graphic Radeon HD3650, Memory Zeppelin 4x1GB KIT 800Mhz.
    I start with change of PSU from 550W to 800W but it didnt work, previus PSU had (+3,3V 30A, +5V 32A, 2x+12V 18A, -12V 0,8A, 5VSB 3A),
    i try change memory, but no efect.
    After update bios there was standard warning about bad cheksum, after resave Bios settings it was gone, and compie boot after that.
    Any idea?
    Thanks

    So my problem is solved...but my feeling of this is not good...
    I updated BIOS from 1.9 to 1.10, reset Bios settings, after restart i pressed F2 for load standart settings and i changed in Bios only that i am using RAID and disable disket and it works...i boot my compie into windows without any problem...
    So i try change another things in Bios and my compie hangs in continous resets without booting into windows...no BSOD only restart and restart...
    After reseting Bios settings and again Load to Default it works...and run windows...
    There was only one new thing ... screen flick for the second with new screen about checking NVRAM ....this screen was not visible before (and maybe this is the problem), cos if i change something in BIOS about clocking and power management and other ones, this screen is by booting missing...and compie not run in Windows...
    Next thing what i see, that in CPU multiplication dont work multiplication 9,5 and proc used frequency 2400 (9x) (it is E7200 on 2533)
    i hope that this bios 1.10 fixed my problems...and my opinion is that P35 Neo 2 FIR is not ideal board for E7200 proc...so i m looking for another proc...and maybe another board...

  • Problem with boot / new install system ond SSD

    Hi guys,
    I have fresh installed system on my new SSD. I use my old HDD as external usb drive.
    I have problem with boot when I dont have connected HDD to usb.
    My system boot only to console no to KDE. When I connect external HDD to usb and reboot system, system boot normally.
    Logs after boot.
    Feb 26 16:46:39 arch systemd[1]: Reached target Login Prompts.
    Feb 26 16:46:39 arch systemd[1]: Starting K Display Manager...
    Feb 26 16:46:39 arch systemd[1]: Started K Display Manager.
    Feb 26 16:46:39 arch systemd-logind[231]: New seat seat0.
    Feb 26 16:46:39 arch systemd[1]: Started Login Service.
    Feb 26 16:46:40 arch kernel: microcode: CPU0 sig=0x1067a, pf=0x80, revision=0xa07
    Feb 26 16:46:40 arch kernel: platform microcode: Direct firmware load failed with error -2
    Feb 26 16:46:40 arch kernel: platform microcode: Falling back to user helper
    Feb 26 16:46:40 arch kernel: random: nonblocking pool is initialized
    Feb 26 16:46:40 arch kernel: uvcvideo: Found UVC 1.00 device CNF7129 (04f2:b071)
    Feb 26 16:46:40 arch laptop-mode[271]: enabled, not active
    Feb 26 16:46:40 arch kernel: input: CNF7129 as /devices/pci0000:00/0000:00:1a.7/usb3/3-3/3-3:1.0/input/input16
    Feb 26 16:46:40 arch kernel: usbcore: registered new interface driver uvcvideo
    Feb 26 16:46:40 arch kernel: USB Video Class driver (1.1.1)
    Feb 26 16:46:40 arch systemd[1]: Started Wicd a wireless and wired network manager for Linux.
    Feb 26 16:46:40 arch systemd[1]: Starting Network.
    Feb 26 16:46:40 arch systemd[1]: Reached target Network.
    Feb 26 16:46:40 arch systemd[1]: Starting OpenSSH Daemon...
    Feb 26 16:46:40 arch systemd[1]: Started OpenSSH Daemon.
    Feb 26 16:46:40 arch systemd[1]: Starting NoMachine Server daemon...
    Feb 26 16:46:40 arch sshd[373]: Server listening on 0.0.0.0 port 22.
    Feb 26 16:46:40 arch sshd[373]: Server listening on :: port 22.
    Feb 26 16:46:40 arch mtp-probe[404]: checking bus 7, device 2: "/sys/devices/pci0000:00/0000:00:1d.1/usb7/7-2"
    Feb 26 16:46:40 arch mtp-probe[404]: bus: 7, device: 2 was not an MTP device
    Feb 26 16:46:40 arch kernel: hidraw: raw HID events driver (C) Jiri Kosina
    Feb 26 16:46:40 arch kernel: usbcore: registered new interface driver usbhid
    Feb 26 16:46:40 arch kernel: usbhid: USB HID core driver
    Feb 26 16:46:40 arch systemd[1]: Starting Sound Card.
    Feb 26 16:46:40 arch systemd[1]: Reached target Sound Card.
    Feb 26 16:46:40 arch systemd-udevd[145]: renamed network interface eth0 to enp3s0
    Feb 26 16:46:40 arch kernel: psmouse serio4: elantech: assuming hardware version 2 (with firmware version 0x040101)
    Feb 26 16:46:40 arch kernel: psmouse serio4: elantech: Synaptics capabilities query result 0x7e, 0x13, 0x0d.
    Feb 26 16:46:40 arch kernel: i915 0000:00:02.0: irq 45 for MSI/MSI-X
    Feb 26 16:46:40 arch kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
    Feb 26 16:46:40 arch kernel: [drm] Driver supports precise vblank timestamp query.
    Feb 26 16:46:40 arch kernel: vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
    Feb 26 16:46:40 arch kernel: iTCO_vendor_support: vendor-support=0
    Feb 26 16:46:40 arch kernel: iTCO_wdt: Intel TCO WatchDog Timer Driver v1.10
    Feb 26 16:46:40 arch kernel: iTCO_wdt: Found a ICH9M TCO device (Version=2, TCOBASE=0x0860)
    Feb 26 16:46:40 arch kernel: iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
    Feb 26 16:46:40 arch kernel: input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio4/input/input15
    Feb 26 16:46:40 arch systemd-logind[231]: Watching system buttons on /dev/input/event2 (Lid Switch)
    Feb 26 16:46:40 arch systemd-logind[231]: Watching system buttons on /dev/input/event1 (Sleep Button)
    Feb 26 16:46:40 arch systemd-logind[231]: Watching system buttons on /dev/input/event3 (Power Button)
    Feb 26 16:46:41 arch kernel: microcode: CPU1 sig=0x1067a, pf=0x80, revision=0xa07
    Feb 26 16:46:41 arch kernel: platform microcode: Direct firmware load failed with error -2
    Feb 26 16:46:41 arch kernel: platform microcode: Falling back to user helper
    Feb 26 16:46:41 arch kernel: input: 2.4G Wireless Wireless Receiver as /devices/pci0000:00/0000:00:1d.1/usb7/7-2/7-2:1.0/input/input17
    Feb 26 16:46:41 arch kernel: hid-generic 0003:1915:0F01.0001: input,hidraw0: USB HID v1.11 Keyboard [2.4G Wireless Wireless Receiver ] on usb-0000:00:1d.1-2/input0
    Feb 26 16:46:41 arch kernel: input: 2.4G Wireless Wireless Receiver as /devices/pci0000:00/0000:00:1d.1/usb7/7-2/7-2:1.1/input/input18
    Feb 26 16:46:41 arch kernel: hid-generic 0003:1915:0F01.0002: input,hidraw1: USB HID v1.11 Mouse [2.4G Wireless Wireless Receiver ] on usb-0000:00:1d.1-2/input1
    Feb 26 16:46:41 arch kernel: BUG: unable to handle kernel NULL pointer dereference at (null)
    Feb 26 16:46:41 arch kernel: IP: [<ffffffffa06c1317>] mousedev_open_device+0x77/0x100 [mousedev]
    Feb 26 16:46:41 arch kernel: PGD b650b067 PUD b650a067 PMD 0
    Feb 26 16:46:41 arch kernel: Oops: 0000 [#1] PREEMPT SMP
    Feb 26 16:46:41 arch kernel: Modules linked in: mousedev(+) hid_generic iTCO_wdt iTCO_vendor_support ath9k(+) usbhid ath9k_common hid ath9k_hw ath uvcvideo mac80211 microcode(+) videobuf2_vmalloc videobuf2_memops videobuf2_core videodev media evdev psmouse serio_raw pcspkr cfg80211 lpc_ich i915(+) atl1e snd_hda_codec_via snd_hda_intel drm_kms_helper snd_hda_codec drm snd_hwdep snd_pcm snd_page_alloc i2c_algo_bit i2c_core snd_timer asus_laptop snd battery ac soundcore sparse_keymap acpi_cpufreq rfkill video input_polldev thermal intel_agp intel_gtt shpchp processor button ext4 crc16 mbcache jbd2 sr_mod cdrom sd_mod atkbd libps2 ahci libahci libata scsi_mod ehci_pci uhci_hcd ehci_hcd usbcore usb_common i8042 serio
    Feb 26 16:46:41 arch kernel: CPU: 1 PID: 227 Comm: acpid Not tainted 3.13.5-1-ARCH #1
    Feb 26 16:46:41 arch kernel: Hardware name: ASUSTeK Computer Inc. K50IJ /K50IJ , BIOS 217 12/04/2009
    Feb 26 16:46:41 arch kernel: task: ffff88007ffeda00 ti: ffff8800b6516000 task.ti: ffff8800b6516000
    Feb 26 16:46:41 arch kernel: RIP: 0010:[<ffffffffa06c1317>] [<ffffffffa06c1317>] mousedev_open_device+0x77/0x100 [mousedev]
    Feb 26 16:46:41 arch kernel: RSP: 0018:ffff8800b6517c10 EFLAGS: 00010202
    Feb 26 16:46:41 arch kernel: RAX: 0000000000000000 RBX: ffff8801390f5800 RCX: ffff8801390f5868
    Feb 26 16:46:41 arch kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000246
    Feb 26 16:46:41 arch kernel: RBP: ffff8800b6517c28 R08: 0000000000000000 R09: ffff88013b001600
    Feb 26 16:46:41 arch kernel: R10: 0000000000000000 R11: 0000000000000004 R12: 0000000000000000
    Feb 26 16:46:41 arch kernel: R13: ffff8801390f5880 R14: ffff8800b3287558 R15: ffff880138c8f600
    Feb 26 16:46:41 arch kernel: FS: 00007f8de7e14700(0000) GS:ffff88013fd00000(0000) knlGS:0000000000000000
    Feb 26 16:46:41 arch kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Feb 26 16:46:41 arch kernel: CR2: 0000000000000000 CR3: 00000000b6507000 CR4: 00000000000407e0
    Feb 26 16:46:41 arch kernel: Stack:
    Feb 26 16:46:41 arch kernel: ffff88013926e400 ffff8801390f5800 ffff8801390f5878 ffff8800b6517c60
    Feb 26 16:46:41 arch kernel: ffffffffa06c20cc ffff8801390f5b48 ffff8800b3287558 ffff880138c8f600
    Feb 26 16:46:41 arch kernel: ffffffffa06c2e80 ffff880138c8f610 ffff8800b6517c98 ffffffff811a834f
    Feb 26 16:46:41 arch kernel: Call Trace:
    Feb 26 16:46:41 arch kernel: [<ffffffffa06c20cc>] mousedev_open+0xcc/0x150 [mousedev]
    Feb 26 16:46:41 arch kernel: [<ffffffff811a834f>] chrdev_open+0x9f/0x1d0
    Feb 26 16:46:41 arch kernel: [<ffffffff811a19e7>] do_dentry_open+0x1b7/0x2c0
    Feb 26 16:46:41 arch kernel: [<ffffffff811aedc1>] ? __inode_permission+0x41/0xb0
    Feb 26 16:46:41 arch kernel: [<ffffffff811a82b0>] ? cdev_put+0x30/0x30
    Feb 26 16:46:41 arch kernel: [<ffffffff811a1e01>] finish_open+0x31/0x40
    Feb 26 16:46:41 arch kernel: [<ffffffff811b1bf2>] do_last+0x572/0xe90
    Feb 26 16:46:41 arch kernel: [<ffffffff811af0b6>] ? link_path_walk+0x236/0x8d0
    Feb 26 16:46:41 arch kernel: [<ffffffff811b25cb>] path_openat+0xbb/0x6b0
    Feb 26 16:46:41 arch kernel: [<ffffffff811b3cda>] do_filp_open+0x3a/0x90
    Feb 26 16:46:41 arch kernel: [<ffffffff811c05c7>] ? __alloc_fd+0xa7/0x130
    Feb 26 16:46:41 arch kernel: [<ffffffff811a2fd4>] do_sys_open+0x124/0x220
    Feb 26 16:46:41 arch kernel: [<ffffffff811a30ee>] SyS_open+0x1e/0x20
    Feb 26 16:46:41 arch kernel: [<ffffffff8152142d>] system_call_fastpath+0x1a/0x1f
    Feb 26 16:46:41 arch kernel: Code: c0 6e e5 e0 5b 44 89 e0 41 5c 41 5d 5d c3 66 0f 1f 44 00 00 4c 89 ef 41 bc ed ff ff ff e8 a2 6e e5 e0 eb e0 48 8b 15 c9 21 00 00 <8b> 02 8d 48 01 85 c0 89 0a 75 c6 48 8b 05 37 1f 00 00 48 3d 60
    Feb 26 16:46:41 arch kernel: RIP [<ffffffffa06c1317>] mousedev_open_device+0x77/0x100 [mousedev]
    Feb 26 16:46:41 arch kernel: RSP <ffff8800b6517c10>
    Feb 26 16:46:41 arch kernel: CR2: 0000000000000000
    Feb 26 16:46:41 arch kernel: ---[ end trace 76aa0cbb67cf77f6 ]---
    Feb 26 16:46:41 arch kernel: microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
    Feb 26 16:46:41 arch systemd[1]: acpid.service: main process exited, code=killed, status=9/KILL
    Feb 26 16:46:41 arch systemd[1]: Unit acpid.service entered failed state.
    Feb 26 16:46:41 arch kernel: [drm] GMBUS [i915 gmbus dpc] timed out, falling back to bit banging on pin 4
    Feb 26 16:46:41 arch systemd[1]: Started Laptop Mode Tools.
    Feb 26 16:46:41 arch nxserver[374]: NX> 161 Enabled service: nxserver.
    Feb 26 16:46:42 arch kernel: fbcon: inteldrmfb (fb0) is primary device
    Feb 26 16:46:42 arch kernel: ath: phy0: Enable LNA combining
    Feb 26 16:46:42 arch kernel: ath: EEPROM regdomain: 0x60
    Feb 26 16:46:42 arch kernel: ath: EEPROM indicates we should expect a direct regpair map
    Feb 26 16:46:42 arch kernel: ath: Country alpha2 being used: 00
    Feb 26 16:46:42 arch kernel: ath: Regpair used: 0x60
    Feb 26 16:46:42 arch kernel: ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
    Feb 26 16:46:42 arch kernel: ieee80211 phy0: Atheros AR9285 Rev:2 mem=0xffffc90011e80000, irq=17
    Feb 26 16:46:42 arch systemd-udevd[139]: renamed network interface wlan0 to wlp2s0
    Feb 26 16:46:42 arch kernel: Console: switching to colour frame buffer device 170x48
    Feb 26 16:46:42 arch kernel: i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
    Feb 26 16:46:42 arch kernel: i915 0000:00:02.0: registered panic notifier
    Feb 26 16:46:42 arch kernel: ACPI: Video Device [VGA] (multi-head: yes rom: no post: no)
    Feb 26 16:46:42 arch kernel: acpi device:38: registered as cooling_device2
    Feb 26 16:46:42 arch kernel: input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input19
    Feb 26 16:46:42 arch nxserver[374]: NX> 161 Enabled service: nxnode.
    Feb 26 16:46:42 arch nxserver[374]: NX> 161 Enabled service: nxd.
    Feb 26 16:46:42 arch systemd[1]: Started NoMachine Server daemon.
    Feb 26 16:46:42 arch systemd[1]: Starting Multi-User System.
    Feb 26 16:46:42 arch systemd[1]: Reached target Multi-User System.
    Feb 26 16:46:42 arch systemd[1]: Starting Graphical Interface.
    Feb 26 16:46:42 arch systemd[1]: Reached target Graphical Interface.
    Feb 26 16:46:42 arch systemd[1]: Startup finished in 1.241s (kernel) + 3.231s (userspace) = 4.473s.
    Feb 26 16:46:46 arch kernel: IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
    Feb 26 16:46:48 arch kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
    Feb 26 16:46:49 arch wicd[226]: dhcpcd[1383]: dhcpcd not running
    Feb 26 16:46:49 arch dhcpcd[1383]: dhcpcd not running
    Feb 26 16:46:49 arch kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
    Feb 26 16:46:49 arch wicd[226]: Failed to connect to non-global ctrl_ifname: wlp2s0 error: No such file or directory
    Feb 26 16:46:49 arch wicd[226]: dhcpcd[1389]: dhcpcd not running
    Feb 26 16:46:49 arch dhcpcd[1389]: dhcpcd not running
    Feb 26 16:46:49 arch kernel: IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
    Feb 26 16:46:49 arch wicd[226]: Failed to connect to non-global ctrl_ifname: enp3s0 error: No such file or directory
    Feb 26 16:46:49 arch wicd[226]: dhcpcd[1397]: dhcpcd not running
    Feb 26 16:46:49 arch dhcpcd[1397]: dhcpcd not running
    Feb 26 16:46:49 arch kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
    Feb 26 16:46:49 arch wicd[226]: Failed to connect to non-global ctrl_ifname: wlp2s0 error: No such file or directory
    Feb 26 16:46:51 arch systemd[1]: Starting Getty on tty2...
    Feb 26 16:46:51 arch systemd[1]: Started Getty on tty2.
    Feb 26 16:46:52 arch kernel: wlp2s0: authenticate with 08:86:3b:7f:86:08
    Feb 26 16:46:52 arch kernel: wlp2s0: send auth to 08:86:3b:7f:86:08 (try 1/3)
    Feb 26 16:46:52 arch kernel: wlp2s0: authenticated
    Feb 26 16:46:52 arch kernel: ath9k 0000:02:00.0 wlp2s0: disabling HT/VHT due to WEP/TKIP use
    Feb 26 16:46:52 arch kernel: wlp2s0: associate with 08:86:3b:7f:86:08 (try 1/3)
    Feb 26 16:46:52 arch kernel: wlp2s0: RX AssocResp from 08:86:3b:7f:86:08 (capab=0x411 status=0 aid=4)
    Feb 26 16:46:52 arch kernel: wlp2s0: associated
    Feb 26 16:46:52 arch kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
    Feb 26 16:46:53 arch dhcpcd[1416]: version 6.2.1 starting
    Feb 26 16:46:54 arch dhcpcd[1416]: DUID 00:01:00:01:1a:96:a5:70:1c:4b:d6:a2:1f:ad
    Feb 26 16:46:54 arch dhcpcd[1416]: wlp2s0: IAID d6:a2:1f:ad
    Feb 26 16:46:54 arch dhcpcd[1416]: wlp2s0: soliciting an IPv6 router
    Feb 26 16:46:54 arch dhcpcd[1416]: wlp2s0: ipv6nd_sendrsprobe: sendmsg: Cannot assign requested address
    Feb 26 16:46:54 arch dhcpcd[1416]: wlp2s0: rebinding lease of 192.168.2.3
    Feb 26 16:46:55 arch kernel: type=1006 audit(1393429615.096:2): pid=1406 uid=0 old auid=4294967295 new auid=0 old ses=4294967295 new ses=1 res=1
    Feb 26 16:46:55 arch login[1406]: pam_unix(login:session): session opened for user root by LOGIN(uid=0)
    Feb 26 16:46:55 arch systemd[1]: Starting user-0.slice.
    Feb 26 16:46:55 arch systemd[1]: Created slice user-0.slice.
    Feb 26 16:46:55 arch systemd[1]: Starting User Manager for 0...
    Feb 26 16:46:55 arch kernel: type=1006 audit(1393429615.106:3): pid=1477 uid=0 old auid=4294967295 new auid=0 old ses=4294967295 new ses=2 res=1
    Feb 26 16:46:55 arch systemd[1]: Starting Session 1 of user root.
    Feb 26 16:46:55 arch systemd[1]: Started Session 1 of user root.
    Feb 26 16:46:55 arch systemd-logind[231]: New session 1 of user root.
    Feb 26 16:46:55 arch systemd[1477]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
    Feb 26 16:46:55 arch login[1406]: ROOT LOGIN ON tty2
    Feb 26 16:46:55 arch systemd[1477]: Failed to open private bus connection: Failed to connect to socket /run/user/0/dbus/user_bus_socket: No such file or directory
    Feb 26 16:46:55 arch systemd[1477]: Mounted /sys/kernel/config.
    Feb 26 16:46:55 arch systemd[1477]: Stopped target Sound Card.
    Feb 26 16:46:55 arch systemd[1477]: Starting Default.
    Feb 26 16:46:55 arch systemd[1477]: Reached target Default.
    Feb 26 16:46:55 arch systemd[1477]: Startup finished in 7ms.
    Feb 26 16:46:55 arch systemd[1]: Started User Manager for 0.
    Feb 26 16:46:59 arch dhcpcd[1416]: wlp2s0: leased 192.168.2.3 for 283824000 seconds
    Feb 26 16:46:59 arch dhcpcd[1416]: wlp2s0: adding route to 192.168.2.0/24
    Feb 26 16:46:59 arch dhcpcd[1416]: wlp2s0: adding default route via 192.168.2.1
    Feb 26 16:46:59 arch dhcpcd[1416]: forked to background, child pid 1522
    Feb 26 16:47:10 arch kdm[238]: X server startup timeout, terminating
    Feb 26 16:47:12 arch systemd-udevd[131]: worker [140] /devices/pci0000:00/0000:00:02.0 timeout; kill it
    Feb 26 16:47:12 arch systemd-udevd[131]: seq 1255 '/devices/pci0000:00/0000:00:02.0' killed
    Feb 26 16:47:12 arch systemd-udevd[131]: worker [146] /devices/platform/i8042/serio4/input/input15 timeout; kill it
    Feb 26 16:47:12 arch systemd-udevd[131]: seq 1659 '/devices/platform/i8042/serio4/input/input15' killed
    Feb 26 16:47:12 arch systemd-udevd[131]: worker [148] /devices/pci0000:00/0000:00:1d.1/usb7/7-2/7-2:1.1/input/input18 timeout; kill it
    Feb 26 16:47:12 arch systemd-udevd[131]: seq 1679 '/devices/pci0000:00/0000:00:1d.1/usb7/7-2/7-2:1.1/input/input18' killed
    Feb 26 16:47:12 arch kernel: [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
    Feb 26 16:47:12 arch systemd-udevd[131]: worker [140] terminated by signal 9 (Killed)
    Feb 26 16:47:12 arch systemd-udevd[131]: worker [148] terminated by signal 9 (Killed)
    Feb 26 16:47:12 arch systemd[1]: Starting Load/Save Screen Backlight Brightness of acpi_video0...
    Feb 26 16:47:12 arch systemd[1]: Started Load/Save Screen Backlight Brightness of acpi_video0.
    Feb 26 16:47:12 arch kernel: input: failed to attach handler mousedev to device input15, error: -4
    Feb 26 16:47:12 arch systemd-udevd[131]: worker [146] terminated by signal 9 (Killed)
    Feb 26 16:47:12 arch kernel: input: failed to attach handler mousedev to device input18, error: -4
    Feb 26 16:47:12 arch kernel: mousedev: PS/2 mouse device common for all mice
    Feb 26 16:47:13 arch kdm[238]: X server for display :0 cannot be started, session disabled
    Feb 26 16:48:56 arch kernel: usb 7-2: USB disconnect, device number 2
    Feb 26 16:48:56 arch laptop-mode[1782]: Laptop mode
    Feb 26 16:48:56 arch laptop-mode[1783]: enabled, not active
    Feb 26 16:48:56 arch laptop-mode[1834]: Laptop mode
    [xx@arch Desktop]$ uname -a
    Linux arch 3.13.5-1-ARCH #1 SMP PREEMPT Sun Feb 23 00:25:24 CET 2014 x86_64 GNU/Linux
    Could you please someone help me with this?
    Thanks

    Sorry to bump this, but I'm having the exact same error tonight on my HTPC, any chance you found out what the problem was ?
    To make matters worse, it's not happening every single time, but maybe every 4 out of 5 boots (same kernel, no changes in between.)
    I thought this was a kernel issue related to this:
    https://lkml.org/lkml/2014/3/10/359
    I've tried adding atkbd and psmouse to my mkinitcpio.conf MODULES section and rebuilt, but no change.
    I changed the NVidia driver from nvidia-304xx to nvidia-full-beta-all ( 334.21 ) from AUR but it had the same error at the same place.
    Here's the part from `dmesg` where it borks:
    [ 3.229195] logitech-djreceiver 0003:046D:C52B.0003: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:04.0-3/input2
    [ 3.236312] input: Logitech Unifying Device. Wireless PID:400e as /devices/pci0000:00/0000:00:04.0/usb3/3-3/3-3:1.2/0003:046D:C52B.0003/input/input6
    [ 3.237230] logitech-djdevice 0003:046D:C52B.0004: input,hidraw1: USB HID v1.11 Keyboard [Logitech Unifying Device. Wireless PID:400e] on usb-0000:00:04.0-3:1
    [ 3.279150] BUG: unable to handle kernel NULL pointer dereference at (null)
    [ 3.280083] IP: [<ffffffffa1cbc317>] mousedev_open_device+0x77/0x100 [mousedev]
    [ 3.280810] PGD c99ea067 PUD c9f4a067 PMD 0
    [ 3.281266] Oops: 0000 [#1] PREEMPT SMP
    [ 3.281668] Modules linked in: mousedev(+) nvidia(PO+) snd_hda_codec_realtek hid_logitech_dj usbhid hid usb_storage coretemp evdev microcode pcspkr serio_raw snd_hda_intel(+) snd_hda_codec shpchp snd_hwdep snd_pcm snd_page_alloc snd_timer snd soundcore i2c_nforce2 i2c_core wmi processor button r8169 mii ext4 crc16 mbcache jbd2 sd_mod ata_generic pata_acpi ahci libahci libata ohci_pci ohci_hcd ehci_pci ehci_hcd scsi_mod usbcore usb_common psmouse atkbd libps2 i8042 serio
    [ 3.281820] CPU: 1 PID: 211 Comm: acpid Tainted: P O 3.13.6-1-ARCH #1
    [ 3.281820] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./MCP7A-ION, BIOS 080015 10/10/2009
    [ 3.281820] task: ffff8800ca5c1b00 ti: ffff8800c97f0000 task.ti: ffff8800c97f0000
    [ 3.281820] RIP: 0010:[<ffffffffa1cbc317>] [<ffffffffa1cbc317>] mousedev_open_device+0x77/0x100 [mousedev]
    [ 3.281820] RSP: 0018:ffff8800c97f1c10 EFLAGS: 00010202
    [ 3.281820] RAX: 0000000000000000 RBX: ffff8800c9987000 RCX: ffff8800c9987068
    [ 3.281820] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000246
    [ 3.281820] RBP: ffff8800c97f1c28 R08: 0000000000000000 R09: ffff8800cf401600
    [ 3.281820] R10: 0000000000000000 R11: 0000000000000004 R12: 0000000000000000
    [ 3.281820] R13: ffff8800c9987080 R14: ffff8800c0260058 R15: ffff8800c9f2a500
    [ 3.281820] FS: 00007f8f12f05700(0000) GS:ffff8800cfa80000(0000) knlGS:0000000000000000
    [ 3.281820] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
    [ 3.281820] CR2: 0000000000000000 CR3: 00000000ca93e000 CR4: 00000000000007e0
    [ 3.281820] Stack:
    [ 3.281820] ffff8800c9940000 ffff8800c9987000 ffff8800c9987078 ffff8800c97f1c60
    [ 3.281820] ffffffffa1cbd0cc ffff8800c9987348 ffff8800c0260058 ffff8800c9f2a500
    [ 3.281820] ffffffffa1cbde80 ffff8800c9f2a510 ffff8800c97f1c98 ffffffff811a83ef
    [ 3.392372] Call Trace:
    [ 3.398245] [<ffffffffa1cbd0cc>] mousedev_open+0xcc/0x150 [mousedev]
    [ 3.398245] [<ffffffff811a83ef>] chrdev_open+0x9f/0x1d0
    [ 3.398245] [<ffffffff811a1a87>] do_dentry_open+0x1b7/0x2c0
    [ 3.398245] [<ffffffff811aee61>] ? __inode_permission+0x41/0xb0
    [ 3.398245] [<ffffffff811a8350>] ? cdev_put+0x30/0x30
    [ 3.398245] [<ffffffff811a1ea1>] finish_open+0x31/0x40
    [ 3.398245] [<ffffffff811b1c92>] do_last+0x572/0xe90
    [ 3.398245] [<ffffffff811af156>] ? link_path_walk+0x236/0x8d0
    [ 3.398245] [<ffffffff811b266b>] path_openat+0xbb/0x6b0
    [ 3.508083] random: nonblocking pool is initialized
    [ 3.398245] [<ffffffff811b3d7a>] do_filp_open+0x3a/0x90
    [ 3.398245] [<ffffffff811c0617>] ? __alloc_fd+0xa7/0x130
    [ 3.398245] [<ffffffff811a3074>] do_sys_open+0x124/0x220
    [ 3.398245] [<ffffffff811a318e>] SyS_open+0x1e/0x20
    [ 3.398245] [<ffffffff815216ad>] system_call_fastpath+0x1a/0x1f
    [ 3.556729] Code: 40 c1 85 df 5b 44 89 e0 41 5c 41 5d 5d c3 66 0f 1f 44 00 00 4c 89 ef 41 bc ed ff ff ff e8 22 c1 85 df eb e0 48 8b 15 c9 21 00 00 <8b> 02 8d 48 01 85 c0 89 0a 75 c6 48 8b 05 37 1f 00 00 48 3d 60
    [ 3.556729] RIP [<ffffffffa1cbc317>] mousedev_open_device+0x77/0x100 [mousedev]
    [ 3.556729] RSP <ffff8800c97f1c10>
    [ 3.556729] CR2: 0000000000000000
    [ 3.563412] ---[ end trace 590b482a8704c6ac ]---
    [ 3.980300] input: HDA NVidia HDMI/DP,pcm=3 Phantom as /devices/pci0000:00/0000:00:08.0/sound/card0/input7
    Here's the output on a good boot:
    [ 3.415791] logitech-djreceiver 0003:046D:C52B.0003: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:04.0-3/input2
    [ 3.422256] input: Logitech Unifying Device. Wireless PID:400e as /devices/pci0000:00/0000:00:04.0/usb3/3-3/3-3:1.2/0003:046D:C52B.0003/input/input6
    [ 3.422644] logitech-djdevice 0003:046D:C52B.0004: input,hidraw1: USB HID v1.11 Keyboard [Logitech Unifying Device. Wireless PID:400e] on usb-0000:00:04.0-3:1
    [ 3.434861] mousedev: PS/2 mouse device common for all mice
    [ 3.853639] input: HDA NVidia HDMI/DP,pcm=3 Phantom as /devices/pci0000:00/0000:00:08.0/sound/card0/input7
    Here's my mkinitcpio.conf
    : grep -v ^\# /etc/mkinitcpio.conf
    MODULES="atkbd psmouse"
    BINARIES=""
    FILES=""
    HOOKS="base udev autodetect modconf block filesystems keyboard fsck"
    Last edited by corpdecker (2014-03-19 02:47:30)

  • UEFI bios boot into safe mode w/o msconfig or F8

    Hi, thanks in advance for taking the time to answer.  First off I'm using an ASUS motherboard with UEFI bios on windows 7 64bit.
    I'm having trouble with my user account being corrupted and cannot be logged into.  I've already looked up how to fix this issue but it requires me logging into safe mode to do so. 
    I am aware of the 2 common methods people are prescribing (msconfig and F8) but neither are an option in this situation it seems.
    Being that I can't log in, and I do not have a second admin account, I cannot use the msconfig method.  I've already tried hitting F8 during start and it just gives me the option to either boot my HD or enter bios.  I also went through the bios
    options and didn't see anything there either.  There's got to be another method than the two I've previously mentioned, right?  Or am I just missing something simple here?
    == edit ==
    == Solved problem myself ==
    heres how for those with same problem:  after hard restarting my computer quite a few times (apparently its SUPPOSED to do this each time but other folks on the internet and myself find it to only work 40% or less) it went into automatic repair mode. 
    after that ran through, to no avail (BIG surprise), it allowed me to enter Command Prompt mode outside of windows.  there I was able to enable a safe mode boot loop so each time my computer boots it automatically goes into safe mode.  fixed what
    i needed and undid the safe mode loop in msconfig.
    back to business as usual!  woot woot

    Asus boards BIOS Boot Menu key is F8... this is annoying if you use their boards with Windows installed, as it is also the key for getting the Windows boot menu.
    What needs to be done is use the F8 to get the menu, select the hard disk (or boot manager if EFI) and then start hitting F8 after you press enter on the boot device. This is the easiest way I've found, as trying to guess when the boot is handed off from
    the board to Windows is hit and miss.

  • Can't update BIOS boot logo

    Hi,
    I've tried changing the BIOS boot logo of my Thinkpad E420, but a specific image isn't working, for some reason.  I use the last "BIOS update utility", being 1.26, from here.  No error shows up during the upgrade.
    http://support.lenovo.com/en_US/research/hints-or-tips/detail.page?&DocID=HT037710
    This is what I should do to change the BIOS Logo:
     *  NOTES ON CUSTOM START UP IMAGE                                    *
     *  THIS VERSION OF THE FLASH UPDATE PROGRAM GIVES THE OPTION OF      *
     *  REPLACING (OR ELIMINATING) THE DEFAULT "LENOVO" IMAGE THAT IS     *
     *  DISPLAYED DURING SYSTEM START UP.                                 *
     *  GUIDELINES FOR CUSTOM START UP IMAGE:                             *
     *  1. THE IMAGE FILE SIZE IS LIMITED TO 30KB.                        *
     *  2. RESOLUTION OF THE IMAGE SHOULD BE LESS THAN 640X480.           *
     *  3. VALID FORMATS FOR THE IMAGE ARE AS FOLLOWS:                    *
     *        BITMAP (.BMP) FILE FORMAT                                   *
     *        JPEG (.JPG) FILE FORMAT                                     *
     *        GIF (.GIF) FILE FORMAT                                      *
     *  STEPS TO ENABLE CUSTOM START UP IMAGE:                            *
     *  1. PREPARE YOUR IMAGE AND COPY IT TO THE SAME PLACE WHERE         *
     *     WINUPTP.EXE EXISTS.                                            *
     *  2. RENAME THE IMAGE AS FOLLOWS.                                   *
     *         BITMAP FILE --> LOGO.BMP                                   *
     *         JPEG FILE --> LOGO.JPG                                     *
     *         GIF FILE --> LOGO.GIF                                      *
     *  3. RUN WINUPTP.EXE AND FOLLOW INSTRUCTIONS.                       *
     *  AFTER YOU UPDATE THE BIOS ON YOUR SYSTEM, YOUR LOGO WILL          *
     *  APPEAR ON THE STARTUP SCREEN.                                     *
    Interestingly, this image work as it should:
    https://www.dropbox.com/s/600u9o08a1ax1wp/LOGO_OLD.jpg
    But this one don't:
    https://www.dropbox.com/s/hrayfjslyv57o53/LOGO.JPG
    I never get any error during the update, I click "YES" on the popup "Custom image was found, do you want to use it", but if I chose the second image, I get a black screen at the BIOS logo (Computer continue booting normally, and I can access the BIOS - but I have a black screen).
    What's wrong with the second image?  How is the second image different from the first one, that does work?  I don't get it. :/
    I can also succesfully restore the BIOS logo to the Default, if I delete LOGO.JPG from the update folder.
    Thanks for the help.

    Hi GameX,
    the only difference that I can see immediately is something which caused me problems with a particular web publishing software once, took me ages to find the bug.  Your second picture has JPG as the ending, the first jpg - maybe the utility is case sensitive on file endings??
    Andy  ______________________________________
    Please remember to come back and mark the post that you feel solved your question as the solution, it earns the member + points
    Did you find a post helpfull? You can thank the member by clicking on the star to the left awarding them Kudos Please add your type, model number and OS to your signature, it helps to help you. Forum Search Option T430 2347-G7U W8 x64, Yoga 10 HD+, Tablet 1838-2BG, T61p 6460-67G W7 x64, T43p 2668-G2G XP, T23 2647-9LG XP, plus a few more. FYI Unsolicited Personal Messages will be ignored.
      Deutsche Community     Comunidad en Español    English Community Русскоязычное Сообщество
    PepperonI blog 

  • Help! problems with boot...

    My system has worked fine for a week, but I have been unable to get the usb in front of my computer to work so I tried again today. I booted right after that but a strange noice came, sounded like electrisity and I got a bad CMOS message and the machine refused to boot. I tried to run flash recovery but for some reason both my floppy and keyboard does not seem to work/boot. I have tried another keyboard but nothing happends. I have tried to reset bios and to take out the cmos-battery but it made no change. any ideas of what I can do?

    Quote
    Originally posted by Jocko
    Hi
    The differance between this mobo and others, is the useage of the +12v, the CPU and mobo need at least 12amps to post. That leaves nothing for HDDs, Cds, fans, Graphic Card, etc. Your system will not be able to cope for long.
    jocko
     Taraquin these guys told me the same thing a few weeks ago about my PSU. My system was working fine, so I was like no that can't be right. but after some research on the net. I found that Jocko, SAB, and tiresmoke was dead on the money about the PSU.
      From what I read and put together from several resources was that this mobo, CPU combo all by it's self pull heavily on the PSU. you add a Vid card, like an ATI 9800, a few cd roms and floppy and a few hard drives and use something different than the on board sound. What would be considered an average to good PSU just will not cut it with this system. after reading all of this I purchased an Antec true 550. you can believe what you like. but my system that i thought was having no problems, Now boots smoother, I have kept a check on my voltages they don't fluctuate like they did before. and the over performance of the system is better. I remember reading somewhere and I can't remember if it was here or else where that on the 12+ side you need a minimum of 24A for this system to operate well. DeMaxx

  • BIOS Boot-Up

    On ititial Power Up I cannot always get to the BIOS Power On Password screen.  After switching from DC only power to AC only power and then sometime both - The blue Power On password screen comes up.  I've tried that 15 seconds of holding the Power Button - It works sometimes, but there is no real solution - Just switching from one power source to the other and sometimes opening the DVD  tray so the BIOS boot up sequence doesn't access the Drive.  Again no real solution - Just keep swiching power source and the P/W Screen appear  I just upgraded to Win 10 from Win 7 yesterday - No change iin this problem Another FYI All Drivers and BIOS are current.  

    Dear all,
    The issue seems to be resolved after installing the latest storage matrix driver from Intel. The boot time drop from 15minutes to approx 40 seconds.
    It appears that the EFI BIOSes is very sensitive even to the drivers used by Windows?
    Regards,
    Titus

  • MOVED: Bios booting colours ?

    This topic has been moved to AMD64 nVidia Based board.
    Bios booting colours ?

    Dude,
    Yep, as soon as i turn on the PC to getting to the Windows logo its black and white even if i enter bios it doest change, it only changes when im at the welcome screen where it turns into colour.
    Once im in windows i dont have any problems in 2d applications and games, only booting and bios is black and white, how wierd the graphics card is brand new only got it a few days ago.

  • Howto retrieve the bios boot device

    i am trying to retrieve the bios boot device used on startup. not what the kernel reports in /proc/sys/kernel/real-root-dev but the actuall bios device. i know on boot when "int 19h" is called, DL holds this info (0x80, 0x81, etc) , but i have no idea if/were i can retrieve this easily. i can code a small asm program to read the cmos data (in 71h) but i think there might be a simpler/native way todo it. any ideas?
    thanks.

    tnx man.
    i know its gonna be x86 only, but thats ok - as long as Arch is i686, its fine with me
    i looked at the syslinux MBR sources (thats what im using on my livecd) and saw it does save DL on startup, but doesnt retrieve it to users' use. so i might make a patch to add the DL as a parameter to the command line something like "BIOSBOOTDEV=0x80". the problem is with USB - i didnt understand how it uses the MBR - some docs said it doesnt need to have MBR installed, and i got confused by that - if no MBR is installed, how can i retrieve my lovely DL ? so, im gonna leave this for now until im gonna tackle with the liveusb version, then i'll know some more...
    i decided reading the cmos data from cmos area using "in 71h" is REALLY bad cause each bios stores the cmos-data in a diff format and in a diff location... i got crazy with shifting bits to get the info from AMI bios... so MBR hacking will be my best bet.

  • 875P NEO FIS2R problems with booting at power-up

    Having problems with booting at power-up.
    Recently, with no apparent modification to system - at power up the system will often not boot.  About 80% of time systems seems to go into a loop with CD/DVD drive light blinking a few times, then the floppy drive light comes on and can hear the FDD run – within 30 seconds or so, this process starts over again.  Power switch LED is on and HDD LED is on (continuously).  All fans are running (power supply fan, case fan, CPU fan and Intel Canterwood 875 fan ).
    Monitor power on light is in power save mode (amber) when system does not boot.  When boot is successful the monitor power light turns green immediately.
    After pressing the reset button several times (varies between pressing reset button 1 time to 30 or more times) system will then boot OK or go into set up.
    Once running there is no apparent problem.
    This mainboard comes with D Bracket containing 2 USB 2.0 ports, and 4 diagnostics LEDs - when boot problem occurs the diagnostic LEDs, give a code that in the MSI mainboard manual states “Initializing Keyboard Controller” and diagnostic LEDs stays in this mode until via reset button provides a successful boot and start up.
    Have reseated all connectors.
    SYSTEM
    Mainboard – MSI 875P Neo FIS2R   (MSI 6758)
    BIOS – AMI v1.8 (has not been updated)
    CPU – Intel P4 2.6 GHz - system bus 800 MHz 512 KB L2 Cache
    Memory – 1.5 gb (2 x 256 mb and 2 x 512mb)
    Power Supply – Antec 380 watt
    HDD – IED WD 160 GB and IED WD 40 GB
    Video Card – ATI Radeon 9600 (128 RAM)
    Operating System – MS Windows XP Pro (sp2)

    Quote from: BOSSKILLER on 17-May-08, 03:34:12
    Have you done >>Clear CMOS Guide<<?
    Cleared CMOS - no change same problem.  Also, re-seated all connectors at same time.
    Quote from: Wonkanoby on 17-May-08, 09:06:54
    have you just added the second wd drive
    are they jumpered right
    jumperless if alone on ide
    jumpered master /slave if two on it
    No, second 40GB HDD was installed months before this issue started and is jumpered as slave drive.  Also, no other additional hardware installed for several months before issue.

  • Bootcamp problem when booting win vista

    hello guys
    i have one small problem while booting with windows vist. i make a clean install with vista.
    first i created bootcamp partition and then i boot with vista dvd and i formated the ''bootcamp'' partition and install vista. after restart and pressing the option key to select the vista boot the booting started with some errors. because is not possible to make screen shots on bootime i record a video and i uploaded to youtube so u can watch the errors.
    does this happen on all macbooks with bootcamp/vista installation or the problem is on my macbook or the vista installation...?
    http://www.youtube.com/watch?v=J7PrnQw-T_A
    thanks

    If Vista installed, and did an automatic restart after expanding and copying files to your hard drive, it should restart on its own into Vista until all the updates are applied. No need to use the Option key.
    I didn't visit YouTube to try to see, other than what you have described.
    As long as you formatted to NTFS and Vista accepted the partition (20-50GB is good number).
    I would install Boot Camp from your OEM DVD from Apple either before doing any auto updates from Microsoft, or when it is all done. Either works. And add AV software like Norton AV 2009 (and yes, it is fine, unlike 2008 and before, and no need for any of the "Suites" with Vista, most get in the way and take over).
    I have had trouble with Vista SP1 DVD though.

  • Problems with Boot Camp - PLEASE HELP!

    I'm having problems with Boot Camp. Here's what's happening. I ran Boot Camp Assistant, partitioning a 32GB BOOTCAMP drive. I insert my copy of XP and start the installation. My MBP restarts and boots into the Windows Setup. I let it run through the initial actions. I press ENTER to proceed, F8 to accept the license agreement, then when I get to the part where I should be able to select the Partition 3 BOOTCAMP drive (as it says in the Apple Boot Camp Manual) there is only a Partition 1 Unknown drive. It is the only drive to choose from and its a C: drive. I can't figure out why after I run boot camp the partitioned drive doesn't appear as an option in the windows installation. Please help!!!
    Message was edited by: CarlConti08

    Boot into Leo, start Disk Utility and you should see two partitions, your Leo partition and a Fat32 partition of 32GB at the end of the drive.
    If not, boot camp didn't create it for some reason. If it is there then check it with DU and make sure its OK.
    While your in there give it a name so you can easily identify it in your windows installer.
    If there is no partition, create one using Disk Utility at the END if the drive. make sure you create it as a msdos (Fat32) partition and give it a name. The name cannot be more than 11 characters must be comprised of numbers and/or letters (no special characters).
    Verify it before exiting DU.
    Put in windows install disk, reboot - hold option key after the chime until you see the boot screen - select windows CD to begin install.
    Don't forget to install Leo windows drivers after installing windows.
    Kj

  • G41M-E43 and BIOS BOOT IMAGE

    Does anyone know if this board can have it's BIOS BOOT image replced with a custom one?
      What tool is used to do this?
    I would like to change the image to something for my HTPC I am building....I know I can disable it.  I want to put my own image on the BOOT screen.
    Thanks,
    *BH*

    ThinkWiki says you have to work with them. I haven't come across a method to suppress them.
    http://www.thinkwiki.org/wiki/How_to_change_the_BIOS_bootsplash_screen
    I don't work for Lenovo. I'm a crazy volunteer!

  • Regarding query or code to get Bios Boot Order list display in windows

    hi ,
    I wAnyone can help me that i want to display bios boot order list in windows system  without going to Bios Setup.So is there any query or command to get boot order list in windows system  which is applicable to any company like hp,compaq,dell,lenova.
    Thanks in Advance,
    Isha Priya

    In 64 bit with UEIF boot it is BCDEdit.
    On other systems it is not possible.
    There is no script for this.
    bcdedit /?
    ¯\_(ツ)_/¯

  • Problem during booting

    hi guys
    I installed Xp and then removed from my macbook.
    Now there is problem in booting....
    A black screen written " no booting device" comes during start of laptop...
    Plz help

    Hi and welcome to Discussions,
    startup your MacBook while holding down the Option/Alt-key.
    Choose your OSX volume to boot from.
    Once in OSX goto System Preferences - Startup Volume and set your OSX volume as the default startup volume.
    Restart and all should be well.
    Hope it helps
    Stefan

Maybe you are looking for