LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices


Reply
  Search this Thread
Old 03-26-2010, 03:28 PM   #91
MTK358
LQ 5k Club
 
Registered: Sep 2009
Posts: 6,443

Original Poster
Blog Entries: 3

Rep: Reputation: 723Reputation: 723Reputation: 723Reputation: 723Reputation: 723Reputation: 723Reputation: 723

I noticed that the files giving the push/pop errors are assemply language (.S). I searched for .S files, and I found that they are all and a directory called "X86" (my CPU is x86_64)!

I wonder if there are x86_64 alternatives, or is there some way to translate them?

Code:
$ find -name '*.S'
./src/metisse-0.4.1/xserver/GL/mesa/X86/sse_xform3.S
./src/metisse-0.4.1/xserver/GL/mesa/X86/3dnow_xform1.S
./src/metisse-0.4.1/xserver/GL/mesa/X86/x86_cliptest.S
./src/metisse-0.4.1/xserver/GL/mesa/X86/x86_xform4.S
./src/metisse-0.4.1/xserver/GL/mesa/X86/mmx_blend.S
./src/metisse-0.4.1/xserver/GL/mesa/X86/x86_xform2.S
./src/metisse-0.4.1/xserver/GL/mesa/X86/3dnow_normal.S
./src/metisse-0.4.1/xserver/GL/mesa/X86/3dnow_xform2.S
./src/metisse-0.4.1/xserver/GL/mesa/X86/glapi_x86.S
./src/metisse-0.4.1/xserver/GL/mesa/X86/common_x86_asm.S
./src/metisse-0.4.1/xserver/GL/mesa/X86/x86_xform3.S
./src/metisse-0.4.1/xserver/GL/mesa/X86/sse_xform1.S
./src/metisse-0.4.1/xserver/GL/mesa/X86/sse_normal.S
./src/metisse-0.4.1/xserver/GL/mesa/X86/3dnow_xform3.S
./src/metisse-0.4.1/xserver/GL/mesa/X86/sse_xform2.S
./src/metisse-0.4.1/xserver/GL/mesa/X86/sse_xform4.S
./src/metisse-0.4.1/xserver/GL/mesa/X86/3dnow_xform4.S
 
Old 03-26-2010, 07:32 PM   #92
lupusarcanus
Senior Member
 
Registered: Mar 2009
Location: USA
Distribution: Arch
Posts: 1,022
Blog Entries: 19

Rep: Reputation: 146Reputation: 146
Quote:
Originally Posted by Metisse Website.
Intel CPUs don't understand AMD's 3DNow assembly.
Disable the glx extension when building metisse
to work around the issue.
Look at ./configure --help for some useful info.
 
Old 03-26-2010, 07:41 PM   #93
MTK358
LQ 5k Club
 
Registered: Sep 2009
Posts: 6,443

Original Poster
Blog Entries: 3

Rep: Reputation: 723Reputation: 723Reputation: 723Reputation: 723Reputation: 723Reputation: 723Reputation: 723
Code:
 --enable-glx            enable GLX extension (default: disabled)
 --enable-glx-x86        enable GLX extension with x86 optimization (default:
                          disabled)
So they aren't enabled by default. Let's see the PKGBUILD, and look what I found here:

Code:
./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var \
   --libexecdir=/usr/lib/ --enable-mmx --enable-glx-x86 --with-x
  make CC='gcc' || return 1
  make CC='gcc' DESTDIR="$pkgdir" install
 
Old 03-26-2010, 07:49 PM   #94
MTK358
LQ 5k Club
 
Registered: Sep 2009
Posts: 6,443

Original Poster
Blog Entries: 3

Rep: Reputation: 723Reputation: 723Reputation: 723Reputation: 723Reputation: 723Reputation: 723Reputation: 723
YES!!!!!!!

I tried changing it to "--enable-glx" instead of "--enable-glx-x86" and it worked!

When I tried installing the package, it failed because it conflicted with FVWM (after all, Metisse is a modded FVWM). But it installed perfectly when I removed FVWM.

LET'S TRY IT!
 
Old 03-26-2010, 07:55 PM   #95
lupusarcanus
Senior Member
 
Registered: Mar 2009
Location: USA
Distribution: Arch
Posts: 1,022
Blog Entries: 19

Rep: Reputation: 146Reputation: 146
Quote:
Originally Posted by MTK358 View Post
YES!!!!!!!

I tried changing it to "--enable-glx" instead of "--enable-glx-x86" and it worked!

When I tried installing the package, it failed because it conflicted with FVWM (after all, Metisse is a modded FVWM). But it installed perfectly when I removed FVWM.

LET'S TRY IT!
WOOHOO!!!! Party at MTK's Window manager!!!!!
 
