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

[Linux-gpib-general] progress?

[<tim...@ex...>]

Hello,

I now have the NI AT-GPIB-TNT software compiled.  Everything seems to be OK until I run ibtest.  The response is "trying to open pad 0..."

But the computer is totally hung.  Have to push reset.  As before, this configuration works under Win98.

I've included some supporting files below.  By the way, I've upgraded to 3.1.3.

Any suggestions appreciated.

Thanks,

Tim



gpib.conf

interface {
        minor = 0
        board_type = atgpib 
        pad = 0
        sad = 0
        timeout = 3s

        eos = 0x0a
        set-reos yes
        set-bin no

        base = 0x2C0
        irq  = 15
        dma  = 7

        master yes
}

device {
        name = bk   
        minor = 0
        pad = 26
        sad = 0
}



[root@speedy root]# lsmod
Module                  Size  Used by    Not tainted
soundcore               4100   0  (autoclean)
tnt4882                 5060   0  (unused)
nec7210                 8096   0  [tnt4882]
gpib-common            13536   0  [tnt4882]
autofs                 10244   0  (autoclean) (unused)
3c59x                  26216   1 
ext3                   62048   6 
jbd                    40376   6  [ext3]
aic7xxx               116256   7 
sd_mod                 11552  14 
scsi_mod               96524   2  [aic7xxx sd_mod]
[root@speedy root]# cat /proc/interrupts
           CPU0       
  0:      24213          XT-PIC  timer
  1:        795          XT-PIC  keyboard
  2:          0          XT-PIC  cascade
  8:          1          XT-PIC  rtc
 10:       7695          XT-PIC  aic7xxx, eth0
 12:       1334          XT-PIC  PS/2 Mouse
NMI:          0 
ERR:          0
[root@speedy root]# cat /proc/ioports
0000-001f : dma1
0020-003f : pic1
0040-005f : timer
0060-006f : keyboard
0070-007f : rtc
0080-008f : dma page reg
00a0-00bf : pic2
00c0-00df : dma2
00f0-00ff : fpu
02f8-02ff : serial(auto)
03c0-03df : vga+
03f8-03ff : serial(auto)
0cf8-0cff : PCI conf1
fc00-fcff : Adaptec AIC-7881U
ff00-ff3f : 3Com Corporation 3c905 100BaseTX [Boomerang]
  ff00-ff3f : 00:0f.0
ffa0-ffaf : Intel Corp. 82371SB PIIX3 IDE [Natoma/Triton II]

dmesg:

Linux-GPIB Driver -- Kernel Release 2.4.18-0.13custom
gpib: registered atgpib interface
gpib: registered ni_pci interface
Available NI device IDs:





------------------------------------------------

Re: [Linux-gpib-general] another try

[frank m. h. <fm...@st...>]

Oops, the driver expects the board_type to be 'atgpib' instead of
'ni_isa'.  It's changed to 'ni_isa' in CVS now, or you can just change
your gpib.conf to use 'atgpib'.  Although, 3.1.2 does have a potentially
nasty race bug which might cause problems during reads, depending on how
fast your device's gpib chip operates.

Frank

On Tue, 30 Apr 2002,  wrote:

>  Hello,
>
> I have done a fresh install of RedHat 7.3 Beta with kernel 2.4.18.  I
> also installed Win98.  Under Win98, the NI AT-GPIB board installed OK
> at IRQ 5, DMA 7, and IO 0x2C0.  I was able to communicate with the
> board and instrument using the NI Windows software.
>
> I was able to get linux-gpib-3.1.2 to compile and the modules to
> install, but cannot communicate.
>
> gpib.conf:
>
> /*******************/
> interface {
>         minor = 0
>         board_type = ni_isa
>         pad = 0
>         sad = 0
>         timeout = 10s
>
>         eos = 0x0a
>         set-reos yes
>         set-bin no
>
>         base = 0x2C0
>         irq  = 5
>         dma  = 7
>
>         master yes
> }
> /*********************/
>
> /* now the device section defines the device characteristics for each device.
>  */
>
>
> device {
>         name = bk
>         minor = 0
>         pad = 26
>         sad = 0
> }
>
>
> dmesg:
>
> Linux-GPIB Driver -- Kernel Release 2.4.18-0.13custom
> gpib: registered atgpib interface
> gpib: registered ni_pci interface
> Available NI device IDs:
>
> lsmod:
>
> [root@speedy linux-gpib-3.1.2]# lsmod
> Module                  Size  Used by    Not tainted
> nls_iso8859-1           2816   0  (autoclean)
> sr_mod                 15192   0  (autoclean)
> cdrom                  27872   0  (autoclean) [sr_mod]
> soundcore               4100   0  (autoclean)
> tnt4882                 5060   0  (unused)
> nec7210                 8064   0  [tnt4882]
> gpib-common            13504   0  [tnt4882]
> autofs                 10244   0  (autoclean) (unused)
> 3c59x                  26216   1
> usb-uhci               21636   0  (unused)
> usbcore                59072   1  [usb-uhci]
> ext3                   62048   6
> jbd                    40376   6  [ext3]
> aic7xxx               116256   7
> sd_mod                 11552  14
> scsi_mod               96524   3  [sr_mod aic7xxx sd_mod]
>
>
>
> ibtest:
>
> [root@speedy linux-gpib-3.1.2]# examples/ibtest
> enter primary address for device [0-30]: 0
> trying to open pad = 0 on /dev/gpib0 ...
>
>  ibBoardFunc    :[Tue Apr 30 17:53:34 2002](-)  EDVR
>                -- errno=19 (No such device)
>
>  ibBoardFunc    :[Tue Apr 30 17:53:34 2002](-)  EDVR
>                -- errno=19 (No such device)
>
>  ibBoardFunc    :[Tue Apr 30 17:53:34 2002](-)  EDVR
>                -- errno=19 (No such device)
> failed to get descriptor
>
>
> [root@speedy linux-gpib-3.1.2]# examples/ibtest
> enter primary address for device [0-30]: 26
> trying to open pad = 26 on /dev/gpib0 ...
>
>  ibBoardFunc    :[Tue Apr 30 17:54:09 2002](-)  EDVR
>                -- errno=19 (No such device)
>
>  ibBoardFunc    :[Tue Apr 30 17:54:09 2002](-)  EDVR
>                -- errno=19 (No such device)
>
>  ibBoardFunc    :[Tue Apr 30 17:54:09 2002](-)  EDVR
>                -- errno=19 (No such device)
> failed to get descriptor
>
>
> /var/log/messages when ibtest is run:
>
> Apr 30 10:58:28 speedy kernel: gpib: no gpib board configured on /dev/gpib0
>
>
>
>
> Any ideas?
>
> Thanks,
>
> Tim
>
>
>
>
>
>
>
> ------------------------------------------------
>
>

[Linux-gpib-general] another try

