The time now is Thu 21 Jan 2021, 23:18
All times are UTC - 4 |
Page 35 of 58 [857 Posts] |
Goto page: Previous 1, 2, 3, ..., 33, 34, 35, 36, 37, ..., 56, 57, 58 Next |
Author |
Message |
dcung
Joined: 13 Jul 2018 Posts: 242 Location: Down Under - 3rd rock from Sun.
|
Posted: Thu 06 Sep 2018, 05:17 Post subject:
|
|
I saw other dogs have separate locale SFS for 32 & 64 bit.
Just confirming, BionicDog 32 & 64 use same sfs (only see one on 1st page)?
99-locales-BionicDog-2018-04-21.squashfs
How do you set locale? I loaded the SFS and I was looking for a menu to set locale but could not see it.
I am assuming that this would get rid of those setlocale warnings that I sometimes saw?
Thanks.
|
Back to top
|
|
 |
fredx181

Joined: 11 Dec 2013 Posts: 4481 Location: holland
|
Posted: Thu 06 Sep 2018, 15:39 Post subject:
|
|
Hi dcung,
For the locales, 64 or 32-bit makes no difference AFAIK.
It's not straightforward for Bionicdog and will be not be perfect, to do manually, see earlier topic (Russian) (first put "99-locales-BionicDog-2018-04-21.squashfs" in casper directory and reboot):
http://murga-linux.com/puppy/viewtopic.php?p=991270#991270
(and scroll down for more about it (and some on next page)
More info on Xenialdog thread, for German (a bit different method but should work on Bionicdog also)
http://murga-linux.com/puppy/viewtopic.php?p=963259#963259
Quote: | I am assuming that this would get rid of those setlocale warnings that I sometimes saw? |
What warnings were that ?
Fred
_________________ Dog Linux website
Tinylinux blog by wiak
|
Back to top
|
|
 |
dcung
Joined: 13 Jul 2018 Posts: 242 Location: Down Under - 3rd rock from Sun.
|
Posted: Thu 06 Sep 2018, 17:03 Post subject:
|
|
fredx181 wrote: | What warnings were that ? |
Sometimes these appears when I run apt-get to install apps.
Code: | perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
|
AFAIK it is 'cosmetic', ie. apps still installed OK.
And I came across this
https://ubuntuforums.org/showthread.php?t=1720356
which basically says (?)
Code: | # add to /etc/environment and reboot.
LANGUAGE="en_US.UTF-8"
LC_ALL="en_US.UTF-8"
LANG="en_US.UTF-8" |
It seems to 'solve' apt-get warning, but 'create' another problem.
When I open a terminal, then I get the same warning...
So, it seems to 'migrate'...
So, I thought....maybe play with locales...
.
.
|
Back to top
|
|
 |
trister
Joined: 01 Mar 2015 Posts: 137
|
Posted: Fri 07 Sep 2018, 04:43 Post subject:
nomodeset Subject description: If you can't start BionicDog64 - nomodeset - extra drives for xorg if you can't boot |
|
Squashfs that adds some missing xorg drivers (I hope I got the terminology right) that will allow to run BionicDog64 to some "difficult" PCs/Laptops.
bionicdog64_extra_stretchdog64_drivers_vesa_v01.squashfs https://1fichier.com/?jnnfcy223opa26anprrp
This was a revelation for me since cause of this problem I was forced to using DebianDogs (I don't regret it though )
The history behind this (you can ignore it ) :
2 years ago I had to select a current linux distro for my work. My old requirements were very old PCs so I was using puppy distros like fluppy and precise.
I got a new i5 PC and started trying puppy and dog distros.
In short I could only boot fluppy, DebianDog, XenialDog32 and StretchDog and WindowsXP live CDs . The machine was booting with generic drivers (and it was ok for me since I don't use heavy graphics apps).
I tried many distros (even arch linux did not boot) Only setting nomodeset in kernel parameters I could startX.
Yesterday, I tried BionicDog64 and it (as I expected) it also did not run -even with nomode set.
Comparing with StretchDog64 I found that VESA drivers were missing. I did a squashfs with drivers from StretchDog64 that did not exist in BionicDog64 and now I have a working BIonicDog64 system (using nomodeset parameter).
I am posting the additional drivers here because I think the lack o VESA drivers will stop this distro from working in many "strange: laptops & PCs.
I still haven't managed to manually set or detect my real graphics card in xorg ( Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] ) but at least I can work with bionicdog64 and vesa.
Files that are contained in the squashfs are :
/usr/lib/xorg/modules/drivers/ :
-rw-r--r-- 1 root root 31800 May 7 2015 cirrus_alpine.so
-rw-r--r-- 1 root root 19448 May 7 2015 cirrus_drv.so
-rw-r--r-- 1 root root 27928 May 7 2015 cirrus_laguna.so
-rw-r--r-- 1 root root 23656 Sep 23 2013 fbdev_drv.so
-rw-r--r-- 1 root root 149728 May 7 2015 mach64_drv.so
-rw-r--r-- 1 root root 144856 Jan 18 2017 mga_drv.so
-rw-r--r-- 1 root root 66640 May 8 2015 neomagic_drv.so
-rw-r--r-- 1 root root 348592 Jan 23 2017 openchrome_drv.so
-rw-r--r-- 1 root root 140992 Jan 18 2017 savage_drv.so
-rw-r--r-- 1 root root 77240 Jan 18 2017 sisusb_drv.so
-rw-r--r-- 1 root root 66040 Jan 18 2017 tdfx_drv.so
-rw-r--r-- 1 root root 142320 Jan 18 2017 trident_drv.so
-rw-r--r-- 1 root root 27760 Oct 28 2015 vesa_drv.so
|
Back to top
|
|
 |
rcrsn51

Joined: 05 Sep 2006 Posts: 13129 Location: Stratford, Ontario
|
Posted: Fri 07 Sep 2018, 10:26 Post subject:
|
|
@trister: Here are some additional thoughts on this issue:
1. The only people who still have these old machines are computer hobbyists and obsessive hoarders. Everyone else sent them to e-waste recycling long ago.
2. Read proebler's report here about his Computer #4. Even though it wanted the mga driver, the version out of Debian no longer worked with his hardware. I suspect that this will also be true with other ancient video cards.
Luckily, it's easy to install VESA from the console prompt if Xorg fails to start:
Code: | apt-get update
apt-get install xserver-xorg-video-vesa
startx |
3. I debated including this driver in the Starter Kit ISO. But I was curious about how many people would be impacted by its absence. In my experience, the built-in modesetting drivers handle the vast majority of machines fine.
4. Many owners of Win8/Win10/UEFI machines are switching them to legacy mode so they can install a Linux. But this sometimes has a nasty side-effect - only VESA video now works. I have seen this myself.
The preferred solution on these machines is to disable Secure Boot and boot Linux using the UEFI firmware.
----------------
|
Back to top
|
|
 |
trister
Joined: 01 Mar 2015 Posts: 137
|
Posted: Fri 07 Sep 2018, 16:36 Post subject:
|
|
rcrsn51 wrote: | @trister: Here are some additional thoughts on this issue:
1. The only people who still have these old machines are computer hobbyists and obsessive hoarders. Everyone else sent them to e-waste recycling long ago.
|
rcrsn51 wrote: |
2. Read proebler's report here about his Computer #4. Even though it wanted the mga driver, the version out of Debian no longer worked with his hardware. I suspect that this will also be true with other ancient video cards.
Luckily, it's easy to install VESA from the console prompt if Xorg fails to start:
Code: | apt-get update
apt-get install xserver-xorg-video-vesa
startx |
|
The school lab I was in the past (4 years ago) had computer #4 but with only 500MB ram (P4). I did not know and Dogs distro then only puppy. In these old PCs I used precise puppy and fluppy (which is so far the most reliable puppy I've used). I also had added a modified version of edupup200.iso and HanSamBen431. These PCs runned Windows XP and was very slow. In the next building there were the same machines but with windows 2000. The speed difference was noticable.
I also discovered somewhere a PII with 32MB and Windows 98. It run with a very decent speed and had Office 2000... In the last PC I tried pulp and pUPnGO puppies but they ware dead slow...
rcrsn51 wrote: |
3. I debated including this driver in the Starter Kit ISO. But I was curious about how many people would be impacted by its absence. In my experience, the built-in modesetting drivers handle the vast majority of machines fine.
|
I had this issue in many of my friends PCs and laptops. In a very new PC with a new GPU even StretchDog64 could not run.
I tried the modsetting driver just today morning in my work PC (the problematic i5 I mentioned) and it did not work (tried without nomodeset kernel parameter).
rcrsn51 wrote: |
4. Many owners of Win8/Win10/UEFI machines are switching them to legacy mode so they can install a Linux. But this sometimes has a nasty side-effect - only VESA video now works. I have seen this myself.
- |
rcrsn51 wrote: |
The preferred solution on these machines is to disable Secure Boot and boot Linux using the UEFI firmware.
---------------- |
I suspect this would be the case... After many tries I decided that LICK boot loader is the best solution. It installs in Windows 10 a grub4dos-like boot loader without any problems.
I don't know though how I could boot an StretchDog frugal installation....
|
Back to top
|
|
 |
dcung
Joined: 13 Jul 2018 Posts: 242 Location: Down Under - 3rd rock from Sun.
|
Posted: Fri 07 Sep 2018, 20:35 Post subject:
|
|
A member (step) provided me with the code I needed for Fatdog
http://murga-linux.com/puppy/viewtopic.php?t=114126&start=1
Code: | /usr/sbin/fatdog-drive-icon-mount-helper.sh /dev/sdb1 /mnt/sdb1 |
I'm looking to do the same in BionicDog.
Anyone knows what codes get invoked when you click USB disk 'icon'?
.
i.e. I'd to 'pretend' I have clicked/mounted that at each boot.
Description |
|
Filesize |
52.74 KB |
Viewed |
1046 Time(s) |

|
|
Back to top
|
|
 |
rcrsn51

Joined: 05 Sep 2006 Posts: 13129 Location: Stratford, Ontario
|
Posted: Fri 07 Sep 2018, 23:39 Post subject:
|
|
With what filesystem is sdb1 formatted?
|
Back to top
|
|
 |
trister
Joined: 01 Mar 2015 Posts: 137
|
Posted: Sat 08 Sep 2018, 01:35 Post subject:
Subject description: Speed comparison between BionicDog64 & StretchDog64 (made with Freds script) |
|
In the 2 PCs I've tried (in the 1 both use vesa and in the other both detect/use i915) I see quite a speed difference.
In normal operations (browsing, libreoffice ,flash games) StretchDog 64bit seems a lot quicker than BionicDog 64bit.
StretchDog loads at start 120+ squashfs and bionicdog loads 10 squashfs (which are the exact ones that I use in StretchDog).
Is this speed difference normal?
It's not that important to me , I just ask out of curiosity.
|
Back to top
|
|
 |
dcung
Joined: 13 Jul 2018 Posts: 242 Location: Down Under - 3rd rock from Sun.
|
Posted: Sat 08 Sep 2018, 01:40 Post subject:
|
|
rcrsn51 wrote: | With what filesystem is sdb1 formatted? |
ext4.
Does it matter though? I'm hoping it doesn't, that way whatever USB disk I plug in, the startup command still works.
|
Back to top
|
|
 |
fredx181

Joined: 11 Dec 2013 Posts: 4481 Location: holland
|
Posted: Sat 08 Sep 2018, 03:45 Post subject:
|
|
dcung wrote: | A member (step) provided me with the code I needed for Fatdog
http://murga-linux.com/puppy/viewtopic.php?t=114126&start=1
Code:
/usr/sbin/fatdog-drive-icon-mount-helper.sh /dev/sdb1 /mnt/sdb1
I'm looking to do the same in BionicDog. |
How about "fatdog-drive-icon-mount-helper.sh" ?
Well... it works but needs "guessfstype", install from synaptic or apt-get.
I modified a bit (commented out a few lines that are puppy specific only and not needed for Bionicdog), see attached. should work the same as in Fatdog, e.g.
Code: | fatdog-drive-icon-mount-helper.sh /dev/sdb1 /mnt/sdb1 |
EDIT:
Quote: | Anyone knows what codes get invoked when you click USB disk 'icon'? |
That is "pup-volume-monitor", it runs as a daemon, started at boot, I don't think it can be used to mount a single partition (anyway, I couldn't find how)
Fred
Description |
fatdog-drive-icon-mount-helper.sh (modified) depends on package "guessfstype"
|

Download |
Filename |
fatdog-drive-icon-mount-helper.sh_mod.tar.gz |
Filesize |
1.46 KB |
Downloaded |
113 Time(s) |
_________________ Dog Linux website
Tinylinux blog by wiak
|
Back to top
|
|
 |
fredx181

Joined: 11 Dec 2013 Posts: 4481 Location: holland
|
Posted: Sat 08 Sep 2018, 04:03 Post subject:
|
|
trister wrote: | StretchDog loads at start 120+ squashfs and bionicdog loads 10 squashfs (which are the exact ones that I use in StretchDog). |
Do you mean that Bionicdog is limited to load no more than 10 squashfs ?
I have no idea about why there's speed difference for you, for me it's practically the same.
Fred
_________________ Dog Linux website
Tinylinux blog by wiak
|
Back to top
|
|
 |
dcung
Joined: 13 Jul 2018 Posts: 242 Location: Down Under - 3rd rock from Sun.
|
Posted: Sat 08 Sep 2018, 04:23 Post subject:
|
|
fredx181 wrote: | How about "fatdog-drive-icon-mount-helper.sh" ?
Well... it works but needs "guessfstype", install from synaptic or apt-get.
I modified a bit (commented out a few lines that are puppy specific only and not needed for Bionicdog), see attached. should work the same as in Fatdog, |
Good idea, Fred! 🏆
I just tried it (using your modified one), but could not find guess_fstype or guessfstype (thru synaptic nor apt-get). I did update the database first apt-get update.
Code: | root@biodog-sh:~# apt-get install guess_fstype
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package guess_fstype
root@biodog-sh:~#
root@biodog-sh:~/MyData# ./fatdog-drive-icon-mount-helper.sh /dev/sdb1 /mnt/sdb1
./fatdog-drive-icon-mount-helper.sh: line 53: guess_fstype: command not found
root@biodog-sh:~/MyData# |
EDIT - It just appears... Maybe you just uploaded to repo..and it needs time to sync.
And..
Yes....IT WORKS!
Thanks Fred...
Last edited by dcung on Sat 08 Sep 2018, 05:09; edited 1 time in total
|
Back to top
|
|
 |
dcung
Joined: 13 Jul 2018 Posts: 242 Location: Down Under - 3rd rock from Sun.
|
Posted: Sat 08 Sep 2018, 04:50 Post subject:
|
|
dcung wrote: | rcrsn51 wrote: | With what filesystem is sdb1 formatted? |
ext4.
Does it matter though? I'm hoping it doesn't, that way whatever USB disk I plug in, the startup command still works. |
Now, I get it why Bill was asking...
And I also was having trouble when I just execute mount command back then, before step provided fatdog script.
Never realised that guess_fstype took care of that..🙂
|
Back to top
|
|
 |
trister
Joined: 01 Mar 2015 Posts: 137
|
Posted: Sat 08 Sep 2018, 05:18 Post subject:
|
|
fredx181 wrote: | trister wrote: | StretchDog loads at start 120+ squashfs and bionicdog loads 10 squashfs (which are the exact ones that I use in StretchDog). |
Do you mean that Bionicdog is limited to load no more than 10 squashfs ?
Fred |
No , I have seen no limitation to the number of loaded squashfs in Bionic. (I would like to thank you again that in the distant past you had increased the number of sfs I could load )
I was just trying to point out that I see Bionic run more slow with just a fraction of the (same) squashfs files I use on StretchDog. I'm talking about the same PCs that see the same GPUs.
I was just making an observation. It just seems a bit odd. For example in the same palemoon with the same flash version. I had opened 5 swf games in StretchDog and 2 on Bionic and I had much worst fps. It seemed strange to me. Maybe it lacks another acceleration driver that I can't think of.
The most important thing I want Bionic to do for me is run the Vidyo Conference client (it runs only in ububtu -not debian) so this doesn't bother me.
|
Back to top
|
|
 |
|
Page 35 of 58 [857 Posts] |
Goto page: Previous 1, 2, 3, ..., 33, 34, 35, 36, 37, ..., 56, 57, 58 Next |
|
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
|