4.1 Alpha 4

[Firefox]

Burned pup404 to cd`s in multi and normal mode.
booted pfix=ram
did not notice any lights on modem being tested - previous
versions usually sequenced twice during bootup.
clicked PupDial from Menu - NO RESPONCE or a window config to click on.
Clicked Desktop connect - Window appeared - clicked button
- NO RESPONCE to probe or setup, just disapeared - unable to
retreave by clicking Desktop connect again.
Clicked Wizard wizard icon for dialup - NO RESPONCE.
UNABLE TO CONNECT TO INTERNET AS THE
ONLY FACILITY IN MENU FOR DIALUP MODEMS
IS PUPDIAL WHICH DOESN`T WORK!!!!!!!!!!!!!!!!!!!!!

[BarryK]

I'm booting 404 from CD with a pup_save on flash.

As compiled, Seamonkey 1.11 appears quite unstable. I experienced one outright crash and three hangs of various extents in the first two hours of testing. The crash did not affect X but SM would not restart. The three hangs partially or completely disabled X - no keyboard and/or mouse response.

Please advise as to how I can capture log/debug.

Can you try this:
Edit the 'syslinux.cfg' or 'extlinux.cfg' file on the Flash drive and append
layerfs=aufs
onto the end of the line.

That will cause Puppy to use Aufs rather than Unionfs. Then use SM for awhile and let us know if it crashes.

[kirk]

Working nice for me. Very impressive.

A couple of suggestions:

1) Any reason AUFS is not the default?

2) I really hate these long threads for every bug in a release. Makes it hard to know if a bug has been reported or if a solution to a bug has been posted or if several people have reported the same bug. Without reading the whole thread. Alpha3 thread is 5 pages long and Puppy4 is 15 pages long. Could we have a sub-section under bugs for each release? Then people could start a new thread for each bug and if someone has the same problem they could post on that thread.

Ok, my rant is over.

Nice job Barry.

[dogone]

Can you try this:
Edit the 'syslinux.cfg' or 'extlinux.cfg' file on the Flash drive and append layerfs=aufs onto the end of the line. That will cause Puppy to use Aufs rather than Unionfs. Then use SM for awhile and let us know if it crashes.

I do not find syslinux.cfg or extlinux.cfg anywhere on the flash, CD or in any sfs file. I find only /initrd/pup_r02/sbin/extlinux, which is a binary. Can you be more specific?

Perhaps I should add that I've three Puppy installs on my flash stick, in /mnt/home/301, /mnt/home/400 and now /mnt/home/404, so all boots include a stop at the pup_save list.

[Jim1911]

I'm a new puppy user who has been having a great time learning about this superb product. It's amazing what you all have accomplished with puppy in such a short time.

This distribution is very stable on my Dell Dimension 8250. One problem though, Gparted Partition Manager fails to recognize the partitions on sdb where there are 4 partitions where my frugal installations are located. It reports "unallocated 117.75GiB" for that drive. This is true also for the earlier 4.1 alphas. 4.0 and earlier releases reports the partitions accurately. I've consistently had the same problem whether using pfix=ram or updating an earlier save file.

Thanks for all your hard work, dedication, and enthusiasm for a great linux distribution.
Jim

Followup: Using Pup 4.0, pfix=ram, I repartitioned this drive into 4 partitions, fat32, ntfs, ext2, and swap. Then checked with 4.1 alpha, partitions still not recognized.

[ttuuxxx]

Hi Barry I don't know if you seen this thread I started
http://www.murga-linux.com/puppy/viewto ... 951#215951
Basically its a 11kb program that lxde uses to set Xorg Setting within the window manager, It works really well. Something like that would make a great addition to puppy, since it doesn't leave Jwm and exits X to set the settings, That way you keep all the pages/files without them closing, Great if your a web designer who wants to test different screen sizes. It works on Puppy 4.0 without any added files.

This is the pet package I compiled on puppy 4.0 dingo
http://www.murga-linux.com/puppy/viewto ... h&id=10877

This is the original source location http://downloads.sourceforge.net/lxde/l ... g_mirror=0


This is main the locations of LXDE
http://lxde.org/
http://sourceforge.net/projects/lxde/
ttuuxxx

[BarryK]

Barryk wrote:
"Can you try this: Edit the 'syslinux.cfg' or 'extlinux.cfg' file on the Flash drive and append layerfs=aufs onto the end of the line. "

Barry, I do not find syslinux.cfg or extlinux.cfg anywhere on the flash, CD or in any sfs file. I find only /initrd/pup_r02/sbin/extlinux, which is a binary. Can you be more specific?

P.S. I should add that I've three Puppy installs on my flash stick, in /mnt/home/301, /mnt/home/400 and now /mnt/home/404, so all boots include a stop at the pup_save list.

How have you installed Puppy to the Flash drive? Normally it would have a syslinux.cfg file if the f.s. is vfat, or extlinux.cfg if the f.s. is ext2/3 on the drive boot partition.
You reported the crashing was occurring when booted from Flash, so that's why I gave that reply.

[dogone]

How have you installed Puppy to the Flash drive? Normally it would have a syslinux.cfg file if the f.s. is vfat, or extlinux.cfg if the f.s. is ext2/3 on the drive boot partition.

No, 404 is not installed. I am booting 404 from CD in conjunction with a pup_save.2fs file on the flash stick (sdb1).

Following my first 404 session, I was prompted to create the pup_save file. I specified that "pup_save-404.2fs" be placed in directory "/404/" of sdb1. I then accepted the option of copying the additional files to the stick.

Reboot was successful and fast (<30 sec). Looking at the stick, I found only /home/pup_404.sfs and my save file, /home/404/pup_save-404.2fs. There are no other 404 related files on my flash stick. Sound right?

[Sit Heel Speak]

It is not recognizing the pupsave which the initial install creates (***EDITED: somehow, the pup-save file was created in the topmost folder on the partition, not in /puppy404 alongside pup_400.sfs. Moving it there, makes it work OK***)

At the end of my initial live-CD session, I used Puppy Universal Installer to put a frugal install on the third IDE hard drive, first partition (sdc1). Then, shut down, and in response to the prompts as usual created a pupsave file in the psubdir, /puppy404 (***EDITED: incorrect, it was in the topmost directory***). Upon rebooting, selecting the new install in grub, the pupsave was not recognized (e.g. had to select us keyboard and the xorg resolution all over again). The pupsave is present, just not seen.

[BarryK]

Barry,
To clarify. 404 is NOT installed. I am booting 404 from CD in conjunction with a pup_save.2fs file on the flash stick (sdb1).

Following my first 404 session, I was prompted to create the pup_save file. I specified that "pup_save-404.2fs" be placed in directory "/404/" of sdb1. I then accepted the option of copying the additional files to the stick.

Reboot was successful and fast (<30 sec). Looking at the stick, I found only /home/pup_404.sfs and my save file, /home/404/pup_save-404.2fs. There are no other 404 related files on my flash stick. Sound right?

Ok, well it's very simple then. When you get the 5 second boot screen, type:
puppy layerfs=aufs

then you will boot up using Aufs instead of Unionfs.

[ricstef]

Hi,
This looks like a really interesting version, and am looking forward to testing all the new features.
The first time i've experienced this problem is in 404:
My ethernet driver: atl2 can not be loaded and seems no where on the distro. Same for my wifi driver: ath_pci.
Doing the >Load module >More >Auto-probe thing results in various modules being selected but none allows a new interface to be detected. ...
Soooo, how do I get these drivers ? Or, where are they located on the 301 Pupeee, and what is the appropriate directory to place them in ?
Thanks for any help.

Cheers
Richard.

[prehistoric]

I experienced hangs at shutdown earlier on my Compaq Armada M700. So far, none with aufs. From now on, posters need to say if they are using aufs, as layer problems can show up in many ways.

Remaining problems are familiar: isapnp sound (ess18xx) doesn't get configured correctly by default; wireless card (WaveBuddy, uses atmel_cs driver,) will not configure correctly until some other wireless device is connected. The latter sounds like some problem with cardmgr or another module needed before wireless can load driver modules.

With regard to kirk's difficulty finding bug reports on threads, how about a wiki page listing bugs named in the thread and their status? This doesn't have to be very official, and, even if incomplete, it would cut down on reports of problems already addressed.

[Sit Heel Speak]

Solved my problem of the not-seen pup_save-pup404.2fs. Somehow, it got created in the topmost folder, not my psubdir. Moving it there, fixed it.

Now let's see how this SIP thingy works...

[tempestuous]

My ethernet driver: atl2 can not be loaded and seems no where on the distro. Same for my wifi driver: ath_pci.

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.

[CHLee]

Dear Barry,
1. zd1211rw couldn't load firmware, when dmesg have below output:

zd1211rw 4-6:1.0: phy0
usbcore: registered new interface driver zd1211rw
zd1211rw 4-6:1.0: couldn't load firmware. Error number -2
zd1211rw 4-6:1.0: couldn't load firmware. Error number -2
zd1211rw 4-6:1.0: couldn't load firmware. Error number -2
zd1211rw 4-6:1.0: couldn't load firmware. Error number -2
zd1211rw 4-6:1.0: couldn't load firmware. Error number -2

2. Both pmedia=ideflash and pmedia=ataflash can not make
pup404 go to PUPMODE 13, only PUPMODE=12.
My extlinux.conf as below :

default p404
display boot.msg
prompt 1
label p404
kernel /p404/vmlinuz
append initrd=/p404/initrd.gz pmedia=ideflash psubdir=p404
timeout 50

The 4.1 Alpha 4 was install in EEEPC internal SSD(IDE flash disk).
Could you let puppy run in PUPMODE 13 when you detact "flash"
in pmedia ?

3. pppoeconf not working, I type the pppoeconf in rxvt, and
it find network eth0, ask me for username and password,
it ask me other question. At the last window it ask :
"Your PPPD is configured now. Would you like to start
the connection at boot time? Yes /No" . Even I select
Yes or no, the script exit. The below is the display
of the rxvt:

#pppoeconf
chown: unknown user/group root:dip
cp: cannot stat `/etc/network/interfaces':
No such file or directory
/usr/sbin/pppoeconf: line 380: /etc/ppp/ip-down.d/0clampmss:
No such file or directory
chmod: cannot access `/etc/ppp/ip-down.d/0clampmss': No such file or directory
chmod: failed to get attributes of `/etc/network/interfaces': No such file or directory
/sbin/ifconfig eth0 up # line maintained by pppoeconf
run-parts /etc/network/if-pre-up.d
pon dsl-provider
run-parts /etc/network/if-up.d
run-parts /etc/network/if-pre-up.d
run-parts /etc/network/if-up.d
mv: cannot move `/tmp/interfaces.pppoeconf.R19206' to `/etc/network/interfaces': No such file or directory

4. Puppy Axel download accelerator have Segmentation fault error
and DOWNLOAD FAILURE.

5. In pup301, we can use mouse to high light the content and
Paste it any test editor. But 4.1 Alpha 4 can not.

Thanks Barry very much ! You let us enjoy linux.
C.H.Lee

[boscobearbank]

To add to the intel/i810 driver problem stories, I'll start with the output of lspci:

00:02.0 VGA compatible controller: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 03)

I've can get 1680x1050 with a custom modeline in my xorg.conf files. Works fine in older Puppies, Fedora, and Ubuntu. I boot Puppy 404 from the CD (using xorg, 1280x1024), exit X, copy my custom xorg.conf file to /etc/X11, re-enter X (typing either xwin or startx, it doesn't matter), and I'm back at 1280x1024; my custom xorg.conf file has disappeard and been replaced. Mounting one of my old pup_save files where 1680x1050 actually works, exiting X, and copying /root, /etc, /usr, and /tmp from the pup_save file to / actually lets me run X as 1680x1050. What's going on here?

[dogone]

Ok, well it's very simple then. When you get the 5 second boot screen, type:
puppy layerfs=aufs...

Barry, you pegged it precisely. Those very serious problems with Seamonkey 1.11 disappeared immediately after booting the CD with the "layerfs=aufs" option. SM is fast and appears stable.

Update: I've remastered the original alpha 4 disk with one change: added "layerfs=aufs" to boot options in isolinux.cfg. I'll continue to test using this re-master.

[playdayz]

ricstef wrote:
My ethernet driver: atl2 can not be loaded and seems no where on the distro. Same for my wifi driver: ath_pci.

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.

tempestuous, i don't understand this I have been using ath_pci in 301 and in 4.00 and my wifi has been working In 4.04 there seems to be no ath_pci and my wifi is not working (as in message on p2 of this thread). no worries, this is what alphas are for i think.

[tempestuous]

The ath_pci module is a third party driver from the MADWiFi project. There is the standard ath_pci module normally contained in Puppy, and the specially patched version compatible with Atheros AR5007EG as found in the Asus Eee.

[linuxcbon]

takes a long time to find the sda1, sda2 ... and to show icon "drives" --> PC very slow

free mem applet is not displayed anymore ?

sound is always 0 at start

Code: Select all

# pppoeconf
chown: unknown user/group root:dip