On Thu, May 03, 2007 at 11:00:04PM +0200, Robert Millan wrote: > On Thu, May 03, 2007 at 04:14:46PM -0400, William Thompson wrote: > > > > > > I mean with grub. It's easy to miss-identify a "hang" as just console > > > fuckup, > > > and the point you described is precisely where you would stop seeing > > > anything > > > if it was the latter. > > > > There was no way I know of to determine if it actually booted or not (Given > > the setup I'm using). > > Well, in my setup it's even harder, since I don't have any OptiPlex 320 :-)
It'll be difficult for me as well being that I no longer have access to one. > I would also suggest that you try with GRUB 2 and report if it has the same > problem. GRUB Legacy is deprecated and we're probably going to replace it > soon now. If it didn't conflict with grub legacy, I would. I looked at the files in the grub2 package. If the /usr/lib/grub/i386-pc was placed in /usr/lib/grub2/i386-pc, there wouldn't be a conflict. (Actually, looking closer, there's probably no conflict as it is, but the files shouldn't be in the same directory) > > There are other users of grub that have reported this > > same problem with the OptiPlex 320 machines. > > I don't see anyone else in this bug log. Did any of these users contact us or > file a bug report? Do a google search for grub optiplex 320. They weren't necessarily debian users or they never reported the problem. Not all users bother to file bug reports, they just find workarounds and forget about it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
