Puppy 4.3.1 -- bug reports and suggestions

[rjbrewer]

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.

Wrong conclusion;

I play many types of files with gxine, vlc, realplayer, or mplayer on
any puppy version since 4.0.

You may have a hardware problem of some kind?
The post you made in "how to" shows an elaborate and unneccesary
method of playing files.

I just drag the files from rox or my storage usb and drop them on the
gxine or vlc icon and they play fine.

[nubc]

Your characterization of the procedure as elaborate may be accurate, but to call it unnecessary is an opinion, that I don't share. Why should I drag stuff around on the desktop when I can single click it where it lies? I am working with the interface, and that's how to set VLC for FLV playback. You make a general claim that gxine plays it all on various Puppy 4.x versions, but you dont say specifically 4.3.1. I'm just reporting a bug, not looking for a debate.

[rjbrewer]

I have 4 different versions of 4.3.1 installed. No problems with any
as far as playing video files goes.

Just clicking on a flv, mp4, or wmv file opens the default player
and starts playing it.

Asf or asx files I drag to icon.

[Pizzasgood]

I just tested it with Qemu. Yeah, it plays fine. However, the file I tested didn't run when I clicked it. It didn't have a .flv extension (no extension at all). Perhaps that's the problem. (I tried playing it directly out of /tmp while Seamonkey was on the page it came from, which I assume is what nubc was trying to do.)

I didn't look into it beyond that. Got stuff that needs doing tonight. Sorry.

[technosaurus]

to avoid dragging you can:
right click on it
set run action
defaultmediaplayer "$1"

(this goes similar for all filetypes that are missing mime-types that puppy can handle)

there will be a file in:
/root/.config/rox.sourceforge.net/MIME-types/

Please gzip and share it here if it works

[Jana]

Hello and sorry, if someone asked this before (didn't find the answer).

I'm running Puppy 4.3 on old Compaq Armada E500 and thanks to this forum I got mostly everything working. I don't know if this is a bug, but every time I start computer, sound is muted and I have to adjust the volume manually. Is there a cure for that?

Besides that, there is no volume icon, only an empty space on the tray (the button utself works though).

Any ideas?


Update: tried doing
# alsamixer
and
# alsactl store

but didn't help

[Jana]

Ok, figured out myself

http://www.murga-linux.com/puppy/viewto ... 113#330113

This pet solves those problems

[JustGreg]

I have a strange one. I have a used Acer Aspire One (Model ZG5 on case, Bios has AOA150). If I boot Puppy 4.3.1 from a USB CDROM on the Aspire, then every thing works fine. Puppy detects all the devices, display, sound, wifi, ethernet and web camera. The devices all work except for the Web Camera. I have not tested the web camera with the CDROM system.

If I do a frugal instal to a USB Flash drive and boot using the USBBootFlash tool. I get a notice during the modules loading stage of disabling IRQ #11. I get three to four of these messages during modules loading period. Puppy starts up. The display and wifi are fine. However, the sound and web camera do not work right. The sound has the problem that has been reported before. When a sound file is play, the sounds (beginning) keep repeating and never stops. I have tested 2barks (both wav and au) and Ivy.mpg. Both have the problem.

I first thought I had a corrupted file on the USB Flash drive. I did a md5sum check on vmlinuz, initrd.gz and pup-431.sfs files. They matched the md5sum for the same files on the CDROM.

The particular USBFlash drive (256 megabye)has been around since the ninities and been used for many Puppy experiments. I thought that it may have the "too many read/write" problem. I have some 1 Gigabyte micro USB hard drives. I did a frugal install to ione. I found the same problem! IRQ #11being disabled. This drive also has the Grub4Dos boot loader on its VFAT partition. It works well. So it is not the USB drives.

Any thoughts on this one.

I do have a second 1 Gigabyte USB micro Hard Drive that has EXT2 File system. I installed Grub4 Dos boot loader using Quirky. Shinobar, the install program works fine.
What I would like to do is full EXT2 Puppy install to it. I would be doing a manual full install to the USB drive. I know how to expand pup431.sfs and install directories and files. I do not know how to handled the files in initrd.gz. Do I just expand it and install or is there something that needs to be done?

Thanks in advance for any help on this one.

[JustGreg]

I found that Windows XP lists IRQ #11 as for
Intel 82801G (ICH7 Family) SMBUS Control

Time to use Google to see what SMBUS Control does.

I did a frugal install to the Hard Drive. I used to Windows Boot Manager and Grub4Dos per the Grub4Dos tutorial. It worked well and did not modify the MBR. The install and configuration of Grub4Dos was manual experiment. However, the IRQ#11 problem was still there. I even tried booting from the CDROM and creating the pupsave file from that configuration. It did not help. The problem occurs with all frugal installation expect for the CDROM media.

Thanks in advance for any help on this one.

I have check my notes on the full EXT2 install to USB hard disk. I do not think it can be done. I was beating that drum about two years ago. No Luck then.

[JustGreg]

I did a bunch of reading. SMBus is the System Management Bus device. It is a PCI device. From various bug posts, it controls temperature sensor, fan, audio, web camera and the multi-media reader.

I did find other linux distributions that resolve the audio problem by adding to modprobe.conf this:
options snd-hda-intel model=
which choices of model being equal to acer, aspire-one or 3-stacks. With Puppy 4.3.1, the result was the IRQ #11 was not disabled, but, one did not have a sound card. I used aplay -l to show whether or not a sound card was available.

I have also noticed the fan runs continuously.

Mint Linux bug posting had kernel 2.6.27rc2 fixing the problem.

[ecomoney]

Today I installed puppy 4.3.1 on a computer as a second boot option with a hard disk formatted to ext 3 (it already had 2.15ce based ecopup on it). I booted it from the hard disk and then installed firefox from here, and went to shutdown and save the session. I was greeted with a black screen saying "session not saved"! Why when I "livebooted" (aleibeit from a hard disk) did it not offer to save my (limited) setup in a pup_save.2fs file?

[mikeb]

Today I installed puppy 4.3.1 on a computer as a second boot option with a hard disk formatted to ext 3 (it already had 2.15ce based ecopup on it). I booted it from the hard disk and then installed firefox from here, and went to shutdown and save the session. I was greeted with a black screen saying "session not saved"! Why when I "livebooted" (aleibeit from a hard disk) did it not offer to save my (limited) setup in a pup_save.2fs file?

my guess is you have initrd.gz on more than one partition or no file named initrd.gz....a feature apparently.

mike

[technosaurus]

or perhaps you somehow ended up using your old pupsave and now it has firefox on it... When you boot back into 2.15 take a look - that should help narrow it down some.

[OverDrive]

Hi, I encountered a problem with using the ath5k module in 4.31. This is on a 3 year old Toshiba laptop with a Celeron M380 CPU (1.6 GHz, 1 MB L2 cache, 400 MHz FSB 768 MB Ram and Atheros AR5005G 54g wifi. The wifi hardware works fine in Windoze XP and Puppy 4.31 Retro using the ath_pci module, Though I really don't consider this hardware retro.

ath5k detects, tests and loads fine using 4.31 standard with the network wizard. But the ath5k module in 4.31 retro wouldn't even find a wifi network. What happens in 4.31 standard is when you are browsing on the web to some pretty graphics/script heavy pages, such as:

http://sports.yahoo.com/nfl or http://news.yahoo.com/

The progress bar zooms over to about 50%, backs up a wee bit and then just stays there for several minutes before occasionally finally finishes and letting you in. It also does it with a pfix=ram session. It's seems almost like it chokes on it. With ath_pci, no problems encountered. I'm thinking, if possible, we should include ath_pci in future regular versions until this module gets beyond the "experimental" state...

Or is this just me....

OverDrive

[JustGreg]

Here is the information from the system messages log on the IRQ #11 problem:

Jan 30 05:16:33 (none) user.info kernel: uhci_hcd 0000:00:1d.0: irq 11, io base 0x00006080
Jan 30 05:16:33 (none) user.info kernel: HDA Intel 0000:00:1b.0: PCI INT A -> Link[LNKG] -> GSI 10 (level, low) -> IRQ 10
Jan 30 05:16:33 (none) user.debug kernel: HDA Intel 0000:00:1b.0: setting latency timer to 64
Jan 30 05:16:33 (none) user.err kernel: irq 11: nobody cared (try booting with the "irqpoll" option)
Jan 30 05:16:33 (none) user.warn kernel: Pid: 2895, comm: modprobe Not tainted 2.6.30.5 #1
Jan 30 05:16:33 (none) user.warn kernel: Call Trace:
Jan 30 05:16:33 (none) user.warn kernel: [<c0151784>] ? __report_bad_irq+0x24/0x80
Jan 30 05:16:33 (none) user.warn kernel: [<c0151930>] ? note_interrupt+0x150/0x190
Jan 30 05:16:33 (none) user.warn kernel: [<c0152434>] ? handle_level_irq+0x74/0xc0
Jan 30 05:16:33 (none) user.warn kernel: [<c0105317>] ? handle_irq+0x17/0x20
Jan 30 05:16:33 (none) user.warn kernel: [<c0104b57>] ? do_IRQ+0x47/0xb0
Jan 30 05:16:33 (none) user.warn kernel: [<c0103409>] ? common_interrupt+0x29/0x30
Jan 30 05:16:33 (none) user.warn kernel: [<c012c15e>] ? __do_softirq+0x4e/0x170
Jan 30 05:16:33 (none) user.warn kernel: [<c0150569>] ? handle_IRQ_event+0x49/0x130
Jan 30 05:16:33 (none) user.warn kernel: [<c01068ed>] ? enable_8259A_irq+0xd/0x50
Jan 30 05:16:33 (none) user.warn kernel: [<c012c2a7>] ? do_softirq+0x27/0x30
Jan 30 05:16:33 (none) user.warn kernel: [<c012c565>] ? irq_exit+0x55/0x60
Jan 30 05:16:33 (none) user.warn kernel: [<c0104b60>] ? do_IRQ+0x50/0xb0
Jan 30 05:16:33 (none) user.warn kernel: [<c04184ae>] ? schedule+0xe/0x20
Jan 30 05:16:33 (none) user.warn kernel: [<c0123605>] ? __cond_resched+0x15/0x30
Jan 30 05:16:33 (none) user.warn kernel: [<c0103409>] ? common_interrupt+0x29/0x30
Jan 30 05:16:33 (none) user.warn kernel: [<c029f9fd>] ? delay_tsc+0x1d/0x40
Jan 30 05:16:33 (none) user.warn kernel: [<c029f9a6>] ? __delay+0x6/0x10
Jan 30 05:16:33 (none) user.warn kernel: [<f81d62f2>] ? azx_get_response+0x102/0x1c0 [snd_hda_intel]
Jan 30 05:16:33 (none) user.warn kernel: [<f81d76a9>] ? azx_probe+0x7f9/0x9e3 [snd_hda_intel]
Jan 30 05:16:33 (none) user.warn kernel: [<f81d6130>] ? azx_send_cmd+0x0/0xc0 [snd_hda_intel]
Jan 30 05:16:33 (none) user.warn kernel: [<f81d61f0>] ? azx_get_response+0x0/0x1c0 [snd_hda_intel]
Jan 30 05:16:33 (none) user.warn kernel: [<f81d63b0>] ? azx_get_wallclock+0x0/0x10 [snd_hda_intel]
Jan 30 05:16:33 (none) user.warn kernel: [<f81d63c0>] ? azx_get_linkpos+0x0/0x10 [snd_hda_intel]
Jan 30 05:16:33 (none) user.warn kernel: [<f81d59c0>] ? azx_attach_pcm_stream+0x0/0x1e0 [snd_hda_intel]
Jan 30 05:16:33 (none) user.warn kernel: [<c0309820>] ? __driver_attach+0x0/0x80
Jan 30 05:16:33 (none) user.warn kernel: [<c02add1b>] ? local_pci_probe+0xb/0x10
Jan 30 05:16:33 (none) user.warn kernel: [<c02ae4e0>] ? pci_device_probe+0x60/0x80
Jan 30 05:16:33 (none) user.warn kernel: [<c0309749>] ? driver_probe_device+0x69/0x140
Jan 30 05:16:33 (none) user.warn kernel: [<c02adde0>] ? pci_match_device+0x10/0xa0
Jan 30 05:16:33 (none) user.warn kernel: [<c0309892>] ? __driver_attach+0x72/0x80
Jan 30 05:16:33 (none) user.warn kernel: [<c0308d92>] ? bus_for_each_dev+0x42/0x60
Jan 30 05:16:33 (none) user.warn kernel: [<c02adda0>] ? pci_device_shutdown+0x0/0x30
Jan 30 05:16:33 (none) user.warn kernel: [<c02ae420>] ? pci_device_remove+0x0/0x40
Jan 30 05:16:33 (none) user.warn kernel: [<c03095f6>] ? driver_attach+0x16/0x20
Jan 30 05:16:33 (none) user.warn kernel: [<c0309820>] ? __driver_attach+0x0/0x80
Jan 30 05:16:33 (none) user.warn kernel: [<c0309349>] ? bus_add_driver+0xc9/0x280
Jan 30 05:16:33 (none) user.warn kernel: [<c02adda0>] ? pci_device_shutdown+0x0/0x30
Jan 30 05:16:33 (none) user.warn kernel: [<c02ae420>] ? pci_device_remove+0x0/0x40
Jan 30 05:16:33 (none) user.warn kernel: [<c0309b78>] ? driver_register+0x58/0x120
Jan 30 05:16:33 (none) user.warn kernel: [<f819a000>] ? alsa_card_azx_init+0x0/0x14 [snd_hda_intel]
Jan 30 05:16:33 (none) user.warn kernel: [<c02ae72d>] ? __pci_register_driver+0x3d/0xa0
Jan 30 05:16:33 (none) user.warn kernel: [<f819a000>] ? alsa_card_azx_init+0x0/0x14 [snd_hda_intel]
Jan 30 05:16:33 (none) user.warn kernel: [<c0101133>] ? do_one_initcall+0x33/0x170
Jan 30 05:16:33 (none) user.warn kernel: [<c0155547>] ? tracepoint_module_notify+0x27/0x30
Jan 30 05:16:33 (none) user.warn kernel: [<c013eb20>] ? notifier_call_chain+0x30/0x60
Jan 30 05:16:33 (none) user.warn kernel: [<c013edd3>] ? __blocking_notifier_call_chain+0x53/0x70
Jan 30 05:16:33 (none) user.warn kernel: [<c014dd27>] ? sys_init_module+0x87/0x1c0
Jan 30 05:16:33 (none) user.warn kernel: [<c0187251>] ? sys_read+0x41/0x70
Jan 30 05:16:33 (none) user.warn kernel: [<c0102e05>] ? syscall_call+0x7/0xb
Jan 30 05:16:33 (none) user.err kernel: handlers:
Jan 30 05:16:33 (none) user.err kernel: [<f80835f0>] (usb_hcd_irq+0x0/0x70 [usbcore])
Jan 30 05:16:33 (none) user.err kernel: [<f80835f0>] (usb_hcd_irq+0x0/0x70 [usbcore])
Jan 30 05:16:33 (none) user.err kernel: [<f80835f0>] (usb_hcd_irq+0x0/0x70 [usbcore])
Jan 30 05:16:33 (none) user.err kernel: [<f80835f0>] (usb_hcd_irq+0x0/0x70 [usbcore])
Jan 30 05:16:33 (none) user.err kernel: [<f80835f0>] (usb_hcd_irq+0x0/0x70 [usbcore])
Jan 30 05:16:33 (none) user.emerg kernel: Disabling IRQ #11

I have similar messages for device ath5k 0000:03:00.0, jmb38x_ms 0000:04:00.3,
and sdhci-pci 0000:04:00.0. Does anyone know what the above means, have an
idea for me to check or work on next? Thanks in advance for any help.

[rjbrewer]

About ath5k:

http://murga-linux.com/puppy/viewtopic. ... 31&t=47267

[JustGreg]

Thank you jjbrewer for point to the post by tempestuous. I had found it before.

But, I did find a solution! I added the kernel boot parameter, irqpoll to the kernel line. This eliminates the IRQ #11 disabled messages and the sound works normally. An alternate solution is to use acpi=off, but, this causes an incomplete power shutdown. The system only halts and one has to press the power button to completely turn off the system.

I found the information on irqpoll in Ubuntu post on the same problem. There are kernel boot parameters that do many things. The only way to find out about them is to read the kernel documentation.

For Puppy 4.3.1, my suggestion is the message from initrd.gz be change from "IRQ #11 disabled" to "IRQ #11 disabled try acpi=off kernel boot parameter". The "acpi=off" kernel boot parameter is documented on Puppy Linux wiki and other sources. The irqpoll parameter is not documented. This would help people when they encountered the problem. Pressing the power button to turn off the system at shutdown is a reasonable work around.

This whole problem is the result of Windows 2000 plug and pray, opps, I mean plug and play scheme. It uses irq 11 as general interrupt for a host of devices. I hope this helps.

31 January. I did some more research into kernel parameters. I found and tested acpi=noirq. This appears to be a better way to solve this rather than irqpoll.

[rjbrewer]

JustGreg:

To have it poweroff cleanly; add acpi=force, to the end of the
kernel line in /boot/grub/menu.lst.

[ecomoney]

Thanks technosaurus, but ecopup has been modified to use a "eco_save.2fs", so this cant be the reason. There was no pup_save.2fs on the hard disk at all when I booted it.

[JustGreg]

Thanks again, for the advice and help, jdbrewer. I tried the boot parameter acpi=force and it did not work. I got the same with IRQ #11 being disabled. Only boot parameters acpi=off and irqpoll seem to work. But, I do thank you for help.

It seems the best approach is acpi=noirq