X won't start

Help with booting MiniMyth

Moderator: Pablo

Post Reply
roundel
Member
Posts: 13
Joined: Wed Jun 24, 2009 12:45 pm

X won't start

Post by roundel » Sat Jan 19, 2013 2:25 pm

I've just returned to Minimyth after a couple of years absence or so, and I'm struggling to get my Zotac IONITX box to boot.

I'm running ram-minimyth-0.25.0-80 booting using PXELinux.

I get the blue screen with the progress at the bottom, until "Starting X..." and then the screen goes black with a flashing cursor top-left for a couple of seconds. Nothing then seeems to start.

My messages are:

Code: Select all

root@dodo:/var/log # cat messages
Jan 12 13:01:33 (none) syslog.info syslogd started: BusyBox v1.20.2
Jan 12 13:01:36 (none) daemon.info init: Entering runlevel: 5
Jan 12 13:01:37 (none) local0.info minimyth: starting splash screen
Jan 12 13:01:37 (none) local0.info minimyth: configuring shared libraries ...
Jan 12 13:01:37 (none) local0.info minimyth: starting loopback network interface ...
Jan 12 13:01:37 (none) daemon.err rpcbind: cannot bind 127.0.0.1 on udp: Address already in use
Jan 12 13:01:38 (none) local0.info minimyth: configuring network interface (one shot) ...
Jan 12 13:01:38 (none) local0.info minimyth: running DHCP client command '/sbin/udhcpc -S -o -O subnet -O router -O dns -O logsrv -O hostname -O domain -O broadcast -O ntpsrv -O tcode -p /var/run/udhcpc.pid -s /etc/udhcpc.script -i eth0 -q > /var/log/udhcpc 2>&1'.
Jan 12 13:01:38 (none) daemon.info udhcpc[337]: udhcpc (v1.20.2) started
Jan 12 13:01:38 (none) daemon.info udhcpc[337]: Sending discover...
Jan 12 13:01:41 (none) daemon.info udhcpc[337]: Sending discover...
Jan 12 13:01:44 (none) daemon.info udhcpc[337]: Sending discover...
Jan 12 13:02:07 (none) daemon.info udhcpc[337]: Sending discover...
Jan 12 13:02:07 (none) daemon.info udhcpc[337]: Sending select for 192.168.1.28...
Jan 12 13:02:07 (none) daemon.info udhcpc[337]: Lease of 192.168.1.28 obtained, lease time 21600
Jan 12 13:02:07 (none) local0.info minimyth: fetching configuration file  ...
Jan 12 13:02:07 (none) local0.info minimyth: fetching 'confro:/minimyth.conf': local file will be '/etc/minimyth.d/minimyth.conf'.
Jan 12 13:02:07 (none) local0.info minimyth: fetching 'confro:/minimyth.conf': URL 'tftp://192.168.1.24/PXEClient/conf/dodo/minimyth.conf' not fetched (it may not exist).
Jan 12 13:02:07 (none) local0.info minimyth: fetching 'confro:/minimyth.conf': URL 'tftp://192.168.1.24/PXEClient/conf/default/minimyth.conf' fetched.
Jan 12 13:02:07 (none) local0.info minimyth: checking for obsolete variables ...
Jan 12 13:02:07 (none) local0.info minimyth: Processing DHCP override variables ...
Jan 12 13:02:08 (none) local0.info minimyth: configuring network interface ...
Jan 12 13:02:08 (none) local0.info minimyth: running DHCP client command '/sbin/udhcpc -S -o -O subnet -O router -O dns -O logsrv -O hostname -O domain -O broadcast -O ntpsrv -O tcode -p /var/run/udhcpc.pid -s /etc/udhcpc.script -i eth0 -r 192.168.1.28 > /var/log/udhcp
Jan 12 13:02:08 (none) daemon.info udhcpc[499]: udhcpc (v1.20.2) started
Jan 12 13:02:08 (none) daemon.info udhcpc[499]: Sending discover...
Jan 12 13:02:08 (none) daemon.info udhcpc[499]: Sending select for 192.168.1.28...
Jan 12 13:02:08 (none) daemon.info udhcpc[499]: Lease of 192.168.1.28 obtained, lease time 21600
Jan 12 13:02:08 (none) local0.info minimyth: Fetching firmware files ...
Jan 12 13:02:08 (none) local0.info minimyth: loading kernel modules (automatic) ...
Jan 12 13:02:12 (none) local0.info minimyth: loading kernel modules (manual) ...
Jan 12 13:02:13 (none) local0.info minimyth: processing configuration file ...
Jan 12 13:02:16 (none) local0.warn minimyth: 'unknown audio device. assuming audio gain is '90'.
Jan 12 13:02:16 (none) local0.warn minimyth: 'unknown audio device. assuming audio device number is '0'.
Jan 12 13:02:16 (none) local0.warn minimyth: 'unknown audio card. assuming audio card number is '0'.
Jan 12 13:02:16 (none) local0.info minimyth: starting system logging ...
Jan 12 13:02:16 (none) syslog.info syslogd exiting
Minimyth.log

