SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Hi! I finally upgraded to kernel 2.6.13, added udev, hotplug, hal, dbus.It actually worked this morning! When plugggin in my usb HD's they showed up in /media/, but I could not see anything on them!? I tried to burn a cd with kb3, and saw both devices listed in there (hdc, hdd), even burnt a cd just fine. Tried mounting and unmounting various cd's, worked flawlessly. I was just working on adding more media support for dvd's, when I decided to restart for some reason. Now anytime I try to mount (doesn't matter what) it just hangs, and does nothing. My usb drives don't show up, k3b fails to start. I must have messed up something, but can't figure out what.. Can someone please shed some light on this?
One thing that might have caused it, was that I accidently created a symlink aka "ln -s hdb /dev/dvd"- which was wrong I meant to use "hdc"
so I tried removing the link with:
unlink /dev/dvd
rm -rf /dev/dvd
and recreated it like:
ln -s hdc /dev/dvd
This is what's currently in there, do I need to change that?:
# permissions for IDE CD devices
BUS="ide", KERNEL="*[!0-9]", PROGRAM="/bin/cat /proc/ide/%k/media", RESULT="cdrom*", NAME="%k", GROUP="cdrom", MODE="0660"
# permissions for IDE floppy devices
BUS="ide", KERNEL="*[!0-9]", PROGRAM="/bin/cat /proc/ide/%k/media", RESULT="floppy*", NAME="%k", GROUP="floppy", MODE="0660"
Here might be another clue: It's telling me those points don't exist, but they are there!?
root@wildblue:~# mount -t iso9660 dev/cdrom /mnt/cdrom
mount: special device dev/cdrom does not exist
root@wildblue:/dev# mount -t iso9660 dev/hdc /mnt/cdrom
mount: special device dev/hdc does not exist
root@wildblue:/dev# mount -t iso9660 dev/hdd /mnt/cdrom
mount: special device dev/hdd does not exist
root@wildblue:~# lsusb
Bus 006 Device 001: ID 0000:0000
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 002: ID 03f0:2911 Hewlett-Packard
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 003: ID 04b4:6830 Cypress Semiconductor Corp. USB-2.0 IDE Adapter
Bus 001 Device 001: ID 0000:0000
looks like it'spicking up my printer, but not the usb drive...
Ok! I fixed it by removing and reinstalling dbus, hal, udev, and kdebase.
It all works, except the directories for my usb drives still show "empty", any idea why it's doing that?
I put no enties in fstab, I thought dbus or hal is taking care of that, maybe I ma wrong!?
mount:
/dev/hda6 on / type reiserfs (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
/dev/hda1 on /media/fat-c type vfat (rw)
/dev/hda2 on /media/fat-d type vfat (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
usbfs on /proc/bus/usb type usbfs (rw)
now,-this is strange! after I had everything working (besides that one usb problem), I did one restart. Now, no cd drives get recognized, no audio cd, k3b is crashing wile trying to start. The exact same problem I had earlier. I am wondering if I should give up on that hal-dbus thing. How do you guys usually go about making all that work, reliably? Just write udev rules?
I was suggested to look at the /usr/share/hal/fdi/90defaultpolicy/storage-policy.fd :
media true managed kudzu true true true true true true true true true auto cdrom cdrecorder cdrecorder cdrecorder cdrecorder cdrecorder cdrecorder cdrecorder true auto floppy true auto zip true auto jaz true true volume.fstype @block.storage_device:storage.bus disk zip volume.label false true true true true true true true false true true true true true true true true fals
Do you know what this means?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.