Lighthouse 64 5.14.2 Beta 4

Message

meeki · #106 Post by **meeki** » Thu 26 Jul 2012, 08:51

you are right about slackware vs LH64 = wierd diff.

I have 3 slakware paks running with out a issue

The skype ver 4 I linked works perfect

Also running 2 lib packs for depends

I had 2 not work as all.

And the last one I tryed was apache server for slackware and i will perma crash your pup save after boot.

So its hit or miss. I'm happy to take it

Thanks for letting me know where GKrellM is located and started saved me the time of tracking it all down. I just had so much going on at the time i did it the cheezy way

your script is nice... checks if its running "pidof " then "gerp" chacks the GKrellm.pid ???

only issue is it does not check where its drawn on X.

For some reason It trys to load all 3 windows and crashes. because more than one instance of it is running.

2 ways I'll try to fix this tomorrow as i need ot goto bed.

Put DISPLAY=:0.0 in your bash

or the EZ way put a countdown on my script to wait about 5 seconds till it draws DISPLAY=:0.1 and DISPLAY=:0.2

I'll try to fix it in your scrip so you can update it in the next release so other nuts with mufti monitors don't crash.

I bet you did not think people would have multiple monitors on Lighthouse.

gcmartin · #107 Post by **gcmartin** » Thu 26 Jul 2012, 14:01

@Meeki,
Questions

Might you have made a PET of your work?
And, might you be aware of this, reported from a Fatdog601 user?

smokey01 wrote:
gcmartin wrote:
smokey01 wrote:Thanks but no.
Is there something wrong with that PET that was offered you?
Just curious of the problem you encountered.
Thanks in advance
It wasn't a pet and it didn't run. Something is wrong, not sure yet.

It keeps complaining it can't fine the file or directory. ...

Here to help

meeki · #108 Post by **meeki** » Thu 26 Jul 2012, 18:14

I have attempted to make a pet of Skype 4.0.0.8 It works but has a bug where you cant close the chat window if you open it up.

While goofing around I found and tried the Slackware package 4.0.0.7 tried it and it worked fine.

MAKE SURE you have your devx for your package installed. befor you go trying o use a Slackware package.

pixelblip · #109 Post by **pixelblip** » Thu 26 Jul 2012, 18:20

Earth to Meeki come in over

I've been asking on the forums about something and they have sent me here hoping you can help me. Fingers crossed!

I installed Lighthouse 64 the other day - it's really good! It works a treat on my AMD 4400.

I wanted to make some music with it but I can't see where I can find a Wineasio.dll that will work on this distro. I tried Ubuntu / .deb compiled for 64 bit but that didn't work.

Can anyone help please? I am desperate !

Thank you for any help you can offer.

meeki · #110 Post by **meeki** » Thu 26 Jul 2012, 19:37

Hang in there I'm building a sfs ATM for tazoc so we can have an Apache Web Server, MySQL, PHP. This should work in Lighthouse64 and FATDOG64. It takes my work box about 1 hr to ./config the Perl for it. I'm on round 3 of this.

After that I'll look into getting your winealso working.

Then after that It looks like everyone wants a true skype4 pet for the 64bit puppys
The issue with skype is that the have no static 64bit version. So it runs off of 32libs getting them into the install folder and called right is a pain. As stated before I have one that works but has bugs. I may share or host a pet from another source but when I make a pet by hand like I did with dropbox I make sure there are no bugs with current Lighthouse release.
So until I get the Message Window fixed in the pet fixed I will not release it.

I'm working on all the above. Give me some time ill sort it out.

pixelblip · #111 Post by **pixelblip** » Thu 26 Jul 2012, 19:58

Thanks loads Meeki! I really appreciate it.

tazoc · #112 Post by **tazoc** » Thu 26 Jul 2012, 20:15

meeki wrote:Put DISPLAY=:0.0 in your bash

or the EZ way put a countdown on my script to wait about 5 seconds till it draws DISPLAY=:0.1 and DISPLAY=:0.2

I'll try to fix it in your scrip so you can update it in the next release so other nuts with mufti monitors don't crash.

I bet you did not think people would have multiple monitors on Lighthouse.

Actually, I'm running 2 monitors and I think Q5sys has 3 or 4, but we're both running proprietary video drivers and haven't seen problems. Just restart X with all monitors on and I get one huge desktop with just one GKrellM. (Its options has a setting whether or not to allow multiple instances, default is no.) I also use Zarfy Monitor Control in the System Menu sometimes.

But yeah whatever changes /usr/local/bin/GKrellm needs I'll put them in, thanks! For now I'm putting

Code: Select all

DISPLAY=:0.0 #1207226 suggested by meeki

near the top.

TaZoC

meeki · #113 Post by **meeki** » Thu 26 Jul 2012, 21:01

I'm running The Nivida drivers pet.

I'm not running Xinerama or twin view. Or one big desktop. I'm running seperate X-Screens for each. So I have 3 instances of X and 3 instances of Openbox going at one time.

No crashes for over 2 hrs now with the startup scrip modded. The below mod puts it in the stock window. I'm running it on my far Right monitor with DISPLAY=:0.1

Code: Select all

#!/bin/sh
# 2010-01 TazOC-www.lhpup.org
DISPLAY=:0.0
PIDFILE="/var/run/GKrellm.pid"

if pidof GKrellM | grep " "; then # >1 instance of this script
 [ -s /var/run/GKrellm.pid ] && kill `cat $PIDFILE`
 sleep 1
fi
echo "`pidof GKrellM`" > ${PIDFILE}

if [ -x /usr/bin/gkrellm ];then
 sleep 3
 pidof gkrellm 1>/dev/null && killall gkrellm
 sleep .1
 gkrellm &
fi
rm -f ${PIDFILE}

exit # END SCRIPT

Q5sys · #114 Post by **Q5sys** » Thu 26 Jul 2012, 23:55

tazoc wrote:Actually, I'm running 2 monitors and I think Q5sys has 3 or 4, but we're both running proprietary video drivers and haven't seen problems. Just restart X with all monitors on and I get one huge desktop with just one GKrellM. (Its options has a setting whether or not to allow multiple instances, default is no.) I also use Zarfy Monitor Control in the System Menu sometimes.

But yeah whatever changes /usr/local/bin/GKrellm needs I'll put them in, thanks! For now I'm putting
Code: Select all
DISPLAY=:0.0 #1207226 suggested by meeki
near the top.

TaZoC

Correct. I'm running 4x screens with no problem whatsoever. Once I got the driver loaded I just used the bundled nvidia configure program to set everything up the way I wanted and let it write the xorg.conf script.

Code: Select all

# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings:  version 280.13  (buildmeister@swio-display-x86-rhel47-03.nvidia.com)  Wed Jul 27 17:15:45 PDT 2011


Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 1080
    Screen      1  "Screen1" 0 0
    Screen      2  "Screen2" 1920 0
    Screen      3  "Screen3" 1920 1080
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
    Option         "Xinerama" "1"
EndSection

Section "Files"
    FontPath        "/usr/share/fonts/default/Type1"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"

    # HorizSync source: edid, VertRefresh source: edid
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "Samsung SMEX2220"
    HorizSync       30.0 - 81.0
    VertRefresh     56.0 - 75.0
    Option         "DPMS"
EndSection

Section "Monitor"

    # HorizSync source: edid, VertRefresh source: edid
    Identifier     "Monitor1"
    VendorName     "Unknown"
    ModelName      "Samsung SMEX2220"
    HorizSync       30.0 - 81.0
    VertRefresh     56.0 - 75.0
    Option         "DPMS"
EndSection

Section "Monitor"

    # HorizSync source: edid, VertRefresh source: edid
    Identifier     "Monitor2"
    VendorName     "Unknown"
    ModelName      "Samsung SMEX2220"
    HorizSync       30.0 - 81.0
    VertRefresh     56.0 - 75.0
    Option         "DPMS"
EndSection

Section "Monitor"

    # HorizSync source: edid, VertRefresh source: edid
    Identifier     "Monitor3"
    VendorName     "Unknown"
    ModelName      "Samsung SMEX2220"
    HorizSync       30.0 - 81.0
    VertRefresh     56.0 - 75.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GTX 550 Ti"
    BusID          "PCI:1:0:0"
    Screen          0
EndSection

Section "Device"
    Identifier     "Device1"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GTX 550 Ti"
    BusID          "PCI:1:0:0"
    Screen          1
EndSection

Section "Device"
    Identifier     "Device2"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GTX 550 Ti"
    BusID          "PCI:6:0:0"
    Screen          0
EndSection

Section "Device"
    Identifier     "Device3"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GTX 550 Ti"
    BusID          "PCI:6:0:0"
    Screen          1
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "TwinView" "0"
    Option         "metamodes" "DFP-0: nvidia-auto-select +0+0"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen1"
    Device         "Device1"
    Monitor        "Monitor1"
    DefaultDepth    24
    Option         "TwinView" "0"
    Option         "metamodes" "DFP-3: nvidia-auto-select +0+0"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen2"
    Device         "Device2"
    Monitor        "Monitor2"
    DefaultDepth    24
    Option         "TwinView" "0"
    Option         "metamodes" "DFP-0: nvidia-auto-select +0+0"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen3"
    Device         "Device3"
    Monitor        "Monitor3"
    DefaultDepth    24
    Option         "TwinView" "0"
    Option         "metamodes" "DFP-3: nvidia-auto-select +0+0"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

meeki · #115 Post by **meeki** » Fri 27 Jul 2012, 04:28

Q5sys, your running Xinerama. Its a fine way to do a desktop. I have no issues with it.

Xinerama allows "X applications and window managers to use two or more physical displays"; so its handling the applications

I'm just bucking the system

Best way I can describe what im doing, though I'm sure im wrong on the details:
I'm running 3 separate desktops they function independent of each other. you cant drag an open window to the other screen. Other funny things happen too! if you were to try and open a second instance of firefox on the other monitor it will freek out and say sorry its already runnin. There is a way around this with multiple profiles firefox -p "profile name" I then use sync to tie them all together.

meeki · #116 Post by **meeki** » Sun 29 Jul 2012, 14:18

Well I now know why WineASIO is not standard package anywhere.

"Get the ASIO SDK from Steinberg
Due to the licensing restrictions of the SDK it's impossible to distribute the asio.h header file with WineASIO so you have to get it yourself. "
quote source http://wiki.cockos.com/wiki/index.php/I ... g_WineASIO

Also here is the ASIO Licensing agreement.pdf
http://dl.dropbox.com/u/12968946/lighth ... eement.pdf

Sad to say mate your on your own.

Before you go trying to build it you should know that it needs the wine-dev for a file on make called wine/debug.h
Because lighthouse and puppys are small package builders tend to clean up at the end killing such files that do not effect run.

So unless I can get the build sfs I can not do much about the ASIO issue.

Q5sys · #117 Post by **Q5sys** » Wed 01 Aug 2012, 01:06

meeki wrote:Q5sys, your running Xinerama. Its a fine way to do a desktop. I have no issues with it.

Xinerama allows "X applications and window managers to use two or more physical displays"; so its handling the applications

I'm just bucking the system

Best way I can describe what im doing, though I'm sure im wrong on the details:
I'm running 3 separate desktops they function independent of each other. you cant drag an open window to the other screen. Other funny things happen too! if you were to try and open a second instance of firefox on the other monitor it will freek out and say sorry its already runnin. There is a way around this with multiple profiles firefox -p "profile name" I then use sync to tie them all together.

Its always good to have people buck the system and do things different!

Q5sys · #118 Post by **Q5sys** » Wed 01 Aug 2012, 01:54

Truecrypt 7.1a (64bit)

someone want to test this on their lhp64 system?

meeki · #119 Post by **meeki** » Wed 01 Aug 2012, 09:06

Testing now

Q5sys · #120 Post by **Q5sys** » Wed 01 Aug 2012, 09:21

meeki wrote:Testing now

dont forget to set it to not to use Kernel crypto services.

meeki · #121 Post by **meeki** » Fri 03 Aug 2012, 03:18

well ive put it through a few paces.

It does not like me to make linux ext2 - 4 drives unless I use the entire drive option.
"device-mapper: reload ioctl failed: No such file or directory
Command failed"

Anniekin · #122 Post by **Anniekin** » Sun 05 Aug 2012, 04:19

subcribing

Q5sys · #123 Post by **Q5sys** » Mon 06 Aug 2012, 01:41

meeki wrote:well ive put it through a few paces.

It does not like me to make linux ext2 - 4 drives unless I use the entire drive option.
"device-mapper: reload ioctl failed: No such file or directory
Command failed"

I got that message the first time I loaded it. After a reboot though it went away.

RandSec · #124 Post by **RandSec** » Tue 07 Aug 2012, 21:26

Hi tazoc!

1. This is an issue I first noticed in 5.12: Pburn fails when commanded to erase a DVD. That means I have to boot a 32-bit Puppy just to erase discs. Here are the error log results from my earlier comment:

(first, selecting a complete blank)
Pburn version 3.3.4

###################################################
COMMAND:
###################################################

growisofs -use-the-force-luke=notray -Z sr0=/dev/zero

###################################################
OUTPUT:
###################################################
:-( "sr0=/dev/zero": unexpected errno:No such file or directory

(next, selecting a fast blank)
Pburn version 3.3.4

###################################################
COMMAND:
###################################################

dvd+rw-format -force sr0

###################################################
OUTPUT:
###################################################
* BD/DVD±RW/-RAM format utility by <appro@fy.chalmers.se>, version 7.1.
- usage: dvd+rw-format [-force[=full]] [-lead-out|-blank[=full]]
[-ssa[=none|default|max|XXXm]] /dev/dvd

2. I operate solely and completely as a LiveDVD. When it comes time to copy a disc (for other computers, or as a backup, or just to reduce the number of sessions which load upon startup) I am used to making another .ISO disc, and then doing a Save to that disc. That works, at least when the ISO is the same. So I am questioning the instruction text which says:

"Please insert the Lighthouse64 live-CD/DVD media that you booted from...."

It should say something like "For a new backup copy of the whole disc, insert a new bare ISO, or to save the current session, insert the Lighthouse64 boot disc."

On the other hand, it should be reasonably easy for the computer to check if the Lighthouse64 media is already there, or is a new ISO, which could avoid having the novice user try to do something when nothing is needed.

I love Lighthouse64, and hope it continues!

Ted Dog · #125 Post by **Ted Dog** » Thu 09 Aug 2012, 03:28

growisofs -use-the-force-luke=notray -Z /dev/sr0=/dev/zero

simple typo

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

Lighthouse 64 5.14.2 Beta 4

Wineasio request

Multiple monitors and GKrellM

Re: Multiple monitors and GKrellM

Some Issues