Page 7 of 32
Posted: Sun 07 Jul 2013, 20:38
by tazoc
edoc wrote:I clicked on bootx64.efi it cycled me back to the Boot Manager window which took me back to the Shim UEFI then back to the Boot Manager window.
What am I missing, please?
http://www.lhpup.org/help/faqs/uefi-harddrive.htmlAfter you have added your new boot option, move that new boot option to the top of the boot order. Again, this will vary with different UEFI implementations. Then save and reboot.
Posted: Sun 07 Jul 2013, 21:41
by edoc
Step 1
Done.
Step 2
Done.
Step 3
Done.
Step 4
Done.
Step 5
Here's the hugely confusing part ...
I get these options at the Lighthouse Pup splash/menu:
Start EFI Shell
NOTE: This brings me to
EFI Shell version 2.31 [4096.1]
Current running mode 1.1.2
[color=ye
llow]Device mapping table
[/color] ....
Shell>
Start MOK utility at EFI\BOOT\MokManager.efi on lh64b2
NOTE: This takes me to "Shim UEFI key management" with the options
Continue boot
Enroll key from disk
Enroll hash from disk
Start MOK utility at EFI\BOOT\MokManager.efi on 9 MiB FAT volume
NOTE: This takes me to "Shim UEFI key management" with the options
Continue boot
Enroll key from disk
Enroll hash from disk
About rEFInd
Shut Down Computer
Reboot Computer
OR, I can arrow-up and get "Boot Lighthouse64 Linux from 9 MiB FAT volume".
So, where do I go to complete Step 5, please?
Everything I have tried so far has be chasing my tail ...
Thanks, David
VM hosting via KVM or VirtualBox
Posted: Mon 08 Jul 2013, 14:45
by gcmartin
YES, @AwesomesaurusRex both VM subsystems do create a "box" (really its a PC, virtually) within your running LH64 system...internally.
And, just as you would with a separate PC on your LAN, that "box" will need to connect to your LAN to use any files/folders/apps that are on any other PC on your LAN. IT would do it in exactly similar way that any other PCs can access files on other computers. So, essentially, the virtual PC, the "box", behaves and operates as a REAL PC.
There is one additional thing to remember when you use either VM host (QEMU-KVM or VirtualBox), you MUST instruct LH64 to create a network so that the "box" can live on the same LAN as LH64. Many users have missed this key piece in understanding.
Should you or anyone want to do this, post back indicating such. And, if anyone has already done this with LH64, also post back. TaZoC has posted an excellent approach to initiate running a 32bit OS in the "box" on LH64. This is a excellent element of LH64 and FATDOG-V600+.
Here to help
Posted: Wed 10 Jul 2013, 02:30
by tazoc
edoc wrote:OR, I can arrow-up and get "Boot Lighthouse64 Linux from 9 MiB FAT volume".
So, where do I go to complete Step 5, please?
Everything I have tried so far has be chasing my tail ...
Thanks, David
I'm assuming you've added your custom boot entry that we discussed earlier, and moved it to the top of your boot options (Step 5) (both done in UEFI Setup -> Boot page (aka BIOS Setup) by pressing F2 or similar when your PC starts.
Now it looks like you've rebooted and are seeing the rEFInd boot manager. So arrow-up to 'Boot Lighthouse64...' and press Enter. Usually that is already selected by default so that LH64 will boot when pressing Enter, or automatically after 10 sec. if nothing is pressed. On my system there is also an icon for starting Windows 8.
The screen you described is defined by the file refind.conf in /EFI/boot/ in your new Fat32 1GB partition, which can be opened with a text editor and tweaked as needed.
e.g., change 'timeout 10'
to 'timeout 5' or so
There should be an entry in refind.conf for Windows 8, which you can change to Windows 7. If it doesn't work there are suggestions in red under Step 4 of the install guide.
Hope that helps,
TaZoC
Posted: Wed 10 Jul 2013, 03:56
by edoc
It's working, it's working, it's working!
Thank you!
FULL INSTALL?
Posted: Wed 10 Jul 2013, 22:59
by dblmint
MAYBE THIS WAS ADDRESSED BEFORE, BUT:
...just wish I could do full install of Lighthouse64, and why not
I really don't fully understand [ noob am i ] ... so if not Lighthouse64, is there a 64bit, XFCE Puppy that can be fully installed?
Sincere thanks for your kind words of advice -
Posted: Thu 11 Jul 2013, 16:39
by edoc
edoc wrote:It's working, it's working, it's working!
Thank you!
Bad news ... not working ...
The lighthouse64 selection in the Boot Manager has disappeared.
I am back to needing the USB stick in order to boot to LH64.
Arghhh!
Re: FULL INSTALL?
Posted: Fri 12 Jul 2013, 18:44
by tazoc
dblmint wrote:...just wish I could do full install of Lighthouse64, and why not
I really don't fully understand [ noob am i ] ... so if not Lighthouse64, is there a 64bit, XFCE Puppy that can be fully installed?
Sincere thanks for your kind words of advice -
Welcome dblmint!
Please see this post:
http://www.murga-linux.com/puppy/viewto ... 059#704059
...and this guide for recommended installation:
http://www.lhpup.org/help/faqs/harddrive.html
I think after giving a frugal install a try, you'll find it works very well. You can boot off a USB stick or the hard drive itself. The only tough part of installation is, if your machine came with Windows 8 and UEFI firmware. But that applies to both a full and a frugal install. I recently tried a full install with Slackware64-current on a notebook with Win 8 and UEFI, and it was harder than I expected; took me about a week to get it working properly.
-TaZoC
Re: FULL INSTALL?
Posted: Fri 12 Jul 2013, 23:10
by dblmint
tazoc wrote:dblmint wrote:
Please see this post:
http://www.murga-linux.com/puppy/viewto ... 059#704059
...and this guide for recommended installation:
http://www.lhpup.org/help/faqs/harddrive.html
I think after giving a frugal install a try, you'll find it works very well. You can boot off a USB stick or the hard drive itself. The only tough part of installation is, if your machine came with Windows 8 and UEFI firmware. But that applies to both a full and a frugal install. I recently tried a full install with Slackware64-current on a notebook with Win 8 and UEFI, and it was harder than I expected; took me about a week to get it working properly.
-TaZoC
THANKS for your response! I'll check the links ...
Posted: Sat 13 Jul 2013, 13:57
by edoc
I gave up on UEFI Frugal for the moment & am booting, albeit a little inconsistently, from a USB stick.
OK, so not so funny guys, where are the files hidden?
I can see Seamonkey 12 files I acquired via Puppy Package Manager when I use pfind but when I go to /usr to look at them they are nowhere to be found - and I do have All on to show them in case they are Hidden.
Very weird.
Thunderbird is such a MS-Outlook like behemoth.
I'd live with Firefox if there were an integrated email alternative for 64. Sigh.
Posted: Sat 13 Jul 2013, 14:21
by Jim1911
Hi edoc,
A little off topic. I don't know anything about UEFI, but before I installed Windows 8, I did have frugal installations on the same drive with Vista that worked well. It appears that you need to resize your Windows partition and create a new linux partition for your frugal installations. CAUTION: Resize using Windows itself. Then install Grub4Dos to boot, it works great. That will get you away from booting with an USB installation.
Jim
Posted: Sat 13 Jul 2013, 14:59
by edoc
Any chance any of these alternative email apps may be available for LH64, please?
Evolution (Looks a lot like Seamonkey email - good for LH64? Plays nicely with Firefox?l)
Kmail (can't tell if it easily handles multiple accounts)
Sylpheed (not sure if I like the way it works)
I looked at others but most seemed to be abandonware or severely limited somehow:
Alpine
Balsa
Cone
GNUmail
mailx
Mutt
Pine
Wanderlust (emacs)
WDYT?
David
Posted: Sat 13 Jul 2013, 15:27
by rcrsn51
edoc wrote:Sylpheed (not sure if I like the way it works)
There is a Sylpheed package in the Fatdog repo
here. I have not tested it in LH64.
volume labels
Posted: Sat 13 Jul 2013, 15:28
by CatDude
Hello tazoc
I was wondering if it is at all possible to turn off the volume label on the desktop drive icons
CatDude
.
Posted: Sat 13 Jul 2013, 15:46
by edoc
Evolution is part of this Slackware GNOME project:
http://gnomeslackbuild.org/about/
Posted: Sat 13 Jul 2013, 16:05
by edoc
rcrsn51 wrote:edoc wrote:Sylpheed (not sure if I like the way it works)
There is a Sylpheed package in the Fatdog repo
here. I have not tested it in LH64.
Just spotted that, thanks!
I have had bad experiences with Sylpheed in the past, especially the way they handled multiple accounts, but perhaps that's been fixed.
It's worth a try.
Posted: Sat 13 Jul 2013, 16:10
by edoc
rcrsn51 wrote:edoc wrote:Sylpheed (not sure if I like the way it works)
There is a Sylpheed package in the Fatdog repo
here. I have not tested it in LH64.
I'm getting a pop-up:
This application wants to run:
/usr/sbin/petget
The administration password is required.
I don't recall setting an administration password.
Posted: Sat 13 Jul 2013, 16:20
by edoc
Jim1911 wrote:Hi edoc,
A little off topic. I don't know anything about UEFI, but before I installed Windows 8, I did have frugal installations on the same drive with Vista that worked well. It appears that you need to resize your Windows partition and create a new linux partition for your frugal installations. CAUTION: Resize using Windows itself. Then install Grub4Dos to boot, it works great. That will get you away from booting with an USB installation.
Jim
We rolled back the MS version of windows from win8 to win7.
There's a problem with setting up the Lighthouse64 EFI boot file - it's non-persistent for some reason ... will chase that later.
Meanwhile, I can't see the Seamonkey I downloaded nor can I find the Firefox files.
I'm hoping I can reuse the Mozilla E-mail and Internet files from Seamonkey so I don't have to rebuild everything.
Posted: Sat 13 Jul 2013, 16:24
by edoc
edoc wrote:rcrsn51 wrote:edoc wrote:Sylpheed (not sure if I like the way it works)
There is a Sylpheed package in the Fatdog repo
here. I have not tested it in LH64.
I'm getting a pop-up:
This application wants to run:
/usr/sbin/petget
The administration password is required.
I don't recall setting an administration password.
Just remembered ... it's been a really long time since I used a password with Puppy!
Posted: Sat 13 Jul 2013, 16:25
by edoc
Should I be concerned about this pop-up message?
The locale encoding is not UTF-8, but the environmental variable G_FILENAME_ENCODING is not set.
If the locale encoding is used for file name or directory name, it will not work correctly.
In that case, you must set the following environmental variable (see README for detail):
G_FILENAME_ENCODING=@locale
Continue?