Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Tue 16 Jan 2018, 11:52
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Derivatives
EasyOS Pyro64 0.6.6, Xerus64 0.6.8, released Jan. 2/4, 2018
Moderators: Flash, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 28 of 28 [420 Posts]   Goto page: Previous 1, 2, 3, ..., 26, 27, 28
Author Message
Billtoo


Joined: 07 Apr 2009
Posts: 3330
Location: Ontario Canada

PostPosted: Sun 07 Jan 2018, 20:22    Post subject:  

Sage wrote:
Quote:
I connect to the wired network with Frisbee

Thanks for that comment, Bill. I have never, ever managed to connect with Frisbee on legions of systems since it was first announced. Apart from being unnecessarily complicated, I wonder whether it has something to do with UK being on PoA rather than PoE like RoW? Ignorance usually wins out in my case, though. IMHO these compact distro need to be (small!), fast, simple, universal and foolproof! Failing on any aspect is failure, surely?! Chasing apps that major releases do well misses the point.


Hi Sage,

I'll attach the Frisbee setup screen, when finished setting up save and reboot.
frisbeesetup.jpg
 Description   
 Filesize   82.41 KB
 Viewed   975 Time(s)

frisbeesetup.jpg

Back to top
View user's profile Send private message 
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 8403
Location: Perth, Western Australia

PostPosted: Sun 07 Jan 2018, 20:27    Post subject:  

don570 wrote:
3) To my surprise Samba server went smoothly.
I ticked off all the options except printer and didn't choose advanced.
Also I didn't even set up a samba user i.e. no smbpasswd -a was used.
My other computer saw the server, no problem. Cool


Good.

Regarding 0.6.6, I have just been through the exercise. Created two pristine 0.6.6 usb sticks, booted them on my two desktop machines, that are connected via ethernet router.

First bootup,

PC#1
1. quicksetup: chose "Australia/Perth" timezone, clicked "OK"
2. clicked "share" button
3. clicked button to run firewall, ticked the two samba checkboxes
4. clicked button to run samba setup
5. clicked "samba off" button to start daemon
6. typed in a new password, clicked "Apply" button, then "Quit"

PC#2
1 - 5. as above
6. left password as "woofwoof", clicked "Quit" button.

QuickSamba showed the remote shares as available. PC#1 and PC#2 both saw each others shared folders. Just had to click "mount shares" button and enter username and password, voila, it works.

In other words, it works perfactly.

0.6.8, as I mentioned, has a bug with smbnetfs, the DEB is not setup properly. That will be fixed in next release.
But, the broken smbnetfs is only for detecting and mounting remote shares -- in your case, the remote computer is able to see the local shared folder, smbnetfs is not used.

_________________
http://barryk.org/news/
Back to top
View user's profile Send private message Visit poster's website 
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 8403
Location: Perth, Western Australia

PostPosted: Sun 07 Jan 2018, 20:51    Post subject: Re: Networking fix-candidate for slow PCs
Subject description: For Easy (& quirky?) SNS and default ethernet interface
 

rerwin wrote:
Barry,
With recent Puppies and Easy, I have encountered issues with the detection and connection of wired and wireless network interfaces. I have been working on solutions for the puppies and have now developed changes to rc.network_eth and the SNS rc.network for Easy and (probably) related distros. Running Easy Xerus64 0.6.8 from a USB flash drive, the following fixes work on my old 2008-BIOS Compaq Presario SR5413WM with a 64-bit AMD uniprocessor. I provide them here for your consideration.

The main problem is the slow starting of the network devices during boot-up, which necessitates increasing loop counts to wait up to 20 seconds, mainly for driver loading. My PC needs 12-18 seconds I have seen cases with both Easy and Xenialpup where dhcpcd does not appear to change resolv.conf (judging from the "MODTIME" values) even though a connection can be made if resolv.conf contains nameserver data (by ignoring the MODTIME test); clearing resolv.conf during initialization (in network_default_connect) and changing the MODTIME comparison logic seems to handle that special case.

Although I have yet to see an instance (with the change) of the MODTIME not changing, that might be because clearing of the resolv.conf content could force an initial update.

Also, adding a timeout value for dhcpcd seems to improve chances of success in connecting -- I assume that delays the return from dhcpcd, allowing more time for the resolv.conf update.

I also found that rc.network_eth does not find the wired ethernet device because it is a "bridge" ([0680]) instead of a controller ([0200]); I add a check for the bridge as long as it has "Ethernet" in its name (from lspci -nn).

