Dud wrote:Hello Micko,
As is Raspup WiFi is sufficiently responsive for *just* long enough that a cursory test looks OK but longer transfers fail.
Your short-burst test and the intermittent, grouped, response to my longer ones makes me wonder:
Is there something else taking up resources and only releasing every few seconds so the Pi's attention is diverted much of the time?
OR
Is one, occasionally used call failing with a timeout that causes the batching?
'though the difference between Raspbian Stretch and Buster suggests there may be something else involved too.
Part of the problem too I think is that many of the hook scripts in /lib/dhcpcd/ are systemd agnostic which of course puppy doesn't use. I'll try to find replacements (slackware will be a good place to look).
That it works at all suggests very few of those calls are going astray - a couple of small patches might be enough.
Thanks for all the good work - the Pi4 is so close to being a viable desktop replacement and a good Puppy might just tip the balance.
Cheerio,
We'll see...
My wireless is still up, from the original test.
I've logged into the samba share on my laptop downstairs; it's right near the router but the pi 4 signal has to get around a couple of walls and the floor. I'm currently copying a slackware-live-plasma5 iso image, 4.4 GB, over smb (cli - rox tends to bog down, not just a pi issue there). I prefixed the command with
time so I should get a rough idea of the time it takes - bearing in mind that smb is quite a bit slower than ftp.
After that I might download a hefty iso from the internet with wget to see how that fares, but it certainly seems that my connection is more stable using the commandline.
Cheers
------------------
Later ...
Code: Select all
# mount.cifs //10.1.1.222/puppyshare ./sam -o user=root,pass=woofwoof -v
mount.cifs kernel mount options: ip=10.1.1.222,unc=\\10.1.1.222\puppyshare,user=root,pass=********
# pwd
/mnt/mmcblk0p2
# cd sam
# ls ..
lost+found raspupsave-piZero sam
# time cp slackware64-live-plasma5-current.iso ../
real 186m52.222s
user 0m0.121s
sys 0m46.115s
Yup, 3 hours for ~4.4GB over smb. For comparison ftp took ~14 mins for a 300MB iso. However, to be fair, my desktop was about the same with the same iso and the same server under the same conditions on my network - wifey watching netflix and grandson playing youtube.
Still no dropouts though (and still running from RAM - about to make a save and use my cli method at boot).