Black screen at boot after installpkg modules in a slack11 - huge26
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Can i put the boot screen messages in a file in order to inspect them when the computer hungs, so that I can access the last line the boot was working with before it hunged? (when the computer are hunged i cant read the messages because the screen turns to black).
Ok. I tried to disable sony_acpi (read in the forum) but doesnt work.
Yes. blank screen before login prompt. No kernel panic. I can boot with NOHOTPLUG editing menu.lst (GRUB) and i can use the filesystem.
More information. A lot of messages scrolling at the screen before the black screen. I can see lot of raid, Acpi, usb, bla bla bla but i cant see the last line before the system hang.
I cant login. The dmesg & syslogs files have only the information if i use the NOHOTPLUG. No relevant messages i think.
i spend a lot of hours but i cant use this slack version.
Thanks again guys.
I suggest that you use the Slackware install cd1 to boot then;
#mkdir /slacktmp #tmp mount point
#mount /dev/hda# /slacktmp #mount the Slack /
#/dev/hda# change to yours
#chroot /slacktmp #chroot
#cd /slacktmp #change too /
#ls /slacktmp/var/log #will list the logs
;you will need to look at dmesg & syslog. These should be the last boot information.
You can now copy, redirect or just capture the logs to post them thus allowing us too diagnosis the problem.
Well. The files dont have information about the hang boot. The system only fill new information when i boot with NOHOTPLUG option. I think not necessary post this information because there is not errors.
Finally i unistalled SLACK and try with Gentoo. Same problem but instead of black screen i receive a kernel panic. Cant access to root partition.
Distribution: Slackware 12 Kernel 2.6.24 - probably upgraded by now
did you install kernel-modules-220.127.116.11-i486-1.tgz ? or any other file?
Try the 2.6.18 kernel in /testing of the DVD. That generally works well for me.
Try booting to single user mode. Add the word single to what you are booting to.
e.g if you select linux in lilo , then automatically the text linux is displayed. Press space and type 'single' and then press enter. then maybe you can log in.
To disable the module you want just change the appropriate rc.modules file.
I am still not clear on your exact problem so can't help you much. Could post the problem you are FACING NOW clearly with all the logs? If you can't log in then write down the logs , or open /var/logs from another distro. ... but we need the logs.