On Tue, Apr 14, 2009 at 5:07 PM, Michael Sullivan <msulli1...@gmail.com> wrote: <SNIP> > [drm:i915_getparam] *ERROR* Unknown parameter 5 > [drm:i915_getparam] *ERROR* Unknown parameter 5 > mythfrontend[31548]: segfault at 6f732e4c ip 6f732e4c sp bfe0b09c error > 4 > [drm:i915_getparam] *ERROR* Unknown parameter 5 > [drm:i915_getparam] *ERROR* Unknown parameter 5 > mythfrontend[32128]: segfault at 6f732e4c ip 6f732e4c sp bffb8a4c error > 4 > [drm:i915_getparam] *ERROR* Unknown parameter 5 > [drm:i915_getparam] *ERROR* Unknown parameter 5 > mythfrontend[32527]: segfault at 6f732e4c ip 6f732e4c sp bf98041c error > 4 <SNIP> > > Here's what I could gather from Xorg.0.log: > > camille log # grep EE Xorg.0.log > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > (II) Loading extension MIT-SCREEN-SAVER > (EE) Failed to load module "type1" (module does not exist, 0) > (EE) Failed to load module "freetype" (module does not exist, 0) > (EE) AIGLX error: dlopen of /usr/lib/dri/i915_dri.so failed > (/usr/lib/dri/i915_dri.so: cannot open shared object file: No such file > or directory) > (EE) AIGLX: reverting to software rendering > camille log # grep WW Xorg.0.log > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > (WW) The directory "/usr/share/fonts/CID/" does not exist. > (WW) The directory "/usr/share/fonts/OTF" does not exist. > (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or > directory) > (WW) Warning, couldn't open module type1 > (WW) Warning, couldn't open module freetype > (WW) intel(0): libpciaccess reported 0 rom size, guessing 64kB > (WW) intel(0): ESR is 0x00000001, instruction error > (WW) intel(0): Existing errors found in hardware state. > <SNIP>
This is all suggesting to me a fairly serious setup problem, but not necessarily a problem with Myth. You are correct - there is no mythfrontend log file. That would be on your server. My mistake. You still might want to look through the tail of that file but I doubt anything about this will be there. As I said earlier, you should simply remove the freetype line from the fonts section of your xorg.conf file. It's not an issue though. PRobably the same for the type1 font, assuming it's a font. Xorg isn't finding those fonts which jsut means it cannot use them. That's not going to cause a crash in Myth though. I'm not understanding why your system isn't finding the right video driver. It appears hal wants you to run the i915 driver. Is the i915 driver in memory? (lsmod|grep i915) Is it on your system? On the 32-bit machine they are in /usr/lib/dri. Your Xorg.0.log file says they aren't there. Why not? dragonfly ~ # ls -la /usr/lib/dri/ total 8824 drwxr-xr-x 2 root root 4096 2009-04-12 08:37 . drwxr-xr-x 125 root root 77824 2009-04-14 17:22 .. -rwxr-xr-x 1 root root 2150796 2009-04-12 08:37 i810_dri.so -rwxr-xr-x 1 root root 2372108 2009-04-12 08:37 i915_dri.so -rwxr-xr-x 1 root root 2422028 2009-04-12 08:37 i965_dri.so -rwxr-xr-x 1 root root 1978328 2009-04-12 08:37 swrast_dri.so dragonfly ~ # If they really aren't there then you need to build them. They are provided byxf86-video-intel. I don't have them on this AMD64 machine but note that if I wanted to add them then they drag in XvMC which I am suspecting is causing the segfault crash on my wife's 32-bit Intel based machine: lightning mythtv # emerge -pv1 xf86-video-intel These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] app-admin/eselect-xvmc-0.1 0 kB [ebuild N ] x11-libs/libXvMC-1.0.4 USE="-debug" 220 kB [ebuild N ] x11-drivers/xf86-video-intel-2.6.3-r1 USE="dri -debug" 772 kB Total: 3 packages (3 new), Size of downloads: 992 kB lightning mythtv # I am curious as to whether this matters. xvmc is one of the rendering technologies and is pretty much default with Myth. On my wife's machine neither implementation is selected. Possibly that's part of the problem on her machine. I'll have to play with that a bit: dragonfly ~ # eselect xvmc list Available XvMC implementations ( * is current ): [1] xorg-x11 [2] intel dragonfly ~ # I don't know what other clues to give you. I'm going back to xorg-1.3 as we speak to see if I can get her machine working again. I'll let you know how it goes. - Mark
