View Issue Details

IDProjectCategoryView StatusLast Update
0001144Kali LinuxGeneral Bugpublic2018-01-29 11:17
ReporterMister_X Assigned Tog0tmi1k  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionsuspended 
PlatformarmhfOSKaliOS Version1.0
Product Version1.0.6 
Summary0001144: Building custom Utilite Pro image fails to completely boot - Hangs at Network Manager
Description

Utilite Pro image hangs during boot after starting Network Manager. It never goes any further (or to the login) and doesn't show anything on the screen (even if connected on the DVI port).

I attached the log of the end of the boot, showing exactly where it stops (and then hangs).

Steps To Reproduce

Follow the tutorial 'Ultimate pentesting PwnBox for 2013 - Utilite Pro' but you have to patch the utilite.sh script with the 2 patches on bug 0001137.

Connect the serial console and open the serial port. Then boot it. It will not do anything after starting NetworkManager (or maybe tell you the network is down) then hang a few seconds later (10-15).

Attached Files
utilite_fail_boot.txt (1,575 bytes)   
[ ok ] Mounting local filesystems...done.
[ ok ] Activating swapfile swap...done.
[ ok ] Cleaning up temporary files....
[ ok ] Setting kernel variables ...done.
[....] Configuring network interfaces...NET: Registered protocol family 10
Internet Systems Consortium DHCP Client 4.2.2
Copyright 2004-2011 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

eth0: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=1:00, irq=-1)
ADDRCONF(NETDEV_UP): eth0: link is not ready
Listening on LPF/eth0/00:01:c0:14:9d:2a
Sending on   LPF/eth0/00:01:c0:14:9d:2a
Sending on   Socket/fallback
DHCPREQUEST on eth0 to 255.255.255.255 port 67
PHY: 1:00 - Link is Up - 100/Full
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 10.21.21.1
bound to 10.21.21.78 -- renewal in 137304 seconds.
done.
[ ok ] Cleaning up temporary files....
[....] Setting up ALSA...amixer: Invalid command!
done.
[info] Setting console screen modes and fonts.
setterm: cannot (un)set powersave mode: Invalid argument
[ ok ] Setting up X socket directories... /tmp/.X11-unix /tmp/.ICE-unix.
INIT: Entering runlevel: 2
[info] Using makefile-style concurrent boot in runlevel 2.
[ ok ] Starting enhanced syslogd: rsyslogd.
[ ok ] Starting periodic command scheduler: cron.
[ ok ] Starting system message bus: dbus.
saned disabled; edit /etc/default/saned
[ ok ] Starting network connection manager: NetworkManager.
ADDRCONF(NETDEV_UP): eth1: link is not ready
utilite_fail_boot.txt (1,575 bytes)   
kali_utilite_full_boot_log.txt (19,630 bytes)   

U-Boot 2009.08 (Dec 03 2013 - 09:47:02)

CPU: Freescale i.MX6 family TO6.4 at 792 MHz
Temperature:   22 C, calibration data 0x5764d669
mx6q pll1: 792MHz
mx6q pll2: 528MHz
mx6q pll3: 480MHz
mx6q pll8: 50MHz
ipg clock     : 66000000Hz
ipg per clock : 66000000Hz
uart clock    : 80000000Hz
cspi clock    : 60000000Hz
ahb clock     : 132000000Hz
axi clock   : 264000000Hz
emi_slow clock: 29333333Hz
ddr clock     : 528000000Hz
usdhc1 clock  : 198000000Hz
usdhc2 clock  : 198000000Hz
usdhc3 clock  : 198000000Hz
usdhc4 clock  : 198000000Hz
nfc clock     : 11000000Hz
Board: CM-FX6:[ WDOG ]
Boot Device: SD
I2C:   ready
DRAM:   2 GB
NAND:  No NAND device found!!!
0 MiB
MMC:   FSL_USDHC: 0,FSL_USDHC: 1,FSL_USDHC: 2
JEDEC ID: 0x20:0x71:0x15
In:    serial
Out:   serial
Err:   serial
Net:   got MAC address from IIM: 00:00:00:00:00:00
FEC0
Hit any key to stop autoboot:  0
mmc2 is current device
reading boot.scr

