(OLD) (ARCHIVED) Puppy Linux Discussion Forum Forum Index (OLD) (ARCHIVED) Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info

This forum can also be accessed as http://oldforum.puppylinux.com
It is now read-only and serves only as archives.

Please register over the NEW forum
https://forum.puppylinux.com
and continue your work there. Thank you.

 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups    
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Mon 30 Nov 2020, 13:34
All times are UTC - 4
 Forum index » House Training » Beginners Help ( Start Here)
Puppy linux frugal installation, problem booting [Solved]
Moderators: Flash, Ian, JohnMurga
This forum is locked: you cannot post, reply to, or edit topics.   This topic is locked: you cannot edit posts or make replies. View previous topic :: View next topic
Page 1 of 5 [74 Posts]   Goto page: 1, 2, 3, 4, 5 Next
Author Message
LidiaS

Joined: 26 Feb 2017
Posts: 25

PostPosted: Mon 27 Feb 2017, 05:13    Post subject:  Puppy linux frugal installation, problem booting [Solved]  

Hello everyone,

please excuse my ignorance; I have been using Linux Ubuntu and Linux Mint for quite some time now but I cannot say I have good understanding of the more deep issues of Linux.

I have a netbook with poor performance (2 GB DD3, Intel Atom N2600) for which I have been trying to find the best software to make it work faster, with no luck so far. I have tried Ubuntu, Mint, other variations and the latest was Lubuntu. More or less I was happy with that, it only takes too much time to boot and also relatively bad speed when I'm browsing, when I build latex etc.

Yesterday, I thought of trying puppy and see what performance I get. I booted from a USB stick with the iso on it, and then performed a frungal install; I don't understand the details, but I thought that my Lubuntu would stay on the computer (which I wanted for the time being), and I would be able to test Puppy whenever I had time, something about being on the same partition was quite confusing though. In the process, I also think I installed Grub4dos (haven't used this before either).

Next time I boot my netbook, without the USB stick (I thought that was the point), in the boot setup (F12) I didn't have a choice for Lubuntu or Puppy as I thought (I later understood that is the frungal and not full installation), just HDD, and then there was a strange message as follows:

wee 0> find --set-root /grldr (0x80,0)
wee 0> /grldr
wee 13>

I spent hours googling to try to understand what's going on with no luck. I then noticed that when I plug the USB, it works 'normally', going directly to puppy. I tried to also erase Grub4dos since I got the feeling that this could solve my problem, but no luck. I tried to configure it but again, I wasn't sure what I was doing.

Finally, this morning, my computer instead of the `wee' message, it only says `Error loading operating system'.

Any comments that would help me understand what has happened would be welcome. More importantly, since I will need my netbook for traveling soon, can you guide me through uninstalling puppy and everything that came with it, and go back to my Lubuntu state? I guess later I will try to create a partition for Puppy but right now, I just want to use my netbook again!

Thank you very much in advance.

Last edited by LidiaS on Fri 03 Mar 2017, 05:31; edited 2 times in total
Back to top
View user's profile Send private message 
Galbi


Joined: 21 Sep 2011
Posts: 1113
Location: Bs.As. - Argentina.

PostPosted: Mon 27 Feb 2017, 11:22    Post subject:  

Hi, how did you make the USB stick bootable?
Which Puppy did you try?

For what I know, wee it's a bootloader, Grub4Dos it's another one.

I'm not familiar with wee, but Grub4dos (if it's correctly installed) it's very keen on finding other OS in the hard drive and presenting them in the menu to choose which OS to boot.

Please give more information to can help you:

You do what?
You see what?

Saludos.

_________________
Remember: "pecunia pecuniam parere non potest"
Back to top
View user's profile Send private message 
mikeslr


Joined: 16 Jun 2008
Posts: 3913
Location: 500 seconds from Sol

PostPosted: Mon 27 Feb 2017, 12:27    Post subject: Post Subject  

Hi wee,

I'm not familiar with the wee bootloader either. But it seems that was the bootloader you had on your hard-drive which was being used to boot Lubuntu.

Then you did a frugal install of Puppy. To where? To the USB-Stick? To a folder on your hard-drive? To your hard-drive without specifying a Folder? My guess is probably the last as it seems you've somehow over-written wee's booting instructions as it no longer finds Lubuntu.

