Re: ALSA on nVidia board

2003-10-24 Thread linux-il
Hetz Ben Hamo wrote:
Hi,

If you have read the ALSA instructions - you really don't need to compile all 
the drivers - just PCI, and your driver that is needed..
I did this after getting tired from trying to guess which card I need,
I wasn't sure that it's the i810.
Could you supply please the output of /sbin/lspci please?
I attached a file below with the output of lspci -vvv (it's almost 200
lines).
Also, make it really matters HOW do you play the files - if with XMMS, then 
with aplay, as the document says.

BTW, I killed KDE's aRts daemon.

make sure you either using the ALSA driver in XMMS or if you use XMMS with 
I changed XMMS to use ALSA.  But I have afeeling the more basic aplay
is the way to test...
OSS drivers - the the snd-pcm-oss drivers are loaded to memory..

BTW: you better upgrade - the 0.9.8 got some bugs fixes (although still not 
for ALi 5451 - the shit chip inside IBM R40e notebooks..)
OK, will look for it.  I was just taking what's in Debian and until you
said so I though that 0.9.6 is the latest.
Thanks,
Hetz
Thank you,

--Amos
00:00.0 Host bridge: nVidia Corporation nForce2 AGP (different version?) (rev c1)
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- 
SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR-
Latency: 0
Region 0: Memory at d000 (32-bit, prefetchable) [size=64M]
Capabilities: [40] AGP version 2.0
Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- 
FW+ AGP3- Rate=x1,x2,x4
Command: RQ=1 ArqSz=0 Cal=0 SBA+ AGP+ GART64- 64bit- FW- Rate=x4
Capabilities: [60] #08 [2001]

00:00.1 RAM memory: nVidia Corporation nForce2 Memory Controller 1 (rev c1)
Subsystem: nVidia Corporation: Unknown device 0c17
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- 
SERR- FastB2B-
Status: Cap- 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR-

00:00.2 RAM memory: nVidia Corporation nForce2 Memory Controller 4 (rev c1)
Subsystem: nVidia Corporation: Unknown device 0c17
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- 
SERR- FastB2B-
Status: Cap- 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR-

00:00.3 RAM memory: nVidia Corporation nForce2 Memory Controller 3 (rev c1)
Subsystem: nVidia Corporation: Unknown device 0c17
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- 
SERR- FastB2B-
Status: Cap- 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR-

00:00.4 RAM memory: nVidia Corporation nForce2 Memory Controller 2 (rev c1)
Subsystem: nVidia Corporation: Unknown device 0c17
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- 
SERR- FastB2B-
Status: Cap- 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR-

00:00.5 RAM memory: nVidia Corporation nForce2 Memory Controller 5 (rev c1)
Subsystem: nVidia Corporation: Unknown device 0c17
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- 
SERR- FastB2B-
Status: Cap- 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR-

00:01.0 ISA bridge: nVidia Corporation nForce2 ISA Bridge (rev a4)
Subsystem: Giga-byte Technology: Unknown device 0c11
Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- 
SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR-
Latency: 0
Capabilities: [48] #08 [01e1]

00:01.1 SMBus: nVidia Corporation nForce2 SMBus (MCP) (rev a2)
Subsystem: Giga-byte Technology: Unknown device 0c11
Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- 
SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR-
Interrupt: pin A routed to IRQ 5
Region 0: I/O ports at c000 [size=32]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:02.0 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4) (prog-if 10 
[OHCI])
Subsystem: Giga-byte Technology: Unknown device 5004
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- 
SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR-
Latency: 0 (750ns min, 250ns max)
Interrupt: pin A routed to IRQ 11
Region 0: Memory at e0003000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [44] Power Management version 2
Flags: 

Re: Error code from a shell pipeline.

2003-10-24 Thread Beni Cherniavsky
Shlomi Fish wrote on 2003-10-12:

 I want that if one of the (first) components of the pipeline exits with an
 error code, I'll know about it somehow. How?

info bash --index PIPESTATUS

$ true | false | true | false; echo [EMAIL PROTECTED]
0 1 0 1
$ { true | false | true | false; }; echo [EMAIL PROTECTED]
0 1 0 1

However, using parenthesis you launch the whole pipeline in a subshell
so it won't work:

$ ( true | false | true | false; ); echo [EMAIL PROTECTED]
1

Also, it mysteriously seems to be lost after every command in
interactive mode:

$ true | false | true | false
$ echo [EMAIL PROTECTED]
0

Although it does work in non-interactive mode:

$ echo $'true | false | true | false\necho [EMAIL PROTECTED]' | sh
0 1 0 1

If you want a less fragile approach, Oded Arbel gave a good advice.

-- 
Beni Cherniavsky [EMAIL PROTECTED]


=
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word unsubscribe in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]



Re: Error code from a shell pipeline.

2003-10-24 Thread Shlomi Fish
On Fri, 24 Oct 2003, Beni Cherniavsky wrote:

 Shlomi Fish wrote on 2003-10-12:

  I want that if one of the (first) components of the pipeline exits with an
  error code, I'll know about it somehow. How?
 
 info bash --index PIPESTATUS


Cool thanks.

 $ true | false | true | false; echo [EMAIL PROTECTED]
 0 10 1
 $ { true | false | true | false; }; echo [EMAIL PROTECTED]
 0 1 0 1

 However, using parenthesis you launch the whole pipeline in a subshell
 so it won't work:

 $ ( true | false | true | false; ); echo [EMAIL PROTECTED]
 1

 Also, it mysteriously seems to be lost after every command in
 interactive mode:

 $ true | false | true | false
 $ echo [EMAIL PROTECTED]
 0


Works for me:

shlomi:~$ true | false | false | true
shlomi:~$ echo [EMAIL PROTECTED]
0 1 1 0

Maybe you execute some command after every prompt.

 Although it does work in non-interactive mode:

 $ echo $'true | false | true | false\necho [EMAIL PROTECTED]' | sh
 0 1 0 1


Wow, I wasn't aware of the $'' construct. I guess you learn something new
every day. :-)

 If you want a less fragile approach, Oded Arbel gave a good advice.


This approach is also dependent on the user shell being bash. I am using
this shell call from a Perl script. In any case, I eliminated the pipeline
from the command and now this is no longer relevant.

Thanks anyway.

Regards,

Shlomi Fish


--
Shlomi Fish[EMAIL PROTECTED]
Home Page: http://t2.technion.ac.il/~shlomif/

Writing a BitKeeper replacement is probably easier at this point than getting
its license changed.

Matt Mackall on OFTC.net #offtopic.


=
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word unsubscribe in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]



Proposing lecturing activism

2003-10-24 Thread Ian
Peace, Linux lovers!

I'm hereby offering to give free/open lectures/series/courses on
a variety
of topics... with the proviso that the community (that's you!)
help make
this have an impact on Linux/FLOSS adoption locally. Right?!

I'm a professional, avid lecturer, with years of experience in
the training
industry, and over 20 years of programming... and militant on
free
software. (And, BTW, looking for work -- your help most
appreciated! :o)

The _least_ I'd expect is help in getting a crowd (and I mean _a
crowd_)
show up. And I mean newbies (!), business people... any potential
Linux
converts who could use a push. (I disagree with Jonathan: Linux
advocacy
in IL ain't over -- quite the opposite!)

Tentative offerings:
1. Web applications development (see below)
2. Security (for fun and profit; see below)
3. Python vs other PLs (for programmers... and language lawyers
:o)

Topics I'd need help with/love to help others with:
4. Unix haters (for advanced admins; bring protective gear and
iodine)
5. Symposium on taking over the Israeli OS market: advice from
marketing strategists and stories from the trenches
6. Continental philosophy... oops! off topic, just kidding

et cetera.

Oh, and of course I'd love to assist anyone with their own
lectures, with
didactics, syllabi construction, brain-storming... lots of free
advice :o).


I hope Hamakor will take this up. And seriously.


Details?
Really, off the top of my head, mere suggestions (your feedback
requested):


=Web applications development=

