Linux-Hardware Digest #247, Volume #9            Sat, 23 Jan 99 01:13:37 EST

Contents:
  Re: Problems setting up SoundBlaster AWE64 Gold on RH 5.2 ("Ritchie")
  Re: initio 9100UW & videomodelines
  Re: Linux with Non Intel
  Re: Cirrus 5424 @ 16bpp? (Jakob Eriksson)
  DSP boards & Linux? (Satyajit Rao)
  Linux Drivers for Cards that drive digital LCDs?? (Satyajit Rao)
  Re: Removed NETEAR FA310TX- Wont work after putting it back in.
  Re: Linux keyboard? (For emacs use) (Erik Naggum)
  Re: Wacom Woes... (Guus Zijlstra)
  Re: Winmodem or no?? (Rick Brice)
  PnP sound in the new pre 2.2 kernel (David Barnard)
  Re: Modem compatability ("Carson Saunders")
  Re: Linux keyboard? (For emacs use) (David Fox)

----------------------------------------------------------------------------

From: "Ritchie" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Re: Problems setting up SoundBlaster AWE64 Gold on RH 5.2
Date: Fri, 22 Jan 1999 19:46:08 -0700

Any luck yet?  I am struggling with the same problem.  I upgraded to the
newest version of isapnptools 1.17, which sndconfig uses to detect the card.
I also updated sndconfig to version 29, which accomplished nothing so I went
back to version 27.

Using sndconfig version 27 and isapnptools 1.17 I ran sndconfig.  It detects
my card as a AWE 64 and succeeds in playing the sample file.  I then
rebooted, and noticed that it detects my sound card, but fails in detecting
the AWE support.

I am able to play .au file using
cat <filename.au> > /dev/audio

But no luck playing a midi file.
playmidi -f <filename.midi>
No device or something like that.

I haven't even attempted testing whether or not AWE support works.

Let me know if you have any luck with this, and if you get midi support to
work.
John Welch wrote in message <[EMAIL PROTECTED]>...
>Hello,
>    I have recently installed RedHat 5.2 on my PC (P166, 48MB).  While
>the install went smoothly, I have been struggling to set up some
>things.  I worked through getting an X-server running.  It also took
>some time for me to get my modem up and running.  In each case by doing
>research on newsgroups and HOWTO docs I was able to find my problems and
>
>successfully configure these things.  However, I am now stuck in trying
>to get my Sound Blaster AWE64 Gold sound card working.
>   These are the steps that I have followed:
> 1. Read Sound Blaster AWE32/64 HOWTO.  I basically ignored the section
>on rebuilding the kernel because it is my understanding that these
>modules are already built into this kernel (2.0.36).
> 2.  Ran sndconfig program.  This program found my card and correctly
>identified it.  It then said it was going to run a sound card test.
>However an "isapnp error" window comes up saying:
>                  LD setting verify failed.....
>                  Try adding (VERIFYLD N) to top of your script
>                   Error occurred executing request 'LD2' on or around
>                   Line 324 --- Further action aborted
>I click OK to this message and another window comes up saying:
>       Autoconfig failed now proceeding with manual config. (I click OK)
>
>I step through the manual config  but it comes right back to the isapnp
>error screen.  All I can do at this point is cancel out.
>3.  After exiting the sndconfig program I looked around and found a file
>
>called 'soundcard' in the /etc/sysconfig directory.  This file says that
>
>it was created by the sndconfig program.  The only active line
>(non-commented) says "CARDTYPE = SB32"
>4.  I then edited the /etc/isapnp.conf file which also was created by
>the sndconfig program.  I added the (VERIFYLD N) to the top of the
>script.  I also looked at the IRQ, DMA, and I/O settings in each
>section.  These settings match exactly the settings from Windows 95
>(where the card is working by the way).
>5.  I re-executed the command 'isapnp /etc/isapnp.conf'.  When I do this
>
>it sees Board 1 (my modem) and then says "Board CTl009/2547404 not
>found" three times.
>6.  I then rebooted the PC to watch it go through the boot process.
>When the system gets to the ISAPNP
>Conf program it finds two boards, my modem and my soundcard.
>7.  Executing the command 'modprobe -a sound' returns nothing and when I
>
>execute 'cat /proc/sndstat'
>no devices show up.
>  I have searched the linux newsgroups and have found other problems
>with the SB32/64 sound cards but nothing really similar to my problem.
>
>  Sorry for being so long winded but I wanted to include as much detail
>as possible.  Any comments or suggestions would be appreciated.
>
>Thank You in Advance,
>
>John
>
>
>



------------------------------

From: [EMAIL PROTECTED] ()
Subject: Re: initio 9100UW & videomodelines
Date: 21 Jan 1999 17:13:42 GMT

On 11 Jan 1999 22:47:14 GMT, Horvath Gabor <[EMAIL PROTECTED]> wrote:
>I need some info on the $Subject SCSI card. I know that the manufacturer 
>provides a driver but I'd like to know how good it is and if there is  any
>kernel development going on about it. I would also care for some perfomance 
>info. I plan to swap my aha2940W to an initio9100UW. 
>I have no idea if it will be worth.

I am currently working on/maintaining the initio driver. It is working with
2.0.x, 2.1.x and 2.2.x. It's quite fast, and I haven't got any problems with
it. I'm not sure if you want to exchange it for an Adaptec 2940 UW though.
If you want specific information on performance, let me know what you want to
know, how to get the data and I can post it here.

Regards,

Bas Vermeulen

--
When I shop for hardware I always look for the "Designed for Windows 95" logo.
I really thank Microsoft(TM) for encouraging manufacturers to label their
products this way, so I know what to AVOID.

I stick to quality software:

Linux 2.0.36                        | IBM OS/2 Warp (TM) v4.0

------------------------------

From: [EMAIL PROTECTED] ()
Crossposted-To: alt.os.linux,alt.uu.comp.os.linux.questions
Subject: Re: Linux with Non Intel
Date: 21 Jan 1999 17:21:07 GMT

On Sun, 17 Jan 1999 19:28:14 -0500, [EMAIL PROTECTED] wrote:
>I cant wait till the K7 comes out im gonna build my linux box around that
>beautiful chip.  AMD chip, which will take over Intels spot at #1 and 
>Linux which will take microsofts #1 spot.

Neither can I. When the mainboards come out for it, I'll get a bios that
works with the newer Alpha's (which uses the same CPU slot... *grin*)
and ditch the complete x86 platform. Eat that, AMD, Microsoft and Intel.

Bas Vermeulen

--
When I shop for hardware I always look for the "Designed for Windows 95" logo.
I really thank Microsoft(TM) for encouraging manufacturers to label their
products this way, so I know what to AVOID.

I stick to quality software:

Linux 2.0.36                        | IBM OS/2 Warp (TM) v4.0

------------------------------

From: Jakob Eriksson <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.x
Subject: Re: Cirrus 5424 @ 16bpp?
Date: Thu, 21 Jan 1999 18:37:38 +0100

On Thu, 21 Jan 1999 [EMAIL PROTECTED] wrote:

> In article <7872e4$4ah$[EMAIL PROTECTED]>,
>   [EMAIL PROTECTED] (John David Bowden) wrote:
> > It has enough Video RAM (1meg) to go up to 800x600@16bit, which is how I'd
> > like to run it.  But according to the X docs, it says if I have a Cirrus
> > 5424 in an ISA slot, and more than 16megs of system RAM, I can't run the
> > card higher than 8bit.
> >
> > I even tried appending "mem=16M" to LILO, but that didn't help.
> Snip...
> 
> The reason you can't get the higher colour depth is because the 8bpp mode
> uses a stock interface to the card and 16+bpp uses a hardware specific
> interface.  This driver will only access the card in this manner if the video
> buffer has been overlaid into the CPU address space - which you can't do
> because you've already got RAM there:)
> 
> I've been working on a driver for the CLGD5434 for about a year.  I have a
> 486/33 with 64MB ram and I hit the same problem as you.  My solution was to
> start working on a repacement driver.  It should be ready sometime towards the
> summer if you're not in a big hurry:)
> 
> If you're interested in testing it on your 5424 let me know and I'll e-mail
> you the betas in Mar/Apr.  (It would be sooner but work keeps me busy;).


I have a 5424. (I think, I have an old Compaq Presario 486-66MHz)

I could try it out some day.

BUT!
Since you seem to be someone having a few clues:

can one use a Tseng ET4000 and a 5424 (or any other VGA) at the same time?

That would be cool, two monitors on the same machine.
I know it works with Hercules monochrome (stoneage) and VGA,
but two VGA-type cards at the same time?
Please enlighten me.


BTW, my news server is _very_ flaky, so if you send a copy to my mailaccount,
I'll be glad!

Regards,
Jakob Eriksson



------------------------------

From: Satyajit Rao <[EMAIL PROTECTED]>
Subject: DSP boards & Linux?
Date: Fri, 22 Jan 1999 23:12:53 -0500

Hi,
       I would like to use DSP boards for some heavy-duty number
crunching. These boards
may either be standalone,  or  hang off the PCI bus of my PC. (running
Linux). I would imagine
that board specific linux drivers are necessary in the latter case. Is
this assumption true? Are there people out there that have some
experience in either driving or downloading code to DSP boards from a
Linux machine?
                                     Any pointers will be appreciated,

Thanks,

Sajit
PS: Please copy any responses to
       [EMAIL PROTECTED]



------------------------------

From: Satyajit Rao <[EMAIL PROTECTED]>
Subject: Linux Drivers for Cards that drive digital LCDs??
Date: Fri, 22 Jan 1999 23:23:32 -0500

Hi,
        I would like to get a good *digital* LCD  montior for my linux
machine. The first problem of
course is that there aren't many digital LCD monitors out there.  There
is the new SGI 1600SW,
monitor that requires a Number Nine Revolution IV card, but as far as I
know this card does not
have a linux driver.

Does anybody know of linux drivers for cards that drive digital LCDs?


Thanks,

Sajit


------------------------------

From: [EMAIL PROTECTED] ()
Crossposted-To: comp.os.linux.misc
Subject: Re: Removed NETEAR FA310TX- Wont work after putting it back in.
Date: 23 Jan 1999 04:19:24 GMT

On Fri, 22 Jan 1999 21:02:50 -0500, burk <[EMAIL PROTECTED]> wrote:
>I recently read on another newsgroup that the newer FA310TX's no longer
>use the DEC tulip chip set and give Linux fits. Anybody else hear this? 
>Jason does your card have the DEC chip on it (IIRC it was easily visible
>on the card)?
>
>-burk

I had FA310TX revD1 for four days at which time it finally died! It has
a Lite-On PNIC which is kinda supported but very unreliable. At the 
beginning it had some performance issues and had a hard time receiving
bradcasts(dhcpc). By the fourth day it was unable to communicate at ALL!
I tried the tulip.c shipped with it (0.88) and couple other versions
including the freshest 0.90f. None of the were able to revive it by
the fourth day. After searching the newsgroups I found out that I
wasn't the only person with problems with this card. Apparently if
it will manage to work for you it'll be much slower than DECtulip
and unreliable when receiving Broadcasts.

I got Intel EtherExpress Pro+ 10/100 and can't be happier with it.
Great performance, decent price 65$, and very well supported.

Good Luck

BTW my "episode" with Netgear happened this week.


-- 
Michal Sabala aka Saahbs
 Linux'er since 0.97 :)
 UIUC Class of 2002; ECE
Linux, hardware, C, Html,
aviation, rc-air models

http://fly.to/saahbs

------------------------------

From: Erik Naggum <[EMAIL PROTECTED]>
Crossposted-To: 
comp.os.linux.misc,comp.unix.questions,comp.unix.misc,comp.emacs,comp.editors
Subject: Re: Linux keyboard? (For emacs use)
Date: 23 Jan 1999 02:48:56 +0000

* Erik Naggum <[EMAIL PROTECTED]>
| ... I use two spaces after sentence-ending punctuation. 
  
* [EMAIL PROTECTED] (Jari Aalto+mail.emacs)
| Which is some odd relict that somebody still seems to believe is needed...

  wow!  it's possible to smoke out certain people with only two spaces.
  I just love it.

#:Erik
-- 
  SIGTHTBABW: a signal sent from Unix to its programmers at random
  intervals to make them remember that There Has To Be A Better Way.

------------------------------

Date: Thu, 21 Jan 1999 21:30:15 +0100
From: Guus Zijlstra <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Re: Wacom Woes...

Bruce, thanks for the reply. Somehow I managed to find only
the type 4 protocol drivers.

But, this leaves me with the following newbie questions:
 - assuming good old levien is talking about xfree86: how do I find
   out if I'm running 3.3.2 or 3.3.3?
 - How do I rebuild the Xserver package?

I have a debian installation and a cable modem, so getting stuff is
not a problem. Debians dselect, however, does not give a good
overview of what's available. Can you help, or refer to a good
source of info?

Ciao,
Guus.

[EMAIL PROTECTED] wrote:

> Guus Zijlstra <[EMAIL PROTECTED]> writes:
>
> > Thanks for the xinput link. My tablet does not seem to be supported.
> > It's a rather new line, I think. Intuos, they call it.
>
> Mine works fine.  Follow the links from <URL:http://www.wacom.com>
> (you're looking for drivers, and there's a link to a site containing
> an updated (unsupported, of course) XFree86 driver).  I've only got
> the basic pen; the web page indicates that (for example) rotation with
> the "4D Mouse" doesn't work yet, and similar things.  The pen seems to
> work fine, though, although I've not found anything that does anything
> interesting with tilt.

--
============================================================
To reply, please remove the no.spam. from my e-mail address.



------------------------------

From: Rick Brice <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux,comp.os.linux.advocacy,comp.os.linux.setup,comp.modems
Subject: Re: Winmodem or no??
Date: Thu, 21 Jan 1999 14:31:46 -0500
Reply-To: [EMAIL PROTECTED]

Interesting Idea
but basically there is nothing standard about the external modem except
that the RS232? interface is a specification, not a standard, that you
generally cannot depend upon for consistency from one manufacturer, much
less from different manufacturers.
The wiring may be different from series to series or manufacturer to
manufacturer.....
from one generation of software to the next you cannot even depend on the
same implementations of a/an/(the?) AT command set.
When you add in an external interface RS232 ports on whatever manufacturers
computer, using whatever manufacturer's UART's, or Modem emulator's, or
however they see fit to implement the interface to the external box......ad
infinitum........
Give me an internal that works....anyday!

Rick

jedi wrote:

>

<SNIP>

>         That's ironic as hell considering that the standard
>         external modem is one of the best perservering
>         elements of computer technology across the entire
>         span of the age of microcomputers.
>
>         You have your own tunnel vision.
>
> --
>                 Herding Humans ~ Herding Cats
>
> Neither will do a thing unless they really want to, or         |||
> is coerced to the point where it will scratch your eyes out   / | \
> as soon as your grip slips.
>
>         In search of sane PPP docs? Try http://penguin.lvcm.com

--
==============
Earth is a small target suspended in space......
r dot w dot brice at lmco dot com



------------------------------

From: David Barnard <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.help,comp.os.linux.setup,comp.os.linux.questions
Subject: PnP sound in the new pre 2.2 kernel
Date: Fri, 22 Jan 1999 18:15:36 +0000

Somebody please help me!  I've been loosing sleep for three days
staying up all night compiling kernel after kernel trying to get the new
pre-2.2 kernel to find my PnP Sound Blaster card.

  I've recently acquired a new Sound Blaster PCI128 sound card for my
machine which is running RedHat 5.1.  The card is basically an SB(16?)
PCI PnP card with fancy software.  My BIOS alledges to support PnP, and
I've had it recognize other cards when I used to have an MS
partition(which was sacrificed to the bit-bucket in favor of kde)  The
BIOS gives me a message right before the LILO prompt which appears to
denote that it recognizes a "multimedia device" on IRQ 7.  I was doing
some reading and found that PnP was supposed to be supported in the new
(2.1 & 2.2) kernels.  I got the source, compiled with PnP support
activated.  I compiled in all the usual sound goodies and installed the
new kernel.
  The kernel boots, but doesn't seem to recognize the card.  Do I have
to do something special to get the kernel to actually LOOK for a PnP
card, or is it supposed to do it automagically?
  If someone could send me a step by step outline of what I need to do
in order to get the card to be recognzied by the OS, I'd appreciate it.
  Please if possible list:

1) any files which may need to be tinkered with (full paths of where
they are "supposed" to live?)
2) exact (or near to it) options to be compiled into the kernel for a
real Sound Blaster card.
3) Steps neccessary aside from building a new kernel
4) URL's of any relevant documentation on PnP support in the new kernel,
getting sound to actually work under Linux, and/or getting the new
kernel to actually recognize and configure a PCI PnP device
  If you need ANY information to help you diagnose what I'm doing wrong,
please don't hesitate to ask.  Please if possible reply to
[EMAIL PROTECTED] (remove the JUNKMAILCONTROLL)
  Here is a cat of my /dev/sndstat and a uname -a

  Any help would be GREATLY appreciated.
  Millions and millions of thanks in advance.

  David

uname -a:
Linux felix.geeks_R_us 2.2.0-pre8 #6 Thu Jan 21 12:30:47 CST 1999 i586
unknown

cat /dev/sndstat:
OSS/Free:3.8s2++-971130
Load type: Driver compiled into kernel
Kernel: Linux felix.geeks_R_us 2.2.0-pre8 #6 Thu Jan 21 12:30:47 CST
1999 i586
Config options: 0

Installed drivers:
Type 1: OPL-2/OPL-3 FM
Type 26: MPU-401 (UART)
Type 2: Sound Blaster
Type 29: Sound Blaster PnP
Type 7: SB MPU-401
Type 36: SoftOSS Virtual Wave Table
Type 37: Loopback MIDI Device

Card config:
SoftOSS Virtual Wave Table
(Sound Blaster at 0x220 irq 7 drq 1,5)
(SB MPU-401 at 0x330 irq 1 drq 0)
(OPL-2/OPL-3 FM at 0x388 drq 0)
Loopback MIDI Device drq 0

Audio devices:

Synth devices:
0: SoftOSS

Midi devices:
0: Loopback MIDI Port 1
1: Loopback MIDI Port 2

Timers:
0: System clock
1: SoftOSS

Mixers:

------------------------------

From: "Carson Saunders" <[EMAIL PROTECTED]>
Subject: Re: Modem compatability
Date: Fri, 22 Jan 1999 18:04:52 -0500

I tried to use isapnp but it requires a config file.  Where do I get that?
US Robotics doesnt make a driver/config file for Linux.  Any other thoughts?

Thanks
Carson

>It may or may not work.  Dell sells both 3COM/USR modems and
>winmodems.  If it is a winmodem it will not work!  If it is a modem.
>Setserial can help configure it, if it is PnP (Plug and Pray), use isapnp.
>--
>           Dan Nguyen            | There is only one happiness in
>        [EMAIL PROTECTED]         |   life, to love and be loved.
>http://www.cse.msu.edu/~nguyend7 |                   -George Sand
>



------------------------------

From: d s f o x @ c o g s c i . u c s d . e d u (David Fox)
Crossposted-To: 
comp.os.linux.misc,comp.unix.questions,comp.unix.misc,comp.emacs,comp.editors
Subject: Re: Linux keyboard? (For emacs use)
Date: 21 Jan 1999 06:39:36 -0800

Shaun Lipscombe <[EMAIL PROTECTED]> writes:

> i also, always choose a good monitor and keyboard.  As you rightly
> state, if you don't wish to suffer from repetitive strain injuries, or
> such like, it is a neccesity.

Or even if you do!
-- 
David Fox           http://hci.ucsd.edu/dsf             xoF divaD
UCSD HCI Lab                                         baL ICH DSCU

------------------------------


** 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
******************************

Reply via email to