[debian] unexpected troubles

Neil Jerram neiljerram at googlemail.com
Mon Oct 12 22:22:08 CEST 2009


Hi there...

Is this generally the best place for Debian questions?  Or is
smartphones-userland better?

I've just installed Debian again, and am surprised to be experiencing
some low-level problems.  Hopefully they are easily fixable.

As context, what I'm aiming at is:
- Debian - for the best available package management
- E17 + Illume - for Raster's keyboard, decent launcher and easy
switching between windows
- John Sullivan's fso-el - for performing phone functions from within Emacs.

I've installed e17, and the UI comes up as expected.  I set an overall
scaling factor of 2, to make everything easier to read and press.

The problems I'm seeing now are:

- Load average unreasonably high.  Right now, for example, my top says
"load average: 8.11, 8.13, 8.09".  Yet CPU usage is only reaching
around 6%.

- Emacs never appears, yet can't be killed.  E.g. I clicked on the
launcher icon for Emacs about an hour ago, and nothing has appeared
yet.  "ps waux" shows that there is an emacs process:

root  1579  0.0   3.2   25700  3952 ?       DNs  17:44   0:00 /usr/bin/emacs23

But "kill 1579" and "kill -9 1579" seem to have no effect on this.

- Battery not apparently charging.  I'm using the USB lead from
another Linux computer, which successfully charges OM2009/Paroli and
SHR.  But with Debian there is no + on the battery icon, and no orange
(or blue) light behind the power button.

- ssh (via USB) not working.  The desktop end looks fine:

neil at arudy:~$ netstat -rn
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
192.168.0.0     0.0.0.0         255.255.255.0   U         0 0          0 eth1
192.168.11.0    0.0.0.0         255.255.255.0   U         0 0          0 eth0
0.0.0.0         192.168.11.1    0.0.0.0         UG        0 0          0 eth0

but

neil at arudy:~$ ssh 192.168.0.202 -l root
ssh: connect to host 192.168.0.202 port 22: No route to host

- "shutdown -h now" doesn't work, and so I have no way of shutting
down cleanly.  I get a message saying that the system is going down,
but then nothing else happens.

Can anyone see the cause(s) of these problems and suggest how to fix them?

Thanks,
      Neil



More information about the community mailing list