contents of menu.list (grub) changes on updating
Hello All,
I have some strange problem with GRUB's menu.lst file. intially with my fresh install contents of my menu.lst file were as follow: Code:
title Debian GNU/Linux, kernel 2.6.13 Code:
title Debian GNU/Linux, kernel 2.6.13 Code:
title Debian GNU/Linux, kernel 2.6.13(splashy) It is not a porblem of splashy, because even if I install a new compiled kernel it does the same thing. How can I resolve this? Thanks in advance |
Have you looked at your /etc/fstab lately? What is on hda1? If you have a Linux there, it is possible that you are booting from the kernel on (hd0,0)/boot/ and then running /sbin/init /dev/hdc1, but if your fstab was created for your original install on hda and not edited after the change (for hdc), then you may be mounting the wrong partition. On the other hand, if you don't have a working Linux on hda1, I'm at a loss. If you run 'mount' are their any surprises?
|
Quote:
I am totally lost. Also what do you mean when you say: Code:
and then running /sbin/init /dev/hdc1, |
Quote:
I've only worked with Debian for a short while, but I have noticed that some configuration files have as their first line something about where it's from or something similar. But really I have no clue. I've moved drives and partitions several times before with other distros and haven't seen anything like what you describe.... |
Isn't your root hd(0,0) line the same before and after you changed primary and master disk designation? Wouldn't man grub give you better info? Isn't the root different after the disk change? hd(0,0) is /dev/hda1 no? Good luck.
|
Quote:
|
Quote:
I don;t know what is causing this problem.:( |
Can anyone give any clue why this is happening?
|
Without update?
Do you update your grub manually with grub-update, or the program you install does it? If former, after changing the /dev/hda1 to /dev/hdc1 do not run update-grub. It should be OK.
|
Quote:
I am toally lost at this point...:confused: |
Quote:
Code:
## ## Start Default Options ## |
I like debian because there a 10 methods to do a thing :)
Here's another one that should help you: modify /etc/kernel-img.conf and remove postinst_hook = /sbin/update-grub New kernel images installation won't launch anymore update-grub but then when you install a new image, you have to edit yourself /boot/grub/menu.lst otherwise next reboot... |
Thank you nx5000 and bobbens!!!!!!
I will try that. I think it should do the trick in my case. btw, from where did u get this information(man? debian doc??). Once again, thanks a lot.. |
I think I discovered this conf file while looking in the documentation for kernel-package, especially:
/usr/share/doc/kernel-package/README.grub There are interesting things in this directory |
Quote:
Also, nx5000 I tried the method that you suggeted but it did not work.The program that I installed still went ahead and made changes to the menu.lst Thank you to both of you for the kind help...... Debian Rules.....:D |
Quote:
This kernel-img.conf only works for new kernel-image installation, I was maybe not clear. |
Quote:
|
When I tried it, it had overriden my kopt values in menu.lst as if it did not use update-grub but its own mechanism. I then copied back a backup of this file. But what really annoyed me is that it left the /etc/init.d/splashyxx after uninstalling it. So I deleted them. I'm a bit fussy but it never happens in general with debian.
But that's my own opinion and maybe now it is corrected. The positive thing is that it is in user space while bootsplash is in kernel space and I'm not sure its a good thing to have a bootsplash in kernel space (the only advantage of this is that it can run earlier) |
Quote:
:) |
As I said my biggest problem while when uninstalling it so you'll see :)
|
All times are GMT -5. The time now is 11:25 PM. |