I managed to find a spare CDRW. After checking the md5 of the Slacko64 5.8.8 iso again I blanked the disc and burnt the image in ImgBurn on the Win 7 side (previous disc had been done in Puppy with Pburn). The disc passed verification so I did a pfix=ram boot from it without incident.
I reformatted the partition I wanted to install the test Full to. 10GB ext4, partition was sda5 (see attached GParted screen for layout). Drive is a 1TB SATA HDD.
I then ran Universal Installer via the Install desktop icon. The icon in the section 'Filesystem in partition' is missing, see screen. I chose to install to sda5, the partition created above. Chose Full install, and wipe when prompted (that seemed strange as there wasn't anything on the partition other than the Lost+Found directory).
Once the install had completed, I rebooted into a 32-bit install of Slacko since Grub4DOS Config is missing in the 64 bit version for some reason and once that util had created the new menu.lst I then tried to boot into the new Full of Slacko 64.
It seemed to start to boot but then bombed out with a "Kernel panic - not syncing: no working init found" error. See screen photo for the error. It seems to do this whether I manually update menu,lst with the text provided by Universal Installer or whether I use Grub4DOS Config.
I don't use the Legacy Grub thing as the first two partitions on the drive are NTFS. Is there any reason why Grub4DOS Config isn't provided?
The thing I find strange is that the LiveCD is working fine. Haven't tried a Frugal yet.
Slacko64 - 64 bit Puppy - 6 Feb 2014
Can't get Full Install working on my Pentium D.
- Attachments
-
- Mer_sda.png
- Partition layout on main HDD in Merlin. sda5 is the partition for the full. Screen from after Full install attempt.
- (44.97 KiB) Downloaded 939 times
-
- PUI_Icon.png
- Missing icon on Universal Installer.
- (47.79 KiB) Downloaded 908 times
Zhaan - AMD K6 2 500, 512MB RAM, ATI Rage 128 VR. Full install Wary 5.5 [url=http://tinyurl.com/dy66kh8]HardInfo Report[/url]
Merlin - Core i5-4590, 8GB RAM, Radeon R9 270X. Slacko 5.7.0
Merlin - Core i5-4590, 8GB RAM, Radeon R9 270X. Slacko 5.7.0
Hi jades
My note to 01micko and his reply here
http://murga-linux.com/puppy/viewtopic. ... &start=135
(2nd & 3rd posts)
may provide a small insight into what’s happening.
HTH a little - regards - Ray
My note to 01micko and his reply here
http://murga-linux.com/puppy/viewtopic. ... &start=135
(2nd & 3rd posts)
may provide a small insight into what’s happening.
HTH a little - regards - Ray
[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.
@Jades
switch swap in regular partion scheme with the boot in extended partion scheme. This may have nothing to do with Slacko46 but limits on what can be booted from. Unsure how or where your boot files are but that setup is not common.
Must have the boot loader files access in regular partion and Grub4Dos can do your setup for you but direct boot full install uses full GRUB and must have a bootible partion.. ie where swap is now. swap can be anywhere it does not care.
switch swap in regular partion scheme with the boot in extended partion scheme. This may have nothing to do with Slacko46 but limits on what can be booted from. Unsure how or where your boot files are but that setup is not common.
Must have the boot loader files access in regular partion and Grub4Dos can do your setup for you but direct boot full install uses full GRUB and must have a bootible partion.. ie where swap is now. swap can be anywhere it does not care.
oh Jades you cant mix 32 bit loaders and boot 64bit. I reread your methods for getting around missing 64bit Grub4Dos.. Your setup will never work. And the error message is DUE to the attempted switch from 32 bit land into 64 bit land. Nothing to due with anything else. I do not recall a 64bit version of Grub4Dos.
They barely tested the reverse booting 64bit loaders to run 32bit.. At least that is possible and some have shown to work. Your setup will never be.
Maybe have Grub4Dos call regular GRUB64 to complete the boot but I have serious doubts that could work. well or easily..
They barely tested the reverse booting 64bit loaders to run 32bit.. At least that is possible and some have shown to work. Your setup will never be.
Maybe have Grub4Dos call regular GRUB64 to complete the boot but I have serious doubts that could work. well or easily..
Thanks to Ted Dog and Ray MK for the info. I have a cold so aren't in a particularly technical frame of mind but here's a little more info about the partition setup.
sda1 is the 'System Reserved' partition for the main Windows 7 Pro install on that drive. It's usually hidden on Win 7. This is where Grub4Dos is installed and is where menu.lst resides. Formatted NTFS.
sda2 is the main partition for the Windows 7 Pro install. I should point out that this is the 64-Bit version and is pefectly happy booting via Grub4Dos, hence my confusion. Also NTFS.
The two above had been set up by installing Win7 Po to a blank drive. The space for the following partitions was created by shrinking sda2 to free up space once I was happy Win7 was running.
sda3 is a Linux swap partition. It's here because it's nearer the start of the disc, not sure if that matters.
sda4 is an extended partition containing the partitions for the Linux stuff.
sda5 is the partition where I'm trying to get the Slacko64 install to boot from. ext4.
sda6 is for storing data which I want to access from the various Linux installs running on the machine without having to remember on which pupsave stuff is stored. ext4.
sda7 is intended for testing full installs, and currently has a PAE test build of Slacko (5.6.5.5 IIRC) installed to it. Partition is ext4 and this install boots perfectly every time.
For comparison purposes, my setup on the K6-2 500 machine can be seen on my site - I'm not posting it here to avoid confusion. That setup has worked fine for years but of course everything running on it is 32-bit.
The save files for the LiveCD installs are on sdb1, which is a 160GB SATA drive containing a single NTFS-formatted partition which is the Windows XP install. Booting for LiveCDs is of course from the DVD drive, so wouldn't be affected by boot loader oddities on the HDD.
HTH! Won't be able to test anything today, but may have a go tomorrow. Many thanks for the feedback, it's been very interesting.
sda1 is the 'System Reserved' partition for the main Windows 7 Pro install on that drive. It's usually hidden on Win 7. This is where Grub4Dos is installed and is where menu.lst resides. Formatted NTFS.
sda2 is the main partition for the Windows 7 Pro install. I should point out that this is the 64-Bit version and is pefectly happy booting via Grub4Dos, hence my confusion. Also NTFS.
The two above had been set up by installing Win7 Po to a blank drive. The space for the following partitions was created by shrinking sda2 to free up space once I was happy Win7 was running.
sda3 is a Linux swap partition. It's here because it's nearer the start of the disc, not sure if that matters.
sda4 is an extended partition containing the partitions for the Linux stuff.
sda5 is the partition where I'm trying to get the Slacko64 install to boot from. ext4.
sda6 is for storing data which I want to access from the various Linux installs running on the machine without having to remember on which pupsave stuff is stored. ext4.
sda7 is intended for testing full installs, and currently has a PAE test build of Slacko (5.6.5.5 IIRC) installed to it. Partition is ext4 and this install boots perfectly every time.
For comparison purposes, my setup on the K6-2 500 machine can be seen on my site - I'm not posting it here to avoid confusion. That setup has worked fine for years but of course everything running on it is 32-bit.
The save files for the LiveCD installs are on sdb1, which is a 160GB SATA drive containing a single NTFS-formatted partition which is the Windows XP install. Booting for LiveCDs is of course from the DVD drive, so wouldn't be affected by boot loader oddities on the HDD.
HTH! Won't be able to test anything today, but may have a go tomorrow. Many thanks for the feedback, it's been very interesting.
Zhaan - AMD K6 2 500, 512MB RAM, ATI Rage 128 VR. Full install Wary 5.5 [url=http://tinyurl.com/dy66kh8]HardInfo Report[/url]
Merlin - Core i5-4590, 8GB RAM, Radeon R9 270X. Slacko 5.7.0
Merlin - Core i5-4590, 8GB RAM, Radeon R9 270X. Slacko 5.7.0
http://www.jewishvirtuallibrary.org/jso ... 12918.html
Our families where those forced to leave in 1250 actually it was eariler up the hang on types lasted unt then our family left around 50 years before late 1190s
Our families where those forced to leave in 1250 actually it was eariler up the hang on types lasted unt then our family left around 50 years before late 1190s
But to be on topic it is good you have a 64 bit machine and Grub4Dos. Since G4D will call a 64bit bootloader to load windows then the workaround idea for it to call a 64 bit GRUB should work fine. But the call for kernel and initrd needs to be made after Grub4Dos hands off boot to a 64bit compiled GRUB.. Does that sound logical to you.. You could still load 32bit linuxes fine from Grub4Dos but 64bit needs a different extra step and its own grub.lst
TBH I didn't even know that the Pentium D is a 64-Bit CPU until relatively recently, the XP install is 32-Bit as have been all of the other versions of Puppy I have used. Slacko64 is the very first 64-bit Linux I've tried using and I only decided to do that after getting Win 7 Pro 64-bit running.
With regard to bootloaders, the main reason I'm using Grub4Dos is because I like the Grub4Dos Config util that Shinobar has written and also it seemed to work fine on the K6-2 500 setup. This is the first time I've encountered major problems, but it's also the first time I've tried to get a 64-bit Full running. I've only been using a bootloader on the Pentium D since I put Win 7 on it, previous Puppy use on that machine being exclusively via LiveCD setups.
Thinking about it, Grub4Dos Config running on a 32-Bit Puppy would automatically install a 32-Bit loader because that's the environment it finds itself running in...
Suggestions for alternative bootloaders are of course welcome, but I should point out that, while I'm happy enough tweaking the layout for the Linux stuff, the first two partitions have to stay as they are as Win 7 is the main OS for that machine. This is for an assortment of reasons, not least of which is that I'm not the only one using it.
[Edit: fixed typos]
With regard to bootloaders, the main reason I'm using Grub4Dos is because I like the Grub4Dos Config util that Shinobar has written and also it seemed to work fine on the K6-2 500 setup. This is the first time I've encountered major problems, but it's also the first time I've tried to get a 64-bit Full running. I've only been using a bootloader on the Pentium D since I put Win 7 on it, previous Puppy use on that machine being exclusively via LiveCD setups.
Thinking about it, Grub4Dos Config running on a 32-Bit Puppy would automatically install a 32-Bit loader because that's the environment it finds itself running in...
Suggestions for alternative bootloaders are of course welcome, but I should point out that, while I'm happy enough tweaking the layout for the Linux stuff, the first two partitions have to stay as they are as Win 7 is the main OS for that machine. This is for an assortment of reasons, not least of which is that I'm not the only one using it.
[Edit: fixed typos]
Last edited by Jades on Tue 25 Feb 2014, 22:38, edited 2 times in total.
Zhaan - AMD K6 2 500, 512MB RAM, ATI Rage 128 VR. Full install Wary 5.5 [url=http://tinyurl.com/dy66kh8]HardInfo Report[/url]
Merlin - Core i5-4590, 8GB RAM, Radeon R9 270X. Slacko 5.7.0
Merlin - Core i5-4590, 8GB RAM, Radeon R9 270X. Slacko 5.7.0
For whatever it's worth I've got two boxes multi-booting 64 bit Windows 7 Ultimate with both 32 and 64 bit Puppy and other Linux versions.I use good old Legacy grub (stage 1 in the MBR and stage 2 on sda3 on both boxes). sda1 and 2 are Windows 7 partitions while sda3 is for Puppy frugals and grub stage 2.Remainder of both drives are divided extended partitions.
Have had no trouble booting anything,either 32 bit or 64 bit.
I've got a few minutes so I'll do a quick full install of Slacko64 just as a test.
Have had no trouble booting anything,either 32 bit or 64 bit.
I've got a few minutes so I'll do a quick full install of Slacko64 just as a test.
The results are....... total failure.Kernel panic after kernel panic.
Tried Legacy Grub,Grub4dos........ even used the latest Fatdog to install Grub .....all kernel panics.
No problem with frugal installs....posting from Slacko64 frugal now.
I really love testing...... 
Tried Legacy Grub,Grub4dos........ even used the latest Fatdog to install Grub .....all kernel panics.
No problem with frugal installs....posting from Slacko64 frugal now.
Code: Select all
title Puppy Slacko 5.6 Frugal on sda3
rootnoverify (hd0,2)
kernel /pup01/vmlinuz pmedia=atahd pdev1=sda3 pfix=fsck psubdir=pup01
initrd /pup01/initrd.gz
title Puppy Slacko64 5.8.7 frugal in sda3
rootnoverify (hd0,2)
kernel /pup02/vmlinuz pmedia=atahd pdev1=sda3 pfix=fsck nouveau.noaccel=1 psubdir=pup02
initrd /pup02/initrd.gz
#
title Windows 7 Ultimate on (hd0,0)
root (hd0,0)
chainloader +1
title PCLOS Mate 2013
root (hd0,5)
chainloader +1
#
title Mepis 12 on (hd0,6)
root (hd0,6)
kernel /boot/grub/i386-pc/core.imgLuckily there's no problem with frugal installs....Grub installed with Slacko 5.6 on both boxes.
Just reformatted both drives a few weeks ago so I'm starting fresh.
Just reformatted both drives a few weeks ago so I'm starting fresh.
Code: Select all
title Puppy Slacko 5.6.5.2 Frugal on sda3
rootnoverify (hd0,2)
kernel /pup01/vmlinuz pfix=fsck pdev1=sda3 pmedia=atahd nouveau.noaccel=1
initrd /pup01/initrd.gz
title Puppy Slacko64 5.8.7 Frugal on sda3
rootnoverify (hd0,2)
kernel /pup02/vmlinuz pfix=fsck pdev1=sda3 pmedia=atahd nouveau.noaccel=1
initrd /pup02/initrd.gz
title Puppy Slacko 5.6.5.6 Frugal on sda3
rootnoverify (hd0,2)
kernel /pup03/vmlinuz pfix=fsck pdev1=sda3 pmedia=atahd psubdir=pup03
initrd /pup03/initrd.gz
title Puppy Slacko64 5.8.8 Frugal on sda3
rootnoverify (hd0,2)
kernel /pup04/vmlinuz pfix=fsck pdev1=sda3 pmedia=atahd psubdir=pup04 nouveau.noaccel=1
initrd /pup04/initrd.gz
title Fatdog64
root (hd0,2)
kernel /vmlinuz nouveau.noaccel=1
initrd /initrd
title Lighthouse64 Linux 602 frugal in sda3
rootnoverify (hd0,2)
kernel /pup11/vmlinuz pfix=fsck pdev1=sda3 pmedia=atahd psubdir=pup11 nouveau.noaccel=1
initrd /pup11/initrd.xz
title Puppy Raring 3.9.9.2 frugal in sda6
rootnoverify (hd0,5)
kernel /pup10/vmlinuz pfix=fsck pdev1=sda6 pmedia=atahd psubdir=pup10 nouveau.noaccel=1
initrd /pup10/initrd.gz
#
title Windows on (hd0,1)
root (hd0,0)
chainloader +1With time tonight now short, I thank James C for his input - both on this particular issue, as well as the numerous other cases where I have been testing Puppy and had wondered whether it really was just me who was encountering a problem.
Zhaan - AMD K6 2 500, 512MB RAM, ATI Rage 128 VR. Full install Wary 5.5 [url=http://tinyurl.com/dy66kh8]HardInfo Report[/url]
Merlin - Core i5-4590, 8GB RAM, Radeon R9 270X. Slacko 5.7.0
Merlin - Core i5-4590, 8GB RAM, Radeon R9 270X. Slacko 5.7.0
Slacko64 5.8.8 live w/ save on usb flash on another old box.....no hdd so I can't try any installs.Working well though.
# report-video
Report Video 1.3 - Tue 25 Feb 2014 on Slacko64 Puppy 5.8.8 - Linux 3.13.1 x86_64
Chip description:
5.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RS480 [Radeon Xpress 200 Series]
oem: ATI RADEON Xpress 200G Series
X Server: Xorg Driver used: radeon
X.Org version: 1.12.4
dimensions: 1024x768 pixels (270x203 millimeters)
depth of root window: 24 planes
...the above also recorded in /tmp/root/ as report-video,
and archived with xorg.conf and Xorg.0.log as report-video-full.gz
# glxgears
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
354 frames in 5.0 seconds = 70.711 FPS
375 frames in 5.0 seconds = 74.826 FPS
376 frames in 5.0 seconds = 75.005 FPS
376 frames in 5.0 seconds = 75.026 FPS
376 frames in 5.0 seconds = 75.026 FPS
-Computer-
Processor : AMD Athlon(tm) 64 Processor 3400+
Memory : 958MB (389MB used)
Machine Type : Physical machine
Operating System : Slacko64 Puppy - 5.8.8
User Name : root (root)
Date/Time : Tue 25 Feb 2014 05:40:01 PM CST
-Display-
Resolution : 1024x768 pixels
OpenGL Renderer : Gallium 0.4 on ATI RS480
X11 Vendor : The X.Org Foundation
-Audio Devices-
Audio Adapter : ATIIXP - ATI IXP
-Input Devices-
AT Translated Set 2 keyboard
ImPS/2 Logitech Wheel Mouse
-Printers (CUPS)-
CUPS-PDF : <i>Default</i>
-SCSI Disks-
HL-DT-ST CD-RW GCE-8483B
Kingston DataTraveler 2.0
# report-video
Report Video 1.3 - Tue 25 Feb 2014 on Slacko64 Puppy 5.8.8 - Linux 3.13.1 x86_64
Chip description:
5.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RS480 [Radeon Xpress 200 Series]
oem: ATI RADEON Xpress 200G Series
X Server: Xorg Driver used: radeon
X.Org version: 1.12.4
dimensions: 1024x768 pixels (270x203 millimeters)
depth of root window: 24 planes
...the above also recorded in /tmp/root/ as report-video,
and archived with xorg.conf and Xorg.0.log as report-video-full.gz
# glxgears
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
354 frames in 5.0 seconds = 70.711 FPS
375 frames in 5.0 seconds = 74.826 FPS
376 frames in 5.0 seconds = 75.005 FPS
376 frames in 5.0 seconds = 75.026 FPS
376 frames in 5.0 seconds = 75.026 FPS
-Computer-
Processor : AMD Athlon(tm) 64 Processor 3400+
Memory : 958MB (389MB used)
Machine Type : Physical machine
Operating System : Slacko64 Puppy - 5.8.8
User Name : root (root)
Date/Time : Tue 25 Feb 2014 05:40:01 PM CST
-Display-
Resolution : 1024x768 pixels
OpenGL Renderer : Gallium 0.4 on ATI RS480
X11 Vendor : The X.Org Foundation
-Audio Devices-
Audio Adapter : ATIIXP - ATI IXP
-Input Devices-
AT Translated Set 2 keyboard
ImPS/2 Logitech Wheel Mouse
-Printers (CUPS)-
CUPS-PDF : <i>Default</i>
-SCSI Disks-
HL-DT-ST CD-RW GCE-8483B
Kingston DataTraveler 2.0
Code: Select all
# free
total used free shared buffers
Mem: 958672 884760 73912 0 66756
-/+ buffers: 818004 140668
Swap: 0 0 0
# -
gcmartin
OK, I've set up a Frugal install of 5.8.8 on the Pentium D, using Universal Installer and having booted into the LiveCD install. Installed to a sub directory on the same partition that I'm trying to get the Full working on (sda5, see my earlier post). Copied and pasted the recommended text that was suggested by PUI into the existing menu.lst on sda1.
Been through a number of boots, and am typing this on it right now. Working fine, so it's just the Full that won't boot. This seems to go along with James C's earlier tests on a similar partition layout to mine.
Been through a number of boots, and am typing this on it right now. Working fine, so it's just the Full that won't boot. This seems to go along with James C's earlier tests on a similar partition layout to mine.
Zhaan - AMD K6 2 500, 512MB RAM, ATI Rage 128 VR. Full install Wary 5.5 [url=http://tinyurl.com/dy66kh8]HardInfo Report[/url]
Merlin - Core i5-4590, 8GB RAM, Radeon R9 270X. Slacko 5.7.0
Merlin - Core i5-4590, 8GB RAM, Radeon R9 270X. Slacko 5.7.0
Slacko64 5.8.8
Live CD first boot.
New Netgear WNA1100 USB wireless adapter
Atheros AR9271
This Wireless adapter was not detected and manually loading the driver did not work.
Had the same problem trying to use it with Lupusuper-5.2.8.6-k3.0.25-2131124, but a fix was found.
The Linux driver is ath9k_htc for USB.
The problem seems to be that the name of the firmware files changed at some point.
A pet was made to correct this for Lupusuper.
I installed this pet in Slacko64 5.8.8.
It worked.
This wireless USB adapter now works with no problem. Now detected at bootup. Wireless setup works with no problem.
The problem and firmware pet fix is posted here:
http://www.murga-linux.com/puppy/viewto ... 834#739834
Live CD first boot.
New Netgear WNA1100 USB wireless adapter
Atheros AR9271
This Wireless adapter was not detected and manually loading the driver did not work.
Had the same problem trying to use it with Lupusuper-5.2.8.6-k3.0.25-2131124, but a fix was found.
The Linux driver is ath9k_htc for USB.
The problem seems to be that the name of the firmware files changed at some point.
Code: Select all
Older firmware map:
AR9271 - ar9271.fw
AR7010 - ar7010.fw or ar7010_1_1.fw
Newer firmware map:
AR9271 - htc_9271.fw
AR7010 - htc_7010.fwI installed this pet in Slacko64 5.8.8.
It worked.
This wireless USB adapter now works with no problem. Now detected at bootup. Wireless setup works with no problem.
The problem and firmware pet fix is posted here:
http://www.murga-linux.com/puppy/viewto ... 834#739834
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
Thanks bigpup
That firmware is in there but in the wrong spot. Fixed at woof level. In a few days I'll bring out a 32 bit slacko with the change.. can you give that a test with that wireless device please. Tia.
That firmware is in there but in the wrong spot. Fixed at woof level. In a few days I'll bring out a 32 bit slacko with the change.. can you give that a test with that wireless device please. Tia.
Puppy Linux Blog - contact me for access
-
gcmartin