hal.parport_ko : Device or Resource busy error
- kborsum
- Offline
- Senior Member
Less
More
- Posts: 45
- Thank you received: 2
11 Aug 2019 01:01 #141888
by kborsum
hal.parport_ko : Device or Resource busy error was created by kborsum
I'm also new to the inner workings of LinuxCNC (and Linux in general) and trying to get a system up and running on a new computer.
lspci -v gives my two parallel ports at 0xe010 and 0xd010, so the system seems to recognize them.
But regardless of the Hal_Parport settings, I still get the same error message when LinuxCNC tries to load:
hal.parport_ko : Device or Resource busy error
the Hal file generated by stepconf (even tho I specified two parallel ports) contains:
loadrt hal _parport cfg "0xe010 out 0 out"
I've tried a number of variations such as:
loadrt hal _parport cfg "0xe010 out"
loadrt hal _parport cfg "0xe010 out 0xde010" etc
wit the the same results.
After playing a bit, I tried a new load of LinuxCNC with the hal file containing loadrt hal_parport cfg "0xe010" and got a different error:
HAL: ERROR: 'parport 1 read' not found
lspci -v gives my two parallel ports at 0xe010 and 0xd010, so the system seems to recognize them.
But regardless of the Hal_Parport settings, I still get the same error message when LinuxCNC tries to load:
hal.parport_ko : Device or Resource busy error
the Hal file generated by stepconf (even tho I specified two parallel ports) contains:
loadrt hal _parport cfg "0xe010 out 0 out"
I've tried a number of variations such as:
loadrt hal _parport cfg "0xe010 out"
loadrt hal _parport cfg "0xe010 out 0xde010" etc
wit the the same results.
After playing a bit, I tried a new load of LinuxCNC with the hal file containing loadrt hal_parport cfg "0xe010" and got a different error:
HAL: ERROR: 'parport 1 read' not found
Please Log in or Create an account to join the conversation.
- pl7i92
- Offline
- Platinum Member
Less
More
- Posts: 1875
- Thank you received: 354
11 Aug 2019 07:06 #141896
by pl7i92
Replied by pl7i92 on topic hal.parport_ko : Device or Resource busy error
it seams that the parport card is not set to ECP
can you please post the output of
terminal command
dmesg | grep parpo*
can you please post the output of
terminal command
dmesg | grep parpo*
Please Log in or Create an account to join the conversation.
- tommylight
- Away
- Moderator
Less
More
- Posts: 19529
- Thank you received: 6553
11 Aug 2019 08:01 #141901
by tommylight
Replied by tommylight on topic hal.parport_ko : Device or Resource busy error
Device or resource busy usually means the wrong address and you must reboot the computer after editing the hal file to change the address.
Please Log in or Create an account to join the conversation.
- kborsum
- Offline
- Senior Member
Less
More
- Posts: 45
- Thank you received: 2
12 Aug 2019 16:34 #141970
by kborsum
Replied by kborsum on topic hal.parport_ko : Device or Resource busy error
I tried your command on the terminal, but got no response.
lspci -v shows two parallel ports: e010 and d010.
After much playing around and reboots, I am able to talk to a BOB on the first port, and can turn the spindle on and off, and control other functions (and perhaps most importantly) it also responds to the EStop command.
I'll be trying the second port shortly.
Thanks for the quick response.
kelly
lspci -v shows two parallel ports: e010 and d010.
After much playing around and reboots, I am able to talk to a BOB on the first port, and can turn the spindle on and off, and control other functions (and perhaps most importantly) it also responds to the EStop command.
I'll be trying the second port shortly.
Thanks for the quick response.
kelly
Please Log in or Create an account to join the conversation.
- kborsum
- Offline
- Senior Member
Less
More
- Posts: 45
- Thank you received: 2
12 Aug 2019 16:35 #141972
by kborsum
Replied by kborsum on topic hal.parport_ko : Device or Resource busy error
Its taken several tries, but I think the computer is now talking to the BOB's.
Thanks
Thanks
Please Log in or Create an account to join the conversation.
- tommylight
- Away
- Moderator
Less
More
- Posts: 19529
- Thank you received: 6553
12 Aug 2019 17:40 #141974
by tommylight
Replied by tommylight on topic hal.parport_ko : Device or Resource busy error
Nice, glad you got it working properly.
Please Log in or Create an account to join the conversation.
Time to create page: 0.053 seconds