From: Marvin Stodolsky <stodolsk@rcn.com>
To: Martin Mares <mj@suse.cz>
Cc: linux-kernel@vger.kernel.org, Jacques.Goldberg@cern.ch,
Mark Spieth <mark@digivation.com.au>,
Sean Walbran <sean@walbran.org>
Subject: Re: BIOS problem, pro Microsoft, anti other OS
Date: Mon, 25 Dec 2000 13:25:06 -0500 [thread overview]
Message-ID: <3A479102.C7611586@rcn.com> (raw)
In-Reply-To: <3A4769AC.F38B372C@rcn.com> <20001225170914.A15598@atrey.karlin.mff.cuni.cz>
Jacques
> Can you check what does Linux 2.4.0-test<latest> behave, please?
Are you comfortable compiling kernels?
If not I'll compile one for you for the test.
Currently I'm happily under 2.4.0-test 12:
lsmod:
Module Size Used by
ppp_deflate 39164 1 (autoclean)
bsd_comp 4148 0 (autoclean)
ppp_async 6220 1 (autoclean)
ppp_generic 12820 2 (autoclean) [ppp_deflate bsd_comp
ppp_async]
ltmodem 364948 1
input 3328 0
serial 42192 1 (autoclean) (ONLY suporting my mouse)
isa-pnp 27528 0 (autoclean) [ltmodem serial]
usbcore 27684 0 (unused)
Martin
Are there any particular kernel config choices that will be
beneficial for this problem?
Mark
> You probably should make the ltmodem driver check the region base
> registers and interrupts and if they are not set, recommend the user to
> change the OS or PNP settings in their BIOS setup.
Can these be included in the LTmodem packages you are working up?
MarvS
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-25 18:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-25 15:37 BIOS problem, pro Microsoft, anti other OS Marvin Stodolsky
2000-12-25 16:09 ` Martin Mares
2000-12-25 18:25 ` Marvin Stodolsky [this message]
2000-12-26 19:37 ` David Riley
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=3A479102.C7611586@rcn.com \
--to=stodolsk@rcn.com \
--cc=Jacques.Goldberg@cern.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@digivation.com.au \
--cc=mj@suse.cz \
--cc=sean@walbran.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.