linux-gpib-general — linux-gpib package mailing list

Re: [Linux-gpib-general] Problem with Ines PCI gpib board on AlmaLinux 9 (RHEL 9 clone)

[George A. <ga...@ip...>]

Hi Dave,

I am glad we are able to contribute some debugging for the linux-gpib project.
Παρακαλώ !

I did set "master = no" in gpib.conf and  "sudo gpib_config --minor 0"

The results from ibtest are:

: v
enter new status byte (bit 0x40 requests service): 0x07
gpib status is:
ibsta = 0x1100 < SRQI CMPL >
iberr= 0

ibcntl = 0

: l
DAV off
NDAC off
NRFD off
IFC on
REN on
SRQ on
ATN on
EOI off
gpib status is:
ibsta = 0x1100 < SRQI CMPL >
iberr= 0

ibcntl = 0

: v
enter new status byte (bit 0x40 requests service): 0x00
gpib status is:
ibsta = 0x1100 < SRQI CMPL >
iberr= 0

ibcntl = 0

: l
DAV off
NDAC off
NRFD off
IFC on
REN on
SRQ on
ATN on
EOI off
gpib status is:
ibsta = 0x1100 < SRQI CMPL >
iberr= 0

ibcntl = 0

I checked this with both ines_pci_unaccel & ines_pci_accel. Results are the same

George

On Mon, 2026-01-12 at 13:41 +0100, dave penkler wrote:
Hi George,
Thank you very much for the information. This is most helpful as I do not have an INES card to test with.
The analysis so far:
The INES GPIB chip (one of the best) has two modes - NEC7210 mode and extended mode.
The Bus Control line  Monitor (BCM) register is only accessible in extended mode.
From the lspci we see that we are dealing with the full capability INES gpib chip PCI_DEVICE_ID_INES_GPIB_QL5030 0x0011.
The driver enables it in extended mode. write_byte(nec_priv, INES_AUX_XMODE, AUXMR);
The hypothesis is that extended mode, for some reason to be determined, is not being enabled.
In support of this hypothesis we have
- When reading the Bus Control Monitor register 0x13 we get rubbish (ibtest (l)ines output)
- We get the fifo failed message even if no fifo access has happened
- The accel interface does not work (using extended mode fifos)
- The unaccel interface, which works, uses only the NEC7210 registers.
In order to verify this hypothesis we could perform the following experiment which checks whether
register 0x13 (BCM) is being mapped to 0x3 (serial poll response), (high order register address bits being ignored) because the NEC7210 has only 8 registers.:
1 Set the master = configuration parameter in gpib.conf to no
  (this is to be able to set the serial poll response register)
2 sudo gpib_config
3 ibtest, open board, and try these commands
  v request ser(v)ice (board only)
  enter new status byte (bit 0x40 requests service): 0x07
 l get bus (l)ine status
  If we see DAV, NRFD and NDAC on (the others off) the hypothesis is not refuted.
  v request ser(v)ice (board only)
  enter new status byte (bit 0x40 requests service): 0x00
  l get bus (l)ine status
  If now we see all lines off (in particular DAV, NRFD and NDAC) then the hypothesis is confirmed.
If it is confirmed it remains to figure out why extended mode is not being enabled.
Ευχαριστώ,
-Dave

Re: [Linux-gpib-general] Problem with Ines PCI gpib board on AlmaLinux 9 (RHEL 9 clone)

[dave p. <dpe...@gm...>]

Hi George,
Thank you very much for the information. This is most helpful as I do not
have an INES card to test with.
The analysis so far:
The INES GPIB chip (one of the best) has two modes - NEC7210 mode and
extended mode.
The Bus Control line  Monitor (BCM) register is only accessible in extended
mode.
>From the lspci we see that we are dealing with the full capability INES
gpib chip PCI_DEVICE_ID_INES_GPIB_QL5030 0x0011.
The driver enables it in extended mode. *write_byte(nec_priv,
INES_AUX_XMODE, AUXMR);*
The hypothesis is that extended mode, for some reason to be determined, is
not being enabled.
In support of this hypothesis we have
- When reading the Bus Control Monitor register 0x13 we get rubbish (ibtest
(l)ines output)
- We get the fifo failed message even if no fifo access has happened
- The accel interface does not work (using extended mode fifos)
- The unaccel interface, which works, uses only the NEC7210 registers.
In order to verify this hypothesis we could perform the following
experiment which checks whether
register 0x13 (BCM) is being mapped to 0x3 (serial poll response), (high
order register address bits being ignored) because the NEC7210 has only 8
registers.:
1 Set the *master = *configuration parameter in gpib.conf to *no*
  (this is to be able to set the serial poll response register)
2 sudo gpib_config
3 ibtest, open board, and try these commands
  *v* request ser(v)ice (board only)
  enter new status byte (bit 0x40 requests service): *0x07*
* l *get bus (l)ine status
  If we see DAV, NRFD and NDAC on (the others off) the hypothesis is not
refuted.
  *v* request ser(v)ice (board only)
  enter new status byte (bit 0x40 requests service): *0x00*
  *l* get bus (l)ine status
  If now we see all lines off (in particular DAV, NRFD and NDAC) then the
hypothesis is confirmed.
If it is confirmed it remains to figure out why extended mode is not being
enabled.
Ευχαριστώ,
-Dave

Re: [Linux-gpib-general] Problem with Ines PCI gpib board on AlmaLinux 9 (RHEL 9 clone)

[George A. <ga...@ip...>]

Hi Dave,

The output of lspci:

$ sudo lspci -vnn -d 16da:
02:02.0 Communication controller [0780]: Advantech Co., Ltd. INES GPIB-PCI [16da:0011]
Subsystem: Advantech Co., Ltd. INES GPIB-PCI [16da:0011]
Flags: medium devsel, IRQ 10
Memory at f7d00000 (32-bit, non-prefetchable) [disabled] [size=16K]
I/O ports at e000 [disabled] [size=32]
Kernel driver in use: ines_gpib
Kernel modules: ines_gpib

I have tried also
boardtype = "ines_pci_accel"
and
boardtype = "ines_pci"
in /etc/gpib.conf.
I tried to communicate with my Keithley voltmeter at address 16, with "ibterm -d 16".
In both cases I get no reply to an "*IDN?" query, although no error is reported.

Only with "ines_pci_unaccel" the instrument's reply is obtained.

Best regards
George

On Sun, 2026-01-11 at 13:36 +0100, dave penkler wrote:
Hi George,
It looks like the driver does not read the bus control line monitor register correctly for your board.
Can you please provide me with the oiutput of:
sudo lspci -vnn  -d 16da:
so that I can identify the exact hardware you  are using.
Also have you tried the accelerated interface ?

On Sat, 10 Jan 2026 at 20:57, George Apostolopoulos <ga...@ip...<mailto:ga...@ip...>> wrote:
Update:

After adding return_to_local: ines_return_to_local in ines_init.c and rebuilding the 4.3.6 kernel modules the device started talking!!


$ ibterm -d 16

Attempting to open /dev/gpib0

pad = 16, sad = 0, timeout = 10, send_eoi = 1, eos_mode = 0x0000

ibterm>*IDN?

KEITHLEY INSTRUMENTS INC.,MODEL 2000,1187798,A20  /A02

I did also the commands with ibtest. The results are different:


$ ibtest

Do you wish to open a (d)evice or an interface (b)oard?

        (you probably want to open a device): b

enter name of interface board (or device) you wish to open: ines

trying to open board named 'ines'


: g

ATN released.

gpib status is:

ibsta = 0x1164  < SRQI CMPL REM CIC LACS >

iberr= 0


ibcntl = 0


: l

DAV off

NDAC off

NRFD off

IFC on

REN on

SRQ on

ATN on

EOI off

gpib status is:

ibsta = 0x1164  < SRQI CMPL REM CIC LACS >

iberr= 0


ibcntl = 0


: k

Enter '1' to assert ATN synchronously, or '0' for asynchronously [1]: 1

Taking control synchronously...

ATN asserted.

gpib status is:

ibsta = 0x1174  < SRQI CMPL REM CIC ATN LACS >

iberr= 0


ibcntl = 0


: l

DAV off

NDAC off

NRFD off

IFC on

REN on

SRQ on

ATN on

EOI off

gpib status is:

ibsta = 0x1174  < SRQI CMPL REM CIC ATN LACS >

iberr= 0


ibcntl = 0



On Sat, 2026-01-10 at 18:26 +0000, George Apostolopoulos via Linux-gpib-general wrote:
Hi Dave,

Thank you very much for your help and generally for the linux-gpib project.

My gpib.conf file is


$ cat /etc/gpib.conf

interface {

        minor = 0       /* board index, minor = 0 uses /dev/gpib0, minor = 1 uses /dev/gpib1, etc. */

        board_type = "ines_pci_unaccel" /* type of interface board being used */

        name = "ines"

        pad = 0 /* primary address of interface             */

        sad = 0 /* secondary address of interface           */

        timeout = T3s   /* timeout for commands */

        eos = 0x0a      /* EOS Byte, 0xa is newline and 0xd is carriage return */

        set-reos = yes  /* Terminate read if EOS */

        set-bin = no    /* Compare EOS 8-bit */

        set-xeos = no   /* Assert EOI whenever EOS byte is sent */

        set-eot = yes   /* Assert EOI with last byte on writes */

master = yes    /* interface board is system controller */

}

I run ibtest with the commands you requested and the output was:


: g

ATN released.

gpib status is:

ibsta = 0x1120  < SRQI CMPL CIC >

iberr= 0


ibcntl = 0


: l

DAV off

NDAC off

NRFD off

IFC on

REN on

SRQ on

ATN on

EOI off

gpib status is:

ibsta = 0x1120  < SRQI CMPL CIC >

iberr= 0


ibcntl = 0


: k

Enter '1' to assert ATN synchronously, or '0' for asynchronously [1]: 1

Taking control synchronously...

ATN asserted.

gpib status is:

ibsta = 0x1130  < SRQI CMPL CIC ATN >

iberr= 0


ibcntl = 0



: l

DAV off

NDAC off

NRFD off

IFC on

REN on

SRQ on

ATN on

EOI off

gpib status is:

ibsta = 0x1130  < SRQI CMPL CIC ATN >

iberr= 0


ibcntl = 0


I will recompile 4.3.6 with your suggestions and send here the results.

Best regards
George


On Sat, 2026-01-10 at 13:11 +0100, dave penkler wrote:
Hi Dr Apostolopoulos,
For the SSL problem you may try the answer provided here<https://superuser.com/questions/1214116/no-openssl-sign-file-signing-key-pem-leads-to-error-while-loading-kernel-modules/1322832#1322832> for signing kernel modules.
For the fifo failed message, I am not sure, please send your gpib_config file.
For the ENOL error, in the meantime you might try and rebuild after adding the line
 skip_check_for_command_acceptors : 1
after
 return_to_local: ines_return_to_local,
in the 4.3.6 file drivers/gpib/ines/ines_init.c
at lines 256,285 and 314

To understand what is going on can you please run ibtest with your device attached and powered on.
Open the board and provide me with the output for the following commands.
g (g)o to standby
l get bus (l)ine status
k ta(k)e control
l get bus (l)ine status
Thanks,
-Dave

On Fri, 9 Jan 2026 at 19:03, George Apostolopoulos via Linux-gpib-general <lin...@li...<mailto:lin...@li...><mailto:lin...@li...<mailto:lin...@li...>><mailto:lin...@li...<mailto:lin...@li...><mailto:lin...@li...<mailto:lin...@li...>>>> wrote:
Hello,

I am trying to install linux-gpib on AlmaLinux 9 to operate an Ines PCI
GPIB board.

I have tried both linux-gpib-4.3.6 and linux-gpib-4.3.7.

In both versions, during "make install" of the kernel part, I get a lot
of messages:

   At main.c:167:
   - SSL error:FFFFFFFF80000002:system library::No such file or
   directory: crypto/bio/bss_file.c:67
   - SSL error:10000080:BIO routines::no such file:
   crypto/bio/bss_file.c:75
   sign-file: certs/signing_key.pem: No such file or directory

However, the modules are installed.

After make/make install of the user part, the board seems to be
recognized in the system.
E.g. the following is obtained for 4.3.6 with dmesg:

   $ dmesg | grep gpib
   [    5.904112] gpib_common: loading out-of-tree module taints kernel.
   [    5.904118] gpib_common: module verification failed: signature and/or required key missing - tainting kernel
   [    5.939516] gpib: registered ines_pci interface
   [    5.939522] gpib: registered ines_pci_unaccel interface
   [    5.939523] gpib: registered ines_pci_accel interface
   [    5.939524] gpib: registered ines_isa interface


After

   $ sudo gpib_config --minor 0

the following messages are seen with dmesg:

   [  128.442229] ines_gpib 0000:02:02.0: enabling device (0000 ->0003)
   [  128.442361] ines gpib: fifo error

With an instrument attached at gpib address 16 I get the following with
ibterm:

   $ ibterm -d 16
   Attempting to open /dev/gpib0
   pad = 16, sad = 0, timeout = 10, send_eoi = 1, eos_mode = 0x0000
   ibterm>*IDN?
   ibterm error: Unable to write to device at pad 16

    - ENOL 2: No listeners

The system was operational up to now with CentOS 7 and linux-gpib-
4.3.0.

Any help would be greatly appreciated.

Best regards
George Apostolopoulos



_______________________________________________
Linux-gpib-general mailing list
Lin...@li...<mailto:Lin...@li...><mailto:Lin...@li...<mailto:Lin...@li...>>
https://lists.sourceforge.net/lists/listinfo/linux-gpib-general

Re: [Linux-gpib-general] Problem with Ines PCI gpib board on AlmaLinux 9 (RHEL 9 clone)

[dave p. <dpe...@gm...>]

Hi George,
It looks like the driver does not read the bus control line monitor
register correctly for your board.
Can you please provide me with the oiutput of:
*sudo lspci -vnn  -d 16da:*
so that I can identify the exact hardware you  are using.
Also have you tried the accelerated interface ?

On Sat, 10 Jan 2026 at 20:57, George Apostolopoulos <
ga...@ip...> wrote:

> Update:
>
> After adding return_to_local: ines_return_to_local in ines_init.c and
> rebuilding the 4.3.6 kernel modules the device started talking!!
>
>
> $ ibterm -d 16
>
> Attempting to open /dev/gpib0
>
> pad = 16, sad = 0, timeout = 10, send_eoi = 1, eos_mode = 0x0000
>
> ibterm>*IDN?
>
> KEITHLEY INSTRUMENTS INC.,MODEL 2000,1187798,A20  /A02
>
> I did also the commands with ibtest. The results are different:
>
>
> $ ibtest
>
> Do you wish to open a (d)evice or an interface (b)oard?
>
>         (you probably want to open a device): b
>
> enter name of interface board (or device) you wish to open: ines
>
> trying to open board named 'ines'
>
>
> : g
>
> ATN released.
>
> gpib status is:
>
> ibsta = 0x1164  < SRQI CMPL REM CIC LACS >
>
> iberr= 0
>
>
> ibcntl = 0
>
>
> : l
>
> DAV off
>
> NDAC off
>
> NRFD off
>
> IFC on
>
> REN on
>
> SRQ on
>
> ATN on
>
> EOI off
>
> gpib status is:
>
> ibsta = 0x1164  < SRQI CMPL REM CIC LACS >
>
> iberr= 0
>
>
> ibcntl = 0
>
>
> : k
>
> Enter '1' to assert ATN synchronously, or '0' for asynchronously [1]: 1
>
> Taking control synchronously...
>
> ATN asserted.
>
> gpib status is:
>
> ibsta = 0x1174  < SRQI CMPL REM CIC ATN LACS >
>
> iberr= 0
>
>
> ibcntl = 0
>
>
> : l
>
> DAV off
>
> NDAC off
>
> NRFD off
>
> IFC on
>
> REN on
>
> SRQ on
>
> ATN on
>
> EOI off
>
> gpib status is:
>
> ibsta = 0x1174  < SRQI CMPL REM CIC ATN LACS >
>
> iberr= 0
>
>
> ibcntl = 0
>
>
>
> On Sat, 2026-01-10 at 18:26 +0000, George Apostolopoulos via
> Linux-gpib-general wrote:
> Hi Dave,
>
> Thank you very much for your help and generally for the linux-gpib project.
>
> My gpib.conf file is
>
>
> $ cat /etc/gpib.conf
>
> interface {
>
>         minor = 0       /* board index, minor = 0 uses /dev/gpib0, minor =
> 1 uses /dev/gpib1, etc. */
>
>         board_type = "ines_pci_unaccel" /* type of interface board being
> used */
>
>         name = "ines"
>
>         pad = 0 /* primary address of interface             */
>
>         sad = 0 /* secondary address of interface           */
>
>         timeout = T3s   /* timeout for commands */
>
>         eos = 0x0a      /* EOS Byte, 0xa is newline and 0xd is carriage
> return */
>
>         set-reos = yes  /* Terminate read if EOS */
>
>         set-bin = no    /* Compare EOS 8-bit */
>
>         set-xeos = no   /* Assert EOI whenever EOS byte is sent */
>
>         set-eot = yes   /* Assert EOI with last byte on writes */
>
> master = yes    /* interface board is system controller */
>
> }
>
> I run ibtest with the commands you requested and the output was:
>
>
> : g
>
> ATN released.
>
> gpib status is:
>
> ibsta = 0x1120  < SRQI CMPL CIC >
>
> iberr= 0
>
>
> ibcntl = 0
>
>
> : l
>
> DAV off
>
> NDAC off
>
> NRFD off
>
> IFC on
>
> REN on
>
> SRQ on
>
> ATN on
>
> EOI off
>
> gpib status is:
>
> ibsta = 0x1120  < SRQI CMPL CIC >
>
> iberr= 0
>
>
> ibcntl = 0
>
>
> : k
>
> Enter '1' to assert ATN synchronously, or '0' for asynchronously [1]: 1
>
> Taking control synchronously...
>
> ATN asserted.
>
> gpib status is:
>
> ibsta = 0x1130  < SRQI CMPL CIC ATN >
>
> iberr= 0
>
>
> ibcntl = 0
>
>
>
> : l
>
> DAV off
>
> NDAC off
>
> NRFD off
>
> IFC on
>
> REN on
>
> SRQ on
>
> ATN on
>
> EOI off
>
> gpib status is:
>
> ibsta = 0x1130  < SRQI CMPL CIC ATN >
>
> iberr= 0
>
>
> ibcntl = 0
>
>
> I will recompile 4.3.6 with your suggestions and send here the results.
>
> Best regards
> George
>
>
> On Sat, 2026-01-10 at 13:11 +0100, dave penkler wrote:
> Hi Dr Apostolopoulos,
> For the SSL problem you may try the answer provided here<
> https://superuser.com/questions/1214116/no-openssl-sign-file-signing-key-pem-leads-to-error-while-loading-kernel-modules/1322832#1322832>
> for signing kernel modules.
> For the fifo failed message, I am not sure, please send your gpib_config
> file.
> For the ENOL error, in the meantime you might try and rebuild after adding
> the line
>  skip_check_for_command_acceptors : 1
> after
>  return_to_local: ines_return_to_local,
> in the 4.3.6 file drivers/gpib/ines/ines_init.c
> at lines 256,285 and 314
>
> To understand what is going on can you please run ibtest with your device
> attached and powered on.
> Open the board and provide me with the output for the following commands.
> g (g)o to standby
> l get bus (l)ine status
> k ta(k)e control
> l get bus (l)ine status
> Thanks,
> -Dave
>
> On Fri, 9 Jan 2026 at 19:03, George Apostolopoulos via Linux-gpib-general <
> lin...@li...<mailto:
> lin...@li...><mailto:
> lin...@li...<mailto:
> lin...@li...>>> wrote:
> Hello,
>
> I am trying to install linux-gpib on AlmaLinux 9 to operate an Ines PCI
> GPIB board.
>
> I have tried both linux-gpib-4.3.6 and linux-gpib-4.3.7.
>
> In both versions, during "make install" of the kernel part, I get a lot
> of messages:
>
>    At main.c:167:
>    - SSL error:FFFFFFFF80000002:system library::No such file or
>    directory: crypto/bio/bss_file.c:67
>    - SSL error:10000080:BIO routines::no such file:
>    crypto/bio/bss_file.c:75
>    sign-file: certs/signing_key.pem: No such file or directory
>
> However, the modules are installed.
>
> After make/make install of the user part, the board seems to be
> recognized in the system.
> E.g. the following is obtained for 4.3.6 with dmesg:
>
>    $ dmesg | grep gpib
>    [    5.904112] gpib_common: loading out-of-tree module taints kernel.
>    [    5.904118] gpib_common: module verification failed: signature
> and/or required key missing - tainting kernel
>    [    5.939516] gpib: registered ines_pci interface
>    [    5.939522] gpib: registered ines_pci_unaccel interface
>    [    5.939523] gpib: registered ines_pci_accel interface
>    [    5.939524] gpib: registered ines_isa interface
>
>
> After
>
>    $ sudo gpib_config --minor 0
>
> the following messages are seen with dmesg:
>
>    [  128.442229] ines_gpib 0000:02:02.0: enabling device (0000 ->0003)
>    [  128.442361] ines gpib: fifo error
>
> With an instrument attached at gpib address 16 I get the following with
> ibterm:
>
>    $ ibterm -d 16
>    Attempting to open /dev/gpib0
>    pad = 16, sad = 0, timeout = 10, send_eoi = 1, eos_mode = 0x0000
>    ibterm>*IDN?
>    ibterm error: Unable to write to device at pad 16
>
>     - ENOL 2: No listeners
>
> The system was operational up to now with CentOS 7 and linux-gpib-
> 4.3.0.
>
> Any help would be greatly appreciated.
>
> Best regards
> George Apostolopoulos
>
>
>
> _______________________________________________
> Linux-gpib-general mailing list
> Lin...@li...<mailto:
> Lin...@li...>
> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>

Re: [Linux-gpib-general] Problem with Ines PCI gpib board on AlmaLinux 9 (RHEL 9 clone)

[George A. <ga...@ip...>]

Update:

After adding return_to_local: ines_return_to_local in ines_init.c and rebuilding the 4.3.6 kernel modules the device started talking!!


$ ibterm -d 16

Attempting to open /dev/gpib0

pad = 16, sad = 0, timeout = 10, send_eoi = 1, eos_mode = 0x0000

ibterm>*IDN?

KEITHLEY INSTRUMENTS INC.,MODEL 2000,1187798,A20  /A02

I did also the commands with ibtest. The results are different:


$ ibtest

Do you wish to open a (d)evice or an interface (b)oard?

        (you probably want to open a device): b

enter name of interface board (or device) you wish to open: ines

trying to open board named 'ines'


: g

ATN released.

gpib status is:

ibsta = 0x1164  < SRQI CMPL REM CIC LACS >

iberr= 0


ibcntl = 0


: l

DAV off

NDAC off

NRFD off

IFC on

REN on

SRQ on

ATN on

EOI off

gpib status is:

ibsta = 0x1164  < SRQI CMPL REM CIC LACS >

iberr= 0


ibcntl = 0


: k

Enter '1' to assert ATN synchronously, or '0' for asynchronously [1]: 1

Taking control synchronously...

ATN asserted.

gpib status is:

ibsta = 0x1174  < SRQI CMPL REM CIC ATN LACS >

iberr= 0


ibcntl = 0


: l

DAV off

NDAC off

NRFD off

IFC on

REN on

SRQ on

ATN on

EOI off

gpib status is:

ibsta = 0x1174  < SRQI CMPL REM CIC ATN LACS >

iberr= 0


ibcntl = 0



On Sat, 2026-01-10 at 18:26 +0000, George Apostolopoulos via Linux-gpib-general wrote:
Hi Dave,

Thank you very much for your help and generally for the linux-gpib project.

My gpib.conf file is


$ cat /etc/gpib.conf

interface {

        minor = 0       /* board index, minor = 0 uses /dev/gpib0, minor = 1 uses /dev/gpib1, etc. */

        board_type = "ines_pci_unaccel" /* type of interface board being used */

        name = "ines"

        pad = 0 /* primary address of interface             */

        sad = 0 /* secondary address of interface           */

        timeout = T3s   /* timeout for commands */

        eos = 0x0a      /* EOS Byte, 0xa is newline and 0xd is carriage return */

        set-reos = yes  /* Terminate read if EOS */

        set-bin = no    /* Compare EOS 8-bit */

        set-xeos = no   /* Assert EOI whenever EOS byte is sent */

        set-eot = yes   /* Assert EOI with last byte on writes */

master = yes    /* interface board is system controller */

}

I run ibtest with the commands you requested and the output was:


: g

ATN released.

gpib status is:

ibsta = 0x1120  < SRQI CMPL CIC >

iberr= 0


ibcntl = 0


: l

DAV off

NDAC off

NRFD off

IFC on

REN on

SRQ on

ATN on

EOI off

gpib status is:

ibsta = 0x1120  < SRQI CMPL CIC >

iberr= 0


ibcntl = 0


: k

Enter '1' to assert ATN synchronously, or '0' for asynchronously [1]: 1

Taking control synchronously...

ATN asserted.

gpib status is:

ibsta = 0x1130  < SRQI CMPL CIC ATN >

iberr= 0


ibcntl = 0



: l

DAV off

NDAC off

NRFD off

IFC on

REN on

SRQ on

ATN on

EOI off

gpib status is:

ibsta = 0x1130  < SRQI CMPL CIC ATN >

iberr= 0


ibcntl = 0


I will recompile 4.3.6 with your suggestions and send here the results.

Best regards
George


On Sat, 2026-01-10 at 13:11 +0100, dave penkler wrote:
Hi Dr Apostolopoulos,
For the SSL problem you may try the answer provided here<https://superuser.com/questions/1214116/no-openssl-sign-file-signing-key-pem-leads-to-error-while-loading-kernel-modules/1322832#1322832> for signing kernel modules.
For the fifo failed message, I am not sure, please send your gpib_config file.
For the ENOL error, in the meantime you might try and rebuild after adding the line
 skip_check_for_command_acceptors : 1
after
 return_to_local: ines_return_to_local,
in the 4.3.6 file drivers/gpib/ines/ines_init.c
at lines 256,285 and 314

To understand what is going on can you please run ibtest with your device attached and powered on.
Open the board and provide me with the output for the following commands.
g (g)o to standby
l get bus (l)ine status
k ta(k)e control
l get bus (l)ine status
Thanks,
-Dave

On Fri, 9 Jan 2026 at 19:03, George Apostolopoulos via Linux-gpib-general <lin...@li...<mailto:lin...@li...><mailto:lin...@li...<mailto:lin...@li...>>> wrote:
Hello,

I am trying to install linux-gpib on AlmaLinux 9 to operate an Ines PCI
GPIB board.

I have tried both linux-gpib-4.3.6 and linux-gpib-4.3.7.

In both versions, during "make install" of the kernel part, I get a lot
of messages:

   At main.c:167:
   - SSL error:FFFFFFFF80000002:system library::No such file or
   directory: crypto/bio/bss_file.c:67
   - SSL error:10000080:BIO routines::no such file:
   crypto/bio/bss_file.c:75
   sign-file: certs/signing_key.pem: No such file or directory

However, the modules are installed.

After make/make install of the user part, the board seems to be
recognized in the system.
E.g. the following is obtained for 4.3.6 with dmesg:

   $ dmesg | grep gpib
   [    5.904112] gpib_common: loading out-of-tree module taints kernel.
   [    5.904118] gpib_common: module verification failed: signature and/or required key missing - tainting kernel
   [    5.939516] gpib: registered ines_pci interface
   [    5.939522] gpib: registered ines_pci_unaccel interface
   [    5.939523] gpib: registered ines_pci_accel interface
   [    5.939524] gpib: registered ines_isa interface


After

   $ sudo gpib_config --minor 0

the following messages are seen with dmesg:

   [  128.442229] ines_gpib 0000:02:02.0: enabling device (0000 ->0003)
   [  128.442361] ines gpib: fifo error

With an instrument attached at gpib address 16 I get the following with
ibterm:

   $ ibterm -d 16
   Attempting to open /dev/gpib0
   pad = 16, sad = 0, timeout = 10, send_eoi = 1, eos_mode = 0x0000
   ibterm>*IDN?
   ibterm error: Unable to write to device at pad 16

    - ENOL 2: No listeners

The system was operational up to now with CentOS 7 and linux-gpib-
4.3.0.

Any help would be greatly appreciated.

Best regards
George Apostolopoulos



_______________________________________________
Linux-gpib-general mailing list
Lin...@li...<mailto:Lin...@li...>
https://lists.sourceforge.net/lists/listinfo/linux-gpib-general

Re: [Linux-gpib-general] Problem with Ines PCI gpib board on AlmaLinux 9 (RHEL 9 clone)

[George A. <ga...@ip...>]

Hi Dave,

Thank you very much for your help and generally for the linux-gpib project.

My gpib.conf file is


$ cat /etc/gpib.conf

interface {

        minor = 0       /* board index, minor = 0 uses /dev/gpib0, minor = 1 uses /dev/gpib1, etc. */

        board_type = "ines_pci_unaccel" /* type of interface board being used */

        name = "ines"

        pad = 0 /* primary address of interface             */

        sad = 0 /* secondary address of interface           */

        timeout = T3s   /* timeout for commands */

        eos = 0x0a      /* EOS Byte, 0xa is newline and 0xd is carriage return */

        set-reos = yes  /* Terminate read if EOS */

        set-bin = no    /* Compare EOS 8-bit */

        set-xeos = no   /* Assert EOI whenever EOS byte is sent */

        set-eot = yes   /* Assert EOI with last byte on writes */

master = yes    /* interface board is system controller */

}

I run ibtest with the commands you requested and the output was:


: g

ATN released.

gpib status is:

ibsta = 0x1120  < SRQI CMPL CIC >

iberr= 0


ibcntl = 0


: l

DAV off

NDAC off

NRFD off

IFC on

REN on

SRQ on

ATN on

EOI off

gpib status is:

ibsta = 0x1120  < SRQI CMPL CIC >

iberr= 0


ibcntl = 0


: k

Enter '1' to assert ATN synchronously, or '0' for asynchronously [1]: 1

Taking control synchronously...

ATN asserted.

gpib status is:

ibsta = 0x1130  < SRQI CMPL CIC ATN >

iberr= 0


ibcntl = 0



: l

DAV off

NDAC off

NRFD off

IFC on

REN on

SRQ on

ATN on

EOI off

gpib status is:

ibsta = 0x1130  < SRQI CMPL CIC ATN >

iberr= 0


ibcntl = 0


I will recompile 4.3.6 with your suggestions and send here the results.

Best regards
George


On Sat, 2026-01-10 at 13:11 +0100, dave penkler wrote:
Hi Dr Apostolopoulos,
For the SSL problem you may try the answer provided here<https://superuser.com/questions/1214116/no-openssl-sign-file-signing-key-pem-leads-to-error-while-loading-kernel-modules/1322832#1322832> for signing kernel modules.
For the fifo failed message, I am not sure, please send your gpib_config file.
For the ENOL error, in the meantime you might try and rebuild after adding the line
 skip_check_for_command_acceptors : 1
after
 return_to_local: ines_return_to_local,
in the 4.3.6 file drivers/gpib/ines/ines_init.c
at lines 256,285 and 314

To understand what is going on can you please run ibtest with your device attached and powered on.
Open the board and provide me with the output for the following commands.
g (g)o to standby
l get bus (l)ine status
k ta(k)e control
l get bus (l)ine status
Thanks,
-Dave

On Fri, 9 Jan 2026 at 19:03, George Apostolopoulos via Linux-gpib-general <lin...@li...<mailto:lin...@li...>> wrote:
Hello,

I am trying to install linux-gpib on AlmaLinux 9 to operate an Ines PCI
GPIB board.

I have tried both linux-gpib-4.3.6 and linux-gpib-4.3.7.

In both versions, during "make install" of the kernel part, I get a lot
of messages:

   At main.c:167:
   - SSL error:FFFFFFFF80000002:system library::No such file or
   directory: crypto/bio/bss_file.c:67
   - SSL error:10000080:BIO routines::no such file:
   crypto/bio/bss_file.c:75
   sign-file: certs/signing_key.pem: No such file or directory

However, the modules are installed.

After make/make install of the user part, the board seems to be
recognized in the system.
E.g. the following is obtained for 4.3.6 with dmesg:

   $ dmesg | grep gpib
   [    5.904112] gpib_common: loading out-of-tree module taints kernel.
   [    5.904118] gpib_common: module verification failed: signature and/or required key missing - tainting kernel
   [    5.939516] gpib: registered ines_pci interface
   [    5.939522] gpib: registered ines_pci_unaccel interface
   [    5.939523] gpib: registered ines_pci_accel interface
   [    5.939524] gpib: registered ines_isa interface


After

   $ sudo gpib_config --minor 0

the following messages are seen with dmesg:

   [  128.442229] ines_gpib 0000:02:02.0: enabling device (0000 ->0003)
   [  128.442361] ines gpib: fifo error

With an instrument attached at gpib address 16 I get the following with
ibterm:

   $ ibterm -d 16
   Attempting to open /dev/gpib0
   pad = 16, sad = 0, timeout = 10, send_eoi = 1, eos_mode = 0x0000
   ibterm>*IDN?
   ibterm error: Unable to write to device at pad 16

    - ENOL 2: No listeners

The system was operational up to now with CentOS 7 and linux-gpib-
4.3.0.

Any help would be greatly appreciated.

Best regards
George Apostolopoulos

[Linux-gpib-general] Problem with Ines PCI gpib board on AlmaLinux 9 (RHEL 9 clone)

[George A. <ga...@ip...>]

Hello,

I am trying to install linux-gpib on AlmaLinux 9 to operate an Ines PCI
GPIB board.

I have tried both linux-gpib-4.3.6 and linux-gpib-4.3.7. 

In both versions, during "make install" of the kernel part, I get a lot
of messages:

   At main.c:167:
   - SSL error:FFFFFFFF80000002:system library::No such file or
   directory: crypto/bio/bss_file.c:67
   - SSL error:10000080:BIO routines::no such file:
   crypto/bio/bss_file.c:75
   sign-file: certs/signing_key.pem: No such file or directory
   
However, the modules are installed.
 
After make/make install of the user part, the board seems to be
recognized in the system.
E.g. the following is obtained for 4.3.6 with dmesg:

   $ dmesg | grep gpib
   [    5.904112] gpib_common: loading out-of-tree module taints kernel.
   [    5.904118] gpib_common: module verification failed: signature and/or required key missing - tainting kernel
   [    5.939516] gpib: registered ines_pci interface
   [    5.939522] gpib: registered ines_pci_unaccel interface
   [    5.939523] gpib: registered ines_pci_accel interface
   [    5.939524] gpib: registered ines_isa interface

   
After

   $ sudo gpib_config --minor 0

the following messages are seen with dmesg:

   [  128.442229] ines_gpib 0000:02:02.0: enabling device (0000 ->0003)
   [  128.442361] ines gpib: fifo error
   
With an instrument attached at gpib address 16 I get the following with
ibterm:

   $ ibterm -d 16
   Attempting to open /dev/gpib0
   pad = 16, sad = 0, timeout = 10, send_eoi = 1, eos_mode = 0x0000
   ibterm>*IDN?
   ibterm error: Unable to write to device at pad 16
   
    - ENOL 2: No listeners

The system was operational up to now with CentOS 7 and linux-gpib-
4.3.0.

Any help would be greatly appreciated.

Best regards
George Apostolopoulos


-- 
_________________________________
Dr. George Apostolopoulos
Fusion Technology Group               
INRASTES / NCSR "Demokritos"
15341 Agia Paraskevi Attikis, 
Greece           
 
tel:   +30-210-650-3731 
email: ga...@ip...
web:   http://ftg.demokritos.gr/

Re: [Linux-gpib-general] Segfault in python bindings

[dave p. <dpe...@gm...>]

OK. We should probably suppress the  "libgpib: invalid descriptor" message.
I'll push the change.



On Fri, 28 Nov 2025 at 11:08, Matthias Geiger <m_g...@wi...> wrote:

> Am 28.11.25 um 10:23 schrieb dave penkler:
> > Hi Matthias,
> > There was a problem in the C library code. A fix has been pushed to
> > the git
> > <
> https://sourceforge.net/p/linux-gpib/git/ci/88183039ff0a4621af2b3ddd79186f089869208d/
> >.
> > Please let me know if this works for you.
> > cheers,
> > -Dave
> >
> >
> Hi Dave,
>
> thanks for the quick fix. Rebuilding the userspace bindings does not
> lead to a segfault anymore:
>
>  >>> gpib.read(9999, dev)
> libgpib: invalid descriptor
> libgpib: invalid descriptor
> Traceback (most recent call last):
>    File "<python-input-4>", line 1, in <module>
>      gpib.read(9999, dev)
>      ~~~~~~~~~^^^^^^^^^^^
> gpib.GpibError: read() failed: One or more arguments to the function
> call were invalid.
>
> It still complains about an invalid descriptor though. Thanks for the
> quick fix! I will cherry-pick this into Debian and then backport the
> whole package
> to current stable (trixie).
>
> --
> Freundliche Grüsse / Best regards
>
> Matthias Geiger
> __________________________________________________________________
> Matthias Geiger
> Werkstudent
> Forschung & Entwicklung/Research & Development
>
> Phone : +49-6441-609-3004
> Email : m_g...@wi...
> URL   : www.wiwa.de
>
> WIWA Wilhelm Wagner GmbH & Co. KG
> Gewerbestrasse 1-3, 35633 Lahnau, Germany
> Besucheranschrift/visitor address:
> Georg-Ohm-Strasse 12, 35633 Lahnau, Germany
>
> AG WETZLAR HRA 3223, Komplementär : Wagner GmbH (AG Wetzlar HRB 363)
> UST-ID Nr: / VAT-No: DE113745802
> Geschäftsführer: Dipl.-Ing. (FH) Peter Turczak, Dipl.-Wirt.-Ing. Malte
> Weber
>
>
>
>
> _______________________________________________
> Linux-gpib-general mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>

Re: [Linux-gpib-general] Segfault in python bindings

[Matthias G. <m_g...@wi...>]

Am 28.11.25 um 10:23 schrieb dave penkler:
> Hi Matthias,
> There was a problem in the C library code. A fix has been pushed to 
> the git 
> <https://sourceforge.net/p/linux-gpib/git/ci/88183039ff0a4621af2b3ddd79186f089869208d/>.
> Please let me know if this works for you.
> cheers,
> -Dave
>
>
Hi Dave,

thanks for the quick fix. Rebuilding the userspace bindings does not 
lead to a segfault anymore:

 >>> gpib.read(9999, dev)
libgpib: invalid descriptor
libgpib: invalid descriptor
Traceback (most recent call last):
   File "<python-input-4>", line 1, in <module>
     gpib.read(9999, dev)
     ~~~~~~~~~^^^^^^^^^^^
gpib.GpibError: read() failed: One or more arguments to the function 
call were invalid.

It still complains about an invalid descriptor though. Thanks for the 
quick fix! I will cherry-pick this into Debian and then backport the 
whole package
to current stable (trixie).

-- 
Freundliche Grüsse / Best regards

Matthias Geiger
__________________________________________________________________
Matthias Geiger
Werkstudent
Forschung & Entwicklung/Research & Development

Phone : +49-6441-609-3004
Email : m_g...@wi...
URL   : www.wiwa.de

WIWA Wilhelm Wagner GmbH & Co. KG
Gewerbestrasse 1-3, 35633 Lahnau, Germany
Besucheranschrift/visitor address:
Georg-Ohm-Strasse 12, 35633 Lahnau, Germany

AG WETZLAR HRA 3223, Komplementär : Wagner GmbH (AG Wetzlar HRB 363)
UST-ID Nr: / VAT-No: DE113745802
Geschäftsführer: Dipl.-Ing. (FH) Peter Turczak, Dipl.-Wirt.-Ing. Malte Weber

Re: [Linux-gpib-general] Segfault in python bindings

[dave p. <dpe...@gm...>]

Hi Matthias,
There was a problem in the C library code. A fix has been pushed to the git
<https://sourceforge.net/p/linux-gpib/git/ci/88183039ff0a4621af2b3ddd79186f089869208d/>
.
Please let me know if this works for you.
cheers,
-Dave

On Thu, 27 Nov 2025 at 12:17, Matthias Geiger <m_g...@wi...> wrote:

> Am 27.11.25 um 11:55 schrieb Matthias Geiger:
> >
> > <http://intraserv.common.wiwa.loc/gitlab/><
> http://intraserv.common.wiwa.loc/gitlab/><
> http://intraserv.common.wiwa.loc/gitlab/><
> http://intraserv.common.wiwa.loc/gitlab/>
> >
> > <http://intraserv.common.wiwa.loc/gitlab/>
> >
> Whoops,
>
> ignore that.
>
> --
> Freundliche Grüsse / Best regards
>
> Matthias Geiger
> __________________________________________________________________
> Matthias Geiger
> Werkstudent
> Forschung & Entwicklung/Research & Development
>
> Phone : +49-6441-609-3004
> Email : m_g...@wi...
> URL   : www.wiwa.de
>
> WIWA Wilhelm Wagner GmbH & Co. KG
> Gewerbestrasse 1-3, 35633 Lahnau, Germany
> Besucheranschrift/visitor address:
> Georg-Ohm-Strasse 12, 35633 Lahnau, Germany
>
> AG WETZLAR HRA 3223, Komplementär : Wagner GmbH (AG Wetzlar HRB 363)
> UST-ID Nr: / VAT-No: DE113745802
> Geschäftsführer: Dipl.-Ing. (FH) Peter Turczak, Dipl.-Wirt.-Ing. Malte
> Weber
>
>
>
>
> _______________________________________________
> Linux-gpib-general mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>

Re: [Linux-gpib-general] Segfault in python bindings

[Matthias G. <m_g...@wi...>]

Am 27.11.25 um 11:55 schrieb Matthias Geiger:
>
> <http://intraserv.common.wiwa.loc/gitlab/><http://intraserv.common.wiwa.loc/gitlab/><http://intraserv.common.wiwa.loc/gitlab/><http://intraserv.common.wiwa.loc/gitlab/> 
>
> <http://intraserv.common.wiwa.loc/gitlab/>
>
Whoops,

ignore that.

-- 
Freundliche Grüsse / Best regards

Matthias Geiger
__________________________________________________________________
Matthias Geiger
Werkstudent
Forschung & Entwicklung/Research & Development

Phone : +49-6441-609-3004
Email : m_g...@wi...
URL   : www.wiwa.de

WIWA Wilhelm Wagner GmbH & Co. KG
Gewerbestrasse 1-3, 35633 Lahnau, Germany
Besucheranschrift/visitor address:
Georg-Ohm-Strasse 12, 35633 Lahnau, Germany

AG WETZLAR HRA 3223, Komplementär : Wagner GmbH (AG Wetzlar HRB 363)
UST-ID Nr: / VAT-No: DE113745802
Geschäftsführer: Dipl.-Ing. (FH) Peter Turczak, Dipl.-Wirt.-Ing. Malte Weber

[Linux-gpib-general] Segfault in python bindings

[Matthias G. <m_g...@wi...>]

Hi,
I came across a segfault in the python bindings for GPIB.
This is with the bitbang kernel module on a Raspberry Pi 4 running 
raspbian trixie and the python3-gpib package installed from Debian unstable.
This can be reproduced like this:
<http://intraserv.common.wiwa.loc/gitlab/><http://intraserv.common.wiwa.loc/gitlab/><http://intraserv.common.wiwa.loc/gitlab/><http://intraserv.common.wiwa.loc/gitlab/>
<http://intraserv.common.wiwa.loc/gitlab/>

sudo modprobe gpib_bitbang
sudo /sbin/gpib_config
export DEBUGINFOD_URLS="https://debuginfod.debian.net"
gdb --args python3 -i
(gdb) run
(gdb) >>> import gpib
(gdb) >>> dev = gpib.dev(0, 9)
(gdb) >>> gpib.write(dev, ":ID?")
(gdb) 8448
(gdb) >>> gpib.read(dev, 9999)
(gdb) b'HP3488A\r\n
(gdb) >>> gpib.read(9999, dev)
libgpib: invalid descriptor
Segmentation fault
(gdb) bt

Trying to read the wrong way should result in type error from python. I 
attached the backtrace; let me know if you need any additional info.

-- 
Freundliche Grüsse / Best regards

Matthias Geiger
__________________________________________________________________
Matthias Geiger
Werkstudent
Forschung & Entwicklung/Research & Development

Phone : +49-6441-609-3004
Email : m_g...@wi...
URL   : www.wiwa.de

WIWA Wilhelm Wagner GmbH & Co. KG
Gewerbestrasse 1-3, 35633 Lahnau, Germany
Besucheranschrift/visitor address:
Georg-Ohm-Strasse 12, 35633 Lahnau, Germany

AG WETZLAR HRA 3223, Komplementär : Wagner GmbH (AG Wetzlar HRB 363)
UST-ID Nr: / VAT-No: DE113745802
Geschäftsführer: Dipl.-Ing. (FH) Peter Turczak, Dipl.-Wirt.-Ing. Malte Weber

[Linux-gpib-general] [PATCH] Fixing of miscellaneous typos

[Matthias G. <m_g...@wi...>]

Hi,

see attachement.

-- 
Freundliche Grüsse / Best regards

Matthias Geiger
__________________________________________________________________
Matthias Geiger
Werkstudent
Forschung & Entwicklung/Research & Development

Phone : +49-6441-609-3004
Email : m_g...@wi...
URL   : www.wiwa.de

WIWA Wilhelm Wagner GmbH & Co. KG
Gewerbestrasse 1-3, 35633 Lahnau, Germany
Besucheranschrift/visitor address:
Georg-Ohm-Strasse 12, 35633 Lahnau, Germany

AG WETZLAR HRA 3223, Komplementär : Wagner GmbH (AG Wetzlar HRB 363)
UST-ID Nr: / VAT-No: DE113745802
Geschäftsführer: Dipl.-Ing. (FH) Peter Turczak, Dipl.-Wirt.-Ing. Malte Weber

[Linux-gpib-general] Debian packages, some comments and patches

[Matthias G. <m_g...@wi...>]

Hi all,

I am glad to announce the userspace parts of linux-gpib are now 
available in Debian unstable [0].
It provides the C library, the python bindings, the userspace tools and 
the documentation.
Once those migrated to testing (in three days) I will backport the 
package to trixie (current Debian stable).
I won't be packaging the kernel parts as those are in staging anyway; am 
hoping to enable those once they are in mainline.
Currently, the user tools mention in the README.Debian that the DKMS 
module is still needed.

To comply with Debian policy (no prebuilt/pregenerated files) I had to 
jump through some hoops. The whole process is documented in 
README.source [1]
It would be great if future release tarballs would match the pristine 
git tree for the corresponding tag; this would really ease future 
package updates.

Another thing I ran into when building the manpages is Debian shipping 
the xml stylesheet under a different directory, and providing osg2xml as 
/usr/bin/osx.
This resulted in the following patch [2]

For the python bindings I opted to version them separately form the GPIB 
version [3]. I did this since setuptools.py also mentions 1.0 as 
version; furthermore this allows
for an easier split should the bindings be maintained separately at some 
point. Regarding this, I commited a version using pyproject.toml, and 
cleaned up the code to the
best of my abilities. The last four commits might be of interest here; 
they fix the indentation for all python files and take care of some 
other minor warnings [4]
IMO the python binding should be split from the source tree to allow 
building with pyproject.toml; should you choose to switch to that, my 
fork has all the bits ready.
If a standalone setuptools build gets deprecated in Debian I will use my 
fork and provide the bindings from there (from a separate package).

Additionally, for some reason the Changelog is not present in git from 
4.3.7; this causes a build failure when trying to build from git since 
the makefile expects the Changelog to
be present. To mitigate this, I touched an empty one; however this 
should be fixed properly [5].

The last issue I ran into is hardening. Debian recommends that we set 
the following hardening flags [6]:
CFLAGS=-g -O2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer 
-flto=auto -ffat-lto-objects -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection
hardening features: bindnow=no branch=yes format=yes fortify=yes pie=yes 
relro=yes stackclash=yes stackprotector=yes stackprotectorstrong=yes

Exported for make:

export LDFLAGS += -pie -Wl,-z,relro
export CFLAGS := -g -O2 -fno-omit-frame-pointer 
-mno-omit-leaf-frame-pointer  -flto=auto -ffat-lto-objects 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection
CFLAGS += -fPIE -fstack-clash-protection -D_FORTIFY_SOURCE=2

Since configure.ac overrides the exports I have set those aren't 
included in the build. It would be great if those could be included.


[0] https://tracker.debian.org/pkg/linux-gpib-user
[1] 
https://sources.debian.org/src/linux-gpib-user/4.3.7-2/debian/README.source
[2] 
https://sources.debian.org/src/linux-gpib-user/4.3.7-2/debian/patches/fix-docbook-path.diff
[3] https://sources.debian.org/src/linux-gpib-user/4.3.7-2/debian/rules#L7
[4] https://codeberg.org/werdahias/python-gpib
[5] https://sources.debian.org/src/linux-gpib-user/4.3.7-2/debian/rules#L26
[6] https://wiki.debian.org/Hardening

-- 
Freundliche Grüsse / Best regards

Matthias Geiger
__________________________________________________________________
Matthias Geiger
Werkstudent
Forschung & Entwicklung/Research & Development

Phone : +49-6441-609-3004
Email : m_g...@wi...
URL   : www.wiwa.de

WIWA Wilhelm Wagner GmbH & Co. KG
Gewerbestrasse 1-3, 35633 Lahnau, Germany
Besucheranschrift/visitor address:
Georg-Ohm-Strasse 12, 35633 Lahnau, Germany

AG WETZLAR HRA 3223, Komplementär : Wagner GmbH (AG Wetzlar HRB 363)
UST-ID Nr: / VAT-No: DE113745802
Geschäftsführer: Dipl.-Ing. (FH) Peter Turczak, Dipl.-Wirt.-Ing. Malte Weber

Re: [Linux-gpib-general] Announce linux-gpib-4.3.7 Release

[Jakub L. <la...@vo...>]

Great

I was even able to install it with gentoo portage (by editing the ebuild 
files).

I will be testing it next few days and will report any difficulties if 
encountered.

J.

[Linux-gpib-general] Announce linux-gpib-4.3.7 Release

[dave p. <dpe...@gm...>]

The linux-gpib-4.3.7
<https://sourceforge.net/projects/linux-gpib/files/linux-gpib%20for%203.x.x%20and%202.6.x%20kernels/4.3.7/>
release has been uploaded to the sourceforge site.

With this release we support kernels from 4.0 up to and including 6.17.

The drivers in the kernel part of the package have been updated to follow
the staging drivers in the kernel but modified to support older kernels
also.

A new driver to support the xyphro compact usb to GPIB adapter has been
added (see Supported Hardware
<https://linux-gpib.sourceforge.io/doc_html/supported-hardware.html#XYPHRO>
in the docs for details).

On the user side a number of bugs were fixed, features added and docs were
improved (see the README and ChangeLog for more details).

cheers,
-Dave

Re: [Linux-gpib-general] almost one year since I'm unable to install linux-gpib on my gentoo

[Andreas K. H. <dil...@ge...>]

Am Dienstag, 23. September 2025, 21:44:28 Mitteleuropäische Sommerzeit schrieb Jakub Ladman:
> Hi,
> 
> for almost whole year I am unable to install linux-gpib on my gentoo linux.
> 
> Since kernel was updated to 6.12 the packages (ebuilds) that are 
> describing to the system how the linux-gpib(-kernel) sources are to be 
> obtained and how to build them, are no longer able to build it.
> 
> For short while it was possible instead of the "stable" ebuild 
> linux-gpib-4.3.6 to use linux-gpib-9999 which is set to fetch the top of 
> the development git.
> 
> Now every attempt fails.

OK so I just tried and 9999 builds fine against 6.12 here.

What kernel and gcc versions are you using?


>>> Completed installing sci-libs/linux-gpib-modules-9999 into /var/tmp/portage/sci-libs/linux-gpib-modules-9999/image

 * Final size of build directory: 22524 KiB (21.9 MiB)
 * Final size of installed tree:   1168 KiB ( 1.1 MiB)


> 
> I am waiting for kernel update to the dream version containing the gpib 
> drivers, but for many months nothing.
> 
> There is masked package of linux 6.16.8 but anything I can do including 
> unmasking it leads not to bootable system.
> 
> I was hoping also for version 4.3.7 of the gpib suite will appear and 
> solve it, but no ...
> 
> I know you can't support every distro there exist in this universe, but 
> I honestly don't know what to do, so just complaining ...
> 
> There were years where no problem with installing linux-gpib were present.
> 
> J.
> 
> 
> _______________________________________________
> Linux-gpib-general mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
> 


-- 
Andreas K. Hüttel
dil...@ge...
Gentoo Linux developer
(council, toolchain, base-system, perl, libreoffice)

Re: [Linux-gpib-general] Python bindings, now updated

[Matthias G. <m_g...@wi...>]

Am 30.09.25 um 15:44 schrieb Matthias Geiger:
> After hacking some more on my source tree:
> a) does not work as cc does not know against which library to link.
> b) would be indeed the way to go; however this would require splitting 
> the python bindings in a separate repo, so they can link against the C 
> libgpib.
> I'd be willing to write patches for this if you agree to go ahead with 
> this. This would make python-gpib futureproof and ease distribution, 
> e.g. on pypi.
> In my Debian packaging I hacked around setup.py, but it's kinda ugly 
> and it will break sooner or later.
>
Hi all,

I extracted the python bindings in a standalone repo and cleaned up the 
examples a bit. The build now works fine with modern python tooling 
(i.e. pyproject.toml); I kept the Makefile for now.
To run the build you just need to have python3-build, python3 and the 
library bindings (libgpib) installed. I would appreciate 
testing/comments; it works for me, but python is not
my strong suit.

Work is at [0], ideally this would live also on sourceforge in its own repo.

[0] https://codeberg.org/werdahias/python-gpib


-- 
Freundliche Grüsse / Best regards

Matthias Geiger
__________________________________________________________________
Matthias Geiger
Werkstudent
Forschung & Entwicklung/Research & Development

Phone : +49-6441-609-3004
Email : m_g...@wi...
URL   : www.wiwa.de

WIWA Wilhelm Wagner GmbH & Co. KG
Gewerbestrasse 1-3, 35633 Lahnau, Germany
Besucheranschrift/visitor address:
Georg-Ohm-Strasse 12, 35633 Lahnau, Germany

AG WETZLAR HRA 3223, Komplementär : Wagner GmbH (AG Wetzlar HRB 363)
UST-ID Nr: / VAT-No: DE113745802
Geschäftsführer: Dipl.-Ing. (FH) Peter Turczak, Dipl.-Wirt.-Ing. Malte Weber

[Linux-gpib-general] PATCH: Fix manpage warnings fron lexgrog

[Matthias G. <m_g...@wi...>]

Hi,

attached is a patch that converts the usage of "and" for the three 
manpages mentioning multiple commands to ", ".
This is a kinda cosmetic change, though lexgrog complains otherwise 
about spaces in manpages.

-- 
Freundliche Grüsse / Best regards

Matthias Geiger
__________________________________________________________________
Matthias Geiger
Werkstudent
Forschung & Entwicklung/Research & Development

Phone : +49-6441-609-3004
Email : m_g...@wi...
URL   : www.wiwa.de

WIWA Wilhelm Wagner GmbH & Co. KG
Gewerbestrasse 1-3, 35633 Lahnau, Germany
Besucheranschrift/visitor address:
Georg-Ohm-Strasse 12, 35633 Lahnau, Germany

AG WETZLAR HRA 3223, Komplementär : Wagner GmbH (AG Wetzlar HRB 363)
UST-ID Nr: / VAT-No: DE113745802
Geschäftsführer: Dipl.-Ing. (FH) Peter Turczak, Dipl.-Wirt.-Ing. Malte Weber

[Linux-gpib-general] PATCH: Use standard /usr/share/doc path

[Matthias G. <m_g...@wi...>]

Hi,

attached patch adjusts the doc Makefile to use the standard 
/usr/share/doc patch for installing the documentation files.

-- 
Freundliche Grüsse / Best regards

Matthias Geiger
__________________________________________________________________
Matthias Geiger
Werkstudent
Forschung & Entwicklung/Research & Development

Phone : +49-6441-609-3004
Email : m_g...@wi...
URL   : www.wiwa.de

WIWA Wilhelm Wagner GmbH & Co. KG
Gewerbestrasse 1-3, 35633 Lahnau, Germany
Besucheranschrift/visitor address:
Georg-Ohm-Strasse 12, 35633 Lahnau, Germany

AG WETZLAR HRA 3223, Komplementär : Wagner GmbH (AG Wetzlar HRB 363)
UST-ID Nr: / VAT-No: DE113745802
Geschäftsführer: Dipl.-Ing. (FH) Peter Turczak, Dipl.-Wirt.-Ing. Malte Weber

Re: [Linux-gpib-general] PATCH: Fixing of typos

[dave p. <dpe...@gm...>]

Applied,
Thank you!

On Wed, 1 Oct 2025 at 12:20, Matthias Geiger <m_g...@wi...> wrote:

> Hi,
>
> attached patch fixed multiple typos for the userspace documentation.
> Found while preparing the Debian package.
>
> --
> Freundliche Grüsse / Best regards
>
> Matthias Geiger
> __________________________________________________________________
> Matthias Geiger
> Werkstudent
> Forschung & Entwicklung/Research & Development
>
> Phone : +49-6441-609-3004
> Email : m_g...@wi...
> URL   : www.wiwa.de
>
> WIWA Wilhelm Wagner GmbH & Co. KG
> Gewerbestrasse 1-3, 35633 Lahnau, Germany
> Besucheranschrift/visitor address:
> Georg-Ohm-Strasse 12, 35633 Lahnau, Germany
>
> AG WETZLAR HRA 3223, Komplementär : Wagner GmbH (AG Wetzlar HRB 363)
> UST-ID Nr: / VAT-No: DE113745802
> Geschäftsführer: Dipl.-Ing. (FH) Peter Turczak, Dipl.-Wirt.-Ing. Malte
> Weber
> _______________________________________________
> Linux-gpib-general mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>

[Linux-gpib-general] PATCH: Fixing of typos

[Matthias G. <m_g...@wi...>]

Hi,

attached patch fixed multiple typos for the userspace documentation.
Found while preparing the Debian package.

-- 
Freundliche Grüsse / Best regards

Matthias Geiger
__________________________________________________________________
Matthias Geiger
Werkstudent
Forschung & Entwicklung/Research & Development

Phone : +49-6441-609-3004
Email : m_g...@wi...
URL   : www.wiwa.de

WIWA Wilhelm Wagner GmbH & Co. KG
Gewerbestrasse 1-3, 35633 Lahnau, Germany
Besucheranschrift/visitor address:
Georg-Ohm-Strasse 12, 35633 Lahnau, Germany

AG WETZLAR HRA 3223, Komplementär : Wagner GmbH (AG Wetzlar HRB 363)
UST-ID Nr: / VAT-No: DE113745802
Geschäftsführer: Dipl.-Ing. (FH) Peter Turczak, Dipl.-Wirt.-Ing. Malte Weber

Re: [Linux-gpib-general] Python bindings

[Matthias G. <m_g...@wi...>]

Am 30.09.25 um 15:25 schrieb Matthias Geiger:
>
>
> this is because the python3 build module needs to be installed.
> With that it just fails because the gpib/ib.h header is not present:
>
>
> * Building wheel from sdist
> * Creating venv isolated environment...
> * Installing packages in isolated environment... (setuptools>=61)
> * Getting build dependencies for wheel...
> /tmp/build-env-qiaffj9e/lib/python3.12/site-packages/setuptools/config/pyprojecttoml.py:72: 
> _ExperimentalConfiguration: `[tool.setuptools.ext-modules]` in 
> `pyproject.toml` is still *experimental* and likely to cha
> nge in future releases.
>   config = read_configuration(filepath, True, ignore_option_errors, dist)
> running egg_info
> writing gpib.egg-info/PKG-INFO
> writing dependency_links to gpib.egg-info/dependency_links.txt
> writing top-level names to gpib.egg-info/top_level.txt
> reading manifest file 'gpib.egg-info/SOURCES.txt'
> writing manifest file 'gpib.egg-info/SOURCES.txt'
> * Building wheel...
> /tmp/build-env-qiaffj9e/lib/python3.12/site-packages/setuptools/config/pyprojecttoml.py:72: 
> _ExperimentalConfiguration: `[tool.setuptools.ext-modules]` in 
> `pyproject.toml` is still *experimental* and likely to cha
> nge in future releases.
>   config = read_configuration(filepath, True, ignore_option_errors, dist)
> running bdist_wheel
> running build
> running build_py
> creating build/lib.linux-x86_64-cpython-312
> copying Gpib.py -> build/lib.linux-x86_64-cpython-312
> running egg_info
> writing gpib.egg-info/PKG-INFO
> writing dependency_links to gpib.egg-info/dependency_links.txt
> writing top-level names to gpib.egg-info/top_level.txt
> reading manifest file 'gpib.egg-info/SOURCES.txt'
> writing manifest file 'gpib.egg-info/SOURCES.txt'
> running build_ext
> building 'gpib' extension
> creating build/temp.linux-x86_64-cpython-312
> x86_64-linux-gnu-gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g 
> -O2 -Wall -fPIC -I../../include -I/tmp/build-env-qiaffj9e/include 
> -I/usr/include/python3.12 -c gpibinter.c -o 
> build/temp.linux-x86_64-cpython-31
> 2/gpibinter.o
> gpibinter.c:12:10: fatal error: gpib/ib.h: Datei oder Verzeichnis 
> nicht gefunden
>    12 | #include <gpib/ib.h>
>       |          ^~~~~~~~~~~
> compilation terminated.
> error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
>
> ERROR Backend subprocess exited when trying to invoke build_wheel
> make[3]: [Makefile:494: build] Fehler 1 (ignoriert)
>
> From what I understand, this would require the header to a) either be 
> present locally *in the same* directory, or b) to be included via 
> /usr/share/include.
> Since the latter is IMO not feasible I will look into getting a) to work.
>
> best,
>
> Matthias Geiger
>
>
After hacking some more on my source tree:
a) does not work as cc does not know against which library to link.
b) would be indeed the way to go; however this would require splitting 
the python bindings in a separate repo, so they can link against the C 
libgpib.
I'd be willing to write patches for this if you agree to go ahead with 
this. This would make python-gpib futureproof and ease distribution, 
e.g. on pypi.
In my Debian packaging I hacked around setup.py, but it's kinda ugly and 
it will break sooner or later.

-- 
Freundliche Grüsse / Best regards

Matthias Geiger
__________________________________________________________________
Matthias Geiger
Werkstudent
Forschung & Entwicklung/Research & Development

Phone : +49-6441-609-3004
Email : m_g...@wi...
URL   : www.wiwa.de

WIWA Wilhelm Wagner GmbH & Co. KG
Gewerbestrasse 1-3, 35633 Lahnau, Germany
Besucheranschrift/visitor address:
Georg-Ohm-Strasse 12, 35633 Lahnau, Germany

AG WETZLAR HRA 3223, Komplementär : Wagner GmbH (AG Wetzlar HRB 363)
UST-ID Nr: / VAT-No: DE113745802
Geschäftsführer: Dipl.-Ing. (FH) Peter Turczak, Dipl.-Wirt.-Ing. Malte Weber

Re: [Linux-gpib-general] Python bindings

[Matthias G. <m_g...@wi...>]

