(old)Puppy Linux Discussion Forum

Hey Rodney Byne,

I replied to your message about openvpn, but I hit "new topic" instead of "post reply"! The message went here: http://murga-linux.com/puppy/viewtopic.php?t=92859

Regards,

eowens2

to Country Bumkin :

Make sure you install from precise Puppy 5.7.1 i.e. run the script
while in Precise Puppy 5.7.1

You will experience strange problems if you do not.
___________________________________________________

To don570..

The use of a Puppy distro appears to be necessary, despite the release notes offering this advice..

and be running a very recent Linux distribution (that understands f2fs

and

for example with Ubuntu you might need to install 'mtools', 'syslinux' and 'f2fs-tools' -- if the latter is not in the repo, then the distro is too old!)

from http://distro.ibiblio.org/quirky/quirky ... ky-6.x.htm

Regards CB

Country Bumkin wrote:and be running a very recent Linux distribution

That's odd

In a previous install note Barry clearly recommended
Precise 5.7.1. He seems to have changed the wording
in his install notes.
_________________________________________________

Yes, 5.7.1 was the clearly the recommended choice. I guess as newer puppies came out, he changed the wording. I've been using the 5.7.1 for f2fs without any noticeable issues.

Best,

Slavvo67

Request for understanding
I must ask this question for some understanding. If the process for 8GB stick creation merely uses "xz" utility for getting to the bootable full-install on USB, WHY do I need to have any system that has "f2fs"? Reason: "xz" decompression step uses "dd" comannd-type approach to stream the datablocks needed to the USB.-in fact, the process to create the full-install doesn't care what's on the USB stick when it is run. "xz" is going to over-write whatever exist in the first 8GB on that USB.Currently, I trying to understand the need for Precise 5.7.1 to get to the running full-install on the USB stick using "xz".

Help if you can shed some light on this.

I think, you started the process of understanding from the wrong end - xz, that is.
Read this first:http://en.wikipedia.org/wiki/SquashFS

Can I suggest reading Barry's Blog and search by content for f2fs?

I hope this helps.

http://bkhome.org/news/


Regards,

Slavvo67

I did 3 Quirky Tahr 6.0.5 installs today, 1 16gb flashdrive, 1 16gb
SDHC card, and 1 8gb flashdrive.
The 16gb installs used the install to drive script and the 8gb used the
# xz --decompress --stdout quirky-6.0.5-8gb.img.xz > /dev/sdX
# sync
method.
All 3 work great.

video-info-glx 1.5.3 Tue 1 Apr 2014 on Quirky Tahr 6.0.5 Linux 3.12.6 i686
2.0 VGA compatible controller: Intel Corporation 82G33/G31 Express Integrated Graphics Controller (rev 02)
oem: Intel(r)Q33/Q35/G33 Graphics Chip Accelerated VGA BIOS
product: Intel(r)Q33/Q35/G33 Graphics Controller Hardware Version 0.0

X Server: Xorg Driver: intel
X.Org version: 1.15.0
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: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) G33 x86/MMX/SSE2
OpenGL version string: 1.4 Mesa 10.0.1

Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GHz
Core 0: @1200 1: @1200 MHz

I wonder if there will be a new release soon?

@gcmartin
Using information from:
http://distro.ibiblio.org/quirky/quirky ... ky-6.x.htm

gcmartin wrote:Request for understanding
I must ask this question for some understanding. If the process for 8GB stick creation merely uses "xz" utility for getting to the bootable full-install on USB,

In this case you are using "Method D: 8GB image"

WHY do I need to have any system that has "f2fs"?

You don't when installing by "Method D"

Reason: "xz" decompression step uses "dd" comannd-type approach to stream the datablocks needed to the USB.-in fact, the process to create the full-install doesn't care what's on the USB stick when it is run. "xz" is going to over-write whatever exist in the first 8GB on that USB.

Code: Select all

xz --decompress --stdout quirky-6.1-8gb.img.xz > /dev/sdb

This command unsquashes the image

"quirky-6.1-8gb.img"

before writing it to the flash-drive. It contains a partition with f2fs-filesystem.

Currently, I trying to understand the need for Precise 5.7.1

... or any distribution having the 'f2fs-tools'.

You only need 'f2fs-tools', when using

"Method A: install to any size Flash drive"

where 'mkfs.f2fs' is needed to make a partition with f2fs-filesystem. Please look into the install-script for "Method A":

'install-quirky-to-drive.sh'

Thanks @Cinclus_Cinclus. You re-enforce the case I wrote about. The post describing those cases could be worded a little more accurately. But, I think, by now, most have gotten the message we share with better clarity.

What I had found is that any system that has "xz" support correctly writes the USB for booting in this distro's case. There was no requirement for f2fs as it only confused things in understanding where that specific case/command was used to generate the USB.

Thanks again for pointing this out.

Running Quirky 6.0.5 from a 32gb usb 3.0 flash drive, pc is a compaq
Presario S6700NX desktop pc.
VIDEO REPORT: Quirky Tahr, version 6.0.5
Chip description:
VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV280 [Radeon 9200 PRO] (rev 01)
Display controller: Advanced Micro Devices, Inc. [AMD/ATI] RV280 [Radeon 9200 PRO] (Secondary) (rev 01)
Requested by /etc/X11/xorg.conf:
Depth (bits, or planes): 24
Modules requested to be loaded: dbe
Modules requested to not be loaded: glx
Drivers requested to be loaded: modesetting
Probing Xorg startup log file (/var/log/Xorg.0.log):
Driver loaded (and currently in use): modesetting
Loaded modules: dbe extmod fb kbd mouse shadow
Actual rendering on monitor:
Resolution: 3840x1080 pixels (1013x285 millimeters)
Depth: 24 planes
Computer
Processor 2x Intel(R) Pentium(R) 4 CPU 2.80GHz
Memory 1553MB (269MB used)

This is an older install that was moved to this pc, updated to 6.0.5,
updated PPM and added Firefox 29.0,libxrandr2_1.4.2-1 and
arandr_0.1.7.1-1

It's working well.

I moved my 32gb usb 3.0 flash drive from the compaq desktop to a
gateway desktop pc in order to use the proprietary nvidia driver.

video-info-glx 1.5.3 Sun 4 May 2014 on Quirky Tahr 6.0.5 Linux 3.12.6 i686
0.0 VGA compatible controller: NVIDIA Corporation GF110 [GeForce GTX 560 Ti OEM] (rev a1)
oem: NVIDIA
product: GF110 Board - 12630002 Chip Rev
X Server: Xorg Driver: nvidia
X.Org version: 1.15.0
dimensions: 3840x1080 pixels (1204x343 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 core profile version string: 4.3.0 NVIDIA 331.67

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

Added xbmc 12.3 from PPM.

just moved a flash drive install to a different machine. quirky tahr 6.5 (four?) connected, booted, did everything well in its new location. new machine had what i thought were hard drive issues, but it's grinding and grumbling with it removed so i guess it's a fan issue or some other moving part...think that's the last remaining one though. anyway, i remember this being a question at some earlier time and, yes, you can move a usb installation of quirky tahr from computer to computer. (in this case, a dell and an asus netbook) and have it go smoothly. all my autostart/automount stuff went correctly, it synced with drop box after having been on a shelf for a couple of weeks...

very nice.

Puppus Dogfellow wrote:just moved a flash drive install to a different machine. ... it [went] smoothly...
very nice.

I agree, moving a flash drive install from PC to PC goes smoothly with QT 6.0.5. It's one of the reasons I like it; using the same configuration on all PCs. I moved the same usb key from/to a dell notebook, two acer notebooks, two hp notebooks, a samsung netbook and even a couple of old desktops. Had zero issues so far.

New installation of Quirky 6.0.5 to a usb 3.0 hard drive running on a Mac mini pc.

video-info-glx 1.5.3 Sat 10 May 2014 on Quirky Tahr 6.0.5 Linux 3.12.6 i686
2.0 VGA compatible controller:
Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
oem: Intel(R) Sandybridge/Ivybridge Graphics Chipset Accelerated VGA BIOS
product: Intel(R) Sandybridge/Ivybridge Graphics Controller Hardware Version 0.0
X Server: Xorg Driver: intel
X.Org version: 1.15.0
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: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Ivybridge Mobile x86/MMX/SSE2
OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.0.1

Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz
Core 0: @1200 1: @1200 2: @1200 3: @1200 MHz

It's working great.

I installed the 3.12.11 kernel pet that BarryK posted in his blog. I was expecting to see the kernel version that uname -a reports change from 3.12.6 to 3.12.11, but it didn't. So how can I make sure that after installing the kernel pet QT effectively runs the new kernel? Or is there something else I need to do to enable the new kernel?

EDIT 1 - It appears that this dotpet is intended for the Woof build system, so I need to build a new image. Back to study... [Forum time now 25 May 2014, 02:05]

EDIT 2 - For deployment: need to replace vmlinuz in the first partition of the USB key image file. [Forum time now 25 May 2014, 04:29]

EDIT 3 - Indeed installing this dotpet and copying one file is enough to boot up kernel 3.12.11 - no need to recompile or use woof2. This dotpet overwrites three files and adds a bunch of new files, so first we're going to make backup copies:

# cp /boot/vmlinuz /boot/vmlinuz.3.12.6
# cp /etc/modules/modules.builtin /etc/modules/modules.builtin.3.12.6
# cp /etc/modules/modules.order /etc/modules/modules.order.3.12.6

Now go ahead and install the dotpet. Finally, if you installed QT on a USB key, copy the new kernel file to your actual boot partition. Shutdown QT and connect the USB key to another puppy. Assuming that /dev/sdb is your USB key:

# mkdir -p /mnt/sdb1 /mnt/sdb2
# mount /dev/sdb1 /mnt/sdb1
# mount /dev/sdb2 /mnt/sdb2

# cp /mnt/usb1/vmlinuz /mnt/usb1/vmlinuz.3.12.6 # backup
# cp /mnt/sdb2/boot/vmlinuz /mnt/sdb1/vmlinuz

Disconnect and reboot QT with this USB key. Check results:
# uname -a # should report 3.12.11
# dmesg | grep -E 'zram|aufs' # should output two lines

Sorry if I'm stating the obvious, but you did reboot before running uname didn't you?

Keef wrote:Sorry if I'm stating the obvious, but you did reboot before running uname didn't you?

Yes, I did.

Hi step,

Before you installed the kernel dotpet had you installed the devx-6.0.5-tahr.pet and the kernel_src-3.12.6-patched.sfs?
The kernel dotpet, will I suspect, at least require the tools in the devx. A reboot after installing those and before installing the kernel dotpet might be a good idea.

The kernel source sfs can be found here: http://www.bkhome.org/sources/kernel-3.12.6/