I was reluctant to do the upgrade until after the semester but I just did it. Fairly easy switch out to be honest. Got my existing Windows switched over to the new hardware with no hiccups and the driver bundle installed. I still want to visit AMD’s website and update drivers for processor/graphics chip. After that and some Windows updates, I’ll put together my Windows environment with apps and virtualization. I probably won’t bother with dual booting Linux until the end of next week.
I have had two DPC_WATCHDOG_VIOLATIONS BSODs on my prebuilt 7840U Windows 11.
This was after Framework’s 3.03 firmware and driver package was installed. Between first and second BSOD I went to AMD’s website and did the autodetect driver install, so that didn’t resolve it either.
Opening a support ticket This is a replacement device for another laptop (non-Framework) that was randomly BSODing.
@NickCao I suppose the good thing here is that if there’s a screen fault and you need to RMA it, it’s a simple replacement process and doesn’t need a whole new machine sending out.
What hardware & software are you using it with? Any games or older applications?
I think I was able to tie my own BSODs to when I tried playing Deus Ex: Mankind Divided out of nostalgia. That game is known for BSODs when very specific settings aren’t set and there’s more than 4 cores assigned to it. I have since changed settings accordingly and seemingly alleviated myself of the issue.
One was on battery, one was plugged in. Only common denominator I can identify is Firefox was running at the time. The first time I was running Remote Desktop/WSL 2.0/Handbrake as well, the second time was simply browsing the web on battery.
Just got my board today an did the upgrade. I installed Windows and Fedora (dual boot) and so far everything is working flawlessly.
After I installed Windows, I loaded up the bundle drivers and then double checked my bios. After that I went to AMD and updated my chipset driver. All other Windows updates took place and everything is running smooth. As far as Linux, Fedora is installed but I’ve yet to use it much and haven’t installed any apps on it.
I’ll keep running it through the paces and post anything here if I run into problems but I’m keeping my fingers crossed as I’m typing this because I know so many others have had problems.
Well for me today will be the day I put the machine through its paces so hopefully my mileage is different. When I updated the drivers I avoided using Adrenaline, just updated the driver by itself. Used AMDs product search for the CPU and it brought me to a page with the drivers.
My laptop showed up today and I’ve spent the past couple of hours getting it set up. This will be a linux only device and for now I have installed Fedora 39 KDE. I tend to tinker a lot so this might end up changing a few times before I settle.
So far everything has been smooth and I’m impressed with the build quality and display. Coming from a refurbished Dell Lattitude E7440, the Framework is a major upgrade!
two days in and the bottom left side of my trackpad is significantly lower than the right.
Everything still works, but boy is it noticeable. Probably have to open a ticket with FW on this one, I haven’t taken off the input cover since putting it together, and it was level when I got it.
Received my Ryzen 7840 DIY as estimated (on Monday), but didn’t have a chance to play with it till yesterday.
Assembly was a breeze (but yes NVME screw was a bit tight, however, FW screwdriver did the job; I was extra careful though)
Expansions cards - for me does seem rather hard to get them out.
BIOS password setting is perculiar*
Setting it up with NixOS
Have not heard the fan yet, but I was not pushing my fw either
*Limit to 10 char limit is odd; also strangely BIOS did not recognise my password. I think it did not like ! in the password when I was trying to log in afterwards (although I was too lazy to verify this, so there is a chance I messed up typing it in; would be nice if BIOS actually showed the password when setting it up), so I had to reset BIOS.
On top of that it has character restrictions. Oddly, it said must contain at least 1 character. But then followed with must contain at least one capitol letter, one special character, etc. This all needs to be completely removed on next BIOS update.
I understand what you’re saying now. I read it to mean “one normal character, one capital letter and so on”. Definitely means there could be clarity provided in a future update if we are interpreting the same words with different meanings.
I have finally found time to move my system from my old laptop to the Framework. And… I’m happy Everything I need works, even the not-so-posh (a.k.a. the cheapest I could find) mokin docking station charges the laptop and outputs the HDMI with no issues.
The only snag was the pvmove from an external enclosure, which overheated my old SSD and I had to revert the config and try again.
What must a man do to get the attention of the framework tech support? It appears that I am the only unfortunate customer who received a faulty laptop the last week. I tried troubleshooting myself, reseat memory, plugin to external monitor, plugin motherboard to different framework laptop and still no display. I opened a ticket on Monday, and as of today, I haven’t heard back. I would be grateful for any advice.
Patience. I realize that it can be frustrating but the Support team would be inundated with requests because they must have shipped hundreds (if not thousands) of laptops.
It took Support 5 days to respond to my request (my input cover was not working) but once they responded, the problem was diagnosed in a few hours and a replacement was shipped in 2 days. Granted, my problem my have been an easy one to resolve so YMMV.
I’m at 18 days since shipping so far, and it’s been at the local distribution hub for 9 days with no update.
Not sure if/when I should try to contact FedEx or Framework about it
This is a replacement device for another laptop (non-Framework) that was randomly BSODing.