Attached are difference listings and the updated scripts, as well as a hardware summary of my PC. The tarball should probably be extracted to /tmp or "home". For anyone desiring to test with the scripts, they should be installed as follows:
    network_default_connect ==> /usr/sbin
    rc.network ==> /usr/local/simple_network_setup
    rc.network_eth ==> /etc/rc.d
Richard


richard,
Yeah, I was gobsmacked at how slow it has become.

_________________
http://barryk.org/news/
Back to top
View user's profile Send private message Visit poster's website 
mmmrr


Joined: 03 Mar 2009
Posts: 174
Location: vancouver island, canada

PostPosted: Mon 08 Jan 2018, 03:25    Post subject:  

wow the xerus is fast, good learning curve and elegant.
elegant. sensible,
using the background colour to identify
which terminal was doing what. lovely colours. this is the
current champion, the keeper. thanks v much mr b. there
a lot of happy people in albania, tonight.

i'm going to shut down up the ram from 2gb to4gb
cheers, mm
Back to top
View user's profile Send private message 
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 8403
Location: Perth, Western Australia

PostPosted: Mon 08 Jan 2018, 05:26    Post subject: Re: Networking fix-candidate for slow PCs
Subject description: For Easy (& quirky?) SNS and default ethernet interface
 

rerwin wrote:
The main problem is the slow starting of the network devices during boot-up, which necessitates increasing loop counts to wait up to 20 seconds, mainly for driver loading. My PC needs 12-18 seconds I have seen cases with both Easy and Xenialpup where dhcpcd does not appear to change resolv.conf (judging from the "MODTIME" values) even though a connection can be made if resolv.conf contains nameserver data (by ignoring the MODTIME test); clearing resolv.conf during initialization (in network_default_connect) and changing the MODTIME comparison logic seems to handle that special case.

Although I have yet to see an instance (with the change) of the MODTIME not changing, that might be because clearing of the resolv.conf content could force an initial update.

Also, adding a timeout value for dhcpcd seems to improve chances of success in connecting -- I assume that delays the return from dhcpcd, allowing more time for the resolv.conf update.


rerwin,
The default timeout for dhcpcd is 30 seconds, so putting "-t 20" is making it shorter.

But, there is something very odd happening in dhcpcd.

I am trying to get away from putting sleeps in all over the place. Toward, that end, I have changed this code in rc.network_eth:

Code:
 DHCPCDFIX="-I ''"
 
 #180108 use inotifywait to query resolv.conf...
 inotifywait -t 30 -q -e modify /etc/resolv.conf & #weird, -d (daemonize) does not work)
 inPID="$!"
 dhcpcd $DHCPCDFIX $INTERFACE
 wait $inPID
 
 if grep '^nameserver' /etc/resolv.conf >/dev/null; then
  echo "$INTERFACE" > /tmp/sns_interface_success
  exit #success.
 else
  ifconfig $INTERFACE down
  dhcpcd --release $INTERFACE 2>/dev/null
  ip route flush dev $INTERFACE
 fi


...very odd, but the "-d" option of inotifywait does not work.

This code works ok for me. Overkill?

_________________
http://barryk.org/news/
Back to top
View user's profile Send private message Visit poster's website 
Sage

Joined: 04 Oct 2005
Posts: 5336
Location: GB

PostPosted: Mon 08 Jan 2018, 09:58    Post subject:  

Glad to know I'm not alone re. Frisbee! [mmmrr]
Quote:
internet connection wizard
- do you mean SNS/Dougal's utility? Served me well if the developer has done his bit on NIC drivers (notably not the case for the ubiquitous RTL8201CL/SiS900, recently!)
Back to top
View user's profile Send private message 
mmmrr


Joined: 03 Mar 2009
Posts: 174
Location: vancouver island, canada

PostPosted: Mon 08 Jan 2018, 13:44    Post subject: RAM TEST CLAIMS ONE CASUALTY, oops  

i mean the connection tool at the bottom of the list.
below dougal's/sns.

right click on connect icon,
click 'execute Internet Connection Wizard'
page with list appears.

internet connection took 2 slow tries to establish,
sluggish while on internet

connection settings not saved on shutdown
personal desktop mods are saved.

switching back to 2gb machine to check
by luck i have 2 lenovox61 computers,
one has 4gb ram, the other 2gb

this 4gb box booted from cold in about 10 seconds.

cheers, mm

edit 1

same usb key holding easy xerus 0.6.8

running alternately on 4gb and 2gb same models

to observe any differences of operation

on the 2gb machine, wireless settings were remembered
between boots.
on the 4gb machine the wireless settings were never remembered

so i swapped the 4gb of memory into the 2gb machine
which was running better than the 4gb machine.

