SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
hey
i have slack1337 and i have problem loading it.
everything was fine till i installed kernel 2.6.38-4 from testing in DVD along with every thing there(like mesa and video-intel- i have intel graphic card). again everthing was fine till i wanted to do a upgrade(slackpkg upgrade-all).it said it should remove those packages in order to install new ones and i said to do so. after that, i couldnt use X because it didnt recognize my graphic&mouse&keyboard correctly, then i installed all those packages(testings) to have my X back, but then this happened.
i use windows loader(and easy bcd for adding Slack), when i enter into slack and in LILO i select linux, it goes for decompressing linux and then stops @ ...... .
what should i do now?
i searched a bit and founded that i should ran lilo after upgrade(or install), and thats the solution but how could i do that? i dont have a shell...
Toss in your CD/DVD, boot from that, give the proper parameters to the boot prompt and in the shell, if needed mount and chroot to your root partition, if necessary mount the boot partition as well and re-run lilo.
Welcome to LQ!
The easiest way would be to use Slackware install media to boot the system as if you were going to install.
After you get to the login then from the cli (command line);
Code:
~#mkdir /slacktemp #temporary mount point
~#mount /dev/your_device /slacktemp #device you installed to
~#chroot /slacktemp #change to yours
~#cd /slacktemp/etc #change to directory with lilo.conf
~#vi lilo.conf #edit lilo.conf, if need be
~#lilo -v -t -b /dev/your_device #sda, hda this will only test
~#lilo -v -b /dev/your_device #this will write to your boot device
You can 'man commands' in the above example to get a full understanding of the commands and options.
Quote:
excerpt from 'man lilo'
LILO(8)
NAME
lilo - install boot loader
SYNOPSIS
Main function:
/sbin/lilo - install boot loader
Auxiliary uses:
/sbin/lilo -A - activate/show active partition
/sbin/lilo -E - edit header or update a bitmap file
/sbin/lilo -I - inquire path name of current kernel
/sbin/lilo -M - write a Master Boot Loader on a device
/sbin/lilo -q - query map
/sbin/lilo -R - set default command line for next reboot
/sbin/lilo -T - tell more about specified topic
/sbin/lilo {-u|-U} - uninstall LILO boot loader
DESCRIPTION
lilo installs a boot loader that will be activated the next time you boot your system. The default configuration file /etc/lilo.conf (see
'man lilo.conf') will contain most options, but many, including those
which override the configuration file, may be specified on the command line.
-A master-device [ N ]
Used with a single argument, inquire of active partition on
device master-device; e.g., /dev/hda. With N==0, deactivate all
partitions on the device. With N in the range [1..n], activate
the specified partition and deactivate all others. Normally,
only primary partitions [1..4] may be activated, but if the
Extended Master Boot Loader is present on the Master Boot Record
of the device (see the -M option), any partition may be made
active. Whether the actual OS in the partition will boot from
an extended partition depends on the characteristics of the OS.
LILO boot records for Linux may be booted from an extended par-
tition.
-b bootdev
Specify the boot device; i.e., where the boot loader will be
installed. "-b /dev/hda" specifies the Master Boot Record; "-b
/dev/sdb5" specifies the first extended partition on the second scsi disk.
You should ‘man lilo’ to get the rest for options.
The above link and others available from 'Slackware-Links'. More than just Slackware® links!
EDIT: I experienced network error(s) and when I look at the post it seemed normal. Advanced mode showed font setting @ 3 for WYSIWYG. Why?? What do you guys see now? [obj] was inserted on one line. I did not insert that either.
Edit2: Remove stale link
Last edited by onebuck; 06-20-2011 at 09:55 AM.
Reason: font settings errors. mangle on paste
@OP my apologies for the font & obj errors. I cannot reason as to why. I pasted the links and at the same time experienced a network error. I'll look into this to see why. Should not have experienced this. WYSIWYG advanced mode but the paste should not have changed all font settings. The post looked normal on my system until a preview then all font size were changed to 3. Submit was done. I edited the post to reset things.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.