Linux-Hardware Digest #667, Volume #14 Sun, 22 Apr 01 06:13:07 EDT
Contents:
Re: sound in intel810e AC97 (Warren Burke)
Re: Alcatel/Efficient SpeedStream 4060 USB DSL Modem ("Rick")
Re: Modem trouble (Keith Mastin)
Re: Where can I buy bridgeboards? (B'ichela)
Re: Where can I buy bridgeboards? ("Rob Turk")
Re: Where can I buy bridgeboards? ("Rob Turk")
Re: NICs for multi-multihomed hosts ("Vik Heyndrickx")
Re: asus a7v133 ("Vik Heyndrickx")
Re: 3 com nic ("Peter T. Breuer")
Re: Where can I buy bridgeboards? (Rick)
Re: es1371 - No Sound (Dougie Richardson)
Re: Pentium133 down for the count?? (Dougie Richardson)
Re: Modem trouble (Dougie Richardson)
----------------------------------------------------------------------------
From: Warren Burke <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux,comp.os.linux.setup
Subject: Re: sound in intel810e AC97
Date: Sun, 22 Apr 2001 03:49:15 -0400
Did you update your /etc/modules.conf (or /etc/conf.modules) file?
Read the INSTALL file that came in "alsa-driver-0.5.10b.tar", it tells
you how to properly update your /etc/modules.conf (or
/etc/conf.modules).
Alan Andrade wrote:
>
> Hi
> I have been trying to configure sound on my machine its on intel810E AC97
> codec
> i ran ./configure..make ..make install on the following file
> alsa-driver-0.5.10b.tar
> alsa-lib-0.5.10b.tar
> alsa-utils-0.5.10.tar
> then ran ./snddevices from the devices dir
> then
> modprobe snd-intel8x0 (as modprobe snd-card-intel8x0 was not working)
> then on testing by
> cat /proc/modules the following is seen
> snd-intel8x0 6288 0 (unused)
> snd-ac97-codec 23104 0 [snd-intel8x0]
> snd-mixer 27248 0 [snd-ac97-codec]
> snd-pcm 30008 0 [snd-intel8x0]
> snd-timer 8640 0 [snd-pcm]
> snd 36716 0 [snd-intel8x0 snd-ac97-codec snd-mixer
> snd-pcm snd-timer]
> soundcore 2596 0 [snd]
> agpgart 4660 1 (autoclean)
> lockd 31176 1 (autoclean)
> sunrpc 52964 1 (autoclean) [lockd]
> nls_iso8859-1 2240 3 (autoclean)
> nls_cp437 3748 3 (autoclean)
> vfat 9372 3 (autoclean)
> fat 30720 3 (autoclean) [vfat]
>
> on cat /proc/asound/cards
> --no soundcard---
> well i am not sure what to make of all this and would like to rpoceed ...do
> let me know how ..
> I had proceeded till here through the HOWTO from alsa-proj
> thanks in advance
> Alan
--
Regards,
-Warren Burke
If you pick up a starving dog and make him prosperous, he will not
bite you. This is the principal difference between a dog and a man.
-Mark Twain
"The greatest pleasure in life is doing what people say you cannot do."
-Walter Bagehot
Write the bad things that are done to you in the sand, but write the
good
things that happen to you on a piece of marble.
-Arabian wisdom
In matters of style, swim with the current; in matters of principle,
stand like a rock!
-Thomas Jefferson
If you cannot convince them, confuse them.
-Harry S Truman
"Do not follow where the path may lead. Go instead
where there is no path and leave a trail."
-George Bernard Shaw
------------------------------
From: "Rick" <[EMAIL PROTECTED]>
Subject: Re: Alcatel/Efficient SpeedStream 4060 USB DSL Modem
Date: Sun, 22 Apr 2001 04:03:52 -0400
Have seen various allusions to Alcatel driver availability, but there seems
to be no references anywhere to this BellSouth distributed modem--including
the Alcatel site. They seemingly do not acknowledge even manufacturing it!
Anyone have any insights in this regard, as I'd love to get my Linux on
line?
--
Rick
[EMAIL PROTECTED]
------------------------------
Crossposted-To: alt.linux,comp.os.linux.help,comp.os.linux.redhat,comp.os.linux.setup
From: Keith Mastin <[EMAIL PROTECTED]>
Subject: Re: Modem trouble
Date: Sun, 22 Apr 2001 08:04:21 GMT
Its a winmodem. Remove the modem. Get a hammer. Hit the modem. Hit it
again. It not a real modem. Go to the linmodem site, which has some
drivers for one or two winmodems. Mostly, I'de say that you're sol. Get a real modem,
but first check the linux_hardware_compatability_howto at linuxdoc.org.
On Mon, 16 Apr 2001, Krstanovic wrote:
>I have Rockvell 56k ISA modem.It works on IRQ#3 and COM2 port under Win Me
>and DOS,but will not work under Red Hat 7
>Help me to configure it.Without the modem Linux is not so useful,in my
>opinion :)
>Thanx!
>
>
>
--
Keith Mastin [EMAIL PROTECTED]
BeechTree Information Technology Services Inc.
137 Laird Drive M4G 3V5 Tel(416)696-6070
http://www.beechtree-its.com
------------------------------
From: B'ichela <[EMAIL PROTECTED]>
Crossposted-To: comp.periphs.scsi,comp.os.cpm,comp.sys.tandy
Subject: Re: Where can I buy bridgeboards?
Date: Sun, 22 Apr 2001 07:34:34 GMT
Reply-To: [EMAIL PROTECTED]
On Sat, 21 Apr 2001, Herbert R Johnson wrote:
> You might look over my Web site for Mac equipment. I have a number
> of small but cheap SCSI drives for Macs, but they should work
> with other old SCSI systems. My 80MB drives are $10 each plus shipping
> for instance. I happen to have some old "SCSI" external drives which
> are actually MFM drives and some kind of converter. I may not
> have these listed in my hard drive section but I have a few left
> that I'd sell if you are interested. Let me know and I can provide
> details.
Can you tell me anything about these boards? For example
manufacturer? is there a model number on them?
Related to this. does your external drives/enclosures of this
type have instruction manuals?
I may be interested in aquiring one full 80MB external drive
if/when I can spare the money.
B'ichela
------------------------------
From: "Rob Turk" <[EMAIL PROTECTED]>
Crossposted-To: comp.periphs.scsi,comp.os.cpm,comp.sys.tandy
Subject: Re: Where can I buy bridgeboards?
Date: Sun, 22 Apr 2001 10:13:19 +0200
"B'ichela" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> UPDATE!!!!
> I got it working finally. Turns out that that whoever wrote
> the acb-40XX patch set was asleep at the error detection switch ;)
Congratulations!
> I forgot one thing. What is the fake scsi Identify of a
> ACB-4070 to define the second LUN drive when/if I plug one in.
It's identical to the first. Only the response to non-existing LUN's is
different. If you see that the host is trying to talk LUN's higher than 1,
still return the Inquiry data, but make the first byte 0xFF.
> Drive 0 is used to format only right? Swap the cables on your
> drives so you can now low level drive 1 ;) Meaning make drive 1 drive
> 0.
Just build a SCSI Mode Select and Format CDB that use the SCSI-1 methode of
specifying the LUN. The upper 3 bits of the second byte in each CDB should
indicate the LUN. Simply do a logical OR with 0x20 and you're talking to LUN
1.
>
> B'ichela
>
------------------------------
From: "Rob Turk" <[EMAIL PROTECTED]>
Crossposted-To: comp.periphs.scsi,comp.os.cpm,comp.sys.tandy
Subject: Re: Where can I buy bridgeboards?
Date: Sun, 22 Apr 2001 10:20:24 +0200
"B'ichela" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> BTW what is the
> Biggest capacity RLL drive one can buy? lets see if you have 16 heads
> 32 sectors per track at 512 byte sectors with 2048 cylindars.
> Thats based on the Limits of my ACB-4070 mode select. that
> comes out to 536,870,912 bytes! I never saw a 520MB RLL drive before!
The largest drive I ever used with my ACB-4070 was an OEM Maxtor XT-2190
(DEC RD-54 from a MicroVAX II) which is a 159MB drive with MFM, With RLL it
gave me close to 240MB. The drive wasn't RLL certified but worked for me...
Maxtor had a version with higher capacity (XT-4380) which comes pretty close
to your maximum. You may want to search the internet for a document called
'TheREF', which used to be the golden guide on harddisks.
Rob
------------------------------
From: "Vik Heyndrickx" <[EMAIL PROTECTED]>
Subject: Re: NICs for multi-multihomed hosts
Date: Sun, 22 Apr 2001 08:25:36 GMT
"Carsten Cimander,,," <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> AFAIK 3Com and intel and DEC offer PCI-Cards with 4 LAN interfaces on one
> single card. each card is treated as a single interface. But I am not
> shure if this
> works like LUN-numbers (subnumbers) of SCSI-IDs (mainnumbers) i.e. if the
> interfaces must be invoked as a subinstance of the main/carrier card.
As long as I can treat the four LAN Interfaces completely separately as e.g.
eth0 up to eth3, I would be very happy. Anyone, any experience with this?
Could this work that way?
> As you want to implement a 2.4 kernel I assume that you don't want to
> install
> it on an box with a i386 CPU :-)
Why not? I've been running 2.4 kernels since a couple of months on an actual
Intel 80386-16. But, no, in this case it would go in a state-of-the-art new
machine.
Thanks & Regard,
--
Vik
------------------------------
From: "Vik Heyndrickx" <[EMAIL PROTECTED]>
Subject: Re: asus a7v133
Date: Sun, 22 Apr 2001 08:37:41 GMT
"Dave" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> Can someone tell me what a RAID0 controller is?
Well, it is actually an IDE controller which implements RAID0. I suppose you
know what an IDE controller is, so my best effort for explaining RAID0:
In a RAID0 configuration, local consecutive tracks are written to different
physical hard disks drives, effectively increasing the thoughput towards the
disks. So track 0, 2, 4, 8 go to disk0 and track 1,3,5,9 go to disk1. Take
this explanation with a grain of salt, it's actually more complex.
The linux kernel has been implementing this for years in software (software
RAID). Specialized SCSI RAID controllers have also existed for years, but
IDE RAID is rare. The Promise controller on the A7V133 can be put into two
modes: a normal ATA100 IDE controller, and a IDE ATA100 RAID0 controller.
Regards,
--
Vik
------------------------------
From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Subject: Re: 3 com nic
Date: Sun, 22 Apr 2001 10:43:33 +0200
Chris <[EMAIL PROTECTED]> wrote:
>> Okay, you should not play with the IRQ paramaters. The DOS program has an
>> AUTO probe feature use that! For the linux part: you load it as "insmod
>> 3c509" . And "ifconfig eth0".
> I hope someone notices my little question on this old-ish thread...
> The above two commands finally enabled my 3C509B card that's been driving
> me batty for days. The only problem is that every time I reboot, I have to
> retype the commands. Is there a way they can be made permanent? I am a
No you don't.
> complete Linux newbie and would need baby steps.
You'll have to (in the worst of cases) to Add them to your init scripts.
Or just tell your distro that you have this card, using its setup tools,
which is the correct way for a newbiw to do it. Sorry, no info in, no info
out! You'd have to tell us which distro, and what you previously did by
way of configuration, to get more precise instructions. And even then,
RTFM is probably your best bet, since remote advice without a feedback
loop is not going to be error-free.
Peter
------------------------------
From: Rick <[EMAIL PROTECTED]>
Crossposted-To: comp.periphs.scsi,comp.os.cpm,comp.sys.tandy
Subject: Re: Where can I buy bridgeboards?
Date: Sun, 22 Apr 2001 05:24:59 -0700
Richard Erlacher wrote:
> On Sun, 22 Apr 2001 02:20:28 -0000, [EMAIL PROTECTED] wrote:
>
> >
> >On 2001-04-22 [EMAIL PROTECTED] said:
> >
> > >I think you both may be wrong in assuming that MFM and RLL drives
> > >are the same.
>
> Some vendors made drives that were "different" in that they
> specifically added logic to detect that the modulation was RLL rather
> than MFM, and, sensing that the modulation wasn't MFM, they made the
> drive malfunction. This was a cyinical but, probably unavoidable
> result of the availability of cheap controllers at a time when pushing
> drive capacity was a costly issue.
>
> > >I don't know a thing about the subject. But I do have an article
> > >that states the RLL controller fools the computer into thinking the
> > >drive ( Heads, Sectors, Tracks ) are not what they physically
> > >really are. MFM has limitations as to the number of sectors per
> > >track and tracks per drive and the controller doesn't know computer
> > >doesn't know this only the controller.
> > >When RLL came along the Controller Manufactures were able to fool
> > >the computer into accepting larger capacity drives.
> > >If you want I can E-Mail the disk with the more detailed explanation
> > >Jack
> >
> >That's not necessary; you're correct.
> >
> >But the bigger problem -- which someone already alluded to earlier
> >in this thread -- is that an RLL drive is built to different technical
> >and material specifications than is an MFM drive.
> >
> >If you connect an MFM drive to an RLL controller, you can usually expect
> >to get an inordinate number of physical disk errors at the time you low-
> >level format the drive.
> >
> >Even if the low-level format completes without an outrageously large
> >number of errors, you generally find that disk errors begin to creep in
> >as the disk is used on a day-to-day basis.
> >
>
> This isn't necessarily the case, as the RLL timing was in no way more
> restrictive than that used for MFM. RLL used a set of rules that
> crammed more bits into the same space but fiddled with the spacing of
> the flux reversals so they didn't occur any more often than with MFM.
It depends on what you are referring to as timing. MFM encoding involves
clocking information being relayed with the data pulses. It relies on the
flux reversals being evenly spaced and because of that less sophisticated
error correction is required. RLL, OTOH sends no clocking information. Since
the flux reversals can arrive at irregular intervals, accurate reading of the
flux reversals is even more important under RLL. The fiddling with the
spacing, or timing, of the flux reversals varies under RLL encoding.
Otherwise you wouldn't see a gain in data density. The *density* of the flux
pattern for each scheme is basically the same. But the *frequency* of flux
reversals per linear space is fixed under MFM and varies under RLL.
> Some drives using a dedicated servo surface (these always had an odd
> number of heads, BTW) had trouble with RLL, because the flux reversals
> didn't sync with those written on the servo surface. I used one, for
> a very long time with RLL, however, and actually had very little
> trouble with others of the same type, but they did seem to have
> problems with RLL and ARLL (Perstor) modulation.
>
> >
> >It's somewhat like trying to use a 720k double-density floppy disk as
> >a 1.44 meg high-density floppy. Sure, you can drill an extra hole in
> >the 720k disk's case, but that doesn't make it a 1.44 meg disk. The
> >two disks' technical specs are quite different.
> >
> That may exhibit the same result, but it's for a totally different
> reason.
> >
> >Even if you successfully format a 720k disk to 1.44 meg, you find that,
> >after a period of time, the data you've stored on that disk -- or the
> >disk format itself -- starts to disappear.
> >
> >Much the same thing happens with an MFM hard disk that's connected to
> >an RLL controller.
> >
> It may, but won't with proper maintanance.
> >
> >Not a recommended practice! :) You might get away with it for awhile,
> >but ultimately you can expect degradation to occur. So be aware.
> >
> Speed tolerance is the only theoretical issue that arises. If you
> look at how 2,7 RLL is generated and compare the results with what MFM
> does, you'll see that 2,7 RLL doesn't violate any of the constraints
> placed on drives designed to use MFM. If short-term speed variations,
> which would only occur with a very old and mechanically unsound drive,
> occur, you could get into timing trouble because the PLL can't track
> without some jitter.
>
> Dick
I beg to differ on that one. If you are using an ST225 - a cheap drive with
relatively low quality media surface - and you are cramming more data onto it
by eliminating the fixed flux reversal pattern of MFM recording there will be
more errors introduced. Simply because of the cheap media surface are
relative lack of tolerance for media errors under RLL. Combined with a
stepper motor for a head actuator - which provides no positioning feedback -
as a second source for inducing read errors. The media surface and inaccurate
head positioning are far more likely to be a source for error under RLL than
any potential speed variation in the drive.
------------------------------
From: Dougie Richardson <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.help,linux.redhat
Subject: Re: es1371 - No Sound
Date: Sun, 22 Apr 2001 10:39:34 +0100
Bob Bucy wrote:
> Multimedia audio controller: Ensoniq ES1371 [AudioPCI-97] (rev 6).
> IRQ 5.
> Master Capable. Latency=96. Min Gnt=12.Max Lat=128.
> I/O at 0x1440 [0x147f].
Its not a Soundblaster 128 - its an ES1371 - there is a specific module in
the 2.2 kernel for the ES1370 and for AC97 have you tried using them
instead?
Dougie Richardson //================================
//
[EMAIL PROTECTED]
=================// http://www.incarnate.uklinux.net
------------------------------
From: Dougie Richardson <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc
Subject: Re: Pentium133 down for the count??
Date: Sun, 22 Apr 2001 10:44:16 +0100
Donald A. Newell Jr. wrote:
> Sounds like a CMOS battery is on last legs....
> Just a hint, good luck.
> Don
>
I'd check the memory too - my old p133 kept crashing out in a similar
fashion when I installed RH5.1 on it - after swapping the memory in bank 1
it works fine now - slow usually relates to memory.
--
Dougie Richardson //================================
//
[EMAIL PROTECTED]
=================// http://www.incarnate.uklinux.net
------------------------------
From: Dougie Richardson <[EMAIL PROTECTED]>
Crossposted-To: alt.linux,comp.os.linux.help,comp.os.linux.redhat,comp.os.linux.setup
Subject: Re: Modem trouble
Date: Sun, 22 Apr 2001 10:52:17 +0100
Mark Bratcher wrote:
> Anyway, I think the Rockwell chip set _might_ be for a Windows-modem
> (winmodem). In other words, all signal processing functions are performed
> on the PC's driver for the OS. Windows OS driver model uses "special"
> drivers for devices like this in which the complexity of the device is
> programmed into the driver.
The rockwell chipset is a winmodem and is not supported by Linux as
rockwell won't divulge the details - winmodems using the Lucent chipset and
a couple of others are supported however - take a look at:
http://linmodems.org for more information.
Dougie Richardson //================================
//
[EMAIL PROTECTED]
=================// http://www.incarnate.uklinux.net
------------------------------
** 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
******************************
