search for: b120

I am installing 4.2 on the new dell $499 B120 laptop. Centos installs just fine. however, when rebooting it is starting udev and then says Disabling IRQ#11 and stops. Any ideas on why that would be?? THanks, Jerry -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/at...

>/Jerry Geis wrote: />// I am installing 4.2 on the new dell $499 B120 laptop. //>/ Centos installs just fine. however, when rebooting />/ it is starting udev and then says Disabling IRQ#11 and stops. />/ />/ Any ideas on why that would be?? />/ / >/Do you have a USB devices plugged in? I reinstalled CentOS 4.2 on my />/laptop this past weekend...

...seconds, at which statistics should be displayed. If > this option is not specified, statistics are > displayed once. Which rather suggest it will display statistics for all flows and not only first one. Looking at the code of flowadm.c from b120: flow_stats() [...] > /* > * If an interval is specified, continuously show the stats > * for only the first flow. > */ > state->fs_firstonly = (interval != 0); Is there a reason why only first flow is displayed? If one wants stats for...

I have a 5-500GB disk Raid-Z pool that has been producing checksum errors right after upgrading SXCE to build 121. They seem to be randomly occurring on all 5 disks, so it doesn''t look like a disk failure situation. Repeatingly running a scrub on the pools randomly repairs between 20 and a few hundred checksum errors. Since I hadn''t physically touched the machine, it seems a

We''re testing out the Puppetlabs-Firewall module. And it seems I''m either missing something fundamental or Logging/Accpet works/doesn''t work in an irregular way. I would be most grateful for some input. *COMMON:* firewall { ''002 accept related established rules INPUT'': proto => ''all'', state =>