similar to: Nouveau on GeForce 7950GTX (NV49)

I''ve been using ''define'' to make a few custom types. For example, I have a simple ''file'' like thing (s3::file) that downloads a file from S3, only if the one on the local machine doesn''t match, and it can send out notifications if the file changed. This is basically an exec command that uses some scripts I wrote in an

https://bugs.freedesktop.org/show_bug.cgi?id=36090 Ilia Mirkin <imirkin at alum.mit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|terminal's visual bell is |[NV34] [NV49] terminal's |very slow with nouveau |visual bell is very slow

It looks like fixed width. I just used the last position of each field to get the size and used the 'readr' package; > input <- "And XVIII 000214.5+450520 0.69 17 9 0.00 -8.7 26.8 6.44 6.78 < 6.65 -44 0.5 MESSIER031 0.6 1.54 + PAndAS-03 000356.4+405319 0.10 17 0.00 -3.6 27.8 4.38 2.8 MESSIER031

https://bugs.freedesktop.org/show_bug.cgi?id=110988 Bug ID: 110988 Summary: [NV49] Graphical issues on KDE desktop with GeForce 7950 GX2 Product: Mesa Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component:

Hello this patch is a merge of jb17bsome's nv49 patch and mine. I have tested it for a couple of days on a nv4b and didnt get crashes. Please rewiew and apply Greetings Stephan Schmid -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: nv49_nv4b.diff Url:

Commit dceef5d87 (drm/nouveau/fb: initialise vram controller as pfb sub-object) moved some code around and introduced these null derefs. pfb->ram is set to the new ram object outside of this ctor. Reported-by: Ronald Uitermark <ronald645 at gmail.com> Tested-by: Ronald Uitermark <ronald645 at gmail.com> Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> ---

https://bugs.freedesktop.org/show_bug.cgi?id=36090 --- Comment #3 from Harald Judt <h.judt at gmx.at> --- Thanks for your suggestion, but I can no longer call me owner of such a card and therefore am unable to test this. -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL:

https://bugs.freedesktop.org/show_bug.cgi?id=36090 Ilia Mirkin <imirkin at alum.mit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #4 from Ilia Mirkin <imirkin at

https://bugs.freedesktop.org/show_bug.cgi?id=36090 aebenjam at opentext.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID |--- --- Comment #5 from aebenjam at opentext.com --- Problem still exists

https://bugs.freedesktop.org/show_bug.cgi?id=36090 --- Comment #6 from Ilia Mirkin <imirkin at alum.mit.edu> --- Are you on a recent version of the ddx? (xf86-video-nouveau) Also, what card do you have (G72M means nothing to me... what does nouveau say as the "Chipset" in dmesg)? -- You are receiving this mail because: You are the assignee for the bug. -------------- next part

https://bugs.freedesktop.org/show_bug.cgi?id=36090 --- Comment #7 from aebenjam at opentext.com --- I'm not sure how to answer your question about the ddx... is this what you mean? rpm -qa |grep -i nouveau xorg-x11-drv-nouveau-1.0.7-1.fc18.i686 Re: the card, dmidecode suggests it is: Quadro NVS 110M Let me know if you need more. Thanks, Adam -- You are receiving this mail because: You

https://bugs.freedesktop.org/show_bug.cgi?id=36090 --- Comment #8 from Ilia Mirkin <imirkin at alum.mit.edu> --- dmesg | grep -i chipset sounds like your ddx is new enough though. Can you provide detailed repro steps? I'm not even sure how to enable visual bell. -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML

https://bugs.freedesktop.org/show_bug.cgi?id=36090 --- Comment #9 from aebenjam at opentext.com --- #dmesg | grep -i chipset [ 1.887251] nouveau [ DEVICE][0000:01:00.0] Chipset: G72 (NV46) Reproduction: You can fire up an xterm with -vb to request the visual bell. You can also use control + middle-mouse-button to bring up a menu which allows you to enable/disable the visual bell. Let me

https://bugs.freedesktop.org/show_bug.cgi?id=36090 --- Comment #10 from Ilia Mirkin <imirkin at alum.mit.edu> --- Hmmm... FWIW I couldn't reproduce any oddness with a NV42 card, kernel 3.11, and xf86-video-nouveau 1.0.9 both with and without xcompmgr running. Without a compositor, it _is_ a bit on the slow side, but like a half-second, nothing like the 3s delay mentioned in the original

https://bugs.freedesktop.org/show_bug.cgi?id=36090 --- Comment #11 from aebenjam at opentext.com --- Interesting. So, I'm a Fedora (currently v18) user. I created a stock account, logged in to a standard Gnome environment, and fired up an xterm with visual bell running, and it doesn't have the same problem. In fact, I couldn't even SEE a visual bell. Odd. All I could tell was that

https://bugs.freedesktop.org/show_bug.cgi?id=36090 --- Comment #12 from Ilia Mirkin <imirkin at alum.mit.edu> --- OK, by increasing the terminal size, I do indeed see that the visual bell is really rather slow. During that time, X is using up 100% CPU, so it's probably something highly unoptimal happening in the DDX. It seems like almost all of that CPU time is going into fbSolid()

https://bugs.freedesktop.org/show_bug.cgi?id=36090 --- Comment #13 from Ilia Mirkin <imirkin at alum.mit.edu> --- Looking into EXA a bit, there's a EXASolid impl shared by all pre-nv50 cards. One of the things it apparently doesn't handle are 32-bit visuals with solid draws that include a fancy "op", which I assume the visual bell would, like xor or whatever. I have a hard

https://bugs.freedesktop.org/show_bug.cgi?id=36090 Martin Peres <martin.peres at free.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |MOVED Status|REOPENED |RESOLVED --- Comment #14 from Martin Peres

https://bugs.freedesktop.org/show_bug.cgi?id=111463 Bug ID: 111463 Summary: [NV49] MMIO write FAULT at 00c200 Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: not set Priority: not set Component: Driver/nouveau Assignee: nouveau

Is this a fixed width format? If so, read.fwf() in base, or read_fwf() in the readr package will solve the problem. You may need to trim trailing spaces though. B. > On Oct 5, 2017, at 10:12 AM, jean-philippe <jeanphilippe.fontaine at gssi.infn.it> wrote: > > dear R-users, > > > I am facing a quite regular and basic problem when it comes to dealing with datasets,