blank_screen_during_boot:_Suse_7.1_Pro,_Toshiba_Tecra_8000
![](https://seccdn.libravatar.org/avatar/ea4efd96975474e30cc4b92fb3e83bd2.jpg?s=120&d=mm&r=g)
Hi- I just recently installed Suse 7.1 Pro onto a Toshiba Tecra 8000 laptop. The install went fine(in text mode), and the initial screen with TUx on it and the kernel selection list is there: linux, linux_2.4, suse, memtest86. Right now, I'm hitting ESC to boot into text mode as I haven't configured X yet. If I choose any of the 3 kernels listed: linux, linux_2.4 or suse, it goes through the normal startup procedures hw swap fsck mounts timezone syslog boot log pcmcia "all report back with green 'done'". Then : A big fat blank screen! I can hear the harddrive spin up and it blinks on occasion, but all I get is a blinking '_' in the upper left hand corner. No response from the keyboard, and no output is displayed. The BIOS setting are set to the defaults and there are no PCMCIA cards in the system. Crtl-Atl-Del does nothing to the system either. Oh, I can boot off of the floppy and load the rescue system, mount the filesystems(of my installed system), those look OK, lilo.conf looks OK. The 3 kernels are all the same size, sorry, didn't do a 'sum' to verify, the associated initrd's are different sizes, but again, any choice made produces the same result. Any thoughts? Besides: a different computer, newer OS(I have the 7.1 disks and I don't need much on these systems) ;-)) thanks in advace, brian -- Brian Jackson Photography Action Athletics http://www.brianjacksonphoto.com "Excellence in Sports Imagery" 650-218-5082 http://www.actionathletics.com
![](https://seccdn.libravatar.org/avatar/27baa448681c4a5c26d14d8f44fbe635.jpg?s=120&d=mm&r=g)
On Mon, 23 Sep 2002 12:03:09 -0400 (EDT)
"Brian Jackson"
I just recently installed Suse 7.1 Pro onto a Toshiba Tecra 8000 laptop.
If I choose any of the 3 kernels listed: linux, linux_2.4 or suse, it goes through the normal startup procedures
"all report back with green 'done'". Then : A big fat blank screen!
I can hear the harddrive spin up and it blinks on occasion, but all I get is a blinking '_' in the upper left hand corner. No response from the keyboard, and no output is displayed.
Any thoughts? Besides: a different computer, newer OS(I have the 7.1 disks and I don't need much on these systems) ;-))
Thoughts? Yeah. Someone a little while back had some trouble with a monitor, and he fixed it by setting vga = normal instead of the framebuffer, in lilo.conf. Maybe your laptop can't switch from framebuffer to X? Maybe that, and make sure you are using an ascii login instead of the graphical one. Maybe your laptop isn't setup for X properly, and you have a graphical login set, then it just hangs. To be extra safe, edit your /boot/@boot.b to point to boot-text.b instead of boot-menu.b. Try to boot in the most basic way possible to a console prompt, then work on why X is fussy. -- use Perl; #powerful programmable prestidigitation
![](https://seccdn.libravatar.org/avatar/ea4efd96975474e30cc4b92fb3e83bd2.jpg?s=120&d=mm&r=g)
On Mon, 23 Sep 2002 12:03:09 -0400 (EDT) "Brian Jackson"
wrote: I just recently installed Suse 7.1 Pro onto a Toshiba Tecra 8000 laptop.
If I choose any of the 3 kernels listed: linux, linux_2.4 or suse, it goes through the normal startup procedures
"all report back with green 'done'". Then : A big fat blank screen!
I can hear the harddrive spin up and it blinks on occasion, but all I get is a blinking '_' in the upper left hand corner. No response from the keyboard, and no output is displayed.
Any thoughts? Besides: a different computer, newer OS(I have the 7.1 disks and I don't need much on these systems) ;-))
Thoughts? Yeah. Someone a little while back had some trouble with a monitor, and he fixed it by setting vga = normal instead of the framebuffer, in lilo.conf. Maybe your laptop can't switch from framebuffer to X? Maybe that, and make sure you are using an ascii login instead of the graphical one. Maybe your laptop isn't setup for X properly, and you have a graphical login set, then it just hangs.
To be extra safe, edit your /boot/@boot.b to point to boot-text.b instead of boot-menu.b.
Try to boot in the most basic way possible to a console prompt, then work on why X is fussy.
Thanks. Yea, I'm not even worried about X at this point. I know I will have to configure that later. I can't even boot in text mode. lilo.conf has 'vga = normal' (retriece from /dev/hda1 mounted on the rescue system) When I try to boot any of the 3 kernels listed in 'text mode', I get the problem. When the initial LILO screen comes up, I hit 'ESC' to bring up the ASCII LILO screen, then choose the kernel. It attempts to go through a normal startup procedure: fsck, timezone. loopbakc, serial ports, pcmcia, then goes to a blank screen. I think there's some sort of mess up with the PCMCIA initialization. The boot process signifies that the PCMCIA card manager is running reports 'done'. There are no errors reported on the console and I can't get to atl-f10 to see if there are any additional errors. I've tried this with and without a PCMCIA card in the slot. I also get it if I try in GUI mode, but that's to be expected and I don't care about GUI/X mode right now. I just want a "login: " prompt. I've installed linux several times and not had problems like this. Slackware, redhat & suse, but this is the first time trying to get it to run on a laptop. thanks, brian -- Brian Jackson Photography Action Athletics http://www.brianjacksonphoto.com "Excellence in Sports Imagery" 650-218-5082 http://www.actionathletics.com
![](https://seccdn.libravatar.org/avatar/27baa448681c4a5c26d14d8f44fbe635.jpg?s=120&d=mm&r=g)
On Wed, 25 Sep 2002 17:47:01 -0400 (EDT)
"Brian Jackson"
"all report back with green 'done'". Then : A big fat blank screen!
I can hear the harddrive spin up and it blinks on occasion, but all I get is a blinking '_' in the upper left hand corner. No response from the keyboard, and no output is displayed.
Thanks. Yea, I'm not even worried about X at this point. I know I will have to configure that later. I can't even boot in text mode.
I think there's some sort of mess up with the PCMCIA initialization. The boot process signifies that the PCMCIA card manager is running reports 'done'. There are no errors reported on the console and I can't get to atl-f10 to see if there are any additional errors. I've tried this with and without a PCMCIA card in the slot.
I saw this on groups.google.com ########################################################## http://sdb.suse.de/en/sdb/html/pcmcia_keyboardlock.html Another possibility is to disable GPM. If you type 'linuc single' at the LILO prompt you can get into the OS enough to fire up linuxconf and disable GPM from starting. Ups. Something I forgot to mention: If this is the pcmcia problem, you can work around it by random keypresses during boot. Linux then knows that this particular irq is taken and looks for another one. Or you could login using the n #########################################################3 -- use Perl; #powerful programmable prestidigitation
participants (2)
-
Brian Jackson
-
zentara