opensuse 11.4 usb mouse/keyboard does not power down

English Hardware
1

recently i updated from 11.2 64bit to 11.4 64bit and have had a problem with the usb optical mouse and usb keyboard.

scenario:

When i do a normal shutdown: computer/shutdown/shut down the mouse stays ‘on’. in other words, the lamp in the mouse remains lit

The keyboard has the same problem. In normal shutdown the NumLock lamp stays lit.

However, when the computer shuts down of its own accord in power saving mode, the mouse/kb lamps are not lit.

…

I’ve checked a number of forum/google posts but haven’t found anything.

I’ve looked at the Xorg and boot logs but they don’t tell me anything (not that i’m an expert at reading them)

Can someone point me in the right direction?

Thanks.

::::::::Totally unrelated or not:::::::::::

Normally when I upgrade my system I do a total re-install. My ‘/home’ directory sits on a separate drive.

When going from 11.2 to 11.4, I first tried to do just an ‘upgrade’. This failed in that gdm would not start.

I then did a new install. ie format system drive and add ‘/home’ name to drive 2.

On the final config page in the install process, I get a warning that the bootloader may not function. Finished the install and system does boot.

However, I now find that I’ve got two ‘/home’ directories. One on each drive. The one on the system drive is the active one.

:::::::::::::::::::::::

2

That story on the two /home diirectories is a bit strange. You can have but one */home *directory in a system. To get information about that, please post the output of:

fdisk -l

and

cat /etc/fstab

and

mount

(do not forget to put that between CODE tags: Posting in Code Tags - A Guide)

3

First: on your /home: you missed something during upgrading, the option “Import mountpoints” during the partitioning stage of the install. That would have mounted your old /home.
Second: Do you have an xorg.conf in /etc/X11 ? If so, remove/rename it. Then reboot, shutdown and report what happens.

Personally I prefer a clean install instead of upgrading, but these days that should be a matter of taste.

4

to: hcw

result of fdisk, fstab, cat query:

linux:/home/bobert # fdisk -l /dev/sda
Absolute path to 'fdisk' is '/sbin/fdisk', so running it may require superuser privileges (eg. root).
linux:/home/bobert # cd /sbin
linux:/sbin # fdisk -l
Absolute path to 'fdisk' is '/sbin/fdisk', so running it may require superuser privileges (eg. root).

??? – I also Opened nautilus as root and tried to open fdisk. Nothing happened.

linux:/etc # cat /etc/fstab
/dev/disk/by-id/ata-Hitachi_HDT721016SLA380_STA0L7MB1RP5MB-part2 swap                 swap       defaults              0 0
/dev/disk/by-id/ata-Hitachi_HDT721016SLA380_STA0L7MB1RP5MB-part1 /                    ext3       acl,user_xattr        1 1
/dev/disk/by-id/ata-Hitachi_HDT721016SLA380_STA0L7MB1XZS5B-part1 /home                ext3       defaults              1 2
proc                 /proc                proc       defaults              0 0
sysfs                /sys                 sysfs      noauto                0 0
debugfs              /sys/kernel/debug    debugfs    noauto                0 0
usbfs                /proc/bus/usb        usbfs      noauto                0 0
devpts               /dev/pts             devpts     mode=0620,gid=5       0 0

linux:/ # mount
devtmpfs on /dev type devtmpfs (rw,relatime,size=1987888k,nr_inodes=496972,mode=755)
tmpfs on /dev/shm type tmpfs (rw,relatime)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000)
/dev/sda1 on / type ext3 (rw,relatime,errors=continue,user_xattr,acl,commit=15,barrier=1,data=ordered)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
/dev/sdb1 on /home type ext3 (rw,relatime,errors=continue,commit=15,barrier=1,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
gvfs-fuse-daemon on /home/bobert/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,relatime,user_id=1000,group_id=100)
5

"Normally when I upgrade my system I do a total re-install. My ‘/home’ directory sits on a separate drive.

When going from 11.2 to 11.4, I first tried to do just an ‘upgrade’. This failed in that gdm would not start.

**I then did a new install. ie format system drive and add ‘/home’ name to drive 2. **

On the final config page in the install process, I get a warning that the bootloader may not function. Finished the install and system does boot.

However, I now find that I’ve got two ‘/home’ directories. One on each drive. The one on the system drive is the active one."

Second: Do you have an xorg.conf in /etc/X11 ? If so, remove/rename it. Then reboot, shutdown and report what happens.

No xorg.conf only xorg.conf.install

6

