the install is not really messy and not many packages are installed, this USB key is purposed for hardware/system testing and to diagnose such issues. system is stored on and boots from an USB 3.1 key plugged on an USB 2.0 port, there is no on-disk swap but zram-based swap in compressed ram is used, the GPUs are AGP ones using R300 and R500 technology (pre-TeraScale), the CPU only has one core, no hyperthreading (AMD Athlon 64 FX for socket 939), Also, even without the game running or on a lightweight desktop like LXDE, cycling windows is not smooth and window refreshing is slow enough to be noticeable. When the game is running cycling between windows using Alt-Tab takes a lot of second while it's immediate on 5.4.0-47-generic kernel. When the game is running, a very high load is reported by htop, which does not look like the experience seen on the 5.4.0-47-generic kernel. Note: for unknown reasons, GNOME Shell loads properly on the ATI Radeon 9500 but not on the Radeon X1950 PRO.Įverything is slow. Unvanquished game runs on ATI Radeon 9500 at 3 fps on 640×480 resolution. Unvanquished game runs on ATI Radeon X1950 PRO at 7 fps on 1280×720 resolution, Running GNOME Shell with startx or from a lone xterm started with startx leads to same issues. GNOME Shell never finish to load on Radeon X1950 PRO, either a grey screen is displayed and keyboard shortcuts does not respond, or the top bar is stuck between the center and the top of the screen and the shell does not respond, or the top bar on the top of the screen but the shell does not respond, to get a desktop I run `sudo systemctl stop display-manager` then `startx /usr/bin/lxsession` from a TTY. Unvanquished game runs on ATI Radeon 9500 at 40 fps on 640×480 resolution.Įverything looks consistent with the limits and the age of the hardware. Unvanquished game runs on ATI Radeon X1950 PRO at 70 fps on 1280×720 resolution, GNOME shell loads properly on Radeon X1950 PRO, There is two kernels available on this system: It’s pretty handy.This system runs Ubuntu 20.04, freshly installed 3~4 months ago (July 2020). If you use Dell equipment and that’s of interest to you check with your account team about it. I still find that the SUU disc/ISO method of updating firmware is the most effective on older Dell servers.Īs an aside, I get weekly updates about all firmware, driver, and systems management updates from my Dell SE, in the form of a Product & Driver Update PDF. Moral of the story is that if your older Dell server has a BMC that’s configured with an IP you probably ought to patch it. I always like to know what the problem is, figuring that the bad guys probably already know, and it helps me determine my priority for the fix. Similarly, there’s an urgent update to the Dell-supplied ESXi 4.0 U4 software.ĭell describes the fixes as “Critical Security Update –Urgent BMC Release.” To me that says Dell fixed something that’s remotely exploitable and doesn’t want to say what it was out of fear of tipping off troublemakers. If you’re running a Dell PowerEdge 1900, 1950, 2900, 2950, 2970, 6950, R300, T300, R605, R805, or R905 there are urgent & critical security updates that have been released by Dell on October 15, 2012.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |