Jump to content


  • Posts

  • Joined

  • Last visited

Profile Information

  • Location
    Chicago, IL

pmpatrick's Achievements

Mandriva Guru

Mandriva Guru (6/7)



  1. Installed the KDE version yesterday and everything is running great. This is a really solid release. Congratulations to the Mageia devs and everyone involved in this project; your future looks very bright to me. It is so nice to have a community based project like this that isn't subject to the dubious business whims of upper management. Best of luck.
  2. pmpatrick


    Thanks ian; I can now rest easy. :D
  3. pmpatrick


    I don't think it's unusual for the Mageia devs to want their own forum hosted on their website. In fact, that's pretty much the norm for any distro that I can think of. You have to remember that what happened with this forum and mandrake/mandriva was an aberration. The old timers will remember how it all came about. Basically, back in the day, mandrake setup a quasi-official forum moderated and run by a mandrake employee, Tom something or another(if anyone remembers his last name please post it as it is driving me nuts). At this time(2001-2002), mandrake was easily the number one desktop distro around and ubuntu wasn't even a gleam in Mark Shuttleworth's eye. Tom was a very good guy and well liked by the community. Sometime later, mandrake shifted its business model and decided that it wanted to try making money selling service to desktop users through the official mandrake website. Unfortunately, the service mandrake offered was inferior to what you could get at Tom's forum for free. The inevitable finally occurred and Tom was terminated by mandrake and pretty much just disappeared; it was all very mysterious at the time. As a result, Tom's forum was in limbo for awhile and some of the forum members got together and started this forum. Ever since, Mandrake/mandriva has been, to a greater or lesser extent, somewhat ambivalent at best and downright hostile at worst, when it came to this forum.
  4. That about sums up my feelings on this topic. And I don't think signing petitions will do any good. Kernel development has been driven by the commercial linux companies that market to the enterprise like RH, Novel, IBM, Oracle, etc. Servers don't need sound and the big names in kernel development aren't going to devote any resources to linux sound development; they have their own agenda.
  5. I'm beginning to wonder about the health of that hard drive; that's pretty odd behavior. If you have adequate external storage, I recommend backing up your data now. Also, go to the the hard drive manufacturer's website and download their hard drive diagnostic utilities iso; all the major hard drive manufacturers have them for free. Run the diagnostic utility in thorough mode and see if any problems are detected. Other things I would try - boot with any linux livecd and see if you have any problems picking up sda1; boot up mandriva and immediately after booting up run: $ dmesg | grep sda* That will print out all the kernel messages relating to sda. See if any I/O or read/access errors are reported. Those types of messages can mean a hard drive that is starting to fail.
  6. Try mounting with just ntfs instead of ntfs-3g: # mount -t ntfs /dev/sda1 <mount point> Also, check if sda1 shows up with cat /proc/partitions after running mknod. Finally, is sda1 shown in Mandriva Control Center > Disks? If so, is any further information given about sda1? Is this a standard ntfs windows partition, i.e. not a Windows Dynamic Disk?
  7. Fdisk clearly shows that sda1 and sda5 are being picked up by the system. Please also post the output of: $ cat /proc/partitions If sda1 and sda5 are not listed in the above(likely), you can manually create the device files for them in /dev using the mknod command. To test for sda1 run as root: # mknod /dev/sda1 b 8 1 If mknod runs without error and creates /dev/sda1, try mounting it and see if it works.
  8. I don't know what type of sound card you have but I'd be willing to bet it's some version of on-board intel sound on your motherboard. I finally got tired of having my sound fail every other kernel update and bought this turtle beach sound card which has excellent linux support: http://www.newegg.com/Product/Product.aspx?Item=N82E16829118103 I haven't had a sound problem since. If your running a desktop with a spare pci slot, it will be the best $25 you've spent on computer gear in a long time.
  9. To update from the command line, login on the command line like you did before and run: $ su <enter root password> # urpmi.update -a After updating the repos, you can update all installed packages with: # urpmi --update --auto-select
  10. That should be /dev/sda7 not dev/sda7. I would suggest you use this example for you FAT32 partitions: /dev/sda7 <mount point> vfat umask=000,iocharset=utf8 0 0 You can choose whatever directory you want for a mount point. Traditionally, most people put mount points in the /mnt or /media directory, thus the suggestion that you make your mount points in the form /mnt/fat*. The addition of "umask=000" in the above line will ensure that you have read/write access to all your FAT32 partitions, which is what most people want. Without the umask option, a mounted FAT32 partition defaults to read only. Re your question about the difference in form for your root partition and what's been suggested for your FAT32 partitions, that's because mandriva and most other distros set up fstab using UUID instead of device files. Device files for partitions are typically in the form of /dev/sd** or /dev/hd**. UUID(universal unique identifier) is an alternative way of uniquely identifying a partition using a lengthy 128 bit number. You can use either method with fstab but it's just easier to use device files. As far as your two swap files go, you can have as many as you want; it won't hurt a thing. Almost all distros, including mandriva, will detect the existence of swap partitions during the installation and automatically set up mount points to use any and all existing swap partitions.
  11. You also need to post your /etc/fstab file. You can either open the file and copy and paste it here or run the cat /etc/fstab command in the terminal and post the output here. The fstab file is what controls mounting. You probably just need to edit these entries to get your FAT32 partitions to auto mount at boot: /dev/sda7 7358 14717 59119168+ b W95 FAT32 /dev/sda8 14718 22032 58757706 b W95 FAT32 /dev/sda9 22033 30515 68139666 b W95 FAT32 and: /dev/sdd1 * 1 9729 78148161 b W95 FAT32 Mandriva usually sets up in entries in fstab for FAT32 partitions but they are generally set to not auto mount. It's an easy thing to change.
  12. I doubt your battery is bad; your motherboard is too new for that to be a likely cause.When the cmos battery starts going you get symptoms like the date and time resetting. Without a good cmos battery, the cmos cannot retain its setting when power is removed and it keeps resetting to the cmos defaults. From what you describe, the most likely causes are/were bad ram or a failing power supply. It's almost surely a hardware issue, however. If you want to test your ram use a utility called memtest. A lot of livecds like Parted Magic have memtest as a boot option: http://partedmagic.com/ Just boot up with Parted Magic and select Memtest from the boot options. Let it run for a couple hours and see if any errors are reported. You need special equipment to test a power supply.
  13. My permissions on su are different: $ ls -l /bin/su -rwsr-xr-x 1 root root 31696 2008-03-07 14:16 /bin/su* The "sr" indicates that su perms are SUID. You can change the permissions on your /bin/su by logging in as root on a virtual console like you did before and running: # chmod 4755 /bin/su and then checking to make sure you have the same permissions as I do by running: # ls -l /bin/su It should change the permissions but su permissions and changes to them are usually done by security applications. The one mandriva uses is called msec which runs as a demon and it can reset any changed permissions that it doesn't like. The front end for msec is found in the mandriva control center>Security>Set up security level. I suspect that you may have setup msec at a very high security level; one which doesn't allow ordinary users to su to root and open other administrative applications. To check all this out, I would recommend you login to a gui root session by doing the following: 1. Reboot and when you get to the grub screen hit F3 and then "3" instead of "1" like you did last time; 2. That will take you to a command line login prompt. Login as root and run: # startx 3. That should start your defalt gui(kde or gnome). You will have full root privileges from within this environment so be careful. Check out your security setting in mcc and see if anything looks off.
  14. If you go to a virtual console by hitting Ctrl-Alt-F1 can you log in as root? After doing that, you can get back to a gui by hitting Ctrl-Alt-F7. Also, post the output of: $ ls -l /etc/passwd and $ ls -l /bin/su If you can login as root from a virtual console but can't su to root, it could be a permission problem with su.
  • Create New...