search for: trackpoints

Displaying 20 results from an estimated 26 matches for "trackpoints".

Did you mean: tracepoints
2014 May 11
0
irq 45: nobody cared (try booting with the "irqpoll" option)
Hello, [ 4.762826] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [ 5.025098] udevd[441]: starting version 175 [ 5.134411] i2c i2c-0: nForce2 SMBus adapter at 0x2140 [ 5.134585] i2c i2c-1: nForce2 SMBus adapter at 0x2100 [ 5.137320] ACPI: bus type USB registered [ 5.137444] usbcore: registered new interface driver usbfs [ 5.137535] usbcore: registered
2009 May 04
1
Please help me subset this dataframe, thanks...
Dear R-helpers, I have a dataframe called "trackpoints" with several columns including a column called "time", eg: > trackpoints ?? ? ? ?time 1 ? 12:00:00 2 ? 12:00:01 3 ? 12:00:02 . . . 298 12:04:57 299 12:04:58 300 12:04:59 I also have a dataframe called "data" that contains columns called "ID", "start&quo...
2016 Dec 07
2
GM108GLM?
Hi again, It works :-) Reclocking, however, is another kettle of fish. Trying #echo 0f > /sys/kernel/debug/dri/0/pstate hangs X. Trying the same with no X running reveals: Dec 7 10:08:42 dell-smo kernel: [ 728.831020] nouveau 0000:08:00.0: clk: unable to find matching pll values a number of time as then soft lockup. Very much akin to
2016 Dec 08
2
GM108GLM?
Hi, With drm-next from http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-next/2016-12-08/ I don't get the error messages, but I still get a soft cpu lockup. What info would you need from me to get it working? Best regards, Sune Mølgaard On 2016-12-08 08:10, Karol Herbst wrote: > hi, > > give the drm-next kernel tree a try. Sadly the reclocking improvements didn't land with
2016 Dec 08
2
GM108GLM?
Aha! That seems to do it. If I interpret correctly, it doesn't set it quite to full power, though, but it's certainly an improvement: 07: core 405 MHz memory 810 MHz 0a: core 270-1124 MHz memory 1600 MHz 0f: core 270-1124 MHz memory 2002 MHz AC DC * AC: core 1012 MHz memory 2002 MHz A short run of glmark2 shows aver 100% improvement to ~550 FPS. Interestingly, it's still nowhere
2016 Oct 27
0
GM108GLM?
Hello, The idea was to use the modesetting DDX instead of Nouveau’s one for Maxwell+ as EXA was [broken][1]. But you can give a try at Ilia’s [patches][2], which fix the Nouveau DDX for GM10x and GM20x (I don’t think it has been tested on a GM108 yet). Best regards, Pierre Moreau [1]: https://cgit.freedesktop.org/nouveau/xf86-video-nouveau/commit/?id=3e2e0faa2ee1cce9c1bb5c7ad80d0592460f3edc
2016 Dec 08
0
GM108GLM?
hi, give the drm-next kernel tree a try. Sadly the reclocking improvements didn't land with 4.9, so 4.10 is required. Greetings. On 7 December 2016 10:26:44 a.m. GMT+01:00, "Sune Mølgaard" <smo at translucent.dk> wrote: >Hi again, > >It works :-) > >Reclocking, however, is another kettle of fish. > >Trying #echo 0f > /sys/kernel/debug/dri/0/pstate
2016 Dec 08
0
GM108GLM?
also you can't change the clocks when there is nothing running on the GPU. I have some patches pending for this in another series, but maybe I may be able toe extract those fixes. Changing the clocks while something is running shouldn't cause any troubles. Alternatively if you don't care about power consumption, you can boot with nouveau.runpm=0 so that the gpu is always on.
2016 Dec 08
0
GM108GLM?
you can boot with nouveau.config=NvBoost=2 to enable higher clocks, but that won't fill in the difference compared to Intel. For this there are some changes needed on the mesa side regarding scheduling. Also keep in mind, that PCIe is an important bottleneck here, because the GPU can't push frames fast enough through the bus, that's why any "high FPS" benchmark will be in
2016 Oct 18
2
GM108GLM?
Hi, It would seem like it (attachments are from 4.9-rc1, btw), but it doesn't look like there is any support in the Xorg driver. How can I help with that? Best regards, Sune Mølgaard Translucent ApS On 2016-04-22 09:33, Pierre Moreau wrote: > Hello, > > A patch was merged yesterday to recognise GM108 (see >
2008 Nov 27
2
Mouse crazy on Full screen app + Tablet PC
Hi, I don't really expect this to get fixed but I have an issue and I was hoping someone would be able to at least diagnose it. I have a X41T Thinkpad. It is a tablet pc and when I have a full screen app (i.e. game) open the digitizer pen goes nuts. The cursor tries to go off the screen. Holding it perfectly still will cause the mouse to glide slowly across the screen while moving it
2016 Apr 28
0
[ANNOUNCE] xf86-input-synaptics 1.8.99.1
The first snapshot for synaptics 1.9 is now available. A bunch of patches that have been sitting on git master for quite a while now but many of these have been ported over to the 1.8.x stable releases. Perhaps the most (in)significant change in this release is that we dropped touch events from the driver. Previously, when all in-driver gestures like two-finger scrollings were disabled, the
2016 Mar 01
3
[REGRESSION] nouveau: 30 second boot hang after commit 2b700825e
Hello, I am encountering a 30 second hang during boot, in the Xorg process just before the display manager comes up. I have bisected the problem to the following commit: commit 2b700825e7a7702fb862edba1262c98040dc1bf6 Author: Ben Skeggs <bskeggs at redhat.com> Date: Thu Aug 20 14:54:22 2015 +1000 drm/nouveau/mc: move device irq handling to platform-specific code The hang only
2014 Jun 13
2
REGRESSION: Kernel PANIC 8777c5c11764d8336d8270f96778158c34c92108 - drm/nouveau/dp: probe dpcd to determine connectedness
Hello Ben, commit (mini) [~/work/linux-2.6] git bisect bad 8777c5c11764d8336d8270f96778158c34c92108 is the first bad commit commit 8777c5c11764d8336d8270f96778158c34c92108 Author: Ben Skeggs <bskeggs at redhat.com> Date: Fri Jun 6 18:09:55 2014 +1000 drm/nouveau/dp: probe dpcd to determine connectedness Signed-off-by: Ben Skeggs <bskeggs at redhat.com> introduces a
2014 Jun 15
0
REGRESSION: Kernel PANIC 8777c5c11764d8336d8270f96778158c34c92108 - drm/nouveau/dp: probe dpcd to determine connectedness
On Fri, Jun 13, 2014 at 7:58 PM, Thomas Glanzmann <thomas at glanzmann.de> wrote: > Hello Ben, > commit Hey Thomas, Are you able to double-check that bisect? I'm not at all sure how that particular commit could trigger the issue you're seeing. Some of the others, certainly. It might be worth trying a couple of times before marking something as "good", in case
2013 Dec 06
2
Regression: drm/nouveau/clk: implement power state and engine clock control in core (7c856522069755ab9d163a24ac332cd3cb35fe30) breaks GeForce 9400 on Intel Mac Mini Model November 2010 model
Hello everyone, the current git HEAD of Linus Torvalds tree breaks Nouveau on my Mac Mini Model 2010. I get variation of the following kernel panic when booting. (gateway) [~] nc -u -l -p 6666 [ 3.796018] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 3.796100] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 3.796304] ata1.00: ATA-7: INTEL SSDSA2M160G2GC, 2CV102HA, max
2016 Oct 14
4
CentOS on new Dell
On 10/13/2016 7:10 PM, Rob Kampen wrote: >> Mmn, that didn't work. I dd'd the latest Fedora Live iso onto a USB >> drive, put it into a brand spanking new Dell Latitude E7470, hit F12 >> at Dell logo and got "Selected boot device failed". Do I need to make >> it bootable using fdisk or some such? > Not that I recall - a simple dd of the iso onto a usb
2016 Oct 27
0
Fwd: CentOS on new Dell
On Mon, Oct 24, 2016 at 8:11 PM, Milos Blazevic <milos.blazevic at sbb.rs> wrote: > I've seen the thread(s) you started on CentOS mailing list about Dell and ThinkPad > laptops and running Centos on 'em. > > Not sure if you've seen my question, but I'm considering to purchase a laptop, run EL7 on it, and I'm weighing between the Thinkpad and Latitude, so: >
2016 Oct 28
1
Fwd: CentOS on new Dell
On 10/27/2016 04:22 PM, Michael B Allen wrote: > On Mon, Oct 24, 2016 at 8:11 PM, Milos Blazevic <milos.blazevic at sbb.rs> wrote: >> I've seen the thread(s) you started on CentOS mailing list about Dell and ThinkPad >> laptops and running Centos on 'em. >> >> Not sure if you've seen my question, but I'm considering to purchase a laptop, run EL7 on
2014 Aug 30
5
[Bug 83271] New: Windowed mode causes framebuffer not to refresh with PRIME on optimus/kepler discrete GPU
https://bugs.freedesktop.org/show_bug.cgi?id=83271 Priority: medium Bug ID: 83271 Assignee: nouveau at lists.freedesktop.org Summary: Windowed mode causes framebuffer not to refresh with PRIME on optimus/kepler discrete GPU QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified