[ Date Index ][
Thread Index ]
[ <= Previous by date /
thread ]
[ Next by date /
thread => ]
You may be tired of this thread but take heart -- this may be the last. Skip to the end for details. On Tue, Nov 16, 2004 at 11:37:49PM +0000, Neil Williams wrote:
If the keyboard works in a console login and doesn't in a graphical login, the problem is in the X server config.
There's nothing wrong with XF86Config-4. Logically I agree that X is involved somehow.
... concerned about the behaviour of the wireless adaptor.
The wireless adapter is fine; I tried it on another PC.
... a problem with your ADSL connection.
I run a PC connected 24/7 on a DC project and ADSL drops only very rarely. On this occasion the connection dropped and the keyboard locked but logically I don't know what caused what; I know the ping failure came first.
... there's nothing flaky about Debian stable.
Mm. Maybe so (and I am using debian testing) but I am trying to do a standard install on a very ordinary PII and all I get is problems.
You can set the IP of the box in /etc/network/interfaces
I might do that later. Meanwhile I'd prefer to have eth0 switched off.
Solve the IP problem first. Using Ctrl-C is more likely to cause problems with the rest of the setup as you can end up with some parts of the setup incomplete.
Yes, I thought of that but letting dhcp run out of time led to the same result. Also I did what you suggested and asked google for 'debian keyboard' which brought up a thread in www.linuxquestions.org from Feb 2002 where people had the keybaord lock up. One guy did CTRL-ALT-F1, then went back to X and when kdm loaded the keyboard locked. None found the cause but he eventually re-installed and it was ok. Another guy said that he dropped kdm and installed xdm and that fixed it. So I commented 'auto eth0' out, removed kdm and installed xdm. Big mistake. The keyboard still locked but there is no escape route from xdm so I was in zugzwang. After some hours with a rescue floppy I put exit 0 into both /etc/init.d/kdm and /etc/init.d/xdm and tried again. I get a console login screen so I log in as root, fire up linux-wlan-ng and type startx. kde springs to life as if by magic and at last everything works, wireless, keyboard, mozilla, the lot. Let joy be unconfined. Thank you for all your support and advice but I do have to say that this has been the most unpleasant experience I have had with linux in the whole 10 years I have been using it. Now perhaps I can begin to enjoy debian instead of wrestling ti to the floor. I will try to find the cause of the keyboard problem but at the moment I have no theory that fits all the facts. Tony Sumner -- The Mailing List for the Devon & Cornwall LUG Mail majordomo@xxxxxxxxxxxx with "unsubscribe list" in the message body to unsubscribe.