Quirky 1.2 feedback
Quirky 1.2 isn't better than 1.1
Quirky is very nice on my system compared with other Puppies but I have to say that 1.2 isn't fast and stable like 1.1
Maybe what I am feeling it just a placebo effect or maybe I am right
I have a suggestion
There should be a utility in Quirky that will help any newbies change their DNS servers like changing them to Google DNS or OpenDns easily.
And maybe the coming 1.3 will be more speedy
Thanks a lot
Maybe what I am feeling it just a placebo effect or maybe I am right
I have a suggestion
There should be a utility in Quirky that will help any newbies change their DNS servers like changing them to Google DNS or OpenDns easily.
And maybe the coming 1.3 will be more speedy
Thanks a lot
Re: Persistant problems
There has been some recent discussion about Samba vis-a-vis setting up a fileserver and how Puppy compares to other distros.BarryK wrote:Interesting that we are getting conflicting reports about Samba. Some people are reporting it doesn't work in Quirky 1.2rc/1.2.
The last time I checked, the Samba client functions for connecting to a Windows shared printer are working correctly in Quirky.
Of course, Puppy has never contained the full Samba server functionality. I don't know if anyone has successfully tested the Samba fileserver PET from the PPM with Quirky.
On all my machines, the traytemp reading matches the one in System > Hardinfo > Sensors.BarryK wrote:Are we sure that 'traytemp' is reporting true CPU temp?
Definitely true. I have an old machine that runs close to traytemp's default threshold of 70C. I'm sure on a hot day, I could get it to trigger a warning. With other Puppies, I never would have known.So, even if the temp did spike temporarily in earlier puppies, you would not have known.
The outstanding question is whether there is something in Quirky (like the new video drivers or ACPI) that makes it run hotter. Why is it that Quirky apparently needs ondemand CPU scaling to run cool on some machines when other Puppies did not?
[Edit] I actually found a machine that runs a little hotter under 4.3.1 than with Quirky.
FYI, there have been several reports (including me) of traytemp segfaulting and never launching. I got jemimah's source code and compiled it on an offending machine, but it didn't help.
Last edited by rcrsn51 on Sun 06 Jun 2010, 12:41, edited 2 times in total.
The problem is not the script, which is executable and runs fine from the console. It just does not run at startup although it is properly linked. (This worked in Puppy 4.3.1.)Quote:
A shell script !#bin/sh does not start on booting despite link form executable in path to /root/Startup.
rcrsn51 wrote:
Can you give an example? This also works for me. Have you declared the script file executable?
It occurred to me that, if applications in Startup are not actually running at "startup," this might have some baring on traytemp and start_cpu_freq, which seem to be involved in the temperature problem.
I have tried this with abiword 2.8.3 and OpenOffice 3.1. It seems to make no difference whether I print the ps-file from CUPS-PDF or print to file. Neither provides the correct margins. Printing directly to a pdf-file works fine from both applications.drblock2 wrote:
Printing to a ps-file via CUPS-PDF still has no upper-left margin.
Can you give an example? What application are you printing from? This appears to work for me. Instead of using the CUPS-PDF driver, have you tried using "Print to File"? Most applications have this print option.
PS-files generated with the same version of OpenOffice and an earlier version of abiword are properly formatted under Puppy 4.31 using the same hardware and network setup. I might add that ps-files generated by the Apple Color LaserWriter 12 under the "un-operating system" behave normally in Quirky 1.2. Hence, the problem seems to lie with the process that generates ps-files directly from the word processor.
In general, startup routines DO work. For some reason, your problem is specific to your setup. Are none of the startup apps initializing for you?drblock2 wrote:It occurred to me that, if applications in Startup are not actually running at "startup," this might have some baring on traytemp and start_cpu_freq, which seem to be involved in the temperature problem.
OK. I can confirm the issue. Puppy 4.3.1 has Ghostscript 8.15.2 while Quirky has Ghostscript 8.15.4. Maybe there was some change that affects Postscript files.Printing to a ps-file via CUPS-PDF still has no upper-left margin.
the112-120 devx delta
Could some kind soul generate and upload the112-120 devx delta for Qiuiky please. If it's not too big.
Last edited by zygo on Sun 06 Jun 2010, 12:34, edited 1 time in total.
alternative dns servers
chrismt,
AltDNS: created by GuestToo and last updated on 09 Dec 2009 by Wolf Pup http://www.murga-linux.com/puppy/viewtopic.php?t=28177.
AltDNS: created by GuestToo and last updated on 09 Dec 2009 by Wolf Pup http://www.murga-linux.com/puppy/viewtopic.php?t=28177.
Quirky 1.2 Retro support for Agere HDA 11c1:1040 modem
Loaded Quirky 1.2 Retro K2.6.30.5 LiveCD onto my HP550 laptop
with aim of trying to get the modem
- Agere Systems HDA modem with manufacturer:model id = 11c1:1040
to work
I've forced loading of agrserial and agrmodem at bootup
Bootup screen shows that the version is 2.1.60.0.Linspire (2005-11-16)
dmesg after bootup reports:
agrmodem: module license 'Proprietary' taints kernel.
Disabling lock debugging due to kernel taint
agrsm: created 0 infos
Loading module Agere Modem Controller driver version 2.1.60.0.Linspire (2005-11-16)
ttyAGS3 at I/O 0x400 (irq = 3) is a AgereModem
agrserial: Loading module Agere Modem Interface driver version 2.1.60.0.Linspire (2005-11-16)
after command modem-stats -c "ATI3" /dev/ttyAGS3 is issued - returns Killed - dmesg reports:
BUG: unable to handle kernel NULL pointer dereference at 00000004
IP: [<f8789d53>] LXSoftModemStart+0x23/0x230 [agrmodem]
*pde = 00000000
Oops: 0000 [#1] SMP
last sysfs file: /sys/devices/pci0000:00/0000:00:1c.1/0000:10:00.0/ssb0:0/net/wlan0/statistics/tx_bytes
Modules linked in: snd_pcm_oss snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_mixer_oss i915 drm i2c_algo_bit i2c_core rfkill_input agrserial agrmodem(P) arc4 ecb b43 mac80211 input_polldev led_class rfkill cfg80211 ohci_hcd snd_hda_codec_analog snd_hda_intel snd_hda_codec snd_pcm snd_page_alloc snd_timer snd_hwdep snd soundcore serio_raw pcspkr shpchp pci_hotplug e1000e intel_agp agpgart video output wmi fan battery container evdev thermal button processor ac fuse aufs nls_iso8859_1 nls_cp437 usbhid usb_storage squashfs ssb uhci_hcd ehci_hcd usbcore
Pid: 17328, comm: modem-stats Tainted: P (2.6.30.5 #1) HP 550
EIP: 0060:[<f8789d53>] EFLAGS: 00010296 CPU: 0
EIP is at LXSoftModemStart+0x23/0x230 [agrmodem]
EAX: 00000008 EBX: f6ad2df8 ECX: fffb6000 EDX: f88053c0
ESI: 00000000 EDI: f6ad2e08 EBP: f66f3de4 ESP: f66f3d5c
DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
Process modem-stats (pid: 17328, ti=f66f2000 task=f70f54e0 task.ti=f66f2000)
Stack:
c16cdb00 00000008 f87c482b c01653c5 00000001 00000044 00000246 f66d8000
00000000 c05a7380 c053cf80 00000001 00000000 00000000 000280d0 c053da6c
00000246 00000000 00000000 00000001 00000000 c053cf80 c053cf80 f6ad2df8
Call Trace:
[<c01653c5>] ? get_page_from_freelist+0x2e5/0x470
[<f8785326>] ? linux_modem_open+0x26/0x110 [agrmodem]
[<c011ea8e>] ? __wake_up+0x3e/0x60
[<f86df3a5>] ? modemPortOpen+0x5/0x10 [agrmodem]
[<f8803ae5>] ? serial8250_startup+0x195/0x270 [agrserial]
[<c0300a7c>] ? uart_startup+0x4c/0x150
[<c0302259>] ? uart_open+0x109/0x360
[<c02e9394>] ? check_tty_count+0x14/0xb0
[<c02eb61c>] ? tty_init_dev+0x8c/0x160
[<c02999cf>] ? kobject_get+0xf/0x20
[<c02eb8b9>] ? tty_open+0x1c9/0x430
[<c0189795>] ? chrdev_open+0x95/0x150
[<c0189700>] ? chrdev_open+0x0/0x150
[<c0184c1e>] ? __dentry_open+0xbe/0x240
[<c0185d53>] ? nameidata_to_filp+0x53/0x70
[<c0191272>] ? do_filp_open+0x1e2/0x7a0
[<c01722e9>] ? __do_fault+0x2c9/0x3f0
[<c01849fa>] ? do_sys_open+0x5a/0x100
[<c0184b1c>] ? sys_open+0x2c/0x40
[<c0102e05>] ? syscall_call+0x7/0xb
Code: 00 89 d8 eb a7 8d 76 00 55 b8 2b 48 7c f8 89 e5 57 56 53 83 ec 7c 8b 75 08 89 44 24 08 c7 45 e4 78 56 34 12 8d 46 08 89 44 24 04 <8b> 46 04 89 04 24 e8 e2 13 00 00 85 c0 89 c3 0f 88 68 01 00 00
EIP: [<f8789d53>] LXSoftModemStart+0x23/0x230 [agrmodem] SS:ESP 0068:f66f3d5c
CR2: 0000000000000004
---[ end trace e8eaa8a297c5c21d ]---
with aim of trying to get the modem
- Agere Systems HDA modem with manufacturer:model id = 11c1:1040
to work
I've forced loading of agrserial and agrmodem at bootup
Bootup screen shows that the version is 2.1.60.0.Linspire (2005-11-16)
dmesg after bootup reports:
agrmodem: module license 'Proprietary' taints kernel.
Disabling lock debugging due to kernel taint
agrsm: created 0 infos
Loading module Agere Modem Controller driver version 2.1.60.0.Linspire (2005-11-16)
ttyAGS3 at I/O 0x400 (irq = 3) is a AgereModem
agrserial: Loading module Agere Modem Interface driver version 2.1.60.0.Linspire (2005-11-16)
after command modem-stats -c "ATI3" /dev/ttyAGS3 is issued - returns Killed - dmesg reports:
BUG: unable to handle kernel NULL pointer dereference at 00000004
IP: [<f8789d53>] LXSoftModemStart+0x23/0x230 [agrmodem]
*pde = 00000000
Oops: 0000 [#1] SMP
last sysfs file: /sys/devices/pci0000:00/0000:00:1c.1/0000:10:00.0/ssb0:0/net/wlan0/statistics/tx_bytes
Modules linked in: snd_pcm_oss snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_mixer_oss i915 drm i2c_algo_bit i2c_core rfkill_input agrserial agrmodem(P) arc4 ecb b43 mac80211 input_polldev led_class rfkill cfg80211 ohci_hcd snd_hda_codec_analog snd_hda_intel snd_hda_codec snd_pcm snd_page_alloc snd_timer snd_hwdep snd soundcore serio_raw pcspkr shpchp pci_hotplug e1000e intel_agp agpgart video output wmi fan battery container evdev thermal button processor ac fuse aufs nls_iso8859_1 nls_cp437 usbhid usb_storage squashfs ssb uhci_hcd ehci_hcd usbcore
Pid: 17328, comm: modem-stats Tainted: P (2.6.30.5 #1) HP 550
EIP: 0060:[<f8789d53>] EFLAGS: 00010296 CPU: 0
EIP is at LXSoftModemStart+0x23/0x230 [agrmodem]
EAX: 00000008 EBX: f6ad2df8 ECX: fffb6000 EDX: f88053c0
ESI: 00000000 EDI: f6ad2e08 EBP: f66f3de4 ESP: f66f3d5c
DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
Process modem-stats (pid: 17328, ti=f66f2000 task=f70f54e0 task.ti=f66f2000)
Stack:
c16cdb00 00000008 f87c482b c01653c5 00000001 00000044 00000246 f66d8000
00000000 c05a7380 c053cf80 00000001 00000000 00000000 000280d0 c053da6c
00000246 00000000 00000000 00000001 00000000 c053cf80 c053cf80 f6ad2df8
Call Trace:
[<c01653c5>] ? get_page_from_freelist+0x2e5/0x470
[<f8785326>] ? linux_modem_open+0x26/0x110 [agrmodem]
[<c011ea8e>] ? __wake_up+0x3e/0x60
[<f86df3a5>] ? modemPortOpen+0x5/0x10 [agrmodem]
[<f8803ae5>] ? serial8250_startup+0x195/0x270 [agrserial]
[<c0300a7c>] ? uart_startup+0x4c/0x150
[<c0302259>] ? uart_open+0x109/0x360
[<c02e9394>] ? check_tty_count+0x14/0xb0
[<c02eb61c>] ? tty_init_dev+0x8c/0x160
[<c02999cf>] ? kobject_get+0xf/0x20
[<c02eb8b9>] ? tty_open+0x1c9/0x430
[<c0189795>] ? chrdev_open+0x95/0x150
[<c0189700>] ? chrdev_open+0x0/0x150
[<c0184c1e>] ? __dentry_open+0xbe/0x240
[<c0185d53>] ? nameidata_to_filp+0x53/0x70
[<c0191272>] ? do_filp_open+0x1e2/0x7a0
[<c01722e9>] ? __do_fault+0x2c9/0x3f0
[<c01849fa>] ? do_sys_open+0x5a/0x100
[<c0184b1c>] ? sys_open+0x2c/0x40
[<c0102e05>] ? syscall_call+0x7/0xb
Code: 00 89 d8 eb a7 8d 76 00 55 b8 2b 48 7c f8 89 e5 57 56 53 83 ec 7c 8b 75 08 89 44 24 08 c7 45 e4 78 56 34 12 8d 46 08 89 44 24 04 <8b> 46 04 89 04 24 e8 e2 13 00 00 85 c0 89 c3 0f 88 68 01 00 00
EIP: [<f8789d53>] LXSoftModemStart+0x23/0x230 [agrmodem] SS:ESP 0068:f66f3d5c
CR2: 0000000000000004
---[ end trace e8eaa8a297c5c21d ]---
rcrsn51 wrote:
freememapplet_tray and network_tray work at startup, but traytemp returns a segmentation fault as you reported. I made a copy of the shell script under another name, made it executable and put it in Startup. It did not startup at boot time.In general, startup routines DO work. For some reason, your problem is specific to your setup. Are none of the startup apps initializing for you?
I installed the Ghostscript 8.15.2 pet (confirmed the version in the console), but it did not resolve the problem.OK. I can confirm the issue. Puppy 4.3.1 has Ghostscript 8.15.2 while Quirky has Ghostscript 8.15.4. Maybe there was some change that affects Postscript files.
-
- Posts: 3
- Joined: Mon 31 May 2010, 14:01
- Location: Bario Faro, Guayanilla, Puerto Rico A tin roof shack on the beach.
Quirky 1.2 feedback
1. Dell SX260 256 RAM P4 2654 MHz Sagem Dongle to belkin router
2. Qrky 1.2 CD installed readily on partition 15 DOS Grub worked fine.
3. 3 hours later, no amount of tinkering gave internet connection.
4. Could not locate an .inf file in neighboring 98 SE, 2k Pro or XP Pro partitions. Suspect windows driver is a .sys.
5. Formatted 15 and installed Qret 1.2 from CD. No boot from same grub.
6. In menu.lst substituted qret-120.sfs. No go.
7. 15 did not have initrd.gz or vmlinuz. Copied them manually from CD.
8. Bingo! Instant gratification. Connect to internet? Bingo! Instant gratification.
Thanks to all for genius group work. Still cannot understand why last CD install did not put those 2 files into 15 / as Qrky 1.2 did.
Frog (DOB 1930)
2. Qrky 1.2 CD installed readily on partition 15 DOS Grub worked fine.
3. 3 hours later, no amount of tinkering gave internet connection.
4. Could not locate an .inf file in neighboring 98 SE, 2k Pro or XP Pro partitions. Suspect windows driver is a .sys.
5. Formatted 15 and installed Qret 1.2 from CD. No boot from same grub.
6. In menu.lst substituted qret-120.sfs. No go.
7. 15 did not have initrd.gz or vmlinuz. Copied them manually from CD.
8. Bingo! Instant gratification. Connect to internet? Bingo! Instant gratification.
Thanks to all for genius group work. Still cannot understand why last CD install did not put those 2 files into 15 / as Qrky 1.2 did.
Frog (DOB 1930)
BarryK:
I'm curious what's in nvidia-195.36.15-k2.6.33.2-1-q1.pet that makes flash work. I can delete all it's files, run xorgwizard, and flash still works even after a reboot. If I uninstall nvidia and run xorgwizard however, the jerky flash problem reappears. The nvidia-195.36.15-k2.6.33.2 -q1.pet version doesn't have whatever is needed.
I'm curious what's in nvidia-195.36.15-k2.6.33.2-1-q1.pet that makes flash work. I can delete all it's files, run xorgwizard, and flash still works even after a reboot. If I uninstall nvidia and run xorgwizard however, the jerky flash problem reappears. The nvidia-195.36.15-k2.6.33.2 -q1.pet version doesn't have whatever is needed.
pNethood
Unfortunately pNethood is still broken in my tests with my Samba LANDisk.
I reported on Barry's blog the same problem with Q112.
The main problem for me is after it finds shares and mounts them, Rox Filer is does not show the files (just a mounted unnamed folder). If I navigate to the mount point and open a terminal, "ls" shows the correct files and sub-folders.
Another problem is that the "Refresh" and "Re-Scan Network" butttons appear to no longer work. So I have to quit and launch the app to do a re-scan.
Needless to say it worked perfectly on 431 (and 412) and is the main reason I use Puppy. If there is anything I can do to track down the problem please let me know.
(nb lameSMBExplorer is too unreliable in my tests in other Puppiy's)
Rgds Mike
I reported on Barry's blog the same problem with Q112.
The main problem for me is after it finds shares and mounts them, Rox Filer is does not show the files (just a mounted unnamed folder). If I navigate to the mount point and open a terminal, "ls" shows the correct files and sub-folders.
Another problem is that the "Refresh" and "Re-Scan Network" butttons appear to no longer work. So I have to quit and launch the app to do a re-scan.
Needless to say it worked perfectly on 431 (and 412) and is the main reason I use Puppy. If there is anything I can do to track down the problem please let me know.
(nb lameSMBExplorer is too unreliable in my tests in other Puppiy's)
Rgds Mike
Re: pNethood
Does clicking the ROX Rescan button have any effect?mawebb88 wrote:The main problem for me is after it finds shares and mounts them, Rox Filer is does not show the files (just a mounted unnamed folder). If I navigate to the mount point and open a terminal, "ls" shows the correct files and sub-folders.
Re: pNethood
@rcrsn51rcrsn51 wrote:Does clicking the ROX Rescan button have any effect?mawebb88 wrote:The main problem for me is after it finds shares and mounts them, Rox Filer is does not show the files (just a mounted unnamed folder). If I navigate to the mount point and open a terminal, "ls" shows the correct files and sub-folders.
Yes it does! It show the files/sub-folders. If I un-mount and re-mount (uing the PNethhod buttons) the files are mostly instantly there. But it seems somewhat random because if I click on a folder (within the mounted folder) it sometimes show a mounted (unnamed) folder icon which on Rox refresh show the files. So is there a clue as to how to fix it?
(Nb there is still the other problem of the 2 Pnethood buttons being inoperative)
Rgds Mike