Re: [Mageia-dev] RFC: dropping prebuilt broadcom-wl drivers
2012/12/27 Wolfgang Bornath molc...@googlemail.com: 2012/12/27 Thomas Backlund t...@mageia.org: Wolfgang Bornath skrev 27.12.2012 22:39: 2012/12/27 Thomas Backlund t...@mageia.org: Wolfgang Bornath skrev 27.12.2012 22:17: 2012/12/27 Thomas Backlund t...@mageia.org: Wolfgang Bornath skrev 27.12.2012 19:54: Ok, so now I am at the point where I try to configure wifi without any additional media than the core repository- The correct wifi is found but the system says that there are additionaöl software and drivers needed (namely broadcom-wl) which I may find in non-free or elsewhere. Just as expected. Did it try to configure it anyway, or did it stop there ? No, it ends there- you can close the ,essage and go back where you have the already used option or the option to use a windows driver with ndiswrapper. Or go back and leave the cinfiguration Hm, ok, so I guess it would need manual configuration to test, but it is easier to test the free drivers you can test with the no-wl test livecd Reboot. Now could I use the same installation to upgrade and use the same usb stick, just activating the core plus non-free ? Or do I have to redo the whole instatallotion? Just use the same install and install dkms-broadcom-wl Ok. so all I have to do go online with cable bound network, set media including non-free, and then install dkms-broadcom-wl plus the needed things. then reboot and try a new attempt at configuring . yep. it might still suggest to install some of the prebuilt drivers, but thats ok. the important part is the blacklist that comes with dkms-broadcom-wl Ok, here I may have been too fast. I went online, set the media including non-free and shot at 'urpmi dkms-broadcom-wl'- The system installed 18 packages but at the end it gave errors: Error! Could not locate wl.ko.xz for module broadcom-wl in the DKMS tree. Yoou must run a dkms build for kernel first- warning: %post(dkms-broadcom-wl-5.100.82.112-5.mga3.non-free.i586) scriptlet failed, exit status 4 Hm, do you have the -devel package matching the kernel you use installed ? Damn! When you are too tired and still go on simple errors are creeping up! I have to call it a day will go on tomorrow, if my brain is still there where I left it. G'night. Ok, new day new challenges! I booted with your KDE live with broadcom-wl. Results concerning wifi: The wifi chip was found and just 4 networks/APs (usually there are more than 15 metworks in the list). Mine is not on the list, filled in the infos including password, started but failed. Rebooted, same. Only 4 of the usually more than 15 networks of my block, but not mine nore any other of the usually busy networks are listed. My wifi router is standing less than a foot away from the AP and the AP is worling, I have another machine running MGA3B1 running with wifi (Atheros chip) working nicely. -- wobo
Re: [Mageia-dev] glibcompat.h?
On Fri, Dec 28, 2012 at 12:14 AM, Kristoffer Grundström kristoffer.grundstrom1...@gmail.com wrote: Where's that file supposed to be located? I have updated the db, but urpmf glibcompat.h doesn't give me a hint to where it is located. Many projects have a file called glibcompat.h, which one do you want?
Re: [Mageia-dev] File Commander Linux repo configuration
Am 27.12.2012 09:48, schrieb Felix Miata: On 2012-12-27 09:02 (GMT+0100) Guillaume Rousse composed: Felix Miata composed: According to http://silk.apana.org.au/fc2development.html I ought to be able to configure a repo from the content of http://silk.apana.org.au/rpm-stable-dev/fcl.repo : You should reread it more carefully, they are assuming everyone uses yum metadata... Morevoer, a binary package build on fedora 1O isn't likely to install properly on mageia. Mandriva 2009 is explicitly listed. libstdc++5-3.3.6-4mdv2009.0.i586.rpm installs on Cauldron (and AFAICT compat with or substitute for it still isn't available from Mageia repos). So I would expect since that works, so would an FCL rpm expressly built for the same system, even if not conveniently via a configured repo. It's author has been around Linux a long time. I doubt he would claim what he claims about running on/built for old Fedora Mandriva releases if it wouldn't install on newer versions. His goal is for it to just work using a minimum of deps that all distros require or at least provide anyway. It installed for me easily using the supplied repo file at least on openSUSE 11.3, 11.4, 12.1, 12.2 release next. I find it hard to believe it wouldn't install as well on Mageia 1, 2 or next, and I would rather have it from a configured repo instead of having to fetch it manually for each new devel build. You'd better get the source package and rebuild it. I looked around that site but didn't notice source even being available. I guess to find out if it even is requires access via a repo mechanism. Not counting Gentoo, last I built anything from source was more than 5 years ago, and I don't expect it will happen again in my lifetime. I don't build. I test software others build. You should be able to install it via urpmi http://silk.apana.org.au/pub/fcl/filecommander-2.40-release1_fedora10.i386.rpm or urpmi http://silk.apana.org.au/pub/fcl/filecommander-2.40-release1_fedora10.x86_64.rpm for x86_64 system, but that doesn't mean that the package will necessarily work. You can't add a Fedora/RHEL style repo as an urpmi repo, and as it only contains one package, which receives no updates, this is even quite useless.
Re: [Mageia-dev] task-obsolete - questions about implementation details and how to disable it
Am 27.12.2012 09:49, schrieb AL13N: Op donderdag 27 december 2012 00:02:28 schreef Florian Hubold: Am 25.12.2012 22:41, schrieb Charles A Edwards: On Tue, 25 Dec 2012 22:24:56 +0100 Guillaume Rousse wrote: As root, run this command: echo task-obsolete /etc/urpmi/skip.list This will add task-obsolete into the skip list and you can use obsoleted software. even easier: rpm -e task-obsolete Needed, but if you do not add it to the skip.list it will be re-installed the next time you update. Charles OK, so there is currently only the option to have all packages obsoleted or to have the mechanism completely disabled? No proper way to only have selected obsoletes? @Thierry, do you have any other clever solution here? Or some workaround or something similar? i just don't think there's any reasonable use case for this. (if you're not a developer), meaning you can maintain it yourself. Well, i just gave one use case (k9copy) which does not need to be maintained, but has been obsoleted. Which does not mean in turn, there's a drop-in replacement for it and/or that it has become obsolete at all. With that in mind, quoting the author: Published on Sunday, 24 July 2011 Written by Jean-Michel Developments on K9Copy stopped. After seven years, I decided to move on and get involved in other projects. The DVD is obsolete, and I no longer believe in the future of desktop Linux. I started working on this project after the installation of Mandrake. I thought it was wonderful and it could replace Windows. One thing was missing: a software to backup my DVD. That was my first program for Linux. I did not know what language to use, or what programming environment. I chose C + + and KDevelop on KDE, because it worked well on Mandrake. Well, the DVD is not really obsolete, many people still use it and want to provide contents via DVDs as that is the only widespread medium that most people have players for. But i get what you mean, and this is quite a cornercase ... Still i'd be happy if there's some solution for this problem.
Re: [Mageia-dev] RFC: dropping prebuilt broadcom-wl drivers
On Thu, 27 Dec 2012 19:34:31 -0700, Thomas Spuhler wrote: I opened the Networkcenter again and the same message apeared: Unable to find network interface for selected device (using wl driver) I've been through all that on a netbook with Broadcom BCM43225 and running fully-updated Mageia-3-A2. I now have solid WiFi after starting to use NetworkManager, which I installed with the following instructions: (1) Install plasma-applet-networkmanager*, and add it to your panel. (To find its icon, Unlock Widgets, go into the 'Panel Tool Box' on the right of the KDE panel, select Add Widgets Then type network in the Categories box, and float your mouse cursor over each until you find Network Management. Double-click on this one and it will show up somewhere on your Panel.) (2) In /etc/NetworkManager/NetworkManager.conf change: plugins=ifcfg-rh,keyfile to: plugins=keyfile (3) Click on the NM applet. It should bring up a dialog which will list your SSID. Click on it to connect (or configure) This has withstood all s/w updates so far, which is more than I can say for Mageia-2 which is my bread-and-butter install on the netbook. Its WiFi was at first working but a s/w update broke it, though over in Google-land I saw a suggestion to install: kernel-firmware-nonfree* after which the WiFi was back to normal. However I have not dared not do any more s/w updates to Mageia-2 in case the WiFi breaks again, though I guess I could always try NetworkManager if it did (or start using M3A2 as main system). (*Tried that on Mageia-3-A2 but did not solve the problem.) -- /\/\aurice
[Mageia-dev] MGA2 - weird usbkey udisksd error
I have a 32GB usb key that I use for playing music on my car stereo, which have an usb input. Today I was attempting fo rthe first time to add files to the usb key using Mageia and not my mdv2010.2 system. But the key doesn't show up in mga2, as it does on mdv2010.2. looking at the syslog, I see this: = Dec 28 15:58:18 solbu-1 kernel: [1108473.573209] usb 3-3: new high-speed USB device number 2 using xhci_hcd Dec 28 15:58:18 solbu-1 kernel: [1108473.584879] usb 3-3: New USB device found, idVendor=0781, idProduct=5566 Dec 28 15:58:18 solbu-1 kernel: [1108473.584883] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Dec 28 15:58:18 solbu-1 kernel: [1108473.584886] usb 3-3: Product: Cruzer Slice Dec 28 15:58:18 solbu-1 kernel: [1108473.584888] usb 3-3: Manufacturer: SanDisk Dec 28 15:58:18 solbu-1 kernel: [1108473.584890] usb 3-3: SerialNumber: 43171113C0E08B90 Dec 28 15:58:18 solbu-1 kernel: [1108473.585033] usb 3-3: ep 0x81 - rounding interval to 32768 microframes, ep desc says 0 microframes Dec 28 15:58:18 solbu-1 kernel: [1108473.585037] usb 3-3: ep 0x2 - rounding interval to 32768 microframes, ep desc says 0 microframes Dec 28 15:58:18 solbu-1 kernel: [1108473.585293] scsi6 : usb-storage 3-3:1.0 Dec 28 15:58:18 solbu-1 mtp-probe: checking bus 3, device 2: /sys/devices/pci:00/:00:14.0/usb3/3-3 Dec 28 15:58:18 solbu-1 mtp-probe: bus: 3, device: 2 was not an MTP device Dec 28 15:58:19 solbu-1 kernel: [1108474.584566] scsi 6:0:0:0: Direct-Access SanDisk Cruzer Slice 8.02 PQ: 0 ANSI: 0 CCS Dec 28 15:58:19 solbu-1 kernel: [1108474.585361] sd 6:0:0:0: [sdb] Attached SCSI removable disk Dec 28 15:58:19 solbu-1 udisksd[6749]: Error opening /etc/crypttab file: Failed to open file '/etc/crypttab': No such file or directory (g-file-error-quark, 4) Dec 28 15:58:19 solbu-1 udisksd[6749]: Error opening /etc/crypttab file: Failed to open file '/etc/crypttab': No such file or directory (g-file-error-quark, 4) Dec 28 15:58:19 solbu-1 udisksd[6749]: Error opening /etc/crypttab file: Failed to open file '/etc/crypttab': No such file or directory (g-file-error-quark, 4) Dec 28 15:58:19 solbu-1 udisksd[6749]: Error opening /etc/crypttab file: Failed to open file '/etc/crypttab': No such file or directory (g-file-error-quark, 4) Dec 28 15:58:19 solbu-1 udisksd[6749]: Error opening /etc/crypttab file: Failed to open file '/etc/crypttab': No such file or directory (g-file-error-quark, 4) Dec 28 15:58:19 solbu-1 udisksd[6749]: Error opening /etc/crypttab file: Failed to open file '/etc/crypttab': No such file or directory (g-file-error-quark, 4) = The udisksd mesages floods in for as long as the usb key is plugged in to the system, and stops only when I remove the key. But the key still works flawlessly on mdv2010.2. So, now what. Should I file this as a bug? -- Johnny A. Solbu PGP key ID: 0xFA687324 signature.asc Description: This is a digitally signed message part.
Re: [Mageia-dev] MGA2 - weird usbkey udisksd error
On Friday 28. December 2012 16.18, Johnny A. Solbu wrote: The udisksd mesages floods in for as long as the usb key is plugged in to the system, and stops only when I remove the key. If I create an empty «/etc/crypttab» file, the flooding stops, and the key eventually show up after perhaps a minute. -- Johnny A. Solbu PGP key ID: 0xFA687324 signature.asc Description: This is a digitally signed message part.
[Mageia-dev] fstab issue - can mount but not umount as user, ehh, what?
Hi. Continuing the usbkey saga, I discovered another bug that I can't resolve. I have an external drive and a usbkey that I attach to my desktop systems. Both have fstab entries, identified by UUID, and its worked nice for the last 2 years. When I plug in the usbkey, I can mount it as a reguklar user, but I cannot unmount it. The error message says that only root can do that. The fstab entry is this: == UUID=0893-1889 /media/usbbrikke vfat nosuid,noexec,dmask=022,fmask=133,uid=500,noauto,user,iocharset=utf8 0 0 == It is the same entry on the mdv2010.2 and mga2 systems, and it works on mdv but not on mga2. Does anyone know why this fstab entry allow me to mount the patition but deny me the right to umount it? -- Johnny A. Solbu PGP key ID: 0xFA687324 signature.asc Description: This is a digitally signed message part.
Re: [Mageia-dev] RFC: dropping prebuilt broadcom-wl drivers
2012/12/28 Maurice Batey maur...@bcs.org.uk: On Thu, 27 Dec 2012 19:34:31 -0700, Thomas Spuhler wrote: I opened the Networkcenter again and the same message apeared: Unable to find network interface for selected device (using wl driver) I've been through all that on a netbook with Broadcom BCM43225 and running fully-updated Mageia-3-A2. I now have solid WiFi after starting to use NetworkManager, which I installed with the following instructions: After reading messages from numerous users who are using Broadcom chips I get the impression that it does not depemd on the chip or the driver or using network manager or not or which kernel, it seems tp depemd on ALL of it. Until MGA2 my Broadcom only worked outside of gnome and after explicitely uninstalling network manager. Another user told his same chip pnly works with network manager, a third one a different story - and all are talking about the sa,e kernel amd the same MGA version and the same Broadcom 4312. It's not only Mageia, trying Debian, Ubuntu, openSuse, Mint and a few others including Mageia, only 2 of them were able to get it to run longer than from one boot to the next. I'll never ever buy that chip again but everywhere you ask peope keep telling you it's ok to buy this hardware for Linux - mine even came with SLED preinstalled. Ok, so much to let out steam after I woke up in a storm of feathers because some how I had torn my bed cover last night. 2 minutes after I started to clean up the dust bowl in my sleeping room my hoover turned belly up (motor seems overheated) and spread all the feathers and dust all over the place. So pls forgive me the short rant about a hardware whith a problem. -- wobo
Re: [Mageia-dev] RFC: dropping prebuilt broadcom-wl drivers
On Fri, 28 Dec 2012 18:15:16 +0100, Wolfgang Bornath wrote: It's not only Mageia, trying Debian, Ubuntu, openSuse, Mint and a few others including Mageia, only 2 of them were able to get it to run longer than from one boot to the next. On the same netbook I also installed Ubuntu 12.01 and Mint 13 KDE. With both of them, they operated the Broadcom WiFi perfectly 'out of the box' - no fuss, no mention of 'looking for...', it just worked. -- /\/\aurice
Re: [Mageia-dev] fstab issue - can mount but not umount as user, ehh, what?
On Fri, 28 Dec 2012 11:13:10 -0500, Johnny A. Solbu coo...@solbu.net wrote: When I plug in the usbkey, I can mount it as a reguklar user, but I cannot unmount it. The error message says that only root can do that. The fstab entry is this: == UUID=0893-1889 /media/usbbrikke vfat nosuid,noexec,dmask=022,fmask=133,uid=500,noauto,user,iocharset=utf8 0 0 == Change the user option to users. https://bugs.mageia.org/show_bug.cgi?id=3533 Regards, Dave Hodgins
Re: [Mageia-dev] RFC: dropping prebuilt broadcom-wl drivers
27.12.2012 18:28, Thomas Backlund kirjutas: Thomas Backlund skrev 27.12.2012 17:01: [...] Theese are exactly the same as the official beta1 isos, with only exceptions are the broadcom-wl tests: * No broadcom-wl drivers on iso, and no wl entries in ldetect-lst: http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/people/tmb/mga3-beta1-wl-test/Mageia-3-beta1-no-wl-LiveCD-KDE4-en-i586-CD/ So i used this iso to test. At first i saw such device reported for wifi connections: Wireless (Wi-Fi) Broadcom Corporation BCM43224 802.11a/b/g/n Clicking on it prompted to install wl stuff. So no luck at first. Then i checked dmesg and saw that b43 was loaded. I ran rmmod on these modules: b43, brcmsmac, bcma After that i blacklisted b43 in /etc/modprobe.d/blacklist-mga.conf and reloaded bcma. Now i saw new interface wlan0 and i was able to configure it. But connection test failed. I think it failed because wpa_supplicant was in bad mood. As i couldn't restart LiveCD i just ran service network restart. After that my laptop connected automatically and network was usable. So if wrong modules are blocked and correct ones loaded then everything seems to work. Output of lspcidrake -v: wl : Broadcom Corporation|BCM43224 802.11a/b/g/n [NETWORK_OTHER] (vendor:14e4 device:4353 subv:1028 subd:000e) (rev: 01) -- Sander
Re: [Mageia-dev] RFC: dropping prebuilt broadcom-wl drivers
2012/12/28 Maurice Batey maur...@bcs.org.uk: On Fri, 28 Dec 2012 18:15:16 +0100, Wolfgang Bornath wrote: It's not only Mageia, trying Debian, Ubuntu, openSuse, Mint and a few others including Mageia, only 2 of them were able to get it to run longer than from one boot to the next. On the same netbook I also installed Ubuntu 12.01 and Mint 13 KDE. With both of them, they operated the Broadcom WiFi perfectly 'out of the box' - no fuss, no mention of 'looking for...', it just worked. Yes. And with MAG1 and MAG2 and Mdv 2010.x it operated out of the box here, no fuss, no mention of looking for. it just worked. Same netbook worked with openSuse but never with network manager nor with Gnome. And now it does not work with MGA3 and (after all this testing MGA3) it does not work anymore with MGA2. using the same software as a couple of weeks ago. So I get the impression that something else was changed, not just the version of the os. -- wobo
Re: [Mageia-dev] Mageia-dev Digest, Vol 28, Issue 77
2012-12-28 12:00, mageia-dev-requ...@mageia.org skrev: Send Mageia-dev mailing list submissions to mageia-dev@mageia.org To subscribe or unsubscribe via the World Wide Web, visit https://www.mageia.org/mailman/listinfo/mageia-dev or, via email, send a message with subject or body 'help' to mageia-dev-requ...@mageia.org You can reach the person managing the list at mageia-dev-ow...@mageia.org When replying, please edit your Subject line so it is more specific than Re: Contents of Mageia-dev digest... Today's Topics: 1. Re: glibcompat.h? (Pascal Terjan) -- Message: 1 Date: Fri, 28 Dec 2012 10:54:52 + From: Pascal Terjanpter...@gmail.com To: Mageia development mailing-listmageia-dev@mageia.org Subject: Re: [Mageia-dev] glibcompat.h? Message-ID: ca+cx+bhwloqdv4ok_jfvwwahepjp8rt+4pgcxtlvbwugxyd...@mail.gmail.com Content-Type: text/plain; charset=ISO-8859-1 On Fri, Dec 28, 2012 at 12:14 AM, Kristoffer Grundstr?m kristoffer.grundstrom1...@gmail.com wrote: Where's that file supposed to be located? I have updated the db, but urpmf glibcompat.h doesn't give me a hint to where it is located. Many projects have a file called glibcompat.h, which one do you want? End of Mageia-dev Digest, Vol 28, Issue 77 ** For Pidgin.
[Mageia-dev] acpid under systemd
Hi Colin :) I have a funny issue with acpid as it is started under systemd (on mga2) I have a little script on my laptop in /etc/acpi/actions that starts xset -display dpms force off or xset -display dpms force on according to the lid state. That commands used to work in the pre-systemd era but now does nothing when acpid is started by systemd. Now, if I start acpid manually from a terminal it works, I can only see some eventual permission isssue with cggroup, Any idea how I could debug this? Cheers, Chris.