Am 30.09.25 um 14:54 schrieb dave penkler:
> After applying your patch I get:
>
> Making all in python
> make[3]: Entering directory 
> '/home/dave/src/linux-gpib-git/linux-gpib-user/language/python'
> { /usr/bin/python -m build && touch build; } || { rm -f -r build; exit 
> 1; }
> /usr/bin/python: No module named build.__main__; 'build' is a package 
> and cannot be directly executed
> make[3]: [Makefile:501: build] Error 1 (ignored)
> make[3]: Leaving directory 
> '/home/dave/src/linux-gpib-git/linux-gpib-user/language/python
>
> without your patch I get:
>
> Making all in python
> make[3]: Entering directory 
> '/home/dave/src/linux-gpib-git/linux-gpib-user/language/python'
> { /usr/bin/python setup.py build && touch build; } || { rm -f -r 
> build; exit 1; }
> running build
> running build_py
> creating build/lib.linux-x86_64-cpython-312
> copying Gpib.py -> build/lib.linux-x86_64-cpython-312
> running egg_info
> creating gpib.egg-info
> writing gpib.egg-info/PKG-INFO
> writing dependency_links to gpib.egg-info/dependency_links.txt
> writing top-level names to gpib.egg-info/top_level.txt
> writing manifest file 'gpib.egg-info/SOURCES.txt'
> reading manifest file 'gpib.egg-info/SOURCES.txt'
> writing manifest file 'gpib.egg-info/SOURCES.txt'
> running build_ext
> building 'gpib' extension
> creating build/temp.linux-x86_64-cpython-312
> gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O3 -Wall -fPIC 
> -I../../include -I/usr/include/python3.12 -c gpibinter.c -o 
> build/temp.linux-x86_64-cpython-312/gpibinter.o
> gcc -shared build/temp.linux-x86_64-cpython-312/gpibinter.o 
> -L../../lib/.libs -L/usr/lib64 -lgpib -lpthread -o 
> build/lib.linux-x86_64-cpython-312/gpib.cpython-312-x86_64-linux-gnu.so 
> <http://gpib.cpython-312-x86_64-linux-gnu.so>
> make[3]: Leaving directory 
> '/home/dave/src/linux-gpib-git/linux-gpib-user/language/python'
>
> cheers,
> -dave
Hi Dave,

this is because the python3 build module needs to be installed.
With that it just fails because the gpib/ib.h header is not present:


* Building wheel from sdist
* Creating venv isolated environment...
* Installing packages in isolated environment... (setuptools>=61)
* Getting build dependencies for wheel...
/tmp/build-env-qiaffj9e/lib/python3.12/site-packages/setuptools/config/pyprojecttoml.py:72: 
_ExperimentalConfiguration: `[tool.setuptools.ext-modules]` in 
`pyproject.toml` is still *experimental* and likely to cha
nge in future releases.
   config = read_configuration(filepath, True, ignore_option_errors, dist)
running egg_info
writing gpib.egg-info/PKG-INFO
writing dependency_links to gpib.egg-info/dependency_links.txt
writing top-level names to gpib.egg-info/top_level.txt
reading manifest file 'gpib.egg-info/SOURCES.txt'
writing manifest file 'gpib.egg-info/SOURCES.txt'
* Building wheel...
/tmp/build-env-qiaffj9e/lib/python3.12/site-packages/setuptools/config/pyprojecttoml.py:72: 
_ExperimentalConfiguration: `[tool.setuptools.ext-modules]` in 
`pyproject.toml` is still *experimental* and likely to cha
nge in future releases.
   config = read_configuration(filepath, True, ignore_option_errors, dist)
running bdist_wheel
running build
running build_py
creating build/lib.linux-x86_64-cpython-312
copying Gpib.py -> build/lib.linux-x86_64-cpython-312
running egg_info
writing gpib.egg-info/PKG-INFO
writing dependency_links to gpib.egg-info/dependency_links.txt
writing top-level names to gpib.egg-info/top_level.txt
reading manifest file 'gpib.egg-info/SOURCES.txt'
writing manifest file 'gpib.egg-info/SOURCES.txt'
running build_ext
building 'gpib' extension
creating build/temp.linux-x86_64-cpython-312
x86_64-linux-gnu-gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O2 
-Wall -fPIC -I../../include -I/tmp/build-env-qiaffj9e/include 
-I/usr/include/python3.12 -c gpibinter.c -o 
build/temp.linux-x86_64-cpython-31
2/gpibinter.o
gpibinter.c:12:10: fatal error: gpib/ib.h: Datei oder Verzeichnis nicht 
gefunden
    12 | #include <gpib/ib.h>
       |          ^~~~~~~~~~~
compilation terminated.
error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1

ERROR Backend subprocess exited when trying to invoke build_wheel
make[3]: [Makefile:494: build] Fehler 1 (ignoriert)

 From what I understand, this would require the header to a) either be 
present locally *in the same* directory, or b) to be included via 
/usr/share/include.
Since the latter is IMO not feasible I will look into getting a) to work.

best,

Matthias Geiger

Re: [Linux-gpib-general] Python bindings

[dave p. <dpe...@gm...>]

After applying your patch I get:

Making all in python
make[3]: Entering directory
'/home/dave/src/linux-gpib-git/linux-gpib-user/language/python'
{ /usr/bin/python -m build && touch build; } || { rm -f -r build; exit 1; }
/usr/bin/python: No module named build.__main__; 'build' is a package and
cannot be directly executed
make[3]: [Makefile:501: build] Error 1 (ignored)
make[3]: Leaving directory
'/home/dave/src/linux-gpib-git/linux-gpib-user/language/python

without your patch I get:

Making all in python
make[3]: Entering directory
'/home/dave/src/linux-gpib-git/linux-gpib-user/language/python'
{ /usr/bin/python setup.py build && touch build; } || { rm -f -r build;
exit 1; }
running build
running build_py
creating build/lib.linux-x86_64-cpython-312
copying Gpib.py -> build/lib.linux-x86_64-cpython-312
running egg_info
creating gpib.egg-info
writing gpib.egg-info/PKG-INFO
writing dependency_links to gpib.egg-info/dependency_links.txt
writing top-level names to gpib.egg-info/top_level.txt
writing manifest file 'gpib.egg-info/SOURCES.txt'
reading manifest file 'gpib.egg-info/SOURCES.txt'
writing manifest file 'gpib.egg-info/SOURCES.txt'
running build_ext
building 'gpib' extension
creating build/temp.linux-x86_64-cpython-312
gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O3 -Wall -fPIC
-I../../include -I/usr/include/python3.12 -c gpibinter.c -o
build/temp.linux-x86_64-cpython-312/gpibinter.o
gcc -shared build/temp.linux-x86_64-cpython-312/gpibinter.o
-L../../lib/.libs -L/usr/lib64 -lgpib -lpthread -o
build/lib.linux-x86_64-cpython-312/gpib.cpython-312-x86_64-linux-gnu.so
make[3]: Leaving directory
'/home/dave/src/linux-gpib-git/linux-gpib-user/language/python'

cheers,
-dave

On Tue, 30 Sept 2025 at 11:34, Matthias Geiger <m_g...@wi...> wrote:

> Hi,
>
> I am finalizing my packaging of the userspace tools for Debian. The
> major blocker to get this uploaded are the python bindings.
> I ran into the following issues:
> - The install path is hardcoded to
> /usr/local/lib/python3.12/dist-packages; this should be
> /usr/lib/$(pythonversion)/distpackages
> - setuptools is deprecated:
>
> running install
> /usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py:66:
> SetuptoolsDeprecationWarning: setup.py install is deprecated.
> !!
>
>
> ********************************************************************************
>          Please avoid running ``setup.py`` directly.
>          Instead, use pypa/build, pypa/installer or other
>          standards-based tools.
>
>          See
> https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for
> details.
>
> ********************************************************************************
>
> !!
>
> Attached you can find a patch that converts the userspace tools to use
> pyproject.toml. This does not work (yet), since
> pyproject can't deal with a header that is not in the same directory as
> the project root:
> https://discuss.python.org/t/include-header-above-project-root/102221/3
> None of the solutions for this are nice; IMO the best would be to
> symlink/copy Gpib.h to the language/python subdirectory.
> Alternatively, the whole build process could be implemented in make,
> however that is not ideal and I'd like to avoid that.
> I'd like to ask for guidance what the project prefers; the current
> setuptools approach will break sooner or later (it's already deprecated).
>
> --
> Freundliche Grüsse / Best regards
>
> Matthias Geiger
> __________________________________________________________________
> Matthias Geiger
> Werkstudent
> Forschung & Entwicklung/Research & Development
>
> Phone : +49-6441-609-3004
> Email : m_g...@wi...
> URL   : www.wiwa.de
>
> WIWA Wilhelm Wagner GmbH & Co. KG
> Gewerbestrasse 1-3, 35633 Lahnau, Germany
> Besucheranschrift/visitor address:
> Georg-Ohm-Strasse 12, 35633 Lahnau, Germany
>
> AG WETZLAR HRA 3223, Komplementär : Wagner GmbH (AG Wetzlar HRB 363)
> UST-ID Nr: / VAT-No: DE113745802
> Geschäftsführer: Dipl.-Ing. (FH) Peter Turczak, Dipl.-Wirt.-Ing. Malte
> Weber
> _______________________________________________
> Linux-gpib-general mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>