March 2010

[opensuse-factory] nouveau ABI major version change
by Brian Millett 31 Mar '10

31 Mar '10

I'm using the opensuse 11.3 milestone 4 and have been using the nouveau driver. After the latest zypper update, I now get the following nouveau error (II) LoadModule: "nouveau" (II) Loading /usr/lib64/xorg/modules/drivers/nouveau_drv.so (II) Module nouveau: vendor="X.Org Foundation" compiled for 1.7.99.902, module version = 0.0.15 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 7.0 (EE) module ABI major version (7) doesn't match the server's … [View More]

2 1

Re: [opensuse-factory] Firefox persona for openSUSE
by Atri Bhattacharya 31 Mar '10

31 Mar '10

Forwarding original message and response. On Tue, 2010-03-30 at 15:56 +0200, Jakub Rusinek wrote: > > I think it would be nice to give users the most native appearance under > both KDE and GNOME they can get... Using Personas by default would only > confuse them. > The basic user interface would still remain as integrated with the desktop as it is now, I was not talking of a garish theme that makes firefox look like a rain forest, but a subtle one that makes it look more … [View More]

2 1

[opensuse-factory] Firefox persona for openSUSE
by Atri Bhattacharya 30 Mar '10

30 Mar '10

Hi! Since v 3.6 Firefox supports light themes called personas. I think it will be nice to have a default opensuse-themed persona on Firefox by default for 11.3. -- Atri -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

1 0

[opensuse-factory] kde4.4 and compiz
by dale ritchey 30 Mar '10

30 Mar '10

After sundays factory update compositing with kde's desktop effects really doesn't work but compiz woks quite well. Which hasn't really worked with kde until sundays update. Is this planned or should I file a bug report? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 1

[opensuse-factory] should Office pattern NOT install openoffice?
by Andrea Florio 30 Mar '10

30 Mar '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi people, as you know, i'm working on LXDE into 11.3 i noticed a strange thing with Office pattern. if you install office pattern, it will install OO.o this is imho wrong... in particular for xfce and lxde, that may want to use a lighter solution (check lxde-office pattern). i think, that Office pattern sould install "nothing" and call as "dependencie" $DE_office pattern something like "imaging" pattern.. what do you think about it? - -- - -… [View More]

7 8

[opensuse-factory] Milestone 4 Announcement Review
by Andreas Jaeger 30 Mar '10

30 Mar '10

I'd like to see Milestone 4 announced tomorrow and have drafted the following announcement. Please review it and send me suggestions on improving the text. If you want to rewrite it completely, I'm fine as well ;) I'd like to see from packagers a few more details on the major packaging changes, enhancements are welcome. Thanks, Andreas [Graphic: Geeko at work from MIlestone3] The fourth of seven scheduled milestone releases for 11.3 was completed and released on schedule. Milestone 4 … [View More]focuses on switching to upstart as init daemon. Here's what you may find interesting in the new release: * OpenOffice.Org has been updated to 3.2.1 Beta1 * NetworkManager was updated to version 0.8 * cups has been updated to version 1.4.2 * The conntrack - network filtering system has been added * The mono stack has been updated to version 2.6.3 * Python was updated to version 2.6.5 RC 2 * samba was updated to version 3.5.1 * The Moblin team has started with the integration of the Moblin UI into the distribution and plan to have everything ready for the next milestone Gnome/GTK desktop users: * GNOME has been updated to the GNOME 2.30 release candidate (2.39.92) KDE desktop users: * KDE has been updated to version 4.4.1. * Amarok is now at version 2.3. * k3b is updated to version 1.91. Testing! Testing! Testing! As this is a milestone release, 11.3 milestone 4 does contain bugs that we know about, but should not stand between courageous contributors and release testing. You can track the most annoying bugs on the wiki along with 11.3 development. If you want to make sure 11.3 final is free of annoying bugs, we’ll need your help finding, reporting, and fixing those hidden bugs. To learn more about testing openSUSE, visit the Testing pages on the openSUSE wiki. To follow the testing and development process, we suggest that you subscribe to the openSUSE-Factory mailing list (Subscribe | Help | Archives) and join the #openSUSE-Factory channel on Freenode to discuss openSUSE development. The next openSUSE Milestone is scheduled to be released on Thursday, March the 25th, with additional new features and bug fixes. Get Milestone 4 Today! What are you waiting for? Grab the milestone release from software.opensuse.org/developer today! -- Andreas Jaeger, Program Manager openSUSE, aj(a){novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 [View Less]

4 7

[opensuse-factory] Request to move lilypond from contrib to factory?
by Dave Plater 29 Mar '10

29 Mar '10

Hi, I asked how to go about moving lilypond to factory on the packaging list and it was suggested that I ask on this list as well as a submit request. I've made submit request id 35916 already and here are my reasons :- I maintain contrib lilypond and multimedia:apps rosegarden4,rosegarden4 should "Require: lilypond" but because lilypond resides in contrib I can only recommend it in rosegarden because a new user might not have the contrib repo enabled. Lilypond used to be part of the main … [View More]

4 4

[opensuse-factory] Kernel Mode Setting (KMS) for openSUSE.
by Egbert Eich 29 Mar '10

29 Mar '10

Folks - In yesterday's discussion about the future of SaX2 it has been requested that changes that will affect users in the future are communicated to the openSUSE community early. KMS (kernel mode setting) integration would be such a feature, thus I would like to announce this here and one step further dive into a technical discussion about a possible solution. Furthermore test packages are available to try things out on Factory. I would like to encourage people interested in development and … [View More]technical discussions in general to participate in the discussion and the development efforts. Kernel Modesetting (KMS) ======================== All of you who are using a graphical desktop on Linux have been using the X Window Sytem. The X Window System Server (XServer) is the instance which receives requests from your desktop applications to draw all the widgets (windows, buttons, images etc.) you see on your desktop. It also processes input from your keyboard and mouse and sends them to applications as events. Traditionally on Linux the XServer does not only draw images to the screen (ie writes them to some sort of frame buffer) but it is in charge of initializing, setting up and driving the graphics hardware. This paradigm which has been true since the X Window System has been ported to Linux is about to change: Much of the initialization, set up (video mode setting) and control of the graphics hardware is about to move to the Linux kernel. There are a number of advantages to this: - A central instance is in charge of the graphics hardware, other user mode applications (not just the Xserver) can take advantage of mode setting. - The Xserver will no longer require full root privileges as it doesn't talk to the hardware directly any more. - Faster boot process: The Xserver doesn't need to (re)initialize the graphics hardware any more, this is all done by the kernel very early in the boot cycle. - Smoother (flicker free) boot experience: The screen doesn't flicker and changes resolution any more when the Xserver starts. - One central entity is in charge and manages the resources of the graphics hardware - like the video memory which makes sharing of these resources between several applications (like Xserver and several DRI (Direct Rendering 3D) applications much easier. KMS is integrated in the DRM drivers. In the near future most graphics driver will switch to KMS: - Intel already ships a fully working KMS driver. Future Intel chipsets will be supported by the KMS driver only. - KMS in the Radeon DRM driver is still work in progress but it is already working well on some chipsets. - Noveau is relying heavily on KMS for their free 3D driver for NVIDIA chipsets. The proprietary ATI and NVIDIA drivers are unlikely to switch to KMS in the near future. Integration in openSUSE ======================= Now this begs the question what we have to do to integrate it into openSUSE. Originall I had plans to look into this for openSUSE 11.2 already - but then I got side tracked by other stuff it fell on the floor and noone else beat me to it either ... oh well. Now I had the chance to play around with KMS a little and came up with some ideas and a proof of concept. It turned out that the changes to openSUSE needed to fully support KMS are quite small. Key is to load the KMS aware DRM driver as early as possible in the boot process to avoid video mode changes later in the boot cycle - preferrably in the initrd. The Boot Process ---------------- On openSUSE the boot loader is configured for two boot scenarios: default and failsafe. The user can select the failsafe boot scenario in case the default scenario does not work for him. In the failsafe scenario certain features are deactivated which have shown to cause problems on some systems. Since KMS is a new feature it is a candidate for deactivation during a failsafe boot. Instead the system should then boot into the VESA framebuffer mode. Should this also fail the kernel will automatically fall back to a VGA text mode. To disable KMS on boot a new boot parameter is introduced: 'nomodeset'. This parameter is to the boot command line for the failsafe mode. The user may add this parameter by hand for any other boot mode. The kernel command line is parsed in initrd and an appropriate entry is created in /etc/modprobe.d/options. Furthermore the graphics driver module and - if required - the agp module(s) are added in the correct order (agp modules first) to the list of modules to be loaded initially. Changes to individual packages ============================== 1. yast2-bootloader & perl-Bootloader ------------------------------------- The boot parameter 'nomodeset' is added to the failsafe boot paramter lists in each of the modules. (I have not been able to find out which module provides the entry relevant for which situation, therefore I've whacked both.) yast2-bootloader updates the variable FAILSAFE_APPEND in /etc/sysconfig/bootloader appropriately. 2. kernel-source ---------------- To use KMS for a certain DRM driver the kernel config option CONFIG_DRM_<driver_name>_KMS needs to be set to 'y'. At the moment we will support KMS only for Intel hardware, thus only the variable CONFIG_DRM_I915_KMS needs to be changed. In the sample build this has been enabled for the -default, -desktop, -pae, -debug, -trace and -vanilla kernels for the i386 and x86_64 platforms. The kernel boot splash has already been fixed for KMS for openSUSE 11.2. 3. mkinitrd ----------- This package writes the initrd file. To add KMS support to the initrd mkinitrd needs to perform the following tasks: 1. Check the sysconfig variable NO_KMS_IN_INITRD, if set, don't attempt to install a KMS DRM capable driver. 2. Obtain a list of PCI devices installed on the system. 3. a. In the list of PCI devices identify those devices which are of class VGA and look for a matching driver. b. Before a driver is matched check the PCI vendor, device, subvendor and subdevice ids against a blacklist in /etc/kms/blacklist should this file exist. This file contains one vendor, device, subvendor and subdevice id per line, '*' serves as a wildchar, trailing wildchars may be ommitted, '#' at the beginning of a line serves as a comment. c. Use the standard modprobe alias mechanism to find a matching DRM driver module. This way standard blacklistings of kernel modules will be honored and update modules will be searched if they are available. KMS capable DRM drivers provide an alias list (in contrast to non-KMS capable DRM drivers which are to be loaded explicitely by the Xserver). d. If a driver is found check for a black listing in /etc/kms/<driver_name>.blacklist. The same rules as in 3 b. apply. 4. If a KMS capable DRM driver is found search for an agp driver: a. Obtain a list of all known agp drivers for the specific kernel and collect their alias lists. b. Match all installed PCI devices against the alias lists of each agp driver. If a match is found add the driver to the lists of modules to be loaded. Make sure that this driver is loaded prior the the DRM driver. Two scripts setup-kms.sh and boot-kms.sh are added to mkinitrd. The former performs the tasks listed above, the latter provides the required module dependencies in the required order, parses the boot command line for the 'nomodeset' option and adds the apropriate entry to /etc/modprobe.d/options. The linuxrc script is extended to search the boot command line for <drivername>.<option>=* strings for each driver loaded in initrd and add the <option>=* part to /etc/modprobe.d/options. 4. udev ------- Udev loads any modules which are not loaded by linuxrc scripts directly. It is possible to let udev load the required DRM and AGP modules provided it is made sure that this happens in the correct order. Since there is no explicit dependency of DRM modules to AGP drivers as there is no general one to one match between the two drivers a udev rule must exist to enforce the correct order for all cases where a AGP module is required. This is true for Intel DRM drivers and any other driver for an AGP graphics chip. For this a rule file 79-waitfor-agp.rules is added which is run before 80-drivers.rules. It checks if either an Intel graphics (class VGA) device is processed or if the graphics device is an AGP device. The latter condition is tested by an auxiliary tool (is_agp) which is passed the kernel name of the event device. If either condition is true udev will wait for /dev/agpgart to appear before proceeding to load a DRM driver module. 'is_agp' checks the capabilities flags in the PCI config space of this device for AGP. The changes to udev are not strictly required to make KMS work, still they augment the default module load process Installation ============ Modified packages for Factory of - kernel-source, - mkinitrd, - yast2-bootloader, - perl-Bootloader, - mkinitrd - udev can be found in my build service home on OBS under home:eeich:Factory-KMS. For installation add http://download.opensuse.org/repositories/home://eeich://Factory-KMS/openSU… to your installation repository and update the packages in question (going thru the usual vendor change hassle). It is advisable to update mkinitrd before updating the kernel. Then when the kernel is installed the modified mkinitrd will be used and all steps required to install KMS will be performed. TODO ==== - The kernel bootsplash sometimes produces wrong colors (WIP). Add KMS - Add KMS support to the RadeonHD driver. Cheers, Egbert. -- Egbert Eich (Res. & Dev.) SUSE LINUX Products GmbH X Window System Development Tel: +49 911-740 53 0 http://www.suse.de ----------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org [View Less]

18 68

[opensuse-factory] Moving lilypond to multimedia:apps with the intention to submit it to factory.
by Dave Plater 29 Mar '10

29 Mar '10

Hi, I'm planning to move lilypond from openSUSE:Factory:Contrib to multimedia:apps and to submit it to factory, to enable multimedia:apps and factory rosegarden4 to require it. I'm making this announcement because I've maintainer rights in multimedia:apps and don't want to unwittingly abuse my privilege. I will wait until Wednesday before doing this and when it's accepted into factory will disable the factory build in contrib and delete the binaries leaving only 11.2 and 11.1 available. Any … [View More]

1 0

[opensuse-factory] openSUSE 11.3 Support for Intel Core i3 / i7
by Andi Sugandi 28 Mar '10

28 Mar '10

Hi Listmates, I tried installing openSUSE (oS) 11.2 and 11.3 M3 on Dell Inspiron 1440 and Acer Aspire 4740, and the results seem similar: 1. oS 11.2: Live KDE: It failed to boot. Installation: Succeeded to run YaST-Installer, but after reboot it failed to finish the installation processes. 2. 11.3 M3: Live CD KDE4: It booted well. but hang when it was in progress on YaST Installer (when formatting new partitions) Installation: I can see it booted well but no GUI ran, only blank screen, I … [View More]

3 3

Main

Development

Information

Community

Social Media

Other

openSUSE Factory