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.
Distribution: slamd64 2.6.12 Slackware 2.4.32 Windows XP x64 pro
Posts: 383
Rep:
May not be anything, but did you replace the symlink in /usr/src/ for linux to the source for 2.6.10? I found that if you don't point the programs to the source some don't work.
I'd go and ln -s /usr/src/linux /usr/src/2.6.10 just a thought
Update: k3b 0.11.19 is fixed for 2.6.10. Back to 2.6.10 for me again.
The udev rules must be comma delimited with no spaces. The site I went to was misleading on this issue. This has allowed me to mount both of my pen drives. However, I still cannot get my SD flash memory card to work.
Below is the output of dmesg. This is quite suspicious, because it seems to think my USB card reader is an ethernet card or something.
Quote:
eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
Vendor: SMSC Model: 223 U HS-CF Rev: 1.95
Type: Direct-Access ANSI SCSI revision: 00
Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 0
And below is the pertinent line from my rules file:
This creates a symlink /dev/flash that points to /dev/sda and a /dev/flash0 that points to a character device /dev/sg0. It doesn't recognize any partitions (i.e., my actual card itself), which I would expect to be something like /dev/sda1. I don't know where I'd find the mounting point, if it exists, or if it doesn't exist, how I would allow it to mount.
I just set up my cups server on my slack 10 box and it was a snap.
First I uncommented the paralell printer section in /etc/rc.d/rc.modules file.
(I don't know if I needed to do this but I did it any way.)
Next I rebooted and the system spotted my printer right off the bat.
I went to settings > control center > peripherals > printers and clicked add...
Printer works!
Slackware is a full featured system and most things can be set up without the radical approch.
I do a full install and most anything I need is already there.
For example: You can turn the arts system off in control center then type killall -9 artsd
This is how I would get rid if arts sound.
After install I always type mail to see the latest advice from Volkerding. This showed me how to set my ide cd-rw drive to scsi so I could use it to create / burn cd's using cdparanoia, mkisofs, cdrecord.
See the man pages and /usr/doc/cdrtools...
Lots of good ideas in the slackware install forum under how I do it.
I have tried lots of distros, but I keep coming back to slack because I think it is the best!
Good luck.
Originally posted by Hangdog42 I'm not sure why you are having trouble with k3b and 2.6. My straight Slack 10.0 installation (none of that -current nonsense) is running a 2.6.7 kernel and k3b works just fine. I suppose one of the later 2.6 kernels might break it, I just haven't tried.
actually ALL of the later ones break it.. it was decided that scsi emulation was evil/stupid and was removed, that's why it didn't work.. luckily for me I have an older extenal scsi burner as well as an internal ide one
About the xmms/xine problem: alsa in general doesn't like outputting sound from two sources at once. As earlier mentioned you might want to disable arts/kde sound, and you also might want to take a look at something like dmix (gentoo guide, might be helpful: http://gentoo-wiki.com/HOWTO_ALSA_sound_mixer_aka_dmix). But do you really need sound from xmms and xine at the same time?
it was decided that scsi emulation was evil/stupid and was removed, that's why it didn't work..
Hmm. I never had SCSI emulation enabled in the first place (at least I don't think so). In my kernel config SCSI CDROM support is disabled. However I do have IDE/ATAPI CDROM support compiled into my kernel. I may have to download the 2.6.10 source and see if that disables k3b on my system.
Originally posted by Hangdog42 Hmm. I never had SCSI emulation enabled in the first place (at least I don't think so). In my kernel config SCSI CDROM support is disabled. However I do have IDE/ATAPI CDROM support compiled into my kernel. I may have to download the 2.6.10 source and see if that disables k3b on my system.
I believe you will need SCSI emulation for USB and Firewire drive, am I right?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.