Re: Re: can't change screen resolution

From: Pietro R.A. Binetti (binabin_at_libero.it)
Date: 08/30/04

  • Next message: Alexander Dalloz: "Re: [Fwd: Mailman hostname]"
    To: fedora-list@redhat.com
    Date: Mon, 30 Aug 2004 19:55:06 +0200
    
    

    yes, I also tried to make some changes in xorg.conf file, but
    unsuccessfully. under section "screen" i had "800x600" "640x480".
    i deleted "640x480", but nothing! now if i look in the Display settings
    i can read 800x600, but i actually see my screen with 640x480.
    Beside this, in this laptop (acer tm212t) I also have win xp, in which i
    perfectly see @ 800x600.

    i really don't know how to solve this problem!

    pietro

    On Mon, 2004-08-30 at 19:27, fedora-list-request@redhat.com wrote:
    > From: hicham <hichamlinux@yahoo.fr>

    > did you try to make changes at
    > "/etc/X11/xorg.conf"
    > look at Section "Screen"
    > ........
    > Modes "640x480"
    >
    > change it to "800x600"
    >
    >
    > --- "Pietro R.A. Binetti" <binabin@libero.it> a crit
    > :
    > > Firstly I apologize for the wrong indication: I am
    > > stuck on 640x480
    > > resolution (not 800x600) and I want to have 800x600
    > > (not 1024x768).
    > > However
    > > the problem doesn't change so much: I am still
    > > stuck.
    > >
    > > Some of you suggested me to look at the video memory
    > > in my BIOS
    > > settings.
    > > Now there are 2 problems:
    > > 1. accessing my BIOS settings at the startup I can't
    > > see anywhere issues
    > > relating on video memory
    > > 2. I checked my system hardware and I discovered
    > > that my video card
    > > shares
    > > the memory with the RAM: it takes 8MB of 128MB. It
    > > does mean something,
    > > doesn't it?
    > >
    > > I also checked on the Acer webpage: there are no
    > > updates available for
    > > my
    > > BIOS.
    > >
    > > Regards,
    > > Pietro
    > >
    > > -----Original Message-----
    > >
    > > > Pietro R.A. Binetti wrote:
    > > > > Hello everyone,
    > > > >
    > > > >
    > > > >
    > > > > I am a new user of Fedora core 2, and a newer of
    > > linux-like OS as
    > > > >
    > > > > well.
    > > > >
    > > > > 2 days ago I installed Fedora on my notebook:
    > > acer travel mate 212T.
    > > > >
    > > > > I already have some problems that I can't solve:
    > > > >
    > > > >
    > > > >
    > > > > 1. Screen resolution
    > > > >
    > > > > I can't change the screen resolution: it is
    > > fixed on 800x600!
    > > > >
    > > > > During the OS installation i tried to select
    > > "generic LCD monitor" with
    > > > >
    > > > > different resolutions (as my monitor is not in
    > > the list). In all cases,
    > > > >
    > > > > once installed Fedora, I can't switch the
    > > resolution to the wanted
    > > > >
    > > > > 1024x768. I tried to do that changing the
    > > Display settings in the System
    > > > >
    > > > > Settings option panel. I select 1024x768 but I
    > > still see in 800x600
    > > > >
    > > > > resolution.
    > > > >
    > > > > What should I do?
    > > >
    > > >
    > > > Check to see if there is a later BIOS version for
    > > your machine. I had a
    > > > problem being stuck at 640 x 480 because of a
    > > buggy BIOS version.
    > > >
    > > > Also, check your BIOS setting for things that
    > > relate to video memory. If
    > > > I recall, some systems are set to pretty low
    > > settings for shared memory.
    > > > This will limit your resolution top setting. I
    > > believe that 1 meg would
    > > > limit you to 640 x 480.
    > > >
    > > > >
    > > > > 2. Touch pad
    > > > >
    > > > > My touch pad is working correctly, even if I
    > > have to touch the left
    > > > >
    > > > > button to press the left mouse button: pressing
    > > the pad with a "touch"
    > > > >
    > > > > it doesn't work. The "touch" isn't recognized,
    > > or something like that.
    > > > >
    > > > > Should I configure the touch pad somewhere else?
    > > >
    > > >
    > > > Check the archives for this information. You have
    > > to add
    > > > psmouse=proto.imps or similar to your grub.conf
    > > file. This changes the
    > > > order of events the kernel uses. (Info from an
    > > earlier post by another
    > > > lister)
    > > > I'm on a a machine that does not need this added
    > > to the kernel. My
    > > > memory recall might not be the correct context.
    > > Look for 2.6 kernel and
    > > > synaptics related posts in the list archives.
    > > > I couldn't find the postings myself. Your search
    > > might be more successful.
    > > >
    > > > The link to the archives is at the bottom of every
    > > posting. Click on the
    > > > link below or at the bottom of the message to
    > > search the archives.
    > > >
    > > > http://www.redhat.com/archives/fedora-list/
    > > >
    > > > This might lead you in the right direction to a
    > > resolution. (hopefully!)
    > > >
    > > > Jim
    > > >
    > > > > Best regards,
    > > > > Pietro

    -- 
    fedora-list mailing list
    fedora-list@redhat.com
    To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
    

  • Next message: Alexander Dalloz: "Re: [Fwd: Mailman hostname]"

    Relevant Pages

    • Re: Laptop Display Problem while booting up
      ... You should upgrade your BIOS.... ... I have this laptop and had a similar issue ... You should be able to get the updated BIOS from Dell's website. ... with the function keys for the display settings (CRT/LCD, Font, and ...
      (microsoft.public.windowsxp.help_and_support)
    • Re: Lack of agpvar.h causing nvidia-driver build to fail
      ... Bad news is that changing the docking method in the BIOS didn't help. ... it was still the same display settings as the laptop monitor, ...
      (freebsd-current)
    • display problems after upgrading
      ... have a problem with my display settings, ... searched the microsoft website and found a solution to my ... motherboard's BIOS. ... need to contact the manufacturer of the motherboard to ...
      (microsoft.public.win2000.windows_update)