Hello Raul, The 2.6 kernel comes with the old IXJ driver that doesn't support recent cards. You have to use the newest nixj from openh323.sourceforge.net for your card to work, however, that driver is not fully ready yet for 2.6. Le mardi 31 août 2004 à 22:08 +0300, Raul Z. Martinez a écrit : > Hi everybody. > > I have recently purchased a Quicknet Phone Jack PCI (linux version) and > installed it in my computer. I am running SuSE 9.1 with a 2.6.5 kernel. Once > installed, I included the proper command (modprobe ixj) in my boot scripts, > which loads ixj and phonedev. So far so good. However, I found that upon > starting gnomemeeting (1.0.1 SuSE rpm) the program didn't detect any quicknet > card installed, just my regular soundcard. > > Going over the whole configuration, it seems SuSE has problems to properly > configure the Quicknet card as a telephony device: it certainly finds it and > assigns appropriate resources, this is the output of "lspci -vx": > > 0000:02:05.0 Communication controller: Individual Computers - Jens Schoenfeld > Intel 537 > Subsystem: Quicknet Technologies Inc: Unknown device 0003 > Flags: bus master, medium devsel, latency 32, IRQ 17 > I/O ports at d000 > Memory at f3022000 (32-bit, non-prefetchable) [size=4K] > Capabilities: [40] Power Management version 2 > 00: 59 e1 01 00 07 00 10 02 00 00 80 07 00 20 00 00 > 10: 01 d0 00 00 00 20 02 f3 00 00 00 00 00 00 00 00 > 20: 00 00 00 00 00 00 00 00 00 00 00 00 e2 15 03 00 > 30: 00 00 00 00 40 00 00 00 00 00 00 00 0b 01 01 80 > > However, "cat /proc/ixj/" shows this: > > $Id: ixj.c,v 4.7 2001/08/13 06:19:33 craigs Exp $ > $Id: ixj.h,v 4.1 2001/08/04 14:49:27 craigs Exp $ > $Id: ixjuser.h,v 4.1 2001/08/05 00:17:37 craigs Exp $ > Driver version 1.0.1 > sizeof IXJ struct 21168 bytes > sizeof DAA struct 642 bytes > Using old telephony API > Debug Level 0 > > No information about any card associated to the driver. It took me a while to > find the card in the SuSE hardware manager, until I realized that -for > reasons that I don't understand, but that I suspect are related to the chip > it uses- it was being detected as an ISDN adapter. I have tried to remove it > from the hardware manager, but I really don't know how to coerce the system > into identifying it as a telephony device and associating it with the proper > driver, so Gnomemeeting still doesn't detect it and every time I reboot it > gets re-detected as an ISDN adapter. > > I have requested support from quicknet, but I am still waiting for a reply > and their linux support seems a little lacking, so in the meantime I thought > that, althought this doesn't look like a gnomemeeting problem, if somebody is > likely to have found this kind of trouble before this would be another > gnomemeeting user. > > I'd greatly appreciate any advice or suggestions that you can give me. Thanks > in advance! > > > R > _______________________________________________ > 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 : http://www.fosdem.org v_/_ H.323 phone : callto:ils.seconix.com/dsandras seconix com
Attachment:
signature.asc
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=