Puppy Linux Discussion Forum

rerwin · Joined: 24 Aug 2005 Posts: 1318 Location: Maine, USA

To the first two downloaders of the delta 5-to-6 package posted here: http://www.murga-linux.com/puppy/viewtopic.php?p=408355#408355

Please re-download the package, uninstall the previous package, and reinstall the newer one. This will clean out now-obsolete udev rules files that might interfere with usb-wireless-modem mode switching.
Richard

rerwin · Joined: 24 Aug 2005 Posts: 1318 Location: Maine, USA

Barry,
Thanks for taking my latest modem update. In response to your statement that you excluded the usb_modeswitch binary, which is inside the modem-fix package, I have attached a separate package, usb-modeswitch-1.1.1.pet, to the message containing those latest updates.
http://www.murga-linux.com/puppy/viewtopic.php?p=388235#388235

The fix-pack copy is the binary supplied with the source package, whereas the separate version was complied in puppy. Although the sizes differ (32K vs. 36K), the separate (36K) one seems to work as well as the other.

Keep in mind that I can test only with an ordinary flash drive, so cannot verify that mode switching still works. And I have seen no feedback either way! Apparently we have to build the changes into something and let users stumble into any bugs. I prefer to test as thoroughly as possible beforehand, but must rely on those with the modems to report their experiences with the new version of usb_modeswitch.

Anyway, without the binary, mode switching will fail, because the old (1.0.2) version does not handle the new configuration database that improves automated detection -- and won't have the old rules to work with.

Users who have already installed the two packages need not install the new one, but no harm would be done if the "1.1.1" package replaces the other version.

BTW: A version 1.1.2 is being worked on by the developer. But it seems to be taking a while to get released. I will provide it and related updates soon after they are released.

Another BTW: The usb_modeswitch product includes a script written in tcl, which standard puppies do not support. I have replicated that script with a bash script. However, if tcl is installed (find "tcl . . ." in package installer) the tcl script will be used instead. That provides a workaround if you encounter a problem with the bash imitation.
Richard

mama21mama · Posted: Tue 20 Apr 2010, 14:32 Post subject: kernel/drivers error

Reaperz · Guest

Any one ever get this message?

"Intel chipset detected. However, 915resolution was unable to determine the chip set type."

After running the Everest utility in Windows, this is what it found for the chipset:
North Bridge - Intel Whitney i810
South Bridge - Intel 82801AA

mama21mama

always receive the message.

:s

PANZERKOPF · Joined: 16 Dec 2009 Posts: 250 Location: Earth

PANZERKOPF · Joined: 16 Dec 2009 Posts: 250 Location: Earth

Yet one bug in /etc/rc.d/rc.update script at line 235:
xmesssage "Dependencies may be missing..................etc..."
____^^^ xmessage with 3 "s"-es

BarryK · Posted: Fri 14 May 2010, 21:27 Post subject:

rerwin · Joined: 24 Aug 2005 Posts: 1318 Location: Maine, USA

I have now added a supplemental package (modem_ti_qc_ipwi_updates-6.1.pet) in an attempt to support all of the modems (actually, their driver modules) using the ttyUSBn device name that I know of. If you know I have missed one, please tell me. The dotpet is with the others that upgrade modem support, on page 16, here: http://www.murga-linux.com/puppy/viewtopic.php?p=388235#388235

The support for the IPWireless PCMCIA modems has been using the wrong device name, but I have corrected that, to ttyIPWp0, etc.

I need the hear from anyone trying those modem types with pupdial, so I can know whether further attention is needed to make them work. Thanks for whatever help you can provide.
Richard

scsijon · Last edited by scsijon on Sat 05 Jun 2010, 21:55; edited 1 time in total

Just had a problem with a full install 4.3.1

The usb power has turned itself off after a crash (brownout)
fsck came up ok except for the usual blocks errors

you start the pc, it's all ok
boot into the one partition, mouse light goes off, usb probing runs and it just stops at the <prompt> #
I can manually start xwin ok and with the direct kbd/mouse all works

shutdown and reboot
it all starts again (like in a loop)

any sugestions folks before I blow it all away

thanks
scsijon

topic : http://www.murga-linux.com/puppy/viewtopic.php?p=260963#260963
seems to relate

Pizzasgood · Posted: Sun 23 May 2010, 18:17 Post subject:

Have you tried removing the flag file in /tmp? IIRC it is named /tmp/bootcnt.txt.

scsijon · Posted: Sun 23 May 2010, 21:55 Post subject:

?if your talking to me pizzasgood, then no, and it's a zero length file created when I just booted up, will give it a go though.

i've just found I can have a full and frugal install on the one partition and am using that to run with (2 grub entries though)

thanks
scsijon

PANZERKOPF · Joined: 16 Dec 2009 Posts: 250 Location: Earth

Yet one ounce about rc.update :
There are string (in checking procedure) which calls "/usr/local/petget/findinstalledpkgs.sh"
Puppy 4.3.1 hasn't such a file.
Also the xmessage cannot work (even after correcting), says "cannot open display 0:0". A possible reason of that behaviour is chrooted environment, under which this script is running.

scsijon · Posted: Fri 28 May 2010, 05:05 Post subject: