Fedora Linux Support Community & Resources Center
  #1  
Old 14th August 2015, 05:51 PM
Vinz1165 Offline
Registered User
 
Join Date: Aug 2015
Location: USA
Posts: 9
windows_7firefox
[Dell D630] Hardware issues after upgrading to F22 (graphics + sleep issues)

Hi everyone,

My name is Vincent and I am coming to you because I am experiencing issues running F22 on a Dell D630 laptop. It is a pretty old configuration but it worked well on F21 (despite showing its age in terms of performance).

I was using F21 with the proprietary nvidia drivers (this is an Nvidia Quadro NVS135M AFAIK). Resolution was OK and all HW was working as expected. I upgraded to F22 using fedup, which failed to upgrade the graphics drivers properly (I think). The upgrade finished with no X running but I could solve this by uninstalling the nvidia drivers.

I am now running nouveau but it fails to properly detect my native screen resolution (1440x900). Instead, it runs in 1280x720. This problem existed in F21 already and I could not solve it which is why I moved to the nvidia drivers.

Could someone tell me where I should look to fix this problem? I am attaching my dmesg, lspci and Xorg logs. Let me know if you need more information from me.

Thanks for your help!

Vincent

PS: The other issues I have are : no KMS (graphical console) and the laptop does not sleep when I close its lid. The former did not work either in F21 but the latter did. I will expand on those as the thread goes.

PPS: I searched the forums for some help but posts I got for this config were all pretty old (due to the age of the HW).
Reply With Quote
  #2  
Old 14th August 2015, 05:56 PM
Vinz1165 Offline
Registered User
 
Join Date: Aug 2015
Location: USA
Posts: 9
windows_7chrome
Re: [Dell D630] Hardware issues after upgrading to F22 (graphics + sleep issues)

Hi again,

I cannot manage to upload my logs. I consistently get an upload error such as : "dmesg.txt:
Upload of file failed." without any error code or reason. The same is true if I put them into a zip file instead and retry.

Is it OK for me to paste those inline here? Any other place I can put them?

Thanks for the guidance,

Vincent

Last edited by Vinz1165; 14th August 2015 at 05:59 PM. Reason: Added info about zip file failure
Reply With Quote
  #3  
Old 14th August 2015, 06:47 PM
DBelton Offline
Administrator
 
Join Date: Aug 2009
Posts: 8,432
linuxfedorafirefox
Re: [Dell D630] Hardware issues after upgrading to F22 (graphics + sleep issues)

Yes, paste them inline. There is an issue with attachments currently.
Reply With Quote
  #4  
Old 14th August 2015, 07:28 PM
Vinz1165 Offline
Registered User
 
Join Date: Aug 2015
Location: USA
Posts: 9
windows_7firefox
Re: [Dell D630] Hardware issues after upgrading to F22 (graphics + sleep issues)

Hi DBelton,

Thanks for your reply. However, pasting does not work either as there is a restriction on the number of characters (10k, my dmesg is 70k). I can only include the lspci output.

I think I would need to be selective on what to include. I have put what I think might be useful.

