Jump to content

austinjreid

Members
  • Posts

    3
  • Joined

  • Last visited

Everything posted by austinjreid

  1. Arde, I see you MSI KT4AV mobo has a Via Chipset, I've only seen this on nforce2 chipset boards but it may be worth a try.... Kareena, Your ASUS A7N8Xboard has an nForce2 chipset. I had exaclty the same problem with my Biostar M7NCD with nForce2 chipset, also with Ath-XP 2600+. I posted this earlier on linuxquestions.org.... I searched for ages for a solution, even tried a few other distros (gentoo, suse, PClinuxOS, Knoppix, Kanotix, even debian sarge and sid!), all would eventually start locking up, then only a hard reset was possible, which of course invoked a disk fschk and then HANG again! What you need to do is include the following in your kernel boot options (append line in lilo) .. noapic nolapic note this isnt ACPI! it is the APIC which is interferring with the ACPI, or so I could figure out after loads of searching. I may have got the reason wrong but including the above options WORKS, I have not experienced a hang in over 2 weeks, including a spate of over 72 hrs without rebooting (yes I know its only a small amount of time but its just a figure, not a boast! lol) And the second option above uses a lower case 'L' (not a number 1 or a pipe). I use the above on any live CD i try, just pass those params to the kernel with any others, if its Grub then you can edit the line on the fly at boot time. Also, if you use them with the boot options for install of MDK10.0 (mine used to freeze during install!!) then lilo will be configured with the noapic option, I always add the nolapic option to be sure. Like I said above I'm not entirely sure of the reason, but my ACPI still works and power-down still works, and no hanging! I have no clue what APIC does, all I know it would screw my system! lol Hope this works, and I have seen this for a few nforce2 boards. Aus.
  2. Using the script on http://www.linuxcompatible.org/story23334.html I was able to create a single DVD.ISO from 3 CD.ISOs. The script in the article is actually for Fedora but it worked for me. Basically I think it just breaks up the ISOs and then recompiles them keeping the same dir structure. Being for the Fedora ISOs it does create a warning at the end saying it could not include the Fredora MD5SUM (I think) but it then burned with k3b with no probs. I did this onto a DVD+RW so I didn't mind if it screwed up. However this was before I just saw the above tool from mdk.
  3. I've installed superkaramba and wanted to use the 'slickbar' from kde-look.org. This requires PyKDE (which in turn requires PyQt & SIP) all this then seems to require a setup of Qt3 which is slightly different to the pre-packaged setup on a standard mandrake9.1 install. I'm having a hell of a time trying to install PyKDE because my python won't 'import qt'. I've been told from the mail-lists on PyKDE about re-building Qt3 with cirtain things enabled etc but this seems to just screw up my installation and I don't know where i'm at! Has anyone else had this trouble? If so, to save me keep going round in circles or keep re-building mdk to get Qt3 back to normal, has anyone got a simple step way of doing this? many thanks for any help Austin.
×
×
  • Create New...