Re: Inspiron 5000 text-console freezing, somehow linked to X ?
Hello again !
Today I re-entered the contest with the 'freezing console'.
I built some different kernels and wrote a simple 'emergency-shutdown' script
which performs a regular reboot after a predefined amount of time.
At least I can test conditions without filesystem-corruption now.
This is what I found out so far:
'apm: get_event: interface not connected'
is shown up first early at boot-time, before starting any services, no matter
if apm in BIOS is activated or not. Btw i8K says 'Unable to get SMM
Dell-signature / BIOS version'.
I suppose now it's rather not related to the freezing phaenomen.
nikolaj erichsen:
> I have an i8100 and had the same kind of problem, the solution was to
> turn all apic (not acpi) off in the kernel (CONFIG_X86_UP_APIC).
>
> Hope it helps
>
> -->negon
A good hint.
Unfortunateley, on my I5000 it doesn't. I turned all APIC-Options out,
from within menuconfig:
CONFIG-X86_IO=n
CONFIG-X86_LOCAL=n
and one more try with
CONFIG-X86_GOOD=n
which I found only in the .config itself.
Btw i found Symmetric Multiprocessing turned on, but there's only a
Math-Coprozessor built in the PIII. So i turned it off, too. HTR...
Stumbaum, Rainer:
> can you reproduce the error immediately when touching the touchpad???
> I installed gpm and used gpmdata for mouse input in X to solve that issue.
> Good luck
> Rainer
That was a good hint, too.
Originally I disabled gpm by init. I made some tests:
1. Unchanged setting.
After booting into console ( without X and without gpm ):
- Touching the pad didn't harm.
But starting kdm, and back on console, it immediateley produces the 'frost' (
or better 'frust' :).
- Starting gpm works, /dev/gpmdata and the 'runtime' gpmctl seem to be
alright. But after kill gpm, touching the pad freezes.
Setting:
XF86 configures mouse: gpm:
/dev/psaux
( later: gpmdata) /dev/psaux
IMPS/2 autops
repeat-type ms3
(later:append ="_Rms3")
2. With XF86 pointing to gpmdata I started gpm with -Rms3 ( see below ).
It works on console, but in X rather produces trash, so I think it's not the
right -R protocol.
Now, back to console, killing gpm and touching the pad still freezes as usual.
I couldn't manage to find out more yet, and have to leave it for now.
True I don't understand what's going on, but the mouse-device seems to be a
good trace since it could explain why the 'frost' appears together with
starting X.
I feel that the solution is quite near, but I just can't see it.
Perhaps someone else has sharper eyes ?
;-)
> > -----Original Message-----
> > From: mw [mailto:Michael.Wordehoff@gmx.de]
> > Sent: Monday, December 09, 2002 6:22 PM
> > To: debian-laptop@lists.debian.org
> > Subject: Inspiron 5000 text-console freezing, somehow linked to X ?
> >
> >
> > Hello.
> > Ive managed one more step towards a running Woody on my Dell Inspiron
> > 5000....X is working, and I installed many packages last night :)
> >
> > I need to configure now from the text-console,
> > but something wickened happens:
> > After about two minutes from console-login suddenly there's
> > no more input
> > from keyboard possible !
> > Even not the fnar 2--keys or ctrl-alt-Functions including
> > Ctrl-alt--del.
> > I had to turn off power several times and let e2fschk clean
> > up the mess....
> >
> > This didn't occur when I suspended kdm and logged in only a
> > text-console.
> > It seems not to happen 2 - 3 minutes after entering X , and
> > it's sufficient
> > only to reach the kdm-login. ( Package xfree86-common,
> > Version 4.1. 0-16 )
> > Just now I'm writing this letter ( on another box ) I reached
> > a 'frozen'
> > text-console on the lap without any tty-login.
> > So i suppose the 'freezing' happens after entering the
> > kdm-login, and I only
> > recognize it by changing to text-console with ctrl-alt-F1.
> >
> > The problem may be related to error-messages occuring
> > immediateley after
> > login. From different sources, they are:
> >
> > apm:get_event: interface not connected
> > apm:set display: interface not found
> > kernel:apm:set display: interface not connected
> > kernel:apm:set suspend: interface not connected
> >
> >
> > I ran the lap from 'line', without a battery plugged in.
> > Freezing does not depend on APM dis/enabled in BIOS.
> > I did enable APM in the kernel ( 2.4.18 custom ).
> > I installed powermgmt-base, apmd 3.0.2 ( apm-bios 1.2 ),
> > libapm1, and sleepd.
> > But later I suspendet them all. Further on I experimented
> > with the standard
> > kernel-2.2.20 idepci in runlevel 1 ( single ). After starting
> > kdm, the same
> > failure, still no change.
> > I didn't suspend noflushd yet. On several occasions I noticed a short
> > HD-Action the second before the goodbye. I'm not sure if
> > always, however.
> >
> >
> > I feel rather helpless now. Does anybody could give me a hint ?
> >
> >
> > ----------- Settings ( / = some stuff i changed for testing )
> > --------------
> > Dell Inspiron P III 600 mhz / 128 MB / 12 GB
> > Kernel 2.4.18 ( custom ) / Kernel 2.2.20-idepci ( standard )
> >
> > APM compiled in Kernel, but no ACPI
> > BIOS A07: no matter if apm disabled / activated
> >
> > Video:
> > XFree 4.1.0
> > Console is VGA+ 80x25
> > VCI v.100
> > agpgart seems to work properly
> >
> > No PnP-Plugins / PCMCIA-Cards plugged in yet.
> >
> > I installed makedev, and found a char-device /dev/apm_bios,
> > and while I
> > 'touched' it with mc, this conole gets frozen, but i was able
> > to move to
> > another. Few seconds later the whole system freezes 'regularly'....
> To add from the XF86-Log:
> "Cannot shadow an accelerated framebuffer"
> and later "Option UseFBDev not used".
> It's a 8 MB ATI Rage, and in the XF86Config
> i turned FBDev on and DPMS off.
> No errors else.
Reply to: