Quirky April 7.1.93 (7.2beta)
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Quirky April 7.1.93 (7.2beta)
I DECIDED TO WITHDRAW VERSION 7.1.93
I am working on the next version, will update this Forum thread when it is ready (probably in a few days)
7.1.93 announcement and download:
http://bkhome.org/news/?viewDetailed=00262
I recommend, install to a USB-stick, SD-card, or external solid-state drive.
This will be a conventional full installation, it does not have the mode of entirely loading into RAM, as possible with Puppy, so with USB2, that interface is a speed bottleneck.
Even so, performance is perky. USB3 would be better.
You could try a full hard-drive partition install, but I am not supporting frugal for now.
I welcome feedback!
Lots of things to test. Ex:
Does the new Samba work? (should I have both SSM and YASSM installed?)
Any 32-bit apps/utilities misbehave with the 64-bit kernel?
I am working on the next version, will update this Forum thread when it is ready (probably in a few days)
7.1.93 announcement and download:
http://bkhome.org/news/?viewDetailed=00262
I recommend, install to a USB-stick, SD-card, or external solid-state drive.
This will be a conventional full installation, it does not have the mode of entirely loading into RAM, as possible with Puppy, so with USB2, that interface is a speed bottleneck.
Even so, performance is perky. USB3 would be better.
You could try a full hard-drive partition install, but I am not supporting frugal for now.
I welcome feedback!
Lots of things to test. Ex:
Does the new Samba work? (should I have both SSM and YASSM installed?)
Any 32-bit apps/utilities misbehave with the 64-bit kernel?
Last edited by BarryK on Thu 01 Oct 2015, 13:16, edited 2 times in total.
[url]https://bkhome.org/news/[/url]
Installquirky.amd64 errors out with
Pretty certain I'm running a 64 bit cpu......
Code: Select all
Verifying archive integrity... All good.
Uncompressing installquirky 100%
ERROR: The host Linux OS must have architecture 'amd64'. Please download the correct Quirky Installer. Aborting.
Warning: Missing charsets in String to FontSet conversion
Script completed hit RETURN to close window.
Code: Select all
root# inxi -Fff
System: Host: puppypc26852 Kernel: 4.1.7 x86_64 (64 bit) Desktop: JWM git-1263 Distro: tahrpup64 6.0.3.7
Machine: Mobo: ASUSTeK model: M5A97 LE R2.0 version: Rev 1.xx serial: 150545593600028
Bios: American Megatrends version: 2601 date: 03/24/2015
CPU: Hexa core AMD FX-6300 Six-Core (-MCP-) cache: 12288 KB
Clock Speeds: 1: 1400.00 MHz 2: 1400.00 MHz 3: 1400.00 MHz 4: 2000.00 MHz 5: 1400.00 MHz 6: 1400.00 MHz
CPU Flags: 3dnowprefetch abm aes aperfmperf apic arat avx bmi1 clflush cmov cmp_legacy
constant_tsc cpb cr8_legacy cx16 cx8 de decodeassists extapic extd_apicid f16c flushbyasid
fma fma4 fpu fxsr fxsr_opt ht hw_pstate ibs lahf_lm lbrv lm lwp mca mce misalignsse mmx
mmxext monitor msr mtrr nodeid_msr nonstop_tsc nopl npt nrip_save nx osvw pae pat pausefilter
pclmulqdq pdpe1gb perfctr_core perfctr_nb pfthreshold pge pni popcnt pse pse36 rdtscp
rep_good sep skinit sse sse2 sse4_1 sse4_2 sse4a ssse3 svm svm_lock syscall tbm tce topoext
tsc tsc_scale vmcb_clean vme vmmcall wdt xop xsave
Graphics: Card: NVIDIA GT218 [GeForce 210]
X.org: 1.15.1 drivers: nouveau (unloaded: vesa) tty size: 80x25 Advanced Data: N/A for root
Audio: Card-1: NVIDIA High Definition Audio Controller driver: snd_hda_intel Sound: ALSA ver: k4.1.7
Card-2: Advanced Micro Devices [AMD/ATI] SBx00 Azalia (Intel HDA) driver: snd_hda_intel
Network: Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169
IF: eth0 state: up speed: 100 Mbps duplex: full mac: 1c:87:2c:5a:bb:e2
Drives: HDD Total Size: 1120.2GB (2.2% used) 1: id: /dev/sda model: KINGSTON_SV300S3 size: 120.0GB
2: id: /dev/sdb model: WDC_WD10EZEX size: 1000.2GB
Partition: ID: swap-1 size: 8.60GB used: 0.00GB (0%) fs: swap
RAID: No RAID devices detected - /proc/mdstat and md_mod kernel raid module present
Sensors: None detected - is lm-sensors installed and configured?
Info: Processes: 137 Uptime: 7 min Memory: 389.9/7875.3MB Client: Shell (bash) inxi: 1.9.17
root#
Just for the hell of it, I ran installquirky.x86....
Code: Select all
Verifying archive integrity... All good.
Uncompressing installquirky 100%
./installquirky: line 119: /tmp/selfgz2065431574/dmidecode: No such file or directory
./installquirky: line 120: /tmp/selfgz2065431574/dmidecode: No such file or directory
./installquirky: line 121: /tmp/selfgz2065431574/dmidecode: No such file or directory
./installquirky: line 279: /tmp/selfgz2065431574/gtkdialog: No such file or directory
Script completed hit RETURN to close window.
The 32 bit installer is working in 32 bit Vividpup, downloading Aprilneo now....
- Attachments
-
- capture10949.jpg
- (64.06 KiB) Downloaded 1035 times
Quirky April 7.1.93 (7.2beta)
I ran the installer from Librepup:
# chmod 755 installquirky.x86
# sh installquirky.x86
Verifying archive integrity... All good.
Uncompressing installquirky 100%
/tmp/selfgz765622912/gtkdialog: /tmp/selfgz765622912/liblzma.so.5: no version information available (required by /usr/lib/libxml2.so.2)
/tmp/selfgz765622912/gtkdialog: /tmp/selfgz765622912/liblzma.so.5: no version information available (required by /usr/lib/libxml2.so.2)
/tmp/selfgz765622912/gtkdialog: /tmp/selfgz765622912/liblzma.so.5: no version information available (required by /usr/lib/libxml2.so.2)
/tmp/selfgz765622912/gtkdialog: /tmp/selfgz765622912/liblzma.so.5: no version information available (required by /usr/lib/libxml2.so.2)
/tmp/selfgz765622912/gtkdialog: /tmp/selfgz765622912/liblzma.so.5: no version information available (required by /usr/lib/libxml2.so.2)
/tmp/selfgz765622912/gtkdialog: /tmp/selfgz765622912/liblzma.so.5: no version information available (required by /usr/lib/libxml2.so.2)
Uncompressing aprilneo-7.1.93.usfs.xz to aprilneo-7.1.93.usfs...
Some preliminaries on the sdg...
Size of drive=60017MB
/tmp/selfgz765622912/gtkdialog: /tmp/selfgz765622912/liblzma.so.5: no version information available (required by /usr/lib/libxml2.so.2)
5+0 records in
5+0 records out
20971520 bytes (20.0MB) copied, 0.454253 seconds, 44.0MB/s
1+0 records in
1+0 records out
440 bytes (440B) copied, 0.000502 seconds, 856.0KB/s
mkfs.fat 3.0.26 (2014-03-07)
mkfs.fat: warning - lowercase labels might not work properly with DOS or Windows
/usr/local/apps/ROX-Filer/ROX-Filer: /tmp/selfgz765622912/liblzma.so.5: no version information available (required by /usr/lib/libxml2.so.2)
/usr/local/apps/ROX-Filer/ROX-Filer: /tmp/selfgz765622912/liblzma.so.5: no version information available (required by /usr/lib/libxml2.so.2)
F2FS-tools: mkfs.f2fs Ver: 1.4.1 (2015-03-04)
Info: Label = quirky2
Info: sector size = 512
Info: total sectors = 117669888 (in 512 bytes)
Info: zone aligned segment0 blkaddr: 512
Info: format version with
"Linux version 3.14-librepup (root@hazak) (gcc version 4.6.4 (Ubuntu/Linaro 4.6.4-6ubuntu2) ) #1 SMP Sat Sep 26 03:50:00 GMT-8 2015"
Info: Discarding device
Info: This device doesn't support TRIM
Info: format successful
1+0 records in
1+0 records out
440 bytes (440B) copied, 0.793709 seconds, 554B/s
/tmp/selfgz765622912/gtkdialog: /tmp/selfgz765622912/liblzma.so.5: no version information available (required by /usr/lib/libxml2.so.2)
#
I compiled cmus,links-2.1.2,and pcmanfm.
I managed to bugger up the panel when adding launchers to it, don't know how to fix it.
The flash drive is a 64gb usb-3.0 kingston
# chmod 755 installquirky.x86
# sh installquirky.x86
Verifying archive integrity... All good.
Uncompressing installquirky 100%
/tmp/selfgz765622912/gtkdialog: /tmp/selfgz765622912/liblzma.so.5: no version information available (required by /usr/lib/libxml2.so.2)
/tmp/selfgz765622912/gtkdialog: /tmp/selfgz765622912/liblzma.so.5: no version information available (required by /usr/lib/libxml2.so.2)
/tmp/selfgz765622912/gtkdialog: /tmp/selfgz765622912/liblzma.so.5: no version information available (required by /usr/lib/libxml2.so.2)
/tmp/selfgz765622912/gtkdialog: /tmp/selfgz765622912/liblzma.so.5: no version information available (required by /usr/lib/libxml2.so.2)
/tmp/selfgz765622912/gtkdialog: /tmp/selfgz765622912/liblzma.so.5: no version information available (required by /usr/lib/libxml2.so.2)
/tmp/selfgz765622912/gtkdialog: /tmp/selfgz765622912/liblzma.so.5: no version information available (required by /usr/lib/libxml2.so.2)
Uncompressing aprilneo-7.1.93.usfs.xz to aprilneo-7.1.93.usfs...
Some preliminaries on the sdg...
Size of drive=60017MB
/tmp/selfgz765622912/gtkdialog: /tmp/selfgz765622912/liblzma.so.5: no version information available (required by /usr/lib/libxml2.so.2)
5+0 records in
5+0 records out
20971520 bytes (20.0MB) copied, 0.454253 seconds, 44.0MB/s
1+0 records in
1+0 records out
440 bytes (440B) copied, 0.000502 seconds, 856.0KB/s
mkfs.fat 3.0.26 (2014-03-07)
mkfs.fat: warning - lowercase labels might not work properly with DOS or Windows
/usr/local/apps/ROX-Filer/ROX-Filer: /tmp/selfgz765622912/liblzma.so.5: no version information available (required by /usr/lib/libxml2.so.2)
/usr/local/apps/ROX-Filer/ROX-Filer: /tmp/selfgz765622912/liblzma.so.5: no version information available (required by /usr/lib/libxml2.so.2)
F2FS-tools: mkfs.f2fs Ver: 1.4.1 (2015-03-04)
Info: Label = quirky2
Info: sector size = 512
Info: total sectors = 117669888 (in 512 bytes)
Info: zone aligned segment0 blkaddr: 512
Info: format version with
"Linux version 3.14-librepup (root@hazak) (gcc version 4.6.4 (Ubuntu/Linaro 4.6.4-6ubuntu2) ) #1 SMP Sat Sep 26 03:50:00 GMT-8 2015"
Info: Discarding device
Info: This device doesn't support TRIM
Info: format successful
1+0 records in
1+0 records out
440 bytes (440B) copied, 0.793709 seconds, 554B/s
/tmp/selfgz765622912/gtkdialog: /tmp/selfgz765622912/liblzma.so.5: no version information available (required by /usr/lib/libxml2.so.2)
#
I compiled cmus,links-2.1.2,and pcmanfm.
I managed to bugger up the panel when adding launchers to it, don't know how to fix it.
The flash drive is a 64gb usb-3.0 kingston
- Attachments
-
- screenshot.jpg
- (31.04 KiB) Downloaded 994 times
Quirky April 7.1.93 (7.2beta)
I started over and ran the installer from Librepup to a 64gb usb-3.0 KingstonDataTraveller flash drive.
- Attachments
-
- screenshot.jpg
- (61.96 KiB) Downloaded 975 times
Full install to a 30 gb ext4 hdd partition.
-
Code: Select all
# report-video
VIDEO REPORT: Quirky April neo64, version 7.1.93
Chip description:
VGA compatible controller: nVidia Corporation Device 0a65 (rev a2)
Requested by /etc/X11/xorg.conf:
Resolution (widthxheight, in pixels): 1024x768x16
Depth (bits, or planes): 24
Modules requested to be loaded: dbe
Probing Xorg startup log file (/var/log/Xorg.0.log):
Driver loaded (and currently in use): nouveau
Loaded modules: dbe dri2 exa extmod fb glx kbd mouse shadowfb
Actual rendering on monitor:
Resolution: 1440x900 pixels (380x238 millimeters)
Depth: 24 planes
...the above also recorded in /tmp/report-video
Code: Select all
# free
total used free shared buffers
Mem: 8086416 363308 7723108 4440 11652
-/+ buffers: 351656 7734760
Swap: 8396796 0 8396796
#
Code: Select all
-Computer-
Processor : 6x AMD FX(tm)-6300 Six-Core Processor
Memory : 8086MB (219MB used)
Machine Type : Physical machine
Operating System : Quirky April neo64
User Name : root (root)
Date/Time : Thu Oct 1 02:48:26 2015
-Display-
Resolution : 1440x900 pixels
OpenGL Renderer : Unknown
X11 Vendor : The X.Org Foundation
-Audio Devices-
Audio Adapter : HDA-Intel - HDA ATI SB
Audio Adapter : HDA-Intel - HDA NVidia
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Are you using the latest installers from here:James C wrote:Installquirky.amd64 errors out withCode: Select all
Verifying archive integrity... All good. Uncompressing installquirky 100% ERROR: The host Linux OS must have architecture 'amd64'. Please download the correct Quirky Installer. Aborting. Warning: Missing charsets in String to FontSet conversion Script completed hit RETURN to close window.
http://distro.ibiblio.org/quirky/quirky ... eo-7.1.93/
Install instructions here:
http://distro.ibiblio.org/quirky/quirky ... README.htm
In your 64-bit Tahpup, file /etc/DISTRO_SPECS, what does variable DISTRO_TARGETARCH have?
...if it doesn't have "amd64", that is the cause of the problem.
[url]https://bkhome.org/news/[/url]
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Re: Quirky April 7.1.93 (7.2beta)
Yeah, the installer has some shared libs inside it, so that the utilities inside the installer, are not dependent on libs in the host system.Billtoo wrote:I ran the installer from Librepup:
# chmod 755 installquirky.x86
# sh installquirky.x86
Verifying archive integrity... All good.
Uncompressing installquirky 100%
/tmp/selfgz765622912/gtkdialog: /tmp/selfgz765622912/liblzma.so.5: no version information available (required by /usr/lib/libxml2.so.2)
/tmp/selfgz765622912/gtkdialog: /tmp/selfgz765622912/liblzma.so.5: no version information available (required by /usr/lib/libxml2.so.2)
/tmp/selfgz765622912/gtkdialog: /tmp/selfgz765622912/liblzma.so.5: no version information available (required by /usr/lib/libxml2.so.2)
/tmp/selfgz765622912/gtkdialog: /tmp/selfgz765622912/liblzma.so.5: no version information available (required by /usr/lib/libxml2.so.2)
/tmp/selfgz765622912/gtkdialog: /tmp/selfgz765622912/liblzma.so.5: no version information available (required by /usr/lib/libxml2.so.2)
/tmp/selfgz765622912/gtkdialog: /tmp/selfgz765622912/liblzma.so.5: no version information available (required by /usr/lib/libxml2.so.2)
Uncompressing aprilneo-7.1.93.usfs.xz to aprilneo-7.1.93.usfs...
Some preliminaries on the sdg...
Size of drive=60017MB
/tmp/selfgz765622912/gtkdialog: /tmp/selfgz765622912/liblzma.so.5: no version information available (required by /usr/lib/libxml2.so.2)
5+0 records in
5+0 records out
20971520 bytes (20.0MB) copied, 0.454253 seconds, 44.0MB/s
1+0 records in
1+0 records out
440 bytes (440B) copied, 0.000502 seconds, 856.0KB/s
mkfs.fat 3.0.26 (2014-03-07)
mkfs.fat: warning - lowercase labels might not work properly with DOS or Windows
/usr/local/apps/ROX-Filer/ROX-Filer: /tmp/selfgz765622912/liblzma.so.5: no version information available (required by /usr/lib/libxml2.so.2)
/usr/local/apps/ROX-Filer/ROX-Filer: /tmp/selfgz765622912/liblzma.so.5: no version information available (required by /usr/lib/libxml2.so.2)
F2FS-tools: mkfs.f2fs Ver: 1.4.1 (2015-03-04)
Info: Label = quirky2
Info: sector size = 512
Info: total sectors = 117669888 (in 512 bytes)
Info: zone aligned segment0 blkaddr: 512
Info: format version with
"Linux version 3.14-librepup (root@hazak) (gcc version 4.6.4 (Ubuntu/Linaro 4.6.4-6ubuntu2) ) #1 SMP Sat Sep 26 03:50:00 GMT-8 2015"
Info: Discarding device
Info: This device doesn't support TRIM
Info: format successful
1+0 records in
1+0 records out
440 bytes (440B) copied, 0.793709 seconds, 554B/s
/tmp/selfgz765622912/gtkdialog: /tmp/selfgz765622912/liblzma.so.5: no version information available (required by /usr/lib/libxml2.so.2)
#
I compiled cmus,links-2.1.2,and pcmanfm.
I managed to bugger up the panel when adding launchers to it, don't know how to fix it.
The flash drive is a 64gb usb-3.0 kingston
But, that is a work-in-progress. Mostly I have put in some libs, such as libf2fs.so.*, that may not be in the host.
In your case, there is gtkdialog builtin to the installer, and it is using, I think, liblzma in the host system, and there is a version mismatch.
Ha ha, I don't know how the tray could get like that!
The only solution I know for such a situation is to take a system snapshot beforehand, and roll back.
[url]https://bkhome.org/news/[/url]
Yes.BarryK wrote:Are you using the latest installers from here:James C wrote:Installquirky.amd64 errors out withCode: Select all
Verifying archive integrity... All good. Uncompressing installquirky 100% ERROR: The host Linux OS must have architecture 'amd64'. Please download the correct Quirky Installer. Aborting. Warning: Missing charsets in String to FontSet conversion Script completed hit RETURN to close window.
http://distro.ibiblio.org/quirky/quirky ... eo-7.1.93/
Read those.
BarryK wrote:In your 64-bit Tahpup, file /etc/DISTRO_SPECS, what does variable DISTRO_TARGETARCH have?
...if it doesn't have "amd64", that is the cause of the problem.
Code: Select all
#Prefix for some filenames: exs: tahrsave.2fs, tahr-6.0.2.sfs
DISTRO_FILE_PREFIX='tahr64'
#The version of the distro whose binary packages were used to build this distro:
DISTRO_COMPAT_VERSION='trusty'
#the kernel pet package used:
DISTRO_KERNEL_PET='Huge_Kernel'
DISTRO_XORG_AUTO='yes'
DISTRO_TARGETARCH='x86'
DISTRO_DB_SUBNAME='tahr64'
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Kernel configuration:Iguleder wrote:I don't really understand, Barry. Is it x32 or x86?
If it's built for x32, how come the same userspace works on x86 too? x32 is x86_64 only AFAIK.
CONFIG_IA32_EMULATION=y
CONFIG_IA32_AOUT=y
CONFIG_X86_X32=y
Yes, the entire x86 build just works, as-is, with the 64-bit kernel.
There are some gotchas, however. I have /lib64 with some libc libs, to be able to run 64-bit commandline utilities, they work fine. However, "ldd" doesn't work with them.
So far, the only utility that I had to use 64-bit, is ddcprobe, the 32-bit version returned nothing.
[url]https://bkhome.org/news/[/url]
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Ah, someone will have to inform 666philb that a 64-bit build should have an appropriate value in DISTRO_TARGETARCH, either "amd64" (which is what I use in woofQ), or "x86_64".James C wrote:BarryK wrote:In your 64-bit Tahpup, file /etc/DISTRO_SPECS, what does variable DISTRO_TARGETARCH have?
...if it doesn't have "amd64", that is the cause of the problem.Answers that question.Code: Select all
#Prefix for some filenames: exs: tahrsave.2fs, tahr-6.0.2.sfs DISTRO_FILE_PREFIX='tahr64' #The version of the distro whose binary packages were used to build this distro: DISTRO_COMPAT_VERSION='trusty' #the kernel pet package used: DISTRO_KERNEL_PET='Huge_Kernel' DISTRO_XORG_AUTO='yes' DISTRO_TARGETARCH='x86' DISTRO_DB_SUBNAME='tahr64'
[url]https://bkhome.org/news/[/url]
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Livestreamer is written in Python, which Quirky only has in the devx -- and I have gone back to having the devx as a separate PET.linuxcbon wrote:Hi Barry,
3 features requests, small programs :
To watch twitch :
1/ livestreamer (needs python to install, not sure if it needs it to run)
2/ livestreamer-twitch-gui
To play games :
3/ steam client
Cheers
[url]https://bkhome.org/news/[/url]
Just did.BarryK wrote:Ah, someone will have to inform 666philb that a 64-bit build should have an appropriate value in DISTRO_TARGETARCH, either "amd64" (which is what I use in woofQ), or "x86_64".James C wrote:BarryK wrote:In your 64-bit Tahpup, file /etc/DISTRO_SPECS, what does variable DISTRO_TARGETARCH have?
...if it doesn't have "amd64", that is the cause of the problem.Answers that question.Code: Select all
#Prefix for some filenames: exs: tahrsave.2fs, tahr-6.0.2.sfs DISTRO_FILE_PREFIX='tahr64' #The version of the distro whose binary packages were used to build this distro: DISTRO_COMPAT_VERSION='trusty' #the kernel pet package used: DISTRO_KERNEL_PET='Huge_Kernel' DISTRO_XORG_AUTO='yes' DISTRO_TARGETARCH='x86' DISTRO_DB_SUBNAME='tahr64'
http://www.murga-linux.com/puppy/viewto ... 983#865983
- Iguleder
- Posts: 2026
- Joined: Tue 11 Aug 2009, 09:36
- Location: Israel, somewhere in the beautiful desert
- Contact:
You misunderstood my question. Yes, I know you can use pure 32-bit userspace with a 64-bit kernel. My question is whether the userspace is built for x86 or for x86_64 with the x32 ABI (which won't work on x86_64 incapable processors, of course).BarryK wrote:Kernel configuration:Iguleder wrote:I don't really understand, Barry. Is it x32 or x86?
If it's built for x32, how come the same userspace works on x86 too? x32 is x86_64 only AFAIK.
CONFIG_IA32_EMULATION=y
CONFIG_IA32_AOUT=y
CONFIG_X86_X32=y
Yes, the entire x86 build just works, as-is, with the 64-bit kernel.
There are some gotchas, however. I have /lib64 with some libc libs, to be able to run 64-bit commandline utilities, they work fine. However, "ldd" doesn't work with them.
So far, the only utility that I had to use 64-bit, is ddcprobe, the 32-bit version returned nothing.
[url=http://dimakrasner.com/]My homepage[/url]
[url=https://github.com/dimkr]My GitHub profile[/url]
[url=https://github.com/dimkr]My GitHub profile[/url]
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Oh, crap, you are right. I will need to back off claiming this is x32. It is x86 running with a x86_64 kernel.Iguleder wrote:I don't really understand, Barry. Is it x32 or x86?
If it's built for x32, how come the same userspace works on x86 too? x32 is x86_64 only AFAIK.
I skimmed over the docs too quickly.
OK, 7.1.93 is a proof-of-concept that an all-32-bit build works fine with a 64-bit kernel.
...which is nice, it means that I can build with a 32-bit or 64-bit kernel, using the same 32-bit packages.
But, to get actual x32, and the speed improvements, I need to recompile everything in T2 with "-mx32" option.
OK, will do.
NOTICE TO EVERYONE
Testing is still very helpful, there is so much new stuff in 7.1.93, such as Samba. The installer.
But, I will be doing a recompile in T2, to (hopefully) get that true x32 optimisation.
[url]https://bkhome.org/news/[/url]
- Iguleder
- Posts: 2026
- Joined: Tue 11 Aug 2009, 09:36
- Location: Israel, somewhere in the beautiful desert
- Contact:
Glad I asked that question.
It's the consistency in your blog posts ('x86', 'x32', 'ia32' ...) and the documentation you mentioned that caught my attention.
x32 is indeed interesting, because of the performance gains under some workloads (like multimedia). However, it's an ABI for x86_64 only, so you lose the ability to build a Puppy with two kernels and one shared userspace. You gain the security and performance benefits of x86_64, without the memory overhead.
By the way: you'll have to rebuild everything for x32 - x32 and the x86 ABI are incompatible.
It's the consistency in your blog posts ('x86', 'x32', 'ia32' ...) and the documentation you mentioned that caught my attention.
x32 is indeed interesting, because of the performance gains under some workloads (like multimedia). However, it's an ABI for x86_64 only, so you lose the ability to build a Puppy with two kernels and one shared userspace. You gain the security and performance benefits of x86_64, without the memory overhead.
By the way: you'll have to rebuild everything for x32 - x32 and the x86 ABI are incompatible.
Last edited by Iguleder on Thu 01 Oct 2015, 11:10, edited 1 time in total.
[url=http://dimakrasner.com/]My homepage[/url]
[url=https://github.com/dimkr]My GitHub profile[/url]
[url=https://github.com/dimkr]My GitHub profile[/url]