public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: pazke@orbita1.ru
To: linux@horizon.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: What's the status of kernel PNP?
Date: Mon, 9 Jul 2001 12:51:15 +0400	[thread overview]
Message-ID: <20010709125115.A19087@orbita1.ru> (raw)
In-Reply-To: <20010709105756.A18230@orbita1.ru> <20010709073410.1567.qmail@science.horizon.com>
In-Reply-To: <20010709073410.1567.qmail@science.horizon.com>; from linux@horizon.com on Mon, Jul 09, 2001 at 07:34:10AM -0000

[-- Attachment #1: Type: text/plain, Size: 2358 bytes --]

On Mon, Jul 09, 2001 at 07:34:10AM -0000, linux@horizon.com wrote:
> > Please provide more detailed hardware description and a output of
> > 'cat /proc/isapnp'.  IMHO this problem can be solved easily.
> 
> Thank you for being so soothing.  As you could probably notice, I was a bit
> frustrated.
> 
> On the first machine, with the modem (note that I ran isapnp manually, since
> this modem is my net connection!):
> 

> Card 1 'MOT15f0:Motorola VoiceSURFR 56K Modem' PnP version 1.0
>   Logical device 0 'MOT15f0:Unknown'
>     Supported registers 0x2
>     Compatible device MOT15f0
>     Device is active
>     Active port 0xffff,0xffff,0xffff,0xffff,0xffff,0xffff,0xffff,0xffff
		  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
		    
Use of isapnptools package mixed with kernel 2.4.x ISA PNP subsystem is asking 
for trouble. Move /etc/isapnp.conf file to some other place and try to reboot.

[SNIP]

> isapnp: Scanning for PnP cards...
> isapnp: Card 'Motorola VoiceSURFR 56K Modem'
> isapnp:   Device 'Unknown'
> isapnp: 1 Plug & Play card detected total
> PnP: PNP BIOS installation structure at 0xc00fdbd0
> PnP: PNP BIOS version 1.0, entry at f0000:d20e, dseg at f0000
> Linux NET4.0 for Linux 2.4
> Based upon Swansea University Computer Society NET3.039
> Initializing RT netlink socket
> apm: BIOS version 1.1 Flags 0x03 (Driver version 1.14)
> Starting kswapd v1.8
> parport0: PC-style at 0x378, irq 7 [PCSPP(,...)]
> matroxfb: Matrox Millennium (PCI) detected
> matroxfb: 640x480x8bpp (virtual: 640x13081)
> matroxfb: framebuffer at 0xFE000000, mapped to 0xc6807000, size 8388608
> Console: switching to colour frame buffer device 80x30
> fb0: MATROX VGA frame buffer device
> pty: 256 Unix98 ptys configured
> Serial driver version 5.05b (2001-05-03) with MANY_PORTS SHARE_IRQ SERIAL_PCI ISAPNP enabled
> ttyS00 at 0x03f8 (irq = 4) is a 16550A
> ttyS01 at 0x02f8 (irq = 3) is a 16550A
> ttyS02 at port 0x03e8 (irq = 5) is a 16550A
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Hmm, looks strange to me, it seems that serial driver found your modem and configured
it as /dev/ttyS2. Did you try to test it with minicom for example ?

-- 
Andrey Panin            | Embedded systems software engineer
pazke@orbita1.ru        | PGP key: http://www.orbita1.ru/~pazke/AndreyPanin.asc

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

       reply	other threads:[~2001-07-09  8:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20010709105756.A18230@orbita1.ru>
     [not found] ` <20010709073410.1567.qmail@science.horizon.com>
2001-07-09  8:51   ` pazke [this message]
     [not found]     ` <20010709112502.3364.qmail@science.horizon.com>
2001-07-11 14:12       ` What's the status of kernel PNP? pazke
2001-07-07  5:48 linux

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010709125115.A19087@orbita1.ru \
    --to=pazke@orbita1.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@horizon.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox