FedoraProject - Recent changes [en]

User:Gtwilliams

2013-05-19T20:27:03Z

‎Controlling Backlight on Dell XPS-13 in Fedora 18:

Test Results:Fedora 19 Beta RC2 Install

2013-05-19T20:03:56Z

‎General Tests:

File:Backlight.tar.gz

2013-05-19T20:02:48Z

Gtwilliams uploaded "File:Backlight.tar.gz" Small daemon to watch backlight changes on XPS-13 and re-enable them each change.

User:Gtwilliams

2013-05-19T20:00:07Z

XPS-13 Backlight Control in Fedora 18

New page

== Controlling Backlight on Dell XPS-13 in Fedora 18 ==

I just bought a Dell XPS-13 which comes installed with Ubuntu. I didn't want that, so I installed Fedora 18 from a USB stick. I did test a bit with the shipped OS and all the power management stuff Just Works(tm).

The first thing I noticed after installing Fedora was that the display backlight controls were inoperative. The OSD pops up displaying the brightness level when you press one of the keys to control brightness or when, due to idle, the power management function adjusts the brightness. Doing some searches on Google turned up the suggestion to do this to enable the backlight control:

<code>echo 0 >/sys/class/backlight/intel_backlight/brightness</code>

Well, that immediately enables the backlight controls and all appears to work fine. For a while. Eventually the system reverts to the disabled state on backlight control.

I don't know what all this means. I read that a bug on the kernel should be opened in this case and someone has done that, [https://bugzilla.redhat.com/show_bug.cgi?id=928688|BZ 928688].

But in the mean time, I figured out how to work around this problem more effectively. Here's a small daemon that starts up at boot-time and watches for changes to the backlight level and continuously re-enables the function when it "sees" a change.

[[File:backlight.tar.gz]]

Test Results:Fedora 19 Beta RC2 Install

2013-05-19T19:36:31Z

‎General Tests:

Solutions Libres et Open Source 2013

2013-05-19T18:39:33Z

‎Who ?:

Test Results:Fedora 19 Beta RC2 Install

2013-05-19T17:56:42Z

‎General Tests:

PackagingDrafts/MinGWCrossCompiler

2013-05-19T16:53:32Z

markup

User:Sagitter

2013-05-19T16:04:27Z

‎Proposed packages for Fedora:

Pt BR/Projetos/Censo 2013

2013-05-19T15:40:19Z

‎Sobre este documento:

PackagingDrafts/MinGWCrossCompiler

2013-05-19T15:22:59Z

markup

Pt BR/Projetos/Censo 2013

2013-05-19T15:18:40Z

‎Sobre este documento:

PackagingDrafts/MinGWCrossCompiler

2013-05-19T15:08:08Z

The guidelines apply to all current Fedora releases

Features/Hadoop

2013-05-19T13:48:54Z

‎Current status:

Test Day:2013-05-09 SSSD Improvements and AD Integration

2013-05-19T13:48:09Z

‎Tests: Basics of sssd and realmd:

QA/Test Days/Anaconda-usability-test-day

2013-05-19T12:37:23Z

‎iSCSI target setup:

Test Day:2013-05-09 SSSD Improvements and AD Integration

2013-05-19T11:56:36Z

‎Tests: Basics of sssd and realmd:

QA/Test Days/Anaconda-usability-test-day

2013-05-19T11:46:16Z

‎iSCSI target setup:

Test Day:2013-05-09 SSSD Improvements and AD Integration

2013-05-19T11:36:37Z

‎Tests: Basics of sssd and realmd:

Name suggestions for Fedora 20

2013-05-19T11:16:07Z

‎Suggestion Table:

Test Day:2013-05-09 Red Hat Test Bed

2013-05-19T11:10:21Z

‎Currently used accounts:

QA/Test Days/Anaconda-usability-test-day

2013-05-19T11:03:09Z

‎Initial setup:

Upgrading Fedora using yum/it

2013-05-19T10:15:35Z

‎Fedora 18 -> Fedora 19 (pre release branched):

