WINE problems

the-yikes · 03-22-2007, 02:22 PM

Hey folks,
I'm going kind of daft here, i'm running Slackware 11 and i just downloaded wine, the installation went fine but when i try to run an executable this is what i get:

bash-3.1# wine airodump-ng.exe
wine: glibc >= 2.3 without NPTL or TLS is not a supported combination.
It will most likely crash. Please upgrade to a glibc with NPTL support.
wine: creating configuration directory '/root/.wine'...
wine: glibc >= 2.3 without NPTL or TLS is not a supported combination.
It will most likely crash. Please upgrade to a glibc with NPTL support.
wine: Unhandled page fault on write access to 0x003ffd80 at address 0x60933103 (thread 0009), starting debugger...
wine: glibc >= 2.3 without NPTL or TLS is not a supported combination.
It will most likely crash. Please upgrade to a glibc with NPTL support.
wine: Unhandled page fault on write access to 0x003ffd80 at address 0x60936103 (thread 000b), starting debugger...
wine: glibc >= 2.3 without NPTL or TLS is not a supported combination.
It will most likely crash. Please upgrade to a glibc with NPTL support.
err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr 0x6000c04b
wine: wineprefixcreate failed while creating '/root/.wine'.
bash-3.1# wine: Unhandled page fault on write access to 0x003ffd80 at address 0x60936103 (thread 000d), starting debugger...
err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr 0x6000c04b
err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr 0x6000c04b
wineserver: could not save registry branch to /root/.wine-3G4QWF/system.reg : No such file or directory
wineserver: could not save registry branch to /root/.wine-3G4QWF/user.reg : No such file or directory

Iv'e checked and i have all the dependencies. Please can somebody enlighten me? or point me in the right direction for answers. Iv'e googled it and been to wine hq but nothing!

Thanks

The Yikes

H_TeXMeX_H · 03-22-2007, 03:05 PM

I believe this has been asked before. Are you running a 2.4.x kernel ? If so, you should upgrade to a 2.6.x. Wine works best (or at all) on a 2.6.x kernel.

the-yikes · 03-22-2007, 04:14 PM

Hi H_TeXMeX_H,
Well as usual your bang on the money, i just checked the kernel version and it's 2.4. Okay well that out of the way it's to to start looking at upgrading my kernel.

I wouldnt say i'm scared at the prospect of doing this, i think terrified would be more fitting! hahaha

Well time to jit google for some answers.

Thanks H_TeXMeX_H

The Yikes

H_TeXMeX_H · 03-22-2007, 05:44 PM

It isn't that hard ... http://www.slackbook.org/html/book.h...URATION-KERNEL

The hard part is re-compiling any modules you may have built for 2.4.x, such as nvidia or fglrx (proprietary) etc.

the-yikes · 03-22-2007, 08:27 PM

Ok H_TeXMeX_H or anyone!
if your looking at this PLEASE help me! i have followed the instructions on both http://xushi.co.uk/guides/kernel.php and on the link H_TeXMeX_H gave above and nothing! it's not working! the only error i received was when i issued the command

"make dep"

and the system reported that it was not neccescary . Please can some tell me how to upgrade my kernel SUCCESSFULLY or at least tell what the be jaysus i'm doing wrong!

Thanks

The Yikes

H_TeXMeX_H · 03-22-2007, 09:37 PM

Code:

4.2.1 The /kernels Directory on the Slackware CD-ROM

The precompiled Slackware kernels are available in the /kernels directory on the Slackware CD-ROM or on the FTP site in the main Slackware directory. The available kernels change as new releases are made, so the documentation in that directory is always the authoritative source. The /kernels directory has subdirectories for each kernel available. The subdirectories have the same name as their accompanying boot disk. In each subdirectory you will find the following files:
File 		Purpose
System.map 	The system map file for this kernel
bzImage 	The actual kernel image
config 		The source configuration file for this kernel

To use a kernel, copy the System.map and config files to your /boot directory and copy the kernel image to /boot/vmlinuz. Run /sbin/lilo(8) to install LILO for the new kernel, and then reboot your system. That's all there is to installing a new kernel.

The kernels that end with a .i are IDE kernels. That is, they include no SCSI support in the base kernel. The kernels that end with .s are SCSI kernels. They include all the IDE support in .i kernels, plus SCSI support.

source: slackbook

If you are instead compiling a kernel from source, 2.6.x kernels no longer need 'make dep' or 'make clean' ...

Code:

4.2.2.2 Linux Kernel Version 2.6.x

The compilation of a 2.6 kernel is only slightly different from a 2.4 or a 2.2 kernel, but it is important that you understand the differences before delving in. It's no longer necessary to run make dep and make clean. Also, the kernel compilation process is not as verbose in the 2.6 kernel series. This results in a build process that is easier to understand, but has some short comings as well. If you have trouble building the kernel, it's highly recommended that you turn verbosity back up. You do this simply by appending V=1 to the build. This allows you to log more information that could help a kernel developer or other friendly geek aid you in resolving the issue.

# make bzImage V=1

source: slackbook

So, basically just get a kernel off the install disk or here and copy 'System.map', 'vmlinuz', and 'config' into '/boot'. You might wanna save the old versions as 'vmlinuz.old', 'System.map.old' and 'config.old' and do this to '/etc/lilo.conf':

Code:

# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/hda1
  label = Linux
  read-only
image = /boot/vmlinuz.old
  root = /dev/hda1
  label = Linux-old
  read-only
# Linux bootable partition config ends

Oh, and run '/sbin/lilo' (If you're using grub, just add another entry)

the-yikes · 03-23-2007, 08:33 AM

Right, i'll give it a try! at this point im not overly concerned as to whether or not i mess things up. Iv'e backed up everything i need so the worst case scenario is a clean install! I'm going to go a try what youv'e suggested so just in case you don't hear back from me any time soon, it's because i've murdered my system! at which point i'll be trying to dispose of any forensic evidence linking me to the crime! MWhahahaha!

Thanks Again

The Yikes

the-yikes · 03-23-2007, 10:51 AM

Quote:

So, basically just get a kernel off the install disk or here and copy 'System.map', 'vmlinuz', and 'config' into '/boot'. You might wanna save the old versions as 'vmlinuz.old', 'System.map.old' and 'config.old' and do this to '/etc/lilo.conf':

ok! i clicked the link and downloaded the 3 files, just one thing, none of them are called 'vmlinuz' i have

System.map

Config

and BzImage

....

Any one know that song from M.A.S.H..you know here he says"and suicide is painless"...well... i think you get my point! hahahaha i'm losing the plot!

Thanks

The Yikes

H_TeXMeX_H · 03-23-2007, 02:56 PM

Oh yeah, rename 'bzImage' to 'vmlinuz' ... I dunno why they do that. I guess it might be because bzImage is actually vmlinuz.bz2 and it is decompressed on the fly on boot.

the-yikes · 03-23-2007, 04:35 PM

Thanks H_TeXMeX_H,
i'm going to try it. If it turns out that it is that simple i'm gonna kick by own behind for being such a halfwit!

I'll post back the results!

Thanks

The Yikes

rkrishna · 03-24-2007, 03:10 AM

first try installing an alternate 2.6 kernel from slack install cd, install huge26.s
just see if u r comfortable, if so try compiling a custom 2.6 kernel

alternate kernl
--------------
#cd /boot
#cp /media/cdrom/kernels/huge26.s/bzImage vmlinuz-2.6.17.13
#cp /media/cdrom/kernels/huge26.s/System.map.gz System.map-2.6.17.13
#ln -sf System.map-2.6.17.13 System.map

mount 2nd cd, install the modules
Command:

#installpkg /media/cdrom/extra/linux-2.6.17.13/kernel-modules-2.6.17.13-i486-1.tgz

edit lilo, like this
File: /etc/lilo.conf

image = /boot/vmlinuz-2.6.17.13
root = /dev/hdax ----give proper device
label = lin-2.6
read-only

rkrishna · 03-24-2007, 03:12 AM

if we are using 2.6 kernel series please follow the mini how to on initrd by pat it will be there in 2nd slack install cd or in your /boot ie,.
/boot/README.initrd

/media/cdrom/extra/linux-2.6.17.13/README.initrd

run lilo it is very important, dont upgrade package with the alternate kernels given in slackware cd

if we are using 2.6 kernel series please follow the mini how to on initrd by pat it will eb there in 2nd slack install cd or in your /boot ie,. /boot/README.initrd

rkrishna · 03-24-2007, 03:20 AM

my sequence of kernel compiling

$ make menuconfig
$ make
# cp System.map /boot/System.map-2.6.x.x ; ln -sf /boot/System.map-2.6.x.x /boot/System.map
# make modules_install
# cp arch/i386/boot/bzImage /boot/vmlinuz-2.6.x.x
#lilo ------ edit lilo before this
#reboot ------to test the new kernel