Dell wireless WLAN 1450 Dual Band WLAN Mini-PCI card not recognised
Linux - Wireless NetworkingThis forum is for the discussion of wireless networking in 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.
First:
May be you misunderstood me, because my last query was not related to NTFS , it was general question, about umask and chmod.
Second:
Dose modifying any files on my windows NTFS partition from Linux, mean modifying NTFS partition itself????
Third:
section
((3.2 Can the Driver write to an NTFS volume, too?
Not really, but if you only need to copy files from Linux to Windows on a dual-boot machine, see "How to write to NTFS" below for a possible way to work around the lack of write support. For write support in Linux, read on.
There are two drivers, currently. The original driver, in 2.4 has some write code in it, but it is extremely dangerous to use it. The possibility of destroying your filesystem is very high.))
I have been confused here, what does it mean the driver here? see the title : Can the Driver write.........
For umask and chmod, you probably do want to search around here or read the man pages. I really can't intelligently discuss the differences between the two.
Quote:
Dose modifying any files on my windows NTFS partition from Linux, mean modifying NTFS partition itself????
Well, yes and no. You aren't modifying the size of the partition, buyt you are modifying the contents of the partition. And should something go wrong, you stand to lose the entire contents of the partition.
Quote:
I have been confused here, what does it mean the driver here? see the title : Can the Driver write.........
In this context, "the driver" is referring to the bit of code (which is part of the kernel) that actually handles the NTFS read and write operations. The code differs between the 2.4 adn 2.6 series kernels, hence the different warnings. And as you can see from the warnings, even the improvements made since the 2.4 drivers don't really make the NTFS driver useful.
but I leave them as read-only for the reasons stated in the quote. If I need to write to XP, I actually mount a USB drive (which is VFAT, not NTFS) and write to that instead of NTFS
Do you mean you are capable to leave them as read and write also?????because I left them as read and write but I could not write to the contents of the partition!!!!!!
Sorry, I missed your post. And to be honest, I'm not sure I understand what you are asking. Let me rephrase it and please correct where I'm wrong.....
You can read from your NTFS partition just fine, but when you need to write back so Windows can read it, you mount a USB driver and write to that instead. OK, that is good and should work. What I don't get is this:
Quote:
Do you mean you are capable to leave them as read and write also?????because I left them as read and write but I could not write to the contents of the partition!!!!!!
I'm taking this to mean that you have your NTFS partition set to read/write but still can't write. If this is what you mean, then this is not a bad thing. Like I said in an earlier post, I personally don't believe that Linux can safely write to NTFS partitions. It is possible that you don't have the proper drivers compilied into your kernel so even if you can set the NTFS partition to write, you may not have the software in place to actually do so.
but I leave them as read-only for the reasons stated in the quote. If I need to write to XP, I actually mount a USB drive (which is VFAT, not NTFS) and write to that instead of NTFS
I understood from what you had said above, that there are 2 options: read only(ro), ,,,,,,, read and write (rw).
Now my query: why didn't you leave it as (read and write), instead of read-only?Is there any difference or affect?
Second , could you please look to this URL about NTFS, and give me your opinion, specially look under Dual-Boot Setup, step 6
Man, I have got to start drinking coffee again. Sorry zillah, I spaced on my last reply.
Functionally, there really is no difference between read only and read-write other than the brutally obvious that you can't write to a read only drive. If your NTFS partition is read-write, you don't need to change it to read only. I keep it read only so that I don't do something stupid like try to write to it accidentally and screw up my NTFS partition, however that is a personal preference, not a performance-based decision.
As for the link you gave, it sounds OK, but I don't dual boot that way, so I have no practical experience. I use LILO as my boot loader and I have it happily residing in the MBR, which the author of that link is trying to avoid. I actually have no idea why he is since both LILO and GRUB can be used in the MBR without a problem. It is somewhat risky installing LILO/BRUB on the MBR, and you may end up having to re-install Windows, but I personally think the danger is low. By the way, I dual boot Slackware with Windows XP.
At least you have to remember me and send some electronic coffee , we can name it e-coffee.hhhhh
Quote:
As for the link you gave, it sounds OK, but I don't dual boot that way, so I have no practical experience. I use LILO as my boot loader and I have it happily residing in the MBR, which the author of that link is trying to avoid. I actually have no idea why he is since both LILO and GRUB can be used in the MBR without a problem. It is somewhat risky installing LILO/BRUB on the MBR, and you may end up having to re-install Windows, but I personally think the danger is low. By the way, I dual boot Slackware with Windows XP.
Do you agree with the author, that if we have not install LILO or GRUB on the MBR , it will work?
I tried that myself , I installed bootloader (GRUB) in the fist sector of boot partition, after completion there were no sign of Linux at all!!!!!!, there was only my windows OS, because I had dual OS!!!!!!!!!!!.
and could you please look at this (last reply), he was experiencing same my problem :
Do you agree with the author, that if we have not install LILO or GRUB on the MBR , it will work?
I'm going to plead ignorance on this question. Like I said, I have no problem dual booting with LILO on the MBR. Both Linux and Windows seems happy with it.
Quote:
I installed bootloader (GRUB) in the fist sector of boot partition, after completion there were no sign of Linux at all!!!!!!,
Well, I think this is to be expected. When you boot a computer, it always uses the boot loader on the MBR. If you installed GRUB to the first sector of /boot, and didn't modify the Windows boot loader (which is what that previous website you found was about) then the Windows boot loader has absolutely no idea there is anything besides Windows on the computer.
So if you want to dual boot, You either have to use the Windows boot loader or GRUB/LILO.. For the former you'll need to follow the instructions on the site you pointed out. If you want to use GRUB. jump in and put GRUB on your MBR. There should be lots of examples here at LQ on how to configure GRUB to dual boot with Windows.
I just realized now that the previous site is : How to modify the NT bootloader (boot.ini),in order to include Linux.
Before I read your hint
Quote:
So if you want to dual boot, You either have to use the Windows boot loader or GRUB/LILO.. For the former you'll need to follow the instructions on the site you pointed out
I thought step 6 of that site was trying to modify the NTFS partition to be readable by Linux!!!!but actually is not, because he was trying to modify NTFS partition to include his linux bootloader.
Another issue that I experienced always,,,if I have more than one operating system on my machine on different partitions,,, and when I tried to use Magic Partition to check partitions for error , it tells me there is an error on your partition (not all partition, only one of them), have you faced same thing? Is this because I have more than one operating system?Is this common problem?[
To be honest, I don't really know. I used Partition Magic to set up my partitions originally and then I never used it on that machine again. I guess I've never worried about checking for errors on the partitions themselves.
If you want help with that question, I'd start a new thread
I think it is good idea, because I believed that the problem it happen when we have more than one operating system on PC, etc XP and Linux or XP and Unix.
VERY new to Linux here. I have a Dell 8600 with the 1450 wireless card. I tried to download ndiswrapper and install it, but I have no idea how to do this. Do I save it to somewhere and then run it or run it automatically (with Ark?) I also don't know how to follow some of the instructions they give for running ndiswrapper--the prerequisites: http://ndiswrapper.sourceforge.net/w...p/Installation
1) I don't know how to make sure the source is installed or to install it--I have Mandrake 2.6.8.1-8mdksmp (?)
2) I tried to make the link using:
ln -s /usr/src/linux-<2.6.8.1-8mdksmp> /lib/modules/<2.6.8.1-8mdksmp>/build
and I got the reply:
bash: /lib/modules/: Is a directory
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.