martouf

uuuhhh, but DHCP is done by daemons or userspace client utilities. you thinking about something else?

Quote: if you need an analogy: fitting you with a distribution is like fitting you with a shoe. The choice of shoe depends on what you intend to do with it. [tt]If you know the purpose up front, that may be true, but, starting with a vague idea... well???[/tt] you sure you want to go feed the goats in those shoes? 8)

card, I wish. naww, onboard PnP chip - can you imagine?!

ok, if you're getting joy from building kernels, then one thing you could do is compare the original 2.6.7 config very carefully against the 2.6.8.1 config. (if you haven't already, that is) "diff /boot/config-2.6.7 /boot/config-2.6.8.1" anything interesting in the output? one way of expressing the design philosophy (as I understand it) is the kernel that best matches your hardware is the kernel which has loaded the modules your hardware needs.

danger, will robinson! writing to NTFS is still dangerous to the health of your filesystem. last I read about it, the driver still has problems allocating new NTFS space for files. It's safe only to overwrite existing files and only so long as the new contents are no larger than the old contents.

great! I gather setup #1 worked just fine, right? now, did setup #2 work? or were you only able to communicate with the d-link wifi box (the DI-514)? btw, thanks for the info about the ISP. I looked through their technical support. They're careful to avoid actually providing much help in setting up your own LAN using their service. tsk! when the d-link box says the WAN port is ready, what does it say about it? can you collect the info from the Management section about the WAN port? (don't post a screenshot, if you can avoid it, please) I'm most interested in seeing what it says the IP addr is of the WAN port. don't enable the DHCP server of the d-link box until it's clear it won't interfere with the WAN port settings. when you have successfully communicated with the d-link box, use WinXP and: Start -> Run -> "cmd" -> OK (you type what's in the "" chars) then: "ipconfig /all" please report: the info from your ethernet interface so far so good .. one step forward at a time...

glad to hear the burlap had a touch of dry rot what?! 'thick'? no way! (really, no way!) you've been at this for what? 5 days (clock time)? you want me to tell you about fussing with a HP 6340 Pavillion with its almost-but-not-quite Soundblaster 5 plug-n-pray sound chip? for three weeks? "A mind once expanded by a new idea, never returns to its original shape." -- Oliver Wendell Holmes (the quote is quite likely paraphrased) hmm.. does that go for waistlines, too? :x say, what's the output of 'cat /proc/asound/cards'? and do you have a /etc/init.d/alsasound file? the 'root' that is init should do the card restoration automagically during the boot process. You're doing manually what should be happening without your intervention. also, try 'su - root' instead of simply 'su' and check the PATH envar. I'll gladly explain if you note a difference.

