Jump to content
xisto Community
Sign in to follow this  
iGuest

USB

Recommended Posts

Anyone have any luck at all getting any version of Linux to utilize the high speed mode of their USB 2.0 card?I have no problems with getting any of my USB stuff to work in Knoppix 3.4 or Debian or Mandrake 10.0. But all version are only using the USB in the slow mode (v1.1). It would be nice to get it to high speed. In Win2000 I get a huge speed increase. I can copy a 4 meg file in less than 2 seconds in Win2000. On Linux it takes about 7 seconds or about 600KB/s.Is there some driver that must be loaded to get the speed up?Using an 80Gig external USB drive in slow mode can be painfull.Card in question is a Belkin USB 2.0 PCI card.

Share this post


Link to post
Share on other sites

Next Prob!i was told that this might be a bug in the distro...I am using Overclockix hd installed which is a knoppix remastered.this is how my fstab looked like before any changes. NOTE that i do not have a dvd and overclockix auto-named the devices as dvd and cdaudio1/etc/fstab: filesystem table.## filesystem mountpoint type options dump pass/dev/hda1 / ext3 defaults,errors=remount-ro 0 1/dev/hda2 none swap sw 0 0proc /proc proc defaults 0 0/dev/fd0 /floppy vfat defaults,user,noauto,showexec,umask=022 0 0/dev/dvd /dvd iso9660 defaults,ro,user,noexec,noauto 0 0/dev/cdaudio /cdaudio iso9660 defaults,ro,user,noexec,noauto 0 0/dev/cdrom /cdrom iso9660 defaults,ro,user,noexec,noauto 0 0# Added by KNOPPIX/dev/hdb5 /mnt/hdb5 ntfs noauto,users,exec,ro,umask=000 0 0# Added by KNOPPIX/dev/sda1 /mnt/sda1 vfat noauto,users,exec,umask=000 0 0and this is my mtab/dev/hda1 / ext3 rw,errors=remount-ro 0 0none /proc proc rw 0 0devpts /dev/pts devpts rw,gid=5,mode=620 0 0usbfs /proc/bus/usb usbfs rw 0 0/dev/cdaudio /cdaudio iso9660 defaults,ro,user,noexec,noauto 0 0/dev/cdrom /cdrom iso9660 defaults,ro,user,noexec,noauto 0 0i click on the cdrom icon and i get an error saying : error kdektopunable to run the specified command. THe file or folder file:/mnt/cdrom does not existsame thing for the cd wras root i try to create a folder names cdrom in the mnt directory and it does not let me .From a console i do this: mount /mnt/cdrom and it does not let me . I can see the cdrom and cdaudio folder in the root partition thoughI corrected the fstab because i did not mount them in /dev but instead i said /mnt/cdrom/dev/cdaudio /mnt/cdaudio1 iso9660 defaults,ro,user,noexec,noauto 0 0/dev/cdrom /mnt/cdrom iso9660 defaults,ro,user,noexec,noauto 0 0Then, the cdrom worked fine but i was still getting this error for the cdrwCould not mount device.The reported error was:mount: special device /dev/cdaudio does not existin the /mnt dir there is a cdrom folder and a cdaudio folderi just tried burning an ISO image using the cd rw and it worked fine. On the other hand though, when i create a new device cdrw on my desktop , i get the above errorls -al /dev | grep cdbrw-rw---- 1 root cdrom 29, 0 Apr 14 2001 aztcd0brw-rw---- 1 root cdrom 41, 0 Apr 14 2001 bpcdlrwxrwxrwx 1 root root 3 May 17 22:45 cdrom -> sr0brw-rw---- 1 root cdrom 24, 0 Apr 14 2001 cdu535brw-rw---- 1 root cdrom 30, 0 Apr 14 2001 cm206cd0brw-rw---- 1 root cdrom 16, 0 Apr 14 2001 gscd0brw-rw---- 1 root cdrom 24, 0 Apr 14 2001 lmscdbrw-rw---- 1 root cdrom 23, 0 Apr 14 2001 mcdlrwxrwxrwx 1 root root 5 May 17 22:40 mcdx -> mcdx0brw-rw---- 1 root cdrom 20, 0 Apr 14 2001 mcdx0brw-rw---- 1 root cdrom 20, 1 Apr 14 2001 mcdx1brw-rw---- 1 root cdrom 20, 2 Apr 14 2001 mcdx2brw-rw---- 1 root cdrom 20, 3 Apr 14 2001 mcdx3brw-rw---- 1 root cdrom 20, 4 Apr 14 2001 mcdx4brw-rw---- 1 root cdrom 17, 0 Apr 14 2001 optcdbrw-rw---- 1 root cdrom 46, 0 Jun 2 2001 pcd0brw-rw---- 1 root cdrom 46, 1 Jun 2 2001 pcd1brw-rw---- 1 root cdrom 46, 2 Jun 2 2001 pcd2brw-rw---- 1 root cdrom 46, 3 Jun 2 2001 pcd3crw-rw-rw- 1 root tty 2, 221 Apr 14 2001 ptycdlrwxrwxrwx 1 root root 6 May 17 22:40 sbpcd -> sbpcd0brw-rw---- 1 root cdrom 25, 0 Apr 14 2001 sbpcd0brw-rw---- 1 root cdrom 25, 1 Apr 14 2001 sbpcd1brw-rw---- 1 root cdrom 25, 2 Apr 14 2001 sbpcd2brw-rw---- 1 root cdrom 25, 3 Apr 14 2001 sbpcd3brw-rw-r-- 1 root cdrom 11, 0 May 30 2001 scd0brw-rw---- 1 root cdrom 11, 1 May 30 2001 scd1brw-rw---- 1 root cdrom 11, 10 May 30 2001 scd10brw-rw---- 1 root cdrom 11, 11 May 30 2001 scd11brw-rw---- 1 root cdrom 11, 12 May 30 2001 scd12brw-rw---- 1 root cdrom 11, 13 May 30 2001 scd13brw-rw---- 1 root cdrom 11, 14 May 30 2001 scd14brw-rw---- 1 root cdrom 11, 15 May 30 2001 scd15brw-rw---- 1 root cdrom 11, 16 May 30 2001 scd16brw-rw---- 1 root cdrom 11, 2 May 30 2001 scd2brw-rw---- 1 root cdrom 11, 3 May 30 2001 scd3brw-rw---- 1 root cdrom 11, 4 May 30 2001 scd4brw-rw---- 1 root cdrom 11, 5 May 30 2001 scd5brw-rw---- 1 root cdrom 11, 6 May 30 2001 scd6brw-rw---- 1 root cdrom 11, 7 May 30 2001 scd7brw-rw---- 1 root cdrom 11, 8 May 30 2001 scd8brw-rw---- 1 root cdrom 11, 9 May 30 2001 scd9brw-rw---- 1 root cdrom 18, 0 Apr 14 2001 sjcdbrw-rw---- 1 root cdrom 15, 0 Apr 14 2001 sonycdlrwxrwxrwx 1 root root 4 May 17 22:40 sr0 -> scd0lrwxrwxrwx 1 root root 4 May 17 22:40 sr1 -> scd1lrwxrwxrwx 1 root root 5 May 17 22:40 sr10 -> scd10lrwxrwxrwx 1 root root 5 May 17 22:40 sr11 -> scd11lrwxrwxrwx 1 root root 5 May 17 22:40 sr12 -> scd12lrwxrwxrwx 1 root root 5 May 17 22:40 sr13 -> scd13lrwxrwxrwx 1 root root 5 May 17 22:40 sr14 -> scd14lrwxrwxrwx 1 root root 5 May 17 22:40 sr15 -> scd15lrwxrwxrwx 1 root root 5 May 17 22:40 sr16 -> scd16lrwxrwxrwx 1 root root 4 May 17 22:40 sr2 -> scd2lrwxrwxrwx 1 root root 4 May 17 22:40 sr3 -> scd3lrwxrwxrwx 1 root root 4 May 17 22:40 sr4 -> scd4lrwxrwxrwx 1 root root 4 May 17 22:40 sr5 -> scd5lrwxrwxrwx 1 root root 4 May 17 22:40 sr6 -> scd6lrwxrwxrwx 1 root root 4 May 17 22:40 sr7 -> scd7lrwxrwxrwx 1 root root 4 May 17 22:40 sr8 -> scd8lrwxrwxrwx 1 root root 4 May 17 22:40 sr9 -> scd9crw-rw-rw- 1 root tty 3, 221 Apr 14 2001 ttycdas of today , this is my fstab/etc/fstab: filesystem table.## filesystem mountpoint type options dump pass/dev/hda1 / ext3 defaults,errors=remount-ro 0 1/dev/hda2 none swap sw 0 0proc /proc proc defaults 0 0/dev/fd0 /floppy vfat defaults,user,noauto,showexec,umask=022 0 0/dev/dvd /dvd iso9660 defaults,ro,user,noexec,noauto 0 0/dev/cdaudio /mnt/cdaudio iso9660 defaults,ro,user,noexec,noauto 0 0/dev/cdrom /mnt/cdrom iso9660 defaults,ro,user,noexec,noauto 0 0# Added by KNOPPIX/dev/hdb5 /mnt/hdb5 ntfs noauto,users,exec,ro,umask=000 0 0# Added by KNOPPIX/dev/sda1 /mnt/sda1 vfat noauto,users,exec,umask=000 0 0i do not have a dvd drive but the dvd in the fstab was entered by knoppix , not by me.in the / root partition i see a folder named cdaudio and another one cdromin the /dev directory i see only a cdrom nothing for cdaudioonce again i did not give my cdrw the name cdaudio. It was named like that by default.ls -al /dev/dvdlrwxrwxrwx 1 root root 16 May 17 22:45 /dev/dvd -> /KNOPPIX/dev/dvdi do not have a dvd drive. Myabe knoppix thinks the cdrw is a dvd ???ls -al /dev/cdromlrwxrwxrwx 1 root root 3 May 17 22:45 /dev/cdrom -> sr0i have 2 IDE devices. one cd rom and one cd rwplease help as this thing is driving me nuts

