Puppy 4 DINGO

[rerwin]

Barry,
I was going to wait for later, but since you requested easy-to-fix issues...

In improving the formatting of bootsysinit.log, the "loading" messages did not get indented as I recommended. Please insert two spaces before the text in lines 124 and 174 of /etc/rc.d/rc.modules, as:

Code: Select all

    echo "  loading module $MODULE"

Thanks.
Richard

[prit1]

@Barryk: My Averatec 3225 HS laptop with RT2500 wireless module works perfectly well in Puppy version 2.17.1. But in the Dingo 4.00. I have to run the Network Wizard everytime I login and only then the wireless network would start working. This is inspite of the profile being saved. This happens for both kernels.

[geneven]

"With the .25 kernel, the bcm43xx module is replaced by b43 and b43legacy modules. "

Well, they don't work for me. I guess I'll have to stay with the older kernel.

[Lobster]

You are the second person reporting this problem. I have a suspicion that the problem experienced with the .23/.24 kernels and usb has re-emerged.

Suddenly realised - I am using a ps2 mouse and keyboard (both lock) During the bootup at the choose locale, I can not scroll down - no keyboard response. Once I got to the desktop but the mouse was not working . . .

[jonyo]

Just a quick report. Compaq sr2020nx (AMD Athlon 64 3500+ / 2.2 GHz, NVIDIA GeForce 6150 LE) 2 gig ram, d-link dwl-g122 ver b1 usb wifi dongle using the win Netrtusb .inf (rt2500) with wep 64 hex. Thing's worked on everything I've tried right down through to 2.12.

Didn't see the native rt2570 available so dloaded the enhanced 1.6.1 ..but haven't sorted that out yet.

Have to use xvesa cos I lose the mouse cursor with xorg (prob goes back to 2.15 for me on this box), Apparently someone else does also with the same onboard graphics. Haven't tried the Nvidia driver yet though.. Thought I had a fix suggested by prehistoric the other day but the prob came back, but is much better.

At first glance, quite a few changes here from 3xx soo..have some catching up to doo..

dingo k2.6.25 setup with linNwin & xpsp2

[HairyWill]

Will,
I'm working through your suggestions. I don't understand something about your problem with vi. What sort of file causes Rox to run vi? If I click on a text file, Geany starts, but you have stated that "clicking on various text files" causes an error about vi. I don't understand.

Try clicking a README file in a source package. Rox lists its mimetype as text/x-readme

[veronicathecow]

Hi Barry, I am afraid this Sanity Check has bounced

2.6.25 Kernel, MD5 sum correct. disk verified on blowing. Intel D201GLY2 MB

Live CD will not boot

Sticks at booting the kernel.
Tried adding acpi=off result the same
Tried pfix=ram and acpi=off result same.

Previous version booted okay with acpi=off
Thanks Tony
P.S. fascinating about windmill please lets us know more and wish you well. I'm installing a water turbine and have a wood stove.

[urban soul]

One of the contributors to the Network Wizard has put that code in that puts up a message about WPA not being supported ...but, how to know that?

Can anyone think of a better way to do the above? or, do we just have to update it regularly?

I just PM'ed you and Will a new version of wag-profiles.sh. I disabled this 'warning'. I am working on auto-dedecting the encryption type (and as a requisite testing the driver for WPA support). I just need one more week or so.

Urban

[HairyWill]

Pupdial has been broke for me since beta1. My init2 string is Init2 = AT$QCMDR=3, but shows up as AT3. I guess the $ is messing it up in beta2 - sc1. If i change line 177 from:
<input>echo "${INIT2M}"</input>
to
<default>"${INIT2M}"</default>
like it was in beta1, then it works correctly as it did in the past. I guess line 170, which is init1, would have the same problem.

arrrrgggghhhh
The reason it was changed was to allow quotation marks
Kirk can you try leaving 170, 177 as they come in the iso and replacing lines 79 and 80 with
INIT1M="`cat /etc/wvdial.conf | grep '^Init1 = ' | cut -f 3-12 -d ' '| sed 's/"/\\\"/g;s/\\$/\\\\$/g;'`"
INIT2M="`cat /etc/wvdial.conf | grep '^Init2 = ' | cut -f 3-12 -d ' '| sed 's/"/\\\"/g;s/\\$/\\\\$/g;'`"
Warning I haven't put that in a code block to avoid stretching the page.

Does anybody else know of any interesting characters that might break gtkdialog. An obvious candidate would be < > I really hope there are not any connection strings that require these.

[divisionmd]

Hello,

Just wanted to say this:

Dual core and quad core computers works perfect with Dingo RC 4!

Now when i type "cat /proc/cpuinfo" it lists all cpus!

Great work Barry!

Best regards,
Johan

[BarryK]

5-Had some seamonkey crashes when running Flash Player. Tried to diagnose by launching seamonkey from the shell but haven't gotten it to crash again. The only info I've gotten is this warning:

6-can't copy and paste between rxvt and geany.

It's an old bug that SeaMonkey crashes under certain circumstances. I can reproduce it in youtube by closing a tab when a video is still running.

The daemon that automatically copies the selection buffer to clipboard is no longer there.
For rxvt, highlight some text, then in geany paste it by pressing the middle button. This works via the selection buffer, not the clipboard.

[BarryK]

Will,
I'm working through your suggestions. I don't understand something about your problem with vi. What sort of file causes Rox to run vi? If I click on a text file, Geany starts, but you have stated that "clicking on various text files" causes an error about vi. I don't understand.

Try clicking a README file in a source package. Rox lists its mimetype as text/x-readme

Ok, fixed.

[BarryK]

Pupdial has been broke for me since beta1. My init2 string is Init2 = AT$QCMDR=3, but shows up as AT3. I guess the $ is messing it up in beta2 - sc1. If i change line 177 from:
<input>echo "${INIT2M}"</input>
to
<default>"${INIT2M}"</default>
like it was in beta1, then it works correctly as it did in the past. I guess line 170, which is init1, would have the same problem.

arrrrgggghhhh
The reason it was changed was to allow quotation marks
Kirk can you try leaving 170, 177 as they come in the iso and replacing lines 79 and 80 with
INIT1M="`cat /etc/wvdial.conf | grep '^Init1 = ' | cut -f 3-12 -d ' '| sed 's/"/\\\"/g;s/\\$/\\\\$/g;'`"
INIT2M="`cat /etc/wvdial.conf | grep '^Init2 = ' | cut -f 3-12 -d ' '| sed 's/"/\\\"/g;s/\\$/\\\\$/g;'`"
Warning I haven't put that in a code block to avoid stretching the page.

Does anybody else know of any interesting characters that might break gtkdialog. An obvious candidate would be < > I really hope there are not any connection strings that require these.

Ha ha, a little hiccup. If you guys can sort that out pronto, that'll be great. I'm itching to get 4.00 "out the door" as I want to get going on the next version.

[BarryK]

Pupdial has been broke for me since beta1. My init2 string is Init2 = AT$QCMDR=3, but shows up as AT3. I guess the $ is messing it up in beta2 - sc1. If i change line 177 from:
<input>echo "${INIT2M}"</input>
to
<default>"${INIT2M}"</default>
like it was in beta1, then it works correctly as it did in the past. I guess line 170, which is init1, would have the same problem.

arrrrgggghhhh
The reason it was changed was to allow quotation marks
Kirk can you try leaving 170, 177 as they come in the iso and replacing lines 79 and 80 with
INIT1M="`cat /etc/wvdial.conf | grep '^Init1 = ' | cut -f 3-12 -d ' '| sed 's/"/\\\"/g;s/\\$/\\\\$/g;'`"
INIT2M="`cat /etc/wvdial.conf | grep '^Init2 = ' | cut -f 3-12 -d ' '| sed 's/"/\\\"/g;s/\\$/\\\\$/g;'`"
Warning I haven't put that in a code block to avoid stretching the page.

Does anybody else know of any interesting characters that might break gtkdialog. An obvious candidate would be < > I really hope there are not any connection strings that require these.

Will,
I put your fix into pupdial. It seems ok to me. I don't have access to dialup from here, but I can at least test that it saves to /etc/wvdial.conf ok, and reloads, gtkdialog is not broken.

[BarryK]

Barry,
I was going to wait for later, but since you requested easy-to-fix issues...

In improving the formatting of bootsysinit.log, the "loading" messages did not get indented as I recommended. Please insert two spaces before the text in lines 124 and 174 of /etc/rc.d/rc.modules, as:

Code: Select all

    echo "  loading module $MODULE"

Thanks.
Richard

Ok, I've done that.

Note, I didn't put in some of your last changes, which were mostly cosmetic, as I ran into some potential issues that I wanted to think about, but decided to leave that for after 4.00. You will notice that I put in your code to unload some modem modules, then commented it out -- thinking that partly through, I saw some logical issues, so decided to just freeze everything as it was.

[ARAN]

Hello !

One of the most used input methods for Puppy Users (the Keyboard) don't work for me and a asume for a lot of other people too !

I am running at the moment Puppy Dingo 4 with Xvesa.

Changing the Keyboardlayout using the Programm

Menu -> Desktop -> Choose Locale

don't has any effects on the keyboard layout switching !

Whats wrong with changing the Kayboardlayout !
Using Puppy Linux with a different keyboard layout isn't really funny.

[melhundo]

I am running at the moment Puppy Dingo 4 with Xvesa.

That is the problem. Don't even touch Xvesa.

[BarryK]

Hello !

One of the most used input methods for Puppy Users (the Keyboard) don't work for me and a asume for a lot of other people too !

I am running at the moment Puppy Dingo 4 with Xvesa.

Changing the Keyboardlayout using the Programm

Menu -> Desktop -> Choose Locale

don't has any effects on the keyboard layout switching !

Whats wrong with changing the Kayboardlayout !
Using Puppy Linux with a different keyboard layout isn't really funny.

I presume that you want to change the keyboard layout for your country? Then you have done the wrong thing. You need to run the Mouse/Keyboard Wizard.

...which works perfectly with Xvesa, I just tested it.

Just click on the 'setup' icon on the desktop and all setup choices are neatly presented.

Basides, I don't understand something. The first time that you boot Puppy, a dialog box comes up and asks you what layout you want, and you choose that. So, what's the problem?

Do you mean something else by the words "keyboard layout"?

[kirk]

arrrrgggghhhh Wink
The reason it was changed was to allow quotation marks
Kirk can you try leaving 170, 177 as they come in the iso and replacing lines 79 and 80 with
INIT1M="`cat /etc/wvdial.conf | grep '^Init1 = ' | cut -f 3-12 -d ' '| sed 's/"/\\\\"/g;s/\\$/\\\\$/g;'`"
INIT2M="`cat /etc/wvdial.conf | grep '^Init2 = ' | cut -f 3-12 -d ' '| sed 's/"/\\\\"/g;s/\\$/\\\\$/g;'`"

Thanks, that fixes it!


Also, /root/ghttpd is still there. There is no executable, just the remains of the web server package. It should be deleted. If you want a small web server, Monkey works well. On your blog, you said it was a official pet package, but I don't see it on ibiblio. I'll attach it just in case you want it.

[tempestuous]

One of the contributors to the Network Wizard has put that code in that puts up a message about WPA not being supported

Yes, that was Dougal and me.
Whether the Network Wizard should warn about modules not supporting WPA is up for discussion (I think it should), but the wag-profiles.sh script definitely must be updated whenever new wifi modules are introduced - because wpa_supplicant needs a different "-D" (driver) parameter depending on what module is in use.
You will notice that the WPA section of the wag-profiles.sh script not only defines the modules which are WPA-compatible, but more importantly it specifies what "-D" parameter to pass to wpa_supplicant. The modules and "D" parameters that are currently listed in the wag-profiles script are absolutely correct thus far ... but of course, recent kernels now provide some new wifi kernel modules which must be incorporated.

How to know what -D parameter applies to each wifi module? Careful reading of the wpa_supplicant README and also the documentation provided with the source code of each wifi driver. I discussed this at length with rarsa when he first wrote the Network Wizard. Since then, I have helped Dougal add rt61/rt73 (Ralink) and r8180/r8187 (Realtek). We also added WPA2 support, which requires a significantly different configuration file for wpa_supplicant.

I just downloaded Puppy-4.00-k2.6.25 to have a look at the new wifi modules.
These are the new modules which need to be added to the Wizard:
D parameter "wext" -
ath5k
b43
b43legacy
iwl3945
iwl4965
rndis_wlan (Broadcom USB)
rt61pci
rt73usb

D parameter "ipw" -
rtl8180
rtl8187

Notice that the new rt61pci and rt73usb modules use the "wext" D parameter, whereas the old rt61 and rt73 modules use the "ralink" D parameter. This is because the new modules are from a completely revised development stream; the "next-generation" rt2x00 series.

I cannot guarantee that the new driver parameters I have specified are completely correct. I do not own all of these devices, and the information is difficult to glean from the web. Testing may prove me wrong on some of these.