adamw

When you set your router to static IP, I believe you're dealing with *its* IP - the IP it uses to access the network on the *other* side of it, i.e., the internet. I don't think you're dealing with whether clients on your *local* network can connect to it via DHCP or not. This is just what it looks like to me from the page you quoted, though, IMBW.

soulse: I'm not sure having swap smaller than RAM will work for this specific thing, though. I'm not massively up on the technical details, but I *thought* hibernation worked by writing the exact memory state to disk then basically shutting the system down, and reading the state back into memory when you woke it up again. How would that work if the swap partition - which Linux uses for the hibernation data - was smaller than the size of the RAM on the system? In general, you're right, though. Huge swap files are pretty pointless.

Pierre: not a lot functionally changed up to 6629, so if you have an official commercial version of MDK with nice customised 6111 drivers (they patched the drivers to fix the problem with 6111 and recent kernels), good for you, I wouldn't worry about updating :). I ran an SN41G2 Shuttle (nforce2 based) under Mandrake for a long time and never had hardware-related problems. Just for data.

You might want to try editing /etc/sysconfig/network-scripts/ifcfg-eth0 and ifcfg-eth1 (I expect your cards are eth0 and eth1, respectively) and adding MII_NOT_SUPPORTED=YES to both. Let us know if that helps any. If it doesn't, revert the change.

cenobite: it's normal(ish). mplayer is quite conservative with caching - it caches 20% of the file on startup. Other players don't cache so much so early. With an mp3 file this should be barely noticeable (it's just spooling about 1MB of data from hard disk to memory, after all) but with a big video file you'll notice it; the bigger the file, the slower your hard disk, the more you'll notice it. (If you try loading a 650MB movie over a wireless network link, you'll REALLY notice it :>)

I don't know, offhand. Why not just read 'em? IIRC, the hdlist files are vaguely human parsable, take a look and you should be able to figure which one matches which directory.

have you tried 'urpmi amarok', yet? Possibly after doing the easyurpmi dance, http://easyurpmi.zarb.org/ ?

RPMS2 in that address doesn't actually mean it's on CD2, it means it's in contrib (RPMS2 is a symlink to contrib, in online mirrors, RPMS3 is a symlink to jpackage). That would make sense, because it means in all likelihood the gimp2 package wasn't on the CDs for 10.0. In that case, as you say, the reporter should go to easyurpmi and set up a contrib source for 10.0, then he'll be able to urpmi the package. BTW, there was a GIMP "2.0" in MDK 9.2 as well, though back then it was actually GIMP 1.3 (the development branch that turned into 2.0). If you have 9.2 and want a newer GIMP, setup a contrib source and install the gimp1.3 package. Hope that's useful to someone out there :)

Ooh, you were doing well up until you downloaded freetype :). In actual fact you *do* have a more recent freetype on the system - MDK installs both freetype 1.x and freetype 2.x alongside each other, the freetype2 package is actually called libfreetype6 (for some bizarre reason). Look for the package and you'll find it. When you're building something on Mandrake and it complains that something is 'not installed', it's a bit misleading - in many cases the *library* is installed, but the files that you need to build other software against the library are *not*. This is because Mandrake splits such files out into separate packages called -devel packages in order to reduce the amount of space needed just to use software (as opposed to building it). So what you actually need to do is install the freetype devel library, and all will (hopefully) be well. Try this, as root: urpmi libfreetype6-devel That should do the trick. Then re-run the Scribus build. Keep this in mind in future - whenever you get a 'so-and-so is not installed' error in a ./configure, you need the libso-and-so-devel package. If you ever come across a build error that traces back to a command with -Lblahblah in it, and blahblah is not found, again you need libblahblah-devel. That one's a bit tricky to explain, but if you see it, hopefully you'll know what I mean.

well, basically the kernel is trying to load the module and it can't because there's something wrong with it. That suggests the build process went badly wrong somewhere, but it's hard to know where :(. Could you find any kind of log output? I'm sorry, I'm not familiar with the ATI module build process.

It needs to build the module because it doesn't have a pre-built one for Mandrake 10.1 - that's OK. Just make sure you have the kernel-source-2.6 package installed and then re-run the installer, it should then be able to rebuild the module just fine. Make sure you're using the most recent nvidia driver, version 6629 I think - the previous one, 6111, and any earlier than that *won't* work (due to a recent change in the stock kernel).

I think 179MB is the smallest installation you can get out of Mandrake, though it sounds like the minimal option hasn't been worked on lately (when it was introduced, IIRC it was much smaller). I don't think Mandrake is the best base for such a project, being a general purpose distro; you might be better off looking at something like Damn Small Linux.

as online gamers the world over are aware, ping times aren't a particularly accurate test of bandwidth, and vice versa. You can have high bandwidth and high ping (high ping is bad), or low bandwidth and low ping. A far more useful test would be to download a moderately sized file (say, a megabyte) and test the transfer speed. Ping *can* be an indicator, a server with a very high ping is unlikely to give you good transfer speeds, but one with very low ping certainly isn't guaranteed to give you a good transfer either.

Please hit ESC during the boot process and tell us what's showing on the screen when the boot process is slow. As far as wifi goes, can you be more specific than 'doesn't work'? What type of card are you using? Do you get useful error messages in dmesg?

