X will not automatically work for kernels-2.1.18 and 2.4.x. Well it's not directly the kernels fault, it is the new devfs and/or the new input layer that causes the problem. Actaully I couldn't get my machine to boot because of devfs. You need to install devfsd to around the booting problem (if you have it) or you can pass the parameter devfs=nomount to the kernel via lilo.
To get X to work, you need to change your XF86Config file (or XF86Config-4 for X 4.0.x) so that the mouse device is something like /dev/inputs/mouse0 or /dev/inputs/mouse1. Change /etc/inittab to a runlevel where X does not try to fire up automatically. Then use startx to manually invoke X and see what the error messages are. They should also be logged to /var/log/XFree86.0.log Brendan Simon. tom wrote: > tom wrote: > > > > Well, I upgraded from stable to testing. > > > > Now X is dead. > > > > I run 'XFree86 -configure' and it locks up like a Windows Box > > would. I have to power down to get it to let go. > > I run 'X -configuer' and I get the same thing.. > > > > I've attached a 'tail' of my XFree86.log file. > > > > >From a guess, it is missing the pci device 01:00.0 > > from 'lspci' > > 01:00.0 VGA compatable controller: ATI Technologies Inc 3D Rage > > P/M Mobility AGP 2x (rev 64) > > > > Now What? > > > > -- > > 8:33am up 25 days, 14:44, 2 users, load average: 0.00, 0.00, > > 0.00 > > > > It seems that the text based configuration tool works OK. > The default video of 'apm' that was used was locking up the > notebook. > I don't know why it picked apm, but that's what it did. > > -- > 9:14am up 25 days, 15:25, 2 users, load average: 0.00, 0.00, > 0.00 > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
