Discuss

discuss@lists.centos.org

34758 discussions

kernel 2.6.9-42.0.8.EL error while booting - CentOS 4.4
by Indunil Jayasooriya 08 Feb '07

08 Feb '07

Hi , I am ruuning Senmail with MailScanner on CentOS 4.4. It has updated to kernel 2.6.9-42.0.8.EL from its past kernel 2.6.9-42.0.3.EL. Now the Server can not boot up and gives the below error. mkrootdev: label / not found Mounting root filesystem mount: error 2 mouting ext3 switchroot: mount failed: 22 Kernel panic - not syncing: Attempted to kill init! But I can boot up from its last kernel 2.6.9-42.0.3.EL. I have booted it up from that kernel. But I wnat to rectify that new kernel error in order to boot from that kernel. Help needed. -- Thank you Indunil Jayasooriya -- Thank you Indunil Jayasooriya

3 4

USB-HDD cannnot connect automatically
by n.uryu 08 Feb '07

08 Feb '07

Hi all, I got a USB-HDD, but it doesn't looked like connect and cannot mount it just after PC boot. But insert and remove a usb cable from PC, it connect (with hotplug?) Is there any good how-to's for getting a usb-HDD to auto connect when It is booted the computer? lsmod is following: [lsmod of just after boot] Module Size Used by Not tainted parport_pc 19076 1 (autoclean) lp 9028 0 (autoclean) parport 37088 1 (autoclean) [parport_pc lp] autofs 13364 0 (autoclean) (unused) e1000 71712 1 floppy 58160 0 (autoclean) microcode 4724 0 (autoclean) keybdev 2976 0 (unused) mousedev 5524 0 (unused) hid 22212 0 (unused) input 5888 0 [keybdev mousedev hid] ehci-hcd 20104 0 (unused) usb-uhci 26412 0 (unused) usbcore 79392 1 [hid ehci-hcd usb-uhci] ext3 91592 9 jbd 52336 9 [ext3] [lsmod of insert and remove a usb cable] Module Size Used by Not tainted sd_mod 13776 2 (autoclean) usb-storage 74624 1 scsi_mod 108968 2 [sd_mod usb-storage] parport_pc 19076 1 (autoclean) lp 9028 0 (autoclean) parport 37088 1 (autoclean) [parport_pc lp] autofs 13364 0 (autoclean) (unused) e1000 71712 1 floppy 58160 0 (autoclean) microcode 4724 0 (autoclean) keybdev 2976 0 (unused) mousedev 5524 0 (unused) hid 22212 0 (unused) input 5888 0 [keybdev mousedev hid] ehci-hcd 20104 0 (unused) usb-uhci 26412 0 (unused) usbcore 79392 1 [usb-storage hid ehci-hcd usb-uhci] ext3 91592 10 jbd 52336 10 [ext3] Enviroment is following: [Enviroment] - Computer : FM V ESPRIMO C5200 (Fujitsu) - USB-HDD : I-O DATA USB-HDD - OS : CentOS version.3 If need to other information about problem solving, I will post. -- Regards Naoaki Uryu

1 0

Problems loading CentOS 4.4 on ASUS M2N-MX mobo
by Ed Burgstaler 08 Feb '07

