Re: [CentOS] Problem with install Boardcom driver
On Sun, Sep 7, 2008 at 10:37 PM, Pete Kay <[EMAIL PROTECTED]> wrote: > Hi, > > I have to install Broadcom driver because the Dell Optiplex 330 > running Centos 5.2 is not able to connect to the network. > > I am trying to install a Broadcom driver, but I get the followng error: > > [EMAIL PROTECTED] tg3-3.85l]# > [EMAIL PROTECTED] tg3-3.85l]# make > make -C /lib/modules/2.6.18-92.el5/build > SUBDIRS=/usr/src/Server/Linux/Driver/tg3-3.85l modules > make[1]: Entering directory `/usr/src/kernels/2.6.18-92.el5-x86_64 (snip) > make: *** [default] Error 2 > [EMAIL PROTECTED] tg3-3.85l]# > > Does anyone know how to resolve this problem? It looks like you are trying to compile the tg3 module. If so, it is included in CentOS-5. $ /sbin/modinfo tg3 filename: /lib/modules/2.6.18-92.1.10.el5/kernel/drivers/net/tg3.ko version:3.86 license:GPL description:Broadcom Tigon3 ethernet driver You network problem may be due to something else ? Akemi ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] [resend] USB drive fails at sector 0xFFFFFFF
I'm backing up to a NTFS partition on an external USB drive with dump. I'm seeing failures in /var/log/messages reading sector 0xFFF that cause the verify pass to fail. Are there any known problems in the USB driver? Kernel via uname -a: Linux segw2.mpa.lan 2.6.18-92.1.6.el5 #1 SMP Wed Jun 25 13:49:24 EDT 2008 i686 i686 i386 GNU/Linux Message reported. (Note the number 268435455, which is 0xFFF, and occurs every time I see this happen. But a subsequent attempt to read this region with dd succeeds, so it appears to be intermittent, or dependent on some other precondition.) Sep 7 10:48:39 segw2 kernel: sd 5:0:0:0: Device not ready: <6>: Current: sense key: Not Ready Sep 7 10:48:39 segw2 kernel: Add. Sense: Logical unit not ready, cause not reportable Sep 7 10:48:39 segw2 kernel: Sep 7 10:48:39 segw2 kernel: end_request: I/O error, dev sdb, sector 268435455 Sep 7 10:48:39 segw2 kernel: Buffer I/O error on device sdb1, logical block 33554424 Sep 7 10:48:39 segw2 kernel: sd 5:0:0:0: Device not ready: <6>: Current: sense key: Not Ready Sep 7 10:48:39 segw2 kernel: Add. Sense: Logical unit not ready, cause not reportable Sep 7 10:48:39 segw2 kernel: Sep 7 10:48:39 segw2 kernel: end_request: I/O error, dev sdb, sector 268435455 Sep 7 10:48:39 segw2 kernel: Buffer I/O error on device sdb1, logical block 33554424 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Problem with install Boardcom driver
Hi, I have to install Broadcom driver because the Dell Optiplex 330 running Centos 5.2 is not able to connect to the network. I am trying to install a Broadcom driver, but I get the followng error: [EMAIL PROTECTED] tg3-3.85l]# [EMAIL PROTECTED] tg3-3.85l]# make make -C /lib/modules/2.6.18-92.el5/build SUBDIRS=/usr/src/Server/Linux/Driver/tg3-3.85l modules make[1]: Entering directory `/usr/src/kernels/2.6.18-92.el5-x86_64' CC [M] /usr/src/Server/Linux/Driver/tg3-3.85l/tg3.o In file included from /usr/src/Server/Linux/Driver/tg3-3.85l/tg3.c:85: /usr/src/Server/Linux/Driver/tg3-3.85l/tg3.h:234: error: redefinition of 'skb_transport_offset' include/linux/skbuff.h:1006: error: previous definition of 'skb_transport_offset' was here /usr/src/Server/Linux/Driver/tg3-3.85l/tg3.h:239: error: redefinition of 'ip_hdr' include/linux/ip.h:109: error: previous definition of 'ip_hdr' was here /usr/src/Server/Linux/Driver/tg3-3.85l/tg3.h:244: error: redefinition of 'ip_hdrlen' include/net/ip.h:48: error: previous definition of 'ip_hdrlen' was here /usr/src/Server/Linux/Driver/tg3-3.85l/tg3.h:249: error: redefinition of 'tcp_hdr' include/linux/tcp.h:169: error: previous definition of 'tcp_hdr' was here /usr/src/Server/Linux/Driver/tg3-3.85l/tg3.h:254: error: redefinition of 'tcp_optlen' include/linux/tcp.h:179: error: previous definition of 'tcp_optlen' was here make[2]: *** [/usr/src/Server/Linux/Driver/tg3-3.85l/tg3.o] Error 1 make[1]: *** [_module_/usr/src/Server/Linux/Driver/tg3-3.85l] Error 2 make[1]: Leaving directory `/usr/src/kernels/2.6.18-92.el5-x86_64' make: *** [default] Error 2 [EMAIL PROTECTED] tg3-3.85l]# Does anyone know how to resolve this problem? Many thanks in advance for all your help. Regards, Pete ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] USB drive fails at sector 0xFFFFFFF
On Sun, Sep 7, 2008 at 6:44 PM, Kenneth Porter <[EMAIL PROTECTED]> wrote: > I'm backing up to a NTFS partition on an external USB drive with dump. I'm > seeing failures in /var/log/messages reading sector 0xFFF that cause the > verify pass to fail. Are there any known problems in the USB driver? > > Kernel via uname -a: > > Linux segw2.mpa.lan 2.6.18-92.1.6.el5 #1 SMP Wed Jun 25 13:49:24 EDT 2008 > i686 i686 i386 GNU/Linux > > Message reported. (Note the number 268435455, which is 0xFFF, and occurs > every time I see this happen. But a subsequent attempt to read this region > with dd succeeds, so it appears to be intermittent, or dependent on some > other precondition.) > > Sep 7 10:48:39 segw2 kernel: sd 5:0:0:0: Device not ready: <6>: Current: > sense key: Not Ready > Sep 7 10:48:39 segw2 kernel: Add. Sense: Logical unit not ready, cause > not reportable > Sep 7 10:48:39 segw2 kernel: > Sep 7 10:48:39 segw2 kernel: end_request: I/O error, dev sdb, sector > 268435455 > Sep 7 10:48:39 segw2 kernel: Buffer I/O error on device sdb1, logical block > 33554424 > Sep 7 10:48:39 segw2 kernel: sd 5:0:0:0: Device not ready: <6>: Current: > sense key: Not Ready > Sep 7 10:48:39 segw2 kernel: Add. Sense: Logical unit not ready, cause > not reportable > Sep 7 10:48:39 segw2 kernel: > Sep 7 10:48:39 segw2 kernel: end_request: I/O error, dev sdb, sector > 268435455 > Sep 7 10:48:39 segw2 kernel: Buffer I/O error on device sdb1, logical block > 33554424 My Newbie guess is that the device has an intermittent problem at sector 268435455 and it is failing intermittently at that location. Hopefully someone more knowledgeable can answer your question about the USB driver. Do you have any Diagnostics for that USB drive that you can run on it? If not, see if you can download diagnostics from the web site of the manufacturer. Maybe a problem at 33554424 also? ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] USB drive fails at sector 0xFFFFFFF
I'm backing up to a NTFS partition on an external USB drive with dump. I'm seeing failures in /var/log/messages reading sector 0xFFF that cause the verify pass to fail. Are there any known problems in the USB driver? Kernel via uname -a: Linux segw2.mpa.lan 2.6.18-92.1.6.el5 #1 SMP Wed Jun 25 13:49:24 EDT 2008 i686 i686 i386 GNU/Linux Message reported. (Note the number 268435455, which is 0xFFF, and occurs every time I see this happen. But a subsequent attempt to read this region with dd succeeds, so it appears to be intermittent, or dependent on some other precondition.) Sep 7 10:48:39 segw2 kernel: sd 5:0:0:0: Device not ready: <6>: Current: sense key: Not Ready Sep 7 10:48:39 segw2 kernel: Add. Sense: Logical unit not ready, cause not reportable Sep 7 10:48:39 segw2 kernel: Sep 7 10:48:39 segw2 kernel: end_request: I/O error, dev sdb, sector 268435455 Sep 7 10:48:39 segw2 kernel: Buffer I/O error on device sdb1, logical block 33554424 Sep 7 10:48:39 segw2 kernel: sd 5:0:0:0: Device not ready: <6>: Current: sense key: Not Ready Sep 7 10:48:39 segw2 kernel: Add. Sense: Logical unit not ready, cause not reportable Sep 7 10:48:39 segw2 kernel: Sep 7 10:48:39 segw2 kernel: end_request: I/O error, dev sdb, sector 268435455 Sep 7 10:48:39 segw2 kernel: Buffer I/O error on device sdb1, logical block 33554424 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Time delaying (or time lagging)
...and sorry, I have forgot to include printout from ntptrace, so: localhost.localdomain: stratum 2, offset 0.29, synch distance 0.949418 tak.cesnet.cz: stratum 1, offset 0.00, synch distance 0.002272, refid 'GPS' 2008/9/8 happymaster23 <[EMAIL PROTECTED]> > Thank you very much, > > all is working perfectly. I am using ntp.nic.cz (CZ NIC is cz TLD > registry), tak.cesnet.cz (CESNET is czech academic network) and > 1.cz.pool.ntp.org. I think, that this servers are good? Am I right? Or is > better to use more NTP servers? > > Thanks > > 2008/9/6 John R Pierce <[EMAIL PROTECTED]> > > happymaster23 wrote: >> >>> Hello everyone, >>> >>> I have problem with time delaying on my CentOS powered server. I have >>> tried to set time in BIOS and in OS (with saving time to BIOS), but time >>> still delaying, so after month is about five minutes delayed. In past I was >>> using this box with Windows and there wasn´t this time problem, but I cant >>> warrant, that there are no hardware issues. So I was decided, that easiest >>> way to fix this problem will be setting up the NTP. I have found many >>> howtos, but I don´t believe them. So my question is: How to clearly set NTP >>> in CentOS 5? >>> >> >> >> # yum install ntp >> >> then, edit /etc/ntp.conf, and at a minimum specify some ntp servers and >> restrict access to localhost... >> >> restrict 127.0.0.1 >> restrict -6 ::1 >> >> # Use public servers from the pool.ntp.org project. >> # Please consider joining the pool (http://www.pool.ntp.org/join.html). >> server ntp1.sf-bay.org >> server ntp2.sf-bay.org >> server reloj.kjsl.com >> server ntp1.mainecoon.com >> server ntp2.mainecoon.com >> server time.berkeley.netdot.net >> >> >> >> (note, those are the LOCAL TO ME ntp servers that *I* am using, you should >> undoubtedly use others as appropriate, or use the pool servers... see >> http://ntp.isc.org/bin/view/Servers/WebHome for guidelines)... >> >> finally... >> >> # chkconfig ntpd on >> # service ntpd start >> >> and wait about 20 mins for it to sync up, and verify functionality with >> ntptrace... >> >> # ntptrace >> localhost.localdomain: stratum 3, offset 0.004351, synch distance >> 0.088396 >> zorro.sf-bay.org: stratum 2, offset 0.000543, synch distance 0.044773 >> clock.via.net: stratum 1, offset 0.27, synch distance 0.000446, >> refid 'GPS' >> >> if your systems clock is particularlly funky, it may be a good idea to >> edit, /etc/sysconfig/ntpd and set SYNC_HWCLOCK=yes rather than no. >> (this tells it to set your HW CMOS clock when it sets the system clock >> during the initial synchronization) >> >> >> ___ >> CentOS mailing list >> CentOS@centos.org >> http://lists.centos.org/mailman/listinfo/centos >> > > ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Time delaying (or time lagging)
Thank you very much, all is working perfectly. I am using ntp.nic.cz (CZ NIC is cz TLD registry), tak.cesnet.cz (CESNET is czech academic network) and 1.cz.pool.ntp.org. I think, that this servers are good? Am I right? Or is better to use more NTP servers? Thanks 2008/9/6 John R Pierce <[EMAIL PROTECTED]> > happymaster23 wrote: > >> Hello everyone, >> >> I have problem with time delaying on my CentOS powered server. I have >> tried to set time in BIOS and in OS (with saving time to BIOS), but time >> still delaying, so after month is about five minutes delayed. In past I was >> using this box with Windows and there wasn´t this time problem, but I cant >> warrant, that there are no hardware issues. So I was decided, that easiest >> way to fix this problem will be setting up the NTP. I have found many >> howtos, but I don´t believe them. So my question is: How to clearly set NTP >> in CentOS 5? >> > > > # yum install ntp > > then, edit /etc/ntp.conf, and at a minimum specify some ntp servers and > restrict access to localhost... > > restrict 127.0.0.1 > restrict -6 ::1 > > # Use public servers from the pool.ntp.org project. > # Please consider joining the pool (http://www.pool.ntp.org/join.html). > server ntp1.sf-bay.org > server ntp2.sf-bay.org > server reloj.kjsl.com > server ntp1.mainecoon.com > server ntp2.mainecoon.com > server time.berkeley.netdot.net > > > > (note, those are the LOCAL TO ME ntp servers that *I* am using, you should > undoubtedly use others as appropriate, or use the pool servers... see > http://ntp.isc.org/bin/view/Servers/WebHome for guidelines)... > > finally... > > # chkconfig ntpd on > # service ntpd start > > and wait about 20 mins for it to sync up, and verify functionality with > ntptrace... > > # ntptrace > localhost.localdomain: stratum 3, offset 0.004351, synch distance > 0.088396 > zorro.sf-bay.org: stratum 2, offset 0.000543, synch distance 0.044773 > clock.via.net: stratum 1, offset 0.27, synch distance 0.000446, > refid 'GPS' > > if your systems clock is particularlly funky, it may be a good idea to > edit, /etc/sysconfig/ntpd and set SYNC_HWCLOCK=yes rather than no. > (this tells it to set your HW CMOS clock when it sets the system clock > during the initial synchronization) > > > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 4.7 status
josh donovan wrote: Any update on this situation? The last security updates for 4.6 were released in July so it looks as though the 4X branch has ground to a halt. The 4.7 release is syncing out to external mirrors right now, we should have enough done for release by Monday night ( for i386/x86_64 ) -- Karanbir Singh : http://www.karan.org/ : [EMAIL PROTECTED] ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] check mal server speed n performance
> The most likely issues are DNS, virus scan and yet one too many messages. Are the timeouts occuring with mailbox access? IMAP / Webmail / etc? Check the size of your users inboxes and mail folders. If you are using the default mbox storage format, that has a tendancy to get slow as the mailbox sizes increase. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
thnks guys -- [CentOS] check mail server speed n performance
Thanks guys n really apprecite for ur quick reply i do some checks anyway regards Fabian > Dear All, > > I have Centos 5.1 and sendmail mail server running for over a year and > been workin fine > > i also use mailscanner + clamav > > now some remote users have been complaing that the mail sometimes time out > > i have even tried to stop the mail scanner and jus test my sendmail but > the problem exists > > now i would apprecite if someone cd help me or let me know of a link where > i could test the mail server performance and know if its working fine > > so to rule out the possibility of any problem with my mail server software > > the mail logs r normall and dont show any different thing > > > thanks and regards > > > apprecite ur help > > > > regards > > Fabian > > > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Problem with running Centos 5.2 on Dell Optiplex 330
On Sun, Sep 7, 2008 at 7:29 AM, nate <[EMAIL PROTECTED]> wrote: > Pete Kay wrote: >> Hi, >> >> I am havind deep trouble with a bunch of our newly arrived Optiplex >> 330 as it can't run Centos 5.2 property. >> .. >> >> Does anyone know how I can fix this problem? > > It's quite possible the network driver isn't compatible with > the system. Looking at the support site for Dell that system > isn't supported with Linux, and it looks like it has a pretty > new broadcom chip on it. > > I'd bet that updating the driver will allow the NIC to work, > the latest drivers for that system are available. The quick and handy way to do this is to pick up an inexpensive USB ethernet link or other ether net card. After a yum update to a new kernel you may well have a driver that works. If a yum update does not update the driver, you have enough connectivity to download then install vendor bits and tools. This is the trick I have used for a number of early access Intel 'engineering' boxes. It lets me kickstart to a lab configuration and connect long enough to add the updated driver. I can save all the fun new bits and script up the driver update into a single dir to copy from one to the next. Then burn that dir of bits to a CDROM... If you are shopping, the older the USB ethernet device the more likely it is to work. -- NiftyCluster T o m M i t c h e l l ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] check mal server speed n performance
On Sun, Sep 7, 2008 at 9:33 AM, fabian dacunha <[EMAIL PROTECTED]> wrote: > Dear All, > > I have Centos 5.1 and sendmail mail server running for over a year and > been workin fine > > i also use mailscanner + clamav > > now some remote users have been complaing that the mail sometimes time out > > i have even tried to stop the mail scanner and jus test my sendmail but > the problem exists > > now i would apprecite if someone cd help me or let me know of a link where > i could test the mail server performance and know if its working fine > > so to rule out the possibility of any problem with my mail server software > > the mail logs r normall and dont show any different thing > > > thanks and regards > > > apprecite ur help The most likely issues are DNS, virus scan and yet one too many messages. Look hard at DNS resolution... spam filters now do host name checks forward, back, inside, out. A volume email server needs access to a local quick name server. Adding a local name server or moving the local name server to a dedicated machine could be a win. There is no easy way to benchmark a mail server that is in operation. One thing to tinker with is a "fetchmail" benchmark of a known set of messages from some place like gmail. You can watch the mail get processed (mailq), watch the name server and file IO etc. By refilling your INBOX from "All Mail" or a saved folder you should be able to play it again. If you need a pile of spam use a throw away gmail account and almost register for one of those "free laptop offers" that Google pops up. -- NiftyCluster T o m M i t c h e l l ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] check mal server speed n performance
Dear All, I have Centos 5.1 and sendmail mail server running for over a year and been workin fine i also use mailscanner + clamav now some remote users have been complaing that the mail sometimes time out i have even tried to stop the mail scanner and jus test my sendmail but the problem exists now i would apprecite if someone cd help me or let me know of a link where i could test the mail server performance and know if its working fine so to rule out the possibility of any problem with my mail server software the mail logs r normall and dont show any different thing thanks and regards apprecite ur help regards Fabian -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Re: Troubles with NetworkManager
Now, When I tried to run the NetworkManager applet manually, i got the same popup error and with the few more details saying the the activity icons are missing. This is the default installation; I tried two time times and nothing is modified in the themes. Sounds much more like a bug, could someone please confirm it. [EMAIL PROTECTED] ~]# nm-applet ** (nm-applet:9388): WARNING **: Icon nm-device-wired-autoip missing: Icon 'nm-device-wired-autoip' not present in theme (nm-applet:9388): Gdk-CRITICAL **: gdk_x11_get_server_time: assertion `GDK_IS_WINDOW (window)' failed (nm-applet:9388): Gdk-CRITICAL **: gdk_x11_window_set_user_time: assertion `GDK_IS_WINDOW (window)' failed (nm-applet:9388): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nm-applet:9388): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nm-applet:9388): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nm-applet:9388): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nm-applet:9388): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nm-applet:9388): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nm-applet:9388): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nm-applet:9388): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nm-applet:9388): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nm-applet:9388): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nm-applet:9388): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nm-applet:9388): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nm-applet:9388): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nm-applet:9388): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nm-applet:9388): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nm-applet:9388): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nm-applet:9388): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nm-applet:9388): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nm-applet:9388): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nm-applet:9388): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nm-applet:9388): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nm-applet:9388): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nm-applet:9388): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nm-applet:9388): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nm-applet:9388): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nm-applet:9388): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nm-applet:9388): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nm-applet:9388): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nm-applet:9388): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nm-applet:9388): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nm-applet:9388): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nm-applet:9388): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nm-applet:9388): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nm-applet:9388): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nm-applet:9388): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nm-applet:9388): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nm-applet:9388): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nm-applet:9388): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nm-applet:9388): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nm-applet:9388): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nm-applet:9388): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nm-applet:9388): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nm-applet:9388): GLib-GObject-CRITICAL **: g_object_unref: asser
[CentOS] Troubles with NetworkManager
NetworkManager used to work fine for me but during the last few installations its a big hurdle in the wireless connectivity. I'm using Madwifi and its interface is correctly listed and working but I cannot connect to any wifi AP without NetworkManager. I've two interfaces: eth0 and wifi0. Starting NetworkManager doesn't show any notification icon in the top right in gnome and I believe its only activating the ath0 instead of wireless interface wifi0 but still I am unable to see any of the notification icon in the gnome as I was used to in past for any of the NICs. The error which I recieve upon logging into the gnome is: "The NetworkManager applet could not find some required resources. It cannot conitnue". But still, there are no errors in the syslogs besides the below ones particularly *"localhost NetworkManager: nm_device_802_11_wireless_scan (): could not trigger wireless scan on device ath0: Network is down*". Thanks in advance for the helpout. [EMAIL PROTECTED] abbask]# grep -A 2 -B2 NetworkManager /var/log/messages | tail -60 Jan 15 05:35:31 localhost NetworkManager: Activation (eth0) Stage 1 of 5 (Device Prepare) started... Jan 15 05:35:31 localhost NetworkManager: Activation (eth0) Stage 2 of 5 (Device Configure) scheduled... Jan 15 05:35:31 localhost NetworkManager: Activation (eth0) Stage 1 of 5 (Device Prepare) complete. Jan 15 05:35:31 localhost NetworkManager: Activation (eth0) Stage 2 of 5 (Device Configure) starting... Jan 15 05:35:31 localhost NetworkManager: Activation (eth0) Stage 2 of 5 (Device Configure) successful. Jan 15 05:35:31 localhost NetworkManager: Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled. Jan 15 05:35:31 localhost NetworkManager: Activation (eth0) Stage 2 of 5 (Device Configure) complete. Jan 15 05:35:31 localhost NetworkManager: Activation (eth0) Stage 3 of 5 (IP Configure Start) started... Jan 15 05:35:31 localhost dhclient: wifi0: unknown hardware address type 801 Jan 15 05:35:31 localhost dhclient: wifi0: unknown hardware address type 801 -- Jan 15 05:35:31 localhost NET[6581]: /sbin/dhclient-script : updated /etc/resolv.conf Jan 15 05:35:31 localhost dhclient: bound to 13.13.13.4 -- renewal in 1581 seconds. Jan 15 05:35:32 localhost NetworkManager: Activation (eth0) Beginning DHCP transaction. Jan 15 05:35:32 localhost dhclient: wifi0: unknown hardware address type 801 Jan 15 05:35:32 localhost NetworkManager: Activation (eth0) Stage 3 of 5 (IP Configure Start) complete. Jan 15 05:35:32 localhost NetworkManager: DHCP daemon state is now 12 (successfully started) for interface eth0 Jan 15 05:35:32 localhost NetworkManager: DHCP daemon state is now 1 (starting) for interface eth0 Jan 15 05:35:32 localhost dhclient: wifi0: unknown hardware address type 801 Jan 15 05:35:32 localhost avahi-daemon[5154]: New relevant interface eth0.IPv6 for mDNS. -- Jan 15 05:35:32 localhost dhclient: DHCPREQUEST on eth0 to 255.255.255.255port 67 Jan 15 05:35:32 localhost dhclient: DHCPACK from 13.13.13.3 Jan 15 05:35:32 localhost NetworkManager: DHCP daemon state is now 4 (reboot) for interface eth0 Jan 15 05:35:32 localhost NetworkManager: Activation (eth0) Stage 4 of 5 (IP Configure Get) scheduled... Jan 15 05:35:32 localhost NetworkManager: Activation (eth0) Stage 4 of 5 (IP Configure Get) started... Jan 15 05:35:32 localhost dhclient: bound to 13.13.13.4 -- renewal in 1438 seconds. Jan 15 05:35:32 localhost dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.host_name -- Jan 15 05:35:32 localhost dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_domain Jan 15 05:35:32 localhost dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_servers Jan 15 05:35:32 localhost NetworkManager: Retrieved the following IP4 configuration from the DHCP daemon: Jan 15 05:35:32 localhost NetworkManager:address 13.13.13.4 Jan 15 05:35:32 localhost NetworkManager:netmask 255.255.255.0 Jan 15 05:35:32 localhost NetworkManager:broadcast 13.13.13.255 Jan 15 05:35:32 localhost NetworkManager:gateway 13.13.13.3 Jan 15 05:35:32 localhost NetworkManager:nameserver 13.13.13.3 Jan 15 05:35:32 localhost NetworkManager: Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled... Jan 15 05:35:32 localhost NetworkManager: Activation (eth0) Stage 4 of 5 (IP Configure Get) complete. Jan 15 05:35:32 localhost NetworkManager: Activation (eth0) Stage 5 of 5 (IP Configure Commit) started... Jan 15 05:35:32 localhost avahi-daemon[5154]: Withdrawing address record for 13.13.13.4 on eth0. Jan 15 05:35:32 localhost avahi-daemon[5154]: Leaving mDNS multicast group on interface eth0.IPv4 with address 13.13.13.4. -- Jan 15 05:35:33 localhost dnsmasq[5162]: reading /etc/resolv.conf Jan 15 05:35:33 localhost dnsmasq[5162]: using nameserver 13.13.13.3#53 Jan 15 05:35:33 localhost NetworkManager: A
Re: [CentOS] Problem with running Centos 5.2 on Dell Optiplex 330
Pete Kay wrote: > Hi, > > I am havind deep trouble with a bunch of our newly arrived Optiplex > 330 as it can't run Centos 5.2 property. > > The installation works fine, but when it boots up, it can't be > connected to the network. I am getting error saying " link is not > ready" when doing system-config-network. I check lspci and it can > detect the network controller no problem. The light next to the cable > is also on as well. > > Does anyone know how I can fix this problem? It's quite possible the network driver isn't compatible with the system. Looking at the support site for Dell that system isn't supported with Linux, and it looks like it has a pretty new broadcom chip on it. I'd bet that updating the driver will allow the NIC to work, the latest drivers for that system are available here: http://www.broadcom.com/support/ethernet_nic/netlink.php Broadcom has a history of updating their network chips in ways that are not compatible with existing drivers, forcing you to install new ones, for this reason I've preferred Intel network chips for some time now. nate ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Problem with running Centos 5.2 on Dell Optiplex 330
--- On Sun, 7/9/08, Pete Kay <[EMAIL PROTECTED]> wrote: > From: Pete Kay <[EMAIL PROTECTED]> > Subject: [CentOS] Problem with running Centos 5.2 on Dell Optiplex 330 > To: centos@centos.org > Date: Sunday, 7 September, 2008, 12:48 PM > Hi, > > I am havind deep trouble with a bunch of our newly arrived > Optiplex > 330 as it can't run Centos 5.2 property. > > The installation works fine, but when it boots up, it > can't be > connected to the network. I am getting error saying " > link is not > ready" when doing system-config-network. I check > lspci and it can > detect the network controller no problem. The light next > to the cable > is also on as well. > > Does anyone know how I can fix this problem? > > We should have bought just one and see if it works before > buying more, > and now we are stuck. > > Could someone please kindly give any suggestion? Any help > will be > greatly appreciated. > > Best Regards, > Pete > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos The problem is not with Dell Optiplex as Dell themselves ship systems with Linux, I would reckon it is your admin skills in question here. I have successfully ran Fedora/Red Hat/CentOS on Dell boxes and the network card was automagically recognised. You do have to configure the network though. Look at the CentOS admin docs or look at an old online tutorial http://www.yolinux.com/TUTORIALS/LinuxTutorialNetworking.html#GUI Thanks, Josh ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Problem with running Centos 5.2 on Dell Optiplex 330
Hi, I am havind deep trouble with a bunch of our newly arrived Optiplex 330 as it can't run Centos 5.2 property. The installation works fine, but when it boots up, it can't be connected to the network. I am getting error saying " link is not ready" when doing system-config-network. I check lspci and it can detect the network controller no problem. The light next to the cable is also on as well. Does anyone know how I can fix this problem? We should have bought just one and see if it works before buying more, and now we are stuck. Could someone please kindly give any suggestion? Any help will be greatly appreciated. Best Regards, Pete ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 4.7 status
--- On Wed, 3/9/08, Karanbir Singh <[EMAIL PROTECTED]> wrote: > From: Karanbir Singh <[EMAIL PROTECTED]> > Subject: Re: [CentOS] CentOS 4.7 status > To: "CentOS mailing list" > Date: Wednesday, 3 September, 2008, 4:35 PM > We are working on getting 4.7 out right now, if things goto > plan, and > enough mirrors are seeded we will announce and release the > torrents this > Friday/Saturday so 5th or 6th. > > If things get delayed beyond that, I'll post an email > to this thread. > > -- > Karanbir Singh : http://www.karan.org/ : [EMAIL PROTECTED] > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos Any update on this situation? The last security updates for 4.6 were released in July so it looks as though the 4X branch has ground to a halt. Thanks, Josh. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] xulrunner-devel package missing many header files
On 9/7/08, Ignacio Vazquez-Abrams <[EMAIL PROTECTED]> wrote: > On Sun, 2008-09-07 at 18:01 +1000, hce wrote: > > I've just installed xulrunner-devel from yum, but there are following > > header files cannot be found in xulrunner-sdk-1.9/sdk/include: > > > Did you install xulrunner-devel-unstable? No, I did yum install xulrunner-devel. Did you mean I need to install xulrunner-devel-unstable? Thanks Ignacio. Kind Regards, ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] xulrunner-devel package missing many header files
On Sun, 2008-09-07 at 18:01 +1000, hce wrote: > I've just installed xulrunner-devel from yum, but there are following > header files cannot be found in xulrunner-sdk-1.9/sdk/include: Did you install xulrunner-devel-unstable? -- Ignacio Vazquez-Abrams <[EMAIL PROTECTED]> PLEASE don't CC me; I'm already subscribed signature.asc Description: This is a digitally signed message part ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] xulrunner-devel package missing many header files
Hi, I've just installed xulrunner-devel from yum, but there are following header files cannot be found in xulrunner-sdk-1.9/sdk/include: mozilla-config.h mozilla-config32.h prtypes.h The include/xulrunner-sdk-1.9 constains those above header files, I did link to them, but xulrunner-sdk-1.9/system_wrappers/prtypes.h has a problem as well: #pragma GCC system_header #pragma GCC visibility push(default) #include_next #pragma GCC visibility pop At final, I could not compile VLC plugin with the xulrunner-sdk-1.9/sdk. Please advice how to fix it and where could I install a proper sdk? Thank you. Kind regards, Jim ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
