Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Thu 12 Dec 2019, 14:39
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Projects
BionicDog (updated: 2018-06-04)
Moderators: Flash, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 45 of 57 [844 Posts]   Goto page: Previous 1, 2, 3, ..., 43, 44, 45, 46, 47, ..., 55, 56, 57 Next
Author Message
fredx181


Joined: 11 Dec 2013
Posts: 4209
Location: holland

PostPosted: Fri 09 Nov 2018, 13:21    Post subject:  

wiak wrote:
Hi Fred,

Noticed BionicDog64 pre-installed weX not working properly with Bionic ffmpeg. Simple fix as described here:

http://murga-linux.com/puppy/viewtopic.php?p=1009501#1009501

cheers, wiak


Hi wiak, I'm not sure yet that I understand the details for the fix, but can we possibly work on a new .deb for weX that can make this change automatically maybe ?
(could be difficult, but should be better IMO than only providing info what to do)

Hey Smile almost summer where you live, take it easy !!

EDIT:
William wrote:
When weX is run for the first time it copies /etc/wex folder to ~/.wex automagically, so all should be fine if ~/.wex is removed before first run.

To clarify, I mean that it would be nice if it isn't needed for the user to remove ~/.wex if first run has already been done with earlier version.


Fred

_________________
Dog Linux website
Tinylinux blog by wiak
Back to top
View user's profile Send private message 
wiak

Joined: 11 Dec 2007
Posts: 1842
Location: not Bulgaria

PostPosted: Sun 11 Nov 2018, 00:54    Post subject:  

[quote="fredx181"]
wiak wrote:


EDIT:
William wrote:
When weX is run for the first time it copies /etc/wex folder to ~/.wex automagically, so all should be fine if ~/.wex is removed before first run.

To clarify, I mean that it would be nice if it isn't needed for the user to remove ~/.wex if first run has already been done with earlier version.
Fred


Yes, I agree, and that is in fact one of the things I was planning for this next release I am 'slowly' working on. Reason I had decided not to do that for previous releases is that I didn't want new installation to destroy previous config in case user had some special edits they didn't want to suddenly lose, but I have decided that will be user's responsibility to back up their own special config edits since new installation will over-write the old configs.

Yeah, weather good here, and I'm making some major changes, including, as I said to precord (adding some wex user-util capability to it too), so will be a week to finish, or maybe more if the sun keeps shining here...

wiak

wiak
Back to top
View user's profile Send private message 
fredx181


Joined: 11 Dec 2013
Posts: 4209
Location: holland

PostPosted: Tue 13 Nov 2018, 13:52    Post subject:  

Hi wiak, all,

I misunderstood, obviously weX doesn't work at all on BionicDog.
I thought there were (just) out-of-sync issues. I should have tested a while back already Embarassed

For the time being (until you release new version) I added new package version (0.8.18-2) to repos, which has the ffmpegFilter_Complex0="" in /etc/wex/plugins/audio_in.plug

For who ran weX already earlier, remove ~/.wex after installing new version and it should work ok.

Install new package version from Synaptic (click "Reload" first) or with apt-get:
Code:
apt-get update
apt-get install wex


Fred

_________________
Dog Linux website
Tinylinux blog by wiak
Back to top
View user's profile Send private message 
dcung

Joined: 13 Jul 2018
Posts: 236
Location: Down Under - 3rd rock from Sun.

PostPosted: Fri 23 Nov 2018, 00:40    Post subject: Screen Saver  

Hi,

Screen goes blank/saver kick in when I watch youtube videos, and no mouse activity for a while.

Where do you set the time out or disable screen blanking?

Thanks.


EDIT:
Found it - Thank you.
http://murga-linux.com/puppy/viewtopic.php?t=113210&start=174
Back to top
View user's profile Send private message 
quantumbox

Joined: 03 Feb 2017
Posts: 24
Location: Indonesia, Bali

PostPosted: Thu 29 Nov 2018, 00:43    Post subject: Re: Screen Saver  

dcung wrote:
Hi,

