But problems may be due to some other issue and so should not just be ignored or glossed over with the easy answer - it's the PSU. Using such high resistance polyfuses on the USB was a poor design decision and has caused no end of problems and will cause many more in the future. It would be far more useful to ask have you tried this or have you tried that first. To often the only response to a question has been "its your power supply". We've been troubleshooting a lot of issues with the pi and most of them circle back around to the pi being improperly powered or too much current being drawn from the usb ports. I'm a hardware engineer, or was until I retired, and designed many embedded computer system using PowerPC processors, SCSI and Fibre channel and more often than not problems turned out to be issues with the software, and the operating system? guess what - LINUX.Ībishur wrote:Actually, it's hardly "blindly blam power supplies". My keyboard uses about 2-3mA or 26mA max with the LEDs lit, my optical mouse uses a max of 33mA although generally it only uses about 20mA so to say they cause power issues would be rather ridiculous, although if the power supply was rather mediocre maybe they could.īut to blindly blame power supplies for Pi's not working is not helpful. I've seen people refering to power issues because mice don't work, keyboards don't work and of course wifi in particular. Not sure what you're using but on my windows machine I use putty and then to transfer files there is an addition to putty - pscp - which I use to copy the files. I've tried this to check my wifi and I SSH in to the Pi using the wifi and then transfers large files from the Pi to my Windows laptop. I've tried several times and the results are consistent. My system hung sitting there saying "Receiving objects.
I think I've just run out of space on the SD card but being a Linux newby I'm not sure how to check that. My wifi keeps hanging when it gets near the end of the transfer - its not a power issue as far as I'm concerned. I'm trying to get the Linux source installed on my Pi using wifi and "git clone. Power just happens to be one of them.Į.g. There are plenty of other reasons why this could happen. A rather better test than just blindly assuming that there is an issue with power because the wifi stops. If there is a power issue then something may "break" - eg. You could even try to get several transfers going at once. This will get the wifi transmitting in a fairly continuous mode for some time which is when it will be using most power. To check if it's a power issue with the wifi you can check by copying a large file or files, a couple of hundreds of MBytes, from the Pi to your other machine using the wifi port.
An ifconfig eth0 down also shuts down the wireless interface and causes ping and ssh to not respond. Never got around to do this.īut I tried at your recommendation.
0 kommentar(er)
