Slacko Beta 1
refering to yesterdays's message http://murga-linux.com/puppy/viewtopic. ... &start=142
I confirm your comments about folder icon mismatching and its presence in other puppies.
The xf86-input-synaptics-xf86-input-synaptics-1.499.1-i486.pet of Aug 19 did not fix my synaptics touchpad behavior and introduced more serious problems, likely a minor fix for you. I will PM you some diagnostics.
Thanks!
I confirm your comments about folder icon mismatching and its presence in other puppies.
The xf86-input-synaptics-xf86-input-synaptics-1.499.1-i486.pet of Aug 19 did not fix my synaptics touchpad behavior and introduced more serious problems, likely a minor fix for you. I will PM you some diagnostics.
Thanks!
pupdial password
I can't enter password in pupdial. Got online using pppd-scripts.
Dave, I may have made a booboo, type libxcb* in PPM searchbox, I did see the behaviour and now it's gone. You got mesa installed?DaveS wrote:Ah Ah... same flashy flashy stuff01micko wrote:Dave .. you can retrofit
Go to PPM and type "xcb*" in the search box, then choose xcb-utils, restart X when complete, it's only a small lib
Actually , my radeon was rendering like absolute garbage without the libs, added libs, improvement, added mesa, more improvement, added fglrx driver, perfect rendereing.
On my Brookdale, despite the problems, once they were overcome the rendering was perfect ootb.
-
aarf, I haven't had a problem with my wireless usb modem.. that's what you meant eh? Or are you mobile phone or wireless network?
-
rodin.s, it may be latest gtkdialog, I noticed too, closed pupdial, reopened and it was ok,.. NO, just checked, seems Password entry is broken, ok time to rewrite Pudial.. it's awful on small screens, this has been on my todo list for a long time.
EDIT: Actually, you can enter the password, but just can't see it! Will explore new syntax.
-
JonT, I'll remove that attachment and confiscate my son's laptop! (at least for today)
Last edited by 01micko on Sat 20 Aug 2011, 21:40, edited 2 times in total.
Puppy Linux Blog - contact me for access
Re: petget freeze
Hi shinobarshinobar wrote:Petget freezes at installing any pets under PUPMODE=13(flash).
It freezes at line 230 in installpkg.sh:Slacko alpha and also beta 1.Code: Select all
busybox mount -t aufs -o remount,udba=reval unionfs / #remount with faster evaluation mode.
I have pupmode 13 on my eee pc and I can install pets ok, I can too on my problematic Brookdale machine with broken CD, so easiest way to test is with usb install from stick, 13. I'll do further tests. I see you mention the code, can you suggest alternative code?
Cheers
Puppy Linux Blog - contact me for access
Tried that... made no difference. I dont have Mesa installed, just generic Intel laptop built in graphics. Actually, the rendering is excellent. There is just something very strange going on between X and Rox. Have never seen this behavior in a Puppy before. It only happens if I move a file between two windows or move a desktop icon. In all other situations, including dragging windows around, the rendering is dead stable.
Spup Frugal HD and USB
Root forever!
Root forever!
aarf wrote:slacko b1 getting disconnects and reconnect as different sdxx on usb connected things. sometimes also happens when copy/move is in progress.
529 has it too.
this was a long ago problem that was solved previously.
no sorry, i mean my external usb storage harddrive.01micko wrote:
aarf, I haven't had a problem with my wireless usb modem.. that's what you meant eh? Or are you mobile phone or wireless network?
have tested usb wireless N here. (failed to connect on slacko beta1 among other puppies)
havent tested my mobile phone or phone connection.
mave.. on the todo list, however many from wary/lupq will work. There are NLS files for major progs in PPM
_
onto Pupdial,
I have shrank it and fixed syntax errors, it now fits on my eee screen res, 800x480, though the "CHOOSE" GUI (modem test, delete etc) looks atrocious on the eee
Note the error rodin.s was getting is the expected behaviour according to the gtkdialog examples.. . However there is a proper way discovered by jemimah.. ..and in Frisbee, (yes I'll get to that).(Update, no, I think Dougal was using that and HairyWill)
I have only hacked the gtkdialog code, I'm 99.9% certain I haven't altered any underlying pupdial code.
Test reports please.
Instructions:
EDIT.. ok, I fixed the CHOSE thing, simple notebook, according to xwininfo it should fit snuggly on the eee screen.
_
onto Pupdial,
I have shrank it and fixed syntax errors, it now fits on my eee screen res, 800x480, though the "CHOOSE" GUI (modem test, delete etc) looks atrocious on the eee
Note the error rodin.s was getting is the expected behaviour according to the gtkdialog examples.. . However there is a proper way discovered by jemimah..
Code: Select all
<visible>password</visible>
I have only hacked the gtkdialog code, I'm 99.9% certain I haven't altered any underlying pupdial code.
Test reports please.
Instructions:
Code: Select all
# gunzip pupdial.gz
# chmod 755 pupdial
# cp -f /usr/sbin/pupdial /usr/sbin/pupdia.bak #makes backup
# cp -af pupdial /usr/sbin #overwrites old pudial, preserves permissions
- Attachments
-
- modemprobe.gz
- same instructions for pupdial.. obviously making the sub
- (4.5 KiB) Downloaded 557 times
-
- modemprobe.diff.gz
- for the geekerati
- (256 Bytes) Downloaded 545 times
-
- pupdial.gz
- The MAIN file
- (9.23 KiB) Downloaded 551 times
-
- pupdial.diff.gz
- just a diff for geeks' perusal, NO NEED to download
- (1.77 KiB) Downloaded 517 times
Last edited by 01micko on Sun 21 Aug 2011, 02:20, edited 2 times in total.
Puppy Linux Blog - contact me for access
Re: petget freeze
Tnx mick for testing.01micko wrote:Hi shinobarshinobar wrote:Petget freezes at installing any pets under PUPMODE=13(flash).
It freezes at line 230 in installpkg.sh:Slacko alpha and also beta 1.Code: Select all
busybox mount -t aufs -o remount,udba=reval unionfs / #remount with faster evaluation mode.
I have pupmode 13 on my eee pc and I can install pets ok, I can too on my problematic Brookdale machine with broken CD, so easiest way to test is with usb install from stick, 13. I'll do further tests. I see you mention the code, can you suggest alternative code?
Cheers
It seems hardware specific...
My 2 PCs freeze but another 1 PC is no problem.
The freezing 2 PCs are intel X38 and intel P45, both have Nvidia GeForce 8800 GTX, and may have marvel ide bridge.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
Slacko Beta 1
sszindian wrote:
Spup-312.37 let me probe and select my screen resolution of 1440x900 in xorg, beautiful desktop!
Slacko-4.99.1 Lets me probe and select 1440x900 from list but... when it loads, it auto puts me in 'versa' instead of xorg with a resolution of 1224x1224. I select the xorg feature it suggests after that, again, probe, select 1440x900, again gives me only 1224x1224 with no 1440x900 option.
This makes the screen way to large for monitor and desktop icons (top ones) are half hid 'off screen'.
----------------------------------------------------------------------------------------------
01micko wrote:
indian.. it's most likely xcb.. search PPM for it, install it restart X, It was an oversight when converting from last woof, sorry!..
----------------------------------------------------------------------------------------------
Copied and installed:
xcb <-- http://mirror.aarnet.edu.au/pub/slackwa ... i486-1.txz
----------------------------------------------------------------------------------------------
Does not appear to make any difference, same screen problem remains?
>>>---Indian------>
Spup-312.37 let me probe and select my screen resolution of 1440x900 in xorg, beautiful desktop!
Slacko-4.99.1 Lets me probe and select 1440x900 from list but... when it loads, it auto puts me in 'versa' instead of xorg with a resolution of 1224x1224. I select the xorg feature it suggests after that, again, probe, select 1440x900, again gives me only 1224x1224 with no 1440x900 option.
This makes the screen way to large for monitor and desktop icons (top ones) are half hid 'off screen'.
----------------------------------------------------------------------------------------------
01micko wrote:
indian.. it's most likely xcb.. search PPM for it, install it restart X, It was an oversight when converting from last woof, sorry!..
----------------------------------------------------------------------------------------------
Copied and installed:
xcb <-- http://mirror.aarnet.edu.au/pub/slackwa ... i486-1.txz
----------------------------------------------------------------------------------------------
Does not appear to make any difference, same screen problem remains?
>>>---Indian------>
Cloud Computing For Every Puppy (a .pet)
[url]http://murga-linux.com/puppy/viewtopic.php?t=69192[/url]
[url]http://murga-linux.com/puppy/viewtopic.php?t=69192[/url]
new pupdial
New pupdial works.
X restart Problem
Hello,
I only remembered that I should submit a bug report somewhat after-the-fact, so I'm sorry for not posting this sooner. I am having a problem with regards to starting X. If I select probe at the xorg wizard window and go straight into the desktop, X will boot just fine unless I have to do a restart. If I have to restart, X will turn over, I will see the cursor for a few seconds, and my screen will dissolve into weird multicolored lines. Hitting control Alt backspace does not work, and so far I have been forced to do a hard reboot whenever this happens. If I select “test" at the resolution setup menu, the test will run just fine, but I will encounter the same problem that I do as when I have to restart X. I attempted to manually select the graphics card that I use, but I noticed that the one which I normally use doesn't appear to be in the menu anymore. I am running the latest Slacko beta version on a Dell latitude D610 laptop, 1.73 GHz, 500 megs of RAM with a Radeon mobility X300 graphics card with 64 megs of memory. In Lucid, I normally manually selected the radeonhd driver at start up. I should also mention that in previous attempts with this version of Slacko, Xvesa didn't work either. However, it normally worked on this computer in Lucid 5.25.
Yours,
--S
I only remembered that I should submit a bug report somewhat after-the-fact, so I'm sorry for not posting this sooner. I am having a problem with regards to starting X. If I select probe at the xorg wizard window and go straight into the desktop, X will boot just fine unless I have to do a restart. If I have to restart, X will turn over, I will see the cursor for a few seconds, and my screen will dissolve into weird multicolored lines. Hitting control Alt backspace does not work, and so far I have been forced to do a hard reboot whenever this happens. If I select “test" at the resolution setup menu, the test will run just fine, but I will encounter the same problem that I do as when I have to restart X. I attempted to manually select the graphics card that I use, but I noticed that the one which I normally use doesn't appear to be in the menu anymore. I am running the latest Slacko beta version on a Dell latitude D610 laptop, 1.73 GHz, 500 megs of RAM with a Radeon mobility X300 graphics card with 64 megs of memory. In Lucid, I normally manually selected the radeonhd driver at start up. I should also mention that in previous attempts with this version of Slacko, Xvesa didn't work either. However, it normally worked on this computer in Lucid 5.25.
Yours,
--S
I'm trying out Slacko on the Pentium D machine, and have found that while my Netgear WN111v2 USB wireless dongle works on a pfix=ram boot, it doesn't when booting from a pupsave. It works fine in XP and Luci/Lupu.
I've noticed that when the dongle isn't working, there are some modules not shown in the Kernel Modules screen in HardInfo:-
aes-generic
arc4
ecb
ar9170usb
These all appear to be connected with making the dongle work and the fact that they're not listed when rebooting would probably explain the non-functioning network connection.
Interestingly, there is one module listed in the pupsave boot that doesn't appear in pfix=ram - carl9170.
I've noticed that when the dongle isn't working, there are some modules not shown in the Kernel Modules screen in HardInfo:-
aes-generic
arc4
ecb
ar9170usb
These all appear to be connected with making the dongle work and the fact that they're not listed when rebooting would probably explain the non-functioning network connection.
Interestingly, there is one module listed in the pupsave boot that doesn't appear in pfix=ram - carl9170.
- Attachments
-
- nww_pfram.png
- Network Wizard window on a pfix=ram boot. wlan0 is present, and wireless networking works.
- (19.17 KiB) Downloaded 1081 times
-
- nww_rbt.png
- Network Wizard after booting using a pupsave. Note that there is no internet connection and wlan0 has vanished.
- (21.72 KiB) Downloaded 1250 times
Zhaan - AMD K6 2 500, 512MB RAM, ATI Rage 128 VR. Full install Wary 5.5 [url=http://tinyurl.com/dy66kh8]HardInfo Report[/url]
Merlin - Core i5-4590, 8GB RAM, Radeon R9 270X. Slacko 5.7.0
Merlin - Core i5-4590, 8GB RAM, Radeon R9 270X. Slacko 5.7.0
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Yep, that was fixed in Woof August 15. See:vanchutr wrote:Slacko beta 1 boot from USB-Flash (without hard disk).
(The other (new) puppy (puppies) can't. e.g midnightsun 003, snowpup 020, icepup 15, wary 513, dpup exprimo x 3).
Thank you, 01micko
(I can't boot up my computer with other puppies because there isn't a hard disk.)
Slacko beta 1 load sfs files faster than other puppies. I can connect to internet via my USB-3G modem (Huawei HPSA - E173Eu-1)
Load and run smoothly these apps : TeXlive 2010, Java u_26, Libre-Office, Lazarus - FreePascal -, KDE-K3b and Amarok. These apps were loaded with sfs_load.
Thank you again
http://bkhome.org/blog/?viewDetailed=02409
I think that 01micko is currently using Woof uploaded on Aug 17, so Slacko has the fix.
[url]https://bkhome.org/news/[/url]
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
I don't think that we can compile that driver with any Xorg past version 7.3. That's why you have to use Wary Puppy if you want the i810 Xorg driver (Wary has Xorg 7.3).rjbrewer wrote:Slacko doesn't have the i810 driver, which is best for some Pent.
M laptops with 855gm graphics.
[url]https://bkhome.org/news/[/url]
Thanks for report Jades
That could be something to do with some of the kernel scripts, not sure. However when depmod is run it should update all modules. I'll look into it.
-
sfoster
That is an older radeon that may need "modeset =1" on the kernel line, try booting "puppy nomodest pfix=ram" or (I think) "puppy radeon modeset=1 pfix=ram" to see if that helps. My older radeon worked ootb as does my newer, I thought my older one would bork. I think forum member yarddog has an older radeon, he may tell us his experience one day soon.
-
thanks rodin.s for confirming my pupdial hack is ok
--
sszindian.. strange.. the next beta will have all the stuff 312.37 had ootb for xorg, hopefully that fixes that issue.
-
drblock2, reported to Clarf, pnethood maintainer and he is thankful of the report, I guess he'll update pnethood soon.
-
Thanks zigbert, hopefully Barry will place it in the new "common" repo for all puppy distros.
-
shino, still strange it happens with 2 pc's, I'll pop my nvidia card back in my machine and see if that is an issue. Are you using nv driver or nvidia? [even nouveau, it is in the repo](I wouldn't think that would matter but you never know)
-
Barry, yes we use woof-110817.. I always put which woof in the first post description or the first post it's self
That could be something to do with some of the kernel scripts, not sure. However when depmod is run it should update all modules. I'll look into it.
-
sfoster
That is an older radeon that may need "modeset =1" on the kernel line, try booting "puppy nomodest pfix=ram" or (I think) "puppy radeon modeset=1 pfix=ram" to see if that helps. My older radeon worked ootb as does my newer, I thought my older one would bork. I think forum member yarddog has an older radeon, he may tell us his experience one day soon.
-
thanks rodin.s for confirming my pupdial hack is ok
--
sszindian.. strange.. the next beta will have all the stuff 312.37 had ootb for xorg, hopefully that fixes that issue.
-
drblock2, reported to Clarf, pnethood maintainer and he is thankful of the report, I guess he'll update pnethood soon.
-
Thanks zigbert, hopefully Barry will place it in the new "common" repo for all puppy distros.
-
shino, still strange it happens with 2 pc's, I'll pop my nvidia card back in my machine and see if that is an issue. Are you using nv driver or nvidia? [even nouveau, it is in the repo](I wouldn't think that would matter but you never know)
-
Barry, yes we use woof-110817.. I always put which woof in the first post description or the first post it's self
Puppy Linux Blog - contact me for access
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Woof has the "Sound Wizard" (Click "setup" icon on desktop, then choose "Setup ALSA Sound"), which describes simple steps to test and get sound working.01micko wrote:Lobster
Try this;Choose the first entry, click ok, do not rebootCode: Select all
Multiple-Sound-Card-Wizard
then;in that terminal 2 variables will be echoed.then you see an errorCode: Select all
Card=0 Device=0
Ignore the error; I'll fix it later;Code: Select all
cp: cannot stat `/etc/asound.conf': No such file or directory rm: cannot remove `/etc/asound.conf': No such file or directory
then; run thisthat will restart alsa with correct sound parameters.. if you got 2barks at boot at pfix=ram then you will get 2 barks when you run this:Code: Select all
# /etc/init.d/10alsa restart
__________Code: Select all
# aplay /usr/share/audio/2barks.wav
I have to intercept running of the alsawizard. It should only be necessary with old ISA cards which were very good in their day but are rare in modern HW. (Actually they are much better than the crappy sound chips of today, for good audio these days you need to fork out the moolah).
Basically, if retrovol is running, whether you can hear it or not, alsa is running and has set up sound.
The best avenue then to pursue is either:
right clicking the retrovol icon in the tray and selecting "Full Window", check the boxes that you think are needed, then exit, hopefully things are ok (pizasgood's little proggy is effective though a little confusing)
or
Run "alsamixer" in the terminal and adjust settings with arrow keys. Be aware that some things will be switched off, There is an input source setting on many built in (to motherboard) modern sound cards that toggles whether you want surround sound or front mic or rear mic, use the arrow keys to adjust this. You may need to hit the TAB key (no, a diet cola will not be forthcoming) to see this setting.
We then need a pawdcast!
If anyone comes up with improvements in those steps, patching that file would be the best way to go (script /usr/sbin/alsawizard).
[url]https://bkhome.org/news/[/url]