Re: possible cause of horrifically unreliable NFS?
On Mon, Mar 23, 2009 at 4:46 PM, David Burns tdb...@gmail.com wrote: On Mon, Mar 23, 2009 at 8:31 AM, Robert P. J. Day rpj...@crashcourse.ca wrote: what is the most common cause of NFS bouncing back and forth between OK and not responding? should i be messing with the mount options? 2 prime causes of NFS problems for me are iptables and selinux. Just a guess. Dave Networking issues, and/or a heavily loaded server can also cause OK/not responding, and appear to be normal if things are being pushed to close to max speed (disks and/or networking). -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Advice on changing to 64 bits
Klaus-Peter Schrage wrote: Up to last week, I had Fedora running in subsequent versions 2 or so to 10 on my old Pentium 4 system. Now I have a rather recent new desktop computer with much of the latest and greatest hardware: Intel Core 2 Duo E8400 with 4 GB RAM, harddrive with lots of Gagabytes and so on. Thinking about changing to 64 bits architecture (I have the i386 installation dvd, but not yet the i86_64 one), I was astonished how little I found on pros and cons. So what would you advise? 1. Changing to 64 bits is a must for you. 2. You will benefit from it. 3. Keep your hands off, stay with 64 bits. 4. ... I should mention that I want to use virtualization (KVM, VMware Server), and that the processor has Intel's hardware vitualization capabilities. Thanks for any pointers. Klaus Something to note, I don't know why but the 64-bit versions of Firefox and Thunderbird use a lot more memory than the 32-bit versions, I was originally running a 32-bit f9 with 3GB ram w/2GB swap, and almost never got into swap, after switching to 10 64-bit, I had to add 2GB more of swap and was getting deep into the 4GB of swap, I uninstalled 64-bit firefox/openoffice and thunderbird and put in the 32-bit version and the memory usage went down quite a bit. The memory usage was a at least 50% more. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Hosed fstab, won't boot how to edit?
Robert Moskowitz wrote: Bill Davidsen wrote: Robert Moskowitz wrote: So I mistyped noatime in /etc/fstab; wished there was a way to test this first! Anyway, since this is my ASUS Eee and my swap is on the SD card, by pulling the SD card the boot halts and puts me into Repair Filesystem mode. Thing is /etx fstab is readonly. vi fstab won't let me save the file. I assume you have done the normal write a ro file command (:w!) and that failed as well? I really don't want to do a complete reinstall yet. I want to buy a 8Gb SD card first (and next time I am putting /usr on the SD card). So how can I edit this? Yes, that did not work. I am home now, and will just do a reinstall. I was planning one anyway as I figured out the 'best' way to distribute everything between a 4Gb SSD drive and a 4Gb SD drive. When I just had everything (/) on the 4Gb SSD drive as a ext3 partition, the install failed. Moving /var/cache over to the SD drive worked. But now after looking at things, I am going to put /usr on a 4Gb ext3 partition on the SD drive, a 1.5Gb swap and 2.5Gb / ext3 on the SSD drive. I think that is the best I can do until I get a 8Gb SD card, or figure out how to unsolder the SSD drive and install a larger one I would (as a last try) try doing the remount with the device rather than / and also try adding -s to the original remount command. Or boot it with a install disk and let the install disk mount up the stuff on the hd and edit it. Roger -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Hosed fstab, won't boot how to edit?
On Tue, Jan 20, 2009 at 1:45 PM, Robert Moskowitz r...@htt-consult.com wrote: So I mistyped noatime in /etc/fstab; wished there was a way to test this first! Anyway, since this is my ASUS Eee and my swap is on the SD card, by pulling the SD card the boot halts and puts me into Repair Filesystem mode. Thing is /etx fstab is readonly. vi fstab won't let me save the file. I really don't want to do a complete reinstall yet. I want to buy a 8Gb SD card first (and next time I am putting /usr on the SD card). So how can I edit this? mount -o rw,remount / then edit it. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Hosed fstab, won't boot how to edit?
Robert Moskowitz wrote: Roger Heflin wrote: On Tue, Jan 20, 2009 at 1:45 PM, Robert Moskowitz mount -o rw,remount / So I tried this (had a DAH moment after you posted this), but got an error: mount: / not mounted already, or bad option So I tried just 'mount' to see what the status of / is and got (amongst other pieces of info): /dev/sda1 on / type ext3 (rw) then edit it. mount is not reliable to show what is mounted in some cases. It reads /etc/mtab a file that happens to be located on a ro filesystem that won't have been updated so it won't be right when a machine is in single user mode. do a cat /proc/mounts to figure out what the actual state is, I never use the mount command to see what is mounted there are just too many failures of it (it only shows the options that you used, not (in the case of nfs) the actual parameters being used). try doing a mount -o remount,rw / I know I have done this several times. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F9 doesn't find swap or /root system on new motherboard
M. Fioretti wrote: Greetings, My motherboard, on which I was running F9 x86_64 off one SATA drive, died. I bought a new motherboard with a new cpu of the same type (AMD) and connected the hard disk with F9 to it. Now Grub does start with these options: kernel/vmlinuz/-2.6.27-etc ro root=/dev/sda3 rhgb mem=2048M enforcing 0 but the process stops at a certain point, saying: Trying to resume from /dev/sda2 Unable to access resume device (/dev/sda2) Creating root device Mounting root filesystem Mount: error mounting /dev/root on /sysroot as ext3: no such file or directory IIRC I had these partitions: /boot /dev/sda1 swap /dev/sda2 //dev/sda3 /home /sda5 So (also from some research I made before posting) this means that on the new board the kernel cannot find the swap anymore, but why? I mean, if it boots, as it does, it means that it has found the device corresponding to the hard drive, isn't it? It means that *grub* has found the device using *bios* calls. Linux does not use *bios* calls. And Linux is not find *any* partitions at all, even the boot one. Grub through bios calls loads vmlinuz and initrd into memory and then starts it up, which will find through Linux drivers everything needed to actually boot. The base problem is the new MB likely has a *different* sata device controlling the drives, and the driver for that is not in the initrd used to boot Linux, so Linux cannot find any disk devices. The typical fix is to boot a rescue, figure out from the rescue what driver is needed and update modprobe.conf and rebuilt the initial ram disk with that driver, and try again. You won't be able to fix it through grub, you may be able to change MB settings and change drivers needed for the disk (often sata ports can do either IDE or ahci--each of which uses a different driver--that *maybe* the old mb used). -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F9 doesn't find swap or /root system on new motherboard
Craig White wrote: On Sat, 2009-01-17 at 17:57 -0600, Roger Heflin wrote: M. Fioretti wrote: Greetings, My motherboard, on which I was running F9 x86_64 off one SATA drive, died. I bought a new motherboard with a new cpu of the same type (AMD) and connected the hard disk with F9 to it. Now Grub does start with these options: kernel/vmlinuz/-2.6.27-etc ro root=/dev/sda3 rhgb mem=2048M enforcing 0 but the process stops at a certain point, saying: Trying to resume from /dev/sda2 Unable to access resume device (/dev/sda2) Creating root device Mounting root filesystem Mount: error mounting /dev/root on /sysroot as ext3: no such file or directory IIRC I had these partitions: /boot /dev/sda1 swap /dev/sda2 //dev/sda3 /home /sda5 So (also from some research I made before posting) this means that on the new board the kernel cannot find the swap anymore, but why? I mean, if it boots, as it does, it means that it has found the device corresponding to the hard drive, isn't it? It means that *grub* has found the device using *bios* calls. Linux does not use *bios* calls. And Linux is not find *any* partitions at all, even the boot one. Grub through bios calls loads vmlinuz and initrd into memory and then starts it up, which will find through Linux drivers everything needed to actually boot. The base problem is the new MB likely has a *different* sata device controlling the drives, and the driver for that is not in the initrd used to boot Linux, so Linux cannot find any disk devices. The typical fix is to boot a rescue, figure out from the rescue what driver is needed and update modprobe.conf and rebuilt the initial ram disk with that driver, and try again. My only question to that is that it actually loaded the kernel from /boot before things went awry. *Grub* loaded the kernel/initrd from /boot using *bios* calls, it only knows enough to find the kernel/initrd files, it knows very little beyond that and it turns over everything to Linux. Linux does not use *bios* calls because they have speed and a number of other limitations (16 bit only is a big issue), Linux uses it's own drivers, and if you have the wrong one this is what happens. Yes, I would agree that booting something like a live cd or rescue disk, checking the loaded modules and rebuilding initrd makes sense but I'm not convinced that it would work based upon the fact that it does read /boot (/dev/sda1). Grub is not Linux. Grub can fail to read devices that Linux can read, and Linux can fail to read devices that grub supports through bios calls. I typically rebuilt the initrd before changing MB's but that is not an option if the MB is dead. And sometimes I get the wrong driver and have it do exactly as he is seeing and have to re-do it again with the proper driver. Craig -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F9 doesn't find swap or /root system on new motherboard
M. Fioretti wrote: On Sun, January 18, 2009 1:36 am, Mikkel L. Ellertson wrote: Read the man page for mkinitrd - it tells you how to include specific modules, as well as an option to overwrite the current initrd. just to be sure (sorry, it's almost 2 am here and I'm really tired), this works even if the distro and kernel on the laptop where I'll run mkinitrd are different from the target system? But you have to know the module you need for the new controller. you mean it's only a question of finding what that module is, right? That board has a geforce 8300 controller, should I get the module from the nVidia drivers? Thanks again, M. Once you chroot you will be in the environment of the dead pc just running the kernel that the host pc booted, all commands, and data will be coming from the dead pc's chrooted environment. This will typically only get you in trouble if the kernels are hugely different (one kernel is say 2.4 rather than 2.6, or if the host kernel is 32bit and the target machine was 64bit), other than that it should just work if you can find the correct module. I would suggest trying several of them at one time, sata_nv, and ahci are good choices, but throwing in more won't hurt. I would suggest using mkinitrd with a -v to show what modules it is including so that you can see the new ones actually went into it. You should not need to use cpio to undo/redo it, that does get alot more complicated that letting mkinitrd do its thing. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Simple question regarding touch and mv
Don't some programs interpret -- as stdin? No. But some programs do interpret -- as no more options after this. so: touch -- -foo will work as the -- tells touch that there are no options after this. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: perl-PDL-LAPACK
Patrick Dupre wrote: Hello, I updated my machine to Fedora and I facing a problem that I cannot solve. I need to sue the perl package perl-PDL-LAPACK which is not available in a binary form, so I tried to compile it but it fails because I do not have anymore a f2c.h library thank for your help. Patrick, I would suggest either changing the package to use gfortran or finding a version that does that. Or installing compat-gcc-34, compat-gcc-libf2c-34 and compat-gcc-34-g77.That should provide the old f2c or at least a g77 command that should work as a replacement. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Workstations shutting down for no apparent reason (F8)
Alain Cochard wrote: Hello. I am running 40 workstations with 3 kinds of hardware, all under fedora 8. From time to time -- about once every 3 days -- one of the machine (not always the same) shuts itself down. Otherwise they are running 24 hours a day every day. The excerpt of the /var/log/messages that seems relevant to me is always similar to the following: If you have instant off set in the bios, there are a number of motherboards on which the power switch will pick up enough noise to send a proper off signal even though no one is pushing the button... The easiest solution is to not set instant off. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: any program / script to connect to router to check status
chloe K wrote: Hi Any program to connect to router to check status I would like to output eg: sh int to file Thank you - Now with a new friend-happy design! Try the new Yahoo! Canada Messenger If your router is one that allows telnet, you can use expect to provide commands and passwords to telnet and run any commands that can be done from telnet session. On the routers that run linux you can get information from telnet that are not available on the web interface. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: D-Link DGE-550SX (dl2k): WARNING: at net/sched/sch_generic.c:219 dev_watchdog+0xda/0x12d()
Frantisek Hanzlik wrote: Hello, we just upgraded our old router (Fedora Core 5 on AlphaServer 800, kernel 2.6.17) to new Fedora 10/2.6.27.5-117.fc10.i686 kernel on Core2Duo i686. PCI-X Fiber 1000BASE-SX D-Link Network Adapter DGE-550SX, which worked fine in old Alphaserver, freeze on new machine few minutes after start (What is interesting, in one case after it sent exactly 8192 packets, an other cases are some multiples of 8 too) and stop transmit packets. Only workaround (but for a while) is rmmod + modprobe its dl2k driver. I would go post this to the kernel list, is is definitely some sort of kernel interaction. From what I understand the sch_generic.c error means that the networking driver has an issue with its hardware. I don't believe there is a way to misconfigure things and get this. On other network chipsets others have attempted to work around this sort of issue by changing how the network chipset works (turning on/off tcp offload, or other internal network chipset capabilities, and/or turning off pause-things can be adjusted with ethtool). If you get the correct feature turned off that is required to trigger the bug then it may work. Keep in mind though that typically when you have a 32bit/33Mhz network card it appears that the speed is limited to around 50MB/second each way, even though the PCI bandwidth should be high enough to do more.I don't know why this is, but I have seen it with several different ethernet chipsets (tg3/e1000). -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F10 NFS Install Query
John Austin wrote: Hi Previous versions of Fedora just needed the .iso file on the server for an NFS install For F10 I needed to mount the file in loopback and copy the contents of the DVD to a separate directory before anaconda could find it - is this a bug or a feature? Does anyone know if NFS exporting a loop mounted file is possible. I could not see it when I tried this. I did not want to fiddle with my main server too much Would the nohide option in /etc/exports do the trick ? John I have done that before with non-iso filesystem in a file, it has been a while though. One thing to remember is you have to exportfs -r again after you have mounted the ISO, otherwise only the underlying empty directory is being exported from the original exportfs run. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: mtrr funnies
Bill Davidsen wrote: Roger Heflin wrote: I know a bios engineer once told me that some chipsets/bios can only remap entire dimms (not parts of a dimm) and doing an entire dimm would result in only 2GB below 4GB and that bothers some vendors since it would cause issues with memory availability with 32bit only OSes. That's clearly not the case in general, and I've never seen it. Only old CPUs would have a problem with it (as a hardware issue), since all x86 CPUs recently support PAE for 64GB physical memory. I have never seen any 32 bit MSFT product use PAE, but the PAE Linux kernels will use more than 4GB, which is fine as long as no user program tries to use more than 4GB. The reason was that no 32-bit MSFT product used PAE and they did not want to cause less memory for the only important (from their point of view) 32-bit OS (ie Winblows). Notes: - using PAE results in a performance reduction. I have never found it to be a net loss, more memory makes the system faster to a greater extent than PAE makes it slower (my experience). I have also tested PAE/non-PAE and not been able to find a noticeable difference in performances. - 32 bit versions of many programs run faster than the 64 bit version, because they are smaller and nicer to cache. This is another small effect, not a big deal. You can never generalize about 64bit is always faster, some are going to be faster on 32-bit (as you found) some are going to be faster on 64-bit, too many people assume that since 64-bit has more registers, and a few extra instructions that it is always faster than 32-bit. - 2.6.27 offers both MTRR cleaning and use of PATs. Read the linux kernel mailing list and Intel docs for PATs, LKML for MTRR cleaning. Short answer is that you are likely to use memory better with 2.6.27 and later, that's certainly the case in my experience. Previous to 2.6.27 linux took the mtrr's that the bios offered and did not mess with them (except for X adding one for certain drivers).It appears that much work has gone into linux doing extensive adjustments with the mtrr stuff to make things more optimal. It likely helps that there are a couple of expert AMD and Intel guys working on correcting the various bios writes mtrr mess ups. Check to see if any bios settings change things, on the higher end boards there use to be a memory hole setting that could be set to hardware or software, though if I remember correctly setting it such that you found all of the memory also resulting in the machine being a couple of percent slower. You show your age by remembering that, and I show mine for remembering the details. It seems that some hole settings resulted in using memory which couldn't be cached (not enough address bits in cache memory). That made the memory so slow that programs were written to use it for swap or ramdisk. I had such programs for both MS-DOS and Xenix. I remember those machines, this was more recent. The machines that I saw this one were only about 2 years ago and using software vs hardware memory hole made a 3-5% difference in spec numbers. With one I got all of the memory but it was 3-5% slower, and in this case the spec number was more important than having all of the memory. I believe it was a dual socket board. Roger -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: mtrr funnies
Wolfgang S. Rupprecht wrote: Roger Heflin [EMAIL PROTECTED] writes: Wolfgang S. Rupprecht wrote: On the AMD's I remember one of the AMD experts mentioning that the 4GB memory stuff is automagic so is not listed as a MTRR at all. It is just there. Does cat /proc/meminfo and top both show around 8GB like expected? Yes, it shows most of the 8gig. About half a gig are missing, but then the bios boot screen also mentions that only 7.6 gigs are being made available. I wonder why the rest isn't remapped. to the top of ram. -wolfgang I know a bios engineer once told me that some chipsets/bios can only remap entire dimms (not parts of a dimm) and doing an entire dimm would result in only 2GB below 4GB and that bothers some vendors since it would cause issues with memory availability with 32bit only OSes. Check to see if any bios settings change things, on the higher end boards there use to be a memory hole setting that could be set to hardware or software, though if I remember correctly setting it such that you found all of the memory also resulting in the machine being a couple of percent slower. Roger -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: mtrr funnies
Wolfgang S. Rupprecht wrote: I've got a motherboard with a fairly new chipset (Asus M3A78T w. AMD/ATI 790GX) and I'm seeing a funny MTRR setting. I have 8GB memory and am running a 64-bit kernel, but I'm only seeing ~4GB mentioned in the MTRR's. Is this a bug? Do I need to add the upper 4+GB by hand? $ cat /proc/mtrr reg00: base=0x ( 0MB), size=2048MB: write-back, count=1 reg01: base=0x8000 (2048MB), size=1024MB: write-back, count=1 reg02: base=0xc000 (3072MB), size= 256MB: write-back, count=1 reg03: base=0xd000 (3328MB), size= 256MB: write-combining, count=1 It does seem like the kernel sees the whole memory, at least at times, but it isn't clear if that high memory is being cached the right way. Oct 7 10:54:30 poblano kernel: Memory: 7678940k/8650752k available (2699k kernel code, 184672k reserved, 1485k data, 980k init) -wolfgang On the AMD's I remember one of the AMD experts mentioning that the 4GB memory stuff is automagic so is not listed as a MTRR at all. It is just there. Does cat /proc/meminfo and top both show around 8GB like expected? Roger -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Using all of 4GB RAM... questions and Vista versus Linux...
Linuxguy123 wrote: I have a new HP hdx laptop with a Core Duo T8100 processor and 4 GB of RAM. $ uname -a Linux localhost.localdomain 2.6.26.3-14.fc8 #1 SMP Wed Sep 3 03:40:05 EDT 2008 i686 i686 i386 GNU/Linux Even though I have 4GB of RAM installed, Linux appears to only be using 3GB of it. $ free -t total used free sharedbuffers cached Mem: 3106944 7770562329888 0 60608 419608 -/+ buffers/cache: 2968402810104 Swap: 2040244 02040244 Total: 5147188 7770564370132 I've read in other posts to this group that the cause of this is that the BIOS remaps the some (1GB) of memory to serve as address space for PCI devices, thus creating a memory hole. I understand that some BIOSes allow one to remap those devices elsewhere in the map. My BIOS does NOT allow that option. There is really no other place to put the PCI devices except in the lower 4GB since anywhere else would result in 32-bit OSes being unable to access them. Questions: a) On machines that do not allow PCI remapping, is the processor physically disallowed from accessing that 4GB of RAM ? Ie have the address lines from the processor been disconnected from that RAM due to being connected to the PCI devices ? The chipset is not capable of remapping under certain conditions, or the bios won't do it because it would cause lower memory availability with windows. Some bios can only remap entire dimms, and that would result in less memory for a 32-bit only OS so they don't do it even though it would result in more memory for a 64-bit/PAE os. b) How do XP and Vista handle this ? Are they limited to 3GB of RAM too ? In the case of a bios limitation they would also be limited to only 3GB. c) I am running the 32 bit version of Linux. Would it make any difference to my RAM access if I ran the 64 bit version ? Some bioses will remap memory to above 4GB, but often only if a certain option is set, and often these options are only available on server class MB's, though these options may now be showing up on desktops since desktops can now support more memory. You would have to boot a PAE or 64bit kernel and mess around with bios options to see if you bios can do it, it may or may not be able to do it in a useful way. And of course the bios options are poorly documented. Roger Thanks -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Using all of 4GB RAM... questions and Vista versus Linux...
Linuxguy123 wrote: Here is the spec sheet for my laptop. http://h10025.www1.hp.com/ewfrf/wc/document?docname=c01490775cc=uslc=endlc=enproduct=3747924 It says: Memory 4096 MB Memory Max Up to 4GB DDR2 (Up to 1 GB may not be available due to 32-bit operating system resource requirements) That does not look positive. Since the machine only supports up to 4GB the bios would be less likely to go to the trouble of adding options to support remapping, and that statement appears to indicate that they did not worry about PAE/64bit OSes. You might see if there is a bios update that changes things. Also the major vendors appear to have less options to tune things in the bios than many other MB makers. Roger -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Greater than 2TB disks bootable?
Phil Meyer wrote: There is a lot of confusion available from articles on the Internet about whether or not a greater than 2TB disk can be made bootable in Linux. In order to go that large, the disk must be labelled, via partd, as type GPT. Ok so far. Now, is it possible to use fdisk to cut off 100MB or so for a normal /boot partition? It seems that labelling a disk as GPT does not stomp the MBR, but does affect the partition table. Is this correct? fdisk has issues with 2TB. If I create a 100MB partition using fdisk, and then label the disk as GPT, can I start the large partition with the first cylinder than what I cut off for /boot and expect it to be seen? Anaconda complains that GPT is not bootable. Is that system specific, BIOS specific, anaconda error reading the BIOS, ??? Here is the specific scenario: An intel based server, with 10 1TB drives attached to a SATA RAID device. The RAID is level 5 with 9 drives and a hot spare. If it is a hardware raid controller it is generally possible to partition it in the hardware raid controller (either separate the big r5 into 2, or define 2 separate raid's over the same disks with one only taking up a small part of everything) to setup the boot device 2TB. I have done this before with 3ware and Areca controllers, and would bet almost all of the raid controllers have this ability. Check the manual for the raid controller, it may or may not be able to do it. Roger -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: desperately seeking IgnoreEDID
Robert P. J. Day wrote: i'm still fighting to get my WUXGA display laptop to ignore the EDID information coming back from a video device, so i simplified the problem and here's what's happening so far. i have a fresh install of f9 on an aging dell inspiron 9200 with a full WUXGA display, and i'm trying to drive a full-res WUXGA signal into an external video processing device that is (theoretically) supposed to be able to handle that. if i connect my laptop to an external full WUXGA flat-panel (Samsung) display, no problem -- the image is perfect, pixel-for-pixel, and full WUXGA on both laptop and external monitor. if, however, i connect the laptop to that external video device, that external device is (apparently) returning EDID information that claims to not be able to accept full WUXGA (even though it should be able to, allowing us to conclude that its EDID info is simply wrong and we'll have to fix that at some point.) and doing that also forces my laptop down to a lower resolution. argh. i figured that a simple solution is to just configure my laptop to ignore incoming EDID and keep driving the signal at full WUXGA, but i can't get that to work. here's my change to /etc/X11/xorg.conf (text copied by hand as the laptop is not on the net): Section Device Identifier Videocard0 Driver Radeon Option IgnoreEDID True -- added this EndSection as an experiment, i connected the laptop to a flat panel dell 1280x1024 display to see what would happen, logged out, logged back in, and the Xorg log file contains the line: (**) RADEON(0): Option OptionEDID True which i would have thought confirms the ignoring of incoming EDID, but i still get the same effect of having my laptop resolution dropped noticeably (in this case, to 1152x864, according to xdpyinfo), ostensibly to accommodate the decreased resolution of the external monitor. so, 1) is there something else i should be trying to get my laptop to totally ignore the fact that it's connected to an external device that claims to not be capable of full WUXGA, and 2) if i succeed in ignoring EDID with this test flat panel, obviously, the flat panel can't handle that (full WUXGA) signal so i'm not expecting to get a useful image, but is there a chance i could damage the flat panel? open to suggestions. rday You might try UseEDID as: Option UseEDID FALSE And see if it works any better. Roger -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: desperately seeking IgnoreEDID
nope, that made no difference. in fact, from the X log file, it doesn't appear that it had any effect at all. at least with Option IgnoreEDID True the contents of the X log file suggest that EDID processing is cancelled (even though it clearly isn't). with the option above, the X log file shows that EDID processing is occurring normally. in short, still doesn't solve the problem. rday It looks like those options are specific to each driver, and there does not seem to be any standardizations among them. Other possible ones are: DDCmode and DDC You might also be able to use: Option MonitorLayout [type on primary], [type on secondary] where types are: NONE -- Not connected CRT-- Analog CRT monitor TMDS -- Desktop flat panel LVDS -- Laptop flat panel And select NONE for the secondary to disable it. The EDID stuff always annoys me, my old 20 monitor does not appear to return proper info for its top resolution even though the original docs list it as supported at the given resolution and refresh rate. Roger -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Ntpdate fails to start
Paul Smith wrote: On Sun, Sep 7, 2008 at 2:19 PM, Paul Smith [EMAIL PROTECTED] wrote: At booting, ntpdate fails to start, and also the following command fails: # /sbin/service ntpdate start ntpdate: Synchronizing with time server: [FAILED] # The log messages are: Sep 7 12:50:50 localhost ntpdate[2908]: the NTP socket is in use, exiting Any ideas? service ntpd status Should show you that the ntp daemon is already running. You can't run both ntpd (the server) and ntpdate (the client) at the same time. Thanks, Stuart and Edward. Got this: # /sbin/service ntpd status ntpd (pid 2059) is running... # ntpdate tries to start at booting. So, should I disable it? Which one of the two should I have running in order to have always a correct time on my computer? either, but not both. I suggest ntpd, particularly if you run more than one machine. A local time server can be specified with the prefer (from memory) option, and that will be used if available. See the man pages on this. The nice thing about running your own server is that if your network connection drops your machines will all stay together, handy if you are trying to match logs from one machine to another. If you run just one machine it probably doesn't matter. Thanks, Bill. I am running only one machine. How can I remove one of them from trying to start at booting? Paul You may actually want both. On a typical setup ntpdate runs first (and exits) and syncs the clock close but not exactly on. If this is not done and the time is off by more than a certain amount then ntpd *WON'T* be able to sync things, and will exit with an error. Then after ntpdate gets things close, then ntpd keeps things in proper sync. stop both ntpd and ntpdate, and then start ntpdate and then start ntpd and if both succeed things is likely correct and ntpdate runs and then exits. In F8 ntpdate is ran in the ntpd script to sync things in, and then ntpd is started, they could have separated it in F9. The only way ntpdate would be sensible as a replacement is *if* something is running it every so often to keep things close, otherwise one the machine came up things would start to drift, and things would get worse the longer things were up. Roger -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Nvidia driver
Claude Jones wrote: On Tue August 26 2008 9:20:00 am Per Anton Rønning wrote: rpm -qa | grep kernel returns this: kernel-PAE-2.6.25.14-108.fc9.i686 kernel-headers-2.6.25.14-108.fc9.i386 kerneloops-0.11-1.fc9.i386 kernel-PAE-2.6.25.11-97.fc9.i686 kernel-2.6.25.14-108.fc9.i686 And this seems to be the same as the last result. My machine has 4 GiB ram installed, of which 3.7 GiB is effective. uname -a gives: Linux localhost.localdomain 2.6.25.14-108.fc9.i686.PAE #1 SMP Mon Aug 4 13:57:11 EDT 2008 i686 i686 i386 GNU/Linux I sent a posting about some progress in the matter (my last one) - but I still seem to miss something (ref posting) well, one thing that's wrong is that you're running the PAE kernel with less than 4 GB of memory...I don't think that has anything to do with your nvidia problem, but, if it were me, I'd remove the PAE kernel - it has no business being even installed on your machine Don't count on that, the 4GB thing is a very very rough and often wrong *SIMPLE* rule. Just because a machine has under 4GB of ram does not mean that the PAE kernel won't give you more memory.The bios *CAN* (some do, some don't) remap something that is covered by a video card, or otherwise reserved for something to above 4GB requiring a PAE kernel to use it. And this can start happening at around 3GB of ram or more, the only way to know if PAE is correct for a given setup is to either know exactly what the bios is doing or to test it. It all depends on exactly what the bios is doing, he would need to boot a PAE and a non-PAE kernel and check how much memory is being seen by each, if they are the same or really close (within 100MB) I would avoid the PAE kernel. Roger -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Nvidia driver
Claude Jones wrote: On Tue August 26 2008 10:52:21 am Roger Heflin wrote: Don't count on that, the 4GB thing is a very very rough and often wrong *SIMPLE* rule. Just because a machine has under 4GB of ram does not mean that the PAE kernel won't give you more memory.The bios *CAN* (some do, some don't) remap something that is covered by a video card, or otherwise reserved for something to above 4GB requiring a PAE kernel to use it. And this can start happening at around 3GB of ram or more, the only way to know if PAE is correct for a given setup is to either know exactly what the bios is doing or to test it. It all depends on exactly what the bios is doing, he would need to boot a PAE and a non-PAE kernel and check how much memory is being seen by each, if they are the same or really close (within 100MB) I would avoid the PAE kernel. Interesting... I'll make this a keeper and test soon. I build most of my machines with 4GB of ram now, but that's in Windows land at work - they tend to filter my way as older ones are superceded or retired - my current Linux machines all top out at 3GB If the bios maker *ONLY* worries about having max ram with 32-bit Windows, then it is likely that the did not remap above 4GB, but sometimes there is a bios option to change this behavior to work better for Linux and/or 64-bit windows. Given that windows is changing then it becomes more likely for them to be remapping above 4GB.If they don't remap above 4GB they will maximize the memory usable for 32-bit windows (depending on the exact hw, they may have to remap larger amounts than are actually covered and that would lower the ram usable under 32-bit windows, so no remap is better for 32-bit windows in this case), but a proper remap would allow anything using PAE (I thought the server versions of Windows did use PAE) or 64bit to have more ram that without the remap. And of course it all depends on exactly what the bios engineer for the MB company decided to do, and often it depends on what they classify the motherboard as, server boards and boards that support more than 4GB are more likely to have the options to do remapping as they already expect someone to be using either PAE or 64bit. Roger -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Nvidia driver
Per Anton Rønning wrote: Claude Jones wrote: On Tue August 26 2008 10:52:21 am Roger Heflin wrote: Don't count on that, the 4GB thing is a very very rough and often wrong *SIMPLE* rule. Just because a machine has under 4GB of ram does not mean that the PAE kernel won't give you more memory.The bios *CAN* (some do, some don't) remap something that is covered by a video card, or otherwise reserved for something to above 4GB requiring a PAE kernel to use it. And this can start happening at around 3GB of ram or more, the only way to know if PAE is correct for a given setup is to either know exactly what the bios is doing or to test it. It all depends on exactly what the bios is doing, he would need to boot a PAE and a non-PAE kernel and check how much memory is being seen by each, if they are the same or really close (within 100MB) I would avoid the PAE kernel. Interesting... I'll make this a keeper and test soon. I build most of my machines with 4GB of ram now, but that's in Windows land at work - they tend to filter my way as older ones are superceded or retired - my current Linux machines all top out at 3GB I'm am afraid that it is beyond my qualifications to start kernel management. First I must know the difference between these kernels, hwich I dont. It seems that I need to take a course in advanced Linux to embark upon a venture like that,. So for now I'd better be happy with the two optional screen resolutions that I have, and the 800x600 is not bad at all, I can live vith that without someone holding a gun to my head. Now, I happened to find ftp://download.nvidia.com/XFree86/Linux-x86_64/1.0-8174/README/64bit_html/index.html NVIDIA Accelerated Linux Driver Set README and Installation Guide *googlig for the nvidia-xconfig. * *It is a lot of stuff here that I have to spend some time on, and hopefully I will be better equipped to handle this. Brgds PAR * * * Per, Boot both the PAE kernel and the non-PAE kernel (through the grub screen), boot each and do a cat /proc/meminfo and check MemTotal, if they are about the same use the non-PAE kernel as the PAE kernel won't help you. From your list these 2: kernel-PAE-2.6.25.14-108.fc9.i686 kernel-2.6.25.14-108.fc9.i686 Roger -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: H.D. install problem -
Bob Goodwin wrote: Tim wrote: On Sun, 2008-08-24 at 19:58 -0400, Bob Goodwin wrote: I had hoped to make the new drive a third one but sadly I found only two SATA connectors on the motherboard so I had to revert to plan B. Or there's plan c - buy a SATA card to plug into your motherboard. SATA card: This is the only one I see that recognizes the existence of non Microsoft operating systems [there are some that mention Apple OSX] but do I care? This one has a raid function [which I don't need] that might require MS software but I would expect a controller card to just work except possibly for some change in the BIOS settings? HighPoint ROCKETRAID1520 W/O PCI SATA Controller Card - *Operating Systems Supported:* Windows 98 / ME / NT4.0 / 2K / XP / 2003 Linux (SuSE, Red Hat), and FreeBSD It looks to me like a $15 or $20 card ought to work by just plugging it in without Windows but I need reassurance. Does anyone know for certain? Bob Run away from that card, supported by linux typically means that they include a driver in the box. Any of the Sil* based cards should work, and should be really really cheap ($30). Roger -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: H.D. install problem -
Bob Goodwin wrote: Roger Heflin wrote: Bob Goodwin wrote: Tim wrote: On Sun, 2008-08-24 at 19:58 -0400, Bob Goodwin wrote: I had hoped to make the new drive a third one but sadly I found only two SATA connectors on the motherboard so I had to revert to plan B. Or there's plan c - buy a SATA card to plug into your motherboard. SATA card: This is the only one I see that recognizes the existence of non Microsoft operating systems [there are some that mention Apple OSX] but do I care? This one has a raid function [which I don't need] that might require MS software but I would expect a controller card to just work except possibly for some change in the BIOS settings? HighPoint ROCKETRAID1520 W/O PCI SATA Controller Card - *Operating Systems Supported:* Windows 98 / ME / NT4.0 / 2K / XP / 2003 Linux (SuSE, Red Hat), and FreeBSD It looks to me like a $15 or $20 card ought to work by just plugging it in without Windows but I need reassurance. Does anyone know for certain? Bob Run away from that card, supported by linux typically means that they include a driver in the box. Any of the Sil* based cards should work, and should be really really cheap ($30). Roger Yes, that's what I thought but I have been reluctant to order one until someone verified it. I'll pick one from Newegg's list and order it this afternoon. They show a bunch of them. Most limited to 1.5 gB/s. The drive I bought is spec'd for 3 gigs but I noticed it came jumpered for 1.5? Don't know what the one I removed is rated for. But it has the /boot/ file on it and it would make my life easier to just use it. So far I am quite happy with F-9, even sound works once I got the speaker plug in the right jack, no pulse audio problem here. Tnx. Bob 1.5 or 3 won't matter. It is unlikely the drive itself will overload the 1.5 stuff. The best (they cost quite a bit more-WD Raptors) drives top out at sustained rates of 100MB/second (about 1.0 Gbps), normal drives only do about 60-75MB/second, and likely if you put multiple drives on those boards you will hit the PCI bus limit which is lower than 1.5Gbps (132MB/second), so it won't matter one bit what the actual SATA connection speed is. Roger -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: [OT] Machine won't boot
Marko Vojinovic wrote: On Wednesday 20 August 2008 15:14, Ed Greshko wrote: What motherboard are you talking about...and what time frame are you certain was the time when it was manufactured with faulty capacitors? What I know is not precisely for one specific type of motherboard. It's just that during the Pentium II / III era it was like general practice to put cheap capacitors on motherboards. Note --- *cheap*, not faulty. This means that the lifetime of some capacitors was as a rule far shorter than that of the motherboard, and the outcome was that motherboards often needed replacement after a year or so. Those caps were faulty besides being cheap, the company making them tried to borrow a design from someone else and the design spec they borrow was missing additive(s) that resulted in the caps having a much much shorter life. There was discussion at the time of whether the borrowing company got an early unfinished design, or whether the company with the working design passed them a design that was good enough to pass initial test and fail down the road. See: http://www.geek.com/capacitor-failures-plague-motherboard-vendors/ And besides the p2/p3 era failure, a second failure from an expensive cap maker came along a couple of years after that and hit Dell and Intel MB's, Dell took write downs on the company reports of about US$270,000,000 that quarter. This was for the caps being faulty because they were overfilled (the formula was correct). See: http://en.wikipedia.org/wiki/Capacitor_plague And as of 2005 there were still bad caps around as I have a video board with several bad ones one them that should have been built *AFTER* both of the above events (9/2005, the Dell event caps were built in 2004), and failed 4 of the caps after around 3 years of usage. . Also, while my knowledge on electronics is fairly limited, I believe that capacitors are the one type of component on the motherboard that is most likely to fail after some time. Resistors, transistors and ICs have much bigger lifetime, in my naive opinion. And the very role of capacitors --- to iron out peaks in voltage or whatever --- puts them on the front line for bad external conditions. The caps with liquid in them have at best limited lifetime, though if built correctly will typically last longer than needed, a number of the MB makers are going to solid caps with no liquid in them just because of how difficult it is to make a small high capacity small liquid capacitor with a long life. If they did not have to be small, high capacity, and long life all at the same time there would not be an issue, making them physically larger would have reduced the stress on the component and increased the life. Oh, and you can know that a capacitor failed by visual inspection (if it is deformed in shape and/or has traces of electrolyte flowing out) or by taking it off the motherboard and using an ohm-meter. Generally it is obvious on visual inspection, especially if there is liquid/crusty material on the cap.Also if you have several identical ones and some of them look different that is a bad sign. Roger -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Intel 82541GI NIC comes up at 10mbps on one port
Mikkel L. Ellertson wrote: Sam Varshavchik wrote: Mikkel L. Ellertson writes: Try using ethtoolto lock the port to 100 Mbs Full Duplex. It is probably that the two do not handshake correctly to set the faster speed. If I remember correctly, that was one of the things that the exact protocol was not specified, so not all hardware works correctly. I should've mentioned that I tried that too. By itself speed 100 has no effect, and the link still comes up auto-negotiated at 10mbps. If I use speed 100 autoneg off the '100mbps' LED indicator on the router does come on, but the NIC is completely dead and does not respond to pings. Adding an explicit duplex half or duplex full to the mix makes no difference. I've also tried unplugging and plugging the cable after forcing the speed to 100. The router itself, as I mentioned, has no configurable knobs, just the ports and nothing else. I'm guessing that even after forcing the speed to 100mbps, the router wants to negotiate something. Sorting through the documentation for e1000.ko, there's a module option to limit advertised link speeds to 100 mbps only, that is, auto-negotiation remains on but the card won't advertise 10 mbps speed. After enabling that option, the port does not come up at all. Well, there goes the simple fix. I would not expect configuration knobs on the router. There should be configuration web pages when you open the routers address in a web browser. http://192.168.0.1 or http://192.168.1.1 is the default address, if I remember right. It is in the router manual. But it probably does not have anything to help you with your problem. Mikkel In the past having one side negotiating and not the other got generally bad results (usually 10-half duplex was the default if negotiating failed, no matter what the other side was forced to-and things worked really really bad). On my linksys router (with the add-on linux DD-WRT software) I can set each port to autoneg/100/FD, so it may be possible on a standard router with the standard linksys router software. Roger -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: spooky coincidence or disk killer virus?
Alan Cox wrote: Is this just a sign of superb quality control in the samsung disk factories turning out identical disks that last almost the exact same amount of time in the same CPU case with the same number of power cycles? I gad a very similar thing happen with IBM disks and a raid 1 array. That near miss taught me a lesson about mixing drives in a raid array. Or is there some spooky virus around that can actually destroy the electronics in disk drives (both disks appear to be so dead they can't even be recognized as disk drives by the BIOS). In theory some drives can be firmware flashed and destroyed. In practice there are several more likely things I can think of as well as the identical disks case: - Power problems - Exposure to strong magnetic fields (the firmware is mostly stored on disk so if you trash the disk in a big magnetic field it may not register in future..) I would not count on any magnetic field anyone reasonably comes in contact with doing much of anything to a disk. The disks already have some of the most powerful permanent magnets inside of the disk case within an inch of the disk. And degaussing a disk is almost impossible to do by accident, and in fact it takes a pretty expensive machine to do a proper job of it ($100k US). I know a few years ago somewhere I worked tried to degauss some 8mm tapes and did not have any luck with any of the handheld degaussers, all of the tapes still read just fine, and the current disk material is rated to require close to 10x the magnetic field strength of those tapes, so are even harder to mess up. - Nearby lightning strike damaging electroncis. That would be more likely, I had one of my users take a machine overseas (US 110V machine, not an auto voltage power supply) and someone got the correct local cord and plugged it in without moving the switch to 220. That took out the PS, one of the 2 hard disks, and a few other things, with just a bit more voltage it would have likely gotten everything... Or it could just be chance That is very possible if both disks came from the same batch, I have seen what good process control does when there was a underlying process problem that no one knew about... Usually when I have lost a large portion (or all) of a single lot it has been a spin-up failure (I assume bad lube, or bad bearings, or a bad motor, or ???), and they all tend to fail pretty consistently and usually the ones that have not failed yet consistently fail on the next reboot or power up of any machines with that same disks model in them. Roger -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: PAN Failure -- Help
MIKE - EMAIL IGNORED wrote: On Tue, 12 Aug 2008 20:24:57 -0500, Roger Heflin wrote: MIKE - EMAIL IGNORED wrote: I am talking to you from my laptop (running F8 and pan-0.132-2.fc8) because my desktop (running F7 and pan-0.131-1.fc7) suddenly stopped working. When I start pan (under KDE), its GUI flashes briefly and then disappears. Other things, including Firefox and Apache seem fine so far. Thanks for your help. Mike. If you have not already, open a terminal window and try starting it in there and see if it will give your an error. It puts its config files in ~/.pan2 and there are some things in there that could be delete without it being and issue (cache) but others are a bit more trouble if you delete them. If you don't get an error I would try doing mv ~/.pan2 ~/.pan2.bad and then start it again and see if it works, if this makes it work, there is something in the .pan2 directory that disagrees with it. iv=ch Roger Thanks for this. Starting from a command line results in the dump below. Can anything be discerned from it? (I deleted the long memory map, which I will post if anyone thinks it would be useful.) I renamed the .pan directory as suggested, and pan then works. I guess if there is no better suggestion, I'll restore the .pan directory and start moving out files, starting with the latest modified (tomorrow at standard -0500). Mike. The error is not terribly useful, I doubt there is going to be a better suggestion than to try a few files at a time, though you may be able to run strace -o pan.out -f pan on the command line and see what was the last file being accessed by pan and guess which file is the troublemaker. If you can isolate it down to a single file you might look at that file and see if it is obviously wrong. Though, It may just be that something in the cache is odd and causing the crash. Roger -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: PAN Failure -- Help
Mike -- EMAIL IGNORED wrote: On Wed, 13 Aug 2008 08:30:29 -0500, Roger Heflin wrote: [...] The error is not terribly useful, I doubt there is going to be a better suggestion than to try a few files at a time, though you may be able to run strace -o pan.out -f pan on the command line and see what was the last file being accessed by pan and guess which file is the troublemaker. If you can isolate it down to a single file you might look at that file and see if it is obviously wrong. Though, It may just be that something in the cache is odd and causing the crash. Roger Back on my desktop. The problem was solved by removing tasks.nzb . The software created a new one. The file is a 166 line XML file; a quick look did not show any problem, but I did not spend much time on it. Unless advised otherwise, I intend to discard it. If anyone wants to see it, please let me know, and I'll post it. Thanks again, Mike. If you don't mind, send it to me, and I will see if it crashes mine here, and take a closer look at the file. Roger -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: PAN Failure -- Help
MIKE - EMAIL IGNORED wrote: I am talking to you from my laptop (running F8 and pan-0.132-2.fc8) because my desktop (running F7 and pan-0.131-1.fc7) suddenly stopped working. When I start pan (under KDE), its GUI flashes briefly and then disappears. Other things, including Firefox and Apache seem fine so far. Thanks for your help. Mike. If you have not already, open a terminal window and try starting it in there and see if it will give your an error. It puts its config files in ~/.pan2 and there are some things in there that could be delete without it being and issue (cache) but others are a bit more trouble if you delete them. If you don't get an error I would try doing mv ~/.pan2 ~/.pan2.bad and then start it again and see if it works, if this makes it work, there is something in the .pan2 directory that disagrees with it. Roger -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Hardware trouble? Me? Or ...??
Beartooth wrote: My #1 machine (with F9 on one hard drive, and XP (to run topo maps) on the other) won't do anything; it doesn't even turn its little blue light on. This *could* be my doing. Fool that I was, I went and fiddled with what I had in sys-config-network, or whatever its name is, and also edited /etc/X11/xorg.conf. Logging out and in didn't do what I was trying to. I clicked on reboot, meaning while I was at it to go into the XP drive long enough to update the virus software. It hung up, early in the reboot sequence -- just starting to shut down, in fact, iirc. Reset button did nothing; power button did nothing; I pulled the plug, and walked away. When I came back, nothing I could do would make it so much as turn its blue lights (nor, afaict, a fan) on. This is really really hard to make happen with software.Outside of something in the software losing its mind and corrupting the CMOS settings I have not seen software make a machine not do anything, and even in the CMOS case I believe it did actually turn on fans, just nothing else happened. The UPS is on, and running both the monitor and a laptop. I tried moving the power cable to a different outlet on the back of the UPS; that didn't help either. Has the whole machine chosen this odd moment to die the death? (They do always choose odd moments, don't they?) Or is there hope? Btw, I don't speak hardware; but I have a very capable young friend who is just getting into the business of making computer house calls; I have emailed him,and he'll reply eventually. If the blue light is the normal power on light in the machine, likely it picked a bad time to die.If it is not powering on MB or power supply would be likely and those also seem to be the most common components to die too, probably because they both have a number of capacitors, and capacitors have been a real issue in the last 5-10 years (designed wrong, built wrong,.) Roger -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Unable to compile kernel-2.6.19.2 on FC 9
Vishwas Dubey wrote: Hi All, I am trying to build and compile a new kernel. Currently, I have linux-2.6.25.11-97.fc9.i686 installed on my machine, which I use to build and compile the new kernel for linux-2.6.19.2. I follow the standard procedure for building and compiling the kernel, but still I am unable to boot my machine from the new kernel. I get the following errors when I try to boot the machine from the new kernel:- Uncompressing Linux... OK, booting the kernel ACPI: Getting cpuindex for acpiid 0x2 ACPI: Getting cpuindex for acpiid 0x3 Red Hat nash version 6.0.52 starting irq20: nobody cared (try booting with the irqpoll option) handlers: [c127ae0f] (usb-hcd-irq+0x0/0x56) [c127ae0f] (usb-hcd-irq+0x0/0x56) Disabling IRQ #20 stabilized: open /proc/scsi/scsi : no such file or directory mount: could not find filesystem '/dev/root' setuproot: moving /dev failed: no such file or directory setuproot: error mounting /proc: no such file or directory setuproot: error mounting /sys: no such file or directory mount failed for selinux on /selinux: no such file or directory switch root: mount failed: no such file or directory There are 3 possibilities. #1: is you don't have the device driver needed for old kernel in the initrd. #2: That device driver in 2.6.19 does not work at all for your hardware or does not exist for your hardware in 2.6.19. #3: The old kernel won't work for your hardware at all because of other issues. There are *NO* easy solutions if the problem is #2 or #3, and if your hardware has a newer chipset than existed when 2.6.19 was released then #2 or #3 are very possible. If it is #1 you need to see what the original kernel loads to drive the disk subsystem and see if that is enabled, and installed in the initrd in 2.6.19, and any modules that it needs are there with it. You might try some older recovery CD's, if you find one that works and it is a kernel from around 2.6.19 then you would be able to find the module names used in 2.6.19. I believe a number of the disk modules names have been changed around since 2.6.19 so very likely you don't have the proper module being included in the initrd. Roger -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: NFS mount points (directories) inaccessible in RunLevel 3
djgardner wrote: I have seen the following issue on several and current Redhat Linux distros. I'd like to understand the problem and avoid it. More importantly, I want to fix the problem on my current server. As root, I created 5 directories under /mnt and mounted remote directories via NFS. All was well for weeks. I added a new hard drive (/dev/sdb) and mounted it under /tmp to move files onto it. I umounted then remounted /dev/sdb1 in it's final location (/web.) I then restarted the server and found the directory entries under /mnt were not visible and therefore, unable to be NFS mount points. The new drive mounted fine. I dropped the server into Run Level 2 (from 3) and could see the five directories under /mnt. This is driving me crazy, thus I am missing something. Can someone identify that something? It has always worked fine for me, and I almost always run things at runlevel 3. You should check: chkconfig --list nfs and see if it lists nfs as being on at runlevel 3. Also post the contents of /etc/fstab. Roger -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: No space for new partition on SATA drive, but 61GBfreespace
Nigel Henry wrote: This is the first time that I've used SATA harddrives on this new machine that I've built, so am a bit in the dark. Fedora 8 is using sda1 for / , and sda2 for /home. sda3 is swap sda4 (the 4th primary is the extended partition) sda5, and 6, are / , and /home for another linux distro sda7, and 8, are / , and /home for another linux distro sda9, and 10, are / , and /home for yet another linux distro sda11, and 12, are / , and /home for another linux distro There is still showing 61020 MB of free space on the drive, but trying to create a new partition for the install of Fedora 9, with 1MB for / I get the following output. Written in freehand. Error Partitioning ould not allocate requested partitions: Partitioning failed: Could not allocate partitions as primary partitions. Not enough space left to create partition for /. I'm sure I've seen some stuff about partition limits on SATA drives, but can't remember where. If there are limits, are there any workarounds so that I can use this 61+GB of freespace. Thanks for any suggestions. Nigel. It is not a SATA thing. You only get 4 primary partitions, usually the last of the primaries is an extended partition containing *all* of the rest of the space, if the last partition does not contain all of the rest of the space, well, you cannot use it without repartitioning. There does not seem to be a limit on the number of the partitions in an extended partition, but there could be limits in some of the tools to deal with things. There is a limit of the total number of partitions that a single disk can have and I think that was 16 so your aren't quite there yet. I would suggest not creating /home for each installation (just for the first one) and then changing fstab to mount a shared home, the only steps that would need to be done to properly do this would be to make sure the UID/users on all distributions are the same, and make sure fstab on each distribution has it added as an entry. Roger -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Can I get a word in edgewise here, puhlease?
Gene Heskett wrote: Does anyone know how to make that work, or, how to change channels in the xine front end? I can't find a channel up/down function in its gui. No... Don't actually use xine for this purpose. What do you use? xine works, but it sure is kludgy to change channels. A minute or more with lots of false starts, specially for the hi-def subchannel. Thanks Ed, now if we could get this list back to its stated purpose. Gene, I use mythtv for all of that stuff, both recording and watching TV. If you are watching 1080i or 720p it does require a reasonable CPU and video card to do it. And mythtv can be run in a window, but the default config is full screen. Somethings I watch live, but generally I record it and may watch it almost live (a few minutes behind the current recording) or days later. Roger -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Can I get a word in edgewise here, puhlease?
Gene Heskett wrote: On Tuesday 29 July 2008, Roger Heflin wrote: Gene Heskett wrote: Does anyone know how to make that work, or, how to change channels in the xine front end? I can't find a channel up/down function in its gui. No... Don't actually use xine for this purpose. What do you use? xine works, but it sure is kludgy to change channels. A minute or more with lots of false starts, specially for the hi-def subchannel. Thanks Ed, now if we could get this list back to its stated purpose. Gene, I use mythtv for all of that stuff, both recording and watching TV. yes, but setting up a mythtv system needs real time access to a mythtv guru, and a couple of days to build everything. The guru I have, but he has limited time too. Not really. With no mythtv experience it took me less than a day to setup my original system (putting it on a already running fedora 7 system at the time), the second time I set it up took 2 hours, and that included compiling mythtv from source. And if you do attempt it there is a mythtv list with a number of guru's on it which usually respond reasonably quickly if you can properly describe the issue, but for the most part the howto's describe the steps needed. If you are watching 1080i or 720p it does require a reasonable CPU and video card to do it. And mythtv can be run in a window, but the default config is full screen. One proggy I watched last night claimed to be 1920x1050 or some such figure. And it did miss-fire occasionally since its a good 70 air miles to the transmitter and WV's topology is vertical. Its been said from more than one podium that if WV was stomped out flat, it would be the biggest state in the union. I could see what, I am only about 40 miles from the antenna and if the weather is being difficult things sometimes get messy. Roger -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: stop kernel messages from splashing on the console
Vikram Goyal wrote: Hello, I am getting these kernel messages on the consoles which I want to avoid as many times I have to login through them as the system runs in level 3. I have edited the /etc/syslog.conf as: #kern.* /dev/console kern.*/var/log/kern_messages # Everybody gets emergency messages #*.emerg * *.emerg /var/log/kern_messages Still the messages are getting splashed on to the ttys. The messages are: Jul 27 04:04:55 smcindiaonline kernel: EDAC MC0: CE - no information available: e7xxx CE log register overflow Jul 27 04:04:56 smcindiaonline kernel: EDAC MC0: CE page 0x7e9eb, offset 0x0, grain 4096, syndrome 0x8304, row 2,channel 1, label : e7xxx CE What other tweaks need to done to avoid these? You could replace the memory that is generating the errors, this error is indicating that your memory is having severe errors. Or you could just rmmod the edac modules since you are ignoring the errors. There are a number of things in /sys/module/edac_core/parameters/ the most important being edac_mc_log_ce which would turn things off without rmmod'ing the module, but if one is ignoring the errors, the you might as well turn off the module. From the man pages it is not clear to me if syslog actually handles the internal kernel messages going to the console, there is also klogd, and I know internal messages still make it to the console even when userspace is screwed up badly, so I would suspect that the klogd thread in the kernel is handling it. Roger -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: PAE kernel and 4GB of memory
Howard Wilkinson wrote: I am looking for a definitive answer to the question of where the PAE kernels become useful. I have seen various articles that mention needing PAE kernels if you have more then 4GB of physical memory in a 32-bit processor environment. I have also seen statements that say you need them if you have 4GB or more of memory. Now which is right? Also, even if you need a PAE kernel because the last few bytes are not addressable when you have exactly 4GB is this useful or is the trade off of larger page tables and pages going to eat any benefit of being able to address these few bytes and if so when does the PAE kernel become useful? Howard. It depends on the bios, you would have to try with and without the PAE kernel and see if the amount of usable ram changes. Some bioses won't remap any memory below 4GB (that is covered by something else) to over 4GB, if your bios does not remap anything above 4GB when you only have 4GB (or less) then PAE won't buy you anything.And since often moving the covered memory from below 4GB, sometimes means moving some non-covered memory and therefore lowering the memory usable for an OS that does not support PAE-ie that other OS, often the bios *WON'T* move the covered memory at all because it would lower the usable memory below 4GB for that other OS. This is almost always true on the Desktop class MB's, and it is sometimes true on the higher end stuff also. Roger -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Program to compress AVI files
Paul Smith wrote: On Mon, Jul 14, 2008 at 7:54 PM, Mark Haney [EMAIL PROTECTED] wrote: Is there some program to compress AVI files? Compress? Video and graphics files tend not to compress well at all. Are we talking ZIP compression? Or encoding to a smaller file size? Thanks to both. I am talking about encoding to a smaller file size. Any ideas? Paul mencoder would be a good program. I would suggest first playing it with mplayer and seeing what the current encoding is, if it is already xvid/divx/x264 encoded you won't be able to likely improve things much without lowering the resolution or quality. x264 is supposed to be better than xvid/divx but it is probably not a huge amount, and re-encoding (even on a fast machine) will take anywhere from greater than actual time of the video down to 1/4-1/5 for lower resolution videos. If it is not already one of the good codecs then just reencoding it with the proper settings will be able to reduce it a fair amount. I do a fair amount of re-encoding of various sorts. Roger -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Fedora 9 Install RAID Size Error
Tim Berryhill wrote: Fedora 9 install is failing on a new machine. I suspect the problem is related to my RAID's. I have two small, fast drives in a RAID 0 600GB array, partitioned into two drives which currently hold Vista and XP. I have three large, slow drives in a RAID 5 1.4TB array, as a single partition currently holding ISO's of Fedora 7, 8 and 9 and not much else. The RAID's are defined in the BIOS, using the Intel ICH9. The Fedora installs get past the media check (DVD is fine, it says). I select English and the us keyboard, and get no further response on that console. Randomly pressing keys, I realized alt-F4 offered me this clear statement: 6sde: rw=0, want=2930284536, limit=1465149168 6attempt to access beyond end of device Then I discovered alt-F2 gave me a shell prompt. After the install hangs, /dev includes sda, sda1, sda2, sdb, sdc, sdc1, sdd and sde. fdisk -l thinks sda is 300GB, roughly evenly divided into sda1 and sda2. fdisk -l thinks sdb is 300GB without a partition table. fdisk -l thinks sdc is 750GB with a single large partition. The last block number is very similar to the limit on the 6sde error message. fdisk -l thinks sdd is 750GB, without a partition table. fdisk -l thinks sde is 750GB with a single large partition. The last block number is very similar to the limit on the 6sde error message. So, it seems like my small array and my large array are each twice as big as Fedora sees, and at least in one section of code, Fedora performs a seek to a block which is outside the limit Fedora saw but near the end of the actual array. It seems more likely that it is seeing the underlying disks and not detecting the arrays at all, do those sizes match the sizes of your disks?The partition table on sda looks like the partition table for the R0 array which is why it gets those errors (the disk is too small for the partition table for the R0 array), and the partition on sdc and sde may be the partition for the R5 array, and again the partition table would be too large for the disk. I don't know if F9 supports that Intel controller's raid or not, but currently it does not look like it is finding them as raid. You may want to read up on dmraid installs as this would be a dmraid install as that Intel controller is a fakeraid controller I believe, and would need to be supported in dmraid. How am I misleading Fedora regarding my block counts? I would prefer not to let Fedora define the array (lvm) because I use several OSes (anybody want a copy of OS/2?), and I do not see that inserting a hardware RAID controller would help, so I am hoping for something like a count all the blocks switch to add on the install command. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: FC9 x86_64 powers off unexpectedly
Dan Farmer wrote: Hi All, My system has been spontaneously powering off once or twice a day for the last week or so. The obvious candidate would be thermal issues, so I took some steps to improve cooling and I believe that is fairly well resolved. At the last power off that I was present for I checked the CPU temp in the BIOS when it booted up and the temp was 45 degrees C. I also tweaked some settings related to cpu voltage and powersaving settings that seemed to help a bit (?). But still my longest run of uptime has been about 18 hours. I recently built this sytem, the specs are as follows: System specs: Fedora Core 9 x64_64 500W power supply Core2 Duo E8400 proc @ 3Ghz 4 GB RAM GIGABYTE GA-EP35C-DS3R LGA 775 Intel P35 motherboard nvidia geforce 8800 GT I've built plenty of systems before that never have had problems, but I wouldn't completely rule out build quality I suppose -- I just think it's unlikely. Can anyone give me some direction on what else I can investigate? Any log files, BIOS settings (I know that's a little out of the scope...), etc? Thank you! Other than the intermittent loss of power I've really been digging FC9 :) -Dan I don't know about that Intel's, but on some AMD MB the higher end cpus would cause machines to power off, the issue was that the MB in question was not testing at all with the higher cpu speeds, and the higher cpus pulled too much power and resulted in MB power components overheating, the initial solution was to put a bigger heatsink on the power components, the later solution was to use a larger power component, you may be able to test this sort of theory by having a fan directly blow on the MB to keep everything nice and cool, you might also use a temp meter and measure the temps on various components and see if anything outside of the cpu is getting too warm, or you could using the powersavings setting in Linux to not allow the cpu to run at the highest speed, if not running at the highest speed helps, then it could be overheating, or causing some other component to overheat. Also without something cpu intensive running the cpu temp may not mean anything, if you do get something cpu intensive to run, that may cause it to fall over fairly quickly. Roger -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Trouble installing/compiling the Marvell sky98lin on F8
Ubence Quevedo wrote: Hi All, I am having problems installing the Marvell sky98lin driver on a 32-BIT F8 Core 2 Duo system. I have the kernel source installed like the instructions recommend, but whenever the installer gets to the module creation part it fails. Here is the contents of the install.log file from the failed install: +++ Install mode: User +++ Driver version: 10.60.2.3 (Apr-28-2008) +++ Kernel version 2.6.25.6-55.fc9.i686 +++ smp_count=1 +++ cpu_number=2 +++ kernel_machine=i686 +++ Architecture: i386 +++ modpost available +++ Unpack the sources +++ +++ tar xfv sk98lin.tar 2.4/ 2.4/skdim.c 2.4/sky2.c 2.4/skethtool.c 2.4/Makefile 2.4/skge.c 2.4/h/ 2.4/h/skdrv1st.h 2.4/h/skdrv2nd.h 2.4/skproc.c 2.6/ 2.6/skdim.c 2.6/sky2.c 2.6/skethtool.c 2.6/Makefile 2.6/skge.c 2.6/h/ 2.6/h/skdrv1st.h 2.6/h/skdrv2nd.h 2.6/skproc.c common/ common/skgehwt.c common/skgeasf.c common/sk98lin.htm common/skgeinit.c common/sktwsi.c common/skvpd.c common/sky2le.c common/sk98lin.4 common/skfops.c common/skgespilole.c common/skgeasfconv.c common/skgemib.c common/skaddr.c common/skcsum.c common/skgepnmi.c common/vpdcheck.c common/sklm80.c common/skqueue.c common/sktimer.c common/skrlmt.c common/skgespi.c common/skxmac2.c common/skgesirq.c common/h/ common/h/sktypes.h common/h/skpcidevid.h common/h/skqueue.h common/h/skrlmt.h common/h/skgepnm2.h common/h/skgeasfconv.h common/h/skaddr.h common/h/skdebug.h common/h/mvyexhw.h common/h/skgehw.h common/h/skgehwt.h common/h/skfops.h common/h/sktimer.h common/h/skgepnmi.h common/h/skvpd.h common/h/skgetwsi.h common/h/skerror.h common/h/sktwsi.h common/h/skcsum.h common/h/skversion.h common/h/xmac_ii.h common/h/sky2le.h common/h/skgeasf.h common/h/skgespi.h common/h/skgeinit.h common/h/skgesirq.h common/h/lm80.h common/h/skgedrv.h common/sk98lin.txt misc/ misc/Kconfig misc/Configure.help +++ Compile the driver +++ make: Entering directory `/usr/src/kernels/2.6.25.6-55.fc9.i686' CC [M] /tmp/Sk98IomhaRXPCddXIYGhOSXfK/all/skge.o CC [M] /tmp/Sk98IomhaRXPCddXIYGhOSXfK/all/sky2.o /tmp/Sk98IomhaRXPCddXIYGhOSXfK/all/skge.c: In function ‘sk98lin_init_device’: /tmp/Sk98IomhaRXPCddXIYGhOSXfK/all/skge.c:483: error: ‘struct net_device’ has no member named ‘poll’ /tmp/Sk98IomhaRXPCddXIYGhOSXfK/all/skge.c:484: error: ‘struct net_device’ has no member named ‘weight’ /tmp/Sk98IomhaRXPCddXIYGhOSXfK/all/skge.c:489: error: ‘struct net_device’ has no member named ‘poll’ /tmp/Sk98IomhaRXPCddXIYGhOSXfK/all/skge.c:490: error: ‘struct net_device’ has no member named ‘weight’ /tmp/Sk98IomhaRXPCddXIYGhOSXfK/all/skge.c:611: error: ‘struct net_device’ has no member named ‘poll’ /tmp/Sk98IomhaRXPCddXIYGhOSXfK/all/skge.c:612: error: ‘struct net_device’ has no member named ‘weight’ /tmp/Sk98IomhaRXPCddXIYGhOSXfK/all/skge.c:617: error: ‘struct net_device’ has no member named ‘poll’ /tmp/Sk98IomhaRXPCddXIYGhOSXfK/all/skge.c:618: error: ‘struct net_device’ has no member named ‘weight’ /tmp/Sk98IomhaRXPCddXIYGhOSXfK/all/skge.c: In function ‘SkGeIsr’: /tmp/Sk98IomhaRXPCddXIYGhOSXfK/all/skge.c:2342: error: too few arguments to function ‘netif_rx_schedule_prep’ /tmp/Sk98IomhaRXPCddXIYGhOSXfK/all/skge.c:2345: error: too few arguments to function ‘__netif_rx_schedule’ /tmp/Sk98IomhaRXPCddXIYGhOSXfK/all/skge.c: In function ‘SkGeIsrOnePort’: /tmp/Sk98IomhaRXPCddXIYGhOSXfK/all/skge.c:2513: error: too few arguments to function ‘netif_rx_schedule_prep’ /tmp/Sk98IomhaRXPCddXIYGhOSXfK/all/skge.c:2518: error: too few arguments to function ‘__netif_rx_schedule’ /tmp/Sk98IomhaRXPCddXIYGhOSXfK/all/skge.c: In function ‘SkGePoll’: /tmp/Sk98IomhaRXPCddXIYGhOSXfK/all/skge.c:3277: error: ‘struct net_device’ has no member named ‘quota’ /tmp/Sk98IomhaRXPCddXIYGhOSXfK/all/skge.c:3277: warning: type defaults to ‘int’ in declaration of ‘_y’ /tmp/Sk98IomhaRXPCddXIYGhOSXfK/all/skge.c:3277: error: ‘struct net_device’ has no member named ‘quota’ /tmp/Sk98IomhaRXPCddXIYGhOSXfK/all/skge.c:3298: error: ‘struct net_device’ has no member named ‘quota’ /tmp/Sk98IomhaRXPCddXIYGhOSXfK/all/skge.c:3302: error: too few arguments to function ‘netif_rx_complete’ make[1]: *** [/tmp/Sk98IomhaRXPCddXIYGhOSXfK/all/skge.o] Error 1 make[1]: *** Waiting for unfinished jobs /tmp/Sk98IomhaRXPCddXIYGhOSXfK/all/sky2.c: In function ‘SkY2Isr’: /tmp/Sk98IomhaRXPCddXIYGhOSXfK/all/sky2.c:428: error: implicit declaration of function ‘__netif_rx_schedule_prep’ /tmp/Sk98IomhaRXPCddXIYGhOSXfK/all/sky2.c:429: error: too few arguments to function ‘__netif_rx_schedule’ /tmp/Sk98IomhaRXPCddXIYGhOSXfK/all/sky2.c: In function ‘SkY2Poll’: /tmp/Sk98IomhaRXPCddXIYGhOSXfK/all/sky2.c:665: error: ‘struct net_device’ has no member named ‘quota’ /tmp/Sk98IomhaRXPCddXIYGhOSXfK/all/sky2.c:665: warning: type defaults to ‘int’ in declaration of ‘_y’ /tmp/Sk98IomhaRXPCddXIYGhOSXfK/all/sky2.c:665: error: ‘struct net_device’ has no member named ‘quota’
Re: SATA - System Freezes
Henry Ritzlmayr wrote:
Am Donnerstag, den 19.06.2008, 09:52 -0600 schrieb Robin Laing:
Henry Ritzlmayr wrote:
Am Dienstag, den 17.06.2008, 13:25 -0400 schrieb Jorge Fábregas:
Hello Everyone,
I'm running Fedora 8 and my system freezes (for about 20 to 40 seconds) a
couple of times a day. When it does I see this on /var/log/messages:
--- cut here -
kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
kernel: ata3.00: cmd ca/00:50:67:85:03/00:00:00:00:00/e0 tag 0 dma 40960 out
kernel: res 40/00:00:76:6c:03/84:00:10:00:00/e0 Emask 0x4 (timeout)
kernel: ata3.00: status: { DRDY }
kernel: ata3: port is slow to respond, please be patient (Status 0xd0)
kernel: ata3: device not ready (errno=-16), forcing hardreset
kernel: ata3: soft resetting link
kernel: ata3.00: configured for UDMA/33
kernel: ata3: EH complete
kernel: sd 2:0:0:0: [sdc] 321672960 512-byte hardware sectors (164697 MB)
kernel: sd 2:0:0:0: [sdc] Write Protect is off
kernel: sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
--- cut here -
/dev/sdc is my main drive. The only thing I can think of...is that this drive
is actually a PATA drive connected to the SATA controller on MoBo thru
a SATA-TO-IDE Adapter that I connect on the drive. Perhaps the converter is
faulty...or could this be a known issue with libata? Anyone had same
problem?
Thanks,
Jorge
Many months ago I had the exact same output. Lots of google voodo and
try and error solved it. My issue was that on one outlet of the power
supply there where to many (3) drives connected. After recabling all
went away. Others claimed that they got rid of the problem be refitting
the sata cables.
Henry
Henry,
I was just about to suggest checking the power supply. I had a power
supply that wouldn't supply enough voltage on the 5V rail. My system
would freeze. Turned out to be a known fault with the brand of
powersupplies.
Took two power supplies to find out that it was a known fault. Argh.
Warranties are useless on some products. I also learned that the sensor
voltages were not accurate in the BIOS in comparison to a digital
voltmeter on the actual power cable.
--
Robin Laing
What I didn´t like (still) is the fact that there is no indication, that
this could be even slightly related to the power supply. As stated above
it was more a try and error to solve this issue. Hopefully for the OP
this also solved his issue.
Question to the devs - could you think of any way that the kernel output
could be a bit more informing, or don´t you get enough information from
the hardware for such an issue. I also checked smart for unusual power
cycle counts but to no avail.
Henry
The problem with power supplies is that often they don't fully fail, if the
voltage goes low enough things don't completely fail, only some operations will
fail and some will not, and often things won't notice the PS was low for too
long, and often they may only fail for the short period of the low voltage and
be fine the next second, or if the fully fail the OS may still be able to reset
the device and get it back up, but from the HW's point of view there was never a
complete power failure.And none of the normal voltage monitoring devices sit
there and sample the power voltages over time and verify they were always good
for the entire time, they only check when someone looks, and all that really
matters was that for tiny short period of time the voltage was too low, and
screwed someone up enough to cause trouble.
I have seen a 110V AC outage that resulted in a remote controlled power switch
switching off all of its relays, but the internal computer running those relays
reported them all on (it did not reboot, and had no idea the relays internal to
it were switched off and had no feedback on their position), obviously in this
case the relays were more sensitive to voltage issues than the computer running
the relays, likely a design issue were you really want to make sure the computer
goes off first, or make sure that the computer has actual feedback on the relay
positions so it knows something went wrong.
I have seen a power supply that was undersized on a certain voltage result in
the ethernet going offline (kernel reported the ethernet was screwed up-but had
no idea why and was unable to reset it and get it working again) and required a
reboot to get ethernet back again, but other than the ethernet going offline
nothing else looked wrong with the machines, and there were no other failures
that could be found, and absolutely nothing indicated that there were any
voltage issues.
Roger
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: f9 tar fails during backups
Skunk Worx wrote: Suppose I want to back up my home directory using tar. I see this : ls: cannot access .gvfs: Permission denied d? ? ? ??? .gvfs ...and this : tar: Error exit delayed from previous errors What service do I need to stop to eliminate this vfs file error during backups? # ls /etc/init.d/*vfs* ls: cannot access /etc/init.d/*vfs*: No such file or directory --- John Given the errors, and what ls displays, .gvfs is probably a corrupt directory/file entry and when tar hits it will report an error but hopefully not crash. shutting down and fscking may be required to get it to go away. Roger -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: make thunderbird NOT show html
David Boles wrote: Ric Moore wrote: On Sat, 2008-06-07 at 00:13 +, g wrote: David Boles wrote: Roger Heflin wrote: snip And that bad news for us is those clueless people are developers that develop email programs and really don't have a clue what they are doing, but certainly think they do. Roger Roger are you aware that your email is composed in rich text formating? Which is as annoying as html. ;-) also know as; Content-Type: text/plain; charset=ISO-8859-1 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit which is probably a 'default' config for 'gmail.com'. most 'gmail' that comes thru list is 'rich text'. a lot of folks who use gmail, hotmail, and other 'free' email, --- will not bother to set configs and are usually there to hide. --- This bit above. and are usually there to hide. What's with that? Ric The paranoia factor maybe? ;-) Hotmail I would probably agree with, but both gmail and yahoo provide higher end paid for service if you want it, and both yahoo and gmail are sub-contractors for a number of ISP's mail systems. I am on gmail because my ISP's email had enough issues that I kept getting unsubscribed from various lists (I assume because of funny bounces). My ISP has now fixed that issue by making some sort of deal with gmail for gmail to provide their mail service but I might as well use gmail directly since that email address will stay around for a lot longer than the one through the ISP's gmail connection. Roger -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Kernel Issues
Jelena i Zoran wrote: I have not been able to update the kernel on FC8 since kernel-2.6.24.3-12.fc8. All later versions stop loading at udev stage. I looked on the interned and others seem so have similar issues. None of the suggestions I found on the internet worked. The message I get at the boot stage is /sbin/modprobe abnormal exit ... There is some incompatibility between kernel modules and my computer. I have FC8 on two other computers and I had no trouble with the updates. Would compiling the kernel on my computer make any difference? I really do not know what else to try. I would appreciate any suggestions on how to resolve this issue. The problem is not just that I want to use the latest kernel but that many applications are crashing the x-windows. My thinking is that a kernel update would resolve these other issues (I base this on my previous experience with updates). Thanks, Zoran Compiling the kernel won't likely help, but you never know. It is likely that it is a specific module that is being loaded and causing you to have issues, and it may be a module that you don't even need for anything you actually use. If it is a module that you need though, you have a problem. There is probably a way to prevent udev from loading any modules that you don't absolutely need and then you can go load them one at a time until you figure out which is locking you up. You could for simplicity sake just move the modules that usually get loaded but that are not absolutely out of /lib/modules for the kernel that you are testing and manually reload them with insmod to see if any cause the lockup (assuming that the trouble module is not one needed for boot-ie a disk or disk related module). I believe on one of my machines with certain kernels that the module snd_via82xx_modem was causing me issues, it would lockup on boot most of the time at the udev stage. Roger -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: make thunderbird NOT show html
On Fri, Jun 6, 2008 at 12:32 PM, Mike Wright [EMAIL PROTECTED] wrote: Hi all, It seems that there are many clueless people who could never write a web page but seem to feel more than qualified to send html mail. I am tired of squinting at itty bitty fonts that are rendered by Thunderbird whenever it displays html email. (List denizens, please note: html mail gets an instant delete here; you will receive no help from me.) Does anybody know how to make Thunderbird display only the text/plain portion of multipart email? I've set up a filter to delete email with the header Content-Type: text/html but that only catches some of it. A hearty toast to whomever can solve this one. Maybe: view - message body as - plain text And that bad news for us is those clueless people are developers that develop email programs and really don't have a clue what they are doing, but certainly think they do. Roger -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: make thunderbird NOT show html
David Boles wrote: Roger Heflin wrote: On Fri, Jun 6, 2008 at 12:32 PM, Mike Wright [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi all, It seems that there are many clueless people who could never write a web page but seem to feel more than qualified to send html mail. I am tired of squinting at itty bitty fonts that are rendered by Thunderbird whenever it displays html email. (List denizens, please note: html mail gets an instant delete here; you will receive no help from me.) Does anybody know how to make Thunderbird display only the text/plain portion of multipart email? I've set up a filter to delete email with the header Content-Type: text/html but that only catches some of it. A hearty toast to whomever can solve this one. Maybe: view - message body as - plain text And that bad news for us is those clueless people are developers that develop email programs and really don't have a clue what they are doing, but certainly think they do. Roger Roger are you aware that your email is composed in rich text formating? Which is as annoying as html. ;-) Sorry about that. I used Google's webmail interface for that message, and I checked I cannot see any option in the settings to do it any other way (at least all of the time), it kind of looks like you need to hit plain text on a given reply email, and it kind of looks like once you hit plain text (or rich formatting) on any one message it stays that way for all later reply (not exactly how one would have expected the interface to act-or where one would have expected the option to be, and it should still be in settings as that is were it actually belongs for a what appears to be a permanent setting). This one should not be RTF or HTML, I sent it from thunderbird and I am 99% sure it is setup to only send plain text. Roger -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: make thunderbird NOT show html
David Boles wrote: Roger Heflin wrote: David Boles wrote: Roger Heflin wrote: On Fri, Jun 6, 2008 at 12:32 PM, Mike Wright [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi all, It seems that there are many clueless people who could never write a web page but seem to feel more than qualified to send html mail. I am tired of squinting at itty bitty fonts that are rendered by Thunderbird whenever it displays html email. (List denizens, please note: html mail gets an instant delete here; you will receive no help from me.) Does anybody know how to make Thunderbird display only the text/plain portion of multipart email? I've set up a filter to delete email with the header Content-Type: text/html but that only catches some of it. A hearty toast to whomever can solve this one. Maybe: view - message body as - plain text And that bad news for us is those clueless people are developers that develop email programs and really don't have a clue what they are doing, but certainly think they do. Roger Roger are you aware that your email is composed in rich text formating? Which is as annoying as html. ;-) Sorry about that. I used Google's webmail interface for that message, and I checked I cannot see any option in the settings to do it any other way (at least all of the time), it kind of looks like you need to hit plain text on a given reply email, and it kind of looks like once you hit plain text (or rich formatting) on any one message it stays that way for all later reply (not exactly how one would have expected the interface to act-or where one would have expected the option to be, and it should still be in settings as that is were it actually belongs for a what appears to be a permanent setting). This one should not be RTF or HTML, I sent it from thunderbird and I am 99% sure it is setup to only send plain text. Roger You did see the ;-) in there correct? Yes, I did, I just agree with your statement about RTF. Gmail defaults the same way. It is the 'hard line' Linux zealots can be upset. Most of us just move on. I am more annoyed that it was not in the settings like it should be, I always go into the settings and setup things like I want them, but it is hard to do when they don't put it in the settings, and hide it someplace else. I wonder how many people actually use the extra formatting for anything actually useful. Typically in corporate email none of the extra crap is used for anything actually useful or often at all so is kind of pointless to even have, often when it is used it actually ends up doing something stupid (too small/large of a font, or setting foreground without setting the background or just the opposite), most of which actually make the message harder to get. You mentioned Yahoo and Thunderbird. There is (was) a TB extension that would pop yahoo mail without paying the 'bucks' for the pop service. I have the Yahoo extension, it appears to work reasonably well. Roger -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: testing hardware - use what software ?
max bianco wrote: On Tue, Jun 3, 2008 at 3:41 PM, Roger Heflin [EMAIL PROTECTED] wrote: Robin Laing wrote: Compiling up something called HPL (with something called MPI) at least does nicely at finding that you have a memory/overheat/internal CPU issue. If the results corrupt or the machine crashes something is really wrong, typically it won't tell you what is wrong, but if it successfully runs for a long time then you can expect most things to be correct.Generally it will at least crash the machine several times faster than most other applications. It won't find IO/PCI/Video issues unless they are really severe, though generally most of the issues fall into what it does test. Do you happen to know what the latest version is? I have turned up a version 1.0a dated Jan 20, 2004. Do you know if that is the latest version available. Max It does not change much, so that is the latest version. You will also need a few other pieces of software, none of which will likely be in a rpm to get it to fully compile and run. You will need mpich and either libgoto or atlas or AMD MKL or Intel MKL. I have built it all 4 ways, the AMD and Intel libraries are probably the best choice, though the makefile will need to be adjusted to point the the library. Both of those MKL libraries were the last time I checked available for free download. And then you will have to define a HPL.dat file for your machine, once you know how to do it, really the only a couple of things in the file change when you move things to a new machine (size of the run), and it hpl can be ran across a network on multiple machines. Roger -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: EDAC i5000 NON-FATAL ERRORs
Jack Howarth wrote: I noticed that after upgrading the kernel on a Fedora 7 x86_64 box is the latest kernel (the box hadn't been rebooted for some months) that I am now seeing the following in my messages log... May 25 04:30:56 fourier kernel: EDAC i5000 MC0: NON-FATAL ERRORS Found!!! 1st NON-FATAL Err Reg= 0x1 May 25 04:30:56 fourier kernel: EDAC MC0: CE row 1, channel 0, label : (Branch=0 DRAM-Bank=3 RDWR=Read RAS=14339 CAS=672, CE Err=0x1) These messages always occur on DRAM-Bank 3 and are always NON-FATAL. The messages appear roughly once an hour and are rarely repeated immediately. This machine contains a Tyan Tempest i5000XL motherboard with ECC memory installed. Does anyone know if the recent kernels had any changes which made these motherboard chipset report ECC memory errors which were not reported in the past? I haven't been able to reproduce these errors in memtest86 yet with or without ECC. So I am wondering if I am seeing noise from the EDAC driver or real ECC errors. Thanks in advance for any insights on this. Jack Well, until recently the module that supports the i5000 chipset was probably *NOT* in the kernel, so it was probably added recently or before it was not loading at all. You could check the older kernels and see if it had the proper i5000 modules being loaded. If memtest86 is new enough and can see the ecc monitoring hardware of the i5000 you should be able to duplicate it, if the memtest86 is older and does not properly detect the i5000 hardware then any correctable ECC errors will be silently corrected by the hardware and memtest86 will be none the wiser. There is an edac list someplace and someone over there can probably interpret the error in more detail. If it was noise, I would have expected the bank to move around, if you have more than one dimm you could try moving the dimms around and see if the error location changes, there are also some stuff for edac in /sys that gives more details and has running counters of the errors since the machine has been up. Roger -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
