USB-Mouse not working in Slacko 6.3 after HD install

[bigpup]

I continued with step 4 (Scan...) => no wireless networks were found.

As I understand.
This step only searches for wireless signals in the area.
If the wifi adapter is working. It should find them if there are any.
Encryption (wpa, wep, etc...) comes into play when actually trying to setup a connection with one of the signals.
Probably need a better driver.

[rimatheou]

Could you post the output of the following command when running Slacko?

readlink /sys/class/net/wlan0/device/driver

When I run this command in Slacko5.6, I have no output.

[rcrsn51]

@rimatheou: When you originally did the hard drive install, did you also copy the zdrv.sfs file? Newer Puppies have it - older ones don't.

It contains driver files that may be needed to make your mouse work.

[rimatheou]

@ rcrsn51
When booting slacko6.3.2 from USB, X failed to start after configuration of xorgwizard.
Choosing vesa, the system hangs up,
choosing modesetting and Nothing - Let Xorg guess it:

Code: Select all

Fatal server error: no screens found(EE)

I also removed the zdrv-sfs-file and booted live, but I had the same result of X.

The same procedure with Slacko6.3.0.
I made the live-usb-drive your way described here http://www.murga-linux.com/puppy/viewtopic.php?t=54566
I think I had no problems with X when I transfered the .iso completely to the usb drive with dd.
When I boot tahr6.0.6 from usb I don't have any window manager. I only see the task menu bar.
Unicorn6.0 is working fine from USB.
But booting from HD and having it installed with the zdrv-file, the mouse is NOT working. It's also not possible to make a setup.
Slacko5.7 doesn't have any zdrv-file.

[greengeek]

Hi Rimatheou, all of the information I can find states that your inbuilt wifi adapter does not have a Linux driver that is capable of supporting WPA.

That wifi interface has a windows driver that supports WPA - but not a suitable Linux driver. (the non-usb versions of that adapter do have Linux drivers that seem to support WPA to some extent but this does not help you).

I think your choices are as follows:
- Change your routers security protocol to WEP or open (bad idea)
- Fit a new wifi adapter (either usb or pcmcia) that supports WPA
- Try loading the windows driver to your current inbuilt adapter. I think this is what people call "ndiswrapper" method. Sorry I do not know how to do this. Hopefully someone else will have some idea if/how it is possible for you.

[rimatheou]

I don't know if it helps, but booting Lubuntu 17.10 I get this message:

Code: Select all

prism2_usb 2-2:1.0 (unnamed net_device) (uninitialized() failed on two attempts, results -5 and -5 asus_laptop: Error calling CWAP(1)
prism2_usb 2-2:1.0 (unnamed net_device) (uninitialized): hfa384x_drvr_start() failed,result=-5

Edit: This is a JVC laptop.

[rimatheou]

I get this booting Bhodi Linux:

Code: Select all

asus_laptop: Error calling CWAP(1)compatible bus not detected, module not inserted.
 

and

Code: Select all

usb 2-2: firmware: failed to load prism2_ru.fw (-2)t detected, module not inserted.

[greengeek]

Both of those error messages look like failed attempts to get the wifi interface to establish WPA capability. The firmware has to be WPA compatible and the driver module has to be WPA compatible too.

It looks as if neither Bodhi nor Lubuntu could find the magic spot to initialise WPA abilities.

Whatever the Windows guys did to establish WPA in this wifi device (and you said it works fine on XP) - the Linux guys could not achieve it and as far as I can see looking at lots of websites the Linux developers just gave up on trying to make it work.

This is sad because the non-usb versions of the prism2 interface work fine under Linux. But you are stuck with the usb version.

Probably the only way this might be able to work is if you can force Puppy to use ndiswrapper to load the Windows driver.

But who can help with info for using ndiswrapper??

I will post any links I can find. Here is one interesting one from tempestuous:
http://www.murga-linux.com/puppy/viewto ... 774#145774

Here is a quote from the wikka:http://puppylinux.org/wikka/HowToWifiFromCommand

...Puppy's Network Wizard is one of the best in the business. It supports all currently available Linux wifi drivers including the unconventional linux-wlan-ng (prism2) drivers, plus ndiswrapper. ....For wifi chipsets not supported by a native Linux driver, Puppy also includes ndiswrapper, which will "wrap" a Windows driver. Obviously, you must supply the Windows driver files.

ndiswrapper is a workaround solution, but sometimes it's the ONLY solution.

Also - this page looks very helpful: http://www.puppylinuxforum.org/thread-596.html

(It is probably going to be necessary to manually unload any other prism2usb module that tries to load itself to your wifi interface during boot. Or else blacklist it (I think you can only blacklist after creating a savefile but I really don't know for sure)
.

[rimatheou]

Maybe this is the solution: https://delysid.org/jvcmp-xp7250de.html

The built-in wireless LAN card of the xp7250 is connected internally via USB, and it is a Prism2.5 chipset based adaptor. This card is currently only supported by the Linux-wlan-ng Project, and not by the standard kernel yet. You need to download one of the latest development snapshots (I use 0.2.1pre20), and build/install it. The latest version of linux-wlan-ng in Debian does currently not yet support this USB card variant, so you will need to compile from sources.

Edit:

I successfully installed linux-wlan-ng_0.2.9+dfsg-4_i386.deb (https://ubuntu.pkgs.org/12.04/ubuntu-un ... 6.deb.html). We will see...

[rimatheou]

... no wireless networks detected hmm...

[matchpoint]

Rimatheou, you're attempting to run this using which Puppy?

[rimatheou]

Hi Matchpoint,

I'm using Lupu 528.

[matchpoint]

So we're on the same page, "uname -r" say your kernel version is what?

[rimatheou]

Edit: deleted. I made a mistake

[rimatheou]

Kernel release: 2.6.33.2

[matchpoint]

You down for a quick experiment?

Open a terminal and check that "which ndiswrapper" returns a location. Yes or no?

[rimatheou]

Code: Select all

# which ndiswrapper
/usr/sbin/ndiswrapper

[matchpoint]

Download, extract, then open win32 with ROX and right click + Window + Terminal Here. Install it with:

Code: Select all

ndiswrapper -i MN510.inf

Check your install:

Code: Select all

ndiswrapper -l

Should produce either a "driver present" or "device present" response.

Are we there?

[rimatheou]

Thanks for your help.

Code: Select all

sh-4.1# pwd
/mnt/sdb1/win32
sh-4.1# ndiswrapper -i MN510.inf
installing mn510 ...
sh-4.1# ndiswrapper -l
mn510 : driver installed
	device (04F1:3009) present (alternate driver: prism2_usb)

and

Code: Select all

#modprobe -r prism2_usb

Now I have this Interface in Simple Network Setup

Interface: wlan0
Type: Wireless
Driver: ndiswrapper
Bus: usb
Description: MS Windows driver mn510

BUT, unfortunately, after scanning there are no wireless networks detected.

[matchpoint]

Run "ndiswrapper –m" followed by "modprobe -a" to complete the process.

Then make sure your carrier device is broadcasting and rescan. We have your network?

That my card lacks a Win file to test, confirm whether "modprobe ndiswrapper" throws a FATAL reply.

With the above, for the moment covered, run a quick "dmesg" dump to see where we stand. You can paste it here.