Puppy 4 Beta Bugs

Please post any bugs you have found
Message
Author
TuRDMaN
Posts: 4
Joined: Wed 05 Sep 2007, 04:38

#76 Post by TuRDMaN »

Has anyone else been able to install .pup files? Because I have the same problem as the other users who posted in this thread before me (after installing the packages that puppy says are necessary, clicking on a .pup file just makes a box pop up with the name of the file, nothing else).

User avatar
capoverde
Posts: 232
Joined: Wed 28 Jun 2006, 21:36
Location: Sanremo (Italy) with fine seaview

#77 Post by capoverde »

Booted regularly and fast, but missed on the very first thing I tried -- going for 4 virtual desktops instead of 2. :(

Tried to restart both JWM and X, but no change as for the described problem -- the message "New config corrupt. Keeping original" comes out anyway. But restarting X does change things: all mountable memory device icons appear at the bottom of the screen and the message for first-time-run help appears at its top.

This, it seems, should happen without any X restart, but doesn't: apparently something isn't initialized correctly -- running XVesa at 1280x1024 on a Celeron 2800, Asustek 775i65GV MB (Intel 865GV chipset).

@disciple: no swap partitions are seen here either (!? never noticed that).
Last edited by capoverde on Wed 09 Apr 2008, 11:06, edited 1 time in total.

nic2109
Posts: 405
Joined: Mon 01 Jan 2007, 20:24
Location: Hayslope, near Middlemarch, Midlands, England

Re: Solved wireless network bug reported earlier

#78 Post by nic2109 »

bde wrote:
nic2109 wrote: Sorry but this didn't work for me.

There seem to be several aspects to this bug, for me at any rate.
......

Steps 3 and 4 are the strange ones, so if that helps anyone trouble-shoot, then great!
Nick: What type of wireless card do you have? Also, have you tried or been able to make the wireless connection using manual setup? My wireless card was detected automatically, and wlan0 interface was created. I hit wlan0 in puppy network wizard, and created a profile using essid, key, etc., checking the applicable options. Next, I saved and used the profile. Test wlan0 passed fine. Auto DHCP got the address and made the connection. Upon successful connection, both the top part and the bottom part of blinky blinks.

In the blinky, when the top part blinks it is sending data out; when the bottom part blinks it is receiving data back upon successful connection with IP address allocated. Have you seen the bottom part of blinky flash? Also, what type of encryption (none, wep, wpa, wpa2) are you using for communication with wireless router?
@bde: I'm using WPA encrytion and it's a built-in Intel PRO/Wireless 3945A "card" on the motherboard. The Module it uses is ipw3945.

Manual setup works every time (but including the oddities already described) - it just doesn't get "remembered" for the next boot so must be repeated. I just select the profile (which it has remembered), load it and click 'Use this profile'.

Blinky doesn't really show much activity until the wizard has completed; but this is what you would anticipate.

One difference I note is that for you it's interface 'wlan0' whereas for me it's 'eth1' with wired being 'eth0'. I have no idea whether that would make a difference to your solution.

I did get 'wlan0' when the early dingo alphas were on the latest kernel and using the module ipl3945, but as that only catered for WEP and not WPA (among other reasons) Barry reverted to the previous kernel for the later alphas and now beta 1.
[color=darkblue][b][size=150]Nick[/size][/b][/color]

oli
Posts: 194
Joined: Wed 30 Aug 2006, 09:04
Location: Germany, Frankfurt

#79 Post by oli »

pppoe with wired DSL doesn't work. This is what I did within a shell:

ifconfig eth0 up

pppoe-setup (I entered the same values as in my running Puppy 2.14-configuration)

Then I checked /etc/ppp/pppoe.conf. The entries are the same as in Puppy 2.14.

pppoe-start

But I cannot connet to the internet.

It is a pity that Roaring Penguin is no longer available in Puppy. I think Roaring Penguin is a must have if Puppy wants to be (or stay) one of the most user friendly distros. As you can see pppoe-setup doesn't work and if a user always has to start a shell and enter "pppoe-start / pppoe-stop" is inconvenient.

I hope Barry will change his mind and I hope that someone can show me how to setup the internet connection.

Addendum at 2008-04-12:

It seems that I have an internet connection (see "ifconfig" below), but I cannot open a URL in Mozilla or Gftp.

# ifconfig
eth0 Link encap:Ethernet HWaddr 00:13:8F:E7:59:6A
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:27 errors:0 dropped:0 overruns:0 frame:0
TX packets:27 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1640 (1.6 KiB) TX bytes:1747 (1.7 KiB)
Interrupt:10 Base address:0x8000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:24 errors:0 dropped:0 overruns:0 frame:0
TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1680 (1.6 KiB) TX bytes:1680 (1.6 KiB)

ppp0 Link encap:Point-to-Point Protocol
inet addr:84.59.192.99 P-t-P:84.59.192.1 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1
RX packets:3 errors:8 dropped:0 overruns:0 frame:0
TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:54 (54.0 B) TX bytes:83 (83.0 B)
Last edited by oli on Sat 12 Apr 2008, 19:42, edited 3 times in total.

Sage
Posts: 5536
Joined: Tue 04 Oct 2005, 08:34
Location: GB

#80 Post by Sage »

Jesse who developed MUT, has taken some snapshots of a spectacular orange/yellow sunset
Hope you don't delete those nice plain grey and icy mountains?

But has he sent you a final of MUT2, yet?!

I ran into a minor issue with Pthingy in D4beta1 yesterday with (no)display of a USB stick. Had to revert to an earlier version with MUT to see it ; cfdisk /dev/sdxy wouldn't see it, either. All a bit deja vu.

nic2109
Posts: 405
Joined: Mon 01 Jan 2007, 20:24
Location: Hayslope, near Middlemarch, Midlands, England

#81 Post by nic2109 »

I think this has been noted before (in early alpha testing), but in Dingo PUI still appears to only have eyes for Puppy 398 and won't install any other release.

When it cannot find a "398" .sfs file it bales out with the sanity check failure message.

It's true of both CD and Directory sources.
[color=darkblue][b][size=150]Nick[/size][/b][/color]

bde
Posts: 25
Joined: Sat 29 Mar 2008, 17:36

Re: Solved wireless network bug reported earlier

#82 Post by bde »

nic2109 wrote: @bde: I'm using WPA encrytion and it's a built-in Intel PRO/Wireless 3945A "card" on the motherboard. The Module it uses is ipw3945.

Manual setup works every time (but including the oddities already described) - it just doesn't get "remembered" for the next boot so must be repeated. I just select the profile (which it has remembered), load it and click 'Use this profile'.

Blinky doesn't really show much activity until the wizard has completed; but this is what you would anticipate.

One difference I note is that for you it's interface 'wlan0' whereas for me it's 'eth1' with wired being 'eth0'. I have no idea whether that would make a difference to your solution.

I did get 'wlan0' when the early dingo alphas were on the latest kernel and using the module ipl3945, but as that only catered for WEP and not WPA (among other reasons) Barry reverted to the previous kernel for the later alphas and now beta 1.
Nick: Do you have eth1wireless in /etc directory? What does it have? I think it should have
/usr/sbin/wpa_connect.sh eth1 wext
Also, please check if /etc/wpa_supplicant.conf has the right settings (if you quote the content here please don't forget to replace with dummy key). I can not think of anything else now.

bde
Posts: 25
Joined: Sat 29 Mar 2008, 17:36

Installing pup files in Puppy 4 Beta

#83 Post by bde »

TuRDMaN wrote:Has anyone else been able to install .pup files? Because I have the same problem as the other users who posted in this thread before me (after installing the packages that puppy says are necessary, clicking on a .pup file just makes a box pop up with the name of the file, nothing else).
I was able to install .pup files. The required packages are dotpuphandler and gettext. Please install these packages, retry installing .pup file. Please report back if it worked or not.

nic2109
Posts: 405
Joined: Mon 01 Jan 2007, 20:24
Location: Hayslope, near Middlemarch, Midlands, England

Re: Solved wireless network bug reported earlier

#84 Post by nic2109 »

bde wrote:Nick: Do you have eth1wireless in /etc directory? What does it have? I think it should have
/usr/sbin/wpa_connect.sh eth1 wext
Also, please check if /etc/wpa_supplicant.conf has the right settings (if you quote the content here please don't forget to replace with dummy key). I can not think of anything else now.
Thanks for the response. I cannot check right now as I'm at work using a different PC. Shockingly it's a Windoze box - :evil: - and I've not yet convinced them to roll out Puppy 4 beta. Can't think why :wink: .

I'll check tonight and report back.

As you and I aren't alone in having this problem I doubt that it's hardware related. One of the gurus - I haven't found the post so cannot give you the name (or the link) - did mention that the issue isn't what is saved but it is the sequence of activating stuff when booting up.

Later that same day ....

1. /etc/eth1wireless does not exist

2. /etc/wpa_supplicant.conf looks like this :-

Code: Select all

ctrl_interface=/var/run/wpa_supplicant
ap_scan=2
update_config=1

network={
	ssid="*********"
	psk=********************a19c77**********6457fcde********************
	proto=WPA
	key_mgmt=WPA-PSK
	pairwise=TKIP
	group=TKIP
}
I've replaced sensitive data with **** etc. The SSID is correct, but i have no way of knowing whether the psk value is correct as it has been encrypted! I have left some of it un-asterisked to give the sense of the content. The actual value is 9 characters and not an enormous string.

I hope this is useful and helps crack this problem.
Last edited by nic2109 on Wed 09 Apr 2008, 19:25, edited 1 time in total.
[color=darkblue][b][size=150]Nick[/size][/b][/color]

oli
Posts: 194
Joined: Wed 30 Aug 2006, 09:04
Location: Germany, Frankfurt

#85 Post by oli »

The following isn't really a bug, but perhaps you can improve Puppy's hardware detection:

xorgwizard doesn't recognize my hardware (onboard graphic and Eizo monitor, connected via DVI) properly. I tested XFdrake (from PCLinuxOS) and my hardware is recognized very well. Perhaps you can have a look at XFdrake and find out why this tool has a better hardware detection than Puppy's xorgwizard.

eprv
Posts: 19
Joined: Sat 08 Mar 2008, 22:59

Re: slow download of the beta

#86 Post by eprv »

Dingo wrote:
eprv wrote:Hi, I am 3.01 user, very satisfied, would like to test 4 beta but the download for me (ADSL) is about 2kb/sec about 10 hours to complete and with this rate it is always corrupted or stopped during download. Any idea?
you can download Dingo beta from me:
http://puppylover.netsons.org/dokupuppy ... a_releases
Dingo, thank you for help but this didn't work either, after the number verification on your site nothing happened, so I will probably wait to the final 4.00

nic2109
Posts: 405
Joined: Mon 01 Jan 2007, 20:24
Location: Hayslope, near Middlemarch, Midlands, England

#87 Post by nic2109 »

oli wrote:The following isn't really a bug, but perhaps you can improve Puppy's hardware detection:

xorgwizard doesn't recognize my hardware (onboard graphic and Eizo monitor, connected via DVI) properly. I tested XFdrake (from PCLinuxOS) and my hardware is recognized very well. Perhaps you can have a look at XFdrake and find out why this tool has a better hardware detection than Puppy's xorgwizard.
Any hardware guru reading this (sorry, but it's not me) will want to know some specific details about the graphics "card". Like whether it's Intel, or nVidia, or ATi, what the model and chipset is and so on.

You could also boot up XFDrake/PCLinuxOS and (in a terminal) type

Code: Select all

modprobe -l > filename_of_your_choosing
and compare the result with the same command in Puppy using a diff utility or your very own eyeballs. My guess is that Puppy's will be a shorter list which is why you will need to be specific about your hardware so that the correct module(s) can be identified and added - if suitable.

I hope this helps, and good luck.
[color=darkblue][b][size=150]Nick[/size][/b][/color]

Wolf Pup
Posts: 637
Joined: Fri 28 Apr 2006, 01:37

#88 Post by Wolf Pup »

/usr/lib/mozilla should be a symbolic link to /usr/lib/seamonkey and the plugins in the /usr/lib/mozilla/plugins moved to /usr/lib/seamonkey/plugins. If not seamonkey will be looking in three places for plugins instead of the usual two.
[img]http://img230.imageshack.us/img230/8595/ubd6467dp2.png[/img]
[url=http://www.tinyurl.com/54tu74]Visit The Repository[/url] - Helpful and hard-to-find treats for Puppy 3.
[url=http://www.tinyurl.com/c5a68f]Click Here for Puppy Support Chat, + Helpful Links.[/url]

bde
Posts: 25
Joined: Sat 29 Mar 2008, 17:36

Re: Solved wireless network bug reported earlier

#89 Post by bde »

nic2109 wrote: Later that same day ....

1. /etc/eth1wireless does not exist

2. /etc/wpa_supplicant.conf looks like this :-

Code: Select all

ctrl_interface=/var/run/wpa_supplicant
ap_scan=2
update_config=1

network={
	ssid="*********"
	psk=********************a19c77**********6457fcde********************
	proto=WPA
	key_mgmt=WPA-PSK
	pairwise=TKIP
	group=TKIP
}
I've replaced sensitive data with **** etc. The SSID is correct, but i have no way of knowing whether the psk value is correct as it has been encrypted! I have left some of it un-asterisked to give the sense of the content. The actual value is 9 characters and not an enormous string.

I hope this is useful and helps crack this problem.
Nick: Can you check the following? From the console, type the command below, hit the enter key, and see if you get wireless connection. Assuming that /etc/wpa_supplicant.conf has the correct entry, and the wireless interface is eth1.

Code: Select all

/usr/sbin/wpa_connect.sh eth1 wext
After the connection is made, run from console:

Code: Select all

dhcpcd -t 30 -d eth1
This allocates the IP number to your comuter from the router, and you should be ready to browse. If you see error message that dhcpcd is already running, you have to kill this process, and run the above command again. To kill it, have to run

Code: Select all

ps -A | grep dhcpcd
note the PID (process ID number) on the left hand side of output, and have to run

Code: Select all

kill -9 PID
substituting the PID with the number you found above. Hope this works.
Thanks.
Last edited by bde on Wed 09 Apr 2008, 20:45, edited 3 times in total.

User avatar
rerwin
Posts: 2017
Joined: Wed 24 Aug 2005, 22:50
Location: Maine, USA

Post-install scripts missing from remastered CD

#90 Post by rerwin »

A CD remastered from a puppy with a modem does not detect that modem when booting from that CD.

The /lib/modules/firmware.dep.(kernel) file contains commented lines for each module already set up from zdrv, which can include the copying of a post-install script to /init.d, within /etc. As a result with the remastered CD, the driver modules get loaded but the script is not copied from zdrv, so the modem is "not detected".

To fix that, I added copying of the contents of /etc/init.d to the /etc/init.d directiory in the remaster, after line 348.

Code: Select all

#v3.99 post-install scripts, since /lib/modules/firmware.dep.(kernel) shows them as copied into /etc/init.d.
cp -af /etc/init.d/* /tmp/etc/init.d/   #3.99
The updated script is attached. It should be copied to /usr/sbin.
Richard
Attachments
remaster_post-install_script_fix.tar.gz
Post-install script fix for remasterpup2. Extract it to /usr/sbin.
(8.12 KiB) Downloaded 418 times

User avatar
capoverde
Posts: 232
Joined: Wed 28 Jun 2006, 21:36
Location: Sanremo (Italy) with fine seaview

#91 Post by capoverde »

Update to my previous post about having to restart X for a correct (or almost) initialization: just tried to see what happens using Xorg.

Well, nothing happens -- after a seemingly normal and successful test (at 1280x1024x32) and getting the go, the screen stays black and no key combination takes back to text mode or to reboot: total hang! The MD5 sum says the ISO file is shipshape.

Using the present LCD monitor, former (stable) releases had both Xvesa and Xorg working OK, with apparently identical behavior.

User avatar
HairyWill
Posts: 2928
Joined: Fri 26 May 2006, 23:29
Location: Southampton, UK

#92 Post by HairyWill »

Barry
You asked for ideas for stopping the battery tray app starting on desktop machines. I haven't really followed the overall problem but I suspect it might only be happening on machines that use apm rather than acpi. You can query the apm status by doing cat /proc/apm. Here are a couple of example outputs from my laptop. The first is with the power plugged in and the second is with it disconnected

Code: Select all

sh-3.00# cat /proc/apm
1.16ac 1.2 0x03 0x01 0x03 0x09 99% -1 ?
sh-3.00# cat /proc/apm
1.16ac 1.2 0x03 0x00 0x00 0x01 97% 2 min
sh-3.00#
On my laptop it is possible to test apm behaviour by booting with acpi=off apm=on
Will
contribute: [url=http://www.puppylinux.org]community website[/url], [url=http://tinyurl.com/6c3nm6]screenshots[/url], [url=http://tinyurl.com/6j2gbz]puplets[/url], [url=http://tinyurl.com/57gykn]wiki[/url], [url=http://tinyurl.com/5dgr83]rss[/url]

User avatar
floborg
Posts: 199
Joined: Thu 25 Oct 2007, 12:12
Location: Fort Worth, TX

#93 Post by floborg »

Barry asked for more info about the battery app issue:

I posted the output of lsmod in an earlier post.
I do not have a /proc/acpi directory.
I do not have a /sys/module/battery directory.

On what may be a related note, I've never been able to get CPU temperature information using any of the methods described in these forums (with Puppy 3.01).

jcagle
Posts: 637
Joined: Thu 29 Sep 2005, 20:34

#94 Post by jcagle »

Not sure that this is really a bug...

I was using the Flock web browser in Alpha 7, then went to Puppy 4 Beta...

Flock doesn't work.

first of all, libstdc++.so.5 wasn't there, so I created a symlink to the newer version that was there.

Now I get this
./flock
./flock-bin: /usr/lib/libstdc++.so.5: version `GLIBCPP_3.2' not found (required by ./flock-bin)
./flock-bin: /usr/lib/libstdc++.so.5: version `CXXABI_1.2' not found (required by ./flock-bin)
./flock-bin: /usr/lib/libstdc++.so.5: version `GLIBCPP_3.2' not found (required by ./libxpcom_core.so)
./flock-bin: /usr/lib/libstdc++.so.5: version `CXXABI_1.2' not found (required by ./libxpcom_core.so)
./flock-bin: /usr/lib/libstdc++.so.5: version `GLIBCPP_3.2' not found (required by ./libxpcom_compat.so)
Don't know that this is really a bug, but probably something flock users need to have fixed.

kirk
Posts: 1553
Joined: Fri 11 Nov 2005, 19:04
Location: florida

#95 Post by kirk »

The Battery applet problem Barry mentioned in his blog is with computers that use apm. The docs included with asapm (the battery app) says this should not happen:
This estimate is either
provided by the APM daemon or is calculated by this tool
itself. When there is no estimate available the display is
disabled.
The rc.modules2 script only checks for acpi batterys and loads the needed modules.

Disciple reported on this thread:

http://www.murga-linux.com/puppy/viewto ... 2&start=30

that this only occurs with alpha7 (and now beta1), both have the 2.6.21.7 kernel, and that it did not occur with alpha6 which has the 2.6.24.

1) So the first question is for Barry. Do you still plan on using 2.6.25 for Dingo final? If so this may be a non-problem.

2) Floborg, could you post the output of cat /proc/apm? Then we can compare it to what HairyWill posted and make some kind of test for it.


Also,

Noticed that shift-delete doesn't seem to copy text from rxvt in beta1.

I find Gxine's GUI easy to use, but Xine-ui did seem to work quite well.

Post Reply