Then on first boot, after I enter my password, the graphical loading screen appears for a few seconds, black screen, a series of console outputs(too fast to grasp much of it, tho I noticed a "kernel panic - not syncing: fatal exception" and back to boot.
The same happened at each boot, sometimes it didn't even ask me for my password and failed the same way. I reinstalled Qubes without encryption but the same happened.
I tried to reboot without my wifi card or without the "iommu=no-igfx" parameter in the GRUB boot menu but no result.
Any idea what may be happening?
Any way to save the boot logs? I tried making journalctl persistent and export the files with the troubleshooting tool from the installation media, but nothing was saved.
I'm pretty much using the same machine with the same coreboot build and the same version of Qubes than Awokd but he doesn't have this issue.
Thanks in advance :)
--
You received this message because you are subscribed to the Google Groups "qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users...@googlegroups.com.
To post to this group, send email to qubes...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CAAaskFB0U6fSBs3i06-0_8byp5g%2BNRvVJJcqcv40jVPZ8OUFcQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
On 12/29/2017 08:21 PM, awokd wrote:
Nah I don't like AMD due to PSP - it is simply that they added it much later than intel did ME so the pre-PSP AMD stuff is still fast enough to be useful which is why I recommend it for those who require x86-64.I appreciate your enthusiasm for the AMD products.
I have many times, sometimes I receive a reply but it never goes anywhere :[It was actually one of your posts along with several other people's that convinced me to get the G505s. But there might be more effective ways of communicating your concerns with Purism than frequently repeating it to the same groups of people. :) You mention tech media for example, have you contacted them?
No they are :3 its just that the tech media only cares about shiny appley type products not stuff made for real work.Or how about writing a fact-based expose (make sure it doesn't seem like a rant) and submitting it or blogging it somewhere? I'm no PR guy though, so maybe those aren't good ideas.
Hi!
This seems like a pretty active, general thread full of G505s users, so I thought I'd drop by. My G505s came in the mail today: I'm one of those dumb windows users who realized the error of their ways, working to slowly scrub the microsoft out of my life. (also the Comp Eng student who built the world's crappiest CPU)
My G505s is one of those A10s with the fancy radeon discrete graphics. It also came with 8GB of RAM and a 1TB drive I will promptly fill with zeros.
I'm new to the ways of linux, but I know my way around well enough to get stuff done. I'm eager to help out with the maintenance and support of the G505s any way I can, which I expect will probably involve playing the guinea pig for a while. (good thing ebay has a lot of spare parts, boards included :D)
Stuff I'm considering:
-hunting for rowhammer-proof DDR3 (I have a candidate 8GB SODIMM in mind, current personal record with google's test is 24h+ of single sided hammering followed by a power outage, and 9h45 of single sided hammering followed by a bit flip; ECC and non ECC DDR2 respectively)
-syncing the latest commits and testing that nothing explodes, if that needs to be recorded
-may try (core)booting the G505s with an A8, since those pop up on ebay more often than the A10 variant, and I think I can stomach the cost in the interests of science if people are intrigued
-testing out any attempts to get discrete graphics working, since I've got the nicer of the two available GPUs
-testing attempts to improve other stuff (does ACPI still need work? I get the feeling the wiki's out of date)
My daily driver laptop will probably continue to be a PoS (piece of sh*t) HP laptop with win8.1 (newer and supposedly slower than a G505s, PSP included :/) for the foreseeable future, so I'm not too worried about bricking the G505s once-in-a-while. Don't worry, I have a nice centos 7 desktop with no PSP and full Spectre mitigation (so far, thanks to chicken bits) for the real work.
Anyhoo, that's my introduction. I'll probably have more to say later this week when I can actually get the darn thing out of the box it shipped in.
If anyone has any getting started advice, I'd love to hear it. (beyond buying an ath9k) I plan on documenting the experience, since I figure having a nice, illustrated step-by-step blog will help raise awareness about the G505s.
-Matt
Yep. I'll be making the upgrade soon. :)
The crappy newer HP I have maxes out at 8.
> > I'm new to the ways of linux, but I know my way around well enough to get stuff done. I'm eager to help out with the maintenance and support of the G505s any way I can, which I expect will probably involve playing the guinea pig for a while. (good thing ebay has a lot of spare parts, boards included :D)
> >
> > Stuff I'm considering:
> > -hunting for rowhammer-proof DDR3 (I have a candidate 8GB SODIMM in mind, current personal record with google's test is 24h+ of single sided hammering followed by a power outage, and 9h45 of single sided hammering followed by a bit flip; ECC and non ECC DDR2 respectively)
>
> Installing coreboot will help you here as it *should* increase the
> refresh rate
That's good to know. I'm planning on testing out some DDR3 from hynix though, since I found exactly *one* DDR3 SODIMM they make/made which (supposedly) has an unlimited MAC. (maximum activation count, at least according to some table someone compiled from datasheets that are no longer accessible).
I figure people who are concerned about rowhammer will find the results interesting, good or bad. (especially since we've seen two remote exploits for rowhammer in the last month or so, one which only requires getting about 800 megabits of carefully crafted packets through the network adapter)
Will report back with results as soon as I can get my hands on it.
> > -syncing the latest commits and testing that nothing explodes, if that needs to be recorded
> > -may try (core)booting the G505s with an A8, since those pop up on ebay more often than the A10 variant, and I think I can stomach the cost in the interests of science if people are intrigued
>
> Why not coreboot your faster and better A10? It is very easy and we are
> happy to help!
I should clarify: I do have the A10 model, but I would like to swap the CPU to an A8 to test coreboot on that, since A8 models show up more often on ebay and some people might want to try coreboot with that. (I don't know why they wouldn't buy an A10 and swap it, but whatever)
> > -testing out any attempts to get discrete graphics working, since I've got the nicer of the two available GPUs
> > -testing attempts to improve other stuff (does ACPI still need work? I get the feeling the wiki's out of date)
>
> With coreboot everything works, and 4.0 runs great.
Are you referring specifically to ACPI, or this stupid dual GPU stuff?
From what I've seen, somebody tried running coreboot on a version of the G505s with a discrete GPU, but had to disable the associated PCI device or coreboot would print pages of debug info an crash. I don't know whether they included a VGA BIOS for it. (I'm not 100% sure how/if coreboot supports multiple VGA BIOSs)
That being said, even if it did boot with both GPUs and both VGA BIOSs, the two appear to run in crossfire, with no connection between the discrete GPU and the screen. There doesn't seem to be any real support in linux for crossfire but I guess you could use the discrete GPU to hardware-accelerate various tasks.
By the sound of it, coreboot doesn't have to do anything to support it like switching a video multiplexer, since it sounds like crossfire transfers data of the PCI bus, but I'm no expert. (well, aside from turning it on and off like the stock BIOS can)
Sadly, (well, probably good for coreboot compatibility) after going over the G505s I got shipped, it seems the ebay seller sent me the version with just the APU, no discrete GPU. I wouldn't entirely discount buying a spare motherboard with it, since they're floating around for not *too* much money, but only if somebody really wants to test/work on getting the discrete GPU working (preferably with a use case in mind). Not in the immediate future though.
> > My daily driver laptop will probably continue to be a PoS (piece of sh*t) HP laptop with win8.1 (newer and supposedly slower than a G505s, PSP included :/) for the foreseeable future, so I'm not too worried about bricking the G505s once-in-a-while. Don't worry, I have a nice centos 7 desktop with no PSP and full Spectre mitigation (so far, thanks to chicken bits) for the real work.
> >
> > Anyhoo, that's my introduction. I'll probably have more to say later this week when I can actually get the darn thing out of the box it shipped in.
> >
> > If anyone has any getting started advice, I'd love to hear it. (beyond buying an ath9k) I plan on documenting the experience, since I figure having a nice, illustrated step-by-step blog will help raise awareness about the G505s.
>
> I am/we are very pleased you made the right choice :D and bought the
> genuine article instead of a fake libre laptop.
I considered it, but I have a fair bit of skepticism how well anyone can "fix" the IME at this stage, even google, so I didn't research further.
Removing modules with the ME_Cleaner is nice, but you can't remove the BUP module (bring-up) and there is a known remote code execution vulnerability against the IME itself (positive technologies) that uses a buffer overflow in the BUP. It's been patched by intel, but that means getting new IME firmware and re-cleaning it.
-Matt
--
You received this message because you are subscribed to a topic in the Google Groups "qubes-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/qubes-users/ALUPDysiaEc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to qubes-users...@googlegroups.com.
To post to this group, send email to qubes...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/49cf1b59-c4b2-47c0-85fc-5e05115448ae%40googlegroups.com.