|
(ARCHIVED) Debian Mate (3.10.102 BSP)
|
07-01-2016, 01:55 AM
(This post was last modified: 07-01-2016, 01:57 AM by UnixOutlaw.)
(07-01-2016, 01:00 AM)lenny.raposo-pine64.pro Wrote: oh sorry I forgot to add the MD5 sum for the new image. Cheers mate! Thanks for the quick response...  I'll give it a whirl on Saturday or Sunday! 
07-01-2016, 02:17 AM
i'm not able to download image as google drive is blocked (any other source).
07-01-2016, 11:18 AM
No other source available at this time sorry
If you like my work be sure to check out my site or wish to donate to the cause
Cheers 
07-01-2016, 01:29 PM
(This post was last modified: 07-01-2016, 01:55 PM by Never_same_pw_twice.)
(07-01-2016, 02:17 AM)pushpendrak Wrote: i'm not able to download image as google drive is blocked (any other source). I'll have a mirror on Mega.nz here shortly, finishing my downloads now Edit: Heres the link for Debian Base Debianbase-30.0.102bsp
(2) Pine64+ (2gb) + Wifi/BT
Digital Signage Project
07-02-2016, 11:37 PM
07-03-2016, 02:46 AM
(This post was last modified: 07-03-2016, 02:59 AM by UnixOutlaw.)
Shame you didn't mention the MAC address is fudged and hard-coded on /boot/uEnv.txt file...
36:C9:E3:F1:B8:05 I've got two pine64+ - was trying to watch my router for a DHCP ack - couldn't see my 2nd Pine till I shut it down - updated the file with a different MAC address... Why is this necessary? Shouldn't we be relying on the actual "real" MAC address of the on-board NIC on 64+ models? Also - I've tried HDMI out on 2 different monitors : 1680x1050 Dell 800x480 (noname brand) I've edited the uEnv.txt file tried 1050p_60 on the Dell, and 480p_60 on the no-name brand - both over HDMI Get nothing on either screen... The Dell is capable of switching to 720p if necessary or requested... Anyway - not too bothered about GUI - so I've stopped lightdm - "systemctl stop lightdm", "systemctl disable lightdm" - but there are still some X and lightdm processes... Just rebooting after trying : systemctl set-default multi-user.target I also disabled bluetooth - because it was filling up dmesg with logs about bluetooth... |