Old 03-26-2010, 08:00 PM   #96
MTK358
LQ 5k Club
 
Registered: Sep 2009
Posts: 6,443

Original Poster
Blog Entries: 3

Rep: Reputation: 723Reputation: 723Reputation: 723Reputation: 723Reputation: 723Reputation: 723Reputation: 723
It doesn't work

Code:
$ startmetisse
/usr/bin/xmodmap:  unable to open display ''
xdpyinfo:  unable to open display "".
Invalid geometry -ac
use: X [:<display>] [option]
-a #                   mouse acceleration (pixels)
-ac                    disable access control restrictions
-audit int             set audit trail level
-auth file             select authorization file
bc                     enable bug compatibility
-br                    create root window with black background
+bs                    enable any backing store support
-bs                    disable any backing store support
-c                     turns off key-click
c #                    key-click volume (0-100)
-cc int                default color visual class
-co file               color database file
-core                  generate core dump on fatal error
-dpi int               screen resolution in dots per inch
-deferglyphs [none|all|16] defer loading of [no|all|16-bit] glyphs
-f #                   bell base (0-100)
-fc string             cursor font
-fn string             default font name
-fp string             default font path
-help                  prints message with these options
-I                     ignore all remaining arguments
-ld int                limit data space to N Kb
-lf int                limit number of open files to N
-ls int                limit stack space to N Kb
-nolock                disable the locking mechanism
-logo                  enable logo in screen saver
nologo                 disable logo in screen saver
-nolisten string       don't listen on protocol
-p #                   screen-saver pattern duration (minutes)
-pn                    accept failure to listen on all ports
-nopn                  reject failure to listen on all ports
-r                     turns off auto-repeat
r                      turns on auto-repeat 
-render [default|mono|gray|color] set render color alloc policy
-s #                   screen-saver timeout (minutes)
-su                    disable any save under support
-t #                   mouse threshold (pixels)
-terminate             terminate at server reset
-to #                  connection time out
-tst                   disable testing extensions
ttyxx                  server started from init on /dev/ttyxx
v                      video blanking for screen-saver
-v                     screen-saver without video blanking
-wm                    WhenMapped default backing-store
-x string              loads named extension at init time 
-geometry WxH          set framebuffer width & height
-depth D               set framebuffer depth
-pixelformat format    set pixel format (BGRnnn or RGBnnn)
-udpinputport port     UDP port for keyboard/pointer data
-rfbport port          TCP port for RFB protocol
-rfbwait time          max time in ms to wait for RFB client
-nocursor              don't put up a cursor
-rfbauth passwd-file   use authentication on RFB protocol
-httpd dir             serve files via HTTP from here
-httpport port         port for HTTP
-deferupdate time      time in ms to defer updates (default 40)
-economictranslate     less memory-hungry translation
-desktop name          METISSE desktop name (default x11)
-alwaysshared          always treat new clients as shared
-nevershared           never treat new clients as shared
-dontdisconnect        don't disconnect existing clients when a new non-shared
                       connection comes in (refuse new connection instead)
-viewonly              let clients only to view the desktop
-localhost             only allow connections from localhost
-interface ipaddr      only bind to specified interface address
-inetd                 Xmetisse is launched by inetd
-version               report Xmetisse version on stderr
Start fvwmi with args -d :0 -w metisse://127.0.0.1:1  for FvwmCompositor
[FVWM][main]: <<ERROR>> can't open display 127.0.0.1:1
ERROR: garbage process ID "PID".
Usage:
  kill pid ...              Send SIGTERM to every process listed.
  kill signal pid ...       Send a signal to every process listed.
  kill -s signal pid ...    Send a signal to every process listed.
  kill -l                   List all signal names.
  kill -L                   List all signal names in a nice table.
  kill -l signal            Convert between signal numbers and names.
I wonder what's wrong?

Last edited by MTK358; 03-26-2010 at 08:02 PM.
 
Old 03-26-2010, 08:03 PM   #97
lupusarcanus
Senior Member
 
Registered: Mar 2009
Location: USA
Distribution: Arch
Posts: 1,022
Blog Entries: 19

Rep: Reputation: 146Reputation: 146
Quote:
Originally Posted by MTK358 View Post
It doesn't work

