Page 9 of 14

Posted: Fri 20 Jul 2012, 20:53
by antiloquax
antiloquax wrote:
glxgears test

"Safe" overclock: best reading was 19.170 fps

No overclock: 19.077 fps

Over-voltage: 26.994 fps
Over-voltage with swapon - 29.103
Thought I'd run this in Arch, just for fun.
This was in the "safe" overclock settings, with swapon:
31.844 fps

Posted: Fri 20 Jul 2012, 21:17
by eowens2
Just a couple of comments on SAP6 alpha-4.

The sound "just works" OTB on my powered analogue speakers (I have not tried them on previous alpha versions). I did not go thru any set-up of ALSA. There is occasional static coming thru them; the speakers are quite inexpensive ones just purchased from Walmart, so the static problem could be in the quality of the speakers (I have not used them before on a different system). I used GNOME MPlayer to play some MP3 files.

I am not hearing the "Woof-Woof" during the boot up of Puppy. Has this not been added yet?

The CUPS 1.4.4 continues to work (I used it in alphas 1 and 2 but not try it in 3). It found my HP 6500 e710n multifunction printer (wirelessly connects to my router, R_pi connects by wired ethernet to the router) without difficulty, and installed it using the drivers found in HPLIP.

When one clicks on the "Setup CUPS Printing" choice in the "Setup" Desktop icon, the user is routed thru an info page which says that HPLIPlite is available, but PPM is unable to find HPLIPlite. HPLIP (heavy!) could be found and that I what I used for my printer driver.

PPM is still installing the Ace-of-Penguins games under Utilities/General Utilities/name-of-game; however Mahjong installs under the "Fun" menu. I am still seeing the "line 1 : syntax error: unexpected '(' " during the updating and processing of the databases.

Glad to hear multioot is working with Puppy Alpha4

Posted: Fri 20 Jul 2012, 21:21
by rrolsbe
Rolf

Thanks for keeping us abreast of your multiboot testing!

Since, In my opinion, booting Puppy using only only SFS files and a PUPSAVE file is one of Puppies greatest strengths (among many!), multiboot interests me greatly. Since the Pi must un-compress binaries located inside SFS files, does the Pi seem to launch the binaries slower? I assume the core SFS file is to large to be resident in RAM as it is on my x86 machine with LOTS of RAM? Since the read speed is fairly slow on a typical Pi SDHC card, the time it takes to un-compress might be negligible because less information must be read from the SDHC media? However, this may not be true if the full install and SFS installs were being read from a FASTER USB2.0 attached hard drive/SSD? I am currently trying out Puppy Alpha-4 and Raspbian and have /root for each on two ext4 partitions on an external hard drive. I simply change some settings in the SDHC vfat /boot partition to select which OS to boot. BTW, both OS's are more responsive using /boot from the external hard drive. This external USB hard drive is connected to and is being powered by a USB port on my Motorola LapDock.

What I would like to do is multiboot from a large SDHC card (slow but most portable), large USB stick (faster but must give up a USB port) and a USB spinning/SS drive (hopefully faster than a USB stick but still gives up a USB port and draws more battery power when disconnected from the 110 outlet). Binary loading time testing needs to be performed to verify my speed assumptions.

At this time Raspbian appears to be slightly more responsive that Puppy Alpha-4, but It appears the Puppy Gods are looking at Raspbian armhf for a future Puppy version (YEAH!!!) Hopefully the Raspbian/Puppy developers will incorporate the assembly language SSL code to speed up SSH and HTTPS. When this happens, I predict Puppy will be the official OS recommended by the Raspberry Pi foundation (but I have been wrong many times in the past).

Thanks Again Rolf!
Regards, Ron

Posted: Fri 20 Jul 2012, 23:13
by 01micko
Gutenprint!

This has heaps of new drivers,

http://www.smokey01.com/01micko/armv6/p ... -armv6.pet

dev,nls in folder http://www.smokey01.com/01micko/armv6/p ... s-squeeze/

Note to Barry, needed krb5-multidev squeeze package to compile as gssapi.h is not in the libkrb5-dev package.[ :? strange]

