similar to: CentOS 6.0: panic installing i386 on old Acer Desktop

Package: linux-2.6 Version: 2.6.32-26~bpo50+1 Severity: important --- Please enter the report below this line. --- I've installed the following packages an lenny, which are working well on other maschines. # dpkg -l | grep xen | grep bpo ii libxenstore3.0 4.0.1-1~bpo50+1 Xenstore communications library for Xen ii linux-image-2.6.32-bpo.5-xen-686 2.6.32-26~bpo50+1 Linux 2.6.32 for modern

Okay, this applies particularly to SYSLINUX, not ISO/PXE/EXTLINUX. If you have a system on which 2.13 boots and 3.0x don't, I would like to get as much information as possible about it. In particular, I would like to know: - What device are you booting from (floppy, USB, IDE harddrive...) - Motherboard manufacturer/model - CPU manufacturer/model (a dump of /proc/cpuinfo would

This series of patches adds support for SMBIOS to HVM domU''s. This is needed by many systems management applications, most often to get a useful UUID inside of an HVM domU. They have been tested on changeset 10486:5610d916ad1be231bd6b6c7ae26665374623a90c of xen-unstable. Any comments or help would be greatly appreciated. Andrew ===== sample output from dmidecode: # dmidecode 2.7

Hi every one, I am trying to load a custom kernel with Syslinux on special purpose pc. Surprisingly Syslinux-4.06 boots my kernel, initrd and finally the OS perfectly from an SD-Card. The problem arises when I use the Syslinux-6.03 where the syslinux hangs right at the beginning After I see the message 'Loading vmLinuz0 ...' I read a few posts on your forums and figured out it has to do

In Timo's thread about RAM today, I noticed dmidecode and I got the data for my Dell Dimension 2400 (Celeron CPU) box, which is below. I won this box in a raffle, during February 2005. After I got the box, I got conflicting information, from Crucial.com and from Dell Latin America, regarding the maximum RAM configuration. To be conservative, I bought two 256 MB DIMMS from Crucial.com, early

I have a brand new ASUS MB model M2N-MX which is giving me issues when installing Centos 4.4 64 bit I initially had problems with finding the SATA drives but I resolved that issue by simply selecting the NVIDIA SATA (sata_nv)driver from the list of drivers during the initial install. The install seemed to go fine after that as the installer uses the Generic VESA video driver during the install,

Hi I have a dell 770 bios sees 8g I beleive Ive *vi /etc/yum.repos.d/CentOS-Base.repo* *[centosplus]name=CentOS-$releasever - Plusmirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=centosplus

Am 19.11.2013 11:36, schrieb Laine Stump: > On 11/15/2013 03:35 PM, Thomas Kuther wrote: >> Hello, >> >> I'm trying to migrate a working qemu command line configuration to >> libvirt. >> The part I'm currently failing on is: >> >> $ qemu-system-x86_64 -M Q35 ... -device >> vfio-pci,host=05:00.0,bus=pcie.0 >> >> The right

https://bugs.freedesktop.org/show_bug.cgi?id=50830 Bug #: 50830 Summary: GeForce 8500 GT Connectors Reversed Classification: Unclassified Product: xorg Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component:

On Sun, Sep 6, 2020 at 8:52 PM Marc MERLIN <marc_nouveau at merlins.org> wrote: > > Ok, I have an update to this problem. I added the nouveau list because > I can't quite tell if the issue is: > - the PCIe changes that went in 5.6 I think (or 5.5?), referenced below > > - a new issue with thunderbold on thinkpad P73, that seems to be > triggered if I have a USB-C

First off, the current state of support for Maxwell (GM107/NV110) is not very useful to end-users. It's especially not useful if it's a 3d accelerator card without outputs (as yours appears to be), since acceleration is not supported in 3.15 out of the box. You'd have to figure out how to extract the context switching firmware from the blob driver and load it in nouveau. I'm told

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I suspect that the gold layer on edge connectors 30-odd years ago was a lot thicker than on modern cards. We are talking contacts on 0.1" spacing not some modern 1/10 of a knat's whisker. (Off topic) I also remember seeing engineers determine which memory chip was at fault and replacing the chip using a soldering iron. Try that on a DIMM!

Yes, you are right - the Intel-chip is connected to the display, it just offloads 3D work to do to the nVidia-chip, which isn't even to tell how to get the EDID. I just wanted to try it out, simply for two reasons: 1. I heard that nouveau now "supports" the chip, and since I got the hardware, I wanted to try it out - just for the fun of it. :) 2. As far as I am informed, a way to

Hello, guys. First apologize my flaws, I am not a native English speaker and thus am prone to stupid errors. My box is an ASUSTek Notebook with Optimus capability (no, this is NOT about Optimus, I don't try to use Optimus yet, so please don't switch off here) with a running Gentoo. The first GPU is an Haswell-based Intel chip, the second one is a nVidia GeForce GTX 850M, the chip is a

Ok, I have an update to this problem. I added the nouveau list because I can't quite tell if the issue is: - the PCIe changes that went in 5.6 I think (or 5.5?), referenced below - a new issue with thunderbold on thinkpad P73, that seems to be triggered if I have a USB-C yubikey in the port. With 5.7, my issues went away if I removed the USB key during boot, showing an interaction

How do you detect ECC memory errors when CentOS is booted? Just had a strange hardware error where a server machine hang during anaconda install it passed memtest86 test but the bios dmi log showed dimm bank 1b had failures. Now I wonder what would happen if a machine running in production would get such problems, how do you detect it without having to go into bios? Hints on what to use? Chris

Prowling around in the system logs this morning I discover the following entries: May 27 09:48:27 vhost01 mcelog: Cannot open logfile /var/log/mcelog: Permission denied May 27 09:48:27 vhost01 mcelog: failed to prefill DIMM database from DMI data May 27 09:48:27 vhost01 mcelog: Cannot bind to client unix socket `/var/run/mcel og-client': Permission denied and later: vhost01 setroubleshoot:

After update from centos 6.6 to centos 6.7 and reboot it, I have get a lot of this error into /var/log/messages: > May??3 11:27:20 s-virt kernel: EDAC MC0: CE row 2, channel 1, label > "": (Branch=0 DRAM-Bank=2 RDWR=Read RAS=6093 CAS=896, CE Err=0x10000 > (Correctable Patrol Data ECC)) > May??3 11:27:21 s-virt kernel: EDAC MC0: CE row 2, channel 1, label > "":

I downloaded the Live DVD for CentOS-6.5 and burned a DVD-R using a CentOS-6.5 desktop. To test the validity of the new DVD I then rebooted the same desktop using the same Live DVD. No matter which Live DVD boot option I choose I see this after the splash screen completes the Circle (sounds like a good title for a novel). <--- Kernel panic - Not syncing - Attempting to kill init! Pid: 1,

List- I know this may be slightly off topic and if so tell me to hit up the emu-discuss mailing list, but does anyone know how to detect the difference between a guest that is being fully emulates using qemu and a guest that is running para-virtualized using KVM? I have and when I inspect the CPUs I see the following.... # cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family