Puppy 4.1.2 (2.6.25.16 kernel) final - bug reports

Message

niksfish · #46 Post by **niksfish** » Sat 21 Feb 2009, 20:15

Well i'm posting here because somewere it says that's here the place to post suggestions.

I wanted to install puppy normally in the hdd, like some windows or something else. I have tried a lot, but I couldn't make it boot from the bios.

I would like to see something more automatic, because puppy it's suposed to be an SO for easy use. I'm not noob, really I have tried but I couldn't configure Grub or lilo... Maybe it is my bios, but the wizard to install Puppy on the hard disk sucks. I would like to see something to install it directly (i dont know how is called) on that screen black with withe letters (or blue with white letters), with no graphical interface, like installing windows... Or a better wizard that make more things for you.

zvonik · #47 Post by **zvonik** » Wed 25 Feb 2009, 21:14

First time puppy user on a Dell C600 laptop. Beats xubuntu hands down on this p3 700Mhz and 256M ram laptop.

I tried to install an sfs as instructed and use bootmanager to select it and it didn't work. Multiple posts suggest that this is broken in 412 (I can provide links if needed). Downloading devx_412.sfs to /mnt/home (and also seen at /) in a hard drive install (full?) didn't get seen by menu->system->bootmanager at all. But in a terminal, if I cd to /mnt/home and type bootmanager, presto now it's found (by the upper-right selection) so bootmanager from the menu appears to start in the wrong directory. Now I have an entry in /etc/rc.d/BOOTLOG for this sfs and I reboot and ... nothing. No gcc found. So it's still not being mounted at boot.

Also, bootmanager from the command line spits out this:
/usr/sbin/bootmanager: line 85: cd: /initrd/: No such file or directory

and I get 412# as puppyversion. Is the hash at the end correct?
# cat /etc/puppyversion
412#

I've looked through the bootmanager script but it's too complicated for me. I hope this can be fixed in 4.2 and this should be a priority as some of the fun of puppy is in the sfs mounts.

vtpup · #48 Post by **vtpup** » Thu 26 Feb 2009, 03:14

@zvonik -- I have a frugal install, but I believe the Bootmanager cannot be used to add an sfs to a full hard drive installation.

There are other methods of adding the contents of an sfs to full installs. Do some more searching on these forums -- I believe Artie's thread talks about methods of doing it, along with a lot of other good advice for new users.

#49 Post by **Pizzasgood** » Thu 26 Feb 2009, 04:43

For a full-hd install:

Click the .sfs file. That will cause Puppy to mount it and open a window with the contents. Open a terminal there by either right-clicking and going to "Window -> Terminal Here", OR by pressing the back-quote key.

In the terminal, type this and press enter:

Code: Select all

cp -a * /

When it finishes copying the files, you can close the terminal, click the .sfs again to umount it, and carry on. At this point the actual .sfs file is no longer needed.

zvonik · #50 Post by **zvonik** » Thu 26 Feb 2009, 15:00

Hi guys. Thanks for the replies. I found nothing in the manual or any other documentation that this shouldn't work with a hard drive install. I did find many posts from people with the same problem. And I did find the post about mounting the sfs and copying out the contents but that seemed like such an undocumented kluge in an otherwise elegant environment.

It would be nice to have a built-in sfs installer. Download an sfs, click on it in a file manager and it installs. Whether it installs to /mnt/home and uses the bootmanager behind the scenes or does a mount and copy, the user shouldn't have to know the details. The next release would be a nice place to start doing this.

vtpup · #51 Post by **vtpup** » Thu 26 Feb 2009, 16:45

I'm very much in favor of an error message when attempting to add an sfs and informational hints indicating that an sfs file can not be added to an HD full install in Bootmamanager. People should not need to search a forum to find out why something doesn't work in about 50% of installed systems.

As far as adding capability to install an sfs goes, I believe it might be more appropriate to install the contents of .sfs files for full HD installs in the Puppy package manager than in the Bootmanager, since it has nothing to do with boot loading, as it does for frugal installs. It is a true fileset installation.

Note that in a full install, programs added from an sfs integrate in the same fashion as those from a .pet. Basically you are just overwriting new files onto your file system. Therefore there is no advantage to using an sfs rather than a .pet, assuming what you want is available in a .pet.

In a frugal install, the sfs does behave differently than a .pet, and saves space in the personal savefile. It is an overlay, not an overwrite for existing saved files.

mikeb · #52 Post by **mikeb** » Fri 27 Feb 2009, 04:39

Ok so is not so much a bug as a logic thing...

If a full install is present and a frugal install is added then until there is a pup_save the init script assumes that the full install is the pup_save...mode 6. This is not prevented by pfix=ram...I feel it should be to allow for that first boot although it now seems that this would now prevent creation of a pup_save...and if a blank pup_save was created would this mess up a first frugal boot?

Is mode 6 commonly used?...7 is for those flash internal drives I believe.

And yes having a frugal alongside a full install is very useful for testing...perhaps a better way of differentiating between a 'true full install' and a 'pup_save as a partition' is needed (presence of /initrd is a dead givaway)

crosseyed

mike

PaulBx1 · #53 Post by **PaulBx1** » Fri 20 Mar 2009, 18:47

Flyover info for drive icons is still wrong. It appears to be the case that whatever was first in there, stays there forever. For example, my sda1 was at one time ntfs, but has since been changed to ext3. But the flyover still says ntfs. Also when I right click the icon and select "edit item", the "Arguments to pass..." variable shown is "drive ntfs". Changing that to "drive ext3" does not change anything that I can tell.

Flyovers probably ought to be eliminated if they can't be depended on to give the correct information.

PaulBx1 · #54 Post by **PaulBx1** » Sat 02 May 2009, 23:14

Don't know if anyone pays attention to this thread any more...

When I do "puppy pfix=fsck" for my heavy-encrypted pupsave, I get no indication an fsck is actually taking place.

#55 Post by **BÃ©Ã¨m** » Sat 02 May 2009, 23:18

You could boot with (puppy) pfix=ram and run the fsck on the pup_save by hand. You'll get the messages.

PaulBx1 · #56 Post by **PaulBx1** » Sat 02 May 2009, 23:29

I finally figured out how to do that. Since it badly needed the fsck, it is clear "pfix=fsck" did nothing.

I'm guessing the modprobe of cryptoloop or aes is missing?

#57 Post by **BÃ©Ã¨m** » Sat 02 May 2009, 23:37

Good you saw the "light"

Sage · #58 Post by **Sage** » Mon 11 May 2009, 16:42

Oh dear - third time lucky - popped this into the wrong section twice already.
Glad to see I'm not alone - yes, there's something wrong with the PUI/Xvideo-to-install, (but not the live version):

Don't normally look at the CE and hand-me-down versions - too many cooks, too many fingers burnt. This time I wanted to run up an old AMDKII-6/500. Had to burn to CD-R to use the old CD which can't read RW s, another thing I hate to waste resources on.

Big Mistake - again.

After a FULL install there emerged the return of an old friend - looping associated with the X system. Haven't seen that one for years.

Can't read the exact detail, but the first line talks about 'touch' - 'can't touch'
something about 'temp' files???
lines 401 & 402 ???
doesn't like something in /usr/X11R7/bin/xwin

copied the whole of the X11R7 directory from CD along with various other random guesses to no avail.

Absolute bummer. I know folks like to try hard, but bitter experience with virtually every distro teaches that the lead developer is generally the best option to complete a task successfully. Shame I hate the MarineBeast and he loves it....

rerwin · #59 Post by **rerwin** » Wed 13 May 2009, 19:51

The /usr/bin/dir2pet script reacts unexpectedly if a space character is included in the name of the directory to be made into a PET package. Inserting the following command as the first command (line 12 in 4.1.2; line 13 in 4.7.1) of the script would prevent the behavior and assist the user in correcting the problem.

Code: Select all

[ "`echo "$@" | grep ' '`" != "" ] && echo -e "This script expects a directory name without embedded spaces.\nAdditional arguments are not appropriate.\nPlease remove or replace any space characters in the directory name." && exit #v413

Richard

SilverPuppy · #60 Post by **SilverPuppy** » Sat 30 May 2009, 03:33

I discovered a problem with the desktop interface. If you access a very large directory with ROX, (10,000+ files will definitely do it) the ROX box crashes AND so does the entire desktop (icons and background.) Open programs and JWM continue to work. I'm using 4.1.2 and will never use 4.2.anything, so can you enlighten me as to whether there might be a fix in for this? It's a bit annoying to not be able to access ultra-large directories, as I do data recovery and sometimes create such beasts......

sideburns · #61 Post by **sideburns** » Thu 04 Jun 2009, 23:44

I had an old laptop that was running fine on Puppy 4.0. Then, I "upgraged" to 4.2.1 and was appalled!

First, if you try to mount the CD and use it to upgrade, the installer can't find the needed files. You can only do the upgrade by booting from the CD. Very bad!

Second, not only do you have to edit grub, the installer doesn't bother to mount the partition for you (or remind you to do so). Just Plain SloppAss!

Third, it stomped all over my custom settings for wallpaper and start programs, and I'm going to have to waste hours of time figuring out what to edit and how to get back where I should have been in the first place.

Fourth: it took out the line adding the module needed to see my USB PCMCIA card so that I can't use USB any more. Not only that, if I change the mounter to use mutt, to "see" USB, it tells me it's working, then vanishes without popping up a window so that I can, at least, go back to where it was. Totally unusable!

Quite frankly, I'm sorry I "upgraded." I'm going to need a lot of time, a lot of work and, probably,. some suggestions from some of you to get my system working properly again.

sideburns · #62 Post by **sideburns** » Fri 05 Jun 2009, 23:26

More information. I've managed to get the partition mounter working by deleting a config file. However, I'm now house sitting, and the laptop's all I've got. Puppy 4.2.1 doesn't recognize my PCMCIA NIC, and can't access it, but I happen to have a Puppy 4.0 CD handy. It finds it, loads the pcnet_cs module and It Just Works. Alas, if I boot back into 4.2, it can't find the interface even if I tell it what module to use. Right now, I'm using the Live CD because it's the only Internet access I have. Calling this unacceptable is an understatement!

Does anybody know what I can do, short of nuking my installation and re-installing 4.0? I ask, because 4.2.1 is currently useless to me.

trapster · #63 Post by **trapster** » Mon 08 Jun 2009, 14:30

If 4.2.1 is useless to you, use your backup save file and go back and use 4.00. What was it in 4.2.1 that you needed the upgrade?
I still use 3.0 for a lot of things.

As far as the wifi module. If it's loading a module that is incorrect, make sure you blacklist it before trying to load the correct one.

sideburns · #64 Post by **sideburns** » Mon 08 Jun 2009, 16:38

It's not that I needed something specific from 4.2.1, I thought that it would be better in general. After all, newer versions are supposed to be better.

And, your advice about the "wifi" card shows you didn't read too well. First, it's not wifi, it's a NIC for Ethernet. Second, it was loading the right module, it just can't use it. Right now, I'm running off a Live CD while housesitting at Chaos Manor (http://www.jerrypournelle.com) because it's my only way to get connected.

I'd already figured that I'd have to nuke and reinstall, I just hoped that I'd actually get some help from this forum. My mistake.

James C · #65 Post by **James C** » Mon 08 Jun 2009, 18:46

If you were wanting help your post should probably be in the help section and not the area for bug reports.

More details also needed, type of install( full, frugal, etc.), computer specs, the more info the better.

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum