From GNUtoo at no-log.org Sat Jan 3 08:21:13 2015 From: GNUtoo at no-log.org (Denis 'GNUtoo' Carikli) Date: Sat, 3 Jan 2015 09:21:13 +0100 Subject: [Assist] wireless drivers In-Reply-To: <87bnmnhdmj.fsf@deshackra.com> References: <549ED70D.3020409@gmail.com> <87wq5cg9k8.fsf@deshackra.com> <20141227201817.GA22116@libreboot.coova.org> <87bnmnhdmj.fsf@deshackra.com> Message-ID: <20150103092113.580a29db@top-laptop> On Sun, 28 Dec 2014 11:45:40 -0600 Jorge Araya Navarro wrote: > I don't think such thing is even true... http://www.coreboot.org/Fun_Stuff#BIOS_Restrictions Denis. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From GNUtoo at no-log.org Sat Jan 3 08:23:13 2015 From: GNUtoo at no-log.org (Denis 'GNUtoo' Carikli) Date: Sat, 3 Jan 2015 09:23:13 +0100 Subject: [Assist] wireless drivers In-Reply-To: <93CD7DAC-3905-4513-B8C0-4C648EBE89F5@riseup.net> References: <549ED70D.3020409@gmail.com> <87wq5cg9k8.fsf@deshackra.com> <20141227201817.GA22116@libreboot.coova.org> <87bnmnhdmj.fsf@deshackra.com> <20141228175235.GA25587@libreboot.coova.org> <93CD7DAC-3905-4513-B8C0-4C648EBE89F5@riseup.net> Message-ID: <20150103092313.62ce9be3@top-laptop> On Sun, 28 Dec 2014 23:25:51 +0000 ingegnue wrote: > It depends. Mine, from 2009, gave me no trouble. Newer ones might > though. Perhaps research will do, or perhaps just try it and return > it if the card is rejected. Or buy a USB one. Yes, buying USB cards is strongly recommended if you intend to use it on a computer that still has a proprietary BIOS/EFI/UEFI/etc... Denis. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From GNUtoo at no-log.org Sat Jan 3 10:07:14 2015 From: GNUtoo at no-log.org (Denis 'GNUtoo' Carikli) Date: Sat, 3 Jan 2015 11:07:14 +0100 Subject: [Assist] wireless drivers In-Reply-To: <20141229090824.GC31989@libreboot.coova.org> References: <549ED70D.3020409@gmail.com> <87wq5cg9k8.fsf@deshackra.com> <20141227201817.GA22116@libreboot.coova.org> <87bnmnhdmj.fsf@deshackra.com> <20141228175235.GA25587@libreboot.coova.org> <93CD7DAC-3905-4513-B8C0-4C648EBE89F5@riseup.net> <20141229090824.GC31989@libreboot.coova.org> Message-ID: <20150103110714.4c09b9a4@top-laptop.homenet.telecomitalia.it> On Mon, 29 Dec 2014 09:08:25 +0000 Binh-Khoi Nguyen wrote: > I already use a USB one, I was just wondering whether I could replace > the Wifi card. I'll do my own research then :) If you're very good technically you may be able to do it. There are two approaches: 1) Flashing a patched BIOS: This is very risky: Often the flashing utilities are non-free, and they differ from flashrom in what they do. So the risk of bricking the laptop is very high. Once bricked you have to dissemble most of the laptop, and reflash the BIOS chip with an external programmer, you need another computer, the flasher, and something like a pomona clip. Of course you'd have to look if the requirement above match your case, some laptop have different chips formats. I tried this approach on my x60 in order to be able to keep using my ath9k with the BIOS: I needed it to spot some differences between coreboot and the BIOS. It ended up with a brick because the proprietary flashing tool was assembling BIOS pieces together, and instead I used flashrom's as-is. I recovered from it of course. 2) Making the wifi card give PCI ids that are in the whitelist. I looked rapidly at it for someone else's laptop. On the internet, many people reported some success with this, but with intel wifi chips(sic). Now we don't care about intel wifi chips, instead we want to use the atheros ones. Now I didn't find a way to do it from GNU/Linux. Example with a pc-card ath5k that I have available right now: > # ethtool -e wlan3 > Cannot get EEPROM data: Operation not supported I can't even read the eeprom data, because the kernel driver doesn't support that. Reading and writing the eeprom trough ethtool does work with some other wifi drivers. Here what the driver needs: static const struct ethtool_ops foo_ethtool_ops = { [...] .get_eeprom_len = foo_ethtool_get_eeprom_len, .get_eeprom = foo_ethtool_get_eeprom, // probably for reading .set_eeprom = foo_ethtool_set_eeprom, // probably for writing }; On the 3.18 (retrivied with git grep inside drivers/net/wireless): Wifi drivers having the set_eeprom: ipw2200 Wifi driver having the get_eeprom: ipw2200 ath9k libertas Now I didn't investigate other means: 2a) I didn't look if some specific eeprom driver was used or could be used to do that. 2b) I didn't try dumping the eeprom, modifying it and writing it back with an external flasher. 3b) Using other internal connectors than the usual mini-pcie connector reserved for the wifi card. Maybe extra mini-pci connector or internal usb connector could be used to avoid the BIOS whitelist issue. However you should also consider the antenna: if you succeed to connect to the antennas that are in the screen, you should be good. Since having an internal wifi card is very convenient, it may be worth investigating it more. Advantages/disadvantages of internal(PCI) and external(USB) cards: ------------------------------------------------------------------ USB wifi cards have more probability to break: * You may forget it on the laptop and it can break during transportation. * If the card is big and that you move with the laptop around in buildings or outside, it may break due to a collision with something stripping it out of the USB port, and breaking or the card, the USB port or both. Internal cards takes no space outside and usually have a very good range. With USB cards: -> or you choose a small one and it doesn't have a good signal -> or you choose a big one with a good antenna and you do look strange with a big antenna: For instance when you are at a bus stop, with a wifi cards and a huge antenna, using the shell when trying to download and compile some software, and that you listen to some electronic music, people look at you very strangely, trying to figure out what you are doing. However with an USB card, you can know for sure that the wifi is off by removing the card, it also produces no heat inside the laptop. Denis. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From khoi at bknguyen.be Sat Jan 3 10:15:13 2015 From: khoi at bknguyen.be (Binh-Khoi Nguyen) Date: Sat, 3 Jan 2015 10:15:13 +0000 Subject: [Assist] wireless drivers In-Reply-To: <20150103110714.4c09b9a4@top-laptop.homenet.telecomitalia.it> References: <549ED70D.3020409@gmail.com> <87wq5cg9k8.fsf@deshackra.com> <20141227201817.GA22116@libreboot.coova.org> <87bnmnhdmj.fsf@deshackra.com> <20141228175235.GA25587@libreboot.coova.org> <93CD7DAC-3905-4513-B8C0-4C648EBE89F5@riseup.net> <20141229090824.GC31989@libreboot.coova.org> <20150103110714.4c09b9a4@top-laptop.homenet.telecomitalia.it> Message-ID: <20150103101513.GA5251@libreboot> Hey, Thank you so much for your reply! It is very helpful! Unfortunately, I'm very bad technically. Fortunately, my main computer runs Libreboot with an atheros wifi card, I was just talking about my work computer which is connected by cable anyway. Thanks again and happy new year everyone! Khoi On Sat, Jan 03, 2015 at 11:07:14AM +0100, Denis 'GNUtoo' Carikli wrote: >On Mon, 29 Dec 2014 09:08:25 +0000 >Binh-Khoi Nguyen wrote: > >> I already use a USB one, I was just wondering whether I could replace >> the Wifi card. I'll do my own research then :) >If you're very good technically you may be able to do it. > >There are two approaches: >1) Flashing a patched BIOS: This is very risky: Often the flashing > utilities are non-free, and they differ from flashrom in what they > do. So the risk of bricking the laptop is very high. > > Once bricked you have to dissemble most of the laptop, and reflash > the BIOS chip with an external programmer, you need another > computer, the flasher, and something like a pomona clip. > Of course you'd have to look if the requirement above match your > case, some laptop have different chips formats. > > I tried this approach on my x60 in order to be able to keep using > my ath9k with the BIOS: I needed it to spot some differences > between coreboot and the BIOS. It ended up with a brick because > the proprietary flashing tool was assembling BIOS pieces together, > and instead I used flashrom's as-is. I recovered from it of course. > >2) Making the wifi card give PCI ids that are in the whitelist. > I looked rapidly at it for someone else's laptop. > On the internet, many people reported some success with this, but > with intel wifi chips(sic). > Now we don't care about intel wifi chips, instead we want to > use the atheros ones. > Now I didn't find a way to do it from GNU/Linux. > > Example with a pc-card ath5k that I have available right now: > > # ethtool -e wlan3 > > Cannot get EEPROM data: Operation not supported > > I can't even read the eeprom data, because the kernel driver doesn't > support that. Reading and writing the eeprom trough ethtool does work > with some other wifi drivers. Here what the driver needs: > static const struct ethtool_ops foo_ethtool_ops = { > [...] > .get_eeprom_len = foo_ethtool_get_eeprom_len, > .get_eeprom = foo_ethtool_get_eeprom, // probably for reading > .set_eeprom = foo_ethtool_set_eeprom, // probably for writing > }; > > On the 3.18 (retrivied with git grep inside drivers/net/wireless): > Wifi drivers having the set_eeprom: ipw2200 > Wifi driver having the get_eeprom: ipw2200 ath9k libertas > > Now I didn't investigate other means: > 2a) I didn't look if some specific eeprom driver was used or could be > used to do that. > 2b) I didn't try dumping the eeprom, modifying it and writing it > back with an external flasher. > 3b) Using other internal connectors than the usual mini-pcie > connector reserved for the wifi card. Maybe extra mini-pci connector > or internal usb connector could be used to avoid the BIOS whitelist > issue. > However you should also consider the antenna: if you succeed > to connect to the antennas that are in the screen, you should be > good. > >Since having an internal wifi card is very convenient, it may be worth >investigating it more. > >Advantages/disadvantages of internal(PCI) and external(USB) cards: >------------------------------------------------------------------ >USB wifi cards have more probability to break: > * You may forget it on the laptop and it can break during > transportation. > * If the card is big and that you move with the laptop around in > buildings or outside, it may break due to a collision with > something stripping it out of the USB port, and breaking or the > card, the USB port or both. > >Internal cards takes no space outside and usually have a very good >range. >With USB cards: >-> or you choose a small one and it doesn't have a good signal >-> or you choose a big one with a good antenna and you do look strange > with a big antenna: > For instance when you are at a bus stop, with a wifi cards and a > huge antenna, using the shell when trying to download and compile > some software, and that you listen to some electronic music, people > look at you very strangely, trying to figure out what you are doing. > >However with an USB card, you can know for sure that the wifi is off by >removing the card, it also produces no heat inside the laptop. > >Denis. -- Binh-Khoi NGUYEN khoi at member.fsf.org GPG Key: https://bknguyen.be/gpg.html -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From mtjm at mtjm.eu Sat Jan 3 10:42:43 2015 From: mtjm at mtjm.eu (=?utf-8?Q?Micha=C5=82_Mas=C5=82owski?=) Date: Sat, 03 Jan 2015 11:42:43 +0100 Subject: [Assist] wireless drivers In-Reply-To: <20150103110714.4c09b9a4@top-laptop.homenet.telecomitalia.it> (Denis Carikli's message of "Sat, 3 Jan 2015 11:07:14 +0100") References: <549ED70D.3020409@gmail.com> <87wq5cg9k8.fsf@deshackra.com> <20141227201817.GA22116@libreboot.coova.org> <87bnmnhdmj.fsf@deshackra.com> <20141228175235.GA25587@libreboot.coova.org> <93CD7DAC-3905-4513-B8C0-4C648EBE89F5@riseup.net> <20141229090824.GC31989@libreboot.coova.org> <20150103110714.4c09b9a4@top-laptop.homenet.telecomitalia.it> Message-ID: <87mw60p2l8.fsf@mtjm.eu> > 2a) I didn't look if some specific eeprom driver was used or could be > used to do that. https://iwleeprom.googlecode.com/svn/branches/atheros/ can read the EEPROM of an ath9k card, http://madwifi-project.org/wiki/UserDocs/AthInfo should work for ath5k. No tool succeeded at writing it and I don't know the EEPROM data layout used by ath9k cards. > 2b) I didn't try dumping the eeprom, modifying it and writing it > back with an external flasher. It might be hidden under the RF shield and it might be a very small I2C chip. Not as easy as SOIC-8 SPI flash for laptop's boot firmware. > 3b) Using other internal connectors than the usual mini-pcie > connector reserved for the wifi card. Maybe extra mini-pci connector > or internal usb connector could be used to avoid the BIOS whitelist > issue. There might be internal USB cards in the miniPCIe form factor. Some laptops don't check what is in the second miniPCIe slot, but some have no PCI there (X60 has one PCI-only slot for wifi and one USB-only for WWAN). There might be issues with e.g. the rfkill pin. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 818 bytes Desc: not available URL: From elcorreo at deshackra.com Sun Jan 4 18:59:57 2015 From: elcorreo at deshackra.com (Jorge Araya Navarro) Date: Sun, 04 Jan 2015 12:59:57 -0600 Subject: [Assist] wireless drivers In-Reply-To: <20150103092113.580a29db@top-laptop> References: <549ED70D.3020409@gmail.com> <87wq5cg9k8.fsf@deshackra.com> <20141227201817.GA22116@libreboot.coova.org> <87bnmnhdmj.fsf@deshackra.com> <20150103092113.580a29db@top-laptop> Message-ID: <87zj9yz80i.fsf@deshackra.com> Oh, that changes everything! Denis 'GNUtoo' Carikli writes: > On Sun, 28 Dec 2014 11:45:40 -0600 > Jorge Araya Navarro wrote: > >> I don't think such thing is even true... > http://www.coreboot.org/Fun_Stuff#BIOS_Restrictions > > Denis. -- Pax et bonum. Jorge Araya Navarro. ES: Dise?ador Publicitario, Programador Python y colaborador en Parabola GNU/Linux-libre EN: Ads Designer, Python programmer and contributor Parabola GNU/Linux-libre EO: Anonco grafikisto, Pitino programalingvo programisto kai kontribuanto en Parabola GNU/Linux-libre https://es.gravatar.com/shackra From GNUtoo at no-log.org Sun Jan 4 20:29:39 2015 From: GNUtoo at no-log.org (Denis 'GNUtoo' Carikli) Date: Sun, 4 Jan 2015 21:29:39 +0100 Subject: [Assist] wireless drivers In-Reply-To: References: <549ED70D.3020409@gmail.com> Message-ID: <20150104212939.68cbb0bf@top-laptop> On Mon, 29 Dec 2014 02:34:26 -0600 Isaac David Reyes Gonz?lez wrote: > as far as my knowledge goes, if the driver is non-free then it > shouldn't even exist in Linux-libre. If the chip requires the kernel > to load nonfree firmware on it then the whole card is useless under > Linux-libre, even if the driver is free. How would you know that it requires a non-free firmware? I'm not aware of any proprietary drivers inside the official linux kernel. However some of theses free drivers requires a non-free firmware to make the hardware work. And yes, parabola and linux-libre doesn't remove theses drivers and ship them. How would you know without making mistakes, which driver work and which doesn't work without a non-free firmware. That might sound easy at first, a lot of people know that the intel wireless drivers don't work without the firmware. But where do you actually draw the line when many devices do work, out of the box, with linux-libre, without loading the non-free firmware(and the official linux kernel tries to load the firmware). Many ethernet network cards drivers complains about the lack of free firmware, yet they seem to works flawlessly. How about the radeon GPU? some do work, some don't. The bottom line is that in many cases we need to test on real hardware to really know. Denis. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From GNUtoo at no-log.org Sun Jan 4 20:35:41 2015 From: GNUtoo at no-log.org (Denis 'GNUtoo' Carikli) Date: Sun, 4 Jan 2015 21:35:41 +0100 Subject: [Assist] wireless drivers In-Reply-To: <549ED70D.3020409@gmail.com> References: <549ED70D.3020409@gmail.com> Message-ID: <20150104213541.19761527@top-laptop> On Sat, 27 Dec 2014 09:58:05 -0600 Rill wrote: > This seems odd to me. Doesn't freedom suggest I get to choose > exceptions or to use my laptop away from a wired internet connection? The issue with exception is that they're "not well supported": * You'll have to handle the kernel and its update, it's not convenient at all. * You probably don't know all the outcomes of your choice: -> What can the wifi firmware really do? could it modify what's on your laptop RAM(DMA)? -> What are the global(for everybody, not just for you) consequences for freedom? In my experience, buying the right hardware is way less painful. For instance here if you can find a cheap USB wifi card that is supported by the ath9k_htc driver and that suits you well, it would be way better for you. Then in order to avoid NetworkManager confusion and so on, just blacklist the intel wifi driver module. Denis. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From starbasecafe at gmail.com Sun Jan 4 21:25:02 2015 From: starbasecafe at gmail.com (Rill) Date: Sun, 4 Jan 2015 15:25:02 -0600 Subject: [Assist] wireless drivers In-Reply-To: <20150104213541.19761527@top-laptop> References: <549ED70D.3020409@gmail.com> <20150104213541.19761527@top-laptop> Message-ID: <20150104212502.GA20689@libre> I appreciate everyone chiming in to explain the consequences to me. I have purchased an appropriate usb wireless dongle and everything is working well for me. in fact, I am using it right now to send this message. Rill On Sun, Jan 04, 2015 at 09:35:41PM +0100, Denis 'GNUtoo' Carikli wrote: > On Sat, 27 Dec 2014 09:58:05 -0600 > Rill wrote: > > > This seems odd to me. Doesn't freedom suggest I get to choose > > exceptions or to use my laptop away from a wired internet connection? > The issue with exception is that they're "not well supported": > * You'll have to handle the kernel and its update, it's not convenient > at all. > * You probably don't know all the outcomes of your choice: > -> What can the wifi firmware really do? could it modify what's on > your laptop RAM(DMA)? > -> What are the global(for everybody, not just for you) consequences > for freedom? > > In my experience, buying the right hardware is way less painful. For > instance here if you can find a cheap USB wifi card that is supported > by the ath9k_htc driver and that suits you well, it would be way better > for you. > > Then in order to avoid NetworkManager confusion and so on, just > blacklist the intel wifi driver module. > > Denis. From list at sysfu.com Sun Jan 18 23:27:03 2015 From: list at sysfu.com (Seth) Date: Sun, 18 Jan 2015 15:27:03 -0800 Subject: [Assist] 'could not be locally signed' error when trying to install parabola keyring Message-ID: Trying to convert an Arch system to Parabola and getting the error pasted below when trying to install the parabola-keyring. Any troubleshooting ideas? /etc/pacman.conf has: SigLevel = Never when performing the operation. # pacman -U https://www.parabola.nu/packages/libre/any/parabola-keyring/download/ warning: database file for 'libre' does not exist alpmtmp.k9uAE8 294.8 KiB 415K/s 00:01 [############################################################] 100% loading packages... warning: parabola-keyring-20140920-1 is up to date -- reinstalling resolving dependencies... looking for conflicting packages... Packages (1) parabola-keyring-20140920-1 Total Installed Size: 0.41 MiB Net Upgrade Size: 0.00 MiB :: Proceed with installation? [Y/n] (1/1) checking keys in keyring [############################################################] 100% (1/1) checking package integrity [############################################################] 100% (1/1) loading package files [############################################################] 100% (1/1) checking for file conflicts [############################################################] 100% (1/1) checking available disk space [############################################################] 100% (1/1) reinstalling parabola-keyring [############################################################] 100% ==> Appending keys from parabola.gpg... ==> Locally signing trusted keys in keyring... -> Locally signing key 2DFFE834A07FC9A06F4AAAF444BC7D7F49B9A5A4... ==> ERROR: 2DFFE834A07FC9A06F4AAAF444BC7D7F49B9A5A4 could not be locally signed. -> Locally signing key E511343A987CB73D883EFB7E5CECF9F86574BEF2... ==> ERROR: E511343A987CB73D883EFB7E5CECF9F86574BEF2 could not be locally signed. -> Locally signing key 560B3DEC2F13E822ACED475B2EC52AC76AEEB6A0... ==> ERROR: 560B3DEC2F13E822ACED475B2EC52AC76AEEB6A0 could not be locally signed. -> Locally signing key 1B8C5E87702444D3D825CC8086ED62396D5DBA58... ==> ERROR: 1B8C5E87702444D3D825CC8086ED62396D5DBA58 could not be locally signed. -> Locally signing key 6DC925A471AACC8B4EF9F9AEBDAD9605F06AA3BB... ==> ERROR: 6DC925A471AACC8B4EF9F9AEBDAD9605F06AA3BB could not be locally signed. -> Locally signing key E29BA653739EB52E63722FDF946D344D6467A2AC... ==> ERROR: E29BA653739EB52E63722FDF946D344D6467A2AC could not be locally signed. -> Locally signing key DC7E500D8D4407641EA82893476DC656262FB1AE... ==> ERROR: DC7E500D8D4407641EA82893476DC656262FB1AE could not be locally signed. -> Locally signing key 49F707A1CB366C580E625B3C456032D717A4CD9C... -> Locally signing key B70107A3E6A744682A22208D7D19D1AFDD312BBE... ==> ERROR: B70107A3E6A744682A22208D7D19D1AFDD312BBE could not be locally signed. -> Locally signing key BC88635CDC4B0920A4302E3BA8153DEAFCED02BB... ==> ERROR: BC88635CDC4B0920A4302E3BA8153DEAFCED02BB could not be locally signed. -> Locally signing key 66490C131610180BFD632AB3C6DA3E731B754FD2... ==> ERROR: 66490C131610180BFD632AB3C6DA3E731B754FD2 could not be locally signed. ==> ERROR: 66490C131610180BFD632AB3C6DA3E731B754FD2 could not be locally signed. -> Locally signing key 684D54A189305A9CC95446D36B888913DDB59515... ==> ERROR: 684D54A189305A9CC95446D36B888913DDB59515 could not be locally signed. -> Locally signing key 99195DD3BB6FE10A2F36ED8445698744D4FFBFC9... ==> ERROR: 99195DD3BB6FE10A2F36ED8445698744D4FFBFC9 could not be locally signed. -> Locally signing key 5BDCF80CFCE5298696B88FF3B2A551203712CD90... ==> ERROR: 5BDCF80CFCE5298696B88FF3B2A551203712CD90 could not be locally signed. -> Locally signing key C92BAA713B8D53D3CAE63FC9E6974752F9704456... ==> ERROR: C92BAA713B8D53D3CAE63FC9E6974752F9704456 could not be locally signed. -> Locally signing key 8C3F8ABD30DF2AFAC6C039A45906AB5E9AAD00E5... ==> ERROR: 8C3F8ABD30DF2AFAC6C039A45906AB5E9AAD00E5 could not be locally signed. -> Locally signing key 69639F93426CF7CF074E9DF5D5E9DD655D2AE3BC... ==> ERROR: 69639F93426CF7CF074E9DF5D5E9DD655D2AE3BC could not be locally signed. -> Locally signing key 1E81576B94D05ED2615140BC8F564D05CBDA985E... ==> ERROR: 1E81576B94D05ED2615140BC8F564D05CBDA985E could not be locally signed. -> Locally signing key D3EAD7F9D076EB9AF650149DA170D6A0B669E21A... ==> ERROR: D3EAD7F9D076EB9AF650149DA170D6A0B669E21A could not be locally signed. -> Locally signing key 8BD5A323D71FE444D5FDA1FF24BE374E7B44ABF9... ==> ERROR: 8BD5A323D71FE444D5FDA1FF24BE374E7B44ABF9 could not be locally signed. error: command failed to execute correctly From list at sysfu.com Mon Jan 19 20:02:22 2015 From: list at sysfu.com (Seth) Date: Mon, 19 Jan 2015 12:02:22 -0800 Subject: [Assist] 'could not be locally signed' error when trying to install parabola keyring Message-ID: On Mon, 19 Jan 2015 07:45:40 -0800, ingegnue wrote: > I actually ran into this problem, often times what I have to do is: > > 1) check that I overwrote the old mirrorlist with the new one obtained > from parabola site > 2) then make sure pacman-key is initialized (sometimes it fails at > startup): pacman-key --init > 3) pacman -Sy parabola-keyring > 4) pacman-key --populate parabola > 5) pacman-key --refresh-keys I tried again after rolling back to an unmodified Arch snapshot vim /etc/pacman.conf # change siglevel none pacman -U https://www.parabola.nu/packages/libre/any/parabola-keyring/download/ ## same error 'could not be locally signed' pacman -U https://www.parabola.nu/packages/libre/any/pacman-mirrorlist/download/ ## verified /etc/pacman.d/mirrorlist had parabola mirrors listed in it ## add libre repo vim /etc/pacman.conf ## ## [libre] ## Include = /etc/pacman.d/mirrorlist ## try troubleshooting steps in email and it fails again. pacman-key --init pacman -Sy parabola-keyring :: Synchronizing package databases... libre is up to date core is up to date extra is up to date community is up to date warning: parabola-keyring-20140920-1 is up to date -- reinstalling resolving dependencies... looking for conflicting packages... Packages (1) parabola-keyring-20140920-1 Total Installed Size: 0.41 MiB Net Upgrade Size: 0.00 MiB :: Proceed with installation? [Y/n] (1/1) checking keys in keyring [############################################################] 100% (1/1) checking package integrity [############################################################] 100% (1/1) loading package files [############################################################] 100% (1/1) checking for file conflicts [############################################################] 100% (1/1) checking available disk space [############################################################] 100% (1/1) reinstalling parabola-keyring [############################################################] 100% ==> Appending keys from parabola.gpg... ==> Locally signing trusted keys in keyring... -> Locally signing key 2DFFE834A07FC9A06F4AAAF444BC7D7F49B9A5A4... ==> ERROR: 2DFFE834A07FC9A06F4AAAF444BC7D7F49B9A5A4 could not be locally signed. -> Locally signing key E511343A987CB73D883EFB7E5CECF9F86574BEF2... ==> ERROR: E511343A987CB73D883EFB7E5CECF9F86574BEF2 could not be locally signed. -> Locally signing key 560B3DEC2F13E822ACED475B2EC52AC76AEEB6A0... ==> ERROR: 560B3DEC2F13E822ACED475B2EC52AC76AEEB6A0 could not be locally signed. -> Locally signing key 1B8C5E87702444D3D825CC8086ED62396D5DBA58... ==> ERROR: 1B8C5E87702444D3D825CC8086ED62396D5DBA58 could not be locally signed. -> Locally signing key 6DC925A471AACC8B4EF9F9AEBDAD9605F06AA3BB... ==> ERROR: 6DC925A471AACC8B4EF9F9AEBDAD9605F06AA3BB could not be locally signed. -> Locally signing key E29BA653739EB52E63722FDF946D344D6467A2AC... ==> ERROR: E29BA653739EB52E63722FDF946D344D6467A2AC could not be locally signed. -> Locally signing key DC7E500D8D4407641EA82893476DC656262FB1AE... ==> ERROR: DC7E500D8D4407641EA82893476DC656262FB1AE could not be locally signed. -> Locally signing key 49F707A1CB366C580E625B3C456032D717A4CD9C... -> Locally signing key B70107A3E6A744682A22208D7D19D1AFDD312BBE... ==> ERROR: B70107A3E6A744682A22208D7D19D1AFDD312BBE could not be locally signed. -> Locally signing key BC88635CDC4B0920A4302E3BA8153DEAFCED02BB... ==> ERROR: BC88635CDC4B0920A4302E3BA8153DEAFCED02BB could not be locally signed. -> Locally signing key 66490C131610180BFD632AB3C6DA3E731B754FD2... ==> ERROR: 66490C131610180BFD632AB3C6DA3E731B754FD2 could not be locally signed. -> Locally signing key 684D54A189305A9CC95446D36B888913DDB59515... ==> ERROR: 684D54A189305A9CC95446D36B888913DDB59515 could not be locally signed. -> Locally signing key 99195DD3BB6FE10A2F36ED8445698744D4FFBFC9... ==> ERROR: 99195DD3BB6FE10A2F36ED8445698744D4FFBFC9 could not be locally signed. -> Locally signing key 5BDCF80CFCE5298696B88FF3B2A551203712CD90... ==> ERROR: 5BDCF80CFCE5298696B88FF3B2A551203712CD90 could not be locally signed. -> Locally signing key C92BAA713B8D53D3CAE63FC9E6974752F9704456... ==> ERROR: C92BAA713B8D53D3CAE63FC9E6974752F9704456 could not be locally signed. -> Locally signing key 8C3F8ABD30DF2AFAC6C039A45906AB5E9AAD00E5... ==> ERROR: 8C3F8ABD30DF2AFAC6C039A45906AB5E9AAD00E5 could not be locally signed. -> Locally signing key 69639F93426CF7CF074E9DF5D5E9DD655D2AE3BC... ==> ERROR: 69639F93426CF7CF074E9DF5D5E9DD655D2AE3BC could not be locally signed. -> Locally signing key 1E81576B94D05ED2615140BC8F564D05CBDA985E... ==> ERROR: 1E81576B94D05ED2615140BC8F564D05CBDA985E could not be locally signed. -> Locally signing key D3EAD7F9D076EB9AF650149DA170D6A0B669E21A... ==> ERROR: D3EAD7F9D076EB9AF650149DA170D6A0B669E21A could not be locally signed. -> Locally signing key 8BD5A323D71FE444D5FDA1FF24BE374E7B44ABF9... ==> ERROR: 8BD5A323D71FE444D5FDA1FF24BE374E7B44ABF9 could not be locally signed. error: command failed to execute correctly From list at sysfu.com Mon Jan 19 21:56:24 2015 From: list at sysfu.com (Seth) Date: Mon, 19 Jan 2015 13:56:24 -0800 Subject: [Assist] 'could not be locally signed' error when trying to install parabola keyring In-Reply-To: References: Message-ID: On Mon, 19 Jan 2015 13:06:30 -0800, ingegnue wrote: > That is as I expected -- it should resolve after you do pacman-key > --populate parabola and pacman-key --refresh-keys. Did you try those two > steps? > > After you do those two, what is the output of pacman -Sy > parabola-keyring? I had aborted the process after running "pacman -Sy parabola-keyring" and getting the error again. The key to resolving was to continue in spite of the errors and run both of these commands. pacman-key --populate parabola pacman-key --refresh-keys Thank you for your help. From ingegnue at riseup.net Mon Jan 19 22:18:47 2015 From: ingegnue at riseup.net (ingegnue) Date: Mon, 19 Jan 2015 22:18:47 +0000 Subject: [Assist] 'could not be locally signed' error when trying to install parabola keyring In-Reply-To: References: Message-ID: <7E463834-F16C-4F83-82A9-C287E1336AC4@riseup.net> Great! :) You're welcome! (And welcome to the community!) (Oops, I keep forgetting to hit reply-all..) On January 19, 2015 4:56:24 PM EST, Seth wrote: >On Mon, 19 Jan 2015 13:06:30 -0800, ingegnue >wrote: > >> That is as I expected -- it should resolve after you do pacman-key >> --populate parabola and pacman-key --refresh-keys. Did you try those >two >> steps? >> >> After you do those two, what is the output of pacman -Sy >> parabola-keyring? > >I had aborted the process after running "pacman -Sy parabola-keyring" >and >getting the error again. > >The key to resolving was to continue in spite of the errors and run >both >of these commands. > >pacman-key --populate parabola >pacman-key --refresh-keys > >Thank you for your help. From pietro.ferrera at gmail.com Tue Jan 20 14:26:08 2015 From: pietro.ferrera at gmail.com (Pietro Ferrera) Date: Tue, 20 Jan 2015 15:26:08 +0100 Subject: [Assist] Parabola on Dell XPS 13 9333 Message-ID: Hey guys, I was wondering if I could install Parabola to my laptop and have it fully working. (I am especially worried about my wireless connection, since i have an intel wireless card) I'll attach the output of "sudo lshw" in case it's needed Thank you in advance, Pietro -------------- next part -------------- description: Portable Computer product: XPS13 9333 (060A) vendor: Dell Inc. version: 0.1 serial: 519BPY1 width: 64 bits capabilities: smbios-2.7 dmi-2.7 vsyscall32 configuration: administrator_password=unknown boot=normal chassis=portable family=Shark Bay System frontpanel_password=unknown keyboard_password=unknown power-on_password=unknown sku=060A uuid=44454C4C-3100-1039-8042-B5C04F505931 *-core description: Motherboard product: 0GFTRT vendor: Dell Inc. physical id: 0 version: A00 serial: .519BPY1.CN486433CD0189. slot: Part Component *-cpu description: CPU product: Core i7 (To Be Filled By O.E.M.) vendor: Intel Corp. physical id: 0 bus info: cpu at 0 version: Intel(R) Core(TM) i7-4500U CPU @ 1.80GHz serial: To Be Filled By O.E.M. slot: CPU Socket - U3E1 size: 1799MHz capacity: 3GHz width: 64 bits clock: 100MHz capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt cpufreq configuration: cores=2 enabledcores=2 threads=4 *-cache:0 description: L1 cache physical id: 2 slot: L1-Cache size: 32KiB capacity: 32KiB capabilities: asynchronous internal write-back instruction *-cache:1 description: L2 cache physical id: 3 slot: L2-Cache size: 256KiB capacity: 256KiB capabilities: asynchronous internal write-back unified *-cache:2 description: L3 cache physical id: 4 slot: L3-Cache size: 4MiB capacity: 4MiB capabilities: asynchronous internal write-back unified *-cache description: L1 cache physical id: 1 slot: L1-Cache size: 32KiB capacity: 32KiB capabilities: asynchronous internal write-back data *-memory description: System Memory physical id: 5 slot: System board or motherboard size: 8GiB *-bank:0 description: SODIMM DDR3 Synchronous 1600 MHz (0.6 ns) product: H5TC8G63AMR-PBR vendor: Hynix/Hyundai physical id: 0 serial: 00000000 slot: ChannelA-DIMM0 size: 4GiB width: 64 bits clock: 1600MHz (0.6ns) *-bank:1 description: SODIMM DDR3 Synchronous 1600 MHz (0.6 ns) product: H5TC8G63AMR-PBR vendor: Hynix/Hyundai physical id: 1 serial: 00000000 slot: ChannelB-DIMM0 size: 4GiB width: 64 bits clock: 1600MHz (0.6ns) *-firmware description: BIOS vendor: Dell Inc. physical id: d version: A02 date: 12/11/2013 size: 128KiB capacity: 6592KiB capabilities: pci pnp upgrade shadowing escd cdboot bootselect edd int13floppy360 int13floppy1200 int13floppy720 int5printscreen int9keyboard int14serial int17printer int10video acpi usb ls120boot smartbattery biosbootspecification netboot *-pci description: Host bridge product: Haswell-ULT DRAM Controller vendor: Intel Corporation physical id: 100 bus info: pci at 0000:00:00.0 version: 09 width: 32 bits clock: 33MHz *-display description: VGA compatible controller product: Haswell-ULT Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci at 0000:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:42 memory:f0000000-f03fffff memory:e0000000-efffffff ioport:3000(size=64) *-multimedia:0 description: Audio device product: Haswell-ULT HD Audio Controller vendor: Intel Corporation physical id: 3 bus info: pci at 0000:00:03.0 version: 09 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: driver=snd_hda_intel latency=0 resources: irq:45 memory:f0510000-f0513fff *-usb description: USB controller product: 8 Series USB xHCI HC vendor: Intel Corporation physical id: 14 bus info: pci at 0000:00:14.0 version: 04 width: 64 bits clock: 33MHz capabilities: pm msi xhci bus_master cap_list configuration: driver=xhci_hcd latency=0 resources: irq:41 memory:f0500000-f050ffff *-usbhost:0 product: xHCI Host Controller vendor: Linux 3.17.8-300.fc21.x86_64 xhci_hcd physical id: 0 bus info: usb at 2 logical name: usb2 version: 3.17 capabilities: usb-3.00 configuration: driver=hub slots=4 speed=5000Mbit/s *-usbhost:1 product: xHCI Host Controller vendor: Linux 3.17.8-300.fc21.x86_64 xhci_hcd physical id: 1 bus info: usb at 1 logical name: usb1 version: 3.17 capabilities: usb-2.00 configuration: driver=hub slots=9 speed=480Mbit/s *-usb:0 description: Human interface device product: Synaptics Large Touch Screen vendor: SYNAPTICS physical id: 3 bus info: usb at 1:3 version: 0.01 capabilities: usb-2.00 configuration: driver=usbhid maxpower=144mA speed=12Mbit/s *-usb:1 description: Video product: Integrated_Webcam_HD vendor: CN0Y2TKG724873A4A4DYA00 physical id: 5 bus info: usb at 1:5 version: 39.02 serial: 200901010001 capabilities: usb-2.01 configuration: driver=uvcvideo maxpower=500mA speed=480Mbit/s *-usb:2 description: Bluetooth wireless interface vendor: Intel Corp. physical id: 6 bus info: usb at 1:6 version: 0.01 capabilities: bluetooth usb-2.00 configuration: driver=btusb maxpower=100mA speed=12Mbit/s *-communication description: Communication controller product: 8 Series HECI #0 vendor: Intel Corporation physical id: 16 bus info: pci at 0000:00:16.0 version: 04 width: 64 bits clock: 33MHz capabilities: pm msi bus_master cap_list configuration: driver=mei_me latency=0 resources: irq:43 memory:f0519000-f051901f *-multimedia:1 description: Audio device product: 8 Series HD Audio Controller vendor: Intel Corporation physical id: 1b bus info: pci at 0000:00:1b.0 version: 04 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: driver=snd_hda_intel latency=0 resources: irq:44 memory:f0514000-f0517fff *-pci:0 description: PCI bridge product: 8 Series PCI Express Root Port 1 vendor: Intel Corporation physical id: 1c bus info: pci at 0000:00:1c.0 version: e4 width: 32 bits clock: 33MHz capabilities: pci pciexpress msi pm normal_decode bus_master cap_list configuration: driver=pcieport resources: irq:16 *-pci:1 description: PCI bridge product: 8 Series PCI Express Root Port 3 vendor: Intel Corporation physical id: 1c.2 bus info: pci at 0000:00:1c.2 version: e4 width: 32 bits clock: 33MHz capabilities: pci pciexpress msi pm normal_decode bus_master cap_list configuration: driver=pcieport resources: irq:18 memory:f0400000-f04fffff *-network description: Wireless interface product: Wireless 7260 vendor: Intel Corporation physical id: 0 bus info: pci at 0000:02:00.0 logical name: wlp2s0 version: 6b serial: 5c:51:4f:71:4e:6d width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=3.17.8-300.fc21.x86_64 firmware=25.222.9.0 ip=131.114.104.77 latency=0 link=yes multicast=yes wireless=IEEE 802.11abgn resources: irq:46 memory:f0400000-f0401fff *-isa description: ISA bridge product: 8 Series LPC Controller vendor: Intel Corporation physical id: 1f bus info: pci at 0000:00:1f.0 version: 04 width: 32 bits clock: 33MHz capabilities: isa bus_master cap_list configuration: driver=lpc_ich latency=0 resources: irq:0 *-storage description: SATA controller product: 8 Series SATA Controller 1 [AHCI mode] vendor: Intel Corporation physical id: 1f.2 bus info: pci at 0000:00:1f.2 version: 04 width: 32 bits clock: 66MHz capabilities: storage msi pm ahci_1.0 bus_master cap_list configuration: driver=ahci latency=0 resources: irq:40 ioport:3088(size=8) ioport:3094(size=4) ioport:3080(size=8) ioport:3090(size=4) ioport:3060(size=32) memory:f051c000-f051c7ff *-serial UNCLAIMED description: SMBus product: 8 Series SMBus Controller vendor: Intel Corporation physical id: 1f.3 bus info: pci at 0000:00:1f.3 version: 04 width: 64 bits clock: 33MHz configuration: latency=0 resources: memory:f0518000-f05180ff ioport:efa0(size=32) *-scsi physical id: 2 logical name: scsi2 capabilities: emulated *-disk description: ATA Disk product: LITEONIT LMT-256 physical id: 0.0.0 bus info: scsi at 2:0.0.0 logical name: /dev/sda version: 10F serial: TW0XXM305508539E3019 size: 238GiB (256GB) capabilities: partitioned partitioned:dos configuration: ansiversion=5 logicalsectorsize=512 sectorsize=512 signature=b2feff73 *-volume:0 description: EXT4 volume vendor: Linux physical id: 1 bus info: scsi at 2:0.0.0,1 logical name: /dev/sda1 logical name: /boot version: 1.0 serial: eb9a6e59-c446-458f-b071-435aefa00389 size: 500MiB capacity: 500MiB capabilities: primary bootable journaled extended_attributes huge_files dir_nlink extents ext4 ext2 initialized configuration: created=2014-12-11 22:09:44 filesystem=ext4 lastmountpoint=/boot modified=2015-01-19 21:40:54 mount.fstype=ext4 mount.options=rw,seclabel,relatime,data=ordered mounted=2015-01-19 21:40:54 state=mounted *-volume:1 description: Linux LVM Physical Volume partition physical id: 2 bus info: scsi at 2:0.0.0,2 logical name: /dev/sda2 serial: IM9C50-fTlo-FYMu-CAbs-8MKI-7xGH-vHzHhn size: 237GiB capacity: 237GiB capabilities: primary multi lvm2 *-battery product: DELL vendor: SDI physical id: 1 version: 2008 serial: 1.0 slot: Rear capacity: 55500mWh configuration: voltage=7.5V From list at sysfu.com Tue Jan 20 17:33:59 2015 From: list at sysfu.com (Seth) Date: Tue, 20 Jan 2015 09:33:59 -0800 Subject: [Assist] Parabola on Dell XPS 13 9333 In-Reply-To: References: Message-ID: On Tue, 20 Jan 2015 06:26:08 -0800, Pietro Ferrera wrote: > Hey guys, > I was wondering if I could install Parabola to my laptop and have it > fully working. (I am especially worried about my wireless connection, > since i have an intel wireless card) > > I'll attach the output of "sudo lshw" in case it's needed Have you already looked up your card in these three resources mentioned in the wiki? https://wiki.parabola.nu/Wireless_Setup#Discover_if_the_card_is_supported From elcorreo at deshackra.com Wed Jan 21 04:04:17 2015 From: elcorreo at deshackra.com (Jorge Araya Navarro) Date: Tue, 20 Jan 2015 22:04:17 -0600 Subject: [Assist] Parabola on Dell XPS 13 9333 In-Reply-To: References: Message-ID: <873874bwzi.fsf@abril.charola> I would rather download Trisquel and run it as a live session and test my hardware, I call it the ?easy way? Seth writes: > On Tue, 20 Jan 2015 06:26:08 -0800, Pietro Ferrera > wrote: > >> Hey guys, >> I was wondering if I could install Parabola to my laptop and have it >> fully working. (I am especially worried about my wireless connection, >> since i have an intel wireless card) >> >> I'll attach the output of "sudo lshw" in case it's needed > > Have you already looked up your card in these three resources mentioned in > the wiki? > > https://wiki.parabola.nu/Wireless_Setup#Discover_if_the_card_is_supported > _______________________________________________ > Assist mailing list > Assist at lists.parabola.nu > https://lists.parabola.nu/mailman/listinfo/assist -- Pax et bonum. Jorge Araya Navarro. ES: Dise?ador Publicitario, Programador Python y colaborador en Parabola GNU/Linux-libre EN: Ads Designer, Python programmer and contributor Parabola GNU/Linux-libre EO: Anonco grafikisto, Pitino programalingvo programisto kai kontribuanto en Parabola GNU/Linux-libre https://es.gravatar.com/shackra From GNUtoo at no-log.org Wed Jan 21 20:53:09 2015 From: GNUtoo at no-log.org (Denis 'GNUtoo' Carikli) Date: Wed, 21 Jan 2015 21:53:09 +0100 Subject: [Assist] Parabola on Dell XPS 13 9333 In-Reply-To: References: Message-ID: <20150121215309.38014d08@top-laptop> On Tue, 20 Jan 2015 15:26:08 +0100 Pietro Ferrera wrote: > description: VGA compatible controller > product: Haswell-ULT Integrated Graphics Controller > vendor: Intel Corporation Intel GPU, should work and have 3D acceleration. > product: 8 Series USB xHCI HC > product: xHCI Host Controller > product: Synaptics Large Touch Screen > product: Integrated_Webcam_HD > description: Bluetooth wireless interface > product: 8 Series HD Audio Controller You should test all that. > description: Communication controller That's the management engine[1]. > driver=iwlwifi driverversion=3.17.8-300.fc21.x86_64 > firmware=25.222.9.0 ip=131.114.104.77 latency=0 link=yes Intel wifi card. Get an USB wifi card that works without a non-free firmware. References: ----------- [1]https://en.wikipedia.org/wiki/Intel_Active_Management_Technology#Management_Engine Denis. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From emulatorman at riseup.net Thu Jan 22 11:54:46 2015 From: emulatorman at riseup.net (=?windows-1252?Q?Andr=E9_Silva?=) Date: Thu, 22 Jan 2015 09:54:46 -0200 Subject: [Assist] Parabola on Dell XPS 13 9333 In-Reply-To: <20150121215309.38014d08@top-laptop> References: <20150121215309.38014d08@top-laptop> Message-ID: <54C0E506.3030405@riseup.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 01/21/2015 06:53 PM, Denis 'GNUtoo' Carikli wrote: > On Tue, 20 Jan 2015 15:26:08 +0100 Pietro Ferrera > wrote: >> driver=iwlwifi driverversion=3.17.8-300.fc21.x86_64 >> firmware=25.222.9.0 ip=131.114.104.77 latency=0 link=yes > Intel wifi card. Get an USB wifi card that works without a > non-free firmware. > There are a list about USB wifi cards that works without nonfree firmware to see [0][1] [0]:https://wikidevi.com/wiki/Rtl8187#Supported_modes [1]:https://wikidevi.com/wiki/Ath9k_htc#Supported_modes -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJUwOT3AAoJEOaXR1L5cERWnoUQAOBQZfUuLwwbcB95jb6iPfMg iCL/P1BcfSh9rUGKOPIDJMrw/Jzsv3FqK0YNBoOoFdbPCBY22HFXF9sVjl+rZ2MT iQVu96MMnYbsvPqz9KdxF2GF8+GhOX35Cygd7dnd2xNZM7fBNLcpEF3thiiqE909 9CIRmOzpnDnamvkyksuDtckfDZkD1aGlNGuTSFzFjRIZY/DFPrA4fPOIlatZGbBX lOJHyCuDdfwCgI21E0nipm0LW0mdN84qtJIGavaMYXuKR71Lp6u/xTXqm3UwVcls cuV/N14q7vDP/P+m/ThySK6xBWCucXTYYvfcUgZgLhTluVNZyt6ir70frKNkMgPk bF7o9KJHxAbLZPWdEbcn8UFnlul7GfZk+7omF4UwYmjN37Kl8X4JPDpdpRvyHxwm h7ZiSDVtPy6PmCpkANPnbD++bbWReLZGvf3zwD3h9vkcR7TksOfJZn25lum0bqej BVlLvReUYA7L9cDa+d6a6Mys6IJ+Fr7XHd1ZkFxNsbWWli3t77XO8xLJ7zzog+iC ciqrXsz7F4Qm4/mBtWDQMcZASUpyV2xV9AkO0e3CR1EbJxTAPBqSUPVj1ow88ZuK QMvxAv9vocUgUFJG+KLixEqDAdof3GGN29JtDPQuVoSYcK0Bp4qltdiqSoyxrqvZ NSKMoRIqF/h2yum8EC4/ =d9k7 -----END PGP SIGNATURE----- From khoi at bknguyen.be Tue Jan 27 12:10:42 2015 From: khoi at bknguyen.be (Binh-Khoi Nguyen) Date: Tue, 27 Jan 2015 12:10:42 +0000 Subject: [Assist] Parabola on Ben Nanonote? Message-ID: <20150127121042.GA17011@libreboot.home> Hey, I was wondering if anyone had a Ben Nanonote and if it's possible to install Parabola on it. The people at LibreWRT told me that LibreWRT hadn't been updated for a very long time and that it wasn't recommended for security reasons. Thanks for your help, -- Binh-Khoi NGUYEN khoi at member.fsf.org b.nguyen12 at imperial.ac.uk GPG Key: https://bknguyen.be/gpg.html From ingegnue at riseup.net Tue Jan 27 15:55:32 2015 From: ingegnue at riseup.net (ingegnue) Date: Tue, 27 Jan 2015 15:55:32 +0000 Subject: [Assist] Parabola on Ben Nanonote? In-Reply-To: <20150127121042.GA17011@libreboot.home> References: <20150127121042.GA17011@libreboot.home> Message-ID: On January 27, 2015 7:10:42 AM EST, Binh-Khoi Nguyen wrote: >Hey, > >I was wondering if anyone had a Ben Nanonote and if it's possible to >install Parabola on it. > >The people at LibreWRT told me that LibreWRT hadn't been updated for a >very long time and that it wasn't recommended for security reasons. > >Thanks for your help, A look at the specs says the Nanonote's CPU has an Ingenic XBurst Jz4720?which is compatible with MIPS32, according to the Ingenic wiki. Parabola has support for MIPS64, but not MIPS32 unfortunately. I don't know too much about MIPS but give it a try and it doesn't work, perhaps you can make a port? Some folks have been working on an ARM port so it is probably doable. Supporting the Nanonote seems like a cool idea to me... From zach at zachwick.com Tue Jan 27 16:09:34 2015 From: zach at zachwick.com (zach wick) Date: Tue, 27 Jan 2015 11:09:34 -0500 Subject: [Assist] Parabola on Ben Nanonote? In-Reply-To: <20150127121042.GA17011@libreboot.home> References: <20150127121042.GA17011@libreboot.home> Message-ID: <20150127160934.GA2975@Argo.local> On Tue, Jan 27, 2015 at 12:10:42PM +0000, Binh-Khoi Nguyen wrote: > Hey, > > I was wondering if anyone had a Ben Nanonote and if it's possible to install > Parabola on it. > > The people at LibreWRT told me that LibreWRT hadn't been updated for a very > long time and that it wasn't recommended for security reasons. > I have a Ben Nanonote that I run Debian on without any issues. I also know that LibreCMC [0] will run on the Nanonote. If your intention with running Parabola on the Nanonote is a completely free computing environment, then LibreCMC will satisfy that requirement. LibreCMC is even endorsed by the Free Software Foundation as a Free GNU/Linux distro. [0] http://librecmc.org -zach -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From khoi at bknguyen.be Tue Jan 27 17:53:40 2015 From: khoi at bknguyen.be (Binh-Khoi Nguyen) Date: Tue, 27 Jan 2015 17:53:40 +0000 Subject: [Assist] Parabola on Ben Nanonote? In-Reply-To: <20150127160934.GA2975@Argo.local> References: <20150127121042.GA17011@libreboot.home> <20150127160934.GA2975@Argo.local> Message-ID: <20150127175340.GB12914@libreboot.home> Hi, Thank you for your reply. Basically I just want a free distribution (or Debian), and the more convenient the better. I tried installing Debian once but I couldn't really upgrade to recent software (I think I had a problem when I did a dist-upgrade). Does LibreCMC has a package management system? I basically just want a recent version of vim, vifm, mutt, and calcurse. Thanks! On Tue, Jan 27, 2015 at 11:09:34AM -0500, zach wick wrote: >On Tue, Jan 27, 2015 at 12:10:42PM +0000, Binh-Khoi Nguyen wrote: >> Hey, >> >> I was wondering if anyone had a Ben Nanonote and if it's possible to install >> Parabola on it. >> >> The people at LibreWRT told me that LibreWRT hadn't been updated for a very >> long time and that it wasn't recommended for security reasons. >> > >I have a Ben Nanonote that I run Debian on without any issues. I also >know that LibreCMC [0] will run on the Nanonote. > >If your intention with running Parabola on the Nanonote is a >completely free computing environment, then LibreCMC will satisfy that >requirement. LibreCMC is even endorsed by the Free Software Foundation >as a Free GNU/Linux distro. > >[0] http://librecmc.org > >-zach -- Binh-Khoi NGUYEN khoi at member.fsf.org b.nguyen12 at imperial.ac.uk GPG Key: https://bknguyen.be/gpg.html From lukeshu at sbcglobal.net Tue Jan 27 17:58:06 2015 From: lukeshu at sbcglobal.net (Luke Shumaker) Date: Tue, 27 Jan 2015 12:58:06 -0500 Subject: [Assist] Parabola on Ben Nanonote? In-Reply-To: <20150127121042.GA17011@libreboot.home> References: <20150127121042.GA17011@libreboot.home> Message-ID: <87y4oo5cnl.wl-lukeshu@sbcglobal.net> At Tue, 27 Jan 2015 12:10:42 +0000, Binh-Khoi Nguyen wrote: > Hey, > > I was wondering if anyone had a Ben Nanonote and if it's possible to > install Parabola on it. The Nanonote is MIPS32; Parabola formerly had support for MIPS64 little endian, but we don't even support that anymore (though the repos are still there, should anyone be interested). > The people at LibreWRT told me that LibreWRT hadn't been updated for a > very long time and that it wasn't recommended for security reasons. As Zach noted, libreCMC supports the Nanonote. libreCMC is roughly the same project as LibreWRT, but different people. Politics! Both are based on OpenWRT, and are both FSF-endorsed. -- Happy hacking, ~ Luke Shumaker From elcorreo at deshackra.com Tue Jan 27 19:25:51 2015 From: elcorreo at deshackra.com (Jorge Araya Navarro) Date: Tue, 27 Jan 2015 13:25:51 -0600 Subject: [Assist] Parabola on Ben Nanonote? In-Reply-To: <87y4oo5cnl.wl-lukeshu@sbcglobal.net> References: <20150127121042.GA17011@libreboot.home> <87y4oo5cnl.wl-lukeshu@sbcglobal.net> Message-ID: <8761bs9gao.fsf@abril.charola> Interesting, running an operating system inside a router would allow me to block pornographic websites or do a fine grain filtering by keywords, with the correct software, right? Luke Shumaker writes: > At Tue, 27 Jan 2015 12:10:42 +0000, > Binh-Khoi Nguyen wrote: >> Hey, >> >> I was wondering if anyone had a Ben Nanonote and if it's possible to >> install Parabola on it. > > The Nanonote is MIPS32; Parabola formerly had support for MIPS64 > little endian, but we don't even support that anymore (though the > repos are still there, should anyone be interested). > >> The people at LibreWRT told me that LibreWRT hadn't been updated for a >> very long time and that it wasn't recommended for security reasons. > > As Zach noted, libreCMC supports the Nanonote. libreCMC is roughly > the same project as LibreWRT, but different people. Politics! Both > are based on OpenWRT, and are both FSF-endorsed. -- Pax et bonum. Jorge Araya Navarro. ES: Dise?ador Publicitario, Programador Python y colaborador en Parabola GNU/Linux-libre EN: Ads Designer, Python programmer and contributor Parabola GNU/Linux-libre EO: Anonco grafikisto, Pitino programalingvo programisto kai kontribuanto en Parabola GNU/Linux-libre https://es.gravatar.com/shackra From khoi at bknguyen.be Sat Jan 31 14:50:17 2015 From: khoi at bknguyen.be (Binh-Khoi Nguyen) Date: Sat, 31 Jan 2015 14:50:17 +0000 Subject: [Assist] Parabola on Ben Nanonote? In-Reply-To: References: <20150127121042.GA17011@libreboot.home> Message-ID: <20150131145016.GD13937@libreboot> Hi! Thanks for your reply! I don't know how to port Parabola but I'm willing to learn! I was thinking that I wanted to try to start contributing a bit but didn't know where to start. Is there something that I could read about it? Khoi On Tue, Jan 27, 2015 at 03:55:32PM +0000, ingegnue wrote: > > >On January 27, 2015 7:10:42 AM EST, Binh-Khoi Nguyen wrote: >>Hey, >> >>I was wondering if anyone had a Ben Nanonote and if it's possible to >>install Parabola on it. >> >>The people at LibreWRT told me that LibreWRT hadn't been updated for a >>very long time and that it wasn't recommended for security reasons. >> >>Thanks for your help, > >A look at the specs says the Nanonote's CPU has an Ingenic XBurst Jz4720?which is compatible with MIPS32, according to the Ingenic wiki. Parabola has support for MIPS64, but not MIPS32 unfortunately. I don't know too much about MIPS but give it a try and it doesn't work, perhaps you can make a port? Some folks have been working on an ARM port so it is probably doable. Supporting the Nanonote seems like a cool idea to me... > >_______________________________________________ >Assist mailing list >Assist at lists.parabola.nu >https://lists.parabola.nu/mailman/listinfo/assist -- Binh-Khoi NGUYEN khoi at member.fsf.org b.nguyen12 at imperial.ac.uk GPG Key: https://bknguyen.be/gpg.html