Page 2 of 4

Posted: Mon Nov 10, 2008 4:39 am
by Pablo
I tried the configuration file you sent (after fixing an error in the aspect ratio value). I could not reproduce the problem.

I am thinking that the problem might be with the unionfs 2.5. I have built a test version with unionfs 2.4: 0.21.0-60b4. Could you give it a try?

Also, if it works, then could you give the previous test build a try: 0.21.0-60b3.

Posted: Tue Nov 11, 2008 5:07 am
by YuChem
No way, nothing works but v. 58.

I have tried both v. 59 and 60b4 - same result. I have even connected another monitor trhough VGA instead of DVI - no luck. Noted that there is no X log in /var/logs

I suspect it has something to do with USB. bowlby mentioned the USB keyboard he had to unconnect.
In my case, once I disconnect USB MCE remote receiver (nothing else remains on USB) MM does not boot at all: hangs at
processing configuration file ...

Posted: Tue Nov 11, 2008 7:17 am
by Pablo
Interesting.

I wonder something was broken in the usb subsytem in either the 2.6.27 or 2.6.26 kernel (the previous version used the 2.6.25 kernel). I will build a version with the 2.6.26 version and upload it to the test directory.

Posted: Tue Nov 11, 2008 8:03 pm
by bowlby
Hi,
to be precise: I wasn't using an USB-keyboard but a PS2. If it's connected at boot, it won't boot; if it's connected afterwards it won't work. It's a cheap 3 euro mini-sized keyboard.

Posted: Tue Nov 11, 2008 8:49 pm
by Pablo
I have uploaded a a test build with the 2.6.26 kernel: 0.21.0-60b5. Could you let me know whether or not that fixes the problem?

If it does not fix the problem, then I can build with the 2.6.25 kernel.

Posted: Wed Nov 12, 2008 5:14 am
by YuChem
Hi Pablo,
Pablo wrote: If it does not fix the problem, then I can build with the 2.6.25 kernel.
I do really appreciate your commitment

Unfortunately, the thing did not work. Symptoms are the same with 60b5.
What I have found is that the themes I had indicated in minimyth.conf file are not mount in /usr/share/mythtv/themes/

I don't know if this can be of use: there is a STDOUT file in the root folder, seem to be an output of the MM Perl script:

Code: Select all

# cat STDOUT
tftp: server error: (1) File not found
tftp: server error: (1) File not found
tftp: server error: (1) File not found
tftp: server error: (1) File not found
Use of uninitialized value $mount_options in concatenation (.) or string at /usr/lib/perl5/site_perl/5.10.0/MiniMyth.pm line 1355.
Use of uninitialized value $mount_options in concatenation (.) or string at /usr/lib/perl5/site_perl/5.10.0/MiniMyth.pm line 1355.
Use of uninitialized value $mount_options in concatenation (.) or string at /usr/lib/perl5/site_perl/5.10.0/MiniMyth.pm line 1355.
Can't use an undefined value as a HASH reference at /usr/lib/perl5/site_perl/5.10.0/MiniMyth.pm line 595, <FILE> line 54.
Dunno, whether this will give you a hint.

Please let me know, I would be able to provide you with all the hints I could squeeze from the system.

Posted: Wed Nov 12, 2008 6:02 am
by Pablo
Could you PM the exact contents of /etc/conf.d/minimyth from your failing frontend?

Posted: Wed Nov 12, 2008 10:21 pm
by emlsnws
Can I cross-reference you guys to this thread where I am having the very same problem?
http://minimyth.org/forum/viewtopic.php?p=9850#9850

Also, I didn't notice it this morning when I had minimyth.script as a shell script, and my lcd not working. Whereas tonight I have the lcd at least kinda working (it is on usb) and a perl minimyth.pm.

Thanks,
Simon.

Posted: Thu Nov 13, 2008 1:51 am
by Airic37
I'm seeing this problem as well. Let me know what details I can provide to help resolve it.

Posted: Thu Nov 13, 2008 2:02 am
by Pablo
If you switch from the perl init scripts to the sh init scripts, does the problem go away (You can do the switch by added MM_INIT_TYPE=sh to your boot line)?

If it does, then the problem is likely somewhere in the new perl init scripts.

Posted: Thu Nov 13, 2008 2:11 am
by Airic37
I just noticed this in STDOUT, could this be the issue?

Can't use an undefined value as a HASH reference at /usr/lib/perl5/site_perl/5.10.0/MiniMyth.pm line 595, <FILE> line 54.

Posted: Thu Nov 13, 2008 2:49 am
by broen
I was running into this problem as well on my ASRock motherboard with 60b3. Startup hangs at "Configuring Video". Backing out to version 59 seemed to fix the problem.

