Bug 1074433 - Installation hangs at finding hardware stage
Installation hangs at finding hardware stage
Status: RESOLVED NORESPONSE
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Installation
Current
x86-64 Other
: P5 - None : Normal (vote)
: ---
Assigned To: E-mail List
Jiri Srain
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-01-03 08:48 UTC by Lud
Modified: 2018-04-27 13:54 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---
jreidinger: needinfo? (pierrelud)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lud 2018-01-03 08:48:13 UTC
First menu comes up, I choose installation and then it hangs at finding hardware...

How can I debug this? Do you have a more verbose install version to see what is causing this? 

Sysinfo
=======

System Model:              HP ZBook Studio G3
System Type:               x64-based PC
Processor(s):              1 Processor(s) Installed.
                           [01]: Intel64 Family 6 Model 94 Stepping 3 GenuineIntel ~2592 Mhz
BIOS Version:              HP N82 Ver. 01.18, 08/06/2017

Network Card(s):           7 NIC(s) Installed.
                           [01]: Intel(R) Ethernet Connection (2) I219-LM
                                 Connection Name: Ethernet
                                 Status:          Media disconnected
                           [02]: Intel(R) Dual Band Wireless-AC 8260
                                 Connection Name: Wi-Fi
                                 Status:          Media disconnected
                           [03]: Broadcom NetXtreme Gigabit Ethernet
                                 Connection Name: Ethernet 2
                                 DHCP Enabled:    Yes
                                 DHCP Server:     192.168.2.1
                                 IP address(es)
                                 [01]: 192.168.2.104
                                 [02]: fe80::2958:6f29:cac3:152b
                                 [03]: 2003:dd:83d2:d401:cc90:7456:8b76:5ae4
                                 [04]: 2003:dd:83d2:d401:2958:6f29:cac3:152b
                           [04]: Juniper Networks Virtual Adapter
                                 Connection Name: Local Area Connection* 15
                                 DHCP Enabled:    No
                                 IP address(es)
                                 [01]: 172.16.125.17
                                 [02]: fe80::b41c:1994:8623:72af
                           [05]: VirtualBox Host-Only Ethernet Adapter
                                 Connection Name: VirtualBox Host-Only Network
                                 DHCP Enabled:    No
                                 IP address(es)
                                 [01]: 192.168.56.1
                                 [02]: fe80::cd26:f862:5c8e:b94
                           [06]: Hyper-V Virtual Ethernet Adapter
                                 Connection Name: vEthernet (Default Switch)
                                 DHCP Enabled:    Yes
                                 DHCP Server:     255.255.255.255
                                 IP address(es)
                                 [01]: 172.20.236.65
                                 [02]: fe80::d875:79b8:d47:8bc0
                           [07]: Hyper-V Virtual Ethernet Adapter
                                 Connection Name: vEthernet (DockerNAT)
                                 DHCP Enabled:    No
                                 IP address(es)
                                 [01]: 10.0.75.1
                                 [02]: fe80::d851:7c88:8aaf:13a2
Hyper-V Requirements:      A hypervisor has been detected. Features required for Hyper-V will not be displayed.
Comment 1 Josef Reidinger 2018-01-03 13:07:18 UTC
Hi,
few ideas how to debug it.

if you put to kernel parameters in boot menu for installation 
startshell=1

then you are in console before yast started. And at this part you can run command hwinfo which yast uses for hardware detection.

so if hwinfo there stuck, you can try you place its ouput to log file or run strace on top of it, so we can see in which system call it hangs.

If you need more help do not hesitate to ask.
Comment 2 Lud 2018-01-04 10:15:32 UTC
@josef 

You said "put to kernel parameters in boot menu for installation 
startshell=1" before this (https://doc.opensuse.org/documentation/leap/startup/html/book.opensuse.startup/cha.inst.html#sec.i.yast2.bootscreen), right?

How/where do I put the kernel parameters in boot menu for installation?
Comment 3 Josef Reidinger 2018-01-04 10:41:26 UTC
no, I mean this screen https://doc.opensuse.org/documentation/leap/startup/html/book.opensuse.startup/cha.inst.html#sec.i.yast2.bootscreen_uefi where you are on installation, you can write and write parameter there.
Comment 4 Steffen Winterfeldt 2018-04-27 13:54:12 UTC
Closing as there's been no response for 3 weeks.

If you can provide the requested information, feel free to re-open.