(old)Puppy Linux Discussion Forum

Hi JB,

Thanks for taking the time to send the output, unfortunately I've been a bit clueless, it seems that the commands that ask the drive to eject and close don't have errors reported, even if there were errors reported. I'm sorry, my bad but it was interesting having a look through all the partition node layout on your hda that you have, I take it that they were all detected ok?
I have had a few ideas about making error reporting easier, and I do think that needs to happen considering the number of oddities that have come up so far.
I have recently been using a proram on Solaris called 'truss' its very useful for debugging and I'm trying to think of a way to make that level of tracing occur in MUT2 server, and then be reported somehow...

Jesse

Hello; I have tried to try MUT2 but without success. I downloaded the file and expanded it into a directory of its own. The only thing that happens when I click on mut2.tcl is a vi window. See the screenshot,

Have I missed a step?

I'm keen to try it out as MUT1 had a problem which made me one of the minority that preferred pmount. My laptop has a built-in slot for SD memory cards, but MUT never ever detected it whereas pmount always did (except in early Dingo alphas).

I'm using muppy008 which is MU's build of puppy 3.01.

Nick

Hi Nick,

Oh yes, there is one extra one-off step you need to do.
Right click on the mut2.tcl file in rox, on the menu "File 'mut2.tcl'" -> "Set Run Action", it will open up a window, where it says "Enter a shell command:" type in the word 'wish' so that it looks like:
wish "$@"
Then click "use command", and its all set up.
Wish is the "WIndow SHell" interpreter for tcl script files.

Jesse

Jesse wrote:Hi Nick,

Oh yes, there is one extra one-off step you need to do.
Right click on the mut2.tcl file in rox, on the menu "File 'mut2.tcl'" -> "Set Run Action", it will open up a window, where it says "Enter a shell command:" type in the word 'wish' so that it looks like:
wish "$@"
Then click "use command", and its all set up.
Wish is the "WIndow SHell" interpreter for tcl script files.

Jesse

Thanks Jesse.

Well that made a difference, but it's not yet "working" as the window comes up empty. Clicking on Rescan brings up another little dialogue box saying "Restart MUT daemon.....". See screenshot.

Thanks.

Later Addition:

Following the advice from an earlier post I have tried it from the command line with "interesting" results.
ended with :- (see mut.log1 attached for the full file) and got into a loop following the hardware scan. See mut.log2 attached for the relevant stuff.

I hope this helps. And thanks.

Nick

Sorry if I'm missing something, I admit I didn't read all of the last couple of pages, just searched them for relevant terms.

I believe there is an issue with the server under Dingo 395. I'm running in one terminal, and in another produces correct out out from the ./mut, but produces a segfault from the server. I'm attaching a text file containing it's full output.

I believe the lines from dmesg are the only relevant ones. Hard to tell, I ran it multiple times before checking
The same info is in /var/log/messages.

I've got an Asus m/b with a sata II hdd (two partions; ntfs and ext3) (I think it's on secondary master)
I do have a floppy disk, but I'm not sure if it works.
1 optical drive, a dvd on the primary IDE slave

Both the DVD and HDD work fine, so I don't think the hardware / puppy core are to blame.

Hope this is helpful!
Everitt
[/code]

Hi nic2109 & Everitt,

Thanks for the logs, the reason that MUT2 is not showing a hardware list on Dingo, is that the background server is crashing.
From Everitts log:

1203141345.887: DEBUG: TH080F6830 read cmd stat
1203141345.887: DEBUG: TH080F6830 COMMANDS:for sdb
1203141345.887: ERROR: TH080F6830 received SIGSEGV handler
1203141345.887: ERROR: TH080F6830 Unable to free ptr 0X80F97F8 as its not in the list. lib/backtrace.c:64
1203141345.887: ERROR: TH080F6830 Signal 11, Backtrace: [0x8048225][0x8056b49][0x8056bd9][0xffffe420][0x80562e7][0x805662a][0x8056a85][0x804995e][0x804aa6f][0x80689ea][0x8048131]
1203141345.887: BEGINEND: TH080F6830

