Linux-Setup Digest #340, Volume #21 Thu, 31 May 01 07:13:11 EDT
Contents:
Re: Monitor error ([EMAIL PROTECTED])
Re: Toshiba laptop and Linux trouble ([EMAIL PROTECTED])
Re: Help, I'm trying to find COM2 (KCmaniac)
Re: Can't open dependencies file ("BetrOffDed")
You may now safely reboot! (Perry)
Re: Apache question ("Nils O. Sel�sdal")
Re: Unresolvesymbles for a device driver (Gav)
CUPS filter setup (Bernd Rieke)
vgetty, mgetty and greeting message problem ("xhc")
Linux, CPU HLT instruction et software cooling ! (Georges Goncalves)
Re: SCSI problems (Trevor Hemsley)
Re: Help, I'm trying to find COM2 ("Peter T. Breuer")
Re: Help, I'm trying to find COM2 (M. Buchenrieder)
Re: Help, I'm trying to find COM2 (M. Buchenrieder)
Re: Help, I'm trying to find COM2 ("Peter T. Breuer")
Re: Help, I'm trying to find COM2 ("Peter T. Breuer")
Re: You may now safely reboot! ([EMAIL PROTECTED])
----------------------------------------------------------------------------
From: [EMAIL PROTECTED]
Subject: Re: Monitor error
Date: 31 May 2001 07:19:11 GMT
EC932 <[EMAIL PROTECTED]> wrote:
> i got mandrake installed, during
> installation, when chosing monitor, i
> picked high frequency, but when i boot
> up my monitor goes on stand by and
> all my lights flashes. how can i change
> my monitor setting so i can
> finnaly get into linux.
Start Linux in single-user typing linux single at the LILO:
prompt, then modify the /etc/inittab to start in console mode
instead of graphical mode. Edit the line
id:5:initdefault:
put a '3' where the '5' is.
Restart the machine, so you can see the login prompt, then
use Xconfigurator or whatever there is in your distribution to
fix the configuration for X. See also the XFree86-HOWTO.
Davide
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: Toshiba laptop and Linux trouble
Date: 31 May 2001 07:21:42 GMT
Zachary Wolfenbarger <[EMAIL PROTECTED]> wrote:
> I recently installed Redhat 7.1 on my Toshiba Tecra 730XCDT laptop,
> and it's been one problem after another.
Check on www.linux-laptop.net if there are special configuration
for your model. Maybe is better if you post on comp.os.linux.portable
(not sure of the NG name, check it).
Davide
------------------------------
From: KCmaniac <[EMAIL PROTECTED]>
Subject: Re: Help, I'm trying to find COM2
Date: Thu, 31 May 2001 03:21:27 -0400
> When I installed debian for the first time, it took me three days. On
> the first day I reverse engineered the package format, and installed
> enough of a basic system to begin the bootstrap. It took me two days
> to perfect the base installation (by extracting and running the
> configure scripts by hand) to the point that I could locate the package
> with the man pages in (groff?)
I don't know what you mean by groff. While in the this "base" system (I now
understand where you are
coming from, I was confusing the word base with basic) I have not been able to pull up
any man
pages...
>
> > reading what I have read, however much, and doing all what I have done. It would
>be
> > interesting to see if YOU could have made this work.
>
> Oh, I assure you, I could have.
>
Indeed.
>
> > lines do I read inbetween? How am I supposed to know?? That is why I come here.
>To amuse
> > you. I follow instructions. If the instructions are correct, I win. If they are
>not I lose.
>
> At some point, an intelligent person tosses the instructions on the
> heap, and uses their own eyes and ears and mental capacities.
> Documentation does not keep up with data, and may never have been
> correct. People who know how do not read the docs, so the docs never
> get checked by people who know how. Try writing some instructioins for
> something you know how to do, and revisit them in a years time, or give
> them to your nephew to follow! Then you'll find out what the problem
> is!
>
I know exactly what you mean. Enough said.
>
> > used to explain the install process I went through, but I guess I have a
>misunderstanding of
> > "basic". I find that amusing. So now you must believe me when I say minicom is
>not available
> > with the system I have now. You doubted me before.
>
> It certainly IS available. Try
>
> apt-get install minicom
I will.
> > What is strange here is that when I look at /proc/pci the file includes the Lucent
>Microsystems
> > WinModem and stipulating the correct IRQ and IO ports. Just what the same RH file
>is showing.
>
> This is not strange. The PCI bus reports all the devices on it.
>
This you say makes perfect sense. I did not know this. Sure. The PCI bus system
could report to
the kernal what it has on it, I guess. Sounds right.
>
> > be, considering the IRQ and IO port assignment for this card is software
>controlled on top of
> > it being a PnP peripheral and this is before I even use insmod to install the
>driver. I am
>
> No, PnP is for ISA devices. You have a PCI device.
Right again ... thank you.
>
> > thinking this kernal IS installed with the driver already. How else would
>/proc/pci know about
> > it? So armed with this information, can you tell me why isn't this kernal is not
>associating
> > the modem with a device like the kernal(2.2.14) I am using with my RH system is?
>
> I don't need the information. The fact is that you haven't installed a
> driver for the losemodem. It could hardly be otherwise, since debian
> is a gnu-centric distro, and winmodem source codes are not part of the
> linux kernel source code and are not GPL.
So what you are saying is that by using dpkg on this modem driver I got from
linmodem.org should
enable the kernal to establish the modem so that I can dial out considering there are
no
independencies that keep it from working of which, I remind you, I have nothing to do
with. You also
must be saying that the driver IS necessary for the kernal to make this establishment.
Why, then, in
my RH system does that kernal assign the modem to ttyS14 without the driver because I
install the
driver using insmod in /etc/rc.d/rc.local which is a script that runs last in the boot
process ...
long after the kernal is supposed to set up the modem. Do you see what I am saying?
If I am totally
way off base then I can understand why you would be getting bored with this
conversation. But am I?
RLH
------------------------------
From: "BetrOffDed" <[EMAIL PROTECTED]>
Subject: Re: Can't open dependencies file
Date: Thu, 31 May 2001 07:38:56 GMT
In article <9f3ita$660$[EMAIL PROTECTED]>, "Tsugi" <[EMAIL PROTECTED]>
wrote:
> Thank you for your advice. The problems I had with lilo on MBR was
> that I
> could only boot from either one Win2K or Linux since I had NTFS on
> Win2K.
> If I install lilo on MBR, it cannot see Win2K NTFS to boot it, and I
> cannot avoid
Hmmm, that's odd, my w2k is on NTFS partition too, and lilo boots it just
fine with the entry i posted earlier...
> module dependencies error if I have lilo on the first sector of linux
> root partition.
>
> I realized not having a FDD makes things a lot difficult to dualboot
> with
> linux and win2k.
> Probably it might be easier for me to get another FDD and Power supply
> and
> see if the FDD
> controller is still alive. I might even have to replace Motherboard the
> worst case.
>
> Anyways, is it possible to replace only the power cable that goes to
> FDD?
Are you sure its just the wires? Did they get pinched or cut? It shouldn't
be too hard, but some cheaper power supplies are difficult to take apart,
(i've seen some that you have to nearly destroy to open up. There weren't
screws, but instead the case was sort of crimped together.) and make sure
to watch out for charged capacitors.
> Thanks you,
>
> Tsugi
------------------------------
From: [EMAIL PROTECTED] (Perry)
Subject: You may now safely reboot!
Date: 31 May 2001 00:48:18 -0700
I have installed Linux earlier on a pc and unistalled this by deleting
partition in fdisk under DOS. Now I want install Linux again but end
in visieuze circle "Safely reboot your system".
I have tried several things, but seems something is real wrong,
Changed my harddisk, but this was also not a solution.
What's going on?
Let me subscribe the steps.
1. I insert the Red HAT 7.1 startup disk in the PC (the same disk
which I have used to install Linux earlier. Have create a new startup
disk in the meantime by rawrite from the harddisk, but doesn't changed
anything.)
2. Put the PC on.
- SYSLINUX 5.2
- Welcome to RedHat Linuz 7.1
- boot: [I push ENTER.]
3. Loading initrd.img
.
.
Running Anaconda - Please wait
exec : input/output error
install excited abnormally
sending termination signals..done
sending kill sognals done
disabling swap
unmounting filesystems
/mnt/runtime
/mnt/source/ unmount failed
/dev/pts
/proc
you may safely reboot yuour system
When I keep my diskett in the station I came on the same point.
When I keep the CDROm in the player and reboot from cd rom, I get the
message "PRESS A KEY TO REBOOT"
Who can help me out of here?
Perry
------------------------------
From: "Nils O. Sel�sdal" <[EMAIL PROTECTED]>
Crossposted-To:
linux.redhat.misc,redhat.config,redhat.networking.general,comp.os.linux.admin,comp.os.linux.help,comp.os.linux.misc,comp.os.linux.questions
Subject: Re: Apache question
Date: Thu, 31 May 2001 09:21:21 +0200
"Lamar Thomas" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> I am running RH 7.1 and I have FTP and Apache web servers working.
> However, after rebooting my Linux box no one can connect to my Apache
> web server until I issue the following command: # "service httpd
> restart".
>
> Anyone know how I can make Apache auto start after a reboot? Thanks for
> any and all help.
chkconfig --level 345 httpd on
you might try 'ksysv' or 'tksysv' if you have them installed...
------------------------------
From: Gav <[EMAIL PROTECTED]>
Subject: Re: Unresolvesymbles for a device driver
Date: Thu, 31 May 2001 09:20:49 +0000
Digital Rider wrote:
>
> I have removed, recomplied and installed Linux on my computer. Recently,
> I got a new communication board with
> its device driver. But when I try to use it, it gives me a bunch of error
> messages and it says there're some undefined symbols. I try to use the
> same device and its driver on another Linux box with default settings, and
> this
> time the device works. So I am wondering which component I am missing for
> my optimal system. Here's the listing of the error messages I got.
>
> Using /lib/modules/2.2.14-5.0/misc/streams.o
> /lib/modules/2.2.14-5.0/misc/streams.o: unresolved symbol
> request_module_R27e4dc04
> Using /lib/modules/2.2.14-5.0/misc/streams-dlgnDriver.o
> Warning: kernel-module version mismatch
> /lib/modules/2.2.14-5.0/misc/streams-dlgnDriver.o was compiled for
> kernel version 2.2.12-20
> while this kernel is version 2.2.14-5.0
>
the driver was compiled for kernel version 2.2.12-20 while your kernel is
version 2.2.14-5.0.
What device are you trying to make work? can you just recompile it to your
new kernel then modprobe it? insmod'ing a kernel module from a different
kernel version isnt really a good idea, although can be made to work (ok..
mostly)
> Sincerely,
> Chun Yu
Regards,
Gav
------------------------------
From: Bernd Rieke <[EMAIL PROTECTED]>
Subject: CUPS filter setup
Date: Thu, 31 May 2001 12:37:25 +0200
Hi all,
I installed cups printer system on my linux box, nice tool,
SuSE 7.0. cups 1.1. But now I want to use my own filter.
In which directory do I have to install this filter-program
and where do I have to tell the cups-system to use this filter
for the specific printer. The filter confirms to the rules
given in the cups manuals e.g. it accepts the 6 or 7 parameters,
reads the data, converts the data in any way and sends it to
stdout. Important to me is that cups does nothing with the data
before and after scheduling the filter.
Thanks in advance
Greetings B. Rieke
------------------------------
From: "xhc" <[EMAIL PROTECTED]>
Subject: vgetty, mgetty and greeting message problem
Date: Thu, 31 May 2001 16:46:17 +0800
As a new hand to Linux, and after spending a couple day to set up dailin,
fax, and voice function in one modem with Red Hat 6.2, ther are still two
problem to be solve:
1. By running mgetty in inittab, the dailin and fax work perfectly. To use
voice function I replace mgetty with vgetty, but this cause dailin function
not work. When dial in system response with "line busy" why?
2. For the voice function, the greeting message is played but no sound
generate, no problem with the greeting message file, I can play it in my
local handset.
Would appreciated any linux guru can help about these two problem.
------------------------------
From: Georges Goncalves <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.hardware
Subject: Linux, CPU HLT instruction et software cooling !
Date: Thu, 31 May 2001 10:50:10 +0200
Hi people,
I have a technical question on these topics...
Hardware : AMD Duron 700 @ 950 on Abit KT7, OS Win2K SP2
AMD Duron 700 @ 900 on Abit KT7, OS GNU/Linux (Debian SID)
When the machines are doing NOTHING (Idle) the working temperature is an
average of 55�. On Win2K, I use the HMonitor tool to get temperatures.
It features a "CPU Low Power Mode" option to check (doc says it uses
the HLT command of the CPU to reduce power consumption hence the
temperature drop). It works because a couple of minutes later, the
temperature drops to 39-40�... (a reboot and the BIOS confirms
this temperature). I use LMSensors on Linux to get the temperatures and
it also works at an average temperature of 55� but the temperature
never drops.
What puzzles me is that all modern OSes (WinNT/2K, Linux and others) are
ALREADY meant to use the CPU HLT command when they're Idle, but, the
temperature remains constant (does not drop) HMonitor claims using the
HLT command and the temperature really drops.
Who's right, who's wrong ?
Anyone knows a similar tool on Linux ?
PS: I've recompiled the kernel with APM support "Make Idle CPU calls" or
some
to try the feature but the temperature variation was about a quarter of
a degree.
--
Georges 'Melkor' Goncalves <[EMAIL PROTECTED]>
------------------------------
From: [EMAIL PROTECTED] (Trevor Hemsley)
Crossposted-To: comp.os.linux.hardware
Subject: Re: SCSI problems
Date: 31 May 2001 09:44:15 GMT
On Wed, 30 May 2001 08:50:28, John English <[EMAIL PROTECTED]> wrote:
> I've just installed Red Hat 7.1 on a machine at work which has an
> Adaptec 2940 SCSI controller, to which is attached a Fujitsu M2513A
> 640M magneto-optical drive. I've also got an HP 7100 IDE CD writer,
> which I've got set up for SCSI emulation as per the X-CD-Roast docs.
> I have problems with both devices...
>
> 1) I can mount a disk in the M-O drive, and I can list the contents
> of the directory. As soon as I try to copy to or from the disk,
> I either get a segmentation fault (following a null pointer) or
> sometimes X freezes such that the mouse doesn't move and I can't
> get out.
There's a known problem with FAT formatted media on MO disks (or
anything which uses a 2K sector size) when run with a 2.4.x kernel. I
believe that one of the more recent 2.4.x-ac series kernels has a fix
for this problem included but I do not think it has made its way into
the standard tree yet. Ext2 will work OK with 2.4.x and MO disks, FAT
won't.
> 2) When I try to write a CD, it writes a few meg and then reports
> a recoverable error. It then loops endlessly reading from the
> drive (dunno why).
>
> Has anyone else got this hardware to work? Can anyone tell me what
> the problem is (or what other information I should post here about
> it)?
Since it's an IDE CD, it can't be the normal SCSI solutions of
termination, termination or termination ;-) Have you checked the
quality of the disks you are using? Does the device work with
<shudder> another operating system? Have you tried reducing the speed
at which you are trying to burn? Does it fail when run in -dummy mode
using cdrecord?
--
Trevor Hemsley, Brighton, UK.
[EMAIL PROTECTED]
------------------------------
From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Subject: Re: Help, I'm trying to find COM2
Date: Thu, 31 May 2001 12:08:47 +0200
KCmaniac <[EMAIL PROTECTED]> wrote:
>>
>> NO, I am saying that this may tell you that your system is not ready
>> for the installation,
> This is my point! Why isn't it ready? Where I am at with this system is where the
>installation program
1) Because you didn't ready it.
2) Because it is not compatible with the version of the package that you
tried to install.
> left me. So if it isn't ready then this program must be shotty. What other
>conclusion is there?
Your logic is faulty. If it isn't ready, then you didn't ready it, and
that may be either a good thing or a bad thing, depending on your
intentions. Whatever they were, dpkg correctly told you that your system
wasn't appropriately configured to receive what you tried to put into
it. That was being helpful. Now you can act on that information
and decide whether you want to change your system, or simply avail
yourself of a package directed at the system you have, rather than the
system you might have ...
> me, I am a fighter and I am willing to exasperate my options. But there comes a
>point to where I have to
I think, yes, you are. ;-).
>> If dpkg tells you that you have unmet dependencies (or met
>> anti-dependencies :-), then you will have to resolve them yourself,
>> or at least do enough that apt-get can finish the job for you, given
>> your initial impetus.
> Well, considering I apparently have got now the correct driver for this kernal, I
>should have no
> independencies, right? If I do, then it certainly wasn't caused by anything I did.
>I am a pawn here,
independencies? By anti-dependencies, I meant things installed that depend
on something that you may invalidate by installing the package (which would
have caused dpkg to complain at you). I don't think there are any of
those.
An example would be having development tools that depend on OpenGL
installed, then installing DDI development sources, which probably
conflict with OpenGL, and having to remove OpenGL-dev as a result, and
being told that doing so would render useless your third party development
tools, hence having the command to install DDI devel sources rejected.
>> Not until you have installed compilers, support tools, source code ...
>> the source code for a modern kernel occupies on the order of 100MB.
>> You would know if you had put it on your system.
> I didn't put anything on my system ... the install program did. You don't seem to
>grasp that. Obviously
No, you did. get used to it. You have to take responsibility for what you
tell your tools to do, because nobody else will. It's your
responsibility to check what was put on your system and decide if you
want more or less, and go making the adjustments.
By your account, you laid down a "basic debian system", which I think
is very minimal .. certanly less than 100MB. Possibly only 40MB.
> Anyway, I am going to try and dpkg this most recent modem driver and that is about
>all I know that I can
Well, I'd suggest simply getting the source and compiling it, normally.
After all, it's a kernel thing, so nothing to do with the distro. It's
a third party module too, so nothing really to do with anybody! It'll
be all yours to nurture and feed :-). But you plainly don't have the
expertise or the quantity of support tools instaleld yet to do that.
Please just go through fleshing out your installation with more
packages. I daresay you could multiply the quantity of installed
software by 10 without making a dent in debians archive stores. A
standard common or garden install will run to about 1GB. And you could
easily double that.
> do. If it doesn't work, then it sounds like you are suggesting that I import a new
>kernal, somehow. If
> you are willing to help me, I am willing to try and piece by piece make this system
>work, because it
I'm willing to help, but I may not be the best person to do so. It will
be far easier for you to find a friend nearby who knows what's up, and
ask them to deal with the problem together with you. But if you can
state your problem clearly, providing exact commands and error messages
(as I think you have so far), you can be helped over the wire, yes.
> sounds like that is what it is going to take or am I misunderstanding that, as well?
> So much for a
> smooth install, huh? Then again nothing worthwhile comes without a price, right?
Probably. But it really is that you should pace yourself a bit better.
Installing a lucent modem driver in a kernel and configuring the system
to use it is not what I'd select as a first-day-out task. Why not go
through familiarizing yourself with your system a bit more first?
Do you have X up and running yet?
Peter
------------------------------
From: [EMAIL PROTECTED] (M. Buchenrieder)
Subject: Re: Help, I'm trying to find COM2
Date: Thu, 31 May 2001 05:58:24 GMT
"Peter T. Breuer" <[EMAIL PROTECTED]> writes:
>KCmaniac <[EMAIL PROTECTED]> wrote:
[...]
>> WinModem on COM2 with Debian?
>COM2 does not exist in linux.
[...]
Right. Moreover, COM2 is a serial port with the specification
0x2F8, IRQ3 - which is certainly not where your Lucent WinModem
resides. In the PC world, the COM ports 1 - 4 have standard settings
(which may be altered manually). Additional serial devices must
be assigned a different COM port number. It is just mere lazyness
that many Windows or DOS programs can't handle COM ports above
COM4, which is why the Windows drivers usually try to set WinModems
to COM 2 - 4, whatever is available on the machine.
Given the fact that WinModems are a royal pain in the ***, you'd
be much better off buying a nice external serial modem instead.
Michael
--
Michael Buchenrieder * [EMAIL PROTECTED] * http://www.muc.de/~mibu
Lumber Cartel Unit #456 (TINLC) & Official Netscum
Note: If you want me to send you email, don't munge your address.
------------------------------
From: [EMAIL PROTECTED] (M. Buchenrieder)
Subject: Re: Help, I'm trying to find COM2
Date: Thu, 31 May 2001 06:09:15 GMT
Could you please adjust your line length? 72 chars would be fine.
KCmaniac <[EMAIL PROTECTED]> writes:
[...]
>After it apparently installed the kernal and "basic" system,
[...]
>There is no minicom, emacs, gnome and all the other major programs
>included with this
>"basic" system.
Of course not. That's what "basic" means. It is all the stuff you
need for a running Linux system.
[...]
>After doing some plugging and chugging, I found that indeed my RH
>system does not use
>COM2.
What a surprise.
>It assigns the modem to ttyS14.
Yup. Lucent Winmodem, ltmodem.o .
>I went back and booted into the debian system and
>it is not even doing that. It is not creating a /dev/ttyS14 or
>/dev/modem.
How should it? You're not telling it to do so.
>I am pretty
>sure ltmodem.o does not have anything to do with this because it
>isn't even loaded until
>either the end of the boot process or after it.
[...]
If you're so sure, why do you have to keep posting this thread then?
OK, once again:
- You have a Winmodem.
- This is a bad thing(TM).
- There _is_ a driver from Lucent for this winmodem, which is,
however, only available as a precompiled module (ltmodem.o) .
- Without this driver, Linux doesn't know zilch about the Lucent
winmodem, apart from the resources taken.
- This driver uses /dev/ttyS14 (which is not the driver itself, but
just the device file pointing to the driver [extremely simplified]).
Synopsis: Either get a fully functional Debian installation running
prior to any further attempts, or stay with RH.
Michael
--
Michael Buchenrieder * [EMAIL PROTECTED] * http://www.muc.de/~mibu
Lumber Cartel Unit #456 (TINLC) & Official Netscum
Note: If you want me to send you email, don't munge your address.
------------------------------
From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Subject: Re: Help, I'm trying to find COM2
Date: Thu, 31 May 2001 12:16:36 +0200
KCmaniac <[EMAIL PROTECTED]> wrote:
> after compiling using the make bzimage command, if the file comes out over 640K, is
>it usable? If not
> then why doesn't the make bzimage command tell you that the image is still too big?
>I re-compiled
It isn't too big. A zImage file with over about 500KB of code would be
too big. A bzImage file is not too big. The decompression technique for
bzImage is "a bit at a time", so that the compressed image does
nothave to all fit into lower memory at once. It is loaded into higher
memory and brought down bit by bit, expanded bit by bit, and put in its
final location bit by bit.
> 2.2.14 on my RH system recently because I changed a couple of configuration items.
>The bzimage
> balloned to over 640K. I moved it to /boot and did everything else necessary and
>re-booted. The "new"
640K is not too big for a bzImage. I haev (modularized!) kernels about
800K in size.
> Another thing, the reason I changed a couple of configuration items to 2.2.14 in the
>first place was
> because I was not being able to get IP_Masquerading to work. After all the reading
>I did I concluded I
I've never needed to masquerade. Forwarding is sometimes useful ..
> needed to try this. Well, afterwards I still could not ping an IP address outside
>my LAN from a host
> PC. I could ping from the gateway but not from a host so IP_Masquerading must not
>be working, right?
If your gateway is your router, then it should be handling the
forwarding and stuff, not you. If you are your own gateway, you don't
need to be forwarding or masquerading (for yourself).
> I did everything in accordance with the documentation.
There are too many possible situations that you may be describing for
me to be able to know with security either what you are describing, or
which documentation is appropiate. Ask for someone else who is in your
situation to help you. I guess you are talking about a ppp connection
to the internet, where you want to be the gateway for an intranet?
Peter
------------------------------
From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Subject: Re: Help, I'm trying to find COM2
Date: Thu, 31 May 2001 12:36:25 +0200
KCmaniac <[EMAIL PROTECTED]> wrote:
>> I don't need the information. The fact is that you haven't installed a
>> driver for the losemodem. It could hardly be otherwise, since debian
>> is a gnu-centric distro, and winmodem source codes are not part of the
>> linux kernel source code and are not GPL.
> So what you are saying is that by using dpkg on this modem driver I got from
>linmodem.org should
> enable the kernal to establish the modem so that I can dial out considering there
>are no
Yes, the kernel driver which you will install on your system (and which
you may subsequently have to load into your kernel - I don't know how
the packager has arranged things) provides a fake serial interface through
a special device node - /dev/ttyS14, with major 62 and mimor 78 ? I
imagine the package will set that up for you. You will later want to
talk to that device node with any applications that want to use the
lucent modem.
> independencies that keep it from working of which, I remind you, I have nothing to
>do with. You also
?? You are entirely responsible for your system. If you buy a new steering
wheel for your car, then you are responsible for seeing that the car
matches the steering wheel, or else for seeing that you buy a steering
wheel that matches your car. The situation is the same.
> must be saying that the driver IS necessary for the kernal to make this
>establishment. Why, then, in
That is so. You need a driver for the lucent winmodem.
> my RH system does that kernal assign the modem to ttyS14 without the driver because
>I install the
It does not. And "assign modem to" makes no sense in itself. If you mean,
"links /dev/modem to /dev/ttyS14", then yes, it may well do that. It
sounds like the kind of thing RH may do, without telling you! That
would nicely kibosh a previously working setup :-).
RH probably packages the ltmodem driver with their installed kernels.
It strikes me as the kind of thing they would do.
> driver using insmod in /etc/rc.d/rc.local which is a script that runs last in the
>boot process ...
That's fine. You would do the same here.
> long after the kernal is supposed to set up the modem. Do you see what I am saying?
> If I am totally
The kernel does not "set up" the modem.
> way off base then I can understand why you would be getting bored with this
>conversation. But am I?
You are off base, possibly because of a misconception that the kernel
needs or ought to set up the modem at boot. This is not so. The driver is
responsible for setting up the modem, and it sets it up (i.e. enables it)
whenever you insert the driver in the kernel, and it unsets it up
whenever you remove the driver from the kernel.
Those actions would be modprobe ltmodem and modprobe -r ltmodem,
respectively.
The modem is accessible (via /dev/ttyS14) whenever the driver is loaded
in the kernel.
In addition, RH has some sort of hardware detecton routine (probably a
"cat /proc/pci", followed by a lookup of the device numbers in a table
that translates them to names of modules to load) that probably can load
the driver automatically for you. I am surprised that you have to load
it by hand.
In debian, if you want to force the driver to be loaded at boot, it
probably suffices to add the word "ltmodem" on a line by itself in
/et/modules.
I'd myself probably configure it to be loaded on demand when you
attempt to access /dev/ttyS14, which requires tinkering with
/etc/modutils/aliases (and then running /sbin/update-modules).
In adition, you might want to add a bit of scripting somewhere that
does a linkage of /dev/modem to /dev/ttyS14 when the driver is loaded.
Again, I'd probably opt for a pre-install entry in the modutils
stuff, and you'd probably opt for a line or two in rc.local.
Peter
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: You may now safely reboot!
Date: 31 May 2001 11:01:21 GMT
Perry <[EMAIL PROTECTED]> wrote:
> Running Anaconda - Please wait
> exec : input/output error
> install excited abnormally
Sounds like your CD is damaged... try another CD or
a different distribution.
Davide
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list by posting to comp.os.linux.setup.
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Setup Digest
******************************
