Fedora 7
Neil
trick I learned when installing FC6, and added 'vesa' to the graphical
installer command. That got me past the first problem I had with FC6 and I
could see the graphical installer. But the second problem I encountered
with FC6 persists, and isn't amenable to the solution which worked in that
case. I have no mouse support in the installer, and I assume I wouldn't
have any in the gnome window environment either. [The solution in FC6 was
to boot the version of the kernel which came on the DVD, rather than the
updated version installed subsequently. In F7 the version on the DVD
doesn't work, where could I get an older version from?]
Neil
SaGS
news:O5MsAEip...@TK2MSFTNGP04.phx.gbl...
>I haven't seen this one here yet. Has anyone got it working? I tried the
>trick I learned when installing FC6, and added 'vesa' to the graphical
>installer command. That got me past the first problem I had with FC6 and I
>could see the graphical installer. But the second problem I encountered
>with FC6 persists, and isn't amenable to the solution which worked in that
>case. I have no mouse support in the installer, and I assume I wouldn't
>have any in the gnome window environment either.
For installing from the DVD iso I did the following:
- at the 1st [graphical] screen, hit TAB to modify boot params;
- it will show "vmlinuz initrd=initrd.img";
- add "vesa i8042.noloop psmouse.proto=imps clock=pit".
This got things working for me (up to the point of selecting packages,
as I stopped the install due to lack of disk space on the host).
Details:
- "vesa" selects "vesa" driver instead of the "s3" one; mandatory if you
want the graphics installer. With FC6 this also allowed "Millions of
colors" to be used post-install, don't know about F7.
- "i8042.noloop" makes the PS/2 mouse work, otherwise it's stuck in
the center of the screen; reference: comment #45 at
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=223606
- "psmouse.proto=imps" makes the mouse wheel work; optional as it's
not that usefull during the install, but usefull to add it to kernel
options for normal system use.
- "clock=pit", according to a MSKB article, resolves some problems with
the time[r]; don't know how usefull is it during the install.
Neil
news:OGudlbaq...@TK2MSFTNGP06.phx.gbl...
> For installing from the DVD iso I did the following:
>
> - at the 1st [graphical] screen, hit TAB to modify boot params;
> - it will show "vmlinuz initrd=initrd.img";
> - add "vesa i8042.noloop psmouse.proto=imps clock=pit".
>
> This got things working for me (up to the point of selecting packages,
> as I stopped the install due to lack of disk space on the host).
>
> Details:
>
> - "vesa" selects "vesa" driver instead of the "s3" one; mandatory if you
> want the graphics installer. With FC6 this also allowed "Millions of
> colors" to be used post-install, don't know about F7.
>
> - "i8042.noloop" makes the PS/2 mouse work, otherwise it's stuck in
> the center of the screen; reference: comment #45 at
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=223606
>
> - "psmouse.proto=imps" makes the mouse wheel work; optional as it's
> not that usefull during the install, but usefull to add it to kernel
> options for normal system use.
>
> - "clock=pit", according to a MSKB article, resolves some problems with
> the time[r]; don't know how usefull is it during the install.
>
>
I used all these suggestions and got through the install. But on rebooting
the VM, I had all sorts of graphical corruption. I did try adding the same
text after the "initrd blah.img" entry in the command sequence in the
bootloader, but it was no better.
Neil
SaGS
> "SaGS" <AntiSpamRemov...@hotZmail.com> wrote in message
> news:OGudlbaq...@TK2MSFTNGP06.phx.gbl...
>
>> For installing from the DVD iso I did the following:
>>
>> - at the 1st [graphical] screen, hit TAB to modify boot params;
>> - it will show "vmlinuz initrd=initrd.img";
>> - add "vesa i8042.noloop psmouse.proto=imps clock=pit".
>>
>> This got things working for me (up to the point of selecting packages,
>> as I stopped the install due to lack of disk space on the host).
>
> I used all these suggestions and got through the install. But on
> rebooting the VM, I had all sorts of graphical corruption. I did try
> adding the same text after the "initrd blah.img" entry in the command
> sequence in the bootloader, but it was no better.
>
> Neil
After making enough space to actually do the install, I got the same result
as you.
Here is how I made it work:
After all packages are copied and F7 is ready to reboot the 1st time,
capture the ISO again and reboot from the DVD (or Rescue CD) in rescue mode.
Edit or simply replace xorg.conf with a copy that works. In rescue mode,
this file is accessible as /mnt/sysimage/etc/X11/xorg.conf; I had a good
copy (see end of this post), taken from a FC6 installation, on a floppy and
simply copied it over the one created by the installer. Then release the
ISO, type "exit" to exit the [rescue mode] shell, and it will reboot from
the hd and continue the install normally ("Welcome" screen. license info,
etc).
The graphics boot screen, the graphics login screen and the GUI work OK now.
The "text mode" screens displayed during boot/ reboot/ shutdown remained
trashed, don't know why.
Note about the mouse:
During the install, at the boot loader config screen, check "[V] Configure
advanced boot loader options"; on the next screen, under "General kernel
parameters", type "i8042.noloop psmouse.proto=imps clock=pit". This adds
those params to the default boot config, to get the mouse working
post-install. (Maybe you already did this, but I include it here because
it's not mentioned in my previous post.)
And now the xorg.conf that worked for me.
If you prepare the file on Windows, try to use an editor that lets you have
LF-only as line endings; don't know if it will work with CRLFs, haven't
tried. If you don't have such an editor, use the "DOS mode" EDIT in binary
mode ("edit /75 filename") to replace all CRs with nothing (select the 1st
CR, it looks like a musical note, then "Search"/ "Replace...")
--- CUT HERE, USE AS [/mnt/sysimage]/etc/X11/xorg.conf ---
# Xorg configuration created by system-config-display
Section "ServerLayout"
Identifier "single head configuration"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection
Section "Monitor"
Identifier "Monitor0"
ModelName "LCD Panel 1280x1024"
HorizSync 31.5 - 67.0
VertRefresh 50.0 - 75.0
Option "dpms"
EndSection
Section "Device"
Identifier "Videocard0"
Driver "vesa"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 16
SubSection "Display"
Viewport 0 0
Depth 24
Modes "800x600"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
Modes "800x600" "640x480"
EndSubSection
EndSection
--- END OF SAMPLE xorg.conf ---
emails...@gmail.com
install and afterwards (text mode only) was adding the following boot
parameters:
clock=pit nosmp noapic nolapic vga=771
The first 4 helped solving the clock sync problem and the last one the
garbled screen.
Hope this helps.
Neil
news:1181646469....@d30g2000prg.googlegroups.com...
I have used these and those in the other message from SaGS and everything
works now.
That is apart from sound. I don't think I ever had sound in any of the FC6
or F7 attempts at VPC installation. Is there a trick to making that work?
Neil
SaGS
> That is apart from sound. I don't think I ever had sound in any of the
> FC6 or F7 attempts at VPC installation. Is there a trick to making that
> work?
Yes. See http://vpc.visualwin.com/, the notes for "Fedora Core 5 Final". It
worked fine for me with FC6 and F7 too.
SaGS
>> clock=pit nosmp noapic nolapic vga=771
> ... and everything works now.
> ...
Does this "everything" include the "text mode" display during boot/ reboot/
shutdown?
This is still not OK for me.
I tried both:
(a) Without any "vga=" :
- First lines, upto "Starting udev:", use a true text
mode and look OK.
- Then, and during reboot/ shutdown, the display is switched
to a garbaged 640x480x4bpp (16-color graphics mode)
AND
(b) With "vga=771" and other values:
- First lines, upto "Starting udev:", use a graphics mode that
depends on the value specified for "vga=" (this is OK), and
the text is visible. A penguin gets displayed in the
top-left corner.
- After "Starting udev:", but especially during reboot and
shutdown, the screen is completely black.
- The GUI, including the graphics boot and logon screens,
are OK. It's just the "text mode console" that's black.
So, does it really work 100% OK for you? Note especially during shutdown if
you see scrolling the messages from processes that are stopped, or simply
have a black screen.
Neil
From: "SaGS" <AntiSpamRemov...@hotZmail.com>
Newsgroups: microsoft.public.virtualpc
Sent: Tuesday, June 19, 2007 9:21 AM
Subject: Re: Fedora 7
> "Neil" <ne...@chapellane69.free-online.co.uk> wrote in message
> news:OjoBuDRs...@TK2MSFTNGP02.phx.gbl...
>> <emails...@gmail.com> wrote in message
>> news:1181646469....@d30g2000prg.googlegroups.com...
>> ...
>>> clock=pit nosmp noapic nolapic vga=771
>> ...
>> ... and everything works now.
>> ...
>
> Does this "everything" include the "text mode" display during boot/
> reboot/ shutdown?
>
> So, does it really work 100% OK for you? Note especially during shutdown
> if you see scrolling the messages from processes that are stopped, or
> simply have a black screen.
>
>
Your experience is just like mine. After starting udev during startup the
display shifts to a fully graphical display with a progress bar and some
textual indication of what is going on. But you're completely correct.
During shutdown I cannot see all the messages about stopping processes. I
did notice, but decided I didn't really care. I am insufficiently savvy to
know what any of them means (almost) so they're not an awful lot of use to
me. The only problem I have is that looking at a black screen as it
shutsdown seems to take an awful lot longer than when I used to be able to
see the messages.
I just tried it again and noticed there are some additional black spaces
before and after the graphical boot progress screen. So there's likely to
be things I'm missing in there too.
Neil
SaGS
> ...
> Your experience is just like mine. ...
Thank you for confirming this. I guess we'll need to let it that way, at
least for now. After all, you're right: it's not that important.
emails...@gmail.com
Sorry for the late response. Btw, "uname -a" gives me 2.6.21-1.3228
>Does this "everything" include the "text mode" display during boot/ reboot/
>shutdown?
Yes, I have a perfect text mode during boot/reboot/shutdown. I haven't
tried GUI mode.
> (b) With "vga=771" and other values:
> - First lines, upto "Starting udev:", use a graphics mode that
> depends on the value specified for "vga=" (this is OK), and
> the text is visible. A penguin gets displayed in the
> top-left corner.
I can also see the penguin
> - After "Starting udev:", but especially during reboot and
> shutdown, the screen is completely black.
That was my problem before applying the vga parameter. After "starting
udev" the screen was completely garbled.
Bo Berglund
HELP!
I have come this far too and now I am at a Fedora7 Rescue prompt in
/mnt/sysimage/etc/X11 and by using 'more xorg.conf' I can see that its
default depth is set to 24 bits, just the one that VPC2007 cannot cope
with...
So I want to change it to 16, but how is that done in Linux on the
command prompt???
I have absolutely no clue as to how one starts a text editor in Linux
(Fedora) but I guess that without this fixed there will be no way I
can work with Fedora 7 in VPC2007.
Please give the commands (explicitly) on how one can edit the file in
this situation.
I have no idea how one could copy a file from the floppy either (I
don't have a real floppy and I don't know the command to use) so I
guess my only chance is to edit in place.
Bo Berglund
bo.berglund(at)nospam.telia.com
Neil
From: "Bo Berglund" <bober...@home.se>
Newsgroups: microsoft.public.virtualpc
Sent: Saturday, September 01, 2007 5:03 PM
Subject: Re: Fedora 7
>
> HELP!
> I have come this far too and now I am at a Fedora7 Rescue prompt in
> /mnt/sysimage/etc/X11 and by using 'more xorg.conf' I can see that its
> default depth is set to 24 bits, just the one that VPC2007 cannot cope
> with...
>
> So I want to change it to 16, but how is that done in Linux on the
> command prompt???
>
> I have absolutely no clue as to how one starts a text editor in Linux
> (Fedora) but I guess that without this fixed there will be no way I
> can work with Fedora 7 in VPC2007.
>
> Please give the commands (explicitly) on how one can edit the file in
> this situation.
>
> I have no idea how one could copy a file from the floppy either (I
> don't have a real floppy and I don't know the command to use) so I
> guess my only chance is to edit in place.
>
Having booted from the rescue CD you will have access to (at least) the
editor called 'vi' - there may be others as well, but I know you have 'vi'.
You can then edit the file by typing 'vi /mnt/sysimage/etc/X11/xorg.conf'
However, if you 'chroot /mnt/sysimage' you should also have access to the
more helpful (if you've never used 'vi' before) editor called 'vim' - again
there may be other, even more helpful editors in there, but I managed once I
had found 'vim'.
You would start editing by typing 'vim /etc/X11/xorg.conf'. The editor has
built-in help which you can access by typing ':help' (if no command appears
at the bottom line of the screen when you have typed the colon, try pressing
escape to get out of whatever mode you may have accidentally accessed). But
basically to achieve what you want you only need to know that you can
navigate around the text using the arrow keys, you can delete the character
under the cursor by pressing 'x', and you can start inserting text into the
document by pressing 'i' (when you have added all you want press escape).
To exit and save the file, the appropriate command is ':wq'.
Note you do not need to change the default colour depth to 16 to make the
machine work, using the vesa driver means you can leave it at 24 (though I
think I may have been told that actually it makes no difference to what is
displayed whatever because of the capabilities of the virtual video card).
Below is the text which I use for my 'xorg.conf'. It's basically copied
from that which SaGS supplied. I don't completely understand what all the
bits do (I am a novice), but there were a couple of changes I made. I
truncated the "Screen" section and only included one mode in the "Display"
subsection. I made the maximum supported vertical refresh rate for the
monitor equal to the actual refresh rate (60Hz) in the normal mode
(1680x1050) I use for my host OS desktop, rather than the actual highest
possible which is 75Hz. [I haven't found a way of getting a better
resolution in the VM than 1024x768, and if I don't make that change it tries
to set the vertical refresh to 75Hz for that resolution, and that results in
some small artifacts in the display].
Neil
PS if anyone can help me get a higher resolution for the VM I'd like to
know.
# Xorg configuration created by pyxf86config
Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "pc105"
Option "XkbLayout" "gb"
EndSection
Section "Monitor"
Identifier "Monitor0"
ModelName "LCD Panel 1680 x 1050"
HorizSync 31.5 - 67.0
VertRefresh 50.0 - 60.0
Option "dpms"
EndSection
Section "Device"
Identifier "Videocard0"
Driver "vesa"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1024x768"
EndSubSection
EndSection
Bo Berglund
I asked in the fedora newsgroup on how to edit the xotrg.conf file and
received a number of replies which led me to use nano as editor. It
worked for the purpose I had, to change 24 into 16 in the screen
section.
Someone suggested joe, but that was not a recognized command.
>
>Note you do not need to change the default colour depth to 16 to make the
>machine work, using the vesa driver means you can leave it at 24 (though I
>think I may have been told that actually it makes no difference to what is
>displayed whatever because of the capabilities of the virtual video card).
I had not read your reply yet (unfortunately) when I edited the
xorg.conf file using nano, so the only changes from the default I did
was to change 24 to 16 in two places.
Problem is that when I exited the rescue console and started again
there were probably some things I should have done more (but were not
in he list of stuff to do in the post from SaGS. I just let the bott
run unhindered and now I am looking at a black screen with a garbled
cursor up in the left corner and a band of vertical green lines
running across in the upper part of the screen, typical of what
happens when the color depth is wrong...
On the boot after the change in xorg.conf, am I supposed to interrupt
the boot process like when first installing Fedora7 and add boot
parameters again?
If so, which parameters are needed, and how does one make them stick
for the future?
At the first install screen on the DVD boot I did the following:
- hit TAB to get possibility to modify parameters
- changed them by adding this at the end:
vesa i8042.noloop psmouse.proto=imps clock=pit
Then I could go through all of the install screens of Fedora7 in
graphics mode just fine.
Is this needed when Fedora starts up next time as well?
How is it done then? The initial screen is different from the DVD boot
screen...
>Below is the text which I use for my 'xorg.conf'. It's basically copied
>from that which SaGS supplied. I don't completely understand what all the
Now I can't get at the file I have (the default Fedora7 install file)
since I am stuck with the system in the wrong graphics mode (black
screen) and I don't know what to do....
I have tried to install Fedora one time before (back in wintertime) to
test Linux, but that install did not succeed either. Seems hard to
make it work...
Bo Berglund
bo.berglund(at)nospam.telia.com
Neil
news:f0rkd310qjps6ph2o...@4ax.com...
>
> I had not read your reply yet (unfortunately) when I edited the
> xorg.conf file using nano, so the only changes from the default I did
> was to change 24 to 16 in two places.
>
> Problem is that when I exited the rescue console and started again
> there were probably some things I should have done more (but were not
> in he list of stuff to do in the post from SaGS. I just let the bott
> run unhindered and now I am looking at a black screen with a garbled
> cursor up in the left corner and a band of vertical green lines
> running across in the upper part of the screen, typical of what
> happens when the color depth is wrong...
>
> On the boot after the change in xorg.conf, am I supposed to interrupt
> the boot process like when first installing Fedora7 and add boot
> parameters again?
> If so, which parameters are needed, and how does one make them stick
> for the future?
>
In one of SaGS posts he did tell you what you needed to do. On one of the
very last install screens there is a button to configure the boot loader,
and you should add the same options 'vesa ...' as you added to get the
install going. If you did not use that option then the parameters will not
stick, and you would have to add them every time you boot your machine.
That is, unless you edit one of the other files. This time it should be
easier because you ought to be able to type the options as a modification
when booting, and use 'gedit' from the Applications/Accessories/Text Editor
menu in the gnome desktop. The file you need to edit this time is
'/boot/grub/grub.conf'. In the section having the title associated with the
kernel version you want to use, add the parameter modifications 'vesa ...'.
Don't forget the 'vga=771' which if left out results in some of the "text"
mode screens being garbled, which is possibly what you are describing.
> At the first install screen on the DVD boot I did the following:
> - hit TAB to get possibility to modify parameters
> - changed them by adding this at the end:
> vesa i8042.noloop psmouse.proto=imps clock=pit
> Then I could go through all of the install screens of Fedora7 in
> graphics mode just fine.
>
> Is this needed when Fedora starts up next time as well?
> How is it done then? The initial screen is different from the DVD boot
> screen...
>
Just press a key before your three seconds are up and some options appear.
I think editing is 'e'
Having said all that (I also forgot to add the optional parameters to the
boot loader configuration during the installation, and had to do it by
editing 'grub.conf') there was a point at which I still had to persevere
with a garbled screen, and I'm not quite sure why. If you're lucky
everything'll work out for you, because the only way I managed to get
through it (the bit where you set up an "ordinary" user etc.) was because I
had previously seen it in it's ungarbled form, so knew roughly what it was
asking me to do.
>
> I have tried to install Fedora one time before (back in wintertime) to
> test Linux, but that install did not succeed either. Seems hard to
> make it work...
>
Yes, I was also surprised by how difficult it was to make it work. I think
it is somewhat due to installing on a VM. The time I tried to install it on
a real computer it seemed much easier.
Bo Berglund
<ne...@chapellane69.free-online.co.uk> wrote:
>"Bo Berglund" <bober...@home.se> wrote in message
>news:f0rkd310qjps6ph2o...@4ax.com...
>>
>> I had not read your reply yet (unfortunately) when I edited the
>> xorg.conf file using nano, so the only changes from the default I did
>> was to change 24 to 16 in two places.
>>
>> Problem is that when I exited the rescue console and started again
>> there were probably some things I should have done more (but were not
>> in he list of stuff to do in the post from SaGS. I just let the bott
>> run unhindered and now I am looking at a black screen with a garbled
>> cursor up in the left corner and a band of vertical green lines
>> running across in the upper part of the screen, typical of what
>> happens when the color depth is wrong...
>>
>> On the boot after the change in xorg.conf, am I supposed to interrupt
>> the boot process like when first installing Fedora7 and add boot
>> parameters again?
>> If so, which parameters are needed, and how does one make them stick
>> for the future?
>>
>
>In one of SaGS posts he did tell you what you needed to do. On one of the
>very last install screens there is a button to configure the boot loader,
I am now re-doing all of my install work (created a new blank VHD
file) and I will surely look out for the item to modify the boot
loader. I *almost* got there earlier today when I changed the options
to the xorg.conf file (24->16) via the rescue console and added the
other options to the start on reboot for the kernel. I actually got
into the graphics screen and could log in as root etc.
Dids a lot of stuff including letting Fedora install the 178 updates
it had determined that I needed....
As a by-product of this I found that it also installed a new kernel...
Anyway after the reboot following this I have not been able to start
Fedora no matter what options I give or what kernel I choose without
getting a garbled double-width window at the time X is starting. :-(
It seems like my setting the default depth and the current depth in
xorg.conf somehow does not "take".
>and you should add the same options 'vesa ...' as you added to get the
>install going. If you did not use that option then the parameters will not
>stick, and you would have to add them every time you boot your machine.
>That is, unless you edit one of the other files. This time it should be
>easier because you ought to be able to type the options as a modification
>when booting, and use 'gedit' from the Applications/Accessories/Text Editor
>menu in the gnome desktop. The file you need to edit this time is
>'/boot/grub/grub.conf'. In the section having the title associated with the
>kernel version you want to use, add the parameter modifications 'vesa ...'.
>Don't forget the 'vga=771' which if left out results in some of the "text"
>mode screens being garbled, which is possibly what you are describing.
I did edit the grub.conf file as well as xorg.conf, but results are no
good..
It is actually good now at the *start* of the boot sequence, I can
even see the little Pengin at the top of the text mode screen at the
start!
But as soon as X starts the screen goes completely mad.
Bo Berglund
bo.berglund(at)nospam.telia.com
Neil
>
> Anyway after the reboot following this I have not been able to start
> Fedora no matter what options I give or what kernel I choose without
> getting a garbled double-width window at the time X is starting. :-(
>
>
This sounds a bit like what I had. The screens I had to navigate half-blind
were the ones for adding an "ordinary" (i.e. non-root) user, and a few other
things, I can't quite remember. You may or may not have to do the same at
the end of the day. If you can't avoid it, and still want to persevere, the
following may help. If I remember correctly the only screen that needs any
proper input is the first which has boxes for a userid, password and
password confirmation. You can type in the boxes and tab between them.
Then tab to the 'ok' or 'next' or whatever it is that you can't see and
press return. For the other screens, when I did it, it was just a matter of
finding the correct number of tabs to use to get to the next. If you find
you've gone backwards instead of forwards, try one more tab next time. If
you find that further dialogues pop-up, press escape and try again.
I'm sure all the proper Fedora and/or VPC people reading this are LTAO at
two utterly clueless fools struggling to get the thing installed, but that's
what worked for me this time around. First time it seemed to go more
smoothly, following the SaGS instructions, but then I got a corrupted
filesystem somehow (I don't know whether it was the Linux that corrupted
itself, or the Windows which did something bad to the VHD, but either way I
couldn't get 'fsck' to fix it).
Dragon Park
Thank you everybody.
I solved this problem as your comments.
There's a solution on the previous reply.
In my case,
1. Environments
- MS Windows XP SP2 and MS Virtual PC 2007
- Fedora-7-DVD
2. Installation
From "SaGS" comment :
For installing from the DVD iso I did the following:
- at the 1st [graphical] screen, hit TAB to modify boot params;
- it will show "vmlinuz initrd=initrd.img";
- add "vesa i8042.noloop psmouse.proto=imps clock=pit".
Whole of things were same as general Fedora installation procedures.
3. After Installation
Maybe Fedora should not gracefully run with X
So I modified as belows
Modify at the grub booting.
add "vga=791 i8042.noloop psmouse.proto=imps clock=pit single"
and after first booting, modify /etc/X11/xorg.conf
add below
-------------------------
Section "Monitor"
Identifier "Monitor0"
ModelName "LCD Panel 1280x1024"
HorizSync 31.5 - 67.0
VertRefresh 50.0 - 75.0
Option "dpms"
EndSection
--------------------------
and modify
Monitor "Monitor0"
DefaultDepth 16 #(24->16)
next, add below
---------------------------
SubSection "Display"
Viewport 0 0
Depth 16
Modes "1024x768" "800x600" "640x480" #(if you need, "1280x1024")
EndSubSection
---------------------------
Then, you can access Xwindow login screen.
Thanks again previous comments...
Have a good luck...
Posted via http://www.VirtualServerFaq.com - Brought to you by Business Information Technology Shop - http://www.bitshop.com
Logisex
Hi, i have try all your exemple of xorg.conf and no one work, i'm still stock with the crapy interface and i can't see nothing???
i have a Monitor ACER AL1706 and i really want to run Fedora Core 7 into my VirtualPC 2007 so plz someone help me
Logisex
Can someone send me his Virtual Machine or his xorg.conf because for me there no way to made it work, i have try all what i can
SaGS
news:0f018275-9b67-4b59...@text.giganews.com...
> ...
> Can someone send me his Virtual Machine or his xorg.conf because for me
> there no way to made it work, i have try all what i can
>
There's another thread on the subject, "Fedora7 successful install in
VPC2007" [Bo Berglund, Wednesday, 05 September 2007 00:22]. Followups
include a link to a web page with screenshots [Bo Berglund, Thursday 06
September 2007 21:33 UTC], and a VPC floppy image (*.VFD) with a working
xorg.conf [sags, Monday 10 September 2007 07:57 UTC].
Victor
Hey!
Just done everything said in the posts above an Fedora 7 works well until I try to reboot/shutdown. The screen goes black and it freezes.
Is there a solution for this problem?
Thanks!
SaGS
news:632b7352-17b3-43de...@text.giganews.com...
> ...
> Just done everything said in the posts above an Fedora 7 works well until
> I try to reboot/shutdown. The screen goes black and it freezes.
Did you add a "vga=" parameter? Remove it. For me, that was what made theese
screens completely black [instead of being mostly unreadeable].
Are you *sure* it freezes? It does indeed take a long time to reboot/
shutdown, and with a completely black screen it gives the impression it
never ends...
> Is there a solution for this problem?
> ...
None that I know of, but I'm not a Linux guru...
SaGS
Now I found a solution (or workaround): add the kernel parameter
"fbcon=map:9" (to disable fbcon).