Reboot breaks things
Hi! My SUSE 10.0 won't work properly when I do a reboot. USB keyboard and mouse won't work, My PCMCIA network adapter lights up but won't do much else... When I reboot from WinXP to SUSE or WinXP, everything works. Rebooting from SUSE to XP or SUSE doesn't work. SUSE -> SUSE = failure SUSE -> XP = failure XP -> SUSE = success XP -> XP = success I have tried both with Grub and lilo, with the same results. I have attached "boot.msg" from a "good" and a "bad" boot. Any help would be greatly appreciated! Kind regards, Jan K. -- Just because you are a character, doesn't mean you have character... http://www.fmbv.nu ------------------------------------------------------- -- Just because you are a character, doesn't mean you have character... http://www.fmbv.nu
On Wednesday 02 November 2005 3:43 pm, Jan Karjalainen wrote:
Hi! My SUSE 10.0 won't work properly when I do a reboot. USB keyboard and mouse won't work, My PCMCIA network adapter lights up but won't do much else... When I reboot from WinXP to SUSE or WinXP, everything works. Rebooting from SUSE to XP or SUSE doesn't work.
SUSE -> SUSE = failure SUSE -> XP = failure XP -> SUSE = success XP -> XP = success One question, does your mouse and or keyboard work on the login screen? You can always go to one of the virtual terminals.
Initially, my desktop system (came with USB KB+Mouse) used a KVM so I could share it with the ancient Deskpro. When excised the KVM, SuSE actually recognized it, bit not Windows. I use XP only to install mandatory updates and to install an update to my Treo650 that was Windows only. I suggest that you run YaST/Hardware/Graphics Card and Monitor, open Input devices, change configuration and finalize on both your keyboard and mouse. Or, from the Hardware tab, go directly to Mouse or keyboard layout. The reason to do this is to check and reset the settings. ----------------------------------------------------------------- If your keyboard and mouse work in a virtual terminal (assuming GPM is enabled) and not in KDE or GNOME, then the YaST "Graphics Card and Monitor" (which is SaX2) might fix the problem. If the Keyboard and Mouse are simply dead on the reboot, then there might be a problem either with the drivers or with the mother board. One question, when you do a reboot, are you doing a soft reboot - shutdown -r (or the reboot button). What happens if you power off and power on in the:
SUSE -> SUSE = failure SUSE -> XP = failure
-- Jerry Feldman <gaf@blu.org> Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9
On Wednesday 02 November 2005 22:11, Jerry Feldman wrote:
On Wednesday 02 November 2005 3:43 pm, Jan Karjalainen wrote:
Hi! My SUSE 10.0 won't work properly when I do a reboot. USB keyboard and mouse won't work, My PCMCIA network adapter lights up but won't do much else... When I reboot from WinXP to SUSE or WinXP, everything works. Rebooting from SUSE to XP or SUSE doesn't work.
SUSE -> SUSE = failure SUSE -> XP = failure XP -> SUSE = success XP -> XP = success
One question, does your mouse and or keyboard work on the login screen? You can always go to one of the virtual terminals.
USB keyboard (and mouse) works in Grub menu, but stops working after that. I have a KVM which have worked perfectly under WinXP, Win2k3, Win2k, Suse 9.3 Pro and Suse 10.0 (except during reboot from 10.0).
---------------------------------------------------------------- Initially, my desktop system (came with USB KB+Mouse) used a KVM so I could share it with the ancient Deskpro. When excised the KVM, SuSE actually recognized it, bit not Windows. I use XP only to install mandatory updates and to install an update to my Treo650 that was Windows only.
I suggest that you run YaST/Hardware/Graphics Card and Monitor, open Input devices, change configuration and finalize on both your keyboard and mouse. Or, from the Hardware tab, go directly to Mouse or keyboard layout. The reason to do this is to check and reset the settings. ----------------------------------------------------------------- If your keyboard and mouse work in a virtual terminal (assuming GPM is enabled) and not in KDE or GNOME, then the YaST "Graphics Card and Monitor" (which is SaX2) might fix the problem.
If the Keyboard and Mouse are simply dead on the reboot, then there might be a problem either with the drivers or with the mother board.
One question, when you do a reboot, are you doing a soft reboot - shutdown -r (or the reboot button). What happens if you power off and power on in
the:
SUSE -> SUSE = failure SUSE -> XP = failure
If I power off (interrupt the reboot), then everything works perfectly! With Suse 9.3 Pro I didn't have this problem. Although I think that Suse 10.0 doesn't reboot as "heavily" as WinXP or Suse 9.3 does. With "heavily" I mean that rebooting from XP, the machine really halts for a second (enough to trigger the power saving on my monitor). Rebooting from 10.0 it kind of skips the "halt" and goes to Grub much quicker than when rebooting from XP (or Suse 9.3). -- Just because you are a character, doesn't mean you have character... http://www.fmbv.nu
On Wednesday 02 November 2005 4:28 pm, Jan Karjalainen wrote:
USB keyboard (and mouse) works in Grub menu, but stops working after that. I have a KVM which have worked perfectly under WinXP, Win2k3, Win2k, Suse 9.3 Pro and Suse 10.0 (except during reboot from 10.0). Try removing the KVM from the mix. Is this a USB KVM? -- Jerry Feldman <gaf@blu.org> Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9
On Wednesday 02 November 2005 22:37, Jerry Feldman wrote:
On Wednesday 02 November 2005 4:28 pm, Jan Karjalainen wrote:
USB keyboard (and mouse) works in Grub menu, but stops working after that. I have a KVM which have worked perfectly under WinXP, Win2k3, Win2k, Suse 9.3 Pro and Suse 10.0 (except during reboot from 10.0).
Try removing the KVM from the mix. Is this a USB KVM?
It's a PS/2 KVM. It won't matter what I try, USB or KVM (via PS/2 -> USB adapter), it just won't work after a reboot from Suse 10.0. Network also won't work, although I got green light on "link" and "speed". Restarting services doesn't help either, and overall the system just feel totally weird, kinda slowish and drunk(?), like it's having really hard to focus on what it's supposed to do! ;-) /Jan K. -- Just because you are a character, doesn't mean you have character... http://www.fmbv.nu
On Wednesday 02 November 2005 4:51 pm, Jan Karjalainen wrote:
It's a PS/2 KVM. It won't matter what I try, USB or KVM (via PS/2 -> USB adapter), it just won't work after a reboot from Suse 10.0. Network also won't work, although I got green light on "link" and "speed". Restarting services doesn't help either, and overall the system just feel totally weird, kinda slowish and drunk(?), like it's having really hard to focus on what it's supposed to do! ;-) I think I am out of ideas at the moment, but it looks like the problem is with the PCI bus itself. You mentioned: I think that Suse 10.0 doesn't reboot as "heavily" as WinXP or Suse 9.3 does. But, since you shutdown from SuSE 10, and XP also fails to boot, the issue would appear that there is something that SuSE 10 is not doing during shutdown that SuSE 9.3 and Windows XP does. We also note that a power off reboot does work. This would indicate to me that we are not resetting the bus properly in SuSE 10. Additionally, when SuSE 10 shuts down, are there any error messages?
What happens if on a reboot, you jump into the BIOS and then exit without saving. -- Jerry Feldman <gaf@blu.org> Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9
On Wednesday 02 November 2005 23:04, Jerry Feldman wrote:
On Wednesday 02 November 2005 4:51 pm, Jan Karjalainen wrote:
It's a PS/2 KVM. It won't matter what I try, USB or KVM (via PS/2 -> USB adapter), it just won't work after a reboot from Suse 10.0. Network also won't work, although I got green light on "link" and "speed". Restarting services doesn't help either, and overall the system just feel totally weird, kinda slowish and drunk(?), like it's having really hard to focus on what it's supposed to do! ;-)
I think I am out of ideas at the moment, but it looks like the problem is
with the PCI bus itself. You mentioned:
I think that Suse 10.0 doesn't reboot as "heavily" as WinXP or Suse 9.3 does.
But, since you shutdown from SuSE 10, and XP also fails to boot, the issue would appear that there is something that SuSE 10 is not doing during shutdown that SuSE 9.3 and Windows XP does. We also note that a power off reboot does work. This would indicate to me that we are not resetting the bus properly in SuSE 10. Additionally, when SuSE 10 shuts down, are there any error messages?
What happens if on a reboot, you jump into the BIOS and then exit without saving.
Same disappointing results... Well, I'm off to bed now, I have to continue with this problem tomorrow! /Jan K. -- Just because you are a character, doesn't mean you have character... http://www.fmbv.nu
On Wednesday 02 November 2005 03:43 pm, Jan Karjalainen wrote:
Hi! My SUSE 10.0 won't work properly when I do a reboot. USB keyboard and mouse won't work, My PCMCIA network adapter lights up but won't do much else... When I reboot from WinXP to SUSE or WinXP, everything works. Rebooting from SUSE to XP or SUSE doesn't work.
SUSE -> SUSE = failure SUSE -> XP = failure XP -> SUSE = success XP -> XP = success
I have tried both with Grub and lilo, with the same results. I have attached "boot.msg" from a "good" and a "bad" boot.
Any help would be greatly appreciated!
I think you have a problem with ACPI The following statements were in your GOOD boot but NOT in the BAD boot: <notice>startproc: execve (/usr/sbin/acpid) [ /usr/sbin/acpid ], [ CONSOLE=/dev/console ROOTFS_FSTYPE=reiserfs TERM=linux SHELL=/bin/sh ROOTFS_FSCK=0 LC_ALL=POSIX INIT_VERSION=sysvinit-2.85 REDIRECT=/dev/tty1 COLUMNS=158 PATH=/sbin:/usr/sbin:/bin:/usr/bin:/lib/klibc/bin RUNLEVEL=5 PWD=/ SPLASHCFG=/etc/bootsplash/themes/SuSE/config/bootsplash-1280x1024.cfg PREVLEVEL=N LINES=59 HOME=/ SHLVL=2 BOOT_IMAGE=Linux splash=silent SPLASH=yes ROOTFS_BLKDEV=/dev/root _=/sbin/startproc DAEMON=/usr/sbin/acpid ] acpid: loading ACPI modules ( ac battery button ) done Starting acpid done <notice>startproc: execve (/usr/sbin/powersaved) [ /usr/sbin/powersaved -d -f /var/run/acpid.socket -v 3 ], [ CONSOLE=/dev/console ROOTFS_FSTYPE=reiserfs TERM=linux SHELL=/bin/sh ROOTFS_FSCK=0 LC_ALL=POSIX INIT_VERSION=sysvinit-2.85 REDIRECT=/dev/tty1 COLUMNS=158 PATH=/sbin:/usr/sbin:/bin:/usr/bin:/lib/klibc/bin RUNLEVEL=5 PWD=/ SPLASHCFG=/etc/bootsplash/themes/SuSE/config/bootsplash-1280x1024.cfg PREVLEVEL=N LINES=59 HOME=/ SHLVL=2 BOOT_IMAGE=Linux splash=silent SPLASH=yes ROOTFS_BLKDEV=/dev/root _=/sbin/startproc DAEMON=/usr/sbin/powersaved ] Starting powersaved (accessing ACPI events over acpid) done Notice the "loading ACPI modules" and "Starting acpid". I don't think you will find these in the bad boot. You can try turning ACPI off... and booting. That would be acpi=off on the kernel line. But you could also boot with the 'failsafe' mode and see what that gets you. Why it would load in one case and not the other I don't know but I suspect XP has something to do with it. What happens if you boot to SUSE from a turned-off machine?
On Wednesday 02 November 2005 23:56, Bruce Marshall wrote:
On Wednesday 02 November 2005 03:43 pm, Jan Karjalainen wrote:
Hi! My SUSE 10.0 won't work properly when I do a reboot. USB keyboard and mouse won't work, My PCMCIA network adapter lights up but won't do much else... When I reboot from WinXP to SUSE or WinXP, everything works. Rebooting from SUSE to XP or SUSE doesn't work.
SUSE -> SUSE = failure SUSE -> XP = failure XP -> SUSE = success XP -> XP = success
I have tried both with Grub and lilo, with the same results. I have attached "boot.msg" from a "good" and a "bad" boot.
Any help would be greatly appreciated!
I think you have a problem with ACPI
The following statements were in your GOOD boot but NOT in the BAD boot:
<notice>startproc: execve (/usr/sbin/acpid) [ /usr/sbin/acpid ], [ CONSOLE=/dev/console ROOTFS_FSTYPE=reiserfs TERM=linux SHELL=/bin/sh ROOTFS_FSCK=0 LC_ALL=POSIX INIT_VERSION=sysvinit-2.85 REDIRECT=/dev/tty1 COLUMNS=158 PATH=/sbin:/usr/sbin:/bin:/usr/bin:/lib/klibc/bin RUNLEVEL=5 PWD=/ SPLASHCFG=/etc/bootsplash/themes/SuSE/config/bootsplash-1280x1024.cfg PREVLEVEL=N LINES=59 HOME=/ SHLVL=2 BOOT_IMAGE=Linux splash=silent SPLASH=yes ROOTFS_BLKDEV=/dev/root _=/sbin/startproc DAEMON=/usr/sbin/acpid ] acpid: loading ACPI modules ( ac battery button ) done Starting acpid done <notice>startproc: execve (/usr/sbin/powersaved) [ /usr/sbin/powersaved -d -f /var/run/acpid.socket -v 3 ], [ CONSOLE=/dev/console ROOTFS_FSTYPE=reiserfs TERM=linux SHELL=/bin/sh ROOTFS_FSCK=0 LC_ALL=POSIX INIT_VERSION=sysvinit-2.85 REDIRECT=/dev/tty1 COLUMNS=158 PATH=/sbin:/usr/sbin:/bin:/usr/bin:/lib/klibc/bin RUNLEVEL=5 PWD=/ SPLASHCFG=/etc/bootsplash/themes/SuSE/config/bootsplash-1280x1024.cfg PREVLEVEL=N LINES=59 HOME=/ SHLVL=2 BOOT_IMAGE=Linux splash=silent SPLASH=yes ROOTFS_BLKDEV=/dev/root _=/sbin/startproc DAEMON=/usr/sbin/powersaved ] Starting powersaved (accessing ACPI events over acpid) done
Notice the "loading ACPI modules" and "Starting acpid". I don't think you will find these in the bad boot.
You can try turning ACPI off... and booting. That would be acpi=off on the kernel line.
But you could also boot with the 'failsafe' mode and see what that gets you.
Why it would load in one case and not the other I don't know but I suspect XP has something to do with it.
What happens if you boot to SUSE from a turned-off machine?
When I boot Suse 10.0 from a turned-off machine, everything works great until I reboot it. Then it fails again... I tried with acpi=off and it seems to reboot nicely. Something's wrong with acpi, then... -- Just because you are a character, doesn't mean you have character... http://www.fmbv.nu
participants (3)
-
Bruce Marshall -
Jan Karjalainen -
Jerry Feldman