Announcement

Collapse
No announcement yet.

xorg.config is empty? resolution problem

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    xorg.config is empty? resolution problem

    hi every one i first time install linux ie (kubuntu 8.10&KDE 4.1) but evrything is so big & words are so blur.i try to search and find taht by replacing some word in xorg.conf and it will solve my problem but guess what my xorg.conf(/etc/X11/xorg.cong ) is empty.what should i do?is thaere any way?or shold i go for some other version
    i have via motherboard shold i need to downlaod in driver or something?
    pls help me


    #2
    Re: xorg.config is empty? resolution problem

    what video card? have you tried going to system settings|displays and setting the resolution there?

    mm0
    Dell Inspiron 1720 Laptop<br />Intel T9300 Core2Duo Processor @ 2.5Ghz<br />4 GB Ram | 1920 X 1200 Resolution<br />2 X 160 GB SATA HD Internal<br />Nvidia GeForce 8600M Graphics Adapter<br />Using Kubuntu 9.10

    Comment


      #3
      Re: xorg.config is empty? resolution problem

      i told u i have via motherboard so via video card
      ya i tried that to go change in resolution but it showing only one resolution ie (800x600)

      Comment


        #4
        Re: xorg.config is empty? resolution problem

        sorry, don't know anything about via video cards. I would do some googling, you probably need to find a better driver.
        mm0
        Dell Inspiron 1720 Laptop<br />Intel T9300 Core2Duo Processor @ 2.5Ghz<br />4 GB Ram | 1920 X 1200 Resolution<br />2 X 160 GB SATA HD Internal<br />Nvidia GeForce 8600M Graphics Adapter<br />Using Kubuntu 9.10

        Comment


          #5
          Re: xorg.config is empty? resolution problem

          Still waiting for solution!!!!!!!!!!!!!!!!!!
          pls guys help me

          Comment


            #6
            Re: xorg.config is empty? resolution problem

            Very likely, the installer doesn't recognize the video chip on your motherboard, except at a very generic level. You can manually create an entry in your xorg.conf file that might pick up the actual needed driver that may already exist on your system.

            First, enter
            Code:
            sudo lspci -vv
            ( that's a dash with two "v"'s) and report the results here inside a code box.
            The next brick house on the left
            Intel i7 11th Gen | 16GB | 1TB | KDE Plasma 5.27.11​| Kubuntu 24.04 | 6.8.0-31-generic



            Comment


              #7
              Re: xorg.config is empty? resolution problem

              result for: sudo lspci -vv
              Code:
              00:00.0 Host bridge: VIA Technologies, Inc. P4M800 Host Bridge
                  Subsystem: VIA Technologies, Inc. P4M800 Host Bridge 
                  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-                          
                  Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-                         
                  Latency: 8                               
                  Region 0: Memory at e8000000 (32-bit, prefetchable) [size=128M]     
                  Capabilities: [80] AGP version 3.5                   
                      Status: RQ=8 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3+ Rate=x4,x8                            
                      Command: RQ=1 ArqSz=0 Cal=0 SBA+ AGP+ GART64- 64bit- FW- Rate=x8
                  Capabilities: [50] Power Management version 2              
                      Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)                                   
                      Status: D0 PME-Enable- DSel=0 DScale=0 PME-           
                  Kernel driver in use: agpgart-via                    
                  Kernel modules: via-agp                         
              
              00:00.1 Host bridge: VIA Technologies, Inc. P4M800 Host Bridge
                  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-                          
                  Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-                         
                  Latency: 0                               
              
              00:00.2 Host bridge: VIA Technologies, Inc. P4M800 Host Bridge
                  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-                          
                  Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-                         
                  Latency: 0                               
              
              00:00.3 Host bridge: VIA Technologies, Inc. P4M800 Host Bridge
                  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-                          
                  Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-                         
                  Latency: 0                               
              
              00:00.4 Host bridge: VIA Technologies, Inc. P4M800 Host Bridge
                  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-                          
                  Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-                         
                  Latency: 0                               
              
              00:00.7 Host bridge: VIA Technologies, Inc. P4M800 Host Bridge
                  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-                          
                  Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-                         
                  Latency: 0                               
              
              00:01.0 PCI bridge: VIA Technologies, Inc. VT8237/VX700 PCI Bridge
                  Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-                          
                  Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-                         
                  Latency: 0                               
                  Bus: primary=00, secondary=01, subordinate=01, sec-latency=0      
                  Memory behind bridge: f4000000-f5ffffff                 
                  Prefetchable memory behind bridge: f0000000-f3ffffff          
                  Secondary status: 66MHz+ FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR+ <PERR+                            
                  BridgeCtl: Parity- SERR+ NoISA- VGA+ MAbort- >Reset- FastB2B-      
                      PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-       
                  Capabilities: [70] Power Management version 2              
                      Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)                                   
                      Status: D0 PME-Enable- DSel=0 DScale=0 PME-           
                  Kernel modules: shpchp                         
              
              00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80)                                  
                  Subsystem: Micro-Star International Co., Ltd. Device 7104        
                  Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-                          
                  Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-                         
                  Latency: 32                               
                  Interrupt: pin B routed to IRQ 20                    
                  Region 0: I/O ports at e000 [size=8]                  
                  Region 1: I/O ports at e100 [size=4]                  
                  Region 2: I/O ports at e200 [size=8]                  
                  Region 3: I/O ports at e300 [size=4]                  
                  Region 4: I/O ports at e400 [size=16]                  
                  Region 5: I/O ports at e500 [size=256]                 
                  Capabilities: [c0] Power Management version 2              
                      Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)                                   
                      Status: D0 PME-Enable- DSel=0 DScale=0 PME-           
                  Kernel driver in use: sata_via                     
                  Kernel modules: sata_via                        
              
              00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP])         
                  Subsystem: Micro-Star International Co., Ltd. Device 7104        
                  Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-                          
                  Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-                         
                  Latency: 32                               
                  Interrupt: pin A routed to IRQ 20                    
                  Region 0: [virtual] Memory at 000001f0 (32-bit, non-prefetchable) [size=8]                                       
                  Region 1: [virtual] Memory at 000003f0 (type 3, non-prefetchable) [size=1]                                       
                  Region 2: [virtual] Memory at 00000170 (32-bit, non-prefetchable) [size=8]                                       
                  Region 3: [virtual] Memory at 00000370 (type 3, non-prefetchable) [size=1]                                       
                  Region 4: I/O ports at e600 [size=16]                  
                  Capabilities: [c0] Power Management version 2              
                      Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)                                   
                      Status: D0 PME-Enable- DSel=0 DScale=0 PME-           
                  Kernel driver in use: pata_via                     
                  Kernel modules: pata_via                        
              
              00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)                                    
                  Subsystem: Micro-Star International Co., Ltd. Device 7104        
                  Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-                          
                  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-                         
                  Latency: 32, Cache Line Size: 32 bytes                 
                  Interrupt: pin A routed to IRQ 21                    
                  Region 4: I/O ports at e700 [size=32]                  
                  Capabilities: [80] Power Management version 2              
                      Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)                                  
                      Status: D0 PME-Enable- DSel=0 DScale=0 PME-           
                  Kernel driver in use: uhci_hcd                     
                  Kernel modules: uhci-hcd                        
              
              00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)                                    
                  Subsystem: Micro-Star International Co., Ltd. Device 7104        
                  Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-                          
                  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-                         
                  Latency: 32, Cache Line Size: 32 bytes                 
                  Interrupt: pin A routed to IRQ 21                    
                  Region 4: I/O ports at e800 [size=32]                  
                  Capabilities: [80] Power Management version 2              
                      Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)                                  
                      Status: D0 PME-Enable- DSel=0 DScale=0 PME-           
                  Kernel driver in use: uhci_hcd                     
                  Kernel modules: uhci-hcd                        
              
              00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)                                    
                  Subsystem: Micro-Star International Co., Ltd. Device 7104        
                  Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-                          
                  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-                         
                  Latency: 32, Cache Line Size: 32 bytes                 
                  Interrupt: pin B routed to IRQ 21                    
                  Region 4: I/O ports at e900 [size=32]                  
                  Capabilities: [80] Power Management version 2              
                      Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)                                  
                      Status: D0 PME-Enable- DSel=0 DScale=0 PME-           
                  Kernel driver in use: uhci_hcd                     
                  Kernel modules: uhci-hcd                        
              
              00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)                                    
                  Subsystem: Micro-Star International Co., Ltd. Device 7104        
                  Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-                          
                  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-                         
                  Latency: 32, Cache Line Size: 32 bytes                 
                  Interrupt: pin B routed to IRQ 21                    
                  Region 4: I/O ports at ea00 [size=32]                  
                  Capabilities: [80] Power Management version 2              
                      Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)                                  
                      Status: D0 PME-Enable- DSel=0 DScale=0 PME-           
                  Kernel driver in use: uhci_hcd                     
                  Kernel modules: uhci-hcd                        
              
              00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86) (prog-if 20)
                  Subsystem: Micro-Star International Co., Ltd. Device 7104      
                  Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-                          
                  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-                         
                  Latency: 32, Cache Line Size: 128 bytes                 
                  Interrupt: pin C routed to IRQ 21                    
                  Region 0: Memory at f6000000 (32-bit, non-prefetchable) [size=256]   
                  Capabilities: [80] Power Management version 2              
                      Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)                                  
                      Status: D0 PME-Enable- DSel=0 DScale=0 PME-           
                  Kernel driver in use: ehci_hcd                     
                  Kernel modules: ehci-hcd                        
              
              00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South]                                    
                  Subsystem: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South]                                     
                  Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- DisINTx-                          
                  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-                         
                  Latency: 0                               
                  Capabilities: [c0] Power Management version 2              
                      Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)                                   
                      Status: D0 PME-Enable- DSel=0 DScale=0 PME-           
                  Kernel modules: i2c-viapro                       
              
              00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60)                          
                  Subsystem: Micro-Star International Co., Ltd. Device b012        
                  Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-                          
                  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-                         
                  Interrupt: pin C routed to IRQ 22                    
                  Region 0: I/O ports at eb00 [size=256]                 
                  Capabilities: [c0] Power Management version 2              
                      Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)                                   
                      Status: D0 PME-Enable- DSel=0 DScale=0 PME-           
                  Kernel driver in use: VIA 82xx Audio                  
                  Kernel modules: snd-via82xx                       
              
              00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78)
                  Subsystem: Micro-Star International Co., Ltd. Device 7104       
                  Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-                          
                  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-                         
                  Latency: 32 (750ns min, 2000ns max), Cache Line Size: 32 bytes     
                  Interrupt: pin A routed to IRQ 23                    
                  Region 0: I/O ports at ec00 [size=256]                 
                  Region 1: Memory at f6001000 (32-bit, non-prefetchable) [size=256]   
                  Capabilities: [40] Power Management version 2              
                      Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)                                   
                      Status: D0 PME-Enable- DSel=0 DScale=0 PME-           
                  Kernel driver in use: via-rhine
                  Kernel modules: via-rhine
              
              01:00.0 VGA compatible controller: VIA Technologies, Inc. KM400/KN400/P4M800 [S3 UniChrome] (rev 01)
                  Subsystem: Micro-Star International Co., Ltd. Device 7104
                  Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
                  Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
                  Latency: 32 (500ns min)
                  Interrupt: pin A routed to IRQ 16
                  Region 0: Memory at f0000000 (32-bit, prefetchable) [size=64M]
                  Region 1: Memory at f4000000 (32-bit, non-prefetchable) [size=16M]
                  [virtual] Expansion ROM at f5000000 [disabled] [size=64K]
                  Capabilities: [60] Power Management version 2
                      Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                      Status: D0 PME-Enable- DSel=0 DScale=0 PME-
                  Capabilities: [70] AGP version 3.0
                      Status: RQ=256 Iso- ArqSz=0 Cal=7 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3+ Rate=x4,x8
                      Command: RQ=8 ArqSz=0 Cal=0 SBA+ AGP+ GART64- 64bit- FW- Rate=x8
              i am waiting for reply and thanks for help frds...

              Comment


                #8
                Re: xorg.config is empty? resolution problem

                hi no one reply so i just search something and try replace my xorg.conf contain.but after restart it only get command prompt no gui so agin i delete all contain xorg.conf now it same as prev. only two option for resolution ie(640x330) and (640x400) pls tell me how to increase it.
                waiting for reply

                Comment


                  #9
                  Re: xorg.config is empty? resolution problem

                  Open your xorg.conf file and post it here in a code box.

                  I didn't ask that before because I understood you to say that your xorg.conf was empty -- meaning not having any contents at all. So if you actually have something in it, we can build on that or modify it to work.

                  Also, what resolutions does that chip and your monitor support? and what resolution are you wanting to use?
                  The next brick house on the left
                  Intel i7 11th Gen | 16GB | 1TB | KDE Plasma 5.27.11​| Kubuntu 24.04 | 6.8.0-31-generic



                  Comment


                    #10
                    Re: xorg.config is empty? resolution problem

                    If I understood correctly, you manually deleted every single character in xorg.conf

                    If that is correct, you should try to press ESC during startup and select the Ubuntu Recovery Mode, then select "Repair X-server" or so.
                    It will regenerate your xorg.conf.

                    If that doesn't solve your problem right away, try
                    Code:
                    sudo aptitude install xserver-xorg-video-openchrome
                    Reboot and look if it works.
                    If you still can't find the resolution you need, reboot again and try the "Recovery Mode - Fix X-server" thing again.

                    If it still doesn't work, post the contents of xorg.conf (and any specifications about the behaviour of the system).

                    --------
                    I found this thread (in dutch), which I post here, so I can find it if we need it at a later time. I recommend NOT to copy paste any xorg.conf contents in thread referenced below without looking carefully at what it says. First try the above and report back.
                    http://forum.ubuntu-nl.org/index.php?topic=35255.0
                    Once your problem is solved please edit the first post of your topic and add [SOLVED] in front of the subject. In that way, others can benefit from your experience!

                    Comment


                      #11
                      Re: xorg.config is empty? resolution problem

                      i need 1024x768 resolution which i have in windows

                      results for :sudo aptitude install xserver-xorg-video-openchrome
                      Code:
                      kuldeep@ubuntu:~$ sudo aptitude install xserver-xorg-video-openchrome
                      [sudo] password for kuldeep:
                      Reading package lists... Done
                      Building dependency tree
                      Reading state information... Done
                      Reading extended state information
                      Initializing package states... Done
                      No packages will be installed, upgraded, or removed.
                      0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
                      Need to get 0B of archives. After unpacking 0B will be used.
                      Writing extended state information... Done
                      Reading package lists... Done
                      Building dependency tree
                      Reading state information... Done
                      Reading extended state information
                      Initializing package states... Done
                      as it say
                      0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
                      so i dont think so any thing happen with this

                      after fix xserver in recovery mode
                      xorg.conf content
                      Code:
                      # xorg.conf (X.Org X Window System server configuration file)
                      #
                      # This file was generated by dexconf, the Debian X Configuration tool, using
                      # values from the debconf database.
                      #
                      # Edit this file with caution, and see the xorg.conf manual page.
                      # (Type "man xorg.conf" at the shell prompt.)
                      #
                      # This file is automatically updated on xserver-xorg package upgrades *only*
                      # if it has not been modified since the last upgrade of the xserver-xorg
                      # package.
                      #
                      # Note that some configuration settings that could be done previously
                      # in this file, now are automatically configured by the server and settings
                      # here are ignored.
                      #
                      # If you have edited this file but would like it to be automatically updated
                      # again, run the following command:
                      # sudo dpkg-reconfigure -phigh xserver-xorg
                      
                      Section "Device"
                      	Identifier	"Configured Video Device"
                      EndSection
                      
                      Section "Monitor"
                      	Identifier	"Configured Monitor"
                      EndSection
                      
                      Section "Screen"
                      	Identifier	"Default Screen"
                      	Monitor		"Configured Monitor"
                      	Device		"Configured Video Device"
                      EndSection
                      look i am really new to linux that's why i am getting this problem. i am try to fix it bcoz i really want to use it . so pls help me, and i really appreciate ur help
                      thanks frds.

                      Comment


                        #12
                        Re: xorg.config is empty? resolution problem

                        Can you give the result of:
                        Code:
                        sudo lsmod | grep via
                        Something similar in the forums:
                        http://ubuntuforums.org/showthread.php?t=1014593

                        Comment


                          #13
                          Re: xorg.config is empty? resolution problem

                          One thing to note... KDE 4 is less reliant upon the xorg.conf file. It can still be used but the typical information loaded there by default in an installation is usually very minimal even if the eye candy works.

                          Instead of going into the recovery console you have the option of running the xorg.conf recreate command of:

                          sudo dpkg-reconfigure -phigh xserver-xorg

                          That can be done in konsole or in a CLI only session will walk you through recreating the conf file.
                          ( Ctrl+F1 thru F6 , Ctrl+F7 is the default GUI if you have not used these features before )

                          After you do that log out, and hit Alt+E to reset the Xserver, log back in and see if that worked.
                          It may not and you may need to reboot instead of just a simple Xserver reset.

                          I cannot help much with the VIA hardware though.
                          Been round and round the block on my ATI hardware though trying many different configurations and many resets to get better resolution.
                          Kubuntu 18.04 on AMD

                          Comment


                            #14
                            Re: xorg.config is empty? resolution problem

                            This chip encounters a bug: https://bugs.launchpad.net/ubuntu/+s...rg/+bug/293326

                            I think that if you replace your xorg.conf with the following, it will work (you can leave the lines with # in the file):
                            Code:
                            Section "Module"
                              Load  "dri"
                              Load  "glx"
                            EndSection
                            
                            Section "Device"
                            	Identifier	"VIA Technologies, Inc. VT8378 [S3 UniChrome] Integrated Video"
                                Driver       "openchrome"
                            	BusID		"PCI:1:0:0"
                            EndSection
                            
                            Section "Monitor"
                            	Identifier	"Generic Monitor"
                            	Option		"DPMS"
                            	HorizSync	    28-51
                            	VertRefresh	43-60
                            EndSection
                            
                            Section "Screen"
                            	Identifier	"Default Screen"
                            	Device		"VIA Technologies, Inc. VT8378 [S3 UniChrome] Integrated Video"
                            	Monitor		"Generic Monitor"
                            	DefaultDepth	24
                            	SubSection "Display"
                            		Depth		1
                            		Modes		"1024x768" "800x600" "640x480"
                            	EndSubSection
                            	SubSection "Display"
                            		Depth		4
                            		Modes		"1024x768" "800x600" "640x480"
                            	EndSubSection
                            	SubSection "Display"
                            		Depth		8
                            		Modes		"1024x768" "800x600" "640x480"
                            	EndSubSection
                            	SubSection "Display"
                            		Depth		15
                            		Modes		"1024x768" "800x600" "640x480"
                            	EndSubSection
                            	SubSection "Display"
                            		Depth		16
                            		Modes		"1024x768" "800x600" "640x480"
                            	EndSubSection
                            	SubSection "Display"
                            		Depth		24
                            		Modes		"1024x768" "800x600" "640x480"
                            	EndSubSection
                            EndSection
                            
                            Section "DRI"
                            	Mode	0666
                            EndSection
                            One comment: the copied values for HorizSync and VertRefresh might be different from what is supported by your monitor. These values are used to determine which video modes can be used on your system. I don't know if it can do any harm to your screen to set these values too high (anyone?). Else, you can look in the manual of your monitor for these values.
                            Once your problem is solved please edit the first post of your topic and add [SOLVED] in front of the subject. In that way, others can benefit from your experience!

                            Comment


                              #15
                              Re: xorg.config is empty? resolution problem

                              Guys, see this article by Jack Wallen lamenting about empty xorg.conf...

                              http://ct.techrepublic.com.com/click...CHREPUBLIC&s=5

                              Comment

                              Working...
                              X