Page 7 of 13
Posted: Wed 02 Mar 2011, 06:29
by Roy
Created a FRESH save file and loaded ONLY the skype.sfs... Still won't run from menu. Shows 'Segmentation fault' when attempted via CLI.
Downloaded fresh skype.sfs and replaced original. (Original worked with FD64-500) Still nothing from menu. 'Segmentation fault' from CLI.
Posted: Wed 02 Mar 2011, 16:06
by rcrsn51
Here is the printer driver package for the
foo2xxx collection. I have incorporated the firmware-hotplug components from Patriot's 32-bit version. To reduce the size of the package, I have removed all of the ICM colour files.
I don't own any of these printers, so if you test this package, PLEASE provide feedback.
[Edit] Attachment deleted. No feedback provided after 20 downloads.
Why remove the ICMs?
Posted: Thu 03 Mar 2011, 07:06
by gcmartin
rcrsn51 wrote:... To reduce the size of the package, I have removed all of the ICM colour files.
I don't own any of these printers, so if you test this package, PLEASE provide feedback.
@Rcrsn51. Please don't take this the wrong way as I mean no malice. But would you explain to me why you would remove the ICMs in a system which does NOT have memory issues? I know you mean well, but all 64bit PCs running FATDOG even on LiveDVDs do not suffer from the memory issues that you may be referring to
- .
- Which are you trying to address....FS storage on, say, LiveDVD or RAM used when printing?
- Would including the ICMs have been a less risky assistance provided?
Thanks for helping understand.
Posted: Thu 03 Mar 2011, 11:35
by rcrsn51
If I include the ICM's, the PET is too large to be attached here, so it must be hosted externally. If the package is not downloaded regularly, it will eventually disappear.
If and when someone provides some feedback on this driver and actually requests the ICM data, I will deal with the issue.
Would including the ICMs have been a less risky assistance provided?
I don't know what you mean.
Thanks: Helping me understand your approach. I wasn't aware
Posted: Thu 03 Mar 2011, 17:53
by gcmartin
rcrsn51 wrote:If I include the ICM's, the PET is too large to be attached here, so it must be hosted externally. If the package is not downloaded regularly, it will eventually disappear.
If and when someone provides some feedback on this driver and actually requests the ICM data, I will deal with the issue.
Would including the ICMs have been a less risky assistance provided?
I don't know what you mean.
Thanks for your help. I am just beginning to embark on a PET production journey and your explanation allows me to pay attention as I begin moving forward.
That question was to get your insight on the support risks.
That question you highlight put another way is asking this. If you are aware that you are producing something that MAY reduce/impact functionality for the sake of file size, is it worth the down-the-road user impact/support that must be expended for the sake of size? (Size is a relative thing and I realized that it means one thing in Puppy and a completely different thing in FATDOG where manufacturers ship a completely different machine than many Puppy users might have.).
Lastly, different topic
I understand that Printer/Copier manufacturers do NOT always make drivers (PPDs) available for their products in the LInux community, Another question: If I want to provide a PPD from a Manufacture like Lexmark or Canon who make PPDs, how should we present these to this FATDOG community so that instead of my benefiting, others can too?
Thanks in advance
Posted: Thu 03 Mar 2011, 18:30
by rcrsn51
I understand that Printer/Copier manufacturers do NOT always make drivers (PPDs) available for their products in the LInux community,
PPD files are NOT drivers. They are just text configuration files. If you go to a manufacturer's web site and download a Linux printer package, you will see that there is much more to it than just a PPD file.
Fatdog64-511
Posted: Fri 04 Mar 2011, 11:50
by Billtoo
Posted in error.
Posted: Fri 04 Mar 2011, 12:17
by jamesbond
rcrsn51 wrote:I understand that Printer/Copier manufacturers do NOT always make drivers (PPDs) available for their products in the LInux community,
PPD files are NOT drivers. They are just text configuration files. If you go to a manufacturer's web site and download a Linux printer package, you will see that there is much more to it than just a PPD file.
Learnt this the hard way.
Anyway - rcrsn51, please feel free to upload to
http://mydrive.ch account I posted in page 7 of this thread if you have files too large for the forum. I keep them there for a while and will move it to the main repo based on feedback - so everyone who benefits from rcrsn51 work, or has the printers/scanners that work with it - do let me know. Thanks.
I've just uploaded Billtoo's VLC and Fotowall as an SFS (did I say so in earlier post? If yes, nevermind
) and in the process of uploading Jim1911's LibreOffice SFS.
Roy, I encountered some printer error, I'm not sure whether it's the same as the one you got. For my case, it's caused by poor driver code and also permission error on /tmp. The path /tmp should be world-writable ("rwxrwxrwxt") but on Fatdog (as early as 500) is "rwxr-x-r-x" for spot. I'll highlight this to kirk when a new release is near. Meanwhile, you can just open terminal and type "chmod a+rwxt /tmp" and be done with it.
Roy, I just realised that I don't run skype as SFS - I installed it as a pet (because my 6-slot SFS are all fully occupied). I'll test the skype SFS and let you know.
Posted: Fri 04 Mar 2011, 13:33
by rcrsn51
jamesbond wrote: rcrsn51, please feel free to upload to
http://mydrive.ch account I posted in page 7 of this thread if you have files too large for the forum.
Thanks. As usual, it's an effort to get any systematic testing done by the Puppy community.
Roy, I encountered some printer error, I'm not sure whether it's the same as the one you got. For my case, it's caused by poor driver code and also permission error on /tmp. The path /tmp should be world-writable ("rwxrwxrwxt") but on Fatdog (as early as 500) is "rwxr-x-r-x" for spot. I'll highlight this to kirk when a new release is near. Meanwhile, you can just open terminal and type "chmod a+rwxt /tmp" and be done with it.
I checked this in FD510 and the permissions are correct. What printer do you have? I can look at the driver.
Posted: Fri 04 Mar 2011, 14:00
by jamesbond
It's FujiXerox Apeos printer, and it requires a very obscure driver from Fuji's japanese website here:
http://www.fujixerox.co.jp/download/ape ... odule.html. I already has a driver compiled for it (it's in the repo). It used to work fine for me - until I moved to using flash, and suddenly it refused to work.
After puzzling for a while, I found the root cause is the permission problem. Now this is odd - the permission of /tmp in pup.sfs (/initrd/pup_ro2/tmp) is wrong. When I'm running from frugal harddisk, the permission of /tmp in pupsave (/initrd/pup_rw) is wrong - but the permission seen from aufs (/tmp) is right.
When I'm running frugal from flash, there is nothing in /initrd/pup_rw (which is tmpfs), and the permission in /initrd/pup_ro1/tmp (the real save file) is still wrong, and this time however aufs shows the wrong permission. Chmod-ing the /tmp trickles down the permission update to /initrd/pup_ro1/tmp and at next boot, aufs gets it right. So in short, though the permission is wrong, the problem seems to happen only when I'm running off flash (ie when there is a tmpfs layer between the pupsave).
EDIT: I checked /tmp permission on pup.sfs on both FD500 and FD510. Both shows "rwxr-xr-x". Wary 500 shows the correct (I presume) to be "rwxrwxrwxt".
Posted: Fri 04 Mar 2011, 14:26
by jamesbond
jamesbond wrote:Roy, I just realised that I don't run skype as SFS - I installed it as a pet (because my 6-slot SFS are all fully occupied). I'll test the skype SFS and let you know.
Tested this - it didn't crash on me. I tested with and without 32-bit libs, and it worked fine on both occasions. Anyone else having the same problem? Roy if you can post the output of
just after the segfaults, may be there is some useful information there.
Posted: Fri 04 Mar 2011, 15:19
by rcrsn51
Lupu went through this same problem with /tmp having incomplete permissions. In that situation, syslinux wouldn't work. However, once you make a standard PUPMODE=12 installation, it goes away.
Posted: Sat 05 Mar 2011, 03:01
by Roy
jamesbond,
var/log/messages after running # skype in terminal is attached. (511-based Fatdog64 with only Skype.sfs added) It is really NOT a .zip file -- just rename it to log.txt for reading
Skype doesn't crash for me -- it simply refuses to run at all via the .sfs
Thanks for looking at this for me.
-Roy
Posted: Sat 05 Mar 2011, 12:53
by jamesbond
Roy wrote:jamesbond,
var/log/messages after running # skype in terminal is attached. (511-based Fatdog64 with only Skype.sfs added) It is really NOT a .zip file -- just rename it to log.txt for reading
Skype doesn't crash for me -- it simply refuses to run at all via the .sfs
Thanks for looking at this for me.
-Roy
No worries. Unfortunately I'm not sure how I can help you further - the log doesn't say anything, other than "skype segfaults" - but we already know that. (for me, segfaults = crash). I was hoping to see some status or library or indication where the segfault happens, but it doesn't say so
I'm not sure if you have more than 1 fatdog64-capable computers, if you do - does this happen on all of them?
rcrsn51 - yeah, funny how it "fixes" itself when running in PUPMODE=12, but surfaces the problem in PUPMODE=13? Hmmm....
(I only know this because I started using PUPMODE=13 full time since last week).
Posted: Sun 06 Mar 2011, 03:17
by Roy
jamesbond,
thank you for your time and attention. if the skype.pet works.... well, I'll just go with that instead of the .sfs.
again, I appreciate your efforts (and fd64)!
-Roy
Fatdog64-511
Posted: Mon 07 Mar 2011, 13:22
by Billtoo
xfe-1.32.2-x86_64.pet (X File Explorer) is similar to midnight
commander, it needs fox-1.6.43-x86_64.pet installed as well or it
won't run.
Posted: Tue 08 Mar 2011, 01:13
by jamesbond
No worries Roy.
I wish I can make skype works on your machine
I've mirrored all the files in this thread (including the latest xfe pets from Billtoo) in mydrive.ch (details on page 7) as a staging area before moving it to official pet repository at ibiblio.
cheers!
Fatdog64-511
Posted: Tue 08 Mar 2011, 15:54
by Billtoo
lpairs-1.0.4-x86_64.pet is a memory game.
Posted: Tue 08 Mar 2011, 17:39
by rcrsn51
The printer driver package foo2xxx relies on udev to download firmware to the printer. While attempting to get this working, I discovered that udev was ignoring any rules I added. I also noticed that 55-cups.rules, which is supposed to be necessary for CUPS, is also not working. Somehow, FD64 is printing in spite of this.
Has anyone tried using hardware like modems in FD64 that relies on udev rules? Did you get it to work?
[Edit] I suspect the problem is that the module usblp is not available.
Posted: Wed 09 Mar 2011, 02:30
by kirk
[Edit] I suspect the problem is that the module usblp is not available.
CUPS 1.4.x has a new USB backed that requires usblp not to be loaded.