ALSA help!

2005-05-31 Thread Douglas
I am runnung debian sarge on a really old HP OmniBook 4150. soundcard is NeoMagic 256 lsmod yields: snd_seq_dummy 2692 0 snd_seq48368 1 snd_seq_dummy snd_seq_device 7116 2 snd_seq_dummy,snd_seq snd_pcm_oss48288 0 snd_mixer_oss 17472 1 s

Natural medicine for the New Millennium.

2005-05-31 Thread Frank
Natural medicine for the New Millennium. http://vbcmazh.85b1c9815iqyurq.anguid78m7.com Men for the sake of getting a living forget to live. Who so loves believes the impossible. Bibo, ergo sum. - I drink, therefore I am -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subje

Re: OSS community interaction (was: Re: *** bluber *** Re: Male xxxxxx enhancement formula^)

2005-05-31 Thread Chris Bannister
On Mon, May 30, 2005 at 01:48:34AM -0700, Ian Greenhoe wrote: > On Mon, 2005-05-30 at 16:35 +1200, Chris Bannister wrote: > > > A C/R system on a mailing list? Please don't even consider it. > > Other suggestions are welcome. Please contribute some. If you have > something better that challenge

Re: OSS community interaction (was: Re: *** bluber *** Re: Male xxxxxx enhancement formula^)

2005-05-31 Thread Derek Broughton
On Tuesday 31 May 2005 08:10, Chris Bannister wrote: > On Mon, May 30, 2005 at 01:48:34AM -0700, Ian Greenhoe wrote: > > On Mon, 2005-05-30 at 16:35 +1200, Chris Bannister wrote: > > > > > > > A C/R system on a mailing list? Please don't even consider it. > > > > Other suggestions are welcome. Pl

codec_semaphore: semaphore is not ready (ALSA)

2005-05-31 Thread Johan Holmqvist
What could be done for this error in the syslog? May 31 16:09:59 localhost kernel: codec_semaphore: semaphore is not ready [0x1][0x701300] May 31 16:09:59 localhost kernel: codec_write 1: semaphore is not ready for register 0x54 This seems to have to do with the ALSA driver (snd_intel8x0) if you

Re: ALSA help!

2005-05-31 Thread Koen Vermeer
I'm honestly not trying to be an ass, but this is all the help I can give for now: I searched for 'omnibook 4150 alsa' in google. Look at the first hit, and try that. Consider reporting the results here. Koen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble

New toshutils package

2005-05-31 Thread Roberto C. Sanchez
Please CC me or reply directly as I am not on debian-laptop. I have recently taken over maintaing the toshutils package. I have patched it to use GTK2 instead of GTK+ (this was a personal pieve of mine for a long time). There should be no functional impact on the operation of the program, but I

Re: Grabadora en Linux

2005-05-31 Thread Jhosue Rui
El 19/05/05, Carlos Martínez Fernández<[EMAIL PROTECTED]> escribió: > Hola todos, hola > > He instalado Ubuntu 5 en el portátil y no he tenido ningún problema con > el hw salvo la grabadora. Instalé el xcdroast y el gcombust y ambos me > dicen que no tengo ningún dispositivo SCSI y, por tanto, no

Re: New toshutils package

2005-05-31 Thread Frans Pop
On Tuesday 31 May 2005 19:03, Roberto C. Sanchez wrote: > I am also taking over the toshset package and am preparing an update > for it with a new upstream version that supports some of the ACPI > funcitonality of the newer Toshiba laptops. If you are interested in > helping me to test the new ver

Re: New toshutils package

2005-05-31 Thread Roberto C. Sanchez
On Tue, May 31, 2005 at 07:19:27PM +0200, Frans Pop wrote: > On Tuesday 31 May 2005 19:03, Roberto C. Sanchez wrote: > > I am also taking over the toshset package and am preparing an update > > for it with a new upstream version that supports some of the ACPI > > funcitonality of the newer Toshiba

Debian Sarge + madwifi : cannot bring up interface ath0

2005-05-31 Thread Dominique Orban
Hello, I am running Debian Sarge on a Pentium 4 laptop with kernels 2.6.8-2-386, 2.6.8-2-686 and 2.6.8-2-686-smp. My difficulties with wireless networking are identical with all three kernels. I apologize in advance if this message is a bit long; I hope to provide useful diagnostics. I have a Net

Re: ALSA help!

2005-05-31 Thread Douglas
I have tried that. His problem was that ALSA would not start. My issue seems to be that it is running but for some reason my system believes that /dev/dsp is inaccessible and that I have no sound device installed at all, Alsaconf completes but displays : /usr/sbin/alsactl: load_state:1236: N

Re: Debian Sarge + madwifi : cannot bring up interface ath0

2005-05-31 Thread Robert Goley
It sounds like the driver for the wireless card is not loaded or that the card you are using is not a Atheros based card. I am using several Atheros based cards with those kernels. Try typing "modprobe ath_pci" before typing "ifup ath0". If it works, you may need to at ath_pci to the /etc/module

Brand New Penis Enhancement Product

2005-05-31 Thread Jake
No more penis enlarge ripoffs! http://www.jnaz.net/ss/ Laugh and the world laughs with you, snore and you sleep alone. [End of diatribe. We now return you to your regularly scheduled programming...] Tempt not a desperate man. To err is human; to forgive is simply not our policy By

Re: Debian Sarge + madwifi : cannot bring up interface ath0

2005-05-31 Thread Dominique Orban
On 31 May 2005 14:04:29 -0400, Robert Goley <[EMAIL PROTECTED]> wrote: > It sounds like the driver for the wireless card is not loaded or that > the card you are using is not a Atheros based card. I am using several > Atheros based cards with those kernels. Try typing "modprobe ath_pci" > before

Re: ALSA help!

2005-05-31 Thread Koen Vermeer
Strange. Your ALSA is saying that it cannot find a soundcard. He is saying that you shouldn't use the nm256 driver. So, if you are using the nm256 driver, and he (and others) are saying that you need another driver to get a working setup, I'm not surprised that your ALSA config cannot find a soundc

Re: ALSA help!

2005-05-31 Thread Derek Broughton
On Tuesday 31 May 2005 14:42, Douglas wrote: > I have tried that. His problem was that ALSA would not start. My issue > seems to be that it is running but for some reason my system believes > that /dev/dsp is inaccessible and that I have no sound device installed > at all, Alsaconf completes but

Re: Debian Sarge + madwifi : cannot bring up interface ath0

2005-05-31 Thread Robert Goley
What is the output of "ifup ath0" after you have manually  typed "modprobe ath0"?  That is the only thing your should have to use modprobe on.  The rest are loaded as dependancies when you load them using modprobe.  Try using Kwifi to see if the car is scanning and finding anything also.  Let m

Re: Debian Sarge + madwifi : cannot bring up interface ath0

2005-05-31 Thread Ryan Nowakowski
On Tue, May 31, 2005 at 12:52:40PM -0400, Dominique Orban wrote: [snip] > I have a Netgear WG511T PCMCIA wireless adapter. It has an Atheros > chipset and thus I use madwifi. I am having difficulties bringing the > interface up. I initially had the ethernet port eth0 defined as 'auto' > in /etc/net

Re: Debian Sarge + madwifi : cannot bring up interface ath0

2005-05-31 Thread Andrew McMillan
On Tue, 2005-05-31 at 12:52 -0400, Dominique Orban wrote: > > Regarding the wireless card, I installed the madwifi drivers, loaded > the modules, but 'ifup ath0' gives: > > % ifup ath0 > Error for wireless request "Set ESSID" (8B1A) : Hi Dominique, Does your ESSID have spaces or other less usua

Re: New toshutils package

2005-05-31 Thread Frans Pop
On Tuesday 31 May 2005 19:26, Roberto C. Sanchez wrote: > If you have the toshiba_acpi driver [0] loaded into your kernel or > compiled in (note that it is already included in recent 2.4 and 2.6 > kernels), then newer versions of toshset should work. > [0] http://memebeam.org/toys/ExperimentalTosh

Re: Debian Sarge + madwifi : cannot bring up interface ath0

2005-05-31 Thread Dominique Orban
On 31 May 2005 15:13:34 -0400, Robert Goley <[EMAIL PROTECTED]> wrote: > What is the output of "ifup ath0" after you have manually typed > "modprobe ath0"? That is the only thing your should have to use > modprobe on. The rest are loaded as dependancies when you load them > using modprobe. Try

Re: Debian Sarge + madwifi : cannot bring up interface ath0

2005-05-31 Thread Robert Goley
On Tue, 2005-05-31 at 17:13, Dominique Orban wrote: On 31 May 2005 15:13:34 -0400, Robert Goley <[EMAIL PROTECTED]> wrote: > What is the output of "ifup ath0" after you have manually typed > "modprobe ath0"? That is the only thing your should have to use > modprobe on. The rest are loaded

Re: Debian Sarge + madwifi : cannot bring up interface ath0

2005-05-31 Thread Dominique Orban
Hello Andrew, On 5/31/05, Andrew McMillan <[EMAIL PROTECTED]> wrote: > On Tue, 2005-05-31 at 12:52 -0400, Dominique Orban wrote: > > > > Regarding the wireless card, I installed the madwifi drivers, loaded > > the modules, but 'ifup ath0' gives: > > > > % ifup ath0 > > Error for wireless request

Re: New toshutils package

2005-05-31 Thread Roberto C. Sanchez
On Tue, May 31, 2005 at 10:19:20PM +0200, Frans Pop wrote: > On Tuesday 31 May 2005 19:26, Roberto C. Sanchez wrote: > > If you have the toshiba_acpi driver [0] loaded into your kernel or > > compiled in (note that it is already included in recent 2.4 and 2.6 > > kernels), then newer versions of to

Re: New toshutils package

2005-05-31 Thread Frans Pop
On Wednesday 01 June 2005 00:41, Roberto C. Sanchez wrote: > I am using only a Debian provided kernel-source package from Sarge. > I compile own, though. Are you using a kernel-image directly from > Debian? No, I have exactly the same (self-compiled kernel based on Debian kernel-source with CONF

Re: New toshutils package

2005-05-31 Thread Roberto C. Sanchez
On Wed, Jun 01, 2005 at 01:53:05AM +0200, Frans Pop wrote: > On Wednesday 01 June 2005 00:41, Roberto C. Sanchez wrote: > > I am using only a Debian provided kernel-source package from Sarge. > > I compile own, though. Are you using a kernel-image directly from > > Debian? > > No, I have exactly

Re: Debian Sarge + madwifi : cannot bring up interface ath0

2005-05-31 Thread Andrew McMillan
On Tue, 2005-05-31 at 17:23 -0400, Dominique Orban wrote: > > > You should be able to issue the commands that ifup does manually, like > > so: > > > > ifconfig ath0 up > > iwconfig ath0 essid "your ss id" > > dhclient ath0 > > > > ... and it would seem likely that the problem is occurring in the