Béèm wrote:...
P.S. I know I could use another filemanger, so no need to make the remark.
Why didn't you just let the Video Wizard choose the best driver? For Intel video it would have automatically chosen the 'intel' driver. For for any reason that failed, you could then have tried the 'i810' driver.otropogo wrote:Now for the important problem:
I'm running an Intel Motherboard. I can't find the model number right now, but it uses a 2.5Ghz Celeron cpu and has a 400Mhz FSB and embedded video (I do know it's pre-PCI-Express).
I assumed it would use an Intel video driver, so I told the xorg wizard to try i810, and it responded by removing the Intel driver. After that started a game of musical drivers.
The essential problem - the wizard doesn't know which driver to use, and when trying drivers, can't tell what either the chip or the monitor can handle (the Monitor, admittedly, is a bit difficult, being a converted Sun Microsystems 20" CRT). Puppy 4.3.1's wizard has some difficulties with this combo too, but handles them much better.
Whether using the Intel or the i810 driver, the Wary wizard presents a full complement of resolutions and colour bits, up to 1600x1200x24, and pronounces every one of them "OK for Monitor, OK for video card".
NOT!
So basically, one has to try each combination to find out what will work. The problem then is that, when one combo is aborted with CTL-ALT-BACKSPACE, the wizard removes the driver in use and replaces it with the other one, and you start all over. So you end up going back and forth between the i810 and the Intel driver (oh, there's also a mention at some point of a "newer driver", but I failed to discover how one accesses that one, much less whether it would work).
Eventually, I found a combination that worked under the i810 driver (1280x1024x24), but had to tweak the dsiplay rates downward to 64 Horizontal and 60 refresh (which seems a mite slow - at least I'm pretty sure I get faster rate reports from Puppy 4.3.1).
But the bottom line is, that after all this monkeying, I still don't know whether I'm running the best driver available under Wary. I suspect not.
I noticed that other people have commented about your bad attitude, but I have only just now got around to reading and replying to your posts -- and I see what they mean.otropogo wrote:I burned Wary5 to a multisession CD. As reported in the Pburn thread, I successfully did a complete disk blank with pburn 3.3.1, then burned the iso with burniso2cd, and successfully verified it, before booting up.
When I ended my session by using the shut down option, I got an unfamiliar save screen (blue, instead of the regular grey, IIRC), and selected Save to CD.
That evoked a blue screen with IIRC large black lettering, telling that if the save was delayed unduly, I should make sure the tray was closed and hit enter.
This line repeated several times before I finally hit enter. The line keep rewriting.
Meanwhile, the tray continued closed, and the disk light was blinking furiously.
Finally, I gave up and hit CTL-ALT-DEL, and the display turned black and announced "Puppy is shutting down".
This was followed by the familiar grey save screen, and again I selected "Save to CD", which resulted in a black terminal screen on which I could type.
Obviously, the save function wasn't working (since no prompt for file size appeared), so I did a hard reset.
The disk is no longer bootable.
In restrospect, I'm wondering whether the issue is because the sfs file wasn't written to RAM, and Puppy was unable to read from AND write to the CD (I do have a swap file on one of the hard drives which Puppy 4.3.1 manages to find, but there's in indication Wary noticed it).
Or maybe Wary doesn't know how to write to a CD-RW?
Oh, well, I should be used to this sort of mess by now after all these Puppy years. And I should have known better than to get sucked into using the multisession option just because Flash swears by it.
My guess is that it is ok, udev uses those symlinks to point into /dev, they are only broken from our point of view.technosaurus wrote:I'm not sure if this is a bug report or more likely just acknowledgement of my ignorance of dynamic device setup.
The /dev/.udev/db directory _appears_ to be pre-populated with broken symlinks
I don't know whether they are supposed to be this way but it all still works, as adding a usb flash drive added the appropriate entries:
block:sdb
block:sdb1
usb_device:usbdev2.2
usb:2-1
(all with apparently broken symlinks and a working flash drive)
Not a bug - just a little disconcerting. Now I see further why people complain about udev being finicky.... if only mdev could handle more nuances
That is some time ago... at the time, I did test installations to LS120 and Zip drives, reported on my blog I think.otropogo wrote:Hi Aitch. Barry knows about the LS120 problem or did, because he mentioned way back when having an LS120 drive but no disk for testing. I then mailed him a brand new one, and he acknowledged receipt. But I don't recall seeing any further report on the matter after that.Aitch wrote:I would think a PM/post to Barry K is best, explaining, with links, what you went through [Yes, I remember it well!otropogo wrote:What does it take to get Puppy's doodoo removed?] and results, and current finding/disappointment
http://www.murga-linux.com/puppy/privms ... =post&u=52
http://bkhome.org/blog/
I can only assume it wasn't previously brought to his attention or it's a n other oversight?
Aitch
Yes, I distinctly remember the discussions: after a while I succeeded in getting an installation to an LS120 ( a lot of Compaq machines had these fitted at one time). As I recall, about 30mins to boot a full installation. The advantage of the LS120 was it's massive storage capacity, and all on a 3.5" floppy. I still use my LS120 daily as a convenient storage medium - extremely reliable and the magnetic recording seems to outlast optical ones, as well as flash. I still have a 1.44 FD from 30yrs ago - I check it annually. Kept dry, dark and away from magnetic fields the data remains viable indefinitely.at the time, I did test installations to LS120 and Zip drives
I just tried 8x15B, made this entry in /root/.Xresources and restarted X:don922 wrote:I am using Wary 5.0 Lite on a PII 350 with a new 17" monitor.
I would like to get a 10x20 font to use in Urxvt. Where can I get it and How do I install it?
Wary 5 is supposed to be an "old equipment" Puppy. Old eyes need something better than 7x14; even 9x15B is too small for my eyes.
I don't want to sound like "otro", I can't read the screen in Urxvt -- I am using Sakura, but it uses TTF and I can't find anything that works as well as 10x20. Any suggestions?
Code: Select all
!*font: -misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-*-*
!*font: -misc-fixed-medium-r-normal--13-120-75-75-c-70-*-*
!*font: -misc-fixed-medium-r-normal--14-130-75-75-c-70-*-*
!*font: -misc-fixed-medium-r-normal--15-140-75-75-c-90-*-*
*font: -misc-fixed-bold-r-normal--15-140-75-75-c-90-iso8859-1
Xft.dpi: 78I think that I used the latest jwmconfig PET supplied by the Japanese Puppy developers, as it is supposed to have many bug fixes.don922 wrote:Adding a new launch button to tray causes the screen selector boxes to be removed. Compare graphics below.
I have used these same launch buttons on Puppy 4.12, Puppy 4.00 and Puppy 214X without a problem.
Can this be fixed?
I also have an old laptop - Thinkpad 600 with just 196MB ram and a 2GB swap partition, frugal install.Sage wrote:but would be interested in comments and reports of similar experiences, esp. wrt Wary.