dmesg:
Code:
[    0.000000] microcode: CPU0 microcode updated early to revision 0x95, date = 2010-10-02
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 4.1.4-200.fc22.x86_64 (mockbuild@bkernel01.phx2.fedoraproject.org) (gcc version 5.1.1 20150618 (Red Hat 5.1.1-4) (GCC) ) #1 SMP Tue Aug 4 03:22:33 UTC 2015
[    0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.1.4-200.fc22.x86_64 root=/dev/mapper/fedora00-root ro rd.lvm.lv=fedora00/root vconsole.font=latarcyrheb-sun16 rd.lvm.lv=fedora00/swap rhgb quiet LANG=en_US.UTF-8
[    0.000000] e820: BIOS-provided physical RAM map:
[    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-4.1.4-200.fc22.x86_64 root=/dev/mapper/fedora00-root ro rd.lvm.lv=fedora00/root vconsole.font=latarcyrheb-sun16 rd.lvm.lv=fedora00/swap rhgb quiet LANG=en_US.UTF-8
[    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[    0.000000] Memory: 2025072K/2095072K available (7835K kernel code, 1242K rwdata, 3268K rodata, 1516K init, 1524K bss, 70000K reserved, 0K cma-reserved)
[    0.233537] vgaarb: setting as boot device: PCI:0000:01:00.0
[    0.233543] vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
[    0.233548] vgaarb: loaded
[    0.233551] vgaarb: bridge control possible 0000:01:00.0
[    2.495281] systemd[1]: systemd 219 running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN)
[    2.495567] systemd[1]: Detected architecture x86-64.
[    2.495574] systemd[1]: Running in initial RAM disk.
[    3.029982] ACPI: Video Device [VID] (multi-head: yes  rom: no  post: no)
[    3.030533] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:2e/LNXVIDEO:00/input/input7
[    3.031421] [Firmware Bug]: Duplicate ACPI video bus devices for the same VGA controller, please try module parameter "video.allow_duplicates=1"if the current driver doesn't work
lspci:
Code:
00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 0c)
00:01.0 PCI bridge: Intel Corporation Mobile PM965/GM965/GL960 PCI Express Root Port (rev 0c)
00:1a.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 02)
00:1a.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 02)
00:1a.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 02)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 02)
00:1c.5 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 6 (rev 02)
00:1d.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 02)
00:1d.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f2)
00:1f.0 ISA bridge: Intel Corporation 82801HM (ICH8M) LPC Interface Controller (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 02)
00:1f.2 IDE interface: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) SATA Controller [IDE mode] (rev 02)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 02)
01:00.0 VGA compatible controller: NVIDIA Corporation G86M [Quadro NVS 135M] (rev a1)
03:01.0 CardBus bridge: O2 Micro, Inc. Cardbus bridge (rev 21)
03:01.4 FireWire (IEEE 1394): O2 Micro, Inc. Firewire (IEEE 1394) (rev 02)
09:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5755M Gigabit Ethernet PCI Express (rev 02)
0c:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
Reply With Quote
  #5  
Old 14th August 2015, 07:38 PM
Vinz1165 Offline
Registered User
 
Join Date: Aug 2015
Location: USA
Posts: 9
windows_7firefox
Re: [Dell D630] Hardware issues after upgrading to F22 (graphics + sleep issues)

And here is my edited Xorg.log, after a pretty tricky editing session to fit in the 10k char limit
Code:
X.Org X Server 1.17.2
Release Date: 2015-06-16
[    25.359] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[    25.370] (II) LoadModule: "glx"
[    25.371] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
[    25.373] (==) AIGLX enabled
[    25.373] (==) Matched nouveau as autoconfigured driver 0
[    25.373] (==) Matched nv as autoconfigured driver 1
[    25.373] (==) Matched modesetting as autoconfigured driver 2
[    25.373] (==) Matched fbdev as autoconfigured driver 3
[    25.373] (==) Matched vesa as autoconfigured driver 4
[    25.373] (==) Assigned the driver to the xf86ConfigLayout
[    25.373] (II) LoadModule: "nouveau"
[    25.374] (II) LoadModule: "nv"
[    25.374] (EE) Failed to load module "nv" (module does not exist, 0)
[    25.374] (II) LoadModule: "modesetting"
[    25.374] (II) LoadModule: "fbdev"
[    25.374] (II) LoadModule: "vesa"
[    25.376] (II) NOUVEAU driver 
[    25.376] (II) NOUVEAU driver for NVIDIA chipset families :
[    25.376] 	RIVA TNT        (NV04)
[    25.376] 	RIVA TNT2       (NV05)
[    25.376] 	GeForce 256     (NV10)
[    25.376] 	GeForce 2       (NV11, NV15)
[    25.376] 	GeForce 4MX     (NV17, NV18)
[    25.376] 	GeForce 3       (NV20)
[    25.376] 	GeForce 4Ti     (NV25, NV28)
[    25.376] 	GeForce FX      (NV3x)
[    25.376] 	GeForce 6       (NV4x)
[    25.376] 	GeForce 7       (G7x)
[    25.376] 	GeForce 8       (G8x)
[    25.376] 	GeForce GTX 200 (NVA0)
[    25.376] 	GeForce GTX 400 (NVC0)
[    25.376] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    25.376] (II) FBDEV: driver for framebuffer: fbdev
[    25.376] (II) VESA: driver for VESA chipsets: vesa
[    25.376] (EE) [drm] KMS not enabled
[    25.376] (EE) open /dev/dri/card0: No such file or directory
[    25.376] (WW) Falling back to old probe method for modesetting
[    25.376] (EE) open /dev/dri/card0: No such file or directory
[    25.376] (II) Loading sub module "fbdevhw"
[    25.376] (EE) open /dev/fb0: No such file or directory
[    25.376] (WW) Falling back to old probe method for fbdev
[    25.376] (II) Loading sub module "fbdevhw"
[    25.376] (EE) open /dev/fb0: No such file or directory
[    25.377] (EE) Screen 0 deleted because of no matching config section.
[    25.377] (II) UnloadModule: "modesetting"
[    25.377] (EE) Screen 0 deleted because of no matching config section.
[    25.377] (II) UnloadModule: "fbdev"
[    25.377] (II) UnloadSubModule: "fbdevhw"
[    25.377] (II) Loading sub module "vbe"
[    25.377] (II) Loading sub module "int10"
[    25.377] (II) VESA(0): initializing int10
[    25.379] (II) VESA(0): Primary V_BIOS segment is: 0xc000
[    25.438] (II) VESA(0): VESA BIOS detected
[    25.439] (II) VESA(0): VESA VBE OEM: NVIDIA
[    25.440] (II) VESA(0): VESA VBE OEM Vendor: NVIDIA Corporation
[    25.440] (II) VESA(0): VESA VBE OEM Product: G86 Board - briscoe0
[    25.441] (II) VESA(0): VESA VBE OEM Product Rev: Chip Rev   
[    25.515] (II) VESA(0): Creating default Display subsection in Screen section
	"Default Screen Section" for depth/fbbpp 24/32
[    25.515] (==) VESA(0): Depth 24, (--) framebuffer bpp 32
[    25.516] (II) Loading sub module "ddc"
[    25.516] (II) LoadModule: "ddc"
[    25.517] (II) Module "ddc" already built-in
[    25.588] (II) VESA(0): VESA VBE DDC supported
[    25.589] (II) VESA(0): VESA VBE DDC Level none
[    25.589] (II) VESA(0): VESA VBE DDC transfer in appr. 0 sec.
[    25.907] (II) VESA(0): VESA VBE DDC read failed
[    25.907] (II) VESA(0): Searching for matching VESA mode(s):
[    25.909] Mode: 100 (640x400)
[    25.911] Mode: 101 (640x480)
[    25.915] Mode: 102 (800x600)
[    25.920] Mode: 103 (800x600)
[    25.926] Mode: 104 (1024x768)
[    25.929] Mode: 105 (1024x768)
[    25.937] Mode: 10e (320x200)
[    25.938] *Mode: 10f (320x200)
[    25.940] Mode: 111 (640x480)
[    25.941] *Mode: 112 (640x480)
[    25.943] Mode: 114 (800x600)
[    25.945] *Mode: 115 (800x600)
[    25.946] Mode: 117 (1024x768)
[    25.948] *Mode: 118 (1024x768)
[    25.949] Mode: 130 (320x200)
[    25.951] Mode: 131 (320x400)
[    25.952] Mode: 132 (320x400)
[    26.063] *Mode: 133 (320x400)
[    26.064] Mode: 134 (320x240)
[    26.066] Mode: 135 (320x240)
[    26.067] *Mode: 136 (320x240)
[    26.069] Mode: 13d (640x400)
[    26.074] *Mode: 13e (640x400)
[    26.079] Mode: 160 (1280x800)
[    26.082] *Mode: 161 (1280x800)
[    26.083] Mode: 162 (768x480)
[    26.087] Mode: 164 (1440x900)
[    26.089] *Mode: 165 (1440x900)
[    26.090] *Mode: 17b (1280x720)
[    26.154] (II) VESA(0): <default monitor>: Using default hsync range of 31.50-48.00 kHz
[    26.154] (II) VESA(0): <default monitor>: Using default vrefresh range of 50.00-70.00 Hz
[    26.154] (II) VESA(0): <default monitor>: Using default maximum pixel clock of 65.00 MHz
[    26.154] (WW) VESA(0): Unable to estimate virtual size
[    26.154] (II) VESA(0): Not using built-in mode "1440x900" (no mode of this name)
[    26.154] (II) VESA(0): Not using built-in mode "1280x800" (no mode of this name)
[    26.154] (II) VESA(0): Not using built-in mode "1280x720" (no mode of this name)
[    26.154] (II) VESA(0): Not using built-in mode "1024x768" (no mode of this name)
[    26.154] (II) VESA(0): Not using built-in mode "800x600" (no mode of this name)
[    26.154] (II) VESA(0): Not using built-in mode "640x480" (no mode of this name)
[    26.154] (II) VESA(0): Not using built-in mode "640x400" (no mode of this name)
[    26.154] (II) VESA(0): Not using built-in mode "320x400" (no mode of this name)
[    26.154] (II) VESA(0): Not using built-in mode "320x240" (no mode of this name)
[    26.154] (II) VESA(0): Not using built-in mode "320x200" (no mode of this name)
[    26.154] (WW) VESA(0): No valid modes left. Trying less strict filter...
[    26.154] (II) VESA(0): <default monitor>: Using hsync range of 31.50-48.00 kHz
[    26.154] (II) VESA(0): <default monitor>: Using vrefresh range of 50.00-70.00 Hz
[    26.154] (II) VESA(0): <default monitor>: Using maximum pixel clock of 65.00 MHz
[    26.154] (WW) VESA(0): Unable to estimate virtual size
[    26.154] (II) VESA(0): Not using built-in mode "1440x900" (hsync out of range)
[    26.154] (II) VESA(0): Not using built-in mode "1280x800" (hsync out of range)
[    26.154] (II) VESA(0): Not using built-in mode "640x400" (hsync out of range)
[    26.154] (II) VESA(0): Not using built-in mode "320x400" (hsync out of range)
[    26.154] (II) VESA(0): Not using built-in mode "320x240" (illegal horizontal timings)
[    26.154] (II) VESA(0): Not using built-in mode "320x200" (illegal horizontal timings)
[    26.154] (--) VESA(0): Virtual size is 1280x768 (pitch 1280)
[    26.154] (**) VESA(0): *Built-in mode "1280x720"
[    26.154] (**) VESA(0): *Built-in mode "1024x768"
[    26.154] (**) VESA(0): *Built-in mode "800x600"
[    26.154] (**) VESA(0): *Built-in mode "640x480"
[    26.154] (II) VESA(0): Attempting to use 60Hz refresh for mode "1024x768" (118)
[    26.155] (II) VESA(0): Attempting to use 60Hz refresh for mode "800x600" (115)
[    26.155] (II) VESA(0): Attempting to use 60Hz refresh for mode "640x480" (112)
[    26.156] (**) VESA(0): Using "Shadow Framebuffer"
[    26.156] (II) Loading sub module "shadow"
[    26.156] (II) LoadModule: "shadow"
[    26.156] (II) Loading /usr/lib64/xorg/modules/libshadow.so
[    26.156] (II) Module shadow: vendor="X.Org Foundation"
[    26.156] (II) Loading sub module "fb"
[    26.156] (II) LoadModule: "fb"
[    26.156] (II) Loading /usr/lib64/xorg/modules/libfb.so
[    26.156] (II) Module fb: vendor="X.Org Foundation"
[    26.157] (==) Depth 24 pixmap format is 32 bpp
[    26.157] (II) Loading sub module "int10"
[    26.157] (II) LoadModule: "int10"
[    26.157] (II) Loading /usr/lib64/xorg/modules/libint10.so
[    26.157] (II) Module int10: vendor="X.Org Foundation"
[    26.157] (II) VESA(0): initializing int10
[    26.157] (II) VESA(0): Primary V_BIOS segment is: 0xc000
[    26.207] (II) VESA(0): VESA BIOS detected
[    26.208] (II) VESA(0): VESA VBE Version 3.0
[    26.208] (II) VESA(0): VESA VBE Total Mem: 14336 kB
[    26.208] (II) VESA(0): VESA VBE OEM: NVIDIA
[    26.208] (II) VESA(0): VESA VBE OEM Software Rev: 96.134
[    26.208] (II) VESA(0): VESA VBE OEM Vendor: NVIDIA Corporation
[    26.208] (II) VESA(0): VESA VBE OEM Product: G86 Board - briscoe0
[    26.208] (II) VESA(0): VESA VBE OEM Product Rev: Chip Rev   
[    26.209] (II) VESA(0): virtual address = 0x7fe50ea26000,
	physical address = 0xf3000000, size = 14680064
