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.

Introduction to Linux - A Hands on Guide

This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.

As usual, there are changes in udev packaging that need mentioning...
The system udev rules now reside in /lib/udev/rules.d/ instead of
/etc/udev/rules.d/ in older versions. There should never be a reason
to edit anything in /lib/udev/rules.d/, so if you think you have a case
where this is required, either you're wrong or it needs to be addressed
in the upstream source. However, you can override default rules by
placing one with an identical name inside /etc/udev/rules.d/
The rules files in /etc/udev/rules.d/ are still intended to (maybe) be
edited as needed by local system administrators, and as such, the rules
for optical and network devices will still be placed there.

Also in UPGRADE.TXT in regard to any rc.udev.new that may be residing in your system:

Quote:

6. Fix your config files. Some of the config files in /etc are going to
need your attention. You'll find the new incoming config files on
your system with the ".new" extension. You may need to fill these in
with information from your old config files and then move them over.

Last edited by gegechris99; 04-06-2009 at 10:54 AM.
Reason: Added advice in UPGRADE.TXT

Checkout the /etc and search for the sdx devices where the xx is a combination of first/second device on the channel. For example: usually the sda it's a sata disk(if you have). make a directory in /mnt to mount the camera. after mount the camera like a cdrom drive mount /dev/sdb1 /mnt/hitachi

Checkout the /etc and search for the sdx devices where the xx is a combination of first/second device on the channel. For example: usually the sda it's a sata disk(if you have). make a directory in /mnt to mount the camera. after mount the camera like a cdrom drive mount /dev/sdb1 /mnt/hitachi

i hope that's help in something.

1) you meant /dev/sdx?

2) i upgraded from 12.0 to 12.2, on:
12.0 when i plunged my phone to usb in data storage mode i was able to access its memory card through /dev/sda1 device
but when i plunge it into usb under 12.2 then:
a) non sdx (x is variable) device file is created
b) phone hangs constantly "transferring data" (what fkn data?)
c) turns off in a while

So please - don't tell me that was intended because there is better way to mount a usb device (it doesn't work ERGO it is NOT better at all)
And i think it is not a minor issue (since USB is very popular these days)

But what makes me angry is that: 12.2 suggest that this is tuned up and polished version of slackware 12... instead:

I have problems with my nvidia card - i know it is old - but if windows still support it (and we all know how microsoft like obsolete hardware) why linux can't? (thank God that nvidia released a new version of its drivers (even for cards as old as mine)) - as for open alternative for nvidia drivers...

I have problem with usb - and im writing this because i haven't still found solution (as for udev - someone pls write if it works, and what it messed up when you installed it (if something was messed up))

And java installed in java directory - with symbolic link to current version (if u don't get it - it should be reversed - so updating would require relinking to new version dir) - it is aesthetic but still weird. I didn't noticed at first and now have link to link to other version dir

To be honest, I have no clue, what your problem is actually caused by, so what follows are just some thoughts that may help you to track your problem further down.

If I read this thread correctly your problem occurs only on a system upgraded from Slackware 12.0 to 12.2, but not on a fresh 12.2 installation. This strongly indicates that it is not something inherently wrong with Slackware 12.2, but something that went wrong during the upgrade.

Here are my ideas, hoping they may point you to something useful.

1. It is usually not necessary to compile a kernel for USB device support. Only in rare occasions you need additional driver support for a particular device. But if the huge-smp kernel supports your device, in almost every case the additional driver will work just fine as a module with the generic-smp kernel (or the other stock kernels). Therefore my first suggestion is that you go back to the generic-smp kernel. Hardware support compiled into the kernel may interfere with the UDEV subsystem (not very likely, though).

2. When I upgraded from 12.1 to 12.2 on an old laptop, I overlooked the hint that the UDEV configuration had changed. As a consequence I lost support for my WLAN PC Card. I got it working again by removing and re-installing everything UDEV related, but at the cost that now I had no sound. The reason was, that somehow the firmware for my soundchip was gone, for some reason. Copying the Yamaha files from /usr/src/linux/firmware from another Slackware 12.2 system over to the laptop solved the problem.
May be you have a similar problem.

3. You might try to connect your camera with your computer using Digikam. If Digikam sees your camera, but you still can't mount it, this would, IMHO, indicate, that there is a problem with the USB device mode (PTP vs. mass storage).

install Digikam, eg. using a script from SlackBuilds.org or a pre-compiled binary from Slacky.eu or LinuxPackages.net (all of them work, as far as I can tell); see 3. above

compare the content of /usr/src/linux/firmware on your working fresh 12.2 install with that on the upgraded system, do the same for any directories containing camera drivers

compare the settings in /etc/modprobe.d/... and so on, to see if there is a module activated on one system that is blacklisted or commented out on the other one

Or:

Copy over all things you need for your daily work to your fresh 12.2 system, such as email, then do a fresh install on the upgraded system, too. It depends on the amount of data and configuration work necessary, which approach is more econonmic for you...

If nothing of the above solves your problem, it should at least help you to track the problem further down. The experts here will have a better chance to support you, then (and will certainly happily do so, as they helped me so often demonstrating A LOT of patience; so come back when you have a little more details).