Upgrading Fedora using yum

2013-05-19T09:46:57Z

‎Fedora 18 -> Fedora 19 (pre release branched):

QA/Test Days/Anaconda-usability-test-day

2013-05-19T08:47:19Z

Features/Php55

2013-05-19T08:18:56Z

‎Dependencies:

QA/Test Days/Anaconda-usability-test-day

2013-05-19T08:05:57Z

Ambassadors/MembershipService/VerificationStats

2013-05-19T05:55:21Z

2013-05-19 05:55:09.741439

Ambassadors/MembershipService/Verification2

2013-05-19T05:55:12Z

2013-05-19 05:55:09.741439

Show changes

@@ Line 285: / Line 285: @@
 | [[QA:Testcase_Anaconda_autopart_(use_free_space)_install]]
 | {{result|pass|boblfoot}}
-| {{result|none}}
+| {{result|pass|boblfoot}}
 | style="background:lightgrey;"|
 |-
@@ Line 376: / Line 376: @@
 | [[QA:Testcase_Anaconda_User_Interface_serial_console]]
 | {{result|pass|boblfoot}}
-| {{result|fail|lbrabec|964176}}
+| {{result|fail|lbrabec|964176}}{{result|pass|boblfoot}}
 | style="background:lightgrey;"|
 |-
@@ Line 418: / Line 418: @@
 | [[QA:Testcase_install_repository_NFS_variation]]
 | {{result|pass|boblfoot}}
-| {{result|none}}
+| {{result|pass|boblfoot}}
 | style="background:lightgrey;"|
 |-

@@ Line 284: / Line 284: @@
 | Partitioning
 | [[QA:Testcase_Anaconda_autopart_(use_free_space)_install]]
-| {{result|none}}
+| {{result|pass|boblfoot}}
 | {{result|none}}
 | style="background:lightgrey;"|
@@ Line 375: / Line 375: @@
 | User Interface
 | [[QA:Testcase_Anaconda_User_Interface_serial_console]]
-| {{result|none}}
+| {{result|pass|boblfoot}}
 | {{result|fail|lbrabec|964176}}
 | style="background:lightgrey;"|
@@ Line 417: / Line 417: @@
 | Install Repository
 | [[QA:Testcase_install_repository_NFS_variation]]
-| {{result|none}}
+| {{result|pass|boblfoot}}
 | {{result|none}}
 | style="background:lightgrey;"|

@@ Line 24: / Line 24: @@
 | [[User:Abompard|Aurélien Bompard]] || Fedora || {{check}} || {{check}} || {{check}}  || {{check}}
 |-
-| [[User:Remi|Remi Collet]] || Fedora || +/- || {{check}} || +/- || {{check}}
+| [[User:Remi|Remi Collet]] || Fedora || +/- || {{check}} || {{check}} || +/-
 |}

@@ Line 298: / Line 298: @@
 | Partitioning
 | [[QA:Testcase_Anaconda_autopart_(shrink)_install]]
-| {{result|none}}
+| {{result|pass|boblfoot}}
 | {{result|pass|lnie}}{{result|pass|boblfoot}}
 | style="background:lightgrey;"|
@@ Line 333: / Line 333: @@
 | Partitioning
 | [[QA:Testcase_dualboot_with_windows]]
-| {{result|none}}
+| {{result|warn|boblfoot|964586}}
-| {{result|fail|boblfoot|964586}}
+| {{result|warn|boblfoot|964586}}
 | style="background:lightgrey;"|
 |-
@@ Line 600: / Line 600: @@
 | [[QA:Testcase_upgrade_fedup_cli_previous_desktop_encrypted]]
 | {{result|pass|boblfoot}}
-| {{result|inprogress|boblfoot}}
+| {{result|pass|boblfoot}}
 | {{result|none}}
 |-

@@ Line 448: / Line 448: @@
 The reason for this is that libtool is very fragile and will give up on building a DLL very easily.  Therefore we force the name of the DLL to be listed explicitly in the <code>%files</code> section in order to catch this during RPM builds.
 == Stripping ==
@@ Line 481: / Line 476: @@
 It is allowed to bundle all executables which built while compiling libraries in the binary rpms.
 These executables have to be added to the main <code>mingw32-foo</code> / <code>mingw64-foo</code> subpackages (where the regular libraries and headers are also placed).
 = Example Specfile =

@@ Line 6: / Line 6: @@
 The first thing I noticed after installing Fedora was that the display backlight controls were inoperative.  The OSD pops up displaying the brightness level when you press one of the keys to control brightness or when, due to idle, the power management function adjusts the brightness.  Doing some searches on Google turned up the suggestion to do this to enable the backlight control:
-<code>echo 0 >/sys/class/backlight/intel_backlight/brightness</code>
+<pre>echo 0 >/sys/class/backlight/intel_backlight/brightness</pre>
 Well, that immediately enables the backlight controls and all appears to work fine.  For a while.  Eventually the system reverts to the disabled state on backlight control.
@@ Line 14: / Line 14: @@
 But in the mean time, I figured out how to work around this problem more effectively.  Here's a small daemon that starts up at boot-time and watches for changes to the backlight level and continuously re-enables the function when it "sees" a change.
-[[File:backlight.tar.gz]]
+[[:File:backlight.tar.gz]]

@@ Line 35: / Line 35: @@
 *<del>'''metis''' Serial Graph Partitioning and Fill-reducing Matrix Ordering [https://bugzilla.redhat.com/show_bug.cgi?id=920518 Bug920512]</del>
 *'''ScoPy'''  Python application to play to Scopa, Italian card game [https://bugzilla.redhat.com/show_bug.cgi?id=890859 Bug890859] <br/>
-*'''Ipopt'''  Large-scale optimisation solver <del>[https://bugzilla.redhat.com/show_bug.cgi?id=908089 Bug908089]</del> See [https://bugzilla.redhat.com/show_bug.cgi?id=894604 Bug894604] <br/>
+*<del>'''Ipopt'''  Large-scale optimisation solver <del>[https://bugzilla.redhat.com/show_bug.cgi?id=908089 Bug908089]</del> <del> See [https://bugzilla.redhat.com/show_bug.cgi?id=894604 Bug894604] </del> <br/>
 *<del>'''xgraph''' XGraph with animation [https://bugzilla.redhat.com/show_bug.cgi?id=908090 Bug908090]</del> <br/>
 *'''ascend''' ASCEND modelling environment [https://bugzilla.redhat.com/show_bug.cgi?id=908088 Bug908088] <br/>

@@ Line 16: / Line 16: @@
 | [[User:apahim|Amador Pahim]] 	         	    	   	   || Natal                || RN ||   Sim   ||  Fedora Ambassadors, Traduções, etc.                                       ||
 |-
-| [[User:Penasio|Claudio Penasio Jr.]] 	         	    	   || São Paulo                || SP ||   Sim   ||  Fedora Ambassadors                                   ||
+| [[User:Penasio|Claudio Penasio Jr.]] 	         	    	   || São Paulo            || SP ||   Sim   ||  Fedora Ambassadors
 |-
 | [[User:dbruno|Daniel Bruno]]    	        		   || Manaus               || AM ||   Sim   || Fedora Ambassadors, Mentor de novos embaixadores LATAM, Packager, Fedora Big Data Sig, etc..                                          ||

← Older revision		Revision as of 15:22, 19 May 2013
(2 intermediate revisions by one user not shown)
Line 474:		Line 474:

	The <code>%{?mingw_debug_package}</code> line must be placed after the <code>%description tag</code>. Otherwise spectool and other RPM tools may fail to function		The <code>%{?mingw_debug_package}</code> line must be placed after the <code>%description tag</code>. Otherwise spectool and other RPM tools may fail to function
		+
		+	= Executables (EXEs) =
		+
		+	Most libraries also provide executables. These can include executables which can be used to test or showcase the library in question (for example gtk3-demo.exe in mingw-gtk3).
		+	Other examples are helper executables which are used by the library itself internally (for example gspawn-win32-helper.exe in mingw-glib2).
		+	It is allowed to bundle all executables which built while compiling libraries in the binary rpms.
		+	These executables have to be added to the main <code>mingw32-foo</code> / <code>mingw64-foo</code> subpackages (where the regular libraries and headers are also placed).

	= Example Specfile =		= Example Specfile =

@@ Line 1: / Line 1: @@
 = Packaging Guidelines for MinGW Cross Compilers =
-{{admon/important|Updated Guidelines|These guidelines are active as of Fedora 17. For older Fedora releases (including RHEL-6 and older) the old guidelines still apply which can be be found here: [[Packaging:MinGW_Old]] }}
+{{admon/important|Updated Guidelines|These guidelines apply to all current Fedora releases. For RHEL-5 and RHEL-6 the old guidelines still apply which can be be found here: [[Packaging:MinGW_Old]] }}
 = Introduction =

@@ Line 58: / Line 58: @@
 ** Hadoop spec completion: 60%
 * Test suite
 ** hadoop-hdfs Tests run: 1443, Failures: 5, Errors: 1, Skipped: 3
 ** Disabled: 40 classes (see log below)

@@ Line 387: / Line 387: @@
 | {{result|pass}}
 | {{result|pass}}
+| {{result|fail}} <ref>{{bz|964675}}</ref>
+| {{result|pass}}
+| {{result|pass}} <ref>{{bz|964675}}</ref> <ref>{{bz|961235}}</ref>
+| {{result|pass}}
+| {{result|pass}} <ref>{{bz|964675}}</ref> <ref>{{bz|961235}}</ref>
+| {{result|fail}} <ref>unable to join, can't consult with DC admin, no bug filled</ref>
 | <references/>
 |}

@@ Line 14: / Line 14: @@
 == Initial setup ==
 * have a Fedora 19 Beta RC2 (virtual) machine owned by you, ISO image available at [http://alt.fedoraproject.org/pub/alt/stage/19-Beta-RC2/Fedora/x86_64/iso/Fedora-19-Beta-x86_64-DVD.iso] or [http://alt.fedoraproject.org/pub/alt/stage/19-Beta-RC2/Fedora/i386/iso/Fedora-19-Beta-i386-DVD.iso]
-* alternatively you can use prepared image available at [https://docs.google.com/uc?export=download&confirm=no_antivirus&id=0B_1DLrmpME2zUjQ2el96ekt1OW8]
+* alternatively you can use prepared image available at [https://drive.google.com/uc?export=download&confirm=no_antivirus&id=0B_1DLrmpME2zY09vMzVCS1cwOTg]
 === <code>iSCSI target</code> setup ===
 * prepare iSCSI volume on another VM (called here <code>iscsi_target</code> VM) which is reachable from VM where the installation will be performed
-{{admon/note|Note|Alternatively, you can use prepared images that can be downloaded from [https://docs.google.com/file/d/0B_1DLrmpME2zeW5Mblh2RHIyWXc/edit?usp=sharing]}}
+* Alternatively, you can use prepared images that can be downloaded from [https://drive.google.com/uc?export=download&confirm=no_antivirus&id=0B_1DLrmpME2zZFB5cndpYnJfNDQ]
 <b> Setting up <code>iscsi_target</code> virtual machine </b>
 {{admon/important|Packages needed|you need to have python-virtinst, libvirt, virt-manager and virt-viewer installed on your computer}}
-    # virt-install -n iscsi-target -r 512 --arch x86_64 --import --os-type linux --os-variant rhel7 --disk /var/lib/libvirt/images/iscsi-target.img --serial pty --graphics spice
+ # cd /var/lib/libvirt/images
 * root password is <code>fedora</code>
@@ Line 55: / Line 68: @@
      # service tgtd start
-{{admon/note|Note|If <code>tgtd</code> refuses to start, try to start one more time.}}
+{{admon/note|Note|If <code>tgtd</code> refuses to start, try to start it one more time.}}
 = Usability scenarios =
@@ Line 79: / Line 92: @@
 * Finish the installation and reboot
-== iSCSI target is part of LVM VG (anaconda-lvm-2) ==
+== iSCSI target is part of LVM Volume Group (anaconda-lvm-2) ==
 === Setup ===
 * have virtual machine (VM) with at least one disk ready

@@ Line 104: / Line 104: @@
 |-
 | the Doctor || Schrödinger's Cat is in a box and is related to time and space, the Doctor is in an (blue) box and is related to time and space. || an english society is called doctorsoftware (http://www.doctorsoftware.co.uk/) || || Doctor Who is the oldest SF TV show in the world. As a Time Lord, the Doctor has travel everywhere and everytime ||Very easily || ||
 |-
 |}

@@ Line 99: / Line 99: @@
 Each user has a pre-set password: <code>'''Pass2012!'''</code>
 {|
-!User!!Members of!!User by
+!User!!Members of!!Used by
 |-
 |Amy||amy, planetexpress, testusers||
@@ Line 107: / Line 107: @@
 |Dwight||dwight, planetexpress, testusers||
 |-
-|Hermes||hermes ,planetexpress, testusers||
+|Hermes||hermes ,planetexpress, testusers||lnovy
 |-
 |Farnsworth||farnsworth, planetexpress, testusers||

← Older revision		Revision as of 05:55, 19 May 2013
Line 1:		Line 1:
−	{{admon/note \| Last Updated : 2013-05-18 05:57:14.~~935833~~ UTC. 561 active contributors listed here against 644 total.}}	+	{{admon/note \| Last Updated : 2013-05-19 05:55:09.741439 UTC. 561 active contributors listed here against 644 total.}}

@@ Line 188: / Line 188: @@
-<pre>
+Installare la nuova chiave gpg Fedora 19 ed aggiornare:
-##Installare la nuova chiave gpg Fedora 19:
-−
-rpm --import https://fedoraproject.org/static/FB4B18E6.txt
-yum update yum
+ # rpm --import https://fedoraproject.org/static/FB4B18E6.txt
-yum --releasever=19 distro-sync --nogpgcheck
+ # yum update yum
-</pre>
+ # yum --releasever=19 distro-sync --nogpgcheck
 {{Anchor|17-18}}

@@ Line 1: / Line 1: @@
 == General Instructions ==
 * follow steps in use cases
@@ Line 55: / Line 56: @@
 = Usability scenarios =
-== Text mode installation ==
+== Text mode installation (anaconda-text-1) ==
 === Setup ===
 * power on <code>anaconda-usability</code> Virtual Machine
@@ Line 64: / Line 65: @@
 * Finish the installation and reboot
-== Create multiple Volume Groups ==
+== Create multiple Volume Groups (anaconda-lvm-1) ==
 {{admon/important|Multiple hard drives required|You need a machine with 4 or more disks}}
 === Setup ===
@@ Line 76: / Line 77: @@
 * Finish the installation and reboot
-== iSCSI target is part of LVM VG ==
+== iSCSI target is part of LVM VG (anaconda-lvm-2) ==
 === Setup ===
 * have virtual machine (VM) with at least one disk ready
@@ Line 90: / Line 91: @@
 * boot installed system
-== CHAP authentication against iSCSI target ==
+== LVM on top of RAID (anaconda-lvm-3) ==
 {{admon/note|CHAP|Challenge-Handshake Authentication Protocol (CHAP) authenticates a user or network host to an authenticating entity}}
 {{admon/note|iSCSI target|Internet Small Computer System Interface, an Internet Protocol (IP)-based storage networking standard for linking data storage facilities. An iSCSI target is often a dedicated network-connected hard disk storage device, but may also be a general-purpose computer}}
@@ Line 105: / Line 119: @@
 * Place /boot on local disk, / on iSCSI target, do not use LVM
 * Finish the installation, reboot

@@ Line 70: / Line 70: @@
 * ice-3.5-0.4.b.fc19 (ice-php)
 * libdigidocpp-0.3.0-18.fc19 (php-digidoc)
 * libkolabxml-0.8.3-2.fc19 (php-kolabformat)
 * libpuzzle-0.11-17.fc19 (php-libpuzzle)
@@ Line 120: / Line 121: @@
 Not rebuild yet:
 * mapserver (php-mapserver): FTBFS
 * zarafa (php-mapi): FTBFS, broken dep in BR

@@ Line 15: / Line 15: @@
 * alternatively you can use prepared image available at [http://link]
-== Text mode installation ==
+=== <code>iSCSI target</code> setup ===
-* Install Fedora using text mode (append text on kernel command line)
-* Text mode installation will offer you possibility to continue installation remotely using VNC, please don't use it and continue in the text mode
-* In the installer add new user john with admin rights
-−
-== Create multiple Volume Groups ==
-{{admon/important|Multiple hard drives required|You need a machine with more than 4 disks}}
-=== Action ===
-* Start Fedora 19 installation in graphical mode (default)
-* Use manual partitioning, choose LVM partitioning scheme
-* Create four volume groups, one volume group per disk drive
-* Create four mountpoints: /, /var, /tmp, /home and place each of them to separate volume group
-* Place swap partition to the same volume group as /
-−
-iSCSI target is part of LVM VG
-−
-    Setup
-−
-    have virtual machine ready
-−
-    prepare iSCSI volume on physical machine, accessible from VM
-−
-    # tgtadm --lld iscsi --op new --mode target --tid=1 --targetname iqn.2009-02.com.example:for.all
-−
-    # tgtadm --lld iscsi --op new --mode logicalunit --tid 1 --lun 1 -b /dev/loop0
-−
-    # tgtadm --lld iscsi --op bind --mode target --tid 1 -I ALL
-−
-    can you include all steps with short explanation comments what it does
-−
-    Action
-−
-    Install Fedora to VM
-−
-    Use custom partitioning scheme, use LVM
-−
-    set up new LVM VG consisting of one PV from virtual machine + another PV from iSCSI on physical hosta
-−
-−
-== CHAP authentication against iSCSI target ==
-{{admon/note|CHAP|Challenge-Handshake Authentication Protocol (CHAP) authenticates a user or network host to an authenticating entity}}
-{{admon/note|iSCSI target|Internet Small Computer System Interface, an Internet Protocol (IP)-based storage networking standard for linking data storage facilities. An iSCSI target is often a dedicated network-connected hard disk storage device, but may also be a general-purpose computer}}
-=== Setup ===
-* have virtual machine (VM) with at least one disk ready
 * prepare iSCSI volume on another VM (called here <code>iscsi_target</code> VM) which is reachable from VM where the installation will be performed
 {{admon/note|Note|Alternatively, you can use prepared images that can be downloaded from [http://link]}}
-<b> Preparation of <code>iscsi_target</code> VM </b>
+<b> Setting up <code>iscsi_target</code> virtual machine </b>
-{{admon/important|Packages needed|you need to have python-virtinst, libvirt, virt-manager and virt-viewer installed}}
+{{admon/important|Packages needed|you need to have python-virtinst, libvirt, virt-manager and virt-viewer installed on your computer}}
      # virt-install -n iscsi-target -r 512 --arch x86_64 --import --os-type linux --os-variant rhel7 --disk /var/lib/libvirt/images/iscsi-target.img --serial pty --graphics spice
@@ Line 96: / Line 54: @@
      # service tgtd start
-== Action ==
+= Usability scenarios =
 Install Fedora to VM using graphical user interface. In the installer:
-* find Installation Destionation menu
+* find Installation Destination menu
 * Search for iSCSI target and add it to the Advanced & Network disk section
 {{admon/note|Note|If you use provided <code>iscsi-target</code> image, the IP address of iSCSI target is set to <code>192.168.100.100</code><br> Use CHAP authentication. Username/password is <code>consumer/Longsw0rd</code>}}
 * Select another non-iSCSI(local) disk
 * Continue with iSCSI disk + local disk selected
 * Place /boot on local disk, / on iSCSI target, do not use LVM
 * Finish the installation, reboot