[<tim...@ex...>]

 Hello,

I have done a fresh install of RedHat 7.3 Beta with kernel 2.4.18.  I
also installed Win98.  Under Win98, the NI AT-GPIB board installed OK
at IRQ 5, DMA 7, and IO 0x2C0.  I was able to communicate with the
board and instrument using the NI Windows software.

I was able to get linux-gpib-3.1.2 to compile and the modules to
install, but cannot communicate.

gpib.conf:

/*******************/
interface {
        minor = 0
        board_type = ni_isa
        pad = 0
        sad = 0
        timeout = 10s

        eos = 0x0a
        set-reos yes
        set-bin no

        base = 0x2C0
        irq  = 5
        dma  = 7

        master yes
}
/*********************/

/* now the device section defines the device characteristics for each device.
 */


device {
        name = bk   
        minor = 0
        pad = 26
        sad = 0
}


dmesg:

Linux-GPIB Driver -- Kernel Release 2.4.18-0.13custom
gpib: registered atgpib interface
gpib: registered ni_pci interface
Available NI device IDs:

lsmod:

[root@speedy linux-gpib-3.1.2]# lsmod
Module                  Size  Used by    Not tainted
nls_iso8859-1           2816   0  (autoclean)
sr_mod                 15192   0  (autoclean)
cdrom                  27872   0  (autoclean) [sr_mod]
soundcore               4100   0  (autoclean)
tnt4882                 5060   0  (unused)
nec7210                 8064   0  [tnt4882]
gpib-common            13504   0  [tnt4882]
autofs                 10244   0  (autoclean) (unused)
3c59x                  26216   1 
usb-uhci               21636   0  (unused)
usbcore                59072   1  [usb-uhci]
ext3                   62048   6 
jbd                    40376   6  [ext3]
aic7xxx               116256   7 
sd_mod                 11552  14 
scsi_mod               96524   3  [sr_mod aic7xxx sd_mod]



ibtest:

[root@speedy linux-gpib-3.1.2]# examples/ibtest
enter primary address for device [0-30]: 0
trying to open pad = 0 on /dev/gpib0 ...

 ibBoardFunc    :[Tue Apr 30 17:53:34 2002](-)  EDVR 
               -- errno=19 (No such device)

 ibBoardFunc    :[Tue Apr 30 17:53:34 2002](-)  EDVR 
               -- errno=19 (No such device)

 ibBoardFunc    :[Tue Apr 30 17:53:34 2002](-)  EDVR 
               -- errno=19 (No such device)
failed to get descriptor


[root@speedy linux-gpib-3.1.2]# examples/ibtest
enter primary address for device [0-30]: 26
trying to open pad = 26 on /dev/gpib0 ...

 ibBoardFunc    :[Tue Apr 30 17:54:09 2002](-)  EDVR 
               -- errno=19 (No such device)

 ibBoardFunc    :[Tue Apr 30 17:54:09 2002](-)  EDVR 
               -- errno=19 (No such device)

 ibBoardFunc    :[Tue Apr 30 17:54:09 2002](-)  EDVR 
               -- errno=19 (No such device)
failed to get descriptor


/var/log/messages when ibtest is run:

Apr 30 10:58:28 speedy kernel: gpib: no gpib board configured on /dev/gpib0




Any ideas?

Thanks,

Tim 







------------------------------------------------

Re: [Linux-gpib-general] NI PCII

[frank m. h. <fm...@st...>]

On Tue, 30 Apr 2002, Joan Valduvieco wrote:

> Running ibtest:
>
> master:~/src/linux-gpib-3.1.3/examples# ./ibtest
> enter primary address for device [0-30]: 7
> trying to open pad = 7 on /dev/gpib0 ...
> gpib: ioports are already in useGPIB Hardware Error! (Chip type not found or
> wrong Base Address?)
>
>  ibBoardFunc    :[Tue Apr 30 15:15:12 2002](-)<  ERR>  EDVR <OS Error>
>                 -- errno=1 (Operation not permitted)
> 		failed to bring device online
> 		failed to get descriptor
>

There was a stray semicolon after the if statement that checked if the
allocation of the ioports was successful.  It's fixed in CVS now.  You'll
need to reboot to free up the ioports that the old driver left allocated.
Thanks for the bug report, let me know how it goes.

Frank

Re: [Linux-gpib-general] NI PCII

[Joan V. <jo...@la...>]

Hi,
No other process using gpib. The board is an original NI pcII. It is 
configured in pcII mode using 7210 mode. Base address is configured to be 
0x2b8 interrupt line 3 and dma 1.

Some information that might be interesting:

/proc/ioports before loading module pc2-gpib.o:

0000-001f : dma1
0020-003f : pic1
0040-005f : timer
0060-006f : keyboard
0070-007f : rtc
0080-008f : dma page reg
00a0-00bf : pic2
00c0-00df : dma2
00f0-00ff : fpu
01f0-01f7 : ide0
03c0-03df : vga+
03f6-03f6 : ide0
03f8-03ff : serial(set)
0cf8-0cff : PCI conf1
	d000-d07f : VIA Technologies, Inc. VT86C100A [Rhine 10/100]
d000-d07f : via-rhine
d400-d41f : Intel Corp. 82371AB PIIX4 USB
d800-d80f : Intel Corp. 82371AB PIIX4 IDE
	d800-d807 : ide0
	d808-d80f : ide1
e400-e43f : Intel Corp. 82371AB PIIX4 ACPI
e800-e81f : Intel Corp. 82371AB PIIX4 ACPI

/proc/interrupts:

CPU0
0:      76844          XT-PIC  timer
1:       1994          XT-PIC  keyboard
2:          0          XT-PIC  cascade
8:          3          XT-PIC  rtc
10:       9835          XT-PIC  eth0
12:       4697          XT-PIC  PS/2 Mouse
14:       1461          XT-PIC  ide0
NMI:          0
ERR:          0

Loading the module I get:

master:~/src/linux-gpib-3.1.3# modprobe pc2-gpib
Linux-GPIB Driver -- Kernel Release 2.4.18
gpib: registered pcII interface
gpib: registered pcIIa interface

ioports and interrupts remain the same. 
On /var/log/syslog I see:

Apr 30 17:03:40 master kernel: Linux-GPIB Driver -- Kernel Release 2.4.18
Apr 30 17:03:40 master kernel: gpib: registered pcII interface
Apr 30 17:03:40 master kernel: gpib: registered pcIIa interface

Running ibtest:

master:~/src/linux-gpib-3.1.3/examples# ./ibtest
enter primary address for device [0-30]: 7
trying to open pad = 7 on /dev/gpib0 ...
gpib: ioports are already in useGPIB Hardware Error! (Chip type not found or 
wrong Base Address?)

 ibBoardFunc    :[Tue Apr 30 15:15:12 2002](-)<  ERR>  EDVR <OS Error>
                -- errno=1 (Operation not permitted)
		failed to bring device online
		failed to get descriptor