I asked for

fdisk -l

not for

fdisk -l /dev/sda

Is it difficult to do a copy/past? I forgot to tell you to be root doing this. Well fdisk told you, but you did not become root to solve this (BTW I do not understand your prompt here, did you change that to your own whish?).

In any case, what I see is that* /dev/sda1 i*s mounted on */ *and that */dev/sdb1 is mounted on /home. That is not only the situation when you executed the mount statement, but it is also as it should be after boot as your /etc/fstab *shows.

Thus my conclusion is that you are again/still using the* /home on /dev/sdb1* that you inherited from the earlier instllation. As this is what I assume that you intended to do, I wonder what the problem is. Did you loose your personal documents, pictures, music, other files after the reinstall? You do not complain about that, but that would be the symptom if you now would have a fresh home directory in another /home.

I cite you:

However, I now find that I’ve got two ‘/home’ directories. One on each drive. The one on the system drive is the active one.

As I said earlier, I can not believe this. Can you please illustrate this with computer output? Or tell us otherwise how you come to this conclusion?

7

Is it difficult to do a copy/past? I forgot to tell you to be <em>root</em> doing this. Well <em>fdisk</em> told you, but you did not become <em>root</em> to solve this .

  1. opened a terminal
  2. key in: gnomesu
  3. enter root password
  4. results as shown:

linux:/home/bobert # cd /sbin
linux:/sbin # fdisk -l
Absolute path to 'fdisk' is '/sbin/fdisk', so running it may require superuser privileges (eg. root).<br>

(BTW I do not understand your prompt here, did you change that to your own whish?)

no, copied directly from terminal. used same method for fstab and mount.

However, I now find that I’ve got two ‘/home’ directories. One on each drive. The one on the system drive is the active one.

As I said earlier, I can not believe this. Can you please illustrate this with computer output? Or tell us otherwise how you come to this conclusion?

I tried to upload a screenshot of the directory structure with no success.

Here is a text version:


Nautilus: Filesystem
(name, location, owner)
bin  /  root
boot / root
dev / root
etc / root
home / root
  bin  /home root
  bobert /home user
  boot /home root
  dev /home root
  etc /home root
  home /home root
    bobert /home/home user
  lib  /home root
  lib64 /home root
  lost+found  /home root
  media, mnt, opt, proc, root, sbin, selinux, srv, sys, tmp, usr, var  /home root
lib  /  root
lib64  /  root
lost+found  /  root
media, mnt, opt, proc, root, sbin, selinux, srv, sys, tmp, usr, var  / root

.

8 

linux:/ # whereis fdisk
fdisk: /sbin/fdisk /usr/share/man/man8/fdisk.8.gz
linux:/ # /sbin/fdisk -l

Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders, total 312581808 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00074a77

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *          63   308287349   154143643+  83  Linux
/dev/sda2       308287350   312576704     2144677+  82  Linux swap / Solaris

Disk /dev/sdb: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders, total 312581808 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000854ce

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1              63   312576704   156288321   83  Linux

I’ve got 2 /sbin. Don’t know why.

9

It is either

gnomesu <terminal emulator of your choice>

which will ask for the root password and then start the terminal emulator of your choice in a new window and give you a root prompt.
Or

su -

in a terminal window, which will ask for the root password and then show a root prompt in the same window.

And yes, when it says that it is in* /sbin*, you can call this with /sbin/fdisk (this however is not needed when you are root using one of the methods described above, because then* /sbin* is in your* PATH*).

The use of Nautilus or any GUI oriented file manager is not what I would use to inspect my file tree as a system manager. But from what I guess to see there, it seems that you have succeeded in copying everything in / to /home. Thus now you probably have a /sbin and a /home/sbin (these are NOT two /sbin, because that is impossible).

To check that give us the contents of the two directories

ls -l /

and