soulse: ug, I was misremembering a discussion about the G5 desktops, you're quite right they haven't solved the thermal problem with getting G5s into laptops yet. Sorry. As far as I'm aware, the problems you mentioned are the only ones (though for some people these are showstoppers). "apple makes nice machines but they are expensive for what you are getting...so if you don't intend to dual boot with osX don't get one. (if you like the pretty industrial design work on one get a sony viao...they are pretty)" Well, yeah, but the problem there is that Vaios cost MORE than Apples :). Why do you think I haven't managed to buy a new one in three years? Hehe. Commodity PC laptops are cheap, but brand names are expensive.

Looks like a udev bug, might be worth searching qa.mandrakesoft.com to see if it's been posted yet. (/dev entries on mandrake from 10.1 onwards are created dynamically on boot by udev; obviously it ought to create a raw1394 entry when the kernel is told to load the firewire module, but equally obviously it doesn't). a 'cleaner' hack than the rc.local one would be to edit the udev rules - located in /etc/udev - to create the device when the firewire modules are loaded. But this should be done by MDKsoft, as I said, so if it isn't, it's a bug. Search Bugzilla, if there's not a bug for this already, submit one, and with any luck it'll be fixed for 10.2 :)

@bvc: sorry, I should've phrased that more precisely. I didn't mean to imply that KDE doesn't work :D. I should've said GNOME's philosophy is to 'do the right thing' - they believe that in a lot of cases there's a single sensible default behaviour that the DE should endeavour to know about and apply. KDE's philosophy is more that different behaviours work for different people and it should be easy for a user to configure pretty much any aspect of the DE to behave any way he, she or it likes.

Yep, use urpmi. Or the graphical installer: Or menu, configuration, system, packaging, install software, type 'gimp' in the search box, pick the gimp 2.0 package, and hit 'install'. Bingo! Any of those dependencies that aren't installed yet will be installed for you. Wasn't that easy? :) BTW, if you just do 'urpmi gimp', I think you might end up with version 1.2. Using urpmi you might need to use gimp2 or gimp2_0 or something along those lines.

bvc: well, it started off as a repository for 2.7 on Cooker. If you ever tried to use it 10.0, it wouldn't have worked (very well or possibly at all), because it was always built against Cooker. After 10.1 came out, Goetz rebuilt them all against 10.1 then stuck a fork in them - they'll now never change from their current state. Goetz does quite a lot of packaging work so I'd be surprised if they were totally broken on 10.1. There's another directory on his page where he's building 2.9 against current Cooker, please don't recommend those packages to 10.1 users anybody :)

The 10.1 OE ISO images for non-Club members came out today, so if you haven't started downloading 10.0 yet, may as well go for that! We all make mistakes as noobs, don't worry about it. I think I installed MDK about six times the first month I used it :)

that is odd, yes - what normally happens to me when I update kernels is I run the installer once and I get that error message (it can't update the links, or however it puts it), then I run the installer again and it works. Ah well, whatever works for you is good. :)

To nuke the dedicated driver (which didn't work for me either), edit /etc/modprobe.conf and change the line for the network card - it'll be something like 'alias eth0 acx111', change it to 'alias eth0 ndiswrapper' (that'll try and load ndiswrapper instead). I had the same card, briefly - after my failure with acx111 I tried ndiswrapper, which promptly froze the kernel. Fun stuff. I took the POS back to Future Shop and swapped it for an SMC card - cost seventy bucks more, but it works...:)

yaagob: sorry, I don't currently have a printer, so I'm not sure exactly what service would be dealing with that. If it's the USB service you probably don't want to turn it off so you're probably stuck. If it's a dedicated printing service you could just turn it off. It might be worth looking at the logs right after booting up (/var/log/boot.log and /var/log/syslog are the most pertinent) to see exactly what it's doing all that time. You never know, you might learn something, or be able to fix it. :) lawsonrc: that's not nice :). I don't know offhand. The first thing to do is troubleshoot. Try running MCC from a console; to do this, go to a console, become root, and type 'drakconf'. It'll load MCC and, presumably, hang. If we're lucky, it'll print some kind of error message to explain what's going wrong...

If you have both sets of sources set up, I believe it would ask for the CDs if the versions were the same (i.e. the package had not changed between CE and OE). If OE had a later version of the package, it would go and download it. You could force it to use the CE version with the --media option to urpmi, which limits it to a certain medium or media: urpmi --media main,contrib libfreetype6 would tell urpmi to install libfreetype6 but only from either the 'main' or 'contrib' medium; if you had another medium called, for instance, 'plf', this command would completely ignore that medium. I believe co-existing media from CE and OE are supposed to work OK, but if you want to make absolutely sure there's no problems with the update, scoopy's suggestion to run urpmi.removemedia -a before adding the new sources is a good one.

10.0 for AMD64 was rolled quite a while back now and it was MDK's first cut at it (they didn't have a lot of AMD64 machines around to try it with either). Before you give up I'd suggest trying 10.1 OE for AMD64. It's on mirrors now so you could try an FTP install (though apparently the hdlists are broken, which would make that impossible :<) or according to Warly free ISOs will be released shortly. If you really need it now, though, just go with SuSE - it's a fine distribution, by all accounts. What works is good. :)