Throwing this back over the fence... -- Baloo
--- Begin Message ---
- To: Paul Johnson <baloo@ursine.dyndns.org>
- Subject: Re: More modem problems with kernel 2.4.18
- From: Seth Carbon <sjcarbon@eskimo.com>
- Date: 18 Jun 2002 11:16:20 -0700
- Message-id: <1024424183.7624.17.camel@gloria>
- In-reply-to: <[🔎] 20020618101304.GH17098@ursine.dyndns.org>
- References: <[🔎] 1024366982.4491.2.camel@gloria> <[🔎] 20020618101304.GH17098@ursine.dyndns.org>
On Tue, 2002-06-18 at 03:13, Paul Johnson wrote: > Your internal modem, if roasted and ground sufficiently fine, will make > a surprisingly strong espresso. Go get an external modem. > > http://www.linuxmafia.com/~rick/faq/#internalmodem Even if I'm destined for a good string cup, I'd still like to be able to figure out what's going on :) Some thoughts before I go the external road: 1) The modem has worked fine with every kernel I've put in since I installed potato. Now both potato (with bunk's upgrades) and woody fail. 2) /proc/* information and setserial information are at odds with each other. I mean--jeez--the irq info is missing altogether... 3) The system refuses to even acknowledge that there may be a modem there in the first place, making it hard to diagnose once running. All of this seems to indicate to me that there may be some kernel bug--but I have no idea where to start if it is. This modem is definitely not a win/linmodem. I have also spend some time playing with the jumpers trying to give the kernel (if it even is a kernel problem) a friendly reminder of what the proper information is--but to no avail. Any further thoughts (would I like cream with that? :) ) are greatly appreciated. -Seth
--- End Message ---
Attachment:
pgp1RE76gOF3u.pgp
Description: PGP signature