On Wed, 2004-09-29 at 16:16, Brian Millett wrote:
On Wed, 2004-09-29 at 15:51 -0400, Clyde Kunkel wrote:
(**) Option "Device" "/dev/input/mice" (EE) xf86OpenSerial: Cannot open device /dev/input/mice No such file or directory. (EE) Mouse0: cannot open input device (EE) PreInit failed for input device "Mouse0"
This is the problem. No mouse. Umm. It also looked like other /dev stuff was missing. Have you upgraded your kernel lately? You might want to try to remake the initrd. I seem to remember that this was a problem in the past when people upgraded a udev package with an initrd that did not use the new udev package. If you have, then just ignore me. IE: mkinitrd -f /boot/initrd-2.6.8-1.549.img 2.6.8-1.549
-- Brian Millett - [ Ombuds Wellington, "The Quality of Mercy"] "Anything a telepath sees while inside a defendant's mind is inadmissible evidence."
mkinitrd didn't work....something causing probs with /dev/null in the profile scripts and atd is not starting. Don't know if there is a relationship there or not.
Still probing...not giving up.
Recap: updated nicely working FC3T2 today before I saw the udev hold. Couldn't startx. Fixed udev, still can't startx. Something borked when udev failed????
ons, 29,.09.2004 kl. 17.30 -0400, skrev Clyde Kunkel:
On Wed, 2004-09-29 at 16:16, Brian Millett wrote:
On Wed, 2004-09-29 at 15:51 -0400, Clyde Kunkel wrote:
(**) Option "Device" "/dev/input/mice" (EE) xf86OpenSerial: Cannot open device /dev/input/mice No such file or directory. (EE) Mouse0: cannot open input device (EE) PreInit failed for input device "Mouse0"
This is the problem. No mouse. Umm. It also looked like other /dev stuff was missing. Have you upgraded your kernel lately? You might want to try to remake the initrd. I seem to remember that this was a problem in the past when people upgraded a udev package with an initrd that did not use the new udev package. If you have, then just ignore me. IE: mkinitrd -f /boot/initrd-2.6.8-1.549.img 2.6.8-1.549
-- Brian Millett - [ Ombuds Wellington, "The Quality of Mercy"] "Anything a telepath sees while inside a defendant's mind is inadmissible evidence."
mkinitrd didn't work....something causing probs with /dev/null in the profile scripts and atd is not starting. Don't know if there is a relationship there or not.
Still probing...not giving up.
Recap: updated nicely working FC3T2 today before I saw the udev hold. Couldn't startx. Fixed udev, still can't startx. Something borked when udev failed????
I solved it by downloading and rpm -ivh --force udev-032-2.i386.rpm ;>
On Wed, 2004-09-29 at 18:46, Øivind Hoel wrote:
ons, 29,.09.2004 kl. 17.30 -0400, skrev Clyde Kunkel:
On Wed, 2004-09-29 at 16:16, Brian Millett wrote:
On Wed, 2004-09-29 at 15:51 -0400, Clyde Kunkel wrote:
(**) Option "Device" "/dev/input/mice" (EE) xf86OpenSerial: Cannot open device /dev/input/mice No such file or directory. (EE) Mouse0: cannot open input device (EE) PreInit failed for input device "Mouse0"
This is the problem. No mouse. Umm. It also looked like other /dev stuff was missing. Have you upgraded your kernel lately? You might want to try to remake the initrd. I seem to remember that this was a problem in the past when people upgraded a udev package with an initrd that did not use the new udev package. If you have, then just ignore me. IE: mkinitrd -f /boot/initrd-2.6.8-1.549.img 2.6.8-1.549
-- Brian Millett - [ Ombuds Wellington, "The Quality of Mercy"] "Anything a telepath sees while inside a defendant's mind is inadmissible evidence."
mkinitrd didn't work....something causing probs with /dev/null in the profile scripts and atd is not starting. Don't know if there is a relationship there or not.
Still probing...not giving up.
Recap: updated nicely working FC3T2 today before I saw the udev hold. Couldn't startx. Fixed udev, still can't startx. Something borked when udev failed????
I solved it by downloading and rpm -ivh --force udev-032-2.i386.rpm ;>
Thanks, worth a try. Isn't it the same as manually fixing the if..fi problem?
I solved it by downloading and rpm -ivh --force udev-032-2.i386.rpm ;>
Thanks, worth a try. Isn't it the same as manually fixing the if..fi problem?
The file looked radically different afterwards for what it's worth.
On Wed, 2004-09-29 at 20:18, Øivind Hoel wrote:
I solved it by downloading and rpm -ivh --force udev-032-2.i386.rpm ;>
Thanks, worth a try. Isn't it the same as manually fixing the if..fi problem?
The file looked radically different afterwards for what it's worth.
OK, I'll give it a shot....thanks.
On Thu, 2004-09-30 at 02:18 +0200, Øivind Hoel wrote:
I solved it by downloading and rpm -ivh --force udev-032-2.i386.rpm ;>
Thanks, worth a try. Isn't it the same as manually fixing the if..fi problem?
The file looked radically different afterwards for what it's worth.
That fixed everything!!! Strange that the patch to 032-4 didn't work and had to downgrade udev to 032-2.
Thanks for the help!!
-
Clyde E. Kunkel -
Øivind Hoel