This will fix some local printing issues ie: no driver for your printer. There are lots of new Canon drivers and others.

Posted: Sat 21 Jul 2012, 06:31
by Lobster
I am not hearing the "Woof-Woof" during the boot up of Puppy. Has this not been added yet?
Not been added. Not sure if Barry has sound yet. I have sound from headphone not yet on HDMI.
I changed my TV from auto to PCM audio output. No difference. Still trying to find some elusive setting . . .

Posted: Sat 21 Jul 2012, 11:00
by nooby
Did not somebody comment that the circuit maybe only had Line audio out
and not Headphone or Speaker power out. If you connect it to a mixer board or the sensitive Audio in to an external Amplifier then maybe the sound is okay?

That was what I read but have no link. could be on Barry's blog not sure

Posted: Sun 22 Jul 2012, 01:14
by BarryK
Lobster wrote:
I am not hearing the "Woof-Woof" during the boot up of Puppy. Has this not been added yet?
Not been added. Not sure if Barry has sound yet. I have sound from headphone not yet on HDMI.
I changed my TV from auto to PCM audio output. No difference. Still trying to find some elusive setting . . .
The "woof woof" is done in /usr/sbin/delayedrun using 'aplay' -- but aplay doesn't work.

I did try 'wavplay', but that hangs.

Posted: Tue 24 Jul 2012, 12:32
by 01micko
Well ..

We are having trouble with aplay and wavplay and the signature Puppy 2barks. I converted it to .mp3 format and it plays! Not too bad in mplayer but perfect with mpg321 (in PPM, don't bother with the deps, it works without them).
See attached.

Re: gtkdialog bug fix

Posted: Thu 26 Jul 2012, 10:07
by thunor
jamesbond wrote:The line numbers are specific to gtkdialog revision 320 from svn trunk, but if you do a search, you should be able to find the line in other versions too.

File is src/automaton.c, line number 2149
Reverse a and b, from stackelement _sum(stackelement a, stackelement b)
to
stackelement _sum(stackelement b, stackelement a)

gtkdialog will magically display the correct ordering. Do I get a bounty? 8)

Can't help with the keyboard, I don't own a pi.
EDIT: I see from your post that keyboard problem is resolved with a new kernel Image. So two major problems are resolved then.
Fantastic work :)

I've applied this to gtkdialog r321.

I've wrapped it in "#ifdef __arm__" so I'm expecting it to get compiled in ("gcc -x c /dev/null -E -dM" lists the supported preprocessor macros).

Many thanks.

Posted: Thu 26 Jul 2012, 10:27
by rhadon
I installed mpg321 and it works fine with 2barks.mp3 via HDMI. Via analog (connected to an amp) sometimes it's OK, sometimes there's missing a little bit from the beginning of the first bark.

In delayedrun I replaced

Code: Select all

aplay /usr/share/audio/2barks.au
with

Code: Select all

mpg321 /usr/share/audio/2barks.mp3
but no barking puppy.

I also have the problem that sometimes x server doesn't restart. I get only a black screen and must power off. I guess, this is more serious.

btw. ctrl+alt+bs doesn't work for me. Is it me or in general?

~Rolf

Posted: Tue 31 Jul 2012, 13:03
by 01micko
The drive icons don't get built when changing icon themes, they get copied but the overlay fails. I tried all icon themes and a custom one I built. Netpbm tools seem to work though, oh, no that routine uses vovchik's app right? Looking in to it.

SOLVED!: just overwrite the exec at /usr/sbin/pngoverlay with the attached

Code: Select all

bacon -o -O2 -o -s pngoverlay.bac

Posted: Mon 06 Aug 2012, 09:42
by rhadon
Hi, it looks like to be very silent here, these days... :?

