×

INDI Library v1.9.7 Released (29 Jul 2022)

Bi-monthly INDI Library released with new drivers and bug fixes.

No ASI Camera after Update - Suspect port mapping

  • Posts: 372
  • Thank you received: 91
So I got hit with this tonight. It happened after I updated my Raspbian to the latest, by doing "sudo apt update" and "sudo apt upgrade". It just so happens I had a backup image from only a week ago, so I was able to revert with minimal loss.

This is on my Raspberry Pi 4 with 4GB RAM.

As requested, here are the last 4 lines of /proc/cpuinfo:

Hardware : BCM2835
Revision : c03111
Serial : 1000000089f01859
Model : Raspberry Pi 4 Model B Rev 1.1
The following user(s) said Thank You: Jasem Mutlaq
2 years 1 month ago #57457

Please Log in or Create an account to join the conversation.

cat /proc/cpuinfo | tail -n4

This is mine, also 4GB:
Hardware        : BCM2711
Revision        : c03111
Serial          : 1000000029decc50
Model           : Raspberry Pi 4 Model B Rev 1.1

On the RPI4 with USB issues:
Hardware        : BCM2711
Revision        : c03112
Serial          : 1000000089b8c084
Model           : Raspberry Pi 4 Model B Rev 1.2

Yours is v1.1 but the SoC is BCM2835?? how come? Could this actually be one issue? The Rev 1.2 here exhibits the issue, but it appears the SoC is detected correctly at least.
Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Add your observatory info
2 years 1 month ago #57458

Please Log in or Create an account to join the conversation.

  • Posts: 372
  • Thank you received: 91

How come? I have no idea. :)

Since this might actually be a permissions issue, I wonder if running indiserver as root would help? I've already reverted, and I don't want to update to the latest just to test this theory.
2 years 1 month ago #57459

Please Log in or Create an account to join the conversation.

Yes running as root works, but this is not really a solution. Something is broken.
Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Add your observatory info
2 years 1 month ago #57460

Please Log in or Create an account to join the conversation.

  • Posts: 372
  • Thank you received: 91
Of course I didn't mean it as a permanent solution, but rather a troubleshooting step, to see if it really is a permissions issue with the new update.
2 years 1 month ago #57461

Please Log in or Create an account to join the conversation.

  • Posts: 372
  • Thank you received: 91

Jasem,

Are you using a USB hub? I only had this problem when using a powered USB3 hub. If I unplugged the hub, and plugged my devices into the Pi directly, the problem went away.

Since the skies are cloudy and I'm bored, I updated my system again to the latest, with the 5.4 kernel. I can confirm that running indiserver as root does indeed allow things to work again. I know this is not a fix, but at least it allows us to get up and running with the latest release of Raspbian, while we figure out what the problem is.

I posted a message on the Raspbian forum, we'll see if they can offer some help.
2 years 1 month ago #57495

Please Log in or Create an account to join the conversation.

In fact, I am using an external powered USB hub with the unit giving me the trouble! You got a link to the forum post?
Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Add your observatory info
2 years 1 month ago #57496

Please Log in or Create an account to join the conversation.

  • Posts: 233
  • Thank you received: 24
The powered USB3.0 hub is definitely in the mix. This is one thread www.indilib.org/forum/astroberry/7379-us...day-s-upgrading.html and possibly this www.indilib.org/forum/astroberry/7371-ho...astroberry-rpi4.html
Currently running KStars/Ekos/Indi on two Raspberry Pi 4Bs 4GByte under Raspberry Pi OS thanks to Astroberry
Two mounts, two Fracs, a Newt and a Mak and a couple of OSC cameras.
2 years 1 month ago #57506

Please Log in or Create an account to join the conversation.

Thanks Ed! I was actually asking about the raspbian forum link... If we gather enough info, we can file an issue on the Raspberry Pi Linux github.
Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Add your observatory info
2 years 1 month ago #57507

Please Log in or Create an account to join the conversation.

  • Posts: 372
  • Thank you received: 91
I believe I have traced it down to a permissions issue on the USB bus itself, in the /sys hierarchy.
$ ls -l /sys/bus/usb/devices/usb*
lrwxrwxrwx 1 root root 0 Jul 30 02:41 /sys/bus/usb/devices/usb1 -> ../../../devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1
lrwxrwxrwx 1 root root 0 Jul 30 02:41 /sys/bus/usb/devices/usb2 -> ../../../devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2

Following the symlinks:
$ ls -ld /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb*
drw-rw---- 6 root root 0 Jul 30 02:41 /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1
drwxr-xr-x 6 root root 0 Jul 30 02:41 /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2

Notice anything wrong with the permissions on one of them?

These aren't individual USB devices, but rather USB buses.
$ lsusb
Bus 002 Device 004: ID 03c3:1604  
Bus 002 Device 003: ID 174c:3074 ASMedia Technology Inc. ASM1074 SuperSpeed hub
Bus 002 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074 SuperSpeed hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

As you can see, it only shows Bus 2, which matches the permissions listed above.

Now for the magic.
$ sudo chmod +rx /sys/bus/usb/devices/usb*
$ lsusb
Bus 002 Device 004: ID 03c3:1604  
Bus 002 Device 003: ID 174c:3074 ASMedia Technology Inc. ASM1074 SuperSpeed hub
Bus 002 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074 SuperSpeed hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 009: ID 03c3:1f01  
Bus 001 Device 007: ID 04b4:6572 Cypress Semiconductor Corp. 
Bus 001 Device 005: ID 0bda:b812 Realtek Semiconductor Corp. 
Bus 001 Device 008: ID 1618:0921  
Bus 001 Device 006: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC
Bus 001 Device 004: ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub
Bus 001 Device 003: ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

And I confirmed INDI is now happy, running as a regular user, not root.

So, my short-term fix is to add this one line to /etc/rc.local:
chmod +rx /sys/bus/usb/devices/usb*

sudo isn't necessary because it already runs as root.
The following user(s) said Thank You: Avocette, Bernd Limburg
2 years 1 month ago #57510

Please Log in or Create an account to join the conversation.

  • Posts: 372
  • Thank you received: 91

Not yet. I posted last night, but it hasn't been released from moderation yet. Once it is released, I'll add this information to the Raspbian forum post (and share the link here of course).
2 years 1 month ago #57512

Please Log in or Create an account to join the conversation.

So that doesn't work in my case. So I tried changing what they're pointed to:
chmod -R +rx /sys/devices/platform/scb/fd500000.pcie

So while that makes lsusb works, when you try to use drivers they cannot access libusb still (e.g. QHY). So it's still broken.
Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Add your observatory info
2 years 1 month ago #57513

Please Log in or Create an account to join the conversation.

Time to create page: 0.471 seconds