Page 31 of 37

Linux 3.4.17-PAE(i686 version)

Posted: Wed 21 Nov 2012, 19:51
by Jim1911
Testing the Linux 3.4.17-PAE(i686 version) and except for some minor problems everything appears to be working great. :D I did update the ppm before installing any programs.

1. Bibletime did not work because the ppm installation could not find libclucene.so.0. Bibletime worked fine after installing libclucene.so.0 and it’s link libclucene.so.0.0.0 to /usr/lib.

2. I’ve not been able to install the nvidia driver because I can’t find the kernel source file.

Kudos for your best Slacko to date, :D
Jim

Posted: Thu 22 Nov 2012, 18:36
by Jades
Tested non-PAE Opera Slacko 5.3.7.7 on one of work's old Dell Optiplex GX270s. Pentium 4, 2.1GHz (IIRC) and 1GB of RAM. Tried to create a save file on the machine's NTFS-formatted hard drive, rebooted and encountered the same missing icons and config problem as I see on the Pentium D at home.

Speaking of the Pentium D, the Netgear WN111v2 is definitely having the same dropout problems as before. Nothing obvious in dmesg but I'll post the output later today. I've attached a screengrab of the desktop during attempting to download Firefox. It took around 10 minutes for the system to notice the connection had gone.

Tried installing Firefox from Updates Manager. It's claiming that it's already installed (it isn't) and once it's finished it doesn't create a menu item, although I can run it from the console.

Posted: Thu 22 Nov 2012, 20:07
by zigbert
Updated pFind and pFilesearch - Bugfixing only

Posted: Fri 23 Nov 2012, 01:47
by Jades
As promised, please find attached my dmesg report from a lengthy session of internet use of non-PAE Slacko 5.3.7.7 on the Pentium D machine, connecting using the Netgear WN111v2 wireless dongle. Activity consisted mainly of general surfing and downloading the Libre Office SFS. I had to go into Network Wizard and reload the wireless config and enter the Static IP addresses at regular intervals due to the connection stalling.

Other than the wireless and save problems I've encountered, 5.3.7.7 has been very promising and I hope that the issues can be resolved.

Posted: Fri 23 Nov 2012, 12:14
by CatDude
Hello Mick

Thought i'd post a pic of Slacko-5377 in wobble mode.
It seems to be working OK mate, nice one. :)

Image

CatDude
.

Posted: Sat 24 Nov 2012, 12:14
by 01micko
----------------------------------------------------------------------------------------------

problem solved thanks to rcrsn51

See discussion further down page. This bug would likely affect many puppy versions.

----------------------------------------------------------------------------------------------
Jades wrote:Tested non-PAE Opera Slacko 5.3.7.7 on one of work's old Dell Optiplex GX270s. Pentium 4, 2.1GHz (IIRC) and 1GB of RAM. Tried to create a save file on the machine's NTFS-formatted hard drive, rebooted and encountered the same missing icons and config problem as I see on the Pentium D at home.
Bingo! Found the bug, but need to find an elegant fix... :shock:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Ok, some more on this situation and maybe some of our more knowledgable can lend a hand....

THIS line in /etc/rc.d/rc.shutdown is causing the issue..@line 225

Code: Select all

umount -a -t cifs,smbfs,nfs,sshfs #120220
Why on earth would that umount ntfs? IDK, but it does. Perhaps a bug in the ntfs-3g driver.

Now, if I had my network connected and some network filesystem mounted (didn't seem to matter which) then no bug, all good, save to ntfs is fine. Probably why I never saw the bug. So I got sick of connecting and didn't and could reproduce the bug on my old laptop. IDK if the speed of the machine made any difference. NOTE the date of the change (2012-Feb-20). Slacko-533 would have had the bug but previous versions not. Comment that line and no bug.

So, the question to you who are smarter coders is.. how do we ensure clean unmount of network type filesystems without compromising ntfs?

Here's the code with preceding comments..

Code: Select all

##111107 ldolse: unmount network shares before taking down the network
##(see 111106, need to do it sooner, but 111106 will remount read-only if failed to umount here)
#for MOUNTPOINT in `mount | grep '^//' | cut -d  ' ' -f 3 | tr '\n' ' '`
#do
# umount -f $MOUNTPOINT
#done 
##120219 hmmm, zekebaby reports above does not work for him. i looked up an ex: mount -t nfs boffo.clowns.org:/home/bozo /mnt/bozo
##so this is zekebaby's patch: (see http://murga-linux.com/puppy/viewtopic.php?p=605451#605451)
#for MOUNTPOINT in `mount | grep ':' | cut -d  ' ' -f 3 | tr '\n' ' '`
#do
#  umount -f $MOUNTPOINT
#done
umount -a -t cifs,smbfs,nfs,sshfs #120220
Is zekebaby's patch better? (probably what I'll go with if no better solution is brought forward).

I'd be interested to know if the same fails on other pups. TBH, I reckon saving to ntfs is a bad idea, but it's supported in woof so that's the way it is. Interestingly, it doesn't fail if you use noryb009's windows installer (there is one for 533).

NOTE: there seem to be a lot of potential bugs in rc.shutdown. We see it all the time ..."My pupppy won't shut down!" . There is one particular block of code that brings down the network interface before releasing the the IP lease. Well, that isn't the problem here but it could be affecting someone.

I'll attach, just for interest's sake, my crazy debugging routines added to the relevant files.. most commented with "Jades debug". :lol:

Guess I'm having fun eh? :lol:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -


Here's my crazy log..

Code: Select all

START DEBUG
/dev/sda2 /mnt/sda2 fuseblk rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096 0 0
PUPMODE=128
SAVEPART='sda2'
SAVEFS='ntfs'
PUPSAVE='sda2,ntfs,/slackosave-yes.2fs'
SAVEFILE='/slackosave-yes.2fs'
NAMEONLY='slackosave-yes.2fs'
SAVEPATH='/'
MYPASSWORD=''
SFEXT='2fs'
xPDEV='sr0'
xDEVFS='iso9660'
SMNTPT='/mnt/sda2'
CRYPTO=''
expBOOTDRV=''
save path = /mnt/sda2
Executing /etc/rc.d/rc.shutdown...
PUPMODE is 5
Killing X and all X apps...
Check breakage 1
AH HA! There's the bastard
Check breakage 2
The 5 is pupmode
CHECKPOINT 1: Check if ntfs is mounted rw
/dev/sda2 /mnt/sda2 fuseblk rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096 0 0
CHECKPOINT 2: Check if variables file exists
PUPMODE=128
SAVEPART='sda2'
SAVEFS='ntfs'
PUPSAVE='sda2,ntfs,/slackosave-yes.2fs'
SAVEFILE='/slackosave-yes.2fs'
NAMEONLY='slackosave-yes.2fs'
SAVEPATH='/'
MYPASSWORD=''
SFEXT='2fs'
xPDEV='sr0'
xDEVFS='iso9660'
SMNTPT='/mnt/sda2'
CRYPTO=''
expBOOTDRV=''
DEBUG log: 

Saving session to /slackosave-yes.2fs file on sda2 partition...
/proc/mounts BEFORE mounting /slackosave-yes.2fs
rootfs / rootfs rw,relatime 0 0
tmpfs /initrd/pup_rw tmpfs rw,relatime,size=665840k 0 0
tmpfs /initrd/mnt/tmpfs tmpfs rw,relatime,size=154692k 0 0
/dev/loop0 /initrd/pup_ro2 squashfs ro,noatime 0 0
unionfs / aufs rw,relatime,si=54be455e 0 0
none /proc proc rw,relatime 0 0
none /dev/pts devpts rw,relatime,gid=2,mode=620 0 0
none /sys sysfs rw,relatime 0 0
shmfs /dev/shm tmpfs rw,relatime,size=86552k 0 0
none /proc/bus/usb usbfs rw,relatime 0 0
/dev/sda2 /mnt/sda2 fuseblk rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096 0 0
PUPMODE=128
SAVEPART='sda2'
SAVEFS='ntfs'
PUPSAVE='sda2,ntfs,/slackosave-yes.2fs'
SAVEFILE='/slackosave-yes.2fs'
NAMEONLY='slackosave-yes.2fs'
SAVEPATH='/'
MYPASSWORD=''
SFEXT='2fs'
xPDEV='sr0'
xDEVFS='iso9660'
SMNTPT='/mnt/sda2'
CRYPTO=''
expBOOTDRV=''
Mounting /slackosave-yes.2fs...
added sleep 1 (clutching straws)
checking what got mounted, hopefully /mnt/sda2/slackosave-yes.2fs
/proc/mounts AFTER (attempting) mounting /slackosave-yes.2fs
rootfs / rootfs rw,relatime 0 0
tmpfs /initrd/pup_rw tmpfs rw,relatime,size=665840k 0 0
tmpfs /initrd/mnt/tmpfs tmpfs rw,relatime,size=154692k 0 0
/dev/loop0 /initrd/pup_ro2 squashfs ro,noatime 0 0
unionfs / aufs rw,relatime,si=54be455e 0 0
none /proc proc rw,relatime 0 0
none /dev/pts devpts rw,relatime,gid=2,mode=620 0 0
none /sys sysfs rw,relatime 0 0
shmfs /dev/shm tmpfs rw,relatime,size=86552k 0 0
none /proc/bus/usb usbfs rw,relatime 0 0
/dev/sda2 /mnt/sda2 fuseblk rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096 0 0
/dev/loop1 /tmp/save1stpup ext2 rw,noatime,errors=continue,user_xattr,acl 0 0
RDIRS=/initrd/pup_rw/root /initrd/pup_rw/var /initrd/pup_rw/usr /initrd/pup_rw/initrd /initrd/pup_rw/etc /initrd/pup_rw/lib

END DEBUG


Posted: Sat 24 Nov 2012, 13:01
by zigbert
pMusic 3.0.1

Posted: Sat 24 Nov 2012, 13:16
by 01micko
zigbert wrote:pMusic 3.0.1
Ah.. the pieces are coming together :)

Thank you!

Posted: Sat 24 Nov 2012, 13:39
by pemasu
http://bkhome.org/blog/?viewDetailed=02697

Check shinobar`s solution, would it help:

Code: Select all

#120203 pemasu and shinobar: space in smb or cifs share causes hanging in shutdown
for T in cifs smbfs nfs sshfs; do
  umount -a -t $T
done

Posted: Sat 24 Nov 2012, 20:50
by rcrsn51
01micko wrote:THIS line in /etc/rc.d/rc.shutdown is causing the issue..@line 225

Code: Select all

umount -a -t cifs,smbfs,nfs,sshfs #120220
Change this to "umount-FULL". In my tests with an NTFS-formatted flash drive, it solved the problem.

BTW, this problem with "umount -a -t cifs" conflicting with NTFS goes back at least as far as Quirky. It doesn't affect other filesystems.

Posted: Sat 24 Nov 2012, 20:57
by 01micko
pemasu wrote:http://bkhome.org/blog/?viewDetailed=02697

Check shinobar`s solution, would it help:

Code: Select all

#120203 pemasu and shinobar: space in smb or cifs share causes hanging in shutdown
for T in cifs smbfs nfs sshfs; do
  umount -a -t $T
done
NO, failure again, thanks anyway. It did occur to me that it's only a problem in PUPMODE=5. A test of that condition seems to fix it, however I don't know if this could bork future saves if someone tricks the system into thinking it's PUPMODE=13 when it's actually PUPMODE=12
rcrsn51 wrote:Change this to "umount-FULL". In my tests with an NTFS-formatted flash drive, it solved the problem.

BTW, this problem with "umount -a -t cifs" conflicting with NTFS goes back at least as far as Quirky. It doesn't affect other filesystems.
Yes, will try that right now. Report back in a few minutes.

Posted: Sat 24 Nov 2012, 21:05
by don570
I noticed that you included the excellent Caps plugins for LADSPA effects

/usr/lib/ladspa/

...but you need a version of mhwaveedit that will load ladspa plugins

I made one here.

__________________________________________________

Posted: Sat 24 Nov 2012, 21:10
by 01micko
don570 wrote:I noticed that you included the excellent Caps plugins for LADSPA effects

/usr/lib/ladspa/

...but you need a version of mhwaveedit that will load ladspa plugins

I made one here.

__________________________________________________
At this late stage I won't include your mhwaveedit but I will put it in the repo.

----------------------------------------------------------------------------


umount-FULL works and is a "proper" solution. I didn't give ntfs usb sticks a thought :oops: . Problem solved.

Thank you rcrsn51

Posted: Sat 24 Nov 2012, 21:16
by rcrsn51
Excellent. The problem with the "umount" script is easy to demonstate.

1. Mount the NTFS partition sdxy.

2. Run "umount -a -t cifs"

3. Run "ls /mnt/sdxy"

The NTSF partition has gotten unmounted. However, the drive icon on the desktop still shows it as mounted!

Posted: Sat 24 Nov 2012, 21:34
by pemasu
Bug fix to be carried to the woof ?

Posted: Sat 24 Nov 2012, 21:53
by 01micko
pemasu wrote:Bug fix to be carried to the woof ?
Hopefully!

Attached is what I'll be putting in Slacko-5.4 rc2. I have moved the call down to allow for responsible service scripts. (ie YASSM, network_roxapp)

Posted: Sat 24 Nov 2012, 22:54
by rcrsn51
Here was my test procedure.

1. Booted off the Live CD. It found the sfs on the hard drive.

2. Selected all the defaults and immediately made a save file on an NTFS flash drive. There WAS a network connection, so I don't know how that's significant.

3. Rebooted. The save file was detected, followed by a kernel panic!

4. Repeated using "umount-FULL". No problems.

Posted: Sat 24 Nov 2012, 23:10
by 01micko
rcrsn51 wrote:Here was my test procedure.

1. Booted off the Live CD. It found the sfs on the hard drive.

2. Selected all the defaults and immediately made a save file on an NTFS flash drive. There WAS a network connection, so I don't know how that's significant.

3. Rebooted. The save file was detected, followed by a kernel panic!

4. Repeated using "umount-FULL". No problems.
So looks like the fix is good then..

BTW, we got a prompt woof fix :)

Posted: Sat 24 Nov 2012, 23:37
by rcrsn51
I repeated the procedure with both Wary 5.3 and Slacko 533 and got identical results. If I opened the bad save file from another Puppy, it was empty.

It's odd that when the save file is on an NTFS hard drive partition, it sometimes works.

Posted: Sun 25 Nov 2012, 00:59
by 01micko
rcrsn51 wrote:It's odd that when the save file is on an NTFS hard drive partition, it sometimes works.
My best explanation for this behaviour is that the buggy busybox umount isn't happy until it's found something it can unmount.

For example; more often than not if I'm testing on one of my other machines I'll connect with curl ftp to my main machine to get quick access to files I have edited and such. I was doing this testing shutdown scripts and wasn't getting the bug. So my best explanation for that was that busybox umount was unmounting the curlftpfs and then it was happy. I guess curlftpfs should be one of the umount arguments. I could reproduce the bug 100% of the time when I didn't connect. Took me awhile to figure that one out!

Still, that doesn't explain why it would sometimes work if you had a connection but definitely didn't mount anything over the network. Just a buggy busybox applet I guess.