Wary and Racy 5.3 final

[shariebeth]

Love Racy. It's like a modern 431.

A problem I had and solution:
(frugal install)

I use a wireless dongle with the rtl8188cus chip, which uses the rtl8192cu driver. However the rtl8192cu driver included in Racy would not connect. So following advice, I downloaded and installed the newest driver directly from the Realtek site, compiled it, and installed it with success.
(You can see my progress here if interested: http://puppylinux.info/topic/racy-53-ke ... ver-needed )

Steps:
Installed:
http://ftp.nluug.nl/ftp/pub/os/Linux/di ... cy_5.3.sfs
http://ftp.nluug.nl/ftp/pub/os/Linux/di ... atched.sfs
Typed bootmanager into terminal and moved these two sfs files "over to the right".

Downloaded:
This linux driver version 3.4.2_3727 from here:
http://www.realtek.com.tw/downloads/dow ... =true#2772

Note the installer included did not work for me, but cd'ing directly into the /root/my-documents/RTL8188C_8192C_8192D_USB_linux_v3.4.2_3727.20120404/driver/rtl8188C_8192C_8192D_usb_linux_v3.4.2_3727.20120404/ directory where it was downloaded to then running make and make install from there worked a charm.

It installed into /lib/modules/3.0.25/kernel/drivers/net/wireless/8192cu.ko (which is a different path than the original rtl8192cu driver was in, which is curious to me).

A side note, my WPA2 key does not save in the SNS for some reason upon reboot. The profile is saved but it's not connecting. It does connect when I re-enter it though. Will need to look into that next.

edit: Also sorry if it's my post that messed up the thread format but I can't seem to fix it.

[L18L]

...
edit: Also sorry if it's my post that messed up the thread format but I can't seem to fix it.

It is not your post, see: starting page with your post

[Terryphi]

Last year Barry discussed the possibility of upgrading the versions of glibc and gcc in Wary/Racy:

http://bkhome.org/blog/?viewDetailed=02372

At that time he decided to stick with the existing versions and I supported this view because of the risk of breaking older programs. However, things have moved on. I think it is now time to reconsider because Lucid and Precise have later versions and some recent programs now require them.

[FeodorF]

I have tried different puppy versions on my 32-bit PC's and keep getting the same error:

'segfault'

as last line of urxvt: dmesg

[Karl Godt]

Last year Barry discussed the possibility of upgrading the versions of glibc and gcc in Wary/Racy:

http://bkhome.org/blog/?viewDetailed=02372

At that time he decided to stick with the existing versions and I supported this view because of the risk of breaking older programs. However, things have moved on. I think it is now time to reconsider because Lucid and Precise have later versions and some recent programs now require them.

Still i am able to compile most newer CLI source with Puppy 4 glibc-2.6.1 .
Problems with X/gtk/glib-GUI applications .

I think Puppy is missing a Xorg-server -version 1.5 and glibc-2.8 to reduce the stepping height .

[rcrsn51]

Read here about continuing problems with printing in Wary.

[TKLF]

Apologies if this is a dumb question, but...
Does the newer kernel and Xorg in Racy nullify some of the Wary compatibility with older systems?

[MagicZaurus]

In Wary 5.3 I'm not able to establish a wireless connection with my router. In Wary 5.2.2 it is not a problem at all and working very nice.

In the log file of the Simple Network Setup (SNS), I find the following lines.

Code: Select all

STEP1c: ifconfig wlan0 down
STEP2: iwconfig wlan0 mode managed
STEP3: iwconfig wlan0 channel 3
STEP4: iwconfig wlan0 essid "2WIRE_ABC"
STEP5a: ifconfig wlan0 up
STEP5b: wpa_supplicant -B -Dwext -iwlan0 -c"/etc/simple_network_setup/wpa_supplicant.conf-2WIRE_ABC-00:18:DA:02:1A:F9"
daemon: No such device
Running: wpa_cli -i wlan0 status
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory

The driver used is iwl3945. I had a look at the SNS script (/usr/local/simple_network_setup/sns, but could not find any comment on changes since Wary 5.2.2 which could cause this.

Anybody has any ideas where it could go wrong?

[johnywhy]

thanks for your hard work. great to have an update.

-have had some SD card-reader issues, both internal and usb.
http://murga-linux.com/puppy/viewtopic.php?t=78565

-have had connection issues with simple network tool, had to use the wizard instead (frisbee is best).
http://murga-linux.com/puppy/viewtopic.php?t=78553

-major remastering issues
http://murga-linux.com/puppy/viewtopic.php?t=78575

-xandr issues
http://murga-linux.com/puppy/viewtopic.php?t=78566

-respository issues
http://murga-linux.com/puppy/viewtopic.php?t=78559
http://murga-linux.com/puppy/viewtopic. ... 610#629610

-wine does not run
http://murga-linux.com/puppy/viewtopic.php?t=78629

i give up on racy. too many problems. unusable.

i think Puppy needs a more thorough, systematic testing cycle before new releases, imho.

[rjbrewer]

In Wary 5.3 I'm not able to establish a wireless connection with my router. In Wary 5.2.2 it is not a problem at all and working very nice.

In the log file of the Simple Network Setup (SNS), I find the following lines.

Code: Select all

STEP1c: ifconfig wlan0 down
STEP2: iwconfig wlan0 mode managed
STEP3: iwconfig wlan0 channel 3
STEP4: iwconfig wlan0 essid "2WIRE_ABC"
STEP5a: ifconfig wlan0 up
STEP5b: wpa_supplicant -B -Dwext -iwlan0 -c"/etc/simple_network_setup/wpa_supplicant.conf-2WIRE_ABC-00:18:DA:02:1A:F9"
daemon: No such device
Running: wpa_cli -i wlan0 status
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory

The driver used is iwl3945. I had a look at the SNS script (/usr/local/simple_network_setup/sns, but could not find any comment on changes since Wary 5.2.2 which could cause this.

Anybody has any ideas where it could go wrong?

Compare the /etc/network-wizard/wireless/profiles and wpa
profiles.
If not the same, drag the files from 5.2.2 to 5.3.

[MagicZaurus]

Hi rjbrewer,

thanks for the idea. Unfortunately the files seem to be exactly the same and I copied them over, just to make sure I didn't miss out anything during visual compare. But still no connection.

Maybe I need to dig more deeper.

[vtpup]

i give up on racy. too many problems. unusable.

i think Puppy needs a more thorough, systematic testing cycle before new releases, imho

-have had some SD card-reader issues, both internal and usb.
http://murga-linux.com/puppy/viewtopic.php?t=78565

Uhhh, In Lucid, not Racy.

-have had connection issues with simple network tool, had to use the wizard instead (frisbee is best).
http://murga-linux.com/puppy/viewtopic.php?t=78553

This is a problem? Three alternatives two of which work well with your computer?

-major remastering issues
http://murga-linux.com/puppy/viewtopic.php?t=78575

You remastered and said it worked fine. This seems to be a savefile to card issue, and may be procedural -- you never specified steps to reproduce this issue, and it involved a couple of different (simultaneous?) installs of a remastered OS.

-xandr issues
http://murga-linux.com/puppy/viewtopic.php?t=78566

Known bug in late X11, not Racy specifically, and a regression, therefore sometimes not present in less cutting edge Puppies.

-respository issues
http://murga-linux.com/puppy/viewtopic.php?t=78559
http://murga-linux.com/puppy/viewtopic. ... 610#629610

If you boot stock Racy53 disk (not your remaster) using boot parameter pfix=ram, do you have this issue?

-wine does not run
http://murga-linux.com/puppy/viewtopic.php?t=78629

A.) Racy does not include Wine, so it is not a subject of a its "testing cycle." It's your installation of some version of Wine, a program, that is the issue. You did not specify the method of installation, version of the program or steps to reproduce your error...

and,

B.) From reading your description you probably mean Wine isn't associated with your .exe files, rather than it does not "run".

Suggestion: rather than post that Racy is "unusable", provide "thorough, systematic testing" services to the likewise volunteer developers,

Systematic, and thorough, as in, including full steps to reproduce any discovered issues, full description of your hardware with that issue, OS version under test (so as not to confuse, say Lucid with Racy.), type of install (frugal, full), and media type, all on a per issue basis.

Imho

[johnywhy]

Uhhh, In Lucid, not Racy.

yes, my bad.

Three alternatives two of which work well with your computer?

true, but when something doesn't work that worked in the previous racy, it makes me nervous about the release.

You remastered and said it worked fine. This seems to be a savefile to card issue, and may be procedural -- you never specified steps to reproduce this issue, and it involved a couple of different (simultaneous?) installs of a remastered OS.

The first step of making the remaster worked fine, but actually installing the remaster failed. I don't think i left any steps out, and it involved only one remaster.

-xandr issues\

Known bug in late X11, not Racy specifically, and a regression, therefore sometimes not present in less cutting edge Puppies.

I believe xandr works in previous racy, but i will recheck.

-respository issues

If you boot stock Racy53 disk (not your remaster) using boot parameter pfix=ram, do you have this issue?

will test

Wine-- You did not specify the method of installation, version of the program or steps to reproduce your error...

ok, i will provide that info. I believe its a version of wine and install method that worked with previous racy, but will check.

Suggestion: provide "thorough, systematic testing" services to the likewise volunteer developers,

i'd be happy to, if racy devs care to hear it.

[vtpup]

You remastered and said it worked fine. This seems to be a savefile to card issue, and may be procedural -- you never specified steps to reproduce this issue, and it involved a couple of different (simultaneous?) installs of a remastered OS.

The first step of making the remaster worked fine, but actually installing the remaster failed. I don't think i left any steps out, and it involved only one remaster.

Steps to reproduce = open a clean install of stock Racy 53 and note down, step by step, each action you take to remaster and trial run, in detail, including screen messages and key presses to reach the repeatable issue expression so that another person can repeat (reproduce) your issue. Note software versions installed, and hardware used to do this. Report all of that as an issue. That is thorough and systematic testing, ie. providing steps to reproduce.

[cecc]

This character display problem of jwm menus exists in many versions of Puppies. So I hope there is a solution.

After I had installed the Chinese WenQuanYi MicroHei TTF font in Wary 5.3, and set the system locale to zh_CN, I clicked the "Menu" in the left bottom, the Chinese characters in jwm menus were all displayed in small cubics and could not be recognized. To solve this problem, we need to do some modifications to jwmrc in /root/.jwm.

(Below is one kind of modifiation suggested by labrador several years ago.)

Just open jwmrc in /root/.jwm and replace the dash character with a blank character in all the fontname config lines.

the original fontname config line:

Code: Select all

<font>DejaVu Sans-12:bold</font>

the modified fontname config line:

Code: Select all

<font>DejaVu Sans 12:bold</font>

When we use "DejaVu Sans-12:bold" in fontname, jwm seems to just use DejaVu Sans the English font to display the menus, and will not use Chinese WenQuanYi MicroHei TTF font to display the Chinese characters in the menus. After we replace the dash with a blank character in fontname, jwm will not recognise the fontname in jwmrc and use the suitable fonts in the system to correctly display the menu characters.

And to let all the jwm themes support Chinese menus, we need to go to /root/.jwm/themes and replace the dash character with a blank character in all the fontname config lines of all the *-jwmrc files.

Making these modifications to jwm config files will change the original jwm menu font settings, so I hope that there is a better solution for this problem.

Hope that Barry will do some modifications in Woof or shinobar will do some improvements in his QuickSetup first-run PET to solve this jwm menu display problem, so that the subsequent Puppies will not have this problem.

Thank you all!

Best Regards,

Cecc

[shinobar]

the original fontname config line:

Code: Select all

<font>DejaVu Sans-12:bold</font>

the modified fontname config line:

Code: Select all

<font>DejaVu Sans 12:bold</font>

And to let all the jwm themes support Chinese menus, we need to go to /root/.jwm/themes and replace the dash character with a blank character in all the fontname config lines of all the *-jwmrc files.

Automated tool: (need to extract and give executable permission)
http://shino.pos.to/linux/puppy/jwm_font_repair.sh.gz

Hope Barry to make some modifications in Woof or shinobar to do some improvements in his QuickSetup first-run PET to solve this jwm menu display problem, so that the subsequent Puppies will not have this problem.

So do i hope. All the Japanese versions and my multilingual versions are treated this. And the lang_support_all has the script at /usr/local/bin/jwm_font_repair.sh.
http://www.murga-linux.com/puppy/viewtopic.php?t=51702

[nubc]

I like to run versions as a live CD without saving the settings, so a version has to be reasonably right for me OOTB. I am sure a default resolution of 1280x1024 covers more circumstances than lower resolutions. Nevertheless, I *never* use this resolution because everything is too small. I prefer the resolution of 1024x768 and occasionally 800x600. In the last several recent versions of Wary (run as live CD) I have not been able to change the resolution from default 1280x1024, even when I have upgraded Xorg in Wary 5.3. This latter upgrade involved a 10-minute download by cable connection and had no success at changing the resolution. I wouldn't use Wary 5.3 as a live CD even if the upgrade had been successful at changing the default resolution, because I am not gonna waste 10 to 15 minutes changing the resolution. Is there some way to ensure that a resolution of 1024x768 is easily attainable without jumping through hoops or doing a frugal install?

[vtpup]

I like to run versions as a live CD without saving the settings, so a version has to be reasonably right for me OOTB. I am sure a default resolution of 1280x1024 covers more circumstances than lower resolutions. Nevertheless, I *never* use this resolution because everything is too small. I prefer the resolution of 1024x768 and occasionally 800x600. In the last several recent versions of Wary (run as live CD) I have not been able to change the resolution from default 1280x1024, even when I have upgraded Xorg in Wary 5.3. This latter upgrade involved a 10-minute download by cable connection and had no success at changing the resolution. I wouldn't use Wary 5.3 as a live CD even if the upgrade had been successful at changing the default resolution, because I am not gonna waste 10 to 15 minutes changing the resolution. Is there some way to ensure that a resolution of 1024x768 is easily attainable without jumping through hoops or doing a frugal install?

remaster?

Personal savefile on the CD and then close it?

[nubc]

I guess I meant this as a suggestion for future editions of Wary, and any other Puppy for that matter. Just provide two possible resolutions and I'll be happy. Or allow resolution selection earlier in the setup process so that resolution is actually selectable when running as a live CD. If the resolution of 1024x768x16 is preselected in my Xorg setup, does this not indicate that 1024x768x16 resolution is standard and suitable for my computer?

Edit: In Windows, user can make a 1280x 1024 resolution look like 1024x768 by going into advanced Display settings to change the DPI setting from Normal size (96 dpi) to Large size (120 dpi). Nice and quick tweak, but Windows asks you to reboot.
http://blogs.msdn.com/b/fontblog/archiv ... 90490.aspx

[cecc]

Shinobar,

Thank you for your reply!

Hope that Puppy will be better in the future.

Also thank Barry and you all who has devoted your time and intelligence to this small and lovely distribution!

Best Regards,

Cecc