/proc/interrupts and /proc/ioports:

master:~/src/linux-gpib-3.1.3/examples# cat /proc/interrupts
CPU0
0:      91948          XT-PIC  timer
1:       2969          XT-PIC  keyboard
2:         0          XT-PIC  cascade
8:          3          XT-PIC  rtc
10:      11017          XT-PIC  eth0
12:       6263          XT-PIC  PS/2 Mouse
14:       1547          XT-PIC  ide0
NMI:          0
ERR:          0

master:~/src/linux-gpib-3.1.3/examples# cat /proc/ioports
0000-001f : dma1
0020-003f : pic1
0040-005f : timer
0060-006f : keyboard
0070-007f : rtc
0080-008f : dma page reg
00a0-00bf : pic2
00c0-00df : dma2
00f0-00ff : fpu
01f0-01f7 : ide0
02b8-02bf : pc2	<----------------
03c0-03df : vga+
03f6-03f6 : ide0
03f8-03ff : serial(set)
0cf8-0cff : PCI conf1
d000-d07f : VIA Technologies, Inc. VT86C100A [Rhine 10/100]
  d000-d07f : via-rhine
d400-d41f : Intel Corp. 82371AB PIIX4 USB
d800-d80f : Intel Corp. 82371AB PIIX4 IDE
	d800-d807 : ide0
	d808-d80f : ide1
e400-e43f : Intel Corp. 82371AB PIIX4 ACPI
e800-e81f : Intel Corp. 82371AB PIIX4 ACPI

As you can see iobase isn't freed. lsof says that nobody is accessing 
/dev/gpib*

More info:
Major and minors..
master:~/src/linux-gpib-3.1.3/examples# ls -l /dev/gpib*
crw-rw----    1 root     gpib     160,   0 Apr 25 18:59 /dev/gpib0
crw-rw----    1 root     gpib     160,   1 Apr 25 18:59 /dev/gpib1
crw-rw----    1 root     gpib     160,  10 Apr 25 18:59 /dev/gpib10
crw-rw----    1 root     gpib     160,  11 Apr 25 18:59 /dev/gpib11
crw-rw----    1 root     gpib     160,  12 Apr 25 18:59 /dev/gpib12
crw-rw----    1 root     gpib     160,  13 Apr 25 18:59 /dev/gpib13
crw-rw----    1 root     gpib     160,  14 Apr 25 18:59 /dev/gpib14
crw-rw----    1 root     gpib     160,  15 Apr 25 18:59 /dev/gpib15
crw-rw----    1 root     gpib     160,   2 Apr 25 18:59 /dev/gpib2
crw-rw----    1 root     gpib     160,   3 Apr 25 18:59 /dev/gpib3
crw-rw----    1 root     gpib     160,   4 Apr 25 18:59 /dev/gpib4
crw-rw----    1 root     gpib     160,   5 Apr 25 18:59 /dev/gpib5
crw-rw----    1 root     gpib     160,   6 Apr 25 18:59 /dev/gpib6
crw-rw----    1 root     gpib     160,   7 Apr 25 18:59 /dev/gpib7
crw-rw----    1 root     gpib     160,   8 Apr 25 18:59 /dev/gpib8
crw-rw----    1 root     gpib     160,   9 Apr 25 18:59 /dev/gpib9

/etc/gpib.conf:
interface {
	minor = 0
	board_type = pcII
	pad = 0
	sad = 0
	timeout = 3s

	eos = 0x0a
	set-reos yes
	set-bin no

	base = 0x02b8
	irq  = 3
	dma  = 1

	master yes
}

Hope this helps. Have I missed something?

Thanks for your time.
Joan



A Divendres 26 Abril 2002 20:24, vàreu escriure:
> On Fri, 26 Apr 2002, Joan Valduvieco wrote:
> > Hi,
> > I've been trying to configure NI PCII in PCII mode with
> > linux-gpib-3.1.3.I'm "sure" that base address, IRQ and DMA are well
> > configured, module is loaded but I can't comunicate with GPIB bus.
> > I always get a resurce busy when runing: #./ibtest
>
> Do you have any other processes running that are using the gpib board?
> Could you send a copy of the program's output when it fails, and any
> relevent messages in 'dmesg'?
>
> Frank

Re: [Linux-gpib-general] NI PCII

[Joan V. <jo...@la...>]

Ok,
On monday I'll send it. If anyone has this card working please let me know as 
it would be my fault.
No, I haven't any other proces using it.

Joan

A Divendres 26 Abril 2002 20:24, vàreu escriure:
> On Fri, 26 Apr 2002, Joan Valduvieco wrote:
> > Hi,
> > I've been trying to configure NI PCII in PCII mode with
> > linux-gpib-3.1.3.I'm "sure" that base address, IRQ and DMA are well
> > configured, module is loaded but I can't comunicate with GPIB bus.
> > I always get a resurce busy when runing: #./ibtest
>
> Do you have any other processes running that are using the gpib board?
> Could you send a copy of the program's output when it fails, and any
> relevent messages in 'dmesg'?
>
> Frank
>
>
> _______________________________________________
> Linux-gpib-general mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general

Re: [Linux-gpib-general] NI PCII

[frank m. h. <fm...@st...>]

On Fri, 26 Apr 2002, Joan Valduvieco wrote:

> Hi,
> I've been trying to configure NI PCII in PCII mode with linux-gpib-3.1.3.I'm
> "sure" that base address, IRQ and DMA are well configured, module is loaded
> but I can't comunicate with GPIB bus.
> I always get a resurce busy when runing: #./ibtest

Do you have any other processes running that are using the gpib board?
Could you send a copy of the program's output when it fails, and any
relevent messages in 'dmesg'?

Frank

[Linux-gpib-general] NI PCII

[Joan V. <jo...@la...>]

Hi,
I've been trying to configure NI PCII in PCII mode with linux-gpib-3.1.3.I'm 
"sure" that base address, IRQ and DMA are well configured, module is loaded 
but I can't comunicate with GPIB bus. 
I always get a resurce busy when runing: #./ibtest
If I cat /proc/ioports I see that pc2 has reserved my base port. Sometimes 
when looking /proc/ioports I get a segmentation fault and must reboot.
Any suggest? succes history, tip?
Has anyone a NI PCII working with linux-gpib-3.1.3 or .1.2?

Thanks for your time,
Joan

[Linux-gpib-general] linux-gpib 3.1.3

[frank m. h. <fm...@st...>]

linux-gpib-3.1.3 is available for download.

Changes:

Fixed race in nec7210 read that could cause failure to receive last byte
on reads. Board-specific fixes for ines pci, ines pcmcia, and cec/keithley
pci support.

Frank

Re: [Linux-gpib-general] CEC PC488 board?

[frank m. h. <fm...@st...>]

It should work as a pcII (not a pcIIa) board.

Frank

On Thu, 18 Apr 2002, Stephen Broccardo wrote:

> Hello
>
> I have an old ISA PC488 board from CEC. Since it is
> based on the NEC7210 chip, would I be correct in
> assuming that it will behave like an NEC PCII(a) card?
> Or would the PCI CEC driver work? Or am I outta luck?
>
> Thanks
>
> Steve
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Tax Center - online filing with TurboTax
> http://taxes.yahoo.com/
>
> _______________________________________________
> Linux-gpib-general mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>

[Linux-gpib-general] CEC PC488 board?

[Stephen B. <sbr...@ya...>]

Hello

I have an old ISA PC488 board from CEC. Since it is
based on the NEC7210 chip, would I be correct in
assuming that it will behave like an NEC PCII(a) card?
Or would the PCI CEC driver work? Or am I outta luck?

Thanks 

Steve

__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/

Re: [Linux-gpib-general] ...and inching closer...

[frank m. h. <fm...@st...>]

You should be able to manually conduct serial polls using the ibrsp()
function.  All the 'autopolling' support is broken at the moment though.

Frank

On Tue, 16 Apr 2002, Sridhar Anandakrishnan wrote:

> Hi all on the linux-gpib list - I wonder if you can answer this
> question...
>
> When I want to download a waveform from the oscilloscope, is there a way
> for the user-level program to be informed when the acquisition is done?
> The scope will take 500ms to finish, and is there an interrupt that is
> generated by the linux-gpib code when the oscilloscope sets the Operation
> Complete bit in the status register?  Or is there a way to poll
> periodically from the user level?
>
> I want to ask the scope to average 500 triggers (1ms apart), and then I
> want to download those data.  If I simply send the "acquire" command and
> then immediately request the data "curve?", the 500 averages won't be over
> - what will happen?  Does the software hold the request until the scope is
> done?  Or is the command sent out right away (in which case I think the
> scope responds with the 'incomplete' data - not enough averages...)
>
> I apologize if this question isn't very clear...
>
> Thanks,
> Sridhar.
>
> Sridhar Anandakrishnan  		email:	sa...@es...
> 442 Deike Bldg				Phone: 	(814) 863-6742
> Pennsylvania State University		Dept:	      863-6052
> University Park, PA 16802-2711		Fax:          863-8724
>
>

Re: [Linux-gpib-general] ...and inching closer...

[Sridhar A. <sa...@ge...>]

Hi all on the linux-gpib list - I wonder if you can answer this
question...

When I want to download a waveform from the oscilloscope, is there a way
for the user-level program to be informed when the acquisition is done?
The scope will take 500ms to finish, and is there an interrupt that is
generated by the linux-gpib code when the oscilloscope sets the Operation
Complete bit in the status register?  Or is there a way to poll
periodically from the user level?

I want to ask the scope to average 500 triggers (1ms apart), and then I
want to download those data.  If I simply send the "acquire" command and
then immediately request the data "curve?", the 500 averages won't be over
- what will happen?  Does the software hold the request until the scope is
done?  Or is the command sent out right away (in which case I think the
scope responds with the 'incomplete' data - not enough averages...)

I apologize if this question isn't very clear...

Thanks,
Sridhar.

Sridhar Anandakrishnan  		email:	sa...@es...
442 Deike Bldg				Phone: 	(814) 863-6742
Pennsylvania State University		Dept:	      863-6052
University Park, PA 16802-2711		Fax:          863-8724

[Linux-gpib-general] unresolved symbols

[<tim...@ex...>]

 Hello,

I posted a bit ago about "unresolved symbols".  I have not been able to get depmod -e to report and problems, but I insmod reported this:

[root@speedy linux-gpib-3.1.2]# insmod /lib/modules/2.4.7-10custom/misc/gpib-common.o
/lib/modules/2.4.7-10custom/misc/gpib-common.o: unresolved symbol register_chrdev_R82739b6c

Does this mean anything?

Thanks again,

Tim






------------------------------------------------

Re: [Linux-gpib-general] (no subject)

[<tim...@ex...>]

 OK, now I'm really confused.  Running "depmod -e" returns nothing!

But the install script line I quoted claims to find unresolved symbol. 

Maybe I'm doing something really ignorant here...

Tim





--- On Fri 04/05, frank mori hess  wrote:
> 
> 
> On Fri, 5 Apr 2002,  wrote:
> 
> >  Hello,
> >
> > Here is the output from depmod -e :
> >
> >
> > [root@speedy linux-gpib-3.1.2]#  depmod -e
> 2.4.7-10custom/misc/gpib-common.o
> > # module             id=string
> > # pci module         vendor     device     subvendor  subdevice 
> class      class_mask driver_data
> > # isapnp module      cardvendor carddevice driver_data vendor    
> function   ...
> > # usb module         match_flags idVendor idProduct bcdDevice_lo
> bcdDevice_hi bDeviceClass bDeviceSubClass bDeviceProtocol bInterfaceClass
> bInterfaceSubClass bInterfaceProtocol driver_info
> > # module             pattern
> >
> 
> We're not getting any unresolved symbols here.  You want to run 'depmod
> -e' with no arguments.
> 
> Frank
> 
> 
> _______________________________________________
> Linux-gpib-general mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
> 

------------------------------------------------

Re: [Linux-gpib-general] (no subject)

[frank m. h. <fm...@st...>]

On Fri, 5 Apr 2002,  wrote:

>  Hello,
>
> Here is the output from depmod -e :
>
>
> [root@speedy linux-gpib-3.1.2]#  depmod -e 2.4.7-10custom/misc/gpib-common.o
> # module             id=string
> # pci module         vendor     device     subvendor  subdevice  class      class_mask driver_data
> # isapnp module      cardvendor carddevice driver_data vendor     function   ...
> # usb module         match_flags idVendor idProduct bcdDevice_lo bcdDevice_hi bDeviceClass bDeviceSubClass bDeviceProtocol bInterfaceClass bInterfaceSubClass bInterfaceProtocol driver_info
> # module             pattern
>

We're not getting any unresolved symbols here.  You want to run 'depmod
-e' with no arguments.

Frank

Re: [Linux-gpib-general] (no subject)

[<tim...@ex...>]

 Hello,

Here is the output from depmod -e :


[root@speedy linux-gpib-3.1.2]#  depmod -e 2.4.7-10custom/misc/gpib-common.o
# module             id=string
# pci module         vendor     device     subvendor  subdevice  class      class_mask driver_data
# isapnp module      cardvendor carddevice driver_data vendor     function   ...
# usb module         match_flags idVendor idProduct bcdDevice_lo bcdDevice_hi bDeviceClass bDeviceSubClass bDeviceProtocol bInterfaceClass bInterfaceSubClass bInterfaceProtocol driver_info
# module             pattern


