Re: [Mageia-dev] freeze push: drakxtools drakx-installer-stage2
Le 22/03/2013 00:15, Thierry Vignaud a écrit : Hi Please let in drakxtools drakx-installer-stage2 drakxtools: - bootloader-config: o do not build initrd if no bootloader is detected and --no-initd argument is supplied - diskdrake: o actually preserve UUID when formatting (mga#9428) - drakauth: o install nss-pam-ldapd instead of nss_ldap (mga#9375) drakx-installer-stage2 - do not disable module autoloading (mga#9428) - authentication: o install nss-pam-ldapd instead of nss_ldap (mga#9375) - partitionning: o actually preserve UUID when formatting (mga#9428) thx done... please submiter mail when it's done. I just modified the sources thinking it was nnot done yet... reverting -- Anne http://mageia.org
Re: [Mageia-dev] freeze push: rpmdrake urpmi
Le 21/03/2013 23:56, Thierry Vignaud a écrit : Hi Please let in rpmdrake urpmi urpmi: - library: o account for packages to erase in gurpm progress bar o enable to have a cancel button in global progress bar dialog - gurpmi2: o enable to cancel downloads o fix setting download callback rpmdrake: - adapt to gurpmi enabling to cancel again downloads - death to obsolete curl_download module - fix erase progress in global bar thx done -- Anne http://mageia.org
Re: [Mageia-dev] freeze push: drakx-installer-binaries
2013/3/22 Thierry Vignaud thierry.vign...@gmail.com Hi Please let in drakx-installer-binaries it revert the breakage that prevent loading some modules (such as usb), thus dead stage1 When it's available, please rebuild drakx-installer-images with it (both in core/release nonfree/release) thx done -- Anne http://www.mageia.org
Re: [Mageia-dev] Freeze push: qgis-1.8.0
2013/3/22 FundaWang fundaw...@fundawang.name Hello, Could somebody push qgis 1.8.0 into cauldron? It should be uploaded in the period of alpha testing with other gis software. Currently we have qgis 1.7.4 which cannot be built against current toolchain. Regards. done -- Anne http://www.mageia.org
[Mageia-dev] Freeze push: owncloud
Hi, please push owncloud, this is a new version but this is a must have ( and fixes sec issues too ).
[Mageia-dev] HEADSUP: Full git clone of all package specs (with history)
Hi, Just to avoid a crazy amount of scripting with svn checkouts and such like, I've set running a git svn clone of the cauldron package subversion tree. It'll take a while to complete (likely about 24hrs in total by current estimates) and it should take up about 800MB (rough estimate) in total. When complete it will act as a handy source for doing full repository greps and such like. It will also be useful for making mass changes (git svn rebase and git svn dcommit are you friends). I'll endevour to make it available via a public clone when done, but due to it's size and nature it'll likely only appeal to a few people. Just thought I'd let you know. FWIW, I'll use this to add the necessary stuff to fix https://bugs.mageia.org/show_bug.cgi?id=9302 which requires finding several packages that use a specific macro and updating them. FAO: sysadm team. I'm using valstar for this as it's much closer network wise. Of course I stupidly still used svn+ssh rather than a direct file, thinking it would be more useful generally when moving it later, forgetting that I could probably just have editted the subversion URL after the clone was complete... but meh, it's done now and and it's almost half way through so no point in killing it half way through IMO. Col -- Colin Guthrie colin(at)mageia.org http://colin.guthr.ie/ Day Job: Tribalogic Limited http://www.tribalogic.net/ Open Source: Mageia Contributor http://www.mageia.org/ PulseAudio Hacker http://www.pulseaudio.org/ Trac Hacker http://trac.edgewall.org/
[Mageia-dev] drakxtools drakx-installer-stage2 (mga#9428)
Hi, I've been trying to test the installer change below before RC4, thinking that it might be quite helpful. I am having a little bit of trouble however. Could someone point me in the right direction on a couple of things. 1. How does the src tar.xz file for drakx-installer-stage2 get created? I assume it comes from a build of svn://svn.mageia.org/svn/soft/drakx/trunk, but can't find how it ends up as a tar.xz 2. When I've built a new stage2, any tricks on getting it into an ISO? I tried building an ISO based on beta3, with the new stage2, using something like: mkisofs -o ~nelg/Mageia-3-beta3-x86_64-DVD/Mageia-3-beta3-x86_64-DVD-stage2.iso -b x86_64/isolinux/isolinux.bin -c boot.catalog -no-emul-boot -boot-load-size 4 -iso-level 4 -J -R /tmp/tt/ This is clearly not right. Is the a documented method I should use to build a new ISO with a modified stage2? In the docs I have read: https://wiki.mageia.org/en/Drakx-installer_tips_and_tricks#rebuild_the_stage_2 and svn://svn.mageia.org/svn/soft/drakx/trunk/docs/README, I have not been able to find instructions on actually putting together an ISO. Is: http://wiki.mandriva.com/en/How_to_remaster_a_personal_Mandriva-based_ISO relevant for Mageia? I guess not, as mkcd does not seem to exist in Mageia. So, a quick howto, or pointing me to the right documentation would be great :) Regards Glen Ogilvie On 22 March 2013 12:15, Thierry Vignaud thierry.vign...@gmail.com wrote: Hi Please let in drakxtools drakx-installer-stage2 drakxtools: - bootloader-config: o do not build initrd if no bootloader is detected and --no-initd argument is supplied - diskdrake: o actually preserve UUID when formatting (mga#9428) - drakauth: o install nss-pam-ldapd instead of nss_ldap (mga#9375) drakx-installer-stage2 - do not disable module autoloading (mga#9428) - authentication: o install nss-pam-ldapd instead of nss_ldap (mga#9375) - partitionning: o actually preserve UUID when formatting (mga#9428) thx
Re: [Mageia-dev] drakxtools drakx-installer-stage2 (mga#9428)
On 03/22/2013 07:20 AM, Glen Ogilvie wrote: Hi, I've been trying to test the installer change below before RC4, thinking that it might be quite helpful. I am having a little bit of trouble however. Could someone point me in the right direction on a couple of things. 1. How does the src tar.xz file for drakx-installer-stage2 get created? I assume it comes from a build of svn://svn.mageia.org/svn/soft/drakx/trunk http://svn.mageia.org/svn/soft/drakx/trunk, but can't find how it ends up as a tar.xz I'm maybe about two days ahead of you on this, but here's what I think happens, FWIW. You do your checkout, and then in the mdk-stage1 subdirectory, do a make dist-svn. This should produce the tar.xz in the mdk-stage1 directory. 2. When I've built a new stage2, any tricks on getting it into an ISO? The tar.xz you built above becomes one of the SOURCES for the drakx-installer-binaries package. If you bring that package down to your rpm/SRPMS directory and do an rpm -ivh on it, you'll find a tar.xz file for mdk-stage1 in rpm/SOURCES. You can either replace this with the one you generated above, or I think there is a --(keyword) that will tell rpm to look somewhere else (your svn directory) for SOURCES. Then rebuild drakx-installer-binaries with the new tar.xz. Finally, download the SRPM for drakx-installer-images, and build *it* using the new drakx-installer-binaries. The final binary rpm will include all of the stuff (like boot.iso) that goes in the install directories of the cauldron tree.
Re: [Mageia-dev] drakxtools drakx-installer-stage2 (mga#9428)
'Twas brillig, and Glen Ogilvie at 22/03/13 11:20 did gyre and gimble: 2. When I've built a new stage2, any tricks on getting it into an ISO? I tend to have a urpmi-proxy setup and configure it to not check for updated stage2 (which is the default IIRC). I then just build the stage2 image and copy it to the urpmi-proxy. Then with a simply boot.iso, I point the http install to my server with urpmi-proxy installed and it download *my* stage2. That's how I generally test my modifications and seems quicker than building ISOs etc. Col -- Colin Guthrie colin(at)mageia.org http://colin.guthr.ie/ Day Job: Tribalogic Limited http://www.tribalogic.net/ Open Source: Mageia Contributor http://www.mageia.org/ PulseAudio Hacker http://www.pulseaudio.org/ Trac Hacker http://trac.edgewall.org/
Re: [Mageia-dev] Mageia3-B2 will no longer boot
On Wed, 20 Mar 2013 23:23:06 +, Colin Guthrie wrote: Have you tried switching to ctl+alt+f2 to see if you get a text login? Yesterday I started a boot of MGA-cauldron to try that - and it successfully booted! So did a 470+-s/w update, after which it successfully booted again. Today, however, it only properly booted twice out of a dozen attempts. Sadly, on one of the occasions I again tried to get the netbook's display onto an external monitor (which had been reporting 'Out of range' when connected VGA-VGA) by changing the X server to use 800x600 (which is supported by the external Viewsonic). Unfortunately that not only did not solve the problem but on the netbook screen the display is now squashed into the bottom left-hand corner of the screen, and although I can get into MCC/Hardware to change the resolution back to 'Auto', it does not revert to the native 1024x600. So my Mageia-3B2 is unusable, though it has served its purpose*. (N.B. Nevertheless, Mageia3 did much better than Ubuntu 12.04 and Mint 13, both of which insisted on running the netbook at 800x600) (* It has shown that the MGA3 Broadcom WiFi does work (although as I posted on January 30th (Beta32 and Broadcomm WiFi) I had far better success connecting to the hotel's WiFi with Mageia-2 than I did with MGA3-Beta2, which would seldom connect). -- /\/\aurice
Re: [Mageia-dev] drakxtools drakx-installer-stage2 (mga#9428)
Op vrijdag 22 maart 2013 07:38:56 schreef Frank Griffin: On 03/22/2013 07:20 AM, Glen Ogilvie wrote: [...] 1. How does the src tar.xz file for drakx-installer-stage2 get created? I assume it comes from a build of svn://svn.mageia.org/svn/soft/drakx/trunk http://svn.mageia.org/svn/soft/drakx/trunk, but can't find how it ends up as a tar.xz I'm maybe about two days ahead of you on this, but here's what I think happens, FWIW. You do your checkout, and then in the mdk-stage1 subdirectory, do a make dist-svn. This should produce the tar.xz in the mdk-stage1 directory. [...] make dist actually... it will target make dist-svn or make dist-git depending on if you're using git-svn or not. be advised that dist-svn uses the BASE and any uncommitted change will not be applied. dist-git however, you can commit without pushing them and that will be used.
[Mageia-dev] Freeze push: wine
Please push wine 1.5.26 as it's a new bug fix release of the 1.5.x series. Thanks. -- Damien Lallement twitter: damsweb - IRC: damsweb/coincoin
[Mageia-dev] Freeze push: inxi
Please push inxi 1.8.45 (1.8.24 for now). It adds a lot of new informations about HW and also fixes bugs and update man page. As it's a package used by QA, I think it's a good think to have it up to date on 3. Package tested on my side. Thanks! -- Damien Lallement twitter: damsweb - IRC: damsweb/coincoin
Re: [Mageia-dev] drakxtools drakx-installer-stage2 (mga#9428)
On 22 March 2013 12:20, Glen Ogilvie n...@linuxsolutions.co.nz wrote: I've been trying to test the installer change below before RC4, thinking that it might be quite helpful. I am having a little bit of trouble however. Could someone point me in the right direction on a couple of things. 1. How does the src tar.xz file for drakx-installer-stage2 get created? I assume it comes from a build of svn://svn.mageia.org/svn/soft/drakx/trunk, but can't find how it ends up as a tar.xz 2. When I've built a new stage2, any tricks on getting it into an ISO? I tried building an ISO based on beta3, with the new stage2, using something like: mkisofs -o ~nelg/Mageia-3-beta3-x86_64-DVD/Mageia-3-beta3-x86_64-DVD-stage2.iso -b x86_64/isolinux/isolinux.bin -c boot.catalog -no-emul-boot -boot-load-size 4 -iso-level 4 -J -R /tmp/tt/ This is clearly not right. Is the a documented method I should use to build a new ISO with a modified stage2? In the docs I have read: https://wiki.mageia.org/en/Drakx-installer_tips_and_tricks#rebuild_the_stage_2 and svn://svn.mageia.org/svn/soft/drakx/trunk/docs/README, I have not been able to find instructions on actually putting together an ISO. Is: http://wiki.mandriva.com/en/How_to_remaster_a_personal_Mandriva-based_ISO relevant for Mageia? I guess not, as mkcd does not seem to exist in Mageia. So, a quick howto, or pointing me to the right documentation would be great :) stage2 != ISO ISO is basically the stage1. stage1 is build by drakx-installer-images from: - some packages listed as BR, mainly the kernel drivers firmwares - drakx-installer-binaries that provide the actual stage1 binary = generates what is copied in isolinux/alt0 in install/images/ (*.img + *.iso) stage2 is build by drakx-installer-stage2 = generates what is in install/stage2: mdkinst.sqfs (a squashfs image) there's also rescue.sqfs there that is an alternate stage2 used when using the rescue. stage1 is basically a special initrd that loads the appropriate modules according to detected hardware and to what is specified on command line (eg: the DVD tells it to directly load stage2 from the DVD image). if not instructed to do sg, it displays the text menu asking from where to install (dvd, hard disk, network: http/ftp/nfs). It's a small statically linked program + init + a dhcp client + rescue-gui for the rescue menu it then loads stage2 (install/stage2/mdkinst.sqf or rescue.sqfs) from the URL stage2 is real system, with dynamic libraries, that starts: - an X11 server (if supported and if not asked for text mode) - udev and then go the install steps (language, license, partitionning, installing, summary, updates, ...)
[Mageia-dev] freeze push: ldetect-lst
Hi Please let in ldetect-lst: - disable acceleration on SiS as it crashes (mga#7521) - pcitable: o update ids from proprietary nvidia-current 310.40 - update pci.ids usb.ids
[Mageia-dev] Freeze push warzone2100 and warzone2100-data
Please push them, as current version is not supported anymore upstream ( #9475 )
Re: [Mageia-dev] drakxtools drakx-installer-stage2 (mga#9428)
Hi Colin, On 23 March 2013 01:11, Colin Guthrie mag...@colin.guthr.ie wrote: 'Twas brillig, and Glen Ogilvie at 22/03/13 11:20 did gyre and gimble: 2. When I've built a new stage2, any tricks on getting it into an ISO? I tend to have a urpmi-proxy setup and configure it to not check for updated stage2 (which is the default IIRC). I then just build the stage2 image and copy it to the urpmi-proxy. Then with a simply boot.iso, I point the http install to my server with urpmi-proxy installed and it download *my* stage2. That's how I generally test my modifications and seems quicker than building ISOs etc. Thank you, that will work, and I will try that later on today. I would still like to be able to build a complete iso (not just a boot.iso, but one that contains stage2, packages, etc). I've been able to build a stage1 boot.iso. Glen
[Mageia-dev] Freeze push physfs
Please push physfs 2.0.3 bugfix release source and binary compatible : http://icculus.org/pipermail/physfs/2012-October/001056.html This fixes Warzone 2100 warning about buggy 2.0.2 physfs version.
[Mageia-dev] missing signatures
some signatures to fix : maven-artifact-2.2.1-82.mga3.noarch.rpm maven-model-2.2.1-82.mga3.noarch.rpm maven-plugin-registry-2.2.1-82.mga3.noarch.rpm: Assinatura em falta (OK ((none))) /var/cache/urpmi/rpms/maven-profile-2.2.1-82.mga3.noarch.rpm: Assinatura em falta (OK ((none))) /var/cache/urpmi/rpms/maven-project-2.2.1-82.mga3.noarch.rpm: Assinatura em falta (OK ((none))) /var/cache/urpmi/rpms/maven-settings-2.2.1-82.mga3.noarch.rpm: Assinatura em falta (OK ((none)))
Re: [Mageia-dev] missing signatures
Em 22-03-2013 23:30, zezinho escreveu: some signatures to fix : and : maven-monitor-2.2.1-82.mga3.noarch.rpm maven-toolchain-2.2.1-82.mga3.noarch.rpm felix-parent-1.2.1-8.mga3.noarch.rpm
Re: [Mageia-dev] drakxtools drakx-installer-stage2 (mga#9428)
On 23 March 2013 07:37, Thierry Vignaud thierry.vign...@gmail.com wrote: On 22 March 2013 12:20, Glen Ogilvie n...@linuxsolutions.co.nz wrote: I've been trying to test the installer change below before RC4, thinking that it might be quite helpful. I am having a little bit of trouble however. Could someone point me in the right direction on a couple of things. 1. How does the src tar.xz file for drakx-installer-stage2 get created? I assume it comes from a build of svn://svn.mageia.org/svn/soft/drakx/trunk, but can't find how it ends up as a tar.xz 2. When I've built a new stage2, any tricks on getting it into an ISO? I tried building an ISO based on beta3, with the new stage2, using something like: mkisofs -o ~nelg/Mageia-3-beta3-x86_64-DVD/Mageia-3-beta3-x86_64-DVD-stage2.iso -b x86_64/isolinux/isolinux.bin -c boot.catalog -no-emul-boot -boot-load-size 4 -iso-level 4 -J -R /tmp/tt/ This is clearly not right. Is the a documented method I should use to build a new ISO with a modified stage2? In the docs I have read: https://wiki.mageia.org/en/Drakx-installer_tips_and_tricks#rebuild_the_stage_2 and svn://svn.mageia.org/svn/soft/drakx/trunk/docs/README, I have not been able to find instructions on actually putting together an ISO. Is: http://wiki.mandriva.com/en/How_to_remaster_a_personal_Mandriva-based_ISO relevant for Mageia? I guess not, as mkcd does not seem to exist in Mageia. So, a quick howto, or pointing me to the right documentation would be great :) stage2 != ISO ISO is basically the stage1. stage1 is build by drakx-installer-images from: - some packages listed as BR, mainly the kernel drivers firmwares - drakx-installer-binaries that provide the actual stage1 binary = generates what is copied in isolinux/alt0 in install/images/ (*.img + *.iso) stage2 is build by drakx-installer-stage2 = generates what is in install/stage2: mdkinst.sqfs (a squashfs image) there's also rescue.sqfs there that is an alternate stage2 used when using the rescue. stage1 is basically a special initrd that loads the appropriate modules according to detected hardware and to what is specified on command line (eg: the DVD tells it to directly load stage2 from the DVD image). if not instructed to do sg, it displays the text menu asking from where to install (dvd, hard disk, network: http/ftp/nfs). It's a small statically linked program + init + a dhcp client + rescue-gui for the rescue menu it then loads stage2 (install/stage2/mdkinst.sqf or rescue.sqfs) from the URL stage2 is real system, with dynamic libraries, that starts: - an X11 server (if supported and if not asked for text mode) - udev and then go the install steps (language, license, partitionning, installing, summary, updates, ...) Hi Thierry, I appreciate you taking time to reply and let me know these details. It confirms my understanding. What I would like to know is how to create / master the DVD installer ISO, and make that master contain a stage2 that I have built. I have been able to build a stage1 boot.iso, but what I would like is build a DVD image, based on Mageia-3-beta3-x86_64-DVD.iso, with just a different stage2, and maybe a rebuilt stage1 if needed. I guess someone must know how Mageia-3-beta3-x86_64-DVD.iso, and the other images get created. I don't want to rebuild all the packages that go in them, just assemble one with the same packages as Mageia-3-beta3-x86_64-DVD.iso, and a updated install/stage2/mdkinst.sqf file. Once this is figured out, I will happly update the Mageia wiki with details, which I think will be helpful for anyone wanting to make customised Mageia DVDs. Regards Glen Ogilvie
Re: [Mageia-dev] drakxtools drakx-installer-stage2 (mga#9428)
On 22 Mar 2013 22:21, Glen Ogilvie n...@linuxsolutions.co.nz wrote: On 23 March 2013 05:12, AL13N al...@rmail.be wrote: Op vrijdag 22 maart 2013 07:38:56 schreef Frank Griffin: On 03/22/2013 07:20 AM, Glen Ogilvie wrote: [...] 1. How does the src tar.xz file for drakx-installer-stage2 get created? I assume it comes from a build of svn://svn.mageia.org/svn/soft/drakx/trunk http://svn.mageia.org/svn/soft/drakx/trunk, but can't find how it ends up as a tar.xz I'm maybe about two days ahead of you on this, but here's what I think happens, FWIW. You do your checkout, and then in the mdk-stage1 subdirectory, do a make dist-svn. This should produce the tar.xz in the mdk-stage1 directory. [...] make dist actually... it will target make dist-svn or make dist-git depending on if you're using git-svn or not. be advised that dist-svn uses the BASE and any uncommitted change will not be applied. dist-git however, you can commit without pushing them and that will be used. I've had a good play around with make dist. It seems to me, like running make dist in the perl-install directory, (svn://svn.mageia.org/svn/soft/drakx/trunk/ ) does not produce the same tar.xz file as found within drakx-installer-stage2 sources. For example, the tar.gz produced by make dist does not contain the kernel, perl-install/install directories, etc. Also, inside the tar, the first directory is: drakxtools-15.29, rather than drakx-installer-stage2-15.29. It is also only 2.4MB instead of about 4.3MB. Any suggestions? Yes, you need to go into install subdirectory (if I remember the name correctly)
Re: [Mageia-dev] drakxtools drakx-installer-stage2 (mga#9428)
On 23 March 2013 11:57, Pascal Terjan pter...@gmail.com wrote: On 22 Mar 2013 22:21, Glen Ogilvie n...@linuxsolutions.co.nz wrote: On 23 March 2013 05:12, AL13N al...@rmail.be wrote: Op vrijdag 22 maart 2013 07:38:56 schreef Frank Griffin: On 03/22/2013 07:20 AM, Glen Ogilvie wrote: [...] 1. How does the src tar.xz file for drakx-installer-stage2 get created? I assume it comes from a build of svn://svn.mageia.org/svn/soft/drakx/trunk http://svn.mageia.org/svn/soft/drakx/trunk, but can't find how it ends up as a tar.xz I'm maybe about two days ahead of you on this, but here's what I think happens, FWIW. You do your checkout, and then in the mdk-stage1 subdirectory, do a make dist-svn. This should produce the tar.xz in the mdk-stage1 directory. [...] make dist actually... it will target make dist-svn or make dist-git depending on if you're using git-svn or not. be advised that dist-svn uses the BASE and any uncommitted change will not be applied. dist-git however, you can commit without pushing them and that will be used. I've had a good play around with make dist. It seems to me, like running make dist in the perl-install directory, (svn://svn.mageia.org/svn/soft/drakx/trunk/ ) does not produce the same tar.xz file as found within drakx-installer-stage2 sources. For example, the tar.gz produced by make dist does not contain the kernel, perl-install/install directories, etc. Also, inside the tar, the first directory is: drakxtools-15.29, rather than drakx-installer-stage2-15.29. It is also only 2.4MB instead of about 4.3MB. Any suggestions? Yes, you need to go into install subdirectory (if I remember the name correctly) Ah, great. Thank you.. That does the trick. :) Would anyone mind if update https://wiki.mageia.org/en/Drakx-installer_tips_and_tricks, and then update the URL in the spec file of drakx-installer-stage2 to point to it, along with a comment on how to create the source tar.xz Current URL in the spec is: http://wiki.mandriva.com/Tools/DrakX (which just goes to Mandriva's main wiki page) Regards Glen Ogilvie
Re: [Mageia-dev] disable proprietary codec in Chromium
On Mon, Feb 11, 2013 at 12:16 PM, Adrien Guichard guichard.adr...@gmail.com wrote: is it possible to disable proprietary_codecs in chromium in removing the line : -D proprietary_codecs=1 \ from spec and enable NaCL by removing the line: -D disable_nacl=1 \ nacl was enabled in Chromium 21, so it is a regression from Mageia 2. i will do as soon as i have a building chromium :) tks
[Mageia-dev] Fw: Wifi
Hi all, This seems to be an ongoing issue - can someone please help me with an answer for this user? Cheers! Begin forwarded message: Date: Fri, 22 Mar 2013 21:17:09 -0400 From: Jason Kaiser jasonhowardkai...@gmail.com To: cont...@mageia.org Subject: Wifi Dear Team Mageia, I seriously wanted to love your OS, but I was not even able to connect to the internet via wifi. I'm not green--I've been using computers for 30 years and building them for about 15 of those years. I have installed about every OS known to man, but much as I wanted to LOVE Mageia, it just DOESN'T WORK WITH MY WIFI ADAPTER. After several hours of chat logs and discussions, I decided that it wasn't worth it. There are other OS's. I am running a Dell with an Intel i3 and I have to say that every single OS loads fine and recognizes my wifi adapter with no hassle at all. Mageia is different. It just doesn't work. There is so much I have to do to get it to recognize my Intel adapter--it's crazy and far beyond what any rational person would go through to get their computer connected to the Internet. I seriously hope that this is fixed because I really look forward to using Mageia. It looks great, but without the ability to get online, it's useless to me. Thank you, Jason Kaiser -- Trish Fraser, VVMZ4 91L2V -35.67910, 142.66607 Sat Mar 23 13:08:33 EST 2013 GNU/Linux 1997-2012 #283226 counter.li.org cassiopeia up 4 hour(s), 51 min. Mageia release 2 (Official) for x86_64 kernel 3.4.34-desktop-1.mga2 Dear Team Mageia, I seriously wanted to love your OS, but I was not even able to connect to the internet via wifi. Im not green--Ive been using computers for 30 years and building them for about 15 of those years. I have installed about every OS known to man, but much as I wanted to LOVE Mageia, it just DOESNT WORK WITH MY WIFI ADAPTER. After several hours of chat logs and discussions, I decided that it wasnt worth it. There are other OSs. I am running a Dell with an Intel i3 and I have to say that every single OS loads fine and recognizes my wifi adapter with no hassle at all. Mageia is different. It just doesnt work. There is so much I have to do to get it to recognize my Intel adapter--its crazy and far beyond what any rational person would go through to get their computer connected to the Internet. I seriously hope that this is fixed because I really look forward to using Mageia. It looks great, but without the ability to get online, its useless to me. Thank you, Jason Kaiser signature.asc Description: PGP signature
Re: [Mageia-dev] Fw: Wifi
On Fri, 22 Mar 2013 22:09:56 -0400, Trish Fraser tr...@thefrasers.org wrote: Hi all, This seems to be an ongoing issue - can someone please help me with an answer for this user? I've already responded to the op, basically stating that more info is needed, and suggesting Jason consider joining the qa team, so we have more hardware available for testing. Our messages crossed paths, in that I sent my response in the same pop3 connection where I downloaded Trish's message that the message was being forwarded here. Regards, Dave Hodgins
