sn8kman Posted April 20, 2006 Report Share Posted April 20, 2006 (edited) Ok, since updating to KDE 3.5.2 and trying to customize my computer back to what I had in 3.5.1 I'm getting the following error from MCC>boot>configure how the system boots: :Fatal:not a number :""771"" Any idea how to fix this? :unsure: Edited April 20, 2006 by sn8kman Quote Link to comment Share on other sites More sharing options...
ianw1974 Posted April 20, 2006 Report Share Posted April 20, 2006 I think it's normally 773. Check your /etc/lilo.conf file or /boot/grub/menu.lst depending on what you're using for your boot loader. Quote Link to comment Share on other sites More sharing options...
sn8kman Posted April 20, 2006 Author Report Share Posted April 20, 2006 I think it's normally 773. Check your /etc/lilo.conf file or /boot/grub/menu.lst depending on what you're using for your boot loader. here's the first few lines: default="linux-i586-up-1GB" boot=/dev/sda map=/boot/map vga="\"771\"" keytable=/boot/us.klt menu-scheme=wb:bw:wb:bw prompt nowarn I assume I should remove the extra " from each side of \"771\"? Quote Link to comment Share on other sites More sharing options...
ianw1974 Posted April 20, 2006 Report Share Posted April 20, 2006 Here is my config: [ian@europa ~]$ cat /etc/lilo.conf # File generated by DrakX/drakboot # WARNING: do not forget to run lilo after modifying this file default="linux" boot=/dev/hda map=/boot/map keytable=/boot/uk.klt menu-scheme=wb:bw:wb:bw prompt nowarn timeout=100 message=/boot/message image=/boot/vmlinuz label="linux" root=/dev/hda2 initrd=/boot/initrd.img append="resume=/dev/hda3 splash=silent" vga=788 image=/boot/vmlinuz label="linux-nonfb" root=/dev/hda2 initrd=/boot/initrd.img append="resume=/dev/hda3" image=/boot/vmlinuz label="failsafe" root=/dev/hda2 initrd=/boot/initrd.img append="failsafe resume=/dev/hda3" other=/dev/hda1 label="windows" table=/dev/hda image=/boot/vmlinuz-2.6.12-18mdk label="2612-18" root=/dev/hda2 initrd=/boot/initrd-2.6.12-18mdk.img append="resume=/dev/hda3 splash=silent" vga=788 so I think yes, you just need it to be vga=773 or you can leave as 771 and see what it does. No quotes or slashes, just vga=771, or usually it should be 773 for 1024x768. Quote Link to comment Share on other sites More sharing options...
sn8kman Posted April 20, 2006 Author Report Share Posted April 20, 2006 (edited) thank you - i'll try that :D PERFECT! 771 (not "\"771\"") fixed it. Thank you again! Edited April 20, 2006 by sn8kman Quote Link to comment Share on other sites More sharing options...
sn8kman Posted April 20, 2006 Author Report Share Posted April 20, 2006 Well, it *was* fixed, then I hosed my MBR. :woops: Fixed that, but now I'm getting text again. However, the not a number error is gone. Here's my lilo.conf: # File generated by DrakX/drakboot # WARNING: do not forget to run lilo after modifying this file default="linux-i586-up-1GB" boot=/dev/sda map=/boot/map vga=normal keytable=/boot/us.klt menu-scheme=wb:bw:wb:bw prompt nowarn timeout=60 message=/boot/message disk=/dev/sda bios=0x80 image="/boot/vmlinuz" label="linux" root=/dev/sda1 initrd="/boot/initrd.img" append="resume=/dev/sda5 splash=silent" vga=788 image=/boot/vmlinuz label="linux-nonfb" root=/dev/sda1 initrd=/boot/initrd.img append="resume=/dev/sda5 splash=silent" image=/boot/vmlinuz label="failsafe" root=/dev/sda1 initrd=/boot/initrd.img append="failsafe splash=silent resume=/dev/sda5" image=/boot/vmlinuz-2.6.12-18mdk-i686-up-4GB label="linux-i686-up-4GB" root=/dev/sda1 initrd=/boot/initrd-i686-up-4GB.img append="resume=/dev/sda5 splash=silent" vga=788 image=/boot/vmlinuz-2.6.12-18mdk-i586-up-1GB label="linux-i586-up-1GB" root=/dev/sda1 initrd=/boot/initrd-i586-up-1GB.img append="resume=/dev/sda5 splash=silent" vga=788 image=/boot/vmlinuz-2.6.12-18mdk label="2612-18" root=/dev/sda1 initrd=/boot/initrd-2.6.12-18mdk.img append="resume=/dev/sda5 splash=silent" vga=788 Any suggestions to get back to lilo with graphical would be appreciated. Quote Link to comment Share on other sites More sharing options...
arctic Posted April 20, 2006 Report Share Posted April 20, 2006 Open the MCC, go to the startup section. From there, you can change the visual boot-style with one click. Silent is the default mode, verbose displays booting text in the startup screen, detailed will boot in only text mode. Quote Link to comment Share on other sites More sharing options...
sn8kman Posted April 20, 2006 Author Report Share Posted April 20, 2006 Thanks for the advise. However, once I get past LILO text the graphical boot works fine. It's the bootloader that I'm having a problem getting to go graphical. Call me weird, but I want my bootloader to be pretty Quote Link to comment Share on other sites More sharing options...
arctic Posted April 20, 2006 Report Share Posted April 20, 2006 It can also be configured in the MCC, startup section. Go to the bootloader selection and choose from the first drop-down menu the bootloader type you want to use. grub graphical, grub plain, lilo graphical, lilo plain. :) Quote Link to comment Share on other sites More sharing options...
sn8kman Posted April 20, 2006 Author Report Share Posted April 20, 2006 Again, did that - still not working. Maybe something to do with framebuffer? (just searching around and heard that mentioned once) Quote Link to comment Share on other sites More sharing options...
arctic Posted April 20, 2006 Report Share Posted April 20, 2006 Open a terminal, log in as root. Then launch lilo -V are any errors reported? I doubt that it has anything to do with frambuffer mode, as that one kicks in usually after the bootloader. Quote Link to comment Share on other sites More sharing options...
sn8kman Posted April 20, 2006 Author Report Share Posted April 20, 2006 Open a terminal, log in as root. Then launchlilo -V are any errors reported? I doubt that it has anything to do with frambuffer mode, as that one kicks in usually after the bootloader. only possible error I get: Writing boot sector. /boot/boot.0800 exists - no boot sector backup copy made. full lilo output: lilo -v LILO version 22.6.1, Copyright (C) 1992-1998 Werner Almesberger Development beyond version 21 Copyright (C) 1999-2004 John Coffman Released 17-Nov-2004, and compiled at 14:16:24 on Sep 12 2005 Reading boot sector from /dev/sda Using MENU secondary loader Calling map_insert_data Mapping message file /boot/message -> message-graphic Calling map_insert_file Boot image: /boot/vmlinuz -> vmlinuz-2.6.12-18mdk Mapping RAM disk /boot/initrd.img -> initrd-2.6.12-18mdk.img Added linux Boot image: /boot/vmlinuz -> vmlinuz-2.6.12-18mdk Mapping RAM disk /boot/initrd.img -> initrd-2.6.12-18mdk.img Added linux-nonfb Boot image: /boot/vmlinuz -> vmlinuz-2.6.12-18mdk Mapping RAM disk /boot/initrd.img -> initrd-2.6.12-18mdk.img Added failsafe Boot image: /boot/vmlinuz-2.6.12-18mdk-i686-up-4GB Mapping RAM disk /boot/initrd-i686-up-4GB.img -> initrd-2.6.12-18mdk-i686-up-4GB.img Added linux-i686-up-4GB Boot image: /boot/vmlinuz-2.6.12-18mdk-i586-up-1GB Mapping RAM disk /boot/initrd-i586-up-1GB.img -> initrd-2.6.12-18mdk-i586-up-1GB.img Added linux-i586-up-1GB * Boot image: /boot/vmlinuz-2.6.12-18mdk Mapping RAM disk /boot/initrd-2.6.12-18mdk.img Added 2612-18 Writing boot sector. /boot/boot.0800 exists - no boot sector backup copy made. Quote Link to comment Share on other sites More sharing options...
arctic Posted April 20, 2006 Report Share Posted April 20, 2006 Lilo was set up correctly, the config file looks okay... currently, I have no idea what might be wrong... sorry. Quote Link to comment Share on other sites More sharing options...
sn8kman Posted April 20, 2006 Author Report Share Posted April 20, 2006 Thank you for your help. as an aside - I am currently installing RPMs and noticed one for PXE isn't that something for network booting or is it more along the lines of what a bootloader would use? Quote Link to comment Share on other sites More sharing options...
ianw1974 Posted April 21, 2006 Report Share Posted April 21, 2006 No, PXE is network booting, nothing with LILO. Normally a service you run on a server, and then when you attempt to boot from the network card in your machine it should find the PXE server and connect to it to do whatever. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.