a. GREAT!tazoc wrote:...it will be persistent in the next release.
I'll try to be patient whilst waiting for that to be released.
b. What about smm?
Any chance of a PET for a 64-bit version of that [or even better, something as good as Mailwasher?]
It's never that simple for me ...tazoc wrote:That's it! In Step 5 of the UEFI Install, use 'Boot from EFI File' to add the new boot option, which will start the a LH64 (rEFInd) boot menu from the new Fat32 partition.
Code: Select all
<drivers>
<EFI>
<fonts>
<keys>
<$RECYCLE.BIN>
Shellx64.efi
Code: Select all
---->options "pmedia-atahd pdev1=sda4
Code: Select all
---->options "pmedia-atahd pdev1=lh64b2
menuentry "Windows 8" {
volume ESP (Change ESP to whatever your normal boot partition is. Usually it's sda1 and is labeled ESP or SYSTEM.)
loader \EFI\Microsoft\Boot\bootmgfw.efi
}
If you have problems with refind not finding the ESP partiton when booting , it may show an error like bootmgfw.efi not found. You can try changing volume from ESP to 0: (That's a zero and a colon. The zero represents the first partition. If the normal boot partition is on sda2, then you would want "volume 1:".)
i have heard of virtualbox before. ive never heard of that 2nd one. from some googling it looks like virtualbox is completely separate from the rest of my system. its like its in its own little, box, for lack of a better word.gcmartin wrote:Understanding that LH64 does not run native linux 32bit apps with any reliablilty, and understanding your need, this might help:If you are not familiar with either, what they do is allow you to "boot" an additional PC (virtually) in the running LH64. When you boot the additional running PC within your lh64 you can start and run linux 32bit apps in that virtual PC while the LH64 is running its 64bit/Wine(windows) apps.
- VirtualBox
- KVM-QEMU
... have anything to do with this ...Step 5
Now reboot your computer and press f2 to enter UEFI setup (Some computers use a different key to enter setup). Then add your new fat32 partition as a boot option. Unfortunately this process varies quite a bit.
For this particular laptop you have to disable secure boot to use the "File Browser Add Boot Option", then re-enable it when your done. Again this process varies a lot. Generally on the boot tab you will find some way to add a new boot option. After you find the button to to add a boot option, you will be asked to select a partition. This is kind of cryptic as well, and might take some guessing. Then you will be asked to browse to a bootable EFI application, this will be EFI/boot/bootx64.efi on your new fat32 partition. If you can't browse to that path or you can't see the files that you put in your fat32 partition under EFI/boot/, you probably picked the wrong partition. After 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.
Shim UEFI Key Management
Continue boot
enroll key from disk
Enroll hash from disk
Is this the same thing as the GRUB menu?Generally on the boot tab you will find some way to add a new boot option.
GNU GRUB Version 2.00
Find /grub.cfg, /boot/grub.cfg, /boot/grub/grub.cfg
Manually specify location of grub.cfg to use
Shutdown
Reboot
Code: Select all
bash-4.1# glxinfo
glxinfo: error while loading shared libraries: libGL.so.1: wrong ELF class: ELFCLASS32
Code: Select all
./NVIDIA-Linux-x86_64-304.88.run
Code: Select all
5.0 VGA compatible controller: nVidia Corporation C51PV [GeForce 6150] (rev a2)
oem: NVIDIA
product: Crush50 Board - c51pv1 Chip Rev
X Server: Xorg Driver: nvidia
X.Org version: 1.12.3
The ELF class error is because you probably accidently clicked YES for installing the 32bit GL libs. (next time choose NO) Its an option in the RUN file.Meshworks wrote:Hi again Taz...
I've been running 513 all of this time and felt like trying to get current again!
Of course with my onboard NVIDIA 6150 I've hit a problem installing a driver capable of direct rendering for WoW and Compiz...
The available prebuilt driver doesn't include support for the 6150.
I pulled NVIDIA-Linux-x86_64-304.88.run from the nvidia site which includes 6 series support, and when i compile with getnvidia all seems to go ok with no errors... until i run anything GL related:
When I compile the package without getnvidia eg:Code: Select all
bash-4.1# glxinfo glxinfo: error while loading shared libraries: libGL.so.1: wrong ELF class: ELFCLASS32
The compile goes almost to the end ... then complains about a bunch of files ... cannot create symlink file exists .... press ok to continue ... then the compilation finishes apparently ok ... but with above error when i run GL related software.Code: Select all
./NVIDIA-Linux-x86_64-304.88.run
Code: Select all
5.0 VGA compatible controller: nVidia Corporation C51PV [GeForce 6150] (rev a2) oem: NVIDIA product: Crush50 Board - c51pv1 Chip Rev X Server: Xorg Driver: nvidia X.Org version: 1.12.3
I had a similar problem with 5.13 which has been my main OS since release, but managed a work around for that, so tried compiling earlier drivers eg: NVIDIA-Linux-x86_64-100.14.19-pkg2.run --- However the compile complains 'Cannot find kernel sources' and gives up!
I'm sticking with 6.02 anyway... I still have my old 513 save files if i wanna play WoW but would like this fixed. Any ideas? I'm not going to hold my breath waiting for Nvidia to add support for my outdated kit to the new drivers!
Only other problems I have (apart from the obvious!) are:
Gparted never manages to build a list of drives on my box... just keeps scanning. (workaround = use older version of gparted on different LHP release).
Firstsave wont allow me to select which of the partitions on my disk to place the save file! Always goes for sda3 despite plenty of room on sda1! (workaround = create savefile as required, boot clean, move savefile and sfs to desired partition and reboot).
Hope all is well with you. Keep on truckin'.
I think what may work for you is to run something like Slacko in a Linux Container. However the only person I know here who's tinkering around with Linux Containers is JamesBond, so you might want to poke at him and see if he can point you in the right direction. You'll need a newer kernel, both he and I are both doing testing on the 3.9.4 kernel with LXC support.AwesomesaurusRex wrote:i have heard of virtualbox before. ive never heard of that 2nd one. from some googling it looks like virtualbox is completely separate from the rest of my system. its like its in its own little, box, for lack of a better word.gcmartin wrote:Understanding that LH64 does not run native linux 32bit apps with any reliablilty, and understanding your need, this might help:If you are not familiar with either, what they do is allow you to "boot" an additional PC (virtually) in the running LH64. When you boot the additional running PC within your lh64 you can start and run linux 32bit apps in that virtual PC while the LH64 is running its 64bit/Wine(windows) apps.
- VirtualBox
- KVM-QEMU
is there some way to make it work so I still have the ability to get to my files on the rest of my computer from inside the box?
Code: Select all
<driver>
<EFI>
<keys>
<$RECYCLE.BIN>
Shellx64.efi
Code: Select all
<.>
<..>
<boot>
Code: Select all
<.>
<..>
<drivers_x64>
<icons>
bootx64.efi
MokManager.efi
grubx64.efi
^^ agreed. Not a problem if you have no 32 bit apps !The ELF class error is because you probably accidently clicked YES for installing the 32bit GL libs. (next time choose NO) Its an option in the RUN file.
In this case the symlink errors occur on a clean install... but only when I 'accidentally' choose to install the 32 bit compat stuff!The symlink errors usually occur when you try to re-install the nvidia.run package after its already created the symlinks.
LHP 602 is not 32bit compatible. So you cant run 32bit apps right now, definitely none that need GL acceleration. Awesomesaurusrex asked previously about 32bit compatibility. Check TazOC's reply to her on that.Meshworks wrote:Hi Q! Thanks for taking the time to go thru this with me.
The NVIDIA-Linux-x86_64-304.88.run worked as far as it goes... but only if i select NOT to compile the 32 bit compat stuff.
^^ agreed. Not a problem if you have no 32 bit apps !The ELF class error is because you probably accidently clicked YES for installing the 32bit GL libs. (next time choose NO) Its an option in the RUN file.
The symlink errors usually occur when you try to re-install the nvidia.run package after its already created the symlinks.
Is there a workaround? I thought 'maybe replace the graphics card' ... tried both drivers on a machine with an 8200 card ... still leaves me sans 32 bit support. I've obviously missed something !
Edit:
Should I go back a few releases... 5.15F?
I'd sure appreciate any tips you could offer me.dennis-slacko531 wrote:I've been moving onto these newer kernel pups, like Lighthouse & Barry's latest 13.04 Raring. Grub4dos has been a big help too. I've mirrored Lighthouse on my Godaddy server and provided a link below (and my bootscreen for fun).
http://www.beok.com/lnux
880 x 660 (bootscreen --Smartphone picture)
http://www.beok.com/Downloads/bootscreen1.jpg
Woops! You were so close... The last paragraph quoted in my earlier post had:edoc wrote:Being impatient ... I chose <EFI> which brought me to another File Explorer screen with:Code: Select all
<driver> <EFI> <keys> <$RECYCLE.BIN> Shellx64.efi
... so I chose <boot> which brought me to another File Explorer screen:Code: Select all
<.> <..> <boot>
I chose grubx64.efi which...Code: Select all
<.> <..> <drivers_x64> <icons> bootx64.efi MokManager.efi grubx64.efi
(not grubx64.efi.) Please try again. You've got a good machine there; my UEFI setup has no file explorer so I had to manually type in the path.EFI/boot/bootx64.efi
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.tazoc wrote:Woops! You were so close... The last paragraph quoted in my earlier post had:edoc wrote:Being impatient ... I chose <EFI> which brought me to another File Explorer screen with:Code: Select all
<driver> <EFI> <keys> <$RECYCLE.BIN> Shellx64.efi
... so I chose <boot> which brought me to another File Explorer screen:Code: Select all
<.> <..> <boot>
I chose grubx64.efi which...Code: Select all
<.> <..> <drivers_x64> <icons> bootx64.efi MokManager.efi grubx64.efi
(not grubx64.efi.) Please try again. You've got a good machine there; my UEFI setup has no file explorer so I had to manually type in the path.EFI/boot/bootx64.efi
-TaZoC
I agree with gcmartin, you can install VirtualBox, then install your preferred 32-bit OS inside VB, e.g., Slacko. What I do is install the Devx-L64_602.sfs for LH64-602, then menu -> System -> Oracle VM VirtualBox Installer.AwesomesaurusRex wrote:Are there any options for me to run 32bit stuff in LHP? I don't want to run any of the 32 bit releases, because I've had driver issues with them. LHP works great on my laptop. Can I take parts of the slacko release and add them into LHP?tazoc wrote:No, only Wine (windows apps) should be 32-bit, and only if the optional Wine SFS is loaded. Better to use a 32-bit OS if you need the older apps.