4 quirks with Slackware.
I've been running Slackware for a couple of days now, and it rocks. :) It's so much more sleeker than Red Hat. There are a couple of little things though, which I hope you guys can help me out with.
(1) USB CDROM & Camera How do I get this to work? I tried modprobe usb-storage mount -t iso9660 /dev/sda /mnt/cdrom mount: device /dev/sda is not a valid block device mkdir /mnt/camera mount /dev/sda1 /mnt/camera mount: device /dev/sda is not a valid block device Same with sda1, etc. (2) X crashes when I switch between it and a virtual console. I have no idea what's causing it. I found an instance on google where passing on vga=0x317 as a kernel parameter helped solve this (for monitor resolutions of 1024x768), but I opened my lilo configuration file and found append vga=0x317 already there. Red Hat 9.0 did not have this problem... I could switch happily to and fro. I suspect it may be my monitor or video card, so I tried to run SuperProbe as suggested by the book Slackware Essentials. It doesn't seem to exist, and I can't find it online or in the Slackware mirrors. Where can I get this? (3) When I log in as "Ren", most of my commands don't work (No such file or directory). So I copied the PATH in root, su-ed to Ren, and hit PATH="whatever was copied from root". But some commands don't seem to exist at all, unless I su to root. Sometimes, su-ing to root doesn't work either. I have to switch to a virtual console, and then everything will be alright on that console. (4) This is the weirdest one. #ls bla bla bla xf86cfg xf86config #xf86cfg command not found #xf86config command not found I just used them yesterday, and now I can't? Out of curiousity, can I cut and paste from a rxvt terminal? Other than these weird little problems, I'm so happy with Slackware and Linux (was a fulltime WinXP user until a few days ago). All those wasted years! Ren |
Unfortunetly, I can not help out with 1 or 2, I have had very good success with X and have yet to have to try to mess with any of the default settings. One idea though:
At first you are at a console then when you do startx it takes you over to tty7 console, but the orginal console you typed startx on should be giving messages. For instance on my system, I am logging on in tty1, I startx and it takes me over to tty7, but if I go back to tty1 I can see messages on the screen telling me what X is doing. That might be an idea to see what X is doing when it freezes. The other problems sound like you have a PATH issue. When you are signed in as ren typed echo $PATH and see what it gives you mine looks like this: bash-2.05b$ echo $PATH /usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/usr/games:/opt/www/htdig/bin:/usr/lib/java/bin:/usr/lib/java/jre/bin:/opt/kde/bin:/usr/lib/qt-3.2.2/bin:/usr/share/texmf/bin:.:/home/me/scripts If yours is not listing anything or just a few things, that could be your problem. There are some things on the system, that you can't run enless you are root, most of these are in the /sbin or /usr/sbin directories. I have found that a regular user has somethings in their path that root does not, so that could be why you are having the problem of some programs working under other users, ect. Now if you echo $PATH and /bin is in your path, and the programs in /bin won't run, then I would check permissions on them. Other than that I would be at a loss. You can, also, run a command by in the directory that command is in and typing ./<command>. That will tell you where or not it is the command or the path. If you PATH=$PATH:/home/me in the terminal that will remain valid only for this session. When you log out, then back in again the /home/me will not be on your path any longer. To make it stick, you can do one of two things: 1. edit the file /etc/profile, and add to the PATH variable in there. 2. You can create a file and put it in your home directory that will be executed every time you log in. The name of the file depends on what shell you are using. For bash the name is .bashrc, I believe for the korn shell it is .kshrc, but I am not sure for the others. But you can create this file add in the path you want, then everytime you log in it should be set. Hopefully some of this helps a little bit. mike |
With the CDROM issue, look into lilo.conf, whether u have:
append=" hdd=ide-scsi " the like on it ? If it is ur cdrom is installed on hdd channel, then try mount -t iso9660 /dev/hdd /mnt/cdrom If worked create a symbolic link in /dev/cdrom to point to it, if not try hdc .. As for /etcc/X11/XFree86Config, try replace it with that one from redhat, if worked like it should, then u can find out the diff between them .. |
By default, Slack doesnt allow non root to view or use commands that can change OS stuff.
Of, course you can always add your own paths and permissions. Its kinda kewl, especially if you dont want non root peeps messing with those commands. One more security plus for Slackware. |
re: #4
I had issues running xf86config as root as well.
Seems that if you "su" to root the paths aren't the same. What worked for me was physically logging in as "root" at the login prompt (instead of "su"ing). Worked for me then. Cheers, Bob |
You can 'su -' which makes it like a login shell. And 'man su' for how to change the 'supath'. Many commands can be accessed by typing their full path even if they aren't on your normal path. Only those that check the UID (I suppose) will refuse to run. If you don't know where they are (and 'which' indicates they aren't on your path) 'whereis' will usually turn them up. If not, 'locate' will unless your 'slocate' has actually been set to conceal stuff you don't have access to.
I don't know if the rxvt copy issue was addressed, but you should be able just to drag the mouse over rxvt and middle click wherever you want to paste. If some app takes the mouse in rxvt, like mc, you can shift-drag to get a normal copy operation. Sorry I can't help with the more serious issues. |
Thanks for all the replies, everyone. :) It's much appreciated.
I set the path thing. I'll let you know how it works. "su -" is new to me. Thanks! About my CDROM... I added append=" hdb=ide-scsi" to lilo.conf. Still no luck with it. I went directory hopping in seach of modules, and loaded every one I could find. This one had a problem. root@slackware:~# modprobe usb-ohci /lib/modules/2.4.22/kernel/drivers/usb/host/usb-ohci.o.gz: init-module: No such device /lib/modules/2.4.22/kernel/drivers/usb/host/usb-ohci.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. /lib/modules/2.4.22/kernel/drivers/usb/host/usb-ohci.o.gz: insmod usb-ohci failed What parameters are there? Is this OHCI thing important? Ren |
Quote:
lilo will prompt for successfull, if ur lilo.conf is ok, after reboot take change can then take effect, if u have not yet knew that... As for which hdx u should use, there is 2 EIDE-slots(4 channel), primary master/hda, primary slave/hdb, secondary master/hdc, secondary slave/hdd. You should know to which one ur cdrom is attached on. If u said hdb, it looked like that u shared the same data cable between ur primary master (hda,harddisk) with the cdrom (primary slave, hdb). For performance reason it is recomended to use both of the EIDE-slots primary as well as secondary (with 2 data cables, prevent cable bottle neck..). |
Quote:
No, I didn't know that. Thanks for the clarification. :) I did that, rebooted, and then tried #mount -t iso9660 /dev/hdc /dev/cdrom hdc is not a valid block device. Arghh. Ren |
I suggest :
# dmesg > dmesg.out then grab dmesg.output here enclosed between [_code_] .. [_/code_] with out the underscore. |
/dev/hd? is only for IDE devices. Since your CD ROM is a USB device it should show up as /dev/sda?. Do a dmesg to see if it shows up during boot. Or watch while booting, scrolling back with SHIFT+PGUP in order to see the messages. There are several modules tha'll have to load for your CD ROM and camera to show up. Which kernel are you using? If all else fails go to RUNT linux homepage and get yourself a boot floppy from there. It's designed to boot linux from a USB FLASH device, but also will boot from USB floppy or CD ROM. Boot with that and then do lsmod to see which modules are used.
|
dirstyguy:
I'm sorry, I'm not sure what you meant. I did #dmesg > dmesg.out, opened up the dmesg.out files with an editor, but couldn't find the word [code] anywhere, with out without an underscore. gnashley: I can't seem to see it in dmesg. There's an interesting bit here... usb-ohci.c: usb-00:0d.1, NEC Corporation USB (#2) usb-ohci.c: USB HC TakeOver failed! My kernel version is 2.4.22. I'd be really interested to know what modules to load. I tried loading everything I could find, with no luck. The usb-ohci.c one refuses to load, as I posted earlier. I wish I could follow your suggestion about the RUNT homepage, but I don't have a floppy drive, no external drives at all save for this USB CDROM which I can't access. Actually, while waiting for advice here, I figured maybe I could compile a new kernel and see if that worked. Pretty scary for a newbie. I downloaded the 2.6.1 kernel, compiled it, set up lilo and rebooted. Basically, I followed all the instructions on the www.slackware.com/book site to compile a new kernel, but when I booted up I was at same old 2.4.22 Just not my week. :) Ren |
Forget about the hdx thingy I mentioned if u have a USB CDROM..
I meant, that u should post the entire dmesg.out in here, enclosed between the [ code ] and [ /code ] tag, that help ppl to interprete or find out something .. Kernel compile would be a little bit too much advanture for now I'd say, if .. then better try to upgrade, try swaret, look into /etc/swaret.conf, man swaret. I'd say try to search on the LQ forums for the keywords "USB CDROM" maybe also on google, but post ur dmesg.out here, possibly some one will even can figured out faster .. |
Ah, sorry for misunderstanding you. Here it is. :)
I've looked for several hours on Google and on this site. I can't count how many people have gotten away with #mount /dev/sda1 /mnt/cdrom ... they don't know how lucky they are. ;) Here's the output. I'll look for swaret in the meantime. Code:
Linux version 2.4.22 (root@midas) (gcc version 3.2.3) #6 Tue Sep 2 17:43:01 PDT 2003 |
Sorry I can help with usb, never deal with. U can now remove the line u added to lilo.conf (append=" hdx=ide-scsi "). It is only for ide-atapi-cdrom. Then run lilo, reboot.
In linux, if u use brand new hardware u have count with "patience" .. If u r looking on swaret.conf, comment (or delete) that line that say EXCLUDE=kernel to be #EXCLUDE=kernel Or ur kernel will not be updated. Using swaret mean: swaret --updated then wait .., and later swaret --upgrade Good luck .. |
All times are GMT -5. The time now is 08:56 PM. |