We never doubted it - welcome back and hope you had a good break!
The 'USB issues' are still a challenge and I don't always find the simple 'everything's working' situation that I did a couple of months ago Even with a revertion to the June Astroberry 2.0.2 image, I am now struggling to keep my Pegasus Astro PPB behaving as it did. The PPB contains a FTDI USB to serial adapter and after months of working without even knowing that, now it doesn't want to work anymore even when I move to more favoured ports on my powered USB 3.0 hub. @dmsummers often warns us to make sure we have enough power on hand especially during the powering up current inrush moments and I am wondering if the new kernel could have inadvertently increased the current demand of the RPi4 during booting which may be influencing my results. Perhaps my power distribution and USB connections work marginal before.
The one upgrade I have had to make is to the RPi-eeprom-image or else my RPi reverts to the April 16 bootloader which (I think) is part of the AStroberry 2.0.2 image. If this happens I cannot use a USB connected SSD copy to boot.
Kaczorek wrote: Could you guys provide some detail on kernel version that works and the one that does not work for you?
You've reawoken an old thread here. Not sure about the driver for the ASI2600MC Pro but there are certainly ZWO camera drivers already installed including for my ASI533MC Pro.
I'm running from SSD only these days, with downloading each image from my ASI533MC Pro taking in the order of a second. I use the Asroberry server controlled via VNC from my laptop or iPad. I don't touch USB bandwidth etc!
Many thanks for the clarifications. I certainly would prefer not be be cutting edge! I now have a second SSD running the simple June Astroberry 2.0.2 image (KStars 3.4.2) which continues to serve me well.
Perhaps you be a bit more constructive and help those of us who didn’t know we were compiling ‘indinightly’ to reach the stable version of 3.4.3? Many thanks in advance!
TomAstro wrote: okay. Will never want to upgrade mine to that 3.5.0 first. Unless you wish to solve issues the whole night. I am running on a stable version nowadays. Good luck guys.
I think are experiencing a similar issue to myself and @kross which seems to have arrived a week ago after a major update to the RPi software which upgraded the linux kernel from version 4.19 to 5.4. Until then I had been using my RPi with a tp-link 7-port powered USB3.0 hub with five of its ports occupied. I use the RPi’s USB3.0 port to feed it, and the second USB3.0 port to connect to an SSD which is my boot device. I follow @dmsummers advice and avoid 2.4GHZ wifi. Fortunately I am now back to full functionality after carefully monitoring the USB list of devices (using lsusb in a terminal window) to ensure that all devices are present. In my case if I connect a Pegasus Astro PPB with its FTDI serial port adapter inside to the end port of the hub all list entries on Bus 001 (the USB 2.0 bus) disappear. The same device plugged in further along the hub and a reboot and everything works.again.
mhammady wrote: Hi,
I need 5 USB ports (to use the new filter wheel), but RPi has only 4. I tried to use an old USB hub but didn't work. I purchased a new powered USB hub but also I couldn't see the devices used by the hub.
Any idea what is the correct solution for using a USB HUB with RPi 4?
You are quite correct - nothing is yet off the hook. Attached is my lsusb list from the original working version, pre-kernel-upgrade. The PPB is Bus 001 Device 006. I guess I have to get used to running lsusb before starting up KStars and counting the entries before resorting to replugging everything!
I normally set up a fresh installation with keyboard/mouse/display although to be clear, this on a second RPi4 that is near my Desktop PC where I download images and make SD cards etc. CHANGEME is a ‘empty’ WLAN entry in the Astroberry wireless settings which you could edit to set up with your home SSID and password, but only if you are already logged in to the astroberry interface. I have no idea why you are seeing it as the broadcast hotspot name!
dlwmacgregor wrote: The only new network I can see on my Galaxy is one named CHANGEME.
Is that the one I want?
It can't connect at 10.42.0.1 because it says that the password is wrong.
Do I configure the connection using DHCP or static IP address?
Hi Doug. The power spec of the recommended power supply for the RPi4 is 3A at 5.1V, and I have one spare that I have substituted in place of the 1.5A charger USB port from the hub from time to time. I also measured the voltage and current draw of the RPi4 in this actual configuration with a Sandisk Extreme SSD and the tp-link 7-port powered USB 3.0 hub being the only directly USB connected devices. The input voltage never dropped below 5.07V and with KStars running, mount slewing and camera imaging away the RPi4 current drawn peaked at around 550mA. I'm not discounting possible power issues, but they don't seem to be of infleunce here.