[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: 2 questions



On Thu, Feb 21, 2002 at 07:51:55PM -0500, dman wrote:
> On Fri, Feb 22, 2002 at 08:38:55AM +0800, a wrote:
> | i compile kernel 2.0.36. everything else seems OK except modprobe complain
> | it can't locate char-major-10

iWhat was minor?  If 135, it is RTC.

alias char-major-10-135 rtc

You foregot to enable it when compiling kernel.  If you configure kernel
right, it will not complain and this is harmless if you do not use them.
Check "man update-modules"

> | i have a Ham modem and debian 2.2. i compile the linux driver and
> install | it. but pon fails. i use the command below: | setserial
> /dev/ttyS3 irq 10 | but it does not help.

May be you do not have serial device.

> Debian 2.2 (aka "potato") comes with kernel 2.2.20 now, and AFAIK, has
> always had a 2.2.x kernel.  

No it does not look like so.  Stable potato always and still have 2.0
kernel.  It is ultrastable so version number does not change as
frequently.

$ apt-cache policy kernel-image-2.0.38
kernel-image-2.0.38:
  Installed: (none)
  Candidate: 2.0.38-3
  Version Table:
     2.0.38-3 0
        500 http://http.us.debian.org stable/main Packages

> Your 2.0.36 kernel is extremely old (it
> was what I had when I first saw linux, RH 5.2).  First I would get a
> recent kernel.  Either 2.2.20 or 2.4.17 (I am using the latter).  Then
> check which serial device your modem is plugged in to.  It may not be
> ttyS3.  If you still don't get it to work, then come back and tell us
> what you tried and the exact error messages you got.

You can download newer precompiled one from Debian, too.  Start from
there before compiling kernel.  Also read basic documents on Debian.


-- 
~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ +++++
Osamu Aoki <debian@aokiconsulting.com>, GnuPG-key: 1024D/D5DE453D
Visit Debian reference http://www.debian.org/doc/manuals/quick-reference/
There are 6 files: index.{en|fr|it}.html quick-reference.{en|fr|it}.txt
I welcome your constructive criticisms and corrections.



Reply to: