Puppy 4.3.1 -- bug reports and suggestions
Streaming video
Currently trying to watch a live tv feed http://www.bloomberg.com/avp/avp.htm?clipSRC=LiveBTV which causes ff 354 to crash in puppy 431. I've gone to http://puppylinux.org/wikka/Gxine for help, but where are those codec files in package manager??
-
rameshiyer
Puppy 4.31.
While I am working in Puppy 4.31, power to PC suddenly goes. When I tried to boot again after power supply restored, the PC showing some test parameter on the monitor and the system comes to command prompt and not booting. Also system is not taking any commands in this prompt. I have Harddisk installation (sda 8 ext4 partition ) with dual boot. Likewise, if any simple commands applied to puppy terminal, the system hangs and not able to boot again. Kindly help me to restore my PC as I have already installed lot of things in it. Is it required to reinstall the Puppy OS again.
-
rameshiyer
Puppy 4.31.
While I am working in Puppy 4.31, power to PC suddenly goes. When I tried to boot again after power supply restored, the PC showing some test parameter on the monitor and the system comes to command prompt and not booting. Also system is not taking any commands in this prompt. I have Harddisk installation (sda 8 ext4 partition ) with dual boot. Likewise, if any simple commands applied to puppy terminal, the system hangs and not able to boot again. Kindly help me to restore my PC as I have already installed lot of things in it. Is it required to reinstall the Puppy OS again.
rameshiyer:
Boot from the live CD with boot parameter "puppy pfix=ram"
Run e2fsck on your Puppy partition(s)
Try rebooting from HD
Boot from the live CD with boot parameter "puppy pfix=ram"
Run e2fsck on your Puppy partition(s)
Try rebooting from HD
[size=84][i]hangout:[/i] ##b0rked on irc.freenode.net
[i]diversion:[/i] [url]http://alienjeff.net[/url] - visit The Fringe
[i]quote:[/i] "The foundation of authority is based upon the consent of the people." - Thomas Hooker[/size]
[i]diversion:[/i] [url]http://alienjeff.net[/url] - visit The Fringe
[i]quote:[/i] "The foundation of authority is based upon the consent of the people." - Thomas Hooker[/size]
-
Pizzasgood
- Posts: 6183
- Joined: Wed 04 May 2005, 20:28
- Location: Knoxville, TN, USA
The xorgwizard screws up xorg.conf if Xorg detects that the user can have more than one screen. It leaves the line in the Server section that refers to the second screen, but does not bother to create a section for that second screen, rendering Xorg unrunnable.
This is pretty easy to fix. I already posted one back in the 4.1.x thread, and updated it in the 4.2.x threads.
http://murga-linux.com/puppy/viewtopic. ... 607#256607
http://murga-linux.com/puppy/viewtopic. ... 022#287022
One more change needs to be made to prevent that second change from interfering with the first. In the first one, the # should be removed from inside the grep. Without doing that, Xorg will still start just fine because the additional lines in the Server section will be commented out, but xorgwizard won't bother to create the additional Screen sections. It doesn't hurt to fix it so that it does create them, and that way somebody like me who actually wants to use them just has to uncomment the appropriate line in the Server section, and not have to also create the Screen section.
So, attached are the final patched version of xorgwizard for 4.3.1 and also the patch itself. Don't forget to set the xorgwizard script executable if you grab it from this attachment (gzip does not preserve permissions, so it may not be executable when you download and extract it).
This is pretty easy to fix. I already posted one back in the 4.1.x thread, and updated it in the 4.2.x threads.
http://murga-linux.com/puppy/viewtopic. ... 607#256607
http://murga-linux.com/puppy/viewtopic. ... 022#287022
One more change needs to be made to prevent that second change from interfering with the first. In the first one, the # should be removed from inside the grep. Without doing that, Xorg will still start just fine because the additional lines in the Server section will be commented out, but xorgwizard won't bother to create the additional Screen sections. It doesn't hurt to fix it so that it does create them, and that way somebody like me who actually wants to use them just has to uncomment the appropriate line in the Server section, and not have to also create the Screen section.
So, attached are the final patched version of xorgwizard for 4.3.1 and also the patch itself. Don't forget to set the xorgwizard script executable if you grab it from this attachment (gzip does not preserve permissions, so it may not be executable when you download and extract it).
- Attachments
-
- xorgwizard.gz
- (16.99 KiB) Downloaded 586 times
-
- xorgwizard.diff.gz
- (733 Bytes) Downloaded 545 times
[size=75]Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib[/size]
[img]http://www.browserloadofcoolness.com/sig.png[/img]
[img]http://www.browserloadofcoolness.com/sig.png[/img]
When booting up, I get:
-sh: setenv: command not found.
It doesn't seem to affect the overall operation but was noted during boot up.
After booting up, opening the console, I get:
bash: setenv: command not found
Posted for the group and noted VTPUP also received the same error previously.
Best Regards,
John
-sh: setenv: command not found.
It doesn't seem to affect the overall operation but was noted during boot up.
After booting up, opening the console, I get:
bash: setenv: command not found
Posted for the group and noted VTPUP also received the same error previously.
Best Regards,
John
-
Bruce_n_Duane
- Posts: 71
- Joined: Wed 02 Nov 2005, 01:40
- Location: Washington State
USB Drive goes to sleep
Duane has a special made laptop with dual-core 64 bit intel processor
Running Barry's Puppy 4.3.1 with nosmp in boot parameter
Frugal install on a 4 GB USB flash drive in /dev/sdb1
Laptop has 2 GB of ram.
Hard drives of laptop are not used and not mounted.
Xpup set with screensaver NOT enabled and time=0.
Problem:
If the laptop is left on for 1+ hours without activitiy the connection to the USB Flash sdb1 icon disappears, the time stops.
We can move the mouse and it responds. The keyboard works.
But nothing gets saved when we reboot the computer. It just
shutsdown immediately. This shutdown is equal to pulling the plug. On reboot it asks about a sudden shutdown of Xorg.
Why does the Puppy Drive disappear and time stop?
On reboot we had to reset the time and date. The day was one day ahead and the time was 4 hours behind. We are at USA Pacific time which is -8 GMT and now in Pacific Standard Time.
Thanks for looking at this.
-Bruce and Duane.
Running Barry's Puppy 4.3.1 with nosmp in boot parameter
Frugal install on a 4 GB USB flash drive in /dev/sdb1
Laptop has 2 GB of ram.
Hard drives of laptop are not used and not mounted.
Xpup set with screensaver NOT enabled and time=0.
Problem:
If the laptop is left on for 1+ hours without activitiy the connection to the USB Flash sdb1 icon disappears, the time stops.
We can move the mouse and it responds. The keyboard works.
But nothing gets saved when we reboot the computer. It just
shutsdown immediately. This shutdown is equal to pulling the plug. On reboot it asks about a sudden shutdown of Xorg.
Why does the Puppy Drive disappear and time stop?
On reboot we had to reset the time and date. The day was one day ahead and the time was 4 hours behind. We are at USA Pacific time which is -8 GMT and now in Pacific Standard Time.
Thanks for looking at this.
-Bruce and Duane.
A c shell script somewhere is being attempted by bash. Possible clues to where if you do a pfind for *.csh. Check to see if any of these are in some kind of startup folder or associated with the app startup that you experience it in.laserman wrote:When booting up, I get:
-sh: setenv: command not found.
It doesn't seem to affect the overall operation but was noted during boot up.
After booting up, opening the console, I get:
bash: setenv: command not found
Posted for the group and noted VTPUP also received the same error previously.
Best Regards,
John
Re: 431 Final Observations
I'd like to report that enabling SMP solved my slow-mo mouse problem described/reported here: http://murga-linux.com/puppy/viewtopic. ... 1&start=88
I've discovered this due to some coincidental help from the newest Mandriva 2010 which had the same problem after I had "accidentally" disabled SMP in it
I've discovered this due to some coincidental help from the newest Mandriva 2010 which had the same problem after I had "accidentally" disabled SMP in it
Desktop drive-icon pileup with 1024x600 xorg graphics
I'm sure I read some recent messages concerning persistent pile-up of desktop drive icons at low screen resolutions. I have tried to search for the messages but can't find them. Was there a solution?
I am experiencing this on a Samsung N110 web-book with Xorg and a 1024x600 screen running puppy431 from a bootable flash USB. Whenever I insert additional USB Flash-drives or an external USB DVD RW the icons pile up at the bottom left of the screen. The icons can be drag/dropped to new locations but the problem recurs if the drives are removed then reinserted.
PS I have to use Xorg because Xvesa gives me a reverse colour graphic display.
I am experiencing this on a Samsung N110 web-book with Xorg and a 1024x600 screen running puppy431 from a bootable flash USB. Whenever I insert additional USB Flash-drives or an external USB DVD RW the icons pile up at the bottom left of the screen. The icons can be drag/dropped to new locations but the problem recurs if the drives are removed then reinserted.
PS I have to use Xorg because Xvesa gives me a reverse colour graphic display.
--- quad booting Slacko57NPAE, Slacko56NPAE, Slacko55PAE (with OO4, devx, Gimp) & WXP on DELL Dimension 2400 PC & DELL Latitude 630 Laptop using grub.
---USB-Flash booting same on Samsung N110 WXP Netbook and Lenovo q100 WXP netPC.
---USB-Flash booting same on Samsung N110 WXP Netbook and Lenovo q100 WXP netPC.
I boot my frugal Puppy with Grub.
I try telling Puppy to not load the sfs file into RAM (pfix=noram), but it does so regardless.
Could this be fixed somehow?
Also, I have my frugal pup installed on sda6, and just recently, I've copied it to sda2 and found that, inspite of being told otherwise, pup decided to load itself from there at the next boot.
Out of curiosity, I've also copied it to sda1, and sure enough, it would load itself from there next.
Renaming the folder on sda1/2 helped against this, but I'm not sure is Puppy supposed to be doing this when being frugal-installed on a HDD?
I try telling Puppy to not load the sfs file into RAM (pfix=noram), but it does so regardless.
Could this be fixed somehow?
Also, I have my frugal pup installed on sda6, and just recently, I've copied it to sda2 and found that, inspite of being told otherwise, pup decided to load itself from there at the next boot.
Out of curiosity, I've also copied it to sda1, and sure enough, it would load itself from there next.
Renaming the folder on sda1/2 helped against this, but I'm not sure is Puppy supposed to be doing this when being frugal-installed on a HDD?
ICPUG,
I copied the whole puppy folder as it is, in order to use it separately and only when I explicitly want to boot it.
For example, I have 2 entries in Grub's menu.lst, each for its own pup that are each on its own partition, but if their folder names happen to be the same, whichever entry I boot, the kernel does load from where it's supposed to, but then proceeds to loading the sfs (and the save file) from the first partition of the two (or three).
I'm only pointing this out in case it happens to be "undesired behaviour", and also so that more people will know what the problem is and how to solve it if it happens to someone else.
I copied the whole puppy folder as it is, in order to use it separately and only when I explicitly want to boot it.
For example, I have 2 entries in Grub's menu.lst, each for its own pup that are each on its own partition, but if their folder names happen to be the same, whichever entry I boot, the kernel does load from where it's supposed to, but then proceeds to loading the sfs (and the save file) from the first partition of the two (or three).
I'm only pointing this out in case it happens to be "undesired behaviour", and also so that more people will know what the problem is and how to solve it if it happens to someone else.
puppy 4.31 readmefiles.htm errors
Change pup-430 to 431 and puppy 3.x to 4.31? The file names for download in special puppies are correct.
Re: Desktop drive-icon pileup with 1024x600 xorg graphics
Here is the url you were looking for:r__hughes wrote:I'm sure I read some recent messages concerning persistent pile-up of desktop drive icons at low screen resolutions. I have tried to search for the messages but can't find them. Was there a solution?
I am experiencing this on a Samsung N110 web-book with Xorg and a 1024x600 screen running puppy431 from a bootable flash USB. Whenever I insert additional USB Flash-drives or an external USB DVD RW the icons pile up at the bottom left of the screen. The icons can be drag/dropped to new locations but the problem recurs if the drives are removed then reinserted.
PS I have to use Xorg because Xvesa gives me a reverse colour graphic display.
http://www.murga-linux.com/puppy/viewto ... &start=256
It´s the solution working in dpup and 214X, thanks to MinHundHettePerro
Greetings,
clarf
"puppy pfix=fsck" still does nothing.
Pizzasgood researched this problem, apparently a line commented out in init.gz that shouldn't be. See this thread:
http://www.murga-linux.com/puppy/viewtopic.php?t=41918
The commented line is:
Uncomment it, and it works fine, according to Pizzasgood.
Hope we can get this fixed in 4.3.2, heh. It's a bear to deal with manually, especially for noobs who won't know about that thread.
Pizzasgood researched this problem, apparently a line commented out in init.gz that shouldn't be. See this thread:
http://www.murga-linux.com/puppy/viewtopic.php?t=41918
The commented line is:
Code: Select all
#fsck_func loop1 ext2 $PUPSAVEFILE #v3.01. no, removed, takes ages, and won't mount afterward. Hope we can get this fixed in 4.3.2, heh. It's a bear to deal with manually, especially for noobs who won't know about that thread.
Pburn problem with audio CDs
This is a really queer bug, although nothing similar comes up searching in this thread. Stumbled in it this morning, when trying to burn an audio CD with Puppy 4.3.1's PBurn.
On the disc, all tracks are cut to about 1,5 secs playing time - but there's much worse: even all source *.wav files in the list are crippled to 544 KB each!!! Luckily I had another copy of the originals...
It appears that the crippling happens at the very start of the burning command. During the burn, this message appears for every track:
>WARNING: padding to secsize
>burning 144k of pad data
which I don't remember having seen in previous versions.
Tried booting Puppy 4.3.1 off another CD, with pfix=ram; even tried burning a different kind of CD -- same thing. The ISO's MD5 checks OK; all else seems to work regularly on this box (AMD Athlon 1800, 512 MB Ram, XVesa 1280x1024). PBurn had plenty of space for temporary files (>5GB) and a hardware defect seems unlikely as the ISO was burned successfully.
Although it's not a frequent job here, several audio CDs have been burnt with PBurn in previous Puppy versions on this same machine without problems. I'll try again with one of them to see if they still work right, and with 4.3.1 on other boxes: this behavior is too strange.
On the disc, all tracks are cut to about 1,5 secs playing time - but there's much worse: even all source *.wav files in the list are crippled to 544 KB each!!! Luckily I had another copy of the originals...
It appears that the crippling happens at the very start of the burning command. During the burn, this message appears for every track:
>WARNING: padding to secsize
>burning 144k of pad data
which I don't remember having seen in previous versions.
Tried booting Puppy 4.3.1 off another CD, with pfix=ram; even tried burning a different kind of CD -- same thing. The ISO's MD5 checks OK; all else seems to work regularly on this box (AMD Athlon 1800, 512 MB Ram, XVesa 1280x1024). PBurn had plenty of space for temporary files (>5GB) and a hardware defect seems unlikely as the ISO was burned successfully.
Although it's not a frequent job here, several audio CDs have been burnt with PBurn in previous Puppy versions on this same machine without problems. I'll try again with one of them to see if they still work right, and with 4.3.1 on other boxes: this behavior is too strange.
Dawg
I understand what you are doing now.
Use of the PDEV1 kernel parameter should solve this problem - if it doesn't then it is undesirable behaviour!
PMEDIA - tells it which type of drive
PDEV1 - tells it which partition
PSUBDIR - tells it which directory (only 1 level deep).
The PDEV1 should act as a filter to eradicate from the search list entries for the puppies from other partitions.
I understand what you are doing now.
Use of the PDEV1 kernel parameter should solve this problem - if it doesn't then it is undesirable behaviour!
PMEDIA - tells it which type of drive
PDEV1 - tells it which partition
PSUBDIR - tells it which directory (only 1 level deep).
The PDEV1 should act as a filter to eradicate from the search list entries for the puppies from other partitions.