pUPnGO 2012
Hey, goingnuts, I'm sure I've asked this before, as I've forgotten about this version of pUPnGO for some time... BUT...
Could you incorporate Xorg (just enough for the generic driver) into this somehow? I really don't know enough to do it myself
Also real wireless support would be way cool. Just a port over of SNS would be enough
EDIT: just to give you the full story, this is for the Infernal Dell -- my Latitude CPi (P2 300MHz and 128MB RAM). Xvesa does all sorts of nifty things to the screen about 30sec in. That is to say, it fails quite spectacularly!
Technically, the NeoMagic driver "should" work, but on this system it generally does not -- Puplite5 and Akita get it right, other puplets generally speaking make a mess of things -- the colors are way off. (Not quite as bad a failure as Xvesa, fortunately.)
I still have a wireless-only network, hence that request -- I don't have the (rather rare, I am told) Ethernet->WiFi sort of module, just the regular USB ones. My particular favorite is a Rosewill RNX-N150UBE with the RTL8188 chipset.
Could you incorporate Xorg (just enough for the generic driver) into this somehow? I really don't know enough to do it myself
Also real wireless support would be way cool. Just a port over of SNS would be enough
EDIT: just to give you the full story, this is for the Infernal Dell -- my Latitude CPi (P2 300MHz and 128MB RAM). Xvesa does all sorts of nifty things to the screen about 30sec in. That is to say, it fails quite spectacularly!
Technically, the NeoMagic driver "should" work, but on this system it generally does not -- Puplite5 and Akita get it right, other puplets generally speaking make a mess of things -- the colors are way off. (Not quite as bad a failure as Xvesa, fortunately.)
I still have a wireless-only network, hence that request -- I don't have the (rather rare, I am told) Ethernet->WiFi sort of module, just the regular USB ones. My particular favorite is a Rosewill RNX-N150UBE with the RTL8188 chipset.
- technosaurus
- Posts: 4853
- Joined: Mon 19 May 2008, 01:24
- Location: Blue Springs, MO
- Contact:
a static toolchain means no Xorg, but you can dump Xorg and the shared lib dependencies from any distro where your video does work.
Check out my [url=https://github.com/technosaurus]github repositories[/url]. I may eventually get around to updating my [url=http://bashismal.blogspot.com]blogspot[/url].
Actually... dirty little secret, I got a replacement CPi at some point. The old(er) one is now a parts machine. Looks like that parts machine has some video issues as well as a bad RAM slot -- although pUPnGO looks HORRIBLE on the newer example (not being suited to stripy pink and blue), it *is* stable... strange. I've attached a bad photo of what it looks like -- my amazing photography skills compensate for the fact that every 3rd column or so of pixels is black. Oops.
So I'll want to copy over Xorg, the generic Xorg driver (and MAYBE the neomagic driver) and whatever generates the conf files that Xorg needs.
I'll also be needing to know how to integrate Xorg in -- i.e. how to get the system to call Xorg and not just Xvesa. This should be fun
Hey, speaking of pink and blue... makes me think of J Edgar Swoop, a silly poem that my father illustrated for IIRC like a class project or something in the 80s. A pity that about 90% of that work got lost somewhere along the way -- the part I've seen was excellent.
So I'll want to copy over Xorg, the generic Xorg driver (and MAYBE the neomagic driver) and whatever generates the conf files that Xorg needs.
I'll also be needing to know how to integrate Xorg in -- i.e. how to get the system to call Xorg and not just Xvesa. This should be fun
Hey, speaking of pink and blue... makes me think of J Edgar Swoop, a silly poem that my father illustrated for IIRC like a class project or something in the 80s. A pity that about 90% of that work got lost somewhere along the way -- the part I've seen was excellent.
- Attachments
-
- CPi-pUPnGO-Ewww.jpg
- Scary screenshot... just, yuk.
- (72.64 KiB) Downloaded 516 times
- technosaurus
- Posts: 4853
- Joined: Mon 19 May 2008, 01:24
- Location: Blue Springs, MO
- Contact:
starhawk: I did post a Xorg.pet here but the download does not work any more and I have deleted the pet...maybe you have it still?
The other thing to try is Xfbdev. I have attached a pet with it as well as a small launcher. Start pUPnGO2012 with the boot parameter "vga=785" ex. "puppy vga=785" or use the ask mode "puppy vga=ask" and choose resolution afterwards.
After booting into Xvesa, exit2prompt and run "xfbinit"...
You will have to get the content of the package installed before doing the above,,,
As for changing the resolution try run "setresolution.sh" at a prompt or maybe use the Setup icon on desktop...it will list the modes supported by your hardware.
The other thing to try is Xfbdev. I have attached a pet with it as well as a small launcher. Start pUPnGO2012 with the boot parameter "vga=785" ex. "puppy vga=785" or use the ask mode "puppy vga=ask" and choose resolution afterwards.
After booting into Xvesa, exit2prompt and run "xfbinit"...
You will have to get the content of the package installed before doing the above,,,
As for changing the resolution try run "setresolution.sh" at a prompt or maybe use the Setup icon on desktop...it will list the modes supported by your hardware.
Last edited by goingnuts on Sun 30 Sep 2012, 06:22, edited 1 time in total.
Don't have that Xorg PET file anymore but I know how to drag n drop if you can tell me (again, approximately) what files to pull out of a full install of 432...
The xfbdev pet has problems:
The xfbdev pet has problems:
In other words, THAT'S gonna leave a stain on the rugThe following messages or errors were encountered:
/usr/sbin/pkginstall.sh: cd: line 380: can't cd to /tmp/pet/xfbdev
BusyBox v1.17.0.git (2011-07-24 18:44:24 GMT-8) multi-call binary.
Usage: basename FILE [SUFFIX]
Strip directory path and .SUFFIX from FILE
/usr/sbin/pkginstall.sh: cd: line 390: can't cd to /tmp/pet/xfbdev/
cp: cannot stat `/tmp/pet/xfbdev/*': No such file or directory
rmdir: '/tmp/pet': Directory not empty
Errors from tar and gzip is normally harmless.
Press OK to continue/quit.
Starhawk - you probly already know this but if you rescale the jpg to a width less than 600 pixels it will display on the forum in a much smaller filesize (without loss of onscreen clarity) without requiring each person to download it (which saves John Murga a lot of bandwidth and lets us see the image straight off).
(I use mtpaint and then "image, scale canvas" then set the width to 595 pixels, then click once in the "height" box to allow it to automatically keep the correct aspect ratio)
Then it will be visible on the forum without extra downloading, like this:
(I use mtpaint and then "image, scale canvas" then set the width to 595 pixels, then click once in the "height" box to allow it to automatically keep the correct aspect ratio)
Then it will be visible on the forum without extra downloading, like this:
- Attachments
-
- 100_2887_.JPG
- (28.06 KiB) Downloaded 749 times
I agree thats annoying...but have a look in /tmp/pet/...there it should be...just named xfbdev_static_20120928...and inside you should find the bins. Just copy them to /usr/X11R7/bin.starhawk wrote:/usr/sbin/pkginstall.sh: cd: line 390: can't cd to /tmp/pet/xfbdev/
cp: cannot stat `/tmp/pet/xfbdev/*': No such file or directory
rmdir: '/tmp/pet': Directory not empty
Errors from tar and gzip is normally harmless.
Press OK to continue/quit.
In other words, THAT'S gonna leave a stain on the rug
It must be my naming of the pet which puzzles the pkginstall-program - sorry!
Hi Goingnuts, this is an interesting offering. I am posting from Dillo, via wired connection. I couldn't work out how to activate the wireless card (although iwconfig seems to suggest it is loaded). Can you offer any tips about the best way to configure the wpa password into the wireless config please? I guess it is done from the cli?? cheers!goingnuts wrote:Yes my homebrewed wifimanager is present - which at some tie in the past got me connected via wireless...
We got wpa_cli, wpa_supplicant, wpa_passphrase and iwconfig at hands to play with...but no firmware drivers..
EDIT: Ok, I used wpa_passphrase and it seemed to accept my wifi password, then I didn't know what step to take next. I tried wpa_cli and wpa_supplicant but am stabbing in the dark really... Any ideas appreciated. thx
greengeek: Try looking into the /usr/sbin/wireless.sh script. I have been able to connect with that script but it is not always working - might be my wireless router giving problems. Also I only have tested WPA2...
If you are using the updated pUPnGO from 20120616 (download in first post) most drivers should be present and auto loaded - although there are no guarantee the autoloaded driver works with your hardware. Good luck!
If you are using the updated pUPnGO from 20120616 (download in first post) most drivers should be present and auto loaded - although there are no guarantee the autoloaded driver works with your hardware. Good luck!
xfbdev doesn't work. Black and blue and pink screen, with black blotches when I move the cursor. No icons and no conky.
Correct VGA mode here is 317, BTW (785 is some sorta 800x600 mess). Not that it matters!
One other thing, there is a tiny tiny bug in your xorgwizard (or whatever the startup keyboard/mouse detection shell script is). It reads "Your correct! My mouse is a [WHATEVER] mouse" for option 0. "Your" is grammatically incorrect -- the line should start with "You're" instead. Again, very minor bug that probably nobody cares about. I only picked up on it because Mom used to be a librarian and is VERY picky about my English. ("Ain't ain't a word!")
Correct VGA mode here is 317, BTW (785 is some sorta 800x600 mess). Not that it matters!
One other thing, there is a tiny tiny bug in your xorgwizard (or whatever the startup keyboard/mouse detection shell script is). It reads "Your correct! My mouse is a [WHATEVER] mouse" for option 0. "Your" is grammatically incorrect -- the line should start with "You're" instead. Again, very minor bug that probably nobody cares about. I only picked up on it because Mom used to be a librarian and is VERY picky about my English. ("Ain't ain't a word!")
The Xfbdev launch script is very simple and does not start icons or conky - it is just an example. Sorry that the Xfbdev did not solve your display problem. And thank you for pointing the spelling bug - I have corrected it.starhawk wrote:xfbdev doesn't work. Black and blue and pink screen, with black blotches when I move the cursor. No icons and no conky.
Correct VGA mode here is 317, BTW (785 is some sorta 800x600 mess). Not that it matters!
One other thing, there is a tiny tiny bug in your xorgwizard (or whatever the startup keyboard/mouse detection shell script is). It reads "Your correct! My mouse is a [WHATEVER] mouse" for option 0. "Your" is grammatically incorrect -- the line should start with "You're" instead. Again, very minor bug that probably nobody cares about. I only picked up on it because Mom used to be a librarian and is VERY picky about my English. ("Ain't ain't a word!")
Does other Puppy version looks ok with your display? Just to make sure its not a monitor or cable problem...looks really odd...
OK, I got my wireless running in a LiveCD environment, using WPA. (I am posting this from Dillo - a little hard to see what's what on screen, but working via wireless nevertheless...) I will post the steps I used so I can find the info again next time:goingnuts wrote:greengeek: Try looking into the /usr/sbin/wireless.sh script. I have been able to connect with that script but it is not always working - might be my wireless router giving problems. Also I only have tested WPA2...
EDIT: this works for live CD session, but not for installed session. For instructions that work in both live and installed sessions see my later post at:
http://murga-linux.com/puppy/viewtopic. ... &start=136
1) Create a new file as /etc/wpa_supplicant.conf containing the following:
Code: Select all
ctrl_interface=/var/run/wpa_supplicant
ap_scan=2
update_config=1
network={
id_str="some name to identify the connection you are creating"
ssid="the SSID name of your router"
psk="the shared key password for your router"
proto=WPA
key_mgmt=WPA-PSK
pairwise=TKIP
group=TKIP
priority=1
}
ifconfig eth1 up
then:
wpa_supplicant -D wext -i eth1 -c /etc/wpa_supplicant.conf
(this will then connect but the terminal will appear to hang. Open a new terminal and continue...)
3) dhcpcd -t 30 -h puppypc12345 -d eth1
(the puppypc12345 is the hostname, which should be made unique so each PC stays separately identified)
4) type: ifconfig and check that IP has been correctly assigned
EDIT: I tried to write these 3 steps up as a single script (my first attempt at a script!) but it didn't work. However it turns out that the issue was that the script got hung up at the wpa_supplicant step and wouldn't proceed on to the dhcpcd step. Tempestuous offeres a way around this by including the -B switch in the wpa_supplicant string.
http://www.murga-linux.com/puppy/viewto ... 9&start=10tempestuous wrote:wpa_supplicant may take about 30 seconds to negotiate the connection.
Hopefully you will see a connection reported, then you can open a second console and proceed to obtain an IP address (DHCP).
It's possible to background the wpa_supplicant process in order to keep using the same xterminal by adding "-B" to the command
... but do this only once you know that the wpa_supplicant command is successful, because once backgrounded you won't see any error messages.
So the final wpa_supplicant string I used in my script (which now works) is:
Code: Select all
wpa_supplicant -B -D wext -i eth1 -c /etc/wpa_supplicant.conf
Code: Select all
#!/bin/sh
ifconfig eth1 up
sleep 10
wpa_supplicant -B -D wext -i eth1 -c /etc/wpa_supplicant.conf
sleep 40
dhcpcd -t 30 -h puppypc12345 -d eth1
Last edited by greengeek on Sun 23 Dec 2012, 19:25, edited 2 times in total.
greengeek: Nice! You can alter the fontsize in dillo - view here
And here is a new Xorg-pack with everything coming from P412
Install via "pkginstall.sh pupngo_xorg_pack_412.pet"
exit to prompt
run "xorgwizard"
start x again by "xwin"
If everything works you should be in Xorg.
Do not run the xorgwizard from within X as it will fail - only from command prompt.
I am willing to give it a try - if someone could point me to the full source...I did start at it at some point by cutting scripts out of wary but thats not the way to do it...starhawk wrote:Also real wireless support would be way cool. Just a port over of SNS would be enough
And here is a new Xorg-pack with everything coming from P412
Install via "pkginstall.sh pupngo_xorg_pack_412.pet"
exit to prompt
run "xorgwizard"
start x again by "xwin"
If everything works you should be in Xorg.
Do not run the xorgwizard from within X as it will fail - only from command prompt.