08 Feb '07

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, however, upon the restart after the install, the server then completely locks up. I can only assume it is at the point of loading the video driver although I really don't know what CentOS loads after the "acivating local loopback" section, because that is where it freezes on the screen. I'm thinking that the install to the SATA drive went well since it boots from the drive though it doesn't exactly boot completely. I have tried reinstalling several times already with the same negative results. Would appreciate any help that someone could offer in getting this working with this new MB. Here are the specs of the MB: -Key Specifications: NC-AS-M2N-MX Form Factor: uATX, 9.6" x 8.8" CPU - Support AMD Socket AM2 Athlon 64 X2 / Athlon 64 FX / Athlon 64/ Sempron Chipset - NVIDIA nForce430/GeForce6100 Front Side Bus - 2000 / 1600 MT/s Memory - Dual channel memory architecture - 4 x 240-pin DIMM, support max. 4GB DDR2 800/667/533 ECC and non-ECC,un-buffered memory VGA - Integrated GeForce 6100 GPU - High Definition Video Processing with max. resolutions to 1920 x 1440 Expansion Slots - 1 x PCI Express x16 - 1 x PCI Express x1 - 2 x PCI Storage/RAID - NVIDIA MCP61P - 1 x UltraDMA 133/100/66/33 - *4 x Serial ATA 3Gb/s with RAID 0, RAID 1, RAID 0+1, RAID 5 & JBOD NVIDIA MediaShield? RAID 0, 1, 0+1, 5 and JBOD span cross Serial ATA drives LAN - NVIDIA MCP61P built-in Gigabit MAC with external Attansic PHY Audio - ADI AD1986A High Difinition Audio 5.1channel CODEC - Support Jack-Sensing and S/PDIF out interface USB - 10 USB2.0/1.1 ports Manageability - WfM 2.0, DMI 2.0, WOL by PME, WOR, PXE, Chassis Intrusion BIOS - 4Mb Flash ROM, Award BIOS, PnP, DMI2.0, WfM2.0, SM BIOS 2.3, ACPI 2.0 Overclocking Features - SFS (Stepless Frequency Selection) from 200MHz to 230MHz at 1MHz - increment - Adjustable Voltage : - *core: @ 0.025V stepping - *chipset: 2- stepping - *ddr: 4- stepping - Overclocking Protection: - ASUS C.P.R.(CPU Parameter Recall) Special Features - ASUS Q-Fan - ASUS My Logo 2 - ASUS CrashFreeBIOS2 - ASUS EZ Flash 2 Back Panel I/O Ports - 4 x USB 2.0 ports - 1 x RJ45 - 1 x COM1 - 1 x PS/2 Mouse - 1 x 5.1 channel Audio I/O - 1 x PS/2 Keyboard Internal I/O Connectors - 3 x USB 2.0 connector supports additional 4 USB 2.0 ports - 1 x S/PDIF output connector - High Definition Front panel audio connector - 4-pin CPU Fan / 2*Chassis Fan connectors - Chassis Intrusion connector - CD audio-in connector - 24-pin ATX power connector - 4-pin ATX 12V Power connector Accessories - 1 x Serial ATA cables - 1 x FDD cable - 1 x SATA power cable - 1 x I/O Shield - 1 x UltraDMA 133/100/66 cable - User's manual - 1 x COM1 - 1 x PS/2 Mouse - 1 x 5.1 channel Audio I/O - 1 x PS/2 Keyboard Internal I/O Connectors - 3 x USB 2.0 connector supports additional 4 USB 2.0 ports - 1 x S/PDIF output connector - High Definition Front panel audio connector - 4-pin CPU Fan / 2*Chassis Fan connectors - Chassis Intrusion connector - CD audio-in connector - 24-pin ATX power connector - 4-pin ATX 12V Power connector Accessories - 1 x Serial ATA cables - 1 x FDD cable - 1 x SATA power cable - 1 x I/O Shield - 1 x UltraDMA 133/100/66 cable - User's manual

5 4

RE: [CentOS] Problem with 2.6.11.4 kernel and e1000 driver -Correction
by Mark Hull-Richter 08 Feb '07

08 Feb '07

None of that worked. When I edited out the HWADDR lines, I got this instead: Feb 7 06:36:34 sparenode1 network: Setting network parameters: succeeded Feb 7 06:36:34 sparenode1 network: Bringing up loopback interface: succeeded Feb 7 06:36:34 sparenode1 ifup: e1000 device eth0 does not seem to be present, delaying initialization. Feb 7 06:36:34 sparenode1 network: Bringing up interface eth0: failed Feb 7 06:36:34 sparenode1 ifup: e1000 device eth1 does not seem to be present, delaying initialization. Feb 7 06:36:34 sparenode1 network: Bringing up interface eth1: failed Hwconf did not change significantly when I ran kudzu, so I have no idea what's going on here. Again, this works exactly as is on 32-bit builds. It only fails on the 64 bit build. -----Original Message----- From: centos-bounces(a)centos.org [mailto:centos-bounces@centos.org] On Behalf Of Radu Radutiu Sent: Wednesday, February 07, 2007 5:47 AM To: CentOS mailing list Subject: Re: [CentOS] Problem with 2.6.11.4 kernel and e1000 driver -Correction Editing out HWADDR should fix your problem. Another possible solution is to check that the value in the HWADDR line in /etc/sysconfig/network-scripts/ifcfg-ethX is the same as listed in the /etc/sysconfig/hwconf for the corresponding network interface. Also make sure that the files /etc/sysconfig/networking/devices/ifcfg-ethX and /etc/sysconfig/network-scripts/ifcfg-eth0 are hard links to the same file. You can regenerate the content of the /etc/sysconfig/hwconf by removing it and running kudzu again.

2 1

Support of Marvel Yukon Gigabit Ethernet
by devel 08 Feb '07

08 Feb '07

Hello, Marvel Yukon Gigabit Ethernet is supported by CentOS ? -- -- Devel in Precio http://www.pas-world.com

4 3

Named Troubles
by Matt 07 Feb '07

07 Feb '07

I did a CentOS 4.4 fresh server install. Using it to run Squid. Named is also running but I get this error. [root@sj ~]# /etc/init.d/named status rndc: connection to remote host closed This may indicate that the remote server is using an older version of the command protocol, this host is not authorized to connect, or the key is invalid. [root@sj ~]# /etc/init.d/named restart Stopping named: [ OK ] Starting named: [ OK ] [root@sj ~]# All I want it a caching DNS server for Squid and a few hundred computers to use. Is this error going to be an issue? If so, how do I fix it? Matt

2 1

tzdata - extra info.
by Steve Campbell 07 Feb '07

07 Feb '07

Sorry for the extra info required, but I had digest mode turned on and wouldn't have received the mailing till tomorrow. I have since updated the data manually, but after 'yum update tzdata' was run, the zdump -v for EST5EDT and America/New_York all still showed a date of April 1, instead of March 11. After manually fixing, it is correct. This was mostly a question about why yum provided a tzdata that was for a 2006a rpm instead of the 2006g or later when I did the yum. Thanks Steve Campbell campbell(a)cnpapers.com Charleston Newspapers

3 2

Folding @Home team
by Scott Silva 07 Feb '07

07 Feb '07

I see team Centos will soon be approaching the #150 spot. the_dobc -- MailScanner is like deodorant... You hope everybody uses it, and you notice quickly if they don't!!!!

2 1

Re: tzdata - extra info.
by Steve Campbell 07 Feb '07

07 Feb '07

Ralph, Of course not - I didn't get the fasttrack rpm. Sorry for the noise. Steve Campbell campbell(a)cnpapers.com Charleston Newspapers ----- Original Message ----- From: "Steve Campbell" <campbell(a)cnpapers.com> To: "CentOS Users" <centos(a)centos.org> Sent: Wednesday, February 07, 2007 2:17 PM Subject: tzdata - extra info. > Sorry for the extra info required, but I had digest mode turned on and > wouldn't have received the mailing till tomorrow. > > I have since updated the data manually, but after 'yum update tzdata' was > run, the zdump -v for EST5EDT and America/New_York all still showed a date > of April 1, instead of March 11. After manually fixing, it is correct. > > This was mostly a question about why yum provided a tzdata that was for a > 2006a rpm instead of the 2006g or later when I did the yum. > > Thanks > > Steve Campbell > campbell(a)cnpapers.com > Charleston Newspapers

1 0

RE: [CentOS] qmail on CentOS 4.4
by Mark Schoonover 07 Feb '07

07 Feb '07

R Lists06 wrote: >> I've tried to install qmail 1.03 on CentOS 4.4 using the command: >> >> # make setup check >> >> and I received this error: >> >> ./load auto-str substdio.a error.a str.a >> substdio.a(substdo.o)(.text+0x43): In function `allwrite': >>> undefined reference to `errno' >> collect2: ld returned 1 exit status >> make: *** [auto-str] Error 1 >> >> Can anyone please help? >> >> TIA >> Dick Holland >> > > http://www.google.com > > http://qmail.jms1.net > > http://www.qmailrocks.org > > and there is lifewithqmail.org and several others > > basically what I am saying, is that you should have a well thought > out full install before you start of your just in for headaches > > if you don't install qmail properly and it is an internet facing > unit, some unpleasant issues will eventually arise. > > :-) > > - rh IIRC correctly, this is the (in)famous errno problem. It requires a patch to put qmail at 1.03. Life with qmail has all the instruction you need to patch and install qmail. There's a script to do it all for you. Qmail is really straight forward provided you follow the install directions to the letter. Once you do, you'll have the best SMTP server running. Thanks! Mark Schoonover *** Winner of the 2008 Best Psychic Award IS Manager American Geotechnical - California, Nevada and Arizona V-> 858.450.4040 F-> 714.685.3909 C-> 858.472.3816

10 22

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss