Results 1 to 3 of 3

Thread: 2016.2 installed but hanging early during startup

  1. #1
    Join Date
    2016-Nov
    Posts
    2

    2016.2 installed but hanging early during startup

    Hi Everybody,

    Joined the forum today to get advice on an issue with completing the install of KL2016.2 on a Dell Inspiron laptop with Windows 10 in dual boot. I was surprised at the large number of messages posted about installation issues with KL so seems as though I a not alone but I couldn't find any reference to my particular issue hence the query. First off I am a relative Linux newbie - familiar with it to a point but have spent most of my years in Windows (sorry!).

    I started this journey a couple of days ago by attempting to put KL onto a bootable USB device using the standard guides provided on the KL forum. Seemed to work fine and laptop did boot to initial menu screen but when I selected live version it was always hanging and never completed loading. I tried using the same USB device on my desktop machine and it worked fine so assumed to be no issue with the USB and software on it.

    Today I figured I would try the dual boot option on the laptop. Went through the install procedure fine using the same USB to install KL from and I now have the option to boot KL or windows, with KL now occupying the MBR.
    When I launch the "Kali GNU/Linux" option from the "GNU GRUB Version 2.02~beta2-36" menu it stalls very early. All that I see on screen are the 3 lines below and from reading about these errors it didn't necessarily mean they were the showstoppers.

    /dev/sda7: clean, 320046/11763712 files, 2871457/47032064
    [ 7.285580] tpm_crb MSFT0101:00: can't request region for resource [mem 0xfed40040-0xfed4103f]
    [ 8.683628] lwlwifi 0000:02:00.0: Unsupported splx structure

    Could you KL Superheroes give me some troubleshooting tips as to where to start looking with this? I can get to a command line so can navigate and look at things but there isn't much to go on. How do I begin to evaluate where it's stalling?
    The fact that I could run the USB version on my desktop but not the laptop made me think it may be a video driver issue but no one else reporting similar with Intel and AMD Radeon R7 graphics, so it was just a guess.

    Further update from today (01/12)

    I booted KL into recovery mode and ran journalctl -xb to look for any obvious errors.* Found a few strange entries related to failures in: -

    - fjes module verification failure,
    "fjes: module verification failed: signature and/or required key missing - tainting kernel"

    - tpm_crb failing with error -16
    "tpm_crb MSFT0101:00: can't request region for resource [mem 0xfed40040-0xfed4103f]
    tpm_crb: probe of MSFT0101:00 failed with error -16"

    - iwlwifi unsupported splx structure
    "iwlwifi 0000:02:00.0: Unsupported splx structure"

    - CRAT table not found

    - rescue.service failure with no such file or directory for /bin/Plymouth
    "rescue.service: Failed at step EXEC spawning /bin/Plymouth: no such file or directory"

    The rescue service error was the last entry.

    Thanks in advance for any help !* My laptop is pretty much useless until I get this fixed so will keep looking for solutions.
    Last edited by Hunter23; 2016-12-01 at 11:35. Reason: Updated with further details on errors in logs

  2. #2
    Join Date
    2016-Nov
    Posts
    2

    Progress made to remove some problems....

    Situation has improved based on today's activity....

    I retrieved and applied many updates through the apt-get update and apt-get dist-update commands, and my KL desktop appeared first time after the reboot. dunno what the original issue was but the update catchup has removed it - good news.

    But...I now have some different issues which have appeared but are not catastrophic so would appreciate some input as to whether to ignore or attempt to fix.....here's the current issues I am seeing through the journalctl -xb command...

    1. Seeing lots of errors with my iwlwifi interface...see below. The wifi card is working as it is detecting AP's around, but the errors below are just repeating constantly in the journal file.

    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: Microcode SW error detected. Restarting 0x2000000.
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: CSR values:
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: (2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG)
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: CSR_HW_IF_CONFIG_REG: 0X00c89200
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: CSR_INT_COALESCING: 0X0000ff40
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: CSR_INT: 0X00000000
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: CSR_INT_MASK: 0X00000000
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: CSR_FH_INT_STATUS: 0X00000000
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: CSR_GPIO_IN: 0X00000000
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: CSR_RESET: 0X00000000
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: CSR_GP_CNTRL: 0X080403cd
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: CSR_HW_REV: 0X00000210
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: CSR_EEPROM_REG: 0Xd55555d5
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: CSR_EEPROM_GP: 0X00000000
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: CSR_OTP_GP_REG: 0Xd55555d5
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: CSR_GIO_REG: 0X001f0042
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: CSR_GP_UCODE_REG: 0X00000000
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: CSR_GP_DRIVER_REG: 0X00000000
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: CSR_UCODE_DRV_GP1: 0X00000000
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: CSR_UCODE_DRV_GP2: 0X00000000
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: CSR_LED_REG: 0X00000060
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: CSR_DRAM_INT_TBL_REG: 0X8846afdc
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: CSR_GIO_CHICKEN_BITS: 0X27800200
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: CSR_ANA_PLL_CFG: 0Xd55555d5
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: CSR_MONITOR_STATUS_REG: 0Xd3b7f777
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: CSR_HW_REV_WA_REG: 0X0001001a
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: CSR_DBG_HPET_MEM_REG: 0Xffff0000
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: FH register values:
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: FH_RSCSR_CHNL0_STTS_WPTR_REG: 0X46663100
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: FH_RSCSR_CHNL0_RBDCB_BASE_REG: 0X046663e0
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: FH_RSCSR_CHNL0_WPTR: 0X000000c8
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: FH_MEM_RCSR_CHNL0_CONFIG_REG: 0X80801114
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: FH_MEM_RSSR_SHARED_CTRL_REG: 0X000000fc
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: FH_MEM_RSSR_RX_STATUS_REG: 0X07030000
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 0X00000000
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: FH_TSSR_TX_STATUS_REG: 0X07ff0001
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: FH_TSSR_TX_ERROR_REG: 0X00000000
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: Start IWL Error Log Dump:
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: Status: 0x00000000, count: 6
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: Loaded firmware version: 22.361476.0
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: 0x000014FC | ADVANCED_SYSASSERT
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: 0x000002F0 | trm_hw_status0
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: 0x00000000 | trm_hw_status1
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: 0x00043850 | branchlink2
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: 0x0004A5E8 | interruptlink1
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: 0x00000000 | interruptlink2
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: 0x00000E01 | data1
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: 0x00000000 | data2
    Dec 01 17:31:37 KL2016 kernel: iwlwifi 0000:02:00.0: 0x01010000 | data3

    2. There are lots of errors noted in the journalctl output at different stages, but doesn't seem to be affecting the usability much. Should I be concerned or only look further if something doesn't work? e.g.
    "Failed to start Zeitgeist activity log service"
    "Unit dbus-org.bluez.service not found"
    "Link layer type 113 not ethernet or fddi"
    "firmware: failed to load iwlwifi-7265D-xx,ucode (-2)"
    Still seeing the "iwlwifi unsupported splx structure" error
    Still seeing the tpm_crb MSFT0101:00: cant request region for resource (mem...) error.

    Learned a lot about Linux today so feel that I've made some progress - just not sure whether any of the errors I am seeing are significant or not.

    Many Thanks....!

  3. #3
    Join Date
    2017-Apr
    Posts
    1
    Good day sir Hunter23

    I'm currently in the same situation as you. I also have Dell Inspiron 15 5000 series. Kali live didnt work for me so I also opted for Dual boot.

    I cant get past this error.
    /dev/sda7: clean, 320046/11763712 files, 2871457/47032064
    [ 7.285580] tpm_crb MSFT0101:00: can't request region for resource [mem 0xfed40040-0xfed4103f]
    [ 8.683628] lwlwifi 0000:02:00.0: Unsupported splx structure

    I tried the recovery mode but apt-get update doest work for me. It just says it failed to resolve.

    Did you by any chance solve this? If yes. Please advice. Thank you!

    PS: This is the only thread i can find that discussed this problem.
    I have 0% experience in linux.

Similar Threads

  1. Install Kali 2016.2 on Macbook Pro Early 2011
    By Black-Knight in forum Installing Archive
    Replies: 2
    Last Post: 2017-04-30, 11:10
  2. Kali 2016.2 - GNOME Startup is very slow
    By scila1996 in forum TroubleShooting Archive
    Replies: 0
    Last Post: 2016-12-24, 21:04
  3. Kali Linux 2016.1 - Power Management daemon hanging system
    By Albat0r/ in forum TroubleShooting Archive
    Replies: 1
    Last Post: 2016-06-11, 19:11
  4. How to reset (GRUB) startup screen/menu, if installed DualBoot?...
    By Hyperion in forum TroubleShooting Archive
    Replies: 3
    Last Post: 2013-12-08, 14:36

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •