similar to: NV130 - gtx 1050 ti

On 05/04/2017 04:00 AM, Pierre Moreau wrote: > Hello, > > Acceleration for Pascal cards is coming in Linux 4.12, support for Pascal cards > in xorg-video-nouveau is in 1.0.15, and if I remember correctly, on the > Mesa-side, you will need >=17.0. Thanks - I suspected it was too new. I'm finding the monitor capabilities miss identified even if I use an older card - I'm

This is sort of working -- but I can't get it to do a 4k output. Not sure how the monitor resolution is detected - This monitor is supposed to do 3480x1200 60hz 4:4:4 But the info I get from hwinfo is different. How does nouveau get this information? If it is from an ID - with a list - the list is probably is wrong. # hwinfo --monitor 95: None 00.1: 10002 LCD Monitor [Created at

Hello, Acceleration for Pascal cards is coming in Linux 4.12, support for Pascal cards in xorg-video-nouveau is in 1.0.15, and if I remember correctly, on the Mesa-side, you will need >=17.0. Pierre On 02:04 am - May 04 2017, Karl Schmidt wrote: > This is probably the problem > May 3 16:44:45 kernel: [ 7.068336] nouveau E[ DEVICE][0000:08:00.0] unknown chipset, 0x137000a1 > May

On 05/06/2017 12:38 PM, Ilia Mirkin wrote: > The information comes from the EDID blob supplied by the monitor. > Presumably hwinfo has a primitive EDID parser, which is where that > information comes from. A more complete EDID parser is available at > > https://cgit.freedesktop.org/xorg/app/edid-decode/ > > For example, > > $ ./src/edid-decode/edid-decode

First things first -- I've alluded to this before, but let me be clear -- there is no global database that contains monitor-specific information which is used by any linux drivers. Please forget any notions you had of such a thing existing or being used. The information comes from the EDID blob supplied by the monitor. Presumably hwinfo has a primitive EDID parser, which is where that

The correct way has to be one or the other: http://wiki.dovecot.org/LDA/Exim are mutually exclusive with http://wiki.dovecot.org/HowTo/DebianStable It appears that exim can either call dovecot's LDA or make the delivery itself. There may be good reasons to do it one way or the other. ---------------------------------------------------------------- Karl Schmidt

I have a need to have a live Linux (Debian or sysrescued ) to boot off a hard-drive so that the hard-drive ends up umounted after boot. (for running partimage ). I've gone down the memdisk iso route and read about the issues there - I've seen a way to do this by mounting over nfs (messy) - but I want to do this without the network. I'm thinking that there should be a way to loop

This is set up with Win2K boxes sharing a QB file on a SAMBA share. It may be quite different than with 95-98x-ME(Miserable Edition). There are two or more problems - one thing I identified is that it is possible for two computers to connect to the QB(QuickBooks) share using the same quick books logon - something that will cause data corruption. (Something that could have been easily

Someone might want to add this to the docs - cable list and compatibility list - took me way to long to find. I was trying to find information on my UPS and came up with the following names for the same UPS series. Powerware 5119 Exide name was NetUPS SE Deltec name was PowerRite Pro II (1000VA-3000VA) What I have: The Exide NETUPS SE model PRC2400a p/n 05144038-3904 OUTPUT 2400VA 1600 WATTS

I just moved to dovecot with Maildir. I think this is probably a stupid question, but I couldn't find an answer after an hour of googling and searching the wiki. What would happen if I ran a script that did this: mv ~/Maildir/.folder_one/cur/* ~/Maildir/.folder_two/cur/ My hunch is it might break things. What if dovecot was stopped? ,.,.,. Where can I find a list of files in

Something came up that Confounded problems in my move from UW-imap to dovecot. I found a problem with the new icedove update in Debian lenny when moving from 1.5.0.13+1.5.0.14b.dfsg1-0etch1 to 2.0.0.9-3 that could look like a dovecot issue. Icedove runs for a while but eventually quits updating the displayed email, yet appears to be working and busy trying to get messages from the server. I

I've been trying to use memdisk with grub2 to boot some iso images -( I've done this without any problem with pxe ) There is a memdisk.mod in /boot/grub/ and I've seen some material talking about this, but no example of a menu. After trying countless permutations - Right now I have : menuentry "Memtest-Plus 4.2" { echo `hello` insmod lvm

I was getting a glicthy checkerboard mess at the cursor in some programs (konsol+) with # cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-4.9.0-2-amd64 root=UUID=4107d1db-62a3-427c-8515-c954a103ce25 ro text quiet changed the command line in a blind attempt to: $ cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-4.9.0-2-amd64 root=UUID=4107d1db-62a3-427c-8515-c954a103ce25 ro nouveau.config=NvForcePost=1

https://bugzilla.mindrot.org/show_bug.cgi?id=2327 Bug ID: 2327 Summary: sshd to log one unique string or prefix after connection failure, no matter why. Product: Portable OpenSSH Version: 6.7p1 Hardware: All OS: Linux Status: NEW Severity: enhancement Priority: P5

On Wed, 16 Aug 2017 12:46:46 -0700, H. Peter Anvin via Syslinux wrote: >Is that true for vesamenu only, or even for text mode syslinux? Hi, I'm using menu.c32 (text mode only), this is the complete config: [root at archlinux ~]# cat /boot/syslinux/syslinux.cfg # http://syslinux.zytor.com/wiki/index.php/Doc/menu PROMPT 0 TIMEOUT 600 UI menu.c32 MENU HIDDEN MENU CLEAR MENU COLOR screen

Hi, my primary monitor is a LCD HDMI2 and the secondary monitor is a CRT VGA1. The CRT monitor is only turned on on demand, but always connected by VGA. The BIOS is shown on both monitors, but the syslinux menu only on the CRT, as long as the CRT is connected by VGA. Even if it's turned off, the syslinux menu isn't shown on the LCD connected by HDMI. [root at archlinux ~]# pacman -Q

https://bugs.freedesktop.org/show_bug.cgi?id=54512 Bug #: 54512 Summary: xrandr does not detect screen Classification: Unclassified Product: xorg Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

On Tue, Dec 04, 2018 at 08:03:53AM +0100, Andrzej Hajda wrote: > On 03.12.2018 22:48, Ville Syrjälä wrote: > > On Thu, Nov 29, 2018 at 09:46:16AM +0100, Andrzej Hajda wrote: > >> Quite late, hopefully not too late. > >> > >> > >> On 21.11.2018 12:51, Ville Syrjälä wrote: > >>> On Wed, Nov 21, 2018 at 01:40:43PM +0200, Jani Nikula wrote: >

Ah, I thought you missed in my earlier reply the part about a bug with debug printouts in 2.8.0 (fixed on master since), did not comment on that when you replied with quoting... So, for now options are to bump debugging to 3+ or to build your own in one of many ways possible :\ On Wed, Jul 5, 2023, 06:23 Karl Schmidt <karl at lrak.net> wrote: > On 7/4/23 10:01PM, Jim Klimov wrote: >

On 7/4/23 10:01PM, Jim Klimov wrote: > Normally yes - enable and start the target and the particular services relevant to your setup. > > For the binary you have from packaging (if not rebuilt as suggested earlier), set debug_min=3 in ups.conf section for > upscode2, to currently trade driver viability for some storage traffic with more logs :\ > > Sorry about?that, > Jim