Jump to content
Compatible Support Forums

danleff

Moderators
  • Content count

    2895
  • Joined

  • Last visited

Everything posted by danleff

  1. danleff

    Do Netgear DG834GT Work Under SuSE 10.1

    Any router should work, as long as you have the system set up correctly. Are you using this for wireless, or straight ethernet from your box to the router? If wireless, what is the exact make, model number and revision name of the wirlesss card that you are using? This determines what chipset is on the wireless card, hence, what drivers to use. The issue is more likely the wireless card being configured (drivers, SSID and WEP or WPA passphrase) correctly. If you are using the ethernet connection, then it should work, if you ISP is based on dynamic IP address. Do you use DSL, here you need a username and password to login to your ISP, say like Verizon? More information on your situation would be helpful.
  2. danleff

    driving me crazy!

    Can you give us the site address that you are using, as well as the exact name of the images that you are downloading? You can just give us the name of the first iso image, out of the set of five. Make sure that you are burng the images at no more than 8X speed. Also, what exact media are you using for the burns? What speed are they rated for?
  3. Take a look at the partitions designated for sda. Note that sda1 is marked as a swap partition. Is it possible that you accidently marked (formatted) this partition as a swap file when installing Ubuntu? sda1 = (hd0,0), that is, if you did not change the bios boot order, or the designation of the sata cables to the motherboard. I assume sdb is just a data drive of NTFS type?
  4. danleff

    Sound problems FC5

    Sorry i could not be more helpful on this. Looking arouind, others are having the same issue. It seems to be a problem common to Asus systems. Perhaps they will have a bios update soon that will fix it. Perhaps someone else has a fix they know about and will post it.
  5. Thanks for the feedback! I do appreciate it. I'm sure that I will add more material, say regarding HP machines that have a recovery partition that can muck up the works.
  6. danleff

    Chicken and the Egg

    Wilhelmus, looking at the output of wvdial; --> Carrier detected. Waiting for prompt. CVX Access Switch. Access is restricted to authorized users only. login: --> Looks like a login prompt. --> Sending: guest guest password: --> Looks like a password prompt. --> Sending: (password) Can this mean that the user name and password is not set, so this is why he is getting a disconnect? Or is this set in a script? I have not done dialup in quite a while, so tell me if I am wrong.
  7. Quote: Ah... I think I understand. So what you're saying is that I actually cannot use QTParted (or any application for that matter) to resize my NTFS partition and create a FAT32 partition out of the free space. I would have had to have done that prior to installing FC5. Actually, that is not what I meant. Let's look at a scenario. Your 300 gig drive (hdd in Linux) originally had just an NTFS partition. Let's say for the sake of argument, that the NTFS partiton, which is just a data drive, occupies all of the space on the disk. You want to make room for Fedora and also a fat32 partition to share data with Linux. That partition has 50 gigs of actual data on it. You can use the Windows partitoning utility to resize that partition down to make room for the other partitions. 1. Defrag the partition first. Windows tends to allow placement of scattered files across the partiton. Defrag the drive to move all the files in nice order and away from the end of the partition. 2. Using the XP partitioning utility, resize the partition down to 220 gigs, leaving roughly 80 gigs. 3. Add a fat32 partition of 40 gigs for sharing files between Linux and Windows. This leaves 40 gigs of free, unpartitioned space. 4. Install Fedora, telling it to use the remaining free 40 gigs for Fedora, say using the default layout. No pre-configured Linux partitions to be overwritten. NTFS = 220 gigs fat32 = 40 gigs Fedora = 40 gigs These actual numbers will not be exact, as the actual total usable size of a drive is not equal to 300 gigs, but a little less. In this case, no further partitioning is realistically possible, as you need to keep the logical order of the current partitions the way they are to retain grub looking in the right place for Fedora. Never try to resize or add any partitons at the beginning or middle of the drive, as this will confuse grub. If you think that you will ever need more partitions, say for another Linux installation besides Fedora (adding a distro), always leave empty, unformatted space at the end of the drive. This preserves the logical order and assignment of the current partitions. This assumes a simple configuration for newbies. Of course, there are always ways around this for experienced users. Adding any more partitons can be a little more complicated then this, as usually there is a limit of 4 primary partitions on any given drive. In this case, you could leave your primary NYFS partition intact, add an extended partition to take up the rest of the drive, then add as many partitions as you need as logical partitions, up to the actual size of the extended partition size.
  8. Let's take a look at what happened. You have two hard drives in the system. You pre-formatted some space (resized NTFS) and made a linux partition on the second hard drive, correct? OK, now you install Fedora. However, if you accept all the default options during the installation, this is what happens. Fedora, by default erases all linux partitions on the drive and makes it's own default setup, which includes a small /boot partition and an LVM partition. Take a look at my article here, paying close attention to Figure 4.1. What does that say at the partitioning section by default? Remove Linux partitions on selected drive and create default layout. So now, you have a default Linux setup of your partitions as such; Device Boot Start End Blocks Id System /dev/hdd1 1 31257 251071821 7 HPFS/NTFS /dev/hdd2 * 31258 31270 104422+ 83 Linux /dev/hdd3 31271 36481 41857357+ 8e Linux LVM Now there is no more room on the drive to make any additional changes. So, qtparted can't resize the LVM volume. There is no room left to make additional partitions at the end of the drive. Fedora has used all the available room on the drive, once it trashed your pre-configured Linux partition. You do not want to try and make a partition at the beginning of the drive, or between the NTFS and Linux LVM volume, as this will change the logical order of the partitions and cause grub to fail. Grub is configured to boot the system with your old partitioning scheme. The logical thing to have done, is to origionally make the primary NTFS partition just small enough for your needs on the hdd drive, make an ext3 partition for Fedora, then leave enough space for a fat32 partition to share files between. Then, you could have used the "create custom layout" option in the Fedora partition manager if you wanted to tell Fedora to use pre-existing Linux partitions that you made on the hard drive. Or, resize the NTFS partiton, make a fat32 partition for sharing, then allow Fedora to use the remaining free space on the drive, for it's installation (Use free space on the selected drives and create default layout).
  9. danleff

    Sound problems FC5

    Looks like you are going to have trouble with this. See this Asus Compatibility Matrix for Linux. Note the "N/A" for sound. I bet the drivers are not yet perfected in Alsa sound. Let me look at this. Also, your problem has been described elsewhere and it looks like a fix is I the making, although I could not find any real answers, except for "patches", which means a bit of work.
  10. Quote: As I am using two operating systems, and had installed XP prior to FC5, my XP partitions are all in NTFS format. As I have read and learned, one may effectively read NTFS paritions, but not write to them under linux. And of course, on the flip side XP can neither read nor write to my ext3 linux partition. Techically, your comments are correct. However, Puppy Linux has apparently added NTFS read and write support in their new version. I have not tried that feature yet. There is a program that can at your ext2 and ext3 partitions in Windows, but this is not, in my opinion, effective. Are you using qtparted or gparted? Qtparted can't resize NTFS volumes, but gparted is supposed to be able to do this. The question that I can't answer yet, is if you can manipulate Logical Volume Managment (LVM) volumes, which is what Fedora installs by default. Yes, you have one small ext3 boot partition for holding the grub boot reference files (it has to be), but the rest is LVM. This is why it is good to have a plan before you decide to commit to a partitioning scheme on a system. I always make sure that I leave empty spcae at the end of my drives, just for this reason. Of course, Fedora takes what it wants, unless you manually partition during the installation process. PartitionMagic for Windows will resize your first drive, if you wish. The second drive...this is a good question. I am also looking at another free utility for Windows to see what it will detect and modify. It's called 7tools Partition Manager. I honestly don't have much experience with LVM to recommend a course of action here. Perhaps a new article in the near future?
  11. danleff

    driving me crazy!

    You should not need to get into the bios to change the boot order. I don't have my work Dell with me, but there us a key to press during boot to change the boot media. It may be F12, F2, or just pressing the enter key, as the system boots. Dells boot quickly and it is difficult to see the option on the screen to change the boot priority. consult your users manual for the proper key. However, this does not seem to be your problem. If the Mepis CD boots, then you most likely have an issue with the burned installation CD. Did you burn the iso images as a data file, or burn them as images? See my article here. What burning software did you use with the iso images? Also, Fedora uses sha1sum to verify the images. But first, let's see how you burned the images first.
  12. danleff

    Dual booting winXP & fc5 on HPpavillion using 2HD

    Quote: i have installed fc5 correctly and choose winxp as default os. I assume that you chose to install Fedora on the second hard drive? If so, what options during the installation did you choose to make the partitions and where to place grub, all default options? Quote: IT worked when we boot fc5.but when i try to boot winxp it shows pc recovering and then i am not able to load fc5. It sounds like XP is trying to boot from the HP recovery partition, not the actual Windows OS partition. Are you saying now that you can't boot either OS? Quote: i try to load it from windows boot loader by making changes to bootpart.ini but it shows Missing OS. What changes to the boot.ini file? To load Fedora, or Windows XP? If Fedora, what technique did you use to do this? If you can link to the site's directions that you did this from, this would help. However, depending where you told Fedora to load it's grub reference files, will determine if this works (changing the windows boot.ini to boot Fedora, if that is what you tried). Please try and be specific, so we know what you exactly did.
  13. danleff

    Gigabyte board. wont pick up 2 cd roms ..HELP

    The first question is, how are the CDROM drives jumpered, master, slave, or cable select? If you are shure that they are jumpered correctly and that you have them connected to the correct cooresponding places on the ribbon cable, please post back with the exact model number of the motherboard, if posible. You say that you have 4 IDE connectors on the motherboard. I assume 3 and 4 are raid connectors, which most likely should not be used with CDROM drives.
  14. Grub uses different syntax then what the partition is actually in Linux. Quote: so I noted that my windows drive is referred to as sda1 and tried this: grub> unhide (sda1) sda1 is the actual partition, not the grub command syntax, so this is why you are getting the Error 23: Error while parsing number. It doesn;t know sda1, but the drives are seen in order of (hd0,0), for example. Where hd0 is the first drive in the system and ,0 is the first partition. Do you have one hard drive on the system, or two? If two, is Ubuntu installed on the same hard drive as your Windows installation? Let's look at this logically. If you get into Ubuntu, go to a terminal window, as root user and type the following; fdisk -l Where i is the small letter "L", not the number 1. This should give you an output of your drives and their partitions. Can you post the result here? HINT: if you don't know. To copy and paste the output of the result, highlight the result text. Choose from the dropdown menu...edit-->copy Move to the post quick reply window and hold down <ctrl> then "v" (on the keyboard).
  15. Try the following command, once you are in chroot; grub-install --recheck /dev/hdc This tells grub to recheck the drives and partitions and install the bootloader for grub on /dev/hdc. Of course, make sure that the boot order in the bios is correct, as when Fedora was installed originally. See my article page on the subject, located here. The small /boot partition is normal with a "default" option installation. Just the grub referencce files can be here. when you run the recheck command, the actual MBR will be written to hdc, which then references the actual grub files that it needs on the /bbot partition. If this does not work, post back, as you are experiencing the "grub-bug" that I spoke about in the article. The link to the total article is here.
  16. danleff

    dual boot, then linux only

    There are a number of ways to do this, but remember, don't just remove the Windows partition, as this will confuse your Linux bootloader, unless you install Linux on a second hard drive and not accidently delete your Linux bootloader on the boot drive. To know how to do this, we would need more information. 1. What distro and version of Linux are you using? 2. Are you using Lilo or Grub as your bootloader? 3. Do you plan to install Linux on your only drive in the system, or to a second hard drive? Again, if you just delete the Windows installation (change the partition structure by deleting the Windows partition) the partitions on your hard drive) this will result in Linux not booting, if both are installed on the same hard drive. Best to ask this question when you are really ready to remove Windows.
  17. danleff

    Untitled thread

    A free utility that you can use to burn the iso image, is BurnCDCC. I suggest that you also try to burn the iso image at a slow speed, as ISO images like to be burned at 4 or 8X, not the top speed that the burner is capable of. I'm not sure how the files extract (what files are created) when you unzip the zipped file, but there should be either a setup file, or exe file to start the installation. The directions on the Winternals site really speak to the CD version, but the documentation is located here.
  18. danleff

    Untitled thread

    If the version of the Administrator pak is version 5, you need an activation key. This is provided by the manufacturer. If you did not get one with your purchase, then you most likely bought it from a "bootleg" site. The software is designed to be installed on a Win XP machine. When you unzip the package, you should get a folder with the program files in it (non-CD version). You probably (I am guessing) have a setup or exe file that installs the software on the system. Once the software is on the system, you should have a menu for the program, with an option to create a bootable CD image. You then can make a bootable CD, by burning the iso image to a cd. You can't use the Win XP utility for this, as it just creates a data CD, not a CD from image (bootable CD). So, this is why you needed Nero or another utility to burn the iso image to a CD - "burn as image." Looks like you got this far, but with Linux (k3b). I believe this is what the cue and bin files are for, so the program can create the iso file to burn. If you can't see the "C" drive and the "D" drive is your recovery partition, then I assume that this is a result of the partition problem you have (where the NTFS partition was screwed up when you tried PartitionMagic and it failed to complete), or a result of how you tried to burn the bootable CD disk without installing the program first on an XP machine, then use the CD wizard to make a proper iso image. These are just guesses on my part. As you probably guessed, the inode errors were when the Linux Live CD tried to read the NTFS partition. What Live CD did you try to use? BTW, I asked about the floppy PartitionMagic disks, as this program offers to make a set of bootable floppies that mirror the partitions on the system and can attempt a recovery, using a DOS version of PartitionMagic. This is helpful to have when you have a situation like this. It should be an option under Start-->Programs-->Powerquest...-->PartitionMagic Tools--> Create a rescue disk.
  19. danleff

    Untitled thread

    Looks like you already got an answer on NT Compatible? You found out that the program is run in Windows and then has a wizard to extract an ISO to burn? I use ERD Commander at work all the time. Very good for my needs. How much did Microsoft bump you for this program? Yes, if you did not see it in the title, the firm that makes this program is a division of Microsoft.
  20. danleff

    Edited /etc/fstab and Fedora wouldn't boot

    If you want to, post your motherboard make and model here (or if the NIC care is a PCI card, not onboard, the same for the card) and what make and model sata drive that you have. The new version of Puppy 2.02 sees all my drives (two sata drives included). You have to set up your NIC card in start-->setup-->wizard wizard. Pick the option to set up onboard (wired) NIC and see if the interface is detected.
  21. danleff

    Edited /etc/fstab and Fedora wouldn't boot

    This explains a few things. I wonder if Puppy has added wiresless keyboard and mouse support in their new version. I can't test this, as I have a KVM switch on my systems, which doesn't support wireless keyboards and mice. Simply put, windows does not read and write any Linux partitions. There are a few Windows based programs that allow you to see Linux partitions, but that is it. Fore normal sharing of data files (excluding DVD burns), I use fat32. NTFS write support is still in progreass in Linux. Puppy claims to have full write support for NTFS in their new version. I have not tried this out yet. In terms of file sizes, Linux supports up to 2 TiB of file sizes. What you are probably runnng into, is the limit of the download method that you are using. I seem to remember Fedora's wget utility has a 2 gig limit on download file sizes. For downloading DVD files, you can use a download manager, like gftp. I have downloaded DVD files without a problem with this utility. It is included as an add on in Fedora, either off the DVD (Applications-->add/remove software) or though Yum.
  22. danleff

    Edited /etc/fstab and Fedora wouldn't boot

    Quote: I followed posted instructions on several websites regarding mounting an NTFS partition under Fedora 5. Take a look here for information and module packages. See the RedHat/FC section on the right hand links. For Fedora Core 5 here. Of course, read the instructions, which gives you the information that you are looking for, including modifying the fstab file and mounting the volumes correctly. This is a problem in of itself. Several techniques is not a good idea. There are great packages to allow mounting of NTFS volumes for Fedora. The plan is to use only one package (module) and one technique, specific for that module. Good question about the fstab file. The backup always is read-only. I have used Puppy a lot to correct fstab and grub problems. It has always worked great for me. Can you tell I am a fan of this distro? The driver issue that you note, do you know what the issue was? I'm sure there is a way to do this correctly (command line arguments), but I have never needed to do so. The fstab file is funky about exact syntax. You should be able to boot into Fedora, in rescue mode and fix the original fstab file. Again, I seem to recall that there is a command to change the read-only status of this file when recovering a backup, but again, I have never needed to do this. I never have messed with mtab. This file should never need to be modified, unless you change something significantly with your hard drives. Fedora should auto-correct the drive designations, but we know that that does not always occur as it should, don't we? Some food for thought for some new how-to articles!!
  23. danleff

    Unable to reformat SATA HD

    Quote: First let me say that my dual-boot is working fine, although I recently thought it wasn't. To make a long story short, I had incorrectly thought I needed to re-install Windows and reformat all partitions on my Seagate SATA HD because GRUB was loading Fedora fine, but for Windows it came up with a GRUB error. So, what you found out, was that when Grub does not see the Windows partition correctly (points to a wrong partition), then grub is able to be modified to boot Windows correctly. By re-installing Windows, if that worked, you overwrite the grub bootloader and are no longer able to boot Linux. Quote: -Could this problem be that the Win install doesn't properly see the Linux partitions and is locking up trying to read from them? From my experience, yes, this can happen. Windows wants the first partition of the boot drive. If there is a Linux partition there, say a Linux /boot partition, this will potentually confuse the Windows installer. A number of other hardware issues can also cause this lockup to happen. Quote: -Is there a bootable, stand-alone utility which I can burn to cd which will just do a complete wipe of the HD? Yes several. PartitionMagic will make bootable floppies that will usually do the job. Seagate also had a cd based utility, that will format the drive to use as either a data drive, or prepare the drive for an operating system installation, like Windows. You can also do a "zero-write" on the drive to completely erase the drive, then prepaer it for either options mentioned. See there website and look for "diskwizard" under support downloads. Actually Microsoft has an article, located here, that describes how to remove Linux from a system. Surprised? It makes note to use a linux based utility (fdisk - not the Windows fdisk) to remove the Linux partitions, then how to prepare the drive for a Windows installation.
  24. WOW, this is interesting! I see a couple of possible problems. Let me look at my bios settings and see what I have. Quote: In the bios: IDE1 MASTER cdrom drive IDE1 SLAVE dvd r/w drive IDE2 MASTER cdrom r/w drive IDE2 MASTER NOTHING IDE3 MASTER 120GB sata drive (with winXP installed) IDE3 SLAVE NOTHING IDE4 MASTER 250GB sata drive (new for Fedora) IDE4 SLAVE NOTHING Do you really have three CDROM/CDRW devices on the system on the IDE channels? In the bios, under the advanced tab, what is the onboard Promise raid controller set to, disabled, or enabled? If enabled, is the Operating Mode set to raid, or IDE? If it is set to disabled, then you will not see these two options under the Operating Mode.
  25. danleff

    Untitled thread

    From your second post, I assume that you found the Powerquest article on the subject. This does not look good. I also assume that because you have a recovery partition, then you have a Compaq, HP or Gateway system? Do you have a set of PartitionMagic floppy disks, or were you running PartitionMagic in Windows only? What concerns me, is the small "unallocated" space between the NTFS partition and the recovery partition.
×