World of Warcraft in Wine Success

Wraithfire · 10-12-2006, 04:16 PM

Ahh hell, i'm even having problems with BIOS. The bios screens are blank when i boot up, unless I use a bootable disk. I can boot up ok but I just can't get into BIOS. Is it possible to flash bios on linux? Can i use wine if i need to?

dudeman41465 · 10-12-2006, 10:36 PM

The maker of your motherboard probably has a downloadable bios flash that you can put on a floppy disk or something. Try looking around on their website.

Wraithfire · 10-13-2006, 02:33 AM

I guess I'm just a lil nervous about flashing the bios because I've never done it with Linux as the only OS. Guess that won't matter much, huh? What should I do about my low frame rates, I have an ATI x800xl pci-e graphocs card, so I think I should be getting more than 250 fps. When I was running debian sarge 64bit, I was getting like 1500 fps or something. Of course in Debian I had to compile my own drivers from source, so maybe that's what I should have done instead of install the rpms. Do you think compiling my own would give better performance?

Wraithfire · 10-14-2006, 03:06 AM

hey, check this out. I just did did dmesg | grep pci and got

Code:

ACPI: bus type pci registered
PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
pcie_portdrv_probe->Dev[005d:10de] has invalid IRQ. Check vendor BIOS
Allocate Port Service[0000:00:0b.0:pcie00]
Allocate Port Service[0000:00:0b.0:pcie03]
pcie_portdrv_probe->Dev[005d:10de] has invalid IRQ. Check vendor BIOS
Allocate Port Service[0000:00:0c.0:pcie00]
Allocate Port Service[0000:00:0c.0:pcie03]
pcie_portdrv_probe->Dev[005d:10de] has invalid IRQ. Check vendor BIOS
Allocate Port Service[0000:00:0d.0:pcie00]
Allocate Port Service[0000:00:0d.0:pcie03]
pcie_portdrv_probe->Dev[005d:10de] has invalid IRQ. Check vendor BIOS
Allocate Port Service[0000:00:0e.0:pcie00]
Allocate Port Service[0000:00:0e.0:pcie03]
pci_hotplug: PCI Hot Plug PCI Core version: 0.5

IRQ conflict, wonder if that's my trouble? Does that require a BIOS flash to settle?

Wraithfire · 10-15-2006, 12:23 PM

I had posted this in a different forum, but I wanted to put it up here as well.
Today i tried a new filter for dmesg. I ran dmesg | grep resource and this is returned:

Code:

Allocating PCI resources starting at 50000000 (gap: 40000000:a0000000)
Setting up standard PCI resources
PCI: Cannot allocate resource region 2 of device 0000:05:00.0
PCI: Cannot allocate resource region 0 of device 0000:05:00.1

I'm not sure what these devices are or if they would effect my graphics. Possibly one of these is a NIC. I also installed lshw, and when i run this i noticed the memory controller is listed as Unclaimed. Don't know if that matters or not, but here is some other output I thought was worth looking at from lshd:

Code:

-memory:0
          description: System Memory
          physical id: 1b
          slot: System board or motherboard
          size: 1GB
        *-bank:0
             description: DIMM [empty]
             physical id: 0
             slot: A0
             width: 64 bits
        *-bank:1
             description: DIMM [empty]
             physical id: 1
             slot: A1
             width: 64 bits
        *-bank:2
             description: DIMM
             physical id: 2
             slot: A2
             size: 512MB
             width: 64 bits
        *-bank:3
             description: DIMM
             physical id: 3
             slot: A3
             size: 512MB
             width: 64 bits
     *-memory:1 UNCLAIMED
          description: Memory controller
          product: CK804 Memory Controller
          vendor: nVidia Corporation
          physical id: 4
          bus info: pci@00:00.0
          version: a3
          width: 32 bits
          clock: 66MHz (15.2ns)
          capabilities: bus_master cap_list
          configuration: latency=0
..cut..
*-display:0
             description: VGA compatible controller
             product: R430 [Radeon X800 XL] (PCIe)
             vendor: ATI Technologies Inc
             physical id: 0
             bus info: pci@05:00.0
             version: 00
             size: 256MB
             width: 64 bits
             clock: 33MHz
             capabilities: vga bus_master cap_list
             configuration: driver=fglrx_pci latency=0
             resources: iomemory:b0000000-bfffffff iomemory:fe200000-fe20ffff ioport:6c00-6cff irq:50
        *-display:1 UNCLAIMED
             description: Display controller
             product: R430 [Radeon X800 XL] (PCIe) Secondary
             vendor: ATI Technologies Inc
             physical id: 0.1
             bus info: pci@05:00.1
             version: 00
             size: 64KB
             width: 64 bits
             clock: 33MHz
             capabilities: cap_list
             configuration: latency=0
             resources: iomemory:fe210000-fe21ffff

Now I noticed that the bus info line for display 0 and display 1 lists pci@05:00.0 and pci@05:00.1, respectively. This is similar to the boot error i listed up above. Assuming that 0000 is the pcibus, then something on the videocard is not being detected properly. You can also see the differences in the resources line of each of the display sections. Does anyone know if this something that can corrected with a BIOS flash, or is this telling me that there's something wrong with ATI's driver, or is this telling me that my video card is hosed? Anyone know?

Jayla · 11-21-2007, 05:19 PM

I've been reading this guide and have found it very useful so far

I've been able to install wine, and have copied the WoW folder from my XP partition into /home/jimmy/.wine/drive_c/program files/WoW

I can launch the game fine using wine "C:\World of Warcraft\WoW.exe" -opengl

thats not the issue, I can see the login screen but no matter what I enter it returns "Disconnected from server" and I see the following in the terminal

Code:

fixme:system:SystemParametersInfoW Unimplemented action: 113 (SPI_SETMOUSESPEED)
fixme:system:SystemParametersInfoW Unimplemented action: 113 (SPI_SETMOUSESPEED)
fixme:wininet:InternetSetOptionW Option INTERNET_OPTION_CONNECT_TIMEOUT (5000): STUB
fixme:wininet:InternetSetOptionW INTERNET_OPTION_SEND/RECEIVE_TIMEOUT not supported on protocol 4
fixme:wininet:InternetSetOptionW Option INTERNET_OPTION_CONNECT_TIMEOUT (5000): STUB
fixme:wininet:InternetSetOptionW INTERNET_OPTION_SEND/RECEIVE_TIMEOUT not supported on protocol 4
fixme:reg:GetNativeSystemInfo (0x374029c4) using GetSystemInfo()
fixme:process:IsWow64Process (0xffffffff 0x7c5ac4a4) stub!
fixme:wininet:InternetSetOptionW Option INTERNET_OPTION_CONTEXT_VALUE; STUB
fixme:wininet:InternetSetOptionW Option INTERNET_OPTION_CONTEXT_VALUE; STUB
fixme:system:SystemParametersInfoW Unimplemented action: 113 (SPI_SETMOUSESPEED)

I assuming that there is an issue connecting to the internet via wine? I'm not entirely sure where to start my "trial and error" method of figuring this out, can anyone please point me in the right direction?

Regards

Jayla · 11-22-2007, 04:05 PM

been Googling/Forum raiding/IRC'ing for several days now and still no progress

Is there an option I need to set to allow WINE to access the internet?

someone PLEASE help me!

free cookie to the person who helps me solve this :P

J

Jayla · 11-23-2007, 07:40 PM

Since I've had a hard time finding a solution for this, I'd thought I'd share the wealth so no one else has to

it seemed that the upgrade to the latest version of wine (*.50) didnt retain some settings, I also made sure that thru winecfg, the drive "D" was mapped to /media/sda2 (being my windows C drive)

also I had to re-run wineprefixcreate from the command line (apparently this re-creates the wine files under ~/.wine but I'm not hot enough on Wine to know this)

then I could run the game by calling wine "D:\WoW\WoW.exe" -opengl

(make sure u use the -opengl parameter)

There are some issues connecting, I believe this is due to the new background application Blizzard has implemented to catch hackers (bit like Steam for half life) so yet to find a solution (will post when I do)

But all seems well as I can play guild wars thru wine now

Just like to give a BIG shoutout to the original poster, who I contacted via e-mail to find out about this issue, and to "MKoR" from the #winehq IRC channel who talked me thru the whole thing

Regards