ls -l /home
10 
linux:/home/bobert # ls -l /
total 104
drwxr-xr-x   2 root root  4096 Aug 12 20:17 bin
drwxr-xr-x   3 root root  4096 Aug 13 07:08 boot
drwxr-xr-x  17 root root  4060 Aug 17 06:16 dev
drwxr-xr-x 119 root root 12288 Aug 17 06:15 etc
drwxr-xr-x  23 root root  4096 Aug 16 18:04 home
drwxr-xr-x  13 root root  4096 Aug 16 12:08 lib
drwxr-xr-x  10 root root 12288 Aug 16 12:08 lib64
drwx------   2 root root 16384 Aug 12 19:26 lost+found
drwxr-xr-x   2 root root  4096 Aug 12 21:08 media
drwxr-xr-x   2 root root  4096 Feb 18 22:35 mnt
drwxr-xr-x   2 root root  4096 Feb 18 22:35 opt
dr-xr-xr-x 164 root root     0 Aug 17 06:15 proc
drwx------  16 root root  4096 Aug 17 07:22 root
drwxr-xr-x   3 root root 12288 Aug 12 20:18 sbin
drwxr-xr-x   2 root root  4096 Feb 18 22:35 selinux
drwxr-xr-x   4 root root  4096 Mar  2 12:45 srv
drwxr-xr-x  12 root root     0 Aug 17 06:15 sys
drwxrwxrwt  29 root root  4096 Aug 17 07:21 tmp
drwxr-xr-x  13 root root  4096 Mar  2 12:45 usr
drwxr-xr-x  15 root root  4096 Mar  2 12:52 var



linux:/home/bobert # ls -l /home
total 152
drwxr-xr-x   2 root   root   4096 Aug 12 10:21 bin
drwxr-xr-x  44 bobert users  4096 Aug 17 06:16 bobert
drwxr-xr-x   3 root   root   4096 Aug 12 11:40 boot
drwxr-xr-x   2 root   root   4096 Aug 12 11:39 dev
drwxr-xr-x 126 root   root  12288 Aug 12 12:03 etc
drwxr-xr-x   3 root   root   4096 Feb 18 22:35 home
drwxr-xr-x  13 root   root   4096 Aug 12 10:21 lib
drwxr-xr-x  10 root   root  12288 Aug 12 10:28 lib64
drwx------   2 root   root  16384 May 31  2010 lost+found
drwxr-xr-x   2 root   root   4096 Feb 18 22:35 media
drwxr-xr-x   2 root   root   4096 Feb 18 22:35 mnt
drwxr-xr-x   2 root   root   4096 Feb 18 22:35 opt
drwxr-xr-x   3 root   root   4096 May 31  2010 proc
drwx------  21 root   root   4096 Aug 12 11:02 root
drwxr-xr-x   3 root   root  12288 Aug 12 10:28 sbin
drwxr-xr-x   2 root   root   4096 Feb 18 22:35 selinux
drwxr-xr-x   4 root   root   4096 Feb 18 22:35 srv
-rw-r--r--   1 root   root      0 Aug 12 12:03 success
drwxr-xr-x   3 root   root   4096 May 31  2010 sys
drwxrwxrwt 678 root   root  36864 Aug 12 12:03 tmp
drwxr-xr-x  13 root   root   4096 Aug 12 10:07 usr
drwxr-xr-x  15 root   root   4096 Aug 12 10:07 var
11

Yes, for some reason. inexplicable to me, you have copied all of your* / *into your /home. It looks as if all those are the result of a install done at Aug 12 that was finished at about 12:03. It also seems that you did the install you are now using at the same day at about 20:17. Maybe you remember what you did then.

It does not hurt, but it takes space on disk.

Now to remove these be VERY carefully not to remove the wrong things.

Start a terminal and do

su -

(mind the -) and enter the root password. Then make /home your working directory:

cd /home

To remove every one of the directories with their contents you do the following for all of them, but NOT for bobert and NOT for* lost+found*!

rm -rf bin

for bin and so on (but I repeat: NOT for bobert and* lost+found*). Again, take care, you are in* /home* and do not type any /s in those rm statements.

Wishing you sucess. I am going for a holliday until September 1, thus I will only read your next post in September, but others here will help you when you have more questions.

And a small suggestion: try to read something about the Unix/Linux file system tree, how to address files using absolute or relative pathes and what the PATH environment variable does. You may then better understand what you see on your system and why I say that you can not have two /sbin.

12

On that date I first tried to do an upgrade from v11.2 to v11.4. The upgrade did not go well. The desktop mgr (gdm) would not fire up. So then I chose to do a new install fomatting the / drive and naming the second drive to /home. On the configuration page I got a warning msg that grub may have problems because of where it was being loaded in memory (I don’t remember the verbage precisely). I accepted the configuration. 11.4 loaded without problems. That is the whole story.

linux:/home # ls
bobert  lost+found  success
linux:/home # cd /
linux:/ # ls
bin   dev  home  lib64       media  opt   root  selinux  sys  usr
boot  etc  lib   lost+found  mnt    proc  sbin  srv      tmp  var

Thank you for your help and your patience. I’ve learned a lot. :slight_smile: