Linux-Hardware Digest #367, Volume #13 Sun, 6 Aug 00 22:13:06 EDT
Contents:
For Linux only- 20.4GB HD, bios limitation, EZ-drive or any other?
([EMAIL PROTECTED])
Re: For Linux only- 20.4GB HD, bios limitation, EZ-drive or any other? (Byron A Jeff)
Re: Installing an NIC (Dances With Crows)
How to apply the ide patch (James Richard Tyrer)
Re: Installing an NIC ("Blayne Wessels")
Re: Rockwell 56K ACF II Modem ("Phillip Kimble")
Re: Installing an NIC (Dances With Crows)
Re: Cannot install ISA Network Card (sideband)
Re: What about Rockwell HCF 56k Data fax speakerphone PCI modem (sideband)
Re: Installing an NIC (sideband)
----------------------------------------------------------------------------
Date: Sun, 06 Aug 2000 19:15:41 +0200
From: [EMAIL PROTECTED]
Subject: For Linux only- 20.4GB HD, bios limitation, EZ-drive or any other?
I want to use the whole disk (20.4 gb) for Linux only. One of the Howto
says, linux can bypass the bios. How? How can I make linux to see 20.4
gb?
Thanks
James Richard Tyrer wrote:
>
> [EMAIL PROTECTED] wrote:
>
> > Hi,
> >
> > I have a 4 GB hda for windoze, 4 GB hdb for Debian and just installed a
> > 20.4 GB maxtor HD and also running partition commender's boot manager. I
> > would like to use this 20.4 gb hdd for debian only.
> >
> > My bios does not support bigger than 8.4 GB. I got the latest bios
> > upgrade from gateway2000, but that didn't do anything. I tried setting
> > the hard disk settings in the bios manually (instead of automatic
> > configuration) with 39683 cylinder (manufacturer specs says this is the
> > max cylinder), did not help. I included the 'append = "hdd =
> > 39683,16,63"' in lilo.conf (as suggested by linuxdoc-howto web site),
> > still can not get more than 8.4 gb. This howto says that linux can
> > bypass the bios settings, but it didn't or I missed something.
> >
> > Is there any other way to get the 20.4 gb from this harddrive?
> > Should I install EZ-Drive software that comes from maxtor? Will this
> > screw up the things?
> >
> > Thanks.
>
> If you are using the whole disk for Linux, you don't have to use
> EZ-Drive. The BIOS only has to be able to find the /boot directory, not
> the whole disk. Make a small (10 Mbyte) partition for /boot at the
> beginning of the disk and all will be fine.
>
> JRT
------------------------------
From: [EMAIL PROTECTED] (Byron A Jeff)
Subject: Re: For Linux only- 20.4GB HD, bios limitation, EZ-drive or any other?
Date: 6 Aug 2000 19:27:01 -0400
In article <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]> wrote:
-I want to use the whole disk (20.4 gb) for Linux only. One of the Howto
-says, linux can bypass the bios. How? How can I make linux to see 20.4
-gb?
You don't need to do anything except make sure that the kernel boots within
the 1st 1024 cyliders. And that's not even necessary if you're running
LILO 21.4 or later.
The machine I'm on has only a 20 GB disk. The root partition is 2 GB and
occupies 4100 cylinders. LILO 21.5 boots it just fine.
I repeat Linux doesn't require anything special to use 20 GB or larger
disks. This issue is confined only to booting, and LILO 21.5 will boot
large disks just fine as long as the BIOS supports it.
The solution for old BIOSes is to simply make a small boot partition and
stick the kernel and LILO's required files in that small partition for booting.
Thge kernel will still have no problem using the entire disk.
BAJ
------------------------------
From: [EMAIL PROTECTED] (Dances With Crows)
Subject: Re: Installing an NIC
Date: 7 Aug 2000 00:24:20 GMT
Reply-To: [EMAIL PROTECTED]
On Sun, 06 Aug 2000 22:30:34 GMT, Blayne Wessels wrote:
>I have Debian Linux installed on one of my machines and want to get it on my
>network. I put in a Linksys 10/100Mbps network card (LNE100TX) and it
>didn't recognize it. I later found that I would need the "Tulip Driver." I
>also found, under "\Linux" on the driver disks for the NIC, a file called
>tulip.c. So I guess that what I'm really asking is: do I need to compile
>the kernel with the tulip.c to use the NIC and if so, how?
The tulip.c file is source code for a kernel module. COmpile the
tulip.c code as per the instructions in the README that should be in the
same directory as tulip.c, then move the tulip.o module to
/lib/modules/$KERNELVERSION/net/ and run "depmod -a". Then you should
be able to do "insmod tulip" and be able to use the NIC after you've
given it an IP address with "ifconfig". After you've verified that the
NIC works and such, edit /etc/conf.modules and insert the line
alias eth0 tulip
somewhere, commenting out any other lines that refer to eth0. Then the
module loader will automagically load tulip.o whenever eth0 is accessed.
HTH,
--
Matt G|There is no Darkness in Eternity/But only Light too dim for us to see
Brainbench MVP for Linux Admin / Tyranny is always better organized
http://www.brainbench.com / than freedom.
=============================/ ==Charles Peguy
------------------------------
From: James Richard Tyrer <[EMAIL PROTECTED]>
Subject: How to apply the ide patch
Date: Mon, 07 Aug 2000 00:29:53 GMT
This is a multi-part message in MIME format.
==============FCE788721B81F0B678EA3F18
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
kimerud wrote:
> After reading your postin comp.os.linux.hardware refering to Ultra66
patch,
> I would like your assistance if time is available. I have only
attempted to
> patch twice and both times was unsuccessful and caused me to install
> everything just to get the system running again! Not good. If you
could, I
> would like detailed instructions or a reference to patching the kernel
to
> preclude from such disaters.
>
I have attached a slightly edited excerpt from the README which comes
with the
Kernel source.. This is not quite sufficient to do the job, but it is a
place
to start.
I presume that you have copied the Kernel source and the patch to the
/usr/src
directory and that you have unpacked the Kernel from either a "tar.gz"
or
"tar.bz2" file. When you unpacked the Kernel, the directory: "linux"
will
have been created in the /uar/src directory.
To patch you need to be in the /usr/src directory and execute the
command:
patch -p0 <ide.*.patch
However, if you do this now, the patching will fail. You need to open
the
patch in an editor or with "less" and look at the first few lines. in
this
patch they are:
diff -urN linux-2.2.16-pristine/CREDITS linux-2.2.16.c/CREDITS
--- linux-2.2.16-pristine/CREDITS Wed Jun 7 14:26:42 2000
+++ linux-2.2.16.c/CREDITS Tue Jul 11 00:44:14 2000
note that the third line (which starts with "+++" refers to
"linux-2.2.16.c".
Therefore, for the patch to work you either need to add a symbolic link
("linux-2.2.16.c") to the ("linux") directory. Then execute that patch
instruction as stated above.
Then you should be able to build the Kernel in the usual manner starting
with:
cd linux
then
make config
or
make menuconfig
then
make dep clean bzImage modules
etc.
JRT
==============FCE788721B81F0B678EA3F18
Content-Type: text/x-vcard; charset=us-ascii;
name="tyrerj.vcf"
Content-Transfer-Encoding: 7bit
Content-Description: Card for James Richard Tyrer
Content-Disposition: attachment;
filename="tyrerj.vcf"
begin:vcard
n:Tyrer;James
tel;fax:call first
tel;home:(520) 648-3720
x-mozilla-html:TRUE
org:JRT Engineering
adr:;;1468 North Rio Sonora;Green Valley;Arizona;85614-4007;USA
version:2.1
email;internet:[EMAIL PROTECTED]
x-mozilla-cpt:;2
fn:James Tyrer
end:vcard
==============FCE788721B81F0B678EA3F18==
------------------------------
From: "Blayne Wessels" <[EMAIL PROTECTED]>
Subject: Re: Installing an NIC
Date: Mon, 07 Aug 2000 00:42:14 GMT
Actually, there was no readme: just tulip.c and the GNU General Public
License. Although, being a programmer, I tried using djgpp to compile and
received the following errors:
tulip.c:75: linux/config.h: No such file or directory (ENOENT)
tulip.c:76: linux/version.h: No such file or directory (ENOENT)
tulip.c:87: linux/kernel.h: No such file or directory (ENOENT)
tulip.c:88: linux/sched.h: No such file or directory (ENOENT)
tulip.c:89: linux/string.h: No such file or directory (ENOENT)
tulip.c:90: linux/timer.h: No such file or directory (ENOENT)
tulip.c:91: linux/errno.h: No such file or directory (ENOENT)
tulip.c:92: linux/ioport.h: No such file or directory (ENOENT)
tulip.c:93: linux/malloc.h: No such file or directory (ENOENT)
tulip.c:94: linux/interrupt.h: No such file or directory (ENOENT)
tulip.c:95: linux/pci.h: No such file or directory (ENOENT)
tulip.c:96: linux/netdevice.h: No such file or directory (ENOENT)
tulip.c:97: linux/etherdevice.h: No such file or directory (ENOENT)
tulip.c:98: linux/skbuff.h: No such file or directory (ENOENT)
tulip.c:99: asm/processor.h: No such file or directory (ENOENT)
tulip.c:100: asm/bitops.h: No such file or directory (ENOENT)
tulip.c:101: asm/io.h: No such file or directory (ENOENT)
tulip.c:134: linux/bios32.h: No such file or directory (ENOENT)
Apparently, I don't have the necessary include files to compile into
"tulip.o". Where might I find these?
"Dances With Crows" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> On Sun, 06 Aug 2000 22:30:34 GMT, Blayne Wessels wrote:
> >I have Debian Linux installed on one of my machines and want to get it on
my
> >network. I put in a Linksys 10/100Mbps network card (LNE100TX) and it
> >didn't recognize it. I later found that I would need the "Tulip Driver."
I
> >also found, under "\Linux" on the driver disks for the NIC, a file called
> >tulip.c. So I guess that what I'm really asking is: do I need to compile
> >the kernel with the tulip.c to use the NIC and if so, how?
>
> The tulip.c file is source code for a kernel module. COmpile the
> tulip.c code as per the instructions in the README that should be in the
> same directory as tulip.c, then move the tulip.o module to
> /lib/modules/$KERNELVERSION/net/ and run "depmod -a". Then you should
> be able to do "insmod tulip" and be able to use the NIC after you've
> given it an IP address with "ifconfig". After you've verified that the
> NIC works and such, edit /etc/conf.modules and insert the line
> alias eth0 tulip
> somewhere, commenting out any other lines that refer to eth0. Then the
> module loader will automagically load tulip.o whenever eth0 is accessed.
> HTH,
>
> --
> Matt G|There is no Darkness in Eternity/But only Light too dim for us to
see
> Brainbench MVP for Linux Admin / Tyranny is always better organized
> http://www.brainbench.com / than freedom.
> -----------------------------/ --Charles Peguy
------------------------------
Reply-To: "Phillip Kimble" <[EMAIL PROTECTED]>
From: "Phillip Kimble" <[EMAIL PROTECTED]>
Subject: Re: Rockwell 56K ACF II Modem
Date: Sun, 6 Aug 2000 20:18:35 -0500
1. What comport do you have it set up on? Most isa modems are configuable
those use of jumpers.
2. If your modem is on com1-4, make sure your bios is not interfering with
the modem.... A common mistake is to set your modem up as com2 (.dev.ttyS1)
and forget to shut com2 off in your computer's bios!
3. Try running setserial /dev/ttySx (x=the comport -1) auto_irq auto_config
4. If this doesnt work, post your findings to this newsgroup!! Easier the
more info you give us to work with!!
"Stuart Lightfoot" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> Thanks James
>
> Unfortunately my modem appears to be an ISA modem.
>
> Can anybody else help?
>
> Stuart
>
>
>
> On Fri, 04 Aug 2000 23:38:45 GMT, James Richard Tyrer <[EMAIL PROTECTED]>
> wrote:
>
> >This is a multi-part message in MIME format.
> >--------------983B7E6153BE4FAC4086C26B
> >Content-Type: text/plain; charset=us-ascii
> >Content-Transfer-Encoding: 7bit
> >
> >lightfootstuart wrote:
> >
> >> Can any body assist?
> >>
> >> I have this modem and am assured that it is not a win-modem despite it
> >> being of the internal variety. Still, I can't get linux to play with
> >> it! Any ideas?
> >>
> >> Stuart Lightfoot
> >
> >Is this an ISA modem or a PCI modem?
> >
> >For PCI exec the command "lspci -v | less" as root. The output should
> >include something like this:
> >
> >00:12.0 Serial controller: US Robotics/3Com 56K Fax Modem Model 5610 (rev
> >01) (prog-if 02 [16550])
> > Subsystem: US Robotics/3Com USR 56k Internal Voice Modem (Model
> >2976)
> > Flags: medium devsel, IRQ 14
> > I/O ports at ec00
> > Capabilities: [dc] Power Management version 2
> >
> >Then add a line like this:
> >
> >setserial -b /dev/ttyS0 port 0xec00 auto_irq autoconfig
> >
> >to the appropriate "rc" script ("rc.serial" on my system). The two
> >things which you need to change in the line are the number of the tty and
> >the port address, the tty depends on which com port it is using (e.g. for
> >COM1 use ttyS0) and the port is the "I/O port at" from lspci (in my case:
> >ec00). Remember, the I/O port address may change if you install more
> >hardware.
> >
> >AND, just how do you determine that the modem is connected to COM1? I do
> >not know, but if it is the only PCI serial device that is probably where
> >it will end up. Actually, it appears that you can chose, but I would
> >suspect that it would be better to use one that was not already in use.
> >
> >If you don't have "lspci" you can exec the command: "cat /proc/pci" and
> >your output should include something like this:
> >
> > Bus 0, device 18, function 0:
> > Serial controller: Unknown vendor Unknown device (rev 1).
> > Vendor id=12b9. Device id=1008.
> > Medium devsel. IRQ 14.
> > I/O at 0xec00 [0xec01].
> >
> >Which shows the same I/O address.
> >
> >These are generic instructions for PCI modems. They worked for me!
> >
> >If you have ISA, you will have to ask someone else.
> >
> >JRT
> >
> >--------------983B7E6153BE4FAC4086C26B
> >Content-Type: text/x-vcard; charset=us-ascii;
> > name="tyrerj.vcf"
> >Content-Transfer-Encoding: 7bit
> >Content-Description: Card for James Richard Tyrer
> >Content-Disposition: attachment;
> > filename="tyrerj.vcf"
> >
> >begin:vcard
> >n:Tyrer;James
> >tel;fax:call first
> >tel;home:(520) 648-3720
> >x-mozilla-html:TRUE
> >org:JRT Engineering
> >adr:;;1468 North Rio Sonora;Green Valley;Arizona;85614-4007;USA
> >version:2.1
> >email;internet:[EMAIL PROTECTED]
> >x-mozilla-cpt:;2
> >fn:James Tyrer
> >end:vcard
> >
> >--------------983B7E6153BE4FAC4086C26B--
> >
>
------------------------------
From: [EMAIL PROTECTED] (Dances With Crows)
Subject: Re: Installing an NIC
Date: 7 Aug 2000 01:19:48 GMT
Reply-To: [EMAIL PROTECTED]
On Mon, 07 Aug 2000 00:42:14 GMT, Blayne Wessels wrote:
>Actually, there was no readme: just tulip.c and the GNU General Public
>License. Although, being a programmer, I tried using djgpp to compile and
>received the following errors:
>tulip.c:75: linux/config.h: No such file or directory (ENOENT)
djgpp is the *DOS* version of gcc. I suppose it could compile a Linux
kernel module, if DOS could read ext2 filesystems, but I don't know if
I'd chance that.
Try putting " -I/usr/src/linux/include/linux/ " into the compiler
options. That's where the .h files the module needs live. If that
directory doesn't exist on your system, go apt-get the kernel source, or
at the very least, the kernel headers.
--
Matt G|There is no Darkness in Eternity/But only Light too dim for us to see
Brainbench MVP for Linux Admin / Tyranny is always better organized
http://www.brainbench.com / than freedom.
=============================/ ==Charles Peguy
------------------------------
From: sideband <[EMAIL PROTECTED]>
Subject: Re: Cannot install ISA Network Card
Date: Sun, 06 Aug 2000 21:45:23 -0400
Ok... this helps some....
What's the make/model of the ISA card? Is it ISA PnP? If so, is there some
configuration utility that came with the card that will allow you to turn PnP
off and set config parameters manually (For a free IRQ and Port address, etc)?
The output of /proc/pci is purely informational at this point, as the card is
ISA, so what's next is to find out what type of card it is, and go from there...
If it's a Linksys Ether16, then I know exactly what you're going thru, and I
know exactly how to fix it, as I had one that I had trouble with, at first.
Other NE2K cards should be similar...
Personally, I like to compile things like ethernet drivers, etc, directly into
the kernel, so a module doesn't have to be loaded, but that's just me.
Let me know on the make/model of the card, and we'll go from there.
-SSB
Dheera Venkatraman wrote:
> Hi,
> I've included the results of those commands below. I've temporarily removed
> the eth2 device that I was trying to add since it was giving me erros at
> boot (insmod /lib/modules/2.2.14-5.0/net/ne.o: init_module: Device or
> Resource Busy).
>
> dmesg, as shown below, said that such a card was not found at 0x300. Is
> there a probing program that will tell me the io and irq...?
>
> The card I'm trying to install is actually my third ethernet card - I have
> two PCI ones working, and want to install the ISA one as my third - that's
> why it's eth2... Can this output below help in any way to shed some light on
> the problem? Or would it be best to simply get another PCI card?
>
> Thanks again...
>
> Dheera Venkatraman
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
>
> _________________
> From dmesg:
> ne.c:v1.10 9/23/94 Donald Becker ([EMAIL PROTECTED])
> NE*000 ethercard probe at 0x300: unable to get IRQ 11 (irqval=-16).
> ne.c: No NE*000 card found at i/o = 0x300
> __________________
> 'cat /proc/interrupts' gives me this:
> CPU0
> 0: 9565833 XT-PIC timer
> 1: 4877 XT-PIC keyboard
> 2: 0 XT-PIC cascade
> 4: 27445782 XT-PIC serial
> 8: 1 XT-PIC rtc
> 10: 388174 XT-PIC eth1
> 11: 4297 XT-PIC eth0
> 12: 120 XT-PIC PS/2 Mouse
> 13: 1 XT-PIC fpu
> 14: 940737 XT-PIC ide0
> 15: 285161 XT-PIC ide1
> NMI: 0
> _________________
> 'cat /proc/pci' gives me this:
> PCI devices found:
> Bus 0, device 0, function 0:
> Host bridge: Intel 82437VX Triton II (rev 2).
> Medium devsel. Master Capable. Latency=128.
> Bus 0, device 7, function 0:
> ISA bridge: Intel 82371SB PIIX3 ISA (rev 1).
> Medium devsel. Fast back-to-back capable. Master Capable. No
> bursts.
> Bus 0, device 7, function 1:
> IDE interface: Intel 82371SB PIIX3 IDE (rev 0).
> Medium devsel. Fast back-to-back capable. Master Capable.
> Latency=128.
> I/O at 0xffa0 [0xffa1].
> Bus 0, device 7, function 2:
> USB Controller: Intel 82371SB PIIX3 USB (rev 1).
> Medium devsel. Fast back-to-back capable. IRQ 11. Master Capable.
> Latency=128.
> I/O at 0xff40 [0xff41].
> Bus 0, device 13, function 0:
> Ethernet controller: Realtek 8029 (rev 0).
> Medium devsel. IRQ 11.
> I/O at 0xff80 [0xff81].
> Bus 0, device 14, function 0:
> VGA compatible controller: S3 Inc. ViRGE/VX (rev 2).
> Medium devsel. IRQ 11. Master Capable. Latency=128. Min Gnt=4.Max
> Lat=255.
> Non-prefetchable 32 bit memory at 0xf8000000 [0xf8000000].
> Bus 0, device 15, function 0:
> Ethernet controller: 3Com 3C905 100bTX (rev 0).
> Medium devsel. IRQ 10. Master Capable. Latency=128. Min Gnt=3.Max
> Lat=8.
> I/O at 0xff00 [0xff01].
>
> "sideband" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]...
> > if it's the second ethernet card, it's probably called eth1, as the
> primary is
> > called eth0.
> >
> > at any rate, there's something else going on here, as well.....
> IRQ/DMA/port
> > conflict, or some other problem with the card. If it's PnP, you should try
> to
> > disable it and manually set the settings.
> >
> > How about posting the results of 'cat /proc/interrupts' and 'cat
> /proc/pci' as
> > well as the relevant dmesg output, so maybe we can make some sort of
> intelligent
> > response.
> >
> > -SSB
> >
> > Dheera Venkatraman wrote:
> >
> > > Hi,
> > > I just wanted to hook in another network card to my RedHat 6.2 computer,
> and
> > > I happened to have a spare ISA card lying around (on windows, it used to
> use
> > > the rtl8029 driver... i'm assuming it's ne2000 compatible).
> > >
> > > I went to netcfg and put in the driver, using ne.o as the module in
> > > /etc/conf.modules ... but when I try to activate the interface, it says
> > > "Delaying eth2 initialization." and doesn't work.
> > >
> > > Any ideas, or is there a program available to autodetect and install
> this
> > > card (it's ISA)?
> > >
> > > Dheera Venkatraman
> > > [EMAIL PROTECTED]
> > > [EMAIL PROTECTED]
> >
------------------------------
From: sideband <[EMAIL PROTECTED]>
Subject: Re: What about Rockwell HCF 56k Data fax speakerphone PCI modem
Date: Sun, 06 Aug 2000 21:46:08 -0400
HCF = Winmodem... And I hear the rockwell's don't like to work....
Sorry.
-SSB
Glitch wrote:
> unless it has a lucent chip and therefore would possibly work with the
> ltmodem.o driver then it won't work in Linux. You can thank the
> manufacturer for that.
>
> ino wrote:
> >
> > Will this work on Linux?
> > i got Red Hat 6.0
> > it's on com3 (/dev/ttyS2)
------------------------------
From: sideband <[EMAIL PROTECTED]>
Subject: Re: Installing an NIC
Date: Sun, 06 Aug 2000 21:48:09 -0400
Just recompile and install a new kernel with the tulip driver compiled in it,
and it will work just fine.
-SSB
Blayne Wessels wrote:
> I have Debian Linux installed on one of my machines and want to get it on my
> network. I put in a Linksys 10/100Mbps network card (LNE100TX) and it
> didn't recognize it. I later found that I would need the "Tulip Driver." I
> also found, under "\Linux" on the driver disks for the NIC, a file called
> tulip.c. So I guess that what I'm really asking is: do I need to compile
> the kernel with the tulip.c to use the NIC and if so, how?
------------------------------
** 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 (and comp.os.linux.hardware) via:
Internet: [EMAIL PROTECTED]
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
******************************
