Tiny Core Base > piCore Test Releases

piCore-6.1alpha4 for RPi2

<< < (2/7) > >>

bmarkus:

--- Quote from: sbp on March 15, 2015, 10:39:12 AM ---
Thanks for this version, I'm currently testing but haven't found any problems yet :-)


--- End quote ---

Did you try the 192kbit/s HDMI audio?

sbp:

--- Quote from: bmarkus on March 15, 2015, 03:56:18 PM ---Hi Steen

thanks for the feedback. I had some issues with BusyBox 1.23.1 so I kept 1.22.1 during kernel tests in this version. Now kernel looks ok and it will be used as the final version, I will update BusyBox.

However https works fine. Try


--- Code: ---busybox wget http://google.com
--- End code ---

and


--- Code: ---busybox wget https://google.com
--- End code ---

They will return the index.html file just fine.

--- End quote ---

Hi Bela it doesn't work for me.

--- Code: --- busybox wget https://github.com/ralph-irving/tcz-jivelite/raw/master/jivelite.tcz
wget: not an http or ftp url: https://github.com/ralph-irving/tcz-jivelite/raw/master/jivelite.tcz
--- End code ---

or


--- Code: ---tc@piCorePlayer:~$ busybox wget https://google.com
wget: not an http or ftp url: https://google.com

--- End code ---

Regards
Steen

Rich:
Hi sbp

--- Quote ---tc@piCorePlayer:~$ busybox wget https://google.com
wget: not an http or ftp url: https://google.com
--- End quote ---
I just tried that under the x86 version on TC4 and got the same results. Using GNU wget returns the following:

--- Code: ---tc@box:~/findpcs/src/rollcall$ wget https://www.google.com
--2015-03-16 11:26:50--  https://www.google.com/
Resolving www.google.com... 64.233.177.147, 64.233.177.105, 64.233.177.103, ...
Connecting to www.google.com|64.233.177.147|:443... connected.
ERROR: cannot verify www.google.com's certificate, issued by `/C=US/O=Google Inc/CN=Google Internet Authority G2':
  Unable to locally verify the issuer's authority.
To connect to www.google.com insecurely, use `--no-check-certificate'.
--- End code ---

jncl:
Hi Bela,

  I'm trying to build some packages but am unable to find either a linux-3.18.y_api_headers or linux-3.18.y_v7_api_headers package anywhere, can you please create them or let me know how I can do so please.

  I also noticed going through the available packages in both the armv6 & armv7 repos that 2 seem to be named incorrectly: filesystems-3.8.9_v7-piCore+.tcz & netfilter-3.8.9_v7-piCore+.tcz.

Cheers Jon

bmarkus:

--- Quote from: jncl on March 16, 2015, 01:56:00 PM ---  I also noticed going through the available packages in both the armv6 & armv7 repos that 2 seem to be named incorrectly: filesystems-3.8.9_v7-piCore+.tcz & netfilter-3.8.9_v7-piCore+.tcz.

--- End quote ---

Hi Jon

thanks fixed.

Béla

Navigation

[0] Message Index

[#] Next page

[*] Previous page