Wary Puppy 0.9.4 (094) feedback

[ttuuxxx]

[
It does "just work" now, but it didn't until I'd installed those 2 usb-modemswitch pets that ttuuxxx pointed out. (I'm just checking in case you believe they were not necessary when they were.) In a pristine Wary on its first run I deliberately left the wvdial APN box blank to see what would happen, and it still connected okay to the CJ network.. It's a voda modem that I set up with a Crazy Johns profile in XP. So am I correct in inferring that a blank APN causes it to default to the most recent profile in the modem?

Wow glad that 32kb total extra was enough to fix your issue, its kind of cool that so many other modems can use those 2 small pets also.
ttuuxxx

[BarryK]

In Wary, what is the CLI mimencode utility known as? Or what is the nearest base64 encoder?

I don't think we have one. We do have 'metamail', which if memory serves me correctly can read base64 encoded mail attachments (?)

Oh, I just remembered, had a mental block before. Puppy has 'uuencode' and 'uudecode', Busybox applets.

[glenco]

No luck with my Pctel according to XP & W2K or ttySL0 according to my working puppy 4.21 full install.
I did a full install of 094 to my HD and installed the new –4 pet and still no modem.

[rerwin]

glenco,
Did you also do a CHOOSE > ERASE in pupdial after installing "-4"? This is necessary to activate the fix for the PcTels. Then reboot to see the effect. Do this even if no modem is shown as detected.
Richard

[glenco]

glenco,
Did you also do a CHOOSE > ERASE in pupdial after installing "-4"? This is necessary to activate the fix for the PcTels. Then reboot to see the effect. Do this even if no modem is shown as detected.
Richard

Well rerwin
I have good news and I have bad news. LOL
The good news is probe worked on yet another fresh full HD install following your post to a tee.
The bad news is listed below.
I also attached a new diag I created after the errors.

Code: Select all

--> WvDial: Internet dialer version 1.53
--> Cannot open /dev/ttySL0: Device or resource busy
--> Cannot open /dev/ttySL0: Device or resource busy
--> Cannot open /dev/ttySL0: Device or resource busy

------------------------------------------------------

Welcome to PupDial, originally written by Barry Kauler and enhanced by Richard Erwin for Puppy Linux.

There is a configuration file, /etc/wvdial.conf, that is read by
PupDial, and changes made to any of the above boxes will be saved
to wvdial.conf when you click the 'Exit' or 'Connect' buttons.
Note, you can also manually edit wvdial.conf with a text editor.

Some computers have two modems, perhaps one on the motherboard,
and Puppy may have detected the wrong one. In that case, click the
'probe' button. If it is still wrong, manually edit wvdial.conf.


--> WvDial: Internet dialer version 1.53
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
OK
--> Modem initialized.
--> Sending: ATX3DT9083735
--> Waiting for carrier.
ATX3DT9083735
NO CARRIER
ERROR
--> No Carrier!  Trying again.
--> Sending: ATX3DT9083735
--> Waiting for carrier.
ATX3DT9083735
NO CARRIER
ERROR
--> No Carrier!  Trying again.
--> Sending: ATX3DT9083735
--> Waiting for carrier.
ATX3DT9083735
NO CARRIER
ERROR
--> No Carrier!  Trying again.
--> Sending: ATX3DT9083735
--> Waiting for carrier.
ATX3DT9083735
NO CARRIER
ERROR
--> No Carrier!  Trying again.
--> Sending: ATX3DT9083735
--> Waiting for carrier.
ATX3DT9083735
NO CARRIER

[Billtoo]

My Radeon hd3200 9610 is supported by the pet that you made but
although I could get to the desktop there were problems with it.


# fglrxinfo
fglrxinfo: error while loading shared libraries: libatiuki.so.1:
cannot open shared object file: No such file or directory
# report-video
VIDEO REPORT: Wary Puppy, version 094

Chip description:
oem: ATI ATOMBIOS
product: RS780 01.00

Driver used by Xorg:
radeon

Video mode used by Xorg:
Resolution: Depth 24 Depth: "Display"

...the above also recorded in /tmp/report-video
#
The ati_fglrx-10.10-k2.6.31.14-w5.pet was installed when the above
messages happened.
After installing the pet and rebooting an ATI X video settings option
showed up in the setup menu but clicking on it did nothing.
The games on the hard disk that need hardware acceleration don't start.

I exited to the prompt and a message "out of range" came up on the
screen and I had to reboot.

*******************************************************************************

I already had the kernel source sfs and the devx sfs installed and I
had downloaded the ati-driver-installer-10-10-x86.x86_64.run file so I
rebooted with puppy "pfix=nox" and when it came to the prompt I
installed the commercial driver and entered "aticonfig" and then "xwin"
to get back to the desktop.
The games on the hard disk that need accelerated graphics work now.
I can also exit to the prompt and go back to the desktop with xwin now.

So it's no go with the pet on this pc, I have 2 others in the hd 5000
series but they aren't in the list of supported cards for the pet but
installing the ati-driver-installer-10-10-x86.x86_64.run file works on
them too.
# report-video
VIDEO REPORT: Wary Puppy, version 094

Chip description:
oem: ATI ATOMBIOS
product: RS780 01.00

Driver used by Xorg:
#card0driver

Video mode used by Xorg:
Resolution: Depth 24 Depth: "Display"

...the above also recorded in /tmp/report-video
#
The above shows up in report-video after the commercial driver is installed.

[BarryK]

# fglrxinfo
fglrxinfo: error while loading shared libraries: libatiuki.so.1:
cannot open shared object file: No such file or directory

Ah, a symlink is missing. Do this after installing the PET:

# ln -s libatiuki.so.1.0 /usr/lib/libatiuki.so.1

I will fix this in the PET pkg.

Thanks for testing this.

[BarryK]

Billtoo,
It looks like you need to do these too:

# cd /usr/X11R7/lib
# ln -s libAMDXvBA.so.1.0 libAMDXvBA.so.1
# ln -s libfglrx_dm.so.1.0 libfglrx_dm.so.1
# ln -s libfglrx_gamma.so.1.0 libfglrx_gamma.so.1
# ln -s libGL.so.1.2 libGL.so.1
# ln -s libXvBAW.so.1.0 libXvBAW.so.1

[Billtoo]

Billtoo,
It looks like you need to do these too:

# cd /usr/X11R7/lib
# ln -s libAMDXvBA.so.1.0 libAMDXvBA.so.1
# ln -s libfglrx_dm.so.1.0 libfglrx_dm.so.1
# ln -s libfglrx_gamma.so.1.0 libfglrx_gamma.so.1
# ln -s libGL.so.1.2 libGL.so.1
# ln -s libXvBAW.so.1.0 libXvBAW.so.1

# ln -s libatiuki.so.1.0 /usr/lib/libatiuki.so.1
# cd /usr/X11R7/lib
# ln -s libAMDXvBA.so.1.0 libAMDXvBA.so.1
# ln -s libfglrx_dm.so.1.0 libfglrx_dm.so.1
# ln -s libfglrx_gamma.so.1.0 libfglrx_gamma.so.1
# ln -s libGL.so.1.2 libGL.so.1
ln: creating symbolic link `libGL.so.1': File exists
# ln -s libXvBAW.so.1.0 libXvBAW.so.1
#
#
# report-video
VIDEO REPORT: Wary Puppy, version 094

Chip description:
oem: ATI ATOMBIOS
product: PARK 01.00

Driver used by Xorg:
vesa

Video mode used by Xorg:
Resolution: Depth 24 Depth: "Display"

...the above also recorded in /tmp/report-video
#
Will reboot now:
# report-video
VIDEO REPORT: Wary Puppy, version 094

Chip description:
oem: ATI ATOMBIOS
product: PARK 01.00

Driver used by Xorg:
vesa

Video mode used by Xorg:
Resolution: Depth 24 Depth: "Display"

...the above also recorded in /tmp/report-video
#
I tried exiting to the prompt and entering "aticonfig --initial" and
then "xwin" but x wouldn't start.
The only way I could get back to the desktop was with xvesa.

I saw that my laptop was on the revised list so this is the result of trying to install the pet on it.

no success yet.

[rerwin]

I have added the latest DGC (USB) and HCF modem drivers to the modem update package 4 posted here:
http://www.murga-linux.com/puppy/viewto ... 900#461900
More details there.

Since I do not have an HCF modem for testing, please try the new driver if you have such a modem (other that the riptide combos, which are not supported). Thanks.
Richard

[Shep]

In Wary, what is the CLI mimencode utility known as? Or what is the nearest base64 encoder?

I don't think we have one. We do have 'metamail', which if memory serves me correctly can read base64 encoded mail attachments (?)

Oh, I just remembered, had a mental block before. Puppy has 'uuencode' and 'uudecode', Busybox applets.

Ah, I'd never have expected to find base64 incorporated into uuencode. Thanks for pointing that out.

In the meantime, I tried copying the minencode binary from another over to Wary and found it works okay.

[Billtoo]

I started with a fresh install of 094 on a 4gb flash drive and on
first boot I just setup the network etc. and then rebooted to create
the save file.
On the second bootup I downloaded the new ati pet and installed it,
then rebooted.
Now there was a new entry in the setup menu but clicking on that gave
an error, see attached file errorscrn.jpg
I exited to the prompt and entered "aticonfig --initial" and then xwin
to restart x.
# report-video
VIDEO REPORT: Wary Puppy, version 094

Chip description:
oem: ATI ATOMBIOS
product: REDWOOD 01.00

Driver used by Xorg:
#card0driver

Video mode used by Xorg:
Resolution: Depth 24 Depth: "Display"

...the above also recorded in /tmp/report-video
# Clicking on the new entry in the setup menu doesn't do anything
*but* clicking on one of the game files on the hard drive that
requires accelerated graphics works so the pet is working but needs
the extra step of "aticonfig --initial" at the command prompt then
xwin.
This is on my newest desktop with an ati radeonhd 5570 graphics card.

Edit:
The same method works on my laptop which has ATI Mobility Radeon
HD5470 graphics.

# report-video
VIDEO REPORT: Wary Puppy, version 094

Chip description:
oem: ATI ATOMBIOS
product: PARK 01.00

Driver used by Xorg:
#card0driver

Video mode used by Xorg:
Resolution: Depth 24 Depth: "Display"

...the above also recorded in /tmp/report-video
#
Thanks for the pet

[Karl Godt]

Suggestion for pup_event_frontend_d :

lines ~779 - 786 adding break to prevent from becomming zombie :

Code: Select all

  probe_floppy_func $ONEFLOPPY
 done

break
done #2 second loop.


###END###

added the break command.

It might be fixed at wary094 but since booting a full install and also zenpup that seems to be builded with the actual wary woof which seems not beeing able to mount its devx I am not running it.
I am posting it here because I couldn't find the appropriate thread for this.

[don570]

don570,
As you are in contact with Dmitry, would you mind asking him if he can post the source code, or at least a patch for 3.34.56?

I would like to compile it in Wary (so it won't have that libtiff problem).
And it will be in the next release of Wary. I am particularly interested in this as I too will soon have a input tablet to play with!

On Friday Dmitry posted a new source at git
https://github.com/wjaguar/mtPaint

He also sent me an email explaining what is new...

> Another odd thing I noticed, when I opened the folder that mtpaint was
> stored
> in and launched the terminal, then typed ./mtpaint the pressure wouldn't
> work. See attached image. I checked this several times so it is not an
> accident.

Good that you noticed this. As it happens, luci 235 (and, it seems,
234 as well) has "GDK_NATIVE_WINDOWS=true" set in its terminal's
environment for some reason.
So I made mtPaint 3.34.57 (compiled version attached to this message)
not just leave the variable alone, but actually unset it.

I will be testing it over the weekend and you can do the same.
You'll have a lot of fun with your tablet. I suggest trying 'mypaint'
which requires Ubuntu Linux. It has incredible effects
http://mypaint.intilinux.com/

Best Regards

_________________________________________________________

[ttuuxxx]

Hi guys

I went to play a small screen sized movie on mplayer and it didn't expand the movie size it stayed little in the middle of the screen, lol so it was basically too small to view, next I tried playing a mp4 video and it had sound but no picture, ggrrrrrrrrrrrrrrrrr.
So I decided to compile Gxine, libxine, but one thing I always hated about gxine is the Ugly logo on the player, so I was on a hunt to change this, what a pain in the buttttttt, lol
First the background on the video player is a actually a movie file, mpv. and gxine has a script to make a new video background but puppy doesn't have the software installed by default, So my next step was to figure out what was needed, First it needed Imagemagic and second it needed mjpegtools and mjpegtools needed quicktime libs, So after hours of messing around, the script wouldn't build the video, I made a nice background by using gimp and it was the right size so I looked at the script and basically typed in a terminal png2yuv -n 1 -I p -f 25 -j tmp.png |mpeg2enc -n p -f 3 -a 2 -q 4 -b 10000 -o logo.mpv
and boom it made the movie:) heck I didn't even need imagemagic because the background I made was the right size already .
to make a long story short, below is a new gxine package and you need xinelibs also. I also changed a few of the icons like the volume icon. It plays mp4's and small movies expand on it.
Plus I have the sources also listed with the change background already to be compiled on other puppy versions.
ttuuxxx

Gxine (both files needed)
http://www.smokey01.com/ttuuxxx/Wary/So ... 5-i386.pet
http://www.smokey01.com/ttuuxxx/Wary/So ... 9-i386.pet

Gxine-updated sources
http://www.smokey01.com/ttuuxxx/Wary/So ... src.tar.gz


Image Magic with 25MB of docs, lol
http://www.smokey01.com/ttuuxxx/Wary/So ... 6-i386.pet

mjpegtools needs both pets to fully run
http://www.smokey01.com/ttuuxxx/Wary/So ... 0-i386.pet
http://www.smokey01.com/ttuuxxx/Wary/So ... 5-i386.pet

also the quicktime libs are cool you can play movies via the terminal, Like Quicktime movies.
open a terminal in the movie location and type lqtplay moviename.mp4

enjoy
ttuuxxx

[ttuuxxx]

Here's a older but better version of JWM that doesn't have that desktop switching when you drag a window too far to the right, I really don't like swapping desktops just because I accidentally dragged a window too far to the right. I wish we could turn off that feature, or even better yet have it turned off by default and have a menu listing to turn it on if need be.

ttuuxxx

[BarryK]

I started with a fresh install of 094 on a 4gb flash drive and on
first boot I just setup the network etc. and then rebooted to create
the save file.
On the second bootup I downloaded the new ati pet and installed it,
then rebooted.
Now there was a new entry in the setup menu but clicking on that gave
an error, see attached file errorscrn.jpg
I exited to the prompt and entered "aticonfig --initial" and then xwin
to restart x.
# report-video
VIDEO REPORT: Wary Puppy, version 094

Chip description:
oem: ATI ATOMBIOS
product: REDWOOD 01.00

Driver used by Xorg:
#card0driver

Video mode used by Xorg:
Resolution: Depth 24 Depth: "Display"

...the above also recorded in /tmp/report-video
# Clicking on the new entry in the setup menu doesn't do anything
*but* clicking on one of the game files on the hard drive that
requires accelerated graphics works so the pet is working but needs
the extra step of "aticonfig --initial" at the command prompt then
xwin.
This is on my newest desktop with an ati radeonhd 5570 graphics card.

Edit:
The same method works on my laptop which has ATI Mobility Radeon
HD5470 graphics.

# report-video
VIDEO REPORT: Wary Puppy, version 094

Chip description:
oem: ATI ATOMBIOS
product: PARK 01.00

Driver used by Xorg:
#card0driver

Video mode used by Xorg:
Resolution: Depth 24 Depth: "Display"

...the above also recorded in /tmp/report-video
#
Thanks for the pet

Billtoo,
Would you mind doing one more thing for me. The 'aticonfig --initial' modifies /etc/X11/xorg.conf -- I would like to see that. Could you gzip it and post it here?

[BarryK]

I started with a fresh install of 094 on a 4gb flash drive and on
first boot I just setup the network etc. and then rebooted to create
the save file.
On the second bootup I downloaded the new ati pet and installed it,
then rebooted.
Now there was a new entry in the setup menu but clicking on that gave
an error, see attached file errorscrn.jpg
I exited to the prompt and entered "aticonfig --initial" and then xwin
to restart x.
# report-video
VIDEO REPORT: Wary Puppy, version 094

Chip description:
oem: ATI ATOMBIOS
product: REDWOOD 01.00

Driver used by Xorg:
#card0driver

Video mode used by Xorg:
Resolution: Depth 24 Depth: "Display"

...the above also recorded in /tmp/report-video
# Clicking on the new entry in the setup menu doesn't do anything
*but* clicking on one of the game files on the hard drive that
requires accelerated graphics works so the pet is working but needs
the extra step of "aticonfig --initial" at the command prompt then
xwin.
This is on my newest desktop with an ati radeonhd 5570 graphics card.

Edit:
The same method works on my laptop which has ATI Mobility Radeon
HD5470 graphics.

# report-video
VIDEO REPORT: Wary Puppy, version 094

Chip description:
oem: ATI ATOMBIOS
product: PARK 01.00

Driver used by Xorg:
#card0driver

Video mode used by Xorg:
Resolution: Depth 24 Depth: "Display"

...the above also recorded in /tmp/report-video
#
Thanks for the pet

It is strange that you have to run 'aticonfig --initial', as the 'pinstall.sh' script (post-installation script) of the ATI PET package runs this:

aticonfig --initial --overlay-type=Xv

...could you try this, see if it gives an error message?

Maybe I have to remove that second parameter. Actually, I got that from kirk's ATI PET, that he posted awhile back.

[Billtoo]

I started with a fresh install of 094 on a 4gb flash drive and on
first boot I just setup the network etc. and then rebooted to create
the save file.
On the second bootup I downloaded the new ati pet and installed it,
then rebooted.
Now there was a new entry in the setup menu but clicking on that gave
an error, see attached file errorscrn.jpg
I exited to the prompt and entered "aticonfig --initial" and then xwin
to restart x.
# report-video
VIDEO REPORT: Wary Puppy, version 094

Chip description:
oem: ATI ATOMBIOS
product: REDWOOD 01.00

Driver used by Xorg:
#card0driver

Video mode used by Xorg:
Resolution: Depth 24 Depth: "Display"

...the above also recorded in /tmp/report-video
# Clicking on the new entry in the setup menu doesn't do anything
*but* clicking on one of the game files on the hard drive that
requires accelerated graphics works so the pet is working but needs
the extra step of "aticonfig --initial" at the command prompt then
xwin.
This is on my newest desktop with an ati radeonhd 5570 graphics card.

Edit:
The same method works on my laptop which has ATI Mobility Radeon
HD5470 graphics.

# report-video
VIDEO REPORT: Wary Puppy, version 094

Chip description:
oem: ATI ATOMBIOS
product: PARK 01.00

Driver used by Xorg:
#card0driver

Video mode used by Xorg:
Resolution: Depth 24 Depth: "Display"

...the above also recorded in /tmp/report-video
#
Thanks for the pet

Billtoo,
Would you mind doing one more thing for me. The 'aticonfig --initial' modifies /etc/X11/xorg.conf -- I would like to see that. Could you gzip it and post it here?

here it is:

edit: this xorg.conf is from the computer with the radeon hd3200 onboard graphics, I used the same method on it too.

edit: it gave this error message:

# aticonfig --initial --overlay-type=Xv
Found fglrx primary device section
Error: invalid string value for --ovt option.
Please check aticonfig help info for supported overlay type.
aticonfig: parsing the command-line failed.
#

[ttuuxxx]

here's the latest pidgin basic version with gtktspell checker, you need to install the pidgin pet and gtkspell pet for spelling check, there's also a locales pet for other than English languages
ttuuxxx

http://www.smokey01.com/ttuuxxx/Wary/So ... 5-i386.pet


http://www.smokey01.com/ttuuxxx/Wary/So ... 6-i386.pet

extra-Locales
http://www.smokey01.com/ttuuxxx/Wary/So ... ocales.pet
ttuuxxx