Puppy Linux Discussion Forum

[starhawk]

@greengeek: glad to help!

@all: Got the resolution fixed -- edited xorg.conf manually -- the "preferred resolution" that the screen reported was 800x600 (as was the actual monitor display res) so changing both of those to 1024x768 and restarting X seems to have worked well.

I have a spare flash drive, and I see there's an Install to USB option in the menus, so I'll do that and make a savefile. Easier than booting pfix=ram and mucking with installing and configuring xorg.

Next challenge: this thing doesn't seem to play audio in pUPnGO -- TBH the only puppy I've found (not that I'm actively looking!) that has the correct driver is Puppy 423. I'll edit my post in a few with the name of that driver (I don't remember but it's in a thread somewhere). Can I copy the driver over from 423, or does it have a different kernel from 412?

EDIT: the driver is "cs4236". I know from experience that there is another driver that will not work called "cs4232" -- it is present in Puppy 420, Akita, and Puplite5. I suspect it's an earlier version of the -36 driver but I can't prove it -- all I know is, it doesn't work.

EDIT2: d'oh! Forgot that this system is far, far too old to boot directly from USB. Oops!

Oh well, good thing I've a copy of Plop Boot Manager!

Er, BTW, goingnuts, your USB flash drive installer doesn't seem to work. I select "sdb" for the install and it pulls up a file-find window with no explanation as to what it's looking for. I think we can call that an oops! I ended up doing a manual frugal install with syslinux. Soon as I get Plop on a floppy, I'll let you know how well it went.

EDIT3: hmm, looks like syslinux hates me the USB drive doesn't boot. Was using rcrsn51's instructions here. (The operative word is "was".) I'm just going to drop down grub4dos like I should've in the first place!

[goingnuts]

greengeek: I will test your wifi script later. I have uploaded a new build of Links-2.7 - static...same place as stated in former post - but with more features enabled. Gmail tested and works.

starhawk: There are cs423x drivers present in pupngo2012 (/lib/modules/2.6.25.16/kernel/sound/ISA/cs423x) - might try to load one of them?
The install to usb works here - try running it from within pupngo - and from a prompt or terminal if that fails too. Not every script in pupngo is portable - but normally works in P412 if every external programs are present...
Edit: The file dialog ask for the path to the iso-file you want to install - and nothing indicates that - Sorry.

[starhawk]

Hmmm... cs-4236 loads BUT doesn't work. cs-4232 loads, doesn't work, AND won't unload. Oops! It doesn't help that cs-4232 gives a segfault error. Looks like there's a missing file -- snd-cs4232-lib.ko is not present. FWIW, cs-4231 fails with a device not found error (as it should).

BTW, aumix typed in a terminal makes the system pause for about a half second and then I get a # prompt. No errors, no mixer -- it just doesn't work. Whoops.

...one other question: what calls Xorg / Xvesa on bootup? Is that part of initrd or something later on?

EDIT: going to have some fun here I'm downloading Puppy 431-k2.6.25.16 -- Puppy 432v3, running on the CPi as a full install, is a derivative of 431 by ttuuuxxx (I think I spelled that right ) and I'm gonna lift alsamixer and the required sound driver out, if they work. Vanilla 431 uses a later kernel, but Barry made some "special" models at the time, this being one with the Puppy 4.1.* kernel.

[goingnuts]

Try "aumix -h"
if in X and you type aumix the gtk interface should popup...
It just does not work the way you expect I think.

/etc/profile starts xwin if /etc/autostartx contains "yes"
If Xvesa or Xorg is started depends on to which X is symlinked.

If snd-cs4232-lib.ko is missing its also missing in P412 - if kernel 2.6.25.16 is used in other puppys and you can find the driver there you should be able to copy over. modprobe snd-cs4232 does not segfault here. Attached static build of strace - might be handy to track what is happening.

[starhawk]

aumix -h posts a help message that I've seen before

aumix does as described.

aumix -q results in aumix: error opening mixer as output.

What is strace and how do I use it?

[technosaurus]

Strace tells you a lot of information that is going on behind the scenes. You can often deduce the cause of an error by examining the last several lines of strace output.
strace command args

[starhawk]

So I'm supposed to copy strace to... what, /usr/bin? and then type strace modprobe snd-cs4232 and it'll tell me where the magic breaks down?

EDIT: formatting fixed

...or can I do it by going to /mnt/sdb1 where the strace bin will be, and typing the bold text above and it will work then?

[starhawk]

OK, got strace figured out. Guess I'm not as dumb as I thought

Looks like it's just a driver-device mismatch -- strace spits out, among plenty of other gobbledegook the string "wrong ioctl for device" or something like that.

I'll try strace on the cs4236 driver in a minute, and edit this post with results.

EDIT: does the same thing in the same places. Looks like a bad driver or something. The proper phrase is "inappropriate ioctl for device".

[starhawk]

OK, screw the audio, not gonna work.

A different point of confusion... how does pUPnGO "know" to call xvesa on bootup, and NOT xorg? Even when the Xorg PET is installed by a run through Woofy, something is missing and it still automatically calls xvesa when it should not. What do I change to fix that? (I see no symlinks to xvesa or xorg within /etc/profile -- or, in fact, anywhere else!)

[goingnuts]

[greengeek]

goingnuts - I've had another look at the wireless manager script, and to my untrained eye it seems to contain the ability to scan for networks, ask for passphrase, build the wpa_supplicant and run dhcpcd - but it doesn't do any of that when I run it - so I'm wondering if there are some compulsory prerequisites that I am failing to fulfil?
When I run the wireless manager I get a dialog on screen with 4 options - close, connect, disconnect, or change boot options. If I choose connect it says "wireless adapter found, press ok to continue" but if I press ok it just goes round in a loop. (should there be another entry in that dialog, for "scan for networks" maybe?). Im perfectly happy being able to connect manually with Tempestuous' cli instructions but if there is some easy way to have the manager functional it would be a significant asset.

Also - thanks for the links pet - it works fine. It gave an error when I tried to install it ("can't access /tmp/xxx") but I manually copied the files from /tmp to /usr/bin and share etc and all good now

[goingnuts]

greengeek: Yes - the wireless manager should take care of it all. I just booted pupngo2012 from CD and managed to connect to my wireless with it...so sometimes it work.

You say 'If I choose connect it says "wireless adapter found, press ok to continue"': It should say "wireless adapter found wlan0, press ok to continue" or at least print the found interface. If the interface is missing that might mess up the following call to "wpa_cli -i $INTERFACE scan > /dev/null" which is in an endless loop. Try to look in /tmp/interfaces to view what interfaces was found.

[greengeek]

[goingnuts]

Not quite sure why it says eth1 - have you disconnected all wired net cables during your trials?
The wpa_cli is a binary file not a script. You can use it standalone to connect (as far as I know) from a terminal.
There might be settings in the script for WPA that are wrong - I can only test WPA2 here.
ADD: Some drivers did not make it into pUPnGO which might be needed to get wireless working. I have uploaded a sfs-file here with these drivers.

[starhawk]

One more question -- where is that xorgwizard mini version that you put together (that config's and runs xvesa)? That typo is still in my version (I haven't re-downloaded it) and I'd like to get rid of it.