when i put the 2gb into the slots on the former 4gb machine
there was a faint click. ...i forgot to wipe any static charge off the ram sticks??

i thought 'oh oh'.. all dead so far with that machine pending further
testing. been so busy with the extra 2 gbs on this machine

edit 2.

after an overnight rest and 2 known-working sticks of ram
the machine that died came back to life without breaking stride.

it was the machine that booted xerus first that had the wireless settings saved across boots. the machine that booted second had go through internet connection hoop every time.

Last edited by mmmrr on Tue 09 Jan 2018, 23:58; edited 2 times in total
Back to top
View user's profile Send private message 
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 8403
Location: Perth, Western Australia

PostPosted: Mon 08 Jan 2018, 19:40    Post subject: Re: Networking fix-candidate for slow PCs
Subject description: For Easy (& quirky?) SNS and default ethernet interface
 

BarryK wrote:
But, there is something very odd happening in dhcpcd.

I am trying to get away from putting sleeps in all over the place. Toward, that end, I have changed this code in rc.network_eth:

Code:
 DHCPCDFIX="-I ''"
 
 #180108 use inotifywait to query resolv.conf...
 inotifywait -t 30 -q -e modify /etc/resolv.conf & #weird, -d (daemonize) does not work)
 inPID="$!"
 dhcpcd $DHCPCDFIX $INTERFACE
 wait $inPID
 
 if grep '^nameserver' /etc/resolv.conf >/dev/null; then
  echo "$INTERFACE" > /tmp/sns_interface_success
  exit #success.
 else
  ifconfig $INTERFACE down
  dhcpcd --release $INTERFACE 2>/dev/null
  ip route flush dev $INTERFACE
 fi


...very odd, but the "-d" option of inotifywait does not work.

This code works ok for me. Overkill?


Can't say that I am happy with this code.

dhcpcd is supposed to write to /etc/resolv.conf before exiting, but I found had to put a "sleep 0.1" in the script immediately after dhcpcd returned.

How could this problem happen? Maybe if dhcpcd writes to /etc/resolv.conf as a separate process, and exits before that process has finished.

Anyway, I think inotifywait is overkill. Might just go back to "sleep 0.1".

EDIT
I have posted a question to the dhcpcd mail-list:

https://roy.marples.name/archives/dhcpcd-discuss/0001913.html

_________________
http://barryk.org/news/
Back to top
View user's profile Send private message Visit poster's website 
mmmrr


Joined: 03 Mar 2009
Posts: 174
Location: vancouver island, canada

PostPosted: Wed 10 Jan 2018, 03:14    Post subject:  

after a few hours rest and a better ram 2gb, that machine came back to life
without breaking stride.

see edits in previous post.
Back to top
View user's profile Send private message 
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 8403
Location: Perth, Western Australia

PostPosted: Wed 10 Jan 2018, 06:29    Post subject: Re: Networking fix-candidate for slow PCs
Subject description: For Easy (& quirky?) SNS and default ethernet interface
 

BarryK wrote:
BarryK wrote:
But, there is something very odd happening in dhcpcd.

I am trying to get away from putting sleeps in all over the place. Toward, that end, I have changed this code in rc.network_eth:

Code:
 DHCPCDFIX="-I ''"
 
 #180108 use inotifywait to query resolv.conf...
 inotifywait -t 30 -q -e modify /etc/resolv.conf & #weird, -d (daemonize) does not work)
 inPID="$!"
 dhcpcd $DHCPCDFIX $INTERFACE
 wait $inPID
 
 if grep '^nameserver' /etc/resolv.conf >/dev/null; then
  echo "$INTERFACE" > /tmp/sns_interface_success
  exit #success.
 else
  ifconfig $INTERFACE down
  dhcpcd --release $INTERFACE 2>/dev/null
  ip route flush dev $INTERFACE
 fi


...very odd, but the "-d" option of inotifywait does not work.

This code works ok for me. Overkill?


Can't say that I am happy with this code.

dhcpcd is supposed to write to /etc/resolv.conf before exiting, but I found had to put a "sleep 0.1" in the script immediately after dhcpcd returned.

How could this problem happen? Maybe if dhcpcd writes to /etc/resolv.conf as a separate process, and exits before that process has finished.

Anyway, I think inotifywait is overkill. Might just go back to "sleep 0.1".

EDIT
I have posted a question to the dhcpcd mail-list:

https://roy.marples.name/archives/dhcpcd-discuss/0001913.html


Have gone back to simple code, works for me:

Code:
 DHCPCDFIX="-I ''"
 dhcpcd $DHCPCDFIX $INTERFACE
 sleep 0.1 #180110
 if grep '^nameserver' /etc/resolv.conf >/dev/null; then #180108