** Unable to read "boot.scr" from mmc 2:1 **
reading uImage-cm-fx6

3918896 bytes read
Booting from mmc ...
## Booting kernel from Legacy Image at 10800000 ...
   Image Name:   Linux-3.0.35-cm-fx6-4
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3918832 Bytes =  3.7 MB
   Load Address: 10008000
   Entry Point:  10008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Linux version 3.0.35-cm-fx6-4 (root@mainnerve-3) (gcc version 4.7.3 20130328 (pr                                                                                                                     erelease) (crosstool-NG linaro-1.13.1-4.7-2013.04-20130415 - Linaro GCC 2013.04)                                                                                                                      ) #1 SMP Thu Apr 10 16:33:50 MDT 2014
CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c53c7d
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: Compulab CM-FX6
cm_fx6_v4l_setup: cm_fx6_v4l_msize: 134217728
Memory policy: ECC disabled, Data cache writealloc
CPU identified as i.MX6Q, silicon rev 1.2
PERCPU: Embedded 7 pages/cpu @cce11000 s5280 r8192 d15200 u32768
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 502272
Kernel command line: console=ttymxc3,115200 root=/dev/mmcblk0p2 rw rootwait cm_f                                                                                                                     x6_v4l_msize=128M vmalloc=256M
PID hash table entries: 4096 (order: 2, 16384 bytes)
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 960MB 1024MB = 1984MB total
Memory: 2006196k/2006196k available, 90956k reserved, 1474560K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    DMA     : 0xf4600000 - 0xffe00000   ( 184 MB)
    vmalloc : 0xe2800000 - 0xf2000000   ( 248 MB)
    lowmem  : 0xc0000000 - 0xe2000000   ( 544 MB)
    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    modules : 0xbf000000 - 0xbfe00000   (  14 MB)
      .init : 0xc0008000 - 0xc0043000   ( 236 kB)
      .text : 0xc0043000 - 0xc0714264   (6981 kB)
      .data : 0xc0716000 - 0xc0773b40   ( 375 kB)
       .bss : 0xc0773b64 - 0xc07dc31c   ( 418 kB)
Hierarchical RCU implementation.
        RCU dyntick-idle grace-period acceleration is enabled.
