new to minimyth - possible video conf problem

Help with booting MiniMyth

Moderator: Pablo

Post Reply
windswept321
New Member
Posts: 4
Joined: Wed Dec 09, 2009 2:45 am

new to minimyth - possible video conf problem

Post by windswept321 » Mon Dec 28, 2009 3:22 am

I'm trying to get the ram version of minimyth working with a HP t5000 series thin client using a Geforce 5200 pci card with s-video tv out.

The box will fully load but, instead of the gui, after loading it gives a flashing underline cursor on a black screen so I assume this is a video problem.

Here are my video settings from minimyth.conf, I'm not sure if I'm missing anything.

MM_VIDEO_ASPECT_RATIO='16:9'
MM_VIDEO_DEINTERLACER='auto'
MM_X_OUTPUT_TV='auto'
MM_X_TV_TYPE='PAL-I'
MM_X_TV_OUTPUT='SVIDEO'
MM_X_MODE='720x576'

The settings are for the UK. I have tested the box with a 26" lcd screen and an older 44" rear projection tv.

windswept321
New Member
Posts: 4
Joined: Wed Dec 09, 2009 2:45 am

Re: new to minimyth - possible video conf problem

Post by windswept321 » Mon Dec 28, 2009 6:24 pm

Here are logs related to X:

