DebianDog64 - 64 bit DebianDog-Jessie
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
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.
*** 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:
Fred
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:
See for more info in the ReadMe.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
Fred
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"
}
}
Currently it's not possible, the .deb from the skype website is i386 .oui wrote:Hi
How to install skype?
Kind regards
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
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:
kind regards
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
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:
To reflect the changes made in alsamixer directly during a session;
Fred
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
Code: Select all
alsactl store 0
I think none, it's not for mixer values storedhow far can the thematic of following recent message help here:
Fred
This worked great on top of what I alreay have set up as regards loop-back on alsa for jack audio!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 "$@"' ...... ......
chroot method of creating multi-arch (32/64bit) environment?
Hello Fred,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.
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
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.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.
William
github mcewanw
Hi Stemsee,
Here they are attached.
It could well be, btw, that these are applied now in kernel 4.5
Fred
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 233 times
Hi oui,
Here's what works for me installing skype:
Will take a lot of space, also because of the multi-arch setup.
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:
Fred
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
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
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:
Fred
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
- 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.
Thank you very much Fred!
But a question:
- camera seems to work
- sound not because it is on a «virtual device»
how to commute it to the real sound and open the microphone and speaker/headphone (I don't can hear the Skype test call; it starts well but no sound)? Which app (/usr/bin/... ) does that?
Kind regards
But a question:
- camera seems to work
- sound not because it is on a «virtual device»
how to commute it to the real sound and open the microphone and speaker/headphone (I don't can hear the Skype test call; it starts well but no sound)? Which app (/usr/bin/... ) does that?
Kind regards
Hi oui,
If you installed skype as I described, did you install apulse?
If so, run from terminal:
(/usr/bin/apulse)
If you loaded the skype_apulse.squashfs it should work when running from menu as I edited the .desktop launcher to Exec=apulse skype
In the sound options it should look like in the attached screenshot.
Good luck!
Fred
If you installed skype as I described, did you install apulse?
Code: Select all
apt-get install apulse:i386
Code: Select all
apulse skype
If you loaded the skype_apulse.squashfs it should work when running from menu as I edited the .desktop launcher to Exec=apulse skype
In the sound options it should look like in the attached screenshot.
Good luck!
Fred
- Attachments
-
- apulse-skype.jpg
- apulse-skype
- (31.42 KiB) Downloaded 523 times
OK, nice!oui wrote:Thank you Fred! Works pretty now. Skype is ok!
In case you use the skype_apulse.squashfs module, I found that unloading failed for me, fixed and re-uploaded:
New "skype_apulse.squashfs" without having included libc6 64 bit libraries.
(probably having them included was the reason for the unloading failure, unloading works fine now for me)
https://dl.dropboxusercontent.com/u/363 ... e.squashfs
Fred
Hi Fred
Thank you very much.
I have an other problem now. Skype works, but if I remaster the size of the 01-filesystem.squashfs to include the needing apulse:i386 in my base it increase terribly (from actually 395, because of Ted, NtEd, Granule, Merkaartor, Marble, Gramps and Python, etc., to 578 Mb, now after the use of Skype).
It was the same with the LazY-Puplets all! But RSH did offer in his remaster suite an easy way to unload at remaster time all loaded modules before the system was remastered so that no external module was saved with the "actual" base.
how to do that in DebianDog?
Kind regards
Thank you very much.
I have an other problem now. Skype works, but if I remaster the size of the 01-filesystem.squashfs to include the needing apulse:i386 in my base it increase terribly (from actually 395, because of Ted, NtEd, Granule, Merkaartor, Marble, Gramps and Python, etc., to 578 Mb, now after the use of Skype).
It was the same with the LazY-Puplets all! But RSH did offer in his remaster suite an easy way to unload at remaster time all loaded modules before the system was remastered so that no external module was saved with the "actual" base.
how to do that in DebianDog?
Kind regards