Linux-Hardware Digest #497, Volume #14 Sun, 18 Mar 01 04:13:13 EST
Contents:
Re: Support for Dell PowerEdge RAID controllers? (Dances With Crows)
Re: Logitech Wheel Mouse ([EMAIL PROTECTED])
Re: serial/parallel port card (Dances With Crows)
Re: Adaptec 2940UW with Suse 7.0 (Markus Kossmann)
Re: Adaptec 2940UW with Suse 7.0 ("Tim Cuthbertson")
Need help getting modem to work ("jpm27")
Re: Adaptec 2940UW with Suse 7.0 (Anthony Schlemmer)
Re: modem not up (kernel 2.4 and PPP) (Martigan)
Re: cdrecord fails for audio data (Martigan)
Re: Logitech Wheel Mouse (James Tappin)
Re: Should I abandon SCSI? ("Ron Reaugh")
Re: Re: IDE RAID5 card ( (Joel Fowler)
Re: Re: RAID on Linux: What type of hardware to choose (Joel Fowler)
Re: IDE RAID cards (Joel Fowler)
essosolo - mask bit stuck (Zebee Johnstone)
adaptec 19160 ("Peter T. Breuer")
Can not reboot on Compaq Deskpro 4000 ("paulk93")
----------------------------------------------------------------------------
From: [EMAIL PROTECTED] (Dances With Crows)
Subject: Re: Support for Dell PowerEdge RAID controllers?
Date: 18 Mar 2001 05:17:04 GMT
Reply-To: [EMAIL PROTECTED]
On Sat, 17 Mar 2001 20:37:14 -0500, Rinaldi J. Montessi staggered into
the Black Sun and said:
>Dances With Crows wrote:
>> I don't know where this module is on the SuSE CD-ROMs, but once you've
>> booted the CD-ROM, you could try Ctrl-Alt-Fing over to another virtual
>> console and doing a "modprobe megaraid"... if that doesn't work, pop in
>> the Modules floppy, mount it, copy the scsi-mod.gz file to somewhere,
>> gunzip it, mount that file (sigh), and you'll find megaraid.o in there.
>
>Pardon my eavesdropping, but what does mounting the file accomplish that
>tar -zxvf foo.tar.gz wouldn't?
The .gz is a Minix filesystem image, and as such contains not just the
modules, but a bunch of filesystem information. It's *NOT* a tar
archive; tar says "hmm, this doesn't seem to be a tar file". Hence the
fiddling with mount. I don't know why they decided to do it this way--
probably so the whole thing could be loaded into a RAMdisk with a
minimum of hassle.
--
Matt G|There is no Darkness in Eternity/But only Light too dim for us to see
Brainbench MVP for Linux Admin / Workin' in a code mine, hittin' Ctrl-Alt
http://www.brainbench.com / Workin' in a code mine, whoops!
=============================/ I hit a seg fault....
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: Logitech Wheel Mouse
Date: Sun, 18 Mar 2001 05:20:56 GMT
[EMAIL PROTECTED] wrote:
> Grumble - Logitech - Grumble... There was a discussion about this
> particular issue here quite some time ago...
> For some reason, logitech created the "same" mouse with different
> internals. One of their most popular models (generic PS/2 wheel)
> was made available in many different flavors - Logitech branded,
> Logirech Bulk, and OEM branded. Apparently, only the Logitech
> branded and some of the bulk mice would actually work - all
> of the OEM (AFAIK) were such that they would not work with
> imwheel... Now, this was about 6 mo ago, I wonder if anybody
> has any further info on this... (I have a Compaq branded Logitech
> wheel mouse... Guess what - it doesn't work with the wheel either.)
**** UPDATE *****
Well, I decided to do some digging... If you have a Logitech S-48
mouse (from bottom of mouse) this was the case as described above.
However - a new version of IMWHEEL is available that fixes this
problem (according to the CHANGES - I have not tried this yet.)
What you need is Imwheel 0.9.9, this is supposed to add support
for this bane of society... :-) I know I will be a happy
camper if this actually works! (Unfortunately, won't probably
have a chance to install till Monday - my wife uses the machine
for Windows....)
Anyway, as usual, YMMV...
GL!
kris
------------------------------
From: [EMAIL PROTECTED] (Dances With Crows)
Subject: Re: serial/parallel port card
Date: 18 Mar 2001 05:25:36 GMT
Reply-To: [EMAIL PROTECTED]
On Sat, 17 Mar 2001 22:09:53 -0500, B'ichela staggered into the Black
Sun and said:
>On Sat, 17 Mar 2001 21:51:13 GMT, Cokey de Percin <[EMAIL PROTECTED]>
>wrote:
>>'The lp0 on fire message simply means that the kernel can't figure out
>>the printer status. The fire bit is an old joke.'
>>I've seen this when the printer was on, but 'paused' or off-line.
> Umm would you mind telling me the "joke"? I too have seen this
>when the printer off-line button is activated.
Certain old HP Laserjet III models could catch fire if a paper jam
occurred in the right spot. The "lp0 on fire" thing may be a reference
to this behavior, or it might just be the driver writer was trying to
perpetrate a silly joke, similar to the "All Your Base..." idiocy that
even the mainstream media noticed.
--
Matt G|There is no Darkness in Eternity/But only Light too dim for us to see
Brainbench MVP for Linux Admin / Workin' in a code mine, hittin' Ctrl-Alt
http://www.brainbench.com / Workin' in a code mine, whoops!
=============================/ I hit a seg fault....
------------------------------
From: Markus Kossmann <[EMAIL PROTECTED]>
Subject: Re: Adaptec 2940UW with Suse 7.0
Date: Sun, 18 Mar 2001 05:34:34 +0100
Tim Cuthbertson wrote:
>
> I have been fighting this problem for two weeks. It took me a couple of days
> to find all the SCSI parameters and workarounds I needed to install Suse 7.0
> with my Adaptec 2940UW. But for the past two weeks I have been trying to
> figure out how to boot my installation. Linux is installed on my second SCSI
> hard drive, which Win98 calls D: and Linux calls /dev/sda. Win98 is
> installed on the first SCSI drive (C: to Windows, /dev/sdb to Linux). The
> CDROM drive is also a SCSI device
>
> Last night, I finally came up with a boot floppy that almost works. It loads
> the SCSI driver and detects the host adapter, but then it gives repeated
> "Operation aborted - timeout" messages. This is exactly what it was doing
> when I was trying the initial installation, before I discovered all the
> parameters I had to send to it.
I did't have problems with my setup ( also AHA2940UW + 3 hds + CDROM)
and SuSE-7.0.
So it seems to me that you have some hardware problems. Did you test
your drive with Windows (i.e. by creating and formatting a FAT partition
on it and copying some _large_ files to it, seeing it in Windows is not
enough) ?
Did you allready check if termination and cabling is conforming to the
SCSI specs ?
The Linux SCSI driver may be more sensible to such problems.
It seems strange to me that /dev/sda is your Windows D: drive . It
should be your windows C: drive , unless you've played with the boot
order settings in the Adaptec setup.
What about SCAM ? Do you use it ? Then disable it and jumper your drives
to different SCSI ID's.
--
Markus Kossmann
[EMAIL PROTECTED]
------------------------------
From: "Tim Cuthbertson" <[EMAIL PROTECTED]>
Subject: Re: Adaptec 2940UW with Suse 7.0
Date: Sun, 18 Mar 2001 00:07:13 -0600
"Markus Kossmann" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
>
> I did't have problems with my setup ( also AHA2940UW + 3 hds + CDROM)
> and SuSE-7.0.
> So it seems to me that you have some hardware problems. Did you test
> your drive with Windows (i.e. by creating and formatting a FAT partition
> on it and copying some _large_ files to it, seeing it in Windows is not
> enough) ?
> Did you allready check if termination and cabling is conforming to the
> SCSI specs ?
> The Linux SCSI driver may be more sensible to such problems.
>
> It seems strange to me that /dev/sda is your Windows D: drive . It
> should be your windows C: drive , unless you've played with the boot
> order settings in the Adaptec setup.
> What about SCAM ? Do you use it ? Then disable it and jumper your drives
> to different SCSI ID's.
>
>
>
>
> --
> Markus Kossmann
> [EMAIL PROTECTED]
Well, I don't know about all that stuff. The hardware has been working just
fine for Win98 and BeOS for 3-1/2 years. Also, it works just fine for Suse
Linux if I boot from the CD ROM and provide the aic7xxx parameters. It
works, every time. I don't think it is a hardware problem.
I just need to know how to get it to boot in a simpler fashion (hard disk or
floppy), I don't want to go tearing in to stuff that is working.
Thanks for your advice,
Tim
------------------------------
From: "jpm27" <[EMAIL PROTECTED]>
Subject: Need help getting modem to work
Date: Sun, 18 Mar 2001 00:40:11 -0600
I have a U.S. Robotics 56k PCI Voice Modem and I'm trying to get it to run
under Linux-Mandrake 7.2. When I run HardDrake is shows that the modem has
been recognized under the modem category. But when I try to connect to my
ISP using Kppp and I try all the different com ports all I get on each one
upon trying to connect is a message that states that the modem is busy. Can
someone please tell me the steps I need to take to get the modem working so
I can connect to my ISP? Any help would be greatly appreciated.
John
------------------------------
From: Anthony Schlemmer <[EMAIL PROTECTED]>
Subject: Re: Adaptec 2940UW with Suse 7.0
Date: Sun, 18 Mar 2001 07:09:07 GMT
One thing I did when I was dual booting a system was to install LILO on the
MBR of the primary drive. I had my lilo.conf file setup so I could boot
Win9X from the primary hard drive or Linux from the second drive. You can
even setup which system you want the default to be so in case you don't
specify which partition to boot, LILO boots the default one automatically.
Tim Cuthbertson wrote:
> Anthony Schlemmer wrote:
>>
>> I've been using SuSE Linux starting with version 5.2 and this is the
>> lilo.conf file that I used. I also have a Ataptec 2940UW controller that
>> has served me well for nearly 4 years now:
>>
>> boot=/dev/sda
>> linear
>> read-only
>> prompt
>> timeout=50
>> vga = normal # force sane state
>> image = /vmlinuz
>> root = /dev/sda1
>> label = Linux
>>
>> This configuration was for my system which boots from its first SCSI
>> drive which is /dev/sda. If you're trying use the second SCSI drive then
>> that would be /dev/sdb not /dev/sda.
>>
>> I'm not a wizard with lilo but the other thing about your lilo.conf that
>> might be the culprit is that you have "boot=/dev/fd0" which is your
>> floppy drive. Are you booting from your floppy? If you're trying to boot
>> from your second SCSI drive then you should be attempting to boot from
>> your SCSI drive: "boot=/dev/sdb" instead.
>>
>> Tony
>>
>
> Tony,
>
> Thanks for your response.
>
> Yes, I am trying to boot from the floppy because my system usually boots
> to the other hard disk with Win98.
>
> I was never able to get Suse to load on my system until I found the
> aic7xx parameters in Suse's Knowledge Database. Even now, when booting
> from the Suse CD, if I leave any of those parameters off, it will not
> work.
>
> It is beginning to look like I am always going to have to boot from the
> CD.
>
> Tim
>
>
------------------------------
From: Martigan <[EMAIL PROTECTED]>
Subject: Re: modem not up (kernel 2.4 and PPP)
Date: Sun, 18 Mar 2001 07:38:37 GMT
Dances With Crows wrote:
> On Sat, 17 Mar 2001 22:03:54 GMT, Martigan staggered into the Black Sun
> and said:
> >I'm running a Dell PIII 450, 256 Meg ram, ASUS Ext ISDN.
> >With MD 7.2 2.2.17MDK it works fine, but when I upgrade to 2.4.2 it
> >doesn't. I have enabled ISDN support and enabled ppp Asnyc and all
> >compresions as mods, no luck.
>
> Have you looked in the /usr/src/linux-2.4.2/DOcumentation/Changes file
> and seen the advisory there that says "upgrade pppd to 2.4.0b1 at least,
> otherwise PPP won't work with 2.4.x kernels"? If you haven't upgraded
> your pppd, do so... if you have, then we'll probably need more
> information. HTH,
>
Yes it helps very much sorry for this, I new to linux but was looking in
the worng section i.e. I was reading the notes for ISDN only. ;-(
Thanx.
------------------------------
From: Martigan <[EMAIL PROTECTED]>
Subject: Re: cdrecord fails for audio data
Crossposted-To: comp.os.linux.misc
Date: Sun, 18 Mar 2001 07:42:08 GMT
Parminder Lehal wrote:
> Hello, I am having strange problem with cdrecord. I can write data CDs
> without any problem. But I can not write audio CDs. The problem is buffer
> underrun. When I write data CDs fifo never gets below 90% but for audio
> CDs it stays at about 5-6% and fails .... The cdrecord documentation says
> that if fifo is below certain range then it might be hardware problem. But
> then the same hardware is able to write data CDs.
>
> HELP PLEASE...............................!!!!!!!!!!!!!!!!!!
>
> Parminder
In my experience with "burn'n" when you have this problem some times
slowing the read and burn speed will help.
------------------------------
From: James Tappin <[EMAIL PROTECTED]>
Subject: Re: Logitech Wheel Mouse
Date: Sat, 17 Mar 2001 20:15:17 +0000
Konstantin Schauwecker wrote:
> Hi
> I byed a new Logitech Wheel Mouse but I can't use the mouse wheel. I had
> no problems with my forener MS Intelli Mouse. I added this line to my X11
> config file:
> Option "ZAxisMapping" "4 5"
> Does Logitech use an other protocol?
Some Logitech "Mice" use the mouseman+ protocol, try
Protocol "MouseManPlusPS/2"
Or the XF 4 equivalent. There doesn't seem to be a logical pattern to
decide (my trackman marble wheel is mm+ and my MouseManPlus Wheel optical
is an imps/2). As far as I can tell the best scheme is to try one -- if
doesn't work try the other,
James
--
James Tappin, O__ "I forget the punishment for using
[EMAIL PROTECTED] -- \/` Microsoft --- Something lingering
http://www.xena.uklinux.net/ with data loss in it I fancy"
------------------------------
From: "Ron Reaugh" <[EMAIL PROTECTED]>
Crossposted-To: comp.periphs.scsi
Subject: Re: Should I abandon SCSI?
Date: Sun, 18 Mar 2001 07:45:38 GMT
Ed Blackman wrote in message ...
>On Sat, 17 Mar 2001 01:17:05 GMT, Ron Reaugh wrote:
>>Ed Blackman wrote in message ...
>>>On Thu, 01 Mar 2001 00:09:27 GMT, Ron Reaugh wrote:
>>>>NewsReader2 <[EMAIL PROTECTED]> wrote in message ...
>>>>>Just keep to a single drive for greater reliability and stability.
>>>>>
>>>>>Choose 10K+ SCSI to improve workstation performance
>>>>
>>>>All nonsense. Nothing supplants a good backup scheme at 3:00 or at
>>>>any other time. Fast inexpensive EIDE RAID 0 plus an appropriate
>>>>backup/checkpoint scheme is just as reliable as a SCSI solution.
>>>
>>>Because a single drive failure in RAID 0 array takes down the entire
>>>array, the probability of failure of a RAID 0 array is the *sum* of the
>>>probability of failures of all of the drives in the array. So a single
>>>drive *is* more reliable than a RAID 0 array.
>>
>>That's not the issue.
>
>It might not be the only issue, but it's the one that my comments where
>directed towards. Newsreader2 said that single drives had greater
>reliability and stability. You said that his statement was nonsense.
>I showed you were wrong: it *isn't* nonsense so say that single drives
>are more reliable than a RAID 0 array.
You are a bold faced liar as anyone who reads the thread for themself can
see.
------------------------------
From: [EMAIL PROTECTED] (Joel Fowler)
Subject: Re: Re: IDE RAID5 card (
Date: Sun, 18 Mar 2001 08:01:06 +0000 (UTC)
Check out the 3Ware Escalde 6400 and 6800.
I'm using them with Raid 1 and 1+0 implementations but they recently
announced Raid 5 support.
Joel Fowler
--
Posted from adsl-63-193-246-5.dsl.snfc21.pacbell.net [63.193.246.5]
via Mailgate.ORG Server - http://www.Mailgate.ORG
------------------------------
From: [EMAIL PROTECTED] (Joel Fowler)
Subject: Re: Re: RAID on Linux: What type of hardware to choose
Date: Sun, 18 Mar 2001 08:01:06 +0000 (UTC)
You might want to check out the 3Ware Escalate 6800. It looks to Linux like
a SCSI controller but attaches less expensive IDE disks. The 6800 supports
up to 8 drives. It will support a hot spare and Raid levels 1, 1+0, and 5.
Escalate controllers are pretty easy to configure and require no
maintenance. You would normally store all drives internally in the system
enclosure.
Joel Fowler
--
Posted from adsl-63-193-246-5.dsl.snfc21.pacbell.net [63.193.246.5]
via Mailgate.ORG Server - http://www.Mailgate.ORG
------------------------------
From: [EMAIL PROTECTED] (Joel Fowler)
Subject: Re: IDE RAID cards
Date: Sun, 18 Mar 2001 08:01:07 +0000 (UTC)
I have a Linux (RH 6.0) system where I used software raid 1.
Recently, I built a second Linux (RH6.2) system. Remembering the challenges
I faced with software Raid (which included root & swap partitions), I
decided to try a hardware raid controller. After some checking I decided on
a 3Ware Alcalde 6200. It installed with no difficulty and I have had no
post install problems. It performs well. I haven't run benchmarks and don't
know which system performs best. I can tell you that I feel more confident
with the 3Ware solution as there is much less opportunity for the admin
(Me) to screw thing up.
The 6200 supports Raid 0, 1, and 1+0. The 6400 and 6800 also support a hot
spare and Raid 5.
Mime are not set as hot swap and I'm unsure wether the controller supports it.
As I recall, the cost of my 6200 was $138.
Joel Fowler
Since my experiment we have also deployed two Linux systems where I work
with 3Ware 6x00 controllers. One using Raid 1, the other using Raid 1+0.
--
Posted from adsl-63-193-246-5.dsl.snfc21.pacbell.net [63.193.246.5]
via Mailgate.ORG Server - http://www.Mailgate.ORG
------------------------------
From: [EMAIL PROTECTED] (Zebee Johnstone)
Subject: essosolo - mask bit stuck
Reply-To: [EMAIL PROTECTED]
Date: Sun, 18 Mar 2001 08:38:52 GMT
I have a motherboard with a built in sound chip, that uses the
essosolo module.
When I try and record using rec/sox, it doens't work and comes up with
tasma kernel: solo1: cannot start recording, DDMA mask bit stuck at 1
A google search revealed that this should have been fixed in a kernel
patch 15, so I upgraded to RedHat's 2.2-17 kernel, same problem.
I got the full source for 2.2.18 and compiled it, with solo support
compiled in. Still no go.
What do I try next?
What's really annoying me is that I had it working OK with my 2.12
kernel but it stopped, and damnfino why. Suddenly it started giving
this error. I don't recall changing anything but we know how reliable
that is!
Zebee
------------------------------
From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Subject: adaptec 19160
Date: Sun, 18 Mar 2001 00:03:40 +0100
I'd welcome reports of success with the adaptec 19160 card. (kernel?)
Adaptecs product pages seem to go to lengths to say that the 29160
supports unix/linux blah blah, is for mid range servers, and the
19160 supports windows and home workstations, and never the twain
shall meet.
Of course the 29160 is nearly twice the price. I don't believe it. Same
chip, surely. They both have the same socket count, the same number
of buses, etc, etc. The pix look the same.
I need it to host some scsi2 lvd ultrawide disks.
I've seen a couple of archived reports saying that things work fine in
the 2.2.18 kernel, and others quoting weird effects on boot in earlier
kernels. Fine ... I don't care where the driver fits, so long as there
is one. But the 19160 is NOT listed in the supported cards section of
the 2.4.0 adaptec driver code files.
So which is it?
Peter
------------------------------
From: "paulk93" <[EMAIL PROTECTED]>
Subject: Can not reboot on Compaq Deskpro 4000
Date: Sun, 18 Mar 2001 09:03:31 GMT
Dear linux experts,
I have installed RedHat Linux 7.0 on my Compaq Deskpro 4000 and I am having
trouble rebooting the system with "reboot" command.
When I try to reboot, it shuts down (killing all the processes), but then,
it goes into black screen and does not restart the system. Only way to
restart the system is to push the power button to power down and restart.
I also had Windows NT 4.0 installed before on the same machine and it
rebooted (Shutdown and Restart) fine without any problems. It does appear
to be Linux issue (possible related to Compaqs).
Has anyone had this problem on Compaq?
I have talked to Compaq tech support without success.
Can someone help?
Thank you
------------------------------
** 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
******************************
