Sometimes (but not every time), when booting my Dell Inspiron 530, eth0 will not come up right away. I can boot and log in to Gnome, and the NetworkManager applet shows that the ethernet cable is unplugged. After sitting for 5-10 minutes, it will link up and everything works. If I unplug the network cable and plug it back in, it comes right up. But once it's linked, it works fine and never disconnects after that. I've tried switching to a different port on my switch and a new ethernet cable. So I suspect it's some sort of weird kernel problem. I checked /var/log/messages and the only thing that looks weird is:
Oct 17 07:51:49 obi-wan kernel: e1000e: Intel(R) PRO/1000 Network Driver - 0.3.3.3-k6
Oct 17 07:51:49 obi-wan kernel: e1000e: Copyright (c) 1999-2008 Intel Corporation.
Oct 17 07:51:49 obi-wan kernel: e1000e 0000:00:19.0: PCI INT A -> GSI 20 (level,
[Code].....
But I have a second Inspiron 530 that has the same entry and it works fine. Has anybody seen a problem like this? I've looked around and so far can't find out the exact issue. I've upgraded NetworkManager to the latest version for FC10
my eth0 suddenly stopped working on FC10. i have been using it the whole time, and now it refuses to even ping the gateway. dhclient is not receiving a dhcp offer and when i put in the information manually, it is not even able to ping the gateway. netstat -rn shows that the destination of the router is going nowhere.
i do not think it is the hardware/software, but rather maybe the provider? i am from central europe but just moved up to great britain and working at a friends place. i can connect the mac powerbook without a problem (it will get an ip with dhcp), but not the linux machine.it is a normal ethernet modem connection here. can it be, that it checks MAC addresses or even the computer names? the powerbook also has a really weired IP address: 77.102.xxxxx
i am not using network manager, but command line tools and have nm uninstalled. does anyone have a clue, what this could be about? i am not a newbie, but this is really puzzling me.....
I have a server with two NICs. I tried to bond their network interfaces together, but it bombed out and didn't work, despite the fact I copied the example 100% except for my own numbers for addresses, etc. I decided to go back to a single NIC and let the other unused for now, since I need to get this server running. uh. yesterday.
[Code]...
When I boot up, often times eth0 isn't listed in ifconfig. I'll see eth1, which is just an unused interface at the moment, but eth0 is no where to be found. If I restart the network service, bam. I'm good. Why is it not auto coming up?
We (2 persons) are experiencing a total freeze on first boot after installing fc10 from the 6 CD distro set, and yes, we used the same discs but ran the validate check on each. One machine is a rather ancient Acer G7500G which had previously been running FC3 happily; the other is a very new Dell Notebook (now running FC9 happily). The freeze occurs after the progress bar turns all white. Pressing escape shows that the volume group(s) have been found and are now "active", but that's all she wrote.
The systems can be mounted in repair mode and I notice that there is no "functions" file in /etc/rc.d/init.d but this may be normal for FC10.
The Del owner have officially given up, but before I throw FC10 out and go to 9 also, I though the question was worth asking: has anyone installed FC10 from the CD distro as opposed to the DVD distro successfully?
I installed fedora on my second hdd, the other one had xp before fedora, now in grub it shows xp as other and wont boot into it, just hangs there. SDC is an external drive and sdb is the xp drive as you can tell by the filesystem.
Disk /dev/sda: 320.0 GB, 320072933376 bytes 255 heads, 63 sectors/track, 38913 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x836db2c4 .....
I'm bonding the two NICs on my FC10 server to create a bonded LAG between it and my Cisco Catalyst switch, but during kernel init, the system always give me a notice that "bond0 doesn't appear to exist" so it skips it.Once I log in, I can always open Network Manager and the bond0 interface goes from "Inactive" to "Active" and bond0 immediately works, and I can restart the appropriate network services and everything is fine. But any idea why this bonding wouldn't be initializing during boot up? The ports on the Cisco are configured for hard set speed and duplex and portfast is turned off on them.Is there a guide for best practices for creating LAGs (bonded interfaces) between FC10 and Cisco switches?
I've been upgrading all our servers from FC8 to FC10. One thing that is no longer there are the start up script messages, being replaced by the white and blue line at the bottom.
I like seeing the bootup messages when I reboot (rarely) to make sure nothing went wrong and not having to go into boot.log to check it.
Code: Reading all physical volumes. This may take a while... Found volume group "VolGroup00" using metadata type lvm2 2 logical volume(s) in volume group "VolGroup00" now active Welcome to Fedora
I am using FC10. how do I change the resolution of the "Boot Up" screen? My monitor is 1024x768 capable but my boot screen is 1280x1024. I don't get anything until it finally loads X Windows. When my machine is booting up I cannot see the screen because my monitor can't handle it. When I hook it up to my other monitor (1280x1024 capable) I can see the boot up screen. I'd like to be able to see the boot screen in case there are any errors I need to se. How do I change it?
I am trying to boot kubutu from FC10's grub. FC10 is in MBR, installed kubuntu without grub. Is that a problem for me now? I mean, should I need to install kubutu grub in order to boot from FC10 grub? I tried with these methods but nothing works:
title Kubuntu 8.10 Linux chainloader +1 title Kubuntu 8.10 Linux
I have an Intel DG33TL MB, Intel Core 2 Quad Q9650, 8GB SuperTalent DDR2-800, and 4 Seagate 500GB hard disks. The disks are connected to a 3Ware 9650SE-4LPML and set for RAID0. I partitioned the drive in the following manner: 900GB for XP-Pro x64 (first install), 100 GB XP-Pro (installed second), and the remaining for FC10. After installing FC10 x64 using downloaded DVD .iso I am getting the following error on reboot:
Code: Reading all physical volumes. This may take a while... Volume group "VolGroup00" not found.
I did a fresh install of Fedora Core 10 32bit on my Caompaq Presario AMD 64 laptop which originally only had Vista ultimate 64bit. When I go in to grub and choose windows I get a screen that says:
Windows failed to start... File: windowssystem32winload.exe Status: 0xc0000225 Info: The selected entry could not be loaded because the application is missing or corrupt.
I'm using Fedora 12 on a box with 2 separate NICs in different subnets. The problem is that after a reboot, both NICs always show up as eth0 when you left click on the networking icon on the top right. I have to manually change one of them to eth1 & then things start working.
I have been working on a network problem and have found what the actual problem is. For some reason on boot the netmask for my eth0 is set to be 255.255.255.255 In the network GUI application it is set correctly to 255.255.255.0
I looked in the following files and it is set there correctly too. /etc/sysconfig/networking/devices/ifcfg-eth0 /etc/sysconfig/networking/profile/default/ifcfg-eth0 /etc/sysconfig/networking-scripts/ifcfg-eth0
If I check the box to "controlled by network-manager" the eth0 interface is started at boot but with a netmask of 255.255.255.255. If I uncheck this box then the interface does not come up at boot and I have to go to the GIU application to start it. It still comes up with the netmask of 255.255.255.255
I have to use ifconfig to set it to the right netmask and then everything works until I reboot. "ifconfig eth0 192.168.1.65 netmask 255.255.255.0" How do I get this to work properly? I need it to come up with the correct netmask.
I just finished installing Fedora 12 on a rack mount server. I was modifying the /etc/sysconfig/network-scripts/ifcfg-eth0 file to use a static IP address, but now nothing works. The device does not boot on start up or anything.Currently, ifcfg-eth0 looks like:
Quote:
DEVICE=eth0 ONBOOT=yes BOOTPROTO=none[code].....
The eth0 device does not start on boot; the server does not get the IP address, is not reachable over the network, and will not connect to the internet....
I am trying to sort out some issues following an upgrade from F12.
I have eth0 as the connection I want to use. Prior to the upgrade, this connection was enabled and active at boot.
Now, for some reason after the upgrade it has to be manually enabled at every boot - even though when I go the Network tool, Ethernet Device > General tab - "Activate device when computer starts" is checked.
At every boot time it is inactive.
In all the ifcft-eth0 files, the ONBOOT parameter is set to "yes".
I installed on my system "window xp" and "rhel4 update 2" but due to some problem I removed my windows xp O/S and installed that again after that grub boot menu is not coming so I can't log in properly in linux system.C
I installed Fedora 12 on an Eee PC 1001HA. This laptop has a Ralink RT3070 wireless chipset, for which the driver is not yet in the kernel (still in staging I believe). However I downloaded the driver, compiled it, and installed it. AFAICT, it works fine.
One small obstacle remains: I am uable to get the network interface to come up automatically; I have to run # ifconfig ra0 up. Because of this NetworkManager never sees the wireless interface, making connecting to WAPs a chore.
I created a ifconf-ra0 file in /etc/sysconfig/network-scripts, and it includes the line ONBOOT=yes, but this doesn't do the trick.
i have uninstalled and reinstalled alsa and made sure its not muted, in pulse audio it displays sound is coming out when i play a song, but no sound is actually coming out.. i dont want to go back to windows, but if i cant get sound im going to have to
This on a Vostro 1220 Laptop w/ Intel 5300 wireless:
A.I have long boot up time.I think it's because of the eth0 network search which I don't use.I have an intel wireless 5300 card running.How can I speed up the boot time, i.e. disable or change the eth0 at boot, the searching?
B:When I restart or shutdown, the screen flashes repeatedly and gets some garbled colors along the top before finally rebooting looks like windows ME or something).This vostro has an intel x4500HD vid chipset in it.
C.How do I get into gnome configuration editor to turn on Metacity compositing? Alt-F2 and run gconf-editor doesn't do it. I don't do compiz, but need compositing.
D.I need to install Chromium Browser as it sync my bookmarks.I have RPMforge enabled btw also...how can I do that? I.e. rpm repo for chromium?
This will help me get off to a running start so I can get up to speed on CentOS..
I've looked today on my logs /var/log/message and I find device eth0 entered promiscuous mode I don't remember putting eth0 in promiscuous mode I'm connected to the net thru a router how do i turn that off ?
just as the title states i need to upgrade my os from fc4 to fc10 first let me say i have no physical access to the box. all i have is root ssh access to it. So i need to know the best way of upgrading that will be safe. before i do the upgrade the server will be backed up so i will not loose any files. if the upgrade fails the data center will reload the os with what i need on it. but i would rather not have to format.
After upgrading to F11 I have had a few problems with some applications most like miro I was able to fix by using yum remove and then reinstalling. It appears that after updating some applications have stayed with the fc10 versions despite fc11 versions being available.
I did the yum preupgrade install, all went well, did preupgrade -gui ; did everything fine, then i got the REBOOT now to start updating, clicked and i have just
I recently update FC10 to FC11 and Yum has stopped working. Also, "Add/Remove Software" has no packages listed. And, I have no Software repositories listed. When I try to run Yum I get the following:
There was a problem importing one of the Python modules required to run yum. The error leading to this problem was:
I'm about ready to give up! The modem is a USR5610C it has an rpm file. I guess I'll also need to know if I'm starting it correctly, by restarting the machine.
