my problemFATAL: could not load /lib/modules/2.6.30.5/modules.dep: no such file or directory.
Puppy 4.3.1 -- bug reports and suggestions
Re: modem_fix_pack_delta_5_to_6.pet
To the first two downloaders of the delta 5-to-6 package posted here: http://www.murga-linux.com/puppy/viewto ... 355#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
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
Separate package for usb_modeswitch binary posted
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/viewto ... 235#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
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/viewto ... 235#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
kernel/drivers error
Apr 20 14:52:28 (none) daemon.notice modprobe: FATAL: Error inserting lp (/lib/modules/2.6.30.5/kernel/drivers/char/lp.ko): Unknown symbol in module, or unknown parameter (see dmesg)
Apr 20 14:52:28 (none) daemon.notice modprobe: WARNING: Could not open '/lib/modules/2.6.30.5/initrd/kernel/drivers/parport/parport.ko': No such file or directory
Apr 20 14:52:28 (none) daemon.notice modprobe: FATAL: Error inserting lp (/lib/modules/2.6.30.5/kernel/drivers/char/lp.ko): Unknown symbol in module, or unknown parameter (see dmesg)
paste
-
- Posts: 282
- Joined: Wed 16 Dec 2009, 21:38
- Location: Earth
Possibly You have an incorrect "modules.dep" file. Run "depmod".mama21mama wrote:my problemFATAL: could not load /lib/modules/2.6.30.5/modules.dep: no such file or directory.
If screen resolution is correct, ignore this message or delete "/etc/resolutionfix"Reaperz wrote: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
file.
SUUM CUIQUE.
-
- Posts: 282
- Joined: Wed 16 Dec 2009, 21:38
- Location: Earth
Modem support for Qualcom, Texas Instrument, and IPwireless
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/viewto ... 235#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
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
usb power turned off??? and goes to <prompt>
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/viewto ... 963#260963
seems to relate
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/viewto ... 963#260963
seems to relate
Last edited by scsijon on Sun 06 Jun 2010, 01:55, edited 1 time in total.
- Pizzasgood
- Posts: 6183
- Joined: Wed 04 May 2005, 20:28
- Location: Knoxville, TN, USA
-
- Posts: 282
- Joined: Wed 16 Dec 2009, 21:38
- 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.
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.
SUUM CUIQUE.
that didn't work, eventually backed up all of root, had a list of what I had added (each machine and partition I have has their own record) so reformatted. I had to change & format to ext3 and back to ext2 for it to let me use the partition so something must have corrupted somewhere in the partition settings or the partition itself.scsijon wrote:?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.
Reinstalled from scratch and everything came ok, copied root back, all is ok (so far).
scsijon
How do you delete a network interface?
I have a network interface that has been treated a couple of different ways by the Network Wizard.
The Network Wizard on Puppy 4.3.1 identifies the interface as
pci: D-Link System DFE-690TXD CardBus PC Card.
Looking at TuxMobil I can see that I'm going to be limited to systems that use the 2.4 kernel.
When the interface was treated as eth1 it works.
When the interface was treated as wlan0 using ndiswrapper, it does not work.
How can I make the network wizard forget about the wlan0 alternative, and go back to the eth1 alternative? (I don't know what I did that made it switch.)
Added June 2, 2010: Somehow the interface reverted to eth1 again, and now I have network connectivity again. It would still be nice to know what made the interface change and then change back.
The Network Wizard on Puppy 4.3.1 identifies the interface as
pci: D-Link System DFE-690TXD CardBus PC Card.
Looking at TuxMobil I can see that I'm going to be limited to systems that use the 2.4 kernel.
When the interface was treated as eth1 it works.
When the interface was treated as wlan0 using ndiswrapper, it does not work.
How can I make the network wizard forget about the wlan0 alternative, and go back to the eth1 alternative? (I don't know what I did that made it switch.)
Added June 2, 2010: Somehow the interface reverted to eth1 again, and now I have network connectivity again. It would still be nice to know what made the interface change and then change back.
Last edited by escargo on Thu 03 Jun 2010, 02:00, edited 1 time in total.
startup problem with usb power turned off??? and goes to pro
no, problem back again, (usb power off) and the error seems to be:
waiting for modules to complete loading usb 1 2 3 4 5 6 (etc)
seems likely that something is not loading?
Does anyone know what driver turns on / off the power to the usb?
and
where in what script starts it?
please
scsijon
found another topic relating to the problem
http://www.murga-linux.com/puppy/viewto ... 963#260963
could a dev, when they have some time , have a look please.
waiting for modules to complete loading usb 1 2 3 4 5 6 (etc)
seems likely that something is not loading?
Does anyone know what driver turns on / off the power to the usb?
and
where in what script starts it?
please
scsijon
found another topic relating to the problem
http://www.murga-linux.com/puppy/viewto ... 963#260963
could a dev, when they have some time , have a look please.
Last edited by scsijon on Sun 06 Jun 2010, 01:58, edited 1 time in total.
- abushcrafter
- Posts: 1418
- Joined: Fri 30 Oct 2009, 16:57
- Location: England
- Contact:
-
- Posts: 282
- Joined: Wed 16 Dec 2009, 21:38
- Location: Earth
Not a bug but incorrect working only.
There is a script "gv" in /usr/bin directory which is designed to view the postscript files with epdfview. It converts a ps file into pdf and sends converted file to epdfview via pipe.
The problem is that some converted files are detected by epdfview as encrypted, even they are not encrypted. I don't know a reason of this problem but if we use a temporary file instead of pipe then this problem not occurs.
I attach modified file here.
There is a script "gv" in /usr/bin directory which is designed to view the postscript files with epdfview. It converts a ps file into pdf and sends converted file to epdfview via pipe.
The problem is that some converted files are detected by epdfview as encrypted, even they are not encrypted. I don't know a reason of this problem but if we use a temporary file instead of pipe then this problem not occurs.
I attach modified file here.
- Attachments
-
- gv.gz
- (136 Bytes) Downloaded 1028 times
Last edited by PANZERKOPF on Tue 15 Jun 2010, 19:24, edited 1 time in total.
SUUM CUIQUE.
Dueling symlinks after running Roaring Penguin
Starting Roaring Penguin can lead to "Address Not Found" errors while browsing and the "Too many levels of symbolic links" error message because of the circular link created when Roaring Penguin makes /etc/resolv.conf a symlink to /etc/ppp/resolv.conf, which is already a symlink to /etc/resolv.conf.
Previously I added a post to an existing thread (started by warpinwolf two years ago) which discussed this bug. Perhaps that was not the proper place to post. Since the name of that thread mentioned Dingo it is possible that it was considered ancient history and was overlooked. So I'm adding this post to the 4.3.1 thread to make it clear that the bug still exists in Puppy 4.3.1.
For details and a suggested fix (which is actually a fix previously made by Barry that somehow got lost on the way from Puppy 2 to Puppy 3), see my post at Dingo, PPPOE, No DNS.
Previously I added a post to an existing thread (started by warpinwolf two years ago) which discussed this bug. Perhaps that was not the proper place to post. Since the name of that thread mentioned Dingo it is possible that it was considered ancient history and was overlooked. So I'm adding this post to the 4.3.1 thread to make it clear that the bug still exists in Puppy 4.3.1.
For details and a suggested fix (which is actually a fix previously made by Barry that somehow got lost on the way from Puppy 2 to Puppy 3), see my post at Dingo, PPPOE, No DNS.