I just did some research with my two frontends on version 59, 60b3, and 60b5. I would do other versions, but can't find much in the "old" stable or test directories. Both use ram version booting PXE. The SP8000 fails the same way ("Configuring Video") for each version; the ASRock ALiveNF7G-HDready succeeds in all cases.

Notice any discrepancy? Yeah, I don't know why the ASRock suddenly decided to work with 60b3. I've tested the only thing I thought had changed and have no idea why it didn't work originally.

BTW, both frontends have a Tira IR Receiver (USB). The SP8000 still fails when the receiver is disconnected. I was unable to test disconnecting the receiver on the ASRock, but I presume it would still work.

The following diagnostic lines are from the failing SP8000.

The last lines of /var/log/messages:

Code: Select all

Nov 12 17:31:04 (none) auth.notice su: + none root:minimyth
Nov 12 17:31:04 (none) auth.notice su: + none root:minimyth
Nov 12 17:31:04 (none) auth.notice su: + none root:minimyth
Nov 12 17:31:04 (none) local0.info minimyth: configuring audio ...
Nov 12 17:31:05 (none) local0.info minimyth: configuring video ...
Nov 13 01:31:05 (none) daemon.info init: no more processes left in this runlevel
Nov 12 17:33:30 (none) auth.info login[2338]: root login on 'pts/0'
lspci -mn:

Code: Select all

00:00.0 "0600" "1106" "0259" "1106" "aa01"
00:00.1 "0600" "1106" "1259" "" ""
00:00.2 "0600" "1106" "2259" "" ""
00:00.3 "0600" "1106" "3259" "" ""
00:00.4 "0600" "1106" "4259" "" ""
00:00.7 "0600" "1106" "7259" "" ""
00:01.0 "0604" "1106" "b198" "" ""
00:0d.0 "0c00" "1106" "3044" -r80 -p10 "1106" "3044"
00:0f.0 "0104" "1106" "3149" -r80 "1106" "aa01"
00:0f.1 "0101" "1106" "0571" -r06 -p8a "1106" "aa01"
00:10.0 "0c03" "1106" "3038" -r81 "1106" "aa01"
00:10.1 "0c03" "1106" "3038" -r81 "1106" "aa01"
00:10.2 "0c03" "1106" "3038" -r81 "1106" "aa01"
00:10.3 "0c03" "1106" "3038" -r81 "1106" "aa01"
00:10.4 "0c03" "1106" "3104" -r86 -p20 "1106" "3104"
00:11.0 "0601" "1106" "3227" "1106" "aa01"
00:11.5 "0401" "1106" "3059" -r60 "1106" "aa01"
00:12.0 "0200" "1106" "3065" -r78 "1106" "0102"
01:00.0 "0300" "1106" "3118" -r02 "1106" "3118"
Running "mm_service x start" doesn't seem to produce any output. Perhaps I'm doing something wrong?

My xorg.conf does not include "@NVIDIA_TRUE@" as it's a via chipset.

cat /STDOUT:

Code: Select all

tftp: server error: (1) File not found
tftp: server error: (1) File not found
tftp: server error: (1) File not found
tftp: server error: (1) File not found
tftp: server error: (1) File not found
Can't use an undefined value as a HASH reference at /usr/lib/perl5/site_perl/5.10.0/MiniMyth.pm line 595, <FILE> line 21.
I'll check out MM_INIT_TYPE=sh now, or I can try something else if you like.

Cheers,
Broen

Posted: Thu Nov 13, 2008 2:50 am
by Airic37
Pablo wrote:If you switch from the perl init scripts to the sh init scripts, does the problem go away (You can do the switch by added MM_INIT_TYPE=sh to your boot line)?

If it does, then the problem is likely somewhere in the new perl init scripts.
Thanks, this does "fix" the problem. Anything else I can do to help troubleshoot the perl scripts?

Posted: Thu Nov 13, 2008 3:08 am
by broen
MM_INIT_TYPE=sh fixes the problem for me as well on 59, 60b3 and 60b5.

By the way, I was running 0.20.2-60b2 last week without the MM_INIT_TYPE line "fix". So this problems seems to only affect the 0.21 branch.

Cheers,
Broen

Posted: Thu Nov 13, 2008 8:18 am
by scooter
Adding MM_INIT_TYPE=sh to the boot line fixed it for me as well.
This was with 60b5.

Before that I was able to start x manually, but lirc was dead.


I'm running:
VIA EPIA CN13000G Mini-ITX Mainboard (CN13000G)

Scott