2.16 Alpha Bugs

Please post any bugs you have found
Message
Author
rrolsbe
Posts: 185
Joined: Wed 15 Nov 2006, 21:53

Re: I am getting the save button

#31 Post by rrolsbe »

John Doe wrote:
rrolsbe wrote:Looks like Puppy thinks the external USB hard drive is a USB flash.
You can specify to puppy like this:

puppy pmedia=usbhd
or
puppy pmedia=usbflash

I don't think there is anyway to tell the difference, for certain, in code. The USB class/subclass/protocol seems to be rather unrespected by hardware makers. There is a place for them, but my drives don't seem to fall in line.
Thanks for your suggestion but I am not booting from the USB hard drive I am just using it to store my pup_save configuration file. If I use either of the pmedia commands the boot process expects the boot files to be on the selected device. I agree it would be difficult to determine if the USB attached device was a USB flash, compact flash or hard drive; therefore, if there were a boot command to tell puppy my pup_save files were being stored on a hard drive attached via USB would solve this problem. I know most people do not use a USB attached hard drives and if they do, they boot puppy from the USB attached hard drive. Puppy is by FAR the most flexible Linux distribution I have tried and adding this capability would put Puppy further out in front. NOTE: Puppy works fine thinking the pup_save file is stored on a flash device it just could work better if puppy could be told the pup_save file was on a hard drive.

Again thanks for your reply!!
Regards
Ron

User avatar
capoverde
Posts: 232
Joined: Wed 28 Jun 2006, 21:36
Location: Sanremo (Italy) with fine seaview

#32 Post by capoverde »

Puppy_2.16_alpha first test:

- No bugs found for now, seems quite solid, browsing among videos & audio never gave problems; new firewall version seems faster, requires only two OK's by user;

- Nice icons, grey background doesn't stress eyes - though won't raise wows from graphics enthusiasts; new background faultlessly loaded;

- Sound works well, at least on my old test-PC; Zmixer had no mute buttons, the Puppy mixer has but mutes an input device by throwing its fader to zero. It would be best then if it could keep the fader setting when muted, giving the same volume as before when un-muted, as in hardware mixers;

- Pmount seems to work well, more intuitive GUI.

More to come as testing goes further.
Anyway fine job Barry, always wondering how you manage to do all this...

Henry
Posts: 863
Joined: Sun 30 Jul 2006, 02:28
Location: Oregon USA
Contact:

#33 Post by Henry »

Hello, Barry and all,

Above I wrote negatively about Gxine. I have just edited that out. Please disregard. I was not comparing Gxine with other players, just complaining that I couldn't get it to work. Well, I have finally got my installation fixed and it works. As usual Barry has shown good judgment in this selection.

But I like to run a tight ship, and have already dumped realplayer and the neat xfreecd I had used as bandaids. Sorry for any confusion caused.

Henry
Last edited by Henry on Sat 28 Apr 2007, 01:23, edited 1 time in total.

vanchutr
Posts: 438
Joined: Sat 05 Aug 2006, 12:04

Can't make a 216 alpha frugal installation

#34 Post by vanchutr »

1.
216 alpha is good when I take a full installation on ext2/swap partitions and on usb stick. But i was failed to make it run with the frugal install.
Is this a bug?
2.
216 alpha was not automount the my .sfs file with full installation?. How to?

Kal
Posts: 626
Joined: Thu 05 May 2005, 16:59
Location: California, High Desert

Mini-Volume

#35 Post by Kal »

Just a reminder that rarsa's newest mini-volume.tcl has not been updated in Puppy 2.16a.

http://www.murga-linux.com/puppy/viewtopic.php?t=8293

Kal

vern72023
Posts: 158
Joined: Mon 26 Dec 2005, 05:15
Location: Jacksonville Fl

#36 Post by vern72023 »

vanchutr
I run as a frugal install off of a cf card that presents as an ide drive formatted in fat and in fact thats what i am on writing this

one change in 216 is with how it loads sfs files and it is an enhancement not a bug

there is a new program called bootmanager under system i think and you have to use that the first time you boot to specify what sfs files you want to load - its a nice, simple program and allows for a lot of flexibility and granular control

George
george

vanchutr
Posts: 438
Joined: Sat 05 Aug 2006, 12:04

216 frugal installation

#37 Post by vanchutr »

To Vern72023,
Thank your fast reply.
I'd installed frugal installation with grub.exe and this menu.lst

Code: Select all

timeout 0
default 0
title Puppy RAM
    rootnoverify (hd0,0)
    kernel /vmlinuz root=/dev/ram0 ramdisk_size=16384 PFILE=pup_216.sfs PHOME=hda1
    initrd /initrd.gz

But I was failed with this (with loadlin.exe)

Code: Select all

vmlinuz
root=/dev/ram0
rw
initrd=initrd.gz
vga=normal
ramdisk_size=100000
init=/etc/init
lang=en
apm=power-off
nomce
noapic
noacpi
noscsi
quiet
BOOT_IMAGE=pup_216.sfs
What difference between two installations?

GuestToo
Puppy Master
Posts: 4083
Joined: Wed 04 May 2005, 18:11

#38 Post by GuestToo »

Puppy 216 is not supposed to need a ramdisk parameter ... so root=/dev/ram0 and ramdisk_size=100000 should not be necessary

i think init=/etc/init should be init=/sbin/init ... i think the kernel uses /sbin/init by default, so that parameter also may not be necessary

the BOOT_IMAGE=pup_216.sfs parameter may also not be necessary

vanchutr
Posts: 438
Joined: Sat 05 Aug 2006, 12:04

216 frugal installation

#39 Post by vanchutr »

Thank Guesto for your fast reply (instructions)
I'd found some strange thing:
1. I must put the vmlinuz, initrd.gz and the pup_216 on the C: root (C:\)
2. And I edited the option.txt like that:

Code: Select all

vmlinuz
root=/dev/ram0
rw
initrd=initrd.gz
vga=normal
ramdisk_size=16380
init=/etc/init
lang=en
apm=power-off
nomce
noapic
noacpi
noscsi
quiet
PMEDIA=idehd
BOOT_IMAGE=pup_216.sfs
3. Now my pup216 ran successfully (I'd added the line 'PMEDIA=idehd'

Fishy
Posts: 234
Joined: Fri 27 Jan 2006, 01:22

#40 Post by Fishy »

Where in a full install do you place .sfs files? The boot manager shows the openoffice.sfs installed and the ignore box is not checked.

I placed openoffice.sfs in / just as the pup_save and zdrv.sfs were atomatically placed there.

The openoffice.sfs was downloafed from Barry's site and md5sum checked after download. :D

User avatar
fudgy
Posts: 86
Joined: Wed 07 Jun 2006, 09:40
Location: Berlin, Germany

#41 Post by fudgy »

i had alook at aufs wh-files, and it looks like a big step foreward to me ! Please have a look at the attached file if you like to.

## partview broken ? ##

Code: Select all

sh-3.00# partview
Error in startup script: child process exited abnormally
    while executing
"exec /bin/losetup-FULL /dev/loop1 | grep "/pup_save" | cut -f 2 -d "(" | cut -f 1 -d ")" | cut -f 4 -d "/" "
    (procedure "df_check" line 11)
    invoked from within
"df_check"
    (file "/usr/sbin/partview" line 84)
## bootmanager issue ##
bootmanager only shows *_216.sfs files (e.g. not kde.sfs)

## feature request: bootcode ##
can we please have an official cheat code PUPSAVE=ext3,hda3,/pup_save1.3fs
also: EXTRASFS=ext3,hda3,/kde.sfs ? too many people hacking initrd.gz ...

Very polished outfit... are we going mainstream ? I personnaly think it's now time to give something back to the hard working 'hobbyists' in the form of ... uuhhmm ... money ?

-fudgy
Attachments
aufs.txt.tar.gz
(730 Bytes) Downloaded 452 times

User avatar
tronkel
Posts: 1116
Joined: Fri 30 Sep 2005, 11:27
Location: Vienna Austria
Contact:

Multisession and burniso2cd

#42 Post by tronkel »

Flash wrote:
The iso I downloaded might be corrupted, but I thought I'd report this to see if anyone else is having the same problem with 2.16a multisession.
burniso2cd has been problematical on my system for the last 2 or threee versions of Puppy. Does not seem able to burn a normal ISO far less deal with multisession. I tried Gcombust - was OK with ISO but not OK with multisession.

I now use Xcdroast. It seem to work OK. This is the debian dotpup from Mark Ulrich's puppyisos server. Other versions including the standard version installed via petGet are missing dependencies and do not run.

Wonder if burniso2cd needs some attention.
Life is too short to spend it in front of a computer

User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

#43 Post by BarryK »

GuestToo wrote:Puppy 216 is not supposed to need a ramdisk parameter ... so root=/dev/ram0 and ramdisk_size=100000 should not be necessary

i think init=/etc/init should be init=/sbin/init ... i think the kernel uses /sbin/init by default, so that parameter also may not be necessary

the BOOT_IMAGE=pup_216.sfs parameter may also not be necessary
G2, 2.16alpha uses a cpio initramfs and the init script is now at /init. And yes, /init is the default so no need to specify.

User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

#44 Post by BarryK »

I'm back from the mini-holiday, and have made lots of notes on issues raised in this thread -- will get going on it!

The reports on GParted puzzles me.... it wouldn't be an upgrade problem by any chance?

User avatar
rerwin
Posts: 2017
Joined: Wed 24 Aug 2005, 22:50
Location: Maine, USA

Gparted issue

#45 Post by rerwin »

Glad to have you back. I enjoyed your trip report and pix.
When I encountered the show-stopper with Gparted, I had booted from CD with pfix=ram so I could operate on the entire drive. No update/upgrade involved.
Richard

User avatar
ezeze5000
Posts: 347
Joined: Tue 10 May 2005, 17:48
Location: Missouri U.S.A
Contact:

Grub Possable bug

#46 Post by ezeze5000 »

I Have installed Puppy-216-experimental to a ext2 partition, but grub wouldn't install properly. It doesn't give the choices like installing to mbr.

It wants to use uniofs as a default choice.

I had to boot with puppy-215 to get grub to install properly.

Anyway I got it fixed, I'm writing this to you from puppy-216-experimental, from a stepnote NC1500 laptop.

This Puppy Rocks!
If at first you don't succeed try try again!

sawdust
Posts: 1
Joined: Wed 02 May 2007, 15:58
Location: Virginia USA

2.16exp3-seamonkey-openoffice

#47 Post by sawdust »

All seems to work very well with this alpha.
I did a HD-install and everything just works, I installed Duke nukem and
Supertux dotpups and they were in the menu as dotpups.
After reboot the dotpups list in menu was gone.
This is the only thing I have had go wrong.

Great Puppy!

User avatar
capoverde
Posts: 232
Joined: Wed 28 Jun 2006, 21:36
Location: Sanremo (Italy) with fine seaview

#48 Post by capoverde »

No problems installing Puppy-2.16alpha on a SecureDigital flash card through a USB card reader, boots OK from that card; but on closing, if the pup_save file has to be written on the card and this is write-protected, no warning message is given and the session data get lost.

I'm testing 2.16 alpha on different computers (4) and with different card readers (3).
I know nothing about hardware recognition, but in general it seems that MUT (default mounter in Puppy 2.14) has much better chances to access a flash card than Puppy 2.16's Pmount .
Some card types seem more difficult to access than others (SmartMedia is terrible, SecureDigital works almost always) and one card reader seems not to work at all with Pmount.

Anyone with similar experiences?
Last edited by capoverde on Thu 03 May 2007, 14:55, edited 2 times in total.

User avatar
capoverde
Posts: 232
Joined: Wed 28 Jun 2006, 21:36
Location: Sanremo (Italy) with fine seaview

#49 Post by capoverde »

After more tests with Pmount and MUT in Puppy-2.16alpha, it is confirmed that MUT is far more prone than Pmount to "see" a flash card inserted in a USB reader. In one case only after restarting X (?) Pmount saw the card it didn't see before.
Anyway, after a card is inserted then taken away a couple of times, even MUT seems not to like the game and tends to ignore new card insertions (this happened already in preceding versions).

Of course, once MUT has found the card, Pmount also sees it.

One thing that surprised me: with a machine using a USB keyboard/hub (has a female USB connector on a side) the USB port to which this is connected works OK, but the mainboard's other USB port is simply not activated at all!
This was understood only after twiddling around for about half an hour, no card reader worked from there :-( ... Probably happens with former versions too.

(As a byproduct of these tests, one of the card readers - the brand-new one! - was found to be defective at its SmartMedia slot. Gonna take it back to the dealer...)

User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

#50 Post by BarryK »

I've taken that 2.16exp3 iso off ibiblio so that noone else will download it, as it can cause problems on your PC due to the ext2-compression.

Post Reply