(old)Puppy Linux Discussion Forum

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.

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.

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.

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.

I have found a fix for modems with the ID 19d2:2000 that should allow them to switch into modem state. I put it into a small package, attached. This should be helpful for aracnachid's Vodafone Vodem Zte K3565z USB modem and Whitesnow's Onda MM515UP modem. To give due credit, I derived this fix from information in the USB ModeSwitch Forum.
Richard

look at http://www.murga-linux.com/puppy/viewtopic.php?t=48019 from patriot
contains a number of video drivers INCLUDING a vesa driver that seems to work properly, no funny screen sizes or shifting right or down.

absolute magic

thanks
scsijon

Not exactly a bug... but I have a old vid card that doesn't work unless I choose VESA, instead of the XORG.

It's an 8MB Matrox G200.

Because I have to use VESA, video playback is unacceptably slow. Before I disabled it, I had better playback with my MoBo's 1MB integrated video chipset...

Reaperz wrote:Not exactly a bug... but I have a old vid card that doesn't work unless I choose VESA, instead of the XORG.
It's an 8MB Matrox G200.
Because I have to use VESA, video playback is unacceptably slow. Before I disabled it, I had better playback with my MoBo's 1MB integrated video chipset...

Try following steps:
1) Check file /usr/X11R7/lib/xorg/modules/drivers/mga_drv.so.
2) Open /etc/X11/xorg.conf file with text editor.
3) Change string Driver "vesa" to Driver "mga" in section "Device".
4) Restart X server.

Subject: filemnt won't mount two files with same base name.

To prevent mounting the same file twice (and the the dangers inherent in doing so), filemnt compares the name of the file with the names of files already mounted. Once upon a time, it appears that filemnt simply compared the entire pathnames (which include the directory names), but because one or more of the directories in the pathname could be symlinks, two different pathnames could lead to the same file. So, at least in Puppy 4.3.1, filemnt was improved to compare only the base name of the file.

That improvement prevented mounting the same file twice, even if one of the directory names was a symlink. So far, this is good.

The bug is that if you happen to have two different files with the same base name, as would be the case if, for instance, you were comparing one custom pup-431.sfs with another. You get something similar to the following xmessage which is quite puzzling because it simply isn't true.

Sorry /mnt/sr0/pup-431.sfs is already mounted and in-use by Puppy

Also, if the filename itself (not a directory name) is a symlink, then filemnt will allow the file to be mounted twice.

So the current test gives both false positives and false negatives.

I am attaching a version of filemnt in which I use the stat utility to uniquely identify a file by its device and inode values. This should eliminate both problems.

I have also expanded the error message that appears when you do try to mount a file that is already mounted. Now it gives not just the pathname of the file you tried to mount, but also the mount point of the mounted file and the pathname that was used when it was mounted.

(Note: I am reporting this in the Puppy 4.3.1 thread because 4.3.1 is the Puppy that I have. The bug could certainly exist in older and newer puppies.)

Wireless modem users:
I have posted an upgrade to modem support, particularly for wireless modems, and need users to try it out and to report any for regressions and or failures to function reasonably.
http://www.murga-linux.com/puppy/viewto ... 074#431074

The new functionality is for complex modem cases. Modems using other than ttyUSB0 have been difficult to make work. In the upgrade, that should be more automated, to get the correct port. The upgrade also addresses the complications of having multiple USB-serial-type devices plugged in, not all of which are modems.

To use the upgrade, be sure that the "modem fix pack 6" dotpet (only), available on page 16 of this thread, is already installed, before installing the four upgrade packages.

The sooner people can verify that the upgrade works and does not mess up anything, the sooner it can be integrated into Woof. Thank you for any help you can provide with testing.
Richard


Additional item: I have re-uploaded the "modem_fix_to_431" package on page 16 of this thread to correct a Conexant modem problem that may prevent detection of a USB modem if there is a built-in Conexant. The download count when I uploaded was 199, so later downloads of it contain the fix. Re-download and re-install it if you have a Conexant (DGC, HCF, HSF) modem interfering with detection of a USB modem.
Richard

The connect icon on the desktop opens PPPOE instead of a more general program with several buttons for different connection types that it used to open before (I used the LAN-button for wireless). Even if I restart the problem remains. I don't think it's easy to reproduce this on another computer -- maybe it changed because of lack of RAM. How can I change it back to the way it was originally? Which program was used originally? How do I change which program a desktop icon starts?

Luckily I can still start wireless by using Pwireless-0.8.4 from the Menu, but it doesn't have the same features as the other program.

I use Puppy 4.3.1 with kernel 2.6.25.16 and window manager JWM.

Edit:
I succeeded in solving it by right-clicking and choosing 'Execute the Internet Connection Wizard' and changing Desktop/tray to Internet Connection Wizard. It must have been accidentally changed to PPPoE.

nubc wrote:After messing around for several hours, I have come to the conclusion that Puppy 4.3.1 cannot play back a (downloaded) FLV file, probably because it sees the wrong format, perhaps mistaking flv for mp3, as indicated by assigned icon.

Correct, particularly if you are talking about videos from youtube. It seems that youtube keeps making subtle format changes that place its flv format incompatible with established players. Until mplayer catches up, videos that you download from youtube will play in youtube's flash player but probably not in mplayer. Most flash videos from other sites will probably continue to play okay in mplayer.

There are browser add-ons that will convert to another format, allowing you to save your youtube videos in another format which can then later be played in mplayer. Whether the add-ons will accommodate the latest of youtube's changes is for you to discover.

Subject: filemnt won't mount two files with same base name.