Code: Select all

root@dodo:/var/log # cat minimyth.log
Simple mixer control 'Master',0
  Capabilities: pvolume pvolume-joined pswitch pswitch-joined
  Playback channels: Mono
  Limits: Playback 0 - 64
  Mono: Playback 58 [91%] [-6.00dB] [on]
Simple mixer control 'Front',0
  Capabilities: pvolume pswitch
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 64
  Mono:
  Front Left: Playback 58 [91%] [-6.00dB] [on]
  Front Right: Playback 58 [91%] [-6.00dB] [on]
Simple mixer control 'Surround',0
  Capabilities: pvolume pswitch
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 64
  Mono:
  Front Left: Playback 58 [91%] [-6.00dB] [on]
  Front Right: Playback 58 [91%] [-6.00dB] [on]
Simple mixer control 'Center',0
  Capabilities: pvolume pvolume-joined pswitch pswitch-joined
  Playback channels: Mono
  Limits: Playback 0 - 64
  Mono: Playback 58 [91%] [-6.00dB] [on]
Simple mixer control 'LFE',0
  Capabilities: pvolume pvolume-joined pswitch pswitch-joined
  Playback channels: Mono
  Limits: Playback 0 - 64
  Mono: Playback 58 [91%] [-6.00dB] [on]
mount: wrong fs type, bad option, bad superblock on /dev/loop1,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail or so
And the output from dmesg:

Code: Select all

root@dodo:/var/log # dmesg
-
usb 4-1: new full-speed USB device number 2 using ohci_hcd
\
Refined TSC clocksource calibration: 1599.992 MHz.
Switching to clocksource tsc
done.
usb 4-3: new low-speed USB device number 3 using ohci_hcd
VFS: Mounted root (squashfs filesystem) readonly on device 1:0.
Freeing unused kernel memory: 352k freed
usb 4-4: new low-speed USB device number 4 using ohci_hcd
Registering unionfs 2.5.11 (for 3.3.0-rc3)
>udevd[96]: starting version 182
forcedeth 0000:00:0a.0: eth0: no link during initialization
NET: Registered protocol family 17
forcedeth 0000:00:0a.0: eth0: link up
forcedeth 0000:00:0a.0: eth0: link down
forcedeth 0000:00:0a.0: eth0: link up
Real Time Clock Driver v1.12b
loop: module loaded
ppdev: user-space parallel port driver
input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
ACPI: Power Button [PWRB]
input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
ACPI: Power Button [PWRF]
i2c i2c-0: nForce2 SMBus adapter at 0x4d00
ACPI Warning: 0x00004e00-0x00004e3f SystemIO conflicts with Region \_SB_.PCI0.SM00 1 (20120320/utaddress-251)
ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
wmi: Mapper loaded
cdc_acm 4-1:1.0: ttyACM0: USB ACM device
usbcore: registered new interface driver cdc_acm
cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
sr0: scsi3-mmc drive: 62x/62x writer dvd-ram cd/rw xa/form2 cdda pop-up
cdrom: Uniform CD-ROM driver Revision: 3.20
sr 0:0:0:0: Attached scsi CD-ROM sr0
input: CHESEN USB Keyboard as /devices/pci0000:00/0000:00:06.0/usb4/4-3/4-3:1.0/input/input2
generic-usb 0003:0A81:0101.0001: input,hidraw0: USB HID v1.10 Keyboard [CHESEN USB Keyboard] on usb-0000:00:06.0-3/input0
input: CHESEN USB Keyboard as /devices/pci0000:00/0000:00:06.0/usb4/4-3/4-3:1.1/input/input3
generic-usb 0003:0A81:0101.0002: input,hidraw1: USB HID v1.10 Device [CHESEN USB Keyboard] on usb-0000:00:06.0-3/input1
input: HP HP Wireless Keyboard Mouse Kit as /devices/pci0000:00/0000:00:06.0/usb4/4-4/4-4:1.0/input/input4
generic-usb 0003:03F0:0862.0003: input,hidraw2: USB HID v1.11 Keyboard [HP HP Wireless Keyboard Mouse Kit] on usb-0000:00:06.0-4/input0
input: HP HP Wireless Keyboard Mouse Kit as /devices/pci0000:00/0000:00:06.0/usb4/4-4/4-4:1.1/input/input5
generic-usb 0003:03F0:0862.0004: input,hiddev0,hidraw3: USB HID v1.11 Mouse [HP HP Wireless Keyboard Mouse Kit] on usb-0000:00:06.0-4/input1
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
snd_hda_intel 0000:00:08.0: power state changed by ACPI to D0
snd_hda_intel 0000:00:08.0: power state changed by ACPI to D0
ACPI: PCI Interrupt Link [LAZA] enabled at IRQ 20
hda_intel: Disabling MSI
snd_hda_intel 0000:00:08.0: setting latency timer to 64
nvidia: module license 'NVIDIA' taints kernel.
Disabling lock debugging due to kernel taint
ACPI: PCI Interrupt Link [LPMU] enabled at IRQ 23
ACPI: PCI Interrupt Link [SGRU] enabled at IRQ 22
nvidia 0000:03:00.0: setting latency timer to 64
vgaarb: device changed decodes: PCI:0000:03:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
NVRM: loading NVIDIA UNIX x86 Kernel Module  310.19  Wed Nov  7 23:22:09 PST 2012
unionfs: new lower inode mtime (bindex=0, name=certs)
unionfs: new lower inode mtime (bindex=0, name=ssh)
unionfs: new lower inode mtime (bindex=0, name=libexec)
SQUASHFS error: Filesystem uses "lzma" compression. This is not supported
unionfs: new lower inode mtime (bindex=0, name=gdk-pixbuf-2.0)
NVRM: GPU at 0000:03:00: GPU-0965c81a-0da9-ee47-1768-5a53f7b5f476
NVRM: Your system is not currently configured to drive a VGA console
NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
NVRM: requires the use of a text-mode VGA console. Use of other console
NVRM: drivers including, but not limited to, vesafb, may result in
NVRM: corruption and stability problems, and is not supported.
root@dodo:/var/log #   Mono: Playback 58 [91%] [-6.00dB] [on]
I'm connected via HDMI, hence the warning about VGA, which I am currently ignoring, as minimyth.conf is pointing at HDMI.

