On 17/11/2010, at 6:56am, Dale wrote:
...
So now system boots but I can not seem to the network card going.
On the lspci -k I think you mean lspci -nn (there is no switch -k)
...
The man page shows a -k switch here so maybe what you are booting has a older
version or something.
I advise
On 11/17/10 13:57, Stroller wrote:
On 17/11/2010, at 6:56am, Dale wrote:
...
So now system boots but I can not seem to the network card going.
On the lspci -k I think you mean lspci -nn (there is no switch -k)
...
The man page shows a -k switch here so maybe what you are booting has a older
On 11/17/10 13:57, Stroller wrote:
On 17/11/2010, at 6:56am, Dale wrote:
...
So now system boots but I can not seem to the network card going.
On the lspci -k I think you mean lspci -nn (there is no switch -k)
...
The man page shows a -k switch here so maybe what you are booting has a older
On 11/17/10 00:56, Dale wrote:
It appears udev is renaming the network card so I would check the udev
rules. They are usually in /etc/udev/rules.d and I think it starts from
the higher numbers and works its way down.
I'm not much of a expert on udev.
Dale
:-) :-)
You are correct previous
My ASUS A8V motherboard went down so I change it with another ASUS MB M2NPV
along with CPU. Both CPU's were AMD so no need to change flags.
Have two hard drives both SATA 200G and 500G
However, after trying to boot I get:
VFS: Cannot open root device sda3 or unknown-block (0,0)
In grub.conf I
Joseph wrote:
My ASUS A8V motherboard went down so I change it with another ASUS MB
M2NPV along with CPU. Both CPU's were AMD so no need to change flags.
Have two hard drives both SATA 200G and 500G
However, after trying to boot I get:
VFS: Cannot open root device sda3 or unknown-block (0,0)
On 11/16/10 21:04, Dale wrote:
Joseph wrote:
My ASUS A8V motherboard went down so I change it with another ASUS MB
M2NPV along with CPU. Both CPU's were AMD so no need to change flags.
Have two hard drives both SATA 200G and 500G
However, after trying to boot I get:
VFS: Cannot open root
Joseph wrote:
On 11/16/10 21:04, Dale wrote:
Joseph wrote:
My ASUS A8V motherboard went down so I change it with another ASUS MB
M2NPV along with CPU. Both CPU's were AMD so no need to change flags.
Have two hard drives both SATA 200G and 500G
However, after trying to boot I get:
VFS: Cannot
On 11/16/10 21:45, Dale wrote:
[snip]
The BIOS sees both HD but, boot sector is working OK as grub comes up
but then I get a message:
VFS: Cannot open root device sda3 or unknown-block (0,0)
please append a correct root= boot option; here are the available
partitions:
0300 4191302 hda driver:
Joseph wrote:
On 11/16/10 21:45, Dale wrote:
[snip]
The BIOS sees both HD but, boot sector is working OK as grub comes up
but then I get a message:
VFS: Cannot open root device sda3 or unknown-block (0,0)
please append a correct root= boot option; here are the available
partitions:
0300
On 11/16/10 22:40, Dale wrote:
Thanks for the hint.
What should I look for? I think lspci list some chipset, MCP51 but
kernel is not listing anything on MCP51
Try lspci -k from the CD. That should tell you what driver the CD is
using. Then while in the kernel config, just look for that
Joseph syscon...@gmail.com writes:
So now system boots but I can not seem to the network card going.
On the lspci -k I think you mean lspci -nn (there is no switch -k)
No, he does mean 'lspci -k'. The -k switch lists the kernel driver which
is handling each item. If you do this from the CD
Joseph wrote:
On 11/16/10 22:40, Dale wrote:
Thanks for the hint.
What should I look for? I think lspci list some chipset, MCP51 but
kernel is not listing anything on MCP51
Try lspci -k from the CD. That should tell you what driver the CD is
using. Then while in the kernel config, just
=== On Tue, 11/16, Joseph wrote: ===
Anyhow, dmesg |grep eth shows:
forcedeth :00:14.0 ifname eth0, PHY OUI addr. 00:17:31:83:a1:53
udev: renamed network interface eth0 to eth1
Any idea why is it renaming network interface?
I have forcedeth loaded in the kernel but it is not bringing
14 matches
Mail list logo