Anyway, I try to get picscale working (it doesn't)

The error message:

Code: Select all

# picscale -i au.jpg -o test.jpg 128 128 9

(<unknown>:19664): GdkPixbuf-CRITICAL **: gdk_pixbuf_scale_simple: assertion `dest_width > 0' failed

(<unknown>:19664): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_rowstride: assertion `GDK_IS_PIXBUF (pixbuf)' failed

(<unknown>:19664): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_n_channels: assertion `GDK_IS_PIXBUF (pixbuf)' failed

(<unknown>:19664): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `GDK_IS_PIXBUF (pixbuf)' failed

(<unknown>:19664): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `GDK_IS_PIXBUF (pixbuf)' failed

(<unknown>:19664): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_pixels: assertion `GDK_IS_PIXBUF (pixbuf)' failed

(<unknown>:19664): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
OOPS.. something terrible happened and test.jpg was not created.
# 
I installed gliv_1.9.6-1 form PPM, "image viewer using gdk-pixbuf and OpenGL". This works, so I guess that gdk-pixbuf is OK.

Similar error messages with scale2jpg (picscale is written in bacon, scale2jpg is C). I tried to compile it on the RasPi with

Code: Select all

gcc  -Werror -o scale2jpg scale2jpg.c `pkg-config --libs gdk-pixbuf-2.0 gdk-2.0` `pkg-config --cflags gdk-pixbuf-2.0 gdk-2.0`  -lm 
	strip scale2jpg
based on the makefile, but it makes no difference.

Has anybody any idea, what I could try?
btw. I have a folder /usr/lib/gdk-pixbuf-2.0, but it's empty.

I really like to get this working, :roll:

Rolf

Edit: Problem solved :D . Digging in Barry's blog was helpful :oops: .

memory split?

Posted: Sun 12 Aug 2012, 18:05
by tinker
The latest recommended debian distribution for the pi comes with four different files in /boot:
arm128_start.elf
arm192_start.elf
arm224_start.elf
start.elf

These determine, somehow, the amount of memory out of the 256MB total that is allocated for regular use, as opposed to graphics use. You copy the desired file over start.elf and reboot, to change the allocation. I think it defaults in this release to 192. I switched to using 224 to get more memory for applications. Top now reports 220,592 kib memory total.

Puppy sap comes with only one file that seems to give a memory split at 128MB, at least that's close to the number reported by top and hardinfo.

Does someone know how to create a "Start" file for puppy that gives applications more memory?

I did check the file sizes on debian versus puppy sap, and they're different. I didn't want to just try one of theirs.

Wireless USB Dongle

Posted: Fri 17 Aug 2012, 10:33
by JpDeValen
Alpha 4 is working all ok with my Logitech KB/mouse and I can surf the internet with my box via ethernet cable.
I have a problem with my Belkin Surf N300 wifi USB dongle plugged on the second USB port of the Pi.
I can see it in the hardware system list but it cannot be set up with the connect box.

The parameters are :

realtek
dev 0x4091264
vendor 0x50d
Product Id 0x2103

Thank you for your help

Jean-Pierre

Re: Wireless USB Dongle

Posted: Sat 18 Aug 2012, 12:29
by Montala
JpDeValen wrote:Alpha 4 is working all ok with my Logitech KB/mouse and I can surf the internet with my box via ethernet cable.
I have a problem with my Belkin Surf N300 wifi USB dongle plugged on the second USB port of the Pi.
I can see it in the hardware system list but it cannot be set up with the connect box.

The parameters are :

realtek
dev 0x4091264
vendor 0x50d
Product Id 0x2103

Thank you for your help

Jean-Pierre
Hi Jean-Pierre,

It is generally accepted that the Raspberry Pi is not really powerful enough, by itself, to 'power'a wi-Fi dongle, and this should therefore really be supplied from a powered USB hub.

You can of course also feed your Pi from this as well, but do make sure that the PSU is something like 2 amps.

You can read a lot more information about peripherals which other users have found to work OK at http://elinux.org/RPi_VerifiedPeriphera ... g_USB_Hubs

Hope this helps... and good luck!

Re: memory split?

Posted: Wed 29 Aug 2012, 03:26
by tinker
tinker wrote:The latest recommended debian distribution for the pi comes with four different files in /boot:
arm128_start.elf
arm192_start.elf
arm224_start.elf
start.elf

These determine, somehow, the amount of memory out of the 256MB total that is allocated for regular use, as opposed to graphics use. You copy the desired file over start.elf and reboot, to change the allocation. I think it defaults in this release to 192. I switched to using 224 to get more memory for applications. Top now reports 220,592 kib memory total.

Puppy sap comes with only one file that seems to give a memory split at 128MB, at least that's close to the number reported by top and hardinfo.

Does someone know how to create a "Start" file for puppy that gives applications more memory?

I did check the file sizes on debian versus puppy sap, and they're different. I didn't want to just try one of theirs.
UPDATE: I copied the debian arm224_start.elf file over barry's start.elf file and now I get about 220MB total memory in puppy sap. So, it seems they are compatible. Chromium seems to run better with more memory.

Posted: Tue 04 Sep 2012, 21:46
by Jades
My Dad kindly let me play with his Pi, so I bought myself a 16GB Class 10 Samsung SDHC card - probably overkill but it was a really good price...

Still early days, this is actually the first day I've used SAP Alpha 4, but so far so good!

I'm pleased to see that the comprehensive software bundle I've come to expect from Puppy is present and correct here too. Dad's Pi experience thus far has been with Raspian (IIRC) and an early alpha port of RISC OS 5. From what I've seen, the former is somewhat... spartan.

I'll not comment too much on Chromium other than to say that it seems to work and I assume I'm imagining the sense of someone watching over my shoulder.

With regard to printing, setting it up was simply a matter of connecting the Canon i865 and going through CUPS in exactly the same way as on any other Puppy. Dad watched while I printed the test page, and took it down to show Mam.

Had a few lockups,but can't be sure whether it had crashed or whether I was just impatient.

Tried updating PPM but got a stack of syntax error messages while it was processing the package lists.

Posted: Tue 04 Sep 2012, 22:15
by Jades
Just tried loading the email client from the pinboard icon, and an error window popped up saying "GnuPG is not installed properly, or its version is too old. OpenPGP support disabled." I don't use PGP so can't comment on whether there is actually a problem. Having clicked OK, Puppy then proceeded to work through setting up Slypheed for the first time. I can't be sure until I've checked my Puppy installs on the main PC, but something seems odd with Slypheed too. Could just be the version number.

Over all, so far, this seems to be a remarkably accomplished Alpha!

[Edit: clarified sequence with email]

Posted: Sat 22 Sep 2012, 09:42
by sickgut
Hi people

I have been waiting a long time for the default raspbian for the Pi to bring out an OpenGL accelerated video driver.

Does this version of SAP that is the current release have OpenGL accelerated driver yet? Can it run glxgears?

i would fire up the Pi i have and test it but im using all my sd cards for developing a Pussy equivalent for the Pi...

If it works in Puppy already then i might release a game orientated Puppy that also contains alot of music and video software instead of waiting for raspian to release a driver and using raspbian to make the Pussy OS with all the fancy stuff that i have promised everyone. The server version of Pussy for the Pi is already available:
http://www.thepussycatforest.info/pussy-pie

other than server stuff i do actually believe that the Rasp Pi could be turned into an open source games console similar to the Playstation 1 and 2 with 1 game on each SD card and the game is executed automatically when a very bare OS has loaded up. With the fancy dhcp ethernet auto detection of network settings the user wouldnt have to worry about net connection stuff and could just put the sd card in the Pi, and it would load the game and you could be online playing multiplayer fps games without the user ever having to worry about OS stuff.

However, my hands are tied with no OpenGL driver :(

Posted: Sun 23 Sep 2012, 16:58
by rhadon
sickgut wrote:Can it run glxgears?
Yes, after installing mesa-utils from PPM, it works. Not sure, mesa-utils is needed or it's because glxgears is included.

You can also boot from a usb hd, meaning you need a small sd card with partition 1 and the other partition you can move to a hd or usb stick. You only need to change the path and maybe the file system type in cmdline.txt.

Or maybe you like Berryboot?

HTH
Rolf