4.1 Alpha 4

[Flapdoodle]

I have tried with and without layerfs=aufs and saw no difference. Everythings seems to be working and the drive icons stay (so far) where I place them.

Sound
linksys wireless G USB
floppy
2 USB flashdrives (one is swap)

404 boots from Toshiba CD, but not HP R/W CD ROM drive, however, it does find it on the desktop

My problem with Puppy versions has been the time it takes for "searching drives for Puppy files" while booting

3.01 8 minutes and 5 seconds!
4.0 About the same
4.03 2-4 seconds, both from CD and installed
4.04 8 seconds, but installed 55 seconds

From watching the drive lights it seems Puppy is searching the same drives over again.

AM608BX K7 MB, 256 ram, 800Mhz

[linuxcbon]

Why when I install progs (abiword, pidgin) from source, they go to /usr/local/bin ? And puppy has them in /usr/bin by default

[paulh177]

This is a Lin'n'Win "frugal" install on a Windows XP FAT partition.

Any "find" command always throws the final two errors shown in e.g:

Code: Select all

# find / -name dummy 
/sys/bus/i2c/drivers/dummy
find: /proc/4687/net: Invalid argument
find: /sbin: Invalid argument

[ricstef]

tempestuous wrote

Those are non-standard drivers that I compiled specially for the Eee.
Wait for the final release of 4.1 and I will compile them again.

And I don't think Barry usually includes third-party modules in alpha releases, anyway. Alpha testers should not be attempting to use such drivers.

@tempestuous

Thanks for your reply, I didn't realize that these are 3rd party drivers. And thank you for taking the trouble to compile them for us Eee lovers.
I thought they were stock drivers. So checked the earlier puppies again, turns out I was wrong. I was so impressed with Pupeee-301 for working out of the box that I forgot it was especially set up for the Eee.
Thanks again,
Richard.

[rerwin]

On the first use of PupDial in a fresh (pfix=ram) bootup, PupDial crashes. Running from the command line yields:

** ERROR **: gtkdialog: Error in line 43, near token '</default>': syntax error
aborting...

This appears to be caused by gtkdialog encountering the invalid sequence:

Code: Select all

<default></default>

resulting from null values for four binary (yes/no) variables. This happens when there is no /etc/wvdial.conf file present -- the initial state of things.

The fix is to move four commands in /usr/sbin/pupdial from the logic for the file being in existence, to immediately before the test for that file. Insert the following after line 33:

Code: Select all

ynSTUPID_MODE1=no
ynSTUPID_MODE2=no
ynAUTO_RECONNECT1=yes #default is on.
ynAUTO_RECONNECT2=yes #default is on.

and delete them from their positions later in the code.

With that fix, I can probe and connect with my PCI hardware modem on ttyS2.
Running 4.04 frugal with aufs (but had same problem under unionfs).
Richard

[dogone]

Booting alpha 4 from CD with Aufs and a pup_save on flash...

Puppy Event Manager's control of the floppy icon appears broken. According to the right-most tab ("Unnamed"), the floppy icon defaults to not displayed. Despite, the floppy icon appears on my desktop. Toggling this check box has no effect, even after JWM/X restart..

[dogone]

Booting alpha 4 from CD with pup_save on flash...

Configuring Puppy for Aufs resolved major Seamonkey instabilities. One remaining instability discovered.

On two occasions, pressing the "delete" (I think) key while composing an email caused all SM windows to close... Bang! X restart required to recover. SM mail client defaults to periodic saves to "Drafts" folder, so little was lost. This may not be a Puppy problem but should be tested by all.

[Lobster]

I got Alpha 4 runing from CD on a laptop without HD
(I downloaded and used the 'standard' version to ensure
the touchpad would work - which undev may be required for . . .)
From this used the Universal Install for USB on the Eeepc

Booted, however no wifi driver for the Eeepc included
and unable to connect with Wifi on both machines

I hope Dougals new wizard for wifi will simplify things . . .
http://www.murga-linux.com/puppy/viewto ... 132#216132

[capoverde]

Booted Puppy 4.1 Alpha4 from CD (MD5 checked OK) with pfix=ram, tried reading an SD card which was correctly identified but could not be mounted (red error message); switched card but got same result. Tried setting MUT as default engine, and Puppy Drive Mounter stopped working; no use restarting X, had to reboot.
As on previous versions, my two hard drives were listed in reverse order (sdb first), while Hotplug shows them on-screen in correct order.

Boots quickly, sound OK, pasting a highlighted text OK (read about these problems in previous posts), SeaMonkey seems normally stable.
Asrock 775i65GV MoBo with Celeron 2800.

BTW, Puppy 4.1 Alpha4 is now also downloadable from NLUUG (good and fast):

http://ftp.nluug.nl/ftp/pub/os/Linux/di ... 4.1alpha4/

[aarf]

"I drove to Perth last night, partly because I get access to ADSL2 high speed Internet at my relative's place."
I thought Australia was a first world country! Can't someone please sort this out for our dear leader? If all else fails perhaps mailing a USB flash drive like they do in outback Cambodia? I have some spare sticks I could send if required.
Were is the link to the donation bank account?

[Lobster]

Were is the link to the donation bank account?

http://www.puppylinux.com/download/index.html

[linuxcbon]

Can you include new ffmpeg and x264 support ?

[dogone]

It appears that PupX, Barry's new X configuration tool, has no provisions for display power management. Does alpha 4 indeed lack this?

LCD owners may not miss this but those of us still using CRTs need an easy way of toggling DPMS and setting display standby, sleep and power-off times.

[paulh177]

This is a Lin'n'Win "frugal" install on a Windows XP FAT partition with a pup_save file.

The (wired, ethernet) setup is not saved from session to session.
I set up the network, it works fine, I shut down & restart and have to re-setup all over again.

I see that dougal has produced a new network setup script, so I'll download that and give it a go too .

EDIT/Addendum Well I downloaded and untar'd dougal's new network wizard and re-setup using it , and my network setup now persists through a shutdown/reboot cycle.

[dogone]

Booting the Puppy 404 CD on my Thinkpad 600e, the process "hangs" at "Searching for other puppy files on disk drives". The CD activity light just goes dark. The problem appears very similar to this post: http://www.murga-linux.com/puppy/viewto ... bbaff1edfe
except that v3.01 boots just fine on the machine - as does 4.0. No luck with with any boot option, including "pfix=ram".

This laptop has 295MB of RAM and the latest BIOS. The hard drive is gone - replaced by an IDE to CF card adapter and 4GB card. Puppy 2.17 is currently installed (frugal) on the card and it runs flawlessly. I don't therefore suspect the CF card arrangement.

My guess is that this is a legacy hardware/BIOS problem having to do with the later kernel.

[Greatnessguru]

Puppy 404-Frugal boot ...

# pwd
/mnt
# mkdir davfs0
# mount -t davfs http... davfs0
mount: unknown filesystem type 'davfs'


mount.davfs(8) - Linux man page
http://linux.die.net/man/8/mount.davfs
"Name
mount.davfs - Mount a WebDAV resource in a directory

'Synopsis
mount.davfs [-h | --help] [-V | --version]
mount {dir | webdavserver}

'SYNOPSIS (root only)
mount -t davfs [-o option[,...]]webdavserver dir
mount.davfs [-o option[,...]] webdavserver dir

'Description
mount.davfs allows you to mount the
WebDAV resource identified by
webdavserver into the local filesystem
at dir. ..."

Can this be gotten to work for Puppy 4.1?

The nice GUI resource tab in Pmount
can wait for Puppy 4.2, of course.

Thanks, Barry,
Eddie Maddox

[cthisbear]

" I thought Australia was a first world country! "

With third clas politicians and bureaucrats.

Couldn't wipe their own ##### without instructions or the go-ahead from
someone else.
A robot could do better.

Chris.

[zygo]

Not a Puppy bug.

At work I can quickly dl the Puppy iso but I have to burn the files not the iso to CD then boot it with a wakepup floppy at home. I must have used 7zip instead of winzip to extract the files so they're all named in uppercase. Puppy won't boot because it can't find pup_404.sfs. The file is named PUP_404.SFS!

I'll re-extract and reburn tomorrow but, for the time being, does anyone know a way round this.

[JustGreg]

I have Puppy 4.1 alpha 4 sort of working on the Classmate. The installation is a frugal one on vfat partition of the solid state drive. The installation was done using a CDROM (pfix=ram) with the universal installer and saving the CDROM configuration to the partition as pup_save file.

Initially, the installation would not work and would hang at the start of x-windows. I would get the X mouse cursor and could move the cursor about the screen. However, x-windows startup never finished. Crtl-alt-backspace would end x-windows, The console display would have trace information (lots of hex numbers) and the system was ung.
I almost reach for the screw driver to remove the battery package. However, after holding the power button done for a minute or so, the Classmate shut down.

Using pfix=nox, I found the problem was with x-windows startup. After reading the bug reports, I got the alpha 4 to work with these boot parameters:
pmedia=usbflash pfix=copy, layerfs=aufs
Alpha 4 works and correctly detected the solid state drive for pupmode=13. The save icon is displayed on the desktop.

Alpha 4 still has two problems that I found with alpha 3. The program ffmpeg does not support the video device option. One can not use ffmpeg to check a web camera. The connection wizard still acts funny with a wpa2 connection. It reports wpa2 network not found, but
runs the test wireless and then one can make a auto dhcp request with a working network.

[BarryK]

Puppy 404-Frugal boot ...

# pwd
/mnt
# mkdir davfs0
# mount -t davfs http... davfs0
mount: unknown filesystem type 'davfs'


mount.davfs(8) - Linux man page
http://linux.die.net/man/8/mount.davfs
"Name
mount.davfs - Mount a WebDAV resource in a directory

'Synopsis
mount.davfs [-h | --help] [-V | --version]
mount {dir | webdavserver}

'SYNOPSIS (root only)
mount -t davfs [-o option[,...]]webdavserver dir
mount.davfs [-o option[,...]] webdavserver dir

'Description
mount.davfs allows you to mount the
WebDAV resource identified by
webdavserver into the local filesystem
at dir. ..."

Can this be gotten to work for Puppy 4.1?

The nice GUI resource tab in Pmount
can wait for Puppy 4.2, of course.

Thanks, Barry,
Eddie Maddox

Yes, but where does davfs source come from? I could not find it when I compiled the kernel a couple of days ago, so it seems it isn't part of the source. So it is a 3rd party driver.