Hello!!!

For 3 weeks now i've been trying to make my pcmcia slot to work on my toshiba laptop 1110, so i can get to internet. I'm running out of patience...now. I need some help with it.

I've been using mandrake 9.1, everything else seems to work just fine, all the other devices were detected properly, except pcmcia slot. I haven't found anything from the internet to enlight me in this matter (I'm serioulsy thinking of changing to redhat 9).

My machine has following components:
Toshiba 1110
Mobility Radeon
DVD-Rom SD-2612
256 Ram

Any help would appreciated

Moved to the Hardware -> Laptops forum

(base10) Welcome to Linux Questions! Jeremy has recently added a laptop sub-forum in the Hardware section. Hopefully someone can help you out in there.

Try checking your bios settings for the PCIC

Bios i have on my laptop i so called legacy free type of Bios. It uses ACPI instead, so i don't have that option.

ok, are you ready to type some stuff at the command line and post the responses? Good! here goes, type each item below on the command line and post the response:
(if you're unfamiliar with how to do this, just ask)

lspci
lsmod
dmesg | grep -A 20 'Linux Kernel Card Services'
cat /etc/modules.conf

hopefully these will shed some light on what's going on, additionally can you say exactly what card you're trying to use?

Yes i do need some help. I've been only using mandrake such a short time. How do i check these out

Hi there

I have a similar problem with redhat 9.0

lspci "command not found"
lsmod "command not found"
dmesg | grep etc... no socket drivers loaded
cat /etc/modules returns alias 3c589_cs
alias usb-controller usb-ohci
alias eth0 3c589_cs
alias eth1 pcnet_cs

please help or I will go back to XP.... Sniff

ok, 0987654321, in mandrake you need to click on the black tv-screen looking button to bring up a terminal window, then type those commands and list the responses, you should first type "su", (no quotes) followed by your root password, unless you logged in as root to begin with.

for you, Mr. Lost-It, I'm wondering why no socket drivers were loaded, we're going to need some more info, and this may take a while to fix, then again, it may go quickly, if you're feeling frustrated by it, by all means, boot back to XP, take a break, play a game and then give it another go, you might as well see what RedHat has to offer since you've come this far. here's some info that would be helpful:

what make/model number of your computer (it's a notebook?)?, secondly, we'll need some more console info:
1. ifconfig -a
2. iwconfig

If you're wondering why the installation isn't quite as smooth as windows, you need to be aware that while most manufacturers write drivers for windows and put them on a cd and include it in the box, most do not do the same for linux, it's a market-share thing. Linux is well worth checking out, it's not going to be the same "your 84yr old grandmother can install it", situation though. It's getting closer to that, and for many people it just works right out-of-the-box, for others it does not. Further, you should be aware that some devices are unsupported and it's a "don't hold your breath" kinda thing as to when/if they ever will be.

Just for the record ther is no turning back, I never give in.....

anyway the result of the requested info.

Tosiba Tecra 530cdt

these commands also return command not found.. I am logged into the root, is the console different to a terminal window

wow, these are very basic utils common to all distros, sounds like a corrupted installation, just to be sure can you type ls /sbin and ls /usr/bin and see what you see? You're sure you're logged in as root? Did you do standard installation of redhat?

meanwhile, I'm going to get a look at what hardware's in that machine.

Newbie, if you get

lspci "command not found"
lsmod "command not found"

Then you are probably not logged in as root. These commands are usually not in the search path of non-root accounts. Either login as root, or run the command with the full path attached to it, like 'sbin/lspci'

FYI - you can also get the pci listing as ' cat /proc/pci'

Hope this helps

I login using SU and end up with the # prompt, I can see all the command in sbin but most resturn Bash: lspci: command not found
even if use the full path ?(should I panic no or later)

The result of the cat command

pci devices found

bus o, device o, function 0
host bridge toshiba american info systems 601 (rev 38)
bus 0, device 4, function 0:
vga controller Chips and technologies f65555 HiQVPro (rev 195)
..... (as it is display probably not of interest now)...
bus 0, device 11, function 0:
usb controller nec corp. usb (rev 1)
IRQ 11.
Master capable. latency 64. min gnt =1. Max lat =21
non prefetchable 32 bit mem at 0xfdfff000

regards brett

Yes. But if you su to root, then you still keep the path settings of the account you originally logged in with. Remember that su is not a replacement for login!

In order to have the /sbin in your path you either need to login as root, or add the path to your user account settings.

To see whether you need to panic, do an "ls -l lspci" in /sbin. If there is no lspci then your whole installation is warped. If you can see it, then running the command as /sbin/lspci should work, and if you are root you should be able to run lspci from anywhere.

HI

OK I su and then change directory ot /sbin and can see the command and then enter it or use the full pathe but it still returns the same result.
how else can I log into the root, how can I add the path to my search path when logged in as usr..

I am reinstalling for the second tie but I think I will end up in the same spot.

I will post a follow up from Sunny ? Sweden when it has finished

How to log in as root? Ummmm.... log in as root ;-) Seriously. User root, and then your root password.

I think you still don't understand the difference between login and su. Su just changes user, but DOES NOT LOG YOU IN AGAIN AS THAT USER! I know it's confusing - check the man pages for su. One of the side-effects of this is that when you su, you basically keep the environment settings of the user you su-ed from. So, su-ing to root makes you root, but you won't have the root environment settings.

For that matter, even when you are in /sbin (like you did a 'cd /sbin' , and then you type lspci -- it still won't run lspci, if the 'dot' (i.e. the current position in the file system) is not in the search path! To check whether that might be the case, cd into /sbin and type ./sbin -- if that works then you do not have ./ in your search path.

I'm not sure where mandrake sets user environment variables. You can try in your .bashrc, for example. You'll find that in your home directory. RedHat has a system-wide bashrc in /etc -- as I said not sure how Mandrake does that.

You would add something like
export PATH=$PATH:/sbin
if you wanted /sbin to be added to your path. .bashrc is run every time you launch a shell (assuming bash is your default shell), so that should do it.

Still, what you're saying sounds very strange to me ....