Screen goes blank/saver kick in when I watch youtube videos, and no mouse activity for a while.

Where do you set the time out or disable screen blanking?

Thanks.


EDIT:
Found it - Thank you.
http://murga-linux.com/puppy/viewtopic.php?t=113210&start=174


On Bionicdog cinnamon edition on start menu, search Power Management, then set never on Power Option
Back to top
View user's profile Send private message 
ETP


Joined: 19 Oct 2010
Posts: 1173
Location: UK

PostPosted: Thu 29 Nov 2018, 06:55    Post subject: Screen Saver in Cinnamon edition of BionicDog.  

Hi quantumbox,

Please note that in the Cinnamon version the proper SS is not set up OOTB but it is a simple 3 step process to enable it.
It will not cut in if you are viewing YT videos or movies in another player.

How to:
In "System Settings Control Center"

1. Create a new "Startup Applications" item as in the screenie below.

2. In the existing "Screensaver" item set your desired delay.

3. Reboot making sure that you save the session.
Create_startup_item.png
 Description   
 Filesize   107.7 KB
 Viewed   1176 Time(s)

Create_startup_item.png

Set_screensaver_delay.png
 Description   
 Filesize   23.69 KB
 Viewed   1152 Time(s)

Set_screensaver_delay.png


_________________
Regards ETP

Kennels
Back to top
View user's profile Send private message 
ETP


Joined: 19 Oct 2010
Posts: 1173
Location: UK

PostPosted: Sat 01 Dec 2018, 03:39    Post subject: Using the proprietary Nvidia driver with BionicDog  

HOW-TO:

1. Backup your changes folder !!!!!!!!! - (If on your hardware you perceive no great advantage when using the Nvidia driver you can simply restore from that)

2. Check first with the following command in a terminal. It will recommend the correct Nvidia driver for the installed card.

Code:
ubuntu-drivers devices


The output in my case was:-

    root@live64:~# ubuntu-drivers devices
    == /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0 ==
    modalias : pci:v000010DEd0000104Asv00001043sd00008460bc03sc00i00
    vendor : NVIDIA Corporation
    model : GF119 [GeForce GT 610]
    driver : nvidia-340 - distro non-free
    driver : nvidia-driver-390 - distro non-free recommended
    driver : xserver-xorg-video-nouveau - distro free builtin


3. Then, still in the terminal issue the following commands for the recommended non-free driver:

Code:
apt-get update
apt-get install linux-headers-$(uname -r)
apt-get install nvidia-driver-390


4. Save and reboot to bring into operation

5. Also recommeded but optional, using Synaptic Package Manager, install nvidia-settings to view the status of your card. (e.g. temperature & memory usage)

TIPS:

A. With my old low spec card the observed improvement over the current Nouveau driver was very slight.
It is probably only worth using the proprietary Nvidia driver if you wish to squeeze the best out of a high end recent card or are a gamer.
The extra MBs to be loaded at every boot will extend the boot process slightly. That has to be weighed up against the slightly smoother snappier performance once running.
Any benefits will be hardware dependent.

B. In Puppy the nvidia-settings utility is best left at it's default settings and used as a view only tool. Do not allow it to modify xorg as doing so can break Puppy.
Screenshot from 2018-12-01 08-24-00.png
 Description   
 Filesize   135.79 KB
 Viewed   1107 Time(s)

Screenshot from 2018-12-01 08-24-00.png


_________________
Regards ETP

Kennels
Back to top
View user's profile Send private message 
fredx181


Joined: 11 Dec 2013
Posts: 4209
Location: holland

PostPosted: Sat 01 Dec 2018, 17:45    Post subject:  

Thanks very much ETP, added to bottom of first post of this thread a link to your How-to.

Greetings, Fred

_________________
Dog Linux website
Tinylinux blog by wiak
Back to top
View user's profile Send private message 
recobayu


Joined: 15 Sep 2010
Posts: 376
Location: indonesia

PostPosted: Mon 03 Dec 2018, 05:57    Post subject:  

Hi All,
I new to use this bionicdog. I use apt2sfs. I try to make inkscape sfs. But the end of process, I got inkscape.squashfs. I right click to it but nothing load sfs on the fly. I click on it, but it mount that file. How to load on the fly it? Is it possible? Like in puppy linux usually.
Thank you.
Back to top
View user's profile Send private message 
backi

Joined: 27 Feb 2011
Posts: 1852
Location: GERMANY

PostPosted: Mon 03 Dec 2018, 07:40    Post subject:  

Hi recobayu !

Just a little bit different than Puppy .
You probably did a left-click onto your Module which does mount it .
I am posting from Xenial Dog right now...could be Bionic Dogs is a bit different .

I assume when you do a right-click with PcManfm onto your inkscape.squashfs......
you should get a Menu with (among other Options ):

Activate module (safe Mode)
Load-sfs-chroot-full install
Activate module
Deactivate module

If choosing "Activate module" .....a Message will appear (something like ......." module activated").........then look into main Menu to start your application.
You can also Experiment (safely) with the other Module loading Options.
IF you activated your module .....you can also deactivate it again by right-clicking onto the module and choose "Deactivate module"
Back to top
View user's profile Send private message 
recobayu


Joined: 15 Sep 2010
Posts: 376
Location: indonesia

PostPosted: Mon 03 Dec 2018, 21:19    Post subject:  

Thank you Backi. I use bionic dog cinnamon. Here is my screenshot in nemo file manager. I don't see any "activate module" here. Please help me.
Thank you.
2018-12-04-081411_1366x768_scrot.png
 Description   right click
 Filesize   42.37 KB
 Viewed   944 Time(s)

2018-12-04-081411_1366x768_scrot.png

Back to top
View user's profile Send private message 
ETP


Joined: 19 Oct 2010
Posts: 1173
Location: UK

PostPosted: Tue 04 Dec 2018, 02:17    Post subject: Load 'On the Fly'  

Hi recobayu,

The cinnamon version of BionicDog contains both PCManFM and Nemo. Fred wisely included
PCManFM as it includes more right click options including those you seek.

Another option is the menu item SFS-Load Gui for loading 'On the Fly' but please note the
warnings about the need to load the sfs from actual storage rather than /root or /

Full sized screen-shot here: (Press F11 to toggle into full screen then click on link)
https://drive.google.com/uc?export=view&id=1yRAoOrg0GFE-r4mGqwspKL0lKf-ZbWcl
.

_________________
Regards ETP

Kennels
Back to top
View user's profile Send private message 
stemsee

Joined: 27 Jun 2013
Posts: 2544
Location: In The Way

PostPosted: Mon 17 Dec 2018, 17:12    Post subject:  

Hi Fred et al.

I bought a 2-in-1 laptop HP x2 210 g2 with Atom zx8350 4gb ram and 64gb emmc,on ebay for £69.

I booted BD and to my surprise it picked up the soundcard, bytecrt5 or something like that. FatDog64 doesn't see anything. I believe that is pulse related.

I knew that all sound levels (50+ sliders) for atom soundcards usually need to be set to about 50%. I did this but I also activated every (MM) muted switch to (00) un-muted. I have done this before with other atom tablets sporting different soundcards, and there has never been a sound emit from the speakers or headphones. However, there were pops crackles, continuous hissing, and even mic feedback. "Wow!" I thought, "the sound system is going to work." However I hurriedly un-muted everything without reading what each setting was for! Then I started to smell electrical burning! I felt the back of the tablet and it was in the area that corresponds to the back of the speakers. Looking again at the front speaker grills I saw that they were melting! Yes, somehow the voltage to the speakers was very high and the coils around the speaker magnets overheated and melted the plastic frame and partly the speakers, which are now much quieter, probably as the speaker membrane is mis-shaped and hardened after cooling down! The headphone socket has no problem.

The good news is that it looks like the atom zx8350 sound system is going to work with DebianDog.

cheers!
stemsee
Back to top
View user's profile Send private message MSN Messenger 
check5


Joined: 17 Mar 2018
Posts: 5
Location: Bavaria, Germany

PostPosted: Fri 28 Dec 2018, 14:34    Post subject: Mesa 18.3x  

Hi fredx181,
How did you manage to install the mesa driver? I wanted to compile the current Mesa 18.3x and then comes the following output:
Code:

./configure --prefix=/usr --with-platforms="x11" --with-gallium-drivers=i915

checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking target system type... x86_64-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/ginstall -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... bin/install-sh -c -d
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether UID '0' is supported by ustar format... yes
checking whether GID '0' is supported by ustar format... yes
checking how to create a ustar tar archive... gnutar
checking whether make supports nested variables... (cached) yes
checking whether make supports the include directive... yes (GNU style)
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... gcc3
checking for ar... ar
checking the archiver (ar) interface... ar
checking how to run the C preprocessor... gcc -E
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking whether gcc understands -c and -o together... (cached) yes
checking dependency style of gcc... (cached) gcc3
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking for grep that handles long lines and -e... /bin/grep
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking dependency style of gcc... gcc3
checking for GNU make... make
checking for a Python interpreter with version >= 2.7... python
checking for python... /usr/bin/python
checking for python version... 2.7
checking for python platform... linux2
checking for python script directory... ${prefix}/lib/python2.7/dist-packages
checking for python extension module directory... ${exec_prefix}/lib/python2.7/dist-packages
checking for a sed that does not truncate output... /bin/sed
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking how to print strings... printf
checking for a sed that does not truncate output... (cached) /bin/sed
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-pc-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for a working dd... /bin/dd
checking how to truncate binary pipes... /bin/dd bs=4096 count=1
checking for mt... no
checking if : is a manifest tool... no
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking how to run the C++ preprocessor... g++ -E
checking for ld used by g++... /usr/bin/ld -m elf_x86_64
checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking dynamic linker characteristics... (cached) GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking for rm... rm -f
checking for bison... bison -y
checking if bison is the parser generator... yes
checking for flex... flex
checking lex output file root... lex.yy
checking lex library... none needed
checking whether yytext is a pointer... no
checking if flex is the lexer generator... yes
checking for indent... cat
checking if module mako in python is installed... No module named mako
no
checking if compiling with clang... no
checking whether gcc version is sufficient... yes
checking whether __SUNPRO_C is declared... no
checking for __builtin_bswap32... yes
checking for __builtin_bswap64... yes
checking for __builtin_clz... yes
checking for __builtin_clzll... yes
checking for __builtin_ctz... yes
checking for __builtin_expect... yes
checking for __builtin_ffs... yes
checking for __builtin_ffsll... yes
checking for __builtin_popcount... yes
checking for __builtin_popcountll... yes
checking for __builtin_unreachable... yes
checking for __attribute__((const))... yes
checking for __attribute__((flatten))... yes
checking for __attribute__((format))... yes
checking for __attribute__((malloc))... yes
checking for __attribute__((packed))... yes
checking for __attribute__((pure))... yes
checking for __attribute__((returns_nonnull))... no
checking for __attribute__((unused))... yes
checking for __attribute__((visibility))... yes
checking for __attribute__((warn_unused_result))... yes
checking for __attribute__((weak))... yes
checking for __attribute__((alias))... yes
checking for __attribute__((noreturn))... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking whether C compiler accepts -Wall... yes
checking whether C compiler accepts -Werror=implicit-function-declaration... yes
checking whether C compiler accepts -Werror=missing-prototypes... yes
checking whether C compiler accepts -Wmissing-prototypes... yes
checking whether C compiler accepts -Wmissing-field-initializers... yes
checking whether C compiler accepts -Wformat-truncation... no
checking whether C compiler accepts -fno-math-errno... yes
checking whether C compiler accepts -fno-trapping-math... yes
checking whether C compiler accepts -fvisibility=hidden... yes
checking whether C++ compiler accepts -Wall... yes
checking whether C++ compiler accepts -fno-math-errno... yes
checking whether C++ compiler accepts -fno-trapping-math... yes
checking whether C++ compiler accepts -fvisibility=hidden... yes
checking whether C++ compiler accepts -Wmissing-field-initializers... yes
checking whether C++ compiler accepts -Wformat-truncation... no
checking whether C compiler accepts -Werror=pointer-arith... yes
checking whether C compiler accepts -Werror=vla... yes
checking whether C++ compiler accepts -Werror=pointer-arith... yes
checking whether C++ compiler accepts -Werror=vla... yes
checking whether c++11 is enabled by default... no
checking whether c++11 is enabled by via -std=c++11... yes
checking whether C compiler accepts -Woverride-init... yes
checking whether C compiler accepts -Winitializer-overrides... no
checking whether __atomic_load_n is supported... yes
checking whether __sync_add_and_fetch_8 is supported... yes
checking whether byte ordering is bigendian... no
checking whether gcc supports -mpower8-vector... no
checking if ld supports -Bsymbolic... yes
checking whether ld supports --gc-sections... yes
checking if the linker supports version-scripts... yes
checking if the linker supports --dynamic-list... yes
checking whether to enable assembly... yes, x86_64
checking whether sys/types.h defines makedev... no
checking sys/mkdev.h usability... no
checking sys/mkdev.h presence... no
checking for sys/mkdev.h... no
checking sys/sysmacros.h usability... yes
checking sys/sysmacros.h presence... yes
checking for sys/sysmacros.h... yes
checking xlocale.h usability... yes
checking xlocale.h presence... yes
checking for xlocale.h... yes
checking sys/sysctl.h usability... yes
checking sys/sysctl.h presence... yes
checking for sys/sysctl.h... yes
checking endian.h usability... yes
checking endian.h presence... yes
checking for endian.h... yes
checking for dlfcn.h... (cached) yes
checking for strtof... yes
checking for mkostemp... yes
checking for timespec_get... yes
checking for memfd_create... no
checking whether strtod has locale support... yes
checking for dlopen... no
checking for dlopen in -ldl... yes
checking for dladdr... yes
checking for dl_iterate_phdr... yes
checking for clock_gettime... yes
checking for posix_memalign... yes
checking for ZLIB... yes
checking for the pthreads library -lpthreads... no
checking whether pthreads work without any flags... no
checking whether pthreads work with -Kthread... no
checking whether pthreads work with -kthread... no
checking for the pthreads library -llthread... no
checking whether pthreads work with -pthread... yes
checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE
checking if more special flags are required for pthreads... no
checking for PTHREAD_PRIO_INHERIT... no
checking whether pthread_setaffinity_np is supported... yes
checking linux/futex.h usability... yes
checking linux/futex.h presence... yes
checking for linux/futex.h... yes
checking for LIBELF... yes
checking for llvm-config... no
checking for LIBDRM... no
checking for GLPROTO... yes
configure: error: Direct rendering requires libdrm >= 2.4.75


Is there a trick? LibDRM is 2.4.96
greetings
Back to top
View user's profile Send private message 
dancytron

Joined: 18 Jul 2012
Posts: 1413

PostPosted: Fri 28 Dec 2018, 15:29    Post subject: Re: Mesa 18.3x  

check5 wrote:
Hi fredx181,
How did you manage to install the mesa driver? I wanted to compile the current Mesa 18.3x and then comes the following output:
Code:

./configure --prefix=/usr --with-platforms="x11" --with-gallium-drivers=i915

checking build system type... x86_64-pc-linux-gnu

//snipped

configure: error: Direct rendering requires libdrm >= 2.4.75


Is there a trick? LibDRM is 2.4.96
greetings


Is there a reason you aren't using the mesa drivers that are already compiled in the repository?

Are you trying to compile drivers because you found an intel page telling you to do that? If so, ubuntu/debian has already done that for you.

edit: see http://murga-linux.com/puppy/viewtopic.php?p=965414#965414
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 45 of 57 [844 Posts]   Goto page: Previous 1, 2, 3, ..., 43, 44, 45, 46, 47, ..., 55, 56, 57 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Puppy Projects
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0938s ][ Queries: 13 (0.0166s) ][ GZIP on ]