Page 1 of 1

segfault with CLE266 on ram-minimyth-0.25.2-81

Posted: Mon Nov 12, 2012 12:41 pm
by mattj
I realise openchrome is no longer supported, and it's possible I'm the last CLE266 user, but I'm getting a segfault on boot on my one remaining CLE266 frontend with 0.25.2-81 once X tries to start. From what I can see in the log it's segfaulting once it gets to detecting the videoram. I'm not using XVMC-VLD, I just need a working X display - does anyone else have this release working on a CLE266 ? I've got a CX700 based frontend which is using openchrome on 0.25.2-81 and this works fine.

Thanks

Matt

Re: segfault with CLE266 on ram-minimyth-0.25.2-81

Posted: Thu Nov 29, 2012 2:48 am
by Pablo
Does MiniMyth 82 have the same problem?

Re: segfault with CLE266 on ram-minimyth-0.25.2-81

Posted: Sun Dec 02, 2012 3:49 pm
by mattj
Yep, exactly the same behaviour on 82. Gets to :

[1544490.290] (II) Module vbe: vendor="X.Org Foundation"
[1544490.290] compiled for 1.13.0, module version = 1.1.0
[1544490.290] ABI class: X.Org Video Driver, version 13.0
[1544490.290] (II) Loading sub module "int10"
[1544490.290] (II) LoadModule: "int10"
[1544490.291] (II) Loading /usr/lib/xorg/modules/libint10.so
[1544490.291] (II) Module int10: vendor="X.Org Foundation"
[1544490.291] compiled for 1.13.0, module version = 1.0.0
[1544490.291] ABI class: X.Org Video Driver, version 13.0
[1544490.291] (II) CHROME(0): initializing int10

Then no more log output, white cursor in top right hand corner and no X.

Strangely, the process table shows X running :

1520 ? S 0:00 /usr/bin/xinit
1525 tty2 Rs+ 3:59 /usr/bin/X :0.0 vt02 -logverbose 6 -verbose 0

Re: segfault with CLE266 on ram-minimyth-0.25.2-81

Posted: Sun Dec 02, 2012 4:09 pm
by mattj
I think this is actually a problem with my xorg.conf. After some fiddling I now get to :

[1546071.847] (II) CHROME(0): VT1622ModeValid
[1546071.847] (II) CHROME(0): TV standard is PAL. This is a NTSC mode.
[1546071.847] (II) CHROME(0): Mode "640x480" is not supported by TV encoder.
[1546071.847] (II) CHROME(0): Not using default mode "640x480" (unknown reason)

But I'm not sure why it thinks it should use this mode as I clearly have a mode set in my xorg.conf ( which is definitely being used ) :

Modes "720x576Noscale"

I'll keep digging