Page 3 of 22
Posted: Fri 13 May 2011, 14:47
by rjbrewer
Full install on Inspiron 700m.
I use i810 graphics.
All usb problems with any version since 098 have now disappeared.
No cursor freeze with usb mouse.
No extended modules loading time.
Very nice so far.
application_x-bittorrent NOT set to Transmission
Posted: Fri 13 May 2011, 19:12
by broomdodger
Wary 5.1.1.53 and 5.1.1.56
application_x-bittorrent NOT set to Transmission
I downloaded the ubuntu torrent link:
ubuntu-11.04-desktop-i386.iso.torrent
When I clicked it, it did not open Transmission.
ok, I said to myself "what is the runtime action?"
This is what I found:
/root/Choices/MIME-types/application_x-bittorrent
That file it is referencing pctorrent:
#!/bin/bash
echo "$1" > $HOME/.pctorrent/torrfile
pctorrent &
1) searched for pctorr:
# find / -iname '*pctorr*'
And found nothing.
2) searched for transmiss:
# find / -iname '*transmiss*'
/usr/share/applications/transmission-gtk.desktop
This is the content of that file:
#! /bin/sh
exec transmission-gtk "$@"
3) changed application_x-bittorrent:
#!/bin/bash
## echo "$1" > $HOME/.pctorrent/torrfile
## pctorrent &
exec transmission-gtk "$@"
4) clicking the .torrent file now works.
Is this the right thing to do?
-Bill
wary 5.1.1.56 rsync missing
Posted: Sat 14 May 2011, 02:40
by broomdodger
wary 5.1.1.56 rsync missing
Thought I would look at Snap2 snapshot backup but the dialog said rsync missing.
Went to console:
which rsync
Not here!
Went back to wary 5.1.1.53 and it is there!
-Bill
Posted: Sat 14 May 2011, 03:31
by James C
Manual frugal install of 5.1.1.56 on my old P3 test box (everything is onboard Intel). Display (1024x768), sound and internet all working on initial boot.
Installed Mesa....working.
Looking good here as well.
Posted: Sat 14 May 2011, 03:44
by James C
PupRadio wouldn't launch......directory /root/.pupradio/ was missing.
Copied missing directory from Spup 120 to solve problem.
rsync is in devx
Posted: Sat 14 May 2011, 07:25
by broomdodger
rsync is in devx
I did not have devx loaded in 5.1.1.56
So... Why does Snap2 snapshot backup depend on it?
-Bill
Posted: Sat 14 May 2011, 08:31
by CHLee
Dear Barry,
1. The chooselocale script:
The locale and $LANG mismatch, If selected UTF-8.
Before Country setup:
Code: Select all
# echo $LANG
en_US
# locale -a
C
en_US
POSIX
After Country setup (with UTF-8 ) :
Code: Select all
# echo $LANG
en_US.UTF-8
# locale -a
C
en_US
en_US.utf8
POSIX
You could see, the $LANG is en_US.UTF-8 but the locale is en_US.utf8. I think the locale should en_US.UTF-8, same as the $LANG.
2. We need /usr/share/i18n/locales/iso14651_t1_pinyin , if missing it, the locale output directory will empty.
Code: Select all
# localedef -c -f UTF-8 -i zh_CN /usr/lib/locale/zh_CN.UTF-8
cannot open locale definition file `iso14651_t1_pinyin': No such file or directory
Please add the /usr/share/i18n/locales/iso14651_t1_pinyin to glibc_locales templates in woof and add this file to glibc_locales-2.10.1-w5.pet.
Thank you very much.
C.H.Lee
Posted: Sat 14 May 2011, 15:39
by rcrsn51
I can confirm that the problem with hard-drive-less machines not booting off USB is now fixed.
Posted: Sat 14 May 2011, 16:23
by rcrsn51
Boot off LIve CD
Select Xorg video
Wait 10 seconds
Get the "Your mouse has not moved" message
Select usb/ps2 and click OK (the mouse is USB)
Screen refreshes
Mouse pointer disappears!
A full reboot is required.
Boot off Live CD
Select Xvesa
Don't get the Welcome popup message
Mouse works correctly
Posted: Sat 14 May 2011, 18:50
by Sage
Thank you, rcrsn51. My reports here aren't always heeded nor believed because I am not one of the inner circle of coders. However, as a dispassionate scientific observer and reporter, I suspect I have as much experience and credibility as any, not least because experience accrues with age! So thanks my friend for confirming my earlier report on this occasion.
Posted: Sat 14 May 2011, 19:14
by rcrsn51
Thanks for the vote of support. But I was not able to duplicate your "blank screen" scenario.
Also, I tried to duplicate MY "no mouse pointer" scenario on a different machine and could not.
Posted: Sat 14 May 2011, 19:30
by Sage
OK, just managed to confirm reported effects on a couple other spare machines running single core AMD, 1/2 - 1Mb mem. and ATI cards. The strange mouse and screen behaviours are always replicated from a live pfix=ram boot but the blank screen detente seems to vary from 10 - 30s between boxes. In this respect, these are entirely new features.
Sound card failure - agrsm firmware not at fault
Posted: Sat 14 May 2011, 20:37
by rerwin
I suspect that Barry's sound card issue (reported in his blog) is only a symptom of a larger problem. The default sound card is expected to be number 0, but the number is assigned by backend_modprobe (or ALSA's autoloader, if used) first-come-first-served. So the choice is affected by the timing of hardware initialization and related event generation. (Without its 2-second delay, the agrsm firmware blacklists 3 built-in modems that could otherwise grab number 0 before the actual sound card gets it.) In wary and woof, it appears also that until the alsa wizard is run, the number gets re-chosen on each bootup, which would account for inconsistent sound behaviour.
Although I have addressed all of this in my "modprobe protect" function, the wary/woof replacement for it does not. I found good information in the alsa-base.conf file in Lucid Puppy, originally from ubuntu and debian. Besides some install statements for built-in modems, it contains a section that prevents non-sound-card drivers from using card number 0 -- ALSA modems , video-capture cards and some USB sound devices.
My guess is that with the ALSA autoloader the ALSA drivers interpret an index value of "-2" to mean to skip number zero during assignment. Although I cannot find a straightforward declaration about that value, all indications from googling are that it means this. Apparently, the drivers obtain their numbers somehow, although Puppy takes over that function, pre-empting the drivers' need to be further assigned. Anyway, I believe that Puppy needs to implement the avoidance of non-sound-card devices from getting number zero when it assigns the numbers. In addition, it should retain the setting for card zero across reboots -- commonly reported as a problem.
Because of the complexity of wary/woof's number assignment technique, I must leave it to Barry to implement these improvements in woof. A start would be to either adopt the debian/ubuntu alsa-base.conf configuration file or include most of its content in alsa.conf, and add backend_modprobe logic to use that information to determine the devices that must not use "0" unless overridden by the alsawizard (to use the USB sound devices).
Here is the alsa-base information I am referring to:
Code: Select all
# autoloader aliases
install sound-slot-0 /sbin/modprobe snd-card-0
install sound-slot-1 /sbin/modprobe snd-card-1
install sound-slot-2 /sbin/modprobe snd-card-2
install sound-slot-3 /sbin/modprobe snd-card-3
install sound-slot-4 /sbin/modprobe snd-card-4
install sound-slot-5 /sbin/modprobe snd-card-5
install sound-slot-6 /sbin/modprobe snd-card-6
install sound-slot-7 /sbin/modprobe snd-card-7
# Cause optional modules to be loaded above generic modules
install snd /sbin/modprobe --ignore-install snd $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-ioctl32 ; /sbin/modprobe --quiet --use-blacklist snd-seq ; }
#
# Workaround at bug #499695 (reverted in Ubuntu see LP #319505)
install snd-pcm /sbin/modprobe --ignore-install snd-pcm $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-pcm-oss ; : ; }
install snd-mixer /sbin/modprobe --ignore-install snd-mixer $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-mixer-oss ; : ; }
install snd-seq /sbin/modprobe --ignore-install snd-seq $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-seq-midi ; /sbin/modprobe --quiet --use-blacklist snd-seq-oss ; : ; }
#
install snd-rawmidi /sbin/modprobe --ignore-install snd-rawmidi $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-seq-midi ; : ; }
# Cause optional modules to be loaded above sound card driver modules
install snd-emu10k1 /sbin/modprobe --ignore-install snd-emu10k1 $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-emu10k1-synth ; }
install snd-via82xx /sbin/modprobe --ignore-install snd-via82xx $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist snd-seq ; }
# Load saa7134-alsa instead of saa7134 (which gets dragged in by it anyway)
install saa7134 /sbin/modprobe --ignore-install saa7134 $CMDLINE_OPTS && { /sbin/modprobe --quiet --use-blacklist saa7134-alsa ; : ; }
# Prevent abnormal drivers from grabbing index 0
options bt87x index=-2
options cx88_alsa index=-2
options saa7134-alsa index=-2
options snd-atiixp-modem index=-2
options snd-intel8x0m index=-2
options snd-via82xx-modem index=-2
options snd-usb-audio index=-2
options snd-usb-us122l index=-2
options snd-usb-usx2y index=-2
options snd-usb-caiaq index=-2
# Ubuntu #62691, enable MPU for snd-cmipci
options snd-cmipci mpu_port=0x330 fm_port=0x388
# Keep snd-pcsp from being loaded as first soundcard
options snd-pcsp index=-2
HTH
Richard
Posted: Sun 15 May 2011, 03:29
by BarryK
rcrsn51 wrote:Thanks for the vote of support. But I was not able to duplicate your "blank screen" scenario.
Also, I tried to duplicate MY "no mouse pointer" scenario on a different machine and could not.
Interesting, if you do not move the mouse within a certain time, and you get that message, my expectation was that you would just click the 'Cancel' button.
Anyway, I will test what you have described.
Posted: Sun 15 May 2011, 03:31
by BarryK
Sage wrote:OK, just managed to confirm reported effects on a couple other spare machines running single core AMD, 1/2 - 1Mb mem. and ATI cards. The strange mouse and screen behaviours are always replicated from a live pfix=ram boot but the blank screen detente seems to vary from 10 - 30s between boxes. In this respect, these are entirely new features.
Sage,
rcrsn51 is not reporting what you are reporting.
Do you only get the blank screen with ATI video cards?
Posted: Sun 15 May 2011, 05:16
by Sage
rcrsn51 is not reporting what you are reporting.
He reported part of what I saw. The mouse prompting only occurs if one is not sitting in anticipation - appears after some several seconds; I am usually doing more than one thing at a time. Cannot see any valid reason for its appearance.
Answer: I was able to release an nV card last night and confirm the screen blanking is not ATI-specific. With the nV card, the prompt screen is briefly flashed during blanking. Effect is present with both Dell (always a weird one) and bog std. AOC monitors. Not able to test with crt at this time. Swap space always available; can't think of any other non-std. HW aspects.
Posted: Sun 15 May 2011, 10:08
by BarryK
Request for sound testing.
I was discussing a problem with sound with rerwin just prior to releasing Wary 5.1.1.56, but deferred it until now. Rerwin has outlined the issue in his above post.
It may be that the solution is extremely simple. Originally, I had code in /sbin/pup_event_backend_modprobe to assign card slot numbers.
However, the existence of /etc/modprobe.d/alsa-base.conf changes the ball game entirely.
I have simply removed my slot assignment code in pup_event_backend_modprobe. It works fine on my laptop.
I would welcome testers.
Step 1
Could you please download 'alsa-base.conf.gz', ungzip it and place at /etc/modprobe.d.
Step 2
In /etc/modprobe.d you will see one or more files named like this:
alsa_card3049.conf
where you will have some number different from '3049'. Delete those files.
Step 3
Download pup_event_backend_modprobe, ungzip it and place at /sbin (replacing previous).
EDIT: right-click script, choose 'Properties', tick 'execute' checkboxes.
Step 4
Oh one other thing, if you have previously run the Alsa Wizard, it will have created entries in /etc/modprobe.d/alsa.conf -- please delete those lines also. You will find two lines like this:
alias snd-card-0 snd-hda-intel
alias sound-slot-0 snd-hda-intel
Get rid of those, so that you are starting from a clean slate. Reboot, if you find that Alsa Wizard is no longer needed then that will be great.
Then reboot, after doing all 3 (or 4) steps above..
Do you still have sound?
Posted: Sun 15 May 2011, 11:57
by Billtoo
BarryK wrote:Request for sound testing.
Do you still have sound?
Did a fresh frugal install:
On first boot hear two barks,wired network is up on eth0.
See image1.
I put alsa-base.conf in /etc/modeprobe.d
There was a file there named alsa_card6511.conf which I removed.
I did step 3.
This is what alsa.conf looks like:
alias char-major-14-* soundcore
alias char-major-116-* snd
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss
options sb io=0x220 irq=7 dma=1 dma16=5 mpu_io=0x330
*******************************************************************************
I rebooted creating a save file:
Back to desktop.
See image2 & image3 & image4
*******************************************************************************
I deleted my save file and rebooted,image5.
Posted: Sun 15 May 2011, 17:14
by JonT
With a frugual install, booted with pfix=ram, followed instructions for sound testing above, including reboot. Much like Billtoo (just above) lost sound, speaker icon in tray, network connection options. "modprobe ath5k" enabled wireless. One little test,
Code: Select all
# retrovol
retrovol: hcontrol.c:570: snd_hctl_load: Assertion `hctl->count == 0' failed.
Aborted
#
Tried rebooting (having a save file) with existing lines in alsa.conf and with them commented out with no difference noted.
Old alsa.conf was same as Billtoo's.
Ran alsawizard (first time EVER used). Without rebooting, got sound back, speaker icon, retrovol command works.
These lines were found added to alsa.conf.
Code: Select all
# --- BEGIN: Generated by ALSACONF, do not edit. ---
# --- ALSACONF version 1.0.21 ---
alias snd-card-0 snd-intel8x0
alias sound-slot-0 snd-intel8x0
# --- END: Generated by ALSACONF, do not edit. ---
Rebooted, had to add wireless module again. Sound okay.
Still have sound.
Posted: Sun 15 May 2011, 17:42
by rodin.s
I still have sound. Soundcard:
Code: Select all
00:1f.5 Multimedia audio controller: Intel Corporation 82801AA AC'97 Audio Controller (rev 02)
Always detected automatically by Puppies.
Another PC has ESS 1868 and I always have to run alsaconf or manually modprobe snd_ess18xx. I'll do the test on that PC later.