Fatdog64-700/701 [April 22 2015] [CLOSED]
Those settings are meant to set the default soundcard to bluetooth. It does stick. However, it has nothing to do with making the bluetooth connection persistent over reboot. Each time you reboot the bluetooth connection is gone and you'll have to re-connect again. So do you mean to make the bt connection persistent over reboots?Semme wrote:JB, those settings don't stick. I think it's gotta happen manually and I'm pretty sure I know which file.
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
Run
bt-audio -c "your-bluetooth-speaker-name"
or
bt-audio -c "your-bluetooth-audio-MAC-address"
somewhere in rc.local. Or you can do that in /etc/xdg/Startup too (create a startup file there).
Make sure you check that "bluetoothd" is already up and running before running the command.
bt-audio -c "your-bluetooth-speaker-name"
or
bt-audio -c "your-bluetooth-audio-MAC-address"
somewhere in rc.local. Or you can do that in /etc/xdg/Startup too (create a startup file there).
Make sure you check that "bluetoothd" is already up and running before running the command.
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
@Semme - no worries, good luck.
@smokey01 - nothing can be done about it, unfortunately. They are suggesting that we use /dev/disk/by-label or /dev/disk/by-uuid to mount instead of /dev/sdXXX ... but our mount/unmount infrastructure now relies on /dev/sdXXX.
@smokey01 - nothing can be done about it, unfortunately. They are suggesting that we use /dev/disk/by-label or /dev/disk/by-uuid to mount instead of /dev/sdXXX ... but our mount/unmount infrastructure now relies on /dev/sdXXX.
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
-
- Posts: 152
- Joined: Tue 06 Oct 2015, 14:10
- Location: on the inter-planet train
suggestion
dear Jamesbond,
when i open more and more programs, the bottom of the screen may not be enough space.(but i don't want to use number 2 virtual desktop). May I suggest that the text "Menu " four characters adjacent to the dog icon at the left-bottom corner be remove so as to leave more space. see attached screenshot. thanks.
when i open more and more programs, the bottom of the screen may not be enough space.(but i don't want to use number 2 virtual desktop). May I suggest that the text "Menu " four characters adjacent to the dog icon at the left-bottom corner be remove so as to leave more space. see attached screenshot. thanks.
- Attachments
-
- test1.jpg
- (73.87 KiB) Downloaded 542 times
-
- Posts: 152
- Joined: Tue 06 Oct 2015, 14:10
- Location: on the inter-planet train
Thanks Jamesbond for your quick response. Also suggest that the two icons for virtual desktop1 and virtual desktop2 can be combined into a single icon, that is, first click of this single icon bring user to virtual desktop2 and second click of it bring user back to virtual desktop1. Maybe this can further save more space.
-
- Posts: 152
- Joined: Tue 06 Oct 2015, 14:10
- Location: on the inter-planet train
update to kernel 4.3.3
I have been using FD701 since its first release. Just replace the old kerenl with kernel 4.3.3 and everything works fine. Sound effects seems to be better when playing MP3 files with this new kernel.
Thanks again kirk and jamesbond for such a wonderful distro.
Thanks again kirk and jamesbond for such a wonderful distro.
Hey smokey01 , I have the same problem with one of my UEFI based computers changing drives but in my case it's because live disk images are staying memory resident until i physically unplug the power supply for a few seconds as normal power down doesn't clear it.
I can remove all drives including the boot media so only the ram is plugged in and the computer will still boot from the previous live image stored in ram , so i assume when the boot media is attached the previous memory resident image is corrupting the fresh boot image in some way.
I checked the UEFI Bios settings and everything is set to power down and all the green power saving settings are disabled and there isn't any setting in regards to saving the ram page file layer so my only option is to physically unplug until i can find a ram wiper at shutdown.
Just thought i'd mention it in case your situation should arise again as something else to check.
regards
I can remove all drives including the boot media so only the ram is plugged in and the computer will still boot from the previous live image stored in ram , so i assume when the boot media is attached the previous memory resident image is corrupting the fresh boot image in some way.
I checked the UEFI Bios settings and everything is set to power down and all the green power saving settings are disabled and there isn't any setting in regards to saving the ram page file layer so my only option is to physically unplug until i can find a ram wiper at shutdown.
Just thought i'd mention it in case your situation should arise again as something else to check.
regards
If you are on 701 and not willing to update to 702, here is the way to update to the latest glibc.
0. Backup your savefile/savedir.
1. Download the patched glibc http://distro.ibiblio.org/fatdog/packag ... 6_64-2.txz
2. Open terminal.
3. mkdir /tmp/x
4. ROOT=/tmp/x installpkg /path/to/downloaded/glibc-2.19-x86_64-2.txz
5. /aufs/pup_init/bin/busybox cp -a /tmp/x/* /
6. /aufs/pup_init/bin/busybox sync
7. /aufs/pup_init/bin/busybox sync
8. Reboot.
Notes:
- 6 & 7 is not typo, do the sync twice.
- And use /aufs/pup_init/bin/busybox, don't try to be clever and use /bin/busybox (or even worse - use the "cp" and "sync" command directly ...).
- Do this while DISABLING the RAM layer. I haven't tested and don't know whether this will work in when RAM layer is active. (Consequently, I haven't tested and don't know if this will work for multisession users).
________________
Alternative way of doing it:
1. Boot without savefile/savedir
2. Download the updated glibc.
3. Open your savefile/savedir
4. Open terminal.
5. In terminal, "cd" to the location of savedir/savefile.
6. Make sure that "pwd" returns the location of your opened savedir/savefile.
7. Run ROOT=$(pwd) installpkg /path/to/downloaded/glibc-update.txz
8. Reboot.
____________________
Yet alternative way:
1. Download the updated glibc.
2. Extract content somewhere.
3. Make an SFS of the extracted content.
4. Load the SFS, and load it permanently for next boot also.
5. Reboot.
cheers!
0. Backup your savefile/savedir.
1. Download the patched glibc http://distro.ibiblio.org/fatdog/packag ... 6_64-2.txz
2. Open terminal.
3. mkdir /tmp/x
4. ROOT=/tmp/x installpkg /path/to/downloaded/glibc-2.19-x86_64-2.txz
5. /aufs/pup_init/bin/busybox cp -a /tmp/x/* /
6. /aufs/pup_init/bin/busybox sync
7. /aufs/pup_init/bin/busybox sync
8. Reboot.
Notes:
- 6 & 7 is not typo, do the sync twice.
- And use /aufs/pup_init/bin/busybox, don't try to be clever and use /bin/busybox (or even worse - use the "cp" and "sync" command directly ...).
- Do this while DISABLING the RAM layer. I haven't tested and don't know whether this will work in when RAM layer is active. (Consequently, I haven't tested and don't know if this will work for multisession users).
________________
Alternative way of doing it:
1. Boot without savefile/savedir
2. Download the updated glibc.
3. Open your savefile/savedir
4. Open terminal.
5. In terminal, "cd" to the location of savedir/savefile.
6. Make sure that "pwd" returns the location of your opened savedir/savefile.
7. Run ROOT=$(pwd) installpkg /path/to/downloaded/glibc-update.txz
8. Reboot.
____________________
Yet alternative way:
1. Download the updated glibc.
2. Extract content somewhere.
3. Make an SFS of the extracted content.
4. Load the SFS, and load it permanently for next boot also.
5. Reboot.
cheers!
-= The Fatdog Team (kirk, jamesbond, SFR and step) =-
[url=http://murga-linux.com/puppy/viewtopic.php?p=794748#794748]Contributed Fatdog64 packages thread[/url]
This account is used for announcements only. Send PM directly to members' handle.
[url=http://murga-linux.com/puppy/viewtopic.php?p=794748#794748]Contributed Fatdog64 packages thread[/url]
This account is used for announcements only. Send PM directly to members' handle.
Problema booting live cd: kernel panic
Hi, I'm trying Fatdog64 702 with the goal to install on an old Asus A6000KMSeries notebook.
I'm not able to boot the distro with a USB drive because I receive a kernel panic message.
So I tried to use the same iso with virtualbox on an other PC but I receive the same message.
I attach a screenshot of the last test.
Can anybody help me?
Thanks
Salvo
I'm not able to boot the distro with a USB drive because I receive a kernel panic message.
So I tried to use the same iso with virtualbox on an other PC but I receive the same message.
I attach a screenshot of the last test.
Can anybody help me?
Thanks
Salvo
- Attachments
-
- screen_20160507-223020.png
- (15.66 KiB) Downloaded 402 times
-
- Posts: 152
- Joined: Tue 06 Oct 2015, 14:10
- Location: on the inter-planet train
@ktrls,
there is a separate thread for FD702 and you can post the problem you encountered there. Did you try with "small initrd" ? Some machines with limited RAM may not boot huge initrd(contained in the original iso).
edit: some machines may also has some bios limitations. So I would always prefer the small initrd method when booting Fatdog64.
there is a separate thread for FD702 and you can post the problem you encountered there. Did you try with "small initrd" ? Some machines with limited RAM may not boot huge initrd(contained in the original iso).
edit: some machines may also has some bios limitations. So I would always prefer the small initrd method when booting Fatdog64.
Re: Fatdog64-700 FINAL [Feb 22 2015]
These are $40 at the Aussie PO now (just to see if it posts seeing as it says the thread is [CLOSED] )Billtoo wrote:I installed Fatdog64-700 to an external 128gb usb-3.0 SSD.
Thankyou kirk and jamesbond.
Just posting a link to 01micko's Acer Iconia W500 test with fatdog:
http://murga-linux.com/puppy/viewtopic. ... 985#836985
and:
http://www.murga-linux.com/puppy/viewtopic.php?t=98523
Edoc - are you here? Did i see you post about getting puppy running on a similar iconia tablet somewhere??
http://murga-linux.com/puppy/viewtopic. ... 985#836985
and:
http://www.murga-linux.com/puppy/viewtopic.php?t=98523
Edoc - are you here? Did i see you post about getting puppy running on a similar iconia tablet somewhere??