[Now solved] MiniMe Graphics crash on start

[AS]

title   Just19-minime_new_a_(hd1,16)
kernel (hd1,16)/Just19-minime_new_a_(hd1,16)/vmlinuz livecd=/Just19-minime_new_a_(hd1,16)/Just19-minime_new_a_(hd1,16) fromusb root=UUID=a3462aa3-67fa-4bb5-b685-3480c31ef194 acpi=on vga=791 splash=verbose
initrd (hd1,16)/Just19-minime_new_a_(hd1,16)/initrd.gz

/usr/lib/libDrakX/bootloader.pm line 604 <----------

if I understand correctly the script, this is actually failing when trying to add a new entry to menu.lst,
I would temporarily remove the entries related to poorman, may be the installation script fail while parsing unusual lines containing (hd?,?) ...

AS

[wedgetail]

Have just sent the white towel to Just19 

I understand what you are saying, the red was on my request to have something in the name that reflected the partition if something had to be there.

I have no control over the read, I would have supplied  Just19-minime_new_a
and the script the rest.  I did test long and lightly unusual names to provoke the system, perhaps I got my re-ward 

Looking at those lines I can almost understand or guess what is going on, whid there was a way of getting better trace, gdb? except I can't remember how to run it any longer.

To bypass the script all together I have just run a CD-RW with the iso Burnt, this boots fine and runs fine, previously done media check and md5sum on this.  I have tried to install just GUI it fail, the picture with the file transfer vanishes after about 5 seconds.

Done a root konsole draklive-install: result:

[root@localhost guest]# draklive-install
/media/ user
Gtk-CRITICAL **: IA__gtk_widget_set_size_request: assertion `width >= -1' failed at /usr/lib/libDrakX/fs/partitioning_wizard.pm line 390.
Gtk-CRITICAL **: IA__gtk_widget_set_size_request: assertion `width >= -1' failed at /usr/lib/libDrakX/fs/partitioning_wizard.pm line 390.
umount: /dev/sdb18: not mounted
Setting up swapspace version 1, size = 4088504 KiB
LABEL=swap4000, UUID=061c4ede-3435-4b06-8be5-e07ba90e2191
Setting up swapspace version 1, size = 4088504 KiB
no label, UUID=6fdbb9bb-f52e-4f56-8c4b-844de0960066
tune2fs 1.41.12 (17-May-2010)
tar: ./home/guest/.local/share/akonadi/akonadiserver.socket: socket ignored
tar: ./home/guest/.local/share/akonadi/db_misc/mysql.socket: socket ignored
tar: ./home/guest/tmp/ksocket-guest/kdesud_\:0: socket ignored
tar: ./home/guest/tmp/ksocket-guest/kio_http_cache_cleaner: socket ignored
tar: ./home/guest/tmp/ksocket-guest/klauncherMT3198.slave-socket: socket ignored
tar: ./home/guest/tmp/ksocket-guest/kdeinit4__0: socket ignored
tar: ./var/run/acpid.socket: socket ignored
tar: ./var/run/xdmctl/dmctl-\:0/socket: socket ignored
tar: ./var/run/xdmctl/dmctl/socket: socket ignored
tar: ./var/run/uuidd/request: socket ignored
tar: ./var/run/nscd/socket: socket ignored
tar: ./var/run/dbus/system_bus_socket: socket ignored
tar: ./var/run/avahi-daemon/socket: socket ignored
add_entry at /usr/lib/libDrakX/bootloader.pm line 604, <> line 9.

standalone::bug_handler() called from /usr/lib/libDrakX/bootloader.pm:604   why bughandler call

bootloader::add_entry() called from /usr/lib/libDrakX/bootloader.pm:1109
bootloader::suggest() called from /usr/lib/libDrakX/any.pm:211
any::setupBootloaderBefore() called from /usr/lib/libDrakX/any.pm:135
any::setupBootloaderBeforeStandalone() called from /usr/sbin/draklive-install:308
main::setup_bootloader() called from /usr/sbin/draklive-install:73
main::install_live() called from /usr/sbin/draklive-install:42
[root@localhost guest]#

This should mean that the naming probably do not have any influence.

[wedgetail]

The Graphics crash as in the subjectline does not seem to be a problem at the moment.  I am not sure it is a crash as I now seem to be able to login and use startx to get back into GUI environment.

The topic now deals with why GRUB session at the end of a MiniMe full install fails for me.  I will put this on hold until I know more about the cause.    If that is found I will come back and make notes here.

[wedgetail]

I have placed an update status in the first post. The problem changed and settled to a repeatable, well almost, failure of trying to install from LiveCD.  The filesystem seems to be transferred but at the end Grub fails.

I have not given up trying to find why as I now feel uncomfortable with the work stored on the drive giving trouble.  

I have put the problem on hold for little while.

Edit:
Sunday, 22 May 2011

I will marked this as solved, and make a comment in the first post.  Turned out to be a BIOS problem.  Basically the order of HDD and USB HDD, First I had only one HDD and now and also an USB HDD for storage, then many months later when a problem turned up I quickly added another hard drive.

When removing the USB hard drive this made BIOS change the order but I not see this from Linux side, still don't understand the full story but by fising the order so that HDD1, HDD2 and USB_HDD are set in this order, then by removing the USB does not play havoc with the system.