Linux-Hardware Digest #564, Volume #10 Wed, 23 Jun 99 10:13:34 EDT
Contents:
Re: Best sound card for use w/ Linux? (Jeremiah)
Re: Best sound card for use w/ Linux? (David Fox)
Compatible Modems for Linux (Earl Beck)
CD-R and linux (Tero Niemi)
Re: [HELP] Urgent : problem with two SCSI controlers..... (John Munoz)
Compaq proliant 400 dead keyboard (Kostis Mentzelos)
SuSE 6.1 vs RH 5.2 ("Kyle Hittle")
Cable modem not working... (compe)
Re: Organizer to Linux? (killbill)
Re: FIC VA503+ with AMD K62-400 and 66MHz Memory. DO THEY WORK TOGETHER? (Fulton B.
Gonzalez)
Re: Linux Backup Solution. (killbill)
----------------------------------------------------------------------------
Reply-To: [EMAIL PROTECTED]
From: [EMAIL PROTECTED] (Jeremiah)
Subject: Re: Best sound card for use w/ Linux?
Crossposted-To: alt.os.linux,comp.os.linux.misc
Date: Fri, 18 Jun 1999 06:26:34 GMT
In article <7kcdqo$erp$[EMAIL PROTECTED]>,
[EMAIL PROTECTED] (Deryk Barker) spake thusly:
> Anyone recommend a card with decent sounding *input* facilities too?
Check out the following reports at PCVATech:
http://www.pcavtech.com/soundcards/reports/index.htm
Of these, the real standout on a decent-sounding-input-facilities-to-price
basis is the (original) Ensoniq 1370. I picked up an OEM one for
about $20. I haven't yet had the occasion to use it for recoding, but
I hope to soon.
As for Linux support, it's supported by ALSA, and by OSS/Free.
There are drivers for it in the 2.2.x series of kernels. I'm using
ALSA because the drivers that came with RH5.2 aren't particularly
good.
Brian
--
email to bmeloon1 at twcny dot rr dot com. evilquaker is a spam collector.
------------------------------
Crossposted-To: alt.os.linux,comp.os.linux.misc
Subject: Re: Best sound card for use w/ Linux?
From: d s f o x @ c o g s c i . u c s d . e d u (David Fox)
Date: 17 Jun 1999 23:24:01 -0700
[EMAIL PROTECTED] (Deryk Barker) writes:
> David Fox ([EMAIL PROTECTED]) wrote:
> : [EMAIL PROTECTED] (Donovan Rebbechi) writes:
> :
> : > On Wed, 16 Jun 1999 04:49:03 GMT, Gravot wrote:
> : > >prefaced with a "win"? I am especially curious about sound cards. Is
> : > >there any one card that is more suitable than the rest? If so, what is
> : > >the reasoning? Any favorites?
> : >
> : > Creative labs ISA cards are a snap to set up on linux. And you get to put a
> : > useless ISA slot to use (-;
> :
> : But they don't sound particularly good (music-wise) if that is
> : something you are concerned about.
>
> I'm glad you mention that, because I'm looking to get a sound card
> that will allow me to digitize analogue signals (e.e. tapes) so that I
> can put them onto CD.
>
> Anyone recommend a card with decent sounding *input* facilities too?
I use the Turtle Beach Fiji, which sounds great and works quite well
once you get the jumpers right, the firmware file in the right place
(/etc/sound) and the right entry in /etc/conf.modules. There are
reviews at http://www.pcavtech.com/soundcards/.
--
David Fox http://hci.ucsd.edu/dsf xoF divaD
UCSD HCI Lab baL ICH DSCU
------------------------------
Date: Wed, 23 Jun 1999 01:02:14 -0500
From: Earl Beck <[EMAIL PROTECTED]>
Subject: Compatible Modems for Linux
Am wondering if anyone can recomend a not too expensive modem for Linux.
I have a WinModem (even though its not officially) that will not work
due to hardware controllers. Any help is appreciated.
------------------------------
From: Tero Niemi <[EMAIL PROTECTED]>
Subject: CD-R and linux
Date: Wed, 23 Jun 1999 10:13:48 +0300
How to setup a burning... eh.. writing cd-rom in RH6.0?
It works just fine if I try to read but not when I want to write. I've
tried to change it through fstab writable,
but that of course didn't help. I have mitsumi 8x/4x
------------------------------
From: John Munoz <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux,comp.os.linux.help
Subject: Re: [HELP] Urgent : problem with two SCSI controlers.....
Date: Wed, 23 Jun 1999 00:28:52 -0600
> > So my question is :
> >
> > How can I have the 2 controlers, 14 readers working well? have i to
> > upgrade kernel to 2.2 as some people said to me ?
I have a similar problem. I've followed this thread, read the
scsi-howto and scsi-programming-howto, to no avail. I have 9 scsi
drives, 3 are scsi II (with ids 1-4) and 6 uw scsi drives. id0 is uw,
and id's 8-12 are uw also. I also have narrow devices at 5 and 6 (cd and
tape). in /dev/ there are 8 devices, so I make a /dev/sdi device.
There is a big difference between what dmesg shows and what fdisk or
cfdisk show! the mknod /dev/sdi 8 144 command seems to create a device
that loops around, re-using sdd or something. I have no need for 10
logical partitions. Is there any way to make each device use less than
16 of the precious major minor bits so that I can have more than 8
devices (16 addresses x 8 devices = 128 ). What I want is 8 addresses x
16 devices). Anyone know how to make this work? I tried hacking
MAKEDEV, but screwed things up pretty well.
Ive set all drives on second channel to 20 mbps. When I boot, I see
this:
(its all messed up.)
dmesg shows:
scsi0 : BusLogic BT-952
scsi1 : BusLogic BT-952
scsi : 2 hosts.
Vendor: SEAGATE Model: ST32171W Rev: 0338
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
Vendor: SEAGATE Model: ST32550W SUN2.1G Rev: 0418
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdb at scsi0, channel 0, id 1, lun 0
Vendor: SEAGATE Model: ST32550W SUN2.1G Rev: 0418
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdc at scsi0, channel 0, id 2, lun 0
Vendor: SEAGATE Model: ST32550W SUN2.1G Rev: 0418
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdd at scsi0, channel 0, id 3, lun 0
Vendor: COMPAQ Model: CD-ROM CR-503BCQ Rev: 1.1c
Type: CD-ROM ANSI SCSI revision: 02
Detected scsi CD-ROM sr0 at scsi0, channel 0, id 5, lun 0
Vendor: ARCHIVE Model: Python 25501-XXX Rev: 5.72
Type: Sequential-Access ANSI SCSI revision: 02
Vendor: HITACHI Model: DK319H-18WC Rev: AKAJ
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sde at scsi1, channel 0, id 8, lun 0
Vendor: HITACHI Model: DK319H-18WC Rev: AKAJ
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdf at scsi1, channel 0, id 9, lun 0
Vendor: HITACHI Model: DK319H-18WC Rev: AKAJ
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdg at scsi1, channel 0, id 10, lun 0
Vendor: HITACHI Model: DK319H-18WC Rev: AKAJ
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdh at scsi1, channel 0, id 11, lun 0
Vendor: HITACHI Model: DK319H-18WC Rev: AKAJ
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdi at scsi1, channel 0, id 12, lun 0
scsi0: Target 0: Queue Depth 28, Wide Synchronous at 40.0 MB/sec, offset
15
scsi0: Target 1: Queue Depth 28, Wide Synchronous at 20.0 MB/sec, offset
15
scsi0: Target 2: Queue Depth 28, Wide Synchronous at 20.0 MB/sec, offset
15
scsi0: Target 3: Queue Depth 28, Wide Synchronous at 20.0 MB/sec, offset
15
scsi0: Target 5: Queue Depth 3, Asynchronous
scsi0: Target 6: Queue Depth 3, Synchronous at 6.67 MB/sec, offset 15
scsi1: Target 8: Queue Depth 28, Wide Synchronous at 20.0 MB/sec, offset
15
scsi1: Target 9: Queue Depth 28, Wide Synchronous at 20.0 MB/sec, offset
15
scsi1: Target 10: Queue Depth 28, Wide Synchronous at 20.0 MB/sec,
offset 15
scsi1: Target 11: Queue Depth 28, Wide Synchronous at 20.0 MB/sec,
offset 15
scsi1: Target 12: Queue Depth 28, Wide Synchronous at 20.0 MB/sec,
offset 15
SCSI device sda: hdwr sector= 512 bytes. Sectors= 4222640 [2061 MB] [2.1
GB]
sda: sda1 sda2 sda3 sda4
SCSI device sdb: hdwr sector= 512 bytes. Sectors= 4194995 [2048 MB] [2.0
GB]
sdb: sdb1
SCSI device sdc: hdwr sector= 512 bytes. Sectors= 4194995 [2048 MB] [2.0
GB]
sdc: sdc1
SCSI device sdd: hdwr sector= 512 bytes. Sectors= 4194995 [2048 MB] [2.0
GB]
sdd: sdd1
SCSI device sde: hdwr sector= 512 bytes. Sectors= 35970860 [17563 MB]
[17.6 GB]
sde: sde1 sde2
SCSI device sdf: hdwr sector= 512 bytes. Sectors= 35970860 [17563 MB]
[17.6 GB]
sdf: sdf1 sdf2
SCSI device sdg: hdwr sector= 512 bytes. Sectors= 35970860 [17563 MB]
[17.6 GB]
sdg: sdg1 sdg2
SCSI device sdh: hdwr sector= 512 bytes. Sectors= 35970860 [17563 MB]
[17.6 GB]
sdh: sdh1 sdh2 sdh3 sdh4
SCSI device sdi: hdwr sector= 512 bytes. Sectors= 35970860 [17563 MB]
[17.6 GB]
sdi: sdi1 sdi2 sdi3 sdi4
if i do a fdisk -l sd[a,b,c,d,e,f,g,h,i] > file.txt, its all messed up
too. There should be 9 consecutive drive letters, instead i see:
Disk /dev/sda: 255 heads, 63 sectors, 262 cylinders
Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System
/dev/sda1 1 90 722893+ 83 Linux native
/dev/sda2 91 106 128520 82 Linux swap
/dev/sda3 107 196 722925 83 Linux native
/dev/sda4 197 262 530145 83 Linux native
Disk /dev/sdc: 255 heads, 63 sectors, 261 cylinders
Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System
/dev/sdc1 1 261 2096451 6 DOS 16-bit >=32M
Disk /dev/sde: 255 heads, 63 sectors, 261 cylinders
Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System
/dev/sde1 1 261 2096451 6 DOS 16-bit >=32M
Disk /dev/sdg: 255 heads, 63 sectors, 261 cylinders
Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System
/dev/sdg1 1 261 2096451 83 Linux native
Disk /dev/sdh: 255 heads, 63 sectors, 2239 cylinders
Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System
/dev/sdh1 1 574 4610623+ 83 Linux native
/dev/sdh2 575 1148 4610655 83 Linux native
/dev/sdh3 1149 1722 4610655 83 Linux native
/dev/sdh4 1723 2239 4152802+ 83 Linux native
Disk /dev/sdi: 255 heads, 63 sectors, 2239 cylinders
Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System
/dev/sdi1 1 574 4610623+ 83 Linux native
/dev/sdi2 575 1148 4610655 83 Linux native
/dev/sdi3 1149 1722 4610655 83 Linux native
/dev/sdi4 1723 2239 4152802+ 83 Linux native
A direct reply to my address would be greatly appreciated... May miss
the post replies. Thanks...
------------------------------
From: Kostis Mentzelos <[EMAIL PROTECTED]>
Subject: Compaq proliant 400 dead keyboard
Date: Wed, 23 Jun 1999 15:54:54 +0300
Hi all,
I have installed linux my compaq proliant 400 and there is a problem:
there are a possibility (30%) the keyboard will be dead after reboot.
I am using SUSE linux 5.3 with kernel 2.0.35 or 2.0.36
The keyboard will work again after one or two reboots. Everything else
is working fine.
Kostis Mentzelos.
------------------------------
From: "Kyle Hittle" <[EMAIL PROTECTED]>
Subject: SuSE 6.1 vs RH 5.2
Date: Wed, 23 Jun 1999 15:20:43 -0400
i recently obtained a copy of SuSE LiNUX 6.1 and i was previously using RH
5.2. i can't seem to get anything working in SuSE and was wondering about
some opinions of both, which would be better suited to my needs? i am using
LiNUX as a web host for varios domains and i also have a home system.
Any Opiions Would Be Nice
kyle
------------------------------
From: compe <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc,comp.os.linux.networking
Subject: Cable modem not working...
Date: 23 Jun 1999 07:30:54 GMT
I have slackware 4.0 installed on my system and I cannot get my cable modem
to work. To start off www.bresnanlink.net is my ISP, it does not require
authentication, etc. like rr. I have 2 , that's right, 2 NIC's in my
computer, due to it being a gateway machine on my network. The first, eth0
is for the LAN, and the second, eth1 is for the cable modem. It has
successfully worked under Windows95/98/NT4.0 and even Windows NT5 (2000)
beta 3, build 2045. It has ALSO worked under Redhat 6.0. However, it
doesn't want to work under Slackware 4.0. I have been at this 3 days now,
read all the how-to's, faq's, manpages, have been on IRC the entire time,
and unfortunatley, NOBODY can tell me what's going on. I have recompiled my
kernel, included the necessary support for it, both of my NICs are detected
upon bootup, ifconfig -a shows lo, eth0, and eth1.. my LAN NIC works fine,
I can ping the other computer on the network without a problem, but when I
dhcpcd eth1, it timed out and in the /var/log/syslog it says:
"timed out waiting for a valid dhcp server response."
All of my resolv.conf, hosts.conf, rc.d/* is all fine (I am pretty sure). I
have also tried compiling a newer version fo dhcpcd, however, it requires
net/ethernet.h and I imagine other header files, which are glibc. Slackware
4.0 as you know is libc5, and upon installing the glibc package, slackware
dies on me, and the only way I can reboot my computer is pulling the plug.
My cards are LinkSys 10/100 PCI cards, no problems with either of them as
well. I have also tried switching the cables around, aka eth0 is cable
modem, eth1 is lan. The lan still worked, but nope, cable modem didn't.
LINUX is LINUX, and I'm certian if it will work under redhat, it WILL work
under Slackware. I just need to find out HOW. Also another strange feature,
if I ifconfig eth1 208.154.20.222 (the IP address I'm normally leased) I
can ping my nameserver, 208.154.20.1, but I cannot ping any foreign IP
addreses, nor resolve any text hostnames, such as, say www.lycos.com. I
really can't figure out what's going on here, I've even went and tried
using 'pump' which someone said to use, unfortunatley it only is available
in rpm format, so I installed alien, extracted it, then it wouldn't run.
Another problem on the list. ANY HELP is extremely appriciated, I haven't
slept in days, and still have found no answers. Thanks.
================== Posted via SearchLinux ==================
http://www.searchlinux.com
------------------------------
From: killbill <[EMAIL PROTECTED]>
Subject: Re: Organizer to Linux?
Date: Wed, 23 Jun 1999 12:57:38 GMT
In article <[EMAIL PROTECTED]>,
"Eric Wick" <[EMAIL PROTECTED]> wrote:
> Hello,
>
> is there a organizer that works very well with Linux? Meant the data
> exchange to a linux box over IRDA or Serial or whatelse.
>
> Just read a test and always see "win95 requiered" :-(
>
I have been using my Palm Pilot (now 3com) with Linux (and HP-UX) as
well as windows for about 3 years now with great success. It uses the
serial port. I would recommend the Palm IIIx as the unit with the most
bang for the buck, although at about $169 the Palm III is an awful nice
system if you are on a tight budget.
The pilot-link tools allow you to move files back and forth between Unix
and the Pilot, and allow such things as image backups and restores of
your pilot. They work great, and have never failed me... for backup and
restore, they are actually MORE usefull then the windows and mac tools.
There are also packages that synchronize with various information
managers with Unix, but I have not tried those. I have not seen that
much benefit to having a desktop information manager when I always have
the pilot strapped to my hip anyway.
The Palm Pilot Professionals and above (III, IIIx, IV, VII) also come
with built in support for dial up ppp tcp/ip networking, so with the
addition of a nice little portable clip on modem ($79), you can dial up
a properly configured unix system (i.e. your ISP) and use it to
send/receive email, or, for the hopelessly geeky, even run telnet on a
vt100 emulator running on the pilot.
You have not lived until you have seen an emacs session up on your Palm
Pilot :)
--
Bil Kilgallon ([EMAIL PROTECTED])
--"I believe, what I believe, has made me what I am. I did not make
it, It is making me, it is the very truth of God, not the invention
of any man". Rich Mullins, quoting G.K. Chesterton.
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
------------------------------
From: Fulton B. Gonzalez <[EMAIL PROTECTED]>
Crossposted-To: alt.comp.periphs.mainboard.fic
Subject: Re: FIC VA503+ with AMD K62-400 and 66MHz Memory. DO THEY WORK TOGETHER?
Date: Wed, 23 Jun 1999 09:47:25 -0400
On Tue, 22 Jun 1999, Len wrote:
>Larry Mintz wrote:
>>
>> : So it works for 300 and 400 but not 350 and I assume 450???
>> : It seems like it only works for even (3x,4x,etc) multipliers.
>> : Is that your conclusion as well.
>>
>> Not true. My VA-503+ supports the 3.5x multiplier as well. There are others
>> listed in the manual. So I am running a 350MHz unit with the 100MHz bus and
>> a 3.5 multiplier to yield 350MHz.
>
>I know it supports a 3.5x and 4.5x multiplier. I was asking if it
>worked with EDO or FPM memory running at AGP frequency with those
>multipliers. The other poster suggested that it only worked at
>even multipliers like 3x and 4x with the non-PC100 memory.
>
>Well, you could answer the question depending on what memory you have.
>Do you have PC100 or older EDO or FPM and are you running it at front
>side bus or AGP frequency?
I had the exact same motherboard/cpu combo with EDO SIMMs. I often got memory
errors or crashes running Linux at 100Mhz bus (100x4); in exasperation I bought
PC100 SDRAM (cheap nowadays), and my system's been crash-free since.
Fulton B. Gonzalez
------------------------------
From: killbill <[EMAIL PROTECTED]>
Subject: Re: Linux Backup Solution.
Date: Wed, 23 Jun 1999 13:11:24 GMT
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] wrote:
> In article <7k8c6b$ljn$[EMAIL PROTECTED]>, killbill wrote:
>
> >I don't understand why the multi-volume option and the compress
option
> >are mutually exclusive...
>
> Well, to put it simply, tar if used with compression will compress
> a media's worth of data and then write it. I first noticed this
> long ago when attempting to back up to floppies. I, of course, wished
> to save on the # of floppies needed, and at first glance it looked
> like tar w/compression and w/multi-volume would be enough to do the
> job. But it isn't, and it's because tar doesn't know how much space
> is *really* available and usable if it were to do compression. The
> compression is essentially done as a separate process, and tar just
> knows that floppies can hold 1.4 megs of data.
>
> It's not that the two options are necessarily compatible, but if you
> use them it won't buy you anything. tar will happily compress a
> floppies worth of data, write it, and then ask you for the next
> disk. Meanwhile, much of the disk is unused, and you end up using
> the same number of disks either way.
>
> >As a response to that problem, I wrote a GPL package called
backburner
> >(see www.freshmeat.net) that will chop up, fixate, and recombine
> >streams. It is a pretty simple collection of Perl scripts, that
could
>
> Which probably addresses the issue. The key thing here is that you
> need to compress, and then watch the size of your compressed file, and
> when it approaches your limit (e.g., 1.4 meg for a floppy) you stop
the
> compression and write the chunk out to floppy.
>
> >Bil Kilgallon ([EMAIL PROTECTED])
>
> --
>
========================================================================
> David E. Fox Tax Thanks for letting me
> [EMAIL PROTECTED] the change magnetic patterns
> [EMAIL PROTECTED] churches on your hard disk.
>
=======================================================================
>
Thanks for the clarification, although this still sounds like a bug (or
at best an obvious but unimplemented feature) in tar, which of course
knows how much data it has sent out, as it is doing the compression
internally.
On my red hat 5.2 system, tar would actually die if you indicated you
wished both multivolume and compress at the same time. This was
probably the easiest (although least usefull) solution to the bug you
describe.
--
Bil Kilgallon ([EMAIL PROTECTED])
--"I believe, what I believe, has made me what I am. I did not make
it, It is making me, it is the very truth of God, not the invention
of any man". Rich Mullins, quoting G.K. Chesterton.
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
------------------------------
** 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
******************************
