Not sure if this is a networking issue or not but I have a Buffalo drive NAS device that I have my mp3 on. I can see it from my Ubuntu laptop, I can see it from my windows laptop. However when I go to my centos system and the networking option under the places menu nothing comes up. I do see a workgroup and a network option. I tried both but just opens a blank folder. How can I get this drive to mount to my centos system?
View 5 RepliesInstalled Centos 5 on IBM T60P laptop. Intel 82573L Gigabit ethernet controller. Keep getting this erro message, "e1000 device eth0 does not seem to be present, delaying initialization."
View 3 Replies View Relatedi finished installing CentOS 5 and managed to connect to the Internet. My Network Interface Card (NIC) is "Atheros L2 Fast Ethernet" and it is not in the device list. anybody can tells me what i should do now to be connected to the Internet?
View 8 Replies View RelatedI'm trying to install DFE-550TX , network device of D-LINK, with no success. I'm using CentOS 5.6.
View 1 Replies View RelatedEthernet card works, but Wireless card activation fails at bootup time. It also fails if I try it again from the Network Configuration UI.
I have provided some output I got from initial exploration.
I upgraded to a recent version of the 2.6 kernel.
uname -a: Linux localhost.localdomain 2.6.28.7 #1 SMP Sat Mar 14 19:04:11 PDT 2009 i686 i686 i386 GNU/Linux
I have installed the correct firmware hopefully.
cd /lib/firmware ls
Output is:
I do have the bcm* files for firmware.
output of lspci is:
Last two lines show the that Wireless card BCM4312 is visible.
I just installed Centos 5.4 on the 2nd partion of my hard drive. I have an ethernet card in my machine (a 3Com Corporation 3c905 100BaseTX [Boomerang] card), but I need to be able to use my wireless USB device I bought from my local phone company (Qwest)...because I will not always have the luxury of plugging in to a hard-wired connection. The USB wireless device works fine in Windows, but I need to be able to use it on my newly installed Centos 5.4 partition.
Here's some info:
[Code]...
I have installed live cd on usb pendrive. Everything works great. How can I find out which device driver it is using? Where are the device driver files stored? How do you specify the device driver when mounting a device?
View 3 Replies View RelatedI have a desktop that has a d-link DWL-520 wireless card, which was working under Windoze. Today I installed Centos 5.4 on the system , which went cleanly. I then used Network Configuration to set up the wireless card. I specified to use DHCP, set the SSID and authentication password. When I tried to activate the card I get these error messages
Error for wireless request "Set Mode" (8B06): SET failed on device wlan0 ; Operation not supported. Error for wireless request "Set Encode" (8B2A): SET failed on device wlan0 ; Invalid argument. Error for wireless request "Set Encode" (8B2A): SET failed on device wlan0 ; Invalid argument. Determining IP information for wlan0.
The hardware manager seems to have correctly identified the card and chipset, (Intersil Prism 2.5) and installed driver hostap_pci which came with the distro. This web site seems to suggest that this is the correct driver: [URL] searching forums I've found a few references to these errors, but they were from several years ago, and for different distros and cards. I did find a reference to using Network Manager to configure the card instead of Network Configuration. I started the NM service and configured a connection using it instead, but still no luck.
[Code]....
I have had a Supermicro X7DCL-3 motherboard based machine, running CentOS 5.2 x86_64, recently upgraded to 5.3.Strangely enough, although I must have installed the 5.2 using DVD disk, the running system does not show the DVD drive. The machine was not used very much so I noticed that only today, after the update. There is no trace of it in 'dmesg', thera are no /dev/cd* and/or /dev/dvd* devices. The IDE controller is IT8213 (as shown by 'lspci'). In 5.2 kernel (2.6.18-92.el5-x86_64) lspci says "unknown device". I have checked the /usr/src/kernels/*/.config files and both kernels (5.2 and 2.6.18-128.el5-x86_64 of 5.3) seam to have the support for that controller added into the kernel:CONFIG_BLK_DEV_IT821X=yAny idea why it is not working? The Supermicro has apparently noticed this also as their OS compatibility chart lists the IDE interface for that motherboard as supported up to RHEL 5.1 but not for 5.2.
View 2 Replies View RelatedI'm experimenting with a K8055 board, connected through USB to our Asterisk server,running on CentOS. If I connect the device I can see it being connected by watching /var/log/messages. Also the device is mentionned in /proc/bus/usb/devices. But when I do lsusb the device isn't showing up and it should be showing up! If it is not listed with lsusb, I can't connect to it through the k8055 executable...
View 1 Replies View RelatedI have been using SLES 10 SP1 so far with about 6TB Raid system without problems.I have upgraded the OS to CentOS 5.3 i386 and I have noticed the kernel can not recognize raid system larger than 2TB.Is there any parameters that I have to set ? or the i386 distribution simply does not support larger raid, so I have to use x86_64 version, instead?
View 1 Replies View Relatedi install kernel rpm after i boot that kernel network not working kernel name : kernel-rt-trace-2.6.24.7-132.el5.centos.i686 [URL] error "Bringing up interface eth0: Device eth0 has different MAC address than expected, ignoring."
View 1 Replies View RelatedI installed ZTE MF 626 modem in my F10 with kernel 2.6.27.12-170, i run usb_modeswitch and so far things happened normally. Watching through /var/log/messages it says that F10 detects two port device for this modem: ttyUSB1 and ttyUSB2, and in the sequence it disable port ttyUSB1 BUT Network Manager still set this port.I mean, when i connect via wvdial appointing to ttyUSB2 i get connection, but Network Manager fails to do it appointing to ttyUSB1. How to change device port in Network Manager?
View 1 Replies View RelatedWe are having issues with LVM on CentOS 5.4 both 32bit and 64bit on one particular machine. I just can't get my head around it. Usually a device in /dev/ is created when a LVM Volume Group is created. e.g. if you add a volume group called foo, you would have /dev/foo to work with to access LVs inside the volume group.
For some reason it's not being created. The udev service is running, the volume group is created ok, I cant see anything strange in logs or strace.
I knew how to mount it and I was able to view files and folder in it but I don't know how to copy files using CUI (Command not GUI) mode. I have six separate iso files and I want to make a DVD in the removable device.
View 1 Replies View RelatedI am trying to copy some files onto a flash card. The first thing that i do is mount to the flash card:
mount /dev/sdc1 /mnt
then i try and copy a file
cp dev.bin /mnt
but i get a message saying:
cp: writing `/mnt/dev.bin': No space left on device
I was able to copy some files before but i cant seem to do it anymore.
how can i delete everything thats on the flash card so that i can copy files onto it?
I'm using CentOS 5.4 x86_64 on my Dell Inspiron 1440 laptop. How can I configure my bluetooth device through CentOS?
View 5 Replies View RelatedI have an External HDD which has a Data directory in it and I want to move to this directory to use the script mkdvdiso.sh to combine six separate iso file (of CentOS, of course). The syntax of this script is:./mkdvdiso. sh /source /destination/DVD.iso.I don't know what to replace source and destination parameters with.
View 5 Replies View RelatedI have added CentOS5.5 x86-64 to a linux box that already contains installations of Ubuntu 9 and SL 5.2. Grub2 was installed with Ubuntu and is on the MBR of the disk. I did not install grub with anaconda/Cent. Grub update in ubuntu finds the Cent install and addes it to the grub.conf, and Cent appears in the grub menu at boot. If I select Cent, I get the following error.
VFS: Cannot open root device "sda7" or unknown-block(0,0)
Please append a correct "root=" boot option
Below is the output of boot_info_script, which gives the relevant boot file data. There are still grub conf files on the SL install, but grub is not installed there anymore.
Boot Info Script 0.55 dated February 15th, 2010
=> Grub 2 is installed in the MBR of /dev/sda and looks on the same drive in partition #6 for /boot/grub .....
sda3/boot/grub/grub.conf:
# grub.conf generated by anaconda
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You do not have a /boot partition. This means that all kernel and initrd paths are relative to /, eg.
# root (hd1,2)
# kernel /boot/vmlinuz-version ro root=/dev/sdb3
# initrd /boot/initrd-version.img
When CentOS boots up, it tries to determine the IP for a network device (eth0) and fails.
'Determining IP information for eth0... failed; no link present.'
I'm curious to know how, after booting up, I could set the IP information for a wireless device, wlan0, manually. Another way of putting this questions is: if CentOS is able to determine IP information for a network device on bootup, what settings is it configuring exactly?
Have VMWARE workstation 7. Have to extend partition /dev/sda1 mounted to /home/user
1. Originally /dev/sda was 10gb I've extended device via VMWARE to 30gb.
2. When I do: fdisk /dev/sda it tells me that /dev/sda 30gb
3. when I check: df -h /home
it shows 10GB
4. How I can make Linux see the 30gb at /home/user?
i have 5.4 installed on a super-micro server motherboard (has two gigabit ether ports). when i boot while its initializing everything it gets to the "starting eth0" and just stays there?
right before it boots up and says press any key for options i press a key and choose "centos (2.6.18-164.el5)" and it boots up fine but when i choose "centos (2,6,18-164.el5xen)" the problem occurs. and that is the default boot option.
I have a LVM snapshot that triggers these kernel errors when any LVM-related commands run:
Jul 6 10:31:38 itmanager kernel: attempt to access beyond end of device
Jul 6 10:31:38 itmanager kernel: dm-28: rw=0, want=66156996183394672, limit=25165824
dm-28 is the snapshot volume in device mapper. I think this error is generated because most LVM commands will check the first 4K of various drives and volumes for LVM metadata and labels, but attempts to read any of the first eight sectors (ie: 4K) of this particular snapshot logical volume trigger this error.The most interesting thing is that the snapshot is 25165824 sectors long (12G), but attempts to access the first eight sectors result in an attempt to access sector 66156996183394672!I've obtained an info dump from getinfo.sh disk, and added the output from lvs. You can find the results here:URL.. It's not as if the sectors that back the first 4K of the volume are corrupt, either: the read request never hits any hardware because the read request is attempting to read a non-sensical sector, instead of the correct sector. Perhaps the COW metadata for the snapshot is corrupt?
How do I find the cause of this problem?Is this a critical error that I should file a bug report for?I first noticed this some time after turning the machine on Sunday afternoon.As far as I can tell from the logs, the shutdown the previous evening was normal.I use LVM fairly heavily on this machine, and this is the first time I've ever seen this kind of problem..I've worked around the problem by copying the first eight sectors from the Origin volume, and the rest from the Snapshot volume, to a new normal logical volume.However, I'm still concerned about how this error occurred in the first place.
We ran out of space on our server hard drive, so I installed 2 x 1GB drives, set them up as a software RAID1 array, copied the contents of /home to it, mounted it as /home for testing. Everything OK, so I unmounted it,deleted the contents of the /home folders (don't worry, we're backed up), then remounted the array. Everything was fine until we rebooted.Now I can't access the array at all; during booting the error "mount: special device /dev/md1 does not exist" comes up twice, and manually trying toe same issue.The relevant line from fstab reads:/dev/md1 /home ext3 defaults 0 0.However, using webmin shows only md0, the RAID0 device on which the OSD was originally installed.There is no /dev/md1 device file.The mdadm.conf file reads as follows:
# mdadm.conf written out by anaconda
DEVICE partitions
MAILADDR root
ARRAY /dev/md0 level=raid0 num-devices=2 uuid=76fd4050:fb820568:c9bd3a59:ad3e70b0
I installed the following packages:
ieee80211-kmdl-2.6.18-164.10.1.el5-1.2.18-22.el5.i686.rpm
ipw2200-kmdl-2.6.18-164.10.1.el5-1.2.0-45.2.0.1.el5.i686.rpm
from [URL] How to remove them completely? The ipw2200 driver complains that it could not agree with certain symbols in ieee80211 module. Before taking another route, I would like to know how to completely remove the files installed by these driver packages.
I'm experiencing some strange issues with a C5 installation on a Dell server with a QLA2460 HBA. When it boots up, I got a lot of these messages on dmesg:
[Code]...
I am trying to prevent the dm_mod and friends from loading during install.I am installing by PXE boot with NFS and kickstart files over http. This works fine for other machines.Ok, I have a Dell PowerEdge 2900 III with 8gig ram, PERC 6/i raid controller.The raid has 8 1TB drives in it, so the total size of the device is >2TB.There is also an SATA drive, which is NOT on the raid controller.
The problem is, I want to install CentOS on the SATA drive. The SATA drive comes up as a device-mapper drive, with a big crazy device name.This is ok, but the problem is, when the system goes to boot, it just says 'missing operating system'.I can't boot from the raid because it is large enough to require a GPT partition, and CentOS says it can't boot from a GPT partition.The SATA drive would work FINE if I could just prevent the damn device mapper from loading, so that I could install on the SATA drive in ordinary SATA mode.
I have tried re-squashing the stage2.img with /etc/modprobe.conf with alias dm_mod off and such, no luck.I also tried adding an /etc/modprobe.d/blacklist file, that did not work either.I also tried putting blacklist= dm_mod in the kickstart file, but that seems to be a fedora-only option and it kills my install. any ideas on preventing the dm_mod et. al. from loading at install time??
I just installed centos 5.1 on my laptop. Then i upgraded it to 5.3. The problem that i am facing is that at a time only one application can use the audio device. Is this some kind of driver problem or an error in Centos? If one application is using the audio device and if i start the other application that also want to use the audio device it simply gives an error like audio device is locked by other application and is muted. In windows XP my audio device is shown as Sigmatel Audio.
View 1 Replies View RelatedWhen I try to install CentOS 5.3 and when this dialog. Select device Driver to load. I try to install it on ASUS Server.
View 8 Replies View RelatedI just noticed, on both of my CentOS 5.3 servers, within grub, root shows (fd0)device.map = (hd0) /dev/sda and nothing else.
View 4 Replies View Related