LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Black screen at boot after installpkg modules in a slack11 - huge26 (http://www.linuxquestions.org/questions/slackware-14/black-screen-at-boot-after-installpkg-modules-in-a-slack11-huge26-535199/)

Helice 03-06-2007 05:46 PM

blank screen on boot . how to debug conflict module?
 
Hi. I have installed a Slackware 11 from DVD with huge26 option in a toshiba A100 Laptop (Core 2 Duo, chipset Intel® 945PM Express, nvidia gforce go 7300).

When i finished the installation the system boots OK.
But when i installpkg the module-i486 of extras folder and reboot, the system hangs with a blank screen before the login prompt are showed.

If i try to boot with the option nohotplug (editing grub) the system boot ok to the login prompt again.

I think that there is a problem with some module but i dont know how ca i debug it and disable the wrong module.

Thanks a lot.

H_TeXMeX_H 03-06-2007 06:04 PM

check:

http://www.linuxquestions.org/questi...ight=blacklist

Helice 03-07-2007 07:37 AM

Thanks.

I check the post but i don't have necessary knowledge to determine the module that hang my slack.

these is the content of /lib/modules/2.6.17.13

build modules.dep modules.ofmap modules.usbmap
kernel modules.ieee1394map modules.pcimap source
modules.alias modules.inputmap modules.seriomap
modules.ccwmap modules.isapnpmap modules.symbols

Are all of these files loading modules???

Very hard to find the issue to me.

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).

onebuck 03-07-2007 08:32 AM

Hi,

After boot, just look at dmesg and syslogs. You should see any errors or problems.

edit: of course after you log on to the system.

Helice 03-07-2007 09:29 AM

blank screen on boot . how to debug conflict module?
 
Quote:

Originally Posted by onebuck
Hi,

edit: of course after you log on to the system.

Thanks.

:( bad news. I understand if the system are hanged before the boot prompt i can't get the messages into the files that you said me.

There is another method????

---------
It is normal that /etc/rc.d/rc.modules points to rc.modules-2.4.33.3???

Is a 2.6.17.13 system (huge26 during installation) (i can confirm with uname)

Edit: I tried to change the link to rc.modules-2.6.17.13 but doesn't works (same problem, blank screen).

H_TeXMeX_H 03-07-2007 04:13 PM

all the modules are in '/lib/modules/`uname -r`/kernel'

onebuck 03-07-2007 04:38 PM

Quote:

Originally Posted by Helice
Thanks.

:( bad news. I understand if the system are hanged before the boot prompt i can't get the messages into the files that you said me.

There is another method????

---------
It is normal that /etc/rc.d/rc.modules points to rc.modules-2.4.33.3???

Is a 2.6.17.13 system (huge26 during installation) (i can confirm with uname)

Edit: I tried to change the link to rc.modules-2.6.17.13 but doesn't works (same problem, blank screen).

Hi,

Do you mean the login prompt? If the system is hanging at the boot then I would suspect a file system error. Give use some information. Do you get a kernel panic?

Did you install all the modules for the huge26 from /testing? Read the Release notes.

If the system boots and you can login then the dmesg & syslogs are there.

Code:

#dmesg >mydmesg            #will direct the stdout to file
#ls /var/log              #will list the log files

You can redirect the output to a shared file, floppy or flash to allow a post.

Helice 03-07-2007 05:14 PM

Thanks all by answer.

Quote:

all the modules are in '/lib/modules/`uname -r`/kernel'
Ok. I tried to disable sony_acpi (read in the forum) but doesnt work.

Quote:

Originally Posted by onebuck
Hi,

Do you mean the login prompt? If the system is hanging at the boot then I would suspect a file system error. Give use some information. Do you get a kernel panic?

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.

Quote:

Originally Posted by onebuck

If the system boots and you can login then the dmesg & syslogs are there.

Code:

#dmesg >mydmesg            #will direct the stdout to file
#ls /var/log              #will list the log files

You can redirect the output to a shared file, floppy or flash to allow a post.

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.

onebuck 03-07-2007 07:34 PM

Quote:

Originally Posted by Helice
Thanks all by answer.

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.

Hi,

I suggest that you use the Slackware install cd1 to boot then;

Code:

#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.

Helice 03-09-2007 09:44 AM

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.

The partition configuration was:

sda1 windows - primary
sda2 Ubuntu - primary
sda3 Slack - logical
sda4 swap - logical

I deleted the two logical partitions and remake it how Primary. Gentoo finally works.

Well. I understand that you cant boot from a logical partition.

In the nex days i will try slack to kwon if work with primary partition type.

Thanks all by your help.

Helice 03-12-2007 09:24 AM

Finally, when i have a system working i recompiled the Kernel and i have the same issue again.

I d'ont understand. I read a lot of documents and SATA drivers and all filesystem are selected in menuconfig.

what happends????

duryodhan 03-12-2007 09:56 AM

did you install kernel-modules-2.6.17.13-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.


All times are GMT -5. The time now is 07:34 AM.