It's different because you are running ROX, which is probably not recommended.Pete22 wrote:Geoffrey,
thank you for the picture. Under the 4th tab, I could have missed that.
Humm, something IS wrong. When I press properties,
This is what I get this instead.
I wonder why mine is different.
Pete.
Saluki
I'm not sure why you are getting dumped to the console, but the proper command is 'xwin' not 'startxfce4'.NZCyrus wrote:tried to upgrade from 018 to 019 and also tried a fresh install by wiping my drive, but something does not load on boot and i cannot automatically log in. Saluki is the only OS on my laptop. md5sum of 019 was OK.
After the install, all is well and the desktop runs as normal, but when I reboot I am taken to a screen that says automatic login, etc but I am at #. When I type startxfce4 it takes me to the desktop but the screen freezes. Possibly my older hardware, ThinkPad R51 ?
Hmm, no one has mentioned pgrps since I got rid of the connect icon in like saluki-004. It must not be terribly popular.Karl Godt wrote:Really nice experience so far .
Many many new things to explore like adrv.sfs ...
Whow !
One thing for pgprs-setup :
Without the standard connect button not easy to find
[Don't actually know why it is hidden and pupdial so much propagated .]
Funny theme and a stylish background fitting to that , I like it .
Woof is apparently not the newest, pgprs-setup is missing the gettext's
This is some code to add a PUK line to pgprs-setup :
This is to filter devices not attached to modems ie USB to SERIAL adapters :Code: Select all
> RGPIN="AT+CPIN="$PIN"" > if [ "`echo "$PIN" |grep ','`" ];then > PUK=`echo "$PIN" |cut -f1 -d','` > PIN=`echo "$PIN" |cut -f1 -d','` > sed -i "s/$RGPIN/AT+CPIN="$PIN"" /etc/ppp/peers/pgprs-connect-chatmm > fi > [ "$PUK" ] || PUK="""" 77a78
Code: Select all
> DMESG=`dmesg` 81c82 < for DEVICE in /dev/ttyUSB0 /dev/usb/ttyUSB0 /dev/ircomm0 /dev/ttyUB0 /dev/rfcomm0 /dev/ttyS0 --- > for DEVICE in /dev/ttyUSB0 /dev/ttyUSB1 /dev/usb/ttyUSB0 /dev/ircomm0 /dev/ttyUB0 /dev/rfcomm0 /dev/ttyS0 85a87 > if [ "`echo "$DMESG" |grep "${DEVICE##*/}" |grep -i -E 'GSM|modem'`" ];then 87a90 > fi
>Code: Select all
> <text tooltip-text="Only needed if need to unlock SIM card"> > <label>Phone PUK:</label> > </text> > <entry> > <default>${PUK}</default> > <variable>PUK</variable> > </entry> > </hbox>
> <hbox>
164c178
and this is to stop the pupmessage always popping up :Code: Select all
> if [ ! "$PUK" ];then 209a225,227 > else > wordreplace /etc/ppp/peers/gprs-connect-chatmm "$RGPIN" "AT+CPIN="${PUK},${PIN}"" > fi 211c229,233
*Code: Select all
< xmessage -center -title "$(gettext 'PGPRS SETUP')" "$(gettext "Connect to the Internet using 'PGPRS Connect' in the 'Network' menu.")" --- > if [ -f "`which pgprs-shell`" ];then > if [ -x "`which pgprs-shell`" ];then > chmod a-x "`which pgprs-shell`" > xmessage -center -title "PGPRS SETUP" "Connect to the Internet using 'PGPRS Connect' in the 'Network' menu." > fi;fi
One problem with pupdial seems to be the entry
"ABORT ERROR"
in /etc/ppp/chat-script .
Unblocking the SIM and failing to connect mostly works at second attempt, but unblocking the SIM a second time always gives ERROR and the connection can only be tried again if the eeepc internal modem is reset by reboot,poweroff or suspend (to ram) . pgprs-connect also shows the ERROR message but has no "ABORT ERROR" in /etc/ppp/peers/gprs-connect-chatmmm .
*
Saluki performance overall is little slower but vacation for the mind !
Great piece of work , jemimah !
*
[by the way anyone knows how the trash bin can be placed outside the desktop ?]
Saluki is synced with Racy 5.2. I will try to sync it with 5.3 for the second release, but it's going to be a pain since everything is so different now my patches need to be applied manually.
If you make your patches with 'diff -u' it's easier for me to figure out. Better yet, send me the whole patched script and I'll add it to the next release.
There's a trashbin for the panel. Then you can turn of the desktop trash in the desktop settings.
Oohhh, I see. Finally found in thunar!
Even more interesting.
The MD5 did not match. So I am glad I persisted.
I will download it again.
On gtkhash, it showed me the number,
but I had to manually check it with the md5.txt.
I thought if the md5.txt file was in the same directory,
it would automatically check it for me.
Is that wrong?
Pete
Even more interesting.
The MD5 did not match. So I am glad I persisted.
I will download it again.
On gtkhash, it showed me the number,
but I had to manually check it with the md5.txt.
I thought if the md5.txt file was in the same directory,
it would automatically check it for me.
Is that wrong?
Pete
Deleted savefile so fresh frugal install of 019. No problems to speak of.Looking good......
# report-video
Saluki, version 019 on Sat 14 Apr 2012
Chip description:
0.0 VGA compatible controller
nVidia Corporation NV18 [GeForce4 MX 440 AGP 8x] (rev c1)
oem: NVidia
product: NV18 () Board Chip Rev A2
X Server: Xorg
Driver used: nouveau
X.Org version: 1.11.0
dimensions: 1440x900 pixels (380x238 millimeters)
depth of root window: 24 planes
...the above also recorded in /tmp/root/ as report-video,
and archived with xorg.conf and Xorg.0.log as report-video-full.gz
#
# report-video
Saluki, version 019 on Sat 14 Apr 2012
Chip description:
0.0 VGA compatible controller
nVidia Corporation NV18 [GeForce4 MX 440 AGP 8x] (rev c1)
oem: NVidia
product: NV18 () Board Chip Rev A2
X Server: Xorg
Driver used: nouveau
X.Org version: 1.11.0
dimensions: 1440x900 pixels (380x238 millimeters)
depth of root window: 24 planes
...the above also recorded in /tmp/root/ as report-video,
and archived with xorg.conf and Xorg.0.log as report-video-full.gz
#
Hi Jemimah / Pemasupemasu wrote:Dont forget kernel source sfs from the first page so...that you can compile kernel module drivers also....
I think the kernel sources link has gone missing from the front page.....is it k3.2.8-preemptive-fixed-aufs of 12 March?? There are other earlier k3.2.8-preemptives still there....
Thanks
peebee
Last edited by peebee on Sun 15 Apr 2012, 08:02, edited 1 time in total.
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
I can only guess which kernel Jemimah used...but the latest one is in this folder:
http://www.smokey01.com/pemasu/Saluki/k ... ixed-aufs/
Oh yes...and for pae kernel:
http://www.smokey01.com/pemasu/Saluki/k ... .2.13-pae/
http://www.smokey01.com/pemasu/Saluki/k ... ixed-aufs/
Oh yes...and for pae kernel:
http://www.smokey01.com/pemasu/Saluki/k ... .2.13-pae/
10alsa
I think the /etc/init.d/10alsa on Saluki-19 is outdated.DaveS wrote:BUG, 19, frugal install. Sound re-sets to default setting at re-boot, personalised settings are not persistent.
The woof-120226 has recent one, but i have another which is based on the Japanese versions.
Code: Select all
# 7dec2011 shinobar: wait loading modules, conditional saving asound.state (merged form the Quickset Wary, wary-511-01q)
#111210 shinobar: refresh asound.state at restart
#120103 karl godt: fix unloading modules. refer: http://www.murga-linux.com/puppy/viewtopic.php?t=71767&start=390
#120222 revert 111229. 120223 shinobar: better fix.
#120226 01micko: added 'Master Front' entries. 120318 bumped it up, 75% to 100%.
- Attachments
-
- 10alsa-shinobar.gz
- extract, rename, add excutable, and place at /etc/init.d/10alsa
- (1.81 KiB) Downloaded 242 times
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
Partition alphabetical order is not right in Saluki...which is not so apparent due to missing drive icons.
But I believe the /sbin/probepart is about same in Saluki since I use Jemimah's patched version.
http://murga-linux.com/puppy/viewtopic. ... 159#620159
But I believe the /sbin/probepart is about same in Saluki since I use Jemimah's patched version.
http://murga-linux.com/puppy/viewtopic. ... 159#620159
- shelezyaka
- Posts: 52
- Joined: Tue 14 Feb 2012, 13:57
- Location: Ukrainian
Kernel sources are in the repo.peebee wrote:Hi Jemimah / Pemasupemasu wrote:Dont forget kernel source sfs from the first page so...that you can compile kernel module drivers also....
I think the kernel sources link has gone missing from the front page.....is it k3.2.8-preemptive-fixed-aufs of 12 March?? There are other earlier k3.2.8-preemptives still there....
Thanks
peebee
You can try booting without vga=0x311 and see if that sorts it.Sage wrote:More grief with SiS chipsets. Now getting picture at wrong res. at boot-up, but the CLI is black screen, whether nox or CTRL-ALt-BKSPCE. Everything else, old & new - no issues. There is an answer to the SiS conundrum, not know to YT; probably ask micko, PD, pem. or shin.
- OscarTalks
- Posts: 2196
- Joined: Mon 06 Feb 2012, 00:58
- Location: London, England
Was going to report also that it is not remembering the soundcard volume settings.
Not quite sure what to do with shinobar's file, what does "add executable" mean? Sorry for being a beginner in that aspect of things.
I have downloaded, extracted, renamed as "10alsa", removed the old file from /etc/init.d/10alsa and put this one in instead. I think it may be working but am I supposed to do anything else?
Also Jemimah or somebody, this is a problem across all the puppies which needs to be addressed in that the allocation of index 0 for the sound modules in /etc/modprobe.d/alsa-base.conf needs to be locked down somehow. Could something detect the devices and write the code into that file?
Not quite sure what to do with shinobar's file, what does "add executable" mean? Sorry for being a beginner in that aspect of things.
I have downloaded, extracted, renamed as "10alsa", removed the old file from /etc/init.d/10alsa and put this one in instead. I think it may be working but am I supposed to do anything else?
Also Jemimah or somebody, this is a problem across all the puppies which needs to be addressed in that the allocation of index 0 for the sound modules in /etc/modprobe.d/alsa-base.conf needs to be locked down somehow. Could something detect the devices and write the code into that file?
Last edited by OscarTalks on Sun 15 Apr 2012, 16:38, edited 1 time in total.
Oscar in England
I downloaded the delta file to update my luki-17.iso file.
I then picked menu - Utility - Xdelta and dragged and dropped the ISO file in the top box and the delta file in the lower box and selected Create.
This has worked before with no problems.
But this time, after getting a message of "newfile.iso created", I had no new ISO file.
Is xdelta possibly broke in lupu 520?
Or is it a bad delta file?
How would I do this from a command line?
I then picked menu - Utility - Xdelta and dragged and dropped the ISO file in the top box and the delta file in the lower box and selected Create.
This has worked before with no problems.
But this time, after getting a message of "newfile.iso created", I had no new ISO file.
Is xdelta possibly broke in lupu 520?
Or is it a bad delta file?
How would I do this from a command line?
Last edited by 8-bit on Sun 15 Apr 2012, 14:20, edited 1 time in total.
There is no delta for 19. I overwrote my copy of 18 and I don't feel like downloading it again. If someone else wants to make a delta and post it, that's cool with me.8-bit wrote:I downloaded the delta file to update my luki-17.iso file.
I then picked menu - Utility - Xdiff and dragged and dropped the ISO file in the top box and the delta file in the lower box and selected Create.
This has worked before with no problems.
But this time, after getting a message of "newfile.iso created", I had no new ISO file.
Is xdiff possibly broke in lupu 520?
Or is it a bad delta file?
How would I do this from a command line?
Bingo! Set pfix=ram vga=normal screen=800x600. Was able to CTL-ALT-BKSPCE into a readable mode and set correct xorgwizard/Probe to 1440x900/1024x768. Suppose a cheat code of vga=771 would also do the biz. That should also work on older monitors that perhaps less fortunate folks still use. Will pop down to the garage to check it on an old 14" crt with a PCI Trident card when the weather warms up! Some of this years' HW can be a bit troublesome!
Thanks a bunch.
Thanks a bunch.