Share this post


Link to post
Share on other sites

I'm finding a lot to like about Knoppix, but it won't operate onboard sound--Via 8235 AC97-- unless " knoppix alsa" is entered on the boot command line.With hard drive Knoppix installation I've found no way to make the sound system work. Alsa is installed, according to KDE software configuration tables. The enable sound system box is checked on sound configuration panel, but no cigar. SuSE 9.0 runs the sound without any massaging.What needs to be added or modified to start up Alsa at bootup on hard drive Knoppix installation?

Share this post


Link to post
Share on other sites

have tried many many times but nothing ever works. I have followed many online instructions but the installation always failsI ws wondering how many people here have managed to set up ati drivers.

Share this post


Link to post
Share on other sites

I installed knoppix recently and I have a problem which I can't identify.Some of the programs I open takes about 3 minutes to open and someopen right away. For example, konqueror opens in a heartbeat whilekwrite or kview takes forever (3 minutes). Also, opening superkarambatakes a second, but when trying to open the file dialog to select a themeyou wait a long time. Sometimes even the "Start" menu makes youwait several minutes.When starting these programs through konsole showed no errors.Someone has an idea about this issue?thank you./

Share this post


Link to post
Share on other sites

Hi,I am trying to edit video under Knoppix (why not, it works perfectly for editing sound [Audacity is really great], photos, etc...). When I connect my Sony camcorder to my computer (a sony vaio) via firewire, I get the following when I run dmesg:ieee1394: Node added: ID:BUS[0-00:1023] GUID[08004601021bc70c]ieee1394: Node changed: 0-00:1023 -> 0-01:1023raw1394: /dev/raw1394 device initializedscsi singledevice 0 0 1 0scsi singledevice 0 0 2 0scsi singledevice 0 0 3 0scsi singledevice 0 0 4 0scsi singledevice 0 0 5 0scsi singledevice 0 0 6 0scsi singledevice 0 0 7 0scsi singledevice 1 0 1 0scsi singledevice 1 0 2 0scsi singledevice 1 0 3 0scsi singledevice 1 0 4 0scsi singledevice 1 0 5 0scsi singledevice 1 0 6 0scsi singledevice 1 0 7 0Everything looks cool, but how do I mount it?I tried to make a directory in mnt called ieee1394 and mount the raw device:mount /dev/raw1394 ieee1394mount: /dev/raw1394 no es un dispositivo de bloquesWhich hopefully is understandable as being spanish for "not a recognised block device".Any idea what I am doing wrong?

