Puppeee 4.3X
Here is an updated trayclock with a "set the time" feature. Someone asked for this a long time ago and I finally got around to it.
- Attachments
-
- trayclock-.33.pet
- (53.69 KiB) Downloaded 954 times
I found the problem lurking in my savefile, i had 3 whiteout files inside /dev foldersandungas wrote:Yes, tested with several pendrives, none of them is detectedjemimah wrote:There is a window of time between when the kernel does usb detection and when Udev starts that you can plug in a usb device and it won't show up. The solution is to just wait until the desktop has loaded. Are still you having the problem if you wait?.
One of the pendrives has a led, and i can see the blinking pattern that usually does when plugged (maybe this means something to you)
When i plug them, dont appear a new icon in the desktop, if i open pmount and i press "refresh" button the pendrive is not detected
I dont remember exactly what happenend, but the other day i saw an error in pmount when connecting or disconnecting a pendrive
Pmount window was blinking, something like closing and opening continuously
I dont remeber what i did to stop this, i thought that was a fail of pmount and i gave no importance
But it seems that after this my USBs are blind...
.wh.sdc
.wh.sdc1
.wh.sdc2
The only device that i connected with 2 partitions (fat & swap) was a 512mb pendrive USB v1.0
I did this 2 partitions time ago when trying hibernation to USB... but this time i did nothing strange with it, just plug it
I suspect that the files was generated because a disconnection (in fact... the connector of the pendrive seems to fail sometimes, and usually is not detected when plugged)
I hope this helps you to track this problem
Last edited by sandungas on Sun 12 Sep 2010, 09:07, edited 1 time in total.
I installed it yesterday (in a ramboot session), but nothing changedjemimah wrote:Here is an updated trayclock with a "set the time" feature. Someone asked for this a long time ago and I finally got around to it.
Its supossed to work with the 3 windows managers ?
Btw... talking about the clock... this remembers me that i have to purpose you to change some default settings for the next release
As always... are just suggestions
24 hours format clock is smaller in size, and i think that is more "standard"IceWM clock 24 hours
IceWM config file --------> /root/.icewm/preferencesCode: Select all
TimeFormat="%H:%M"
The idea is to make this menu smaller, although is not needed, but we have another help icon in the desktopMenu items
IceWM menu template config file ------> /etc/xdg/templates/_root_.icewm_menu
Here you can remove the "help" icon (and even the "run" icon)
The combination of white over black in the fonts is a standard in other operative systems... is visible over dark & light backgroundsROX desktop
ROX-Filer ---> options ---> Pinboard
Foreground ffffff (white)
Text shadow 000000 (black) shadow type: thin
Font size: 13
Icon grid step: medium (16 pixels)
Font size 13 i think is optimun for small screens... by default is 12... but 12 is a bit small... and 14 is too big
Default grid step (fine setting) is 2 pixels... and is not accurate at all, is very hard to align icons with the default setting
Coarse setting is 32 pixels (is too much, and is not needed)
Puppeee 1.0 should be called Puppeee 4.3X. Most of the libs in 4.3X are the same as 4.3.1. This version is considered stable.
4.4 is my new development version. I'm updating the multimedia stuff and continuing moving forward, trying new things, etc.
Fluppy 005 is the same as Puppeee 4.4Beta1 except the kernel and Eee-control.
4.4 is my new development version. I'm updating the multimedia stuff and continuing moving forward, trying new things, etc.
Fluppy 005 is the same as Puppeee 4.4Beta1 except the kernel and Eee-control.
I just installed Puppeee 4.3X about two weeks ago, and am very happy with it. It makes the OS I love, and which was installed by Asus look like a doorstop.
But I'd like to point out a few things that, to me, seem lacking. Just observations. It won't be turning me off to my decision to install Puppeee, even if they aren't addressed.
1) An equivalent of checkdisk automatically run when errors encountered during boot. Hard to do I am sure given the number of ways people get to their Puppeee, but would be nice.
Being an extreme nub to *nix, I am at a loss to resolve the simple errors. It looked like a few blocks were unallocated due to an improper shutdown/lidclosing, and it seems Puppeee is happy to operate in spite of them. fsck seems to find them, repair them, but each time i have rebooted there are still errors. (And yes, I probably have made a simple situation worse trying fscK, but Puppeee seems fine all the same)
how do I get to fsck and an unmounted Puppeee partition from within Puppeee? Or is this even the correct tool? f-ile s-ystem c-heck k-omrade I presumed
2) I know the Puppeee help says that I can find other people's applications if they are not provided by the Puppeee site, but for me, discovering where to find them (no list?), or what other distro's versions are compatible with Puppeee makes that job seemingly impossible. Puppeee being derived of Puppy is easy. But the rest is harder for me.
ie: I am a diehard eMule user, and am well aware of aMule and how well its claimed to work with Linux distros. But with so many around, no idea what I should base my decision as to which to pick.
Put this in as a request for it to be added as part of Puppeee, or that some kind soul make it available. I couldn't find it.
Again, all this is small potatoes. I love the abilities it provides, and how much RAM real estate it makes available.
Thank you.
But I'd like to point out a few things that, to me, seem lacking. Just observations. It won't be turning me off to my decision to install Puppeee, even if they aren't addressed.
1) An equivalent of checkdisk automatically run when errors encountered during boot. Hard to do I am sure given the number of ways people get to their Puppeee, but would be nice.
Being an extreme nub to *nix, I am at a loss to resolve the simple errors. It looked like a few blocks were unallocated due to an improper shutdown/lidclosing, and it seems Puppeee is happy to operate in spite of them. fsck seems to find them, repair them, but each time i have rebooted there are still errors. (And yes, I probably have made a simple situation worse trying fscK, but Puppeee seems fine all the same)
how do I get to fsck and an unmounted Puppeee partition from within Puppeee? Or is this even the correct tool? f-ile s-ystem c-heck k-omrade I presumed
2) I know the Puppeee help says that I can find other people's applications if they are not provided by the Puppeee site, but for me, discovering where to find them (no list?), or what other distro's versions are compatible with Puppeee makes that job seemingly impossible. Puppeee being derived of Puppy is easy. But the rest is harder for me.
ie: I am a diehard eMule user, and am well aware of aMule and how well its claimed to work with Linux distros. But with so many around, no idea what I should base my decision as to which to pick.
Put this in as a request for it to be added as part of Puppeee, or that some kind soul make it available. I couldn't find it.
Again, all this is small potatoes. I love the abilities it provides, and how much RAM real estate it makes available.
Thank you.
Fsck is on the Advanced boot menu if you created a bootable card with my installer.
If you're booting with grub, you need to add an entry with pfix=fsck on the kernel line.
You find apps on this forum, under Additional Software. You need to use 4.3 packages and not ones for lupu.
This aMule pet might work.
http://www.murga-linux.com/puppy/viewto ... 16&t=38404
If you're booting with grub, you need to add an entry with pfix=fsck on the kernel line.
You find apps on this forum, under Additional Software. You need to use 4.3 packages and not ones for lupu.
This aMule pet might work.
http://www.murga-linux.com/puppy/viewto ... 16&t=38404
@mvainio
There are .pets compatibles with puppy 4 in this folder
http://distro.ibiblio.org/pub/linux/dis ... ackages-4/
Btw...
@jemimah
Take a look at this icon theme when you have a spare time, please
http://distro.ibiblio.org/pub/linux/dis ... inal-1.pet
Is a shiny icon theme, and uses very intuitive images (mostly copied from KDE)
*The only icons i dont like in this theme are the ones refered to "mounted devices" that adds a ugly text over the icon
Yesterday i was thinking in replacing this text with a simple coloured point (like other themes does)
There are .pets compatibles with puppy 4 in this folder
http://distro.ibiblio.org/pub/linux/dis ... ackages-4/
Btw...
@jemimah
Take a look at this icon theme when you have a spare time, please
http://distro.ibiblio.org/pub/linux/dis ... inal-1.pet
Is a shiny icon theme, and uses very intuitive images (mostly copied from KDE)
*The only icons i dont like in this theme are the ones refered to "mounted devices" that adds a ugly text over the icon
Yesterday i was thinking in replacing this text with a simple coloured point (like other themes does)
uhh i cant be bothered to read or update the os...works fine w/e version i got... i got it a few months ago... just wanted to say it runs good and stable, aside from an accidental reboot.. (was wipen dust off..hit power button)
[21:51] &NO_U[ABK] Record Uptime: 5 weeks 4 days 3 hours 55 minutes 7 seconds set on Fri Sep 10 03:07:55 2010
it was on for over a month.....and i run irc/ventrillo/msn on it constantly and occasional website viewing and gameplay...i keep a fan under it...but it runs cool..runs good..very smooth..no issues..all is good.. just wanted to post my pro uptime woulda been like 2 1/2 months now damn reboot
my only..suggestion which i believe is a puppy..or a linux based issue for that matter... is some kind of built in duel monitor support. i know it HAS it..but only a mirror desktop thing goin on ...monitor 1 and monitor 2 would be pwnage.
[21:51] &NO_U[ABK] Record Uptime: 5 weeks 4 days 3 hours 55 minutes 7 seconds set on Fri Sep 10 03:07:55 2010
it was on for over a month.....and i run irc/ventrillo/msn on it constantly and occasional website viewing and gameplay...i keep a fan under it...but it runs cool..runs good..very smooth..no issues..all is good.. just wanted to post my pro uptime woulda been like 2 1/2 months now damn reboot
my only..suggestion which i believe is a puppy..or a linux based issue for that matter... is some kind of built in duel monitor support. i know it HAS it..but only a mirror desktop thing goin on ...monitor 1 and monitor 2 would be pwnage.
Yeah, the zip and play icons don't really look right either IMO.sandungas wrote:\
@jemimah
Take a look at this icon theme when you have a spare time, please
http://distro.ibiblio.org/pub/linux/dis ... inal-1.pet
Is a shiny icon theme, and uses very intuitive images (mostly copied from KDE)
*The only icons i dont like in this theme are the ones refered to "mounted devices" that adds a ugly text over the icon
Yesterday i was thinking in replacing this text with a simple coloured point (like other themes does)
First you need to reboot with the VGA plugged in - it doesn't work right if you plug it in after booting up.Trip[ABK] wrote:
my only..suggestion which i believe is a puppy..or a linux based issue for that matter... is some kind of built in duel monitor support. i know it HAS it..but only a mirror desktop thing goin on ...monitor 1 and monitor 2 would be pwnage.
Then you can use Zarfy to setup spanning. The LxRandr tool only supports mirroring, but Xorg supports spanning fine. If the virtual screen size is not big enough to fit both monitors side by side, there's a way to increase it by editing the xorg.conf. I don't remember what it is off the top of my head though.
I find the LCD on the Eee to be too small to be very useful as a second monitor though - I usually just close the lid when I connect to my external monitor.
Hello jemimah
I'd just like to send a big ass thanks to you for puppeee, I eventually got round to trying it on my son's eeepc 1001ha (I think it is) and it works out of the box I had tried for ages to get the wireless working (I think it's ralink 3090 although I could be wrong) and now you've gone and made fluppy so I'm going to put that on a stick and give that one a whirl.
Once again THANK YOU
I'd just like to send a big ass thanks to you for puppeee, I eventually got round to trying it on my son's eeepc 1001ha (I think it is) and it works out of the box I had tried for ages to get the wireless working (I think it's ralink 3090 although I could be wrong) and now you've gone and made fluppy so I'm going to put that on a stick and give that one a whirl.
Once again THANK YOU
Jemimah, I must do something very wrong but I totally fail to get right time using Fluppy and sorry for asking in Puppy but as you say it is essentially same behavior when it comes to setting time as I get it.
Time does not fail in Lupu and other puppies. Most likely I fail to get what goes wrong.
Any suggestion or hint on how to set it right. I live in Stockholm Sweden so I do set it to GMT+1 but that makes it go one hour wrong. it is 8.46PM now local time but Fluppy says it is 9.46 instead.
And I corrected the time yesterday and it revered back to showing wrong time. Annoying.
Do I have to go into Bios and set that one straight and then do what?
Time does not fail in Lupu and other puppies. Most likely I fail to get what goes wrong.
Any suggestion or hint on how to set it right. I live in Stockholm Sweden so I do set it to GMT+1 but that makes it go one hour wrong. it is 8.46PM now local time but Fluppy says it is 9.46 instead.
And I corrected the time yesterday and it revered back to showing wrong time. Annoying.
Do I have to go into Bios and set that one straight and then do what?
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
-
- Posts: 68
- Joined: Sun 22 Feb 2009, 10:00
Before making the following changes in Fluppy please correct if necessary your local time setting in your BIOS (see below).
-> System
-> Country Wizard
Personalize Settings:
Europe/Stockholm
don"t check "Use UTC Hardware Clock"
-> OK
Afterwards set your local time in:
-> Set date and time
-> Setupnooby wrote: Any suggestion or hint on how to set it right. I live in Stockholm Sweden so I do set it to GMT+1 but that makes it go one hour wrong. it is 8.46PM now local time but Fluppy says it is 9.46 instead.
[/b]
-> System
-> Country Wizard
Personalize Settings:
Europe/Stockholm
don"t check "Use UTC Hardware Clock"
-> OK
Afterwards set your local time in:
-> Set date and time
Leave your time settings in your BIOS as usual or if necessary set them to your local time.Do I have to go into Bios and set that one straight and then do what? [/b]
nooby
The bios clock is often referred to as RTC, real time clock, and along with 'date' is set to the current date/time, where you are, and can cause problems if it's wrong - often, caused by RTC battery failure
As far as I know the local time setting in all puppies now works the same
Stockholm is UTC / GMT +01:00 hours, with no daylight saving time [hour difference] that we apply in UK
Aitch
The bios clock is often referred to as RTC, real time clock, and along with 'date' is set to the current date/time, where you are, and can cause problems if it's wrong - often, caused by RTC battery failure
As far as I know the local time setting in all puppies now works the same
Stockholm is UTC / GMT +01:00 hours, with no daylight saving time [hour difference] that we apply in UK
Aitch
modem/modprobe update for puppeee 1.0 and 4.4
jemimah, et al,
I have collected all the relevant modem and module-loading updates between "level 6" and wary 098, plus some cleanup items into a single dotpet package. It should work with both puppeee 1.0 and 4.4. I have tested it somewhat with both on my eeePC 1005HAGB. It is attached.
It includes usb_modeswitch 1.1.6, which is not yet proven to work. But I have a workaround package ready if anyone reports it not working. I think a few people should try this on either version of puppeee before consideration is given to merging it into a 4.4 beta.
If there is a better place for me to upload this package, just tell me. Thanks to all who try this out. Send me a pmodemdiag file if you encounter a problem.
UPDATE 2/1/2011: Updated the package (after download 36) with minor changes to /sbin/pup_event_background_modprobe and ..._protect, as well as to /usr/sbin/remasterpup2. No need for most people to take it, but those changes should go into the official puppeee. I bumped 9 to 10 to match the generic modem package level 10, reflecting the upgrade to support modeswitch 1.1.6, which was already in the 20110124 package.
UPDATE 2/9/2011: Updated the package (after download 52) with changes to 4 files: the 2 /sbin/pup-event...modprobe... scripts, the .../all-firmware/dgcmodem tarball and /etc/rc.d/rc.sysinit. Puppeee actually does not use that tarball, because the driver module is absent. But since DGC modems are USB types, that driver could be added to puppeee, even though most such modems are already supported by the cdc_acm driver. I would expect the DGC driver to support more functions (fax?), but have not confirmed that. If the driver is not added, then the tarball could be removed.
UPDATE 2/18/2011: Updated the package (after download 87) with a corrected pupdial, to address Toy4's problem with intermittant failures to connect with dialup. (The fix is to insert a "sync" command just before the wvdial command on line 688, for anyone who prefers to make that simple edit instead of reinstalling.)
Richard
I have collected all the relevant modem and module-loading updates between "level 6" and wary 098, plus some cleanup items into a single dotpet package. It should work with both puppeee 1.0 and 4.4. I have tested it somewhat with both on my eeePC 1005HAGB. It is attached.
It includes usb_modeswitch 1.1.6, which is not yet proven to work. But I have a workaround package ready if anyone reports it not working. I think a few people should try this on either version of puppeee before consideration is given to merging it into a 4.4 beta.
If there is a better place for me to upload this package, just tell me. Thanks to all who try this out. Send me a pmodemdiag file if you encounter a problem.
UPDATE 2/1/2011: Updated the package (after download 36) with minor changes to /sbin/pup_event_background_modprobe and ..._protect, as well as to /usr/sbin/remasterpup2. No need for most people to take it, but those changes should go into the official puppeee. I bumped 9 to 10 to match the generic modem package level 10, reflecting the upgrade to support modeswitch 1.1.6, which was already in the 20110124 package.
UPDATE 2/9/2011: Updated the package (after download 52) with changes to 4 files: the 2 /sbin/pup-event...modprobe... scripts, the .../all-firmware/dgcmodem tarball and /etc/rc.d/rc.sysinit. Puppeee actually does not use that tarball, because the driver module is absent. But since DGC modems are USB types, that driver could be added to puppeee, even though most such modems are already supported by the cdc_acm driver. I would expect the DGC driver to support more functions (fax?), but have not confirmed that. If the driver is not added, then the tarball could be removed.
UPDATE 2/18/2011: Updated the package (after download 87) with a corrected pupdial, to address Toy4's problem with intermittant failures to connect with dialup. (The fix is to insert a "sync" command just before the wvdial command on line 688, for anyone who prefers to make that simple edit instead of reinstalling.)
Richard
Last edited by rerwin on Fri 18 Feb 2011, 22:14, edited 6 times in total.
jemimah,
You are welcome. I am reviewing the PCI-modem firmware tarballs to ensure they can handle the absence of the actual driver they support, in case such a modem is installed. I see that 4.4 contains several of the tarballs, but not the drivers. Do you foresee that some netbooks using puppeee (or fluppy) might contain built-in modems that would require the PCI drivers, such as the Agere, Lucent, HCF or HSF?
The slmodem tarball is necessary if a netbook has one of the ALSA modems, even though the PCI and USB drivers are not present. The tarball contains a daemon the ALSA modems would use. The larger question is whether a netbook would ever have a built-in modem.
With my soon-to-be-updated tarballs, it will not matter whether the drivers are present. But if you will never need support for such modems, you could remove the aforementioned tarballs, as well as udev rule file 60-dialup-modem.rules, since relates to only the Intel536/537, Agere and mwave modems.
Richard
You are welcome. I am reviewing the PCI-modem firmware tarballs to ensure they can handle the absence of the actual driver they support, in case such a modem is installed. I see that 4.4 contains several of the tarballs, but not the drivers. Do you foresee that some netbooks using puppeee (or fluppy) might contain built-in modems that would require the PCI drivers, such as the Agere, Lucent, HCF or HSF?
The slmodem tarball is necessary if a netbook has one of the ALSA modems, even though the PCI and USB drivers are not present. The tarball contains a daemon the ALSA modems would use. The larger question is whether a netbook would ever have a built-in modem.
With my soon-to-be-updated tarballs, it will not matter whether the drivers are present. But if you will never need support for such modems, you could remove the aforementioned tarballs, as well as udev rule file 60-dialup-modem.rules, since relates to only the Intel536/537, Agere and mwave modems.
Richard