ClockworkCoder
Chaotic Neutral
Excellent! Looks like this weekend may bring a news bonanza!
Sweet. Dark red pyras.Hello eveybody. Tommorow we will continue with the Black and Red color . Today in 1 hour we will do some samples from the Keyboard mold cause we changed the feeding again. I will try to upload some fotos tommorow when we finish . Monday i will send all the samples to ED .
Sounds to me like we haven't tried all of the configuration options yet, and it might be one of those that affects this. The CPU is spinning up and drawing current, so electrically it all looks pretty damn good to me, it's just a matter of software, only it's software that runs even before the kernel has spun up, so it's pretty esoteric knowledge.Hopefully the Charger Software can be fixed whitout changing the Hardware..
Ditnt sound that great..
This should be possible. From my analysis of the hardware, it should by default allow for the 500mA limit. My HW just wasn’t behaving this way. I’ve been working with HNS to try and find out what the reason for this is. Turns out my charging circuit was damaged in a few ways either by production error or by my error (it’s definitely damaged now by my error after trying to fix it ). Once I get my charge circuit fixed, I’ll be working on some test scripts to improve testing of the charge HW before the units go out as well as improving support for the charger chips in the bootloader to better handle booting. This should all be ready by the time mass production units go out.Sounds great so far azouls,
Hopefully the Charger Software can be fixed whitout changing the Hardware..
Ditnt sound that great..
No I haven’t yet. Power management is always a difficult thing to handle on devices like this. The processor has to come up as minimally as possible and be able to properly configure the various power chips before enabling internal cores and external peripherals. However if cores or peripherals are enabled too early, the hardware could be damaged or get stuck in a boot loop. Similarly if the main ARM core (which will be executing the code which brings up the rest of the system) does not have the power it needs, it won’t be able to bring up the rest of the system.Sounds to me like we haven't tried all of the configuration options yet, and it might be one of those that affects this. The CPU is spinning up and drawing current, so electrically it all looks pretty damn good to me, it's just a matter of software, only it's software that runs even before the kernel has spun up, so it's pretty esoteric knowledge.
Well, not every laptop, some of the really expensive ones still have removable batteries, the system 76 Serval WS has a removable battery for example but it's also a $2000 USD laptop.
From the top of my dome, I'd say redundancy, so that you can still use the device in case your battery got stolen - to contact the police for instance.Anyway, what's the point on booting the Pyra without a battery?
Anyway, what's the point on booting the Pyra without a battery?
They also do bios edits (remove the Intel Management Engine for example) and they also must have something else customised because people have reported running the system 76 driver ppa on a stock unit doesn't work. My laptop actually only cost $200 above stock, and I don't mind paying that for a laptop that is guaranteed to just work.Wait, System 76 Serval WS... that's a rebranded Clevo P775TM1-G. I hate it when Clevo resellers don't mention the base model.
So this guys charge you an extra 500$-1000$ (over other resellers... not counting the OEM W10 license others offer) for pre-installing a Linux distro on a Clevo notebook? that's... interesting
Anyway, what's the point on booting the Pyra without a battery?
In case the battery is 100% drained and cannot boot it? Doesn't the system need to be powered on in order to activate the charge circuit and charging software? Most cell phones have a secondary OS sitting behind the scenes to handle battery charging when, 'off'.
Hmmm, to me, I always understood "Suspend" to be link Windows' Hibernate, where it writes the system state to disk, then powers off. Reloading the state when powering back on.If a battery is fully drained (can happen if a device crashes in suspend and draws power until there's non left)
Certainly in the early days of suspending and sleeping when you often had to trust to luck as to whether your system would come back after either happened, it was possible for a device to crash while it was trying to write its RAM to disc and end up in a zombie state just draining power.Hmmm, to me, I always understood "Suspend" to be link Windows' Hibernate, where it writes the system state to disk, then powers off. Reloading the state when powering back on.
I did have several times where my Pandora was in "Sleep" mode, and it ran out of battery, because it wasn't running the battery monitor checks.
Most laptops I've used with Windows, when put to "Sleep" would automatically Hibernate if the power got too low. Will this be possible on the Pyra?
They also do bios edits (remove the Intel Management Engine for example) and they also must have something else customised because people have reported running the system 76 driver ppa on a stock unit doesn't work. My laptop actually only cost $200 above stock, and I don't mind paying that for a laptop that is guaranteed to just work.
*Edit* forgot to mention, my laptop is not the Serval WS
At least two of my customers had the issue that their GPD Pocket 2 froze in suspend mode, the battery ran dry and now it's not possible to resurrect it (except for charging the battery manually outside the device).
Well I find that quite fishy.
Clevo's P775TM1-G is supposed to offer:
->Overclocking through software (intel XTU).
->Support for Sound Blaster X Pro-Gaming 360º.
->ESS SABRE HiFi DAC.
->Area Fingerprint on the touchpad.
But I see no mention to those on System's notebook. So they support Clevo's hardware on Linux by scrapping those features which are not supported on Linux by default? (you really end up with a notebook with a high quality hifi DAC that serves as ballast for the motherboard??). Fishy fishy...
I would have expected them to write a patch for those things to work on Linux (or them to write some software so you could OC on Linux), that's what I call to support something.
Wow LiPo batteries are quite dangerous to charge when over-discharged... That natural tendency of theirs to self igniting...
Wow LiPo batteries are quite dangerous to charge when over-discharged... That natural tendency of theirs to self igniting...
We all know that the Pyra is a big piece of heating furnace.
This makes problems if the battery temperature goes beyond
60°C (even 50 isn't good) and if the OMAP5 goes beyond 100°C
(internally).
ED has invested a lot of time & work into designing a cooling
system to better distribute heat and get it out of the
plastics case.
While this improves the situation significantly we can't
guarantee that it does not overheat for example if the
Pyra is sitting in the Sahara (or Arizona) in the bright
sun...