Puppy Linux Discussion Forum

[BarryK]

[glenco]

JWM configuation is broke. Can't change wallpaper by clicking JWM configuation > Desktop > Desktop Background icon.
ROX has no right click option of Set As Wallpaper.
Pwallpaper background chooser works but the images must be located in /usr/share/backgrounds only.

[shinobar]

I made a remastered custom CD of Wary-098.
Tested the custom CD of course with pfix=ram.
But it loads the main sfs from HDD original, instead of the CD modified.
PUPSTATE:

[rerwin]

After setting up a test PC for working the woof-woof problem, I did not see the welcome screen on first boot from the remastered (with -5) CD, so lost hope of a quick ALSA fix. I saved to a file (pupsave-test2). The next morning when I rebooted to that pupsave, the Welcome screen appeared and I moused to get the woof-woof. Maybe there is hope.

But then I read the warning message on the welcome screen, which claimed I was very low on RAM. The reality is that the PC has 1GB, but the pupsave has only 32MB total, with about 15MB available. It appears that the available pupsave space is being checked instead of the actual RAM size. My guess is that the assumption is that the welcome only occurs before a pupsave is available. But there it was. Attached is the evidence.
Richard

[Billtoo]

I installed 098 to an 8gb SDHC card formatted to ext4.
I've installed the wary_devx_098.sfs,kernel_src-2.6.31.14-patched.sfs,
and NVIDIA-Linux-x86-260.19.21.run.
I compiled xine-lib-1.1.19.tar.bz2 and added xine-ui-0.99.5-w5 from
the puppy package manager.
The computer is an Acer Revo Nettop.

# report-video
VIDEO REPORT: Wary Puppy, version 098

Chip description:
oem: NVIDIA
product: MCP79 Board - hornet-0 Chip Rev

Driver used by Xorg:
nvidia

Video mode used by Xorg:
Resolution: Depth 24 Depth: "Display"

...the above also recorded in /tmp/report-video
#
Computer
Processor 4x Intel(R) Atom(TM) CPU 330 @ 1.60GHz
Memory 1813MB (829MB used)
Operating System Puppy Linux 0.09
User Name root (root)
Date/Time Sat 20 Nov 2010 09:35:54 PM EST

Display
Resolution 1280x1024 pixels
Vendor The X.Org Foundation
Version 1.3.0

The graphics chip is an Nvidia ION.

The network,and sound were working on first boot although the wireless
wlan0 doesn't even show up the wired network works fine.

The xine DVD player works well with my Sony usb dvd drive, so does Ogle.

Edit: this install was running well (I thought) on the Revo but it
locked up the computer after a few hours and I had to shut it down.
I just pulled the SDHC card out of the Revo and put it in my Gateway
desktop which has ATI HD3200 onboard graphics.

At first bootup it went to the xorgwizard prompt and I chose probe and
it got the resolution correct.The network was up but Retrovol needed
to be re-configured.
I downloaded the ati_fglrx-10.10-k2.6.31.14-w5.pet and installed
it,then rebooted and followed the instructions.
# report-video
VIDEO REPORT: Wary Puppy, version 098

Chip description:
oem: ATI ATOMBIOS
product: RS780 01.00

Driver used by Xorg:
radeon
fglrx

Video mode used by Xorg:
Resolution: Depth 24 Depth: "Display"

...the above also recorded in /tmp/report-video
#
I'll let this run for a few hours and see how it goes, it's working
a-one right now.

Wary 094 ran problem free on the Revo running with a flash drive
install so I think the SDHC card was the problem.

[zekebaby]

[shinobar]

My eth0 automatically connect at the first boot.
But i dare to test the SNS.
The SNS found eth0 and easily connected.
Set the SNS as the default connecting tool.

Reboot. The connection lost
Right clicked the 'connect' icon on the desktop, got no response.
Setup again with SNS, successfully connect.
But loose the connection after reboot.

Setup again and switched to Dugal's, successfully connect.
Set Dugal's as the default connecting tool.
Reboot. The connection OK.

Does it occur only with my PC?
The ethernet controller is Atheros AR81xx PCI-E and the driver is atl1e.

[Sage]

[01micko]

[Billtoo]

[BarryK]

[BarryK]

[Sage]

[rerwin]

To try to reconcile Barry's complaint about wary 098's failure to bark as expected, I set up a test PC and tried to recreate his situation. In the process, I created versions of the involved scripts that log trace information to show the order that events occur. My test specifically simulates the effect of the Agere and Intel537 driver variant switching. I ran with 098 plus the update-5 package, then added the "wired" versions of the "-5" scripts.

I attach a dotpet containing those wired scripts and an installation script that resets the variants so they are forced to switch on first use. The dotpet can be installed repeatedly, to reset those cases as needed.

My test results show that I cannot recreate any situation that disrupts the welcome barks! I encourage anyone, particularly Barry, who feels that the barks don't work when the Agere modem is installed, to try this package on top of the "-5" package.

For useful results, be sure to have pupdial CHOOSE > ERASE the modem selection, even if none is shown. This forces the full driver initialization process to occur at the next bootup, which is where the problem apparently exists. On subsequent tests, do both the CHOOSE-ERASE and reinstall the debug package, to reset the variant configuration. Please post or PM a pmodemdiag file if you find sound initialization not right.

Now, to try it on an old dual-CPU PC, to see how it keeps the two from stepping on each other.
Richard

[shinobar]