Linux-Hardware Digest #446, Volume #14 Tue, 6 Mar 01 23:13:05 EST
Contents:
Re: iPaq + Pocketlinux -> le bon plan ???? (Michael Heiming)
Re: FastTrak100 - accessing and booting from RAID 0 array ("Will")
Re: poll_wait and interruptible_sleep_on (Michael Mueller)
Re: Ack! Newbie linux sound troubles (Alex Weiss)
Re: Video Capture Card/TV Tuner (William Burrow)
Re: KT7A RAID et Linux ("Simon Turvey")
Re: Video Capture Card/TV Tuner (Drew Roedersheimer)
Mustek 4800P almost works..help needed with xsane/xscanimage (Chris Harris)
SoundMAX Integrated Digital Audio ([EMAIL PROTECTED])
Re: HELP - Dual Input Monitor (Michael Meissner)
Re: Install help: Crusoe laptop with only a PCMCIA CD-ROM drive?
xp1000 sound (John)
Re: HELP ME!: How can I enable ALSA MIDI synth sound? (for SB AWE64 & (CYBERYOGI
=CO= Windler)
Re: joystick woes ("D. Stimits")
----------------------------------------------------------------------------
Date: Wed, 07 Mar 2001 00:44:47 +0100
From: Michael Heiming <[EMAIL PROTECTED]>
Subject: Re: iPaq + Pocketlinux -> le bon plan ????
James Forbes wrote:
> No probably just hoping that someone may realise , someday that more than
> one language is spoken in this world ;-)
I think most people who read this ng, are able to realise, that there are
other languages.
It just looks like this is an english ng...:-)
>
>
> And I dont even speak french ......
I know a bit french, but don't know anything about pocketlinux and I'm always
offended if
someone is not posting in english. The worst (for me) is if I read someones
posting in german...:-(
Michael Heiming
>
>
> "Arctic Storm" <[EMAIL PROTECTED]> wrote in
> message news:eboo6.1717$[EMAIL PROTECTED]...
> > > Je me renseigne sur le PC de poche iPaq de Compaq tournant avec
> > > Pocketlinux (www.pocketlinux.com ):
> > >
> > > Quelles sont les applications dispo ?
> > > La reconnaissance d'�criture est-elle probante ?
> > >
> > > + toutes infos disponible sur la b�te...
> >
> > Since you wrote your post in french, you probably don't speak English.
> > If you *do* speak English, but posted in french, that would be a whole
> > different problem.
> > Were you hoping that someone who reads/writes french to stumble upon your
> > post?
> >
------------------------------
From: "Will" <[EMAIL PROTECTED]>
Subject: Re: FastTrak100 - accessing and booting from RAID 0 array
Date: Tue, 6 Mar 2001 18:01:00 -0600
The only way you will be able to use a FastTrack raid array is to use the
driver provided on the Promise website. It works quite nicely though.
"iQXth" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> OK, here is how my Promise FastTrak100 is setup:
>
> Channel 1 master/slave has two 45GB drives striped to form an array
> with geometry of 11213/255/63.
>
> Channel 2 master has a 28GB drive by itself to form a single-disk span
> array with geometry of 3467/255/63.
>
> When installing Red Hat Linux 7.0, I can switch over to the command
> prompt and do a 'cat /proc/pci' and get some info on the Promise
> controller. Here is a snippet of the info:
>
> 0x9400
> 0x9800
> 0x9c00
> 0xa000
> 0xa400
>
> With this info, I can use the boot parameter 'ide#=#x####,#x####' and
> get access to individual drives only. So, when I go to install Red Hat
> Linux 7.0, I use:
>
> expert ide2=0x9400,9x9802 ide3=0x9c00,0xa002
>
> Using this, it shows that I have access to 3 drives with geometry
> 5606/255/63, 5606/255/63, and 3467/255/63. The first two are obviously
> members of the striped array and the third is the lone 28GB drive.
>
> I can install to the 28GB drive and Red Hat'll install, boot, and run
> just fine. But this is not how I originally wanted to do it, since the
> 28GB drive is a removable drive, I want Linux on the array. I hesitate
> to install to one of the drives in the array because I have this
> feeling that it'll corrupt the data that is already there since it is
> not reporting the geometry correctly.
>
> Ideally, I want to be able to access and install to the array using
> boot parameters. The result of this should be access to a drive of
> geometry 11213/255/63.
>
> Does anyone know how to do this? Could the '0xa400' be part of the
> solution? That number was not used during the original boot parameter
> to access the individual drives.
>
> If you need more info please ask.
>
>
> --- iQXth ---
> Please respond to this thread
> or post with 'ulvfboqj' in the
> subject to get my attention.
------------------------------
From: Michael Mueller <[EMAIL PROTECTED]>
Crossposted-To:
comp.os.linux.development.system,alt.os.linux,comp.os.linux.embedded,linux.redhat.devel,linux.dev.kernel
Subject: Re: poll_wait and interruptible_sleep_on
Date: Wed, 07 Mar 2001 00:19:33 +0100
Hi Ajit,
you wrote:
> Can anyone provide me the difference between these two calls (poll_wait and
> interruptible_sleep_on) . I'm confused between the usage of two. Also, it
> would be much better if you can let me know how shall I implement the poll
> function in a driver.
>
> Does the poll_wait puts the process in the sleep mode?
If I see right pool_wait() does return instantly and do_poll()
implemented in ./fs/select.c does the the waiting. This should be of
need since a single call to the poll() syscall can wait for events on
any of multiple filedescriptors. If the device-specific implementation
would already block one could only wait for the case every of the
filedescriptors had an event.
> I don't have to poll for read or write methods. All I need is to let the
> user process know if the interrupt status has been changed. So if he calls
> the poll system call. I want to wait in this call (in my driver) until the
> interrupt status has been changed. The change of status will happen in the
> interrupt handler. So is this a valid assumption that
>
> 1. If I call the poll_wait function in my poll routine, user process will
> remain in the sleep mode, until Interrupt handler changes the status and
> call the wake_up_interruptible.
If the user already does wait on for change of the interrupt status
(borken design) it might be usefull to return the value of the interrupt
status to the user. This could be accomplished by providing a little
buffer the read() function does take the value for.
For examples of an poll implementation see:
./fs/pipe.c(pipe_poll)
./drivers/net/ppp_generic.c(ppp_poll)
./net/ipv4/tcp.c(tcp_poll)
> 2. And this is the right way to implement
Yes, you should call wakeup_interruptible() with the second parameter of
poll_wait when ever you think one of the events poll() can wait for did
occour. If I read the source correctly the device dependend poll
function then can feature it out in detail for the case the occourence
of an event is not assured.
Malware
------------------------------
From: Alex Weiss <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Re: Ack! Newbie linux sound troubles
Date: 7 Mar 2001 00:04:13 GMT
In comp.os.linux.hardware Angry Bob <[EMAIL PROTECTED]> wrote:
> What would you like to read? [comp.os.linux.setup or *?]
> This is a Alex Weiss <[EMAIL PROTECTED]> scroll! it says:
> > 1. Run sndconfig as root and in console mode. While the installation, once
> > again, went without problems, this did not solve my problem.
> su to root and type:
> esd &
> --
> AngryBob Systems Consultant - http://www.trellisinc.com
> The secret to not getting burned out is to play at working hard,
> and not taking things too seriously.
> -- Linus Torvalds
------------------------------
From: [EMAIL PROTECTED] (William Burrow)
Subject: Re: Video Capture Card/TV Tuner
Date: Wed, 07 Mar 2001 00:15:14 -0000
Reply-To: [EMAIL PROTECTED]
On Tue, 06 Mar 2001 04:43:44 GMT in comp.os.linux.hardware,
Drew Roedersheimer <[EMAIL PROTECTED]> wrote:
>I haven't tried capturing at all - just watching - sorry. I have a Pentium
>II 450. And I've never tried using it in Windows, but I doubt there would
>be a performance difference because I *never* experience frame dropping,
>noise, machine slowdown, etc...
This is because you are watching in overlay mode -- the video is being
sent directly from the capture card to the video card without the CPU
intervening. The wonders of PCI bus.
So, for viewing only, CPU has little to do with it, so long as a
busmastering PCI slot is available for the capture card. Actually
capturing video seems to depend a lot on the disk and CPU.
--
William Burrow -- New Brunswick, Canada o
Copyright 1999 William Burrow ~ /\
Y1.99K compliant message. ~ ()>()
------------------------------
From: "Simon Turvey" <[EMAIL PROTECTED]>
Subject: Re: KT7A RAID et Linux
Date: Wed, 7 Mar 2001 00:21:14 -0000
Bonjour Guy,
d'abord, excusez s'il vous pla�t la traduction faible. En second lieu,
l'installation standard de SUSE Linux 7.x supportera la technologie HPT370
actuelle sur votre carte m�re.
J'esp�re que ceci aide,
Simon Turvey
"Guy Vivier" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> J'ai fais l'acquisition d'une carte KT7A raid , j'ai pluger mon disk dur
> Western digital
> sur IDE3 pour b�n�ficier de ATA100. Lors de l'installation de la
> mandrake 7.1
> ainsi que pour la redhat 7.0, j'ai le message suivant:
>
> An error has occured. no valid devices were found
> on which to create new filesystems.
> please check your hardware for the cause of this probl�me.
>
> Pouvez-vous me d�panner sur ce probl�me.
> Merci d'avance
>
------------------------------
From: [EMAIL PROTECTED] (Drew Roedersheimer)
Subject: Re: Video Capture Card/TV Tuner
Reply-To: [EMAIL PROTECTED]
Date: Wed, 07 Mar 2001 00:29:18 GMT
On Wed, 07 Mar 2001 00:15:14 -0000, William Burrow wrote:
>On Tue, 06 Mar 2001 04:43:44 GMT in comp.os.linux.hardware,
>Drew Roedersheimer <[EMAIL PROTECTED]> wrote:
>>I haven't tried capturing at all - just watching - sorry. I have a Pentium
>>II 450. And I've never tried using it in Windows, but I doubt there would
>>be a performance difference because I *never* experience frame dropping,
>>noise, machine slowdown, etc...
>
>This is because you are watching in overlay mode -- the video is being
>sent directly from the capture card to the video card without the CPU
>intervening. The wonders of PCI bus.
>
>So, for viewing only, CPU has little to do with it, so long as a
>busmastering PCI slot is available for the capture card.
It was quite obvious to me that something similar to DMA (for my video card)
was going on since CPU load was nonexistent. Much more than I cared to know,
but thanks for sharing. =)
>Actually capturing video seems to depend a lot on the disk and CPU.
>
>--
>William Burrow -- New Brunswick, Canada o
>Copyright 1999 William Burrow ~ /\
>Y1.99K compliant message. ~ ()>()
<tongue in cheek>
I wonder why....
</tongue in cheek>
-DR
--
Build a system that even a fool can use and only a fool will want to use it.
------------------------------
From: Chris Harris <[EMAIL PROTECTED]>
Subject: Mustek 4800P almost works..help needed with xsane/xscanimage
Date: Wed, 07 Mar 2001 07:32:32 -0300
Hi,
I was given a Mustek Scanmagic 4800P scanner to play with... At first I
didn't think parallel scanners were supported then found that they are
in version 1.0.4 of sane so I downloaded that and installed, then
followed the instructions (for the Mustek backend at
http://home/germany.net/freestyle/sane/ ) to check the makefiles and
dll.conf.
I think I have mustek_pp.conf correct. I have uncommented the entry for
this scanner.
If I run xscanimage I get an error, in the konsole, saying that no
scanners where identified.
If I run xscanimage mustek_pp:SM-4800P
An window pops up with the message "failed to open device
"mustek_pp:SM-4800P" invalid argument".
If I run scanimage the scanner scans something squirting garbage across
the konsole until it finishes scanning, but doesn't seem to save it
anywhere.
The scanner now seems to be recognised by scanimage, if I run
SANE_DEBUG_MUSTEK_PP=128 scanimage -L, I get
bash-2.04# SANE_DEBUG_MUSTEK_PP=128 scanimage -L
[sanei_debug] Setting debug level of mustek_pp to 128.
[mustek_pp] init: SANE v1.0.4, backend v1.0.9-devel
[mustek_pp] I wouldn't let myself be root if I were you...
[mustek_pp] init: option io-mode 2
[mustek_pp] init: option niceload
[mustek_pp] init: trying port `0x378'
[mustek_pp] attach: device 0x378 attached
[mustek_pp] attach: asic 0xa5, ccd 00
[mustek_pp] attach: use600 is `no'
[mustek_pp] init: naming device 0x378 'SM-4800P'
[mustek_pp] init: device 0x378 is from 'Mustek'
[mustek_pp] init: option wait-lamp 15
[mustek_pp] init: setting wait-lamp to 15 for device SM-4800P
[mustek_pp] init: option strip-height 16
[mustek_pp] init: setting strip-height to 16 for device SM-4800P
[mustek_pp] init: option buffer 122400
[mustek_pp] init: setting buffer to 122400 for device SM-4800P
device `mustek_pp:SM-4800P' is a Mustek MFS-600IIIP flatbed scanner
[mustek_pp] exit: (...)
I am running SuSE 7.0
Has anybody got any ideas? Do I have to do something else in xsane or
xscanimages configuration? I think I must be almost there.
Thanks
Chris
------------------------------
From: [EMAIL PROTECTED]
Subject: SoundMAX Integrated Digital Audio
Date: Tue, 06 Mar 2001 16:51:07 -0800
Reply-To: [EMAIL PROTECTED]
Just got a new Dell Dimension 4100 for my office, first thing I did was
repartition the disk and install Linux. Trouble is I am having no luck
setting up the integrated "SoundMAX" audio that comes with this
machine. There is no driver of info on the Dell web site, yet. Can
anyone help me on this?
Thanks
Bob
------------------------------
Crossposted-To:
alt.os.linux,comp.os.linux.misc,linux.redhat.misc,redhat.config,redhat.general,redhat.hardware.arch.intel
Subject: Re: HELP - Dual Input Monitor
From: Michael Meissner <[EMAIL PROTECTED]>
Date: 06 Mar 2001 20:41:28 -0500
"Jeff Gentry" <[EMAIL PROTECTED]> writes:
> Hello All,
>
> I am researching dual input monitors.
> I will soon be upgrading to RedHat 7.0 on an Intel x86 host
> platform due to project constraints.
> I have limited work space but a generous equipment budget.
> Can someone tell me if RedHat will support dual input monitors?
> If so, can I get the vendor and model numbers for the video card(s)
> and monitor?
I don't know what you mean by dual input monitors. I imagine it could either
mean monitors that take 2 separate inputs from different computers, or you mean
having one computer drive 2 monitors.
The first case is purely hardware, and Linux wouldn't notice whether or not
another box is connected to the same monitor or not. If this is case, I would
suggest you look at a KVM (keyboard, video, mouse switcher) instead of just
switching the monitor, because you still need 2 keyboards, and 2 mice. Sooner
or later, you will have one system showing on the monitor in front of you, and
type on the other keyboard or mouse. You definately want an electronic KVM and
not a mechanical switch. Prices are $150 - $1000 depending on features. Also,
be sure the KVM can handle your desired resolution and display rate (ie, a lot
of KVMs are more geared towards server farms where it is not important to have
high resolution). I've used the 4 port Cybex Autoview (ok, except the sequence
to switch screens make my repetive motion symptoms flare up), or the 8 port
CompuCable Power Reach (have some problems with mouse state). Other people
have used the Belkin OmniCube or OmniView SE with good results. I used a
version of the OmniView without the SE designation several years ago, and it
could not display a 1024x768 screen worth a damn.
The second case, I've heard of people using either the Matrox G400 (and now
G450) or separate pci video cards (especially Matrox cards) to display 2
screens. I don't think Red Hat linux supports this out of the box, but it
should be possible.
--
Michael Meissner, Red Hat, Inc. (GCC group)
PMB 198, 174 Littleton Road #3, Westford, Massachusetts 01886, USA
Work: [EMAIL PROTECTED] phone: +1 978-486-9304
Non-work: [EMAIL PROTECTED] fax: +1 978-692-4482
------------------------------
From: <[EMAIL PROTECTED]>
Subject: Re: Install help: Crusoe laptop with only a PCMCIA CD-ROM drive?
Date: Wed, 07 Mar 2001 01:47:45 GMT
Steven M. Casagrande <[EMAIL PROTECTED]> wrote:
> I've just bought a Fujitsu P1000 (Crusoe), with USB floppy and PCMCIA
> CD-ROM drive. The P1000 won't boot from the CD-ROM, but I can get it
> to boot the RH6.2 Linux install floppy. However, once there I can't
> figure out how to get it to recognize the PCMCIA CD-ROM drive so I can
> continue with the rest of the installation.
Hmm... Sounds like you want to create a boot disk with PCMCIA support...
I dont' know if that will work, but I guess it would be worth the
try.
In the images directory of the CD you should have a file called pcmcia.img,
or something to that extent. Use rawrite (in the dosutils dir)to copy
this file to a floppy. This floppy will be bootable, and should then see
the PCMCIA bus, and hopefully then the CDROM...
Good luck!
Kris
------------------------------
From: John <[EMAIL PROTECTED]>
Subject: xp1000 sound
Date: Wed, 07 Mar 2001 02:11:21 +0000
Hello,
I can't get a sound driver to work. I'm working with opensound and
Redhat but to no avail. There are no problems or errors to be found, just
no sound (except the terminal bell). Can anyone help me, or point me in
some direction?
Thank you,
John
_______________________________________________
Submitted via WebNewsReader of http://www.interbulletin.com
------------------------------
From: CYBERYOGI =CO= Windler <[EMAIL PROTECTED]>
Crossposted-To:
linux.dev.sound,linux.debian.user,comp.os.linux.misc,comp.os.linux.setup,comp.music.midi
Subject: Re: HELP ME!: How can I enable ALSA MIDI synth sound? (for SB AWE64 &
Date: Wed, 07 Mar 2001 04:21:17 +0100
"J. H. Brown" schrieb:
>
> I don't know about ALSA or the Gravis, but it should be no problem
> getting the AWE64 to work. You need to double check your interrupts and
> dma settings. Login as root and run sndconfig and reboot. If you can
> use the KDE or gnome midi players, then you might try installing ALSA.
>
In ALSA there is nothing like a "sndconfig".There is only a very buggy(though unusable)
"alsaconf" untility though I had to write my config file by hand.I already wrote my
own isapnp.conf entry though I know exactly which IRQs etc. the card takes.
MAY THE SOFTWARE BE WITH YOU!
*============================================================================*
I CYBERYOGI Christian Oliver(=CO=) Windler I
I (teachmaster of LOGOLOGIE - the first cyberage-religion!) I
I ! I
*=============================ABANDON=THE=BRUTALITY==========================*
{http://www.informatik.fh-hamburg.de/~windle_c/e_index.html}
------------------------------
Date: Tue, 06 Mar 2001 20:18:16 -0700
From: "D. Stimits" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: Re: joystick woes
"Michael J. Sherman" wrote:
>
> I have kernel 2.2.14, and am trying to get a Logitech
> Wingman joystick to work.
>
> Now, I can buy any joystick, I don't care, but I just
> happen to have this one.
>
> I have done a insmod joystick.o and it loaded in the
> joystick driver, but when I try a jstest on /dev/js0
> I get an error "no such device".
>
> What do I have to do to get joystick support enabled?
> I'm basically just trying to use a joystick with MAME
> to play those great old arcade games...
>
> All the documentation online is less than helpful, it
> seems. Anyone have a joystick working with Linux and
> MAME? Any tips would be greatly appreciated.
>
> Thanks,
> Mike
>
> --
> Michael J. Sherman
> http://stealthboy.com/
> http://221bakerstreet.org/
You're only using part of the necessary modules. In general, joystick.o
is the general support. Once this is in, you need a second module for
the specific. Analog joysticks use joy-analog.o after joystick.o. The
joystick you mention then requires joy-logitech.o (or at least I think
that is the one, it may have been renamed in later kernels, but is
probably correct for 2.2.x). To make things worse, there is a
possibility that the joystick port itself needs a module. For example,
the soundblaster live! uses the emu10k1 module for audio, but also
requires emu10k1-joy.o for the port, prior to ANY joystick modules (for
earlier kernels and emu10k1). Note that the joystick portion of emu10k1
has changed dramatically over the last year, so in that particular case,
the port supporting module may have a different name. Using an old
emu10k1 sblive port driver, and an analog joystick, the sequence would
go something like this:
insmod emu10k1-joy io=0x200
insmod joystick
insmod joy-analog
Often some information on items like joystick config can be found in
/usr/src/linux/Documentation/Changes, along with other files in the
Documentation directory of the kernel source.
D. Stimits, [EMAIL PROTECTED]
------------------------------
** 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
******************************
