(old)Puppy Linux Discussion Forum

Posted: **Mon 01 Jul 2013, 01:59**

[quote="Q5sys"]
You might have to move just the /spot/ directory alone and symlink it.
[/quit]

No luck....and when I tell the system to reboot....it just sits there til the cows come home and then I have to do a hard reboot.

And so, like Barry's recent stuff this OS simply doesn't work for me. Shame, as it looked impressive.

Posted: **Mon 01 Jul 2013, 02:25**

Q5sys wrote:
edoc wrote:OK, y'all strategically-ignored me long enough so that I fumbled my way to the right Menu and figured out the right (don't use Radeon driver) modifier.

Now I have to figure out in Personalize Settings z.1.8.4-L64 what to do about the driver.

The Vesa it used by default looks fine to me but I am guessing may cause problems in certain apps?
lol. I havent pulled down the new ISO yet, so i havent had time to mess around with the UEFI stuff yet.
So you did get your system up and running?

Yes, it's beautiful ... so far so good ... just need to resolve the graphics thing right now.

Posted: **Mon 01 Jul 2013, 02:32**

Ran xorgwizard and it recommended Vesa as best I could sort out - Probe failed to a command line prompt - xorgwizard-puppy just cycled back to the menu.

There is an Openbox Syntax error pup-up noting XML syntax errors.

The last error seen was in file "root/.config/openbox/menu.xml" line 136 with message Extra content at the end of the document

Posted: **Mon 01 Jul 2013, 02:34**

Will Grub work with 602-B2 where UEFI is involved?

Posted: **Mon 01 Jul 2013, 03:11**

One of the primary reason this "freaking" thing comes up< as it was referenced by an earlier member, is that there is no standard acceptable method prescribed when distros are released on what should be done to help both articulate, understand, report, and get feedback on video issues. Some documentation that accompany's the distro probably is needed for this kind of problem.

TaZoC has done a really creditable job in documenting much of what we can encounter. But this specific problem is not one of those

This kind of problem along with the frustrations of some are a little disheartening when frustrations run high causing un-intended responses.

to provide better information lets look at the facts.

this site shows what is supported by the driver ===> http://www.nvidia.com/object/linux-display-amd64-319.23-driver.html
My system's Hardinfo reports shows the GTS250 adapter identified by the system hardware as shown below
The message still surfaces for a supported adapter

So, am I to believe my system's hardware report, the nVidia site's report, or the message generated by the system?

Please refrain from flying off the handle again. Replies and behavior as such is not good for any of this community. Although, I'm sure you're trying to help by your emphasis. But, in this case, the system information gives a picture different than what you describe.

If there are other tools that development would like me/others to use to give a better view of what's going on, ask and it will be given/shared.

The NOUVEAU driver is working OK. I thought that possibly the nVidea driver would add video responsiveness or reduce CPU loadings. So there must be a mismatch in system reporting or as the message indicates something is missing somewhere. This is why I posted my findings for review.

If i am mis-interpreting the information I am looking at, please guide me appropriately so that I and others have a reference for future use. And, if there is other system information that would bear more light to help, please advise.

Any ideas on this problem would be appreciated or any information that we can provide to help, expect that it will be given.

Here to help

Posted: **Mon 01 Jul 2013, 03:18**

I moved my Lighthouse64 602 install to another pc (SDHC card plugged
into a usb card reader) and booted it up.
I had to recompile the proprietary Nvidia driver and set to wireless
up again but that only took a few minutes.

video-info-glx 1.5.3 Sun 30 Jun 2013 on Lighthouse64 602 Linux 3.8.7 x86_64
0.0 VGA compatible controller: nVidia Corporation Device 1082 (rev a1)
oem: NVIDIA
product: GF110 Board - 12630002 Chip Rev

X Server: Xorg Driver: nvidia
X.Org version: 1.12.3
dimensions: 3840x1080 pixels (1049x292 millimeters)
depth of root window: 24 planes

direct rendering: Yes
server glx vendor string: NVIDIA Corporation
server glx version string: 1.4
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GTX 560 Ti/PCIe/SSE2
OpenGL version string: 4.3.0 NVIDIA 319.32

Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz
Core 0: @1600 1: @1600 2: @1600 3: @1600 4: @1600 5: @1600 6: @1600
7: @1600 MHz

It's working well here too.

Posted: **Mon 01 Jul 2013, 04:25**

Found one very small flea affecting lid suspend on the Fujitsu s6520 laptop I reported on earlier.
Suspend occurred correctly on lid closure, wireless shut down ok. On reopening, x restarted, network enabled, frisbee acquired a lease... and then it immediately suspended again.

Cause is, in /etc/acpi/events,lid calls /etc/acpi/action/suspend.sh for any lid event, open or close. Could put a test in it so only a closure calls suspend.sh but the appropiate test already exists in lines 4 through 7 of /etc/acpi/actions/suspend.sh. I uncommented those lines as below and changed the comment line slightly to better reflect what it does

Code: Select all

# do not suspend on lid open event
if [ "$(cat /proc/acpi/button/lid/*/state | grep open)" != "" ] ; then
exit
fi

and the false resuspend is gone.

I also Installed lxappearance from the repository mostly to switch icon themes. Works fine. I just start it in a terminal for now. Both tint2 and conky are set up and working just fine, but by resetting the bottom margin to 0 pixels in the openbox config, the Lxpanel now has full transparency and I'm happy enuf with it.

Posted: **Mon 01 Jul 2013, 07:03**

couple weeks ago I posted a problem that I'm having with a HP laptop. I aasked devlopers to hold off as the latest LH64 was eminent. Now that LH64-602 is here, i just tested and find same issues as reported there ===> http://murga-linux.com/puppy/viewtopic.php?p=708924#708924

The laptop's use of the Wifi works without issue in Vista, but, in Linux, it does NOT, even with the newer kernel. All symptoms are exactly as they were before.

Questions

Is there a LH64/FATDOG document that might lead to either resolution or recommendation?
Is there anything development would like me to present which could provide insights to resolution?

Thanks for any guidance in an effort to resolve

Posted: **Mon 01 Jul 2013, 11:37**

gcmartin wrote:
Please refrain from flying off the handle again. Replies and behavior as such is not good for any of this community. Although, I'm sure you're trying to help by your emphasis. But, in this case, the system information gives a picture different than what you describe.

If i am mis-interpreting the information I am looking at, please guide me appropriately so that I and others have a reference for future use. And, if there is other system information that would bear more light to help, please advise.

Any ideas on this problem would be appreciated or any information that we can provide to help, expect that it will be given.

Here to help

Gcmartin,
Please confirm
m the exact card you have. Your first post stated you had the GTX 250. Now you are reporting that you have the GLS 250. Those are difference cards. One I spported by Nvidias driver and one is not. Accurate information is needed for support.
If you have the gls250, then there is a support issue we need to look into; however if you have the gtx 250, as you first reported, there is little we can so.

.

Posted: **Mon 01 Jul 2013, 14:07**

The images from the system shows what the system has on its video peripheral. That information is the same when "video...glx" is run in a terminal/console.

Maybe, there is a better way to approach this, from a developer's perspective (if there are other ways, maybe it can also be posted).

For nVidia
Maybe an approach can be documented which takes any user from the normal Nouveau driver to, say, the "nv" driver, then assuming that worked, a user can be advise to attempt installation of the PET that brings in the latest from driver for adapter functions. If you agree, then, so that the community has your approach documented, it could serve as a guide for all of us in the community. And, when users report, they could be steered to the supporting documentation for guidance.

This would have the added benefit of reducing the frustration level, too.

What say you?

Posted: **Mon 01 Jul 2013, 14:13**

Installed to usb.

Excellent work, can't wait to try it out but still stuck with my usual problem i.e: broadcom wl driver.

Maybe peebee or someone might oblige.

I have the multipet but need a delta for the kernel.

Thanks.
irishrm.

Posted: **Mon 01 Jul 2013, 16:37**

Hi TazOC,

Working great, including all software tested on my hardware.

Thanks for separating out the Wine sfs. It's much simpler to use now.

One problem: With 5KDE-4.6.5-x86_64-H.sfs and Gvfs-1.12.3-x86_64-3.sfs loaded, I am still unable to switch to the KDE window manager (WM). When WM tries to start it shows an error: "kstartupconfig4 does not exist or fails. The error code is 127." Clicking on OK provides the shutdown screen and allows me to switch to another WM. All other WM work fine.

Thanks again for another super distribution, you continue to outdo yourself.

Jim

@gcmartin

gcmartin wrote:. . .For nVidia
Maybe an approach can be documented which takes any user from the normal Nouveau driver to, say, the "nv" driver, then assuming that worked, a user can be advise to attempt installation of the PET that brings in the latest from driver for adapter functions. If you agree, then, so that the community has your approach documented, it could serve as a guide for all of us in the community. And, when users report, they could be steered to the supporting documentation for guidance. . . .

For me, it's better to include guidance in the release notes. No need to be directed elsewhere. This information in the release notes worked for me:
"For Nvidia press 'N' at the boot menu for the 7th entry or use blacklist=nouveau in Grub
If you experience a blank screen, problems with console or reboot, choose 'For severe video problems - disable KMS, use wizard' at the boot menu, (LiveCD) or add this to the kernel line in your Grub config: nomodeset pfix=vesa,ram"

Hardware: NVIDIA Geforce 8400 GS 512MB, Asus P6T Motherboard, Intel core i7-920 (8MB Cache, 2.66 GHz), DDR3 3GB 1333MHz ram, Pioneer DVR-2910 DVD+-RW Dual Layer Burner, Realtek ALC1200 Audio, HP Photosmart C5280 All-in-One

Posted: **Mon 01 Jul 2013, 16:59**

Grub4DosConfigConfig - Error

Boot flag not found on sda.

How should I proceed, please?

Posted: **Mon 01 Jul 2013, 17:03**

Q5sys wrote:I cant wait to test it out!

Are any of the SFS packages from 601 the same in the 602 directory? I dont want to eat your bandwidth downloading new SFS files if there has been no change.

The only sizable SFS that has not been updated is NLS_KDE-4.6.5.sfs (KDE localization for non-en_US locales.) You can sort the listing by date. Anything dated prior to Mar 30, 2013 is the same as LH64-601. 2 exceptions: Udisks2 and Xfce4 are the same, but I rebuilt them with higher compression (larger blksize) to keep the Mariner ISO under 700MiB.

Sylvander wrote:a. It seems it won't be possible to install applications that are important to me.
e.g. "SaveMyModem"=smm [or some alternative similar to Mailwasher], Xfe.

I looked in PPM and couldn't find either. For Xfe,
Fatdog64 has these, however I'm assuming that you've already tried SpaceFM in the Filesystem menu:
http://distro.ibiblio.org/fatdog/pets/6 ... 45-600.pet (dependency)
http://distro.ibiblio.org/fatdog/pets/6 ... .5-600.pet

For SaveMyModem maybe you can compile it from source:
http://www.lhpup.org/help/faqs/pet-package.html

b. Would it be possible to edit the ISO to change to pmedia=ataflash, so that a pupsave on an internal HDD is treated as though on a Flash Drive?
I normally do this so as to be able to choose whether/when "to save or not to save" during the session and at shutdown/reboot.
I'd tr

Please try the Lighthouse 64 boot option
pfix=noautosave
Enter it on the kernel line. From the LiveCD boot menu, press <tab> (BIOS firmware) or 'e' (UEFI firmware) to edit the menu selection.
noautosave is designed to prevent any automatic save file updates; manual or shutdown (after prompting) only.
-TaZoC

Posted: **Mon 01 Jul 2013, 17:13**

edoc wrote:
Grub4DosConfigConfig - Error

Boot flag not found on sda.
How should I proceed, please?

open gparted program and right click on the partition where you installed lighthouse; should be SDA1; this will open manage flags menu. select boot as the flag for that partition, run grubfordos again then reboot. should fix your issue.

Posted: **Mon 01 Jul 2013, 17:14**

edoc wrote:
Grub4DosConfigConfig - Error

Boot flag not found on sda.
How should I proceed, please?

Grub4Dos is not compatible with UEFI/GPT hardware. I'm thinking about removing it from LH64. Please use the Lighthouse Universal Installer in the Setup menu, which has been updated to detect UEFI/GPT and prepare a USB stick or point to an (advanced) guide for GPT hard drive installation.

-TaZoC

Posted: **Mon 01 Jul 2013, 18:00**

tazoc wrote:
edoc wrote:
Grub4DosConfigConfig - Error

Boot flag not found on sda.
How should I proceed, please?
Grub4Dos is not compatible with UEFI/GPT hardware. I'm thinking about removing it from LH64. Please use the Lighthouse Universal Installer in the Setup menu, which has been updated to detect UEFI/GPT and prepare a USB stick or point to an (advanced) guide for GPT hard drive installation.

-TaZoC

Is "GPT hard drive installation" similar to Frugal?

Is Lighthouse Universal Installer the same as PupControl Puppy Universal Installer?

Posted: **Mon 01 Jul 2013, 18:52**

edoc wrote:Is "GPT hard drive installation" similar to Frugal?

Is Lighthouse Universal Installer the same as PupControl Puppy Universal Installer?

Hi edoc,

Yes and yes. I suspect your hard disk has GPT even though you've installed Windows 7. If so, a button in the new Universal Installer will open something like this in /usr/share/doc/faqs:
http://www.lhpup.org/help/faqs/uefi-harddrive.html

But I highly recommend using the 'Make UEFI Flash drive' button first. That is much easier and should work on any 64-bit computer that can boot from USB flash. (By pressing and holding a specific key like <Esc> or <F8> when the PC first starts to, bring up the 'BBS' BIOS Boot Selection menu.)

Here is some info on GPT disk partition tables:
http://en.wikipedia.org/wiki/GPT_Disk

Posted: **Mon 01 Jul 2013, 19:02**

irishrm wrote:Installed to usb.

Excellent work, can't wait to try it out but still stuck with my usual problem i.e: broadcom wl driver.

Maybe peebee or someone might oblige.

I have the multipet but need a delta for the kernel.

Thanks.
irishrm.

What is the multipet?

Please try booting without a savefile and enable the proprietary Broadcom driver by using menu -> Setup -> Fatdog64 Service Manager and start the 'BC-wl' service. I can't verify that it works as my WiFi adapters are Realtek and Atheros. If not, please type this in a terminal and post the o/p:

Code: Select all

modprobe lib80211
modprobe cfg80211
insmod /usr/share/broadcom/wl.ko

Thanks,
TaZoC

Posted: **Mon 01 Jul 2013, 19:16**

Mariner working great on a P4 32bit machine with 2.5gb ram, only thing odd is when installing a pet via ppm a password is needed , which is "woofwoof".

(old)Puppy Linux Discussion Forum

Lighthouse 64 602 Beta2 with GIMP-2.8.4 (6-29-2013)

Re: Pidgin Logs

Vesa for Radeon?

Grub OK to dual boot Win7 & 602-B2?

Lighthouse 64 602 Beta2 with GIMP-2.8.4

lid suspend

Lighthouse 64 602 beta2

Grub4DosConfigConfig

Re: Grub4DosConfigConfig

Re: Grub4DosConfigConfig