Fatdog64-710 Final [4 Dec 2016]

Message

jamesbond · #256 Post by **jamesbond** » Mon 13 Feb 2017, 14:05

@Dr. Dan: you could have attempted to download fatdog-update when I was updating it. Please try again.

@stemsee: That seems to be a weird xorg bug. You can see it happening by running this in terminal "setxkbmap pt" and then check the result by typing "setxkbmap -query". I use a "us" layout and after running the above, I got "layout: us,pt" instead of the correct "layout: pt". I have a workaround however, but I need to test how robust the workaround is.

@chiefengineer: I have Epson XP-200. It worked with DNSD protocol back in 702, but in 710 for inexplicable reasons it stopped working. I now use LPD protocol for the same printer, and it works. This is my connection: lpd://EPSONEC16A8.local:515/PASSTHRU

stemsee · #257 Post by **stemsee** » Mon 13 Feb 2017, 20:39

Jamesbond

after installing one of icakes chinese packages I was able to correctly change keyboard layout.

Code: Select all

# setxkbmap pt
# setxkbmap -query 
rules:      evdev
model:      pc105
layout:     pt
options:    terminate:ctrl_alt_bksp
#

dr. Dan · #258 Post by **dr. Dan** » Tue 14 Feb 2017, 02:56

@jamesbond: Just tried, same result, on two computers.

stemsee · #259 Post by **stemsee** » Tue 14 Feb 2017, 07:16

As regards locale switching, I have found a situation where after changing locale and restartx then change locale again and restartx all input devices are locked up! Then I must perform a hard reset (hold power button 4 seconds).

The context is fd-ls.sfs installed, icakes yong installed and a chinese system pet. I didn't try this out on a pristine fd4-710 insall; it may well be a bug in the base.

jamesbond · #260 Post by **jamesbond** » Tue 14 Feb 2017, 18:23

@Dr.Dan: anyone else can confirm Dr.Dan's problem? I can't duplicate the problem on my side.

Alternatively, Dr.Dan - just to download the file directly from http://distro.ibiblio.org/fatdog/packag ... arch-2.txz, and then check the checksum. List of checksums can be found here: http://distro.ibiblio.org/fatdog/packag ... CKSUMS.md5. If the checksum matches, you can install it. If not, then please don't install.

@stemsee: there is a way to make "pt" to behave correctly, but it is rather unexpected. The fact that you can get it right when you install the chinese pet could be an co-incidence rather than a fix.

RE: your "hang" - can you please try it in pristine mode. I have encountered similar crash before, when I have XIM configured but I don't run XIM server. It could be that icake's pets only run XIM server when it detects that the locale is Chinese.

@jake29: Your wine 2.0 package and SFS have been uploaded to the official repo. Thank you for your contribution.

Gobbi · #261 Post by **Gobbi** » Tue 14 Feb 2017, 19:22

No problem here .
Gslapt installed well fatdog-update-710.0-noarch-2.txz .

jake29 · #262 Post by **jake29** » Wed 15 Feb 2017, 06:35

jamesbond wrote:@jake29: Your wine 2.0 package and SFS have been uploaded to the official repo. Thank you for your contribution.

Glad I could help.

step · #263 Post by **step** » Thu 16 Feb 2017, 13:34

Just a note for people trying to troubleshoot wifi connection problems. It might help to peek at the system console, because the wpi_gui process (the "brains" behind the radar tray icon) logs its error messages there. You can dump system console output by opening a terminal window and typing to the shell: conspy -d 1 then scroll up the window until you get to the wpa_supplicant section. Example (your invalid lines - if any - will look different):

Code: Select all

50-Wpagui - auto dhcp for eth0                                                                                                                                  
50-Wpagui - loading wpa_supplicant for wlan0                                                                                                                    
Successfully initialized wpa_supplicant                                                                                                                         
Line 54: Invalid BSSID '"c4:6e:f1:40:8a:90"'.                                                                                                                   
Line 54: failed to parse bssid '"c4:6e:f1:40:8a:90"'.                                                                                                           
Line 62: failed to parse network block.                                                                                                                         
Line 78: Invalid BSSID '"30:a2:8f:98:46:bd"'.                                                                                                                   
Line 78: failed to parse bssid '"30:a2:8f:98:46:bd"'.                                                                                                           
Line 85: failed to parse network block.
                                     
Failed to read or parse configuration '/etc/wpa_supplicant.conf'.

In this example the last line tells us that the wlan0 interface isn't configured, hence it won't even show up in the pull-down list of adapters when you click the radar tray icon.

fr33land · #264 Post by **fr33land** » Thu 16 Feb 2017, 14:02

stemsee · #265 Post by **stemsee** » Thu 16 Feb 2017, 19:24

Wifi problems.

Try Wifi-Connect, with Wifi-Profiles, Wifi-Eduroam, Wifi-Scanner and Wifi-HotSpot.

wpagui only displays one wifi interface, when started with default configura.

Wifi-Connect, currently only at Alpha stage,
lets you use any or all! It's what I use on FatDog.

here is a shot of scanner admin mode.

jamesbond · #266 Post by **jamesbond** » Fri 17 Feb 2017, 05:02

Thanks for the info. Diversity is good, and of course use what works for you

.

@step - your error looks like a misconfiguration in wpa_supplicant.conf. This should not happen unless you edit the file manually.

@stemsee: where's the link to Wifi-Connect?
Also, "wpagui only recognises one wifi interface." - this needs to be corrected. You can have it manage multiple wifi cards. It's an unusual configuration and is not supported out of the box, but it can be done (very easily). In fact what you change is how you start wpa_supplicant. There is no change on how you run wpa_gui.

drunkjedi · #267 Post by **drunkjedi** » Fri 17 Feb 2017, 16:39

Hi Jamesbond,
How did you make that gif screencapture?

I used our Screencaster app to make avi, then used ffmpeg to make gif.
I didn't use any options, so the resulting gif was of poor quality and high on size.

Please share your method.

belham2 · #268 Post by **belham2** » Fri 17 Feb 2017, 17:13

drunkjedi wrote:Hi Jamesbond,
How did you make that gif screencapture?

I used our Screencaster app to make avi, then used ffmpeg to make gif.
I didn't use any options, so the resulting gif was of poor quality and high on size.

Please share your method.

Haha, I am glad somebody asked, because ever since he posted it, I've been staring and wondering how in heck he did that. I didn't know if it was proper manners/form to bug one of our leaders with such trivia. But Drunkjedi is Nobility, fears no God nor mortal men, so thus my slaver-skin will soon have an answer to "how did he do dat?". Gracias Drunkjedi!!

jamesbond · #269 Post by **jamesbond** » Sat 18 Feb 2017, 09:38

Haha, no worries at all.

Actually I do that exactly like what drunkjedi said.

I used screencaster, and selected the screen area I want to capture. Then I set capture quality to high --- this is important, high quality capture means lesser artefacts, and lesser artefacts means better GIF compression. If the default "high-quality" setting is not enough (you capture a larger area), go to custom quality setting and increase the video bit rate. And capture with mp4 - it has **much** better quality than AVI for the same bit rate.

Then I just use ffmpeg to convert it to gif: "ffmpeg -i video.mp4 output.gif". The final GIF quality isn't great, but the file size is small (good for forum upload). If the file size is still too big, you can scale the image by using ffmpeg option "-vf scale:200:-1" (set horz resolution to 200 pixels wide, with aspect ratio preserved for vert resolution; change 200 to whatever value you like).

There are options to produce a much better GIF quality by doing two-pass convesion (look here), but it increases the file size between 2-5 times in my test (definitely bigger than the mp4 video you get from screencaster).

This, scripted, may be an idea I can contribute for the next release of puppylinux newsletter that has been recently launched.

stemsee · #270 Post by **stemsee** » Sat 18 Feb 2017, 14:32

@Jamesbond

How to start wpa_supplicant so that any wifi interfaces connected can be selected?

What is your work-around for setting portuguese keyboard?

Here is Wifi-Connect-beta.sfs. First use of Wifi-HotSpot requires devx loaded, for compiling and installing create_ap AP creation tool.

https://drive.google.com/file/d/0B8-coZ ... FprRVhUOWM

step · #271 Post by **step** » Sat 18 Feb 2017, 14:39

@jamesbond, I misconfigured wpa_supplicant on purpose, just to show an example I could capture for my post.

jamesbond · #272 Post by **jamesbond** » Sat 18 Feb 2017, 15:37

@step - yes, of course.

@stemsee: Thank you stemsee.

To run wpa_supplicant so it can support multiple wifi interface, do it like this:
wpa_supplicant -i wlan0 -c/etc/wpa_supplicant.conf -N -i wlan1 -c/etc/wpa_supplicant1.conf -N -i wlan2 -c/etc/wpa_supplicant2.conf ... ad nauseam.

wpa_supplicant.conf, wpa_supplicant1.conf, wpa_supplicant2.conf etc can be the same file if you wish (which is what I did for my example).

Fatdog uses wpa_supplicant (for obvious reasons), wpa_cli (for automatic IP address setting) and wpa_gui. To support multiple interfaces, wpa_gui does not need to change; wpa_supplicant needs to be modified as above; and wpa_cli needs to be run multiple times, one for every interface.

EDIT: the "pt" workaround is to run setxkbmap -query as soon after running setxkbmap.

L18L · #273 Post by **L18L** » Sat 18 Feb 2017, 19:05

Never got any new puppy or fatdog or quirky run on my computer before.

Archlinux gave me a solution.

No xorg driver modesetting needed
Only disadvantage: resolution cannot be changed without reboot.

Other operation systems which I could get running are slacko64 and remixOS (matter of kernel configuration).

drunkjedi · #274 Post by **drunkjedi** » Sun 19 Feb 2017, 03:54

Thanks James for the Gif screencapture help.

step · #275 Post by **step** » Sun 19 Feb 2017, 15:16

Hi L18L, good t o se e you in the forum! Your post reminded me of the only computer I ever owned with poulsbo graphics. It was a Dell netbook. It worked very well with Windows XP but behind that, Windows 7 or Linux regardless, getting decent graphics output was a nightmare. I got rid of that computer. Glad you got yours tamed.

L18L wrote:Never got any new puppy or fatdog or quirky run on my computer before.

Archlinux gave me a solution.

No xorg driver modesetting needed
Only disadvantage: resolution cannot be changed without reboot.

Other operation systems which I could get running are slacko64 and remixOS (matter of kernel configuration).

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

Fatdog64-710 Final [4 Dec 2016]

solution for poulsbo graphics

Re: solution for poulsbo graphics