martouf

I googled: "micro innovations" usb linux and found this Sourceforge project, so you might be able to get your camera going. If your goal is to have a web camera but not just to make this particular camera work, then you might try to google: "usb camera" linux Find a camera which is already supported by a driver included in Major distro.

Well, you being the grad student with a Bright Idea, you have been granted the supreme opportunity to Learn Something. 8) The scope of the project seems more than sufficient for using a LDAP server for containing the user account database, unless the SMB server you mention is supposed to be the authoritative source of all identification and authentication information. More information about the SMB server is in order, as well as an indication of the linux boxes being intended for use by one person at a time or many? The linux boxes may participate in a Windows Domain or a Windows Workgroup, and one could even serve as a Domain Controller. Linux Journal had a very excellent series of articles about a LDAP implementation - it starts here. Part II and Part III

I hear your frustration, but keep in mind Mandrake reliably serves a substantial user population world-wide. When you say "freezes", do you mean the mouse pointer won't move and when you tap the Caps Lock button, the CapsLock LED doesn't change state? or do you mean some progress indicator window just sits there unchanging? Have you typed Ctrl-Alt-1 and logged in as root to see what your system is up to? It sounds like you've got flakey USB hardware.

I don't think you need to worry about package availability because both Red Hat and SuSE serve practically identical audiences - only one is to the west of the Atlantic and the other to the east, respectively. I say this as a RHCE who uses SuSE at home.

ah, well then supermount is either making an icon for the usb drive because it's still listed in /etc/fstab or there's a config file which now has an entry in it for the usb drive. 'lsof' is a good tool to use to see what files supermount has open so you can find the config file if the documentation for it doesn't spell out where to look for the config file.

There are Fedora mirrors and I'm certain you can adjust your Fedora config to use them. As for the distro choice, I think you're observing a cylindrical clear silica liquid container filled to half capacity. In other words: 6 of a set of 12 or a half-dozen, your choice. "Faster" should not be a consideration, much less a Real World issue.

there's probably an arrow head as part of the icon which is empty when the device isn't connected and mounted and turns color when the device is there... a slight change to indicate current status. the stuff which appears on the desktop is found in the Desktop directory, which means you could get rid of it by deleting the correct file found in that directory or you could just right-click on the offending icon and select "delete".

There is a firmware issue with some of the LG CD drives. The affected LG drives are not entirely ATAPI compliant. Please be sure to either update your firmware or to confirm the LG drive you have is not one of the problematic drives before you load Linux. Read these threads: 1. Mandrake forum 2. Mandrake Linux notice I would expect the problematic drives would end up non-functional with any distro if they have not had their firmware updated.

In general, if hardware is flakey in Windows, you can't expect it to be much better with Linux. There are exceptions, of course. Windows stupidity can cause flakiness which vanishes with Linux. The point being, if you have an honest-to-goodness hardware problem, there's no software/operating_system which can fix it. Yes, it appears now confirmed the firewire port on the Audigy card is the source of the problem(s). Since you have other firewire ports, there's no loss to disabling the Audigy firewire port, just gain. Your options are to configure the Audigy card itself to disable that problematic firewire port (if that's at all possible), or to read through the threads I indicated very carefully to learn how to edit your system's pcimap so that no firewire driver is loaded for the Audigy port even though the port is detected. The problem is not in the list of things which can be solved by switching to another distro. You have a serious but not impossible to overcome hardware problem.

the good-for-testing manual equivalent of the line you had in your /etc/fstab is: "mount -t ext2 -o user,noauto,umask=0 /dev/sda1 /mnt/usbstick" So, if "mount -t ext2 /dev/sda1 /mnt/usbstick" works but the above does not, then ... If danleff hadn't spotted the problem, I would have suggested building your way up from the simplest (least options) manual mount and add options until it stop working. That way you'd be able to zero in on the problem.

try extracting them first in your home directory, then become 'root' and move ('mv') them to the icewm/themes directory. you want to get this done right the first time to avoid having to reinstall icewm and trying again, so you might practice this first by moving the extracted files to a directory you create under your home directory. the fact that important system files are owned by root and not by yourself in your login persona of a regular user - is to protect you from trashing Something Important.

