Network problem and github

[svkatielee]

I have been trying to compile a legacy kernel for Orange Pi PC for 48 hours.

(I want to add the DisplayLink driver for USB monitor like the Lilliput 10")

 

I have a very poor network connection , wifi to my boat in the marina work yard, Philippines.

Then I tried each of these via the cell phone network (my phone as a hotspot)

 

./compile.sh fails

so I tried cloning the repo by cmdline, and at github and ssh vs http:

git clone -n https://github.com/igorpecovnik/linux.gitsun8i -b sun8i --depth 1   

git clone -n https://github.com/svkatielee/linux.gitsun8i -b sun8i --depth 1
git clone -n git@github.com:svkatielee/linux.git sun8i -b sun8i --depth 1

 

Each time it fails, git deletes everything it did download, so I can't get there incrementally.

 

The most common error:
error: RPC failed; curl 56 SSL read: error:00000000:lib(0):func(0):reason(0), errno 104
fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed

 

Then I tried all the combinations of Download Zip

I get any where from 2 to 100 Mb then it hangs and fails, but usually less than 10Mb.

 

Then I went to a friends boat, 6 Mb before Download Zip froze then errored out in Firefox (where I don't see the message)

 

Is there any other place to download a zip file of linux sun8i that is more resilient to dropped packets and congested network?

Is there a way to break up the repo into smaller pieces that I might eventually get downloaded?

Maybe a torrent?

Is there a problem with github.com?
 

[svkatielee]

I finally succeeded!. I did the git clone to a friend's system in Seattle. Then did an scp back to the Philippines. It worked.

The compile has no errors. Soon I'll try to boot it and see if the DisplayLink USB monitors work.

 

Github still does not like the local network, but it can succeed in a pull, if not much has changed.

 

Thanks for letting me rant.

[lanefu]

I finally succeeded!. I did the git clone to a friend's system in Seattle. Then did an scp back to the Philippines. It worked.

The compile has no errors. Soon I'll try to boot it and see if the DisplayLink USB monitors work.

 

Github still does not like the local network, but it can succeed in a pull, if not much has changed.

 

Thanks for letting me rant.

 

 

That's pretty frustrating.  Complex git requests get picky over HTTP especially with pushes.    

 

You may have better luck setting up a github account and adding your public SSH key (if you haven't already)  and switch your clone method to SSH-based prior to copying the clone URL to your clipboard.

 

SSH is much more resilient, and you'll have additional tuning options available to you

[svkatielee]

SSH is much more resilient, and you'll have additional tuning options available to you

If you notice above, I did try SSH, multiple times.

Thanks, Can you expand on the additional tuning options available (with SSH)?  I'm not too good with that.

 

I would have particularly liked an option to 'not erase everything' on failure. Once it managed 114 out of 148MB and several times as much as 20Mb. If it hadn't erased each try I would have been done a couple days earlier.

[svkatielee]

SSH is much more resilient, and you'll have additional tuning options available to you

If you notice above, I did try SSH, multiple times.

Thanks, Can you expand on the additional tuning options available (with SSH)?  I'm not too good with that.

 

I would have particularly liked an option to 'not erase everything' on failure. Once it managed 114 out of 148MB and several times as much as 20Mb. If it hadn't erased each try I would have been done a couple days earlier.