Re: [GnomeMeeting-list] Re: GnomeMeeting-list digest, Vol 1 #914 - 9 msgs
- From: Damien Sandras <dsandras seconix com>
- To: gnomemeeting-list gnome org
- Subject: Re: [GnomeMeeting-list] Re: GnomeMeeting-list digest, Vol 1 #914 - 9 msgs
- Date: Tue, 04 Nov 2003 22:08:55 +0100
Le mar 04/11/2003 à 20:55, Costin a écrit :
> My GnomeMeeting is 0.96.0.
>
You shoudl really upgrade it!
> Costin
> ----- Original Message -----
> From: <gnomemeeting-list-request gnome org>
> To: <gnomemeeting-list gnome org>
> Sent: Tuesday, November 04, 2003 12:00 PM
> Subject: GnomeMeeting-list digest, Vol 1 #914 - 9 msgs
>
>
> > Send GnomeMeeting-list mailing list submissions to
> > gnomemeeting-list gnome org
> >
> > To subscribe or unsubscribe via the World Wide Web, visit
> > http://mail.gnome.org/mailman/listinfo/gnomemeeting-list
> > or, via email, send a message with subject or body 'help' to
> > gnomemeeting-list-request gnome org
> >
> > You can reach the person managing the list at
> > gnomemeeting-list-admin gnome org
> >
> > When replying, please edit your Subject line so it is more specific
> > than "Re: Contents of GnomeMeeting-list digest..."
> >
> >
> > Today's Topics:
> >
> > 1. (no subject) (Costin)
> > 2. Re: (no subject) (Damien Sandras)
> > 3. Re: GnomeMeeting crash (Anne Wilson)
> > 4. re: snd-via82xx full-duplex (Alien999999999)
> > 5. Re: GnomeMeeting crash (Damien Sandras)
> > 6. Re: re: snd-via82xx full-duplex (Damien Sandras)
> > 7. Re: GnomeMeeting crash (Anne Wilson)
> > 8. Re: re: snd-via82xx full-duplex (Maarten Vanraes)
> > 9. Re: re: snd-via82xx full-duplex (Damien Sandras)
> >
> > --__--__--
> >
> > Message: 1
> > From: "Costin" <costinm1 verizon net>
> > To: <gnomemeeting-list gnome org>
> > Cc: <dsandras seconix com>
> > Date: Tue, 4 Nov 2003 10:29:38 -0500
> > Subject: [GnomeMeeting-list] (no subject)
> > Reply-To: gnomemeeting-list gnome org
> >
> > This is a multi-part message in MIME format.
> >
> > ------=_NextPart_000_0070_01C3A2BE.8C927400
> > Content-Type: text/plain;
> > charset="iso-8859-1"
> > Content-Transfer-Encoding: quoted-printable
> >
> > I have another endpoint registered at 192.168.0.2 That is a Netmeeting. =
> > 192.168.0.1 is the Ip address of the server Ethernet card where =
> > 192.168.0.2 is connected to. GnomeMeeting is on the server. (Linux =
> > RedHat).
> >
> > Do you know how I could force GnomeMeeting to use a different IP address =
>
> > as a resource?
> >
> > Costin
> >
> >
> > Subject: Re: [GnomeMeeting-list] (no subject)
> > From: Damien Sandras <>
> > To: gnomemeeting-list gnome org
> > Date: Tue, 04 Nov 2003 13:11:49 +0100
> > Reply-To:=20
> > Le mar 04/11/2003 =E0 13:06, Costin a =E9crit :
> > > =20
> > > Damien,
> > > =20
> > > Thans for you advice. I tried applying your sugestion and is not
> > > working. I still get adminssion reject. It seems that there is problem
> > > with IP-s. GnomeMeeting is using as resource IP 192.168.0.1 The same
> > > IP is used also by a network card adapter. It might be a conflict
> > > here......
> > > =20
> >
> > GnomeMeeting will use your IP to register, you can not force it spoofing
> > IP's.=20
> >
> > Is there another endpoint registered with that 192.168.0.1 IP to the
> > gatekeeper? Is it the 0.98.5 version?
> >
> >
> > ------=_NextPart_000_0070_01C3A2BE.8C927400
> > Content-Type: text/html;
> > charset="iso-8859-1"
> > Content-Transfer-Encoding: quoted-printable
> >
> > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
> > <HTML><HEAD>
> > <META http-equiv=3DContent-Type content=3D"text/html; =
> > charset=3Diso-8859-1">
> > <META content=3D"MSHTML 6.00.2800.1264" name=3DGENERATOR>
> > <STYLE></STYLE>
> > </HEAD>
> > <BODY bgColor=3D#ffffff>
> > <DIV><FONT face=3DArial size=3D2>I have another endpoint registered at =
> > 192.168.0.2=20
> > That is a Netmeeting. 192.168.0.1 is the Ip address of the server =
> > Ethernet card=20
> > where 192.168.0.2 is connected to. GnomeMeeting is on the server. (Linux =
> >
> > RedHat).</FONT></DIV>
> > <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> > <DIV><FONT face=3DArial size=3D2>Do you know how I could force =
> > GnomeMeeting to use a=20
> > different IP address as a resource?</FONT></DIV>
> > <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> > <DIV><FONT face=3DArial size=3D2>Costin</FONT></DIV>
> > <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> > <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> > <DIV>Subject: Re: [GnomeMeeting-list] (no subject)<BR>From: Damien =
> > Sandras=20
> > <><BR>To: <A=20
> > href=3D"mailto:gnomemeeting-list gnome org">gnomemeeting-list gnome org</=
> > A><BR>Date:=20
> > Tue, 04 Nov 2003 13:11:49 +0100<BR>Reply-To: <BR>Le mar 04/11/2003 =E0 =
> > 13:06,=20
> > Costin a =E9crit :<BR>> <BR>> Damien,<BR>> <BR>> =
> > Thans for=20
> > you advice. I tried applying your sugestion and is not<BR>> working. =
> > I still=20
> > get adminssion reject. It seems that there is problem<BR>> with IP-s. =
> >
> > GnomeMeeting is using as resource IP 192.168.0.1 The =
> > same<BR>> IP=20
> > is used also by a network card adapter. It might be a conflict<BR>>=20
> > here......<BR>> <BR><BR>GnomeMeeting will use your IP to =
> > register, you=20
> > can not force it spoofing<BR>IP's. <BR><BR>Is there another endpoint =
> > registered=20
> > with that 192.168.0.1 IP to the<BR>gatekeeper? Is it the 0.98.5=20
> > version?<BR><BR></DIV></BODY></HTML>
> >
> > ------=_NextPart_000_0070_01C3A2BE.8C927400--
> >
> >
> >
> > --__--__--
> >
> > Message: 2
> > Subject: Re: [GnomeMeeting-list] (no subject)
> > From: Damien Sandras <dsandras seconix com>
> > To: gnomemeeting-list gnome org
> > Date: Tue, 04 Nov 2003 16:33:09 +0100
> > Reply-To: gnomemeeting-list gnome org
> >
> > Le mar 04/11/2003 à 16:29, Costin a écrit :
> > > I have another endpoint registered at 192.168.0.2 That is a
> > > Netmeeting. 192.168.0.1 is the Ip address of the server Ethernet card
> > > where 192.168.0.2 is connected to. GnomeMeeting is on the server.
> > > (Linux RedHat).
> > >
> > > Do you know how I could force GnomeMeeting to use a different IP
> > > address as a resource?
> >
> > That's not possible yet.
> >
> > >
> > > Costin
> > >
> > >
> > > Subject: Re: [GnomeMeeting-list] (no subject)
> > > From: Damien Sandras <>
> > > To: gnomemeeting-list gnome org
> > > Date: Tue, 04 Nov 2003 13:11:49 +0100
> > > Reply-To:
> > > Le mar 04/11/2003 à 13:06, Costin a écrit :
> > > >
> > > > Damien,
> > > >
> > > > Thans for you advice. I tried applying your sugestion and is not
> > > > working. I still get adminssion reject. It seems that there is
> > > problem
> > > > with IP-s. GnomeMeeting is using as resource IP 192.168.0.1 The
> > > same
> > > > IP is used also by a network card adapter. It might be a conflict
> > > > here......
> > > >
> > >
> > > GnomeMeeting will use your IP to register, you can not force it
> > > spoofing
> > > IP's.
> > >
> > > Is there another endpoint registered with that 192.168.0.1 IP to the
> > > gatekeeper? Is it the 0.98.5 version?
> > --
> > _ Damien Sandras
> > (o-
> > //\ It-Optics s.a.
> > v_/_ GnomeMeeting: http://www.gnomemeeting.org/
> > FOSDEM 2004: http://www.fosdem.org
> > H.323 phone: callto:ils.seconix.com/dsandras seconix com
> >
> >
> > --__--__--
> >
> > Message: 3
> > From: Anne Wilson <cannewilson tiscali co uk>
> > To: gnomemeeting-list gnome org
> > Subject: Re: [GnomeMeeting-list] GnomeMeeting crash
> > Date: Tue, 4 Nov 2003 15:35:23 +0000
> > Reply-To: gnomemeeting-list gnome org
> >
> > On Tuesday 04 Nov 2003 12:23 pm, Damien Sandras wrote:
> > > Le mar 04/11/2003 =E0 13:14, Anne Wilson a =E9crit :
> > > > I tried to do just that, but couldn't get it to work properly, so
> > > > I rebooted. Now I have lost /dev/v4l ! I'm going to urpme v4l
> > > > and reinstall it. I'll let you know what happens.
> > >
> > > Just modprobe webcam modules and it should reappear. That is the
> > > Mandrake hardware detection tool that probably failed.
> > >
> > I'm afraid it is worse than that, Damien. I found that I had lost all=20
> > use of the usb hub, and indeed all usb directly connected. I=20
> > strongly suspect that the pwcx module is not compatible with the=20
> > win4lin patch.
> >
> > I have booted to an unpatched kernel, run a manual insmod and found=20
> > that GnomeMeeting runs fine (and other usb equipment is recognised). =20
> > However, I now can't get back into my Win4Lin patched kernel. I took=20
> > the insmod line out of modules.conf, but during bootup I am still=20
> > seeing
> >
> > finding module dependencies: depmod: ***Unresolved symbols in=20
> > /lib/modules/2.4.21-0.13mdk/misc/pwcx-2.4.20.o
> >
> > At the point of probing for hardware the system freezes.
> >
> > How can I get rid of this altogether in this kernel? I'll use the=20
> > other one when I want to run GnomeMeeting, but I need the Win4Lin=20
> > from time to time.
> >
> > If there is anything I can do to help you get information you=20
> > want/need for future use, please tell me, as well as how to solve my=20
> > pressing problem. Thanks
> >
> > Anne
> > =2D-=20
> > Registered Linux User No.293302
> > Have you visited http://twiki.mdklinuxfaq.org yet?
> >
> >
> > --__--__--
> >
> > Message: 4
> > From: Alien999999999 <alien999999999 users sourceforge net>
> > To: gnomemeeting-list gnome org
> > Date: Tue, 4 Nov 2003 16:44:15 +0100
> > Subject: [GnomeMeeting-list] re: snd-via82xx full-duplex
> > Reply-To: gnomemeeting-list gnome org
> >
> > =2D----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > I have tried the druid, that was the first thing I did.
> > i only have /dev/sound/dsp
> > I have oss modules loaded:
> >
> > lsmod:
> > snd-seq-oss 32000 0 (unused)
> > snd-seq-midi-event 6080 0 [snd-seq-oss]
> > snd-seq 42544 2 [snd-seq-oss snd-seq-midi-event]
> > snd-pcm-oss 43652 0
> > snd-mixer-oss 14200 0 [snd-pcm-oss]
> > snd-via82xx 15360 4
> > snd-pcm 79588 3 [snd-pcm-oss snd-via82xx]
> > snd-timer 18436 0 [snd-seq snd-pcm]
> > snd-ac97-codec 45752 0 [snd-via82xx]
> > snd-page-alloc 9044 0 [snd-via82xx snd-pcm]
> > snd-mpu401-uart 4704 0 [snd-via82xx]
> > snd-rawmidi 17760 0 [snd-mpu401-uart]
> > snd-seq-device 5832 0 [snd-seq-oss snd-seq snd-rawmidi]
> > snd 41380 1 [snd-seq-oss snd-seq-midi-event
> snd-seq=20
> > snd-pcm-oss snd-mixer-oss snd-via82xx snd-pcm snd-timer snd-ac97-codec=20
> > snd-mpu401-uart snd-rawmidi snd-seq-device]
> > soundcore 6340 0 [snd]
> >
> >
> > again, my question, how do i check if it is full-duplex? and how do I
> turn=
> > =20
> > that on?
> >
> > =2D --
> > Alien is my name and headbiting is my game.
> > pgp keys: http://users.pandora.be/Alien999999999/public_keys.gpg
> >
> > =2D----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.2.3 (GNU/Linux)
> >
> > iD8DBQE/p8lPuBWKXETrtdcRAggxAJ40waeW25SHSyZPQr0iteo4pEU/gQCgq2A4
> > jxQ04+MzOqC84uY0O15OaqY=3D
> > =3DlB8F
> > =2D----END PGP SIGNATURE-----
> >
> >
> > --__--__--
> >
> > Message: 5
> > Subject: Re: [GnomeMeeting-list] GnomeMeeting crash
> > From: Damien Sandras <dsandras seconix com>
> > To: gnomemeeting-list gnome org
> > Date: Tue, 04 Nov 2003 16:58:52 +0100
> > Reply-To: gnomemeeting-list gnome org
> >
> > Le mar 04/11/2003 à 16:35, Anne Wilson a écrit :
> > > I'm afraid it is worse than that, Damien. I found that I had lost all
> > > use of the usb hub, and indeed all usb directly connected. I
> > > strongly suspect that the pwcx module is not compatible with the
> > > win4lin patch.
> >
> > Even if it is the case, it shouldn't break your hardware. I don't know
> > exactly what the Win4lin patches are doing however.
> >
> > >
> > > I have booted to an unpatched kernel, run a manual insmod and found
> > > that GnomeMeeting runs fine (and other usb equipment is recognised).
> > > However, I now can't get back into my Win4Lin patched kernel. I took
> > > the insmod line out of modules.conf, but during bootup I am still
> > > seeing
> > >
> > > finding module dependencies: depmod: ***Unresolved symbols in
> > > /lib/modules/2.4.21-0.13mdk/misc/pwcx-2.4.20.o
> > >
> >
> > Did Mandrake copy it elsewhere?
> >
> > > At the point of probing for hardware the system freezes.
> > >
> > > How can I get rid of this altogether in this kernel? I'll use the
> > > other one when I want to run GnomeMeeting, but I need the Win4Lin
> > > from time to time.
> > >
> >
> > That's a question for Mandrake support, or perhaps any other Mandrake
> > user here can help you.
> >
> > > If there is anything I can do to help you get information you
> > > want/need for future use, please tell me, as well as how to solve my
> > > pressing problem. Thanks
> > >
> >
> > I think the problem is solved as it "seems" to work with the unpatched
> > kernel, we have the proof that the problem was the patched kernel.
> > However, if you have problems with the unpatched kernel too, then
> > recontact me.
> >
> > Now for the Mandrake problem, I'm not the right person to help you. Just
> > do the reverse steps of what you did to automatically insert pwcx.
> >
> > > Anne
> > --
> > _ Damien Sandras
> > (o-
> > //\ It-Optics s.a.
> > v_/_ GnomeMeeting: http://www.gnomemeeting.org/
> > FOSDEM 2004: http://www.fosdem.org
> > H.323 phone: callto:ils.seconix.com/dsandras seconix com
> >
> >
> > --__--__--
> >
> > Message: 6
> > Subject: Re: [GnomeMeeting-list] re: snd-via82xx full-duplex
> > From: Damien Sandras <dsandras seconix com>
> > To: gnomemeeting-list gnome org
> > Date: Tue, 04 Nov 2003 16:59:56 +0100
> > Reply-To: gnomemeeting-list gnome org
> >
> > Le mar 04/11/2003 à 16:44, Alien999999999 a écrit :
> > >
> > > again, my question, how do i check if it is full-duplex? and how do I
> turn
> > > that on?
> >
> > With the druid. Also do an lsof /dev/dsp to see if no other software is
> > using the device, causing the failure.
> >
> > There is no way to turn full-duplex on / off.
> > --
> > _ Damien Sandras
> > (o-
> > //\ It-Optics s.a.
> > v_/_ GnomeMeeting: http://www.gnomemeeting.org/
> > FOSDEM 2004: http://www.fosdem.org
> > H.323 phone: callto:ils.seconix.com/dsandras seconix com
> >
> >
> > --__--__--
> >
> > Message: 7
> > From: Anne Wilson <cannewilson tiscali co uk>
> > To: gnomemeeting-list gnome org
> > Subject: Re: [GnomeMeeting-list] GnomeMeeting crash
> > Date: Tue, 4 Nov 2003 16:06:42 +0000
> > Reply-To: gnomemeeting-list gnome org
> >
> > On Tuesday 04 Nov 2003 3:58 pm, Damien Sandras wrote:
> > > Le mar 04/11/2003 =E0 16:35, Anne Wilson a =E9crit :
> > > > I'm afraid it is worse than that, Damien. I found that I had
> > > > lost all use of the usb hub, and indeed all usb directly
> > > > connected. I strongly suspect that the pwcx module is not
> > > > compatible with the win4lin patch.
> > >
> > > Even if it is the case, it shouldn't break your hardware. I don't
> > > know exactly what the Win4lin patches are doing however.
> > >
> > It hasn't broken the hardware - just the ability to recognise them. =20
> > The same hardware is working without problems on the unpatched=20
> > kernel.
> >
> > > > How can I get rid of this altogether in this kernel? I'll use
> > > > the other one when I want to run GnomeMeeting, but I need the
> > > > Win4Lin from time to time.
> > >
> > > That's a question for Mandrake support, or perhaps any other
> > > Mandrake user here can help you.
> > >
> > =46air enough - I'll ask them.
> >
> > > > If there is anything I can do to help you get information you
> > > > want/need for future use, please tell me, as well as how to solve
> > > > my pressing problem. Thanks
> > >
> > > I think the problem is solved as it "seems" to work with the
> > > unpatched kernel, we have the proof that the problem was the
> > > patched kernel.=20
> >
> > So it seems to me - at least you'll know to advise against running it=20
> > on a win4lin patched kernel.
> >
> > > However, if you have problems with the unpatched
> > > kernel too, then recontact me.
> > >
> > Will do.
> >
> > > Now for the Mandrake problem, I'm not the right person to help you.
> > > Just do the reverse steps of what you did to automatically insert
> > > pwcx.
> > >
> > I thought I had done that. Never mind, though, I'll probably figure=20
> > it out with a bit of help from my friends :-) and if not, well it=20
> > will give me the excuse to load a later kernel and put win4lin on=20
> > that instead.
> >
> > At least I know that I can run GnomeMeeting by booting to the other=20
> > kernel. It's not ideal, but it's workable. Thanks for your help.
> >
> > Anne
> > =2D-=20
> > Registered Linux User No.293302
> > Have you visited http://twiki.mdklinuxfaq.org yet?
> >
> >
> > --__--__--
> >
> > Message: 8
> > From: Maarten Vanraes <maarten vanraes pandora be>
> > To: gnomemeeting-list gnome org
> > Subject: Re: [GnomeMeeting-list] re: snd-via82xx full-duplex
> > Date: Tue, 4 Nov 2003 17:11:28 +0100
> > Reply-To: gnomemeeting-list gnome org
> >
> > at the moment of testing, nothing is using the /dev/dsp or /dev/sound/dsp,
> =
> > but=20
> > I can tell you that I have have lots of programs using /dev/dsp and they
> al=
> > l=20
> > work fine (at least for sound output) (for example, I have a game
> running,=
> > =20
> > and GAIM and xine and they all use it together, with no problems at all),
> b=
> > ut=20
> > at the moment of testing, I turned them all off, so that nothing was
> using=
> > =20
> > /dev/dsp.
> >
> > is that it? you mean that I can't have a working microphone in linux? at
> al=
> > l?
> >
> > that just sucks...
> >
> > Op dinsdag 4 november 2003 16:59, schreef Damien Sandras:
> > > Le mar 04/11/2003 =E0 16:44, Alien999999999 a =E9crit :
> > > > again, my question, how do i check if it is full-duplex? and how do I
> > > > turn that on?
> > >
> > > With the druid. Also do an lsof /dev/dsp to see if no other software is
> > > using the device, causing the failure.
> > >
> > > There is no way to turn full-duplex on / off.
> >
> > =2D-=20
> > pgp keys: http://users.pandora.be/Alien999999999/public_keys.gpg
> >
> >
> > --__--__--
> >
> > Message: 9
> > Subject: Re: [GnomeMeeting-list] re: snd-via82xx full-duplex
> > From: Damien Sandras <dsandras seconix com>
> > To: gnomemeeting-list gnome org
> > Date: Tue, 04 Nov 2003 17:20:10 +0100
> > Reply-To: gnomemeeting-list gnome org
> >
> > Le mar 04/11/2003 à 17:11, Maarten Vanraes a écrit :
> > > at the moment of testing, nothing is using the /dev/dsp or
> /dev/sound/dsp, but
> >
> > Have you checked with lsof?
> >
> > > I can tell you that I have have lots of programs using /dev/dsp and they
> all
> > > work fine (at least for sound output) (for example, I have a game
> running,
> > > and GAIM and xine and they all use it together, with no problems at
> all), but
> >
> > You named it, all those programs are only using output and never
> > input/output, so being full-duplex or not is not a problem.
> >
> > > at the moment of testing, I turned them all off, so that nothing was
> using
> > > /dev/dsp.
> >
> > > is that it? you mean that I can't have a working microphone in linux? at
> all?
> > >
> > > that just sucks...
> > >
> >
> > Buy a decent soundcard after having checked yours is not full-duplex.
> > However I doubt your soundcard is not full-duplex, you most probably
> > have misconfigured your ALSA installation.
> >
> >
> > > Op dinsdag 4 november 2003 16:59, schreef Damien Sandras:
> > > > Le mar 04/11/2003 à 16:44, Alien999999999 a écrit :
> > > > > again, my question, how do i check if it is full-duplex? and how do
> I
> > > > > turn that on?
> > > >
> > > > With the druid. Also do an lsof /dev/dsp to see if no other software
> is
> > > > using the device, causing the failure.
> > > >
> > > > There is no way to turn full-duplex on / off.
> > --
> > _ Damien Sandras
> > (o-
> > //\ It-Optics s.a.
> > v_/_ GnomeMeeting: http://www.gnomemeeting.org/
> > FOSDEM 2004: http://www.fosdem.org
> > H.323 phone: callto:ils.seconix.com/dsandras seconix com
> >
> >
> >
> > --__--__--
> >
> > _______________________________________________
> > GnomeMeeting-list mailing list
> > GnomeMeeting-list gnome org
> > http://mail.gnome.org/mailman/listinfo/gnomemeeting-list
> >
> >
> > End of GnomeMeeting-list Digest
>
>
> _______________________________________________
> GnomeMeeting-list mailing list
> GnomeMeeting-list gnome org
> http://mail.gnome.org/mailman/listinfo/gnomemeeting-list
--
_ Damien Sandras
(o- GnomeMeeting: http://www.gnomemeeting.org/
//\ FOSDEM 2003: http://www.fosdem.org
v_/_ H.323 phone: callto://ils.seconix.com/dsandras seconix com
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]
