-
-
Notifications
You must be signed in to change notification settings - Fork 349
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
weird problem on raspbian #2547
Comments
I'd first focus on physical aspects - try different ports, cables, check if the same cable and UPS that work on one RPi misbehave on the other. Maybe even switch SD cards and boot with the "successful" OS on the misbehaving one. It may be possible that it is just broken (some soldering went loose, GPIO overlap, firmware wrong, etc.) We had a fair amount of reports of issues with Raspberries and allegedly RPi3 and RPi5 had problems with USB, RPi4 was better. But I still can't say if that says more about popularity of the platform (so we see many reports with them due to frequent use, reporter's bias) or really about its quality. |
thanks. As I wrote , I have already tried diffrent cables. I also tried all ports. " switch SD cards and boot with the "successful" OS on the misbehaving one" --> that's something I did not try. I will try and report back. is there a USB OTG driver that I should update on the Raspbian ? |
Can't really say, don't have much experience with Raspberries. I know some HATs require pre-loaded files (DTB, kernel settings args, or whatnot) to function. |
what else can I check ? |
Looking more at your original post, I see that both devices claim to be Raspberry Pi 3B (or so you say), but have different USB Hub identifiers. Probably different board revisions and maybe variation due to that. Also the not-working one seems to have an Ethernet adapter on the USB bus - is that the built-in port or a separate dongle (can you try seeing the UPS with this port unplugged then)? One more thought is about USB subsystem perhaps not having enough electrical power to establish a stable connection (e.g. the Ethernet port eats some away?) Can you try feeding this RPi from a more powerful source, to confirm or rule out this possibility? |
I just had time to try different combinations. Then as you asked, I checked the board revisions. So they are both RPI3B but one is B+
there is nothing else on the external USB ports of the PI. I assume the ethernet adapter is an internal connection from USB hub. I tried the working OS SD card on the not-working PI as you suggested. In conclusion, the problem is not about HW but the OS , kernel or drivers. If I use the working SD on the not working PI, I see the device detection on dmesg output as:
|
That's more of an OS question. I gather If you have spare SD cards, you might want to |
"apt dist-upgrade" didn't change the release. another "dist-upgrade" does not do anything. |
ok, now following :
let's see... |
with that method I get this error:
I think I can solve the signature issue and try upgrade again.
I believe, I need a better USB driver but I know nothing about drivers on linux. note: |
UPDATE: But the USB device is still not detected:
isn't that interesting / weird ? If I put the bullseye SD card to the same RPI 3B, it can detect the USB device. this seems like a missing or old usb device driver (kernel mod) to me. |
Weird indeed. Try to compare |
well, I could not find anything about usb in lsmod output. this is the working one:
and this is the non-working one:
maybe it is some package like usbutils. working:
not-working:
|
Well, the module lists do differ significantly. I've sorted the two and passed into IIRC Raspberries also have a lot of impact from DTB files and other configuration on the card which passes device information and kernel arguments to the Linux which is eventually loaded. Do those differ in an interesting manner? |
Ok but I can't try every possibility. I need some clue to test 1-2 of missing modules.
Where are those files ? |
Well, it is your Raspberry. I've only read about them and saw at colleagues' rigs, but did not really get to setting up any myself. My understanding is that the SD card is usually FAT-formatted for the boot part, and there are text files on it... Can't say more. |
Hi,
I have a weird problem and Github issues might not be the correct place to write this. Please forgive me and let me know where to write it in that case.
The problem:
I have a working NUT setup on a raspberry pi 3B with raspbian bullseye.
Now I need to move it to another RPI 3B, but the OS is older on this one (buster)
In fact, I also have a working NUT setup on this RPI (the one that I am moving to) but it is using a different UPS.
So , I have 2 RPI ; lets call them RPI-a and RPI-b
Both RPI has working NUT setup but with different UPS. RPI-a is connected to UPS-a , RPI-b is connected to UPS-b
Now I want to connect RPI-b to UPS-a
When I connect the UPS with its USB cable to RPI-b, it does not recognize it as a device.
Does not show up in "lsusb" , and all I see in "dmesg" is :
root@raspbx:/boot# dmesg | grep usb
[ 841.494024] usb 1-1.4: new low-speed USB device number 8 using dwc_otg
[ 842.044035] usb 1-1.4: new low-speed USB device number 9 using dwc_otg
[ 842.494267] usb 1-1-port4: attempt power cycle
[ 843.154035] usb 1-1.4: new low-speed USB device number 10 using dwc_otg
[ 843.694036] usb 1-1.4: new low-speed USB device number 11 using dwc_otg
so I collected these information below from each RPI when UPS-a is connected with a USB cable.
Working PI:
not working PI:
I don't know where to focus so I could only try:
Could you please tell me where to focus ?
note:
The text was updated successfully, but these errors were encountered: