LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   Shutdown trouble Slackware 12 (https://www.linuxquestions.org/questions/linux-newbie-8/shutdown-trouble-slackware-12-a-597937/)

sr_25 11-07-2007 10:40 PM

Shutdown trouble Slackware 12
 
If I don't startx I can switch to virtual consoles and reboot or shutdown my Slackware 12 laptop without a hitch. After starting X I cannot shutdown, logoff, reboot, or swap to another virtual console. I am currently using KDE and if I select 'log out' via the menu
or
Code:

'ctlr-alt-backspace' or 'shutdown -r now', or 'shutdown -h now'
I just get a black screen with my mouse pointer.

I don't know if the virtual consoles is related or not but I thought I should mention it. I am currently using vesa driver.

Thanks for you time.

Tinkster 11-08-2007 01:59 AM

What chipset have you got, does your fullscreen console use
framebuffer?


Cheers,
Tink

sr_25 11-08-2007 08:25 PM

This is a junker laptop I mess around with it's an old Compaq Presario 700.

The motherboard chipset is a VIA VT8364(A) Apollo KL133(a) / BT8365(A) ProSavage KM133, with a S3 Graphics Twister K Compaq (16MB).

edit/
Sorry, how do I tell if I am using 'fullscreen console framebuffer'. I did a search but I still don't know how to tell.

Tinkster 11-08-2007 09:01 PM

Do you get a little tux in the top left corner when you boot? :)


Cheers,
Tink

sr_25 11-08-2007 09:06 PM

No little tux a boot.
Thanks,

Tinkster 11-09-2007 02:07 AM

When you set-up lilo, did you explicitly choose not to
have frame-buffer mode enabled?


Cheers,
Tink

sr_25 11-09-2007 11:35 AM

I like grub better so that is what I am using.

/edit
Here are the commands that were auto configured:

Code:

title Slackware 12 (/dev/hda7)
root (hd0,6)
kernel /boot/vmlinuz root=/dev/hda7 ro vga=normal


sr_25 11-10-2007 11:39 AM

Is there some basic method to help track down the problem I am having here I don't even know where to begin.

I looked in /var/log/syslog: and found a few things that look amiss but couldn't find out how to fix them.

Code:

kernel: vt596+smbus 0000:000"07.4: smbus: error: host smbus controller not enabled: upgrade BIOS or use force-l
kernel: failed initialization of WD-700 SCSI card!
kernel: via 686 0000:000:07.4: Base address not set-upgrade BIOS or use force_addr=oxaddr
kernel: kobject_add failed uhci_hcd with -EEXIST, don't try to register things with the same name in the same dire$
sshd[2758]: error: Bind to part 22 on 0.0.0.0 failed: address already inuse.

"force-l" where do I need to use this option?
I believe I am using the latest BIOS but I will double check.
"...-EEXIST..." Sounds like Kde is not quite configured correctly?

Also, because of the black screen lockup I always have to press and hold the power button to get a reboot. I am worried that one of these times it will hose my system! Maybe I should go back to 10.2 because I don't remember any of these issues with that version. Also, I think Slackware 10.2 was quite a bit more responsive on this old clunker, but I havent done any testing to prove it.

Thanks for you help so far.

brianL 11-10-2007 02:00 PM

All those -EEXIST messages are from using the huge-smp kernel. After installation it's recommended that you change to the generic-smp kernel.
See the README.initrd in /boot.


All times are GMT -5. The time now is 07:38 PM.