There were some concerns that were raise with the JRE.
As you probably remember, PEMASU did assist with a suitable resolution.
Question
Was his resolution included in the most recent version of PUP526?
Is it incorporated in QuickPET or PPM or both?
Thanks in advance.
Lucid Puppy 5.2.7 RC2
I have to agree with the delta files idea.
You, Playdayz, are kicking out new test versions so fast that a new one is released almost before the previous one finished downloading.
And for those with a slow connection or download limits, downloading a new test version every couple days is just wrong.
Give the testers a little time to explore and use the release for a little while before jumping into creating a new release every time a bug is reported.
The last version I downloaded was luci_263.
You, Playdayz, are kicking out new test versions so fast that a new one is released almost before the previous one finished downloading.
And for those with a slow connection or download limits, downloading a new test version every couple days is just wrong.
Give the testers a little time to explore and use the release for a little while before jumping into creating a new release every time a bug is reported.
The last version I downloaded was luci_263.
Rox right click behaviour
I posted about this just above. In my enthusiasm, I was under the impression that the changes i suggested were merely customisations of Rox. Digging just a bit, it looks as if they likely require code patching, so much harder to do.
I still think that they would be a very useful enhancement to Puppy usability though.
Whilst on the topic, I note that the whole clumsy need to use wrapper scripts in customisation may be related to what seems to be a bug in Puppy/Rox since 432 v3 at least. According to the Rox manual, setting the run action should only require dragging a program to the action entry box. if you do that, Rox tells you, rather indirectly, to add "$@" to the command. I note that the text file type default run action in Puppy has "$1" instead.
I still think that they would be a very useful enhancement to Puppy usability though. Whilst on the topic, I note that the whole clumsy need to use wrapper scripts in customisation may be related to what seems to be a bug in Puppy/Rox since 432 v3 at least. According to the Rox manual, setting the run action should only require dragging a program to the action entry box. if you do that, Rox tells you, rather indirectly, to add "$@" to the command. I note that the text file type default run action in Puppy has "$1" instead.
It's funny, funny. Firefox has a capital F in the pet so it doesn't get caught in downloading when looking for firefox--but seamonkey did get caught.As soon as the SeaMonkey download starts,maybe a two second delay, the Flash dialog appears. As you observed with Firefox,the Flash dialog doesn't appear until the first time Firefox is launched.
-----------------------------------------------------------------------
Yes, I will make a delta file from 263 to 264.
------------------------------------------------------------------------
Maybe Chromium 13 is better behaved than Chromium 14.
http://distro.ibiblio.org/puppylinux/pe ... cid525.pet
Last edited by playdayz on Thu 14 Jul 2011, 02:52, edited 1 time in total.
264 frugal manual hdd install. Same timing out of network wizard and SNS script after installing broadcom wl wifi driver.
wl driver recognized loaded and waiting for completion of connection but times out. this happens no matter how many times I get the driver loaded either manually or with network wizard or SNS.
This is not an isolated incident there is good bit discussion on this board.
Individuals have posted there code fix for this broken script. would be nice if it could get included in puppy.
"After quite a bit of messing around, I managed to get auto DHCP from startup on this Dell Vostro 1000 with Broadcom 43xx card. The bcm43xx driver seems to work fine for me, whereas I could not get the windows driver bcmwl5.inf to work at all through ndiswrapper.
I think the DHCP problem is it trying to log-in the card immediately after turning it on, as someone else suggested. I therefore added this to rc.local and now I'm on the net as soon puppy starts and I click on Firefox. eth0wireless & eth0mode files can be deleted, which will stop the network card being booted twice at startup. Basically it's putting a delay in the initialisation of the card, but why it won't work if you put the same script into eth0wireless I'm unsure.
Code:
rmmod bcm43xx
modprobe bcm43xx
sleep 5s
ifconfig eth0 up
iwconfig eth0 essid xxxxxxxxxx
iwconfig eth0 channel x
iwconfig eth0 mode managed
iwconfig eth0 key open xxxxxxxxxx
rm /etc/dhcpc/*.pid
dhcpcd -t 30 -h puppypc -d eth0"
Frisbee contains script that fix this problem for those with the troublesome drivers. Which is how I could get connected.
Booting a cd that all but automatically discovers your hardware and available wifi connections and makes that connection with only a few user inputs is different from somehow finding out what you need to connect with is in a program, quickpet, then getting it somehow.
How different is it? The less you know about computers the bigger that difference.
Miserable script timing out after successful recognition and loading of driver with interface brought up and available.
Interface: eth1 Driver: wl Bus: x MacAddress: AC:81:12:1D:A9:5E
Description: x
STEP1a: ifconfig eth1 up
STEP1b: iwlist eth1 scan
eth1 Scan completed :
Cell 01 - Address: 00:19:E4:4B:D3:19
ESSID:"2WIRE789"
Mode:Managed
Frequency:2.457 GHz (Channel 10)
Quality:5/5 Signal level:-56 dBm Noise level:-93 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
STEP1c: ifconfig eth1 down
STEP2: iwconfig eth1 mode managed
STEP3: iwconfig eth1 channel 10
STEP4: iwconfig eth1 essid "2WIRE789"
STEP5: iwconfig eth1 key restricted 9977453890
STEP5a: ifconfig eth1 up
ERROR, TIMEOUT. Have not got an Access Point.
Result of 'iwconfig eth1':
eth1 IEEE 802.11 ESSID:""
Mode:Managed Frequency:2.457 GHz Access Point: Not-Associated
Bit Rate:8 Mb/s Tx-Power:24 dBm
Retry min limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Managementmode:All packets received
Link Quality=5/5 Signal level=0 dBm Noise level=0 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
STEP5: iwconfig eth1 key open 9977453890
STEP5a: ifconfig eth1 up
ERROR, TIMEOUT. Have not got an Access Point.
Result of 'iwconfig eth1':
eth1 IEEE 802.11 ESSID:""
Mode:Managed Frequency:2.457 GHz Access Point: Not-Associated
Bit Rate:8 Mb/s Tx-Power:24 dBm
Retry min limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Managementmode:All packets received
Link Quality=5/5 Signal level=0 dBm Noise level=0 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
*********************************************************
LAST 10 LINES of /var/log/messages:
Jul 14 20:04:39 puppypc user.info kernel: registered panic notifier
Jul 14 20:04:39 puppypc user.info kernel: acpi device:01: registered as cooling_device2
Jul 14 20:04:39 puppypc user.info kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input10
Jul 14 20:04:39 puppypc user.info kernel: ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)
Jul 14 20:04:39 puppypc user.info kernel: [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
Jul 14 20:04:39 puppypc user.info kernel: wl 0000:03:00.0: PCI INT A disabled
Jul 14 20:04:39 puppypc user.info kernel: wl 0000:03:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
Jul 14 20:04:39 puppypc user.debug kernel: wl 0000:03:00.0: setting latency timer to 64
Jul 14 20:04:39 puppypc user.warn kernel: eth1: Broadcom BCM4727 802.11 Hybrid Wireless Controller 5.60.48.36
Jul 14 20:04:39 puppypc user.info kernel: HDMI hot plug event: Pin=6 Presence_Detect=1 ELD_Valid=0[/url]
wl driver recognized loaded and waiting for completion of connection but times out. this happens no matter how many times I get the driver loaded either manually or with network wizard or SNS.
This is not an isolated incident there is good bit discussion on this board.
Individuals have posted there code fix for this broken script. would be nice if it could get included in puppy.
"After quite a bit of messing around, I managed to get auto DHCP from startup on this Dell Vostro 1000 with Broadcom 43xx card. The bcm43xx driver seems to work fine for me, whereas I could not get the windows driver bcmwl5.inf to work at all through ndiswrapper.
I think the DHCP problem is it trying to log-in the card immediately after turning it on, as someone else suggested. I therefore added this to rc.local and now I'm on the net as soon puppy starts and I click on Firefox. eth0wireless & eth0mode files can be deleted, which will stop the network card being booted twice at startup. Basically it's putting a delay in the initialisation of the card, but why it won't work if you put the same script into eth0wireless I'm unsure.
Code:
rmmod bcm43xx
modprobe bcm43xx
sleep 5s
ifconfig eth0 up
iwconfig eth0 essid xxxxxxxxxx
iwconfig eth0 channel x
iwconfig eth0 mode managed
iwconfig eth0 key open xxxxxxxxxx
rm /etc/dhcpc/*.pid
dhcpcd -t 30 -h puppypc -d eth0"
Frisbee contains script that fix this problem for those with the troublesome drivers. Which is how I could get connected.
Booting a cd that all but automatically discovers your hardware and available wifi connections and makes that connection with only a few user inputs is different from somehow finding out what you need to connect with is in a program, quickpet, then getting it somehow.
How different is it? The less you know about computers the bigger that difference.
Miserable script timing out after successful recognition and loading of driver with interface brought up and available.
Interface: eth1 Driver: wl Bus: x MacAddress: AC:81:12:1D:A9:5E
Description: x
STEP1a: ifconfig eth1 up
STEP1b: iwlist eth1 scan
eth1 Scan completed :
Cell 01 - Address: 00:19:E4:4B:D3:19
ESSID:"2WIRE789"
Mode:Managed
Frequency:2.457 GHz (Channel 10)
Quality:5/5 Signal level:-56 dBm Noise level:-93 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
STEP1c: ifconfig eth1 down
STEP2: iwconfig eth1 mode managed
STEP3: iwconfig eth1 channel 10
STEP4: iwconfig eth1 essid "2WIRE789"
STEP5: iwconfig eth1 key restricted 9977453890
STEP5a: ifconfig eth1 up
ERROR, TIMEOUT. Have not got an Access Point.
Result of 'iwconfig eth1':
eth1 IEEE 802.11 ESSID:""
Mode:Managed Frequency:2.457 GHz Access Point: Not-Associated
Bit Rate:8 Mb/s Tx-Power:24 dBm
Retry min limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Managementmode:All packets received
Link Quality=5/5 Signal level=0 dBm Noise level=0 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
STEP5: iwconfig eth1 key open 9977453890
STEP5a: ifconfig eth1 up
ERROR, TIMEOUT. Have not got an Access Point.
Result of 'iwconfig eth1':
eth1 IEEE 802.11 ESSID:""
Mode:Managed Frequency:2.457 GHz Access Point: Not-Associated
Bit Rate:8 Mb/s Tx-Power:24 dBm
Retry min limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Managementmode:All packets received
Link Quality=5/5 Signal level=0 dBm Noise level=0 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
*********************************************************
LAST 10 LINES of /var/log/messages:
Jul 14 20:04:39 puppypc user.info kernel: registered panic notifier
Jul 14 20:04:39 puppypc user.info kernel: acpi device:01: registered as cooling_device2
Jul 14 20:04:39 puppypc user.info kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input10
Jul 14 20:04:39 puppypc user.info kernel: ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)
Jul 14 20:04:39 puppypc user.info kernel: [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
Jul 14 20:04:39 puppypc user.info kernel: wl 0000:03:00.0: PCI INT A disabled
Jul 14 20:04:39 puppypc user.info kernel: wl 0000:03:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
Jul 14 20:04:39 puppypc user.debug kernel: wl 0000:03:00.0: setting latency timer to 64
Jul 14 20:04:39 puppypc user.warn kernel: eth1: Broadcom BCM4727 802.11 Hybrid Wireless Controller 5.60.48.36
Jul 14 20:04:39 puppypc user.info kernel: HDMI hot plug event: Pin=6 Presence_Detect=1 ELD_Valid=0[/url]
I do that, yes. I find it an effective method of working, especially when we are close to the end--or when I screw one up, such as 262. I am sorry to say that 265 will come quickly also, but I will provide the delta. Thanks.I have to agree with the delta files idea.
You, Playdayz, are kicking out new test versions so fast that a new one is released almost before the previous one finished downloading
http://diddywahdiddy.net/Puppy500/luci- ... .iso.delta
2c755d5945c37e437f15896f1c116ca3
d/l 264 iso, booted to desktop and did full install
Installed Seamonkey 2.2.pet from smokey01 and symlinked to /usr/bin/seamonkey same as have been doing in luci 262 and 263
Strange happenings. After setting browser home page to file:///usr/share/doc/home.htm and making this my home page at sign on, at next signon I receive browser screen with http://bi/ and IT WORKS! in body of screen. Then have to press home button to go to actual home page
What's going on with this?
thanks
yarddog
Installed Seamonkey 2.2.pet from smokey01 and symlinked to /usr/bin/seamonkey same as have been doing in luci 262 and 263
Strange happenings. After setting browser home page to file:///usr/share/doc/home.htm and making this my home page at sign on, at next signon I receive browser screen with http://bi/ and IT WORKS! in body of screen. Then have to press home button to go to actual home page
What's going on with this?
thanks
yarddog
Last edited by yarddog on Thu 14 Jul 2011, 04:51, edited 1 time in total.
Deleted full install, booted live cd to desktop and did another full install.yarddog wrote:d/l 264 iso, booted to desktop and did full install
Installed Seamonkey 2.2.pet from smokey01 and symlinked to /usr/bin/seamonkey same as have been doing in luci 262 and 263
Strange happenings. After setting browser home page to file:///usr/share/doc/home.htm and making this my home page at sign on, at next signon I receive browser screen with http://bi/ and IT WORKS! in body of screen. Then have to press home button to go to actual home page
What's going on with this?
thanks
yarddog
All is now ok. This was kinda weird but now back in business
yarddog
-
Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
updated 264 Live CD
Can someone check this please:
drag and drop text file onto edit icon and it runs (as it should)
but drag and drop pics are not? (is that just me? Used to work OK - I am running a slightly smaller or updated 3.40 Mtpaint that I think was posted on this thread so that could be it?)
Also when upgrading my flash driver was lost
I did not upgrade (it was offered)
Now where do I get it? Do I have to go hunting in the PPM or the wiki?
Should Flash be added to drivers in Quickpet?
Just trying to upgrade from FF did not work (I don't think it ever has)
Oh incidentally some distros/projects offer nightly builds
There are arguments for and against
Releasing 'early and often' is a choice and preference of the main developer
that I for one prefer
01micko has made the choice to work on a slightly less often release schedule for Slacko (Puppy 5.3 now in early development release)
The delta files are a great option too
Thanks guys
Can someone check this please:
drag and drop text file onto edit icon and it runs (as it should)
but drag and drop pics are not? (is that just me? Used to work OK - I am running a slightly smaller or updated 3.40 Mtpaint that I think was posted on this thread so that could be it?)
Also when upgrading my flash driver was lost
I did not upgrade (it was offered)
Now where do I get it? Do I have to go hunting in the PPM or the wiki?
Should Flash be added to drivers in Quickpet?
Just trying to upgrade from FF did not work (I don't think it ever has)
Oh incidentally some distros/projects offer nightly builds
There are arguments for and against
Releasing 'early and often' is a choice and preference of the main developer
that I for one prefer
01micko has made the choice to work on a slightly less often release schedule for Slacko (Puppy 5.3 now in early development release)
The delta files are a great option too
Thanks guys
-
reckrhodes
- Posts: 116
- Joined: Wed 30 May 2007, 08:15
playdayz:
Ok it's wireless on Puppy 525 and Luci 260....not Luci 264
But I will bet I get the same result.
However, for other people with similar Connection problems,
this may prove helpful in its strange way.
////////////
" Repeat the step Click on >> Test wlan0
Repeat the step Click on Auto DHCP "
http://murga-linux.com/puppy/viewtopic.php?t=69877
Regards....Chris.
Ok it's wireless on Puppy 525 and Luci 260....not Luci 264
But I will bet I get the same result.
However, for other people with similar Connection problems,
this may prove helpful in its strange way.
////////////
" Repeat the step Click on >> Test wlan0
Repeat the step Click on Auto DHCP "
http://murga-linux.com/puppy/viewtopic.php?t=69877
Regards....Chris.
Maybe stupid,
1/ Why maintain the future 526 to an "old" kernel and "old" system libs (ntfs, etc...)?
Barry compiled 2.6.39.3 http://bkhome.org/blog/?viewDetailed=02342
And SystemRescueCD or PartedMagic which are dealing with rescuing systems are upto date see
http://partedmagic.com/doku.php?id=changelog
http://www.sysresccd.org/Changes-x86
2/ I see a few compilation in i686, but as I understand the rest is in i386.
Won't it lead to bugs?
Should there be as proposed one version in i386 and one 64bits version.
( At the same time we release the Community Edition wouldn't it be amazing if we could release a twin 64-bit edition! Or at least a "hybrid" 32/64 bit edition. Iguleder seems to have something going on there.)
1/ Why maintain the future 526 to an "old" kernel and "old" system libs (ntfs, etc...)?
Barry compiled 2.6.39.3 http://bkhome.org/blog/?viewDetailed=02342
And SystemRescueCD or PartedMagic which are dealing with rescuing systems are upto date see
http://partedmagic.com/doku.php?id=changelog
http://www.sysresccd.org/Changes-x86
2/ I see a few compilation in i686, but as I understand the rest is in i386.
Won't it lead to bugs?
Should there be as proposed one version in i386 and one 64bits version.
( At the same time we release the Community Edition wouldn't it be amazing if we could release a twin 64-bit edition! Or at least a "hybrid" 32/64 bit edition. Iguleder seems to have something going on there.)
playdayz, why not just trim down the main SFS file to the essentials and offer an additional SFS with the goodies like Pidgin, Skype etc.playdayz wrote:Yes that's true. The iso is now 124MB. We could add ~3.5MB.There are several good candidates for PETs that will see a lot of use, if incorporated in the Distro as well as being useful, too, as Puppy525 matures.
Pidgin is about 3.5MB.
Transmission is relatively tiny.
XineDVD is about 2-2.5MB.
Other nominations?
-
stu90
Nice surprise in 264 with simplebox and simplegtk already installed
Flash installer picked up my portable version of opera on a separate partition and prompted for download
Playdayz,
Would it be possible to add this bit of code to /root/.config/openbox/rc.xml
around line #159 just under <!-- Keybindings for desktop switching -->
This will open the openbox right click menu from Ctrl + Alt + q
but with xdotool you can also swap the fbpanel menu for the openbox menu - having this means you can easily add a menu to the tint2 panel as well.
Flash installer picked up my portable version of opera on a separate partition and prompted for download
Playdayz,
Would it be possible to add this bit of code to /root/.config/openbox/rc.xml
around line #159 just under <!-- Keybindings for desktop switching -->
Code: Select all
<keybind key="A-C-q">
<action name="ShowMenu">
<menu>root-menu</menu>
</action>
</keybind>but with xdotool you can also swap the fbpanel menu for the openbox menu - having this means you can easily add a menu to the tint2 panel as well.
Hello,Testing 264 now..
Installed xorg-high, GLXgears @ 66fps, same as refresh..
Net via rt2860/5390 thru ndiswrapper... works fine...
Using shared browser (Firefox 8 / Nightly) works fine...
OB, GTK, MTPaint 3.40, theme changes, Rox-Term, all fine..
So far all works fine OOTB...
Not much to report...
Frugal install.. (of course..
)Compaq cq56
Intel 2.2g w/ 2gb ram and 1 gb swap
Intel video and hda audio
Be back...
@Edit..
Tested PupApps, GTK and OB theme makers, SFS on the fly, GParted..
All works great...
Close the Windows, and open your eyes, to a whole new world
I am Lead Dog of the
Puppy Linux Users Group on Facebook
Join us!
Puppy since 2.15CE...
I am Lead Dog of the
Puppy Linux Users Group on Facebook
Join us!
Puppy since 2.15CE...
x2. This simple keybinding plus xdotool opens up fbpanel for power users. I will put together a tutorial on it soon (with due thanks to Stu90stu90 wrote:Nice surprise in 264 with simplebox and simplegtk already installed
Flash installer picked up my portable version of opera on a separate partition and prompted for download
Playdayz,
Would it be possible to add this bit of code to /root/.config/openbox/rc.xml
around line #159 just under <!-- Keybindings for desktop switching -->
This will open the openbox right click menu from Ctrl + Alt + qCode: Select all
<keybind key="A-C-q"> <action name="ShowMenu"> <menu>root-menu</menu> </action> </keybind>
but with xdotool you can also swap the fbpanel menu for the openbox menu - having this means you can easily add a menu to the tint2 panel as well.
).Spup Frugal HD and USB
Root forever!
Root forever!
-
gcmartin
Hi Playdayz. I think what Smokey01 is referring to is something you also referenced when you started this current effort. As I remember, it was a base ISO, and ... (others).smokey01 wrote:playdayz, why not just ... and offer an additional SFS ... .playdayz wrote: ... iso is now 124MB ...
Anyway, Live media testing for current 264 were successful. Looking forward.
Hope this helps