Code:
$ startmetisse
/usr/bin/xmodmap:  unable to open display ''
xdpyinfo:  unable to open display "".
Invalid geometry -ac
use: X [:<display>] [option]
-a #                   mouse acceleration (pixels)
-ac                    disable access control restrictions
-audit int             set audit trail level
-auth file             select authorization file
bc                     enable bug compatibility
-br                    create root window with black background
+bs                    enable any backing store support
-bs                    disable any backing store support
-c                     turns off key-click
c #                    key-click volume (0-100)
-cc int                default color visual class
-co file               color database file
-core                  generate core dump on fatal error
-dpi int               screen resolution in dots per inch
-deferglyphs [none|all|16] defer loading of [no|all|16-bit] glyphs
-f #                   bell base (0-100)
-fc string             cursor font
-fn string             default font name
-fp string             default font path
-help                  prints message with these options
-I                     ignore all remaining arguments
-ld int                limit data space to N Kb
-lf int                limit number of open files to N
-ls int                limit stack space to N Kb
-nolock                disable the locking mechanism
-logo                  enable logo in screen saver
nologo                 disable logo in screen saver
-nolisten string       don't listen on protocol
-p #                   screen-saver pattern duration (minutes)
-pn                    accept failure to listen on all ports
-nopn                  reject failure to listen on all ports
-r                     turns off auto-repeat
r                      turns on auto-repeat 
-render [default|mono|gray|color] set render color alloc policy
-s #                   screen-saver timeout (minutes)
-su                    disable any save under support
-t #                   mouse threshold (pixels)
-terminate             terminate at server reset
-to #                  connection time out
-tst                   disable testing extensions
ttyxx                  server started from init on /dev/ttyxx
v                      video blanking for screen-saver
-v                     screen-saver without video blanking
-wm                    WhenMapped default backing-store
-x string              loads named extension at init time 
-geometry WxH          set framebuffer width & height
-depth D               set framebuffer depth
-pixelformat format    set pixel format (BGRnnn or RGBnnn)
-udpinputport port     UDP port for keyboard/pointer data
-rfbport port          TCP port for RFB protocol
-rfbwait time          max time in ms to wait for RFB client
-nocursor              don't put up a cursor
-rfbauth passwd-file   use authentication on RFB protocol
-httpd dir             serve files via HTTP from here
-httpport port         port for HTTP
-deferupdate time      time in ms to defer updates (default 40)
-economictranslate     less memory-hungry translation
-desktop name          METISSE desktop name (default x11)
-alwaysshared          always treat new clients as shared
-nevershared           never treat new clients as shared
-dontdisconnect        don't disconnect existing clients when a new non-shared
                       connection comes in (refuse new connection instead)
-viewonly              let clients only to view the desktop
-localhost             only allow connections from localhost
-interface ipaddr      only bind to specified interface address
-inetd                 Xmetisse is launched by inetd
-version               report Xmetisse version on stderr
Start fvwmi with args -d :0 -w metisse://127.0.0.1:1  for FvwmCompositor
[FVWM][main]: <<ERROR>> can't open display 127.0.0.1:1
ERROR: garbage process ID "PID".
Usage:
  kill pid ...              Send SIGTERM to every process listed.
  kill signal pid ...       Send a signal to every process listed.
  kill -s signal pid ...    Send a signal to every process listed.
  kill -l                   List all signal names.
  kill -L                   List all signal names in a nice table.
  kill -l signal            Convert between signal numbers and names.
I wonder what's wrong?
NOTHING! It's on their website

Use this instead;
Code:
Xmetisse -geometry 1024x768 -ac :1
# Whatever your resolution is...
Then, let's get the party started with this;
Code:
metisse-start-fvwm -wd :1
TELL ME IF IT IT WORKS!
 
Old 03-26-2010, 08:08 PM   #98
MTK358
LQ 5k Club
 
Registered: Sep 2009
Posts: 6,443

Original Poster
Blog Entries: 3

Rep: Reputation: 723Reputation: 723Reputation: 723Reputation: 723Reputation: 723Reputation: 723Reputation: 723
Quote:
Originally Posted by leopard View Post
Code:
Xmetisse -geometry 1024x768 -ac :1
# Whatever your resolution is...
It segfaulted immediately after the "Starting GLX" step. Maybe I should recompile it, leaving out GLX entirely?

Anyway, I'm done with it for today and will continue tomorrow morning.
 
Old 03-26-2010, 08:12 PM   #99
lupusarcanus
Senior Member
 
Registered: Mar 2009
Location: USA
Distribution: Arch
Posts: 1,022
Blog Entries: 19

Rep: Reputation: 146Reputation: 146
Quote:
Originally Posted by MTK358 View Post
It segfaulted immediately after the "Starting GLX" step. Maybe I should recompile it, leaving out GLX entirely?

Anyway, I'm done with it for today and will continue tomorrow morning.
Damnit. So close.

Look at Xmetisse -help and see if you can disable glx from there.
 
Old 03-27-2010, 07:15 AM   #100
MTK358
LQ 5k Club
 
Registered: Sep 2009
Posts: 6,443

Original Poster
Blog Entries: 3

Rep: Reputation: 723Reputation: 723Reputation: 723Reputation: 723Reputation: 723Reputation: 723Reputation: 723
It does not have a disable GLX option. I will recompile it without the --enable-glx flag.
 
Old 03-27-2010, 07:32 AM   #101
MTK358
LQ 5k Club
 
Registered: Sep 2009
Posts: 6,443

Original Poster
Blog Entries: 3

Rep: Reputation: 723Reputation: 723Reputation: 723Reputation: 723Reputation: 723Reputation: 723Reputation: 723
I recompiled it without GLX. Xmetisse started, but metisse-start-fvwm failed.

Running startmetisse fails the same way it did before.
 
Old 03-27-2010, 11:43 AM   #102
lupusarcanus
Senior Member
 
Registered: Mar 2009
Location: USA
Distribution: Arch
Posts: 1,022
Blog Entries: 19

Rep: Reputation: 146Reputation: 146
What is your video card?
 
Old 03-27-2010, 11:59 AM   #103
lupusarcanus
Senior Member
 
Registered: Mar 2009
Location: USA
Distribution: Arch
Posts: 1,022
Blog Entries: 19

Rep: Reputation: 146Reputation: 146
For the record I've just installed Metisse and ran it fine.

{Intel GMA 950}

The only thing I could suspect at this point is a 64-bit -- 32-bit problem or that you're graphics card doesn't have the correct configuration in Xorg.conf.

For the record do you have the composite extension in your Xorg.conf?
 
Old 03-27-2010, 12:00 PM   #104
MTK358
LQ 5k Club
 
Registered: Sep 2009
Posts: 6,443

Original Poster
Blog Entries: 3

Rep: Reputation: 723Reputation: 723Reputation: 723Reputation: 723Reputation: 723Reputation: 723Reputation: 723
Quote:
What is your video card?
ATI Radeon HD4850

Quote:
For the record do you have the composite extension in your Xorg.conf?
No.

EDIT: Here's my xorg.conf (I have a dual-monitor Xrandr setup):

Code:
Section "Device"
	Identifier "Default Device"
	Driver "radeon"
EndSection

Section "Monitor"
	Identifier "DVI-0"
EndSection

Section "Monitor"
	Identifier "DVI-1"
	Option "RightOf" "DVI-0"
EndSection

Section "Screen"
        Identifier "Default Screen"
        SubSection "Display"
                Virtual 2560 1024
        EndSubSection
EndSection
The numbers after "Virtual" are the combined resolution of both screens.

Last edited by MTK358; 03-27-2010 at 12:10 PM.
 
Old 03-27-2010, 12:13 PM   #105
lupusarcanus
Senior Member
 
Registered: Mar 2009
Location: USA
Distribution: Arch
Posts: 1,022
Blog Entries: 19

Rep: Reputation: 146Reputation: 146
Quote:
Originally Posted by MTK358 View Post
ATI Radeon HD4850
That bad boy is your problem. {I think}
Add this to your xorg.conf and give it another whirl

Code:
Section "Module"
  Load  "glx"
  Load  "dri"
  Load  "drm"
EndSection
If using xf86-video-ato, add this;
Code:
Section "Device"
 Identifier "name"                     # your alias
 Driver "radeon"
EndSection
If using xf86-video-radeonhd;
Code:
Section "Device"
 Identifier "name"                     # your alias
 Driver "radeonhd"
 Option "AccelMethod" "exa"            # to enable 2D and Xv acceleration on R6xx/R7xx - default AccelMethod shadowfb
 Option "DRI" "on"                     # to enable 2D and Xv acceleration on R6xx/R7xx - default DRI disabled
EndSection
Add the composite extension;
Code:
Section "Extensions"
        Option "Composite" "Enable"
EndSection
External Links;
http://wiki.archlinux.org/index.php/Xorg
http://wiki.archlinux.org/index.php/ATI

I attached my xorg.conf if you want to take a look at it and compare.
Of course, since I am using Intel I didn't do most the things up there, but maybe it might help...
Attached Files
File Type: txt sample-xorg.conf.txt (2.5 KB, 7 views)
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[Compile kernel] How to compile/install the modules ? frenchn00b Linux - General 1 09-06-2009 03:18 PM
CLFS 5.9 - Glibc compile: suffix of object files, cannot compile Noddegamra Linux From Scratch 3 04-27-2009 12:49 AM
How to get a self-compiled Metisse run automatically in runlevel 5? Vitalie Ciubotaru Linux - Desktop 4 05-22-2007 03:49 PM
Metisse compile Da_Panther Linux - Software 3 02-03-2007 01:56 PM
Nucleo not compiling in Ubuntu 6.06 Da_Panther Linux - Software 2 12-27-2006 07:09 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Software

All times are GMT -5. The time now is 01:21 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration