Linux-Hardware Digest #339, Volume #14 Tue, 13 Feb 01 15:13:05 EST
Contents:
Re: Best RAID controller for Linux (Prostorage)
Re: Update: Install hangs computer ("Rex Dieter")
Re: Update: Install hangs computer ("Rex Dieter")
Re: Update: Install hangs computer ("Rex Dieter")
Re: Update: Install hangs computer ("Rex Dieter")
Re: Update: Install hangs computer ("Rex Dieter")
Re: Update: Install hangs computer ("Rex Dieter")
Re: Update: Install hangs computer ("Rex Dieter")
Re: Tape drive for Linux (Rob Clive)
Re: ide-scsi on ata 100 hd, safe ??? (Markus Kossmann)
AMI Megaraid ("Steve Wolfe")
Re: devfs and IDE ATAPI floppy (problem solved) (Jonathan DeSena)
hauppauge wintv under 2.4.0 without sound? (Holger Thiele)
Re: a cordless logitech wheelmouse (Jim Newton)
Re: Linux on MPC860: OK? Or asking for trouble? (Josh Stern)
----------------------------------------------------------------------------
Crossposted-To: linux.dev.raid
Subject: Re: Best RAID controller for Linux
From: [EMAIL PROTECTED] (Prostorage)
Date: Tue, 13 Feb 2001 17:14:00 GMT
sort of true
but Adaptec has come out with good Linux drivers for their new
PCI-Ultra-160M RAID controllers, as has Mylex
AND
RAID subsystems based on driverless (using host independent RAID
controllers like Chaparral, Mylex, CMD & Infotrend) are able to be
attached to your SCSI chain, just like an external disk drive, AND
appear to the the system as one, large, transparant disk drive
AND is (usually) a much more powerful, and costly, solution
_____ . .
' \\ . . |>>
O// . . |
\_\ . . |
| | . . . |
/ | . mailto:[EMAIL PROTECTED] . . . |
/ .| 800-324-6711 / 800-720-7618 fax . . . |
/ . | http://www.geocities.com/scsiperipherals . .. . o
======================================================================
Authorized - DIRECT VAR/VAD/Distributor for new SCSI/FC-AL peripherals
from: IBM, Seagate, Quantum, NAS / SAN / RAID, QLogic, JNI, ATL, ect.
In article <cKKh6.49832$[EMAIL PROTECTED]>, [EMAIL PROTECTED]
says...
>
>Best array controllers for Linux (any flavor) are ICP Vortex array
>controllers.
>
>Check out www.icp-vortex.com for more info-- and buy them online 24x7 at
>www.icp-order.com
>
>We've been running them with Redhat here for 3 years (and some NT too
>actually... they work great with any major OS). They have supported Linux
>long before any of the other manufacturers.
>
>-Leo
>
>
>
--
------------------------------
From: "Rex Dieter" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Re: Update: Install hangs computer
Date: Tue, 13 Feb 2001 11:21:15 -0600
Do you have a conventional floppy? If not, that could be it.
I've had installs on machines with LS-120's or zip's only stall because the
floppy driver hangs the boot process. One several occasions, disabling the
floppy interface altogether in the machine's bios helped. On one occasion,
however, this did NOT help.
So, I'll ask everyone: is it possible via kernel/lilo parameter to disable
or prevent the loading of the floppy driver?
--
Rex Dieter
Computer System Administrator
Mathematics and Statistics
University of Nebraska Lincoln
"Marc Ulrich" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> It hadn't even gotten past text mode.
...
> There I type 'linux' or 'expert' and it starts loading what I
> suppose is the boot image:
> initrd.img .................
> vmlinuz ..............
> ..
> bunch of text
> ..
> last three lines of this text before it hangs are:
> PCI: PCI BIOS revision 2.10 entry at 0xfdb91
> PCI: Using configuration type 1
> PCI: probing PCI hardware
> after which the computer hangs.
> The current computer hardware is the following:
> It's a Gateway E-5400 :
> various IDE devices (harddrive, CDRom, Zip drive)
------------------------------
From: "Rex Dieter" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Re: Update: Install hangs computer
Date: Tue, 13 Feb 2001 11:22:58 -0600
Do you have a conventional floppy? If not, that could be it.
I've had installs on machines with LS-120's or zip's only stall because the
floppy driver hangs the boot process. One several occasions, disabling the
floppy interface altogether in the machine's bios helped. On one occasion,
however, this did NOT help.
So, I'll ask everyone: is it possible via kernel/lilo parameter to disable
or prevent the loading of the floppy driver?
--
Rex Dieter
Computer System Administrator
Mathematics and Statistics
University of Nebraska Lincoln
"Marc Ulrich" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> There I type 'linux' or 'expert' and it starts loading what I
> suppose is the boot image:
> initrd.img .................
> vmlinuz ..............
> ..
> bunch of text
> ..
> last lines of this text before it hangs are:
> PCI: Using configuration type 1
> PCI: probing PCI hardware
> after which the computer hangs.
> The current computer hardware is the following:
> various IDE devices (harddrive, CDRom, Zip drive)
------------------------------
From: "Rex Dieter" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Re: Update: Install hangs computer
Date: Tue, 13 Feb 2001 11:24:36 -0600
Do you have a conventional floppy? If not, that could be it.
I've had installs on machines with LS-120's or zip's only stall because the
floppy driver hangs the boot process. One several occasions, disabling the
floppy interface altogether in the machine's bios helped. On one occasion,
however, this did NOT help.
So maybe you could try peeking around in the system bios for a similar
disable option for the floppy interface.
p.s. For posterity: Does anyone know if it is possible via kernel/lilo
parameter to disable or prevent the loading of the floppy driver?
--
Rex Dieter
Computer System Administrator
Mathematics and Statistics
University of Nebraska Lincoln
"Marc Ulrich" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> There I type 'linux' or 'expert' and it starts loading what I
> suppose is the boot image:
> initrd.img .................
> vmlinuz ..............
> ..
> bunch of text
> ..
> last lines of this text before it hangs are:
> PCI: Using configuration type 1
> PCI: probing PCI hardware
> after which the computer hangs.
> The current computer hardware is the following:
> various IDE devices (harddrive, CDRom, Zip drive)
------------------------------
From: "Rex Dieter" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Re: Update: Install hangs computer
Date: Tue, 13 Feb 2001 11:25:02 -0600
Do you have a conventional floppy? If not, that could be it.
I've had installs on machines with LS-120's or zip's only stall because the
floppy driver hangs the boot process. One several occasions, disabling the
floppy interface altogether in the machine's bios helped. On one occasion,
however, this did NOT help.
So maybe you could try peeking around in the system bios for a similar
disable option for the floppy interface.
p.s. For posterity: Does anyone know if it is possible via kernel/lilo
parameter to disable or prevent the loading of the floppy driver?
--
Rex Dieter
Computer System Administrator
Mathematics and Statistics
University of Nebraska Lincoln
"Marc Ulrich" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> There I type 'linux' or 'expert' and it starts loading what I
> suppose is the boot image:
> initrd.img .................
> vmlinuz ..............
> bunch of text
> last lines of this text before it hangs are:
> PCI: Using configuration type 1
> PCI: probing PCI hardware
> after which the computer hangs.
------------------------------
From: "Rex Dieter" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Re: Update: Install hangs computer
Date: Tue, 13 Feb 2001 11:25:25 -0600
Do you have a conventional floppy? If not, that could be it.
I've had installs on machines with LS-120's or zip's only stall because the
floppy driver hangs the boot process. One several occasions, disabling the
floppy interface altogether in the machine's bios helped. On one occasion,
however, this did NOT help.
So maybe you could try peeking around in the system bios for a similar
disable option for the floppy interface.
p.s. For posterity: Does anyone know if it is possible via kernel/lilo
parameter to disable or prevent the loading of the floppy driver?
--
Rex Dieter
Computer System Administrator
Mathematics and Statistics
University of Nebraska Lincoln
"Marc Ulrich" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> last lines of this text before it hangs are:
> PCI: Using configuration type 1
> PCI: probing PCI hardware
> after which the computer hangs.
> The current computer hardware is the following:
> various IDE devices (harddrive, CDRom, Zip drive)
------------------------------
From: "Rex Dieter" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Re: Update: Install hangs computer
Date: Tue, 13 Feb 2001 11:25:57 -0600
Do you have a conventional floppy? If not, that could be it.
I've had installs on machines with LS-120's or zip's only stall because the
floppy driver hangs the boot process. One several occasions, disabling the
floppy interface altogether in the machine's bios helped. On one occasion,
however, this did NOT help.
So maybe you could try peeking around in the system bios for a similar
disable option for the floppy interface.
p.s. For posterity: Does anyone know if it is possible via kernel/lilo
parameter to disable or prevent the loading of the floppy driver?
--
Rex Dieter
Computer System Administrator
Mathematics and Statistics
University of Nebraska Lincoln
"Marc Ulrich" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> the computer hangs.
> The current computer hardware is the following:
> various IDE devices (harddrive, CDRom, Zip drive)
------------------------------
From: "Rex Dieter" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Re: Update: Install hangs computer
Date: Tue, 13 Feb 2001 11:26:13 -0600
Do you have a conventional floppy? If not, that could be it.
I've had installs on machines with LS-120's or zip's only stall because the
floppy driver hangs the boot process. One several occasions, disabling the
floppy interface altogether in the machine's bios helped. On one occasion,
however, this did NOT help.
So maybe you could try peeking around in the system bios for a similar
disable option for the floppy interface.
p.s. For posterity: Does anyone know if it is possible via kernel/lilo
parameter to disable or prevent the loading of the floppy driver?
--
Rex Dieter
Computer System Administrator
Mathematics and Statistics
University of Nebraska Lincoln
------------------------------
From: Rob Clive <[EMAIL PROTECTED]>
Crossposted-To: uk.comp.os.linux
Subject: Re: Tape drive for Linux
Date: Tue, 13 Feb 2001 14:57:21 GMT
On Fri, 09 Feb 2001 00:00:06 GMT, John-Paul Stewart <[EMAIL PROTECTED]> wrote:
>
> HP and Seagate both make ATAPI Travan drives. They DO NOT
> use ftape. You compile the kernel to support ide-tape (or
> alternatively ide-scsi and scsi tape support). The drives
> are much cheaper than DDS, but the tape much more
> expensive. I'm using a Seagate 20GB drive (Travan TR-5,
> 10GB native, 20GB with 2:1 compression). I know they used
> to have a 4/8GB model, too. They're slow but work well.
What software are you using to drive them? I'm using an HP
(really Colorado) 5Gb with ide-tape but it seems to need a
small backup on the tape to start with which it can c*ck up.
The next (real) backup then works OK. It also seems quite
frequently to suffer a DSC timeout. All in all I was
considering swapping it until your article suggested all could
be well. BTW the current backup s/w is KBackup but I've tried
Taper with much the same results. Amanda seems a bit of
overkill for a single server system. Recommendations wanted :-)
Rob Clive
Cirencester, Glos. UK
Take out the rubbish if you want to reply. Now read on....
------------------------------
From: Markus Kossmann <[EMAIL PROTECTED]>
Subject: Re: ide-scsi on ata 100 hd, safe ???
Date: Tue, 13 Feb 2001 18:44:57 +0100
roel wrote:
>
> Hello
>
> Trying to boot direct from ata 100 disk, will not work because lilo will
> only go to hda and not to hde.
> What if I put in lilo append="hde=ide-scsi".
> My gues is Linux will see the ide disk as scsi and therefore lilo will
> write to the mbr of sda.
You will break your disk access, when you are doing this. Only ATAPI
devices will work with the ide-scsi driver, but not disks, which speak
the ATA protocol.
Try an entry
disk=/dev/hde
bios = 0x80
in your lilo.conf instead
--
Markus Kossmann
[EMAIL PROTECTED]
------------------------------
From: "Steve Wolfe" <[EMAIL PROTECTED]>
Subject: AMI Megaraid
Date: Tue, 13 Feb 2001 11:23:22 -0700
Well, Google seems to have screwed up deja's stuff, so I couldn't find
anything. I have two machines, with AMI MegaRaid cards in them. Different
models, one's a 467 2-channel, one's a... well, I don't have the number
handy. : )
The cards will, if the machine has been idle for quite some time, lock
things up. Sometimes the screen is still black and the machine is locked up
solid (hitting ctrl-alt-delete doesn't do anything, and neither does the
power button.) Sometimes, I'll get "locked mailbox" repeated over and over.
Sometimes I just get kernel messages. Each time, though, it's related to
the RAID cards. Now, I've tried three different cards, all of them have
done it, leading me to believe that it's not the cards themselves. I've
tried the drivers from kernels 2.2.14 to 2.4.1. Some seem to work better
than others, but not wonderfully. Increasing the timeout values in
/drivers/scsi/sd.c seems to help a fair amount, but not get rid of the
problem.
Any clue what could be going on? In each machine, the drives are 9 gig
Quantum Atlas (IV?) drives. In one, they're attached to a dual-channel
hot-swappable backplane, in the other machine they're wired straight to the
RAID card.
I'm about to the end of my wits. I convinced the boss to order a new
Mylex card, but the money isn't there to replace the card in the second
machine. There has to be something I'm overlooking.
steve
--
==================
domain for replies is "codon"
------------------------------
From: Jonathan DeSena <[EMAIL PROTECTED]>
Subject: Re: devfs and IDE ATAPI floppy (problem solved)
Date: Tue, 13 Feb 2001 13:38:30 -0500
Paul Bristow wrote:
> Jonathon,
>
> I am working on true devfs support for the IDE-FLOPPY driver, if you are
> willing to test some stuff with me it would help.
>
Sure, I'd be glad to. Just email me.
By the way, upon the latest reboot the trick of reloading the module does
not seem to work. I'll keep trying, maybe I'll figure out what made it
work before.
JTD
------------------------------
From: Holger Thiele <[EMAIL PROTECTED]>
Subject: hauppauge wintv under 2.4.0 without sound?
Date: Tue, 13 Feb 2001 20:24:02 +0100
Hi,
I have an older hauppauge wintv card (with stereo and radio part). Under
2.2.13 everything(!) worked fine.
Now, under 2.4.0, _almost_ evryathing works - but without sound!
I don't really understand this :-)
The card is iirc a "wintv", PCI, BT848 chipset (with radio/stereo) and
MSP3400 chip. Tuner is a philips. In the
modules.conf I have the following entries:
options bttv radio=1
post-install bttv /sbin/modprobe "-k" "tuner"
post-remove bttv /sbin/modprobe "-r" "tuner"
above tuner msp3400
options tuner type=5
The tv card is attached to the linein-port of a SBLive. The mixer is ok,
and if I attached another sound source, I can hear it.
The following entries are from syslog:
Feb 11 21:57:09 moonglow modprobe: modprobe: Can't locate module
sound-slot-1
Feb 11 21:57:09 moonglow modprobe: modprobe: Can't locate module
sound-service-1
[also for 2 and 3. Is that a problem?]
Feb 11 21:57:09 moonglow kernel: Linux video capture interface: v1.00
Feb 11 21:57:09 moonglow kernel: i2c-core.o: i2c core module
Feb 11 21:57:09 moonglow kernel: i2c-algo-bit.o: i2c bit algorithm
module
Feb 11 21:57:09 moonglow kernel: bttv: driver version 0.7.50 loaded
Feb 11 21:57:09 moonglow kernel: bttv: using 2 buffers with 2080k (4160k
total)
for capture
Feb 11 21:57:09 moonglow kernel: bttv: Bt8xx card found (0).
Feb 11 21:57:09 moonglow kernel: bttv0: Bt848 (rev 18) at 00:0b.0, irq:
9, latency: 64, memory: 0xeedff000
Feb 11 21:57:09 moonglow kernel: bttv0: model: BT848A( *** UNKNOWN *** )
[autodetected]
Feb 11 21:57:09 moonglow kernel: i2c-core.o: adapter bt848 #0 registered
as adapter 0.
Feb 11 21:57:09 moonglow kernel: bttv0: i2c: checking for MSP34xx @
0x80... found
Feb 11 21:57:09 moonglow kernel: i2c-core.o: driver i2c msp3400 driver
registered.
Feb 11 21:57:09 moonglow kernel: msp34xx: init: chip=MSP3400C-C6
Feb 11 21:57:09 moonglow kernel: msp3400: daemon started
Feb 11 21:57:09 moonglow kernel: bttv0: i2c attach [MSP3400C-C6]
Feb 11 21:57:09 moonglow kernel: i2c-core.o: client [MSP3400C-C6]
registered to
adapter [bt848 #0](pos. 0).
Feb 11 21:57:09 moonglow kernel: bttv0: i2c: checking for TDA9875 @
0xb0... not
found
Feb 11 21:57:09 moonglow kernel: bttv0: i2c: checking for TDA7432 @
0x8a... not
found
Feb 11 21:57:09 moonglow kernel: i2c-core.o: driver i2c TV tuner driver
registered.
Feb 11 21:57:09 moonglow kernel: tuner: chip found @ 0x61
Feb 11 21:57:09 moonglow kernel: bttv0: i2c attach [Philips PAL]
Feb 11 21:57:09 moonglow kernel: i2c-core.o: client [Philips PAL]
registered to
adapter [bt848 #0](pos. 1).
I don't really find the problem. Maybe someone can give me a hint?
Thanks in advance,
Holger
--
Holger Thiele, <[EMAIL PROTECTED]>
------------------------------
From: [EMAIL PROTECTED] (Jim Newton)
Subject: Re: a cordless logitech wheelmouse
Date: Tue, 13 Feb 2001 19:28:40 +0000
Reply-To: [EMAIL PROTECTED]
On Tue, 13 Feb 2001 12:27:46 GMT, Jeroen de Graaf <[EMAIL PROTECTED]> wrote:
>Hi,
>
>Im having a cordless.... but after all the things people told me to the
>wheel is still not working, ive dloaded the program IMWheel but that didnt
>work.
>With SaX i added some lines to "pointer" but it will still not work. Please
>give me some advice.
>
>Jeroen.
>(SuSE 7.0/kernel 2.2.16/KDE 2.0, etc.)
I have a cordless logitech trackman, which is going to be at least similar
I reckon. I use KDE2 and imwheel appears to be working as part of that. The
relevant part of my X config is:
Section "InputDevice"
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/mouse"
Option "Buttons" "5"
Option "ZAxisMapping" "4 5"
EndSection
If I can help further then let me know.
Jim Newton
------------------------------
Subject: Re: Linux on MPC860: OK? Or asking for trouble?
From: [EMAIL PROTECTED] (Josh Stern)
Date: 13 Feb 2001 19:57:15 GMT
In article <[EMAIL PROTECTED]>,
Pete Wilson <[EMAIL PROTECTED]> wrote:
>We're making a commercial, highly-available embedded system
>from scratch. We're going to install Linux as the real-time
>OS on the main board. We're now choosing the CPU to put on
>that board. The obvious choice is an x86-class machine. But
>we prefer to use a Power PC: an MPC860.
>
>We have ZERO Linux internals experience. We have Red Hat
>Release 7 running on one single PC, and that's it.
>
>Question 1: Are there readily-available, supported incarnations
>of Linux already installed on the MPC860? If not, then how
>much trouble are we getting ourselves into by undertaking to
>do this installation from scratch? Is it suicide? Or is it
>pretty straightforward?
I suggest you look at Debian, http:/www.debian.org
The same distribution runs on x86, PowerPC, Motorola 680x, ARM,
Sparc, etc.
-= Josh
------------------------------
** 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
******************************
