Fatdog64-700/701 [April 22 2015] [CLOSED]

A home for all kinds of Puppy related projects
Message
Author
User avatar
Semme
Posts: 8399
Joined: Sun 07 Aug 2011, 20:07
Location: World_Hub

#1156 Post by Semme »

JB, those settings don't stick.

I think it's gotta happen manually and I'm pretty sure I know which file.

If you don't mind though, please confirm the file..
>>> Living with the immediacy of death helps you sort out your priorities. It helps you live a life less trivial <<<

jamesbond
Posts: 3433
Joined: Mon 26 Feb 2007, 05:02
Location: The Blue Marble

#1157 Post by jamesbond »

Semme wrote:JB, those settings don't stick. I think it's gotta happen manually and I'm pretty sure I know which file.
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?
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]

User avatar
Semme
Posts: 8399
Joined: Sun 07 Aug 2011, 20:07
Location: World_Hub

#1158 Post by Semme »

That may be a better way of putting it, and if possible. Advice?

The onboard card I killed in BIOS. I'll be getting my second shot later this afternoon..

jamesbond
Posts: 3433
Joined: Mon 26 Feb 2007, 05:02
Location: The Blue Marble

#1159 Post by jamesbond »

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.
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]

User avatar
Semme
Posts: 8399
Joined: Sun 07 Aug 2011, 20:07
Location: World_Hub

#1160 Post by Semme »

Thank you JB.. Those are good sounding tips I'm going to put to use TODAY!

I'll let you know how I got on.. :wink:
>>> Living with the immediacy of death helps you sort out your priorities. It helps you live a life less trivial <<<

jamesbond
Posts: 3433
Joined: Mon 26 Feb 2007, 05:02
Location: The Blue Marble

#1161 Post by jamesbond »

@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.
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]

quirkian2new
Posts: 152
Joined: Tue 06 Oct 2015, 14:10
Location: on the inter-planet train

suggestion

#1162 Post by quirkian2new »

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.
Attachments
test1.jpg
(73.87 KiB) Downloaded 542 times

jamesbond
Posts: 3433
Joined: Mon 26 Feb 2007, 05:02
Location: The Blue Marble

#1163 Post by jamesbond »

@quirkian - right-click on the dog menu, choose "configure", and then un-tick "show text".
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]

User avatar
smokey01
Posts: 2813
Joined: Sat 30 Dec 2006, 23:15
Location: South Australia :-(
Contact:

#1164 Post by smokey01 »

@jamesbond it was a loose sata3 connector to my 3TB WD black. The connector does not lock onto the drive the same way it does to the motherboard. Thanks for the heads up.

quirkian2new
Posts: 152
Joined: Tue 06 Oct 2015, 14:10
Location: on the inter-planet train

#1165 Post by quirkian2new »

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.

quirkian2new
Posts: 152
Joined: Tue 06 Oct 2015, 14:10
Location: on the inter-planet train

update to kernel 4.3.3

#1166 Post by quirkian2new »

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.

Fbang
Posts: 7
Joined: Sun 31 Jan 2016, 10:45

#1167 Post by Fbang »

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

fatdog
Posts: 104
Joined: Wed 17 Apr 2013, 03:12

#1168 Post by fatdog »

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!
-= 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.

ktrls
Posts: 3
Joined: Sat 07 May 2016, 20:28

Problema booting live cd: kernel panic

#1169 Post by ktrls »

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
Attachments
screen_20160507-223020.png
(15.66 KiB) Downloaded 402 times

quirkian2new
Posts: 152
Joined: Tue 06 Oct 2015, 14:10
Location: on the inter-planet train

#1170 Post by quirkian2new »

@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.

ktrls
Posts: 3
Joined: Sat 07 May 2016, 20:28

#1171 Post by ktrls »

I'm sorry, quirkian2new. I'm a newbie on this forum and I was wrong.

I'm going to post my question on the right thread.

BTW I don't know how to use a small initrd

Thanks a lot
Salvo

april

Re: Fatdog64-700 FINAL [Feb 22 2015]

#1172 Post by april »

Billtoo wrote:I installed Fatdog64-700 to an external 128gb usb-3.0 SSD.

Thankyou kirk and jamesbond.
These are $40 at the Aussie PO now (just to see if it posts seeing as it says the thread is [CLOSED] )

User avatar
greengeek
Posts: 5789
Joined: Tue 20 Jul 2010, 09:34
Location: Republic of Novo Zelande

#1173 Post by greengeek »

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??

Post Reply