was there a specific issue with the 2.6.7 kernel which prompted you to use the 2.6.8.1 instead? since you have both available, you could compare the varied /proc/sys/net/ipv4/* and ipv6/* settings - that's just a guess, though. No need to look in ipv6 if 'ifconfig' doesn't have a 'inet6 addr' line. what's the most recent kernel Linuxant has tested their driver? my €0,02 - use what works and don't update the kernel unless you have a specific security/driver reason.

before you make your decision, have a look here at the Mepis distro site. the choice of SuSE personal vs. professional means whether or not things like gcc (GNU C Compiler) are included without any additional steps. are you intending to have a Win98-type web surfing system for your use? or a software development and/or LAN server system? if the former, then LiveCDs and 'personal' distro versions will certainly provide the means to further your education. if you need an analogy: fitting you with a distribution is like fitting you with a shoe. The choice of shoe depends on what you intend to do with it.

you may find this article interesting. my personal experience is if the SPEC numbers aren't 2x or 4x different, then it usually isn't readily apparent to the eyeball there's a difference. don't flame, please! 8) I'm writing about everyday low system demand activity on a system not suffering from RAM starvation - not doing big jobs like kernel compilation. so don't slam your wallet closed just because one SPEC result is a few points different than another. iamroot: in any case, you can't really make a clockrate comparison between PowerPC (RISC) and Pentium (CISC). Apples and, umm, Oranges.

you may need to start with a version of Windows labelled "for PCs without an Operating System" (or words to similar effect) - a version which comes with a boot disk. The versions labelled "Upgrade" might not help you very much. if you have a system restore disc instead of bootable WinXP, be aware what it will probably do is restore the 'factory stock' ('as shipped') hard disk image. if your WinXP disc is bootable, the recovery console should be able to fix the MBR issue, but be aware it will prevent Mandrake from booting until you can boot a Mandrake disc and reinstall the Grub (or Lilo) bootloader. Speaking of Lilo - the original bootsector when you loaded it (or caused it to be loaded) should still be found in /boot/boot.NNNN where NNNN is the name of the device where the new MBR was written. You might check the saved bootsector contents with 'xxd /boot/boot.NNNN' to see if it's a Microsoft bootsector. If it is, you could restore it with '/sbin/lilo -s /boot/boot.NNNN -u'. Be aware if you do so, then you'll be at paragraph #3 (above).

the plan for partitioning looks fine to me.. can't use NTFS on the 'shared' filesystem, you'll need to use FAT32 and be aware you can't make filesystem links. distro choice can be very personal and not always completely based on logic I'd rather not get into recommending one or the other. However, I will note it seems to me more people have run into trouble setting up fresh with Mandrake 10 than Fedora. 'course you might consider SuSE... (your call, though)

a pointer to the documentation your ISP provides for setting up the cable modem would really help.. it would be best to start off with a "known good" configuration and then make changes one at a time. as in (stepwise): 1. one computer connected to the cable modem using a 'configuration supported by the ISP' (meaning: usually Windows). (this to learn if your ISP uses an unusual network design) 2. the same computer and configuration now connected to the DI-514, and the DI-514 connected to the cable modem. (this to learn how to set up the DI-514 WAN port) 3. once it's known how to configure the WAN port, then it's possible to know how to set up the DI-514 DHCP server for your LAN. (this to learn how to set up the other computers on your LAN) 4. if the DI-514 is anything like my DI-774, then it's default is to send all wireless traffic directly to the WAN port. No wireless to LAN traffic is permitted. (good for security, but maybe not what you have in mind?)

you might want to consider making a 120MB /boot 'trampoline' on the primary drive. Use partition magic to shrink the WinXP partition 120MB and move it 'down' that same 120MB. If there's an OEM partition ahead of the WinXP partition, then leave that one alone and create the /boot partition in between the OEM and WinXP partitions. With that done, use Grub and go ahead and install it in the MBR of the primary drive, since you'll now always have /boot/grub around to direct your OS loading.

atcskyfox: you need the i386-discX.iso files first. make sure to check the md5sums of the downloads before you burn them. you only need the srpms.iso files (srpm == Source RPM) if you're planning to work with the source code of all of the Fedora software.

kutashi: if you have RH9, then 'rpm -Uhv' this rpm. phos: you using Fedora? if so, then 'rpm -Uhv' the gaim package (not gaim-src, gaim-debug, gaim.tar, or gaim.mdk) from one of these Fedora mirrors.

beej, glad to see you're hanging in there... you're on the right track. give yourself plus points. I've been busy elsewhere with ndiswrapper issues (v0.9 and later) so I haven't been 'round to follow along with every step. believe me, I'm not having a laugh at anyone's expense. if the name of the stored configuration is not specified, then the file /etc/asound.state will be used to store or restore your card's config. the card number need not be specified if you only have one sound card. for example, SuSE 9.1 does "/usr/sbin/alsactl -f /etc/asound.state store" when init invokes "/etc/init.d/alsasound stop", and "/usr/sbin/alsactl -F -f /etc/asound.state restore" when init invokes "/etc/init.d/alsasound start". yours should do likewise, too. if (as root) you get "not found" for "alsactl", it means "/usr/sbin" is not in the PATH environment variable (envar). Check with "echo $PATH". check contents of /etc/asound.state with "more /etc/asound.state" and "ls -l /etc/asound.state". once you've set all of your Audigy controls the way you like them, then 'alsactl store' should save them for use later. Once stored, 'alsactl -F restore' should restore all of controls the way you set them. you'll likely find the contents of asound.state mostly human readable (mostly harmless?), with all of the controls you adjusted named and with suitable values. I realize I may seem a bit "throw 'em in the deep end", but honestly, I'm dropping you in right by the edge of the pool. 8)

using Partition Magic to set up your partitions is a Good Thing. unfortunately, Boot Magic is often a Bad Thing. would you be distressed to uninstall Boot Magic, make sure WinXP is still OK and happy, then install MDK again and permit the native bootloader (Grub, isn't it?) to write to the MBR?

if you were to choose the "S300 gimp-print" driver instead of the "bj8pa06n.upp" driver, you can adjust first the "Print Mode" option (try a higher quality) and then adjust second the "Density" option (try increasing 0.1 at a time). try using the Control Center gui (or Fedora equivalent) to adjust the printer settings/options/parameters.

acpi=ht is applicable to systems with HyperThreading CPUs. acpi=noirq is applicable to many systems, as ACPI support is still "an area of active development" (read: sometimes buggy ) 2.6 kernels seem most sensitive to ACPI handling. 2.4 kernels, not so much. enjoy!

brandon, hi.. you probably don't want to rely on ndiswrapper 0.6. There's been a great deal of development done on the driver since then.. in order to help you along at a later step, please provide your 'uname -r' output. in order to build the kernel module, you need the 'make' package installed. if you don't also have 'gcc' and 'glibc' packages installed, you'll need them, too. (you can grab them from the SuSE 9.1 Professional mirrors)

a rescue disk could be used to boot your system so you can reset all of the account passwords. always keep in mind that linux passwords are case-sensitive eVeN if you UsE InterCapSpelling.

check this reply in your other (identical - tsk!) thread.

this bit of advice looks very hopeful. here's a link to someone who has a similar set up. this message seems hopeful, too. I should stop looking.. this modem has been around since 2000. (see this link) Plug it in, it'll probably work. Have you checked the Mandrake hardware compatibility list? (BTW, my google searches were "speedstream 5200 linux" and "mandrake speedstream 5200" )

this thread was "new" only a month ago. no big changes until the major distros all incorporate more mature SATA drivers. the best advice I can give you is to try to boot from a "Live CD" based on the distro you're interested in eventually installing. using 'lspci' you can learn the technical details of your SATA controller, and then use this site or research the web for information about your controller.