Share this post


Link to post
Share on other sites

Ok I am hoping you all can help me setup a definitive thread on IDE controllers. I presently have 2 systems with Promise Ultra 133 Controllers and had nothing but greif getting them to run right. After reading thru alot of threads here I can see these aren't good to use for CD/DVD burners. I am looking for any feedback negitive and positive you have had with any controllers available for purchase.Is there a brand that you can disable bios so it boots faster?What out there that is speedy any maybe configurable from device manager for speed setting or all do it automatically?What ones work with all devices with no problems?If you see this thread helps you give it a bump to keep it going

Share this post


Link to post
Share on other sites

As many people here have all kinds of computer problems, I thought it would be nice to make a sticky thread, containing some general info on how to check wether your hardware is failing.As there are zillions of different systems around the entire globe, there's no way to make a thread that applies to every situation, but there a few basic things you might want to check, before posting a thread.In this sticky thread, I will include some information on checking:- memory- harddrive- cpu (temperature, voltage)- mainboard (temperature, voltage)- power supplyWell, let's get started!

Share this post


Link to post
Share on other sites

MemoryBad or incompatible memory is one very serious cause of a lot of strange problems. Small errors, to all kinds of strange crashes, can be due to memory problems.The best tool to check if there's a problem with the memory of your system, is MemtestX86.This program tests your memory in a very smart way and will give you trustful results.If you find any errors while checking the memory, it doesn't have to mean your memory is bad. You might want to check a few things, before concluding that the memory is bad.Possible causes for memory problems:- bad memory- CPU problems (CPU voltages too low, overheating, damaged core)- heat problems- power problems (memory voltages too low)- wrong settings (set your BIOS' memory settings to "SPD")- compatibility problems (with mainboard, chipset or other installed memory modules)If you can, it might be good to check your memory on an other system (prefferably with different hardware) as well, before concluding the memory itsself is bad.

Share this post


Link to post
Share on other sites

HarddriveModern harddrives are pretty sensible, when it comes to heat, shocks, or running 24/7. Although they don't brake down that easily (except for some bad series, made by IBM and Maxtor), they can be the cause of some pretty annoying problems.A good tool to check a harddrive is .IBM/Hitachi's Drive Fitness Test.Another good tool for checking a harddrive on mechanical problems is your ear. If you hear any weird noise, coming from your harddrive, it might be dying.

Share this post


Link to post
Share on other sites

CPUModern CPU's don't often get broken, but under certain conditions, they can turn your computer into an electric hell.For all modern CPUs goes, that heat is a killer. Although the Intel CPUs are protected from overheating (most modern chipsets for AMD have this functionality as well), too much heat is never good.There are lots of tools that can show your CPU's temperature. The two programs I like best, are SiSoft Sandra and Mainboard Monitor. MBM is really a nice tool for debugging, as it supports logging of all kinds of system readings.If you own an Intel system (P3/P4), temperatures up to 80C should be no problem, but keeping them at about 50C is the way to go (less is always better!).If you own an AMD system, temperatures up to 90C should be no problem, but keeping them at about 50~60C is once again the best.If your CPU is causing troubles, this also can be due to a mainboard that isn't supplying enough power, a not-so-stable PSU (power supply unit) or a VCore (voltage on the CPU core) that is too low. If you think your VCore is the problem, you might want to crank it up a little. This can be done from the BIOS of most systems. Be careful with this though, as a higher VCore will increase the heat the CPU produces.

Share this post


Link to post
Share on other sites

MainboardMainboards are somewhat harder to check for problems. Some boards are equipped with a diagnostic system (e.g. a display or leds, displaying error messages in case of failures) that can tell you quite a lot, but most boards aren't.Besides of switching mainboards (or other components), you might want to check out the different voltages on the mainboard. By using either MBM or Sandra (see the CPU paragraph), you can check on what voltages your different lines are running. If the readings are way out of order (11V instead of 12V, or 3.8V instead of 3.3V) there's probably something wrong with either your mainboard or your PSU.Nowadays, many boards die from leaking capacitors. If there's any brown mess on/beneath the capacitors on your mainboard (usually situated round the CPU socket), you don't have to search anymore for any other possible causes. This is a very common problem. Some manufacturers replace boards with leaking capacitors under warranty, even if the board's too old for receiving warranty!

Share this post


Link to post
Share on other sites

Power supplyAs I already explained in the mainboard section, many problems can be due to a failing, or too weak power supply. I already told you how to check if the readings of the different powerlines are somewhat correct.If your PSU runs extremely hot, there's a big chance it can't take the load. This is often the cause with cheap supplies, as they aren't intended for heavy use. Depending on the components of your system, you could need quite a heavy PSU.For most modern CPU's, a PSU of at least 350W is recommended. If you can get one with a higer capacity, don't hestitate, but buy!It's pretty likely that some newer systems that are about to be released, will have a CPU consuming over 100W (Intel Prescott). Those systems will need quite a heavy PSU to remain stable.A small note: rather choose a quality PSU over a cheap one. I know you can get 500W PSUs that cost less than a brand 300W PSU. Please don't buy them.... they suck! Most of them can't do the capacity they are sold for, make lots of noise and will generate even some more heat. No good!

Share this post


Link to post
Share on other sites

ConclusionSo you want to check your system's stability? Well, there's quite a nice tool to do so: Prime 95. Just run the torture test for some time and see what happens! If you manage to run it for a long time (e.g. 48 hours) without a single crash, your system is stable!

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.