Activity for Gigaset 307x isdn Linux drivers

Paul Bolle posted a comment on discussion Help

Paul Bolle — Thu, 19 Sep 2019 07:59:33 -0000

Tilman Schmidt schreef op wo 18-09-2019 om 18:16 [+0000]: So I just implemented a timeout and if, after that time, the HD_READY_SEND_ATDATA signal still hasn't arrived, the driver sends the next command anyway, assuming that the signal has just been lost and hoping that the base will complain in a sensible way if that assumption is wrong, most probably by indicating a stall. (A possible alternative would be to send an empty command, analogously to what gigaset_write_cmd() does in the symmetric case...

Malte Forkel posted a comment on discussion Help

Malte Forkel — Wed, 18 Sep 2019 19:02:17 -0000

Am 18.09.2019 um 20:16 schrieb Tilman Schmidt: Hi guys, so finally I couldn't resist looking into this a bit more. Isn't our whole industry based on creating irresistible temptations? Thanks for giving in :-) Malte

Tilman Schmidt posted a comment on discussion Help

Tilman Schmidt — Wed, 18 Sep 2019 18:16:13 -0000

Hi guys, so finally I couldn't resist looking into this a bit more. Am 19.08.2019 um 10:30 schrieb Paul Bolle: Jul 26 09:00:02 servi kernel: [41511.530376] bas_gigaset 1-1.5:1.0: timeout waiting for HD_READY_SEND_ATDATA This seems to be the root problem. You see, the Gigaset base is supposed to send an HD_READY_SEND_ATDATA message whenever it is ready to receive a command, and the driver is not supposed to send a command as long as it hasn't received that message. However the Gigaset documentation...

Malte Forkel posted a comment on discussion Help

Malte Forkel — Wed, 18 Sep 2019 08:46:50 -0000

Am 18.09.2019 um 00:51 schrieb Tilman Schmidt: Hi Paul, Am 17.09.2019 um 20:28 schrieb Paul Bolle: As far as I know the gigaset driver was written by people unfamiliar with i4l, CAPI, the linux network stack, the linux USB stack, etc. That is correct as far as I am concerned. "Etc." would notably include the serial line discipline interface which is used for connecting the ser_gigaset driver to the serial port framework of the kernel. (I was in fact familiar with the concept of line disciplines from...

Malte Forkel posted a comment on discussion Help

Malte Forkel — Wed, 18 Sep 2019 08:45:34 -0000

Am 17.09.2019 um 20:28 schrieb Paul Bolle: Malte Forkel schreef op di 17-09-2019 om 17:32 [+0000]: I think I found out what might be causing the connection failures I reported: There seems to be a conflict between gigacontr using the USB connection to the Gigaset base and a digital video recorder program (vdr) using a DVB-C adapter connected to the Raspberry Pis. This is a Hauppage WinTV soloHD USB adapter; is uses the em28xx kernel driver. Good news! Both Gigaset base and DVB-C adapter are connected...

Paul Bolle posted a comment on discussion Help

Paul Bolle — Tue, 17 Sep 2019 23:23:16 -0000

Tilman Schmidt schreef op di 17-09-2019 om 22:51 [+0000]: "Etc." would notably include the serial line discipline interface which is used for connecting the ser_gigaset driver to the serial port framework of the kernel. (I was in fact familiar with the concept of line disciplines from Unix SVR4 but they Linux implementation is quite different and I had to fix a few errors and omissions in Documentation/serial/tty.txt first before being able to use it.) This reminds me that I had to ask you what on...

Tilman Schmidt posted a comment on discussion Help

Tilman Schmidt — Tue, 17 Sep 2019 22:51:31 -0000

Hi Paul, Am 17.09.2019 um 20:28 schrieb Paul Bolle: As far as I know the gigaset driver was written by people unfamiliar with i4l, CAPI, the linux network stack, the linux USB stack, etc. That is correct as far as I am concerned. "Etc." would notably include the serial line discipline interface which is used for connecting the ser_gigaset driver to the serial port framework of the kernel. (I was in fact familiar with the concept of line disciplines from Unix SVR4 but they Linux implementation is...

Paul Bolle posted a comment on discussion Help

Paul Bolle — Tue, 17 Sep 2019 18:28:08 -0000

Malte Forkel schreef op di 17-09-2019 om 17:32 [+0000]: I think I found out what might be causing the connection failures I reported: There seems to be a conflict between gigacontr using the USB connection to the Gigaset base and a digital video recorder program (vdr) using a DVB-C adapter connected to the Raspberry Pis. This is a Hauppage WinTV soloHD USB adapter; is uses the em28xx kernel driver. Good news! Both Gigaset base and DVB-C adapter are connected to an external USB hub with its own power...

Paul Bolle posted a comment on discussion Help

Paul Bolle — Tue, 17 Sep 2019 17:58:30 -0000

Malte Forkel schreef op di 17-09-2019 om 17:01 [+0000]: Thanks, Paul, for working on the driver! I'm very much in favor of keeping it in the kernel. I would definitely like to continue using it to control my Gigaset base, e.g. for initiating telephone calls from my desktop and retrieving the list of incoming and outgoing connections. Please let me know what I can do to support that cause. Test it like there's no tomorrow! And learn C, while you're at it. Paul Bolle

Malte Forkel posted a comment on discussion Help

Malte Forkel — Tue, 17 Sep 2019 17:32:15 -0000

I think I found out what might be causing the connection failures I reported: There seems to be a conflict between gigacontr using the USB connection to the Gigaset base and a digital video recorder program (vdr) using a DVB-C adapter connected to the Raspberry Pis. This is a Hauppage WinTV soloHD USB adapter; is uses the em28xx kernel driver. Both Gigaset base and DVB-C adapter are connected to an external USB hub with its own power supply. So insufficient power should not be the problem. Also,...

Malte Forkel posted a comment on discussion Help

Malte Forkel — Tue, 17 Sep 2019 17:01:39 -0000

Am 13.09.2019 um 20:23 schrieb Paul Bolle: Paul Bolle schreef op za 31-08-2019 om 21:09 [+0200]: Perhaps I'll try a similar test on my live base (behind a ISDN <-> VOIP bridge). If I'll do, the results will be summarized here. What I have done instead is to hack on the driver with a sledgehammer: - drop ser-gigaset.c; - drop capi.c; - remove /a lot/ of unreachable code; - make the driver Unimodem only. This allowed me to cut out 2/3s of the driver. And in the end I looked at a driver depending only...

Paul Bolle posted a comment on discussion Help

Paul Bolle — Fri, 13 Sep 2019 18:23:18 -0000

Paul Bolle schreef op za 31-08-2019 om 21:09 [+0200]: Perhaps I'll try a similar test on my live base (behind a ISDN <-> VOIP bridge). If I'll do, the results will be summarized here. What I have done instead is to hack on the driver with a sledgehammer: - drop ser-gigaset.c; - drop capi.c; - remove a lot of unreachable code; - make the driver Unimodem only. This allowed me to cut out 2/3s of the driver. And in the end I looked at a driver depending only on TTY and USB. gigacontr still works, to...

Paul Bolle posted a comment on discussion Help

Paul Bolle — Sat, 31 Aug 2019 19:09:42 -0000

Malte Forkel schreef op ma 19-08-2019 om 16:18 [+0000]: No spare base, but currently I'm its only user. So no reason not to run tests. I've run a few hundreds downloads of the log from a spare base in quick succession. Think: every 15 seconds. Nothing quite as serious as you saw in the logs. Note that I'm running v5.3-rcx. Perhaps I'll try a similar test on my live base (behind a ISDN <-> VOIP bridge). If I'll do, the results will be summarized here. Paul Bolle

Malte Forkel posted a comment on discussion Help

Malte Forkel — Mon, 19 Aug 2019 16:18:46 -0000

Hi Paul, Am 19.08.2019 um 10:30 schrieb Paul Bolle: Hi Malte, Malte Forkel schreef op do 15-08-2019 om 11:55 [+0000]: I'm still using self-compiled modules (capi and gigaset) to connect to a Gigaset 3075 base from Raspberry Pi running Raspbian stretch (currently kernel 4.19.58-v7+) as reported in an earlier post (https://sourceforge.net/p/gigaset307x/discussion/75814/thread/c03320a0/). Malte and I determined off list that Malte's setup doesn't require capi. dummy link level will do. But this problem...

Malte Forkel posted a comment on discussion Help

Malte Forkel — Mon, 19 Aug 2019 15:42:28 -0000

In my experiments, unplugging and replugging the USB cable to the base helped best. At one point I even tried to find out whether I could simulate that from the driver, but found no way to do so Temporarily unplugging the base did not work for me (just tried one, though). These are the log entries caused by unplugging and replugging: Aug 18 19:28:29 servi kernel: [95501.773787] bas_gigaset 1-1.5.1:1.0: disconnecting Gigaset base Aug 18 19:28:45 servi kernel: [95517.275818] usb 1-1.5.1: Product: Gigaset...

Paul Bolle posted a comment on discussion Help

Paul Bolle — Mon, 19 Aug 2019 08:30:33 -0000

Hi Malte, Malte Forkel schreef op do 15-08-2019 om 11:55 [+0000]: I'm still using self-compiled modules (capi and gigaset) to connect to a Gigaset 3075 base from Raspberry Pi running Raspbian stretch (currently kernel 4.19.58-v7+) as reported in an earlier post (https://sourceforge.net/p/gigaset307x/discussion/75814/thread/c03320a0/). Malte and I determined off list that Malte's setup doesn't require capi. dummy link level will do. But this problem also happens while running the dummy LL. Too bad....

Paul Bolle posted a comment on discussion Help

Paul Bolle — Mon, 19 Aug 2019 08:26:01 -0000

Tilman Schmidt schreef op za 17-08-2019 om 16:42 [+0000]: In my experiments, unplugging and replugging the USB cable to the base helped best. At one point I even tried to find out whether I could simulate that from the driver, but found no way to do so. So I assume a rmmod/insmod sequence (or its modprobe equivalent) didn't reset the base state to something usable? Paul Bolle

Tilman Schmidt posted a comment on discussion Help

Tilman Schmidt — Sat, 17 Aug 2019 16:42:21 -0000

In my experiments, unplugging and replugging the USB cable to the base helped best. At one point I even tried to find out whether I could simulate that from the driver, but found no way to do so.

Malte Forkel posted a comment on discussion Help

Malte Forkel — Sat, 17 Aug 2019 14:56:02 -0000

Is there anything I can do short of rebooting to access the Gigaset base again?

Tilman Schmidt posted a comment on discussion Help

Tilman Schmidt — Thu, 15 Aug 2019 19:19:01 -0000

I'm afraid I cannot help you. I don't have a Gigaset base anymore, and those "endpoint stalled" errors were always difficult to make sense of even when I encountered them on my own installation, let alone remotely.

Malte Forkel posted a comment on discussion Help

Malte Forkel — Thu, 15 Aug 2019 11:55:37 -0000

Hello, it seems I'm the only one needing help with the Gigaset drivers... :-) I'm still using self-compiled modules (capi and gigaset) to connect to a Gigaset 3075 base from Raspberry Pi running Raspbian stretch (currently kernel 4.19.58-v7+) as reported in an earlier post (https://sourceforge.net/p/gigaset307x/discussion/75814/thread/c03320a0/). Every hour, the base gets queried for the journal log entries by a cron job. I'm also using this for dialing. Last year, connection problems requiring a...

Malte Forkel posted a comment on discussion Help

Malte Forkel — Thu, 01 Feb 2018 18:02:45 -0000

and one that interprets and dials text selected on my Windows desktop. "Dials text"? It uses the current text selection, presumably a telephone number, to run a CGI script on the Rasberry Pi that interprets the text and has the Gigaset base dial the number.. You're free to dive into the source to see what each individual message might mean, what triggers them, etc. (Drop in an email if you need a few pointers.) Perhaps a few tweaks to the code might make those messages go away. Thanks. But I know...

Paul Bolle posted a comment on discussion Help

Paul Bolle — Wed, 31 Jan 2018 10:04:43 -0000

On Sat, 2018-01-27 at 13:18 +0000, Malte Forkel wrote: 0 - I'm currently using two utilities that I build on top of the frontend tools. One that continuously updates a log of incoming and outgoing telephone calls, I see. and one that interprets and dials text selected on my Windows desktop. "Dials text"? 1 - I'd be happy to provide my packaging for Debian / Raspbian if there is interest. No. But I could add the source to the project. Need to see it first, obviously. But nowadays it's probably easiest...

Malte Forkel posted a comment on discussion Help

Malte Forkel — Sat, 27 Jan 2018 13:18:21 -0000

Thanks, Paul. I'm very sorry it took me half a year to reply. I guess I was expecting an automatic notification about a reply and never checked myself... I hope it's not too late now to answer your questions: 0 - I'm currently using two utilities that I build on top of the frontend tools. One that continuously updates a log of incoming and outgoing telephone calls, and one that interprets and dials text selected on my Windows desktop. 1 - I'd be happy to provide my packaging for Debian / Raspbian...

Paul Bolle posted a comment on discussion Help

Paul Bolle — Fri, 21 Jul 2017 12:34:50 -0000

Any advice? 0 - Thanks for posting these questions. I'm thrilled to notice someone is still using this driver. Care to share what your goals are with this project? 1 - Consumer grade ISDN is slowly moving to a very small niche. So it's understandable that distributions disable the gigaset drivers. And, as far as I know, the frontend tools have never been carried by distributions. 2 - It seems that everything worked as expected. Is that correct? (I did test bas_gigaset lightly on, I think, an rc for...

Malte Forkel posted a comment on discussion Help

Malte Forkel — Fri, 21 Jul 2017 12:17:15 -0000

Hello, I am accessing a Gigaset 3075 isdn from a RaspberryPi using the gigaset kernel modules of kernel 4.9.35 and frontend utilities 0.7.2. I had to compile and package all those componets myself, because the kernel modules are not included in the standard Raspbian kernel and there is no package for the frontend in the Raspbian distribution. May be that explains the following log entries. On system start Jul 21 14:09:29 servi kernel: [ 2.395378] usb 1-1.3: New USB device found, idVendor=0681, idProduct=0002...

Paul Bolle committed [63d6da]