When you boot with your USB-stick plugged in (?and press F12), do you get a menu giving you the choice to boot into either Puppy or Lubuntu? If you have that choice, can you then boot into Lubuntu?

I think what you want to be able to do is (1) boot into Puppy if the USB-Stick is plugged in and (2) boot into Lubuntu if the USB-Stick isn't plugged in.

That, by the way is how I dual-boot Puppy and Linux Mint Sarah. So, how to get there?

First read the P.S. concerning Toshibas. If you don't have a Toshiba, you should be able to following these instructions. If you do have a Toshiba, follow the instructions in the P.S.

Since the wee bootloader is no longer working, boot into Puppy and then call up grub4dos: Menu>system>grub4dos bootloader. You'll see a Graphical User Interface like that in the attached screen shot [except that I have 2 hard-drives and the USB-Key which was plugged in to boot Puppies]. By default, the first hard-drive on your computer, as Puppy sees it, is high-lighted indicating that is where grub4dos will install itself if you don't select another location. You can change that location by clicking your the listing for your USB-stick. Don't. You want grub4dos to install itself to your hard-drive so that you can boot without your USB-Stick being plugged in. Just Click OK. Grub4dos will install itself to your hard-drive and create a Menu.lst. When you next boot your computer a menu will appear giving you the choice between booting into Puppy and booting into Lubuntu.

You don't have to do anything else. [Except before Update Lubuntu --which will install Grub-- see the instructions in the P.S.] But if you want to set your computer up so that it will automatically boot into Lubuntu, and only boot into Puppy if the USB-Stick is plugged in, please tell us how you initially booted into Puppy. Was it from a CD? Some other way?

Making those changes can be as simple as having Grub4dos on both the Hard-drive and the USB-Stick and just editing their Menu.lsts --they are just text files-- but can also involve moving Puppy's files into a folder so they aren't scattered around your hard-drive.

In that case, we have to know what operating systems you have available. Puppy on your hard-drive and Puppy from a CD are two operating systems. And --getting back to my original questions-- where your Puppy files are located?

mikesLr

P.S. Is your computer a Toshiba? My wife has a Toshiba Satellite L775d. It booted Puppies fine with Grub4dos on the USB-Key. But when I installed Grub4dos to the hard-drive, it wouldn't boot anything at all without the USB-key plugged in. I don't know what Toshiba does with computers. Others have experienced similar problems after installing Grub4dos on Toshibas and only Toshibas. In the end I had to install a Linux which used Grub --not grub4dos. If that's the case, your best option would be to somehow boot into Lubuntu --perhaps from grub4dos on your USB-Stick-- and run its Grub boot-loader installing it to your hard-drive. Grub, however, doesn't recognize a Frugal Puppy as an operating system. So, if you wanted to boot a Puppy, you'd have to customize Grub's confg file, or install grub4dos on your USB-Stick. Recommend the latter.
grub4dos.png
 Description   Grub4Dos Graphical User Interface
 Filesize   37.78 KB
 Viewed   6506 Time(s)

grub4dos.png

Back to top
View user's profile Send private message 
LidiaS

Joined: 26 Feb 2017
Posts: 25

PostPosted: Tue 28 Feb 2017, 07:28    Post subject:  

Hi and thank you both for your answers.

The operating system is puppy Tahrpup 6.0.5 PAE, I burned the .iso to my USB stick on Windows using the Rufus USB installer, and my current state of affairs is: after installing Grub4dos as mikeslr suggested with his helpful picture, (although I did this also before fore sure), when I boot without the USB stick, the exact same wee messages come up again, whereas when I boot with the USB stick I can either choose to go puppy, or to HDD (from the F12 menu), but when I choose HDD the wee messages arise again. So if I understand correctly, instead of the wee mesages I should be able to boot to Lubunu. Unfortunately that is not the case.

To reply to the rest of questions, I did a frugal install to my hard drive. About the specifying a folder part, I remember being asked for a name for some folder, which I called somehow; I kind of remember if that's useful.

To sum up, no, I never get the option to log on Lubuntu, the wee messages are back, and I don't have a Toshiba, I have a packard bell. But still without being able to log to my old system, I couldn't do the Grup solution.