Thanks,

Tim




--- On Thu 04/04, frank mori hess  wrote:
> 
> What is the ouput of 'depmod -e'?
> 
> Frank
> 
> On Thu, 4 Apr 2002,  wrote:
> 
> >
> > Hello,
> >
> > I have compiled linux-gpib-3.1.2 with no errors.  However, when I do
> "make install", I get the following message:
> >
> > depmod -a 2.4.7-10custom
> > depmod: *** Unresolved symbols in
> /lib/modules/2.4.7-10custom/misc/gpib-common.o
> >
> > depmod: *** Unresolved symbols in
> /lib/modules/2.4.7-10custom/misc/nec7210.o
> >
> > depmod: *** Unresolved symbols in
> /lib/modules/2.4.7-10custom/misc/tms9914.o
> >
> > I am running RedHat 7.2.  Any ideas what might be happening here?
> >
> > Thank you,
> >
> > Tim Holmes
> >
> >
> >
> >
> >
> > ------------------------------------------------
> >
> >
> > _______________________________________________
> > Linux-gpib-general mailing list
> > Lin...@li...
> > https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
> >
> 
> 

------------------------------------------------

Re: [Linux-gpib-general] Problems compiling 3.1.2 on a Red Hat 7.2 system

[Marc L. <Mar...@un...>]

On Fri, 5 Apr 2002 09:43:59 -0600 (CST),=20
frank mori hess <fm...@st...> wrote :

Dear Frank,

thanks a lot for your quick answer and help.

> Marc,
>=20
> There are at least 3 different pci codes for ines pci boards, try looki=
ng
> through the driver provided by ines.  There are a few source code files=
,
> and I remember the pci ids are listed in one of them (driver/ie_pci.c i=
n
> the ines package), also I remember the different boards used different

You're right. In fact, I tried first their linux-2.2 driver, which had
no source code with it. Indeed, the lab machine was running a 2.2 kernel.

I then found about linux-gpib, and moved the board to a 2.4 machine
for testing since there was apparently no 2.2 driver available. Thus,
I did not look at the ines 2.4 driver because I thought there
absolutely no source code of the driver available. It looks like there
is now only ieksys.o whose source code is not available.

> base address indexes for their gpib chip.  There will probably also be
> some interrupt-related issues depending on what kind of pci chip the bo=
ard
> you have is using (amcc5920 apparently).

OK. I will have a look at their source code and try their 2.4 driver.
After a quick look, they seem to do the pci_find_device with the same
values as me so that call shoulsd succeed but you are right that they
seem to different things with different boards.

I guess I need to have a closer look at that.


>  By the way, the id numbers are given in hex, maybe you entered them
> as decimal?

I have fallen too often into that trap not to immune now :-)

/* #define INES_VENDOR_ID 0x10b5 */
/* #define INES_DEV_ID    0x9050 */
/* #define INES_SUBID 0x107210b5L */
#define INES_VENDOR_ID 0x10e8
#define INES_DEV_ID    0x8259


>=20
> Frank

By the way, I have got in touch with INES support this week. Their
linux developer is on vacation this week, but should come back to me
next week. Do you want me to suggest them that they should help you
more ?

Marc


--=20
_____________________________________________________________
 Marc Lefranc, Charg=E9 de Recherche au CNRS
 Laboratoire de Physique des Lasers, Atomes, Mol=E9cules
 Bat P5, UFR de Physique
 Universit=E9 des Sciences et Technologies de Lille
 F-59655 Villeneuve d'Ascq CEDEX (FRANCE)
 e-mail: Mar...@un...
 Tel : +33 (0)3 20 33 64 50 ;  FAX : +33 (0)3 20 33 70 20
_____________________________________________________________

Re: [Linux-gpib-general] Problems compiling 3.1.2 on a Red Hat 7.2 system

[frank m. h. <fm...@st...>]

Marc,

There are at least 3 different pci codes for ines pci boards, try looking
through the driver provided by ines.  There are a few source code files,
and I remember the pci ids are listed in one of them (driver/ie_pci.c in
the ines package), also I remember the different boards used different
base address indexes for their gpib chip.  There will probably also be
some interrupt-related issues depending on what kind of pci chip the board
you have is using (amcc5920 apparently).  By the way, the id numbers are
given in hex, maybe you entered them as decimal?

Frank

On 5 Apr 2002, Marc Lefranc wrote:

> On 05 Apr 2002 16:59:08 +0200,
> Marc Lefranc <Mar...@un...> wrote :
> > Looking in driver/ines/ines_init.c, I see that the init code looks for
> > a board that has vendor_id and device_id INES_VENDOR_ID and
> > INES_DEV_ID, but my Ines board does not advertise itself as such :
> >
> > /sbin/lspci -vv :
> >
> > 00:0b.0 PIC: Applied Micro Circuits Corporation: Unknown device 8507 (p=
rog-if 00 [8259])
> [...]
> > I will try to replace the INES_VENDOR_ID and INES_DEV_ID with the
> > values obtained with lspci and see what happens.
>
> Well, this didn't help : I still get the same error message...
>
> I am quite surprised that pci_find_device does not find the vendor and
> device id listed by lspci ??
>
> Marc
>
> If that helps, here is the output ls lspci -vvx :
>
> 00:0b.0 PIC: Applied Micro Circuits Corporation: Unknown device 8507 (pro=
g-if 00 [8259])
> =09Subsystem: Applied Micro Circuits Corporation: Unknown device 1072
> =09Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- St=
epping- SERR- FastB2B-
> =09Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=3Dmedium >TAbort- <TA=
bort- <MAbort- >SERR- <PERR-
> =09Interrupt: pin A routed to IRQ 5
> =09Region 0: I/O ports at e400 [size=3D128]
> =09Region 1: I/O ports at e800 [size=3D32]
> 00: e8 10 07 85 03 00 80 02 00 00 00 08 00 00 00 00
> 10: 01 e4 00 00 01 e8 00 00 00 00 00 00 00 00 00 00
> 20: 00 00 00 00 00 00 00 00 00 00 00 00 e8 10 72 10
> 30: 00 00 00 00 00 00 00 00 00 00 00 00 05 01 00 00
>
>
>
> --
> _____________________________________________________________
>  Marc Lefranc, Charg=E9 de Recherche au CNRS
>  Laboratoire de Physique des Lasers, Atomes, Mol=E9cules
>  Bat P5, UFR de Physique
>  Universit=E9 des Sciences et Technologies de Lille
>  F-59655 Villeneuve d'Ascq CEDEX (FRANCE)
>  e-mail: Mar...@un...
>  Tel : +33 (0)3 20 33 64 50 ;  FAX : +33 (0)3 20 33 70 20
> _____________________________________________________________
>
> _______________________________________________
> Linux-gpib-general mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>

Re: [Linux-gpib-general] Problems compiling 3.1.2 on a Red Hat 7.2 system

