Dpup Wheezy. Woof-CE built debian wheezy 7.2 packages used

[anikin]

Hi pemasu,
fresh, first run.
Boot is OK, quick setup ... and I notice that sda1 is mounted. That's exclusively winxp territory and it's never been intruded (mounted on boot) before. All my puppies are on sdc1. Once the quick setup is done, sda1 magically unmounts itself.

Thank you very much for ppower. I'd like two things with it: 1) remove turbo mode from source. 2) compile and install it in another puppy (with acpi scripts from wheezy). I almost figured out how the turbo mode is invoked.

[pemasu]

Boot is OK, quick setup ... and I notice that sda1 is mounted.

I believe it is due to new fail safe graphics feature. /usr/sbin/quickset has new feature to save pupdesk.flg file, starting from this row:

Code: Select all

 #130509 need to create pupdesk.flg before bring up gui window, with $XDRIVERSUCCESS stored in it, for xorgwizard-cli...

It might be that it creates that file somewhere from where to access it if hard reboot is needed. So the failed boot to desktop will be registered and at next boot the failsafe xorgwizard-cli will be launched without booting to the X and you can choose the graphics driver.

[anikin]

Well, I don't mind pupdesk.flg being created in a partition where puppy resides. But I do very much mind my other partitions being sniffed in the process.

[pemasu]

Anikin. you should post about the feature to Barry`s blog.

Here is the snapshot of the desktop when the sda1 is mounted and the failsafe file has been created.

I believe that the failsafe feature is still under progress. Feedback would be noted by Barry K surely.

http://i.imgur.com/xLmN8G7.jpg

[01micko]

Well, I don't mind pupdesk.flg being created in a partition where puppy resides. But I do very much mind my other partitions being sniffed in the process.

I tend to agree. It is a good idea but should ask the user if it's ok to make the file, especially for ntfs/fat. I won't be producing a pup with that enabled.
This is of course just my opinion and I will post to BK's blog.

Cheers

[Billtoo]

Manual frugal install to a 16gb SDHC card running on an Acer desktop
pc.
video-info-glx 1.5.3 Sun 12 May 2013 on Dpup Wheezy 3.5.2.7
Linux 3.5.2-dpup i686
2.0 VGA compatible controller:
Intel Corporation Core Processor Integrated Graphics Controller(rev18)
oem: Intel(R)Ironlake Desktop Graphics Chipset Accelerated VGA BIOS
product:
Intel(R)Ironlake Desktop Graphics Controller Hardware Version 0.0

X Server: Xorg Driver: intel
X.Org version: 1.12.4
dimensions: 1920x1080 pixels (507x285 millimeters)
depth of root window: 24 planes

direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
OpenGL vendor string: Tungsten Graphics, Inc
OpenGL renderer string: Mesa DRI Intel(R) Ironlake Desktop x86/MMX/SSE2
OpenGL version string: 2.1 Mesa 8.0.5

Intel(R) Core(TM) i3 CPU 540 @ 3.07GHz
Core 0: @1200 1: @1200 2: @1200 3: @1200 MHz

# glxgears
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
302 frames in 5.0 seconds = 60.261 FPS
300 frames in 5.0 seconds = 59.999 FPS
300 frames in 5.0 seconds = 59.999 FPS
#
I installed several applications with ppm,
kdegames,vlc,mc,lxterminal,audacious,and more.
No problems at all so far, straight to the desktop on first boot and
everything working.

[anikin]

I believe that the failsafe feature is still under progress. Feedback would be noted by Barry K surely

Barry has already responded to this in his blog: http://bkhome.org/blog2/?viewDetailed=00226 and I'm glad he decided to re-implement pupdesk.flg in a different way. As I'm not registered there, I will briefly quote Barry and respectfully disagree with him on this account:

Note also, pupdesk.flg only gets created/removed in PUPMODE=5. So it doesn't happen after installation, nor in full HD installation. In other words, it is a "one off" thing.
...to object to that is really being paranoid.

I have chosen to completely abandon the save file, which means my puppies will always be running in pupmode 5. That's exactly my "modus operandi", I'm condemned to it. And don't see the issue as a "one off" happening. As to being paranoid ... I'd rather be safe than sorry.

[pemasu]

'pupdesk.flg' redesigned

http://bkhome.org/blog2/?viewDetailed=00238

When I get confirmation, that the revived method works, I will download new woof and update Dpup Wheezy to use it. There has been a lot other woof fixes due to frenzy Precise Puppy development.

[don570]

I compiled a Wacom tablet driver for latest Wheezy

http://www.murga-linux.com/puppy/viewto ... 362#703362


________________________________________________

[don570]

I compiled Gimp2.8.4 in Wheezy and dicovered that the app would
run in Precise, Raring and Slacko as well, but it was substantially bigger.

The opposite isn't true i.e. an app compiled in Precise won't run in Wheezy.

http://www.murga-linux.com/puppy/viewto ... 374#703374

__________________________________________

[pemasu]

Thanks don570. Your gimp pet and sfs needed some finetuning. Some missing libs which I add. Also that wheezy compiled but precise named sfs had older version of gimp libs inside. You should look at it.

All above has been uploaded to the repo after finetuning.

Thanks.

[don570]

Should /usr/bin/strippkg be in devx package?

________________________________________

[pemasu]

Yep. I have moved strippkg and splitpkg to the devx sfs now. Thanks.

[anikin]

Posted on 14 May 2013, 8:56 by BarryK
Re pupdesk.flg alternatives
I was thinking that if the user enters the boot parameters:

puppy pfix=ram
or
puppy pfix=nox

Then 'pupdesk.flg' will not be created, ie that mechanism will be disabled.

That would be a compromise. So, if someone needs to do repair/recovery off a HD and don't want to write anything to it, then those options will do it.

Such a compromise would perfectly fit not only my "saveless" puppy layout. Think also of all those who remaster their stock releases into kiosk/appliance/embedded puppies.

[musher0]

Hello, pemasu.

I tried 3.5.2.7 version and saw no visible changes, except for the more complex/complicated xorgwizard... One positive aspect: update of my pup_save file was a cinch.

That said, following your lead in a message above, I removed the diagnostics "set -xe" commands manually in some /etc scripts in 3.5.2.5, and that produced satisfactory results in its xerrs.log.

So, I'm sticking with WheezyPup 3.5.3.5 until more substantial changes are made.

Best regards.

musher0

[pemasu]

Next update will be using the woof2 with settled version of xorgwizard and the failsafe property included or declined. There is now choice when you woof the build. Also there will be application updates. And more adaptation to new hardcoded xft.dpi 96. Nothing fancy because there should not be much need for them. The Wheezy debian base is quite ok atm. Finetuning mostly.

[vicmz]

OpenboxPlus 1.5 with Lxpanel task and dock bars, wider GTK theme collection including GTK engines, and more:

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

[Satori]

I've been using the updated Dpup Weezy and found some questionable behaviors...

Using a micro-sdhc 32gb adapter connected to a dual port usb 3.0 expressbus adaptor in my laptop, it usually is not picked
up until I connect another flash drive into the second usb port of that adaptor. But a micro-sdhc of 16gb is immediately found.

The same 32gb usb adaptor works in the laptops 2.0 usb ports, tho.

FatDog64 has no problems finding the 32gb usb drive, so is this a kernel difference problem.

-----

Your GTK-youtube-viewer precise installedl properly and works fine when the video is played in window mode.

When played in full screen mode, however, the video constantly flashes with wide bands of video on screen while playing
the video, as tho every other frame is out of synch.

Google Chrome plays youtube in full screen with no problems.

I'm using NVidia's latest driver, 319.17, on the laptop's NVS M140 (aka 8400GT), so is this a problem with the driver or the kernel.

I'm not using the devx SFS package, but will test with that later.

------

When running multiple OpenGL applications and displaying them on screen simulatinously, the X server sometimes
will constantly flash the desktop with a blank screen and then hang. The power button performs a shutdown but the screen
remains blank until a full reboot.

Also when running the OpenGL app, the Network Status window will extend from top to the bottom of the screen, when
normally it's a simple box.

I'm not sure if it's a thermal gpu problem, or the new driver (NVidia 310 had no problems), or kernel 3.5
since kernel 3.6 also didn't have this problem.

------

Upgrade of the savefile from 3.5.6 to 3.5.7 when well, tho I do miss the old Desktop Custom Icons restore utility since
I customize the desktop to my own needs.

------

I have two identical Dell D830 (ebay cheap!) and both exhibit the above problems.

Thank you for the temptray app, it's really a neccessity for laptops.

Ah well... more testing, but overall it looks promising as a stable distro.

--------

More Testing...

When resizing the GTK-Youtube-Viewer video window, then the entire desktop also exhibits the flashing video bands.
Restoring the window to it's original size clears up the problem, this was performed while having the devx SFS file loaded.

Resizing a GNOME MPlayer video window when playing a DVD, has no problems.

[pemasu]

Satori. I believe most of your problems is partly due to kernel.
I have debian mplayer included. Gnome-mplayer is my compile, but it is mostly graphical shell for mplayer.

I suppose that newer kernel would help your problems, at least some of them probably would vanish.

Of course there can incompatibilities with your nvidia proprietary driver also.

Micro-sdhc adapter problem would be mostly due to kernel.

[Eyes-Only]

Hi pemasu,

I'm sure that somewhere in these 25 pages worth of posts someone must have reported this by now, I just haven't had the time to read through the entire 25 pages - nor even skim them ( my apologies kind sir! ) - but after installing Dpup Wheezy to my hard drive in a full install I found that I was unable to do a package update of Puppy's Package Manager.

My machine is an old Dell Optiplex with 1.5gigs of RAM, 2.5gigs swap, 2.8gig dual-core pentium processor ( which can clock to 3.2 or 3.4gig I believe the stats said? ), with a 150gig or so hard drive... all on a 50meg wireless net connection.

So when I press the "update" button to update the offered packages in PPM I get the CLI running down through its choices of debian/puppy repos and respectively press the "enter" key... until right at the point where the programme should then parse the downloaded files into a format which the PPM is able to "read" - and that's where the CLI abruptly quits on me without an explanation or software files update, nor did I have any hints as to what may have happened in the xerrs.log under /tmp.

Mystifying indeed!

Unfortunately I'm unable to help any further than this as the partition has since been wiped for the next test distro. But I thought I should at least report this finding. Other than this one fault Dpup Wheezy is excellent. Had this problem not have been such a show-stopper for me I surely would've enjoyed working further with Dpup! Perhaps later when this is corrected?

Good luck and thanks pemasu for everything that you do in the advancement of our favourite distro!

Cheers/Amicalement,

Eyes-Only
"L'Peau-Rouge d'Acadie"