[    26.252] (II) VESA(0): Setting up VESA Mode 0x17B (1280x720)
[    26.468] (==) VESA(0): Default visual is TrueColor
[    26.468] (==) VESA(0): Backing store enabled
[    26.468] (==) VESA(0): DPMS enabled
[    26.468] (==) RandR enabled
[    26.473] (II) SELinux: Disabled by boolean
[    26.474] (II) AIGLX: Screen 0 is not DRI2 capable
[    26.474] (EE) AIGLX: reverting to software rendering
[    26.485] (II) AIGLX: Loaded and initialized swrast
[    26.485] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[    26.526] (**) Video Bus: always reports core events
[    26.526] (**) Option "Device" "/dev/input/event6"
Reply With Quote
  #6  
Old 20th August 2015, 06:56 AM
Vinz1165 Offline
Registered User
 
Join Date: Aug 2015
Location: USA
Posts: 9
linuxfedorafirefox
Re: [Dell D630] Hardware issues after upgrading to F22 (graphics + sleep issues)

Hi there,

Some more news on the issue as I actually booted the live image from F22 which does not have the problem: KMS is enabled with the correct resolution right at boot and I immediately get graphical consoles. GNOME does not start though (with the dreaded 'oh no! something has gone wrong' message which I find pretty useless given that there is no mention of any log).

That configuration allowed me to grab an Xorg log from the working configuration. Diffing the two, I can see that mine does not have KMS enabled:
Code:
(II) modesetting: Driver for Modesetting Kernel Drivers: kms
 (II) FBDEV: driver for framebuffer: fbdev
 (II) VESA: driver for VESA chipsets: vesa
 (++) using VT number 2

 KMS not enabled
 (EE) open /dev/dri/card0: No such file or directory
 (WW) Falling back to old probe method for modesetting
whereas the liveCD has it:
Code:
(II) modesetting: Driver for Modesetting Kernel Drivers: kms
 (II) FBDEV: driver for framebuffer: fbdev
 (II) VESA: driver for VESA chipsets: vesa
 xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
 nouveau interface version: 1.2.1
 (WW) Falling back to old probe method for modesetting
Looking earlier in the log, I can see the working config has that line:
Code:
 (II) xfree86: Adding drm device (/dev/dri/card0)
 (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 9 paused 0
This might explain the non-graphical consoles (no KMS) and most likely the non-detection of the screen native resolution (although it did not seem to me DRI was needed for that).

I also get a little differences on the ordering of the autoconfigured drivers. The working case has :
Code:
(==) AIGLX enabled
 (==) Matched nouveau as autoconfigured driver 0
 (==) Matched nv as autoconfigured driver 1
 (==) Matched nouveau as autoconfigured driver 2
 (==) Matched nv as autoconfigured driver 3
 (==) Matched modesetting as autoconfigured driver 4
 (==) Matched fbdev as autoconfigured driver 5
 (==) Matched vesa as autoconfigured driver 6
 (==) Assigned the driver to the xf86ConfigLayout
 (II) LoadModule: "nouveau"
while the broken install has :
Code:
(==) AIGLX enabled
 (==) Matched nouveau as autoconfigured driver 0
 (==) Matched nv as autoconfigured driver 1
 (==) Matched modesetting as autoconfigured driver 2
 (==) Matched fbdev as autoconfigured driver 3
 (==) Matched vesa as autoconfigured driver 4
 (==) Assigned the driver to the xf86ConfigLayout
 (II) LoadModule: "nouveau"
Could anyone with KMS/gfx knowledge help pinpoint the issue here? Does the driver ordering matter? Who is in charge of creating the /dev/dri/card0? Is that udev?

Thanks for your insight!

Vincent
Reply With Quote
Reply

Tags
d630, dell, f22, graphics, hardware, issues, nvidia, sleep, upgrading

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Issues waking from Hibernation/Sleep mode jaybone Hardware & Laptops 3 21st November 2009 02:50 AM
[Fedora 11] Graphics Issues -- Dell Dimension 2400 codenamegimmick Using Fedora 10 27th October 2009 08:06 PM
Dell Fan, ACPI, Sound, LCD Hardware Issues Rager1 Hardware & Laptops 1 29th January 2009 11:06 PM
Issues in hibernate and sleep with F9 on Laptop abhishek_kr7 Hardware & Laptops 6 15th September 2008 10:28 AM
Fedora 9 and Dell Wireless 5520 on Dell D630 gammag Hardware & Laptops 0 9th June 2008 07:34 AM


Current GMT-time: 18:19 (Tuesday, 25-04-2017)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat