03-20-2009, 11:10 PM | #61 | ||
Master
Join Date: Jul 2008
Location: South Central USA
Posts: 260
|
Hi Hally... I am using my little loader script.
create the following file in your regnum directory rolaucher.sh Quote:
Quote:
The same thing happened to me on a fresh install until I starting using this script again... this smells of regression from the memory leeks that caused me to write this little script to begin with. I also have libxtc installed.. find a howto here: http://regnumonlinegame.com/forum/sh...ad.php?t=31371 Hope this helps .. -onemyndseye Last edited by onemyndseye; 03-20-2009 at 11:23 PM. |
||
03-21-2009, 10:48 AM | #62 |
Pledge
Join Date: Jul 2007
Posts: 32
|
So nice ! It works perfectly well with your script !
Im also using libxtc (thanks to your how to ...) |
03-22-2009, 07:08 AM | #63 |
Initiate
Join Date: Aug 2008
Location: The Desert, The Mountains, The Sky
Posts: 152
|
Part of this segmentation fault I believe is that the Linux client is not geared like the windows client and some function calls falling to individual drivers are handled differently, ie. causing users to do work arounds to try and get things to work because they aren't as well supported as the Windows drivers. Since I have some experience fiddling around with Ubuntu variants this post will be more geared toward them:
While trying to help some individuals with the i965 graphics chipset we modified their Xorg config file to utilize the "intel" driver as outlined in the following link: https://bugs.launchpad.net/ubuntu/+s...el/+bug/252094 Because it is more than just Regnum that has issues with these chipsets it maybe a wait until Jaunty hits final that the newer drivers intel/mesa interweave will function properly for an average Windows user that is making the switch to linux (ie. a person not familiar with linux at all, just trying to get their shit to work). When trying to help troubleshoot their systems their original Xorg conf files did not indicate the driver to be used and for some reason Regnum loaded and played prior to this segmentation issue. These individuals were able to play Regnum prior to the updates and then Regnum would not load after the update. When the XOrg pointed towards the correct Intel driver in the XOrg file, Regnum would start back up, but still crashes. When the XOrg conf file was switched to legacy mode for compatibility Regnum reports unsupported video card. If you can't wait for Jaunty and want to check out the updated Mesa for yourself and add in the latest Intel Drivers you can do so at the following links: Mesa 7.3 (it did update Intel DRI to use GEM and DRI2, with "Assorted i965 driver fixes" - though 7.2 and 7.3 both implement OpenGL2.1) Compile and Depends, if you rather look for Ubuntu DEB packages you can find them here on the resulting binaries tab. Intel Drivers (Experimental): Ubuntu Intel Drivers 2.6.1 and Ubuntu Intel DBG 2.6.1 If you are unsure/uncomfortable with modifying your system it maybe prudent for you to wait until Jaunty is released and do a dist-upgrade using APT. If you modify you do so at your own risk. Unfortunately at this time Regnums requirements state Ati or NVIDIA and make no mention of Intel. Also most of the Intel Chipsets are on the experimental list for NGD and is probably why they aren't commenting on the forums. While Jaunty (ubuntu version 9.04) will introduce new drivers, it does not mean RO will work with it fine. If your other 3d games are working with your Intel chipset with the way your linux box is configured (ie. UrbanTerror, TORCS, Tilerace), then likely it is a coding of the NG3d engine and it's function calls per driver causing the issue; ie. Intel is still on DRI1 and NVIDIA on DRI2 so NGD programs for DRI2 without leaving a legacy call back for DRI1 leaving Intel users in the dark. This issue may never be fully resolved if the Intel chips aren't given the same attention as the main stream gaming cards receive and individual fixes to this problem providing work arounds may not work next update. Some regressions to previous versions of Ubuntu may work for sometime if the NG3d code referenced a replaced/updated package that does not follow the same PATH line. But it would not be a solid fix. Unfortunately I only have computers with NVIDIA chipsets and are unable to troubleshoot or view the back traces for the segmentation fault. If you guys want to shoot me a copy you can send a copy to my remailer address: syd@sydrex.tk and I will get to it when I can and see what I can make of it. If you take the step to install new Mesa and Intel drivers please report back here for other users to learn if it works or not.
__________________
Doing something maybe nothing, maybe nothing with something. Last edited by Sydonay_Rex; 03-22-2009 at 07:56 AM. |
03-22-2009, 09:28 AM | #64 |
Master
Join Date: Jul 2008
Location: South Central USA
Posts: 260
|
Thanks.. alot of good info there...
However atleast for ATI users there is no end in sight with Jaunty.. same problem persists in Jaunty even with the fixes repo you list there. I so suspect that it will solve the problem for atleast some intel users though. |
03-22-2009, 07:46 PM | #65 |
Initiate
Join Date: Aug 2008
Location: The Desert, The Mountains, The Sky
Posts: 152
|
For you guys with ATI I feel for ya. I was using ATI back when they switched to Radeon during the 7k series and I was using Suse 7, it was the largest pain in the ass I had to go through to get 3d support since there wasn't much of any official support when those cards first came out. Thats why I made the switch to NVIDIA later when I heard NVIDIA was actually supporting their cards in Linux.
Unfortunately it seems to almost be reverting to that way since distros like Arch are refusing to carry the ATI drivers. I'm not saying ditch ATI and go buy NVIDIA I am just saying you guys maybe in for a bumpy ride until it all gets sorted out.
__________________
Doing something maybe nothing, maybe nothing with something. |
03-23-2009, 01:39 PM | #66 |
Master
Join Date: Jul 2008
Location: South Central USA
Posts: 260
|
"...I'm not saying ditch ATI and go buy NVIDIA..."
I am without doubt.... however my laptop cannot be changed My home PC has a NVIDIA 9600GT |
03-23-2009, 03:18 PM | #67 |
Initiate
Join Date: Aug 2008
Location: The Desert, The Mountains, The Sky
Posts: 152
|
onemyndseye, you may have an MXM based laptop (ie. your video is on a card rather than integrated into the mobo). If your laptop is MXM based you can check out http://www.mxm-upgrade.com/store.html and they may have a solution for you. Little known secret that for some of these newer laptops with NVIDIA and ATI you can purchase the card separate rather than getting a new laptop.
__________________
Doing something maybe nothing, maybe nothing with something. |
03-23-2009, 04:36 PM | #68 |
Baron
Join Date: Nov 2007
Location: Not where it looks like, to either of us.
Posts: 706
|
Actually nVidia don't use DRI at all. They have their own system....
__________________
If you can't detect sarcasm yourself, please pay attention when it's pointed out to you.
Arathael :: Wyrd Sceote :: Gwn M'ger — Soul Taker, Imperial Guard of Ignis |
03-24-2009, 05:21 AM | #69 |
Initiate
Join Date: Aug 2008
Location: The Desert, The Mountains, The Sky
Posts: 152
|
fudje that was just figurative example, yes NVIDIA has supplied a work around for their chipsets away from DRI just about since they started supporting linux with proprietary drivers. The point I was getting at is that this game is tailored to the more main stream gamer graphics card rather than the middle ground affordable pc or laptop that contains intel graphics chipsets that run on linux.
I was getting at is that unless NGD does the legwork and starts officially supporting other chipsets besides ATI and NVIDIA, this problem will likely continue and may manifest itself in other areas later down the road.
__________________
Doing something maybe nothing, maybe nothing with something. |
04-06-2009, 05:58 AM | #70 |
Pledge
Join Date: Oct 2008
Posts: 1
|
Supporting the mesa stack would be good
|
|
|