By the way, when I pressed 'ok' to installing Grub4dos on my hard drive, it showed me the image attached. I just pressed 'ok'. Is it alarming that it says Ubuntu is there and no Lubuntu?

Any ideas are very welcome, and thanks already for your help.
capture9534.png
Description 
png

 Download 
Filename  capture9534.png 
Filesize  143.54 KB 
Downloaded  480 Time(s) 
Back to top
View user's profile Send private message 
puppytahruser

Joined: 02 Oct 2016
Posts: 63

PostPosted: Tue 28 Feb 2017, 08:36    Post subject: re
Subject description: re
 

I am also using tahrpup 6.0.5. What I feel that you might choose the usb stick for frugal install instead of hdd. You can try reinstall tahrpup again but this time more carefully and taking more time understanding each step. May that can solve your problem. Though I am not linux expert either, may be this can help you.
Back to top
View user's profile Send private message 
foxpup

Joined: 29 Jul 2016
Posts: 1141

PostPosted: Tue 28 Feb 2017, 10:35    Post subject:  

It looks as if the wee bootloader was used for lubuntu and still is in use, but it seems to have gone wrong.

Can you find weemenu.txt on your sda1 (home)? What is in it?
Can you find grldr on sda1?
Can you find menu.lst on sda1? What is in it?

(Rufus puts isolinux, or something similar, on the usb, another bootloader.)
Back to top
View user's profile Send private message 
LidiaS

Joined: 26 Feb 2017
Posts: 25

PostPosted: Tue 28 Feb 2017, 11:41    Post subject:  

foxpup wrote:

Can you find weemenu.txt on your sda1 (home)? What is in it?
Can you find grldr on sda1?
Can you find menu.lst on sda1? What is in it?


weemenu.txt: I cannot find it anywhere.

grldr: I find it, yes.

menu.lst :
# menu.lst produced by grub4dosconfig-v1.9.2
color white/blue black/cyan white/black cyan/black
#splashimage=/splash.xpm
timeout 10
default 0

# Frugal installed Puppy

title Puppy tahr 6.0.5 (sda1/tahr6.0.5frugal)
uuid 3711e60d-bb1a-4de4-b789-44271b599c68
kernel /tahr6.0.5frugal/vmlinuz pmedia=atahd psubdir=tahr6.0.5frugal pfix=fsck
initrd /tahr6.0.5frugal/initrd.gz

title Puppy tahr 6.0.5 (sdb1)
find --set-root --ignore-floppies --ignore-cd /puppy_tahr_6.0.5.sfs
kernel /vmlinuz pmedia=usbflash pfix=fsck
initrd /initrd.gz

# Full installed Linux

title Ubuntu 16.10 (sda1)
uuid 3711e60d-bb1a-4de4-b789-44271b599c68
kernel /vmlinuz root=/dev/sda1 ro
initrd /initrd.img

# Windows
# this entry searches Windows on the HDD and boot it up
title Windows\nBoot up Windows if installed
errorcheck off
find --set-root --ignore-floppies --ignore-cd /bootmgr
chainloader /bootmgr
find --set-root --ignore-floppies --ignore-cd /ntldr
chainloader /ntldr
find --set-root --ignore-floppies --ignore-cd /io.sys
chainloader /io.sys
errorcheck on

# Advanced Menu
title Advanced menu
configfile /menu-advanced.lst
commandline

In fact, grldr and menu.lst, along with that folder which I gave my own name while installing, are all together in the directory /initrd/mnt/dev_save, if that gives any clue.

Thank you so much for trying to help!
Back to top
View user's profile Send private message 
mikeslr


Joined: 16 Jun 2008
Posts: 3913
Location: 500 seconds from Sol

PostPosted: Tue 28 Feb 2017, 12:41    Post subject: Grub4dos did find your Lubuntu  

Hi Lidia5,

Grub4dos did find your Lubuntu installation. Lubuntu is Ubuntu with the openbox window manager and Lxde desktop (and a few other tweaks). The files relating to the window manager are opened during the bootup process. [You could, if you wanted, install some other Window manager --such as Mate or Unity-- and choose which desktop you want to use]. But the initial files loaded into Random Access Memory are identical whichever desktop you are using. Grub4dos doesn't read that far into the bootup process. Consequently, it sees only that the installation is Ubuntu.

You can edit Grub4dos's Menu.lst and just add an "L" to the front of "Ubuntu" if it will make you happier. [A real problem exists when Grub4dos sees several Ubuntu installations, but gives them each the same name. But, as each Ubuntu must use an entire partition, and Grub4dos and its menu.lst tells you where the OS is located, see below, you can figure it out and edit menu.lst to give each the name you want].

At any rate, Grub4dos and its menu.lst also see two "Frugal" installs: one on Sda1 and the other on Sdb1, "Sdb" is your USB-Stick: pmedia=usbflash means grub4dos saw it as a flash-drive. So it appears that somehow Puppy's necessary files were copied to both your hard-drive and your USB-Stick.

Go ahead and install Grub4dos to sda so that you can boot into Lubuntu without having to first plug in your stick. Do follow foxpup’s suggestion below and call up Menu>system>gparted to make certain that the “boot flag” has been set for sda. Puppies don’t always care, but Lubuntu will. Installing a bootloader should over-write the one previously there. But perhaps it didn't. And that may be caused by what happens when you boot into any Puppy which will use a SaveFile/Folder. So, while you’re looking at what gparted displays, see which drives gparted noted as being “locked”.

I’m pretty certain that you have the required Puppy files on both sda (your hard-drive) and sdb (your usb-stick). But just to make sure, see if you can boot into both. In booting, Puppy automatically mounts the drive from which it booted. There will be an “x” in the top-right corner of the drive icon representing Puppy’s Home drive. If you click that icon a window will open showing you files and folders at the top of that drive. A drive on which you have both Lubuntu and the folder tahrpup6.0.5frugal is located will also show folders with names such as bin, boot, media, and var to name a few. Click the tahrpup6.0.5frugal folder and see if there’s a file in it named something like tahrsave-xxx. Emphasis supplied. The xxx represents any addition you chose to add to a SaveFile/folder when you created it. But also see if within that folder are all of the following files: initrd.gz, vmlinuz, puppy_tahr_6.0.5.sfs and zdrv_tahr_6.0.5.sfs. Those files are necessary for a Puppy to boot from the directory specified by the pmedia command in the menu.lst. The presence of tahrsave would indicate that you had booted into that “installation” of tahr and created a SaveFile/Folder for it.

Even though the Menu.lst on your USB-Stick has an argument telling it to only look into the tahrpup6.0.5frugal folder on the USB-stick for SaveFiles/Folder, if one isn’t there Puppy will examine your other drives for a SaveFile/Folder, and on finding it use it. When it does, it mounts the drive on which the SaveFile/Folder was found. Gparted will see that drive as locked. And it may be that grub4dos can’t over-write the gldr already written to a locked drive.

It would appear that both wee and grub4dos "write" a binary (machine code) named "gldr" to the drive you selected as the location for your bootloader. Gldr looks for a text file: menu.lst if using grub4dos; and I guess weemenu.txt if using wee. My best guess is that somehow weemenu.txt was deleted. My second best guess is that Tahrpup’s grub4dos wasn’t able to overwrite wee’s gldr. The two files may share the name gldr at the human level but be different at the machine level. See if you can manually delete it. Right-Click it and from the pop-up menu select delete. If you get an error message, or just to be doubly sure, you’ll have to boot into Tahrpup without calling on the use of any SaveFile/Folder on your sda drive. I discuss below how to add that possibility to a Menu.lst. But if you have quick fingers and a good memory, you can always get Puppy to do that on bootup.

Reboot Puppy. As soon as it starts to boot –you have about 4 seconds to begin- type puppy pfix=ram.

Puppy won’t use any SaveFile/Folder and won’t mount/lock any drive. Puppy still has administrative privileges over your entire computer including the right to delete any file. And this is also a good time to make certain via gparted that sda is set as a bootable device and to have grub4dos write its gldr and menu.lst to sda.

Additional thoughts – background info you need not act on now.

