The xhci driver is a standard kernel module - the only way to update it is to move up to a more recent kernel version (such as Slacko) ...
... but it sounds to me that the xhci driver is not at fault. The driver should have no impact on the read/write status of the drive - I suspect it's more a case of how the NTFS-3G filesystem driver detects the condition of the NTFS filesystem on your drive. In other words, the NTFS-3G driver is possibly "unhappy" about the condition of the filesystem, so mounts it as read-only.

I'm not an expert in this area, so you should consider making a separate post on this subject ...
but a quick thing to try is to connect the drive to a Windows XP computer, then defragment the drive by going to
Start > Programs > Accessories > System Tools > Disk Degfragmenter

Once defragmented, reconnect the drive to Puppy and see if you get a better result.

The xhci driver is a standard kernel module - the only way to update it is to move up to a more recent kernel version (such as Slacko) ...

I wonder then why Slacko 5.3 is unable to detect anything on the USB3 ports?

Quote:

... but it sounds to me that the xhci driver is not at fault. The driver should have no impact on the read/write status of the drive - I suspect it's more a case of how the NTFS-3G filesystem driver detects the condition of the NTFS filesystem on your drive. In other words, the NTFS-3G driver is possibly "unhappy" about the condition of the filesystem, so mounts it as read-only.

Then how to explain the fact that Puppy 5.2.8 has no problem with the drive on the desktop that doesn't have the USB3 driver installed, only on the one that does? Or the fact that Slacko 5.29.6, Windows 7, and Win2K report no problems with the drive? All of these mount the drive as writable every time. OTOH, the system that reports the ntfs-3g problem is inconsistent, and sometimes changes its mind and finds the partition acceptable. Since I boot from CD every time, I conclude the difference stems from the lupusave 2fs file on the USB3 PC.

Quote:

I'm not an expert in this area, so you should consider making a separate post on this subject ...
but a quick thing to try is to connect the drive to a Windows XP computer, then defragment the drive by going to
Start > Programs > Accessories > System Tools > Disk Degfragmenter

Once defragmented, reconnect the drive to Puppy and see if you get a better result.

OK. Any suggestion as to where I should post it and with what subject heading? Most of my past posts on hardware issues have failed to evoke any response from the technical gurus.

As it happens, I don't have a system with XP installed at the moment. But more importantly, I don't want to "swallow a spider to catch the fly..." unless the indications are very persuasive that this is the only solution.

Update: my mistake, the ntfs-3g error DOES occur on the system without the USB3 driver. It's intermittent, and I'd forgotten that. So intermittent that two ntfs drives can be mounted on the same port, and one is mounted normally, the other read only. And the problem can even be resolved sometimes by simply moving the drive from one port to another or even, more rarely, by unmounting, unplugging, and replugging, remounting it in the same place. Most frequently, though, these tricks result in the drive disappearing and failing to reappear without a reboot...

NB: I have discovered since my original post that the problem doesn't occur with Racy 5.2.2.

Unfortunately, I haven't been able to figure out how to install ufraw, rawstudio, or a working copy of xfprot in Racy..._________________otropogo@gmail.com facebook.com/otropogo

Sound is OK in Exprimo 5.X.10.2. But there is no speaker icon on the taskbar nor any sound output in Lupu 5.2.8. I would like to run Lupu 5.2.8 as it seems to give a better battery life than Exprimo 5.X.10.2.

Edit Dec.22,2011
This has now been solved by installing alsa_driver-1.0.24.pet.

Here is the meye webcam driver for the Sony Motion Eye device found in certain Sony VAIO PCG-C1* laptops.
This driver depends on the sony-laptop driver, which in turn depends on the rfkill driver, which was not enabled in the standard 5.1.x-5.2.x Puppy releases. This driver dotpet package provides these additional drivers.
Be aware that the addition of the rfkill driver might break Puppy's existing wifi drivers. If your find that your wifi driver stops working after installing this package, you will need to install my updated rfkill-compatible wifi drivers from earlier in this thread -
http://www.murga-linux.com/puppy/viewtopic.php?p=452093#452093

Also be aware there are several generations of Motion Eye cameras. The only one supported by this driver is device ID 136B:FF01
If in doubt, run this command to check which camera device ID you have -

Code:

lspci -n

INSTRUCTIONS:
After installing this dotpet, reboot. Run the "lsmod" command to check that the meye driver and sony-laptop driver have both automatically loaded. If not, you need to configure Puppy to do so. Go to
Menu > System > BootManager configure bootup > Click here to add a new module:
Add the "meye" module to the right-hand pane, then click "OK".
Now reboot again. Your new driver should be loaded and ready to use. As always, a suitable application such as mplayer must then be used to display the webcam image.

There are some notes in the module .txt asking people to test this module as it is the replacement for the older sonypi module; sonypi works for me and enables the jogdial but I get the above error when loading sony_laptop. I made sure sonypi wasn't loaded before trying to load sony_laptop.

Is there anything further I can do to debug this or should I contact the person maintaining the sony_laptop kernel module?

Initially I suggest you check whether your webcam is actually compatible with the meye driver. Run this command -

Code:

lspci -n

looking for 136b:ff01 If your webcam has a different ID, there's no point going any further.

But if your webcam is compatible, I suggest the first thing to check is the health of your ACPI system. Run this command -

Code:

dmesg

and look at everything relating to ACPI and hardware resource allocation. You might see errors relating to ACPI, and if so, we might be able to fix this by passing boot options to the kernel.

If ACPI looks healthy, some troubleshooting of the sony-laptop module, itself, could help.
First move /etc/modprobe.d/sony-laptop.conf somewhere else (such as /root) because this is the module configuration which I assumed to be correct ("camera=1").

Now try to load the sony-laptop module, experimenting with various parameters:

Code:

modprobe sony-laptop

Code:

modprobe sony-laptop compat=1

Code:

modprobe sony-laptop no_spic=1

Code:

modprobe sony-laptop minor=250 camera=1

If the module loads without reporting errors in any of these instances, you will need to unload it before trying again with other parameters -

I saw back on page 2 of this thread that you had Ralink drivers compiled.

I'm having a hair tearing experience trying to get Ralinks rt61 drivers compiled. Perhaps you know the secret. I have the kernel sources all linked in. Not sure why it won't compile. I have the source files should you need em (just email or PM me).

The rt61 module that comes with Puppy 528 (and earlier) is just not strong enough. In Pup 4 series I had better luck with Ndiswrapper and the windows driver giving me transmission strength control that the linux driver didnt have.

Unfortunately in all Pup 5 series I get horrible unrecoverable crashes when either modules (native or ndiswrapper) don't pick up the WLAN. It might also be a crash in the scan routine. Ndiswrapper is the latest (1.56) in Puppy 528 so I don't want to fight further down that path until I've tested the latest possible native driver.

Its a real shame if it can't work as I'm effectively cornered and may need to spend money on a compatible card - I'm too much of scrooge for that and I don't like the fact that a puppy version upgrade is responsible. (I Love the pup - It shouldn't be his fault).

@Tempestuous
Thankyou for the drivers on page 2 for railink usb wifi adapters.
After much messing around and reboots, my Tenda W322U v2.0 usb adapter works perfectly in dpup exprimo! Will try in others and report back here _________________Download a better Computer Puppy Linux Songaltern8life

I'm having a hair tearing experience trying to get Ralinks rt61 drivers compiled.
...
I have the source files should you need em (just email or PM me).

paulski, I tried to compile the vendor-supplied rt61 driver, and it definitely fails under the 2.6.33.2 kernel.
The source code is quite old, and clearly won't work with recent kernels.

I suggest you persist with the standard rt61pci driver in Lucid - by configuring this driver to disable its internal decryption function. This is a common way to solve "misbehaving" wifi drivers.
Create a new file in Geany, containing this line -

Code:

options rt61pci nohwcrypt=1

and save it as /etc/modprobe.d/rt61pci.conf
Then reboot, and see if your wifi connection is more reliable.

Regarding Broadcom bcm43xx wifi devices
4. If still no success, you must then move on to the proprietary Broadcom wifi driver supplied by forum member piratesmack here -
http://www.murga-linux.com/puppy/viewtopic.php?p=421596#421596
Be aware that this driver competes for an overlapping range of hardware claimed by the ssb driver, so you will need to unload (or blacklist) the ssb driver for the new driver to work. And when you disable the ssb driver, some other devices such as USB interfaces may then be disabled!
.

This version of lupu528 handles my BCM4311 wifi quite differently to any other puppy to date.

It is using the wl driver and is creating eth1 whereas other puppies use b43 and create wlan0.

My problem which I am reporting here is that although I can create successful initial WPA-PSK-TKIP connections with all 3 connection tools - SNS, Network Wizard and Frisbee - none of these connections survive a reboot.

I have tried disabling the SSB module as described in the forum but whatever I do it still appears in the LSMOD list.

I've been able to achieve a connection after a reboot by the following steps:
1. create a profile with Network Wizard
2. put dhcpcd into /etc/rc.d/rc.local and reboot
3. right click the tray icon and disconnect
4. right click the tray icon and connect

after 4. a message box from Network Wizard appears and then a short time after a small green box with borderless success in it.

I've attached to this post in an archive file:
1. lsmod from the standard version of lupu528 which uses the b43 modules
2. lsmod from the initial boot of lupu528-testing after establishing a connection but before pupsave created
3. lsmod after a reboot but before the steps listed above
4. dmesg ditto

One thing I notice but don't know significance of is the appearance of module michael-mic in the list before the reboot but not after the reboot.

and it looks like the broadcom-sta problem reported above is caused by the combination of changes in the lupu528-testing iso rather than the driver that playdayz / rerwin have included from this thread.

The 3.0-series kernel, as featured in recent Puppy versions such as Slacko 5.3.x and Racy, has a new driver called "samsung-laptop" which should be able to manage cpu/fanspeed, wifi & backlight control.

This dotpet will install 2 new drivers: easy_slow_down_manger and samsung-backlight
After installing the dotpet, for CPU/fanspeed control, first load the easy_slow_down_manger driver with this command -

Code:

modprobe easy_slow_down_manager

Now run the following commands, depending on what you want to do:
To turn the laptop to "speed" mode -

If you want to be able to adjust your screen's backlight, you must first modify Puppy's boot code; open /boot/grub/menu.lst in Geany, and on the line that starts with "kernel ..." add a space, then "acpi_backlight=vendor" without the quotation marks.
Now boot up, and load the samsung-backlight driver, with this command -

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum