Date: Sun, 5 Oct 2014 12:03:03 -0700 (PDT) From: Beeblebrox <zaphod@berentweb.com> To: freebsd-current@freebsd.org Subject: printing text file with LPD - non-printable characters Message-ID: <20141005220221.1ed7df8d@rsbsd.rsb> In-Reply-To: <20141005183517.GA1073@unixarea.DDR.dd> References: <1412530903064-5954561.post@n5.nabble.com> <20141005183517.GA1073@unixarea.DDR.dd>
next in thread | previous in thread | raw e-mail | index | archive | help
@Matthias: > I moved the thread by setting Reply-To: to the normal > freebsd-question@ list; I'm using the nabble interface, so if the move does not work.. (I've never tried with moved thread before). > First of all check, what encoding has your text file, UTF-8 or ISO or $ file print.txt > UTF-8 Unicode text, with very long lines > Then run the file through the filter Thanks for that idea - helped narrow down the problem to enscript: $ enscript mytext.txt -o filter.txt [ 4 pages * 1 copy ] left in ens.txt 59 lines were wrapped 7 non-printable characters Resulting file has same encoding errors as hard copy. * I should also mention that I tried this from both Desktop and from tty* with same results. * Will any environment settings affect this? The only relevant entry is: LANG=en_US.UTF-8 Regards. -- FreeBSD_amd64_11-Current_RadeonKMS ----- FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS -- View this message in context: http://freebsd.1045724.n5.nabble.com/printing-text-file-with-LPD-non-printable-characters-tp5954561p5954593.html Sent from the freebsd-current mailing list archive at Nabble.com. From owner-freebsd-current@FreeBSD.ORG Sun Oct 5 19:56:13 2014 Return-Path: <owner-freebsd-current@FreeBSD.ORG> Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id ADF524DC; Sun, 5 Oct 2014 19:56:13 +0000 (UTC) Received: from fep23.mx.upcmail.net (fep23.mx.upcmail.net [62.179.121.43]) by mx1.freebsd.org (Postfix) with ESMTP id C5A7C1A1; Sun, 5 Oct 2014 19:56:12 +0000 (UTC) Received: from edge03.upcmail.net ([192.168.13.238]) by viefep16-int.chello.at (InterMail vM.8.01.05.05 201-2260-151-110-20120111) with ESMTP id <20141005195557.DEJB709.viefep16-int.chello.at@edge03.upcmail.net>; Sun, 5 Oct 2014 21:55:57 +0200 Received: from [192.168.0.27] ([178.84.134.112]) by edge03.upcmail.net with edge id zXvv1o00z2Rg3Ey01Xvvam; Sun, 05 Oct 2014 21:55:56 +0200 X-SourceIP: 178.84.134.112 Message-ID: <1412538862.1608.2.camel@rainbow-runner.nl> Subject: Re: i915 driver update testing From: Koop Mast <kwm@rainbow-runner.nl> To: Konstantin Belousov <kostikbel@gmail.com> Date: Sun, 05 Oct 2014 21:54:22 +0200 In-Reply-To: <20141003170258.GG26076@kib.kiev.ua> References: <20141003170258.GG26076@kib.kiev.ua> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.12.6 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Cc: x11@freebsd.org, current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current <freebsd-current.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>; List-Post: <mailto:freebsd-current@freebsd.org> List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sun, 05 Oct 2014 19:56:13 -0000 On Fri, 2014-10-03 at 20:02 +0300, Konstantin Belousov wrote: > Please find at the > https://kib.kiev.ua/kib/drm/i915.1.patch > a patch which provides some updates to the i915 driver. At large, this > is import of the batch of Linux commits, and as such, it is interesting > mostly as attempt to restart the race to get us more up to date Linux code > imported. It might provide some bug fixes, most likely for IvyBridge. > Interesting from the development PoV is the update of the GEM i/o ioctl > code path to mimic Linux code structure. > > I am asking _only_ for reports of regressions with the patch applied, > comparing with the code which is currently in HEAD. I will not debug > any existing bugs, my goal right now is to commit this update, which is > needed for further work. I.e., only when you get an issue with the patch > applied, but cannot reproduce the problem without the patch, please > prepare a bug report. > > FYI, the driver will attach to haswell gfx, but I am not interested in > reports about this (see above paragraph). On my test box, which is Core > i7 4770S, the mode-setting and front-buffer rendering works, but Mesa > immediately cause renderer to bug out. > > Work was sponsored by The FreeBSD Foundation, both by time and hardware, > and Intel provided access to the documentation. Hi, I got a working X-server and framebuffer console on my Sandybridge system. The only regression I noticed so far is the line below, where the number after 'expected' changes per time the line is printed. Oct 5 21:50:12 crashalot kernel: error: [drm:pid1049:gen6_sanitize_pm] *ERROR* Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS expected 160d0000, was 16000000 Oct 5 21:51:04 crashalot kernel: error: [drm:pid1049:gen6_sanitize_pm] *ERROR* Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS expected 160d0000, was 16000000 Oct 5 21:53:14 crashalot kernel: error: [drm:pid1170:gen6_sanitize_pm] *ERROR* Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS expected 160d0000, was 16000000
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20141005220221.1ed7df8d>