similar to: [Bug 108043] New: Nouveau reports timeout on MX150

I always forget those CC's :(( ---------- Forwarded message ---------- Date: Tue, 22 Aug 2000 18:39:14 +0200 (CEST) From: Igmar Palsenberg <i.palsenberg at jdimedia.nl> To: zack at wolery.cumb.org Subject: Re: Work around Linux kernel bug provoked by nchan.c Hi, Regarding this bug : the man page states : On success, zero is returned. On error, -1 is returned and errno is set

Hi, I just finished integrating CryptoCard support in OpenSSH. - Native X9.9 support. Should work with CryptoCard en Secure Computing tokens. This basically gives support for Challenge / Response - Licensed under BSD license I'll put the patch on http://www.jdimedia.nl/igmar/pam, but that wil shorty change to projects.jdimedia.nl. If desired I could also put in on the mail. Let me

Hi, Patch that makes CryptoCard word natively with OpenSSH is on http://www.jdimedia.nl/igmar/openssh Damien, please forward this to any list you thing is relevant. Regards, Igmar Palsenberg JDI Media Solutions -- Igmar Palsenberg JDI Media Solutions Jansplaats 11 6811 GB Arnhem The Netherlands mailto: i.palsenberg at jdimedia.nl

Hi, I usually stay away from issues like this, basically because I'm not a lawyer (and don't want to be one), and I don't have a real interest in these issues. Quoting Tatu : > We also have a trademark pending on the Secure Shell mark This seriously undermines the IETF standard draft. It's the same as registering 'milk' as a trademark. Both Secure and Shell are

Some reactions on the thread : Integrating SmartCard in PAM is no problem. Problem I'm facing with for example CryptoCard and SecureID tokens is that those manufacturers refuse to give out any form of information about the internal operation of those tokens. That prevents me from implementing event synchronous mode. The best way to handle this with SSH is probably the way for example Apache

Hi, I've got a system with a 3com 590 NIC (Boomerang / Vortex), and instructed it to boot using PXE. System load the initrd and the kernel image from the FTP server, boots the image and starts the install routine. So far so good. The strange part is that after the PXE boot completes the kernel doesn't detec the NIC. It's not a driver issue, the same kernel on a floppy does

Hi, OpenSSH doesn't comply to the PAM spec, and always assume that a password is asked. This prevents for example pam-cryptocard from operating. I'll post a patch this week to make things work.... (and will also change the pam-cryptocard name. It's to confusing :) Regards, Igmar -- -- Igmar Palsenberg JDI Media Solutions Jansplaats 11 6811 GB Arnhem The Netherlands

https://bugs.freedesktop.org/show_bug.cgi?id=107959 Bug ID: 107959 Summary: System hangs up when loading nouveau for NVIDIA MX150 card Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component:

Hi, I had a contractor write a patch to allow CryptoCard support in OpenSSH. It works with portable openssh-2.1.1p4, and it was posted to the SSH mailing lists, but I see that it hasn't been included in the openssh-2.2.0p1 release. Would it be possible to include this patch in the official release? The reason why I ask is because it will not be difficult to do that, it will support the

[+cc Intel folks] On Fri, Aug 31, 2018 at 03:30:57PM +0800, Daniel Drake wrote: > On over 40 Intel-based Asus products, the nvidia GPU becomes unusable > after S3 suspend/resume. The affected products include multiple > generations of nvidia GPUs and Intel SoCs. After resume, nouveau logs > many errors such as: > > fifo: fault 00 [READ] at 0000005555555000 engine 00 [GR]

On 38+ Intel-based Asus products, the nvidia GPU becomes unusable after S3 suspend/resume. The affected products include multiple generations of nvidia GPUs and Intel SoCs. After resume, nouveau logs many errors such as: fifo: fault 00 [READ] at 0000005555555000 engine 00 [GR] client 04 [HUB/FE] reason 4a [] on channel -1 [007fa91000 unknown] DRM: failed to idle channel 0 [DRM]

On over 40 Intel-based Asus products, the nvidia GPU becomes unusable after S3 suspend/resume. The affected products include multiple generations of nvidia GPUs and Intel SoCs. After resume, nouveau logs many errors such as: fifo: fault 00 [READ] at 0000005555555000 engine 00 [GR] client 04 [HUB/FE] reason 4a [] on channel -1 [007fa91000 unknown] DRM: failed to idle channel 0 [DRM]

https://bugs.freedesktop.org/show_bug.cgi?id=108047 Bug ID: 108047 Summary: No recognition of DVI-D monitor Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at

https://bugs.freedesktop.org/show_bug.cgi?id=107628 Bug ID: 107628 Summary: On GeForce 8200M G, driver reports wild temperature fluctuations, effectively blocking the system at boot Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal

Hello, I'm asking if there is a way to do extra troubleshooting for admin auth, by adjusting a config parameter (i.e. loglevel), then looking at log files. Sometimes I can auth properly when trying to update metadata using a url with basic auth embedded before the server/hostname, requested from a web browser like google chrome. i.e. http://admin:password at

======================================================== "By failing to prepare, you are preparing to fail." Benjamin Franklin ======================================================== Release Announcements --------------------- This is the latest stable release of the Samba 4.9 release series. Major enhancements include: --------------------------- o s3: nmbd: Stop

======================================================== "By failing to prepare, you are preparing to fail." Benjamin Franklin ======================================================== Release Announcements --------------------- This is the latest stable release of the Samba 4.9 release series. Major enhancements include: --------------------------- o s3: nmbd: Stop

https://bugs.freedesktop.org/show_bug.cgi?id=107003 Bug ID: 107003 Summary: Timeout in nvkm_falcon_v1_clear_interrupt on gp104 Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

https://bugs.freedesktop.org/show_bug.cgi?id=110931 Bug ID: 110931 Summary: Timeout initializing Falcon after cold boot Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee:

https://bugs.freedesktop.org/show_bug.cgi?id=69465 Priority: medium Bug ID: 69465 Assignee: nouveau at lists.freedesktop.org Summary: Kernel freeze with NVA3 kernel 3.11.1 / PGRAPH][0000:01:00.0] PGRAPH TLB flush idle timeout fail QA Contact: xorg-team at lists.x.org Severity: critical