Jump to content

pmpatrick

Members
  • Posts

    1861
  • Joined

  • Last visited

Everything posted by pmpatrick

  1. Click on the "Easy-Urpmi" link above and follow the directions for adding the additional mandriva software repositories to your urpmi database. The lame packages are in the plf repos IIRC along with a lot of other packages that mandriva can't distribute for legal reasons like win32 codecs. Once the repos are set up the packages you need will be visible in mcc.
  2. For what it's worth, I have a few observations that you may find useful. First with UUID, there are definitely pluses and minuses involved in using that system. UUID is pretty much standard on debian and all debian based distros now, including ubuntu. It was originally adopted when libata was undergoing rapid development in the linux kernel and no one could be sure how hard drive device files were going to be designated from one kernel release to the next. UUID should be invariant regardless of how the kernel designates the drive device file. However, unlike partition labels, UUID is embedded at the filesystem level. As a result, if you reformat or resize a partition, the UUID will change which can lead to a whole host of problems if you are not aware of that fact. For example, a lot of distros will reformat an existing swap partition during an installation. If you are dual or multi booting several distros all using the same swap partition, this will cause the swap partition to disappear because the reformat caused swap's UUID to change. Re lilo vs grub. I was a lilo guy from way back and always preferred lilo to grub basically because I knew lilo and didn't want to learn a new bootloader. However, lilo is not being actively developed any more and every distro except slackware and some slack derviatives is now using grub. It's really time to take the plunge and learn grub. Once you do, you will find grub is much easier to use in situations where device file names are changing because you don't need to write changes to the mbr every time you make a configuration change in the bootloader. This can become a real problem with lilo where your root partition has gone from hda to sda in a kernel upgrade but you can only boot with the old kernel that still uses hda. You can edit lilo.conf to go from hda to sda in the old kernel but you can't write that change to the mbr because sda doesn't exist when the old kernel is booted. You'll just get an error message if you try to run lilo -v.
  3. I think that might be from a kde utility, kgpg. IIRC it comes in a package called kdeutils-kgpg. Check to see if that's installed. If it is uninstalling the kgpg package will put an end to those prompts. You can also configure kgpg to not start on login but if you're not going to use it, you may as well uninstall it.
  4. There's a few things you could try. Your usb drive is designated /dev/sdb during installation but that may change when you set it as the first boot device in your bios, i.e. it may go from sdb to sda. Note the output where it says it can't find the resume device, /dev/sdb6. It may be that the resume device, a/k/a your swap partition, is now sda6. The top four lines indicate the usb modules, ehci and ohci are loading. The puzzling thing is that mdv2008.1 designates the root partition in grub using UUID instead of device file and UUID should be invariant. As such, the root partition should be found regardless of device file naming. One thing you can try fooling around with is passing various options and edits to grub. When you see the grub boot screen hit the Esc key and then Enter which will take you to an ncurses version of that screen. Select the boot entry you want, probably "linux", And then hit the "e" key. That will allow you to edit the grub entry. Try changing the root= line from UUID to /dev/sda1, i.e. from: root=UUID=<long sequence of letters and numbers> to: root=/dev/sda1 See if it will boot.
  5. If you don't want to use a console based text editor you really don't have to if you are running a gui like kde. Just open konsole and run: $ kdesu kwrite You will be prompted for the root password and then a graphical text editor, kwrite, will come up with root privileges. Kwrite works just like a simple word processor. Navigate to the file you want to edit and have at it.
  6. Try changing this grub entry: title linux kernel (hd1,0)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=d55586eb-0d28-437b-9e62-a46df03b1f00 resume=/dev/mapper/nvidia_bhbafcde5 splash=silent acpi=ht vga=788 initrd (hd1,0)/boot/initrd.img to this: title linux kernel (hd1,0)/boot/vmlinuz BOOT_IMAGE=linux root=/dev/sdb1 resume=/dev/sdb5 splash=silent acpi=ht vga=788 initrd (hd1,0)/boot/initrd.img It's not finding the root filesystem and may be having problems with the UUID designation. If that doesn't work, it's probably a hardware problem in detecting your sata controller and loading the appropriate modules to support it. Post your hardware specs, in particular which motherboard you are using and how you have sata setup in your bios(AHCI?).
  7. Quickly reading your output, I have the following observations: 1. Your bios is properly detecting your usb drive and loads the grub bootloader from the mbr on your usb drive; 2. After grub loads and apparently loads the kernel vmlinuz and initrd which it locates in /boot on the usb drive, the kernel seems to be unable to read the usb drive partitions when it takes over. All this would indicate that the initrd generated during the installation may not have the appropriate modules to detect and use a usb hard drive at boot time. Since two people are reporting the same issue, I would suspect a bug in the installation routine, perhaps one which only becomes apparent with certain hardware configurations.
  8. You have the right command but it is almost certainly in the wrong spot. Mandriva 2007.1 uses either the either kdm or gdm display manager, not xdm; can't recall which one it is. You could try poking around in /etc/X11/ to try and find a better place to put your "nolisten tcp" line. First determine which dm you are using by going into mcc>boot>display manager and work from there. For sure it's not xdm and placing your command in an xdm config file will insure that the command is never run. You could also try sticking the command in a more primitive X startup file like /etc/X11/Xsession, but the dm config file might override that when it executes. Also, take a look at /etc/X11/wmsession.d and /etc/X11/dm.d. Those are the locations in mdv2008.1 that I would look at and they are probably the same in mdv 2007.1. You will probably have to do some tracing down through the X init scripts to find the one that actually starts X. If you want to forgo a dm altogether and start X from a command line login, you could probably accomplish what you want with: $ startx -- -nolisten tcp
  9. That's not normal for your hardware IMHO. Which desktop are you running, kde or gnome? Whichever it is, try the other and see if the problem goes away. Is beagle enabled? If so disable it. Also, try running without the 3D desktop and see if the problem goes away. That might help limit down what's causing the problem.
  10. pmpatrick

    Easy-urpmi

    Are you sure that's the complete output for lspci? It just doesn't look right. For example, I would assume you have an nvidia based mobile graphics adapter but I don't see that listed there unless I've missed something. In fact, I don't recognize anything that looks like a graphics card. Try running: $ lspci -vv That will give you more verbose output. Also, using some of the gui configuration tools, try going into Menu>Tools>System Tools>Configure Your Computer which will bring up Mandriva Control Center(mcc). In mcc go into Hardware>Browse and Configure Your Hardware and see if your broadcom wireless card is detected.
  11. I don't have answer but this may help: http://poerwo2211.wordpress.com/2008/02/21...os-pecas-ndahe/ It's in a language that I don't understand and is not a simple procedure but it appears that this fellow got your device working in PCLinuxOS which is very similar to mandriva. Perhaps someone more familiar with that language and your hardware can decipher the technique used better than me.
  12. From what you describe, you have either a hardware problem, i.e. the drive is physically defective or "going"; or a software problem, i.e. your partitioning operations screwed up your mbr partition table(most likely). To check for any hardware issues, go the hard drive manufacturer's website and download their hard drive diagnostic utilities which are usually in the form of a bootable iso. Burn the iso to a cd as an image, boot off the cd and run the thorough version of the diagnostic utilities. If the drive doesn't pass, see if you are within the warranty period, usually three years, five for Seagate, and contact the manufacturer if you are for a warranty replacement. If the drive passes, you can be relatively sure you have a corrupted partition table in your mbr. In that case, you can try to repair the partition table using the testdisk utility as described in the prior post. Or you can use the diagnostic utility cd to do a zero fill of the drive which will totally wipe the drive leaving it in the same condition as when it left the factory. You can then repartition, reinstall and restore from your backups.
  13. Thanks dex, you just made my day :thumbs:
  14. Just downloaded and installed the mdv2009- kde4.1 beta livecd. All I can say is that I hope and pray that kde 3.5.9 will also be available in mdv2009 as an alternative. KDE 4.1 looks nice and shows promise but it is not any where near ready for day-to-day use. I know this is a beta release, but it is apparent to me after trying both mandriva's and suse's livecds that kde4.1 is still at a beta level and won't be ready for prime time for at least another year. The best that can be said is that it is much better than kde4.0 which was totally unusable. Nonetheless, I found 4.1 nonintuitive, subject to random lockups too numerous to mention, feature bereft and just plain frustrating. I'm sure some of these problems will get ironed out before final release, but the unfinished nature of kde 4.1 is readily apparent to anyone and has no place as a default desktop on any distro. And what's the deal with that silly bar that appears next to a plasmoid every time you put the mouse cursor on one? Just don't get that at all; that should only come up with a right mouse click. That's just a style point and people can differ on that issue. In general, the look of kde4.1 is beautiful. The lack of stability, the current reduced level of configurability, and the reduced number of stable applications available for kde 4.1 are its main issues.
  15. Open a console and post the output of: $ lspci That will list everything on your pci bus from which you can determine exactly what ethernet controller you have. By the way, I assume you are trying to configure a wired connection. I generally associated atheros with wireless cards which made me wonder.
  16. You can use wait or sleep in your script: http://www.linux.com/articles/113976
  17. Also be aware that some java apps will not run with the open source version of java installed by default in mandriva. See: https://mandrivausers.org/index.php?showtopic=55924&hl= especially ianw's post re setting the default version of java to use when you have both the open source and sun versions installed.
  18. Have you tried any slackware based distros? There are several specifically designed for limited hardware like zenwalk, slax and vector. One that's getting a lot of favorable reviews is wolvix: http://wolvix.org/ It's based on slax but customized with xfce instead of kde.
  19. Doubt that will work arctic. IIRC the info to restore the windows bootloader is also stored on that deleted linux partition. I think he will have to restore the windows bootloader using his windows install cd and the procedure is different in vista and winxp. For vista see: http://windowshelp.microsoft.com/Windows/e...2f3f351033.mspx For winxp, follow this procedure: Boot with the XP installation CD. When prompted, press R to repair a Windows XP installation. If repairing a host with multiple operating systems, select the appropriate one (XP) from the menu. If you have only one operating system, enter 1 to select it. Enter the administrator password if prompted . If you don't have an admin password, just hit the Enter key when prompted and you will be taken to a command prompt. To fix the MBR, type the following command at the command prompt: fixmbr Then hit the "Enter" key and confirm by pressing the "Y" key when prompted. That will reinstall the windows bootloader, assuming you have winxp installed on the C:\ drive. If you have multiple windows OSes installed, this could get more tricky.
  20. The b44 module is for the regular wired ethernet port, not the broadcom wireless card. On most Compaq laptops the onboard nic also has a broadcom chipset which is why the b44 module is loading.
  21. Just to add my two cents, I have the identical card on a Compaq F730. It has been a pain to configure on many distros but it works perfectly with mandriva 2008.1 using ndiswrapper. As others have advised, it will not work with the open source bcm43xx broadcom driver that most distros will use by default so don't even go there. Also, it was extremely tricky to configure on mandriva 2008 so I would advise skipping that and using only Mandriva 2008 Spring edition, a/k/a Mandriva 2008.1.
  22. I'm using one right now with no problems on mandriva 2008 and 2008.1. Drives on the card are designated in the hdx format, not sdx like on some distros. Those distros where ide drives are designated sdx are using the newer libata where all ide drives are now being run under the scsi protocol. With certain 2.6 kernels, the implementation for the promise controller in libata is very buggy although that seems to be fixed in the most recent 2.6.25 kernels. At any rate, the mandirva kernels and hardware detection are configured to use legacy ide modules on the promise controllers and those work fine. Just note that you could have potential problems on other distros that use libata for the promise controller drives.
  23. According to this: http://www.nvidia.com/object/unix.html the most recent nvidia driver is 173.14.09. You can always try installing that driver and see if that works. The package attempts to automatically compile the driver from source and install. It's not that hard to do. Back in the old days, that's the only way we had to install that driver.
  24. Just to make sure I'm on the same page, you have this ViewSonic lcd: http://www.pcwb.com/catalogue/item/A0419279?cidp=Ciao If that's the case, nothing jumps out at me in your xorg.conf file that looks wrong. I think the nvidia driver is the likely cluprit. I would check the nvidia ReadMe or errata file if one is installed on your system. There may be something you can do in xorg.conf to work around this problem.
  25. In kde, open a console and run: $ kdesu XFdrake enter the root password when prompted and the mandriva graphics configuration utility, XFdrake, should come up. Tick the "Monitor" button, then select Generic Flat Panel 1360x768. Go back and hit the Test button in XFdrake and see if it works. I also think there is something not right in the monitor detection which may be screwing things up. I'm hoping by manually setting it to Generic Flat Panel 1360x768, the problem might go away.
×
×
  • Create New...