Racy Puppy 5.2.2 Final, 18 Nov. 2011
- veronicathecow
- Posts: 559
- Joined: Sat 21 Oct 2006, 09:41
Am running in virtualbox version 4.1.4 and am having problems with mouse integration and resolution
When I move in certain parts of the screen the cursor changes to the host cursor unless I disable integration.
Secondly no matter what resolution I choose it still takes up to large an area and means I have to scroll.
Thanks
When I move in certain parts of the screen the cursor changes to the host cursor unless I disable integration.
Secondly no matter what resolution I choose it still takes up to large an area and means I have to scroll.
Thanks
UPDATE: grub4dos-0.4.4.v1.7.1
Was failed with some environment when the 1st partition is ext4 file system (thanks to jim3630 and billtoo).
grub4dos-0.4.4.v1.7.1.pet (Update: 29 Oct 2011) now available.
http://www.murga-linux.com/puppy/viewtopic.php?t=51697
* 29oct11 v1.7.1: fix was failed with ext4, drive letter, gtkdialog4 thanks to 01micko, help button, no sort probepart, bootable check
grub4dos-0.4.4.v1.7.1.pet (Update: 29 Oct 2011) now available.
http://www.murga-linux.com/puppy/viewtopic.php?t=51697
* 29oct11 v1.7.1: fix was failed with ext4, drive letter, gtkdialog4 thanks to 01micko, help button, no sort probepart, bootable check
Last edited by shinobar on Sat 29 Oct 2011, 15:52, edited 1 time in total.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
Indeed.Billtoo wrote:It works great, thanks.rcrsn51 wrote:Here is guvcview for Racy.
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==
same on dual core p6100 hp, intel graphics but not sure what driver ? vesa see prior postBarryK wrote:I have a problem with 'glxgears' in Racy, see my blog report:
http://bkhome.org/blog/?viewDetailed=02574
Tests of glxgears on other video hardware greatly appreciated!
Make sure all apps etc. closed before testing, in case it hangs. I had to hold down the power-off button on my laptop for 4 seconds.
Re: UPDATE: grub4dos-0.4.4.v1.7.1
it works!shinobar wrote:Was failed with some environment when the 1st partition is ext4 file system (thanks to jim3630 and billtoo).
grub4dos-0.4.4.v1.7.1.pet (Update: 29 Oct 2011) now available.
http://www.murga-linux.com/puppy/viewtopic.php?t=51697
* 29oct11 v1.7.1: fix was failed with ext4, drive letter, gtkdialog4 thanks to 01micko, help button, no sort probepart, bootable check
Code: Select all
--- /initrd/pup_ro2/usr/sbin/xorgwizard 2011-09-27 01:31:20.000000000 -0100
+++ /usr/sbin/xorgwizard 2011-10-29 23:21:58.566654034 -0100
@@ -330,6 +330,7 @@ if [ ! "`echo -n "$PSFND" | grep "\\.xin
NEXTWM="`cat /etc/windowmanager`"
echo -n "$NEXTWM" > /etc/windowmanager #this makes change permanent.
echo -n "$NEXTWM" > /tmp/wmexitmode.txt
+ echo -n "ICONWIPE" >/tmp/pup_event_icon_change_flag ##in case Xvesa selects different resolution
sync
exec killall X
;;
@@ -1919,5 +1920,5 @@ fi
#[ -f /tmp/ddcprobeoem.txt ] && rm /tmp/ddcprobeoem.txt && exec xwin
#3.99 end
[ -f /tmp/ddcprobeoem.txt ] && rm /tmp/ddcprobeoem.txt #w478
-
+echo 'ICONWIPE' > /tmp/pup_event_icon_change_flag
###END###
- Attachments
-
- after-xorgwizard-driveicons-would-need-ICONWIPE.png
- (77.78 KiB) Downloaded 749 times
NEXT : SAVE to CREATED CRYPT"A" file did not succeed at reboot .
--------- This time I did reboot from the prompt [wmexit] and the same :
--------- DID NOT SAVE new CREATED|CHANGED files into PUPSAVE !
--------- LIKE in slacko from X .
SAVEFILE gets created in ext2 at shutdown AND mounted successfully at boot :
# cat /etc/rc.d/BOOTCONFIG
LASTUNIONRECORD='racysave_crypta-2011_10_30_cryptA_ext2.2fs puppy_racy_5.1.110.sfs'
EXTRASFSLIST=''
# mount
/dev/sda4 on /initrd/mnt/dev_save type fuseblk (rw,noatime,user_id=0,group_id=0,default_permissions,blksize=4096)
/dev/loop1 on /initrd/pup_rw type ext2 (rw,noatime,errors=continue)
# df
/dev/sda4 14964544 11064844 3899700 74% /initrd/mnt/dev_save
/dev/loop1 516040 4528 511512 1% /initrd/pup_rw
# lsmod
cbc 1939 1
cryptoloop 1515 1
fuse 47672 2
unionfs 58158 1
squashfs 19073 1
# grep -i AES /etc/modules/*
/etc/modules/DOTconfig-3.0.7:CONFIG_CRYPTO_AES=y
/etc/modules/DOTconfig-3.0.7:CONFIG_CRYPTO_AES_586=m
/etc/modules/DOTconfig-3.0.7:# CONFIG_CRYPTO_AES_NI_INTEL is not set
The desktop was only black background and with jwm-taskbar .
After running " gdk-pixbuf-query-loaders --update-cache " as suggested by 01micko
AND " rox -p /root/Choices/ROX-Filer/PuppyPin " the normal Puppy desktop environment showed up !
The new pupdialog to select extra sfs seems to be a little unrelyable ,
maybe because of some 2>/tmp/choice/txt.$$ like
"GDK-WARNING : SOME_LONG_TEXT_HERE
GDK-WARNING : SOME_LONG_TEXT_HERE
GDK-WARNING : SOME_LONG_TEXT_HERE
GDK-WARNING : SOME_LONG_TEXT_HERE
devx_racy_version.sfs
"
For security reasons i would advise a
in all these dialog|Xdialog scripts : TAIL to filter above Error messages out ( JUST IN CASE ) .
Iguleders inpu-001 had much of these i can remember .
--------- This time I did reboot from the prompt [wmexit] and the same :
--------- DID NOT SAVE new CREATED|CHANGED files into PUPSAVE !
--------- LIKE in slacko from X .
SAVEFILE gets created in ext2 at shutdown AND mounted successfully at boot :
# cat /etc/rc.d/BOOTCONFIG
LASTUNIONRECORD='racysave_crypta-2011_10_30_cryptA_ext2.2fs puppy_racy_5.1.110.sfs'
EXTRASFSLIST=''
# mount
/dev/sda4 on /initrd/mnt/dev_save type fuseblk (rw,noatime,user_id=0,group_id=0,default_permissions,blksize=4096)
/dev/loop1 on /initrd/pup_rw type ext2 (rw,noatime,errors=continue)
# df
/dev/sda4 14964544 11064844 3899700 74% /initrd/mnt/dev_save
/dev/loop1 516040 4528 511512 1% /initrd/pup_rw
# lsmod
cbc 1939 1
cryptoloop 1515 1
fuse 47672 2
unionfs 58158 1
squashfs 19073 1
# grep -i AES /etc/modules/*
/etc/modules/DOTconfig-3.0.7:CONFIG_CRYPTO_AES=y
/etc/modules/DOTconfig-3.0.7:CONFIG_CRYPTO_AES_586=m
/etc/modules/DOTconfig-3.0.7:# CONFIG_CRYPTO_AES_NI_INTEL is not set
The desktop was only black background and with jwm-taskbar .
After running " gdk-pixbuf-query-loaders --update-cache " as suggested by 01micko
AND " rox -p /root/Choices/ROX-Filer/PuppyPin " the normal Puppy desktop environment showed up !
The new pupdialog to select extra sfs seems to be a little unrelyable ,
maybe because of some 2>/tmp/choice/txt.$$ like
"GDK-WARNING : SOME_LONG_TEXT_HERE
GDK-WARNING : SOME_LONG_TEXT_HERE
GDK-WARNING : SOME_LONG_TEXT_HERE
GDK-WARNING : SOME_LONG_TEXT_HERE
devx_racy_version.sfs
"
For security reasons i would advise a
Code: Select all
choice=`cat /tmp/choice.txt.$$ | tail -n 1`
Iguleders inpu-001 had much of these i can remember .
NEXT : JWMCONFIG !!
Thie jwmconfig has got several bugs , which I was observing for one year now ,
[ perhaps will open a thread in the Cutting Edge section , but my fixes may still contain bugs also ]
Shinobar attempted to fix the line numbering , but moving the panel buttons around , deleted two lines in .jwmrc-tray :
I have made some attempts to fix jwmconfig and one solution for the line numbering using wc -l could be :
ENSURE TRAILING NEWLINE IN .JWMRC-TRAY !!!!!!!!!!!!!!!!!!!!!!
this could be achieved by adding this code into /usr/local/jwmconfig2/panel-buttons :
Thie jwmconfig has got several bugs , which I was observing for one year now ,
[ perhaps will open a thread in the Cutting Edge section , but my fixes may still contain bugs also ]
Shinobar attempted to fix the line numbering , but moving the panel buttons around , deleted two lines in .jwmrc-tray :
Code: Select all
<Pager/>
<!-- Additional TaskList attribute: maxwidth -->
ENSURE TRAILING NEWLINE IN .JWMRC-TRAY !!!!!!!!!!!!!!!!!!!!!!
this could be achieved by adding this code into /usr/local/jwmconfig2/panel-buttons :
Code: Select all
--- /initrd/pup_ro2/usr/local/jwmconfig2/panel-buttons 2010-08-23 04:04:43.000000000 +0100
+++ /usr/local/jwmconfig2/panel-buttons 2011-10-30 01:32:57.000000000 +0100
@@ -17,6 +17,21 @@ fi
cat /root/.jwmrc-tray | sed '/^$/d' > /tmp/.jwmrc-tray ### remove all blank lines in .jwmrc-tray
mv /tmp/.jwmrc-tray /root/
+if test "`tail -n 1 $HOME/.jwmrc-tray | hexdump | grep -o '0a'`" = "" ; then
+ #KRGensure newline so wc counts the real line numbers :)
+
+ lastLine=`cat $HOME/.jwmrc-tray | tail -n 1`
+
+ if test "$lastLine" = "</JWM>" ;then
+ echo >> $HOME/.jwmrc-tray
+ else
+ if test "`grep -o -w '</JWM>' $HOME/.jwmrc-tray`" = "" ; then
+ echo '</JWM>' >> $HOME/.jwmrc-tray
+ echo >> $HOME/.jwmrc-tray
+ fi
+ fi
+fi
# 2009-NOV-06 low and high position fixed
total=`wc -l /root/.jwmrc-tray | sed -e 's/ *//' | sed -e 's/ .*//g'` ### get total number of lines
low=`grep -n '^[[:blank:]]*<TrayButton' /root/.jwmrc-tray | head -n 1| cut -d':' -f1` ### get line number of the first button(Menu)
did it work? I'm stuck with vesa, 1600x900 and xorgwizard from the firstrun-gui only cycles me back to same display without giving any choices.Karl Godt wrote: Bogus thingy , that bothered me for one year , but now racy-110 gave me vesa instead of nv or nouveau at startup , so ran xorgwizard from the new firstrun-gui :
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Jim,jim3630 wrote:same on dual core p6100 hp, intel graphics but not sure what driver ? vesa see prior postBarryK wrote:I have a problem with 'glxgears' in Racy, see my blog report:
http://bkhome.org/blog/?viewDetailed=02574
Tests of glxgears on other video hardware greatly appreciated!
Make sure all apps etc. closed before testing, in case it hangs. I had to hold down the power-off button on my laptop for 4 seconds.
Would you mind looking in file /var/log/xorg.0.log, and do a search for "i9" and "i8". That will determine which of the i810, i915 or i965 DRI drivers are loading.
On my laptop, it is the i965 DRI driver that is the culprit.
[url]https://bkhome.org/news/[/url]
Yes , it apparently [seems to have] worked :jim3630 wrote:did it work? I'm stuck with vesa, 1600x900 and xorgwizard from the firstrun-gui only cycles me back to same display without giving any choices.Karl Godt wrote: Bogus thingy , that bothered me for one year , but now racy-110 gave me vesa instead of nv or nouveau at startup , so ran xorgwizard from the new firstrun-gui :
There are three buttons to select @xorgwizard :
dialog --colors --extra-button --title "Puppy Video Wizard"
--ok-label "Probe" --cancel-label "vesa" --extra-label "Choose"
the Choose option presented the whole drivers list , that the script found in its search
and there i had chosen "nouveau" and then it tested ok .
BUT i did not check the content of xorg.conf .....
after mounting the save-file
xorg.conf is /mnt/loop5/etc/X11/xorg.conf.NVIDIAAOCA790
BUT the card driver section looks like
#110627 remove...
##server can find BusID automatically, comment out...
#Section "Device"
# Identifier "Card0"
# Driver "vesa" #card0driver
# VendorName "Unknown Vendor"
# BoardName "Unknown Board"
## BusID "PCI:0:2:0" #card0busid
#EndSection
?????
[ guessing for now a simple grep 'vesa' syntax in the firstrun-gui caused this ]
So i have to reboot into it again to check for the card driver :S
I'm running Racy 5.1.110 with no problems in my old laptop:
Toshiba s1410 , 512MB ram, GeForce 440 , Celeron 1.8Ghz.
Pnethood works well with win98 shares.
# report-video
Calling INT 0x15 (F000:FEA8)
EAX is 0x5F15
Calling INT 0x15 (F000:FEA8)
EAX is 0x5F15
Racy Puppy, version 5.1.110 on Dom 30 Otu 2011
Chip description:
0.0 VGA compatible controller
nVidia Corporation NV17 [GeForce4 420 Go] (rev a3)
oem: NVidia
product: NV17 () Board Chip Rev A2
X Server: Xorg
Driver used: nouveau
X.Org version: 1.11.0
dimensions: 1024x768 pixels (270x203 millimeters)
depth of root window: 24 planes
I experienced the same problem of forum member peebee with b43 driver:
modprobe b43 won't load the b43 firmware. I solved with the old method:
rmmod b43
tar -zxf /lib/modules/all.firmware/b43.tar.gz
cp -a /lib/modules/all.firmware/b43/* /
sync
modprobe b43
The b43 driver works on reboots. My wifi card is a Broadcom 4306 minipci.
I would like to install tightvnc viewer, will it work the puppy 3.01 repo .pet or do I need a more recent .pet?
I continue testing... Bye!
Toshiba s1410 , 512MB ram, GeForce 440 , Celeron 1.8Ghz.
Pnethood works well with win98 shares.
# report-video
Calling INT 0x15 (F000:FEA8)
EAX is 0x5F15
Calling INT 0x15 (F000:FEA8)
EAX is 0x5F15
Racy Puppy, version 5.1.110 on Dom 30 Otu 2011
Chip description:
0.0 VGA compatible controller
nVidia Corporation NV17 [GeForce4 420 Go] (rev a3)
oem: NVidia
product: NV17 () Board Chip Rev A2
X Server: Xorg
Driver used: nouveau
X.Org version: 1.11.0
dimensions: 1024x768 pixels (270x203 millimeters)
depth of root window: 24 planes
I experienced the same problem of forum member peebee with b43 driver:
modprobe b43 won't load the b43 firmware. I solved with the old method:
rmmod b43
tar -zxf /lib/modules/all.firmware/b43.tar.gz
cp -a /lib/modules/all.firmware/b43/* /
sync
modprobe b43
The b43 driver works on reboots. My wifi card is a Broadcom 4306 minipci.
I would like to install tightvnc viewer, will it work the puppy 3.01 repo .pet or do I need a more recent .pet?
I continue testing... Bye!
Racy Puppy 5.1.110 (5.2 beta2 - 27 Oct 2011)
I made an sfs file of Goggles Music Manager.
It is approximately 7mb in size and contains all the dependencies
required by gogglesmm.
The download link is:
http://www.datafilehost.com/download-8a433947.html
It is approximately 7mb in size and contains all the dependencies
required by gogglesmm.
The download link is:
http://www.datafilehost.com/download-8a433947.html
- Attachments
-
- goggles.jpg
- (105.39 KiB) Downloaded 1160 times
Last edited by Billtoo on Sun 30 Oct 2011, 14:51, edited 1 time in total.
crash when Internet connection wizard launch
Racy is fine in the AMD Fusion E-350 with AR 8152 and BCM 4313, until the Internet Connection Wizard is launched (when there is no ethernet plugged in). If wired connection is established at boot (ethernet is connected), no problem.
Puppy user since Oct 2004. Want FreeOffice? [url=http://puppylinux.info/topic/freeoffice-2012-sfs]Get the sfs (English only)[/url].
Changed the board to Asrock, changed the cpu to A2500+mobile, changed the monitor to 19"widescreen and the on-board SiS chipset gave the 1600x900 persistence feature. Nothing will shift it. Not Xorgwiz, not driver change, nothing.
SiS chipset problems only started very recently. It not the chipset, so what's the answer?
SiS chipset problems only started very recently. It not the chipset, so what's the answer?