Your message dated Sat, 22 Oct 2005 04:43:37 +0200 with message-id <[EMAIL PROTECTED]> and subject line kernel hardware autodetection fails to detect the SupraExpress 56i Sp Intl has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -------------------------------------- Received: (at submit) by bugs.debian.org; 19 Feb 2005 17:27:32 +0000 >From [EMAIL PROTECTED] Sat Feb 19 09:27:32 2005 Return-path: <[EMAIL PROTECTED]> Received: from fep02-0.kolumbus.fi (fep02-app.kolumbus.fi) [193.229.0.44] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1D2YOB-0001V8-00; Sat, 19 Feb 2005 09:27:31 -0800 Received: from saempy ([81.197.35.158]) by fep02-app.kolumbus.fi with SMTP id <[EMAIL PROTECTED]> for <[EMAIL PROTECTED]>; Sat, 19 Feb 2005 19:27:29 +0200 Message-ID: <[EMAIL PROTECTED]> From: "Sami Aario" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Subject: kernel hardware autodetection fails to detect the SupraExpress 56i Sp Intl Date: Sat, 19 Feb 2005 19:18:52 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1478 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478 Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-6.5 required=4.0 tests=BAYES_10,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Package: kernel-source-2.6.8 Version: 2.6.8-7 Severity: normal The kernel hardware autodetection fails to detect my SupraExpress 56i Sp Intl modem. Adding the appropriate hardware identification string into drivers/serial/8250_pnp.c fixes this problem. Here's the patch: --- drivers/serial/8250_pnp.c 2005-02-10 20:55:36.000000000 +0200 +++ /home/saempy/8250_pnp.c 2005-02-10 20:55:04.000000000 +0200 @@ -276,6 +276,8 @@ { "SUP1590", 0 }, /* SupraExpress 33.6 Data/Fax PnP modem */ { "SUP1760", 0 }, + /* SupraExpress 56i Sp Intl */ + { "SUP2171", 0 }, /* Phoebe Micro */ /* Phoebe Micro 33.6 Data Fax 1433VQH Plug & Play */ { "TEX0011", 0 }, I didn't use a Tags: patch line because this patch might cause other problems with hardware configuration: resource conflicts etc. But the modem works. -- Sami Aario --------------------------------------- Received: (at 296011-done) by bugs.debian.org; 22 Oct 2005 02:43:37 +0000 >From [EMAIL PROTECTED] Fri Oct 21 19:43:37 2005 Return-path: <[EMAIL PROTECTED]> Received: from baikonur.stro.at [213.239.196.228] by spohr.debian.org with esmtp (Exim 3.36 1 (Debian)) id 1ET9M8-0003jV-00; Fri, 21 Oct 2005 19:43:37 -0700 Received: from sputnik (stallburg.stro.at [128.131.216.190]) by baikonur.stro.at (Postfix) with ESMTP id 011585C01A for <[EMAIL PROTECTED]>; Sat, 22 Oct 2005 04:43:42 +0200 (CEST) Received: from max by sputnik with local (Exim 4.54) id 1ET9M9-0008K1-L1 for [EMAIL PROTECTED]; Sat, 22 Oct 2005 04:43:37 +0200 Date: Sat, 22 Oct 2005 04:43:37 +0200 From: maximilian attems <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: kernel hardware autodetection fails to detect the SupraExpress 56i Sp Intl Message-ID: <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.9i X-Virus-Scanned: by Amavis (ClamAV) at stro.at Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Level: X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no version=2.60-bugs.debian.org_2005_01_02 Version: linux-source-2.6.14 thanks for your bug report, your patch landed in 2.6.14 upstream. sorry that nobody followed up ealier. should work with this image as soon as it lands in unstable. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]