[coreboot] Re: coreboot is under attack? many access problems recently, need to check that sources haven't been tampered
Thank you very much Patrick! For a moment I was afraid that old good "pipermail" disappeared, huge thanks to you for leaving it there. And beautiful new shiny "hyperkitty" UI, really nice looking! Awesome NY present :D Happy New Year dear friend ;) BR, Ivan пн, 31 дек. 2018 г. в 19:56, Carl-Daniel Hailfinger : > > Dear Ivan, > > Patrick Georgi did all the work, he deserves all the thanks. > > Best regards, > Carl-Daniel > > On 31.12.2018 17:48, Ivan Ivanov wrote: > > Dear Carl-Daniel, thank you very much for your assuring reply, and for > > keeping the old "pipermail" mailing list archive because it is much > > easier to wget and browse with links text browser. Happy coming New > > Year ! ;-) > > > > Best regards, > > Ivan > > > > пн, 31 дек. 2018 г. в 19:40, Carl-Daniel Hailfinger > > : > >> On 31.12.2018 12:34, Ivan Ivanov wrote: > >>> Had a lot of access problems recently, both to coreboot website and > >>> its' repositories. Was it a DDoS attack? How to make sure that the > >>> sources at review coreboot repository haven't been modified during > >>> this event? > >> No need to worry. There was a scheduled server migration (better > >> hardware) and the mailing list software was updated as well. This took > >> quite a lot of resources. Things should be a lot snappier now. > >> > >> For details, see the following message: > >> > >> Date: Tue, 25 Dec 2018 00:40:41 +0100 > >> Message-ID: > >> > >> Subject: [coreboot] mailing list changes > >> > >> Regards, > >> Carl-Daniel > >> > > ___ > > coreboot mailing list -- coreboot@coreboot.org > > To unsubscribe send an email to coreboot-le...@coreboot.org > ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
[coreboot] Re: Update on Asus KGPE-D16 with coreboot 4.6 and Qubes 4
Hi Pete, what if this "Intel Optane problem" is not Qubes specific and it's just this SSD (?) is faulty. Do you have any warranty left to RMA and try a different Optane, or even better - take a completely different SSD to avoid supporting Intel corporation with your money, funding the next generation of ME-like backdoors. Ivan пн, 31 дек. 2018 г. в 15:26, petecb via coreboot : > > Hi, > > Season's greetings to everyone! :-) > > I've been able to get my Asus KGPE-D16 running with coreboot 4.6 and Qubes 4 > and I'm pleased to report it has been nice and stable over the holiday > period, save for a few minor issues. > > Suspend works fine on a fresh install of Qubes 4, however applying the latest > updates then stops this from working. (It goes in to suspend but does not > resume properly). I'm assuming this is now a Qubes issue. > > My Intel Optane 900p NVME drive does not work reliably with Qubes 4. It > initially appears fine but anywhere between 4-12 hours after boot the system > will panic and switch to a read-only file system - you can't run any commands > without an "Input/Output Error" even in Dom 0. The only course of action when > this is encountered appears to be a hard reset. Unsurprisingly, getting any > kind of logs about what is actually happening has proven fruitless so far :-( > > I have therefore switched to a normal SATA drive for the last week and this > has been nice and stable. I suspect my best course of action to get a higher > performing filesystem is to move to 4 SATA SSDs in RAID 10. If anyone has any > other suggestions to get faster drive access with this platform (particularly > good random read/write performance for using lots of concurrent VMs in Qubes) > or possible approaches to fix my NVME drive issue, they would be much > appreciated. > > My only other minor issue at the moment is lack of fan control. If I run > "sudo pwmconfig" in dom0 I get the message "There are no pwm-capable sensor > modules installed". I suspect I need to enable some additional modules, so if > anyone can provide me some explicit directions on how to do this, it would > again be much appreciated. > > Kind regards, > > Pete > ___ > coreboot mailing list -- coreboot@coreboot.org > To unsubscribe send an email to coreboot-le...@coreboot.org ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
[coreboot] Re: coreboot is under attack? many access problems recently, need to check that sources haven't been tampered
Dear Ivan, Patrick Georgi did all the work, he deserves all the thanks. Best regards, Carl-Daniel On 31.12.2018 17:48, Ivan Ivanov wrote: > Dear Carl-Daniel, thank you very much for your assuring reply, and for > keeping the old "pipermail" mailing list archive because it is much > easier to wget and browse with links text browser. Happy coming New > Year ! ;-) > > Best regards, > Ivan > > пн, 31 дек. 2018 г. в 19:40, Carl-Daniel Hailfinger > : >> On 31.12.2018 12:34, Ivan Ivanov wrote: >>> Had a lot of access problems recently, both to coreboot website and >>> its' repositories. Was it a DDoS attack? How to make sure that the >>> sources at review coreboot repository haven't been modified during >>> this event? >> No need to worry. There was a scheduled server migration (better >> hardware) and the mailing list software was updated as well. This took >> quite a lot of resources. Things should be a lot snappier now. >> >> For details, see the following message: >> >> Date: Tue, 25 Dec 2018 00:40:41 +0100 >> Message-ID: >> >> Subject: [coreboot] mailing list changes >> >> Regards, >> Carl-Daniel >> > ___ > coreboot mailing list -- coreboot@coreboot.org > To unsubscribe send an email to coreboot-le...@coreboot.org ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
[coreboot] Re: coreboot is under attack? many access problems recently, need to check that sources haven't been tampered
Dear Carl-Daniel, thank you very much for your assuring reply, and for keeping the old "pipermail" mailing list archive because it is much easier to wget and browse with links text browser. Happy coming New Year ! ;-) Best regards, Ivan пн, 31 дек. 2018 г. в 19:40, Carl-Daniel Hailfinger : > > On 31.12.2018 12:34, Ivan Ivanov wrote: > > Had a lot of access problems recently, both to coreboot website and > > its' repositories. Was it a DDoS attack? How to make sure that the > > sources at review coreboot repository haven't been modified during > > this event? > > No need to worry. There was a scheduled server migration (better > hardware) and the mailing list software was updated as well. This took > quite a lot of resources. Things should be a lot snappier now. > > For details, see the following message: > > Date: Tue, 25 Dec 2018 00:40:41 +0100 > Message-ID: > > Subject: [coreboot] mailing list changes > > Regards, > Carl-Daniel > ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
[coreboot] Re: coreboot is under attack? many access problems recently, need to check that sources haven't been tampered
Hi Ivan, On 31.12.18 12:34, Ivan Ivanov wrote: > Had a lot of access problems recently, both to coreboot website and > its' repositories. yes, they were very unresponsive yesterday. > Was it a DDoS attack? I wouldn't know. Though, there's also still the migration to a new mailing list solution (index generation for the archive), that takes many resources on the server. > How to make sure that the > sources at review coreboot repository haven't been modified during > this event? Due to the distributed nature of Git, we always know that the history of the code (and implicitly the state of the code up to a given point) wasn't tampered with. But... there were (authorized) modifications during "this event". So what would remain (if we'd expect tampering) is to distinguish wanted modifications from unwanted ones. Again, Git makes this easy. If you have a trusted commit hash (or local pointer to an earlier revision on master) you can ask Git what changed since then. Nico ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
[coreboot] Re: coreboot is under attack? many access problems recently, need to check that sources haven't been tampered
On 31.12.18 18:34, Ivan Ivanov wrote: Had a lot of access problems recently, both to coreboot website and its' repositories. Was it a DDoS attack? How to make sure that the sources at review coreboot repository haven't been modified during this event? Maybe it's just a lot more of regular traffic because between xmas and new year many nerds have time to tinker with coreboot. ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
[coreboot] Update on Asus KGPE-D16 with coreboot 4.6 and Qubes 4
Hi, Season's greetings to everyone! :-) I've been able to get my Asus KGPE-D16 running with coreboot 4.6 and Qubes 4 and I'm pleased to report it has been nice and stable over the holiday period, save for a few minor issues. Suspend works fine on a fresh install of Qubes 4, however applying the latest updates then stops this from working. (It goes in to suspend but does not resume properly). I'm assuming this is now a Qubes issue. My Intel Optane 900p NVME drive does not work reliably with Qubes 4. It initially appears fine but anywhere between 4-12 hours after boot the system will panic and switch to a read-only file system - you can't run any commands without an "Input/Output Error" even in Dom 0. The only course of action when this is encountered appears to be a hard reset. Unsurprisingly, getting any kind of logs about what is actually happening has proven fruitless so far :-( I have therefore switched to a normal SATA drive for the last week and this has been nice and stable. I suspect my best course of action to get a higher performing filesystem is to move to 4 SATA SSDs in RAID 10. If anyone has any other suggestions to get faster drive access with this platform (particularly good random read/write performance for using lots of concurrent VMs in Qubes) or possible approaches to fix my NVME drive issue, they would be much appreciated. My only other minor issue at the moment is lack of fan control. If I run "sudo pwmconfig" in dom0 I get the message "There are no pwm-capable sensor modules installed". I suspect I need to enable some additional modules, so if anyone can provide me some explicit directions on how to do this, it would again be much appreciated. Kind regards, Pete___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
[coreboot] coreboot is under attack? many access problems recently, need to check that sources haven't been tampered
Had a lot of access problems recently, both to coreboot website and its' repositories. Was it a DDoS attack? How to make sure that the sources at review coreboot repository haven't been modified during this event? Best regards, Ivan ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
