Chris,
Still can't get it to work, here is more info:

Here are the pnp related messages in /var/log/messages during boot up:
Nov 21 10:30:44 localhost kernel: [   51.189333] PnPBIOS: Scanning system 
for PnP BIOS support...
Nov 21 10:30:44 localhost kernel: [   51.189428] PnPBIOS: Found PnP BIOS 
installation structure at 0xc00f7430
Nov 21 10:30:44 localhost kernel: [   51.189453] PnPBIOS: PnP BIOS version 
1.0, entry 0xf0000:0xb801, dseg 0xf0000
Nov 21 10:30:44 localhost kernel: [   51.201238] PnPBIOS: 16 nodes reported 
by PnP BIOS; 16 recorded by driver
Nov 21 10:30:44 localhost kernel: [   51.201329] PCI: Probing PCI hardware
Nov 21 10:30:44 localhost kernel: [   51.202207] PCI quirk: region 8000-803f 
claimed by PIIX4 ACPI
Nov 21 10:30:44 localhost kernel: [   51.202232] PCI quirk: region 7000-700f 
claimed by PIIX4 SMB
Nov 21 10:30:44 localhost kernel: [   51.205480] PCI: Using IRQ router 
PIIX/ICH [8086/7110] at 0000:00:07.0
Nov 21 10:30:44 localhost kernel: [   51.208627] pnp: 00:01: ioport range 
0x4d0-0x4d1 has been reserved
Nov 21 10:30:44 localhost kernel: [   51.208653] pnp: 00:01: ioport range 
0x8000-0x803f has been reserved
Nov 21 10:30:44 localhost kernel: [   51.208676] pnp: 00:01: ioport range 
0x7000-0x700f has been reserved
Nov 21 10:30:44 localhost kernel: [   51.210556] PCI: Bridge: 0000:00:01.0
Nov 21 10:30:44 localhost kernel: [   51.210570]   IO window: disabled.
Nov 21 10:30:44 localhost kernel: [   51.210596]   MEM window: 
fd000000-fdffffffNov 21 10:30:44 localhost kernel: [   51.210618]   PREFETCH 
window: e8000000-efffffff
Nov 21 10:30:44 localhost kernel: [   51.214361] audit: initializing netlink 
socket (disabled)
Nov 21 10:30:44 localhost kernel: [   51.214420] audit(1164122993.310:1): 
initialized
Nov 21 10:30:44 localhost kernel: [   51.215130] VFS: Disk quotas 
dquot_6.5.1
Nov 21 10:30:44 localhost kernel: [   51.215270] Dquot-cache hash table 
entries: 1024 (order 0, 4096 bytes)
Nov 21 10:30:44 localhost kernel: [   51.215661] Initializing Cryptographic 
API
Nov 21 10:30:44 localhost kernel: [   51.215693] io scheduler noop 
registered
Nov 21 10:30:44 localhost kernel: [   51.215732] io scheduler anticipatory 
registered
Nov 21 10:30:44 localhost kernel: [   51.215764] io scheduler deadline 
registered
Nov 21 10:30:44 localhost kernel: [   51.215834] io scheduler cfq registered
Nov 21 10:30:44 localhost kernel: [   51.215855] Limiting direct PCI/PCI 
transfers.
Nov 21 10:30:44 localhost kernel: [   51.216426] isapnp: Scanning for PnP 
cards...
Nov 21 10:30:44 localhost kernel: [   51.574182] isapnp: No Plug & Play 
device found
Nov 21 10:30:44 localhost kernel: [   51.709758] PNP: PS/2 Controller 
[PNP0303,PNP0f13] at 0x60,0x64 irq 1,12

Here is what appears in the /var/log/messages file when I execute the 
commands in the attachment:

Nov 21 09:56:23 localhost kernel: [  862.289668] HAL: creating thread 
test-thread, 1000000 nsec
Nov 21 09:56:23 localhost kernel: [  862.289811] HAL: thread created
Nov 21 09:56:23 localhost kernel: [  862.289831] THREADS: created 1000 uS 
thread
Nov 21 09:56:23 localhost kernel: [  862.325518] parport: PnPBIOS parport 
detected, io_lo=378 io_hi=0
Nov 21 09:56:23 localhost kernel: [  862.372503] config string '0x378'
Nov 21 09:56:24 localhost kernel: [  862.373002] PARPORT: installed driver 
for 1 ports

Anything unusual here?  Everything appears to be working EXCEPT the voltage 
measurement at the pins.
Jerry

btw: the version of src code I loaded and compiled is emc2-2.04

>From: Chris Radek <[EMAIL PROTECTED]>
>Reply-To: "Enhanced Machine Controller (EMC)" 
><[email protected]>
>To: "Enhanced Machine Controller (EMC)" <[email protected]>
>Subject: Re: [Emc-users] Getting parport to work
>Date: Mon, 20 Nov 2006 22:28:45 -0600
>
>On Mon, Nov 20, 2006 at 05:14:04PM -0500, Jerry Mitchell wrote:
> >
> >     scripts/realtime start
>
>This is where you would add the loadrt probe_parport
>
> >     bin/halcmd loadrt hal_parport 'cfg="0x378"
>                                     ^           ^
>                                     extra or missing singlequote
>
> >     bin/halcmd loadrt threads name1=test-thread period1=1000000
> >     bin/halcmd addf parport.0.write
>                                       ^ missing test-thread
>
> >     bin/halcmd start
> >
> >     bin/halcmd newsig tryit bit
> >     bin/halcmd linksp tryit parport.0.pin-01-out
>
>
>I did actually try your commands exactly to make sure you have
>everything you need ... aside from the typos that I bet are just
>transcription errors (marked above) it works fine for me.
>
>Be sure to check your dmesg for any errors that might show
>up there.
>
>Maybe someone else will have more advice.  Maybe you have a
>plug-n-play parport of a type that we haven't seen yet.
>
>Chris
>
>-------------------------------------------------------------------------
>Take Surveys. Earn Cash. Influence the Future of IT
>Join SourceForge.net's Techsay panel and you'll get the chance to share 
>your
>opinions on IT & business topics through brief surveys - and earn cash
>http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>_______________________________________________
>Emc-users mailing list
>[email protected]
>https://lists.sourceforge.net/lists/listinfo/emc-users

_________________________________________________________________
Stay up-to-date with your friends through the Windows Live Spaces friends 
list. 
http://clk.atdmt.com/MSN/go/msnnkwsp0070000001msn/direct/01/?href=http://spaces.live.com/spacesapi.aspx?wx_action=create&wx_url=/friends.aspx&mk


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Emc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users

Reply via email to