https://bugzilla.novell.com/show_bug.cgi?id=678808
https://bugzilla.novell.com/show_bug.cgi?id=678808#c13
--- Comment #13 from Stephan Lauffer 2011-03-14 21:38:35 UTC ---
For comment #11, no, this informations are from one host, for #12, no, only one
NIC is listed with lspci (just depending on -H1 if intel/realtek is shown).
But oh well, looks like my mainboard gonna dies... what happened the last
hours/minutes:
After booting into 11.4 rescue system and again opening the pc tower, checking
every IC, the board, added pci card (the vga adapter, the 3ware and the intel
nic) was:
It is a via based board, no 440BX, so other pci informations were wrong, too.
lspci booting from DVD did _not_ show 440BX hw informations (good) and the
intel nic was shown, too (very good).
I rembered that I added some more, not used kernel modules into the initrd to
become a desaster recovery image from this system booting on other hardware,
too.
So my next step then was: Removing everything else than 3w-xxxx from
/etc/sysconfig/kernel INITRD_MODULES. Plus I removed the intel nic from the
system.
After a boot from HDD with this new initrd showed intel chipset pci ids, too.
The next and last idea was: Loading bios setup defaults... I knew that I
disabled some parts like parport, snd... and I added the snd-via82xx to the
initrd (because I knew this module was right).
So this was the last try. After loading the bios defaults the system did no
longer work. I got no vga signal, the system does no longer boot.
Jiri, if I may get this system working I will add the complete lspci requested
from your comment #12. Now I guess my system (board) was going "mad" and this
caused the trouble. But I never thougth that a diying system would end in wrong
pci ids. I can not say if something loaded a new firmware for any of the
devices.
If I can bring the system back I will let you know. Bad end right of the story
right now. :-/
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.