Puppy 4.3.1 -- bug reports and suggestions

Please post any bugs you have found
Message
Author
User avatar
rerwin
Posts: 2017
Joined: Wed 24 Aug 2005, 22:50
Location: Maine, USA

Dialup/wireless "modem fix pack 7" available for beta tests!

#281 Post by rerwin »

Wireless modem users:
I have posted an upgrade to modem support, particularly for wireless modems, and need users to try it out and to report any for regressions and or failures to function reasonably.
http://www.murga-linux.com/puppy/viewto ... 074#431074

The new functionality is for complex modem cases. Modems using other than ttyUSB0 have been difficult to make work. In the upgrade, that should be more automated, to get the correct port. The upgrade also addresses the complications of having multiple USB-serial-type devices plugged in, not all of which are modems.

To use the upgrade, be sure that the "modem fix pack 6" dotpet (only), available on page 16 of this thread, is already installed, before installing the four upgrade packages.

The sooner people can verify that the upgrade works and does not mess up anything, the sooner it can be integrated into Woof. Thank you for any help you can provide with testing.
Richard


Additional item: I have re-uploaded the "modem_fix_to_431" package on page 16 of this thread to correct a Conexant modem problem that may prevent detection of a USB modem if there is a built-in Conexant. The download count when I uploaded was 199, so later downloads of it contain the fix. Re-download and re-install it if you have a Conexant (DGC, HCF, HSF) modem interfering with detection of a USB modem.
Richard

MOB-i-L
Posts: 7
Joined: Thu 02 Sep 2010, 11:39

connect icon on desktop opens PPPOE [Solved]

#282 Post by MOB-i-L »

The connect icon on the desktop opens PPPOE instead of a more general program with several buttons for different connection types that it used to open before (I used the LAN-button for wireless). Even if I restart the problem remains. I don't think it's easy to reproduce this on another computer -- maybe it changed because of lack of RAM. How can I change it back to the way it was originally? Which program was used originally? How do I change which program a desktop icon starts?

Luckily I can still start wireless by using Pwireless-0.8.4 from the Menu, but it doesn't have the same features as the other program.

I use Puppy 4.3.1 with kernel 2.6.25.16 and window manager JWM.

Edit:
I succeeded in solving it by right-clicking and choosing 'Execute the Internet Connection Wizard' and changing Desktop/tray to Internet Connection Wizard. It must have been accidentally changed to PPPoE.

Shep
Posts: 878
Joined: Sat 08 Nov 2008, 07:55
Location: Australia

#283 Post by Shep »

nubc wrote:After messing around for several hours, I have come to the conclusion that Puppy 4.3.1 cannot play back a (downloaded) FLV file, probably because it sees the wrong format, perhaps mistaking flv for mp3, as indicated by assigned icon.
Correct, particularly if you are talking about videos from youtube. It seems that youtube keeps making subtle format changes that place its flv format incompatible with established players. Until mplayer catches up, videos that you download from youtube will play in youtube's flash player but probably not in mplayer. Most flash videos from other sites will probably continue to play okay in mplayer. :)

There are browser add-ons that will convert to another format, allowing you to save your youtube videos in another format which can then later be played in mplayer. Whether the add-ons will accommodate the latest of youtube's changes is for you to discover.

User avatar
Karl Godt
Posts: 4199
Joined: Sun 20 Jun 2010, 13:52
Location: Kiel,Germany

#284 Post by Karl Godt »

Subject: filemnt won't mount two files with same base name.
(Note: I am reporting this in the Puppy 4.3.1 thread because 4.3.1 is the Puppy that I have. The bug could certainly exist in older and newer puppies.)
I can confess, that filemnt.gz is working on dpup-005.

I really missed that feature !

While running frugal with a lot `acpitool -s` to suspend to ram I was able to mount the booted /mnt/+mnt+home+dpup005+dpup-005.sfs and the remastered /mnt/+mnt+home+dpup-005-06-xephem+dpup-005.sfs by clicking the icon at rox.

I had to look at /etc/DISTRO_SPECS to believe it !

I am very happy about that !
1000 Thanks, npierce !

robert1968
Posts: 9
Joined: Thu 10 Dec 2009, 12:45

USB mount problem - Puppy 431 on stylistic c500

#285 Post by robert1968 »

Hi,

Usually I'm happy with Puppy 431 on an old Fujitsu Stylistic c500 tablet.
Suspend, touchpad (fpit driver) is working fine.

Nowdays I realised USB mount doesn't work.
It does work few month ago, but now not.

I saw, usb modules are present, dmesg shows sdb device recognised, but
no automount. Even no way to mount manually.

dmesg:

usb 1-1: new full speed USB device using uhci_hcd and address 2
usb 1-1: configuration #1 chosen from 1 choice
scsi2 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
scsi 2:0:0:0: Direct-Access OTi Flash Disk 2.00 PQ: 0 ANSI: 2
usb-storage: device scan complete
ready
sd 2:0:0:0: [sdb] 256000 512-byte hardware sectors: (131 MB/125 MiB)
sd 2:0:0:0: [sdb] Write Protect is off
sd 2:0:0:0: [sdb] Mode Sense: 03 00 00 00
sd 2:0:0:0: [sdb] Assuming drive cache: write through
sd 2:0:0:0: [sdb] Assuming drive cache: write through
sdb: sdb1
sd 2:0:0:0: [sdb] Attached SCSI removable disk

Mount:
# mount /dev/sdb1 /mnt/sdb1
mount: /dev/sdb1: can't read superblock

I tried different pendrives.

Any help is appreciated.
Robert

User avatar
Karl Godt
Posts: 4199
Joined: Sun 20 Jun 2010, 13:52
Location: Kiel,Germany

#286 Post by Karl Godt »

mount: /dev/sdb1: can't read superblock
fsck

if fsck can't read the superblock also

# dumpe2fs /dev/hdd1
dumpe2fs 1.41.9 (22-Aug-2009)
Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem UUID: 235d2897-72ab-4945-b443-30dc0eeeb3e0
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file
Filesystem flags: signed_directory_hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 404000
Block count: 1614524
Reserved block count: 80726
Free blocks: 1039906
Free inodes: 344866
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 394
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8080
Inode blocks per group: 505
Filesystem created: Sat Jan 1 16:15:12 2011
Last mount time: Thu Jan 13 11:57:19 2011
Last write time: Thu Jan 13 11:57:19 2011
Mount count: 3
Maximum mount count: 36
Last checked: Wed Jan 12 13:25:14 2011
Check interval: 15552000 (6 months)
Next check after: Mon Jul 11 13:25:14 2011
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
Default directory hash: half_md4
Directory Hash Seed: 5cfa5913-9096-4114-836b-7ee7bfaa00bf
Journal backup: inode blocks
Journal size: 128M


Group 0: (Blocks 0-32767)
Primary superblock at 0, Group descriptors at 1-1
Reserved GDT blocks at 2-395
Block bitmap at 396 (+396), Inode bitmap at 397 (+397)
Inode table at 398-902 (+398)
23777 free blocks, 4927 free inodes, 565 directories
Free blocks: 915-6143, 6225-20479, 20482-24575, 29253, 29258-29265, 29313-29316, 32582-32767
Free inodes: 3154-8080
Group 1: (Blocks 32768-65535)

Backup superblock at 32768, Group descriptors at 32769-32769

which should give an average backup superblock

# fsck --help fsck 1.41.9 (22-Aug-2009)
fsck.ext3: invalid option -- h
Usage: fsck.ext3 [-panyrcdfvtDFV] [-b superblock] [-B blocksize]
[-I inode_buffer_blocks] [-P process_inode_size]
[-l|-L bad_blocks_file] [-C fd] [-j external_journal]
[-E extended-options] device

Emergency help:
-p Automatic repair (no questions)
-n Make no changes to the filesystem
-y Assume "yes" to all questions
-c Check for bad blocks and add them to the badblock list
-f Force checking even if filesystem is marked clean
-v Be verbose

-b superblock Use alternative superblock

fsck -b 32768 -n -f -v /dev/DEVICE

photor
Posts: 17
Joined: Wed 21 May 2008, 01:51

#287 Post by photor »

What's the default user name and password?
I need this when it is dropped to a terminal login.
:roll:

Shep
Posts: 878
Joined: Sat 08 Nov 2008, 07:55
Location: Australia

#288 Post by Shep »

SundayForever wrote:Unless I had made some mistake (which I suspect I haven't), Puppy saw that there was another Puppy nearby and mixed things. In the partition in which the folders are located the are an opera and profile folders that were created when I installed Opera in Puppy 4.3. Maybe this confounded the boot process.
If you have been using a previous frugal install and decided to use a 4.3.1 live CD then I expect it would see the older savefile and ask did you wish to upgrade it to 4.3.1.

If you had puppy software on the HDD but outside the savefile then that software is accessible by any puppy. It may be advantageous to install additional browsers this way, so that you need to install only once and it can be used by your other puppies.

Shep
Posts: 878
Joined: Sat 08 Nov 2008, 07:55
Location: Australia

#289 Post by Shep »

photor wrote:What's the default user name and password?
I need this when it is dropped to a terminal login.
:roll:
Welcome back! 8)

Normally you don't encounter a login. MENU > Utility > Terminal Emulator

Once you get to the terminal, what do you want to do?

User avatar
Argolance
Posts: 3767
Joined: Sun 06 Jan 2008, 22:57
Location: PORT-BRILLET (Mayenne - France)
Contact:

-grabserver Xlock option and JWM transparency effects!

#290 Post by Argolance »

Hello,
When transparency enabled (/root/.xinitrc => #composite & transparency kcompmgr -n &), Xlock doesn't show both screen saver picture and text that prompts user to give the password. However I noticed this problem disappears if the option -grabserver is deleted in /usr/local/apps/Xlock/AppRunn lines n°34 et n°143 and in /.config/Xlock/xlockscreenparams...
My question: what is the option -grabserver used for and what kind of other problem(s) may this modification possibly cause?

Thank you!
Best regards.

kalisti
Posts: 23
Joined: Wed 11 May 2011, 16:14

#291 Post by kalisti »

I guess this may be a silly thing to write a bug report about, but it bugs me, so here it is..

The clock is reset each time I boot puppy 4.3.1 from my save file. I don't boot often from RAM, and I am not about to get this puppy running the way I want it to all over again just to fix the time.

I go to Menu > Desktop, Set Time Zone > Set to GMT +1 > OK -- time is still off. If I set it by going Menu > Desktop > Set time and date -- the clock only gives the correct time for that session, untill I power off/reboot.

Jasper

#292 Post by Jasper »

Hi,

It may be worth setting your time zone to a city rather than using the GMT method.

It may be a waste of your time, but it worked for me when I tried 4.3.1.

My regards

kalisti
Posts: 23
Joined: Wed 11 May 2011, 16:14

#293 Post by kalisti »

Well, I gave it some time, and it seems to be completely random, no matter which method I use. Sometimes she will give the right time for a few days, and then it keeps setting it back to 5:30 AM for the next few days.

How is the clock updated, does it use a clock in my hardware or from the internet, or..? Maybe it's not puppy's fault but my computer?

Edit: Actually I gave up constantly resetting the time, but I just tried again, and no matter whether I use the GMT or the Country method, it doesn't change the time. Only using 'Set time and date' it will, but for this session only..

I forgot to mention I upgraded my 4.3.1 using rerwin's upgrade. I can't recall if the clock did do it's job properly before upgrading.

User avatar
Karl Godt
Posts: 4199
Joined: Sun 20 Jun 2010, 13:52
Location: Kiel,Germany

#294 Post by Karl Godt »

check

Code: Select all

readlink /etc/localtime
look for rtc-cmos,rtc_core,rtc_lib drivers are loaded using `lsmod | grep rtc` , put them into `bootmanager` if not ( I'll have to do this , too ) .
of course , check battery .
you could try something like

Code: Select all

hwclock --debug --adjust
see man hwclock .

kalisti
Posts: 23
Joined: Wed 11 May 2011, 16:14

#295 Post by kalisti »

Karl, thanks for helping,

Where are these drivers located?

Check battery, don't have laptop.

Time should be GMT +1
Clock is reset to 19:06 even though it was displaying the correct time(I told puppy what the right time was last time I posted, maybe that is why it shows. I'm too hungover to read a man page on a clock I'm afraid.

Can't seem to paste from rxvt selecting and pasting with middle mouse button, so here's an screenshot.

Changing the hwclock time didn't change the time on my desktop BTW.

Why 'so many seconds since 1969'? Is 1969 the year of the first HW clock?
Attachments
screen.jpg
Screen rxvt
(51.65 KiB) Downloaded 546 times

User avatar
Karl Godt
Posts: 4199
Joined: Sun 20 Jun 2010, 13:52
Location: Kiel,Germany

#296 Post by Karl Godt »

Oops : Puppy kernels are configured with rtc inside :

Code: Select all

grep -n -i rtc /mnt/hdb5/etc/modules/DOTconfig-K2.6.30.5-01SEPT09-TICKLESS-SMP
240:CONFIG_HPET_EMULATE_RTC=y
1939:CONFIG_RTC=y
2757:CONFIG_SND_RTCTIMER=m
2758:CONFIG_SND_SEQ_RTCTIMER_DEFAULT=y
3194:# CONFIG_RTC_CLASS is not set

I had much more drivers enabled as usual puppies in my kernel configurations and applying the Standard-431.config into `make menuconfig` revealed :
< > Real Time Clock --->
which normally means : ""# CONFIG_RTC is not set""

So there is not much in
find /sys -name "*rtc*"
/sys/devices/virtual/misc/rtc
/sys/class/misc/rtc
or
modprobe -l | grep -i rtc
but

Code: Select all

 file /proc/driver/rtc
/proc/driver/rtc: empty

Code: Select all

cat !$
cat /proc/driver/rtc
rtc_time : 10:11:19
rtc_date : 2011-06-13
rtc_epoch : 1900
alarm : **:**:**
DST_enable : no
BCD : yes
24hr : yes
square_wave : no
alarm_IRQ : no
update_IRQ : no
periodic_IRQ : no
periodic_freq : 0
batt_status : okay

I am running the 2.6.31.14 IDE kernel today and it is the same about "rtc"

And this is from the kernel source documentation rtc.txt :
All PCs (even Alpha machines) have a Real Time Clock built into them.
Usually they are built into the chipset of the computer, but some may
actually have a Motorola MC146818 (or clone) on the board. This is the
clock that keeps the date and time while your computer is turned off.

ACPI has standardized that MC146818 functionality, and extended it in
a few ways (enabling longer alarm periods, and wake-from-hibernate).
That functionality is NOT exposed in the old driver.

However it can also be used to generate signals from a slow 2Hz to a
relatively fast 8192Hz, in increments of powers of two. These signals
are reported by interrupt number 8. (Oh! So *that* is what IRQ 8 is
for...) It can also function as a 24hr alarm, raising IRQ 8 when the
alarm goes off. The alarm can also be programmed to only check any
subset of the three programmable values, meaning that it could be set to
ring on the 30th second of the 30th minute of every hour, for example.
The clock can also be set to generate an interrupt upon every clock
update, thus generating a 1Hz signal.

The interrupts are reported via /dev/rtc (major 10, minor 135, read only
character device) in the form of an unsigned long. The low byte contains
the type of interrupt (update-done, alarm-rang, or periodic) that was
raised, and the remaining bytes contain the number of interrupts since
the last read. Status information is reported through the pseudo-file
/proc/driver/rtc if the /proc filesystem was enabled. The driver has
built in locking so that only one process is allowed to have the /dev/rtc
interface open at a time.
For the +-1 GMT confusion there is written some in the 5series projects threads also ; but /usr/sbin/timezone-set contains code to try to translate '-' to '+' and reverse for GMT but maybe grep sometimes likes +- escaped and sometimes not or there is missing a !not in the if-statement .

Code: Select all

89,90c89,90
< 
< if [ "`echo -n "$ZONERETVAL" | grep 'GMT' | grep '\+'`" = "" ];then
---
> 
> if [ "`echo -n "$ZONERETVAL" | grep 'GMT' | grep '+'`" != "" ];then
The second file would be /usr/sbin/set_hwclock_type for the content of /etc/clock (localtime<>utc) .

And I meant the button-cell of 3V on the board inside the tower .

And for the year 1970 thingy try to read wikipedia about computing languages A and B .

kalisti
Posts: 23
Joined: Wed 11 May 2011, 16:14

#297 Post by kalisti »

Ok, well, thanks. I tried those things, aside from the coding you posted at the end, here's the output again in a screenshot.

Another thing I did was follow the help in psync, which reads
FIRST:
If you have not already done so via Menu/Desktop/Set Timezone, then you must first set your Timezone geographically.
i.e Europe/London - Europe/Madrid etc to match your nearest location. Scroll through the Puppy menu Timezone list to set it to nearest location.
NOT by GMT offset. This is because the built in commands use the locale settings.
You must now reboot to make the setting active. This is before running Psync
Locale zoneinfo contains information on offset plus DST etc. (Daylight Savings Time) allowing Psync to set time correctly according to your location.
Setting the timezone this way also allows the desktop clock to auto change for DST.
GMT file is just a numerical offset etc. which means Psync may ignore it and set your clock according to server location. Which may be set to UTC and cause your clock to be set up to 2 hours off.
Which, once again, worked for that session only.
Attachments
screen2.jpg
(29.63 KiB) Downloaded 1054 times

kalisti
Posts: 23
Joined: Wed 11 May 2011, 16:14

#298 Post by kalisti »

Basically what is happening is that Puppy, or Computer, or whoever, is not keeping time when turned off. If I power off at 5:30am, and power on at 6PM, it will read 5:31am.

Another thing, small, but buggy, is the 'show desktop' icon on the tray. I have to click twice when windows are open on screen. First time is simply ignore.

I can deal with the time being messy and having to click twice on the desktop icon. But, as I see it, they're bugs, and this is a bug thread.

User avatar
rjbrewer
Posts: 4405
Joined: Tue 22 Jan 2008, 21:41
Location: merriam, kansas

#299 Post by rjbrewer »

kalisti wrote:Basically what is happening is that Puppy, or Computer, or whoever, is not keeping time when turned off. If I power off at 5:30am, and power on at 6PM, it will read 5:31am.

Another thing, small, but buggy, is the 'show desktop' icon on the tray. I have to click twice when windows are open on screen. First time is simply ignore.

I can deal with the time being messy and having to click twice on the desktop icon. But, as I see it, they're bugs, and this is a bug thread.
Motherboards (laptop or desktop) have a button cell battery that
the bios (cmos) needs for changing settings and keeping track of
time, etc.
A worn out battery gives a time from years ago on each reboot.

Inspiron 700m, Pent.M 1.6Ghz, 1Gb ram.
Msi Wind U100, N270 1.6>2.0Ghz, 1.5Gb ram.
Eeepc 8g 701, 900Mhz, 1Gb ram.
Full installs

Jasper

#300 Post by Jasper »

Hi all,

Does 4.3.1 have Psync (possibly in the Desktop menu) and if not is there a pet that would work?

My regards

Post Reply