Re: [Mageia-dev] File Commander Linux repo configuration
Le 26/12/2012 19:57, Felix Miata a écrit : 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. You'd better get the source package and rebuild it. -- BOFH excuse #229: wrong polarity of neutron flow
Re: [Mageia-dev] RFC: dropping prebuilt broadcom-wl drivers
27.12.2012 00:54, Thomas Backlund kirjutas: Hi, I'm thinking of dropping the nonfree prebuilt broadcom-wl drivers (and thereby their support from live images) This means also dropping them from ldetect-lst, and if we keep/add some there, it must be for specific reason and on sub-vendor/device level to not force the wl stuff on everyone... [...] To do this I suggest we should do this asap, and keep it for atleast mga3-beta2 isos, so we can check how it works out... Comments ? I'm OK with that as currently i can't use wifi on LiveDVDs. wl driver is causing more mess than it's helping to resolve. -- Sander
Re: [Mageia-dev] starting openssh inside a chroot, as per mageia wiki
Op donderdag 27 december 2012 14:57:23 schreef Glen Ogilvie: Hi, The wiki, recommends starting openssh from within a chroot, on the following two pages: https://wiki.mageia.org/en/Packagers_chroot https://wiki.mageia.org/en/Chroot This does not work, with a current install from cauldron, as /etc/init.d/sshd does not get created. It seems like the systemd way of starting would be: systemctl start openssh.service But, then produces an error: [root@localhost /]# systemctl start openssh.service Running in chroot, ignoring request. So, Any thoughts on what is the recommended way, and I'll be happy to update the wiki to reflect this. Regards Glen Ogilvie i think you'd have to start systemctl inside the chroot
Re: [Mageia-dev] File Commander Linux repo configuration
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. -- The wise are known for their understanding, and pleasant words are persuasive. Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
Re: [Mageia-dev] task-obsolete - questions about implementation details and how to disable it
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.
[Mageia-dev] rpmlib(TildeInVersions)
Does anyone know what this means? rpmlib(TildeInVersions) = 4.10.0-1 is needed by lib64ftgl-devel-2.1.3-0.rc5.8.mga3.x86_64
Re: [Mageia-dev] starting openssh inside a chroot, as per mageia wiki
On Thu, Dec 27, 2012 at 1:57 AM, Glen Ogilvie n...@linuxsolutions.co.nz wrote: Hi, The wiki, recommends starting openssh from within a chroot, on the following two pages: https://wiki.mageia.org/en/Packagers_chroot https://wiki.mageia.org/en/Chroot This does not work, with a current install from cauldron, as /etc/init.d/sshd does not get created. It seems like the systemd way of starting would be: systemctl start openssh.service But, then produces an error: [root@localhost /]# systemctl start openssh.service Running in chroot, ignoring request. So, Any thoughts on what is the recommended way, and I'll be happy to update the wiki to reflect this. Last time I tried, I gave up after various attempts and now went back to the basics: running sshd and killing it to stop it. Maybe I'll fetch some old initscript.
Re: [Mageia-dev] rpmlib(TildeInVersions)
On Thu, 27 Dec 2012, Pascal Terjan wrote: Does anyone know what this means? rpmlib(TildeInVersions) = 4.10.0-1 is needed by lib64ftgl-devel-2.1.3-0.rc5.8.mga3.x86_64 Recent versions of rpm support tilde in version numbers. And it seems lib64ftgl-devel-2.1.3-0.rc5.8.mga3.x86_64 use a ~ in a provide : pkgconfig(ftgl) = 2.1.3~rc5 So it requires a version of rpm that support tilde in version numbers.
Re: [Mageia-dev] starting openssh inside a chroot, as per mageia wiki
Le 27/12/2012 11:29, Pascal Terjan a écrit : It seems like the systemd way of starting would be: systemctl start openssh.service But, then produces an error: [root@localhost /]# systemctl start openssh.service Running in chroot, ignoring request. So, Any thoughts on what is the recommended way, and I'll be happy to update the wiki to reflect this. Last time I tried, I gave up after various attempts and now went back to the basics: running sshd and killing it to stop it. Maybe I'll fetch some old initscript. I guess using a specific unit file, using builtin systemd chroot support, should help. See http://0pointer.de/blog/projects/changing-roots for details. -- BOFH excuse #346: Your/our computer(s) had suffered a memory leak, and we are waiting for them to be topped up.
Re: [Mageia-dev] rpmlib(TildeInVersions)
On Thu, Dec 27, 2012 at 10:38 AM, nicolas vigier bo...@mars-attacks.org wrote: On Thu, 27 Dec 2012, Pascal Terjan wrote: Does anyone know what this means? rpmlib(TildeInVersions) = 4.10.0-1 is needed by lib64ftgl-devel-2.1.3-0.rc5.8.mga3.x86_64 Recent versions of rpm support tilde in version numbers. And it seems lib64ftgl-devel-2.1.3-0.rc5.8.mga3.x86_64 use a ~ in a provide : pkgconfig(ftgl) = 2.1.3~rc5 Well this provide is not new :) So it requires a version of rpm that support tilde in version numbers. It seems to require an old version(= 4.10.0-1), which is strange So the problem would be that this rpm is not installable with urpmi --root if rpm outside of the chroot is too old (rpm 4.9.1.3 from mageia 2). I guess I will need to fix iurt to support --urpmi-root when rebuilding a media
Re: [Mageia-dev] starting openssh inside a chroot, as per mageia wiki
On Thu, Dec 27, 2012 at 10:55 AM, Guillaume Rousse guillomovi...@gmail.com wrote: Le 27/12/2012 11:29, Pascal Terjan a écrit : It seems like the systemd way of starting would be: systemctl start openssh.service But, then produces an error: [root@localhost /]# systemctl start openssh.service Running in chroot, ignoring request. So, Any thoughts on what is the recommended way, and I'll be happy to update the wiki to reflect this. Last time I tried, I gave up after various attempts and now went back to the basics: running sshd and killing it to stop it. Maybe I'll fetch some old initscript. I guess using a specific unit file, using builtin systemd chroot support, should help. See http://0pointer.de/blog/projects/changing-roots for details. Yes having an unit outside of the chroot with RootDirectoryStartOnly=yes would probably help (I had tried the full system chroot and couldn't get it to work and gave up after an hour) but this is annoying to not be able to start a daemon from inside the chroot which is what I usually want to do.
Re: [Mageia-dev] rpmlib(TildeInVersions)
Pascal Terjan skrev 27.12.2012 13:12: On Thu, Dec 27, 2012 at 10:38 AM, nicolas vigier bo...@mars-attacks.org wrote: On Thu, 27 Dec 2012, Pascal Terjan wrote: Does anyone know what this means? rpmlib(TildeInVersions) = 4.10.0-1 is needed by lib64ftgl-devel-2.1.3-0.rc5.8.mga3.x86_64 Recent versions of rpm support tilde in version numbers. And it seems lib64ftgl-devel-2.1.3-0.rc5.8.mga3.x86_64 use a ~ in a provide : pkgconfig(ftgl) = 2.1.3~rc5 Well this provide is not new :) So it requires a version of rpm that support tilde in version numbers. It seems to require an old version(= 4.10.0-1), which is strange So the problem would be that this rpm is not installable with urpmi --root if rpm outside of the chroot is too old (rpm 4.9.1.3 from mageia 2). I guess I will need to fix iurt to support --urpmi-root when rebuilding a media Or fix the package to not use a tilde in provides :) -- Thomas
Re: [Mageia-dev] rpmlib(TildeInVersions)
On Thu, Dec 27, 2012 at 12:34 PM, Thomas Backlund t...@mageia.org wrote: Pascal Terjan skrev 27.12.2012 13:12: On Thu, Dec 27, 2012 at 10:38 AM, nicolas vigier bo...@mars-attacks.org wrote: On Thu, 27 Dec 2012, Pascal Terjan wrote: Does anyone know what this means? rpmlib(TildeInVersions) = 4.10.0-1 is needed by lib64ftgl-devel-2.1.3-0.rc5.8.mga3.x86_64 Recent versions of rpm support tilde in version numbers. And it seems lib64ftgl-devel-2.1.3-0.rc5.8.mga3.x86_64 use a ~ in a provide : pkgconfig(ftgl) = 2.1.3~rc5 Well this provide is not new :) So it requires a version of rpm that support tilde in version numbers. It seems to require an old version(= 4.10.0-1), which is strange So the problem would be that this rpm is not installable with urpmi --root if rpm outside of the chroot is too old (rpm 4.9.1.3 from mageia 2). I guess I will need to fix iurt to support --urpmi-root when rebuilding a media Or fix the package to not use a tilde in provides :) This is an automatic provides from the version in pkg-config file
Re: [Mageia-dev] RFC: dropping prebuilt broadcom-wl drivers
Kamil Rytarowski skrev 27.12.2012 03:33: On 26.12.2012 23:54, Thomas Backlund wrote: Hi, I'm thinking of dropping the nonfree prebuilt broadcom-wl drivers (and thereby their support from live images) This means also dropping them from ldetect-lst, and if we keep/add some there, it must be for specific reason and on sub-vendor/device level to not force the wl stuff on everyone... The rationale is: [...] 6. dkms-broadcom-wl will still be available on mirrors and on traditional install dvds in nonfree section (new feature for mga3) As far as 6 is actual, I am OK with it. My hardware is working only with the propriatary drivers and dkms packages are sufficient. Are you sure this is still the case ? what is the output of lspcidrake -v for that device ? -- Thomas
Re: [Mageia-dev] RFC: dropping prebuilt broadcom-wl drivers
27.12.2012 00:54, Thomas Backlund kirjoitti: Hi, I'm thinking of dropping the nonfree prebuilt broadcom-wl drivers (and thereby their support from live images) This means also dropping them from ldetect-lst, and if we keep/add some there, it must be for specific reason and on sub-vendor/device level to not force the wl stuff on everyone... [...] Comments ? Agreed. Besides, the free driver works much better (i.e. better range) with my laptop. -- Anssi Hannula
Re: [Mageia-dev] RFC: dropping prebuilt broadcom-wl drivers
2012/12/27 Anssi Hannula an...@mageia.org: 27.12.2012 00:54, Thomas Backlund kirjoitti: Hi, I'm thinking of dropping the nonfree prebuilt broadcom-wl drivers (and thereby their support from live images) This means also dropping them from ldetect-lst, and if we keep/add some there, it must be for specific reason and on sub-vendor/device level to not force the wl stuff on everyone... [...] Comments ? Agreed. Besides, the free driver works much better (i.e. better range) with my laptop. As it looks with i586 Beta1 none of the drivers works at the moment- lspci -v 05:00:0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01) Subsystem: Broadcom Corporation Device 04b5 Kernel driver un use: wl -- wobo
Re: [Mageia-dev] RFC: dropping prebuilt broadcom-wl drivers
Wolfgang Bornath skrev 27.12.2012 15:18: 2012/12/27 Anssi Hannula an...@mageia.org: 27.12.2012 00:54, Thomas Backlund kirjoitti: Hi, I'm thinking of dropping the nonfree prebuilt broadcom-wl drivers (and thereby their support from live images) This means also dropping them from ldetect-lst, and if we keep/add some there, it must be for specific reason and on sub-vendor/device level to not force the wl stuff on everyone... [...] Comments ? Agreed. Besides, the free driver works much better (i.e. better range) with my laptop. As it looks with i586 Beta1 none of the drivers works at the moment- lspci -v 05:00:0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01) Subsystem: Broadcom Corporation Device 04b5 Kernel driver un use: wl can you provide either lspcidrake -v or lspci -vnn for that device -- Thomas
Re: [Mageia-dev] starting openssh inside a chroot, as per mageia wiki
On Thu, 27 Dec 2012, Pascal Terjan wrote: On Thu, Dec 27, 2012 at 10:55 AM, Guillaume Rousse guillomovi...@gmail.com wrote: Le 27/12/2012 11:29, Pascal Terjan a écrit : It seems like the systemd way of starting would be: systemctl start openssh.service But, then produces an error: [root@localhost /]# systemctl start openssh.service Running in chroot, ignoring request. So, Any thoughts on what is the recommended way, and I'll be happy to update the wiki to reflect this. Last time I tried, I gave up after various attempts and now went back to the basics: running sshd and killing it to stop it. Maybe I'll fetch some old initscript. I guess using a specific unit file, using builtin systemd chroot support, should help. See http://0pointer.de/blog/projects/changing-roots for details. Yes having an unit outside of the chroot with RootDirectoryStartOnly=yes would probably help (I had tried the full system chroot and couldn't get it to work and gave up after an hour) Do you mean with systemd-nspawn? Christiaan
Re: [Mageia-dev] RFC: dropping prebuilt broadcom-wl drivers
2012/12/27 Thomas Backlund t...@mageia.org: Wolfgang Bornath skrev 27.12.2012 15:18: 2012/12/27 Anssi Hannula an...@mageia.org: 27.12.2012 00:54, Thomas Backlund kirjoitti: Hi, I'm thinking of dropping the nonfree prebuilt broadcom-wl drivers (and thereby their support from live images) This means also dropping them from ldetect-lst, and if we keep/add some there, it must be for specific reason and on sub-vendor/device level to not force the wl stuff on everyone... [...] Comments ? Agreed. Besides, the free driver works much better (i.e. better range) with my laptop. As it looks with i586 Beta1 none of the drivers works at the moment- lspci -v 05:00:0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01) Subsystem: Broadcom Corporation Device 04b5 Kernel driver un use: wl can you provide either lspcidrake -v or lspci -vnn for that device # lspcidrake -v |grep Broadcom wl : Broadcom Corporation | BCN4312 802.11b/g LP-PHY [NETWORK_OTHER] (vendor:14e4 device:4315 subv:14e4 subd:04b5) (rev 1) That's it -- wobo
Re: [Mageia-dev] RFC: dropping prebuilt broadcom-wl drivers
Wolfgang Bornath skrev 27.12.2012 16:04: 2012/12/27 Thomas Backlund t...@mageia.org: can you provide either lspcidrake -v or lspci -vnn for that device # lspcidrake -v |grep Broadcom wl : Broadcom Corporation | BCN4312 802.11b/g LP-PHY [NETWORK_OTHER] (vendor:14e4 device:4315 subv:14e4 subd:04b5) (rev 1) That's it Thanks. that shows the subvendor/device ids. The 4312 ones are problematic iirc... Now for some tests... 1. uninstall any *broadcom-wl* package on the system. 2. disable nonfree medias (to prevent drakx access to them) 3. reboot. 4. try to reconfigure your wireless connection and see if it works. 5. if it does not work, enable nonfree media again 6. install dkms-broadcom-wl 7. reboot 8. try to reconfigure wireless again and see if it works now. -- Thomas
Re: [Mageia-dev] RFC: dropping prebuilt broadcom-wl drivers
On Thursday, December 27, 2012 01:20:23 AM Sander Lepik wrote: 27.12.2012 00:54, Thomas Backlund kirjutas: Hi, I'm thinking of dropping the nonfree prebuilt broadcom-wl drivers (and thereby their support from live images) This means also dropping them from ldetect-lst, and if we keep/add some there, it must be for specific reason and on sub-vendor/device level to not force the wl stuff on everyone... [...] To do this I suggest we should do this asap, and keep it for atleast mga3-beta2 isos, so we can check how it works out... Comments ? I'm OK with that as currently i can't use wifi on LiveDVDs. wl driver is causing more mess than it's helping to resolve. -- Sander The wl driver isn't working on BCM4311, the b43 is Bug #6111 -- Best regards Thomas Spuhler
Re: [Mageia-dev] RFC: dropping prebuilt broadcom-wl drivers
On Thursday, December 27, 2012 07:21:40 AM Thomas Backlund wrote: Wolfgang Bornath skrev 27.12.2012 16:04: 2012/12/27 Thomas Backlund t...@mageia.org: can you provide either lspcidrake -v or lspci -vnn for that device # lspcidrake -v |grep Broadcom wl : Broadcom Corporation | BCN4312 802.11b/g LP-PHY [NETWORK_OTHER] (vendor:14e4 device:4315 subv:14e4 subd:04b5) (rev 1) That's it Thanks. that shows the subvendor/device ids. The 4312 ones are problematic iirc... Now for some tests... 1. uninstall any *broadcom-wl* package on the system. 2. disable nonfree medias (to prevent drakx access to them) 3. reboot. 4. try to reconfigure your wireless connection and see if it works. 5. if it does not work, enable nonfree media again 6. install dkms-broadcom-wl 7. reboot 8. try to reconfigure wireless again and see if it works now. -- Thomas OK, I'll do that tonight on an older laptop that has the 4311 device -- Best regards Thomas Spuhler signature.asc Description: This is a digitally signed message part.
Re: [Mageia-dev] RFC: dropping prebuilt broadcom-wl drivers
2012/12/27 Thomas Backlund t...@mageia.org: Wolfgang Bornath skrev 27.12.2012 16:04: 2012/12/27 Thomas Backlund t...@mageia.org: can you provide either lspcidrake -v or lspci -vnn for that device # lspcidrake -v |grep Broadcom wl : Broadcom Corporation | BCN4312 802.11b/g LP-PHY [NETWORK_OTHER] (vendor:14e4 device:4315 subv:14e4 subd:04b5) (rev 1) That's it Thanks. that shows the subvendor/device ids. The 4312 ones are problematic iirc... Now for some tests... In which mode do you want me to do that ? - live mode - installed without net access (through additional cable) - installed with net access (through additional cable) ? -- wobo
Re: [Mageia-dev] starting openssh inside a chroot, as per mageia wiki
On Thu, Dec 27, 2012 at 2:01 PM, Christiaan Welvaart c...@daneel.dyndns.org wrote: On Thu, 27 Dec 2012, Pascal Terjan wrote: On Thu, Dec 27, 2012 at 10:55 AM, Guillaume Rousse guillomovi...@gmail.com wrote: Le 27/12/2012 11:29, Pascal Terjan a écrit : It seems like the systemd way of starting would be: systemctl start openssh.service But, then produces an error: [root@localhost /]# systemctl start openssh.service Running in chroot, ignoring request. So, Any thoughts on what is the recommended way, and I'll be happy to update the wiki to reflect this. Last time I tried, I gave up after various attempts and now went back to the basics: running sshd and killing it to stop it. Maybe I'll fetch some old initscript. I guess using a specific unit file, using builtin systemd chroot support, should help. See http://0pointer.de/blog/projects/changing-roots for details. Yes having an unit outside of the chroot with RootDirectoryStartOnly=yes would probably help (I had tried the full system chroot and couldn't get it to work and gave up after an hour) Do you mean with systemd-nspawn? Yes, it seems my chroot was not enough of a real system for it to work
Re: [Mageia-dev] RFC: dropping prebuilt broadcom-wl drivers
Wolfgang Bornath skrev 27.12.2012 16:29: 2012/12/27 Thomas Backlund t...@mageia.org: Wolfgang Bornath skrev 27.12.2012 16:04: 2012/12/27 Thomas Backlund t...@mageia.org: can you provide either lspcidrake -v or lspci -vnn for that device # lspcidrake -v |grep Broadcom wl : Broadcom Corporation | BCN4312 802.11b/g LP-PHY [NETWORK_OTHER] (vendor:14e4 device:4315 subv:14e4 subd:04b5) (rev 1) That's it Thanks. that shows the subvendor/device ids. The 4312 ones are problematic iirc... Now for some tests... In which mode do you want me to do that ? - live mode This wont work as you need to reboot to make sure the hw is in good state , wich will make the uninstall part useless. - installed without net access (through additional cable) - installed with net access (through additional cable) ? you dont need cable access for the first part (1-4) but need cable access (or beta1 install dvd) for second part (5-8) after configuration step you obviously need to disconnect the cable to verify that it works with wireless. And you dont need to do a new install to test this, a current installed/updated cauldron system should be enough. -- Thomas
Re: [Mageia-dev] RFC: dropping prebuilt broadcom-wl drivers
2012/12/27 Thomas Backlund t...@mageia.org: Wolfgang Bornath skrev 27.12.2012 16:29: 2012/12/27 Thomas Backlund t...@mageia.org: Wolfgang Bornath skrev 27.12.2012 16:04: 2012/12/27 Thomas Backlund t...@mageia.org: can you provide either lspcidrake -v or lspci -vnn for that device # lspcidrake -v |grep Broadcom wl : Broadcom Corporation | BCN4312 802.11b/g LP-PHY [NETWORK_OTHER] (vendor:14e4 device:4315 subv:14e4 subd:04b5) (rev 1) That's it Thanks. that shows the subvendor/device ids. The 4312 ones are problematic iirc... Now for some tests... In which mode do you want me to do that ? - live mode This wont work as you need to reboot to make sure the hw is in good state , wich will make the uninstall part useless. Ok, that was clear. - installed without net access (through additional cable) - installed with net access (through additional cable) ? you dont need cable access for the first part (1-4) but need cable access (or beta1 install dvd) for second part (5-8) after configuration step you obviously need to disconnect the cable to verify that it works with wireless. And you dont need to do a new install to test this, a current installed/updated cauldron system should be enough. Ah, I need to do a new because I only have one system with this device :( So I just start from fresh, - first with non-free disabled and reboot, - then non-free enabled with reboot -- wübü
Re: [Mageia-dev] RFC: dropping prebuilt broadcom-wl drivers
Wolfgang Bornath skrev 27.12.2012 16:49: 2012/12/27 Thomas Backlund t...@mageia.org: Wolfgang Bornath skrev 27.12.2012 16:29: 2012/12/27 Thomas Backlund t...@mageia.org: Wolfgang Bornath skrev 27.12.2012 16:04: 2012/12/27 Thomas Backlund t...@mageia.org: can you provide either lspcidrake -v or lspci -vnn for that device # lspcidrake -v |grep Broadcom wl : Broadcom Corporation | BCN4312 802.11b/g LP-PHY [NETWORK_OTHER] (vendor:14e4 device:4315 subv:14e4 subd:04b5) (rev 1) That's it Thanks. that shows the subvendor/device ids. The 4312 ones are problematic iirc... Now for some tests... In which mode do you want me to do that ? - live mode This wont work as you need to reboot to make sure the hw is in good state , wich will make the uninstall part useless. Ok, that was clear. - installed without net access (through additional cable) - installed with net access (through additional cable) ? you dont need cable access for the first part (1-4) but need cable access (or beta1 install dvd) for second part (5-8) after configuration step you obviously need to disconnect the cable to verify that it works with wireless. And you dont need to do a new install to test this, a current installed/updated cauldron system should be enough. Ah, I need to do a new because I only have one system with this device :( So I just start from fresh, - first with non-free disabled and reboot, - then non-free enabled with reboot Hm, is that system running mga2 ? I wonder if I should create 2 test livecds to ease testing right now, one without broadcom-wl, and the other with broadcom-wl and in-kernel drivers blacklisted... -- Thomas
Re: [Mageia-dev] RFC: dropping prebuilt broadcom-wl drivers
2012/12/27 Thomas Backlund t...@mageia.org: Wolfgang Bornath skrev 27.12.2012 16:49: 2012/12/27 Thomas Backlund t...@mageia.org: Wolfgang Bornath skrev 27.12.2012 16:29: 2012/12/27 Thomas Backlund t...@mageia.org: Wolfgang Bornath skrev 27.12.2012 16:04: 2012/12/27 Thomas Backlund t...@mageia.org: can you provide either lspcidrake -v or lspci -vnn for that device # lspcidrake -v |grep Broadcom wl : Broadcom Corporation | BCN4312 802.11b/g LP-PHY [NETWORK_OTHER] (vendor:14e4 device:4315 subv:14e4 subd:04b5) (rev 1) That's it Thanks. that shows the subvendor/device ids. The 4312 ones are problematic iirc... Now for some tests... In which mode do you want me to do that ? - live mode This wont work as you need to reboot to make sure the hw is in good state , wich will make the uninstall part useless. Ok, that was clear. - installed without net access (through additional cable) - installed with net access (through additional cable) ? you dont need cable access for the first part (1-4) but need cable access (or beta1 install dvd) for second part (5-8) after configuration step you obviously need to disconnect the cable to verify that it works with wireless. And you dont need to do a new install to test this, a current installed/updated cauldron system should be enough. Ah, I need to do a new because I only have one system with this device :( So I just start from fresh, - first with non-free disabled and reboot, - then non-free enabled with reboot Hm, is that system running mga2 ? No, it is running no system at all save for the one I'm going to install- It's a small harddisk holding just one. Don't bother, I'd have to re-install anyway. -- wobo
Re: [Mageia-dev] rpmlib(TildeInVersions)
On Thu, 27 Dec 2012 12:54:16 + Pascal Terjan wrote: Or fix the package to not use a tilde in provides :) This is an automatic provides from the version in pkg-config file Then why not use define _provides_exceptions Charles -- I put aside my copy of BOWLING WORLD and think about GUN CONTROL legislation... -- Mageia release 3 (Cauldron) for x86_64$ On SuperSizehttp://www.eslrahc.com Registered Linux user #182463 3.7.1-server-1.mga3 x86_64 -- signature.asc Description: PGP signature
Re: [Mageia-dev] rpmlib(TildeInVersions)
On Thu, Dec 27, 2012 at 3:37 PM, Charles A Edwards c...@eslrahc.com wrote: On Thu, 27 Dec 2012 12:54:16 + Pascal Terjan wrote: Or fix the package to not use a tilde in provides :) This is an automatic provides from the version in pkg-config file Then why not use define _provides_exceptions This provides is correct and may be used by other packages, I see no reason to remove it Old rpm accepts it New rpm accepts it and handles it slightly better I don't really see a reason to forbid installing the package with an old version rpm if it was built with the new rpm given that the produced rpm is exactly the same apart from this added rpmlib(TildeInVersions) fake dependency and it would work perfectly fine without it.
Re: [Mageia-dev] rpmlib(TildeInVersions)
On Thu, 27 Dec 2012, Pascal Terjan wrote: On Thu, Dec 27, 2012 at 3:37 PM, Charles A Edwards c...@eslrahc.com wrote: On Thu, 27 Dec 2012 12:54:16 + Pascal Terjan wrote: Or fix the package to not use a tilde in provides :) This is an automatic provides from the version in pkg-config file Then why not use define _provides_exceptions This provides is correct and may be used by other packages, I see no reason to remove it Old rpm accepts it New rpm accepts it and handles it slightly better I don't really see a reason to forbid installing the package with an old version rpm if it was built with the new rpm given that the produced rpm is exactly the same apart from this added rpmlib(TildeInVersions) fake dependency and it would work perfectly fine without it. AFAICT a Requires: pkgconfig(ftgl) 2.1.3 will be rejected by old rpm but matched by new rpm. We may need to backport this feature. Christiaan
Re: [Mageia-dev] RFC: dropping prebuilt broadcom-wl drivers
Thomas Backlund skrev 27.12.2012 17:01: I wonder if I should create 2 test livecds to ease testing right now, one without broadcom-wl, and the other with broadcom-wl and in-kernel drivers blacklisted... And so I did :) 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/ * broadcom-wl drivers on iso, wl entries in ldetect-lst, in-kernel drivers blacklisted: http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/people/tmb/mga3-beta1-wl-test/Mageia-3-beta1-wl-LiveCD-KDE4-en-i586-CD/ And you can soon find them on any Mageia mirror in: people/tmb/mga3-beta1-wl-test Have fun... -- Thomas
Re: [Mageia-dev] RFC: dropping prebuilt broadcom-wl drivers
2012/12/27 Thomas Backlund t...@mageia.org: Thomas Backlund skrev 27.12.2012 17:01: I wonder if I should create 2 test livecds to ease testing right now, one without broadcom-wl, and the other with broadcom-wl and in-kernel drivers blacklisted... And so I did :) 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/ * broadcom-wl drivers on iso, wl entries in ldetect-lst, in-kernel drivers blacklisted: http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/people/tmb/mga3-beta1-wl-test/Mageia-3-beta1-wl-LiveCD-KDE4-en-i586-CD/ And you can soon find them on any Mageia mirror in: people/tmb/mga3-beta1-wl-test Thx for the extra work, I had to re-install anyway, am in the middle to do so- My first attempt is without actiyated non-free which should tell something- After that I will use the usb stick with enabled non-free and checl again. all without cable- -- wobo
Re: [Mageia-dev] rpmlib(TildeInVersions)
On Thu, Dec 27, 2012 at 4:27 PM, Christiaan Welvaart c...@daneel.dyndns.org wrote: On Thu, 27 Dec 2012, Pascal Terjan wrote: On Thu, Dec 27, 2012 at 3:37 PM, Charles A Edwards c...@eslrahc.com wrote: On Thu, 27 Dec 2012 12:54:16 + Pascal Terjan wrote: Or fix the package to not use a tilde in provides :) This is an automatic provides from the version in pkg-config file Then why not use define _provides_exceptions This provides is correct and may be used by other packages, I see no reason to remove it Old rpm accepts it New rpm accepts it and handles it slightly better I don't really see a reason to forbid installing the package with an old version rpm if it was built with the new rpm given that the produced rpm is exactly the same apart from this added rpmlib(TildeInVersions) fake dependency and it would work perfectly fine without it. AFAICT a Requires: pkgconfig(ftgl) 2.1.3 will be rejected by old rpm but matched by new rpm. We may need to backport this feature. Yes but the provides was already there on Mageia 2 and at least will work find if something requires unversionned pkgconfig(ftgl) (and 2.1.3~rc5 is likely to have 2.1.3 API so 2.1.3 not matching is a good thing :) )
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: Thomas Backlund skrev 27.12.2012 17:01: I wonder if I should create 2 test livecds to ease testing right now, one without broadcom-wl, and the other with broadcom-wl and in-kernel drivers blacklisted... And so I did :) 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/ * broadcom-wl drivers on iso, wl entries in ldetect-lst, in-kernel drivers blacklisted: http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/people/tmb/mga3-beta1-wl-test/Mageia-3-beta1-wl-LiveCD-KDE4-en-i586-CD/ And you can soon find them on any Mageia mirror in: people/tmb/mga3-beta1-wl-test Thx for the extra work, I had to re-install anyway, am in the middle to do so- My first attempt is without actiyated non-free which should tell something- After that I will use the usb stick with enabled non-free and checl again. all without cable- 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. 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? -- wobo
Re: [Mageia-dev] libffi.so.6 pb ?
On Thu, 27 Dec 2012, philippe makowski wrote: can someone explain me why now I have in http://check.mageia.org/cauldron/philippem/build.html a lot of fail because libffi.so.6 is not there ? is there somewhere a depency problem ? I never had before to explicitly ask for libffi build depend for these packages See the thread Rebuild failed on i586 for @334667:drakx-installer-stage2-15.15-1.mga3.src.rpm Fixed with ghc-7.6.1-2.mga3 so you should probably just try again. Christiaan
Re: [Mageia-dev] RFC: dropping prebuilt broadcom-wl drivers
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 ? 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 -- Thomas
Re: [Mageia-dev] RFC: dropping prebuilt broadcom-wl drivers
On 27.12.2012 13:58, Thomas Backlund wrote: Kamil Rytarowski skrev 27.12.2012 03:33: My hardware is working only with the propriatary drivers and dkms packages are sufficient. Are you sure this is still the case ? what is the output of lspcidrake -v for that device ? wl : Broadcom Corporation|BCM4322 802.11a/b/g/n Wireless LAN Controller [NETWORK_OTHER] (vendor:14e4 device:432b subv:1028 subd:000d) (rev: 01) If there is a chance that it may work with the current open drivers, then I can give it a try this weekend. Kamil
Re: [Mageia-dev] RFC: dropping prebuilt broadcom-wl drivers
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 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 . -- wobo
Re: [Mageia-dev] RFC: dropping prebuilt broadcom-wl drivers
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 -- Thomas
Re: [Mageia-dev] RFC: dropping prebuilt broadcom-wl drivers
Kamil Rytarowski skrev 27.12.2012 22:14: On 27.12.2012 13:58, Thomas Backlund wrote: Kamil Rytarowski skrev 27.12.2012 03:33: My hardware is working only with the propriatary drivers and dkms packages are sufficient. Are you sure this is still the case ? what is the output of lspcidrake -v for that device ? wl : Broadcom Corporation|BCM4322 802.11a/b/g/n Wireless LAN Controller [NETWORK_OTHER] (vendor:14e4 device:432b subv:1028 subd:000d) (rev: 01) If there is a chance that it may work with the current open drivers, then I can give it a try this weekend. Hm, Initial BCM4322 support got added upstream in 2.6.38, so yes please try the no-wl test livecd to see if it has improved. -- Thomas
Re: [Mageia-dev] RFC: dropping prebuilt broadcom-wl drivers
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 -- wobo
Re: [Mageia-dev] RFC: dropping prebuilt broadcom-wl drivers
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 ? -- Thomas
Re: [Mageia-dev] libffi.so.6 pb ?
On Thu, Dec 27, 2012 at 7:18 PM, Christiaan Welvaart c...@daneel.dyndns.org wrote: On Thu, 27 Dec 2012, philippe makowski wrote: can someone explain me why now I have in http://check.mageia.org/cauldron/philippem/build.html a lot of fail because libffi.so.6 is not there ? is there somewhere a depency problem ? I never had before to explicitly ask for libffi build depend for these packages See the thread Rebuild failed on i586 for @334667:drakx-installer-stage2-15.15-1.mga3.src.rpm Fixed with ghc-7.6.1-2.mga3 so you should probably just try again. New build is in progress, build.html will be updated tomorrow after it completes Meanwhile you can watch it on http://pkgsubmit.mageia.org/autobuild/index.php?run=2012-12-27
Re: [Mageia-dev] RFC: dropping prebuilt broadcom-wl drivers
Em 26-12-2012 23:54, Thomas Backlund escreveu: 3. the broadcom drivers in upstream kernel.org kernels are improving and also adding support for hw that broadcom-wl is not really supporting even if pretends to do so... We should just be carefull about the fact there are 2 different open source drivers: - brcm80211 which I could never use without crash - b43 * can run with b43-openfwwf for 4xxx hw. * needs nonfree firmware files for 4 hw. Then we maybe need to add some way for dkms-broadcom-wl users to instruct the drakx tools that they prefer/need the nonfree driver... Yes, this is the most needed part, currently we just always install wl driver blindly.
Re: [Mageia-dev] RFC: dropping prebuilt broadcom-wl drivers
On Thursday, December 27, 2012 01:24:16 PM Thomas Backlund wrote: Kamil Rytarowski skrev 27.12.2012 22:14: On 27.12.2012 13:58, Thomas Backlund wrote: Kamil Rytarowski skrev 27.12.2012 03:33: My hardware is working only with the propriatary drivers and dkms packages are sufficient. Are you sure this is still the case ? what is the output of lspcidrake -v for that device ? wl : Broadcom Corporation|BCM4322 802.11a/b/g/n Wireless LAN Controller [NETWORK_OTHER] (vendor:14e4 device:432b subv:1028 subd:000d) (rev: 01) If there is a chance that it may work with the current open drivers, then I can give it a try this weekend. Hm, Initial BCM4322 support got added upstream in 2.6.38, so yes please try the no-wl test livecd to see if it has improved. -- Thomas This is a nice link: http://linuxwireless.org/en/users/Drivers/b43 -- Best regards Thomas Spuhler signature.asc Description: This is a digitally signed message part.
Re: [Mageia-dev] RFC: dropping prebuilt broadcom-wl drivers
On Thursday, December 27, 2012 09:28:29 AM Thomas Backlund wrote: Thomas Backlund skrev 27.12.2012 17:01: I wonder if I should create 2 test livecds to ease testing right now, one without broadcom-wl, and the other with broadcom-wl and in-kernel drivers blacklisted... And so I did :) 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-beta 1-wl-test/Mageia-3-beta1-no-wl-LiveCD-KDE4-en-i586-CD/ * broadcom-wl drivers on iso, wl entries in ldetect-lst, in-kernel drivers blacklisted: http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/people/tmb/mga3-beta 1-wl-test/Mageia-3-beta1-wl-LiveCD-KDE4-en-i586-CD/ And you can soon find them on any Mageia mirror in: people/tmb/mga3-beta1-wl-test Have fun... -- Thomas I am going to try it as soon as the ISO is downloaded. Unfortunately, it's on distcoffee. the slowest mirror. -- Best regards Thomas Spuhler signature.asc Description: This is a digitally signed message part.
Re: [Mageia-dev] tomcat 5
On Fri, Dec 28, 2012 at 12:27 AM, Pascal Terjan pter...@gmail.com wrote: Tomcat 5 is no longer maintained (and will be removed from upstream mirrors in a few days). I guess we want to remove it from cauldron, but just wanted a confirmation :) I was looking at (currently failing to build) apache-jasper-5.5.28 and noticed it can die with tomcat5 if you make sure all rpms that have it as BR still build this is OK for me D.
Re: [Mageia-dev] RFC: dropping prebuilt broadcom-wl drivers
On Thursday, December 27, 2012 04:23:25 PM Thomas Backlund wrote: Thomas Spuhler skrev 28.12.2012 01:20: On Thursday, December 27, 2012 09:28:29 AM Thomas Backlund wrote: Thomas Backlund skrev 27.12.2012 17:01: I wonder if I should create 2 test livecds to ease testing right now, one without broadcom-wl, and the other with broadcom-wl and in-kernel drivers blacklisted... And so I did :) 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-b eta 1-wl-test/Mageia-3-beta1-no-wl-LiveCD-KDE4-en-i586-CD/ * broadcom-wl drivers on iso, wl entries in ldetect-lst, in-kernel drivers blacklisted: http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/people/tmb/mga3-b eta 1-wl-test/Mageia-3-beta1-wl-LiveCD-KDE4-en-i586-CD/ And you can soon find them on any Mageia mirror in: people/tmb/mga3-beta1-wl-test Have fun... -- Thomas I am going to try it as soon as the ISO is downloaded. Unfortunately, it's on distcoffee. the slowest mirror. Read again :) It's on every mageia mirror (as soon as they are synced), just navigate to people/tmb/mga3-beta1-wl-test for example kernel.org: http://mirrors.kernel.org/mageia/people/tmb/mga3-beta1-wl-test/ -- Thomas OK. I booted up and connected to the wireless. What info would you need? BTW I am on IRC as Oro Valley -- Best regards Thomas Spuhler signature.asc Description: This is a digitally signed message part.
Re: [Mageia-dev] RFC: dropping prebuilt broadcom-wl drivers
Thomas Spuhler skrev 28.12.2012 02:00: On Thursday, December 27, 2012 04:23:25 PM Thomas Backlund wrote: Thomas Spuhler skrev 28.12.2012 01:20: On Thursday, December 27, 2012 09:28:29 AM Thomas Backlund wrote: Thomas Backlund skrev 27.12.2012 17:01: I wonder if I should create 2 test livecds to ease testing right now, one without broadcom-wl, and the other with broadcom-wl and in-kernel drivers blacklisted... And so I did :) 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-b eta 1-wl-test/Mageia-3-beta1-no-wl-LiveCD-KDE4-en-i586-CD/ * broadcom-wl drivers on iso, wl entries in ldetect-lst, in-kernel drivers blacklisted: http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/people/tmb/mga3-b eta 1-wl-test/Mageia-3-beta1-wl-LiveCD-KDE4-en-i586-CD/ And you can soon find them on any Mageia mirror in: people/tmb/mga3-beta1-wl-test Have fun... -- Thomas I am going to try it as soon as the ISO is downloaded. Unfortunately, it's on distcoffee. the slowest mirror. Read again :) It's on every mageia mirror (as soon as they are synced), just navigate to people/tmb/mga3-beta1-wl-test for example kernel.org: http://mirrors.kernel.org/mageia/people/tmb/mga3-beta1-wl-test/ -- Thomas OK. I booted up and connected to the wireless. What info would you need? BTW I am on IRC as Oro Valley Well, wich iso works ? if both works, wich one works better ? if one does not work, is there any warning/error in dmesg ? -- Thomas
[Mageia-dev] glibcompat.h?
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. For Mageia 2 x86_64 arch. Not using any Backports-medias. Fully updated. /Kristoffer
Re: [Mageia-dev] RFC: dropping prebuilt broadcom-wl drivers
On Thursday, December 27, 2012 04:23:25 PM Thomas Backlund wrote: Thomas Spuhler skrev 28.12.2012 01:20: On Thursday, December 27, 2012 09:28:29 AM Thomas Backlund wrote: Thomas Backlund skrev 27.12.2012 17:01: I wonder if I should create 2 test livecds to ease testing right now, one without broadcom-wl, and the other with broadcom-wl and in-kernel drivers blacklisted... And so I did :) 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-b eta 1-wl-test/Mageia-3-beta1-no-wl-LiveCD-KDE4-en-i586-CD/ * broadcom-wl drivers on iso, wl entries in ldetect-lst, in-kernel drivers blacklisted: http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/people/tmb/mga3-b eta 1-wl-test/Mageia-3-beta1-wl-LiveCD-KDE4-en-i586-CD/ And you can soon find them on any Mageia mirror in: people/tmb/mga3-beta1-wl-test Have fun... -- Thomas I am going to try it as soon as the ISO is downloaded. Unfortunately, it's on distcoffee. the slowest mirror. Read again :) It's on every mageia mirror (as soon as they are synced), just navigate to people/tmb/mga3-beta1-wl-test for example kernel.org: http://mirrors.kernel.org/mageia/people/tmb/mga3-beta1-wl-test/ -- Thomas Here we go: I downloaded the CD w/o the wl driver and booted up the old DELL E1405 with the BCM4311 wl chip. I opened the Networkcenter and had three interfaces showing: 1. Ethernet 2. Wireless (Wi-Fi) and underneath Broadcom Corporation BCM4311 802.11b/g WLAN 3. Wireless (Wi-Fi) and underneath wlan0 in the window under 3, I got the usual local wireless networks showing up and was able to connect to my home network in the window under 2, I got an empty window and two windows popping up: Looking for required software and drivers... and Error Some packages (broadcom-wl) are required but arn't available. These packages can be found in Mageia, or in the official non-free repository The following componenet is missing: wl ... ... -- Best regards Thomas Spuhler signature.asc Description: This is a digitally signed message part.
Re: [Mageia-dev] RFC: dropping prebuilt broadcom-wl drivers
On Thursday, December 27, 2012 05:13:11 PM Thomas Backlund wrote: Thomas Spuhler skrev 28.12.2012 02:00: On Thursday, December 27, 2012 04:23:25 PM Thomas Backlund wrote: Thomas Spuhler skrev 28.12.2012 01:20: On Thursday, December 27, 2012 09:28:29 AM Thomas Backlund wrote: Thomas Backlund skrev 27.12.2012 17:01: I wonder if I should create 2 test livecds to ease testing right now, one without broadcom-wl, and the other with broadcom-wl and in-kernel drivers blacklisted... And so I did :) 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 -b eta 1-wl-test/Mageia-3-beta1-no-wl-LiveCD-KDE4-en-i586-CD/ * broadcom-wl drivers on iso, wl entries in ldetect-lst, in-kernel drivers blacklisted: http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/people/tmb/mga3 -b eta 1-wl-test/Mageia-3-beta1-wl-LiveCD-KDE4-en-i586-CD/ And you can soon find them on any Mageia mirror in: people/tmb/mga3-beta1-wl-test Have fun... -- Thomas I am going to try it as soon as the ISO is downloaded. Unfortunately, it's on distcoffee. the slowest mirror. Read again :) It's on every mageia mirror (as soon as they are synced), just navigate to people/tmb/mga3-beta1-wl-test for example kernel.org: http://mirrors.kernel.org/mageia/people/tmb/mga3-beta1-wl-test/ -- Thomas OK. I booted up and connected to the wireless. What info would you need? BTW I am on IRC as Oro Valley Well, wich iso works ? if both works, wich one works better ? if one does not work, is there any warning/error in dmesg ? -- Thomas See my other e-mail about the ISO w/o the wl driver. I then booted with the no-wl LiveCD ISO I opened the Networkcenter and there was no wireless network showing at all (I noramlly can see 5 of them in my home). In fact there was a brief splash looking for ... Then came up the error window with the message Unable to find network interface for selected device (using wl driver) I then opened harddrake from a konsole and it was looking for packages to install. After connecting the ethernet cable, the packages were installed (dkms-, libs, gcc, kernel-desktop-devel and kernel- server-devel !, etc) I opened the Networkcenter again and the same message apeared: Unable to find network interface for selected device (using wl driver) Besides that the driver ins't working, the installation is a hassle using a LiveCd. A live CD should be something portable and easy for demo, etc. -- Best regards Thomas Spuhler signature.asc Description: This is a digitally signed message part.
