Linux-Hardware Digest #877, Volume #14 Thu, 7 Jun 01 15:13:10 EDT
Contents:
Re: HP Pavilion and RH 7.0 - sound card / modem problem (SwifT)
i815 on 2.2.x kernel series ("Michal \"Mikey\" Szwaczko")
Re: Linux on Integrated Graphics Card Motherboard (J Hayward)
Re: MODEM PCTel HSP56 AMR on PCCHIPS M810 (Robert Heiling)
Re: MODEM PCTel HSP56 AMR on PCCHIPS M810 ("Peter T. Breuer")
laptop compatibility (dream)
Help New Server (Bob)
Modem Prob ("kaidemuyo!")
Re: laptop compatibility ("Tauno Voipio")
HP Colorado T4000s (Phillip Conrad)
Re: MODEM PCTel HSP56 AMR on PCCHIPS M810 (Robert Heiling)
Re: Modem Prob (Robert Heiling)
Re: Xawtv - what did I screw up? ("kyi")
Re: RH7.1 and SoundBlaster Live! ("kyi")
Re: MODEM PCTel HSP56 AMR on PCCHIPS M810 (Robert Heiling)
Re: MODEM PCTel HSP56 AMR on PCCHIPS M810 ("Peter T. Breuer")
----------------------------------------------------------------------------
Crossposted-To: alt.os.linux,be.comp.os.linux,comp.os.linux.misc
From: SwifT <[EMAIL PROTECTED]>
Subject: Re: HP Pavilion and RH 7.0 - sound card / modem problem
Date: Thu, 07 Jun 2001 15:24:33 GMT
On Thu, 7 Jun 2001, marek wrote:
> For the modem:
> (yes, I realize it is WinModem, but there are special drivers for it)
> I tried to install the driver by Imran Ghory from
> http://www.cyberspace.org/~imran/hsflinux.htm, but ins_all script gives
> me the error "cannot find apropriate .inf file", although the file is in
> the same directory.
Maybe you ought to set the PATH-environment so it also contains
the directory in which the file is located?
It can also be that the ins_all-script requires an option like
"--inf=./yourfile.inf". Since I don't know what ins_all does/can,
maybe you can post the output of "ins_all --help"?
> For the sound-card:
> Tried to use sb module - no luck. I care much more about the modem, but
> it could be nice to have sound card working, too.
Try sndconfig. It's a tool which will help you find a working
module.
--
SwifT - Key-ID CDBA2FDB
LUG: http://www.lugwv.be - http://www.keyserver.net
------------------------------
From: "Michal \"Mikey\" Szwaczko" <[EMAIL PROTECTED]>
Subject: i815 on 2.2.x kernel series
Date: Thu, 7 Jun 2001 17:58:20 +0200
Is it possible to fully exploit posibilities of the intel's 815 chipset in
the 2.2.x kernels ?
Any motherboards suggested for i815+Linux marriage ?
TIA.
Michal "Mikey" Szwaczko
------------------------------
From: J Hayward <[EMAIL PROTECTED]>
Subject: Re: Linux on Integrated Graphics Card Motherboard
Date: Thu, 7 Jun 2001 09:14:13 -0700
Hi,
BellSouth News wrote:
<snip...>
>
>
> Told by Gateway that graphics card info is:
> VT 8501 [492VGA] AGP 2D/3D Graphics Accelerator.
>
Try running Xconfigurator like this:
Xconfigurator --preferxf3
Post a copy of you /var/log/XFree86.0.log
Regards,
Jim H
------------------------------
From: Robert Heiling <[EMAIL PROTECTED]>
Subject: Re: MODEM PCTel HSP56 AMR on PCCHIPS M810
Date: Thu, 07 Jun 2001 09:20:28 -0700
Michael wrote:
> According to http://www.idir.net/~gromitkc/winmodem.html there are only
> binary PCtel modem drivers for Linux.
This is the post that I was looking for to see if someone else had already
solved my problem<g>. After spending a lot of time trying to get my modem that
works fine under Win98 to work in Linux, I was suspecting that it was a
WinModem and this confirms that. My system has an HSP56MR modem (WinModem) on
an M805LR MB with Athlon cpu and is running RedHat 7.1 with the 2.4.2-2 kernel.
I looked at that link and downloaded the PCCHIPS file that is available there
on http://linmodems.org/ named Pctel.zip that supposely contains a driver.
That zip file contains files: control.a, dsp.a, hal.a, ptserial.a, Makefile,
Pctel.o, and ptmodule.c. I don't know what ".a" files are and there is no
Readme or instructions of any type and I'm totally confused as to how to use
those files. Any help out there?
Bob
> ----------------------------------
> "Kris Stark" <[EMAIL PROTECTED]> wrote in message
> news:9fjrc7$2qpe$[EMAIL PROTECTED]...
> > Hildebrando Rosa Jr. wrote:
> >
> > > A don't get this device work on mdk with kernel 2.4.3
> > >
> > > The modules available claim for unresolved symbols
> > >
> > > Someone gets this device working on kernel 2.4.x?
> > >
> > > Thanks for any help
> > >
> > > [ ]'s
> >
> > Are the sources available? I can't remember for this particular modem
> > driver, but if they are - download and recompile the sources - which will
> > mean recompiling the kernel. That ought to take care of the problem. I
> > take it that you got the driver from an older version of linux?
> >
> > Kris
> > --
> > Kris Stark -- Remove NO-SPAM from address to reply...
------------------------------
From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Subject: Re: MODEM PCTel HSP56 AMR on PCCHIPS M810
Date: Thu, 7 Jun 2001 18:50:08 +0200
Robert Heiling <[EMAIL PROTECTED]> wrote:
> Michael wrote:
> on http://linmodems.org/ named Pctel.zip that supposely contains a driver.
> That zip file contains files: control.a, dsp.a, hal.a, ptserial.a, Makefile,
> Pctel.o, and ptmodule.c. I don't know what ".a" files are and there is no
> Readme or instructions of any type and I'm totally confused as to how to use
> those files. Any help out there?
Type "make" (that's what the makefile is for). Look at the other files.
Peter
------------------------------
From: dream <[EMAIL PROTECTED]>
Subject: laptop compatibility
Date: Thu, 7 Jun 2001 13:06:53 -0400
Hello. I am planning on buying a laptop and installing RH linux on it, but
I want to be sure that the hardware will be linux compatible. I am talking
about latest models, with 700 MHz processors. Are all/most of the latest
models compatible? Right now I have two possibilites: HP Omnibook XE3 and
IBM Thinkpad A20M. Please help if you can. Email me please at
[EMAIL PROTECTED] Thank you.
------------------------------
From: [EMAIL PROTECTED] (Bob)
Subject: Help New Server
Date: 7 Jun 2001 10:58:12 -0700
I am thinking of making a computer I have into a server.
It is
Asus a7v KT133 Motherboard
AMD 1 gig.
SB 16 sound
Gforce Mx 32 meg video
256 133 mem.
I need help on where to get all the drivers and stuff to load Red Hat 7.1
I have computer knowledge of PC and Windows but this is my
First attempt at Linux.
Any help is appreciated and Thanks in advance.
Bob
------------------------------
From: "kaidemuyo!" <[EMAIL PROTECTED]>
Subject: Modem Prob
Date: Fri, 8 Jun 2001 01:59:06 +0800
I've got a Conexant Doft56k Data, FAx Speaker PCI Modem (using the driver
cd) Installed on Win ME and Linux (Mandrake, ver. 8) Detects it as a
Rockwell International 56k PCI modem. However, when I try to dial up, it
always says that the modem is busy. What do I do?
------------------------------
From: "Tauno Voipio" <[EMAIL PROTECTED]>
Subject: Re: laptop compatibility
Date: Thu, 07 Jun 2001 18:03:30 GMT
"dream" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> Hello. I am planning on buying a laptop and installing RH linux on it, but
> I want to be sure that the hardware will be linux compatible. I am talking
> about latest models, with 700 MHz processors. Are all/most of the latest
> models compatible? Right now I have two possibilites: HP Omnibook XE3 and
> IBM Thinkpad A20M. Please help if you can. Email me please at
> [EMAIL PROTECTED] Thank you.
>
I'm running Red Hat 6.2 on an IBM A21p. Everything else works but the
Winmodem on the Ethernet/modem combo card.
Tauno Voipio
tauno voipio @ iki fi
------------------------------
From: Phillip Conrad <[EMAIL PROTECTED]>
Subject: HP Colorado T4000s
Date: Thu, 07 Jun 2001 18:04:51 GMT
I am trying to use my HP Colorado T4000s under RedHat 7.1, using an
Adaptec 1520B,
without success. It worked fine under Windows, so I'm reasonably
confident of the
hardware, etc.
The drive is seen, and /dev/st0 is in fact recognized as a device.
However, when I
try to do "mt -f /dev/st0 status", the process hangs. It does not
respond to kill -9; the
only way to unhang the process is to reboot.
"mt -f /dev/st0 rewind" produces I/O Error messages.
Here's the output of more /proc/scsi/scsi
# more /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 04 Lun: 00
Vendor: HP Model: T4000s Rev: 1.07
Type: Sequential-Access ANSI SCSI revision: 02
Does anyone have any suggestions?
If the solution is to "throw out this ancient piece of
junk" can anyone report success under Linux with
some specific combination of SCSI card/tape drive
(or for that matter, a non-SCSI tape drive, if it works)
that can in the range of >= 4-8GB... preferably for
under $900?
Thanks,
Phill Conrad
PS: The firmware on the tape drive is at Rev 1.07. There *are* more
recent versions of the firmware, however I no longer have a
dos/windows partition on my box, and am loathe to reinstall one...
I think I'd have to have one to run the firmware installer...
unless there is someway I can stick dos, scsi drivers, and the
firmware installer all on a floppy?
------------------------------
From: Robert Heiling <[EMAIL PROTECTED]>
Subject: Re: MODEM PCTel HSP56 AMR on PCCHIPS M810
Date: Thu, 07 Jun 2001 11:15:35 -0700
"Peter T. Breuer" wrote:
> Robert Heiling <[EMAIL PROTECTED]> wrote:
> > Michael wrote:
> > on http://linmodems.org/ named Pctel.zip that supposely contains a driver.
> > That zip file contains files: control.a, dsp.a, hal.a, ptserial.a, Makefile,
> > Pctel.o, and ptmodule.c. I don't know what ".a" files are and there is no
> > Readme or instructions of any type and I'm totally confused as to how to use
> > those files. Any help out there?
>
> Type "make" (that's what the makefile is for). Look at the other files.
>
> Peter
Thanks for your reply!
I created a folder/directory "Hsp56" on a FAT16 partition that I use to share
files between Win98 & Linux. Pctel.zip was moved to Hsp56 and, strangely enough,
when I then had Winzip extract the files into Hsp56 it created a directory
structure that had not been apparent in looking at it with Winzip as follows:
/Hsp56/lib/ containing pctel.o and all the *.a files which I had previously
looked at and they contain binary gibberish as does pctel.o as expected.
/Hsp56/Src/Module/ containing Makefile & ptmodule.c
ptmodule.c is only:
===================================
/*
* For the definition of __module_kernel_version[] so that
* the modem driver can be compatible with various Linux kernel
* versions.
*
* This file is to be linked with the rest of the libraries in
* the distribution package.
*/
#include <linux/version.h>
const char __module_kernel_version[] __attribute__((section(".modinfo"))) =
"kernel_version=" UTS_RELEASE;
#ifdef MODVERSIONS
const char __module_using_checksums[] __attribute__((section(".modinfo"))) =
"using_checksums=1";
#endif
=====================================
and I wonder where these files should be and where I should be cd'ed to when I
make?
Makefile contents:
======================================
#
# Makefile for the PCtel module
#
# Note! The CFLAGS definition is now inherited from the
# parent makefile.
#
HPATH = ../../include
FINDHPATH = $(HPATH)/asm $(HPATH)/linux $(HPATH)/scsi $(HPATH)/net
HOSTCC =gcc -I$(HPATH)
HOSTCFLAGS =-O -fomit-frame-pointer
CROSS_COMPILE =
COL_DEBUG_FLAGS =
AS =$(CROSS_COMPILE)as
LD =$(CROSS_COMPILE)ld
CC =$(CROSS_COMPILE)gcc -D__KERNEL__ -DMODULE -Wall $(HOSTCFLAGS) -I$(HPATH)
${COL_DEBUG_FLAGS}
CPP =$(CC) -E
AR =$(CROSS_COMPILE)ar
NM =$(CROSS_COMPILE)nm
STRIP =$(CROSS_COMPILE)strip
MAKE =make
EXTRA_LDFLAGS :=
# object files directory
O_TARGET := ../../lib/pctel.o
# object files
O_OBJS := \
ptmodule.o \
OX_OBJS := \
../../lib/control.a \
../../lib/hal.a \
../../lib/dsp.a \
../../lib/ptserial.a
all_targets: $(O_TARGET) $(L_TARGET)
%.s: %.c
$(CC) $(CFLAGS) $(EXTRA_CFLAGS) -S $< -o $@
%.o: %.c
$(CC) $(CFLAGS) $(EXTRA_CFLAGS) -c -o $@ $<
%.o: %.s
$(AS) $(ASFLAGS) $(EXTRA_CFLAGS) -o $@ $<
ifdef O_TARGET
ALL_O = $(O_OBJS) $(OX_OBJS)
$(O_TARGET): $(ALL_O) Makefile
rm -f $@
$(LD) -r $(EXTRA_LDFLAGS) -o $@ $(ALL_O)
endif
clean:
rm -f *.o
ifdef L_TARGET
rm -f $(L_TARGET)
endif
ifdef O_TARGET
rm -f $(O_TARGET)
endif
=================================================
I haven't done anything with this in Linux yet and just made the files accessible
in preparation so far.
Bob
------------------------------
From: Robert Heiling <[EMAIL PROTECTED]>
Subject: Re: Modem Prob
Date: Thu, 07 Jun 2001 11:23:24 -0700
"kaidemuyo!" wrote:
> I've got a Conexant Doft56k Data, FAx Speaker PCI Modem (using the driver
> cd) Installed on Win ME and Linux (Mandrake, ver. 8) Detects it as a
> Rockwell International 56k PCI modem. However, when I try to dial up, it
> always says that the modem is busy. What do I do?
That's the same symptom I was having (busy). I believe you have a WinModem as
I just discovered that I have and it requires a special software driver, if
available. See:
http://www.idir.net/~gromitkc/winmodem.html and
http://linmodems.org/
I'm currently trying to work this out on the thread: Re: MODEM PCTel HSP56
AMR on PCCHIPS M810
HTH
Bob
------------------------------
From: "kyi" <[EMAIL PROTECTED]>
Subject: Re: Xawtv - what did I screw up?
Date: Thu, 7 Jun 2001 11:44:40 -0700
=====BEGIN PGP SIGNED MESSAGE=====
Hash: SHA1
ok then do a 'rm -rf /dev/video' w/out quotes. Then download the
xawtv source, http://bytesex.org/xawtv/xawtv_3.50.tar.gz , you don't
have to compile it just run the MAKEDEV.v4l. That will create the
proper device files. After you do that re-run v4l-conf, it should
work now, hopefully ;-)
- -Jayson
http://linux.microbsys.com
Corey Bodzin <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> Ran v4l-conf; still have a black screen. Here is the output
> (notice that it complains about /dev/video):
>
> [root@penguin /root]# v4l-conf
> v4l-conf: using X11 display :0
> dga: version 2.0
> mode: 1280x1024, depth=16, bpp=16, bpl=2560, base=0xee82e000
> can't open /dev/video: Is a directory
> [root@penguin /root]# xawtv
> This is xawtv-3.49, running on Linux/i686 (2.4.4)
> Xv: video4linux: input video, ports 46-46
> Xv: 3dfx Accelerated Video Engine: input image, ports 47-47
> Xv: using port 46 for video
> image format list for port 47
> 0x32315659 (YV12) planar
> 0x30323449 (I420) planar
> Xv: no usable image format found (port 47)
> wmhooks: gnome
> Warning: Cannot convert string "string" to type AsciiType
> [root@penguin /root]# ls -al /dev/video
> total 88
> drwxr-xr-x 2 root root 4096 May 17 01:30 .
> drwxr-xr-x 15 root root 81920 Jun 6 17:37 ..
> crw------- 1 cbodzin root 10, 204 Mar 23 21:38 em8300
> crw------- 1 cbodzin root 10, 206 Mar 23 21:38 em8300_ma
> crw------- 1 cbodzin root 10, 205 Mar 23 21:38 em8300_mv
> crw------- 1 cbodzin root 10, 207 Mar 23 21:38 em8300_sp
> [root@penguin /root]#
>
> > Have you tryed running, v4l-conf, after changeing video modes? If
> > not that could be your problem. Try it and see, if thats not it,
> > v4l-conf will not mess anything up.
> >
> > - -Jayson
> > http://linux.microbsys.com
> >
> > Corey Bodzin <[EMAIL PROTECTED]> wrote in message
> > news:[EMAIL PROTECTED]...
> > > I have been using xawtv with my Hauppage WinTV card under RH
> > > 7.1 for quite some time now with great success. The other day
> > > I used XConfigurator to switch from 1280x1024x24 to
> > > 1280x1024x16; when I switched back I found that xawtv no longer
> > > worked correctly.
> > >
> > > - In 16bpp color depth it plays all audio but just shows black
> > > for video.
> > > - In 24bpp color depth it does both audio and video, but the
> > > video is outside (above and to the left) of the xawtv window,
> > > and it tends to mess up my display.
> > >
> > > I know my hardware is OK because kwintv runs just fine in
> > > either mode.
> > > I have tried launching xawtv with various switches (especially
> > > -b 16) but have had no luck.
> > >
> > > Anybody have any guesses as to what might be going on?
> > >
> > > Vitals:
> > > RH 7.1, 2.4.4 kernel
> > > Voodoo3 16MB video card
> > > Hauppage WinTV tuner
> > xawtv 3.49, bttv 0.8.5
> >
> > -----BEGIN PGP SIGNATURE-----
> > Version: PGPfreeware 7.0.3 for non-commercial use
> > <http://www.pgp.com>
> >
> > iQA/AwUBOx6KBs/HUx/4DiNjEQIyTQCdFvZIJsMWSwX6j9zHCBG+VzW4ecYAnR03
> > hib8DPVrM0cqVa7FKhEsu9iD
> > =drdx
- -----END PGP SIGNATURE-----
=====BEGIN PGP SIGNATURE=====
Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com>
iQA/AwUBOx/Lk8/HUx/4DiNjEQKebQCg8EI9kY5b57/JqJSoyjqcNHV5J5UAoMDj
v5rGio0W2KxUc+VJW5ZjR1AJ
=fi1g
=====END PGP SIGNATURE=====
------------------------------
From: "kyi" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Re: RH7.1 and SoundBlaster Live!
Date: Thu, 7 Jun 2001 11:50:11 -0700
=====BEGIN PGP SIGNED MESSAGE=====
Hash: SHA1
Well damn it that SUCKS!!! You can still get a regular pci SBLive!
instead and that will work. Other then that..... your are SOL, sorry.
I guess you can blame gateway for not releasing the specs for that
interface, we tried creative and they deny that the thing even
exists.
- -Jayson
http://linux.microbsys.com
Randy Pratt <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> Uh-oh. Indeed this is the Gateway OEM SBLive! with digital output
> and Boston Acoustics speakers. I looked through the archives of
> the
> email list at http://opensource.creative.com and saw what you
> referred to. There doesn't seem to be any fix to the emu10k driver
> as yet to get this up and running. :o<
>
> Randy
>
> kyi wrote:
> >
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > I noticed from your hardware discription that it is a gateway
> > computer. Is the SBLive! the digital one that comes with the
> > gateway? or a standalone pci card? The reason I ask is 'cause if
> > it's the SBLive! digital that comes onboard with the gateway it
> > probably won't work ;-( If it's not, and it's a SBLive! that you
> > bought seperatly then it will work. The reason is there is
> > something flaky about the gateway card, I read this on the
> > opensource.creative.developers mailing list. I strongly suggest
> > that you goto
> > http://opensource.creative.com and follow the links on
> > subscribing to the email list for this card. I personally have
> > the SBLive!, bought from compusa, and it is a very very good
> > card, so all this won't be a wast of time.
> >
> > - -Jayson Garrell
> > http://linux.microbsys.com
> >
>
> --
> Randy Pratt - Agere Systems
> Read Channel Design - Storage Products Organization
> mailto:[EMAIL PROTECTED] - http://megpsrv.agere.com/~rrp2/
>
> There are 3 kinds of people in this world:
those who can count, and those who can't
=====BEGIN PGP SIGNATURE=====
Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com>
iQA/AwUBOx/M3s/HUx/4DiNjEQKLmgCg+Hwtre/Z6Po1BaUfPZGSFhXva3MAoIJZ
V33wv87vtT1mPlNPcA2Rt9bv
=7hIB
=====END PGP SIGNATURE=====
------------------------------
From: Robert Heiling <[EMAIL PROTECTED]>
Subject: Re: MODEM PCTel HSP56 AMR on PCCHIPS M810
Date: Thu, 07 Jun 2001 11:53:52 -0700
Robert Heiling wrote:
> "Peter T. Breuer" wrote:
>
> > Robert Heiling <[EMAIL PROTECTED]> wrote:
> > > Michael wrote:
> > > on http://linmodems.org/ named Pctel.zip that supposely contains a driver.
> > > That zip file contains files: control.a, dsp.a, hal.a, ptserial.a, Makefile,
> > > Pctel.o, and ptmodule.c. I don't know what ".a" files are and there is no
> > > Readme or instructions of any type and I'm totally confused as to how to use
> > > those files. Any help out there?
> >
> > Type "make" (that's what the makefile is for). Look at the other files.
> >
> > Peter
>
> Thanks for your reply!
>
> I created a folder/directory "Hsp56" on a FAT16 partition that I use to share
> files between Win98 & Linux. Pctel.zip was moved to Hsp56 and, strangely enough,
> when I then had Winzip extract the files into Hsp56 it created a directory
> structure that had not been apparent in looking at it with Winzip as follows:
> /Hsp56/lib/ containing pctel.o and all the *.a files which I had previously
> looked at and they contain binary gibberish as does pctel.o as expected.
> /Hsp56/Src/Module/ containing Makefile & ptmodule.c
>
> ptmodule.c is only:
> -----------------------------------
> /*
> * For the definition of __module_kernel_version[] so that
> <SNIP>
> -------------------------------------
> and I wonder where these files should be and where I should be cd'ed to when I
> make?
>
> Makefile contents:
> --------------------------------------
> #
> # Makefile for the PCtel module
> <SNIP>
> -------------------------------------------------
>
> I haven't done anything with this in Linux yet and just made the files accessible
> in preparation so far.
>
> Bob
Ooops! I took another hard look at that C code and realized there wasn't a problem
with the directories. I booted Linux and cd'ed to /hpr56/module/src and did a make.
All went well and I now have a ptmodule.o My new question is what do I do next? Do I
need to build a new kernel now in order to use this module?
Bob
------------------------------
From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Subject: Re: MODEM PCTel HSP56 AMR on PCCHIPS M810
Date: Thu, 7 Jun 2001 21:00:07 +0200
Robert Heiling <[EMAIL PROTECTED]> wrote:
> I created a folder/directory "Hsp56" on a FAT16 partition that I use to share
Don't.
> files between Win98 & Linux. Pctel.zip was moved to Hsp56 and, strangely enough,
Don't.
> when I then had Winzip extract the files into Hsp56 it created a directory
> structure that had not been apparent in looking at it with Winzip as follows:
Look ... please take the Pctel.zip file to linux, in a linux directory,
and unzip it. That's all. Do not use winzip! Do not use windows. Do not
use a vfat directory. You cannot compile sensibly in such a thing!
> /Hsp56/lib/ containing pctel.o and all the *.a files which I had previously
> looked at and they contain binary gibberish as does pctel.o as expected.
Of course.
> /Hsp56/Src/Module/ containing Makefile & ptmodule.c
That's fine. Type "make".
> ptmodule.c is only:
> -----------------------------------
> /*
> * For the definition of __module_kernel_version[] so that
> * the modem driver can be compatible with various Linux kernel
> * versions.
Ya ya ... I was just wondering if they put some compile instructions at
the bottom, other than the obvious "make".
> and I wonder where these files should be and where I should be cd'ed to when I
> make?
?? You have to be where the makefile is. "Read the makefile"'s what make does.
> Makefile contents:
> --------------------------------------
> #
> # Makefile for the PCtel module
> #
> # Note! The CFLAGS definition is now inherited from the
> # parent makefile.
Oh, that looks like they are talking about the kernel Makefile. So you
need kernel sources installed (the ones corresponding to your kernel)
and configured (the way your kernel was configured).
> I haven't done anything with this in Linux yet and just made the files accessible
> in preparation so far.
Please don't think so hard! All you have to is unzip the .zip file in
linux, go to where the makefile is, and type "make". If you need any
further instructions, they'll be on the web page.
Peter
------------------------------
** 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.hardware.
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-Hardware Digest
******************************
