Re: donut is dead, long live the donut
I've tried reinstalling both LILO and the Debian MBR. Neither 'install-mbr' nor rerunning 'liloconfig' seems to have had an effect. i don't know, what liloconfig is for, but does it automatically run lilo? the invocation of /sbin/lilo does the actual installation of the boot sector/mbr ... -- Hi! I'm a .signature virus! Copy me into your ~/.signature, please! -- Linux - the last service pack you'll ever need.
Re: donut is dead, long live the donut
Oswald Buddenhagen [EMAIL PROTECTED] writes: DZM I've tried reinstalling both LILO and the Debian MBR. Neither DZM 'install-mbr' nor rerunning 'liloconfig' seems to have had an effect. OB i don't know, what liloconfig is for, but does it automatically run lilo? OB the invocation of /sbin/lilo does the actual installation of the OB boot sector/mbr ... Actually, it doesn't. (And yes, I have run both LILO and installed the Debian MBR directly; that had no effect.) The default setup is to install LILO on the root partition, rather than in the MBR. A short specialized MBR is installed instead. Just about all of the functionality it has is to offer a choice of partitions to boot from, with a default of the first active partition. It doesn't even have much of an interface; for me, it would display 1FA: if tweaked. But this turns out not to have been a problem. After messing with things some more and finally creating a floppy with GRUB on it, I discovered that the system would just freeze if I tried to touch the hard drive before a Linux kernel booted. I traced this back to a BIOS setting: my system has a known buggy CMD640 IDE interface, and I had disabled the write prefetch option in the BIOS. The system *really* didn't like this, apparently, I re-enabled it and everything is more-or-less happy now. -- David Maze [EMAIL PROTECTED] http://www.mit.edu/~dmaze/ Theoretical politics is interesting. Politicking should be illegal. -- Abra Mitchell
donut is dead, long live the donut
I have a reasonably current woody system, named donut. In a fit of bravery mixed with stupidity, I was playing with 'hdparm' to try to improve disk performance. I must have broken something (and caused MASSIVE FILESYSTEM CORRUPTION; hdparm(8) seems overly paranoid), because I wound up having to reboot and things massively failing. The problem: the BIOS looks at the hard disk, proclaims operating system not found, and does nothing. I can reboot using a slink rescue disk, and get into my system that way. This isn't the most happy thing in the world, though, and I'd really like the system to work correctly. I've tried reinstalling both LILO and the Debian MBR. Neither 'install-mbr' nor rerunning 'liloconfig' seems to have had an effect. Is there some important little piece of information in the boot sector that's gotten lost? Are there any other hints for dealing with this type of situation? Should I just reinstall (not a major disaster, at least if I wait until after my finals)? TIA... -- David Maze [EMAIL PROTECTED] http://www.mit.edu/~dmaze/ Theoretical politics is interesting. Politicking should be illegal. -- Abra Mitchell
