Originally posted by: cleverhandle
Originally posted by: lowtech
There were 4 files that failed during boot & it flash by really quick, and I can only make it out as /var/
Check the output of dmesg for errors that occur before init starts. If your screen blanks before the login prompt (obscuring errors), try renaming /etc/issue - there's probably an escape sequence there that clears the screen.
The input work perfectly in bash, but will not work under X or KDE.
I can get into KDE & X through the use of startx command (becasue I didn't want to start X on boot as default), and the desktop is the prettiest that I have seen in a Linux distro, but the only input that I could do is with a mouse.
So it doesn't work at all. Odd...
I have a lot to learn in Linux, but I have setup many Debians, RH and many other distros that funtion perfectly on the same hardware, and Yoper is the only distro that will not work with my Mitsumi 107 & 105, NEC 104, or Digital 101 keyboard.
Some distros do a better job configuring things than others - I have no idea what Yoper is, so I don't know where it falls. It sounds like these may not be standard PC keyboards? Perhaps Yoper's config program just wasn't expecting that, and you'll have to edit the XF86 keyboard section by hand.
And, thanks for suggesting with editing the XF86Config, becasue I didn't think it was an XF86 problem.
Well, if it works in the console, but not in X, that's the first thing that would occur to me. Maybe there are other possibilities, too, though.
As for the disk image. I just don't know why it would take 1 hour to fdisk format & install, then only 15 min on the next on the same hardware. I can replicate the problem with EXT2, EXT3 & ReiserFS.
Ah... I understand what you're saying now. Sounds more like a bad disk causing rereads than a bad ISO, though. Usually if the ISO data is bad, the install will cough up errors about bad checksums or similar.