First the following errors are logged in dmesg:
[ 31.891848] mtrr: base(0xc0000000) is not aligned on a
size(0xff00000) boundary
[ 32.343580] Xorg:3090 conflicting memory types c0000000-cff00000
uncached<->uncached-minus
[ 32.343585] reserve_memtype failed 0xc0000000-0xcff00000, track
uncached, req write-back
[ 32.344431] Xorg:3090 conflicting memory types fd000000-fe000000
uncached<->uncached-minus
[ 32.344434] reserve_memtype failed 0xfd000000-0xfe000000, track
uncached, req write-back
[ 32.847537] Xorg:3090 conflicting memory types c0000000-cff00000
uncached<->uncached-minus
[ 32.847541] reserve_memtype failed 0xc0000000-0xcff00000, track
uncached, req write-back
[ 32.848203] Xorg:3090 conflicting memory types fd000000-fe000000
uncached<->uncached-minus
[ 32.848205] reserve_memtype failed 0xfd000000-0xfe000000, track
uncached, req write-back
[ 32.920406] Xorg:3090 conflicting memory types c0000000-cff00000
uncached<->uncached-minus
[ 32.920412] reserve_memtype failed 0xc0000000-0xcff00000, track
uncached, req write-back
[ 32.921277] Xorg:3090 conflicting memory types fd000000-fe000000
uncached<->uncached-minus
[ 32.921281] reserve_memtype failed 0xfd000000-0xfe000000, track
uncached, req write-back
[ 32.934457] Xorg:3094 freeing invalid memtype c0000000-cff00000
[ 32.934672] Xorg:3094 freeing invalid memtype fd000000-fe000000
[ 32.980551] Xorg:3090 conflicting memory types c0000000-cff00000
uncached<->uncached-minus
[ 32.980556] reserve_memtype failed 0xc0000000-0xcff00000, track
uncached, req write-back
[ 32.981326] Xorg:3090 conflicting memory types fd000000-fe000000
uncached<->uncached-minus
[ 32.981329] reserve_memtype failed 0xfd000000-0xfe000000, track
uncached, req write-back
[ 32.993372] Xorg:3095 freeing invalid memtype c0000000-cff00000
[ 32.993635] Xorg:3095 freeing invalid memtype fd000000-fe000000
After I click "wine file" nothing appear, and similarly any of the
WINE GUI menu item as well....
Some useful info:
X.Org X Server 1.5.3
Release Date: 5 November 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.18-92.1.18.el5 x86_64
Current Operating System: Linux localhost.localdomain 2.6.29 #39 SMP
Tue Mar 31 01:05:51 EDT 2009 x86_64
Build Date: 11 December 2008 05:27:30PM
Build ID: xorg-x11-server 1.5.3-6.fc10
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Apr 2 19:49:39 2009
(EE) Unable to locate/open config file
(II) Loader magic: 0x7aec60
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 4.1
X.Org XInput driver : 2.1
X.Org Server Extension : 1.1
X.Org Font Renderer : 0.6
(II) Loader running on linux
(++) using VT number 1
(--) PCI:*(0@1:0:0) nVidia Corporation GeForce 8500 GT rev 161, Mem @
0xfd000000/16777216, 0xc0000000/268435456, 0xfa000000/33554432, I/O @
0x00009c00/128, BIOS @ 0x????????/131072
(==) Matched nv for the autoconfigured driver
New driver is "nv"
(==) Using default built-in configuration (30 lines)
Any other information needed?
--
Regards,
Peter Teoh
Error in starting "wine file" in x86_64 FC10 env
Error in starting "wine file" in x86_64 FC10 env
On Thu, Apr 2, 2009 at 10:28 AM, Peter Teoh <[email protected]> wrote:
previous stable.
--
-Austin
Broken video drivers. Upgrade, or if using a beta, downgrade to aAfter I click "wine file" nothing appear, and similarly any of the
WINE GUI menu item as well....
Some useful info:
X.Org X Server 1.5.3
Release Date: 5 November 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.18-92.1.18.el5 x86_64
Current Operating System: Linux localhost.localdomain 2.6.29 #39 SMP
Tue Mar 31 01:05:51 EDT 2009 x86_64
Build Date: 11 December 2008 05:27:30PM
Build ID: xorg-x11-server 1.5.3-6.fc10
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Apr 2 19:49:39 2009
(EE) Unable to locate/open config file
(II) Loader magic: 0x7aec60
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 4.1
X.Org XInput driver : 2.1
X.Org Server Extension : 1.1
X.Org Font Renderer : 0.6
(II) Loader running on linux
(++) using VT number 1
(--) PCI:*(0@1:0:0) nVidia Corporation GeForce 8500 GT rev 161, Mem @
0xfd000000/16777216, 0xc0000000/268435456, 0xfa000000/33554432, I/O @
0x00009c00/128, BIOS @ 0x????????/131072
(==) Matched nv for the autoconfigured driver
New driver is "nv"
(==) Using default built-in configuration (30 lines)
Any other information needed?
--
Regards,
Peter Teoh
previous stable.
--
-Austin
Error in starting "wine file" in x86_64 FC10 env
thanks. broken in what sense? where can i read the relevant error
message? how to turn on wine debugging feature to enable error
trace logging? thank you for the support
.
On Thu, Apr 2, 2009 at 11:34 AM, Austin English <[email protected]> wrote:
--
Regards,
Peter Teoh
message? how to turn on wine debugging feature to enable error
trace logging? thank you for the support

