Hi,
I already explained one year age that the 64-bits wine-development package
does not allow to install 32-bits application into a 32-bits wine chroot ...
I don't find my report bug and in this, it was explained correctly how to
get it. But the mainteners didn't care and prefer to create a wine
Hi,
Make a difference between the stable and unstable version of wine can be a
good idea BUT only in the package's name and not in the application's name.
For me actually, it's very complicated and it will be more difficult to
resolv bug ...
Why you don't create the wine's package like from
/x86_64-linux-gnu +
2014-08-17 17:00 GMT+02:00 jre jre.wine...@gmail.com:
Hi
On 08/17/2014 02:38 PM, LOMBARD Maxime wrote:
Make a difference between the stable and unstable version of wine can be
a good idea BUT only in the package's name and not in the application's
name.
For me actually
, winecfg etc...)
*THE 64-BITS USERS NEED NECESSARILY LIBWINE AMD64 + I386 PACKAGES AND WINE
AMD64 PACKAGE*
2014-08-17 19:13 GMT+02:00 LOMBARD Maxime berilli...@gmail.com:
Actually, the both wine's package in debian repository don't work
correctly when you install the 32-bits and 64-bits package
Hi,
I confirm this bug. I-Nex application (tools like CPU-Z on Windows) need
this library to works correctly.
Launchpad application page : https://launchpad.net/i-nex
Bug report about Debian package problem :
https://bugs.launchpad.net/i-nex/+bug/1258468
Thanks guys,
Max
Package: nvidia-glx
Version: 319.76
Dear Mainteners,
Since nvidia driver 320.x, Nvidia has implemented partially Optimus in
their driver. Earch users which have a laptop with Optimus technology can
enabled the Nvidia card to display the desktop rendered instead of the
Intel card.
For more
Package: wine64
Version: 1.6.1-5
Dear mainteners,
Wine64 + libwine amd64 install only the files to create a 64-bits
wineprefix which allow to run only 64-bits applications. If a Debian user
install wine64, he'll can not install 32-bits applications in her
wineprefix.
Wine's dev propose to
Why you open debian bug report for your problem.
For this bug, and your others bug report #719515 and #719516 = It's not a
debian problem, it's an upstream problem.
So, stop create bug report here and post them in the Wine bugzilla :
http://bugs.winehq.org/
Thanks,
Max
Package: libwine-unstable
Version: 1.5.30-2
Dear mainteners,
With wine-unstable from Debian Sid, there is a cursor problem in two games
: Anno 1404 and Anno 2070.
When i launch these games, i see the cursor but the differents icons/images
for it are not displayed correctly. Instead of to see
Hi guys,
As Andrey found a solution to resolv this problem, i refresh
winesuffix.patch and wineserver.patch files to build the wine-unstable
package with theses modications.
I tested these new patch myself and after to build wine-unstable 1.7.0
package, the problem is gone.
Michael, if you read
Hi,
I installed Nvidia drivers 325.15 and after to modify bumblebee.conf file
and restart bumblebeed service, all work without problem :)
2013/8/9 Vincent Cheng vincentc1...@gmail.com
Hi Maxime and Francesco,
If bumblebeed is still unable to locate and load the nvidia module
(try with the
Hi Vincent,
1- I re-installed Debian Sid + Nvidia Experimental. Concerning
nvidia-modprobe.conf, i have this :
berillions@debian64:~$ cat /etc/nvidia/nvidia-modprobe.conf
alias nvidia nvidia-current
2- Result of update-alternatives --config glx before to re-install
libgl1-mesa-glx :
: error: Could not load GPU driver
2013/8/7 LOMBARD Maxime berilli...@gmail.com
Hi Vincent,
1- I re-installed Debian Sid + Nvidia Experimental. Concerning
nvidia-modprobe.conf, i have this :
berillions@debian64:~$ cat /etc/nvidia/nvidia-modprobe.conf
alias nvidia nvidia-current
2- Result
- Why the module name for the recent driver is nvidia-current ? (On
Archlinux, for the driver 319.32, it's always nvidia for the module name)
2013/8/5 Andreas Beckmann a...@debian.org
On 2013-08-05 12:16, LOMBARD Maxime wrote:
With this new module name, bumblebee can't activate the nvidia
problems my package,
the module nvidia is create but when i launch optirun -vv glxgears, i
have still the same error = could not load the second GPU driver...
I don't understand this problem between 304.88 and 325.08 drivers...
2013/8/6 Andreas Beckmann a...@debian.org
On 2013-08-06 17:15, LOMBARD
, LOMBARD Maxime wrote:
I tried this option too, same result than nvidia-current.
I tried something, i re-package myself the Experimental driver after to
modify the rules file (i replace module=nvidia-$(current) by
module=nvidia) but i don't know if it's suffisant.
I have no error during
@Vincent, optirun is available in Sid with the bumblebee package :
http://packages.debian.org/search?searchon=contentskeywords=optirunmode=pathsuite=unstablearch=anyin
wheezy-backports/Jessie and Sid.
Max
2013/8/6 Vincent Cheng vincentc1...@gmail.com
On Tue, Aug 6, 2013 at 12:45 PM, LOMBARD
at 12:59 PM, LOMBARD Maxime berilli...@gmail.com
wrote:
@Vincent, optirun is available in Sid with the bumblebee package :
http://packages.debian.org/search?searchon=contentskeywords=optirunmode=pathsuite=unstablearch=any
in wheezy-backports/Jessie and Sid.
optirun lets you pick between
So, like we know that the problem come from nvidia-package how to help
Andreas to find where come from the problem.
Actually, i can to stay on Archlinux, all works without problems But i
love Debian. :D
2013/8/6 LOMBARD Maxime berilli...@gmail.com
Ok sorry ;)
On Debian, i didn't launch
module is loaded the
next time).
Maurizio
Il 04/08/2013 18:19, LOMBARD Maxime ha scritto:
Hi guys, I found something.
If you install Nvidia 304.88 package, the module is named : nvidia.ko
but the module for the Nvidia 319.32 package is named : nvidia-current.ko
Even if i modify /etc
Package: nvidia-glx
Version: 325.08-1
Dear mainteners,
Since the 319.32-2 nvidia driver package in experimental, there is a
problem to use the nvidia card with a laptop which have the Optimus
technology.
In Sid, the 304.88-6 driver + Kernel 3.10 has not this problem because for
this driver, the
I create 325.08 nvidia driver package from the debian repository
available
herehttp://ftp.de.debian.org/debian/pool/non-free/n/nvidia-graphics-drivers/nvidia-graphics-drivers_325.08-1.debian.tar.gz.
In this new package, i disabled the both 3.10 kernel patch and i try my
package with the kernel
Hi guys, I found something.
If you install Nvidia 304.88 package, the module is named : nvidia.ko but
the module for the Nvidia 319.32 package is named : nvidia-current.ko
Even if i modify /etc/bumblebee/bumblebee.conf to replace
KernelDriver=nvidia by KernelDriver=nvidia-current, this bug
Hi,
I can confirm that the bug exist only when the nvidia driver 319.32 are
installed.
Kernel 3.10 + Nvidia 304.88-6 : Works
Kernel 3.10 + Nvidia 319.32-2 : Does not work
Max,
There is two solutions :
- Always use the kernel 3.9 which is not uninstalled automatically.
- If you want to use kernel 3.10, create a 32-bits and/or 64-bits chroot
and create a package for the nvidia driver after to add the patch into the
debian folder.
The first solution is more easy. It
Same problem here.
I don't understand why it does not works because the 'wine.inf' exist in
/usr/share/wine-unstable ...
Package: nvidia-glx
Version: 304.88-4
Dear mainteners,
I build myself the latest kernel 3.10 for tests and it seems that there is
a bug concerning the nvidia driver installation.
In fact, with the latest kernel, it's impossible to build the nvidia
module, it fails. This bug concern all Nvidia
27 matches
Mail list logo
