Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Greetings from Amsterdam. This is not really a problem, more of an irritation. When I logout of my system and reboot the GRUB2 bootloader doesn't load. I just get a blinking cursor in the top left hand side of the screen. I have to hit the on/off button and then away she goes. Its fine when I do a full shutdown and restart too. It is as if the timing is all out. I live in total fear of anything to do with the bootloader because I have never had any success with the damn thing. Something always goes wrong. So has anyone had this happen to them and how did you reconfigure GRUB2 without blowing it up? Yes, I have made a double backup just to be safe. As I say, its an irritation rather than a problem but I would like to get it fixed. Many thanks.
If it works from the power on, your boot loader may be ok.
Reboot, hardware reset, and power off/on all do different things.Specifically power on reads the bios into memory is the "Shadow bios" options are set. Eprom & EEprom which hold the bios are slow to read beside dynamic ram - extremely slow by modern standards (~250ns access time). Cascade9 will probably post a list of access times for modern dram :-)). His list would be more accurate than mine.
It's possible the bios are being overwritten at some point. Get into the bios and turn all that off (Shadow this code - NO). Then try your reboot. It's painless, and it may isolate the problem.
It sounds like the reboot when you are logged out and the reboot/shutdown when logged in(I'm assuming that is what you mean by full shutdown)is either using a different shutdown/reboot script or something is being unloaded/disabled during log out.
If it works from the power on, your boot loader may be ok.
Reboot, hardware reset, and power off/on all do different things.Specifically power on reads the bios into memory is the "Shadow bios" options are set. Eprom & EEprom which hold the bios are slow to read beside dynamic ram - extremely slow by modern standards (~250ns access time). Cascade9 will probably post a list of access times for modern dram :-)). His list would be more accurate than mine.
It's possible the bios are being overwritten at some point. Get into the bios and turn all that off (Shadow this code - NO). Then try your reboot. It's painless, and it may isolate the problem.
Many thanks for the feedback. Unfortunately the only things that I understood was, ~250ns access time,lol! I'm relatively new to Linux and have taken the steep learning curve route with Crunchbang. Its working too! Having said that "Idiot Speak" is perfectly acceptable. lol!
It might be that your system has a different way for software to signal the hardware to reboot ... or that you have disabled that function in the BIOS-settings.
If it works from power on, the software sound ok. Go into the BIOS and fix it not to put any of the BIOS in ram. Then try a reboot. That may fix it.
If not, put it back the way it was.
Hi again. That's supper out of the way. My BIOS is a Phoenix SecureCore Version 1.09, EC Version 1.03. In Main I just have the usual set time and info. Advanced, I have the Boot Diagnostic Screen and Wake Up LAN. Both are disabled, The Boot screen has only the facility to change the boot order. That's it for configuration. No facility to not put the BIOS into RAM. Not very exciting at all. It is very strange.
I can't imagine that's the whole BIOS setup. Very sad if that's all they leave to the user. Is there some manufacturer's utility?
I was looking for a hardware solution. There is little software difference between reboot and power up, and your software works, which clears drivers, etc. Some mad systems used to present a different point for track 0 to lilo in times long ago, and that freaked it. Grub managed.
I can't imagine that's the whole BIOS setup. Very sad if that's all they leave to the user. Is there some manufacturer's utility?
I was looking for a hardware solution. There is little software difference between reboot and power up, and your software works, which clears drivers, etc. Some mad systems used to present a different point for track 0 to lilo in times long ago, and that freaked it. Grub managed.
Unfortunately, that's it. It must have been the standard BIOS for Fujitsu-Siemens AMILO Notebooks. It is really basic.
Letś try something then. Best to have a usb key or some way of storing stuff, and start from your home dir (It lands there when you log in). Also get a linux live cd/install cd or dvd of some sort.
You now have the master boot records from the disk, and the first partition. You might also need the one from your boot partition if it is different. Pop in the live cd and reboot. When that comes up, grab a console or terminal and run these
The correct output from the diff is no output. If you get no output, we can eliminate hardware and post your grub or lilo config file. If it says ¨Files differ¨ something weird is wrong.
Last edited by business_kid; 09-14-2013 at 03:09 PM.
Letś try something then. Best to have a usb key or some way of storing stuff, and start from your home dir (It lands there when you log in). Also get a linux live cd/install cd or dvd of some sort.
You now have the master boot records from the disk, and the first partition. You might also need the one from your boot partition if it is different. Pop in the live cd and reboot. When that comes up, grab a console or terminal and run these
The correct output from the diff is no output. If you get no output, we can eliminate hardware and post your grub or lilo config file. If it says ¨Files differ¨ something weird is wrong.
Hi from a very soggy Amsterdam . Thanks for getting back to me and all the effort you are putting in to help me out. I'm going to give it a try in the morning when I've got fresh caffeine in the old veins. I'll let you know the results. This problem is the only one I have with Crunchbang. Other than that, its a real charm of a distro; even for a Linux newbie like myself. I love it . Again, many thanks and have a great evening .
how old is this computer? If I remember right I had an older computer that would do the same thing when the linux kernels switched from apm power control to acpi power control.
Hi from a very soggy Amsterdam . Thanks for getting back to me and all the effort you are putting in to help me out. I'm going to give it a try in the morning when I've got fresh caffeine in the old veins. I'll let you know the results. This problem is the only one I have with Crunchbang. Other than that, its a real charm of a distro; even for a Linux newbie like myself. I love it . Again, many thanks and have a great evening .
Good Morning. I've just tried to run what you suggested and I got this:
Quote:
andy@andy-crunchbang:~$ dd if=dev/sda of=sdambr_on bs=512 count=1
dd: opening `dev/sda': No such file or directory
andy@andy-crunchbang:~$
andy@andy-crunchbang:~$ dd if=dev/sda1 of=sda1mbr_on bs=512 count=1
dd: opening `dev/sda1': No such file or directory
andy@andy-crunchbang:~$
I guess I'm doing something wrong or, there is something wrong with my partitions. This is my partition table; It looks fine to me.
[IMG][/IMG]
I'm baffled. (I hope I'm using the right protocols and formats to share info). Again, many thanks for all of your help.
Last edited by AndyInMokum; 09-15-2013 at 02:18 AM.
Reason: Terrible grammar.
how old is this computer? If I remember right I had an older computer that would do the same thing when the linux kernels switched from apm power control to acpi power control.
Hi and thanks for getting back to me. You ask a very good question. It is a second hand laptop, Fujitsu-Siemens AMILO li 3710 Intel Pentium Dual Core 2Ghz, 4GB RAM. It does have an old the Windows Vista sticker on it. So the old girl is at least 6 years old. The bug or whatever it is, is just an annoyance because I know it is not fixed.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.