A thorough, in-depth coverage of the technologies, the
life-cycle, and
meta issues. (Maybe a full course, or workshop, and actually
building a
_real-world_ site!)

1. Web technologies: the standards (IETF, W3C), accessibility
(UAAG,
i18n...), CGI/FCGI/Apache mods/HTTP servers, caching, hosting,
virtual
hosting, etc.

2. Software engineering: programming languages (dis/advantages,
fitness to purpose, experiences), Web app frameworks/tools,
life-cycle
aspects (testing, adaptivity...), data modeling, quality of
service aspects
(confirmability, robustness...), etc.

3. Implementation: systems architecture (load balancing,
middleware...),
OO, persistence and pervasive paradigm, high availability.

4. Slandering Micrapsoft, pushing penguins and friends. :o)

5. Lively discussion (read: flaming), forking, early releases --
to take
home! (Really, let's build a real(ly good) one! Python, Java...
no PHP!)


=Security=

For the curious, the paranoid, the inventive, and the
pragmatists...
probably not for script-kiddies.

1. History: overview of how infosec/infowar began, phreaking,
hacking,
cracking... Approaching Zero, The Hacker Crackdown,
Underground,
technoculture studies, free software activism, government reports
(CyberCrime, Echelon...), and so on.

2. White hats: case studies, approaches to infosec (risk
management;
defense-in-depth), standards (ISO Common Criteria...), permission
models (Bell-LaPadula, etc, expert systems)... sniffing,
snooping,
spoofing, snorting, scrubbing... and Satan and the Angels, too!

3. Black hats... (think so?)

4. Future: research directions, interesting stuff...

5. Micrapsoft slandering no end! And, sure enough, pushing
penguins
and friends. :o)


And so on.

I can conjure up more, if there are takers.
Speak up!


-- Ilan
iajava(at)yahoo.com
08-946.4468



__
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com

=
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word unsubscribe in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]



Re: Error code from a shell pipeline.

2003-10-24 Thread Oleg Goldshmidt
Shlomi Fish [EMAIL PROTECTED] writes:

 On Fri, 24 Oct 2003, Beni Cherniavsky wrote:
 
  Shlomi Fish wrote on 2003-10-12:
 
   I want that if one of the (first) components of the pipeline exits with an
   error code, I'll know about it somehow. How?
  
  info bash --index PIPESTATUS
 
 
 Cool thanks.

Depending on your needs you may also use the -e option to the shell
(should work for most Bourne shell and csh descendants), the option
will make the shell exit if any of the commands in the pipeline fails.

$ true | false | true
$ echo $?
0
$ bash -e true | false | true
true | false | true: true | false | true: No such file or directory
$ echo $?
1

-- 
Oleg Goldshmidt | [EMAIL PROTECTED]

=
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word unsubscribe in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]



Re: Error code from a shell pipeline.

2003-10-24 Thread Tzafrir Cohen
On Fri, Oct 24, 2003 at 10:47:22PM +0200, Oleg Goldshmidt wrote:
 Shlomi Fish [EMAIL PROTECTED] writes:
 
  On Fri, 24 Oct 2003, Beni Cherniavsky wrote:
  
   Shlomi Fish wrote on 2003-10-12:
  
I want that if one of the (first) components of the pipeline exits with an
error code, I'll know about it somehow. How?
   
   info bash --index PIPESTATUS
  
  
  Cool thanks.
 
 Depending on your needs you may also use the -e option to the shell
 (should work for most Bourne shell and csh descendants), the option
 will make the shell exit if any of the commands in the pipeline fails.
 
 $ true | false | true
 $ echo $?
 0
 $ bash -e true | false | true
 true | false | true: true | false | true: No such file or directory
 $ echo $?
 1

This is because you tried running a script from a file called
true | false | true

However:

$ set -e
$ true | false | true
$ echo $?
0

So setting that doesn't make an error from the middle of a pipe show.

-- 
Tzafrir Cohen   +---+
http://www.technion.ac.il/~tzafrir/ |vim is a mutt's best friend|
mailto:[EMAIL PROTECTED]   +---+

=
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word unsubscribe in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]