Dec 28 17:08:21 192.168.1.131 minimyth: configuring X ...
Dec 28 17:08:23 192.168.1.131 minimyth: starting X ...
Dec 28 17:08:23 192.168.1.131 minimyth: starting X
Dec 28 17:08:23 192.168.1.131 minimyth: stopping splash screen
Dec 28 17:08:28 192.168.1.131 kernel: Modules linked in: snd_pcm_oss snd_mixer_oss snd_via82xx snd_ac97_codec ac97_bus snd_pcm snd_timer snd_page_alloc snd_mpu401_uart evdev snd_rawmidi nvidia(P) snd_seq_device snd psmouse agpga$
Dec 28 17:08:28 192.168.1.131 kernel: Pid: 4561, comm: X Tainted: P (2.6.31.6 #1) hp t5000 series
Dec 28 17:08:28 192.168.1.131 kernel: EIP: 0060:[<d197d8e4>] EFLAGS: 00013006 CPU: 0
Dec 28 17:08:28 192.168.1.131 kernel: EIP is at cache_flush+0x18/0x1c [nvidia]
Dec 28 17:08:28 192.168.1.131 kernel: EAX: 00000090 EBX: 00000000 ECX: 00000018 EDX: 0a471000
Dec 28 17:08:28 192.168.1.131 kernel: ESI: d197d8cc EDI: 00000000 EBP: 00000001 ESP: c3c27cd0
Dec 28 17:08:28 192.168.1.131 kernel: DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
Dec 28 17:08:28 192.168.1.131 kernel: c1023fab ca412ca0 cd3d6000 cd3d4438 d197db4c 000002d4 ca412ca0 00000000
Dec 28 17:08:28 192.168.1.131 kernel: <0> cd3d4448 d1ca3908 d197c54a 00000001 00000001 d1ca3908 00000001 cb32dc40
Dec 28 17:08:28 192.168.1.131 kernel: <0> ca46b800 00001010 cd4cbe5c d18d15d3 d1ca3908 00000001 00000000 00000000
Dec 28 17:08:28 192.168.1.131 kernel: [<c1023fab>] ? on_each_cpu+0x13/0x1a
Dec 28 17:08:28 192.168.1.131 kernel: [<d197db4c>] ? nv_vm_malloc_pages+0x155/0x1d5 [nvidia]
Dec 28 17:08:28 192.168.1.131 kernel: [<d197c54a>] ? nv_alloc_pages+0x2a5/0x343 [nvidia]
Dec 28 17:08:28 192.168.1.131 kernel: [<d18d15d3>] ? _nv004037rm+0x3b/0x3f [nvidia]
Dec 28 17:08:28 192.168.1.131 kernel: [<d185bb34>] ? _nv005784rm+0x31/0x170 [nvidia]
Dec 28 17:08:28 192.168.1.131 kernel: [<d187162f>] ? _nv003105rm+0x165/0x219 [nvidia]
Dec 28 17:08:28 192.168.1.131 kernel: [<d18718f3>] ? _nv003114rm+0x210/0x62f [nvidia]
Dec 28 17:08:28 192.168.1.131 kernel: [<d1718132>] ? _nv011024rm+0x273/0x3b4 [nvidia]
Dec 28 17:08:28 192.168.1.131 kernel: [<d17284a0>] ? _nv010981rm+0x2c/0x3d [nvidia]
Dec 28 17:08:28 192.168.1.131 kernel: [<d1893a36>] ? _nv008508rm+0xb3/0x238 [nvidia]
Dec 28 17:08:28 192.168.1.131 kernel: [<d18936bd>] ? _nv008192rm+0x53/0x8e [nvidia]
Dec 28 17:08:28 192.168.1.131 kernel: [<d17b8aa7>] ? _nv008375rm+0xb/0xf [nvidia]
Dec 28 17:08:28 192.168.1.131 kernel: [<d18db999>] ? _nv002987rm+0xf6/0x19d [nvidia]
Dec 28 17:08:28 192.168.1.131 kernel: [<d18dc433>] ? _nv002993rm+0x2c9/0x437 [nvidia]
Dec 28 17:08:28 192.168.1.131 kernel: [<d18d71a8>] ? rm_init_adapter+0x8b/0xd9 [nvidia]
Dec 28 17:08:28 192.168.1.131 kernel: [<d197d7b0>] ? nv_kern_open+0x318/0x434 [nvidia]
Dec 28 17:08:28 192.168.1.131 kernel: [<c106341b>] ? chrdev_open+0x112/0x128
Dec 28 17:08:28 192.168.1.131 kernel: [<c1063309>] ? chrdev_open+0x0/0x128
Dec 28 17:08:28 192.168.1.131 kernel: [<c105feda>] ? __dentry_open+0xff/0x1e3
Dec 28 17:08:28 192.168.1.131 kernel: [<c1060054>] ? nameidata_to_filp+0x2a/0x3b
Dec 28 17:08:28 192.168.1.131 kernel: [<c1069dc6>] ? do_filp_open+0x3db/0x703
Dec 28 17:08:28 192.168.1.131 kernel: [<c1070ad3>] ? alloc_fd+0x52/0xb5
Dec 28 17:08:28 192.168.1.131 kernel: [<c105fcde>] ? do_sys_open+0x49/0xe7
Dec 28 17:08:28 192.168.1.131 kernel: [<c105fdc0>] ? sys_open+0x1e/0x23

yalu
New Member
Posts: 4
Joined: Mon Dec 21, 2009 8:50 pm

Re: new to minimyth - possible video conf problem

Post by yalu » Fri Jan 01, 2010 6:20 pm

The video driver you're using is causing your kernel to oops. Which is rather annoying, because the video driver you're using is closed source:
Dec 28 17:08:28 192.168.1.131 kernel: Pid: 4561, comm: X Tainted: P (2.6.31.6 #1) hp t5000 series
Even more annoying so because the open source nvidia driver are basically good enough to move windows around or play the odd movie but not much beyond it (that's what you get for buying nvidia).

So, you could try using those.

windswept321
New Member
Posts: 4
Joined: Wed Dec 09, 2009 2:45 am

Re: new to minimyth - possible video conf problem

Post by windswept321 » Thu Jan 07, 2010 11:46 am

Thanks for the reply, you've saved me from yet more wasted effort on this card! I'm guessing i's faulty - it runs VERY hot (even for passively cooled) and doesn't seem able to boot into a ubuntu live cd either.

Post Reply