On Thu, Apr 2, 2009 at 11:34 AM, Austin English <[email protected]> wrote:
On Thu, Apr 2, 2009 at 10:28 AM, Peter Teoh <[email protected]> wrote:Broken video drivers. Upgrade, or if using a beta, downgrade to aAfter I click "wine file" nothing appear, and similarly any of the
WINE GUI menu item as well....
Some useful info:
X.Org X Server 1.5.3
Release Date: 5 November 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.18-92.1.18.el5 x86_64
Current Operating System: Linux localhost.localdomain 2.6.29 #39 SMP
Tue Mar 31 01:05:51 EDT 2009 x86_64
Build Date: 11 December 2008 05:27:30PM
Build ID: xorg-x11-server 1.5.3-6.fc10
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Apr 2 19:49:39 2009
(EE) Unable to locate/open config file
(II) Loader magic: 0x7aec60
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 4.1
X.Org XInput driver : 2.1
X.Org Server Extension : 1.1
X.Org Font Renderer : 0.6
(II) Loader running on linux
(++) using VT number 1
(--) PCI:*(0@1:0:0) nVidia Corporation GeForce 8500 GT rev 161, Mem @
0xfd000000/16777216, 0xc0000000/268435456, 0xfa000000/33554432, I/O @
0x00009c00/128, BIOS @ 0x????????/131072
(==) Matched nv for the autoconfigured driver
New driver is "nv"
(==) Using default built-in configuration (30 lines)
Any other information needed?
--
Regards,
Peter Teoh
previous stable.
--
-Austin
--
Regards,
Peter Teoh
Error in starting "wine file" in x86_64 FC10 env
On Thu, Apr 2, 2009 at 7:27 PM, Peter Teoh <[email protected]> wrote:
Nvidia binary drivers if you can.
For Wine debugging, use WINEDEBUG (http://wiki.winehq.org/DebugChannels).
--
-Austin
The crash is in your video drivers, not Wine. Try changing to thethanks. Â broken in what sense? Â where can i read the relevant error
message? Â Â how to turn on wine debugging feature to enable error
trace logging? Â thank you for the support.
Nvidia binary drivers if you can.
For Wine debugging, use WINEDEBUG (http://wiki.winehq.org/DebugChannels).
--
-Austin
Re: Error in starting "wine file" in x86_64 FC10 e
You using wrong drivers. Use nVidia's drivers. "nv" driver is junk.Peter Teoh wrote:(==) Matched nv for the autoconfigured driver
New driver is "nv"
Error in starting "wine file" in x86_64 FC10 env
On Mon, Apr 6, 2009 at 3:05 AM, Austin English <[email protected]> wrote:
thank you to you too Vitamin!!!!
--
Regards,
Peter Teoh
ah...thank you Austin....u just taught me how to read the log files!!!!On Thu, Apr 2, 2009 at 7:27 PM, Peter Teoh <[email protected]> wrote:The crash is in your video drivers, not Wine. Try changing to thethanks. broken in what sense? where can i read the relevant error
message? how to turn on wine debugging feature to enable error
trace logging? thank you for the support.
Nvidia binary drivers if you can.
thank you to you too Vitamin!!!!
--
Regards,
Peter Teoh