Jump to content

angst

Members
  • Content Count

    55
  • Joined

  • Last visited

Community Reputation

0 Neutral

About angst

  • Rank
    Linux newbie forever

Contact Methods

  • Website URL
    http://
  • ICQ
    0
  1. After much wailing and gnashing of teeth it looks like this may be a linux kernel bug which affects some Asus motherboards.
  2. I tried various acpi apm options. Tried lilo vice grub. Here is a cut of the syslog from shortly before rebooting. This seems notable but I don't know what to do with it or if it is the problem. Nov 10 14:23:21 localhost kernel: ACPI: resource nForce2_smbus [io 0x1c00-0x1c3f] conflicts with ACPI region SM00 [io 0x1c00-0x1c05] Nov 10 14:23:21 localhost kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver Nov 10 14:23:21 localhost kernel: ACPI: resource nForce2_smbus [io 0x1c80-0x1cbf] conflicts with ACPI region SM01 [io 0x1c80-0x1c85] Nov 10 14:23:21 localhost kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver Edited to remove to much probably useless info. see next post.
  3. My HDD with Mandriva 2010.2 died so I purchase a new drive and decided to install 2011. Install went fine and I managed to get updates after using easy-urpmi to find working update servers. Also got rid of that butt ugly Rosa simple launcher. Anyway... When I restart my computer after shutting down with 2011 my MB BIOS reports a boot failure and to reset BIOS to defaults. Doing so is the only way to get the system to boot again. With my Windows 7 HDD installed I have no problems shutting down and restarting. Where should I look to fix this? ACPI or APM settings? Somewhere else? Are there logs I should be looking at? ****Warning: System BOOT Fail **** Your system last boot fail or POST interrupted. Please enter setup to load Default and reboot again. Motherboard is Asus P5N72-T Premium.
  4. What's on your mind?

  5. angst

    Kmail

    Hi John, There are numerous bug reports with regard to column views and column resizing in kmail on the KDE bug list. Many of them are marked as 'fixed' so I guess we just need to wait on Mandriva to update.
  6. I had an orphan notice shortly after a nearly flawless upgrade from 2009.0 to 2009.1. There was a menu entry for Helix player (or maybe it was Totem) which would not run so I used MCC to remove it and upon completion it gave me a very long list of orphans. A quick perusal of the list showed an awful lot of important looking 2009.1 packages so I saved a copy for later examination. Having previously been bitten in the ass by long dependency lists when removing things has made me cautious.
  7. angst

    Display rate

    I typo'd the nvidia-settings. Went back and fixed it. I was actually referring to 'usr'.
  8. angst

    Display rate

    Not trying to be a nit picking *hole or anything but that should be: /usr/bin/nvidia-settings I'm sure daniewicz knew that but mistyped. I do that with 'usr' fairly regularly. :D
  9. Heh heh. I've had this book, dog eared and bookmarked like crazy, laying open on my computer desk directly between me and the monitor for at least 3 years now. Its a great reference when you need it. I haven't really gotten any smarter when it comes to linux though. :unsure: My fault I'm sure.
  10. Nah. I had lame selected. Just now I uninstalled grip 11mdvg and deleted the .grip files in my home dir and reinstalled grip11mdvg. Now I see the proper commands in the encoder command line. Just checked it out and it works fine. Edit: I went into my other user dir and had the same behavior. I then deleted all the .grip files in /~ and ran it again. This time it came up with the proper encoder line for lame. Seems I just needed to delete those files and all is well. Thanks Greg. angst
  11. Got it. Checking it out. Hmm. I can't get it to write v2 tags unless I put '--add-id3v2' in the 'Encoder command-line' box. (which would be the behavior of the official repo version :huh: ) Maybe I am doing something wrong? Please don't spend too much time and trouble on this, Greg. Your efforts are appreciated but there are so many other ripping/encoding options I don't want to see you waste your time on a program that may be used by very few people. You probably have better/more interesting things to do. Plus I now know how to make the repo version spit out the proper tags. Thank you. angst
  12. On Wed, Jan 7, 2009 at 8:18 PM, Adam Williamson <awilliamson@mandriva.org> wrote: > On Wed, 2009-01-07 at 20:11 +0100, Götz Waschk wrote: >> On Wed, Jan 7, 2009 at 8:06 PM, Adam Williamson <devel@mandriva.com> wrote: >> > Adam Williamson <awilliamson@mandriva.com> 1:3.3.1-10mdv2009.1: >> > - enable id3lib support, there's really no reason not to that I can see from [url="http://lists.mandriva.com/cooker/2009-01/msg00263.php"]http://lists.mandriva.com/cooker/2009-01/msg00263.php[/url] >> I have disabled it on purpose. With the lame patch the tags are >> created by lame itself. Lame writes id3v4 while id3lib only supports >> id3v3. So the id3lib dep is unnessessary. > ah, I was going to ask but figured you wouldn't remember. :) > However, it was a user request: > https://mandrivausers.org/index.php?showtopic=77344&hl= The user thinks it only add id3v1, this is caused by lame, see lame's help page: Note: A version 2 tag will NOT be added unless one of the input fields won't fit in a version 1 tag (e.g. the title string is longer than 30 characters), or the '--add-id3v2' or '--id3v2-only' options are used, or output is redirected to stdout. You could add --add-id3v2 to the lame command line in the patch, that would help. Regards, Götz Where Götz writes 'lame writes id3v4 while id3lib only supports id3v3', are id3v3 and id3v4 synonymous with id3v2.3 and id3v2.4? I guess the gist of the above is if you want want the repo version of grip to write id3v2 tags you need to go in Grip to the Config/Encoder/Encoder tab and in the 'Encoder command line' text box add the appropriate id3v2 option to tell lame what or what not to write. If you tell it to write a idv2 tag it will be id3v2.4. If you use Gregs Grip rpm then Grip (using id3lib) will write an id3v2.3 tag. Clear as mud. :D Thank you all for going to all the trouble to make inquiries and/or compile and suggest other software. angst
  13. Greg, Your Grip package seems fine. Installs, runs, removes, and reinstalls ok. And it writes ID3V2 tags as it should. I don't know if there is anything else I should for. Some kind of RPM or Error log maybe? Thank you for your time and effort. angst
  14. Cool. PM me. I will try it out. :D Edit: Got it. Looked good in the little time I had to check it out. Thank you, Greg.
×
×
  • Create New...