fedora 6 & Virtual pc

Today i tried fc6 in VirtualPC,but it's not working.it's showing some grafic problem.help pls

You'll have to be a bit more explicit in your description. Were you running FC6 inside Vmware or something? what was the exact problem? Do be a little more descriptive else we cant help you out.

Cheers
Arvind

joge you can install FC6 in Virtual PC, however, you'll have to do a few things to make it work....

First, when I installed FC6 I had to do it using the text based installer. I could have sworn I was able to use the graphical installer before, but for some reason it didn't work. Anyways, after installing FC6, start in text mode (don't start Gnome, KDE, etc...). Otherwise you'll notice graphic errors.

You'll then have to edit your /etc/X11/xorg.conf so that the DefaultDepth is 16. Personnally I use nano to edit the file then save it.

Then you can type in 'startx' to get your Xwindows session started.

I should note though... when I did all the updates to FC6, the mouse stopped working. I'm still trying to fix that one :'(.

But... if you just want to mess with FC6, maybe do some PHP web development, it's a good place to start.

Good Luck

Hi,
Had exactly the same problem as Meister1867, got everything working fine with Fedora 6, then did the update and ZAP .. no mouse.

Actually, the mouse is there, its Microsoft Virtual PC that seems to not be letting the mouse take to the screen. I noticed on the initial release from discs that you can get the mouse to enter just after boot, but now since the update, that isn't occurring at all.

Would love to hear what you find Meister1867 !!

I am also having the mouse problem with Virtual PC. After updating to the latest kernel version, mouse stops working in graphic mode (keyboard also seems to fail working).

Same here, mouse stops working after update. Tried looking for solution but still stuck

Same issue with update to Fedora 6..... any ideas as to which package could be causing the bug? I'm re-installing now....

Wow... thought I was the only one with the no-mouse issue in Virtual PC, lol.

Anyways, I didn't do anything until I realized other people were experiencing the same issue, but here's an update...

Comparing 2.6.18 to 2.6.19 does reveal some differences.

In 2.6.18, the /dev/input directory contains:
event0, event1, event2, mice, mouse0

Doing a 'cat /dev/input/mice', or the other devices, will reveal that they work under 2.6.18 when you use your mouse (do a Ctrl-Z to break out of the cat).

In 2.6.19, the /dev/input directory only contains:
event0, event1, mice

So somewhere between the 2 kernels we're losing devices. I'm doing a 'yum update' to see if there are any changes that could get it all working again... but my gutt tells me it won't. If not, the missing devices do give a few clues as to what to check... if I get time I'll try it all out(dang RL syndrome).

However, if this offers anyone a clue on how to fix the issue, please feel free to explore a solution and report back . If I find anything out, I'll report back.

Later,
Meister1867

Same here with the mouse probs!!!

Does anybody else have a problem with repeating keys from your keyboard?

I experienced also this problem after the update.

I tried some modifications of the /etc/X11/ xorg .conf mouse section, but no luck.

I registered today to give something back to all the other poeple who have posted details what they have found:

The issue has been traced to an error in the 2.6.19 kernel. And the details can be found in this other fedora thread:
"Death mouse after kernel update FC6"
http://www.linuxquestions.org/questi...d.php?t=521011

I have found as only workable solution to go back to the 2.6.18 kernel.

One way I found around this is to setup remote desktop under Gnome. You can use alt-f1 to browse the menu to set it up. Then I just connect with VNC. I then have a usable mouse. Since it is a virtual pc it is already kind of slow, so using vnc doesn't really make it any slower....

someone mentioned the KDE desktop working using this

# Edit ~/.vnc/xstartup
# For KDE, replace “twm &” with “startkde &”
# For Gnome, replace “twm &” with “exec gnome-session &”

this is TOTALLY WRONG as i have searched forums everywhere with people complaining that this wont work

here is what i did!

i changed this line

exec /etc/X11/xinit/xinitrc

to this line

exec /usr/bin/startkde

you see you have to tell it where the directory is located. the default tells it where knome is located.

there are tons of people having the problem trying to get kde to work with vnc so i thought i should post.