Hi 01micko. Jim1911, bigpup et al,
I am using the "standard" Slacko RC2version with a Multi-session live-CD/DVD and my "Power-off" is working properly.
All continues to go well; except, unimportantly, I failed the IQ test on how best to use the Templates for Desktop icons.
My regards
PS 01micko wrote "... If not release will be delayed by several weeks, I've gotten way too busy in real life, timing couldn't be worse". I'd just like to say "thank you" to 01micko for all his great work with Puppies and also to say any decision of his is fine with me.
Slacko RC2
01micko ver1.02 works and is persistent in using the multi-sound card saved choices.01micko wrote: EDIT! jim3630.. I will post an older gnome-mplayer, I urgently need to know if it works, it does save the config
http://brainwavedesigncentral.net/micko ... 2-i486.pet
EDIT2: actually gmtk, a new dep for gnome-mplayer requires gconf to save configs properly, way too bloated to put in. I really don't like the way gnome-mplayer has gone, the 1.02 version posted should work ok, After that gnome 3 became the focus..
left two menu entries, gnome mplayer and gnome mplayer media player which fixmenus and restart jwm didn't fix.
thanks for your guidance and time and may God bless you in all your endeavors.
I'd rather see the official release come out later with less bugs, than having a rushed release with more bugs in it.01micko wrote: ... If not release will be delayed by several weeks, I've gotten way too busy in real life, timing couldn't be worse...
After all, the forum members still have the RC versions to play with while they are waiting. But in the end, it's your decision. Thanks for all of your efforts in pushing Puppy forward.
Alsawizard does not work for me in RC2 because /bin/getopt is missing.
Rename /bin/getopt-BB-not-used to /bin/getopt and Alsawizard works to change the default sound card. But after the first time, I have to run it twice to get the change.
This can be a workaround for gnome-mplayer not changing the sound card properly--use alsawizard to change the default and leave gnome-mplayer set to default sound card.
Multiple Sound Card Wizard did not work for me to change the default sound card.
gnome-mplayer 1.0.2 did not work for me to change the sound card.
Audacious did work for me to change the sound card.
Pmusic did work for me to change the sound card.
I have an m-audio 2496 which may be the reason that Multiple Sound Card Wizard and gnome-mplayer 1.0.2 did not work--it is a shifty card
----------------------------------------------------------------------------------------
Trying to install Gconf thinking that might cause gnome-mplayer 1.0.4 to save its Preferences, but Gconf gives error in downloading in PPM, and error installing if I manually downloaded the pet.
.
Rename /bin/getopt-BB-not-used to /bin/getopt and Alsawizard works to change the default sound card. But after the first time, I have to run it twice to get the change.
This can be a workaround for gnome-mplayer not changing the sound card properly--use alsawizard to change the default and leave gnome-mplayer set to default sound card.
Multiple Sound Card Wizard did not work for me to change the default sound card.
gnome-mplayer 1.0.2 did not work for me to change the sound card.
Audacious did work for me to change the sound card.
Pmusic did work for me to change the sound card.
I have an m-audio 2496 which may be the reason that Multiple Sound Card Wizard and gnome-mplayer 1.0.2 did not work--it is a shifty card
----------------------------------------------------------------------------------------
Trying to install Gconf thinking that might cause gnome-mplayer 1.0.4 to save its Preferences, but Gconf gives error in downloading in PPM, and error installing if I manually downloaded the pet.
.
Last edited by playdayz on Sun 23 Oct 2011, 20:14, edited 3 times in total.
I already confirmed that, but it's amazing that reports about core function issues often get overlooked whilst trivia and specialist stuff takes unreasonable attention.Alsawizard does not work for me in RC2
Whilst Puppy represents a remarkable suit of OS es, it's a shame that more time isn't spent on the boring aspects of polish and refinement. Too few developers with too narrow a range of HW and precious little spare time will always be the Achilles heel. For best market penetration, ignore the kiddies with the latest toys. Even now, some folks in the real world are still running 486 machines! Frankly, developers of compact distros would do well tell owners of multiple core, PAE, 2GHz GPU, cr*p to shove off - that sort of kit just isn't necessary to browse and send emails which still accounts for 90% of PC activity. The smartest coding gurus will be working on porting for ARM A7/A15 if they know their onions.
Hi all
sage I use some of that crap, mainly to compile things quickly and efficiently mainly for the benefit of others using puppy, please just stop making these sweeping generalizations about people who you don't know the first thing about.
yes puppy is used to keep older hardware alive, but what is the matter in using newer machines to achieve this??
mick if slacko has to be put on hold then so be it. your work and family should always come first, and you know I fully support and understand (well not always understand
) any descision that you make.
cheers
Don
sage I use some of that crap, mainly to compile things quickly and efficiently mainly for the benefit of others using puppy, please just stop making these sweeping generalizations about people who you don't know the first thing about.
yes puppy is used to keep older hardware alive, but what is the matter in using newer machines to achieve this??
mick if slacko has to be put on hold then so be it. your work and family should always come first, and you know I fully support and understand (well not always understand
) any descision that you make.cheers
Don
:D Testing PuppyPhone version 1.3PRE :D
Brookdale Intel video report
01micko,
I have not been following the development of slacko, so may be reporting what you already know. But this is the first that I have tried slacko, on my NetVista with the problematic Intel chipset. I find that the only way I can run slacko, beginning with a CD, is to choose "vesa" instead of "probe", and to reply "no" to the prompt for the special Brookdale treatment. Any other method results in a black screen.
Also, if I let the personal settings wizard restart X, I end up at the command prompt and cannot recover the desktop. So, I reply "no" to any offer to restart X. But my timezone change remains after a save-and-reboot. I assume other settings would remain, as well.
While troubleshooting this issue, I noticed that you have an old version of the i915.conf setup, which has been updated in lupu528. Although I found no improvement after installing it in slacko, I feel it could have some benefit. One of the factors may be random timing differences between bootups, since in lupu, the black screens occur occasionally.
The lupu528 version of the i915 conf and rules files removes 2 possible exposures. It avoids adding to the modprobe.d directory at initial bootup, where the change might not be "registered" in time to be used. It also ensures that module fbcon is loaded before i915, which is apparently a requirement. In case you can make the update to the RCs, I attach a package containing the new rules and conf file. Note that the old 00-i915_modeset0.rules file must be removed (as in the pinstall script), because the name changed slightly.
Two other minor issues I found:
1. The rules file 41-usb_modeswitch-puppy.rules file is obsolete and should be deleted.
2. Xwin can produce an error message when vesa is in use (as I have to do). It is caused by the presence of the vesa_drv.so in both /usr/lib/x and /usr/lib/xorg. Line 255 finds both copies, but expects only one hit. I suggest changing "/usr/lib" to "/usr/lib/xorg" for consistency with other puppies.
EDIT: This might be a clue to the i915 problem with xorg: When I choose "probe" during initial boot-up, select 1024x768 and "test", the screen goes black for a minute, until the wizard screen reappears, but with the refresh-rate and frequency values missing! And the driver is "intel" (although if I were to change to "intel", messages would imply that i810 was the driver -- and i810 is not offered in the choice list).
Richard
I have not been following the development of slacko, so may be reporting what you already know. But this is the first that I have tried slacko, on my NetVista with the problematic Intel chipset. I find that the only way I can run slacko, beginning with a CD, is to choose "vesa" instead of "probe", and to reply "no" to the prompt for the special Brookdale treatment. Any other method results in a black screen.
Also, if I let the personal settings wizard restart X, I end up at the command prompt and cannot recover the desktop. So, I reply "no" to any offer to restart X. But my timezone change remains after a save-and-reboot. I assume other settings would remain, as well.
While troubleshooting this issue, I noticed that you have an old version of the i915.conf setup, which has been updated in lupu528. Although I found no improvement after installing it in slacko, I feel it could have some benefit. One of the factors may be random timing differences between bootups, since in lupu, the black screens occur occasionally.
The lupu528 version of the i915 conf and rules files removes 2 possible exposures. It avoids adding to the modprobe.d directory at initial bootup, where the change might not be "registered" in time to be used. It also ensures that module fbcon is loaded before i915, which is apparently a requirement. In case you can make the update to the RCs, I attach a package containing the new rules and conf file. Note that the old 00-i915_modeset0.rules file must be removed (as in the pinstall script), because the name changed slightly.
Two other minor issues I found:
1. The rules file 41-usb_modeswitch-puppy.rules file is obsolete and should be deleted.
2. Xwin can produce an error message when vesa is in use (as I have to do). It is caused by the presence of the vesa_drv.so in both /usr/lib/x and /usr/lib/xorg. Line 255 finds both copies, but expects only one hit. I suggest changing "/usr/lib" to "/usr/lib/xorg" for consistency with other puppies.
EDIT: This might be a clue to the i915 problem with xorg: When I choose "probe" during initial boot-up, select 1024x768 and "test", the screen goes black for a minute, until the wizard screen reappears, but with the refresh-rate and frequency values missing! And the driver is "intel" (although if I were to change to "intel", messages would imply that i810 was the driver -- and i810 is not offered in the choice list).
Richard
- Attachments
-
- i915-lupu528_version-1.pet
- Lucid Pup version of i915 handling of Brookdale Intel-video chipsets
- (1.54 KiB) Downloaded 241 times
Last edited by rerwin on Sun 23 Oct 2011, 21:33, edited 1 time in total.
What mess?Sage wrote:- self explanatory! You end up with the present mess! A few less lemmings on this planet would solve a lot of problems.what is the matter in using newer machines to achieve this??
Puppy Linux Blog - contact me for access
inter aliaWhat mess?
Despite the helpful little panel that springs up warning about SiS chipset issues, neither 'Yes' + dedicated drivers nor 'No' produces an XOrg picture. VESA works, though. This continues to be the only variant, or any other distro including Slackcentral, that refuses to detect/work with the SiS Mirage chipset. There must be a simple answer somewhere? Sadly not my department to understand these matters.
Retrovol settings are half-cock: please turn everything ON by default. Notwithstanding, Woofwoof still doesn't work when I turn up the wick. I noticed that this stopped working on new Wary and reported it. Must be a Woof issue?
Confirm that ALSAWizard not working, vide supra.
Third time of asking: please can the localisation panel be cast with consistency: presently, we have US peripherals with Perth time. Is it asking too much to settle on GMT, even for an American developer! That does not make things easy for Brits if that causes mental strife for Yankies because we are on BST right now.
I don't see any mention of a development thread. Time to start listening to your target audience - the great unwashed users. Without them sine qua non.Forum index » Advanced Topics » Puppy Projects
Slacko RC2
Use an email or PM if you want to exchange intricate technical details, that's what BK does and he runs an open blog, too.
Actually I'll explain.01micko wrote: What mess?
This release is way over due. People come to expect the latest since Lupu set such a high benchmark. Delay is bad for that.
The sound wizard bug is probably the worst. Nothing else has changed. My fault entirely. No excuses.
Changes have been very minimal since B4. If something isn't working now and did in B4 then that is a bit of a shock. I have always maintained that the 2.6.37.6 version is the main version and the other offered as demand warranted. Most bugs are common to both, of course there will be different kernel bugs.. if the kernel devs had perfected the kernel then there would be no need for updates.
I'm not going to go through a big bunch of RC's. as a matter of fact release would of happened a week ago if I didn't have to go away for near 2 weeks working.
This has been a very long and tedious process which I have enjoyed and would hope that I have handled well. We are nearing completion, but in saying that.. does the job ever end? Of course not!
Cheers
PS: Sage I listen to everything, but of course some of it is noise.
PPS: This project is in it's infancy.. (gestation period?). It can't mature until it is born.
Puppy Linux Blog - contact me for access
slacko RC++ sys pic below is for comparison sake.
the lattest cut down dpups including geek pups that are a waste of time for the uninitiated or newbies unless you want to learn code, compiling, and kernels cannot boast of better resource use on my system at least.
01micko some begrudge your time spent on RC++ even though long term support is already provided in official puppies dedicated to older computers. RC++ is far less buggy than others and as said everything I use works.
looking only at this thread and several didn't post which version they are using but best can tell more problems are with k2.6.37.6 users. Thus, less time required to polish up those few RC++ users and could post as finale.
--------
once past EDC c-section saves lives.
the lattest cut down dpups including geek pups that are a waste of time for the uninitiated or newbies unless you want to learn code, compiling, and kernels cannot boast of better resource use on my system at least.
01micko some begrudge your time spent on RC++ even though long term support is already provided in official puppies dedicated to older computers. RC++ is far less buggy than others and as said everything I use works.
looking only at this thread and several didn't post which version they are using but best can tell more problems are with k2.6.37.6 users. Thus, less time required to polish up those few RC++ users and could post as finale.
--------
once past EDC c-section saves lives.
- Attachments
-
- slacko.png
- (5.12 KiB) Downloaded 968 times
-
MinHundHettePerro
- Posts: 852
- Joined: Thu 05 Feb 2009, 22:22
- Location: SE
After conception, it's alive01micko wrote:PS: Sage I listen to everything, but of course some of it is noise.
PPS: This project is in it's infancy.. (gestation period?). It can't mature until it is born.
. Upon birth, the horrific possibility of a miscarriage is obliterated ................. 
.omnes lectores
The thoughtless European user of a nationalised keyboard would extrapolate the nationalisation of k/b layouts to encompass the world at large - the sage knows that the lion part of non-European users utilise (how horrid the thought) US keyboards ............
quidquid
/ MHHP[color=green]Celeron 2.8 GHz, 1 GB, i82845, many ptns, modes 12, 13
Dual Xeon 3.2 GHz, 1 GB, nvidia quadro nvs 285[/color]
Slackos & 214X, ... and Q6xx
[color=darkred]Nämen, vaf....[/color] [color=green]ln -s /dev/null MHHP[/color]
Dual Xeon 3.2 GHz, 1 GB, nvidia quadro nvs 285[/color]
Slackos & 214X, ... and Q6xx
[color=darkred]Nämen, vaf....[/color] [color=green]ln -s /dev/null MHHP[/color]
seamonkey open containing folder
Small glitch with seamonkey and fix by trapster here
http://murga-linux.com/puppy/viewtopic.php?t=72772
http://murga-linux.com/puppy/viewtopic.php?t=72772
Hi 01micko
From a n00b user viewpoint rc2 is a very good and very usable puppy.
I prefer rc2++ because it seems slightly faster and seems to use fewer resouces than rc2. Presume later kernel helps.
Running on my 8/9yr old Laptop - Acer TravelMate 243LC.
256mb ram, 2.5Ghz Celeron Proc, 800mb swap partition,
manual frugal to sda1 ext3. Wifi via Belkin pcmcia card.
Overall a luvly puppy - many thanks for all you do - much appreciated.
Very best regards - Ray
From a n00b user viewpoint rc2 is a very good and very usable puppy.
I prefer rc2++ because it seems slightly faster and seems to use fewer resouces than rc2. Presume later kernel helps.
Running on my 8/9yr old Laptop - Acer TravelMate 243LC.
256mb ram, 2.5Ghz Celeron Proc, 800mb swap partition,
manual frugal to sda1 ext3. Wifi via Belkin pcmcia card.
Overall a luvly puppy - many thanks for all you do - much appreciated.
Very best regards - Ray
-
Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
Some of the Lucid tips have been updated for Slackoplaydayz wrote:Even right out of the gate Slacko is an advance on Lupu, since it has a much more advanced infrastructure and from what I have seen it is already the cleanest Puppy ever.
http://puppylinux.org/wikka/SlackoTips
What happens when pemasu gets hold of Slacko?
What will he call his beautification process?
Will Ttuuuxx strip it to below 100MB?
Will Iguleder compile it for ARM?
. . . Slacko . . . is just the beginning . . .
Conference calling, support and full refunds are now available with free phone facility
http://puppylinux.org/wikka/PuppyPhone
How does the version numbering work in Slacko?
RC1 is 5.29.5
RC2 is 5.2.97
A bit confusing for a noob.
ps I've been using RC1 (live CD, savefile on NTFS HDD) for a while, tried RC2 (live cd) a couple of time but for some undefinable reason I'm not happy with it although I had no problems. I've gone back to RC1 (offers to upgrade the 2fs file). Old Toshiba laptop.
RC1 is 5.29.5
RC2 is 5.2.97
A bit confusing for a noob.
ps I've been using RC1 (live CD, savefile on NTFS HDD) for a while, tried RC2 (live cd) a couple of time but for some undefinable reason I'm not happy with it although I had no problems. I've gone back to RC1 (offers to upgrade the 2fs file). Old Toshiba laptop.