I just installed 5.03 and everything works out of the box, i am really impressed.
Just the booting time is not that fast as i expected but it`s ok. I can live with that
![Smile :-)](./images/smilies/icon_smile.gif)
That is xload, a very simple applet in the JWM tray. It can be refreshed by clicking Menu | Restart JWM. Here is the config in /root/.jwmrc-tray, near line 30Sylvander wrote:The small window down at bottom right displaying activity or usage or something [red on black background]...
It only displays the bottom 1/3.
If I "Ctrl+Alt+backspace" to drop to a command prompt, then xwin <Enter> to restart the window manager...
Once back at the desktop, the problem is gone until next session.
Code: Select all
<Swallow name="xload" width="32">
xload -nolabel -bg "#888888" -fg red -hl white
</Swallow>
Code: Select all
bash-4.1# xload --help
usage: xload [-options ...]
where options include:
-display dpy X server on which to display
-geometry geom size and location of window
-fn font font to use in label
-scale number minimum number of scale lines
-update seconds interval between updates
-label string annotation text
-bg color background color
-fg color graph color
-hl color scale and text color
-nolabel removes the label from above the chart.
-jumpscroll value number of pixels to scroll on overflow
-remote host remote host to monitor
Code: Select all
<!--<Swallow name="xload" width="32">
xload -nolabel -bg "#888888" -fg red -hl white
</Swallow> -->
Code: Select all
<Swallow name="xload" width="32">
xload -nolabel -bg "gray45" -fg red -hl white
</Swallow>
You're welcome! For shorter boot times you can experiment with disabling the SFS boot prompt and/or copy2ram.Krille wrote:Thanks again for your help.
I just installed 5.03 and everything works out of the box, i am really impressed.
Just the booting time is not that fast as i expected but it`s ok. I can live with that
Good idea. Try this config:Sylvander wrote:The 3 lines of code in my copy of the file read:Knowing this, should I still follow the instructions given?Code: Select all
<Swallow name="xload" width="32"> xload -nolabel -bg "gray45" -fg red -hl white </Swallow>
I've copied this file to a safe location [/03], so I can later restore it if necessary.
Code: Select all
<Swallow name="xload" width="32">
xload -scale 1 -update 4 -nolabel -bg "#7E7070" -fg green -hl "#7E7070"
</Swallow>
It isn't hard. If you installed from the Mariner ISO there are already 6 .sfs files on it. Otherwise browse here or http://lhpup.org/sfs/503 and save one or two into the same folder where your LHPsave file is located, or into /mnt/home. Then click Menu|System|BootManager|Select and configure SFS, move them from the LH side (available) to the RH (selected) side of the window, click OK | OK | Quit and reboot. More information at http://lhpup.org/tips-lhp.htm#sfs A few of them require Mariner 503 and/or JavaRE, as described at the first link above, but most will work fine alone, or with others.I don't know anything about the Mariner SFS.
How do I check on this?
I'd like to be able to use SFS files, but so far haven't done any of that.
Yes it gives me a much better-sized set of messages on boot-up (they fill a single screen).kernel /lhp503G/vmlinuz psubdir=lhp503G pmedia=atahd pdev1=sda6 vga=788 xforcevesa nomodeset video=800x600 nmi_watchdog=0 resume=/dev/sda7 pfix=fbcon,fsck
Hi Barburo,Barburo wrote:Here's the line in question:Yes it gives me a much better-sized set of messages on boot-up (they fill a single screen).kernel /lhp503G/vmlinuz psubdir=lhp503G pmedia=atahd pdev1=sda6 vga=788 xforcevesa nomodeset video=800x600 nmi_watchdog=0 resume=/dev/sda7 pfix=fbcon,fsck
I have integrated intel graphics on this laptop and they display just fine (select "intel" in xorg and choose 1366x768 as screen resolution) but when I use ctrl-alt-backspce to drop to the command line all I see is a blank screen: no command line or messages.
..
How do I get better-sized logon messages and a command line I can see?
WIRELESS: Frisbee seems to work OK - it says that eth0 seems to be missing each time I boot into 503 but it successfully finds my network and connects.
Code: Select all
kernel /lhp503G/vmlinuz psubdir=lhp503G pmedia=atahd pdev1=sda6 video=800x600 pfix=fsck
http://www.lhpup.org/download503.htm#Mariner_SFS Mariner is a combo-pack of apps I find useful, tweaks for Lighthouse and some packages needed by other SFS add-ons.WHAT IS MARINER?
What does it do?
Actually I do understand that from University physics.Sylvander wrote: 5. "Mariner is a combo-pack of apps I find useful, tweaks for Lighthouse and some packages needed by other SFS add-ons"
I'm none the wiser.
That explanation is like: "Heat is an interaction between a system and its surroundings, due solely to the temperature difference between them."
Do you understand that?
It's the official definition of heat given when I was studying Thermo-dynamics.
It's like "rain" being the special name given to water that is in the process of falling from a cloud to the surface of planet Earth.
Hi Jim,Jim1911 wrote:Small problem with Mixer PCM volume slider which does not retain it's setting, it reverts to minimum setting on reboot. This is with KDE desktop, not tested other desktops.
Code: Select all
echo -e '#!/bin/sh\nsleep 5\namixer set PCM 100% unmute' > ~/.kde/Autostart/amixer
chmod 755 ~/.kde/Autostart/amixer
Code: Select all
amixer set PCM,0 100% unmute
Code: Select all
amixer controls
Code: Select all
amixer set PCM Playback Volume 100% unmute
Yes, the extension pack and additions are in /opt/VirtualBox/additionsQ5sys wrote:TazOC,
Does http://www.lhpup.org/sfs/503/VirtualBox-4.0.2-L1.sfs include the Guest additions?
That's a good question. I'm afraid it requires re-mastering the ISO, re-compiling the kernel, or installing GRUB (Menu | Setup | Puppy Universal Installer). I put video=800x600 on the kernel line in the isolinux.cfg file (in the /isolinux folder) of the ISOs. I wonder why sometimes that doesn't work?Sylvander wrote:2. "try typing lhp video=640x480 at the boot menu"
That works, but only for that one time that the command is typed in.
Is there a way to make that permanent?
So there's no need to type it in every time?
I think it means that Sakura doesn't kill smm without asking first. Which is a good idea, in case a process was started from Sakura that you didn't want stopped. So I would stop smm, then close Sakura. Or use another terminal in Lighthouse like lxterminal or rxvt, that doesn't ask before killing processes started from the terminal.Sylvander wrote:I run smm using a console.
And when I close the console...
Instead of it just closing down like in other Puppies [to close BOTH windows]...It asks me "are you sure?", which is a pain. I'd rather it just closed.
4. "in a terminal, type Ctrl+C and/or exit before closing the window"
That works OK, but both need the expense of more time and effort than in other Puppies. [Not good]
I hope that the reply yesterday by Q5sys was helpful. Here is a diagram by Barry Kauler that helped me to visualize the Puppy Architecture:5. "Mariner is a combo-pack of apps I find useful, tweaks for Lighthouse and some packages needed by other SFS add-ons"
I'm none the wiser.
Thank you for trying Lighthouse. Yes, we have observed that bug. I have made several attempts to fix it. Fortunately the simple workaround is to boot with puppy pfix=fsck (or in Lighthouse just hit f at the boot menu) a good idea once in a while, even if the save file is properly sized. (This is listed on <F2> boot options menu and will autorun e2fsck and resize2fs as many other distros do by default.) It is not run by default in LHP or Puppy because ext2/3 file systems can take a long time to run fsck.bwh1969 wrote:I am not sure if this is an issue particular to me or if anyone else sees this.
I went to increase my save file size, and it did increase the actual file size but not the filesystem on the save file. I fixed this running e2fsck then resize2fs on the save file and the save file indicator is showing the appropriate information (as is the command df -h)
Other than that, I am extremely impressed with this!
Your first suggestion worked.tazoc wrote:Hi Jim,Jim1911 wrote:Small problem with Mixer PCM volume slider which does not retain it's setting, it reverts to minimum setting on reboot. This is with KDE desktop, not tested other desktops.
KDE should restore the previous mixer levels when it starts but apparently something is muting the PCM. You might try pasting this into a terminaland restart X. That creates a script in KDE's Autostart folder to force the PCM to 100%. You can then edit /Autostart/amixer with a text editor and change 100% to desired level, e.g., 70%.Code: Select all
echo -e '#!/bin/sh\nsleep 5\namixer set PCM 100% unmute' > ~/.kde/Autostart/amixer chmod 755 ~/.kde/Autostart/amixer