DebianDog64 - 64 bit DebianDog-Jessie

A home for all kinds of Puppy related projects
Post Reply
Message
Author
User avatar
fredx181
Posts: 4448
Joined: Wed 11 Dec 2013, 12:37
Location: holland

#136 Post by fredx181 »

Save as UTF-8 maybe?

stemsee

#137 Post by stemsee »

Hi Fredx181

I want to be able to play DogRadio over bluetooth speaker. This is the command I use to play a media playlist file. It is the same for a single media file just remove -playlist section and supply path to *.mp3 etc

Code: Select all

mplayer -ao alsa:device=btheadset -playlist /tmp/list-"$filext".m3u &
How can I apply this to DogRadio?

User avatar
fredx181
Posts: 4448
Joined: Wed 11 Dec 2013, 12:37
Location: holland

#138 Post by fredx181 »

stemsee wrote:Hi Fredx181

I want to be able to play DogRadio over bluetooth speaker. This is the command I use to play a media playlist file. It is the same for a single media file just remove -playlist section and supply path to *.mp3 etc

Code: Select all

mplayer -ao alsa:device=btheadset -playlist /tmp/list-"$filext".m3u &
How can I apply this to DogRadio?
Hi Stemsee,

Adding this on top of $HOME/.dogradio/data/func should work (doesn't work adding to /usr/local/bin/dogradio):

Code: Select all

#!/bin/bash

shopt -s expand_aliases
alias mplayer='mplayer -ao alsa:device=btheadset "$@"'

......
......
Another way possibly to make new script named mplayer and put it in first PATH env
For me /root/bin

Code: Select all

#!/bin/bash

## USE FULL PATH OF EXISTING MPLAYER BINARY
/opt/bin/mplayer -ao alsa:device=btheadset "$@";
My PATH is:

Code: Select all

root@jessie:~# echo $PATH
/root/bin:/opt/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/usr/local/sbin:/usr/sbin:/sbin
So /root/bin is first in PATH

Fred

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#139 Post by rcrsn51 »

@stemsee: Assuming that DogRadio plays to the default ALSA device, try this /root/.asoundrc:

Code: Select all

pcm.builtin {type hw; card 0;}
ctl.builtin {type hw; card 0;}

pcm.btheadset {
   type plug
   slave {
       pcm {
           type bluetooth
           device XX:XX:XX:XX:XX:XX
           profile "auto"
       }
   }
   hint {
       show on
       description "BT Headset"
   }
}
ctl.btheadset {
  type bluetooth
}

#pcm.!default pcm.builtin
#ctl.!default ctl.builtin

pcm.!default pcm.btheadset
ctl.!default ctl.btheadset
You can switch between your bluetooth audio device and the built-in speakers by changing the commented lines at the bottom.

stemsee

#140 Post by stemsee »

Thanks @fredx181 @ rcrsn51

I will test them both, a specific solutioin and a global solution.

stemsee

post script
One request for DogRadio gui if possible. After clicking the stop button it would be great if it changed colour ( the stop button) and behaved as a pause so that pressing it again resumed the same station; and then changed to red after starting a station or resuming.

User avatar
fredx181
Posts: 4448
Joined: Wed 11 Dec 2013, 12:37
Location: holland

#141 Post by fredx181 »

Hi All,

Fix for loading encrypted save file, added to the Changes and fixes list

9) Fix for loading encrypted save file when using porteus-boot (using live-boot-3 works well)
Problem is with USB keyboard. Not possible to type the password as the module hid_generic is not loaded at this point (keyboard not enabled)
Fixed with new initrd1.xz, download:
https://dl.dropboxusercontent.com/u/362 ... initrd1.xz
Replace it in the "live" folder

Fred
Last edited by fredx181 on Sun 07 Feb 2016, 19:29, edited 2 times in total.

User avatar
fredx181
Posts: 4448
Joined: Wed 11 Dec 2013, 12:37
Location: holland

#142 Post by fredx181 »

Hi All,

I decided to remove the link to DebianDog64 - Stretch version on the first post.
Mainly because:
- There are some problems found with it that I can't solve.
- I don't have enough time to maintain it (e.g. fixes, new packages)

So I'll focus on DebDog64 Jessie only now.

Fred

User avatar
fredx181
Posts: 4448
Joined: Wed 11 Dec 2013, 12:37
Location: holland

#143 Post by fredx181 »

*** LZ4 compression boot support ***

In the 32 bit Debiandog Jessie thread, rufwoof explained some advantages using LZ4 compressed modules.
See more about LZ4 here:
http://cyan4973.github.io/lz4/

Full support for it will be included in next DD64 ISO

For now, to have full LZ4 support for DebianDog64-Jessie, download and extract in the "live" folder this archive:

https://dl.dropboxusercontent.com/u/363 ... ar.gz?dl=1

Or Download with SFS-get from the Menu (Accessories > SFS-get)

From the ReadMe inside:
Supports mounting, creating, extracting and activating (sfs-load) LZ4 compressed .squashfs modules.

Place these files in the "live" folder:
initrd1-lz4.xz
initrd1-lz4.img
initrd-lz4.img
316-squashfs-lz4-support64.squashfs
and
vmlinuz1-lz4 (added here for completeness, in fact it's the same as vmlinuz1 from DebianDog pae ISO, kernel 3.16.0-4-686-pae)


Make new entry in menu.list according to the path/names of the files, e.g:

# Porteus-boot:

title DebianDog 64 with LZ4-squashfs-support - porteus-boot sysvinit
root (hd0,2)
kernel /live/vmlinuz1-lz4 from=/ noauto changes=EXIT:/live/
initrd /live/initrd1-lz4.xz

# Live-boot-3:

title DebianDog 64 with LZ4-squashfs-support - live3 persistence sysvinit
root (hd0,2)
kernel /live/vmlinuz1-lz4 boot=live persistence config swapon quickreboot noprompt autologin
initrd /live/initrd-lz4.img

Reboot
See for more info in the ReadMe.

Fred

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#144 Post by rcrsn51 »

stemsee wrote:I will test them both, a specific solutioin and a global solution.
Whatever happened with this issue?

stemsee

#145 Post by stemsee »

well I don't want to distract from the thread but I didn't implement either cleanly because before I did I implemented this loop to ~.asoundrc

Code: Select all

# ------------------------------------------------------
# hardware 0,0 : used for ALSA playback
pcm.loophw00 {
  type hw
  card Loopback
  device 0
  subdevice 0
  format S32_LE
  rate 48000
}

# ------------------------------------------------------
# playback PCM device: using loopback subdevice 0,0
# Don't use a buffer size that is too small. Some apps 
# won't like it and it will sound crappy 

pcm.amix {
  type dmix
  ipc_key 219345
  slave {
    pcm loophw00
    period_size 2048
    periods 2
  }
}

# ------------------------------------------------------
# software volume
pcm.asoftvol {
  type softvol
  slave.pcm "amix"

  control { name PCM }

  min_dB -51.0
  max_dB   0.0
}

# ------------------------------------------------------
# for jack alsa_in: looped-back signal at other ends
pcm.cloop {
  type hw
  card Loopback
  device 1
  subdevice 0
  format S32_LE
  rate 48000
}

# ======================================================
# ------------------------------------------------------
# hardware 0,1 : used for ALSA capture
pcm.loophw01 {
  type hw
  card Loopback
  device 0
  subdevice 1
  format S32_LE
  rate 48000
}

# ------------------------------------------------------
# for jack alsa_out: looped-back signal at other end
pcm.ploop {
  type hw
  card Loopback
  device 1
  subdevice 1
  format S32_LE
  rate 48000
}

# ======================================================
# ------------------------------------------------------
# duplex device combining our PCM devices defined above
pcm.aduplex {
  type asym
  playback.pcm "asoftvol"
  capture.pcm "loophw01"
}

# ------------------------------------------------------
# default device
pcm.!default {
  type plug
  slave.pcm aduplex

  hint {
       show on
       description "Duplex Loopback"
  }
}

oui

#146 Post by oui »

Hi
How to install skype?
Kind regards

User avatar
fredx181
Posts: 4448
Joined: Wed 11 Dec 2013, 12:37
Location: holland

#147 Post by fredx181 »

oui wrote:Hi
How to install skype?
Kind regards
Currently it's not possible, the .deb from the skype website is i386 .
There are some problems using multiarch on DD 64, see here:
http://murga-linux.com/puppy/viewtopic. ... 963#881963

I'll look at some possible workaround when I have time.

Fred

oui

#148 Post by oui »

Thank you very much Fred

Next detail:

Modern browsers and flash plugins are so, that immediately the sound started, else if you only touch only a really little bit the window of the terrible advertising videos placed by the friend of humanity on the most internet pages.

at normal «master» and «speaker» are at range 60 % («headphone1» at 43 % but «headphone2» at terrible 100 %) in the default values having given to DebianDog64, those videos are a terrible inconvenient if you use the PC in the environment of your asleep partner or baby etc. and microphone is not on. if you use a voice system (ekiga etc.) you have always to turn it on and to open and increase the sound.

how to change the default values before remastering so, that they stay as entered by you after remastering? from which file are the default values coming from?

how far can the thematic of following recent message help here:
stemsee wrote:well I don't want to distract from the thread but I didn't implement either cleanly because before I did I implemented this loop to ~.asoundrc

Code: Select all

# ------------------------------------------------------
# hardware 0,0 : used for ALSA playback
pcm.loophw00 {
  type hw
  card Loopback
  device 0
  subdevice 0
  format S32_LE
  rate 48000
}

# ------------------------------------------------------
# playback PCM device: using loopback subdevice 0,0
# Don't use a buffer size that is too small. Some apps 
# won't like it and it will sound crappy 

pcm.amix {
  type dmix
  ipc_key 219345
  slave {
    pcm loophw00
    period_size 2048
    periods 2
  }
}

# ------------------------------------------------------
# software volume
pcm.asoftvol {
  type softvol
  slave.pcm "amix"

  control { name PCM }

  min_dB -51.0
  max_dB   0.0
}

# ------------------------------------------------------
# for jack alsa_in: looped-back signal at other ends
pcm.cloop {
  type hw
  card Loopback
  device 1
  subdevice 0
  format S32_LE
  rate 48000
}

# ======================================================
# ------------------------------------------------------
# hardware 0,1 : used for ALSA capture
pcm.loophw01 {
  type hw
  card Loopback
  device 0
  subdevice 1
  format S32_LE
  rate 48000
}

# ------------------------------------------------------
# for jack alsa_out: looped-back signal at other end
pcm.ploop {
  type hw
  card Loopback
  device 1
  subdevice 1
  format S32_LE
  rate 48000
}

# ======================================================
# ------------------------------------------------------
# duplex device combining our PCM devices defined above
pcm.aduplex {
  type asym
  playback.pcm "asoftvol"
  capture.pcm "loophw01"
}

# ------------------------------------------------------
# default device
pcm.!default {
  type plug
  slave.pcm aduplex

  hint {
       show on
       description "Duplex Loopback"
  }
}
:?:

kind regards

User avatar
fredx181
Posts: 4448
Joined: Wed 11 Dec 2013, 12:37
Location: holland

#149 Post by fredx181 »

Hi oui,

The file is '/var/lib/alsa/asound.state' where the mixer values are stored.
Comment this line in remasterdog to not remove it:

Code: Select all

rm -f "$WORK"/var/lib/alsa/asound.state
To reflect the changes made in alsamixer directly during a session;

Code: Select all

alsactl store 0
how far can the thematic of following recent message help here:
I think none, it's not for mixer values stored

Fred

stemsee

#150 Post by stemsee »

fredx181 wrote:Adding this on top of $HOME/.dogradio/data/func should work (doesn't work adding to /usr/local/bin/dogradio):

Code: Select all

#!/bin/bash

shopt -s expand_aliases
alias mplayer='mplayer -ao alsa:device=btheadset "$@"'

......
......
This worked great on top of what I alreay have set up as regards loop-back on alsa for jack audio!

mcewanw
Posts: 3169
Joined: Thu 16 Aug 2007, 10:48
Contact:

chroot method of creating multi-arch (32/64bit) environment?

#151 Post by mcewanw »

fredx181 wrote:Hi Mikeslr.

From what I tested and read (searching the web), I think the only way that works for 32 bit wine apps is to setup a multiarch environment.
Hello Fred,

As I was reading up on something else, entirely unrelated, I came across this old (perhaps out-of-date) link, which outlines a method that may or may not be useful as a possible alternative way to create a multi-arch (32bit/64bit) environment. So just posting it in case useful info:

https://www.debian-administration.org/a ... ian_system
One way - they say - is to install the ia32-libs, but I wanted to be all clean about it and use the arguably harder 'chroot' method. This way, one can achieve a modular, easily upgradeble system. Both 64- and 32- bit apps are separated from each other, and all users can - compeletely transparently - call the 32-bit apps from within their 64-bit text consoles and DEs.
EDIT: The method does seem to be quite involved and appears to need modified depending on which Debian distribution version being used - but the idea is perhaps of interest.

William
github mcewanw

stemsee

#152 Post by stemsee »

Hi Fred

Could you post your patches for the fan problem!

cheers
stemsee

User avatar
fredx181
Posts: 4448
Joined: Wed 11 Dec 2013, 12:37
Location: holland

#153 Post by fredx181 »

Hi Stemsee,

Here they are attached.

It could well be, btw, that these are applied now in kernel 4.5

Fred
Attachments
thermal-patches.tar.gz
thermal patches
(2.94 KiB) Downloaded 232 times

User avatar
fredx181
Posts: 4448
Joined: Wed 11 Dec 2013, 12:37
Location: holland

#154 Post by fredx181 »

Hi oui,

Here's what works for me installing skype:
Will take a lot of space, also because of the multi-arch setup.

Code: Select all

# First do some fixing (will be included in next iso release)
# Install debian version of package libxml2 (as it should be)
apt-get install libxml2=2.9.1+dfsg1-5+deb8u1
# Remove 0 byte files, otherwise apt will refuse to install some packages
find /usr/share/doc -type f -exec rm -f {} \;
find /usr/share/man -type f -exec rm -f {} \;

# Add ppa for skype (will install only skype and skype-bin from that repo):
echo -e "\ndeb http://archive.canonical.com/ trusty partner" >> /etc/apt/sources.list

# Add arch i386
dpkg --add-architecture i386
apt-get update
apt-get install skype:i386 # (type y if you trust it)
apt-get install apulse:i386
The apulse package I just added to the DD64 repository.
It's a Pulse emulator for alsa, this way you don't need to install pulseaudio (which skype in fact depends on)

Edit: Almost forgot, start skype with apulse:

Code: Select all

apulse skype
Fred

User avatar
fredx181
Posts: 4448
Joined: Wed 11 Dec 2013, 12:37
Location: holland

#155 Post by fredx181 »

Added to Extra-modules:
Skype module with multi-arch build in, run Skype from Menu> Network after activating.
https://dl.dropboxusercontent.com/u/363 ... e.squashfs

DebDog64-Jessie/Extra-Modules at DropBox

Added new version of (already included) package "openbox-light" to the custom repository, changes:
- added custom keyboard shortcuts
- displays shortcuts info dialog at login (see screenshot)
If you have custom keyboard-shortcuts already set, these will be overwritten, so better backup ~/.config/openbox/rc.xml first in that case.
Install/upgrade with:

Code: Select all

apt-get install openbox-light
Fred
Attachments
keyboard-shortcuts-info-dialog.jpg
keyboard-shortcuts-info-dialog
(46.22 KiB) Downloaded 464 times
Last edited by fredx181 on Mon 22 Feb 2016, 19:21, edited 2 times in total.

Post Reply