Ubuntu Karmic Koala 64bit SoD Crash after path

ProgressionMurp said:
Yes you got it running =) I appreciate it. Seems I must run it through the command line though.
Click to expand...

post me a copy of your .bash_profiles file in your home directory. I am assuming you're using the bash shell here. i dont use ubuntu so im not sure what is standard.

some of this you are going to have to google and tweak i would start with looking into your vga chip set

Intel Mobile Intel® GM45 Express Chipset

and wine. you may need to look and see if you can tweak your xorg.conf file for the chipset and mesa as well.
look up eq and wine as well.

last, wine isnt going to use more then 2 gigs its emulating a 32 bit os. you can cut and paste a;

vmstat

if you want me to take a look at memory usage.

basically, the wine doesnt like the 64 dri libraries so we are telling it to use the 32 bit ones instead. and we need to tell it to do so every time you log in so i need the bash_profile file to fix it for you.
 
Last edited:
Can't seem to find the .bash_profiles in my home directory. I found .profile and a .bash_history after I typed view hidden.

Here is the .profile information.

# ~/.profile: executed by the command interpreter for login shells.
# This file is not read by bash(1), if ~/.bash_profile or ~/.bash_login
# exists.
# see /usr/share/doc/bash/examples/startup-files for examples.
# the files are located in the bash-doc package.

# the default umask is set in /etc/profile; for setting the umask
# for ssh logins, install and configure the libpam-umask package.
#umask 022

# if running bash
if [ -n "$BASH_VERSION" ]; then
# include .bashrc if it exists
if [ -f "$HOME/.bashrc" ]; then
. "$HOME/.bashrc"
fi
fi

# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/bin" ] ; then
PATH="$HOME/bin:$PATH"
fi
 
ProgressionMurp said:
Can't seem to find the .bash_profiles in my home directory. I found .profile and a .bash_history after I typed view hidden.

Here is the .profile information.

# ~/.profile: executed by the command interpreter for login shells.
# This file is not read by bash(1), if ~/.bash_profile or ~/.bash_login
# exists.
# see /usr/share/doc/bash/examples/startup-files for examples.
# the files are located in the bash-doc package.

# the default umask is set in /etc/profile; for setting the umask
# for ssh logins, install and configure the libpam-umask package.
#umask 022

export LIBGL_DRIVERS_PATH=/usr/lib32/dri

# if running bash
if [ -n "$BASH_VERSION" ]; then
# include .bashrc if it exists
if [ -f "$HOME/.bashrc" ]; then
. "$HOME/.bashrc"
fi
fi

# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/bin" ] ; then
PATH="$HOME/bin:$PATH"
fi
Click to expand...

ok what i want you to do is run this

cd

cp .profile .profile.bak

touch .profile

open up the empty file and cut and paste the changed text into it and save. should work every time you login. if not its a ubuntu-ism and we'll put it some place else. make sure you use a bare text editor like gedit or something. should be one under accessories.

whoops
 
Last edited:
last, this is a known bug so you should be applying your patches. should be fixed soon.
 
alex@InMotion:~$ cd
alex@InMotion:~$ cp .bash_profile .bash_profile.bak
cp: cannot stat `.bash_profile': No such file or directory
alex@InMotion:~$ touch .bash_profile
alex@InMotion:~$


Hmm and whats this known bug your talking about?

touch .bash_profile command worked however the .bash_profile didn't work.
 
ProgressionMurp said:
Ok so now I see a .bash_profile in my "alex" folder.
Click to expand...

look again i didn't fully read what you said. using the old sh .profiles file name for bash is appealingly atavistic but unique to ubuntu.

the 64 bit dri library thingy is a bug. its even assigned a tracking number so should be fixed soon. if you apply patches and see a wine version update you can test it by commenting out like this

#export LIBGL_DRIVERS_PATH=/usr/lib32/dri

then saving and logging out of ubuntu. then back in and tryng the start up.
 
Last edited:
go to winehq and check out the eq fixes. i am running the same wine server as you and had to make a couple tweaks to get it to work. its not a huge deal.
 
ProgressionMurp said:
So is what you saying I should be able to utilize 4 gigs of ram at some point due to the wine update?
Click to expand...

run

dmesg | grep memory

for me. but yes if the kernel sees the memory, above command, it should. but i would be shocked if you ever get much over 1.5 gigs used with a linux box with eq running, maybe 2 gigs if you run a lot of apps.
 
Ok will do I appreciate all your help so far Boehm. Before I head over you wanted me to copy the edited .profile text from above and replace the original .profile right?

dmesg | grep Memory

alex@InMotion:~$ dmesg | grep Memory
[ 0.000000] Memory: 3939812k/5177344k available (5313k kernel code, 1095944k absent, 141588k reserved, 3011k data, 660k init)
[ 10.640963] yenta_cardbus 0000:38:03.0: pcmcia: parent PCI bridge Memory window: 0xf2600000 - 0xf26fffff
[ 10.640965] yenta_cardbus 0000:38:03.0: pcmcia: parent PCI bridge Memory window: 0xc0000000 - 0xc7ffffff
[ 10.780990] yenta_cardbus 0000:38:03.1: pcmcia: parent PCI bridge Memory window: 0xf2600000 - 0xf26fffff
[ 10.780992] yenta_cardbus 0000:38:03.1: pcmcia: parent PCI bridge Memory window: 0xc0000000 - 0xc7ffffff
 
Last edited:
yes please, and your memory looks fine. the kernel is seeing all of it. some is being reserved by the video card.
 
You must log in or register to reply here.
Back
Top Bottom