From bill-auger at peers.community Mon Apr 1 07:35:11 2019 From: bill-auger at peers.community (bill-auger) Date: Mon, 1 Apr 2019 03:35:11 -0400 Subject: [Dev] Chromebook C201 wifi In-Reply-To: <20190331194344.2f624d3c@primarylaptop> References: <6aa28e071643ef84863ede5361e220748b6cad0a.camel@disroot.org> <20190330225834.68be9c84@parabola> <9634d6d89ea9d36dc804b1a9a9b423bdc46ae4ed.camel@disroot.org> <20190331111423.GA10608@parabola-pocket.localdomain> <20190331194344.2f624d3c@primarylaptop> Message-ID: <20190401033511.3100e09a@parabola> On Sun, 31 Mar 2019 19:43:44 +0200 Denis wrote: > What about the following: > > Parabola is looking for testers for the librebooted Asus Chromebook the thing is, that these are periodic and timely news posts, (aka. RSS feeds) - they are not intended for future reference nor to be updated like wiki articles - also, they already had been relayed by any number of other downstream news sites such as planet-gnu when they were fresh news; but their time of relevance has long expired t is unfortunate if the original article over-sold itself or promised too much; but that should just be a lesson learned to be more conservative as to what goes int them - i would suggest posting a fresh news article instead From bill-auger at peers.community Mon Apr 1 07:35:38 2019 From: bill-auger at peers.community (bill-auger) Date: Mon, 1 Apr 2019 03:35:38 -0400 Subject: [Dev] Chromebook C201 wifi In-Reply-To: <20190331195239.60157ddb@primarylaptop> References: <6aa28e071643ef84863ede5361e220748b6cad0a.camel@disroot.org> <20190330225834.68be9c84@parabola> <9634d6d89ea9d36dc804b1a9a9b423bdc46ae4ed.camel@disroot.org> <20190331111423.GA10608@parabola-pocket.localdomain> <20190331195239.60157ddb@primarylaptop> Message-ID: <20190401033538.6aa6191c@parabola> On Sun, 31 Mar 2019 19:52:39 +0200 Denis wrote: i think a consolidated hardware advice page is a good idea - there is already a wiki category ([[Category:Hardware]]) that could be expanded[1] - there is also already a wiki page for listing specific coputer models that are known to be compatible, though it also needs expanding[2] - there is also a wiki page about wifi cards[3], and several about graphics cards[4][5][6] categorized as ([[Category: Graphics]])[7] [1]: https://wiki.parabola.nu/Category:Hardware [2]: https://wiki.parabola.nu/List_of_hardware_support [3]: https://wiki.parabola.nu/WiFi_devices_known_to_work_with_Parabola_GNU/Linux-libre [4]: https://wiki.parabola.nu/Nouveau [5]: https://wiki.parabola.nu/ATI [6]: https://wiki.parabola.nu/Intel [7]: https://wiki.parabola.nu/Category:Graphics so it would just be a matter of making a top-level hardware overview advice particle, consolidating access to the existing articles, and then updating and expanding on those in place On Sun, 31 Mar 2019 19:52:39 +0200 Denis wrote: > Some time ago, I also started working on a Libreboot compatible laptop > comparison[1] to help advanced users chose the laptops that best suit > them, FWIW, id say that libreboot constraint is over-shooting the "sweet-spot" somewhat - the set of machines that can boot libreboot is pitifully small - it would be more helpful to broaden the scope to all portable computers that can run parabola-out-of-the-box, perhaps with a special section for those that can also boot free boot-ware; but not to pretend that this is not already a catalog of legacy - looking forward, it would be best to point out that, as the new culture of libre-design hardware gains in popularity, such as those surrounding ARM, RISC-V, and POWER9, that will tend toward more libre-design peripherals being invented - that is most likely where the brightest outlook on the future of mobile libre computing is to be found From leestrobel at disroot.org Mon Apr 1 14:01:16 2019 From: leestrobel at disroot.org (Lee Strobel) Date: Mon, 01 Apr 2019 10:01:16 -0400 Subject: [Dev] Chromebook C201 wifi In-Reply-To: <777638e6-0a26-2836-f37f-05ee2ea037d5@gmail.com> References: <6aa28e071643ef84863ede5361e220748b6cad0a.camel@disroot.org> <20190331174840.09de6a96@primarylaptop> <777638e6-0a26-2836-f37f-05ee2ea037d5@gmail.com> Message-ID: <58028a8cd8928ea3a5baaa365520dd1896aa11dc.camel@disroot.org> Thanks for your input Josh, that is interesting. I had a look at the bootloader options, but couldn't see anything that looked like it would affect the power going to the USB ports. I had another read of the ThinkPenguin page ( https://www.thinkpenguin.com/gnu-linux/penguin-wireless-n-usb-adapter-gnu-linux-tpe-n150usb ) about their wifi dongle in more detail, and under 'Power Consumption', the highest it lists is 310 mA. This is quite a lot lower than the 500mA that a USB 2.0 port is supposed to provide - would the available power really be only 60% of the standard? I also found this page for the ath9k_htc_firmware: https://github.com/qca/open-ath9k-htc-firmware/wiki/usb-related-issues#start-of-content . Under 'USB related issues', it mentions stability issues, so it seems there are some issues the devs are aware of. It mentions about powered USB hubs, saying that people have had issues with specific USB controllers. I will also attach a printout of my dmesg for when I plugged the dongle in, tried to connect (causing the system freeze) and then unplugged it. I'm not sure if it sheds much light on the situation, but some of the errors look similar to what they are talking about on that Atheros firmware page. Regards, Lee On Sun, 2019-03-31 at 21:24 +0100, Josh Branning wrote: > This is interesting, a while back I tried plugging in an external HDD > to > an olinuxino (ARM) using parabola, and it didn't get enough power > either. At that point, I assumed it was because the board wasn't > providing the right power through the USB. I was using a power pack > that > matched the recommended input voltage and current of the board. > > Possibly a different thing entirely, but you never know ... there > could > be some setting in the kernel or bootloader or something that means > the > devices are only getting limited power through the USBs. > > Another way to test if it is a parabola issue, could be to burn a > live > CD or make a usb of a different distro, and see if the adapter works > with that, though if it is solely a bootloader issue, I guess that > wouldn't be much help less a alternate one is also supplied. It is > something I didn't do, because I assumed it would have probably been > the > hardware simply being not able to supply required the power. > > Note that on some other less-free similar dev boards, USB hdds > worked, > albeit with a different distro. I know fosho that on some of these > boards there is a bootloader setting where you can adjust the output > current/voltage, so there may be one in u-boot too. > > Cheers, > > Josh > > -------------- next part -------------- NetworkManager is disabled, this is trying to set up wifi connection manually, using wpa_supplicant: Atheros wifi USB is plugged in (no sign of any problems): [ 60.808087] usb 2-1: new high-speed USB device number 2 using dwc2 [ 61.032485] usb 2-1: New USB device found, idVendor=0cf3, idProduct=9271, bcdDevice= 1.08 [ 61.032564] usb 2-1: New USB device strings: Mfr=16, Product=32, SerialNumber=48 [ 61.032632] usb 2-1: Product: UB93 [ 61.032667] usb 2-1: Manufacturer: ATHEROS [ 61.032707] usb 2-1: SerialNumber: 12345 [ 61.060437] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 61.071605] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 61.109932] usb 2-1: ath9k_htc: Firmware ath9k_htc/htc_9271-1.4.0.fw requested [ 61.110280] usbcore: registered new interface driver ath9k_htc [ 61.389274] usb 2-1: ath9k_htc: Transferred FW: ath9k_htc/htc_9271-1.4.0.fw, size: 51008 [ 61.640980] ath9k_htc 2-1:1.0: ath9k_htc: HTC initialized with 33 credits [ 61.904852] ath9k_htc 2-1:1.0: ath9k_htc: FW Version: 1.4 [ 61.904909] ath9k_htc 2-1:1.0: FW RMW support: On [ 61.904955] ath: EEPROM regdomain: 0x65 [ 61.904957] ath: EEPROM indicates we should expect a direct regpair map [ 61.904963] ath: Country alpha2 being used: 00 [ 61.904964] ath: Regpair used: 0x65 [ 61.930629] ieee80211 phy0: Atheros AR9271 Rev:1 Here, the connection is started and system hangs shortly afterwards: [ 693.696726] wlan0: authenticate with 48:5d:36:d0:27:ae [ 693.955494] wlan0: send auth to 48:5d:36:d0:27:ae (try 1/3) [ 693.959246] wlan0: authenticated [ 693.964085] wlan0: associate with 48:5d:36:d0:27:ae (try 1/3) [ 693.969608] wlan0: RX AssocResp from 48:5d:36:d0:27:ae (capab=0x1431 status=0 aid=3) [ 693.980037] wlan0: associated [ 693.982330] ath: EEPROM regdomain: 0x8348 [ 693.982333] ath: EEPROM indicates we should expect a country code [ 693.982335] ath: doing EEPROM country->regdmn map search [ 693.982337] ath: country maps to regdmn code: 0x3a [ 693.982340] ath: Country alpha2 being used: US [ 693.982342] ath: Regpair used: 0x3a [ 693.982344] ath: regdomain 0x8348 dynamically updated by country element [ 693.984668] dwc2 ff580000.usb: dwc2_hc_chhltd_intr_dma: Channel 8 - ChHltd set, but reason is unknown [ 693.986683] dwc2 ff580000.usb: hcint 0x00000002, intsts 0x06400029 [ 693.992800] dwc2 ff580000.usb: dwc2_hc_chhltd_intr_dma: Channel 4 - ChHltd set, but reason is unknown [ 693.994811] dwc2 ff580000.usb: hcint 0x00000002, intsts 0x06600029 [ 694.080386] dwc2 ff580000.usb: dwc2_hc_chhltd_intr_dma: Channel 2 - ChHltd set, but reason is unknown [ 694.082394] dwc2 ff580000.usb: hcint 0x00000002, intsts 0x06600029 [ 694.182778] dwc2 ff580000.usb: dwc2_hc_chhltd_intr_dma: Channel 0 - ChHltd set, but reason is unknown [ 694.184795] dwc2 ff580000.usb: hcint 0x00000002, intsts 0x06600029 [ 694.285179] dwc2 ff580000.usb: dwc2_hc_chhltd_intr_dma: Channel 1 - ChHltd set, but reason is unknown [ 694.287192] dwc2 ff580000.usb: hcint 0x00000002, intsts 0x06600029 [ 694.387564] dwc2 ff580000.usb: dwc2_hc_chhltd_intr_dma: Channel 6 - ChHltd set, but reason is unknown [ 694.389633] dwc2 ff580000.usb: hcint 0x00000002, intsts 0x06600029 [ 694.489968] dwc2 ff580000.usb: dwc2_hc_chhltd_intr_dma: Channel 5 - ChHltd set, but reason is unknown [ 694.492078] dwc2 ff580000.usb: hcint 0x00000002, intsts 0x06600029 [ 694.592358] dwc2 ff580000.usb: dwc2_hc_chhltd_intr_dma: Channel 7 - ChHltd set, but reason is unknown [ 694.594529] dwc2 ff580000.usb: hcint 0x00000002, intsts 0x06600029 [ 694.694771] dwc2 ff580000.usb: dwc2_hc_chhltd_intr_dma: Channel 2 - ChHltd set, but reason is unknown [ 694.696892] dwc2 ff580000.usb: hcint 0x00000002, intsts 0x06600029 [ 694.797151] dwc2 ff580000.usb: dwc2_hc_chhltd_intr_dma: Channel 1 - ChHltd set, but reason is unknown [ 694.799144] dwc2 ff580000.usb: hcint 0x00000002, intsts 0x06600029 [ 694.899552] dwc2 ff580000.usb: dwc2_hc_chhltd_intr_dma: Channel 6 - ChHltd set, but reason is unknown [ 694.901505] dwc2 ff580000.usb: hcint 0x00000002, intsts 0x06600029 [ 694.992911] dwc2 ff580000.usb: dwc2_hc_chhltd_intr_dma: Channel 1 - ChHltd set, but reason is unknown [ 694.995015] dwc2 ff580000.usb: hcint 0x00000002, intsts 0x06600029 [ 695.001969] dwc2 ff580000.usb: dwc2_hc_chhltd_intr_dma: Channel 4 - ChHltd set, but reason is unknown [ 695.004105] dwc2 ff580000.usb: hcint 0x00000002, intsts 0x06600029 [ 695.104371] dwc2 ff580000.usb: dwc2_hc_chhltd_intr_dma: Channel 5 - ChHltd set, but reason is unknown [ 695.106498] dwc2 ff580000.usb: hcint 0x00000002, intsts 0x06600029 [ 695.206755] dwc2 ff580000.usb: dwc2_hc_chhltd_intr_dma: Channel 0 - ChHltd set, but reason is unknown [ 695.208952] dwc2 ff580000.usb: hcint 0x00000002, intsts 0x06600029 [ 703.983547] wlan0: deauthenticating from 48:5d:36:d0:27:ae by local choice (Reason: 3=DEAUTH_LEAVING) [ 706.820083] ath: phy0: Unable to remove station entry for: 48:5d:36:d0:27:ae Whun I unplug the USB device. Here the system unfreezes and everything works normally again: [ 841.392140] usb 2-1: USB disconnect, device number 2 [ 841.425692] ath: phy0: Failed to wakeup in 500us [ 841.438006] ath: phy0: Failed to wakeup in 500us [ 841.504269] usb 2-1: ath9k_htc: USB layer deinitialized From lovell.joshyyy at gmail.com Mon Apr 1 15:51:47 2019 From: lovell.joshyyy at gmail.com (Josh Branning) Date: Mon, 1 Apr 2019 16:51:47 +0100 Subject: [Dev] Chromebook C201 wifi In-Reply-To: <777638e6-0a26-2836-f37f-05ee2ea037d5@gmail.com> References: <6aa28e071643ef84863ede5361e220748b6cad0a.camel@disroot.org> <20190331174840.09de6a96@primarylaptop> <777638e6-0a26-2836-f37f-05ee2ea037d5@gmail.com> Message-ID: <9baff2f3-5fb0-6c31-95ad-77d84e43960e@gmail.com> Hi just had a look and there doesn't appear to be an easy option, though there are a few things that could help in u-boot by the looks of things, I'm not too familiar with u-boot, and it would require probably require someone who would know what they were doing to really help. But I guess probably you'd need to compile u-boot, changing some stuff, like grepping for "uA", "uV", "max-current" , "max-current" etc. have a look at arch/arm/dts and see what's going in there etc. Probably there is a main voltage regulator and a usb voltage regulator, someone who knows about electronics could tell you if it could be a problem with either, or just one or the other. You could try typing "power info" from the prompt or something similar, which may or may not show you usb current. Else, like you or someone suggested, obtain a usb current and voltage meter and work out if that's the issue for sure. U-boot seems to be very board-specific which generally provides some evidence against my original hypothesis, though it's difficult to tell. Bare in mind, it could be a coincidence that both our arm devices are struggling with USB and turn out not be power related at all, cheers, Josh On 31/03/19 21:24, Josh Branning wrote: > This is interesting, a while back I tried plugging in an external HDD to > an olinuxino (ARM) using parabola, and it didn't get enough power > either. At that point, I assumed it was because the board wasn't > providing the right power through the USB. I was using a power pack that > matched the recommended input voltage and current of the board. > > Possibly a different thing entirely, but you never know ... there could > be some setting in the kernel or bootloader or something that means the > devices are only getting limited power through the USBs. > > Another way to test if it is a parabola issue, could be to burn a live > CD or make a usb of a different distro, and see if the adapter works > with that, though if it is solely a bootloader issue, I guess that > wouldn't be much help less a alternate one is also supplied. It is > something I didn't do, because I assumed it would have probably been the > hardware simply being not able to supply required the power. > > Note that on some other less-free similar dev boards, USB hdds worked, > albeit with a different distro. I know fosho that on some of these > boards there is a bootloader setting where you can adjust the output > current/voltage, so there may be one in u-boot too. > > Cheers, > > Josh > > On 31/03/19 20:43, Lee Strobel wrote: >> lsusb for the Senao EUB9801 says its max power is 450mA, so only 50mA >> less than the Atheros. However, I suspect those are just numbers >> someone's typed in a text file somewhere. They might not actually be >> drawing those currents. >> >> It looks like a USB tester can be purchased online for $10. For that >> money, I might just buy one and actually measure the current draw. >> >> Btw, from what I saw on Wikipedia, it looks like a standard usb 2.0 >> port should be able to supply 500mA as standard. >> >> Lee >> >> >> On Sun, 2019-03-31 at 14:04 -0400, Lee Strobel wrote: >>> Hi Denis, >>> >>>> For the record, the WiFi related bugreport is here: >>>> https://labs.parabola.nu/issues/2261 >>>> >>>> Could you try to see if a USB HUB that is powered by its own power >>>> supply makes it usable. If you don't have one you may know people >>>> that >>>> have one and borrow it just for doing a quick test. >>>> >>> >>> I will see what I can do. I can't think of anyone I know off-hand who >>> would have an externally-powered USB hub, but I will ask around. >>> >>> About the power thing: I actually have an older USB wifi dongle, a >>> 'Senao EUB9801', which seems to work great when plugged directly into >>> the Chromebook (if I use the firmware blob). According to the kernel >>> boot log, I think it is running on a Ralink chip of some kind. I will >>> try to investigate, as you suggested, and see if it requires less >>> power >>> than the ThinkPenguin dongle. It is older (~8-10 years), so maybe it >>> is >>> using an older wifi technology that consumes less power? >>> >>> The reason I asked about the kernel devs is just because I was >>> wondering if the team that maintains the module for the Atheros chip >>> are aware of the issue. I would think we might need their assistance, >>> if any of us wanted to try to modify the module. >>> >>> Lee >>> >>> _______________________________________________ >>> Dev mailing list >>> Dev at lists.parabola.nu >>> https://lists.parabola.nu/mailman/listinfo/dev >> >> _______________________________________________ >> Dev mailing list >> Dev at lists.parabola.nu >> https://lists.parabola.nu/mailman/listinfo/dev >> > From leestrobel at disroot.org Tue Apr 2 10:23:06 2019 From: leestrobel at disroot.org (Lee Strobel) Date: Tue, 02 Apr 2019 06:23:06 -0400 Subject: [Dev] Chromebook C201 wifi In-Reply-To: <9baff2f3-5fb0-6c31-95ad-77d84e43960e@gmail.com> References: <6aa28e071643ef84863ede5361e220748b6cad0a.camel@disroot.org> <20190331174840.09de6a96@primarylaptop> <777638e6-0a26-2836-f37f-05ee2ea037d5@gmail.com> <9baff2f3-5fb0-6c31-95ad-77d84e43960e@gmail.com> Message-ID: <02689e83b782bf838774b726fad49b158d5911b7.camel@disroot.org> Hi Josh, I've got the $10 USB tester on order, should arrive in a few days. Once I have that, hopefully I will be able to confirm whether or not the power level is really the problem. I will compare the ThinkPenguin dongle to the older Ralink one I have. Also, the tester I've ordered has two split outputs (from the same port on the laptop). So I should be able to plug in the wifi dongle; check the current draw for that; then plug something else into the second port on the tester (mouse, or phone charger or something). I should be able to tell, based on whether the current increases when I do that, whether or not the Penguin dongle is maxing out the available supply. Regards, Lee On Mon, 2019-04-01 at 16:51 +0100, Josh Branning wrote: > Hi just had a look and there doesn't appear to be an easy option, > though > there are a few things that could help in u-boot by the looks of > things, > I'm not too familiar with u-boot, and it would require probably > require > someone who would know what they were doing to really help. > > But I guess probably you'd need to compile u-boot, changing some > stuff, > like grepping for "uA", "uV", "max-current" , "max-current" etc. have > a > look at arch/arm/dts and see what's going in there etc. Probably > there > is a main voltage regulator and a usb voltage regulator, someone who > knows about electronics could tell you if it could be a problem with > either, or just one or the other. > > You could try typing "power info" from the prompt or something > similar, > which may or may not show you usb current. Else, like you or someone > suggested, obtain a usb current and voltage meter and work out if > that's > the issue for sure. > > U-boot seems to be very board-specific which generally provides some > evidence against my original hypothesis, though it's difficult to > tell. > Bare in mind, it could be a coincidence that both our arm devices > are > struggling with USB and turn out not be power related at all, cheers, > > Josh > > On 31/03/19 21:24, Josh Branning wrote: > > This is interesting, a while back I tried plugging in an external > > HDD to > > an olinuxino (ARM) using parabola, and it didn't get enough power > > either. At that point, I assumed it was because the board wasn't > > providing the right power through the USB. I was using a power pack > > that > > matched the recommended input voltage and current of the board. > > > > Possibly a different thing entirely, but you never know ... there > > could > > be some setting in the kernel or bootloader or something that means > > the > > devices are only getting limited power through the USBs. > > > > Another way to test if it is a parabola issue, could be to burn a > > live > > CD or make a usb of a different distro, and see if the adapter > > works > > with that, though if it is solely a bootloader issue, I guess that > > wouldn't be much help less a alternate one is also supplied. It is > > something I didn't do, because I assumed it would have probably > > been the > > hardware simply being not able to supply required the power. > > > > Note that on some other less-free similar dev boards, USB hdds > > worked, > > albeit with a different distro. I know fosho that on some of these > > boards there is a bootloader setting where you can adjust the > > output > > current/voltage, so there may be one in u-boot too. > > > > Cheers, > > > > Josh > > > > On 31/03/19 20:43, Lee Strobel wrote: > > > lsusb for the Senao EUB9801 says its max power is 450mA, so only > > > 50mA > > > less than the Atheros. However, I suspect those are just numbers > > > someone's typed in a text file somewhere. They might not actually > > > be > > > drawing those currents. > > > > > > It looks like a USB tester can be purchased online for $10. For > > > that > > > money, I might just buy one and actually measure the current > > > draw. > > > > > > Btw, from what I saw on Wikipedia, it looks like a standard usb > > > 2.0 > > > port should be able to supply 500mA as standard. > > > > > > Lee > > > > > > > > > On Sun, 2019-03-31 at 14:04 -0400, Lee Strobel wrote: > > > > Hi Denis, > > > > > > > > > For the record, the WiFi related bugreport is here: > > > > > https://labs.parabola.nu/issues/2261 > > > > > > > > > > Could you try to see if a USB HUB that is powered by its own > > > > > power > > > > > supply makes it usable. If you don't have one you may know > > > > > people > > > > > that > > > > > have one and borrow it just for doing a quick test. > > > > > > > > > > > > > I will see what I can do. I can't think of anyone I know off- > > > > hand who > > > > would have an externally-powered USB hub, but I will ask > > > > around. > > > > > > > > About the power thing: I actually have an older USB wifi > > > > dongle, a > > > > 'Senao EUB9801', which seems to work great when plugged > > > > directly into > > > > the Chromebook (if I use the firmware blob). According to the > > > > kernel > > > > boot log, I think it is running on a Ralink chip of some kind. > > > > I will > > > > try to investigate, as you suggested, and see if it requires > > > > less > > > > power > > > > than the ThinkPenguin dongle. It is older (~8-10 years), so > > > > maybe it > > > > is > > > > using an older wifi technology that consumes less power? > > > > > > > > The reason I asked about the kernel devs is just because I was > > > > wondering if the team that maintains the module for the Atheros > > > > chip > > > > are aware of the issue. I would think we might need their > > > > assistance, > > > > if any of us wanted to try to modify the module. > > > > > > > > Lee > > > > > > > > _______________________________________________ > > > > Dev mailing list > > > > Dev at lists.parabola.nu > > > > https://lists.parabola.nu/mailman/listinfo/dev > > > > > > _______________________________________________ > > > Dev mailing list > > > Dev at lists.parabola.nu > > > https://lists.parabola.nu/mailman/listinfo/dev > > > > > _______________________________________________ > Dev mailing list > Dev at lists.parabola.nu > https://lists.parabola.nu/mailman/listinfo/dev From GNUtoo at cyberdimension.org Tue Apr 2 13:08:57 2019 From: GNUtoo at cyberdimension.org (Denis 'GNUtoo' Carikli) Date: Tue, 2 Apr 2019 15:08:57 +0200 Subject: [Dev] Chromebook C201 wifi In-Reply-To: <9baff2f3-5fb0-6c31-95ad-77d84e43960e@gmail.com> References: <6aa28e071643ef84863ede5361e220748b6cad0a.camel@disroot.org> <20190331174840.09de6a96@primarylaptop> <777638e6-0a26-2836-f37f-05ee2ea037d5@gmail.com> <9baff2f3-5fb0-6c31-95ad-77d84e43960e@gmail.com> Message-ID: <20190402150857.19427186@primarylaptop> On Mon, 1 Apr 2019 16:51:47 +0100 Josh Branning wrote: > Hi just had a look and there doesn't appear to be an easy option, > though there are a few things that could help in u-boot by the looks > of things, I'm not too familiar with u-boot, and it would require > probably require someone who would know what they were doing to > really help. > > But I guess probably you'd need to compile u-boot, changing some > stuff, like grepping for "uA", "uV", "max-current" , "max-current" > etc. have a look at arch/arm/dts and see what's going in there etc. > Probably there is a main voltage regulator and a usb voltage > regulator, someone who knows about electronics could tell you if it > could be a problem with either, or just one or the other. The best way to do that is to try to understand which chips are involved in the power management in that chromebook and try to find documentation on it. - Start by looking at the devicetree of the device, as it describes the hardware that cannot be automatically detected. - Then try to find some documentation on the chips involved in the USB voltage. Documentation can be found: - in the datasheet/reference manual of the respective chips if they are available online. - In Linux/u-boot/coreboot/depthcharge/chrome-ec Documentation or source code Also when grepping you could look for the following: - vbus: it's the USB 5v - buck boost converter: it's a kind of voltage regulator that raises the voltage for instance from 3.3v to 5V. As I understand the C201 uses the following free software projects: - The EC source code is free software, so some information might also be in chrome-ec[1]. - It also uses Coreboot, but I don't know which payload u-boot chose to use. It's probably depthcharge according to the kernel install script, so it might also be interesting to look into that. References: ----------- [1]https://review.coreboot.org/chrome-ec.git Denis. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From nobody at parabola.nu Wed Apr 3 17:23:17 2019 From: nobody at parabola.nu (Parabola Website Notification) Date: Wed, 03 Apr 2019 17:23:17 -0000 Subject: [Dev] Orphan Libre package [linux-libre] marked out-of-date Message-ID: <20190403172317.31533.59566@winston.parabola.nu> riku.viitanen0 at gmail.com wants to notify you that the following packages may be out-of-date: * linux-libre 5.0.5_gnu-1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/linux-libre/ * linux-libre 5.0.5_gnu-1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/linux-libre/ * linux-libre 5.0.5_gnu-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/linux-libre/ * linux-libre-chromebook 5.0.5_gnu-1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/linux-libre-chromebook/ * linux-libre-docs 5.0.5_gnu-1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/linux-libre-docs/ * linux-libre-docs 5.0.5_gnu-1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/linux-libre-docs/ * linux-libre-docs 5.0.5_gnu-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/linux-libre-docs/ * linux-libre-headers 5.0.5_gnu-1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/linux-libre-headers/ * linux-libre-headers 5.0.5_gnu-1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/linux-libre-headers/ * linux-libre-headers 5.0.5_gnu-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/linux-libre-headers/ The user provided the following additional text: 5.0.6 is available. From leestrobel at disroot.org Fri Apr 5 00:27:28 2019 From: leestrobel at disroot.org (Lee Strobel) Date: Thu, 04 Apr 2019 20:27:28 -0400 Subject: [Dev] Chromebook C201 wifi In-Reply-To: <20190402150857.19427186@primarylaptop> References: <6aa28e071643ef84863ede5361e220748b6cad0a.camel@disroot.org> <20190331174840.09de6a96@primarylaptop> <777638e6-0a26-2836-f37f-05ee2ea037d5@gmail.com> <9baff2f3-5fb0-6c31-95ad-77d84e43960e@gmail.com> <20190402150857.19427186@primarylaptop> Message-ID: Hey, so I received that USB tester in the mail today. Got some interesting results: First, I tried the older Ralink wifi dongle (the one that works). When connected, it seems to operate at around 110-120mA. Very rarely it went up to around 160. So, that is quite a bit lower than the 450mA max power that was reported by 'lsusb'. I then unplugged that and plugged in my phone charger. That was able to draw around 500mA (which is the spec for a USB 2.0 port). I then tried the ThinkPenguin Atheros dongle. It was at about 70mA when connected, but experienced the same freezing issue as when plugged directly in to the Chromebook port. I tried it in my desktop and it works fine on that, both direct and going through the USB tester. No sign of the freezing issue. On the desktop, I think the max current I saw was around 90mA. So, clearly the issue is not a power limitation, as the Chromebook port can deliver the full 500mA. My best guess is that it is some sort of compatibilty bug between the dongle and the particular USB hub that the Chromebook uses. Regards, Lee On Tue, 2019-04-02 at 15:08 +0200, Denis 'GNUtoo' Carikli wrote: > On Mon, 1 Apr 2019 16:51:47 +0100 > Josh Branning wrote: > > > Hi just had a look and there doesn't appear to be an easy option, > > though there are a few things that could help in u-boot by the > > looks > > of things, I'm not too familiar with u-boot, and it would require > > probably require someone who would know what they were doing to > > really help. > > > > But I guess probably you'd need to compile u-boot, changing some > > stuff, like grepping for "uA", "uV", "max-current" , "max-current" > > etc. have a look at arch/arm/dts and see what's going in there etc. > > Probably there is a main voltage regulator and a usb voltage > > regulator, someone who knows about electronics could tell you if it > > could be a problem with either, or just one or the other. > > The best way to do that is to try to understand which chips are > involved in the power management in that chromebook and try to find > documentation on it. > - Start by looking at the devicetree of the device, as it describes > the > hardware that cannot be automatically detected. > - Then try to find some documentation on the chips involved in the > USB > voltage. Documentation can be found: > - in the datasheet/reference manual of the respective chips if they > are available online. > - In Linux/u-boot/coreboot/depthcharge/chrome-ec Documentation or > source code > > Also when grepping you could look for the following: > - vbus: it's the USB 5v > - buck boost converter: it's a kind of voltage regulator that raises > the voltage for instance from 3.3v to 5V. > > As I understand the C201 uses the following free software projects: > - The EC source code is free software, so some information > might also be in chrome-ec[1]. > - It also uses Coreboot, but I don't know which payload u-boot chose > to > use. It's probably depthcharge according to the kernel install > script, so it might also be interesting to look into that. > > References: > ----------- > [1]https://review.coreboot.org/chrome-ec.git > > Denis. > _______________________________________________ > Dev mailing list > Dev at lists.parabola.nu > https://lists.parabola.nu/mailman/listinfo/dev From nobody at parabola.nu Tue Apr 9 09:26:06 2019 From: nobody at parabola.nu (Parabola Website Notification) Date: Tue, 09 Apr 2019 09:26:06 -0000 Subject: [Dev] Orphan Libre package [linux-libre] marked out-of-date Message-ID: <20190409092606.20349.9453@winston.parabola.nu> riku.viitanen0 at gmail.com wants to notify you that the following packages may be out-of-date: * linux-libre 5.0.6_gnu-1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/linux-libre/ * linux-libre 5.0.6_gnu-1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/linux-libre/ * linux-libre 5.0.6_gnu-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/linux-libre/ * linux-libre-chromebook 5.0.6_gnu-1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/linux-libre-chromebook/ * linux-libre-docs 5.0.6_gnu-1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/linux-libre-docs/ * linux-libre-docs 5.0.6_gnu-1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/linux-libre-docs/ * linux-libre-docs 5.0.6_gnu-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/linux-libre-docs/ * linux-libre-headers 5.0.6_gnu-1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/linux-libre-headers/ * linux-libre-headers 5.0.6_gnu-1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/linux-libre-headers/ * linux-libre-headers 5.0.6_gnu-1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/linux-libre-headers/ The user provided the following additional text: 5.0.7 is available. From lukeshu at lukeshu.com Wed Apr 10 20:45:19 2019 From: lukeshu at lukeshu.com (Luke Shumaker) Date: Wed, 10 Apr 2019 16:45:19 -0400 Subject: [Dev] Planned beefcake outage Message-ID: <87imvlio80.wl-lukeshu@lukeshu.com> Hi all, Beefcake will be down for several days starting Saturday (13th) night/Sunday (14th) morning (EDT), as I physcially move it 900 miles east. I don't know how long it will take to get Internet set up at the new location. I appologize for the inconvenience. -- Happy hacking, ~ Luke Shumaker From theova at bluewin.ch Sun Apr 7 09:59:16 2019 From: theova at bluewin.ch (theova) Date: Sun, 7 Apr 2019 11:59:16 +0200 Subject: [Dev] Patch for qutebrowser update 1.6.1 Message-ID: <20190407095916.sonhoijpbwsni6hl@RainbowWarrior.localdomain> Hi! The orphaned package "qutebrowser" is out of date. Version 1.6.1 is released. You can find the patch for upgrading as an attachment. (It was straight forward: new pkgver, new sha256sums.) If you would like me to maintain this package, I would try to maintain it, although I'm not an experienced packager. Best regards and thanks for your work, Theova -------------- next part -------------- ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQC0t4nwTB5M+IWY6KpwlquoqWGsgVhL6N/rewyXcwVS1+/tf49l3TF0kOI7WinXaJBKXpdOMgsgfeq/Xp6W82X83hXoEF7mgg7QEhT9ZxYdTojHEeeOCqXkbYbfXNE+6SqBtBubPuJqbL+RYBoa1qPmrJLyH9HPeR0c+3P+1brepVMgxdIxhmNuYzAVkuJd5W835C2lZU8C6ReNHC3pVxu2svsbggdbScIpU7e/6vE1poRMetRasU6fHdrq1MPjLbj4Ar12vtq5AOE3jRtdmXGlpAAYuFDzHkJ0RKMC7NkXVBxL02Og5neDeyjDbRXyJOQSCzgesXMoKGJpZOdMNPBX theo at RainbowWarrior -------------- next part -------------- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEmebv4QLCFsrMoA8HYV3Rx08rMJEFAlypyIYACgkQYV3Rx08r MJFxfQ/+NmLz9615C6L0LHYuavvAUbvZJFf/JN+O2ixsCcSrSlj7Q1KZiNlzzvJf hP9dct4Q1fLGE3Jf3r/h9jUXWzKvgtbk6jV+arRnGkZrDrlAWTJ4wFfl5cqc+clu jsiwKPdSykD6f++af9LA40DnHQKlKmQTErTLEAYSyD1IMtnmOH5jsN36D4PRI6/x r430+bcBowjjpv5Dgh6X10wTPHkf/oBOjOZPLbuYKzaA2A5t+hDpa8SI/T4gQVMw vmsRJkql3g2IgvRJOsef0RabVOrtJ6SlMlizSqcgo8oiMZf997DJfKSw4NsB7BF5 5sY3bemK4DN9eKG05SGAF2nq8kjTPa68GYrxoFyZuImsHPGj7xIVMUCj2+cGsI83 gYyUzUHwcJimwBhnCqUs/Fx8HnUQYRNKjMDBlAASoTqRhsDAblhufcluYBoIYBhp a2ygEpE2o7RVuSafsLnWaEN1LEXZnzzLjDG973xW/o2IRVw2y9ijT/UiozEnHgmw s3XDOe5lmoNkoYnHp24fH3UQL0qEjNadGdlj4Hn72aXHe1EA8NQCUWjFbQh3/EiP iQaD7uE4mkJM0xEBrOsvyhsxlI5C8NBhJFxgMynmA6HM/T59EjP777ROxVsTSCkF 5X1bWENdqrnw6Xxn5gVje1Wdu8tOAHbQBFcl5aradziffVEnWxE= =dMiL -----END PGP SIGNATURE----- -------------- next part -------------- From 3d3b41efb6800f98f4b1d389ad2656f5853877bf Mon Sep 17 00:00:00 2001 From: theova Date: Sun, 7 Apr 2019 11:34:53 +0200 Subject: [PATCH] upgpkg: libre/qutebrowser-1.6.1-1.par1 --- libre/qutebrowser/PKGBUILD | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/libre/qutebrowser/PKGBUILD b/libre/qutebrowser/PKGBUILD index b3c9eda43..118a212d2 100644 --- a/libre/qutebrowser/PKGBUILD +++ b/libre/qutebrowser/PKGBUILD @@ -9,7 +9,7 @@ # - set webkit backend as default pkgname=qutebrowser -pkgver=1.5.2 +pkgver=1.6.1 pkgrel=1 pkgrel+=.par1 pkgdesc="A keyboard-driven, vim-like browser based on PyQt5 and QtWebKit, without nonfree qt5-webengine recommendation" @@ -29,9 +29,8 @@ options=(!emptydirs) source=("https://github.com/qutebrowser/qutebrowser/releases/download/v$pkgver/qutebrowser-$pkgver.tar.gz" "https://github.com/qutebrowser/qutebrowser/releases/download/v$pkgver/qutebrowser-$pkgver.tar.gz.asc") validpgpkeys=("E04E560002401B8EF0E76F0A916EB0C8FD55A072") -sha256sums=("be126522456902fc80e63466738f36c55639bcb237c23e078c2a246c7d4d214e" - 'SKIP') - +sha256sums=('178421f121d72344dc9640018f6b6c747d7f1e6875932b6e12ef4941d37593e9' + 'SKIP') build() { cd "$pkgname-$pkgver" -- 2.21.0 -------------- next part -------------- -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEmebv4QLCFsrMoA8HYV3Rx08rMJEFAlypyVwACgkQYV3Rx08r MJHu6Q//YMqksAL9Q3jduHJHZ6Rbn+EHzZxQ5H0TSYRLwLkquXrHaSnRweCcx8qD /6WeKMnmOYUJrZ53JcWKykgDlpoXcF0U+Im7KhzzVfAo5cpEW/LjLc7BzpUZJ/iU +eNvTa2Xlw3q0s5iEIcexklQpnEsQpVpLy92ksNWdjzs260NH5unfA0SuFJfcrRq h6SUvctB9kFhHlYe0yKmRFhhAI1RvubwKo7IoGtRa1fCqeIV9/pmPPWROTxIEK9h JALzS92jmd9jOhP+fsHRlRDuPxfmUAQrebYBdwcJ3VwY9oTl2olgP0UW2sZmpAlZ rq3OjUZfKbKTHgzowcJmSKnmilJDC20Xsjy0TJ1nMYwFuqOMKioGdtzHpSLB/Sh5 euBjRXut9alh9o7uPBGJsQQ2qYKqgWxbGYdWoZL5D+HD3OU/q9CfhJEeE87TPekQ MmoxFpZ4Q9LSGOsZkKTKKXLRtPQq6UhjEZqU42L0F6JPdWLGma+vlVxmZi/CZm5P PTDKdZmvn5LcoBs9JoOM93MSj2hCn+xN6McUHNoVYrEw4Dss6ocAet6VgHIt6onM S/4+Uy0MA5ncxA5kJTfPjZ5CsWurHnO9juxoMft9azLaDRjPAeOkMRcHbcVXtyUv inHrXMCJwuA02N3xdemc73+qll6RtMryM95PkpndcS8l/BF6Md8= =KQVd -----END PGP SIGNATURE----- -------------- next part -------------- -----BEGIN PGP PUBLIC KEY BLOCK----- mQINBFx0VEIBEAD2zSQ50f9tWcLnk/rmVdEOnZ4nBCiW07aoc5gvUVCqqvfRkriK ntJONTQiQtQLq0BRbO/dfR7EGc448ZuPpcVyzZwmiJbsCr2qYn4Um+htNVPwBrBY x6p5Y7dIyO2l1R+hgRPwb13wof5VFgr6HKeL+487QL3I3TYQoFVf8ikhMO1/ojBt Lp18j4BjC42cneNm4crHMFVSvbIH0GizQFN5QToKjPwY4qFVfdRPBKBFfJZRgkv8 FT731YlHpQMYI60o0VH3KdWiTuv/0WzPimMsBv3KvGg5zdhCcdkDmwOTimqzriDY VZrOvp+hpeb5mb9sLn+4kWwZhAReQCZLoyqNBUxHjbh+kVMFIqwoyK78NzpnF2oi Zys1Up0dr4NPW7ZED4bJ/m134mPfrGEFuU0k7l/Jx1GovPkrXrN4jm4r2neFrOe+ M8ma8MBqvqk98bT/89sqx9IuJ2wHQ7oq2dHGde4l19zBVA7OQq3vkxkw56qmPMie /VH4Zj3bErWtb8TEXgdhkohiMshufUE+5dle4ESVW9QTVTRsHfl7i4myyZ0WbLih ATZcPzR999yonKei7aKw1TIh7xuiZ9tAR0kXM+gAIHqNdamQhx+APIJXCGmdLktu X9CSiHi+7BUm7CvVqOo+/oDTkoAA32FAUgXnFuBmrT+Xur5CkRdwR+LMOwARAQAB tBp0aGVvdmEgPHRoZW92YUBibHVld2luLmNoPokCVAQTAQoAPhYhBJnm7+ECwhbK zKAPB2Fd0cdPKzCRBQJcdFUEAhsDBQkB4TOABQsJCAcDBRUKCQgLBRYCAwEAAh4B AheAAAoJEGFd0cdPKzCR6KIP/ia3J6VY9PGZZySqTDMnl7DWvnH9R/iHWIW4CvXH NZYsrccbN5cjQGVKTvZkr9tJbGlzXSWpNsqxF10sJWKz+g/hxy8TkTJYoga4zVUT ZORzRPRWdPDZFzh20f2alNfs5Gb4mVnOrs6H/wzPdO5gUpUn352VP2Ut5w0jAbV7 LREYw34YucJZbq14AgB8hcBacUKnodf1NXx+gcGcfhRfK2A2EGW9No2E2Gxwq168 WF2nu6BrveAhIZeak0/fllojagSmw7Ut6pQBDacflFWNdE2o40xplWvIbyyHRQKx dCDYrIVs3CLCCPpbHl394yilJ4EeGuWB4DvCsXt3Vyhj5eEh0jYcXRlc3oA9d6Kv LxyiL5YB/DYpchJ//35i9xcQ3ztufWRv8WTIKvK1fu0a6UOJZcHDLBDoFMoIdf47 e/7No3Bj2GDLjli/JHKkMMvODvJSCdt9SsaFemyeGAYpH0q7HPPDRR3aK9HOZkEj yEN+UHzoffWArOTuZxwvE2tNLkstd/s/B9rYdqVbQsPkJazevwWf069G0gfZgVM5 XUM0Sg4ODtgES+Lj2k/yA2XH1EA8ILBP0liWV0O5VWgQiM5wpdXtP5JgsF6/bH8k CQYc4oWHta+Diu9guHJhOBTx09uLbHm7KisteY8tzfiEBinqAXdP6G8PW2RUGbVb L/4ktB50aGVvdmEgPHRoZW92YUBtZW1iZXIuZnNmLm9yZz6JAlcEEwEKAEECGwMF CQHhM4AFCwkIBwMFFQoJCAsFFgIDAQACHgECF4AWIQSZ5u/hAsIWysygDwdhXdHH TyswkQUCXHRVpwIZAQAKCRBhXdHHTyswkQFRD/9F1X9GRkCa/MqNaJ9oI7/amwaj /f3rOyYLoDUccap3UnO4Z6Ih55pi/aHU+sTXOnpjVnRHSBuzFdSs4Hrp/ewACeyB WdrWyX/wQWX61jYnF5AuHqnTvUbGHItxm3iOUOrirrscnLF3KzE5U/+n6E3GHbuN mIZoxDm7sCPVJ9L5O+8E9BOevqSEF/KG1XE7f6t94VN/nfqZ4+1YbNR3EaXhuKmG 0xALl7CXgGDuVYw21nXJH8TQUn8+oYrT2lOVNH+pt7HjZ76PwLrbeYMnP4TbmWvg dDKhiHMUQhWtE8iIFYJM1HW0bLHgurxuRBoYGA2ImjIE+N6eMNHehQdbrywHlC+a DBtth22MHfYiWld0Q/9oNljAO97A8iN/N5Z/aKZ8tH+Bg2m3PoXDtTNJsIssSdZn zhFn9gr29J6WE5yAFpFgXV8afg3ME06UMKygPt67sKUgxub8Y8Yu31RXX7L0YLCD pkmG5I51hwtU0k2IMV4S97LWPlHZlOD0e6Nr5rv6ciKVpqdAhGQZiOs+gMv4NkvS 4yOudxvGQL57wiH+BG6pS9QbvUlcpSCRHAVLykEGnot0WkCpTt4TOHZLYzWN/6vx vHp08HacIf8I8drmqP/1Xm/QL1RMdbvhMRmdBjHPHZpcgD43zB25Q8RKAr2+1Ksy MKGzHh4lpvW4iYJJW7kCDQRcdFRCARAAxDHcOjvXbEM6RotgMg4DORka9tBzxAjT uaviBMI64hNZUlTD1kvx70DLWxakJgfAYFbwgAt17N+VJph8fVUmUz0jweiU1lJy J1UIW7y9d03+ivrTOyRJnJj+IrJsGDUdUF5r7b0vo8x6PnU0mKsklKi+Jwi84o+3 h0HQiS3Tb1I4wZX0HOWQWHZIGkFr5M+Kgwo7mMTbukV9TZxRRS/5IjhT0Ih80qhj i473j/Cb+RlmBV9F6oL4GVnbFms3kpsflRkwQ5Flt5+rHa2k4VudxXB0coeXeZ/8 ujrYE+BJ5ZNE1qj2YwQED8IHPp5GN4pcrUg6oyl8LXJfnBqH2kqtAzQElmhiTTHl GXHDmzv1ZgyfTLR2yVBQutrSUJwbzEzKcUib6sNmhfuBrc4IDYLhsbPFc3dW+z7m vn4cktgBWhmSZ3siSB98U5kdVYgawd6+wZEa0c5825xJgcWGVghjQXypfufsF/EN IjjFhigGalr/bHN8Ym7MOoNKKRbRydpiImmmUBzOfJtSzrfBpQnW64+8xEXL5dSm w/U47wCNDb50u6v8w9Gusijz+Lp/ezgNT9mn/dkYe2op2QPZWXK1fAynCFhsh1Hn izgii5hl3N4jMDoKRo6DVzTp3MOnV/IeXtlXp95x5yFIA6INaHVLDuseeOJGUaqe SiyOhzwjYcEAEQEAAYkCPAQYAQoAJhYhBJnm7+ECwhbKzKAPB2Fd0cdPKzCRBQJc dFRCAhsMBQkB4TOAAAoJEGFd0cdPKzCRNuoP/00Bus2viNMaK8OMkc2/vhMiI+W4 wS4MbCdyhH4+xlaVh1jiLfdYr9dwEOc/hTKQb39/81X/bPpC0pkLTED9em8y5+O1 qF9WV8g2p6OEHMzwECa2KNaMMb5o1XY/ScE+Z8Qk/SdB1SXILCaeOJ2/qd/V3bjp mmX/31WdRdWAdO5XdjZgtgt9OEbCOTxMUU7GIi24lL4qJkRcrBSRzwrNATviEuNs z/QbHLHnwH9C17yR9i1YkdUV+xu4ZllTM6sO9efuGNPSgqNVHWptTZcuC4IgfyGs g85wq54VzoJpN5kVCihiMpqxOmagxbFo1sRyi/h7bZeAJN343NktJOtN4t4Ve6ck ++CTiCgUDGtaYFs3hocAP4ZMxkaKZIJf/7wWtiKIGNB/+N8AnKYXk6e4dupNDwOj wfxyeDKDW8UZFKN3iwOYxla/zaFEbXSPvC6pTFNVQtiqUlljGxLDQTsnpIMKACid oddUkkU0hsH7aVb1e9RsE6ogBNUEyJumniYDiC6cLMJu5ZIP+AB05nxkv0mlmtu0 Mtq67V2vNRsuzkJt3pRKnYNHAo7BpLuViqdj9Rua4Op71bwYMw8LDgpdySu7oijk 0WFM8UenOcKilIxZw+7vsxdTlsy6uuUHMxhx6p5HiXujzdMlASCG6K6Kevvi+MU8 5KFN2ZTjfeLJua6i =J+1L -----END PGP PUBLIC KEY BLOCK----- -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From bill-auger at peers.community Wed Apr 10 20:59:52 2019 From: bill-auger at peers.community (bill-auger) Date: Wed, 10 Apr 2019 16:59:52 -0400 Subject: [Dev] Planned beefcake outage In-Reply-To: <87imvlio80.wl-lukeshu@lukeshu.com> References: <87imvlio80.wl-lukeshu@lukeshu.com> Message-ID: <20190410165952.3cfa66e1@parabola> no apology necessary :) just be careful not to move it 901 miles east, or else it could get very wet in the atlantic puddle and youll need to rename it to sponge-cake From nobody at parabola.nu Sat Apr 13 08:51:55 2019 From: nobody at parabola.nu (Parabola Website Notification) Date: Sat, 13 Apr 2019 08:51:55 -0000 Subject: [Dev] Orphan Libre package [iceweasel] marked out-of-date Message-ID: <20190413085155.20349.60527@winston.parabola.nu> grizzlyuser at protonmail.com wants to notify you that the following packages may be out-of-date: * iceweasel 1:66.0.2-1.parabola1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/iceweasel/ * iceweasel 1:66.0.2-1.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/iceweasel/ The user provided the following additional text: Thank you for maintaining this package! A new version 66.0.3 is available: https://www.mozilla.org/en-US/firefox/notes/ Updated PKGBUILD from Arch firefox doesn't have any changes except version number. From bill-auger at peers.community Sat Apr 13 19:06:55 2019 From: bill-auger at peers.community (bill-auger) Date: Sat, 13 Apr 2019 15:06:55 -0400 Subject: [Dev] Patch for qutebrowser update 1.6.1 In-Reply-To: <20190407095916.sonhoijpbwsni6hl@RainbowWarrior.localdomain> References: <20190407095916.sonhoijpbwsni6hl@RainbowWarrior.localdomain> Message-ID: <20190413150655.24ec0f1a@parabola> 'qutebrowser' 1.6.1 is in the repos now - thanks many parabola packages show up as "orphaned" - we are not so formal about having one maintainer per package; so "orphaned" doesnt mean very much - if there is anything else you want upgraded, you can just poke someone From bill-auger at peers.community Sat Apr 13 19:18:44 2019 From: bill-auger at peers.community (bill-auger) Date: Sat, 13 Apr 2019 15:18:44 -0400 Subject: [Dev] Patch for qutebrowser update 1.6.1 In-Reply-To: <20190407095916.sonhoijpbwsni6hl@RainbowWarrior.localdomain> References: <20190407095916.sonhoijpbwsni6hl@RainbowWarrior.localdomain> Message-ID: <20190413151844.2f6271e1@parabola> check this out - when you launch qutebrowser, you are greeted with this prominent warning - as a justification for abandoning webkit support, the upstream is explicitly warning users not to use the parabola qutebrowser package QtWebKit backend warning Because of those security issues and the maintaince burden coming with supporting QtWebKit, support for it will be dropped in a future qutebrowser release. It's recommended that you use QtWebEngine instead. (Outdated) reasons to use QtWebKit Most reasons why people preferred the QtWebKit backend aren't relevant anymore: QtWebEngine being unavailable on Parabola: Claims of Parabola developers about QtWebEngine being "non-free" have repeatedly been disputed, and so far nobody came up with solid evidence about that being the case. Also, note that their qutebrowser package is orphaned and was often outdated in the past (even qutebrowser security fixes took months to arrive there). You might be better off chosing an alternative install method. From andreas at grapentin.org Mon Apr 15 08:30:08 2019 From: andreas at grapentin.org (Andreas Grapentin) Date: Mon, 15 Apr 2019 10:30:08 +0200 Subject: [Dev] Patch for qutebrowser update 1.6.1 In-Reply-To: <20190413151844.2f6271e1@parabola> References: <20190407095916.sonhoijpbwsni6hl@RainbowWarrior.localdomain> <20190413151844.2f6271e1@parabola> Message-ID: <20190415083008.GB19639@parabola-pocket.localdomain> We should probably contact them about this and invite them to a discussion about why we think the outstanding issues are still relevant. Best, -A On Sat, Apr 13, 2019 at 03:18:44PM -0400, bill-auger wrote: > check this out - when you launch qutebrowser, you are greeted > with this prominent warning - as a justification for abandoning > webkit support, the upstream is explicitly warning users not to > use the parabola qutebrowser package > > QtWebKit backend warning > > Because of those security issues and the maintaince burden > coming with supporting QtWebKit, support for it will be dropped > in a future qutebrowser release. It's recommended that you use > QtWebEngine instead. > > (Outdated) reasons to use QtWebKit > > Most reasons why people preferred the QtWebKit backend aren't > relevant anymore: > > QtWebEngine being unavailable on Parabola: Claims of Parabola > developers about QtWebEngine being "non-free" have repeatedly > been disputed, and so far nobody came up with solid evidence > about that being the case. Also, note that their qutebrowser > package is orphaned and was often outdated in the past (even > qutebrowser security fixes took months to arrive there). You > might be better off chosing an alternative install method. > _______________________________________________ > Dev mailing list > Dev at lists.parabola.nu > https://lists.parabola.nu/mailman/listinfo/dev -- ------------------------------------------------------------------------------ my GPG Public Key: https://files.grapentin.org/.gpg/public.key ------------------------------------------------------------------------------ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: not available URL: From andreas at grapentin.org Tue Apr 16 08:45:44 2019 From: andreas at grapentin.org (Andreas Grapentin) Date: Tue, 16 Apr 2019 10:45:44 +0200 Subject: [Dev] I am starting a review into whether QtWebEngine is free software Message-ID: <20190416084544.GA20561@parabola-pocket.localdomain> Hello Everyone, You have read the subject line of this email, so you know what's up. ================================= What is the situation? ================================= As you all know, in the past, the freedom of QtWebEngine has been questioned repeatedly, to the point that parabola (and I believe most if not all the FSDG compliant distributions) was forced to remove it from its official repositories. As a consequence, many programs that directly or through their dependencies depend on QtWebEngine needed to be blacklisted as well, or be modified to use the -- arguably outdated -- QtWebKit instead. At the moment, this impacts dozens of packages on parabola, which takes away from the experience of the distributions users. It also creates a considerable amount of work for the us maintainers to keep the modified programs up to date, which gets increasingly difficult as the developers move away from QtWebKit. ================================= What is the plan? ================================= What I am now trying to do is organize the existing allegations made against QtWebEngine, and conclusively determine whether or not QtWebEnigne is free software, and if it is deemed to not be entirely free, what steps need to be taken towards liberating it and towards creating a version of QtWebEngine that can be packaged and distributed by FSDG compliant distros. I will *not* be investigating whether Chromium is free software, at least not right now. This review is only for QtWebEngine, and the subset of chromium that it embeds. ================================= Do you want to help? ================================= If you want to help me out, please forward me any existing allegations against QtWebEngine that I might have missed. I want this review to be conclusive, and it can only be complete if all complaints are sufficiently addressed. If you want to get involved more actively, I am currently in the process of setting up a local fossology instance, but I could easily set up a public instance for a collaborative investigation instead. I am also setting up a git repository to organize the results of the review. If you want to get access to any of these, let me know. Come find me in #parabola on freenode for a chat. Best, Andreas Grapentin (oaken-source) for the parabola GNU/Linux-libre distribution. -- ------------------------------------------------------------------------------ my GPG Public Key: https://files.grapentin.org/.gpg/public.key ------------------------------------------------------------------------------ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: not available URL: From lukeshu at lukeshu.com Tue Apr 16 14:08:08 2019 From: lukeshu at lukeshu.com (Luke Shumaker) Date: Tue, 16 Apr 2019 10:08:08 -0400 Subject: [Dev] Planned beefcake outage In-Reply-To: <87imvlio80.wl-lukeshu@lukeshu.com> References: <87imvlio80.wl-lukeshu@lukeshu.com> Message-ID: <87imvegi0n.wl-lukeshu@lukeshu.com> On Wed, 10 Apr 2019 16:45:19 -0400, Luke Shumaker wrote: > Hi all, > > Beefcake will be down for several days starting Saturday (13th) > night/Sunday (14th) morning (EDT), as I physcially move it 900 miles > east. I don't know how long it will take to get Internet set up at > the new location. > > I appologize for the inconvenience. beefcake is now back online. -- ~ Happy hacking, ~ Luke Shumaker From bill-auger at peers.community Tue Apr 16 17:06:17 2019 From: bill-auger at peers.community (bill-auger) Date: Tue, 16 Apr 2019 13:06:17 -0400 Subject: [Dev] Planned beefcake outage In-Reply-To: <87imvegi0n.wl-lukeshu@lukeshu.com> References: <87imvlio80.wl-lukeshu@lukeshu.com> <87imvegi0n.wl-lukeshu@lukeshu.com> Message-ID: <20190416130617.5fcb8c75@parabola> On Tue, 16 Apr 2019 10:08:08 -0400 Luke wrote: > beefcake is now back online. can not connect channel 0: open failed: connect failed: No route to host stdio forwarding failed ssh_exchange_identification: Connection closed by remote host i restarted the tinc.service and tinc at lvpn.service services on winston but it did not help From lukeshu at lukeshu.com Wed Apr 17 14:51:55 2019 From: lukeshu at lukeshu.com (Luke Shumaker) Date: Wed, 17 Apr 2019 10:51:55 -0400 Subject: [Dev] Planned beefcake outage In-Reply-To: <20190416130617.5fcb8c75@parabola> References: <87imvlio80.wl-lukeshu@lukeshu.com> <87imvegi0n.wl-lukeshu@lukeshu.com> <20190416130617.5fcb8c75@parabola> Message-ID: <87h8awhegk.wl-lukeshu@lukeshu.com> On Tue, 16 Apr 2019 13:06:17 -0400, bill-auger wrote: > > On Tue, 16 Apr 2019 10:08:08 -0400 Luke wrote: > > beefcake is now back online. > > can not connect > > channel 0: open failed: connect failed: No route to host > stdio forwarding failed > ssh_exchange_identification: Connection closed by remote host > > > i restarted the tinc.service and tinc at lvpn.service services > on winston but it did not help Whoops, my bad. My network configuration is a little different, and I had to change '.lan' to '.local' in a file in beefcake's '/etc/tinc/lvpn/'. -- Happy hacking, ~ Luke Shumaker From megver83 at hyperbola.info Thu Apr 18 19:09:04 2019 From: megver83 at hyperbola.info (Megver83) Date: Thu, 18 Apr 2019 15:09:04 -0400 Subject: [Dev] I am starting a review into whether QtWebEngine is free software In-Reply-To: <20190416084544.GA20561@parabola-pocket.localdomain> References: <20190416084544.GA20561@parabola-pocket.localdomain> Message-ID: <94f896ed-b256-804f-9b29-414a930d495d@hyperbola.info> El 16-04-19 a las 04:45, Andreas Grapentin escribi?: > > Hello Everyone, > > You have read the subject line of this email, so you know what's up. > > ================================= > What is the situation? > ================================= > > As you all know, in the past, the freedom of QtWebEngine has been > questioned repeatedly, to the point that parabola (and I believe most if > not all the FSDG compliant distributions) was forced to remove it from > its official repositories. > > As a consequence, many programs that directly or through their > dependencies depend on QtWebEngine needed to be blacklisted as well, or > be modified to use the -- arguably outdated -- QtWebKit instead. At the > moment, this impacts dozens of packages on parabola, which takes away > from the experience of the distributions users. It also creates a > considerable amount of work for the us maintainers to keep the modified > programs up to date, which gets increasingly difficult as the developers > move away from QtWebKit. > > ================================= > What is the plan? > ================================= > > What I am now trying to do is organize the existing allegations made > against QtWebEngine, and conclusively determine whether or not > QtWebEnigne is free software, and if it is deemed to not be entirely > free, what steps need to be taken towards liberating it and towards > creating a version of QtWebEngine that can be packaged and distributed > by FSDG compliant distros. > > I will *not* be investigating whether Chromium is free software, at > least not right now. This review is only for QtWebEngine, and the subset > of chromium that it embeds. > > ================================= > Do you want to help? > ================================= > > If you want to help me out, please forward me any existing allegations > against QtWebEngine that I might have missed. I want this review to be > conclusive, and it can only be complete if all complaints are > sufficiently addressed. > > If you want to get involved more actively, I am currently in the process > of setting up a local fossology instance, but I could easily set up a > public instance for a collaborative investigation instead. I am also > setting up a git repository to organize the results of the review. If > you want to get access to any of these, let me know. > > > Come find me in #parabola on freenode for a chat. > > > Best, > Andreas Grapentin (oaken-source) > > for the parabola GNU/Linux-libre distribution. > > > -- > > ------------------------------------------------------------------------------ > my GPG Public Key: https://files.grapentin.org/.gpg/public.key > ------------------------------------------------------------------------------ > > > _______________________________________________ > Dev mailing list > Dev at lists.parabola.nu > https://lists.parabola.nu/mailman/listinfo/dev > Great! would be good to also see someone from other free distro or GNU/FSF working with you. Pitifully, because of time, I can't help now -- ~Megver83 SIP: megver83 at sip.linphone.org XMPP: megver83 at jabjab.de Tox: megver83 at toxme.io GPG: 0x227CA7C556B2BA78 GNUSocial: @megver82 at quitter.cl Diaspora*: megver83 at diasp.org Matrix: @Megver83:matrix.org PixelFed: pixelfed.social/Megver83 PeerTube: peertube.xtenz.xyz/accounts/megver83 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 520 bytes Desc: OpenPGP digital signature URL: From bill-auger at peers.community Fri Apr 19 19:05:09 2019 From: bill-auger at peers.community (bill-auger) Date: Fri, 19 Apr 2019 15:05:09 -0400 Subject: [Dev] Planned beefcake outage In-Reply-To: <20190416130617.5fcb8c75@parabola> References: <87imvlio80.wl-lukeshu@lukeshu.com> <87imvegi0n.wl-lukeshu@lukeshu.com> <20190416130617.5fcb8c75@parabola> Message-ID: <20190419150509.6e389f63@parabola> On Tue, 16 Apr 2019 13:06:17 -0400 bill-auger wrote: > channel 0: open failed: connect failed: No route to host > stdio forwarding failed > ssh_exchange_identification: Connection closed by remote host can not connect to beefcake today - same error as before From nobody at parabola.nu Sat Apr 20 10:54:59 2019 From: nobody at parabola.nu (Parabola Website Notification) Date: Sat, 20 Apr 2019 10:54:59 -0000 Subject: [Dev] Orphan Pcr-Testing package [shepherd] marked out-of-date Message-ID: <20190420105459.20349.35146@winston.parabola.nu> thibaultblizz at gmail.com wants to notify you that the following packages may be out-of-date: The user provided the following additional text: http://alpha.gnu.org/gnu/shepherd/ ftp://alpha.gnu.org/gnu/shepherd/ shepherd 0.5.0 From nobody at parabola.nu Sat Apr 20 10:55:45 2019 From: nobody at parabola.nu (Parabola Website Notification) Date: Sat, 20 Apr 2019 10:55:45 -0000 Subject: [Dev] Orphan Pcr-Testing package [shepherd] marked out-of-date Message-ID: <20190420105545.20348.18568@winston.parabola.nu> thibaultblizz at gmail.com wants to notify you that the following packages may be out-of-date: The user provided the following additional text: http://alpha.gnu.org/gnu/shepherd/ ftp://alpha.gnu.org/gnu/shepherd/ shepherd 0.5.0 From nobody at parabola.nu Sun Apr 21 14:23:14 2019 From: nobody at parabola.nu (Parabola Website Notification) Date: Sun, 21 Apr 2019 14:23:14 -0000 Subject: [Dev] Orphan Libre package [smplayer] marked out-of-date Message-ID: <20190421142314.29591.57485@winston.parabola.nu> grizzlyuser at protonmail.com wants to notify you that the following packages may be out-of-date: * smplayer 18.2.0-1.parabola1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/smplayer/ * smplayer 18.2.0-1.parabola1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/smplayer/ * smplayer 18.2.0-1.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/smplayer/ The user provided the following additional text: Thank you for maintaining this package! A new version is available: https://www.smplayer.info/en/changes From nobody at parabola.nu Mon Apr 22 13:42:20 2019 From: nobody at parabola.nu (Parabola Website Notification) Date: Mon, 22 Apr 2019 13:42:20 -0000 Subject: [Dev] Orphan Libre package [mplayer] marked out-of-date Message-ID: <20190422134220.29592.29422@winston.parabola.nu> wonkerwilly at yandex.com wants to notify you that the following packages may be out-of-date: * mencoder 38017-1.parabola2 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/mencoder/ * mencoder 38101-1.parabola2 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/mencoder/ * mencoder 38101-2.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/mencoder/ * mplayer 38017-1.parabola2 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/mplayer/ * mplayer 38101-1.parabola2 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/mplayer/ * mplayer 38101-2.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/mplayer/ The user provided the following additional text: MPlayer 1.4 "SubCounter" is out. From bill-auger at peers.community Thu Apr 25 04:17:28 2019 From: bill-auger at peers.community (bill-auger) Date: Thu, 25 Apr 2019 00:17:28 -0400 Subject: [Dev] testing email Message-ID: <20190425001728.0c77a223@parabola> testing email From bill-auger at peers.community Thu Apr 25 03:49:29 2019 From: bill-auger at peers.community (bill-auger) Date: Wed, 24 Apr 2019 23:49:29 -0400 Subject: [Dev] testing email Message-ID: <20190424234929.76ec183f@parabola> testing email From nobody at parabola.nu Fri Apr 26 20:55:49 2019 From: nobody at parabola.nu (Parabola Website Notification) Date: Fri, 26 Apr 2019 20:55:49 -0000 Subject: [Dev] Orphan Libre package [bladerf] marked out-of-date Message-ID: <20190426205549.1080.22203@winston.parabola.nu> riku.viitanen0 at gmail.com wants to notify you that the following packages may be out-of-date: * bladerf 1.8.0-1.parabola1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/bladerf/ * bladerf 1.9.0-1.par1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/bladerf/ * bladerf 1.9.0-1.par1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/bladerf/ The user provided the following additional text: 2.0 is available and required by gqrx which now fails to start because libbladeRF.so.2 doesn't exist. From nobody at parabola.nu Tue Apr 30 18:00:31 2019 From: nobody at parabola.nu (Parabola Website Notification) Date: Tue, 30 Apr 2019 18:00:31 -0000 Subject: [Dev] Orphan Libre package [netsurf] marked out-of-date Message-ID: <20190430180031.1078.86346@winston.parabola.nu> devel at kraitar.com wants to notify you that the following packages may be out-of-date: * netsurf 3.7-2.parabola1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/netsurf/ * netsurf 3.7-2.parabola2 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/netsurf/ * netsurf 3.7-2.parabola2 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/netsurf/ The user provided the following additional text: NetSurf 3.8 was released on 29 Aug 2018.