_________________
http://barryk.org/news/
Back to top
View user's profile Send private message Visit poster's website 
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 8403
Location: Perth, Western Australia

PostPosted: Thu 11 Jan 2018, 18:54    Post subject:  

I am planning to rename QuickSamba to EasyShare, and incorporate setup of network printing with CUPS.

I have figured out a simple way to print over a local network with CUPS:

http://bkhome.org/news/201801/easy-network-printing-with-cups.html

_________________
http://barryk.org/news/
Back to top
View user's profile Send private message Visit poster's website 
foxpup


Joined: 29 Jul 2016
Posts: 311
Location: europa near northsea

PostPosted: Fri 12 Jan 2018, 06:10    Post subject: freeze
Subject description: stop on prompt before going to X
 

I installed easy0.6.8 on my dualcore desktop.
I can boot it with vesa or modesetting, but I have to stop on the prompt first (qfix=nox) and then go to X (xwin). If try to boot straight into X I get a screen with multiple desktops, teard and in a row, and the computer freezes.
This desktop has nvidia graphics. I did not know if 0.6.8 still needs the fix for nvidia cards, but I tried the fix with the xorgwizard_cli, but that does not help.
Back to top
View user's profile Send private message 
Billtoo


Joined: 07 Apr 2009
Posts: 3330
Location: Ontario Canada

PostPosted: Sun 14 Jan 2018, 11:59    Post subject: EasyOS Pyro64 0.6.6, Xerus64 0.6.8, released Jan. 2/4, 2018  

I installed to the hard drive of my Lenovo ThinkCentre desktop pc:

video-info-glx 1.5.3 Sun 14 Jan 2018 on Easy OS 0.6.8 Linux 4.14.11 x86_64
0.0 VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 430] (rev a1)
oem: NVIDIA
product: GF108 Board - 1071v0p1 Chip Rev

X Server: Xorg Driver: nvidia
X.Org version: 1.18.4
dimensions: 1920x1080 pixels (707x392 millimeters)
depth of root window: 24 planes

direct rendering: Yes
server glx vendor string: NVIDIA Corporation
server glx version string: 1.4
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GT 430/PCIe/SSE2
OpenGL core profile version string: 4.5.0 NVIDIA 384.111

Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
Core 0: @2003 1: @2003 MHz

I installed applications with PPM,also installed the proprietary nvidia
driver.

CPU~Dual core Intel Core2 Duo E8400 (-MCP-) speed/max~2003/3003 MHz
Kernel~4.14.11 x86_64 Up~2:03 Mem~640.4/3955.1MB HDD~446.4GB(0.5% used)
Procs~104 Client~Shell inxi~2.2.35

*******************************************************************

EDIT:looks like this is safe from meltdown.
screenshot2.jpg
 Description   
 Filesize   98.68 KB
 Viewed   156 Time(s)

screenshot2.jpg

screenshot.jpg
 Description   
 Filesize   110.05 KB
 Viewed   206 Time(s)

screenshot.jpg

Back to top
View user's profile Send private message 
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 8403
Location: Perth, Western Australia

PostPosted: Today, at 05:37    Post subject: Re: freeze
Subject description: stop on prompt before going to X
 

foxpup wrote:
I installed easy0.6.8 on my dualcore desktop.
I can boot it with vesa or modesetting, but I have to stop on the prompt first (qfix=nox) and then go to X (xwin). If try to boot straight into X I get a screen with multiple desktops, teard and in a row, and the computer freezes.
This desktop has nvidia graphics. I did not know if 0.6.8 still needs the fix for nvidia cards, but I tried the fix with the xorgwizard_cli, but that does not help.


Did you try 0.6.6 on that PC?

It has different video software.

_________________
http://barryk.org/news/
Back to top
View user's profile Send private message Visit poster's website 
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 8403
Location: Perth, Western Australia

PostPosted: Today, at 05:41    Post subject:  

For anyone who is interested, QuickSamba is replaced by EasyShare.

EasyShare will be in EasyOS 0.7, hopefully a few days away, but if you want to find out more about it now, read this:

http://bkhome.org/easyshare/easyshare-super-easy-network-file-and-printer-sharing.html

_________________
http://barryk.org/news/
Back to top
View user's profile Send private message Visit poster's website 
Display posts from previous:   Sort by:   
Page 28 of 28 [420 Posts]   Goto page: Previous 1, 2, 3, ..., 26, 27, 28
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Puppy Derivatives
Jump to:  

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
[ Time: 0.0693s ][ Queries: 15 (0.0060s) ][ GZIP on ]