Re: [Mageia-dev] Perl MIDI:ALSA module (package suggestion for Mageia)
On Sun, 9 Dec 2012, Remy CLOUARD wrote: > On Sat, Dec 08, 2012 at 02:43:47PM +0100, tux99-...@uridium.org wrote: > > Hi, > > If you are curious to see what can be done with the MIDI::ALSA Perl > > module have a look at a program I wrote with it: > > http://www.yamahaforums.co.uk/forum/viewtopic.php?f=9&t=5915 > > > Awesome ! > > Up until now I used to use simple sysexxer to transfer sysex to my DX7. > Editing patches on the DX7 is a major pain, because there is only one > slider to adjust each parameter for all oscillators. > Seems to me that this library will make it way easier to build apps that > do what this app does for the RM50. (maybe you have plans to support > other hardware ?) Yes, IMHO this library together with Perl/Tk (or GTK2-Perl if you prefer) for the GUI makes it very easy to write apps like this one, I have very little programming experience and I still managed to write this in a few weeks in my spare time (I did have basic Perl scripting experience but had never written such large GUI based app before). I might write similar apps for other synths I own in future but I don't own a DX7 (great synth!) so can't support that one. Regards, Andy
Re: [Mageia-dev] Perl MIDI:ALSA module (package suggestion for Mageia)
On Sat, 8 Dec 2012, Shlomi Fish wrote: > > I now packaged your perl-MIDI-ALSA for Mageia Linux 3/Cauldron after some > Mageiaisation of the .spec file. Thanks! That's great, thanks! > If you wish to return the favour you can package Freecell Solver > ( http://fc-solve.shlomifish.org/ ) for Fedora/CentOS. The .tar.bz2 already > has > a built-in .spec and .spec.in and there's also a Mageia package for it here: Unfortunately I'm not a Fedora user or packager at all, I only run a personal repo for EL6 (RHEL6/Centos6/SL6) specialised in Audio/Video packages which is quite popular among EL6 desktop users due to the fact that it has several A/V related packages no other EL6 repo has. If you like I could add Freecell-Solver to my personal EL6 repo, but I don't think that would help much, it would probably get more attention in one of the large EL6 repos like EPEL. Regards, Andy
[Mageia-dev] Perl MIDI:ALSA module (package suggestion for Mageia)
Hi, Thanks to Peter Billam there is now a Perl module that gives Perl complete access to the ALSA MIDI library therefore allowing to easily create programs in Perl that inteface with MIDI capable synthesizers. I have packaged up this Perl module for Centos 6 and I think it should be straightforward to port the Centos 6 spec-file to Mageia, but since I'm not a Mageia packager (and can't be due to lack of time) I wanted to bring this to your attention with the hope that a Mageia packager picks this up and adds this very useful package to Mageia. Here are the Centos 6 files: Spec-file: http://pkgrepo.linuxtech.net/el6/testing/spec-files/perl-MIDI-ALSA.spec Source RPM: http://pkgrepo.linuxtech.net/el6/testing/source/perl-MIDI-ALSA-1.16-1.el6.src.rpm Binary RPMS: http://pkgrepo.linuxtech.net/el6/testing/i686/perl-MIDI-ALSA-1.16-1.el6.i686.rpm http://pkgrepo.linuxtech.net/el6/testing/x86_64/perl-MIDI-ALSA-1.16-1.el6.x86_64.rpm If you are curious to see what can be done with the MIDI::ALSA Perl module have a look at a program I wrote with it: http://www.yamahaforums.co.uk/forum/viewtopic.php?f=9&t=5915 Regards, Andy
Re: [Mageia-dev] Mageia support for GMA 3600 (Cedar Trail Atom)
On Sun, 11 Mar 2012 tux99-...@uridium.org wrote: > > On Fri, 9 Mar 2012 tux99-...@uridium.org wrote: > > > On Fri, 9 Mar 2012, Thomas Backlund wrote: > > > > > tux99-...@uridium.org skrev 8.3.2012 02:18: > > > > > > > > Hi, > > > > I just tried Mageia 2 beta 1 on a Intel DN2800MT board hoping that it > > > > would have framebuffer support for the GMA 3600, but the attached > > > > monitor goes into standby (no signal) as soon as the frame buffer gets > > > > activated during boot. > > > > > > > > As far as I understand there is frame buffer support in the 3.3 kernel > > > > for the GMA 3600 so in theory it should work. > > > > > > > > Are you aware of this issue or should I do a bug report? > > > > > > Yes. > > > > > > There is a bug with Cedar Trail that got fixed upstream a few days after > > > 3.3-rc6 was released, so the fix is not in our current > > > kernel-3.3.0-0.rc6.1.mga2, but it will be fixed in the next build. > > > > Thanks, that's great, I will test the next build and then report back > > how that works with my Cedar Trail board. > > Hi, I noticed a new kernel packages showed up in the cauldron repo > (3.3rc7) so I tried it immediately (reinstalled cauldron from scratch as > I had overwritten the previous install with other distro tests) using > the boot.iso image, but the video behaviour at boot is still the same, > the monitor still goes into no-signal standby as soon as the drm stuff > is started. Just for future reference for anyone who might come across this thread in the ML archives facing the same issue: I solved this, the GMA 3600 kernel DRM driver in 3.3.0 (as included in Mageia) always assumes a LVDS panel is present (as would be the case on netbooks but not on mini-ITX boards) and for some reason it defaults to a 1920x1080 panel. To avoid this and therefore to be able to use the other video outputs (VGA, hdmi) at other resolutions the following kernel parameter needs to be appended on the grub kernel line: video=LVDS-1:d This will force disable the LVDS port and with that parameter Mageia 2 works fine on a Cedarview Atom DN2800MT board. This is a shortcoming of the kernel module (not specific to Mageia), Alan Cox is aware of it and I guess it will eventually be fixed. For anyone interested the xorg.conf I used is here (the monitor section is specific to my monitor, hence will need adapting): http://pastebin.com/X7mpEF3x Also for anyone interested I have done some power draw measurements of the Intel DN2800MT Cedarview Atom board comparing Mageia 2 beta with some other distros (and Win 7), the results are here: http://www.linuxtech.net/reviews/intel_DN2800MT_cedarview_atom_power_draw.html
Re: [Mageia-dev] Mageia 2 Beta 2 is available
On Fri, 16 Mar 2012, Sander Lepik wrote: > 16.03.2012 03:07, tux99-...@uridium.org kirjutas: > > On Thu, 15 Mar 2012, Anne nicolas wrote: > > > >> Hi there > >> > >> Beta 2 is available now for tests. Here is the announcement: > >> http://blog.mageia.org/en/2012/03/15/mageia-2-beta-2-near-the-goal/ > >> > >> We need your tests and reports more than ever! > > Hi Anne, I gave feedback with regards to serious issues when trying > > beta 1 on a Cedarview Atom system, but apart from a couple of > > isolated replies (thanks to those who did reply) that unfortunately > > didn't solve the issues I got no further interest. > And the bug number is? Does your post mean you looked at the info I provided in the previous emails and you concluded that I'm hitting a bug? As I said before I don't know if I'm hitting a bug or if it's a configuration issue, that's what I was trying to find out here. My main problem is I don't really understand how the GMA3600 needs to be configured, I don't know what this DRM kernel driver that's included in 3.3.7rc7 is, is it equivalent to a framebuffer driver, or do I still have to use the generic vesa framebuffer? Regardless of that, out of the box I'm not getting any picture with this GPU (the screen goes into stand-by once the DRM kernel module is activated at boot). I did manage to manually configure xorg to use the generic vesa framebuffer but this way I don't seem to get any DRI capability which I thought the GMA3600 DRM kernel module was supposed to provide. There don't seem to be any docs anywhere with regards to this, neither in the kernel docs nor on the internet, at least I didn't find anything. As it stands Mageia is unusable on a Cedarview Atom for a normal user, and even I'm quite at loss here as I only managed to get generic vesa xorg working (after a lot of trial and error). At least with other distros (Centos 6.2 or Fedora 17 alpha) xorg with the generic vesa driver works out of the box (but those distros don't have the latest kernel with the GMA3600 DRM kernel module).
Re: [Mageia-dev] Mageia 2 Beta 2 is available
On Thu, 15 Mar 2012, Anne nicolas wrote: > Hi there > > Beta 2 is available now for tests. Here is the announcement: > http://blog.mageia.org/en/2012/03/15/mageia-2-beta-2-near-the-goal/ > > We need your tests and reports more than ever! Hi Anne, I gave feedback with regards to serious issues when trying beta 1 on a Cedarview Atom system, but apart from a couple of isolated replies (thanks to those who did reply) that unfortunately didn't solve the issues I got no further interest. Given that Cedarview Atom will be on most Netbooks this year I would have expected more interest in getting Mageia to work on them. Therefore I say it again, I'm available to do any reasonable tests you want me to do or provide any logs you need to get this solved (see my previous mails for details I already provided so far). Regards, tux99
Re: [Mageia-dev] Mageia support for GMA 3600 (Cedar Trail Atom)
On Mon, 12 Mar 2012, zezinho wrote: > Le lundi 12 mars 2012 00:38:00, tux99-...@uridium.org a �crit : > > Sorry ignore the previous pastebins, those were without "vga=795" on the > > kernel line, here are the correct ones: > > > > Please, maybe this could go only into the bug report? There is no bug report because I don't even know if this is a bug or a simple configuration issue, that's what I'm trying to find out.
Re: [Mageia-dev] Mageia support for GMA 3600 (Cedar Trail Atom)
On Sun, 11 Mar 2012 tux99-...@uridium.org wrote: > On Fri, 9 Mar 2012 tux99-...@uridium.org wrote: > > > On Fri, 9 Mar 2012, Thomas Backlund wrote: > > > > > tux99-...@uridium.org skrev 8.3.2012 02:18: > > > > > > > > Hi, > > > > I just tried Mageia 2 beta 1 on a Intel DN2800MT board hoping that it > > > > would have framebuffer support for the GMA 3600, but the attached > > > > monitor goes into standby (no signal) as soon as the frame buffer gets > > > > activated during boot. > > > > > > > > As far as I understand there is frame buffer support in the 3.3 kernel > > > > for the GMA 3600 so in theory it should work. > > > > > > > > Are you aware of this issue or should I do a bug report? > > > > > > Yes. > > > > > > There is a bug with Cedar Trail that got fixed upstream a few days after > > > 3.3-rc6 was released, so the fix is not in our current > > > kernel-3.3.0-0.rc6.1.mga2, but it will be fixed in the next build. > > > > Thanks, that's great, I will test the next build and then report back > > how that works with my Cedar Trail board. > > Hi, I noticed a new kernel packages showed up in the cauldron repo > (3.3rc7) so I tried it immediately (reinstalled cauldron from scratch as > I had overwritten the previous install with other distro tests) using > the boot.iso image, but the video behaviour at boot is still the same, > the monitor still goes into no-signal standby as soon as the drm stuff > is started. > > I have full access to the box via ssh so I have uploaded some logs that > might help figure this out, it looks to like the kernel modules load > fine but somehow they set a screen mode that the monitor doesn't like. > > Basically I don't really know how the drm kernel modules and xorg > interact (and I can't find any useful recent docs about it), who is > responsible for setting the screen mode and where can I manually > configure it, on the kernel line or xorg.conf? > (I have been spoiled by the binary nvidia drivers for too long :) ) > > dmesg: > http://pastebin.com/SLBcgjXx > > lsmod output: > # lsmod|grep gma > gma500_gfx149940 0 > drm_kms_helper 32743 1 gma500_gfx > drm 207700 2 gma500_gfx,drm_kms_helper > i2c_algo_bit 13080 1 gma500_gfx > i2c_core 29836 5 > i2c_i801,gma500_gfx,drm_kms_helper,drm,i2c_algo_bit > video 18640 1 gma500_gfx > > /var/log/Xorg.0.log: > http://pastebin.com/ypw0DAnz > > I'm unsure if this is only a config problem or if this is still due > to some bug. > > Any pointers would be much appreciated. Sorry ignore the previous pastebins, those were without "vga=795" on the kernel line, here are the correct ones: dmesg: http://pastebin.com/4t9L3GVm Xorg.0.log: http://pastebin.com/TsE4gUxW
Re: [Mageia-dev] Mageia support for GMA 3600 (Cedar Trail Atom)
On Fri, 9 Mar 2012 tux99-...@uridium.org wrote: > On Fri, 9 Mar 2012, Thomas Backlund wrote: > > > tux99-...@uridium.org skrev 8.3.2012 02:18: > > > > > > Hi, > > > I just tried Mageia 2 beta 1 on a Intel DN2800MT board hoping that it > > > would have framebuffer support for the GMA 3600, but the attached > > > monitor goes into standby (no signal) as soon as the frame buffer gets > > > activated during boot. > > > > > > As far as I understand there is frame buffer support in the 3.3 kernel > > > for the GMA 3600 so in theory it should work. > > > > > > Are you aware of this issue or should I do a bug report? > > > > Yes. > > > > There is a bug with Cedar Trail that got fixed upstream a few days after > > 3.3-rc6 was released, so the fix is not in our current > > kernel-3.3.0-0.rc6.1.mga2, but it will be fixed in the next build. > > Thanks, that's great, I will test the next build and then report back > how that works with my Cedar Trail board. Hi, I noticed a new kernel packages showed up in the cauldron repo (3.3rc7) so I tried it immediately (reinstalled cauldron from scratch as I had overwritten the previous install with other distro tests) using the boot.iso image, but the video behaviour at boot is still the same, the monitor still goes into no-signal standby as soon as the drm stuff is started. I have full access to the box via ssh so I have uploaded some logs that might help figure this out, it looks to like the kernel modules load fine but somehow they set a screen mode that the monitor doesn't like. Basically I don't really know how the drm kernel modules and xorg interact (and I can't find any useful recent docs about it), who is responsible for setting the screen mode and where can I manually configure it, on the kernel line or xorg.conf? (I have been spoiled by the binary nvidia drivers for too long :) ) dmesg: http://pastebin.com/SLBcgjXx lsmod output: # lsmod|grep gma gma500_gfx149940 0 drm_kms_helper 32743 1 gma500_gfx drm 207700 2 gma500_gfx,drm_kms_helper i2c_algo_bit 13080 1 gma500_gfx i2c_core 29836 5 i2c_i801,gma500_gfx,drm_kms_helper,drm,i2c_algo_bit video 18640 1 gma500_gfx /var/log/Xorg.0.log: http://pastebin.com/ypw0DAnz I'm unsure if this is only a config problem or if this is still due to some bug. Any pointers would be much appreciated.
Re: [Mageia-dev] Mageia support for GMA 3600 (Cedar Trail Atom)
On Fri, 9 Mar 2012, Thomas Backlund wrote: > tux99-...@uridium.org skrev 8.3.2012 02:18: > > > > Hi, > > I just tried Mageia 2 beta 1 on a Intel DN2800MT board hoping that it > > would have framebuffer support for the GMA 3600, but the attached > > monitor goes into standby (no signal) as soon as the frame buffer gets > > activated during boot. > > > > As far as I understand there is frame buffer support in the 3.3 kernel > > for the GMA 3600 so in theory it should work. > > > > Are you aware of this issue or should I do a bug report? > > > > Yes. > > There is a bug with Cedar Trail that got fixed upstream a few days after > 3.3-rc6 was released, so the fix is not in our current > kernel-3.3.0-0.rc6.1.mga2, but it will be fixed in the next build. Thanks, that's great, I will test the next build and then report back how that works with my Cedar Trail board.
Re: [Mageia-dev] Mageia support for GMA 3600 (Cedar Trail Atom)
On Thu, 8 Mar 2012, Colin Guthrie wrote: > 'Twas brillig, and tux99-...@uridium.org at 08/03/12 02:00 did gyre and > gimble: > > On Thu, 8 Mar 2012 tux99-...@uridium.org wrote: > > > >> > >> Hi, > >> I just tried Mageia 2 beta 1 on a Intel DN2800MT board hoping that it > >> would have framebuffer support for the GMA 3600, but the attached > >> monitor goes into standby (no signal) as soon as the frame buffer gets > >> activated during boot. > >> > >> As far as I understand there is frame buffer support in the 3.3 kernel > >> for the GMA 3600 so in theory it should work. > >> > >> Are you aware of this issue or should I do a bug report? > >> > >> Has anyone else tested a GMA 3600 (the GPU that's in all Cedar Trail > >> Atom cpus) with Mageia so far? > >> > >> Regards, > >> tux99 > > > > Just to add: I have tried all grub opptions (normal, non-fb and > > failsafe) on each of them the same thing happens. with non-fb I can see > > the boot process until almost the end, I guess it's the start of the dm > > that triggers the loss of signal in that case. > > > > I tried editing the grub line adding a "3" at end hopeing to get it to > > boot to runlevel 3 but that doesn't seem to work as the behaviour > > doesn't change. Is "3" on the grub line still supposed to work? > > > > I imagine this GMA3600 issue needs solving before the final release as > > CedarTrail Atoms will be in most Netbooks sold this year, and even > > though netbooks are less popular then they used to be, they are still > > selling by the milions especially in Asia. > > > > Let me know what I could do to help debug this. > > This depends on your upgrade path of your Mageia install. Is it a fresh > install? Yes, fresh install using the Mageia 2 beta 1 netinstall ISO, I selected the LXDE desktop to keep the install size small. > Switch to tty2 after booting to runlevel 3. It should let you log in. Well if I press Ctrl-Alt-F2 after waiting 10-15 seconds after the screen goes into standby during boot, I still don't get the a video signal back. I can then press Ctrl-Alt-Del and the system will shut down cleanly so it's not frozen, it's only the video output that doesn't work with Mageia.
Re: [Mageia-dev] Mageia support for GMA 3600 (Cedar Trail Atom)
On Wed, 7 Mar 2012, David W. Hodgins wrote: > On Wed, 07 Mar 2012 21:00:38 -0500, wrote: > > > On Thu, 8 Mar 2012 tux99-...@uridium.org wrote: > > > >> > >> Hi, > >> I just tried Mageia 2 beta 1 on a Intel DN2800MT board hoping that it > >> would have framebuffer support for the GMA 3600, but the attached > >> monitor goes into standby (no signal) as soon as the frame buffer gets > >> activated during boot. > > Try disabling kms by adding either nokmsboot or modeset.i915=0 to > the kernel options. > > Regards, Dave Hodgins > Thanks but neither nokmsboot nor i915.modeset=0 make much of a difference. With nokmsboot I get the mageia splash screen for a second or too (I wasn't seeing that before), but after that the monitor still goes into standby. i915.modeset=0 has no effect. The following Meego ISO works fine with this mobo (both kms and xorg): http://repo.meego.com/MeeGo/updates/1.2.0/images/meego-netbook-ia32-cedartrail/ Also Centos 6.2 boots fine to runlevel 3 without disabling anything (probably because the Centos 6.2 kernel doesn't have any support for the GMA3600).
Re: [Mageia-dev] Mageia support for GMA 3600 (Cedar Trail Atom)
On Thu, 8 Mar 2012 tux99-...@uridium.org wrote: > > Hi, > I just tried Mageia 2 beta 1 on a Intel DN2800MT board hoping that it > would have framebuffer support for the GMA 3600, but the attached > monitor goes into standby (no signal) as soon as the frame buffer gets > activated during boot. > > As far as I understand there is frame buffer support in the 3.3 kernel > for the GMA 3600 so in theory it should work. > > Are you aware of this issue or should I do a bug report? > > Has anyone else tested a GMA 3600 (the GPU that's in all Cedar Trail > Atom cpus) with Mageia so far? > > Regards, > tux99 Just to add: I have tried all grub opptions (normal, non-fb and failsafe) on each of them the same thing happens. with non-fb I can see the boot process until almost the end, I guess it's the start of the dm that triggers the loss of signal in that case. I tried editing the grub line adding a "3" at end hopeing to get it to boot to runlevel 3 but that doesn't seem to work as the behaviour doesn't change. Is "3" on the grub line still supposed to work? I imagine this GMA3600 issue needs solving before the final release as CedarTrail Atoms will be in most Netbooks sold this year, and even though netbooks are less popular then they used to be, they are still selling by the milions especially in Asia. Let me know what I could do to help debug this.
[Mageia-dev] Mageia support for GMA 3600 (Cedar Trail Atom)
Hi, I just tried Mageia 2 beta 1 on a Intel DN2800MT board hoping that it would have framebuffer support for the GMA 3600, but the attached monitor goes into standby (no signal) as soon as the frame buffer gets activated during boot. As far as I understand there is frame buffer support in the 3.3 kernel for the GMA 3600 so in theory it should work. Are you aware of this issue or should I do a bug report? Has anyone else tested a GMA 3600 (the GPU that's in all Cedar Trail Atom cpus) with Mageia so far? Regards, tux99
