d see what it detects.
>>>>> > If "xrandr" is able to detect both outputs it should just be a
>>>>> > matter of configuration, if not then that would suggest a problem
>>>>> > with the driver.
>>>>> >
>>>>
ne that it doesn't detect the monitor? You can read
>>> through /var/log/Xorg.0.log, but it's easier to just run "xrandr" (when
>>> both screens are connected) and see what it detects. If "xrandr" is able
>>> to detect both outputs it should j
On Fri, 2015-06-19 at 14:05 +1200, Bruce Ward wrote:
> Thanks Selim, that fixed it.
Glad you got it working, but there's certainly a bug there.
If you have the time, maybe you could file a bug (preferably directly
upstream) or see if it already has been reported.
--
Cheers,
Sven Arvidsson
http
On 06/19/2015 05:58 AM, Bret Busby wrote:
ii nvidia-prime0.5~hybrid0.0.3
Tools to enable NVIDIA's Prime
Google this, for the love of $DEITY$
http://askubuntu.com/questions/363775/what-is-the-use-of-nvidia-prime
--
My father, Victor Moore (Vic)
On 06/19/2015 02:07 PM, Reco wrote:
I would rather use Debian 6, as it has the superior interface, to the
later Debian versions, and to Ubuntu, but, to use Debian 6, I have to
use a lesser computer.
Ah, I get it now. So, layman's terms put aside, you like to use GNOME2
and not GNOME3. And that
On Friday 19 June 2015 22:51:40 Ric Moore wrote:
> On 06/19/2015 02:51 PM, Lisi Reisz wrote:
> > No, it wouldn't solve the problem. He can get Ubuntu going to his
> > satisfaction, but he cannot get Debian going to his satisfaction.
>
> ...running Squeeze, a 5 year old OS, while expecting it will
On 06/19/2015 02:51 PM, Lisi Reisz wrote:
No, it wouldn't solve the problem. He can get Ubuntu going to his
satisfaction, but he cannot get Debian going to his satisfaction.
...running Squeeze, a 5 year old OS, while expecting it will be
maintained at Wheezy/Jessie level. We've beaten that h
7;t like it, don't use it. No-one is making you.
If he would just take "squeeze" out of the equation, it ~might~ help.
From what I read it won't be a simple matter of installing a nvidia
driver. He's got this video chip hybrid from Hell, and Bumblebee is
~supposed~ to be
On Friday 19 June 2015 19:40:11 Reco wrote:
> Hi.
>
> On Fri, 19 Jun 2015 19:31:56 +0100
>
> Lisi Reisz wrote:
> > On Friday 19 June 2015 18:49:38 Bret Busby wrote:
> > > On 20/06/2015, Lisi Reisz wrote:
> > > > On Friday 19 June 2015 16:54:12 Bret Busby wrote:
> > > >> Unfortunately, it appears
Hi.
On Fri, 19 Jun 2015 19:31:56 +0100
Lisi Reisz wrote:
> On Friday 19 June 2015 18:49:38 Bret Busby wrote:
> > On 20/06/2015, Lisi Reisz wrote:
> > > On Friday 19 June 2015 16:54:12 Bret Busby wrote:
> > >> Unfortunately, it appears that once a version of Debian Linux is
> > >> "released" an
On Friday 19 June 2015 18:49:38 Bret Busby wrote:
> On 20/06/2015, Lisi Reisz wrote:
> > On Friday 19 June 2015 16:54:12 Bret Busby wrote:
> >> Unfortunately, it appears that once a version of Debian Linux is
> >> "released" and decreed stable, development of that version and its
> >> packages, ce
Hi.
On Sat, 20 Jun 2015 01:45:42 +0800
Bret Busby wrote:
> On 20/06/2015, Reco wrote:
>
> >
> > And then again - if Ubuntu satisfies your needs, why suffer with Debian
> > oldstable?
> >
>
> As should be shown by examining the full headers of this and other
> messages not explicitly sent fro
On 20/06/2015, Lisi Reisz wrote:
> On Friday 19 June 2015 16:54:12 Bret Busby wrote:
>> Unfortunately, it appears that once a version of Debian Linux is
>> "released" and decreed stable, development of that version and its
>> packages, ceases, and it goes into maintenance mode, so that only
>> bug
On 20/06/2015, Reco wrote:
>
> And then again - if Ubuntu satisfies your needs, why suffer with Debian
> oldstable?
>
As should be shown by examining the full headers of this and other
messages not explicitly sent from the Debian installations, I am using
Ubuntu 12.04, except where necessary for
On 20/06/2015, Curt wrote:
> On 2015-06-19, Bret Busby wrote:
>>>
>>> Didn't we already go through this once with you in a long, protracted,
>>> confused and confusing thread, the exact same issue, not too long ago?
>>
>> As I have, I believe, previously mentioned, I have been trying for
>> about
On 2015-06-19, Bret Busby wrote:
>>
>> Didn't we already go through this once with you in a long, protracted,
>> confused and confusing thread, the exact same issue, not too long ago?
>
> As I have, I believe, previously mentioned, I have been trying for
> about two years, now, to get Debian worki
Hi.
On Fri, 19 Jun 2015 23:54:12 +0800
Bret Busby wrote:
> As I have, I believe, previously mentioned, I have been trying for
> about two years, now, to get Debian working on this computer, so that
> it can work with the external monitor.
>
> The status of Debian Linux, with the computer, is t
On Friday 19 June 2015 16:54:12 Bret Busby wrote:
> Unfortunately, it appears that once a version of Debian Linux is
> "released" and decreed stable, development of that version and its
> packages, ceases, and it goes into maintenance mode, so that only
> bugfixes and security vulnerabilities, are
On 19/06/2015, Petter Adsen wrote:
> On Fri, 19 Jun 2015 17:50:17 +0800
> Bret Busby wrote:
>> I have attached a copy of the file from the Debian 6 installation.
>
> It's not loading neither the nouveau nor the nvidia driver, is one of
> them correctly installed, and i
On 19/06/2015, Curt wrote:
> On 2015-06-19, Bret Busby wrote:
>>
>> Sorry - I had read the whole of the post, and had tried to respond to
>> it in modularised progressive steps, and when I got down to that part,
>> I had forgotten the content of the first paragraph.
>
> Didn't we already go throu
On Fri, 19 Jun 2015 17:50:17 +0800
Bret Busby wrote:
> I have attached a copy of the file from the Debian 6 installation.
It's not loading neither the nouveau nor the nvidia driver, is one of
them correctly installed, and is the kernel module loaded?
For Squeeze, I simply do not kno
On 2015-06-19, Bret Busby wrote:
>
> Sorry - I had read the whole of the post, and had tried to respond to
> it in modularised progressive steps, and when I got down to that part,
> I had forgotten the content of the first paragraph.
Didn't we already go through this once with you in a long, prot
ow do you determine that it doesn't detect the monitor? You can
>>>> > read through /var/log/Xorg.0.log, but it's easier to just run
>>>> > "xrandr" (when both screens are connected) and see what it detects.
>>>> > If "xrandr" is able
gt;>> > read through /var/log/Xorg.0.log, but it's easier to just run
>>> > "xrandr" (when both screens are connected) and see what it detects.
>>> > If "xrandr" is able to detect both outputs it should just be a
>>> > matter of con
X11/75dpi,
/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType,
built-ins
(==) ModulePath set to "/usr/lib/xorg/modules"
(II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable
AutoAddDevices.
(II) Loader
ne that it doesn't detect the monitor? You can read
>>> through /var/log/Xorg.0.log, but it's easier to just run "xrandr" (when
>>> both screens are connected) and see what it detects. If "xrandr" is able
>>> to detect both outputs it should j
easier to just run
>> > "xrandr" (when both screens are connected) and see what it detects.
>> > If "xrandr" is able to detect both outputs it should just be a
>> > matter of configuration, if not then that would suggest a problem
>> > with the
] (II) The server relies on udev to provide the list of
input devices.
If no devices become available, reconfigure udev or disable
AutoAddDevices.
[25.494] (II) Loader magic: 0x7f0af8cb6c20
[25.494] (II) Module ABI versions:
[25.494]X.Org ANSI C Emulation: 0.4
[25.494
On 2015-06-19, Ric Moore wrote:
>
> "Check and see if you have the tool 'intel-virtual-output' installed.
> This is included in 'xf86-video-intel' =< v2.99, aprox date released is
> 22/Dec/2014
>
"xf86-video-intel" doesn't appear to be a Debian package. I can only find it
here:
http://www.x.or
ns are connected) and see what it detects.
> > If "xrandr" is able to detect both outputs it should just be a
> > matter of configuration, if not then that would suggest a problem
> > with the driver.
> >
> > At least Wheezy is a lot more up to date than Squ
n
> both screens are connected) and see what it detects. If "xrandr" is able
> to detect both outputs it should just be a matter of configuration, if
> not then that would suggest a problem with the driver.
>
> At least Wheezy is a lot more up to date than Squeeze, with newer
&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Jun 19, 2015 at 02:05:37PM +1200, Bruce Ward wrote:
> Thanks Selim, that fixed it.
[selim]
> >>>options forcedeth msi=0 msix=0
> >
> > ^^^
> >Should be like this.
>
> Yes, solution is /etc/modprobe.d/forcedeth.conf containing
> o
log/Xorg.0.log, but it's easier to just run "xrandr" (when
>> both screens are connected) and see what it detects. If "xrandr" is able
>> to detect both outputs it should just be a matter of configuration, if
>> not then that would suggest a problem with t
n
> both screens are connected) and see what it detects. If "xrandr" is able
> to detect both outputs it should just be a matter of configuration, if
> not then that would suggest a problem with the driver.
>
On Debian 6;
"
:~# xrandr
xrandr: Failed to get size of gamma for
On 19/06/2015, Bret Busby wrote:
> On 19/06/2015, Petter Adsen wrote:
>> On Fri, 19 Jun 2015 12:15:59 +0800
>> Bret Busby wrote:
>>> I note also, that I used synaptic to remove all the nvidia stuff, from
>>> the Debian 7 installation, and I removed the bumblebee stuff from that
>>> installation,
On 19/06/2015, Ric Moore wrote:
> On 06/19/2015 12:15 AM, Bret Busby wrote:
>> On 19/06/2015, Ric Moore wrote:
>>> On 06/18/2015 03:25 AM, Petter Adsen wrote:
>>>
There are, however, no hits on bumblebee for squeeze at all, so it
won't help in this case. Maybe you could try to build it
On 19/06/2015, Petter Adsen wrote:
> On Fri, 19 Jun 2015 12:15:59 +0800
> Bret Busby wrote:
>> I note also, that I used synaptic to remove all the nvidia stuff, from
>> the Debian 7 installation, and I removed the bumblebee stuff from that
>> installation, and reinstalled bumblebee on that instal
able
to detect both outputs it should just be a matter of configuration, if
not then that would suggest a problem with the driver.
At least Wheezy is a lot more up to date than Squeeze, with newer
kernel and X. I'd say your odds of getting the second screen going
there would be a lot better
On 06/19/2015 12:15 AM, Bret Busby wrote:
On 19/06/2015, Ric Moore wrote:
On 06/18/2015 03:25 AM, Petter Adsen wrote:
There are, however, no hits on bumblebee for squeeze at all, so it
won't help in this case. Maybe you could try to build it from source? At
this point that may be your only ch
On 19/06/2015, Ric Moore wrote:
> On 06/18/2015 03:25 AM, Petter Adsen wrote:
>
>> There are, however, no hits on bumblebee for squeeze at all, so it
>> won't help in this case. Maybe you could try to build it from source? At
>> this point that may be your only chance. If only you could do that wi
Thanks Selim, that fixed it.
I had tried that months ago on the Wheezy installation I run, but it did
not work then - probably I did not update the module dependencies or the
initramfs at that time!
I had not realised the importance of the 'options' keyword, having seen
few examples of it :-
On Fri, Jun 19, 2015 at 09:06:30AM +1200, Bruce Ward wrote:
> >
> >An entry "options forcedeth ms=0 msix=0" in some /etc/modprobe.d/foo.conf
> >should do thr trick, no?
> >
> >Of course, perhaps you tried that already and I'm mis-interpreting
> >your question completely. Apologies if that's the cas
Hi Tomas
On Thu, Jun 18, 2015 at 11:12:49PM +1200, Bruce Ward wrote:
Installing Jessie 8.1.0 on an Asrock N68-VGS3 FX motherboard. This
has "Giga PHY RTL8211CL" ethernet, which lspci reports as:
"00:07.0 Bridge: NVIDIA Corporation MCP61 Ethernet (rev a2)"
It uses the for
On 06/18/2015 03:25 AM, Petter Adsen wrote:
There are, however, no hits on bumblebee for squeeze at all, so it
won't help in this case. Maybe you could try to build it from source? At
this point that may be your only chance. If only you could do that with
the drivers...
It might also be that it
n MCP61 Ethernet (rev a2)"
>
> It uses the forcedeth driver module, which seems to need parameters
> "msi=0 msix=0" to work. If I blacklist the driver, I can load it
> with "modprobe forcedeth msi=0 msix=0" and all is fine. However, it
> needs this after ev
Installing Jessie 8.1.0 on an Asrock N68-VGS3 FX motherboard. This has
"Giga PHY RTL8211CL" ethernet, which lspci reports as:
"00:07.0 Bridge: NVIDIA Corporation MCP61 Ethernet (rev a2)"
It uses the forcedeth driver module, which seems to need parameters
"msi=0 msix=0
On Thu, 18 Jun 2015 15:07:47 +0800
Bret Busby wrote:
> On 18/06/2015, Petter Adsen wrote:
>
>
>
> >
> > As to your problem with bumblebee, I think Optimus support is
> > something that is fairly recent, and might well have come after
> > Squeeze. Maybe you will find it in backports?
> >
>
>
On 18/06/2015, Petter Adsen wrote:
>
> As to your problem with bumblebee, I think Optimus support is something
> that is fairly recent, and might well have come after Squeeze. Maybe
> you will find it in backports?
>
A problem is that, and, I am not sure whether I indicated this in a
previous
5.36.31-6squeeze2_amd64.deb) ...
> >> Setting up nvidia-kernel-dkms (195.36.31-6squeeze2) ...
> >> Loading new nvidia-195.36.31 DKMS files...
> >> First Installation: checking all kernels...
> >> Building only for 2.6.32-5-amd64
> >> Building initial mod
ing new nvidia-195.36.31 DKMS files...
>> First Installation: checking all kernels...
>> Building only for 2.6.32-5-amd64
>> Building initial module for 2.6.32-5-amd64
>
> As I said, you are installing bits of nvidia 195 driver series. It's
> right there in your frig
Building initial module for 2.6.32-5-amd64
As I said, you are installing bits of nvidia 195 driver series. It's
right there in your frigging log.
That's for REAL OLD nvidia cards. You have a mess. Jerk it all out. Fire
up synaptic, search on nvidia, check on what you currently have
ins
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Jun 16, 2015 at 12:39:00AM +0800, Bret Busby wrote:
> sudo purge nvidia*
>
> (Do not forget to reboot). nVidia ppa's other than xorg-edgers need to
> be disabled or removed for the sake of this particular example.
> "
>
> Trying to run that p
You may have much better
>>> luck with nouveau.
>>>
>>
>> At this stage, as everything that was expected to work, apparently
>> doesn't, including the manufacturer's driver, it has become a matter
>> of grasping at straws.
>
> Simple, purge all
rer's driver, it has become a matter
of grasping at straws.
Simple, purge all of your nvidia packages. Then install mlocate. As root
user, updatedb, then locate nvidia. Clobber everything remaining. Follow
this to make sure your blacklist is set up now to exclude nvidia,
instead of nou
else to find that
>>> information, in Debian 6), I found the following two packages
>>> installed;
>>>
>>> "
>>> xserver-xorg-video-nouveau
>>> X.Org X server -- Nouveau display driver (experimental)
>>>
>>> Version: 1:0.0.1
pers.
>
> Other than that, I was under the impression that you had already tried
> them and had to use the proprietary drivers. You may have much better
> luck with nouveau.
>
At this stage, as everything that was expected to work, apparently
doesn't, including the manufacturer&
found the following two packages
>> installed;
>>
>> "
>> xserver-xorg-video-nouveau
>> X.Org X server -- Nouveau display driver (experimental)
>>
>> Version: 1:0.0.15+git20100329+7858345-5
>> "
>>
>> and
>>
>> "
; "
> xserver-xorg-video-nouveau
> X.Org X server -- Nouveau display driver (experimental)
>
> Version: 1:0.0.15+git20100329+7858345-5
> "
>
> and
>
> "
> xserver-xorg-video-nv
> X.Org X server -- NV display driver
>
> Version: 1:2.1.17-3
rote:
>>>> >>>>> On 11/06/2015, Nick T. wrote:
>>>> >>>>>> Oops, forgot to cc in the mailing list.
>>>> >>>>>>
>>>> >>>>>> - Nick
>>>> >>>
;
>> >>>>>> - Nick
>> >>>>>>
>> >>>>>> On 06/10/2015 09:19 PM, Nick T. wrote:
>> >>>>>>> Install build-essential it should contain all the packages
>> >>>>>>> necessary
t;>> On 06/10/2015 03:45 PM, Bret Busby wrote:
> >>>>> On 11/06/2015, Nick T. wrote:
> >>>>>> Oops, forgot to cc in the mailing list.
> >>>>>>
> >>>>>> - Nick
> >>>>>>
> >>>>
T. wrote:
>>>>>> Oops, forgot to cc in the mailing list.
>>>>>>
>>>>>> - Nick
>>>>>>
>>>>>> On 06/10/2015 09:19 PM, Nick T. wrote:
>>>>>>> Install build-essential it should contain all the pa
>>>>>
>>>>> - Nick
>>>>>
>>>>> On 06/10/2015 09:19 PM, Nick T. wrote:
>>>>>> Install build-essential it should contain all the packages necessary
>>>>>> to install the driver.
>>>>>> A
necessary
to install the driver.
Also you might want to install dkms if you don't want to reinstall the
driver after every kernel update.
- Nick
Thank you for that.
The driver installation appears to have subsequently succeeded.
However, after rebooting, the system still does not se
ild-essential it should contain all the packages necessary
>>>> to install the driver.
>>>> Also you might want to install dkms if you don't want to reinstall the
>>>> driver after every kernel update.
>>>>
>>>> - Nick
>>>>
mailing list.
- Nick
On 06/10/2015 09:19 PM, Nick T. wrote:
Install build-essential it should contain all the packages necessary
to install the driver.
Also you might want to install dkms if you don't want to reinstall
the driver after every kernel update.
- Nick
Thank you for that.
The d
t;> Oops, forgot to cc in the mailing list.
> >>>>
> >>>> - Nick
> >>>>
> >>>> On 06/10/2015 09:19 PM, Nick T. wrote:
> >>>>> Install build-essential it should contain all the packages necessary
> >>>>> t
contain all the packages necessary
to install the driver.
Also you might want to install dkms if you don't want to reinstall the
driver after every kernel update.
- Nick
Thank you for that.
The driver installation appears to have subsequently succeeded.
However, after rebooting, the system
gt; >>> Install build-essential it should contain all the packages necessary
> >>> to install the driver.
> >>> Also you might want to install dkms if you don't want to reinstall the
> >>> driver after every kernel update.
> >>>
> >
On 06/10/2015 03:45 PM, Bret Busby wrote:
On 11/06/2015, Nick T. wrote:
Oops, forgot to cc in the mailing list.
- Nick
On 06/10/2015 09:19 PM, Nick T. wrote:
Install build-essential it should contain all the packages necessary
to install the driver.
Also you might want to install dkms if
en rebooted.
>
> System -> Preferences -> Monitors still did not find the external monitor.
>
> In that menu path, down from Monitors, was an entry,something like
> nVidia xserver settings, so I selected that.
>
> I got a dialogue box, with something like "You appear to b
itors, was an entry,something like
nVidia xserver settings, so I selected that.
I got a dialogue box, with something like "You appear to be not using
the nVidia driver. Run nvidia-xconfig as root and restart xserver."
So, I ran nvidia-xconfig as root, and got a message something like &q
ub as root.
- Nick
On 06/10/2015 10:55 PM, Bret Busby wrote:
On 11/06/2015, Nick T. wrote:
Try adding nomodeset to the boot command if its not already there, I had
to add that to make the driver work.
This will probably make me seem even more stupid than I probably
already appear, but, how do
odeset to the boot command if its not already there, I had
>>> to add that to make the driver work.
>>>
>>
>> This will probably make me seem even more stupid than I probably
>> already appear, but, how do I do that?
>>
>> Thank you in anticipation.
&g
make the driver work.
This will probably make me seem even more stupid than I probably
already appear, but, how do I do that?
Thank you in anticipation.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Conta
On 11/06/2015, Nick T. wrote:
> Try adding nomodeset to the boot command if its not already there, I had
> to add that to make the driver work.
>
This will probably make me seem even more stupid than I probably
already appear, but, how do I do that?
Thank you in anticipation.
--
B
Try adding nomodeset to the boot command if its not already there, I had
to add that to make the driver work.
- Nick
On 06/10/2015 10:45 PM, Bret Busby wrote:
On 11/06/2015, Nick T. wrote:
Oops, forgot to cc in the mailing list.
- Nick
On 06/10/2015 09:19 PM, Nick T. wrote:
Install build
On 11/06/2015, Nick T. wrote:
> Oops, forgot to cc in the mailing list.
>
> - Nick
>
> On 06/10/2015 09:19 PM, Nick T. wrote:
>> Install build-essential it should contain all the packages necessary
>> to install the driver.
>> Also you might want to install dkms i
When last heard Bret was using Squeeze. I think he looked at Wheezy, but
Jessie???
Ah, hopefully he can make the edit properly then, using "squeeze"
instead of "jessie". Still, installing the driver should be a cake walk.
Thanks for the correction, Lisi. It never hurts to have
On Wednesday 10 June 2015 19:36:18 Ric Moore wrote:
> Add "contrib" and "non-free" components to /etc/apt/sources.list, for
> example:
>
> # Debian 8 "Jessie"
> deb http://http.debian.net/debian/ jessie main contrib non-free
When last heard Bret was using Squeeze. I think he looked at Wheezy, but
ame -r|sed 's,[^-]*-[^-]*-,,')
nvidia-kernel-dkms
This will also install the recommended nvidia-driver package. DKMS will
build the nvidia module for your system. (nvidia-xconfig as root)
Create an Xorg server configuration file.
Restart your system to enable the nouveau blacklist.
-
Oops, forgot to cc in the mailing list.
- Nick
On 06/10/2015 09:19 PM, Nick T. wrote:
Install build-essential it should contain all the packages necessary
to install the driver.
Also you might want to install dkms if you don't want to reinstall the
driver after every kernel update.
-
installer ncurses user interface
-> Detected 8 CPUs online; setting concurrency level to 8.
-> License accepted.
-> Installing NVIDIA driver version 346.72.
-> Performing CC sanity check with CC="/usr/bin/cc".
-> The CC version check failed:
The compiler used to compil
On Wednesday 10 June 2015 16:52:50 Bret Busby wrote:
> ERROR: Unable to find the development tool `cc` in your path; please
> make sure that you have the package 'gcc' installed. If gcc is
> installed on your system, then please check that `cc` is in your PATH.
Have you done this?
Start with:
#
ello.
The only available boot option, apart from the normal boot mode, in
the GRUB menu, for Debian 6, was the recovery mode, so I booted into
that, changed to the appropriate directory, and ran the sh command to
try to install the driver.
The error message referred to the log file;
"
:~# c
Problem fixed... Rebooting is a wondrous thing!! I ended up
re-installing the original jessie kernel to get rid of my bull in the
china shop hacking, then re-installed the firmware-b43-installer. Then
with things back the way they should be, I rebootedLife is good,
wifi is on the air.
I
On Tue, 2015-06-02 at 16:25 +0200, David Demelier wrote:
> I have a simple question, is the synaptics driver missing in the
> official Debian ISO files? Because running the graphical installer won't
> let me use my touchpad (which works pretty fine once installed).
>
>
Hello,
I have a simple question, is the synaptics driver missing in the
official Debian ISO files? Because running the graphical installer won't
let me use my touchpad (which works pretty fine once installed).
I think it should be enabled in case it's currently missing.
Regards,
On 05/25/2015 09:52 PM, Sven Arvidsson wrote:
On Mon, 2015-05-25 at 21:22 +0800, mudongliang wrote:
5. I use "glxgears -info" to test the performance. However ,the
performance is so bad ! It seems no ati driver at all!
375 frames in 5.0 seconds = 74.986 FPS
300 frames in 5.0 second
On Mon, 2015-05-25 at 21:22 +0800, mudongliang wrote:
> 5. I use "glxgears -info" to test the performance. However ,the
> performance is so bad ! It seems no ati driver at all!
> 375 frames in 5.0 seconds = 74.986 FPS
> 300 frames in 5.0 seconds = 59.857 FPS
> 300 frame
:68e4] (rev ff)
2. the installation comes from https://wiki.debian.org/AtiHowTo
Installation
The following procedure will install the open source display driver
packages, DRI modules (for 3D acceleration) and driver firmware/microcode:
1)Add "contrib" and "non-free" co
On 01-04-2015 04:11, David Wright wrote:
Quoting venkat (venka...@vortexindia.co.in):
Primary intent : To control connected HDMI and CRT monitors individually.
We use VESA as display driver for connected display(Single display).
Now, we are trying to extend and use dual display as said (HDMI
Quoting venkat (venka...@vortexindia.co.in):
> Primary intent : To control connected HDMI and CRT monitors individually.
>
> We use VESA as display driver for connected display(Single display).
> Now, we are trying to extend and use dual display as said (HDMI and
> CRT).
> We c
2.6.32 kernel with newest version of cedarview driver.
If you show me a trigger point where to start this process it would
be great.
I did a little searching, and from what I find, I don't think you can
without upgrading. The problem is not only the old kernel, but old
versions of X an
ith newest version of cedarview driver.
> If you show me a trigger point where to start this process it would
> be great.
I did a little searching, and from what I find, I don't think you can
without upgrading. The problem is not only the old kernel, but old
versions of X and the n
Hi Peter
Thanks for the response, I really understand the need for the upgrade.
We are definitely working on it.It would definitely take some time.
To handle current situation, I wanted to somehow use 2.6.32 kernel with
newest version of cedarview driver.
If you show me a trigger point where
T and HDMI) and we
> had no luck in making this display controllable.
> On goggling, it was found some graphic driver(cedarview drivers)
> issues with kernel.
> I am pretty new Linux kernel stuffs and applying upgrades.Request
> some guidance on the same.
You could start here:
http
, it was found some graphic driver(cedarview drivers) issues
with kernel.
I am pretty new Linux kernel stuffs and applying upgrades.Request some
guidance on the same.
--
Regards
Venkat.S
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe"
On 17/03/15 13:50, Elimar Riesebieter wrote:
* Andrew Wood [2015-03-17 12:18 +]:
[...]
It just lists one
01:00.0 VGA compatible controller Silicon Motion SM712
I suspect what may be happening is its defaulting to video out on the LVDS
and turning the VGA port off. Is there a way to conf
* Andrew Wood [2015-03-17 12:18 +]:
[...]
> It just lists one
>
> 01:00.0 VGA compatible controller Silicon Motion SM712
>
> I suspect what may be happening is its defaulting to video out on the LVDS
> and turning the VGA port off. Is there a way to configure it to mirror the
> output on bo
901 - 1000 of 4990 matches
Mail list logo