[Marc L. <Mar...@un...>]

On 05 Apr 2002 16:59:08 +0200,=20
Marc Lefranc <Mar...@un...> wrote :
> Looking in driver/ines/ines_init.c, I see that the init code looks for
> a board that has vendor_id and device_id INES_VENDOR_ID and
> INES_DEV_ID, but my Ines board does not advertise itself as such :
>=20
> /sbin/lspci -vv :
>=20
> 00:0b.0 PIC: Applied Micro Circuits Corporation: Unknown device 8507 (p=
rog-if 00 [8259])
[...]
> I will try to replace the INES_VENDOR_ID and INES_DEV_ID with the
> values obtained with lspci and see what happens.

Well, this didn't help : I still get the same error message...

I am quite surprised that pci_find_device does not find the vendor and
device id listed by lspci ??

Marc

If that helps, here is the output ls lspci -vvx :

00:0b.0 PIC: Applied Micro Circuits Corporation: Unknown device 8507 (pro=
g-if 00 [8259])
	Subsystem: Applied Micro Circuits Corporation: Unknown device 1072
	Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Step=
ping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=3Dmedium >TAbort- <TAbo=
rt- <MAbort- >SERR- <PERR-
	Interrupt: pin A routed to IRQ 5
	Region 0: I/O ports at e400 [size=3D128]
	Region 1: I/O ports at e800 [size=3D32]
00: e8 10 07 85 03 00 80 02 00 00 00 08 00 00 00 00
10: 01 e4 00 00 01 e8 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 e8 10 72 10
30: 00 00 00 00 00 00 00 00 00 00 00 00 05 01 00 00



--=20
_____________________________________________________________
 Marc Lefranc, Charg=E9 de Recherche au CNRS
 Laboratoire de Physique des Lasers, Atomes, Mol=E9cules
 Bat P5, UFR de Physique
 Universit=E9 des Sciences et Technologies de Lille
 F-59655 Villeneuve d'Ascq CEDEX (FRANCE)
 e-mail: Mar...@un...
 Tel : +33 (0)3 20 33 64 50 ;  FAX : +33 (0)3 20 33 70 20
_____________________________________________________________

Re: [Linux-gpib-general] Problems compiling 3.1.2 on a Red Hat 7.2 system

[Marc L. <Mar...@un...>]

On 05 Apr 2002 14:09:00 +0200,=20
Marc Lefranc <Mar...@un...> wrote :


> However, I have some problems just compiling the stuff. I have began
> fixing some things, but I would like to have some feedback.

OK. I have downloaded linux-2.4.19-pre6 and compiled it, and then made
another attempt at compiling and installing linux-gpib-3.1.2.

This time everything went perfectly smoothly. Really strange. I guess
subtle things have changed since 2.4.9.

Anyway, the driver now loads but it can't find the INES board. This is
the message I get when I try to run the ibtest program :

Apr  5 16:25:21 cusp kernel: Linux-GPIB Driver -- Kernel Release 2.4.19-p=
re6
Apr  5 16:25:21 cusp kernel: gpib: registered ines_pci interface
Apr  5 16:25:50 cusp kernel: gpib: no ines PCI board found
Apr  5 16:25:50 cusp kernel: GPIB Hardware Error! (Chip type not found or=
 wrong Base Address?)

Looking in driver/ines/ines_init.c, I see that the init code looks for
a board that has vendor_id and device_id INES_VENDOR_ID and
INES_DEV_ID, but my Ines board does not advertise itself as such :

/sbin/lspci -vv :

00:0b.0 PIC: Applied Micro Circuits Corporation: Unknown device 8507 (pro=
g-if 00 [8259])
	Subsystem: Applied Micro Circuits Corporation: Unknown device 1072
	Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Step=
ping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=3Dmedium >TAbort- <TAbo=
rt- <MAbort- >SERR- <PERR-
	Interrupt: pin A routed to IRQ 5
	Region 0: I/O ports at e400 [size=3D128]
	Region 1: I/O ports at e800 [size=3D32]


I will try to replace the INES_VENDOR_ID and INES_DEV_ID with the
values obtained with lspci and see what happens.

All the best,
Marc

--=20
_____________________________________________________________
 Marc Lefranc, Charg=E9 de Recherche au CNRS
 Laboratoire de Physique des Lasers, Atomes, Mol=E9cules
 Bat P5, UFR de Physique
 Universit=E9 des Sciences et Technologies de Lille
 F-59655 Villeneuve d'Ascq CEDEX (FRANCE)
 e-mail: Mar...@un...
 Tel : +33 (0)3 20 33 64 50 ;  FAX : +33 (0)3 20 33 70 20
_____________________________________________________________

Re: [Linux-gpib-general] Problems compiling 3.1.2 on a Red Hat 7.2 system

[Marc L. <Mar...@un...>]

On 05 Apr 2002 14:09:00 +0200,=20
Marc Lefranc <Mar...@un...> wrote :
>=20
> P.S. If that can help, here his the output of=20
>=20
> nm /lib/modules/2.4.9-31/misc/gpib-common.o :

Oops. Since I sent the message, I found the April section of the
archive (for whatever reason, I had only came across the March one
without noticing that this was only March), and saw the request about
depmod -e. Here is the result.

This looks quite strange if you ask me. jiffies is not resolved?

748 # depmod -e
depmod: *** Unresolved symbols in /lib/modules/2.4.9-31/misc/gpib-common.=
o
depmod: 	__wake_up
depmod: 	__generic_copy_from_user
depmod: 	unregister_chrdev
depmod: 	register_chrdev
depmod: 	vfree
depmod: 	boot_cpu_data
depmod: 	interruptible_sleep_on_timeout
depmod: 	del_timer
depmod: 	tvec_bases
depmod: 	jiffies
depmod: 	__vmalloc
depmod: 	printk
depmod: 	add_timer
depmod: 	__const_udelay
depmod: 	__generic_copy_to_user
depmod: *** Unresolved symbols in /lib/modules/2.4.9-31/misc/ines-gpib.o
depmod: 	kmalloc
depmod: 	pci_enable_device
depmod: 	free_irq
depmod: 	write_byte
depmod: 	pci_release_regions
depmod: 	kfree
depmod: 	request_irq
depmod: 	pci_find_device
depmod: 	printk
depmod: 	pci_request_regions
depmod: *** Unresolved symbols in /lib/modules/2.4.9-31/misc/nec7210.o
depmod: 	__wake_up
depmod: 	schedule
depmod: 	remove_wait_queue
depmod: 	interruptible_sleep_on_timeout
depmod: 	write_byte
depmod: 	read_byte
depmod: 	add_wait_queue
depmod: 	printk
depmod: 	__const_udelay
depmod: *** Unresolved symbols in /lib/modules/2.4.9-31/misc/tms9914.o
depmod: 	__wake_up
depmod: 	schedule
depmod: 	remove_wait_queue
depmod: 	interruptible_sleep_on_timeout
depmod: 	write_byte
depmod: 	read_byte
depmod: 	add_wait_queue
depmod: 	printk
depmod: 	__const_udelay



