Slacko B5
Slacko B5
Booted live cd
probe detected 1024x768 screen
sound = ok
auto connect to internet =ok
seamonkey-2.4 = ok
setup printer = ok
next
full install to ext4 partition
probe detected 1024x768 screen
sound = ok
auto connect to internet - did not work on boot of full install, however, did work on boot of live cd - strange
seamonkey-2.4 = ok
setup printer = ok
shutdown and rebooted = no problems on shutdown - reboot clean
added pets from my save partition and have not encountered any problems at this point.
Working great for me.
majorfoo
probe detected 1024x768 screen
sound = ok
auto connect to internet =ok
seamonkey-2.4 = ok
setup printer = ok
next
full install to ext4 partition
probe detected 1024x768 screen
sound = ok
auto connect to internet - did not work on boot of full install, however, did work on boot of live cd - strange
seamonkey-2.4 = ok
setup printer = ok
shutdown and rebooted = no problems on shutdown - reboot clean
added pets from my save partition and have not encountered any problems at this point.
Working great for me.
majorfoo
pemasu thanks!pemasu wrote:http://www.murga-linux.com/puppy/viewto ... 235#568235
Joe Wing is back. New JWM binary fixes the fullscreen bug.
Java in SLACKO
I have already reported on QuickPET issue in its Menu.
Here's an issue with PPM to add JAVA to SLACKO. The problem is easy installation issues because of the dependency requirement.
It would be nice to know how I should proceed to install JAVA in Slacko. Here's what happened to JRE.
I have already reported on QuickPET issue in its Menu.
Here's an issue with PPM to add JAVA to SLACKO. The problem is easy installation issues because of the dependency requirement.
It would be nice to know how I should proceed to install JAVA in Slacko. Here's what happened to JRE.
- Attachments
-
- JRE installation dependency.png
- JRE has dependency requirements
- (19.55 KiB) Downloaded 1990 times
Last edited by gcmartin on Tue 27 Sep 2011, 23:20, edited 1 time in total.
-
- Posts: 58
- Joined: Mon 21 Feb 2011, 00:13
Just made a frugal install of B5 and have the following observations (hope some of it may help):
1. No need any more for acpi=force in Grub nor 01micko's acpi.pet to make a shutdown. Good news.
2. Installed Opera from slickpet but it isn't seen in the Change Browser Default menu selection.
3. And installing Browser-default from slickpet still suggests it's to be found other than where it is ie in Utility.
4. Trivial typo in slickpet
5. I understand the reason why 01Micko doesn't want to put dependancies in slickpet (chromium 15 is still there by the way) but when I tried to install Chromium 16.0.881-slacko instead from slickpet (or at DaveS's suggestion using Playdayz's version from the forum...but I think they are the same though) this time it doesn't tell me I need any dependancies but still won't run, despite appearing in the Default Browser list. From the cmd line it reports
6. And if some kind soul could look into why OOoLight.sfs (see http://download.ooolight.org/) isn't recognised in B5 but is in for example Puppy528 that would be really appreciated.
Many thanks
1. No need any more for acpi=force in Grub nor 01micko's acpi.pet to make a shutdown. Good news.
2. Installed Opera from slickpet but it isn't seen in the Change Browser Default menu selection.
3. And installing Browser-default from slickpet still suggests it's to be found other than where it is ie in Utility.
4. Trivial typo in slickpet
.Transmissiom
5. I understand the reason why 01Micko doesn't want to put dependancies in slickpet (chromium 15 is still there by the way) but when I tried to install Chromium 16.0.881-slacko instead from slickpet (or at DaveS's suggestion using Playdayz's version from the forum...but I think they are the same though) this time it doesn't tell me I need any dependancies but still won't run, despite appearing in the Default Browser list. From the cmd line it reports
What is it missing??Illegal Instruction.
6. And if some kind soul could look into why OOoLight.sfs (see http://download.ooolight.org/) isn't recognised in B5 but is in for example Puppy528 that would be really appreciated.
Many thanks
gcmartin: what, you didn't like DGmod? (I think someone is color blind )
I left slacko running for a few hours, and when I returned:
After cleaning cache:
I left slacko running for a few hours, and when I returned:
Code: Select all
Mem: 879096K used, 155416K free, 0K shrd, 78828K buff, 628472K cached
Code: Select all
Mem: 186180K used, 848332K free, 0K shrd, 2512K buff, 46768K cached
It's the new default jwm theme. It resembles what happens when your laptop video chip needs reseating.gcmartin wrote:"What is DGmod?" Does it come with something in SLACKO that I'm missing?jpeps wrote:gcmartin: what, you didn't like DGmod? (I think someone is color blind ...
I welcome advice or assistance.
Thanks in advance
Hi Mick,
KDE 4.5.5 desktop, installed with PPM, still works with Slacko, although many bugs ie plasma, Shutdown and Panel items don't work.
Shutdown problem is easily corrected by installing radky's PupShutdown, others are more difficult to correct. Hopefully, someone will develop a fully operational KDE 4.5.5 sfs after Slacko is final. However, not I since that's way above my skill level.
Cheers,
Jim
KDE 4.5.5 desktop, installed with PPM, still works with Slacko, although many bugs ie plasma, Shutdown and Panel items don't work.
Shutdown problem is easily corrected by installing radky's PupShutdown, others are more difficult to correct. Hopefully, someone will develop a fully operational KDE 4.5.5 sfs after Slacko is final. However, not I since that's way above my skill level.
Cheers,
Jim
- Attachments
-
- image-1.jpg
- (20.78 KiB) Downloaded 1951 times
Thanks Jim.. actually I have KDE running nicely in my full install of one of the very early slacko alphas.. I use it for kernel compiling.Jim1911 wrote:Hi Mick,
KDE 4.5.5 desktop, installed with PPM, still works with Slacko, although many bugs ie plasma, shutdown.
Shutdown problem is easily corrected by installing radky's PupShutdown, others are more difficult to correct. Hopefully, someone will develop a fully operational KDE 4.5.5 sfs after Slacko is final. However, not I since that's way above my skill level.
Cheers,
Jim
_________________________________________________________
jpeps wrote:It's the new default jwm theme. It resembles what happens when your laptop video chip needs reseating.
__________________________________________________________I wrote:(typos and all)The theme.. you'll either love it or hate it! I think it's co-ordinted, semi-professional and above all fun.
In other news....
Barry has fixed the shutdown bug ... those adventurous enough .. try it. I'm outa here in 2 hours. (I can hear the fishies calling).
Puppy Linux Blog - contact me for access
- Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
01micko wrote:(I can hear the fishies calling)
My file system is behaving erratically
At the moment I have saved a txt file in root, that is saving but not appearing.
There are other instances - this was not happening in B4
The file was a system report from this excellent system reporting pet
http://bkhome.org/blog/?viewDetailed=02503
Also from Barrys blog - New JWM could be tested . . .
http://bkhome.org/blog/?viewDetailed=02507
The fishies are after me
- Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
OK just been running and the fishes never caught me . . .
. . . mystery of missing root save solved
the Lighthouse Sys Info file is saved in /tmp/root . . .
and I thought I was just in root as root was in the dialog box
The fishes are giggling at me again
I enclose my system details for the record
Incidentally Lighthouse is 32bit and 64bit, and complete with all the trimmings . . .
http://www.lhpup.org/index.php
. . . mystery of missing root save solved
the Lighthouse Sys Info file is saved in /tmp/root . . .
and I thought I was just in root as root was in the dialog box
The fishes are giggling at me again
I enclose my system details for the record
Incidentally Lighthouse is 32bit and 64bit, and complete with all the trimmings . . .
http://www.lhpup.org/index.php
- Attachments
-
- sys-info-110928.gz
- (14.86 KiB) Downloaded 409 times
gcmartin,
I have jre 1.6.0.27 as an sfs which I load and it causes no problems. maybe that's the way to go. Can't be sure but I think it came from Barrys site.
The point being I have it in /mnt/home and that way whichever iso I'm using can load it.
Mick,
No real issues but I did notice a slight icon mouse 'focus' issue sometimes. i.e. click on icon on desktop and nothing happens unless I'm dead centre of icon.
I have jre 1.6.0.27 as an sfs which I load and it causes no problems. maybe that's the way to go. Can't be sure but I think it came from Barrys site.
The point being I have it in /mnt/home and that way whichever iso I'm using can load it.
Mick,
No real issues but I did notice a slight icon mouse 'focus' issue sometimes. i.e. click on icon on desktop and nothing happens unless I'm dead centre of icon.
Rob
-
The moment after you press "Post" is the moment you actually see the typso 8)
-
The moment after you press "Post" is the moment you actually see the typso 8)
Re: Slacko B5
You need to get that recharge started.01micko wrote: (I'll be away for some days as of tomorrow.. recharge the batteries before the final assault )
Cheers,
Jim
- charlie6
- Posts: 1230
- Joined: Mon 30 Jun 2008, 04:03
- Location: Saint-Gérard / Walloon part of Belgium
Xorgwizard hangs up from 4.99.4 to .7 using smi driver
Hi,
last edited: summary:
Xorgwizard behaves as if something has changed in it since Slacko4.99.4 and later, that brings xorg.conf not being configured automaticaly as earlier.
All this happens here on laptop (Medion LT9399 ... Asus made) featured with siliconmotion SM720 video set, upon live-cd bootup and xorgwizard setup:
Story
X was working OK on 312.37 (except that Xkblayout keeps fixed to 'us' whatever the Personalize settings change to 'fr azerty' or 'be-latin1') as early reported in the post here:
http://www.murga-linux.com/puppy/viewto ... 7d425a0cf8
That Laptop was also booting up as well with Slacko 4.99.1 and 4.99.2 but with the persisting keyboard layout problem as above.
Got a try now with Slacko B5: X or xorgwizard hangs up upon live-cd boot after manual driver type and resolution choices.
Thanks for any advice
Charlie
edited 29 sept 2011: here are further testings on that Laptop:
Since slacko 4.99.4 till 4.99.7, Xorgwizard cannot configure anymore upon live-cd boot (blackscreen after having manualy choosen the siliconmotion driver and set the display resolution even if manualy set using option 'Z'). Till B1 and B2 X does start: I meanwhile created a slackosave-B1.3fs file for further use and updating with later slacko version.
Updating Slacko from B1 or B2 slackosave file:
Slacko B5 boots up frugal on a slackosave-B1.3fs and updates it nice; but the keyboard layout problem remains: the keyboard keeps set on 'us'.
attached are some documentation files (renamed adding .gz - delete .gz to read them as text)
edited sept 30 sept 2011:
country keyboard setup hopefully solved: (do not know is this is enough ?) by editing xorg.conf and adding the missing Section Device
at the end:
Now xorg.conf looks like:
Remainig problem: on that Laptop xorgwizard hangs up from Slacko 4.99.4 till 4.99.7 upon live-cd fresh bootup (all versions tested).
last edited: summary:
Xorgwizard behaves as if something has changed in it since Slacko4.99.4 and later, that brings xorg.conf not being configured automaticaly as earlier.
All this happens here on laptop (Medion LT9399 ... Asus made) featured with siliconmotion SM720 video set, upon live-cd bootup and xorgwizard setup:
Story
X was working OK on 312.37 (except that Xkblayout keeps fixed to 'us' whatever the Personalize settings change to 'fr azerty' or 'be-latin1') as early reported in the post here:
http://www.murga-linux.com/puppy/viewto ... 7d425a0cf8
That Laptop was also booting up as well with Slacko 4.99.1 and 4.99.2 but with the persisting keyboard layout problem as above.
Got a try now with Slacko B5: X or xorgwizard hangs up upon live-cd boot after manual driver type and resolution choices.
Thanks for any advice
Charlie
edited 29 sept 2011: here are further testings on that Laptop:
Since slacko 4.99.4 till 4.99.7, Xorgwizard cannot configure anymore upon live-cd boot (blackscreen after having manualy choosen the siliconmotion driver and set the display resolution even if manualy set using option 'Z'). Till B1 and B2 X does start: I meanwhile created a slackosave-B1.3fs file for further use and updating with later slacko version.
Updating Slacko from B1 or B2 slackosave file:
Slacko B5 boots up frugal on a slackosave-B1.3fs and updates it nice; but the keyboard layout problem remains: the keyboard keeps set on 'us'.
attached are some documentation files (renamed adding .gz - delete .gz to read them as text)
edited sept 30 sept 2011:
country keyboard setup hopefully solved: (do not know is this is enough ?) by editing xorg.conf and adding the missing Section Device
at the end:
Code: Select all
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc102"
Option "XkbLayout" "be"
EndSection
Code: Select all
#Special base config file used in Puppy Linux.
# **********************************************************************
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"
Load "synaptics"
# This loads the DBE extension module.
Load "dbe" # Double buffer extension
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
# This loads the font modules
# Load "type1"
# Load "freetype"
# This loads xtrap extension, used by xrandr
# Load "xtrap"
# This loads the GLX module (if present). xorg 7.4/5 need explicit disable to disable...
Disable "glx" #LOADGLX
# This loads dri module (if present). 7.4 loads it by default, have to disable...
# Load "dri" #LOADDRI
# Disable "dri"
EndSection
# **********************************************************************
# Files section. This allows default font paths to be set
# **********************************************************************
Section "Files"
# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
FontPath "/usr/share/X11/fonts/misc/"
FontPath "/usr/share/X11/fonts/Type1/"
FontPath "/usr/share/X11/fonts/TTF/"
EndSection
#
*********************************************************************
# Server flags section.
# **********************************************************************
Section "ServerFlags"
# Uncomment this to disable the <Crtl><Alt><Fn> VT switch sequence
# (where n is 1 through 12). This allows clients to receive these key
# events.
# Option "DontVTSwitch"
# Enables mode switching with xrandr
# There is a report that this can cause Xorg not to work on some
# video hardware, so default is commented-out...
# but i want to use it in xorgwizard so leave on...
Option "RandR" "on"
# With this, Xorg won't talk to HAL to add evdev devices and you'll be back
# with the old Xorg behavior (pre-7.4)...
Option "AutoAddDevices" "false"
# For no-Hal, kirk also suggests this...
# Option "AllowMouseOpenFail" "true"
# Xorg 7.4, Ubuntu Jaunty, CTRL-ALT-BACKSPACE is disabled by default...
Option "DontZap" "false"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc102"
Option "XkbLayout" "be"
EndSection
#everything past here is auto-generated by Puppy's Xorg Wizard...
#PuppyHardwareProfile=Silicon_Motion_SM720
- Attachments
-
- reportvideo.txt.gz
- (263 Bytes) Downloaded 329 times
-
- Xorg.0.log.gz
- file BEFORE adding Section Device
- (15.97 KiB) Downloaded 351 times
-
- lspci.txt.gz
- (1.35 KiB) Downloaded 351 times
-
- lsmod.txt.gz
- lsmod
- (1.26 KiB) Downloaded 317 times
-
- ddcprobe.txt.gz
- ddcprobe
- (1.65 KiB) Downloaded 334 times
Last edited by charlie6 on Sat 01 Oct 2011, 07:03, edited 9 times in total.
What is this?... an intelligence test to figure out when the next beta is out?...
B5 looks really nice and works fine too.
I guess next should be an RC.
As usually VM update and SlaXO update and fresh build was smooth.
The shutdown bug is gone in the SlaXO/vfat case (without BK's change of rc.shutdown) and updating to JWM 505 had no issues.
I have a strange bug though. Frisbee works fine in the XO-1.5 but not in the XO-1 I get "failed to set ssid" and indeed /usr/lical/Frisbee/iface is empty.
I guess something is tripped by the XO-1 wifi module.
Does not appear to be the presence of the msh interface because "ignoring" if or bring it down it does not change things. dhcpd also is fine with other connection tools.
wpa_cli or supplicant maybe.(?)
The problem is also present in B4.
The original jemimah's frisbee does not have this problem in XOpup. I guess I'll check it to see how it behaves in SlaXO...
..... No it does not work
B5 looks really nice and works fine too.
I guess next should be an RC.
As usually VM update and SlaXO update and fresh build was smooth.
The shutdown bug is gone in the SlaXO/vfat case (without BK's change of rc.shutdown) and updating to JWM 505 had no issues.
I have a strange bug though. Frisbee works fine in the XO-1.5 but not in the XO-1 I get "failed to set ssid" and indeed /usr/lical/Frisbee/iface is empty.
I guess something is tripped by the XO-1 wifi module.
Does not appear to be the presence of the msh interface because "ignoring" if or bring it down it does not change things. dhcpd also is fine with other connection tools.
wpa_cli or supplicant maybe.(?)
The problem is also present in B4.
The original jemimah's frisbee does not have this problem in XOpup. I guess I'll check it to see how it behaves in SlaXO...
..... No it does not work
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==