no, I used a XFree86 4.3.99 system to try out what I was asking you to do and the underlying OS was SuSE 9.1. Of course there are differences, every distro has a similar but different idea on naming and where-in-the-filesystem-is-carmen-sandy-logfile. 8) Your problem may be caused by your BIOS. There are a number of reports online from people having the same problem with GX270 and SX270 systems. A first try would be to make a BIOS setup change: Enter the BIOS setup, go to 'Integrated Devices', then to 'Onboard video buffer'. Change it from the default 1Mb to 8Mb. If you're comfortable flashing a new BIOS, also consider up[censored] to the "A04" BIOS now available from Dell. If you're not comfortable and the vidbuffer change works for you, then just skip it. The GX/SX270 systems all at one point had BIOSes which did not properly report the amount of video RAM, thus breaking the X i865G drivers. Dell has subsequently fixed this and made newer BIOSes available.

ah ha! Found the documentation here. The 865G chipset is absolutely supported, so the problem must be a matter of not knowing exactly which video modes the BIOS reports are available. Once you adjust your config to use one of the reported modes, you should be fine.

I think the I810 screen driver loaded OK, and the key error message is "No video BIOS modes for chosen depth." Meaning: too many colors, not enough video RAM for requested config Be sure to read the documentation on the X screen driver in case you need to add a line in the config so the driver carves out some system RAM to use as video RAM. The Intel 865G does not have any RAM set aside for it's exclusive use and is given a memory region instead. run this: "X :1 -probeonly" and then cut-and-paste the file it creates "/var/log/XFree86.n.log" (where 'n' is the number reported when you run the hardware probe) so we can have a look..

I think the previous posting properly belongs to the "How to access fdisk in linux?" thread.

sorry to put on my black cap, shirt with vertical white and black alternating stripes, black shorts, raise my arm and blow on my whistle, but: (I think I'll call it "DefRef" in the future - 'Definition Referee' or 'Definition Reference' are possible word plays) actually, the char is a 'vertical bar'. It's just a char like any other byte value. In a command interpreter or 'shell', however, it has special meaning. It is the way to indicate the shell should connect the standard output file descriptor of the process on the left of the char to the standard input file descriptor of the process on the right of the char. It's my experience to call it 'pipe', while suggestive of it's special meaning in a shell, only confuses the new user since it glosses over the subtlety of chars having special meanings only in certain limited contexts. For more information, here are some online references in order of how canonical they are: 1. The Free Dictionary 2. WordIQ (scroll down a ways..) 3. and the international standards organization to be the last word on ISO8859-1 don't let your eyes glaze over reading the last entry, it's your handy complete reference guide!

I found this thread, which won't solve the problem but does make me feel it's very likely you already have all the pieces you need to make your card work. Sometimes the hard part isn't doing the right thing but doing the right things in the right order.

Would you kindly be more descriptive and specific in stating what your difficulty is? Or are you simply asking "is this card supported? will I make a horrible mistake if I buy it?" ?? 'fess up! 8)

Umm, "blue screen"? You mean a screen with light grey text and deep blue background and lots of hex digits in the middle and words at the top like "Exception #XX in XMFXMX.DLL"? and no little funny ascii bug drawing on the screen and the word "Oops"? If that's the case, then the problem is unlikely to be related to the CD at all... Please confirm the above and answer danleff's questions before we can proceed on this.

I'm pretty confident MDK 10 has the wireless extensions already compiled into the kernel. For your wireless card, you're probably going to need one of the following (not certain which at the moment): 1. Intel's Centrino drivers 2. ndiswrapper or 3. Linuxant's DriverLoader If you're happy generally with MDK, then I wouldn't recommend changing the distro. Sorry, DDan, but I think ramza500 has made a good choice and is prepared and self-sufficient enough to make a good go of it. Words of wisdom (I did not author): Quote: What do you mean Unix isn't user friendly?! Of course it's user friendly! It's just picky about who it's friends are. Enjoy!

glad to hear the troubles have been worked out.. 8) I'd venture your friend may have tried some brute-forcing of configuration tools or config files in his efforts to get PPP working. It wouldn't surprise me, and it can sometimes be effective. But the true power of Unix tools and philosophy is the power of subtlety. Extensively and rigorously documented, but subtlety nonetheless. Although, I should point out putting things back to right didn't actually require a full reinstallation: 'cause "Linux" is modular, see? the kppp package is a separate and complete box o'stuff which can be reset to "stock" by simple reinstallation of the package instead of the whole distro (a collection of packages). Add +1 to the happy ending column, folks. My work here is done. a closing remark for all seekers: do, please, do take a little time to compose your problem/request/symptoms, describe them, give examples and include config file contents, speak up on what you've tried to do about the problem, go ahead and give voice to a suspicion you may harbor regarding the cause and effects, because offering help in this way is alot like triage or diagnosis.