--=20
_____________________________________________________________
 Marc Lefranc, Charg=E9 de Recherche au CNRS
 Laboratoire de Physique des Lasers, Atomes, Mol=E9cules
 Bat P5, UFR de Physique
 Universit=E9 des Sciences et Technologies de Lille
 F-59655 Villeneuve d'Ascq CEDEX (FRANCE)
 e-mail: Mar...@un...
 Tel : +33 (0)3 20 33 64 50 ;  FAX : +33 (0)3 20 33 70 20
_____________________________________________________________

[Linux-gpib-general] Problems compiling 3.1.2 on a Red Hat 7.2 system

[Marc L. <Mar...@un...>]

Hi,

I have been very happy to discover this week the existence of
linux-gpib.sourceforge.net. A long time ago, I had had a look at
linux-gpib (I have been using linux since 1995) but unfortunately none
of the GP-IB boards we had at that time were supported.

Recently, we have purchased GPIB-PCI card by Ines as they advertised
it to be supported under linux. Admittedly, they provide kernel
modules for linux 2.2 and 2.4, and one or two sample programs, but
without the source, and no high-level library.

Therefore, I was very happy to find out that (1) linux-gpib had been
resurrected and (2) that it supported Ines boards. I am thus currently
evaluating it.=20

However, I have some problems just compiling the stuff. I have began
fixing some things, but I would like to have some feedback.

This on a Pentium II machine running Red Hat Linux 7.2 (will all
updates applied). I usually compile my kernels, but I have found the
2.4 series a bit unresponsive, and none of the kernels I tried (up to
2.4.19-pre5) has been able to equal the performance of the Red Hat
kernels, contrary to what I was accustomed to.

Thus, I would like to stick to the latest kernel update (2.4.9-31) to
keep the platform stable once everything is in order.

What I have done :=20

1) rpm -i kernel-source.XXXX.rpm (unpacks in /usr/src/linux-2.4.9-31),=20
   cd /usr/src/linux-2.4.9-31
   modify Makefile so that EXTRAVERSION is -31
   cp configs/kernel-2.4.9-i586.config/ .config
   make oldconfig
   make dep

2) go to the freshly untarred linux-gpib-3.1.2 directory;
   make [I indicate /usr/src/linux-2.4.9-31 as the kernel source
         directory, and select the Ines driver only]=20
   compilation begins, with lots of error messages such as=20

make[2]: Entering directory `/home/lefranc/MANIP/gpib/linux-gpib-3.1.2/dr=
iver/nec7210'
gcc -I. -I../include -I../../include  -DEXPORT_SYMTAB   -c -o cmd.o cmd.c
In file included from /usr/include/linux/module.h:21,
                 from board.h:25,
                 from cmd.c:19:
/usr/include/linux/modversions.h:1:2: #error Modules should never use ker=
nel-headers system headers,
/usr/include/linux/modversions.h:2:2: #error but rather headers from an a=
ppropriate kernel-source package.
/usr/include/linux/modversions.h:3:2: #error Change -I/usr/src/linux/incl=
ude (or similar) to
/usr/include/linux/modversions.h:4:2: #error -I/lib/modules/$(uname -r)/b=
uild/include
/usr/include/linux/modversions.h:5:2: #error to build against the current=
ly-running kernel.

OK. I have a look at the Makefiles in driver/* and notice that only
driver/protocol/Makefile has

INCLUDES =3D -I. -I../include -I../../include -I$(LINUXDIR)/include

, while all the others have

INCLUDES =3D -I. -I../include -I../../include

Thus, I add the -I$(LINUXDIR)/include to Makefiles in
driver/{nec7210,tms9914,sys

But then I get errors such as=20

make[2]: Entering directory `/home/lefranc/MANIP/gpib/linux-gpib-3.1.2/dr=
iver/nec7210'
gcc -I. -I../include -I../../include -I"/usr/src/linux-2.4.9-31"/include =
 -DEXPORT_SYMTAB   -c -o cmd.o cmd.c
In file included from ../include/gpib_types.h:22,
                 from ../include/gpibP.h:9,
                 from board.h:23,
                 from cmd.c:19:
/usr/include/stdint.h:37: warning: redefinition of `int8_t'
/usr/src/linux-2.4.9-31/include/linux/types.h:98: warning: `int8_t' previ=
ously declared here
/usr/include/stdint.h:38: warning: redefinition of `int16_t'
/usr/src/linux-2.4.9-31/include/linux/types.h:100: warning: `int16_t' pre=
viously declared here

The problem here is a conflict between standard include files and
those of the kernel. SInce I have done a bit of kernel programming in
the past (writing a driver for an DAQ board), this rings a bell, and I
wonder about the absence of a -D__KERNEL__ in the CFLAGS for compiling
bits of amodule.

SInce all driver/*/Makefile have a line

CFLAGS +=3D $(INCLUDES) $(OPTIONS) -DEXPORT_SYMTAB

I add the following line in driver/Makefile

OPTIONS =3D -D__KERNEL__

(actually, I had to manually add a -D__KERNEL__ to the CFLAGS line of
driver/sys/Makefile)

With these modifications, the whole stuff seems to compile fine.=20

For installation, I had the problem that MODLIB was not defined for
whatever reason so that I had to do

make MODLIB=3D/lib/modules/2.4.9-31 install

I then get :

[...]
install  -D ines-gpib.o /lib/modules/2.4.9-31/misc/ines-gpib.o
make[2]: Leaving directory `/home/lefranc/MANIP/gpib/linux-gpib-3.1.2/dri=
ver/ines'
depmod -a=20
depmod: *** Unresolved symbols in /lib/modules/2.4.9-31/misc/gpib-common.=
o
depmod: *** Unresolved symbols in /lib/modules/2.4.9-31/misc/ines-gpib.o
depmod: *** Unresolved symbols in /lib/modules/2.4.9-31/misc/nec7210.o
depmod: *** Unresolved symbols in /lib/modules/2.4.9-31/misc/tms9914.o
make[1]: *** [install] Error 1
make[1]: Leaving directory `/home/lefranc/MANIP/gpib/linux-gpib-3.1.2/dri=
ver'
make: *** [install] Error 2

Is 2.4.9 too old ?=20

Thank you very much in advance.

Marc



P.S. If that can help, here his the output of=20

nm /lib/modules/2.4.9-31/misc/gpib-common.o :

00002368 T AP_Init
000023d0 T AP_LocalLock
000023f4 T AP_LocalUnLock
00002338 T AP_Lock
00002350 T AP_UnLock
000003e0 C AP_Vector
00000170 D AP_virgin
0000015c D AutoP_mutex
00000030 r DRIVERBITS
000001b0 r DRIVERBITS
000004b0 r DRIVERBITS
00000570 r DRIVERBITS
00000630 r DRIVERBITS
00000690 r DRIVERBITS
00000790 r DRIVERBITS
000007f0 r DRIVERBITS
00000910 r DRIVERBITS
00000990 r DRIVERBITS
000009f0 r DRIVERBITS
00000a50 r DRIVERBITS
00000ad0 r DRIVERBITS
00000b50 r DRIVERBITS
00000bd0 r DRIVERBITS
00000cb0 r DRIVERBITS
00000d50 r DRIVERBITS
00000db0 r DRIVERBITS
00000e70 r DRIVERBITS
         U __const_udelay
0000110c t __constant_c_memset
00001010 t __constant_copy_from_user
00000f24 t __constant_copy_to_user
         U __down_failed
         U __down_failed_interruptible
         U __generic_copy_from_user
         U __generic_copy_to_user
00000000 ? __kstrtab_gpib_register_driver
00000040 ? __kstrtab_gpib_unregister_driver
00000000 ? __ksymtab_gpib_register_driver
00000008 ? __ksymtab_gpib_unregister_driver
000014e8 t __list_add
00001500 t __list_del
         U __up_wakeup
         U __vmalloc
         U __wake_up
         U add_timer
00000680 C board_array
00000900 T board_type_ioctl
         U boot_cpu_data
00001400 T cleanup_module
00001624 t clear_bit
00001ba4 t clear_bit
0000211c t clear_bit
00000b04 T command_ioctl
00001a2c t constant_test_bit
00001d40 t constant_test_bit
         U del_timer
000027a8 t down
00000e84 t down_interruptible
000027b8 t down_interruptible
00000158 D drvstat
0000212c T dvrsp
00000020 D ffmt
00000000 t gcc2_compiled.
00001148 t gcc2_compiled.
00001538 t gcc2_compiled.
0000164c t gcc2_compiled.
0000167c t gcc2_compiled.
000016d4 t gcc2_compiled.
00001804 t gcc2_compiled.
00001858 t gcc2_compiled.
00001a50 t gcc2_compiled.
00001a9c t gcc2_compiled.
00001bb4 t gcc2_compiled.
00001c54 t gcc2_compiled.
00001cb4 t gcc2_compiled.
00001d64 t gcc2_compiled.
00001da0 t gcc2_compiled.
00001f50 t gcc2_compiled.
0000200c t gcc2_compiled.
0000212c t gcc2_compiled.
00002338 t gcc2_compiled.
00000eb4 t get_current
0000115c T gpib_register_driver
00001190 T gpib_unregister_driver
0000271c T ibAPE
00002418 T ibAPWait
00002660 T ibAPrsp
00000004 D ib_exclusive
000000a0 D ib_fops
00000000 D ib_opened
0000167c T ibcac
00000078 T ibclose
000016d4 T ibcmd
00001e98 T ibeos
00001804 T ibgts
00000124 T ibioctl
00001a50 T iblines
00001858 T ibonl
00000000 T ibopen
00001da0 T ibpad
00001a9c T ibrd
00001bb4 T ibrpp
00001c54 T ibrsv
00001df4 T ibsad
00001cb4 T ibsic
00001d64 T ibsre
00001f1c T ibstatus
00001e64 T ibtmo
00001f50 T ibwait
0000200c T ibwrt
000014b0 t init_MUTEX
0000278c t init_MUTEX
000011bc T init_board_array
0000138c T init_module
000014cc t init_timer
00001494 t init_waitqueue_head
00002810 t init_waitqueue_head
         U interruptible_sleep_on_timeout
         U jiffies
00001448 t list_add
00001468 t list_del
00000108 D myPAD
0000010c D mySAD
0000164c T osChngBase
0000166c T osChngDMA
0000165c T osChngIRQ
00001148 T osInit
000015e0 T osRemoveTimer
00001154 T osReset
00001574 T osStartTimer
00000104 D pollTimeidx
00001104 t prefetch
         U printk
000009d8 T read_ioctl
         U register_chrdev
000000e8 D registered_drivers
00001510 t sema_init
000027e8 t sema_init
00001614 t set_bit
00001b94 t set_bit
00001d30 t set_bit
0000210c t set_bit
00000dcc T status_ioctl
00000e50 t strcmp
00000110 D timeTable
00000100 D timeidx
00001634 t timer_pending
         U tvec_bases
         U unregister_chrdev
00000ea4 t up
000027d8 t up
00000ed0 t verify_area
         U vfree
000019d8 t vmalloc
00001538 T watchdog_timeout
00000c64 T write_ioctl
=20

--=20
_____________________________________________________________
 Marc Lefranc, Charg=E9 de Recherche au CNRS
 Laboratoire de Physique des Lasers, Atomes, Mol=E9cules
 Bat P5, UFR de Physique
 Universit=E9 des Sciences et Technologies de Lille
 F-59655 Villeneuve d'Ascq CEDEX (FRANCE)
 e-mail: Mar...@un...
 Tel : +33 (0)3 20 33 64 50 ;  FAX : +33 (0)3 20 33 70 20
_____________________________________________________________

Re: [Linux-gpib-general] (no subject)

[frank m. h. <fm...@st...>]

What is the ouput of 'depmod -e'?

Frank

On Thu, 4 Apr 2002,  wrote:

>
> Hello,
>
> I have compiled linux-gpib-3.1.2 with no errors.  However, when I do "make install", I get the following message:
>
> depmod -a 2.4.7-10custom
> depmod: *** Unresolved symbols in /lib/modules/2.4.7-10custom/misc/gpib-common.o
>
> depmod: *** Unresolved symbols in /lib/modules/2.4.7-10custom/misc/nec7210.o
>
> depmod: *** Unresolved symbols in /lib/modules/2.4.7-10custom/misc/tms9914.o
>
> I am running RedHat 7.2.  Any ideas what might be happening here?
>
> Thank you,
>
> Tim Holmes
>
>
>
>
>
> ------------------------------------------------
>
>
> _______________________________________________
> Linux-gpib-general mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-gpib-general
>

[Linux-gpib-general] (no subject)

[<tim...@ex...>]

Hello,

I have compiled linux-gpib-3.1.2 with no errors.  However, when I do "make install", I get the following message:

depmod -a 2.4.7-10custom
depmod: *** Unresolved symbols in /lib/modules/2.4.7-10custom/misc/gpib-common.o

depmod: *** Unresolved symbols in /lib/modules/2.4.7-10custom/misc/nec7210.o

depmod: *** Unresolved symbols in /lib/modules/2.4.7-10custom/misc/tms9914.o

I am running RedHat 7.2.  Any ideas what might be happening here?

Thank you,

Tim Holmes





------------------------------------------------