Server Crash RH8 updated to 2.4.18-19.8.0

[lmetza]

I just installed the 4191 linux drivers from nvidia (from Tar) onto my system, then i updated the linux kernel to 2.4.18-19.8.0 and then i ot a servercrash when starting x again after restart, but i can still boot into the previous kernel version and it works. But i wish to use the latest kernel.
Can someone please tell me how to get the drivers working on the newer kernel version?

[bwkaz]

I've posted the solution to this one many, many times now. Every time you upgrade your kernel, you need to reinstall the NVIDIA_kernel package. In your case, the process is simple -- just upgrade your kernel-source, and redo the "make install" from the NVIDIA_kernel directory.

[lmetza]

kernel-source?
Should i upgrade to Kernel-Source 2.4.18-19.8.0?
Because i didnt select that 1, i did just the kernal. please let me know.

[aabram]

You need to keep your kernel and kernel source in sync. Update your kernel source too and then build nvidia drivers again.

[lmetza]

works, thanks, did it from tarball. Now im working on wineX from CVS, haveing troubles with a config file and stuff.
Anybody have a compiled version of wineX you could transfer to me???? please.

[bwkaz]

I might, but the installation process for Wine is so convoluted that I'd have no way of finding out whether or not I had all the files. It's a lot like Windows in that respect, actually.

What's the problem with the config file? I don't remember winex having a config file during compilation... and ./tools/wineinstall from the top directory set up a ~/.wine/config that works fine, once I got the thing compiled... This is Transgaming's winex, right?

[lmetza]

yes, here i have copyed and pasted what happens if i go to run a game. I need the wineX registry and ****.



[root@mdoc-km-244-55-249 root]# cd /mnt
[root@mdoc-km-244-55-249 mnt]# ls
cdrom cdrom1 floppy windows
[root@mdoc-km-244-55-249 mnt]# cd windows
[root@mdoc-km-244-55-249 windows]# ls
AUTOEXEC.BAT IntelPRO NVIDIA WINDOWS
boot.ini IO.SYS Program Files WUTemp
CONFIG.SYS MSDOS.SYS RECYCLER
Documents and Settings NTDETECT.COM System Volume Information
epson ntldr Temp
[root@mdoc-km-244-55-249 windows]# cd program files
bash: cd: program: No such file or directory
[root@mdoc-km-244-55-249 windows]# cd Program\ Files/
[root@mdoc-km-244-55-249 Program Files]# ls
Ahead Microsoft ActiveSync Trillian
Common Files microsoft frontpage Uninstall Information
ComPlus Applications Microsoft Office Viewpoint
Diablo II Movie Maker Warcraft III
DivX MSN Windows Media Player
EPSON MSN Gaming Zone Windows NT
FlashFXP MSN Messenger WindowsUpdate
Intel NetMeeting xerox
Internet Explorer Online Services XviD
KaZaA Lite Outlook Express Zone Labs
Messenger RivaTuner
[root@mdoc-km-244-55-249 Program Files]# cd Warcraft\ III/
[root@mdoc-km-244-55-249 Warcraft III]# ls
blizzard.ax icons-WAR3.bni Mss32.dll support worldedit.exe
bncache.dat ijl15.dll Patch.txt war3.exe World Editor.exe
BNUpdate.exe LastReplay.w3g redist War3Inst.log
bnupdate.log License.txt replay war3.mpq
Errors Maps save War3Patch.mpq
game.dll Movies Storm.dll Warcraft III.exe
[root@mdoc-km-244-55-249 Warcraft III]# wine war3.exe
Could not stat /root/.transgaming/c_drive (No such file or directory), ignoring
drive C:
Invalid path 'c:\windows' for windows directory: does not exist
Perhaps you have not properly edited or created your Wine configuration file.
This is (supposed to be) '/root/.wine/config'
[root@mdoc-km-244-55-249 Warcraft III]#

[bwkaz]

Originally posted by lmetza
Could not stat /root/.transgaming/c_drive (No such file or directory), ignoring
drive C:
Invalid path 'c:\windows' for windows directory: does not exist
Perhaps you have not properly edited or created your Wine configuration file.

Couple of things. First, DON'T run things as root if at all possible -- including games. If the game maker decides to put a buffer overflow into the game, and someone in multiplayer decides to use that to take over your computer, your Wine process is hosed. If there are also bugs in wine (it is alpha, after all), your kernel is at risk. If you're running as a user, your kernel will have to be OK. Granted, it's a long shot, but I'm paranoid.

Second, as I saw someone say a while ago, Linux error messages are not like Windows cryptic error messages. What you want to do is exactly what the error says: "perhaps you have not properly edited your config file". The exact part to edit will be the part referenced by the first error: "no such file or directory".

Your config file's [Drive C] section's Path entry is still the default. This needs to be changed to the real base path of a Windows C drive. From your output, your Windows C drive is /mnt/windows.