I quickly tried to use Dingo edition 395, but at boot time with pfix=ram it compained that it could not find pup_395.sfs.
I had a quick look at Dingo from its command line shell and it is certainly using the new /dev/sd nodes for IDE drives, so that is quite a restructure, this must be what is triggering the bug in MUT2.
Also the mut client is not realising that the server connection is being dropped at an inappropriate moment, so this is another bug too.
You guys are great bug spotters! I'll fix these issues up at some point soon, I'm off to watch the motorcycle racing in Paeroa today, there might be some time tonight when I get back to fix up the bugs you spotted.

Jesse

I've posted some updates that I managed to get done this weekend.
Some tweaks to cd drive ioctl (commands) useage.
Added in swapon/swapoff.
http://www.murga-linux.com/puppy/viewtopic.php?t=26336

Has anyone out there that has an internal SD card (non-USB variety) found it accessible via MUT2? I don't have one to try with. MUT2 doesn't load the drivers for it at this stage, you'll have to do that manually.

Jesse

Hi Wolf Pup,

Theres were a few cd-control command doubleups that weren't needed that I've removed in latest edition.
can you please check to see if audio pauses are fixed with mut2_1.0.0.1079?

Thanks,
Jesse

Jesse,

I tested your latest MUT (mut2_1.0.0.1079), and am happy to report the CD/DVD eject and close now work. One thing though, it seems to "double" the name of the drive (see pic below). The text runs over the ReScan button.

JB

Hi JB,

That is odd.
Although theres a bit more data in the middle.

I figured it out. The revision ID is 8 bytes for your drive, and linux defines the revision right before the model.

struct hd_driveid {
...
unsigned char fw_rev[8]; /* 0 = not_specified */
unsigned char model[40]; /* 0 = not_specified */
...
}

And that way there is no nul string terminator to stop the string copy.
They probably did that so that all 8 bytes could be used for revision, and programs calling it, like mut, would be unlikely to crash with the apparently longer string.
I've fixed up mut, I'll post another revision in a day or so.
Jesse

Hi Jesse,

Jesse wrote:Hi Sit Heel Speak,...
..."./mut mutclient" ...
..."./mut mutclient --debug" ...
..."./mut mutclient --debug --foreground --nothreads --nofork"...

The latest (mut2_1.0.0.1079) is throwing these errors in
./mut mutclient --debug. sda is a vintage-1998 2GB Seagate SCSI drive through an old Adaptec 2940UW PCI adapter, allotted as just one reiserfs partition:

1203438987.998: DEBUG: THB5FC3B90 scan_drive_node: sda
1203438987.998: BEGINEND: THB5FC3B90 scan drives sda 8:0
1203438987.999: DEBUG: THB5FC3B90 ensure_dev_node_exists on /dev/sda 8 0
1203438987.999: ERROR: THB5FC3B90 failed to get drive info sda

About 600 lines further down, its last gasp is:

1203438988.244: VERBOSE: TH080F6830 got 1 socks need attention
1203438988.244: DEBUG: TH080F6830 read cmd stat
1203438988.244: DEBUG: TH080F6830 read: <hw_list>
1203438988.244: DEBUG: TH080F6830 reading a line
1203438988.244: ERROR: TH080F6830 received SIGSEGV handler
1203438988.244: ERROR: TH080F6830 Unable to free ptr 0X80FCD48 as its not in the list. lib/backtrace.c:64
1203438988.244: ERROR: TH080F6830 Signal 11, Backtrace: [0x8048225][0x8057191][0x8057221][0xffffe420][0x805692f][0x8056c72][0x8057084][0x80570ba][0x8055277][0x8048ab3][0x8049e6a][0x804aaa3][0x806901a][0x8048131]
1203438988.244: BEGINEND: TH080F6830
1203438988.254: DEBUG: TH080F6830 finished reading <hw_list>
1203438988.254: DEBUG: TH080F6830 hw ctx got.
1203438988.254: BEGINEND: TH080F6830
1203438988.254: ERROR: TH080F6830 DriveContext no pointer? meaning no drives?
1203438988.254: INFO: TH080F6830 main exit code:0
#

I can send you the entire debug output, if you or someone will clue me in on how to enlarge the xterm/rxvt scrollback buffer. Simply piping to debug.txt doesn't work, I copied-and-pasted from the scrollback. If memory serves, at the time I originally set this Puppy up I enlarged it, but have forgotten how...

HTH, SHS

I've noticed another quirk of Puppy 4's new treatment of hdxn partitions as sdxn: Sabayon Gentoo 1.1 PE, which also uses only sdxn, puts the SCSI drive at the top of the chain as sda. Dingo puts it at the bottom, on my system sdd. I don't know whether this is liable to get us into trouble or not.

(the above debug listing is from Puppy 2.17-1, wherein the scsi drive is sda)

Sit Heel Speak wrote:Hi Jesse,

Jesse wrote:Hi Sit Heel Speak,...
..."./mut mutclient" ...
..."./mut mutclient --debug" ...
..."./mut mutclient --debug --foreground --nothreads --nofork"...

Simply piping to debug.txt doesn't work,....

Hi; I found that this worked for me. In other words use > rather than |.

Hope that helps.

Hi SHS,

Thats interesting.
The crash you reported has only been reported on Dingo editions so far. But for you it is happening on 2.17-1.
The only thing that is common with your system and the Dingo editions (that I am aware of) is that there is a scsi disk present.
So perhaps the bug in mut2 is related to scsi disk processing.
Putting Puppy edition aside, the crash bug seems to always happen when processing a scsi disk.
I'm not sure how to test that right at the moment, I'll think about it a little while maybe it'll come to me.

Jesse

Hello,

I've posted a new update. 1.0.0.1109
Some tweaks to cd drive ioctl (commands) useage.
gui window position is saved/restored
Cd disk size added.
Fix hard disk fw revision (JB4x4 bug)
http://www.murga-linux.com/puppy/viewtopic.php?t=26336

All the cdrom controls are finally all working on my PC, be sure to let me know if you have any quirks.

Jesse

Hello,

Ahem! I don't know how kosher this is, but here is mut looking just like pmount (left), running next to pmount (right), all in Dingo alpha 6, running on another computer I have that usually only gets to play DVDs.
This is mut2_1.0.0.1130, minor hacked pmount included.
The Pmount script is different!! please don't install it over your existing Pmount script, unless you make a backup etc... You'll need to put the mut file next to it if you do install it.
This should save the issues of installing tcl/tk for those Dingo testers.

SCSI disks work with this edition of mut2.
Floppy disks are still rattling about with 1130.

Jesse

the mutclient frontend UI wiak idea rip

Hi mcewanw,
Don't write off your idea already, pmount doesn't have eject buttons for the CDs, its doesn't have everything, neither does mut2s tcl/tk gui. If you check through the history of the two, there are elements of each that different people adore, perhaps there is a better soloution to gui out there that you can make happen?
Jesse

Jesse wrote:Hi Wolf Pup,

Theres were a few cd-control command doubleups that weren't needed that I've removed in latest edition.
can you please check to see if audio pauses are fixed with mut2_1.0.0.1079?

Thanks,
Jesse

mut2_1.0.0.1130 does not freeze up puppy anymore, but when play is clicked in MUT2, there is no music played.

I was getting the same errors as SHS but latest MUT2 (1.0.0.1130) working with LHP215.
Rebooted with LHP301 and working as well, except sda,b,c,d are now sde,f,g,h. Minor problem, as this means the 3 series is now usable for me.
And Pmount is detecting all drives for the first time. These are scsi2/scsi3 drives.

LHP215
drive|0|0|sda|sda|8|0|0|0|disk|BB00911CA0|3B07|COMPAQ|sym53c8xx|scsi|scsi|||
LHP301
drive|0|0|sde|sde|8|64|0|0|disk|BB00911CA0|3B07|COMPAQ|sym53c8xx|scsi|scsi|||