My report on Quirky 6.0
Using the quirky install script I get the following errors
Should I try the dd command using the img file as the input and using /dev/sda10 as the output?
/dev/sda10 is formatted to ext4Just about to erase all files in partition 'sda10'!
Press ENTER to continue:
./write-quirky-to-partition: line 228: busybox: command not found
Erasing contents of sda10...
Writing Quirky6 files to sda10...
vmlinuz...
mount: unknown filesystem type 'vfat'
cp: cannot stat ‘mntpt/vmlinuz’: No such file or directory
umount: mntpt: not mounted
all of Quirky files, please wait...
mount: unknown filesystem type 'f2fs'
cp: cannot stat ‘mntpt/*’: No such file or directory
sed: can't read /mnt/sda10/sbin/init: No such file or directory
sed: can't read /mnt/sda10/etc/rc.d/rc.sysinit: No such file or directory
umount: mntpt: not mounted
umount: /mnt/sda10: not mounted
That's it, done!
Should I try the dd command using the img file as the input and using /dev/sda10 as the output?
Life is too short to spend it in front of a computer
Quick test...
Like all distributions I've tested that use X server 1.14, Quirky 6 on my PC with the Rage 128 card gets unsupported video modes with modesetting; I've only gotten a 800x600 display in vesa.
It works nicely on the other PCs...
It works nicely on the other PCs...
Last edited by session on Tue 17 Dec 2013, 08:28, edited 1 time in total.
[color=green]Primary[/color] - Intel Pentium 4 2.40GHz, 571MB RAM, ATI Radeon 7000. Linux Mint 17 Qiana installed.
[color=blue]Secondary[/color] - Pentium 3 533MHz, 385MB RAM, ATI Rage 128 Pro ULTRA TF. Precise Puppy 5.7.1 Retro full install.
[color=blue]Secondary[/color] - Pentium 3 533MHz, 385MB RAM, ATI Rage 128 Pro ULTRA TF. Precise Puppy 5.7.1 Retro full install.
Install Quirky6.0 on a DOS partition table
Install Quirky6.0 on a DOS partition table
Currently, Quirky6.0 install on a GPT partition table. Because kernal need to find a specified linux rootfs by below boot parameters:
Here the "AA2B8242-B2F6-40CB-AFC3-5C888A55380D" are the Partition unique GUID.
You can use gdisk with the "i" command to show the Partition unique GUID.
Since kernel 3.8 and newer it is possible to use MBR 32-bit UUID, so you can use a MBR partition table as well. Please reference to below web page:
http://wiki.gentoo.org/wiki/GRUB
The PARTUUID refer to an MBR partition using the format SSSSSSSS-PP, where SSSSSSSS is a zero-filled hex representation of the 32-bit "Disk identifier", and PP is a zero-filled hex representation of the 1-based partition number
You can use fdisk to check the MBR 32-bit UUID, it is the "Disk identifier".
In my case, the Disk identifier(MBR 32-bit UUID) is cc709394
If I want to boot the sdc1, then the boot parameters will be:
root=PARTUUID=cc709394-01 rootwait
The -01 mean partition 1.
To install Quirky6.0 on a DOS partition table basically have below step:
1. Prepare a USB flash disk, use fdisk(Gparted) to create at least two(or more) partitions.
One partition for boot loader(syslinux or Grub4Dos), FAT16 file system, size about 16M or more.
The other partition for linux rootfs, f2fs file system, size bigger the 1G.
Please remembered your "Disk identifier"
2. Format the FAT16 file system with mkfs.vfat(eg: mkfs.vfat /dev/sdc1)
Format the f2fs file system with mkfs.f2fs(eg: mkfs.f2fs /dev/sdc2)
Skip this step if you use Gparted.
*3. Mount sdc1 and copy the content of the first partition of Quirky6.0 image to sdc1.
*4. Mount sdc2 and copy the content of the second partition of Quirky6.0 image to sdc2.
5. Install the boot loader, I like syslinux,(eg: syslinux -sf /dev/sdc1)
6. Edit the content of the syslinux.cfg on sdc1, change the
to
Here the SSSSSSSS-PP is your "Disk identifier" and partition number.
7. Finish and ready to boot your Quirky6.0.
Remark: * For step 3 and 4, please see my next post.
As a puppy linux user, we usually have a USB boot disk with puppy linux. Use Gparted to resize your existing partitions and add a f2fs partition, then you could easy play with the Quirky6.0.
Thanks for Barry, he created puppy linux to us.
C.H.Lee
Currently, Quirky6.0 install on a GPT partition table. Because kernal need to find a specified linux rootfs by below boot parameters:
Code: Select all
root=PARTUUID=AA2B8242-B2F6-40CB-AFC3-5C888A55380D rootwait
You can use gdisk with the "i" command to show the Partition unique GUID.
Since kernel 3.8 and newer it is possible to use MBR 32-bit UUID, so you can use a MBR partition table as well. Please reference to below web page:
http://wiki.gentoo.org/wiki/GRUB
The PARTUUID refer to an MBR partition using the format SSSSSSSS-PP, where SSSSSSSS is a zero-filled hex representation of the 32-bit "Disk identifier", and PP is a zero-filled hex representation of the 1-based partition number
You can use fdisk to check the MBR 32-bit UUID, it is the "Disk identifier".
Code: Select all
# fdisk -l /dev/sdc
Disk /dev/sdc: 1047 MB, 1047834112 bytes
33 heads, 61 sectors/track, 1016 cylinders, total 2046551 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xcc709394
Device Boot Start End Blocks Id System
/dev/sdc1 65280 2046000 990360+ 83 Linux
/dev/sdc4 * 32 65279 32624 14 Hidden FAT16 <32M
If I want to boot the sdc1, then the boot parameters will be:
root=PARTUUID=cc709394-01 rootwait
The -01 mean partition 1.
To install Quirky6.0 on a DOS partition table basically have below step:
1. Prepare a USB flash disk, use fdisk(Gparted) to create at least two(or more) partitions.
One partition for boot loader(syslinux or Grub4Dos), FAT16 file system, size about 16M or more.
The other partition for linux rootfs, f2fs file system, size bigger the 1G.
Please remembered your "Disk identifier"
2. Format the FAT16 file system with mkfs.vfat(eg: mkfs.vfat /dev/sdc1)
Format the f2fs file system with mkfs.f2fs(eg: mkfs.f2fs /dev/sdc2)
Skip this step if you use Gparted.
*3. Mount sdc1 and copy the content of the first partition of Quirky6.0 image to sdc1.
*4. Mount sdc2 and copy the content of the second partition of Quirky6.0 image to sdc2.
5. Install the boot loader, I like syslinux,(eg: syslinux -sf /dev/sdc1)
6. Edit the content of the syslinux.cfg on sdc1, change the
Code: Select all
append root=PARTUUID=AA2B8242-B2F6-40CB-AFC3-5C888A55380D rootwait
Code: Select all
append root=PARTUUID=SSSSSSSS-PP rootwait
7. Finish and ready to boot your Quirky6.0.
Remark: * For step 3 and 4, please see my next post.
As a puppy linux user, we usually have a USB boot disk with puppy linux. Use Gparted to resize your existing partitions and add a f2fs partition, then you could easy play with the Quirky6.0.
Thanks for Barry, he created puppy linux to us.
C.H.Lee
Install Quirky6.0 on a 1GB(or more) size USB disk
Install Quirky6.0 on a 1GB(or more) size USB disk
The actual size of Quirky6.0 is below 1GB, so we could install it to a 1GB(2GB,4GB or 16GB) USB flash disk.
Assume you downloaded the Quirky6.0 on /mnt/sdb1/tmp,
your USB disk mounted on /mnt/sdc1 and /mnt/sdc2, like my last post.
1. Decompress Quirky6.0 image:
Then you will have the image file quirky6-6.0-8gb.img
2. Prepare two directory, p1 and p2
3. Check the partition struture:
You will see two partition inside it, like below:
It show that the firt partition start at the 2048 sector, and the second partition start at the 49152 sector.
4. Mount these two partition:
p1 is a FAT16 file system, it have the boot loader and linux kernel.
p2 is a f2fs file system, it is the quirky6.0 linux rootfs.
5. Copy the the boot loader setting and linux kernel to sdc1
6. Copy the quirky6.0 linux rootfs to sdc2
7. Un-mount p1 and p2
8. Finished
You can use same method to install quirky6.0 to you hard disk(ext4fs).
C.H.Lee
The actual size of Quirky6.0 is below 1GB, so we could install it to a 1GB(2GB,4GB or 16GB) USB flash disk.
Assume you downloaded the Quirky6.0 on /mnt/sdb1/tmp,
your USB disk mounted on /mnt/sdc1 and /mnt/sdc2, like my last post.
1. Decompress Quirky6.0 image:
Code: Select all
#xz -d -k -v quirky6-6.0-8gb.img.xz
2. Prepare two directory, p1 and p2
Code: Select all
#mkdir p1
#mkdir p2
Code: Select all
#gdisk -l quirky6-6.0-8gb.img
Code: Select all
Disk quirky6-6.0-8gb.img: 14737408 sectors, 7.0 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): FA7BE6A4-E7E3-42F7-BE1E-12CCBE3F73E2
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 15347678
Partitions will be aligned on 2048-sector boundaries
Total free space is 634813 sectors (310.0 MiB)
Number Start (sector) End (sector) Size Code Name
1 2048 34815 16.0 MiB 0700
2 49152 14729215 7.0 GiB 0700
4. Mount these two partition:
Code: Select all
#mount -t vfat -o loop,offset=$((512*2048)) quirky6-6.0-8gb.img p1
#mount -t f2fs -o loop,offset=$((512*49152)) quirky6-6.0-8gb.img p2
p2 is a f2fs file system, it is the quirky6.0 linux rootfs.
5. Copy the the boot loader setting and linux kernel to sdc1
Code: Select all
#cp -arv p2/* /mnt/sdc1
#sync
Code: Select all
#cp -arv p2/* /mnt/sdc2
#sync
Code: Select all
#umount p1
#umount p2
You can use same method to install quirky6.0 to you hard disk(ext4fs).
C.H.Lee
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
tronkel,tronkel wrote:Using the quirky install script I get the following errors
/dev/sda10 is formatted to ext4Just about to erase all files in partition 'sda10'!
Press ENTER to continue:
./write-quirky-to-partition: line 228: busybox: command not found
Erasing contents of sda10...
Writing Quirky6 files to sda10...
vmlinuz...
mount: unknown filesystem type 'vfat'
cp: cannot stat ‘mntpt/vmlinuz’: No such file or directory
umount: mntpt: not mounted
all of Quirky files, please wait...
mount: unknown filesystem type 'f2fs'
cp: cannot stat ‘mntpt/*’: No such file or directory
sed: can't read /mnt/sda10/sbin/init: No such file or directory
sed: can't read /mnt/sda10/etc/rc.d/rc.sysinit: No such file or directory
umount: mntpt: not mounted
umount: /mnt/sda10: not mounted
That's it, done!
Should I try the dd command using the img file as the input and using /dev/sda10 as the output?
What distro are you using? Does it not have busybox?
Busybox must also have the 'mount' applet.
I have added an extra check into the script, for existence of busybox, also renamed with ".sh":
http://distro.ibiblio.org/quirky/quirky ... rtition.sh
Also, it was discussed earlier this thread, you must run the script in a partition with Linux filesystem, not a vfat f.s. (and have over 8GB free).
The script warns about that now, also.
[url]https://bkhome.org/news/[/url]
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
CHLee wrote:
I am sure that the developers of GPT had good reasons for the design decisions, but I have found it to be a headache. The secondary partition-table at the end of the drive, in particular.
I would love to go back to the old MBR. Thanks to you, I can, and will do. Stay tuned.
Oh, that is fantastic!Since kernel 3.8 and newer it is possible to use MBR 32-bit UUID, so you can use a MBR partition table as well.
I am sure that the developers of GPT had good reasons for the design decisions, but I have found it to be a headache. The secondary partition-table at the end of the drive, in particular.
I would love to go back to the old MBR. Thanks to you, I can, and will do. Stay tuned.
[url]https://bkhome.org/news/[/url]
- technosaurus
- Posts: 4853
- Joined: Mon 19 May 2008, 01:24
- Location: Blue Springs, MO
- Contact:
I know the difference between the blkid UUID, and the various GUID, PARTUUID, but I'll probably criss cross them in this post (they are spatially oriented in my brain, not alphabetically)BarryK wrote:I would love to go back to the old MBR. Thanks to you, I can, and will do. Stay tuned.
With this we could automate the install process to modify the GPT.gdiskManpage wrote:g
Change disk GUID. Each disk has a unique GUID code, which gdisk assigns randomly upon creation of the GPT data structures. You can generate a fresh random GUID or enter one manually with this option
This means that each kernel could have its own pregenerated GUID associated with it and annotated in the builtin command line.
Code: Select all
CONFIG_CMDLINE_BOOL=y
CONFIG_CMDLINE="quiet root=PARTUUID=<ourPregeneratedOne> ...."
further info can be found at:
https://wiki.archlinux.org/index.php/EFISTUB
http://blog.realcomputerguy.com/2012/05 ... oader.html
http://www.ondatechnology.org/wiki/inde ... bootloader
Check out my [url=https://github.com/technosaurus]github repositories[/url]. I may eventually get around to updating my [url=http://bashismal.blogspot.com]blogspot[/url].
syslinux 5.10 in Quirky 6.0 missing mcopy
Code: Select all
# syslinux -i -d /boot/syslinux /dev/sdd4
sh: mcopy: command not found
syslinux: failed to create ldlinux.sys
Hi Barry,
Still no joy with the amended script. I've tried both Puppy Precise 5.6 as well as Debian Wheezy. Both of these have Busybox installed. The target partition is ext4.
The error output is the same as before and the amended script issues no warnings while using Puppy as the install distro.
There is a warning when using Debian Wheezy as the install distro. Even although the image file and the install script exist in the same folder, the install script nevertheless can't see the image file.
The script does manage to copy over the boot folder containing the vimlinuz file - but nothing else. The rest of the files do not get copied. So, the script is failing just at that point. Can't see where the error is.
Still no joy with the amended script. I've tried both Puppy Precise 5.6 as well as Debian Wheezy. Both of these have Busybox installed. The target partition is ext4.
The error output is the same as before and the amended script issues no warnings while using Puppy as the install distro.
There is a warning when using Debian Wheezy as the install distro. Even although the image file and the install script exist in the same folder, the install script nevertheless can't see the image file.
The script does manage to copy over the boot folder containing the vimlinuz file - but nothing else. The rest of the files do not get copied. So, the script is failing just at that point. Can't see where the error is.
Last edited by tronkel on Tue 17 Dec 2013, 13:27, edited 1 time in total.
Life is too short to spend it in front of a computer
My report on Quirky 6.0
I needed to compile several other libs + install qt-482, then the
latest VLC compiled successfully.
I'm liking Quirky 6.0 a lot
latest VLC compiled successfully.
I'm liking Quirky 6.0 a lot
- Attachments
-
- vlc-2.1.2-screen.jpg
- (47.03 KiB) Downloaded 1821 times
Quirky
How to install quirky 6.00 in my hard disk either full or frugal. I am already having several other puppies running in Hard Disk. How to install this quirky.img file in any other partition already available in the hard disk (ext4). Please give the some simple method to install in hard disk.
BarryK is working on a method to do exactly that - easy install an image to an existing partition.
It may be known as Quirky-6.1.
Early Xmas maybe ?
It may be known as Quirky-6.1.
Early Xmas maybe ?
[b]Asus[/b] 701SD. 2gig ram. 8gb SSD. [b]IBM A21m[/b] laptop. 192mb ram. PIII Coppermine proc. [b]X60[/b] T2400 1.8Ghz proc. 2gig ram. 80gb hdd. [b]T41[/b] Pentium M 1400Mhz. 512mb ram.
Quirky
I have also tried to install quirky 6.00 by running write-quirky-to-partition.sh. However, it says Quirky image is not available. ( not able to detect Quirky6.00 image file) Even though it was in same folder where sh file is available. I have limited knowledge in linux and also not having any programming skill.
My report on Quirky 6.0
I moved my SDHC install to my eeePC 701SD netbook.
Summary
Computer
Processor Intel(R) Celeron(R) M processor 900MHz
Memory 505MB (34MB used)
Machine Type Physical machine
Operating System Quirky - 6.0
User Name root (root)
Date/Time Tue 17 Dec 2013 11:00:28 AM EST
Display
Resolution 640x480 pixels
OpenGL Renderer Unknown
X11 Vendor The X.Org Foundation
Audio Devices
Audio Adapter HDA-Intel - HDA Intel
Input Devices
AT Translated Set 2 keyboard
Logitech USB Optical Mouse
SynPS/2 Synaptics TouchPad
Asus EeePC extra buttons
Lid Switch
Sleep Button
Power Button
Power Button
Video Bus
PC Speaker
HDA Digital PCBeep
HDA Intel Headphone
HDA Intel Mic
Atheros Communications Inc. AR242x / AR542x Wireless Network Adapter (PCI-Express) (rev 01)
I didn't try connecting an external monitor yet.
EDIT:
I connected a 17" external monitor, it's working well.
Summary
Computer
Processor Intel(R) Celeron(R) M processor 900MHz
Memory 505MB (34MB used)
Machine Type Physical machine
Operating System Quirky - 6.0
User Name root (root)
Date/Time Tue 17 Dec 2013 11:00:28 AM EST
Display
Resolution 640x480 pixels
OpenGL Renderer Unknown
X11 Vendor The X.Org Foundation
Audio Devices
Audio Adapter HDA-Intel - HDA Intel
Input Devices
AT Translated Set 2 keyboard
Logitech USB Optical Mouse
SynPS/2 Synaptics TouchPad
Asus EeePC extra buttons
Lid Switch
Sleep Button
Power Button
Power Button
Video Bus
PC Speaker
HDA Digital PCBeep
HDA Intel Headphone
HDA Intel Mic
Atheros Communications Inc. AR242x / AR542x Wireless Network Adapter (PCI-Express) (rev 01)
I didn't try connecting an external monitor yet.
EDIT:
I connected a 17" external monitor, it's working well.
- Attachments
-
- eeepc2.jpg
- (68.98 KiB) Downloaded 1593 times
-
- eeepc.jpg
- (80.84 KiB) Downloaded 1637 times
I have been able to use BK's scripts and quirky6-6.0.img.xz to install to a f2fs partition using the full space of the USB 16 GB thumb drive.
I began by using ./write-quirky-image-to-drive, writing quirky onto a 16 GB USB thumb drive, leaving about 7 GB of unused space. Rather than adding a third partition (to the FAT16 and f2fs), I deleted the f2fs partition with the root file system. The FAT partition with the bootloader etc I left intact on the drive.
Then I created (with the Gparted version 0.16.2 included in quirky6) a new f2fs partition of 14.88 GB that mostly filled the thumb drive, leaving a little space at the end for the secondary GUID partition table. (This was done with a second functioning copy of Quirky6).
I then used ./write-quirky-to-partition to put the root file system back on to the f2fs partition. BK made some recommended changes for /etc/rc.d/rc.sysinit: I did not make the change at line 152 "DEV1FS='f2fs'", since the partition is still in a f2fs format, but did the change at about line 80 regarding busybox mount.
The system will still not boot yet, because the file SYSLINUX.CFG has the incorrect partition UUID value, and doesn't know where to find the root file system (it is trying to use the UUID value of the original f2fs partition).
To get the new UUID value, do "./gdisk /dev/sdx" where "x" is the thumb drive in question (in my case ./ gdisk /dev/sdc) which will give some preliminary info, and await furthur commands. Enter "i" for detailed information, and enter "2" for the f2fs partition.
Two GUID values will be reported, but the one we need is the one labled "Partition unique GUID". Copy this value and go to the partition 1 (FAT16 partition) and open SYSLINUX.CFG, go to the line "append root=PARTUUID=" and replace the value there with the one copied from gdisk interrogation of the new f2fs partition. Save SYSLINUX.CFG and the system should be bootable. Mine was!
I repeated the above procedure on a 32 GB USB stick (=> a 29.8 f2fs partition) which worked equally well.
I began by using ./write-quirky-image-to-drive, writing quirky onto a 16 GB USB thumb drive, leaving about 7 GB of unused space. Rather than adding a third partition (to the FAT16 and f2fs), I deleted the f2fs partition with the root file system. The FAT partition with the bootloader etc I left intact on the drive.
Then I created (with the Gparted version 0.16.2 included in quirky6) a new f2fs partition of 14.88 GB that mostly filled the thumb drive, leaving a little space at the end for the secondary GUID partition table. (This was done with a second functioning copy of Quirky6).
I then used ./write-quirky-to-partition to put the root file system back on to the f2fs partition. BK made some recommended changes for /etc/rc.d/rc.sysinit: I did not make the change at line 152 "DEV1FS='f2fs'", since the partition is still in a f2fs format, but did the change at about line 80 regarding busybox mount.
The system will still not boot yet, because the file SYSLINUX.CFG has the incorrect partition UUID value, and doesn't know where to find the root file system (it is trying to use the UUID value of the original f2fs partition).
To get the new UUID value, do "./gdisk /dev/sdx" where "x" is the thumb drive in question (in my case ./ gdisk /dev/sdc) which will give some preliminary info, and await furthur commands. Enter "i" for detailed information, and enter "2" for the f2fs partition.
Two GUID values will be reported, but the one we need is the one labled "Partition unique GUID". Copy this value and go to the partition 1 (FAT16 partition) and open SYSLINUX.CFG, go to the line "append root=PARTUUID=" and replace the value there with the one copied from gdisk interrogation of the new f2fs partition. Save SYSLINUX.CFG and the system should be bootable. Mine was!
I repeated the above procedure on a 32 GB USB stick (=> a 29.8 f2fs partition) which worked equally well.
gimp-quirky-2.6.12
gimp-quirky-2.6.12 compiled and available
Compiled with old gegl 0.1
If the included python is installed then it will open ORA files
(native format of mypaint)
Unfortunately I couldn't get the g'mic plugins to work
All pets inside gimp-quirky-2.6.12.tar.gz (just install the main pet package
if that is all you need)
http://www.datafilehost.com/d/afdc41a7 31mb
_______________________________________________
I was able to back up a full install using Barry Kauler's Pudd
______________________________________________
Compiled with old gegl 0.1
If the included python is installed then it will open ORA files
(native format of mypaint)
Unfortunately I couldn't get the g'mic plugins to work
All pets inside gimp-quirky-2.6.12.tar.gz (just install the main pet package
if that is all you need)
http://www.datafilehost.com/d/afdc41a7 31mb
_______________________________________________
I was able to back up a full install using Barry Kauler's Pudd
______________________________________________
Last edited by don570 on Fri 31 Jan 2014, 01:24, edited 2 times in total.
Please be patient with an old grumpy Noob.
I am a frugal fanatic so no way I destroy the only ntfs
partition I have with all the other puppies and other
Linux frugal installs that is on that single partition. sda1 the sda2 is for
windows Vista on the Desktop. I need those for upgrading my smartphones
but I never use it other than for that purpose maybe once a year. .
So please make a version that one can manually install
as a standard frugal install that Puppy has worked for many years.
We need mirrors. Dowloads usally take a few minutes
but this one some33 minutes.
I am a frugal fanatic so no way I destroy the only ntfs
partition I have with all the other puppies and other
Linux frugal installs that is on that single partition. sda1 the sda2 is for
windows Vista on the Desktop. I need those for upgrading my smartphones
but I never use it other than for that purpose maybe once a year. .
So please make a version that one can manually install
as a standard frugal install that Puppy has worked for many years.
We need mirrors. Dowloads usally take a few minutes
but this one some33 minutes.
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though