You are not logged in.
After update to 3.9.2, I was unable to boot. After bios screen I see a black screen with only a white cursor and it hangs forever.
I was able to boot from a usb live image, mount my fs, arch-chroot and downgrade to 3.8.11, then it all worked.
I am using gummiboot with EFI, from SSD drive.
my hwinfo --short
cpu:
Intel(R) Core(TM) i7-3612QM CPU @ 2.10GHz, 1200 MHz
Intel(R) Core(TM) i7-3612QM CPU @ 2.10GHz, 1200 MHz
Intel(R) Core(TM) i7-3612QM CPU @ 2.10GHz, 1200 MHz
Intel(R) Core(TM) i7-3612QM CPU @ 2.10GHz, 1200 MHz
Intel(R) Core(TM) i7-3612QM CPU @ 2.10GHz, 1200 MHz
Intel(R) Core(TM) i7-3612QM CPU @ 2.10GHz, 1200 MHz
Intel(R) Core(TM) i7-3612QM CPU @ 2.10GHz, 1800 MHz
Intel(R) Core(TM) i7-3612QM CPU @ 2.10GHz, 1200 MHz
keyboard:
/dev/input/event0 AT Translated Set 2 keyboard
mouse:
/dev/input/mice Sony Vaio Jogdial
/dev/input/mice SynPS/2 Synaptics TouchPad
graphics card:
Intel VGA compatible controller
sound:
Intel Audio device
storage:
Intel Mobile 82801 SATA RAID Controller
network:
wlp2s0 Intel WLAN controller
enp5s0 Realtek RTL8111/8168B PCI Express Gigabit Ethernet controller
network interface:
lo Loopback network interface
enp5s0 Ethernet network interface
wlp2s0 Ethernet network interface
disk:
/dev/sda TOSHIBA THNSNF25
/dev/sdb TOSHIBA THNSNF25
partition:
/dev/sda1 Partition
/dev/sda2 Partition
/dev/sda3 Partition
/dev/sdb1 Partition
usb controller:
Intel USB Controller
Intel USB Controller
Intel USB Controller
bios:
BIOS
bridge:
Intel Host bridge
Intel PCI bridge
Intel PCI bridge
Intel PCI bridge
Intel PCI bridge
Intel ISA bridge
hub:
Linux 3.8.11-1-ARCH xhci_hcd xHCI Host Controller
Linux 3.8.11-1-ARCH xhci_hcd xHCI Host Controller
Linux 3.8.11-1-ARCH ehci_hcd EHCI Host Controller
Hub
Linux 3.8.11-1-ARCH ehci_hcd EHCI Host Controller
Hub
memory:
Main Memory
unknown:
FPU
DMA controller
PIC
Timer
Keyboard controller
Intel Communication controller
Intel SMBus
Realtek Unclassified device
/dev/input/event10 Ricoh USB2.0 Camera
Last edited by farseerfc (2013-05-21 04:27:36)
Offline
Hi, i have the exact same problem. I also tried booting with refind efistub which hanged as well. The only success I had with 3.9.2 kernel was with refind + grub-efi.
Downgrading to 3.8.8-2 allowed me to boot using gummiboot
What are your bios infos ?
Here is the output of 'bootctl'
System:
Machine ID: f272c25c1bb24621832d44465801e752
Boot ID: b68501e38c1f47faa5bba39dc6e1f25f
Firmware: UEFI 2.31 (INSYDE Corp. 4096.01)
Secure Boot: disabled
Setup Mode: setup
Selected Firmware Entry:
Title: EFI HDD Device
Partition: /dev/disk/by-partuuid/88e4befa-ec4e-4855-8e7b-f2dd99151f22
Boot Loader:
Product: gummiboot 30
Partition: /dev/disk/by-partuuid/88e4befa-ec4e-4855-8e7b-f2dd99151f22
File: └─/EFI/BOOT/BOOTX64.EFI
Selected Boot Loader Entry:
Title: Arch Linux
File: /boot/loader/entries/arch.conf
Some info about system/bios from 'dmidecode' on my Sony Vaio Serie S
BIOS Information
Vendor: Insyde Corp.
Version: R0140C5
System Information
Manufacturer: Sony Corporation
Product Name: SVS15117FDB
Hope this helps !
EDIT: I also tried using the 'noefi' kernel boot argument but it didn't help.
Last edited by antoineniek (2013-05-16 01:44:27)
Offline
There is a thread about this already. It has been occurring off and on since 3.7 to many people, myself included. Though I have not had it happen to me in quite some time. There is a rEFInd binary mentioned in that thread that is a bit differnt that might work better for you.
What I do is use gummiboot, but I always keep a couple extra bootloaders/boot managers installed and configured just in case. I think that since we can be considered somewhat "early adopters" of UEFI in Linux, we are going to run into things like this from time to time. This is especially true since UEFI in general is still so young, and the firmware impementations tend to have all kinds of bugs.
So since the problem is apparently with the EFISTUB bootloader, it is probably wise to keep a more traditional bootloader on hand. I like elilo, but that is just because it is dead simple to configure, so it is easy to maintain.
Offline
Me too!
I think that i915 driver in kernel-3.9.2 cause black screen.
Offline
Thank you antoineniek
I am also use Sony Vaio, SVZ1311AJ
here is my bootctl:
System:
Machine ID: d5945540d2dc4d7bb04a0f6289b33208
Boot ID: af45e33783764c2cabdaee8e91f6ef4e
Firmware: UEFI 2.31 (INSYDE Corp. 4096.01)
Secure Boot: disabled
Setup Mode: setup
Selected Firmware Entry:
Title: EFI HDD Device
Partition: /dev/disk/by-partuuid/36253875-a2ec-484f-8aba-5cbc68a6608e
Boot Loader:
Product: gummiboot 30
Partition: /dev/disk/by-partuuid/36253875-a2ec-484f-8aba-5cbc68a6608e
File: └─/EFI/BOOT/BOOTX64.EFI
Selected Boot Loader Entry:
Title: Arch Linux
File: /boot/loader/entries/arch.conf
And my dmidecode
# dmidecode 2.12
# SMBIOS entry point at 0x9aebcb98
SMBIOS 2.7 present.
18 structures occupying 743 bytes.
Table at 0x9A989000.
Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
Vendor: Insyde Corp.
Version: R0091C6
Release Date: 05/07/2012
Address: 0xE0000
Runtime Size: 128 kB
ROM Size: 3072 kB
Characteristics:
PNP is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
EDD is supported
8042 keyboard services are supported (int 9h)
CGA/mono video services are supported (int 10h)
ACPI is supported
USB legacy is supported
Smart battery is supported
BIOS boot specification is supported
Function key-initiated network boot is supported
Targeted content distribution is supported
UEFI is supported
BIOS Revision: 0.91
Firmware Revision: 0.91
Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: Sony Corporation
Product Name: SVZ1311AJ
Version: J004TSH4
Serial Number: 54582290-0013879
UUID: 0D678980-8C6B-11E2-9426-3C07717887B2
Wake-up Type: Power Switch
SKU Number: N/A
Family: VAIO
Handle 0x0002, DMI type 2, 10 bytes
Base Board Information
Manufacturer: Sony Corporation
Product Name: VAIO
Version: N/A
Serial Number: N/A
Asset Tag: N/A
Features:
Board is a hosting board
Handle 0x0003, DMI type 3, 17 bytes
Chassis Information
Manufacturer: Sony Corporation
Type: Notebook
Lock: Not Present
Version: N/A
Serial Number: N/A
Asset Tag: N/A
Boot-up State: Safe
Power Supply State: Safe
Thermal State: Safe
Security Status: None
OEM Information: 0x00000000
Handle 0x0004, DMI type 4, 40 bytes
Processor Information
Socket Designation: N/A
Type: Central Processor
Family: Core i7
Manufacturer: GenuineIntel
ID: A9 06 03 00 FF FB EB BF
Signature: Type 0, Family 6, Model 58, Stepping 9
Flags:
FPU (Floating-point unit on-chip)
VME (Virtual mode extension)
DE (Debugging extension)
PSE (Page size extension)
TSC (Time stamp counter)
MSR (Model specific registers)
PAE (Physical address extension)
MCE (Machine check exception)
CX8 (CMPXCHG8 instruction supported)
APIC (On-chip APIC hardware supported)
SEP (Fast system call)
MTRR (Memory type range registers)
PGE (Page global enable)
MCA (Machine check architecture)
CMOV (Conditional move instruction supported)
PAT (Page attribute table)
PSE-36 (36-bit page size extension)
CLFSH (CLFLUSH instruction supported)
DS (Debug store)
ACPI (ACPI supported)
MMX (MMX technology supported)
FXSR (FXSAVE and FXSTOR instructions supported)
SSE (Streaming SIMD extensions)
SSE2 (Streaming SIMD extensions 2)
SS (Self-snoop)
HTT (Multi-threading)
TM (Thermal monitor supported)
PBE (Pending break enabled)
Version: Intel(R) Core(TM) i7-3612QM CPU @ 2.10GHz
Voltage: 1.4 V
External Clock: 100 MHz
Max Speed: 2100 MHz
Current Speed: 2100 MHz
Status: Populated, Enabled
Upgrade: None
L1 Cache Handle: 0x0005
L2 Cache Handle: 0x0006
L3 Cache Handle: 0x0007
Serial Number: N/A
Asset Tag: N/A
Part Number: N/A
Core Count: 4
Core Enabled: 4
Thread Count: 8
Characteristics:
64-bit capable
Multi-Core
Hardware Thread
Execute Protection
Enhanced Virtualization
Power/Performance Control
Handle 0x0005, DMI type 7, 19 bytes
Cache Information
Socket Designation: L1 Cache
Configuration: Enabled, Not Socketed, Level 1
Operational Mode: Write Through
Location: Internal
Installed Size: 256 kB
Maximum Size: 256 kB
Supported SRAM Types:
Unknown
Installed SRAM Type: Unknown
Speed: Unknown
Error Correction Type: Parity
System Type: Unknown
Associativity: Unknown
Handle 0x0006, DMI type 7, 19 bytes
Cache Information
Socket Designation: L2 Cache
Configuration: Enabled, Not Socketed, Level 2
Operational Mode: Write Through
Location: Internal
Installed Size: 1024 kB
Maximum Size: 1024 kB
Supported SRAM Types:
Unknown
Installed SRAM Type: Unknown
Speed: Unknown
Error Correction Type: Multi-bit ECC
System Type: Unified
Associativity: 8-way Set-associative
Handle 0x0007, DMI type 7, 19 bytes
Cache Information
Socket Designation: L3 Cache
Configuration: Enabled, Not Socketed, Level 3
Operational Mode: Write Back
Location: Internal
Installed Size: 6144 kB
Maximum Size: 6144 kB
Supported SRAM Types:
Unknown
Installed SRAM Type: Unknown
Speed: Unknown
Error Correction Type: Multi-bit ECC
System Type: Unified
Associativity: 12-way Set-associative
Handle 0x0008, DMI type 11, 5 bytes
OEM Strings
String 1: 0000073306J
String 2: FNC-EXTB
String 3: AYM63CN6oU8U7SR9uU8TnihJnn_1xbtkRSyXt6oU7Y7SRAoU8T
String 4: Reserved
String 5: 8.0.4.1441
Handle 0x0009, DMI type 16, 15 bytes
Physical Memory Array
Location: System Board Or Motherboard
Use: System Memory
Error Correction Type: None
Maximum Capacity: Unknown
Error Information Handle: Not Provided
Number Of Devices: 2
Handle 0x000A, DMI type 17, 21 bytes
Memory Device
Array Handle: 0x0009
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 4096 MB
Form Factor: SODIMM
Set: None
Locator: SODIMM1
Bank Locator: Bank 0
Type: DDR3
Type Detail: Unknown
Handle 0x000B, DMI type 17, 21 bytes
Memory Device
Array Handle: 0x0009
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 4096 MB
Form Factor: SODIMM
Set: None
Locator: SODIMM2
Bank Locator: Bank 1
Type: DDR3
Type Detail: Unknown
Handle 0x000C, DMI type 19, 15 bytes
Memory Array Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x001FFFFFFFF
Range Size: 8 GB
Physical Array Handle: 0x0009
Partition Width: 2
Handle 0x000D, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x000FFFFFFFF
Range Size: 4 GB
Physical Device Handle: 0x000A
Memory Array Mapped Address Handle: 0x000C
Partition Row Position: Unknown
Interleave Position: Unknown
Interleaved Data Depth: Unknown
Handle 0x000E, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00100000000
Ending Address: 0x001FFFFFFFF
Range Size: 4 GB
Physical Device Handle: 0x000B
Memory Array Mapped Address Handle: 0x000C
Partition Row Position: Unknown
Interleave Position: Unknown
Interleaved Data Depth: Unknown
Handle 0x000F, DMI type 32, 20 bytes
System Boot Information
Status: No errors detected
Handle 0x0010, DMI type 136, 11 bytes
OEM-specific Type
Header and Data:
88 0B 10 00 01 44 49 52 53 09 04
Strings:
Sony Corporation
Handle 0x0011, DMI type 127, 4 bytes
End Of Table
Waiting for a solution.
Offline
<snip>
Waiting for a solution.
I take real issue with this statement for two reasons.
The first and probably most significant is that there is a general expectation as an Arch Linux user that you are competent enough to at least try to debug your own issues. I am not saying that you should be able to solve 100% of things that come your way, but that you have a willingness to at least dig a little and look. Posting the output of a couple of commands and simply waiting for someone to just give you the answer just goes against the very principles of the distribution and these threads (especially when the second command output seems just totally random).
Second, I have actually attempted to give you an answer in post #3. I even linked back to a thread where the symptoms you are describing are very similar, though without moer info than "This kernel won't boot " I cannot say that it is the same. Still it is a lead that I would have expected even a non-skilled to have followed. I even mentioned what some people have said solves their issue.
So that leads me to have to ask (not that I am necessarily willing to offer any more help here), but have you tried anything besides simply doengrading your kernel?
Offline
@WonderWoofy
You are right. I did not do my best.
I was trying hard to deal with another issue after downgrading. It seems that 3.8.11-1 cannot connect to wifi in my office. I didn't noticed that because I used lan network in my home. It took me days to realized that the wifi issue was also caused from kernel. Without network, it was hard to diagnose anything.
I skimmed through the first page of the thread you mentioned, there people was talking about common mistakes, and a different kernel version. So I did not continue. I was totally wrong about making this decision.
Thank you very much for telling that thread again. I just found srs5694 clearly described the situation of my problem here: https://bbs.archlinux.org/viewtopic.php … 3#p1233673
So I tried again with gummiboot booting to grub-efi. It worked on 3.9.2-1 ! Thank you!
I am now still digging on this issue, finding a way to get ride of grub-efi from booting process.
BTW, I found you talking about systemd user session there, I want to try that after I fixed my booting.
Last edited by farseerfc (2013-05-17 18:57:06)
Offline
Are you wed to gummiboot? Is another bootloader [grub] an option?
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
@graysky
grub-efi is OK to me.
But if I have to live with grub, I can also use it under BIOS, without vfat partitions and other issues, right? The reason that motivate me to switch to UEFI and gummiboot was its simple configuration style, like what grub legacy provides.
(Also I heard that gummiboot is the only one that support Systemd Bootloader Interface, don't know when grub will provide that.)
BTW I still have grub legacy on my workstation and test server, sound and stable.
Offline
If you enable legacy support in your bios then yes. Why would you want to do that though? Grub is pretty darn easy to configure since the config is autogenerated with a simple, `grub-mkconfig -o /boot/grub/grub.cfg` ...no idea about gummi and that systemd loader support bit.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
@graysky Yes, you are right.
Gummiboot only gives me firmware boot time in systemd-analyze, which is not essential at all.
I just never had time to study about all internal relations between /etc/default/grub and /etc/grub.d/* and /boot/grub/grub.cfg , maybe I should spend some time on that.
From my understanding a bootloader should be just a thin jumper between BIOS/UEFI and kernel, and all the complexity of grub is far beyond that, with foreign language support and gfxterm and other things I don't need.
Now that kernel comes with efi stub, I thought I could try a lightweight bootloader, in case that kernel fails, and gummiboot fits all my needs.
Thank you, I should stop wasting time on this and happy live with grub.
Edit:
I mean a light weight boot manager or bootloader.
Last edited by farseerfc (2013-05-17 21:01:58)
Offline
If you want simplicity in configuration, you should try elilo. It is a bootloader in the traditional sense, so you wont't be relying on the EFISTUB, and the configuration is simple like that of grub-legacy (or plain ol' lilo). The only thing is that elilo by default does not come with any kind of menu interface, and from the documentation, creating one was not incredibly straight forward. Still it works just fine, and saved me those coupel times the kernel wouldn't play nice.
Offline
Upgraded to 3.9.3-1, problem was fixed, mark as solved
Offline