Linux - DistributionsThis forum is for Distribution specific questions.
Red Hat, Slackware, Debian, Novell, LFS, Mandriva, Ubuntu, Fedora - the list goes on and on...
Note: An (*) indicates there is no official participation from that distribution here at LQ.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Suse 9.1 installed on a IBM thinkpad T40. I have a problem with my IBM 256 Mbmemory key. If plugged at startup then boot hangs after Domain name caching and resume only if memory key is removed. If i plug the card after boot and try to mount it with "mount /dev/sda /windows/usbkey" the shell hangs and only when i remove the key i get "/dev/sda is not a valid block".
Key led blinks normally (as it does in windows) and in /var/log/messages everything seems fine and the key is correctly identified and mounted as /dev/sda
I tried disabling hotplug and acpi but no success...
due to some other minor problems, i'm very close to format and install mdk10 ...
I have had similar problems. After upgrading the kernel (2.6.7) everything works fine.
If you do not want to compile a kernel on your own, then use YAST Online Update (YOU).
The latest official SuSE kernel (2.6.5-7.95-default) works also fine with USB sticks.
It also fixes one another problem: It was not possible to read CD/DVD +-RW media
created with Windows Packet writing programs (InCD, DirectCd, etc.)
You can also disable the supermounter (submount) and add a entry
for your USB-Key in your /etc/fstab.
Here the entry for the USB-Stick from my /etc/fstab
....
/dev/sde1_____/media/usb-stick_____auto________noauto,user,exec,sync,gid=100,umask=0003____0_0_#HOTPLUG
...
Sorry for the "_". Since space characters get somehow messed up, a "_" represents a space.
In my case it's /dev/sde. noauto prevents the USB partition getting automatically mounted on boot.
I mount the USB Stick under group ID=100 (Users group) and umask=0003 so the members
of the users group can have r/w access.
Thanks for your detailed reply, but i was using the latest kernel available through YOU. I remeber i had the very same problem using SUSE live CD 9.1, so there must be some incompatibilitiy between the IBM usb key and some SUSE kernel settings.
Due to other minor problem i finally decided to install another distro, and now everything works fine !
Ok, I don't seem to have the problem of usb stick recognition, Suse 9.1 version 2.6.7.95 will not recognize the format (VFAT) the var/log/meesage looks good until "Jul 16 07:37:16 linux submountd: unable to determine filesystem type", Everything else works. I have a Lexar sport jump drive. This was working until the upgrade to 2.6.7.95. Any Thoughts on how to work this out. I have place in my FSTAB /dev/sda1 /mnt vfat noauto users,rq 0 0" and attempted to mount the usbkey the old fashioned way, but I still get the same message. Any thoughts on this? I am about to uninstall and reinstall to base version 2..6.5, which everything worked, including my usb jump drive.
I suggest that you first check if the vfat Filesystem support is there:
cat /etc/filesystems
will give you the list of all filesystems.
If vfat is there, then you may consider to disable submount and mount the "old" way.
If not, you need to enable vfat support, either by compiling vfat into the kernel,
or as loadable module.
I did what you suggested and the lexar jumpdrive works well. I did have to change the entry some to see what was on the drive. I followed the example you gave me and compared it to the Suse portal page. But now I seem to have a problem with the /etc/fstab entries being read properly. I mount the drive and get the error message "(mntenf): warning: no final newline at the end of /etc/fstab" I click "ok" and then the contents of the drive show up in konqueror. Have not made alot of entries in the fstab, but I have never run into this. The entries I made loo k like this:
/dev/sda1 /media/jumpdrive auto noauto,users,exec,sync 0 0
/dev/sdb1 /media/GE auto noauto,users,exec,sync 0 0
The Jumpdrive is the Lexar and the GE is a generic usb key that is made by General Electric. When I put in the umask0000 and rw, the drive would not show it's contents and would not always mount. and it would show an error message "dsev/sda1 not a valid block". I took the entry and modified it to look more like the Suse example and well it works. I just need to find out hime to fix the other error. What is a "final newline" anyway?
I probably need to add that there are spaces like
/dev/sda1 /media/jumpdrive auto noauto,users,exec,sync 0 0
/dev/sdb1 /media/GE auto noauto,user,exec,sync 0 0
There that looks more like my /etc/fstab entries. Sorry for the possible confusion.
I did notice on your /etc/fstab you completed the end by commenting it out. I did not see that on any Suse page. That would not effect anything would it?
Thanks
Susesarus
I put a comment just for a simple reason: To know that the entry is related to a hotplug device.
It will not change anything.
Obviously that umask0000 will lead to an error since the correct syntax is
umask=0000
To correct the "final newline" error, just insert an empty line after the last line in your /etc/fstab.
Hey Vlad,
I found the syntax error and corrected that. I did not think of hitting enter at the end of the line. Kinda of makes sense. This is frustrating when you can't find a clear explaination in the help on your distro. Thanks for athe assistance I am going to fix my "fstab" now. I will tell you how it comes out. Thanks again.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.