NR_IRQS:624
MXC GPIO hardware
sched_clock: 32 bits at 3000kHz, resolution 333ns, wraps every 1431655ms
arm_max_freq=1GHz
MXC_Early serial console at MMIO 0x21f0000 (options '115200')
bootconsole [ttymxc3] enabled
Console: colour dummy device 80x30
Calibrating delay loop... 1581.05 BogoMIPS (lpj=7905280)
pid_max: default: 32768 minimum: 301
Security Framework initialized
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
CPU1: Booted secondary processor
CPU2: Booted secondary processor
CPU3: Booted secondary processor
Brought up 4 CPUs
SMP: Total of 4 processors activated (6324.22 BogoMIPS).
devtmpfs: initialized
print_constraints: dummy:
NET: Registered protocol family 16
print_constraints: vddpu: 725 <--> 1300 mV at 1150 mV fast normal
print_constraints: vddcore: 725 <--> 1300 mV at 1150 mV fast normal
print_constraints: vddsoc: 725 <--> 1300 mV at 1200 mV fast normal
print_constraints: vdd2p5: 2000 <--> 2775 mV at 2400 mV fast normal
print_constraints: vdd1p1: 800 <--> 1400 mV at 1100 mV fast normal
print_constraints: vdd3p0: 2625 <--> 3400 mV at 3000 mV fast normal
cpu regulator mode:ldo_enable
hw-breakpoint: found 6 breakpoint and 1 watchpoint registers.
hw-breakpoint: 1 breakpoint(s) reserved for watchpoint single-step.
hw-breakpoint: maximum watchpoint size is 4 bytes.
L310 cache controller enabled
l2x0: 16 ways, CACHE_ID 0x410000c7, AUX_CTRL 0x02070000, Cache size: 1048576 B
bio: create slab <bio-0> at 0
mxs-dma mxs-dma-apbh: initialized
print_constraints: ads7846_vcc: 3300 mV
print_constraints: vmmc: 3300 mV
vgaarb: loaded
SCSI subsystem initialized
spi_imx imx6q-ecspi.0: probed
spi_imx imx6q-ecspi.1: probed
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Freescale USB OTG Driver loaded, $Revision: 1.55 $
imx-ipuv3 imx-ipuv3.0: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)
imx-ipuv3 imx-ipuv3.1: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)
Advanced Linux Sound Architecture Driver Version 1.0.24.
Bluetooth: Core ver 2.16
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO socket layer initialized
Switching to clocksource mxc_timer1
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
UDP hash table entries: 512 (order: 2, 16384 bytes)
UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
_regulator_get: etb supply vcore not found, using dummy regulator
_regulator_get: etm.0 supply vcore not found, using dummy regulator
_regulator_get: etm.1 supply vcore not found, using dummy regulator
_regulator_get: etm.2 supply vcore not found, using dummy regulator
_regulator_get: etm.3 supply vcore not found, using dummy regulator
Static Power Management for Freescale i.MX6
wait mode is enabled for i.MX6
cpaddr = e2880000 suspend_iram_base=e28f0000
PM driver module loaded
IMX usb wakeup probe
add wake up source irq 75
IMX usb wakeup probe
i.MXC CPU frequency driver
highmem bounce pool size: 64 pages
JFFS2 version 2.2. (NAND) � 2001-2006 Red Hat, Inc.
msgmni has been set to 1038
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
imx-sdma imx-sdma: loaded firmware 1.1
imx-sdma imx-sdma: initialized
Serial: IMX driver
imx-uart.0: ttymxc0 at MMIO 0x2020000 (irq = 58) is a IMX
imx-uart.3: ttymxc3 at MMIO 0x21f0000 (irq = 61) is a IMX
console [ttymxc3] enabled, bootconsole disabled
console [ttymxc3] enabled, bootconsole disabled
imx-uart.1: ttymxc1 at MMIO 0x21e8000 (irq = 59) is a IMX
imx-uart.4: ttymxc4 at MMIO 0x21f4000 (irq = 62) is a IMX
brd: module loaded
loop: module loaded
at24 2-0050: 256 byte at24 EEPROM, writable, 16 bytes/write
ahci: SSS flag set, parallel bus scan disabled
ahci ahci.0: AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl platform mode
ahci ahci.0: flags: ncq sntf stag pm led clo only pmp pio slum part ccc apst
scsi0 : ahci_platform
ata1: SATA max UDMA/133 mmio [mem 0x02200000-0x02200fff] port 0x100 irq 71
m25p80 spi0.0: found m25px16, expected m25p80
m25p80 spi0.0: m25px16 (2048 Kbytes)
Creating 3 MTD partitions on "spi_flash":
0x000000000000-0x0000000c0000 : "uboot"
0x0000000c0000-0x000000100000 : "uboot environment"
0x000000100000-0x000000200000 : "reserved"
No NAND device found.
Chip scan failed
GPMI NAND driver registered. (IMX)
vcan: Virtual CAN interface driver
CAN device driver interface
flexcan netdevice driver
flexcan imx6q-flexcan.0: device registered (reg_base=e29b0000, irq=142)
FEC Ethernet Driver
fec_enet_mii_bus: probed
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller
fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1
fsl-ehci fsl-ehci.0: irq 75, io base 0x02184000
fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
add wake up source irq 72
fsl-ehci fsl-ehci.1: Freescale On-Chip EHCI Host Controller
fsl-ehci fsl-ehci.1: new USB bus registered, assigned bus number 2
fsl-ehci fsl-ehci.1: irq 72, io base 0x02184200
fsl-ehci fsl-ehci.1: USB 2.0 started, EHCI 1.00
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
ARC USBOTG Device Controller driver (1 August 2005)
mousedev: PS/2 mouse device common for all mice
 =======snvs_pwrkey_probe() lp_cr 0x20
 =======snvs_pwrkey_probe() lp_cr 0x20
input: snvs_power_key as /devices/virtual/input/input0
 =======snvs_pwrkey_interrupt()lpstatus 0x40060008, lp_cr 0x20
 set snvs as DUMP PMIC MODE
i.MX6 powerkey probe
i2c-core: driver [isl29023] using legacy suspend method
i2c-core: driver [isl29023] using legacy resume method
i2c /dev entries driver
at24 3-0050: 256 byte at24 EEPROM, writable, 16 bytes/write
CM-FX6: Detected SB-FX6m (Utilite) base board
rtc-em3027 3-0056: rtc core: registered rtc-em3027 as rtc0
iMX6 PCIe PCIe RC mode imx_pcie_pltfm_probe entering.
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1.00: ATA-9: SanDisk SSD U110 32GB, U221000, max UDMA/133
ata1.00: 62533296 sectors, multi 1: LBA48 NCQ (depth 31/32)
ata1.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access     ATA      SanDisk SSD U110 U221 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 62533296 512-byte logical blocks: (32.0 GB/29.8 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sda: sda1 sda2
sd 0:0:0:0: [sda] Attached SCSI disk
PCIE: imx_pcie_pltfm_probe start link up.
usb 2-1: new high speed USB device number 2 using fsl-ehci
hub 2-1:1.0: USB hub found
hub 2-1:1.0: 4 ports detected
link up failed, DB_R0:0x0049fc00, DB_R1:0x08200000!
IMX PCIe port: link down!
i2c i2c-0: Added multiplexed i2c bus 3
i2c i2c-0: Added multiplexed i2c bus 4
gpio-i2cmux gpio-i2cmux: 2 port mux on imx-i2c adapter
lirc_dev: IR Remote Control driver registered, major 252
IR NEC protocol handler initialized
IR RC5(x) protocol handler initialized
IR RC6 protocol handler initialized
IR JVC protocol handler initialized
IR Sony protocol handler initialized
IR RC5 (streamzap) protocol handler initialized
IR LIRC bridge handler initialized
Linux video capture interface: v2.00
imx2-wdt imx2-wdt.0: IMX2+ Watchdog Timer enabled. timeout=60s (nowayout=1)
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
mmc0: SDHCI controller on platform [sdhci-esdhc-imx.0] using DMA
mmc1: SDHCI controller on platform [sdhci-esdhc-imx.2] using DMA
VPU initialized
mxc_asrc registered
Thermal calibration data is 0x5764d669
Thermal sensor with ratio = 180
Anatop Thermal registered as thermal_zone0
anatop_thermal_probe: default cooling device is cpufreq!
caam caam.0: device ID = 0x0a16010000000000
caam caam.0: job rings = 2, qi = 0
alg: No test for authenc(hmac(md5),cbc(aes)) (authenc-hmac-md5-cbc-aes-caam)
caam caam.0: authenc-hmac-md5-cbc-aes-caam
alg: No test for authenc(hmac(sha1),cbc(aes)) (authenc-hmac-sha1-cbc-aes-caam)
caam caam.0: authenc-hmac-sha1-cbc-aes-caam
alg: No test for authenc(hmac(sha224),cbc(aes)) (authenc-hmac-sha224-cbc-aes-caam)
caam caam.0: authenc-hmac-sha224-cbc-aes-caam
alg: No test for authenc(hmac(sha256),cbc(aes)) (authenc-hmac-sha256-cbc-aes-caam)
mmc0: new high speed SDIO card at address 0001
caam caam.0: authenc-hmac-sha256-cbc-aes-caam
alg: No test for authenc(hmac(md5),cbc(des3_ede)) (authenc-hmac-md5-cbc-des3_ede-caam)
caam caam.0: authenc-hmac-md5-cbc-des3_ede-caam
alg: No test for authenc(hmac(sha1),cbc(des3_ede)) (authenc-hmac-sha1-cbc-des3_ede-caam)
caam caam.0: authenc-hmac-sha1-cbc-des3_ede-caam
alg: No test for authenc(hmac(sha224),cbc(des3_ede)) (authenc-hmac-sha224-cbc-des3_ede-caam)
caam caam.0: authenc-hmac-sha224-cbc-des3_ede-caam
alg: No test for authenc(hmac(sha256),cbc(des3_ede)) (authenc-hmac-sha256-cbc-des3_ede-caam)
caam caam.0: authenc-hmac-sha256-cbc-des3_ede-caam
alg: No test for authenc(hmac(md5),cbc(des)) (authenc-hmac-md5-cbc-des-caam)
caam caam.0: authenc-hmac-md5-cbc-des-caam
alg: No test for authenc(hmac(sha1),cbc(des)) (authenc-hmac-sha1-cbc-des-caam)
caam caam.0: authenc-hmac-sha1-cbc-des-caam
alg: No test for authenc(hmac(sha224),cbc(des)) (authenc-hmac-sha224-cbc-des-caam)
caam caam.0: authenc-hmac-sha224-cbc-des-caam
alg: No test for authenc(hmac(sha256),cbc(des)) (authenc-hmac-sha256-cbc-des-caam)
caam caam.0: authenc-hmac-sha256-cbc-des-caam
caam caam.0: cbc-aes-caam
caam caam.0: cbc-3des-caam
caam caam.0: cbc-des-caam
mmc1: host does not support reading read-only switch. assuming write-enable.
mmc1: new high speed SDHC card at address eb42
mmcblk0: mmc1:eb42 SD08G 7.42 GiB
 mmcblk0: p1 p2
platform caam_jr.0: registering rng-caam
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
usbcore: registered new interface driver snd-usb-audio
mxc_spdif mxc_spdif.0: MXC SPDIF Audio
_regulator_get: 2-001a supply AVDD not found, using dummy regulator
_regulator_get: 2-001a supply HPVDD not found, using dummy regulator
_regulator_get: 2-001a supply DCVDD not found, using dummy regulator
_regulator_get: 2-001a supply DBVDD not found, using dummy regulator
imx_wm8731_init: success
asoc: wm8731-hifi <-> imx-ssi.1 mapping ok
asoc: mxc-spdif <-> imx-spdif-dai.0 mapping ok
ALSA device list:
  #0: wm8731-audio
  #1: imx-spdif
NET: Registered protocol family 26
TCP cubic registered
NET: Registered protocol family 17
can: controller area network core (rev 20090105 abi 8)
NET: Registered protocol family 29
can: raw protocol (rev 20090105)
can: broadcast manager protocol (rev 20090105 t)
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP filters: protocol multicast
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
lib80211: common routines for IEEE802.11 drivers
HDMI CEC initialized
mxc_vdoa mxc_vdoa: i.MX Video Data Order Adapter(VDOA) driver probed
mxc_sdc_fb mxc_sdc_fb.0: register mxc display driver hdmi
mxc_hdmi mxc_hdmi: Detected HDMI controller 0x13:0xa:0xa0:0xc1
imx-ipuv3 imx-ipuv3.0: IPU DMFC DP HIGH RESOLUTION: 1(0,1), 5B(2~5), 5F(6,7)
Console: switching to colour frame buffer device 240x67
mxc_sdc_fb mxc_sdc_fb.1: register mxc display driver dvi
_regulator_get: get() with no identifier
mxc_hdmi_soc mxc_hdmi_soc.0: MXC HDMI Audio
asoc: mxc-hdmi-soc <-> imx-hdmi-soc-dai.0 mapping ok
mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video16
mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video17
mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video18
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
Bus freq driver module loaded
Bus freq driver Enabled
mxc_dvfs_core_probe
DVFS driver module loaded
regulator_init_complete: ads7846_vcc: incomplete constraints, leaving on
rtc-em3027 3-0056: setting system clock to 2014-04-15 15:11:20 UTC (1397574680)
EXT3-fs (mmcblk0p2): error: couldn't mount because of unsupported optional features (240)
EXT2-fs (mmcblk0p2): error: couldn't mount because of unsupported optional features (244)
EXT4-fs (mmcblk0p2): recovery complete
EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 179:2.
devtmpfs: mounted
Freeing init memory: 236K
INIT: version 2.88 booting
INIT: /etc/inittab[70]: action field too long
[info] Using makefile-style concurrent boot in runlevel S.
[....] Starting the hotplug events dispatcher: udevdudevd[1467]: starting version 175
. ok
[....] Synthesizing the initial hotplug events...ads7846 spi0.1: touchscreen, irq 303
input: ADS7846 Touchscreen as /devices/platform/imx6q-ecspi.0/spi_master/spi0/spi0.1/input/input1
done.
[....] Waiting for /dev to be fully popuBluetooth: vendor=0x2df, device=0x911a, class=255, fn=2
lated...cfg80211: Calling CRDA to update world regulatory domain
cfg80211: World regulatory domain updated:
cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
cfg80211:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211:     (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
cfg80211:     (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
cfg80211:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211:     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
mwifiex_sdio mmc0:0001:1: WLAN FW already running! Skip FW download
mwifiex_sdio mmc0:0001:1: WLAN FW is active
mwifiex_sdio mmc0:0001:1: driver_version = mwifiex 1.0 (14.66.9.p96)
done.
Starting fake hwclock: loading system time.
Unable to read saved clock information: /etc/fake-hwclock.data does not exist
[ ok ] Setting parameters of disc: (none).
[ ok ] Activating swap...done.
EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[ ok ] Cleaning up temporary files... /tmp.
[ ok ] Activating lvm and md swap...done.
[....] Checking file systems...fsck from util-linux 2.20.1
done.
[ ok ] Mounting local filesystems...done.
[ ok ] Activating swapfile swap...done.
[ ok ] Cleaning up temporary files....
[ ok ] Setting kernel variables ...done.
[....] Configuring network interfaces...NET: Registered protocol family 10
Internet Systems Consortium DHCP Client 4.2.2
Copyright 2004-2011 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

eth0: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=1:00, irq=-1)
ADDRCONF(NETDEV_UP): eth0: link is not ready
Listening on LPF/eth0/00:01:c0:14:9d:2a
Sending on   LPF/eth0/00:01:c0:14:9d:2a
Sending on   Socket/fallback
DHCPREQUEST on eth0 to 255.255.255.255 port 67
PHY: 1:00 - Link is Up - 100/Full
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 10.21.21.1
bound to 10.21.21.78 -- renewal in 147505 seconds.
done.
[ ok ] Cleaning up temporary files....
[....] Setting up ALSA...amixer: Invalid command!
done.
[info] Setting console screen modes and fonts.
setterm: cannot (un)set powersave mode: Invalid argument
[ ok ] Setting up X socket directories... /tmp/.X11-unix /tmp/.ICE-unix.
INIT: Entering runlevel: 2
[info] Using makefile-style concurrent boot in runlevel 2.
[ ok ] Starting enhanced syslogd: rsyslogd.
[ ok ] Starting periodic command scheduler: cron.
[ ok ] Starting system message bus: dbus.
saned disabled; edit /etc/default/saned
[ ok ] Starting network connection manager: NetworkManager.

kali_utilite_full_boot_log.txt (19,630 bytes)   

Activities

steev

steev

2014-04-14 20:41

manager   ~0001693

Do you have a cable plugged in to eth0? Or in to eth1, or in neither?

Mister_X

Mister_X

2014-04-14 22:53

reporter   ~0001696

Cable attached to eth0. No cable attached to eth1.

steev

steev

2014-04-15 00:32

manager   ~0001698

Very interesting - I've not seen this issue here, and I'm not near my utilite for a couple more weeks - would it be possible to attach a full boot log from the console?

If you're using screen as your console method (screen /dev/ttyUSB0 115200) then before powering on the Utilite, you can hit Ctrl+a, and then type ":log" without quotes, and it will save whatever happens in that screen session to screenlog.0 or something around that.

Also, I'm not entirely sure that their kernel supports output on both hdmi and dvi, I believe currently only hdmi is supported, but I need to see what your boot arguments are set to - which I'll get from the full log.

What type of monitor are you plugged in to, and what are the resolutions it supports?

Mister_X

Mister_X

2014-04-15 04:21

reporter   ~0001699

Yes. I will provide the whole output tomorrow evening.

From what I read, it only supports the first HDMI (which is DVI) and on Ubuntu, I got a weird resolution, 1300something instead of 1920. I have no idea for Kali since all I got was from the console connection on COM1.

It's a TV that is plugged. The display stays blank for Kali.

Mister_X

Mister_X

2014-04-16 00:25

reporter   ~0001704

Is there any way I can give you access to my Utilite Pro box so that
we can tackle that issue? With TeamViewer for example.

Mister_X

Mister_X

2014-04-22 00:53

reporter   ~0001717

Do you have any tips you can give me to debug that issue on my own?

steev

steev

2014-04-22 02:39

manager   ~0001719

Hmm, okay, one thing that jumps out at me from the log -

INIT: /etc/inittab[70]: action field too long

What is line 70 in your /etc/inittab file on the sdcard? I think what's happening there is that whatever is on line 70 is incorrectly formatted, and that's what is supposed to start the serial console on ttymxc3 and since it's improperly formatted, it can't/won't start it.

Second, which port are you plugged in to on the Utilite for HDMI? If memory serves, I use the one on the far left (looking at it from the front) - can you plug in to there? What I'm not seeing in the log is where HDMI pulls up the EDID information which makes me think you have hdmi plugged in to the wrong port.

steev

steev

2014-04-22 02:40

manager   ~0001720

I don't have teamviewer installed at the moment, but I can definitely do that if you'd like. I won't be around much tomorrow (Tuesday) during the day time, but in the evening if you ping me (steev) on IRC via a private message, we can definitely get something going. I'm currently in Eastern time zone

Mister_X

Mister_X

2014-04-23 23:47

reporter   ~0001727

/etc/inittab is just one line without any space or other blank character at the end of it (there is just one empty blank line after it) and it's the default value that comes with the package:
T1:23:/sbin/agetty -L ttymxc3 115200 vt100

It works when plugging to the far left HDMI port. I was using the DVI-D port. I think the first time I booted Ubuntu, the HDMI didn't output anything and I used the DVI-D port which worked. I expected the same for Kali.

I think it worth mentioning which port to connect to in the tutorial.

The X resolution is 1920p but the display resolution seems to be limited to 1366x768 (or something in the 1300 range). I don't really know how to explain it but that also happens when you request an area way larger than the resolution your monitor accept, the display area is limited to what your screen can display and you have to move the mouse to one of the corner to make that area move to reach the menus and other stuff.
I don't know if it's a limitation of the TV I used or the HDMI chip or the driver (the same thing happens with the Ubuntu loaded on the Utilite, even after an update).

g0tmi1k

g0tmi1k

2018-01-29 11:17

administrator   ~0007962

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-04-11 05:01 Mister_X New Issue
2014-04-11 05:01 Mister_X File Added: utilite_fail_boot.txt
2014-04-14 20:41 steev Note Added: 0001693
2014-04-14 22:53 Mister_X Note Added: 0001696
2014-04-15 00:32 steev Note Added: 0001698
2014-04-15 04:21 Mister_X Note Added: 0001699
2014-04-16 00:24 Mister_X File Added: kali_utilite_full_boot_log.txt
2014-04-16 00:25 Mister_X Note Added: 0001704
2014-04-22 00:53 Mister_X Note Added: 0001717
2014-04-22 02:39 steev Note Added: 0001719
2014-04-22 02:40 steev Note Added: 0001720
2014-04-23 23:47 Mister_X Note Added: 0001727
2014-05-12 17:16 xploitx Issue cloned: 0001207
2018-01-29 11:17 g0tmi1k Assigned To => g0tmi1k
2018-01-29 11:17 g0tmi1k Status new => closed
2018-01-29 11:17 g0tmi1k Resolution open => suspended
2018-01-29 11:17 g0tmi1k Note Added: 0007962