Can anyone shed a pointer or two to what's going on, please? I'm guessing that the mount error, and squashfs type error are related and the cause of the issue, but not sure where to go to investigate/fix!

Thanks in advance,

John

goldwein
Contributor
Posts: 100
Joined: Sat Sep 11, 2004 6:35 pm

Re: X won't start

Post by goldwein » Tue Mar 05, 2013 2:54 am

Hello John. I am having the same problem. Did you resolve yours?

Thanks,

Joel Goldwein

tsjoender
Contributor
Posts: 87
Joined: Mon Nov 05, 2007 9:45 am
Location: Friesland, The Netherlands

Re: X won't start

Post by tsjoender » Tue Mar 05, 2013 9:24 am

Chances are that X is starting alright, but that it automatically chose an output that was not connected. On my ION motherboard using minimyth.conf's setting:

Code: Select all

MM_X_OUTPUT_HDMI='auto'
gave the behaviour that you describe. Changing this to:

Code: Select all

MM_X_OUTPUT_HDMI='1'
Worked fine as it explicitly defined what output to use and not guess it. If not on HDMI, then similar settings can be used for DVI or VGA.

lofty69
Contributor
Posts: 168
Joined: Fri Mar 02, 2007 5:46 pm
Location: Watching Mythtv via Minimyth

Re: X won't start

Post by lofty69 » Mon Aug 19, 2013 11:37 am

Just updated to the latest .26 build and I'm getting the exact same issue. Chaning the above does not work for me. Anyone have any ideas?

Cheers

Pablo
Site Admin
Posts: 4182
Joined: Tue Dec 14, 2004 2:13 am
Location: La Jolla
Contact:

Re: X won't start

Post by Pablo » Wed Jul 15, 2015 12:09 am

With the latest version I am using, I have not seen the problem. During my update process from 0.24 to 0.27 (I booted and used all the intermediate versions). I will upload a new version soon.

Do you happen to know what version of NVIDIA driver was being used?
MiniMyth running on an Acer ApireRevo 3610 and a Zotac ZBOX-ID80-U. Find out more at my MythTV page.

Post Reply