It's good you're aware you needed to be root to do the install. Ah, well then it seems you might not have the 'binutils' package installed (although it occurs to me you really ought have 'ld' on your system somewhere or else many more things than the nvidia driver install would have problems). 'ld' ought to be in /usr/bin and '/usr/bin' should be in the execution path (check with "echo $PATH" ). hmmm... the installation instructions indicate there's nothing you need to do other than "sh installername.mun". What's your "echo $PATH" looks like? can you "ls -l /usr/bin/ld"? Can you tell me what you have when you run "uname -a"? Can you verify the 'binutil' package is installed? Would you know how to install the package if it's missing?

I think you need to be root, not a regular user, when you run the "sh installername". Login as root or "su - root", then try the Nvidia driver install again. Note that's "su - root" not just "su". You'll need the full root environment just as if you've logged in as root.

.. but it doesn't sound like everything is really fine in Windows. If you're having USB problems or a mysteriously appearing firewire port, then things are not yet really "fine". As you've said, you've tested the Audigy card in another system and there it really is OK, yes? Does your Athlon system have onboard Firewire and/or audio? The SB Audigy card has been well supported since early in the 2.4 kernel series via the EMU10K1 driver, so Mandrake 10 ought to detect it and configure it automagically. Yes, the Windows issue(s) technically don't have anything to do with the linux boot hang, except for the fact it's the same hardware in both cases. And I'm not yet convinced there isn't some sort of underlying hardware problem like IRQ assignments. Hmm... many of the article I'm finding via google talk about having IRQ issues and also the Audigy Firewire port not behaving well. But about the same number of articles are written by people who report no problems with it at all. This Red Hat thread may help. Not sure, though. This other Fedora thread looks more like your problem report.

DDan, the first two meanings of the word are "being in a rough or unfinished state" and "lacking refinement or delicacy". I think an almost breathlessly worded posting with a difficult to discern account of the problem qualifies. Robstr12 - we'll do what we can to help but please keep in mind your responsibility to help us pare down the information to the essence of the problem. Work with us and we'll be able to work with you. It seems you're confusing "static IP address" with the DNS data needed to bootstrap you friend's DNS resolver. Technically, a static IP address is an address assigned to a system for its exclusive use. It cannot be shared with any other system. Dial4less is not selling you an address, so that's why when you ask about a static address they won't agree or respond. When you initiate your PPP link with Dial4less, you are issued a temporary address by their equipment, many times referred to as a "dynamic IP address". DNS is a service which translates human system naming to Internet address numbers. Before DNS is functioning, how can a system resolve names to addresses? You must supply to your system a list of pre-resolved addresses for the DNS servers of your ISP. You can supply the addresses of any DNS server your system can reach, but be aware in many cases ISPs prevent your accessing all but their own DNS servers. It's more a question of neighborliness than legality. The "disable existing DNS servers" checkbox has to do with what should be done with the contents of an existing resolv.conf file when you initiate a PPP link? If you don't choose to disable, then the resolv.conf contents will be used regardless of the state of the PPP link. Choose this only if you have a local network providing DNS services. You will find three tools indispensible in collecting the information you need when setting up a new system. The tools work on a system whose own DNS resolver is functioning, so it may be necessary to get a friend to run them. I'll run them and interpret their output for you (condensing the output as I go): First the "whois" tool: "whois dial4less.com" [size:3][tt]domain is registered by enom.com registry service is provided by domain-registry.com the technical contact is Ecom Networks, Inc and is located in Mount Laurel, NJ name servers are NS.ECOMNET.NET and NS2.ECOMNET.NET [/tt][/color] Secondly the "dig" tool: "dig www.dial4less.com" [size:3][tt]Interesting.. this system has no address. No surprise the website is "down", then. [/tt][/color] "dig ns.ecomnet.net" [size:3][tt]This query returns useful information. Mainly, the IP addresses for all three Ecom DNS servers (one more than is listed in the dial4less registration information). ns.ecomnet.net 209.3.183.5 ns2.ecomnet.net 209.3.185.6 ns3.ecomnet.net 65.115.231.135 [/tt][/color] Thirdly the "host" tool: "host www.nameofsomesystem.com" The host tool is for checking name resolution and for testing the resolver. You must enter the already resolved addresses of the Ecom DNS servers into the DNS configuration section of kppp so that your system knows how to reach the DNS servers when you request name resolution after the ppp link is established.