I recall the adage that the difference between an elephant and a flee is that "an elephant can have many flees but a flee can only have one elephant". A bootloader is the first piece code a computer loads into Random Access Memory [if you don't boot into bios to manage hardware settings]. It tells your computer what to do next -- boot into an operating system, or load a different boot-loader. [That's actually how Grub4dos handles booting into Windows -- it instructs your computer to load Window's bootloader]. But, you can only have one initial bootloader; and that one will be the last bootloader written to the top of the partition your computer is setup to boot from.

There are several different boot-loaders. [The downside of Linux's open-source philosophy. Everyone can create whatever he or she thinks best]. As they do the same job, they are all, more or less, interchangeable. But each as its own strengths and weaknesses. Grub4dos which just reads a text file regarding what to do next is the easiest for a User to customize. You just change the instructions in the text file. And with one or two exception --Manjaro linux being one-- it recognizes every operating system. But, it can't be used with computers employing the (U)efi code such as those specifically built for Windows 10 or Macs. [For the mess Microsoft's change of policy regarding getting it certification caused, see http://www.murga-linux.com/puppy/viewtopic.php?p=858159#858159]. Grub2 can, and so Linux devs seem to have stopped developing grub4dos. But Grub2 doesn't automatically recognize Frugal installs as operating systems. You have to manually customize a file, and that process isn't straight-forward.

If you installed Lubuntu to your hard drive from a running version by first booting it from a CD/DVD or USB-Key, it would have installed the Grub2 bootloader. And if you do an "update" Lubuntu, it may install the newest version of Grub2. [There's a way to prevent that, but you'll have to search Ubuntu's websites. I don't know off-hand]. So, the easiest course is to install Grub4dos to a USB-Key in order to boot Puppies and let Lubuntu do whatever it wants to when booting from your hard-drive.

There are advantages in having both a Tahrpup on your USB-stick and one on your hard-drive . A Frugal Puppy on your USB-Stick can be carried with you and usually booted from many computer you plug it into. A Frugal Puppy on a hard-drive boots up and operates faster than one on a USB-Stick; and offers more room to do stuff. What frugal means is that it frugally uses your drive, unlike a Full install which requires an entire partition. Lubuntu happily ignores whatever files are on its partition which are not part of its system.

But if you do actually have a functional frugal install on sda, there’s one change I would recommend to menu.lsts on both sda and sdb. Grub4dos saw sda as a hard-drive and so wrote “pmedia=atahd”. Puppy has a better way of operating from a hard-drive. Under that current directive, Puppy will periodically write whatever you have in Random Access Memory to your Puppy’s SaveFile/Folder. You can menu>system>Puppy Event Manager, click the Save Session Tab and change how often, but you can’t turn such Savings off entirely. However, if you edit “pmedia=atahd” to read “pmedia=ataflash” Puppy will treat your hard-drive as if it were a flash-drive, only performing a Save when you command it to. Unless you choose otherwise, when you shutdown/reboot you’ll be asked if you want to Save. The default is “No”, so you can just walk-away or do a hard power-off. But being asked is a good mnenmonic device. Under the standard Puppies, a Save icon will appear on your desktop. Under Lxpups, however, I think there will only be a listing on the Menu under the System section.

Having Puppies Save only when you want them to (a) prevents your SaveFile/Folder filling up with junk, including junk you aren’t aware of while surfing the Web; (b) corrupting your SaveFile/Folder if there’s a power-outage while a Save is taking place; and (c) makes it safer to try-out questionable applications. When you install an application it is, initially, only in RAM. You can Menu>Shut-down>Restart-X (AKA Graphical Server) which causes Puppy to re-catalog what is then on its system. If the questionable application doesn’t work or conflicts with another application, you can shutdown without Saving. If everything is OK, you can Save. But, as a Save will copy everything then in RAM to your SaveFile, I think the better practice is to shutdown without Saving; reboot; and before you do anything else re-install the application and Save.

But the downside of not having an Automatic Save is that any changes you made to files within "Puppy-Space" will be lost unless you command a Save. Your /root/my-documents folder --the first place applications look to open datafiles or write datafiles is in "Puppy-Space". So is the Download folder some web-browsers create. There's an easy work-around. Open one File-Manager window to /root and a second file-manager window to your Home Partition, the one which has the x in the top-right corner of its icon as soon as you bootup. Just clicking the icon will open a window to your home partition. Right-click an empty space in that window and from the Popup menu select New>Directory, and give it a name. I use "my-stuff" without the quotes. Left-click to enter that folder. Now, place your mouse-cursor on the my-documents folder, press and then drag it to the "my-stuff" folder, release and select MOVE. Press, hold and drag my-documents back to /root and select Link(relative). This will create something like a Windows short-cut. The folder is no longer in /root, Puppy-space, but your applications will still treat it as if it was.

Your applications will create document in and open documents from your hard-drive. You can, of course, create additional folders within the my-documents folder the same way the my-stuff folder was created. You can also move the Download folder into the my-stuff folder.

Second to last suggestion, for now. Smile It’s always a good idea to be able to boot into a pristine puppy, one which doesn’t copy the contents of a SaveFile/Folder into RAM on bootup. Despite everything you’ve done to avoid problems occasionally something happens and you need to create a new SaveFile/Folder; or you want to try something really dicey and not risk your current SaveFile/Folder. There are other ways to boot Puppy without it automatically using the SaveFile/Folder. But the easiest way for me –I have slow fingers and an iffy memory-- is to edit menu.lst to create another listing for, in your case, tahrpup. This is easy to do. Just open menu.lst in a text-editor (e.g. geany), scroll down to or click on where there’s a space between listing, press Return a couple of times to create some space. Click on the beginning “t” of the word title of the menu listing you desire to copy; hold-down the shift-key and press the down-arrow until you’ve highlighted that entire listing; click Edit on the text-editor’s menu, then click Copy. Scroll to or click on the empty space you created. Click Edit on the text-editor’s menu, then Paste.

Now you only need to change two things on your newly created menu listing. Edit its title to reflect that a SaveFile/Folder will not be used; perhaps “No Save”, “Without Save”, “Safe Mode”. Then, click on just to the right of the letters “fsck” and type “;ram” so that the pfix argument now reads “pfix=fsck;ram”. No space. Save your edited Menu.lst.


I also see that your version of Lubuntu is 16.10. That number refers to the kernel, which is newer than the 15.04 kernel used in Trusty Tahr/Tahrpup. A Kernel is a Linux operating systems "core/foundation" systems. Kernels are constantly being upgraded to deal with problems discovered or newer hardware and software. It is usually preferable to have a distro with the newest kernel that recognizes your hardware. 16.10 tells me that your version of Lubuntu was "spun" from Ubuntu Xenial Xerus.

Not to drive you crazy --well, yah, that's really my secret intent Laughing -- if you like how Lubuntu looks and handles, and as Xenial Xerus provides the drivers for your hardware, you might want to consider peebee's LxPup Xenial, which is the Puppy version of your Lubuntu. LxPups have their own thread on the Forum, http://www.murga-linux.com/puppy/viewtopic.php?p=730071#730071. But, if you follow the links on that thread looking for LxPup Xenial's ISO, you'll end up here: http://lx-pup.weebly.com/. Click where it says "Download", then select Upup Versions.

mikesLr

Last edited by mikeslr on Tue 28 Feb 2017, 23:14; edited 2 times in total
Back to top
View user's profile Send private message 
foxpup

Joined: 29 Jul 2016
Posts: 1141

PostPosted: Tue 28 Feb 2017, 14:07    Post subject:  

I agree with mikeslr: grub4dos finds all your installations - it looks very good - and will boot them ... when given the chance.
Quote:
Go ahead and install Grub4dos to sda so that you can boot into Lubuntu without having to first plug in your stick.

I've got to run now. But I'll post later regarding what may have gone wrong with wee, ... .

LidiaS, if I understand correctly you already tried to install grub4dos on sda. But the problem is exactly that you still find wee on your way.
When choosing to boot from hdd, you should get the menu.lst and have the possibility to boot either (l)ubuntu or puppy from hdd or puppy from usb (if your usb is plugged in) or whatever is in the menu.lst (and is also available).

It still looks as if grub4dos is not correctly installed. Could you reinstall grub4dos to be sure? You have to overwrite the boot record, I think that is where wee is installled.
Also, before that, look with Gparted if the sda1, where you install grub4dos (grldr and menu.lst), has the flag "boot".
Do this with your puppy on usb.

If that does not work, mikeslr will have to guide you further with removing wee/coping with wee.
Back to top
View user's profile Send private message 
LidiaS

Joined: 26 Feb 2017
Posts: 25

PostPosted: Tue 28 Feb 2017, 16:12    Post subject:  

Thanks for all the comments. I reinstalled grub4dos (for the third time) and the same things happen. Straight to puppy when USB is in, wee messages when USB is not it. Should I perhaps edit menu.lst?

If this wee bootloader cannot be deleted, if this causes the problem, should I do any of the following?

1) Try to install puppy at a partition? Will the frugal installation remain or go away?
2) Can I completely remove puppy? And later re-try or something.

Thanks again.

PS. Thanks for the suggestion for another puppy, I might give it a try after I fix this. Also yes, that was the case, I installed grub4dos at sda1 after first checking that it had the flag 'boot' at gparted.
Back to top
View user's profile Send private message 
foxpup

Joined: 29 Jul 2016
Posts: 1141

PostPosted: Tue 28 Feb 2017, 19:23    Post subject:  

Hi LidiaS
I just found this: http://www.murga-linux.com/puppy/viewtopic.php?t=95015
You could try fdisk /mbr to cleanup wee from the mbr and install grub4dos again.
Back to top
View user's profile Send private message 
foxpup

Joined: 29 Jul 2016
Posts: 1141

PostPosted: Tue 28 Feb 2017, 19:49    Post subject:  

Quote:
I have a netbook with poor performance (2 GB DD3, Intel Atom N2600)

Your machine is not that bad at all. It must be from 2011 or later. I have tahr puppy running on a machine that is almost 10 years older and my main machine is from 2008, dual core, 64bit, 2G ram and SSE3 like yours. It also mainly runs tahr. I am looking for a 64bit distro: I am trying out Slacko, Carolina Vanguard and Fatdog64 at the moment. You can probably choose any puppy you like and they will run fast and safe on your machine. Smile
Back to top
View user's profile Send private message 
mikeslr


Joined: 16 Jun 2008
Posts: 3913
Location: 500 seconds from Sol

PostPosted: Tue 28 Feb 2017, 22:42    Post subject: Post Subject  

Well I'm back. In the meantime, you posted some more information and foxpup made a very good suggestion. Together, those provided me with another idea as to what the problem might be.

It was easier for me to place that idea in context of my previous post. So I edited that post --in LibreOffice Writer-- and substituted the new text for the old.

Please refer back to my previous --now significantly re-written-- post.

mikesLr
Back to top
View user's profile Send private message 
LidiaS

Joined: 26 Feb 2017
Posts: 25

PostPosted: Wed 01 Mar 2017, 08:25    Post subject: Re: Grub4dos did find your Lubuntu  

First of all, thanks a million for all the helpful suggestions!

mikeslr wrote:

I’m pretty certain that you have the required Puppy files on both sda (your hard-drive) and sdb (your usb-stick). But just to make sure, see if you can boot into both. In booting, Puppy automatically mounts the drive from which it booted. There will be an “x” in the top-right corner of the drive icon representing Puppy’s Home drive. If you click that icon a window will open showing you files and folders at the top of that drive. A drive on which you have both Lubuntu and the folder tahrpup6.0.5frugal is located will also show folders with names such as bin, boot, media, and var to name a few. Click the tahrpup6.0.5frugal folder and see if there’s a file in it named something like tahrsave-xxx. Emphasis supplied. The xxx represents any addition you chose to add to a SaveFile/folder when you created it. But also see if within that folder are all of the following files: initrd.gz, vmlinuz, puppy_tahr_6.0.5.sfs and zdrv_tahr_6.0.5.sfs. Those files are necessary for a Puppy to boot from the directory specified by the pmedia command in the menu.lst. The presence of tahrsave would indicate that you had booted into that “installation” of tahr and created a SaveFile/Folder for it.


I am afraid I didn't understand how to do what you say, from the boot menu? From inside the puppy?

My gparted doesn't have locked sign anywhere.

I also did the puppy pfix=ram in the beginning of the boot and nothing new happened, just went straight to puppy as usual.

I tried the fdisk/mbr both at the wee blinking messages and at the terminal of my puppy, and nothing happened. In the terminal, it told me there is no such directory.

I deleted grldr and nothing changed (when rebooting), I reinstalled grub4dos and nothing happened.

Surprisingly or not (relevantly to both wee's and grub4dos's grldr case), at the directory /initrd/pup_ro2/usr/lib/grub4dos I found two files, another grldr and one wee.mbr that I cannot erase, I receive errors.

Googling for the wee bootloader, I found http://www.rmprepusb.com/tutorials/wee and more specifically where it says the following:

If you want to run grub4dos from a Windows 7 system that uses BitLocker, you cannot place the grldr file on the encrypted BitLocker system partition because the volume will be encrypted and therefore not recognised by grub4dos. Also grub4dos expects to find the grldr on the boot partition and nowhere else. You can however boot to WEE because bootmgr allows you to specify an MBR file in the BCD and then load grldr from a different partition. grldr will not work when loaded by bootmgr but WEE will. The boot flow looks like this:

MBR (normal Win7 type) -> bootmgr -> reads BCD -> load weegrldr.mbr -> internal wee menu tells wee to load grldr from 2nd partition -> grldr loads and runs grub4dos -> menu.lst is read and displayed -> user selects menu entry...

First create a weemenu.txt file which will just load grldr as follows:

find --set-root /grldr
/grldr

Now run this command to create an mbr file which contains these commands:

weesetup -s weemenu.txt -o weegrldr.bin

This will create a weegrldr.bin file. Now use EasyBCD to add a boot entry to Windows BCD or do it the hard way using BCDEdit.


I don't understand whether this is relevant to my issue, I just thought to put it here in case it helps someone else.

I will go through the rest of mikesLr great comments when I have more time. The truth is that I am flying in three days and I really want to work with my netbook. Being in a hurry, I think that for the time being I should delete Puppy and hope to have Lubuntu back, and try again after I return. I plan to use directions from http://www.puppylinuxfaq.org/first-steps-in-puppy-linux/9-installing-puppy-linux/25-uninstall-puppy-linux.html and hope for the best.
Back to top
View user's profile Send private message 
foxpup

Joined: 29 Jul 2016
Posts: 1141

PostPosted: Wed 01 Mar 2017, 13:08    Post subject:  

Quote:
I should delete Puppy and hope to have Lubuntu back

Hi LidiaS, that will most likely not work.

Quote:
I tried the fdisk/mbr both at the wee blinking messages and at the terminal of my puppy, and nothing happened. In the terminal, it told me there is no such directory.

Okee, that will not work.

Quote:
Surprisingly or not (relevantly to both wee's and grub4dos's grldr case), at the directory /initrd/pup_ro2/usr/lib/grub4dos I found two files, another grldr and one wee.mbr that I cannot erase, I receive errors.

I am surprised too Shocked But it is true! I checked in my puppy.
You are in your puppy on the usbflash then. You probably cannot delete the grldr and wee.mbr there because you use this path /initrd... . You should click the sdb1 to mount and access this place in a more 'accessible' manner. (Do the same to access sda1) But it would not do anything to remove them. It is on the sda1, where you try to install grub4dos, next to the puppy and the lubuntu (I thought l was for light) that the problem lies. The 2 files you found are just aids to grub4dos when you ask it to install on sda1. But this could mean that grub4dos is installed by installing wee.mbr first, certainly by puppy, maybe also by lubuntu (of lubuntu I guessed it from the start). Maybe something mismatched.

I found the info about wee also. But this is for installing linux next to windows. The first 4 steps in the chain are done in windows style.

If you are in a hurry, and do not want to get to the bottom of this, you may do a complete new installation. You would probably loose less time. And consider just one installation.
Reformat with gParted to remove all leftovers first.
WARNING: REFORMATTING WITH GPARTED OR ANY OTHER TOOL WILL ENTIRELY WHIPE OUT ANYTHING ON YOUR PARTITION!!!
FIRST BACKUP ANY ESSENTIAL DATA

USE AS A LAST RESORT ONLY!!!

If you need some help installing a puppy, please ask. It can be done very quickly, since you have it on usb.

Last edited by foxpup on Thu 02 Mar 2017, 05:19; edited 1 time in total
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 1 of 5 [74 Posts]   Goto page: 1, 2, 3, 4, 5 Next
This forum is locked: you cannot post, reply to, or edit topics.   This topic is locked: you cannot edit posts or make replies. View previous topic :: View next topic
 Forum index » House Training » Beginners Help ( Start Here)
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1319s ][ Queries: 12 (0.0458s) ][ GZIP on ]