Linux-Hardware Digest #416, Volume #14 Wed, 28 Feb 01 16:13:07 EST
Contents:
Re: VIA IDE problems (was Re: Need LOTS of disks: Promise ATA RAID??) (Tim Haynes)
Temperature probing? (B N)
where to put setserial for bootup?? ? ? (lucas)
Re: where to put setserial for bootup?? ? ? (glen)
Re: intel 810 chipset ([EMAIL PROTECTED])
Re: How do I load a module at start up? ("Kit Chong")
Can't access scsi drives (Mike Veenhuizen)
Re: RAID on Linux: What type of hardware to choose? (Allen Crider)
Query on ATA/66 and ATA/100 ("Tim Chappell")
Re: Need LOTS of disks: Promise ATA RAID?? (Jonathan Buzzard)
Re: HP Pavilion 9870 can't see keyboard (Raymond McLaughlin)
Re: Should I abandon SCSI? ("NewsReader2")
LILO version 21.7 released (John in SD)
Re: Cirrus Logic (Javier Velazquez)
Re: intel 810 chipset ("John Pfaff")
Re: Can't access scsi drives ("D. Stimits")
----------------------------------------------------------------------------
From: Tim Haynes <[EMAIL PROTECTED]>
Crossposted-To: uk.comp.os.linux
Subject: Re: VIA IDE problems (was Re: Need LOTS of disks: Promise ATA RAID??)
Date: 28 Feb 2001 16:06:59 +0000
Reply-To: Tim Haynes <[EMAIL PROTECTED]>
[EMAIL PROTECTED] (Piercarlo Grandi) writes:
[snip]
> I have been using lots of releases of 2.2.x and 2.3.x and 2.4.x with both
> a VIA 586 chipset with ATA33 and a VIA 686 with ATA66/100, and quite
> successfully. I suspect there is no real problem with the Linux IDE
> driver, perhaps maybe only some tighter timing settings than is prudent,
> but this is only speculation.
This any use? :
VP_IDE: VIA vt82c686a IDE UDMA66 controller on pci0:4.1
ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:DMA, hdd:pio
Been running that kit since last August, IIRC, with whatever kernel's
been available to play with, currently 2.4.1. Not lost a byte yet.
~Tim
--
Roobarb and Custard let fly |[EMAIL PROTECTED]
with their secret weapon. |http://spodzone.org.uk/
------------------------------
From: [EMAIL PROTECTED] (B N)
Subject: Temperature probing?
Date: Wed, 28 Feb 2001 16:19:40 GMT
Hi!
I've got an MSI A7T motherboard with an Athlon 950 processor. I'm
using SuSE 7.0 (I will probably upgrade to 7.1 soon.) Anyhow I'd like
to find some software that gives me the temperature readings etc, like
the readings which I can access in the Bios pane, under health.
Does anyone know which software I can use to do the same while logged
into Linux?
Regards
Bj�rn
------------------------------
Date: Wed, 28 Feb 2001 12:58:04 -0500
From: lucas <[EMAIL PROTECTED]>
Subject: where to put setserial for bootup?? ? ?
hello one and all,
i have an internal isa modem set at ttyS3 under redhat 6.2, kernel version
2.2.14-5.0. the modem works great after i do "setserial /dev/ttyS3 irq 5". i
want to put this in a configuration file so that it properly initializes ttyS3
at bootup. please offer your opinions. thank you in advance and have a nice
day.
lucas
------------------------------
From: glen <[EMAIL PROTECTED]>
Subject: Re: where to put setserial for bootup?? ? ?
Date: Wed, 28 Feb 2001 17:48:52 +0000
> hello one and all,
>
> i have an internal isa modem set at ttyS3 under redhat 6.2, kernel version
> 2.2.14-5.0. the modem works great after i do "setserial /dev/ttyS3 irq 5". i
> want to put this in a configuration file so that it properly initializes ttyS3
> at bootup. please offer your opinions. thank you in advance and have a nice
> day.
>
^^^
Well I put all our serial config into a file named rc.setserial which is located
in /etc/rc.d, this is then sourced by
rc.sysinit :
# Initialize the serial ports.
if [ -f /etc/rc.d/rc.serial ]; then
. /etc/rc.d/rc.serial
fi
Thats my opinion anyway.
Glen
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: intel 810 chipset
Date: Wed, 28 Feb 2001 18:14:08 GMT
[EMAIL PROTECTED] wrote:
> I'm having trouble getting X to work with my Optiplex GX110 system. If you
> would, please send me a copy of your XF86Config file. Also, which server
> are you using? I'm running Red Hat 6.2 with the standard kernel.
I have a number of systems working with the intel 810 chipset.
However, there are a number of things you have to do, including
installing a module called agpgart.o. As I recall, I got a special
copy of XFCom_i810 from the intel website or something.
Here is my version information.
$ X -version
XFCom_i810 Version 1.0.0 / X Window System
(protocol Version 11, revision 0, vendor release 6300)
Release Date: October 13 1999
If the server is older than 6-12 months, or if your card is newer
than the above date, look for a newer version before reporting
problems. (see http://support.intel.com)
Operating System: Linux 2.2.5-15 i686 [ELF]
Configured drivers:
SVGA: server for SVGA graphics adaptors (Patchlevel 0):
i810, i810-dc100, i810e, generic
>> I have a dell optiplex gx 100 system with a intel 810 chipset for video.
>> I'm running mandrake 7.1 and I have a weird problem.
>>
>> After editing the XFconfig file myself because mandrake didn't detect the
>> card at all I have a fine running X system when using the standard kernel
>> 2.2.15. I want to use the 2.4.1 kernel, but when boot that one X starts
>> whining that it doesn't know the intel chipset while I do have the right
>> drivers.
--
Best regards,
Stephen Jenuth
([EMAIL PROTECTED])
Quidquid latine dictum sit, altum viditur.
------------------------------
From: "Kit Chong" <[EMAIL PROTECTED]>
Subject: Re: How do I load a module at start up?
Date: Thu, 1 Mar 2001 02:21:44 +0800
Thanks for the help!
"Matthew Paterson" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> You may have to reference modprobe, as in "/usr/sbin/modprobe/", thats
> what i have to do, or else modprobe doesnt run.
>
> Matt
>
> Markku Kolkka wrote:
> >
> > "Kit Chong" <[EMAIL PROTECTED]> writes:
> > > I'm a linux newbie using 2 D-Link DFE-538TX cards on my PC. I need
to
> > > load the pci-scan.o module before I can load the rtl8139.o drivers for
the
> > > card. How do I load the pci-scan.o at loading time before it loads the
> > > rtl8139.o module so that I don't get the [FAILED] when initializing my
eth0
> > > and eth1?
> >
> > Add the following line to /etc/modules.conf (or conf.modules):
> >
> > pre-install rt18139 modprobe pci-scan
> >
> > --
> > Markku Kolkka
> > [EMAIL PROTECTED]
------------------------------
From: Mike Veenhuizen <[EMAIL PROTECTED]>
Subject: Can't access scsi drives
Date: Wed, 28 Feb 2001 18:27:32 GMT
===============_4D4800CA887D029C0AF0
Content-Description: filename="text1.txt"
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
I have a system with two scsi 9M hard drives. The second one was added =
just two weeks ago. I installed Slackware on this drive. I edited=20
lilo.conf and ran lilo, so that I could boot either linux on sda3, linux=
=20
on sdb1, or windows on sda1. It all worked perfectly. On the weekend I=
=20
recompiled the kernel on sdb1, and ran zlilo. After I rebooted I had a =
kernel panic, with the system unable to access the hard drive. I booted=
=20
up my floppy linux rescue disk, and when I ran fdisk I received the=20
message "Cannot access /dev/sda, or cannot access /dev/sdb. If I tried =
to mount any of the drive partitions, I got the message " device /dev/sd=
*=20
is not a block device". I think the problem is with the scsi bus, but=20=
windows still works fine, and can access, format, partition etc. any of =
the drives. I have been using linux for a number of years, and this is =
a=20
first. Any help?
===============_4D4800CA887D029C0AF0
Content-Description: filename="text1.html"
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"CONTENT-TYPE" CONTENT=3D"text/html; charset=3Diso-8=
859-1">
<TITLE>Can't access scsi drives</TITLE>
<META NAME=3D"GENERATOR" CONTENT=3D"StarOffice/5.2 (Win32)">
<META NAME=3D"CREATED" CONTENT=3D"20010228;13203866">
<META NAME=3D"CHANGEDBY" CONTENT=3D"Mike Veenhuizen">
<META NAME=3D"CHANGED" CONTENT=3D"20010228;13273224">
</HEAD>
<BODY>
<P>I have a system with two scsi 9M hard drives. The second one was
added just two weeks ago. I installed Slackware on this drive. I
edited lilo.conf and ran lilo, so that I could boot either linux on
sda3, linux on sdb1, or windows on sda1. It all worked perfectly. On
the weekend I recompiled the kernel on sdb1, and ran zlilo. After I
rebooted I had a kernel panic, with the system unable to access the
hard drive. I booted up my floppy linux rescue disk, and when I ran
fdisk I received the message "Cannot access /dev/sda, or cannot
access /dev/sdb. If I tried to mount any of the drive partitions, I
got the message " device /dev/sd* is not a block device". I
think the problem is with the scsi bus, but windows still works fine,
and can access, format, partition etc. any of the drives. I have been
using linux for a number of years, and this is a first. Any help?</P>
</BODY>
</HTML>
===============_4D4800CA887D029C0AF0==
------------------------------
From: Allen Crider <[EMAIL PROTECTED]>
Crossposted-To: redhat.linux.misc
Subject: Re: RAID on Linux: What type of hardware to choose?
Date: Wed, 28 Feb 2001 11:19:17 -0800
Toralf Lund wrote:
Are you just wondering or maybe you could imagine how many transactions per
second you are needing.
> We want to set up a RAID system consisting of 6 to 8 36 or 73 Gb disks
> (initially; we may or may not want to add more disks later) for a Linux
> host , which is Intel (dual-Pentium-III) based and runs Red Hat 7.0.
> However, we are uncertain about what type of hardware to choose. As I
> understand, there are 3 different types of configurations, namely:
>
> 1. An external, self-contained SCSI unit (SCSI-to-SCSI)
> 2. Internal (PCI) RAID controller and SCSI disks.
> 3. Internal RAID controller with IDE/ATA disks.
>
> I was just wondering about what other peoples experience with the
> different setups are, and what you would recommend. - At the moment, I'm
> inclined to go for alternative 1. as it seems to be the most reliable
> one, and also the one where the installation involves the least amount
> of hassle. I'm assuming that there will be a certain amount of messing
> around with drivers with 2. and 3., but maybe this isn't really a
> problem? Also, 1. is probably the most expensive solution, which isn't a
> major concern as such, but an added cost obviously has to be justified.
> Finally - and this may be a silly question, but I really have no
> experience with ATA disks - would selecting the IDE/ATA setup mean that
> all disks need to fit into the main cabinet? (I seem to remember that
> there was such a limitation with IDE back in the old days.)
>
>
> - Toralf
>
>
------------------------------
From: "Tim Chappell" <[EMAIL PROTECTED]>
Subject: Query on ATA/66 and ATA/100
Date: Wed, 28 Feb 2001 19:29:03 -0000
All,
I currently have an Asus K7M motherboard with IDE ATA/66 controller/drives.
I'm looking to add a new larger capacity drive (20G+) and install SUSE Linux
7.1. Am I right in thinking that it is ok to add an ATA/100 drive to my
existing
ATA/66 and Linux will support this. I was intending to use the onboard
ATA/66
controller.
(The query stems from the fact I've seen several postings on other groups
mentioning problems with ATA/100 controllers and I wanted to make sure that
if my
controller is ATA/66 then Linux will happily support this - slackware works
fine).
Many thanks for any pointers.
Tim.
--
------------------------------
From: [EMAIL PROTECTED] (Jonathan Buzzard)
Crossposted-To: uk.comp.os.linux
Subject: Re: Need LOTS of disks: Promise ATA RAID??
Date: Tue, 27 Feb 2001 23:11:49 +0000
In article <slah79.a66.ln@helix>,
"Steve Wolfe" <[EMAIL PROTECTED]> writes:
>> These are good but the write perfomance on RAID 5 is a bit sucky and
>> the read is not too hot either. You really need to do your homework
>> first.
>
> Are you sure? I have a RAID 5 array sitting under my desk, consisting of
> only 4 drives (and one of those is a hot spare), and those are only 9 gigs.
> Not the latest, greatest by any means. Yesterday I copied a few gigs from
> an IDE drive to the RAID array under Linux, and even though the IDE drive
> was at full speed reading, the RAID array was only active about 1/2 of the
> time writing. If it will *write* twice as fast as my IDE drive can *read*,
> that's pretty fast.
Sucky compaired to a good SCSI system.
> Granted, it's not as fast as simple striping, but you make it sound like
> it's going to be abysmally slow, which it won't. It should still be faster
> than a single SCSI drive, and simply blow away anything from IDE.
>
You can get a performance boast if you use RAID 0 against two RAID 5
systems, but access times do suffer a little bit.
JAB.
--
Jonathan A. Buzzard Email: [EMAIL PROTECTED]
Northumberland, United Kingdom. Tel: +44(0)1661-832195
------------------------------
From: Raymond McLaughlin <[EMAIL PROTECTED]>
Subject: Re: HP Pavilion 9870 can't see keyboard
Date: Wed, 28 Feb 2001 15:04:03 -0500
Frustrating isn't it? I ran into the same problem when I installed SuSE
7.0 on my mom's Pavilion. It seem the BIOS setting for legacy emulation
is good enough for installing, but craps out once you boot the installed
system. I was in worse shape. I didn't have a regular keyboard so I was
completely out of luck. I'll take one the next time I go to visit.
What I *would* have done, if I could have gotten into the system was
compile a kernel that explicitly supports the USB port and USB keyboard,
and USB mouse. Since you need these devices from the get go I would
compile them into the kernel rather than as modules. I'm not familiar
with your distro, but it probably includes the kernel source, gcc, and a
couple of other things you'll need to make a new kernel.
It is not particularly unusual to have to compile a new kernel to
support some piece of hardware or other, but it can be a pain when it's
something crucial like the keyboard. If you have never compiled a new
kernel before you are in for a learning experience. It would be beyond
the scop[e of this thread to go into too much detail, but here's a short
version.
Install all the packages you need to compile new kernel, inc. kernel
source, gcc, make, and x86assembler. see you documentation for more
details.
as root:
cd /usr/src/linux
make menuconfig
-scroll through menu items and sub menus adding all hardware and
protocols you want supported, and excluding all hardware you don't have.
Most items have descriptive help text. It's often quickest to scroll to
the bottom of these help texts to find short summary like, "most people
don't need this", or "If unsure select yes". When done selecting from
the menu items, exit menuconfig saving changes.\
make dep
make bzImage
make modules
make modules_install
At this point you new bootable kernel will be a file called
/usr/src/linux/arch/i386/boot/bzImage . I recomend you copy it thusly
(while in /usr/src/linux):
cp arch/i386/boot/bzImage /boot/vmlinuz.new
open /etc/lilo.conf in your favorit text editor and find several lines
such as:
image = /boot/vmlinuz
label = linux
root = /dev/hda2
make a copy this block of lines, below the original, and edit the copies
to read something like:
image = /boot/vmlinuz.new
label = new
root = /dev/hda2
save and exit.
Run lilo (command "lilo")
when lilo runs it outputs information about the success/failure of the
installation of the new kernel images. There should be no problems here.
When you reboot type "new" when the lilo prompt appears, and your new
kernel should try to boot. It's success or failure depends largely on
how well you chose among the menu items in menuconfig. If ther are
problems you can reboot and try again starting with make menuconfig .
Your original kernel will be the default boot kernel because it was the
first image entry in lilo.conf at the time you ran lilo.
Once you are satisfied with a new kernel you can move it's
image-label-root enteries to the top of the list in lilo.conf, and run
lilo again to make your new kernel the default.
That's the basic, the devil is in the details. Good luck
Raymond McLaughlin
"Stephen S. Murray" wrote:
>
> I installed Mandrake 7.2 on a clean HP Pavilion 9870 machine.
> Install went fine and both mouse and keyboard worked during the
> installation.
> Upon reboot GRUB menu comes up but will not respond to the keyboard
> (USB) so only the default system boots (Linux). Boot seems to be okay
> (nothing fails) but at the login prompt there is no response to the
> keyboad. It Ireplace the USB keyboard with a standard PC keyboard
> everthing works properly - what can I do to get Grub and Linux to see
> the uSB keyboard that comes with the HP system?
>
> I changed the GRUB default to Windows, attached the USB keyboard and got
> the same results at the GRUB menu, but once Windows booted, the keyboard
> was working.
>
> So, it appears that GRUB doesn't know about the USB keyboard, nor does
> Linux.
>
> Help......
>
> Steve Murray
------------------------------
From: "NewsReader2" <[EMAIL PROTECTED]>
Crossposted-To: comp.periphs.scsi
Subject: Re: Should I abandon SCSI?
Date: Wed, 28 Feb 2001 20:09:04 GMT
"Ron Reaugh" <[EMAIL PROTECTED]> wrote in message
news:7g5n6.6016$[EMAIL PROTECTED]...
>
> J.B. Nicholson-Owens wrote in message ...
> >Donovan Rebbechi wrote:
> >> RAID 0 is great for high performance desktops, but if you want a
> >> storage solution that's also *reliable*, it's useless.
> >
> >I wouldn't say it's useless--that depends on the data stored on the
volume
> >and how well the site has prepared for failure. But I agree--RAID 0 is a
> >high price to pay for failure.
>
>
> Nope, just keep good backups like is required with a single HD.
>
Not good enough at 3:00pm the next day!
Just keep to a single drive for greater reliability and stability.
Choose 10K+ SCSI to improve workstation performance
------------------------------
From: John in SD <[EMAIL PROTECTED]>
Subject: LILO version 21.7 released
Reply-To: [EMAIL PROTECTED]
Date: Wed, 28 Feb 2001 20:25:01 GMT
LILO release 21.7 is based upon Werner Almesberger's LILO version 21.
Version 21.7 adds support for higher serial line rates and fixes a few
minor problems discovered in release 21.6.1. It maintains all backward
compatiblity.
Version 21.6 is an upgrade for users of the Reiser File System, and adds
new diagnostic capabilities. Internal changes allow booting kernels with
larger real-mode setup codes (2.4.0 and later). This version is fully
backward compatible with version 21.5, which added the customizable boot
menu interface, and versions back to 21.2, which allowed booting beyond
the 1024 cylinder limit on disks >8Gb.
Source code is available for download from:
ftp://brun.dyndns.org/pub/linux/lilo (developer's site)
Or from the main distribution site:
ftp://metalab.unc.edu/pub/Linux/system/boot/lilo (please use)
See the distribution file 'CHANGES' for details of the differences between
21.7 and prior releases.
--John Coffman <[EMAIL PROTECTED]>
LILO version 21.6.1 (16-Dec-2000) source at
http://www.ibiblio.org/pub/Linux/system/boot/lilo
patches at ftp://brun.dyndns.org/pub/linux/lilo
------------------------------
From: Javier Velazquez <[EMAIL PROTECTED]>
Subject: Re: Cirrus Logic
Date: Wed, 28 Feb 2001 20:30:05 -0000
Javier Velazquez wrote:
>
>
> I have a Cirrus logic Display Adapter CL-GD5465-HC-C Internal that I
need drivers
> Regards
>
Javier Velazquez
> [EMAIL PROTECTED]
>
>
--
Posted via CNET Help.com
http://www.help.com/
------------------------------
From: "John Pfaff" <[EMAIL PROTECTED]>
Subject: Re: intel 810 chipset
Date: Wed, 28 Feb 2001 16:09:34 -0500
What do you know, that did the trick. Thank you.
<[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
>
> > I'm having trouble getting X to work with my Optiplex GX110 system. If
you
> > would, please send me a copy of your XF86Config file. Also, which
server
> > are you using? I'm running Red Hat 6.2 with the standard kernel.
>
> I have a number of systems working with the intel 810 chipset.
>
> However, there are a number of things you have to do, including
> installing a module called agpgart.o. As I recall, I got a special
> copy of XFCom_i810 from the intel website or something.
>
> Here is my version information.
>
> $ X -version
>
> XFCom_i810 Version 1.0.0 / X Window System
> (protocol Version 11, revision 0, vendor release 6300)
> Release Date: October 13 1999
> If the server is older than 6-12 months, or if your card is newer
> than the above date, look for a newer version before reporting
> problems. (see http://support.intel.com)
> Operating System: Linux 2.2.5-15 i686 [ELF]
> Configured drivers:
> SVGA: server for SVGA graphics adaptors (Patchlevel 0):
> i810, i810-dc100, i810e, generic
>
> >> I have a dell optiplex gx 100 system with a intel 810 chipset for
video.
> >> I'm running mandrake 7.1 and I have a weird problem.
> >>
> >> After editing the XFconfig file myself because mandrake didn't detect
the
> >> card at all I have a fine running X system when using the standard
kernel
> >> 2.2.15. I want to use the 2.4.1 kernel, but when boot that one X starts
> >> whining that it doesn't know the intel chipset while I do have the
right
> >> drivers.
>
> --
> Best regards,
>
> Stephen Jenuth
> ([EMAIL PROTECTED])
>
> Quidquid latine dictum sit, altum viditur.
------------------------------
Date: Wed, 28 Feb 2001 14:09:35 -0700
From: "D. Stimits" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: Re: Can't access scsi drives
> Mike Veenhuizen wrote:
>
> I have a system with two scsi 9M hard drives. The second one was added
> just two weeks ago. I installed Slackware on this drive. I edited
> lilo.conf and ran lilo, so that I could boot either linux on sda3,
> linux on sdb1, or windows on sda1. It all worked perfectly. On the
> weekend I recompiled the kernel on sdb1, and ran zlilo. After I
> rebooted I had a kernel panic, with the system unable to access the
> hard drive. I booted up my floppy linux rescue disk, and when I ran
> fdisk I received the message "Cannot access /dev/sda, or cannot access
> /dev/sdb. If I tried to mount any of the drive partitions, I got the
> message " device /dev/sd* is not a block device". I think the problem
> is with the scsi bus, but windows still works fine, and can access,
> format, partition etc. any of the drives. I have been using linux for
> a number of years, and this is a first. Any help?
I've seen something similar. It seems that the failed boot device causes
the scsi controller to not register the existence of the drive. Boot
floppies based on regular boot allow the drives to be visible and run
fine, but rescue cd's and rescue floppies seem to not see the drives. If
you run under a rescue though, even without the device being found, I
have had lilo -v -u succeed in uninstalling the failed boot sector
(reinstating the original).
As to why it panicked, perhaps you didn't compile in the scsi support
needed. Modules only work if the initial ramdisk is used, with mkinitrd
(modules on the scsi drive can't be found without the ability to access
scsi in the first place, but that ability requires scsi access for
modules to tell it how to...catch 22). I always compile scsi directly
into a kernel, versus modules.
------------------------------
** 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
******************************
