View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0001643Kali LinuxGeneral Bugpublic2014-08-05 19:582018-01-29 11:38
ReporterTBK Assigned Tog0tmi1k  
PrioritynormalSeveritycrashReproducibilityalways
Status closedResolutionsuspended 
Product Version1.0.8 
Summary0001643: Cannot spawn a message bus without a machine-id
Description

I use Kali Linux 64 bit 1.0.8 which I have transferred to my SanDisk Cruzer Fit USB Flash Drive Cruzer Fit 16GB USB using Win32DiskImager.

I start up in default live mode and crashes during the boot process. I get this error (see attached picture):

live-config: debconf hostname user-setup locales locales-all tzdata gdm3 keyboard-configuration sysvinit sysv-rc gnome-panel-data gnome-power-manager gnome-screensaver
(process:919): WARNING : Cannot spawn a message bus without a machine-id: Unable to load /var/lib/dbus/machine-id or /etc/machine-id: Failed to open file '/var/lib/dbus/machine-id': No such file or directory

(process:919): WARNING : Could not connect: No such file or directory

(process:919): WARNING : Cannot spawn a message bus without a machine-id: Unable to load /var/lib/dbus/machine-id or /etc/machine-id: Failed to open file '/var/lib/dbus/machine-id': No such file or directory kde-services debian-installer-launcher policykit util-linux login xserver-xorg

I have found a thread mentioning the same error http://blog.gmane.org/gmane.linux.debian.devel.live/month=20130501 which says that the problem is related to udev not having started at this stage.

Additional Information

It is a desktop computer with:
CPU: Intel Core i7-4770K
Mobo: Asus Z78-Deluxe/Dual
Gfx: Asus GeForce GTX Titan
DVD Drives: Plextor PX-810SA & Lite-On iHAS624B
PCI Network card: Mellanox ConnectX-3 VPI

Attached Files
000294.jpg (200,686 bytes)   
000294.jpg (200,686 bytes)   

Activities

kimocoder

kimocoder

2014-08-05 21:00

reporter   ~0002440

Same error reported here, with several computers. Running in forensics mode will infact avoid this :/
TBK

TBK

2014-08-06 20:26

reporter   ~0002445

I tested all modes with the x64 image and non of them work for me.
TBK

TBK

2014-08-20 01:19

reporter   ~0002481

I figured out the issue. The issue is with the second SATA controller (Asmedia ASM1061), once disabled then Kali will boot. It is a issue related to the Linux kernel.

I also made a couple of other discoveries. If Intel xHCI Mode is set to "Smart Auto" then USB peripherals won't work at startup, but if peripheral is pull and re-plugged then it works again.

Setting xHCI to disabled will make USB peripherals work out of the box.

If iGPU Multi-Monitor is enabled and even if the primary graphic cards has been set to PCI-E (dedicated card) then the primary output will be one of the video socket on the motherboard.
Disabling iGPU Multi-Monitor will make the PCI-E graphic cards the primary output.
g0tmi1k

g0tmi1k

2018-01-29 11:38

administrator   ~0008010

Due to the age of the OS (Kali Moto [v1], Kali Safi [v2], Kali Rolling 2016.x), these legacy versions are no longer supported.
We will be closing this ticket due to inactivity.

Please could you see if you are able to replicate this issue with the latest version of Kali Linux - https://www.kali.org/downloads/)?

If you are still facing the same problem, feel free to re-open the ticket. If you choose to do this, could you provide more information to the issue you are facing,and also give information about your setup?
For more information, please read: https://kali.training/topic/filing-a-good-bug-report/

Issue History

Date Modified Username Field Change
2014-08-05 19:58 TBK New Issue
2014-08-05 19:58 TBK File Added: 000294.jpg
2014-08-05 21:00 kimocoder Note Added: 0002440
2014-08-06 20:26 TBK Note Added: 0002445
2014-08-20 01:19 TBK Note Added: 0002481
2018-01-29 11:38 g0tmi1k Assigned To => g0tmi1k
2018-01-29 11:38 g0tmi1k Status new => closed
2018-01-29 11:38 g0tmi1k Resolution open => suspended
2018-01-29 11:38 g0tmi1k Note Added: 0008010