(Note: I am reporting this in the Puppy 4.3.1 thread because 4.3.1 is the Puppy that I have. The bug could certainly exist in older and newer puppies.)

I can confess, that filemnt.gz is working on dpup-005.

I really missed that feature !

While running frugal with a lot `acpitool -s` to suspend to ram I was able to mount the booted /mnt/+mnt+home+dpup005+dpup-005.sfs and the remastered /mnt/+mnt+home+dpup-005-06-xephem+dpup-005.sfs by clicking the icon at rox.

I had to look at /etc/DISTRO_SPECS to believe it !

I am very happy about that !
1000 Thanks, npierce !

Hi,

Usually I'm happy with Puppy 431 on an old Fujitsu Stylistic c500 tablet.
Suspend, touchpad (fpit driver) is working fine.

Nowdays I realised USB mount doesn't work.
It does work few month ago, but now not.

I saw, usb modules are present, dmesg shows sdb device recognised, but
no automount. Even no way to mount manually.

dmesg:

usb 1-1: new full speed USB device using uhci_hcd and address 2
usb 1-1: configuration #1 chosen from 1 choice
scsi2 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
scsi 2:0:0:0: Direct-Access OTi Flash Disk 2.00 PQ: 0 ANSI: 2
usb-storage: device scan complete
ready
sd 2:0:0:0: [sdb] 256000 512-byte hardware sectors: (131 MB/125 MiB)
sd 2:0:0:0: [sdb] Write Protect is off
sd 2:0:0:0: [sdb] Mode Sense: 03 00 00 00
sd 2:0:0:0: [sdb] Assuming drive cache: write through
sd 2:0:0:0: [sdb] Assuming drive cache: write through
sdb: sdb1
sd 2:0:0:0: [sdb] Attached SCSI removable disk

Mount:
# mount /dev/sdb1 /mnt/sdb1
mount: /dev/sdb1: can't read superblock

I tried different pendrives.

Any help is appreciated.
Robert

mount: /dev/sdb1: can't read superblock

fsck

if fsck can't read the superblock also

# dumpe2fs /dev/hdd1
dumpe2fs 1.41.9 (22-Aug-2009)
Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem UUID: 235d2897-72ab-4945-b443-30dc0eeeb3e0
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file
Filesystem flags: signed_directory_hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 404000
Block count: 1614524
Reserved block count: 80726
Free blocks: 1039906
Free inodes: 344866
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 394
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8080
Inode blocks per group: 505
Filesystem created: Sat Jan 1 16:15:12 2011
Last mount time: Thu Jan 13 11:57:19 2011
Last write time: Thu Jan 13 11:57:19 2011
Mount count: 3
Maximum mount count: 36
Last checked: Wed Jan 12 13:25:14 2011
Check interval: 15552000 (6 months)
Next check after: Mon Jul 11 13:25:14 2011
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
Default directory hash: half_md4
Directory Hash Seed: 5cfa5913-9096-4114-836b-7ee7bfaa00bf
Journal backup: inode blocks
Journal size: 128M


Group 0: (Blocks 0-32767)
Primary superblock at 0, Group descriptors at 1-1
Reserved GDT blocks at 2-395
Block bitmap at 396 (+396), Inode bitmap at 397 (+397)
Inode table at 398-902 (+398)
23777 free blocks, 4927 free inodes, 565 directories
Free blocks: 915-6143, 6225-20479, 20482-24575, 29253, 29258-29265, 29313-29316, 32582-32767
Free inodes: 3154-8080
Group 1: (Blocks 32768-65535)
Backup superblock at 32768, Group descriptors at 32769-32769

which should give an average backup superblock

# fsck --help fsck 1.41.9 (22-Aug-2009)
fsck.ext3: invalid option -- h
Usage: fsck.ext3 [-panyrcdfvtDFV] [-b superblock] [-B blocksize]
[-I inode_buffer_blocks] [-P process_inode_size]
[-l|-L bad_blocks_file] [-C fd] [-j external_journal]
[-E extended-options] device

Emergency help:
-p Automatic repair (no questions)
-n Make no changes to the filesystem
-y Assume "yes" to all questions
-c Check for bad blocks and add them to the badblock list
-f Force checking even if filesystem is marked clean
-v Be verbose
-b superblock Use alternative superblock

fsck -b 32768 -n -f -v /dev/DEVICE

What's the default user name and password?
I need this when it is dropped to a terminal login.

SundayForever wrote:Unless I had made some mistake (which I suspect I haven't), Puppy saw that there was another Puppy nearby and mixed things. In the partition in which the folders are located the are an opera and profile folders that were created when I installed Opera in Puppy 4.3. Maybe this confounded the boot process.

If you have been using a previous frugal install and decided to use a 4.3.1 live CD then I expect it would see the older savefile and ask did you wish to upgrade it to 4.3.1.

If you had puppy software on the HDD but outside the savefile then that software is accessible by any puppy. It may be advantageous to install additional browsers this way, so that you need to install only once and it can be used by your other puppies.

photor wrote:What's the default user name and password?
I need this when it is dropped to a terminal login.

Welcome back!

Normally you don't encounter a login. MENU > Utility > Terminal Emulator

Once you get to the terminal, what do you want to do?

Hello,
When transparency enabled (/root/.xinitrc => #composite & transparency kcompmgr -n &), Xlock doesn't show both screen saver picture and text that prompts user to give the password. However I noticed this problem disappears if the option -grabserver is deleted in /usr/local/apps/Xlock/AppRunn lines n°34 et n°143 and in /.config/Xlock/xlockscreenparams...
My question: what is the option -grabserver used for and what kind of other problem(s) may this modification possibly cause?

Thank you!
Best regards.