Suggestion?Ted Dog wrote:Still no love on my AMD ATI Acer. Black screen of empty-ness. Did boot fine from EFI with all messages.
default vmlinuz initrd=initrd.gz radeon.mode=0 pmedia=usbflash
Suggestion?Ted Dog wrote:Still no love on my AMD ATI Acer. Black screen of empty-ness. Did boot fine from EFI with all messages.
I had a similar problem in the past after updating a rolling release ISO.Ted Dog wrote: ... shell responded
... shutdown dialog worked fine.
I already put it in woof and it works well. I today released slacko-5.6.5.6 (32 bit beta) with the new welcome1stboot binary.01micko wrote:@L18L
Works . Also we need is some translations and it can go into woof-CE (32 also). (vicmz? rodin.s?)
Thanks.01micko wrote:I already put it in woof and it works well.
Code: Select all
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: welcome1stboot 140206\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2014-02-08 11:42+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: /tmp/welcome1stboot.bac.c:403
msgid ""
"\n"
"Congratulations, you are already connected to the Internet."
msgstr ""
#: /tmp/welcome1stboot.bac.c:477
msgid "...mouse-over and click the tray applets, very helpful!"
msgstr ""
#: /tmp/welcome1stboot.bac.c:407
msgid ""
"Click on the 'connect' button on the right, or icon at left of the screen "
"(one click only -- do not double-click!). You will then see some buttons for "
"choosing how you wish to connect to the Internet -- click the most "
"appropriate. It is easy..."
msgstr ""
#: /tmp/welcome1stboot.bac.c:387
msgid "Close window"
msgstr ""
#: /tmp/welcome1stboot.bac.c:415
msgid "Connect to Internet"
msgstr ""
#: /tmp/welcome1stboot.bac.c:461
msgid ""
"Explore the Menu -- see bottom-left of screen. Lots of local help is "
"available -- select Help in the menu. The local Help page also has the "
"Release Notes for this version of ${ISSUE}-- well worth checking out! When "
"you get online, the web browser home page has many more links."
msgstr ""
#: /tmp/welcome1stboot.bac.c:453
msgid "I need help!"
msgstr ""
#: /tmp/welcome1stboot.bac.c:393
msgid "Internet connection"
msgstr ""
#: /tmp/welcome1stboot.bac.c:483
msgid "Setup"
msgstr ""
#: /tmp/welcome1stboot.bac.c:507
msgid "Setup ${ISSUE}"
msgstr ""
#: /tmp/welcome1stboot.bac.c:371
msgid "This is the first time you are running ${ISSUE}!"
msgstr ""
#: /tmp/welcome1stboot.bac.c:491
msgid ""
"Want to install an upgraded video driver? Country localization? Printing? "
"Sound? Mouse? Keyboard? Click here (or 'setup' icon at top of screen):"
msgstr ""
#: /tmp/welcome1stboot.bac.c:353
msgid "Welcome"
msgstr ""
#: /tmp/welcome1stboot.bac.c:363
msgid "Welcome,"
msgstr ""
#: /tmp/welcome1stboot.bac.c:421
msgid "connect"
msgstr ""
#: /tmp/welcome1stboot.bac.c:515
msgid "setup"
msgstr ""
YesL18L wrote:Do you plan to
- install all available translations of welcome1stboot so that they can be used immediately from the beginning
NoL18L wrote:or
- offer to install a langpack as first action at first boot
?
Attached???L18L wrote:Attached file contains german translation in the momanager way.
For other translations save this to /usr/share/doc/nls/welcome1stboot/welcome1stboot.pot
01micko wrote:Attached???
Yes, discovered that! A legacy of me changing ~/.Xdefaults.Ray MK wrote:However a small moment of panic when the terminal went from yellow background with red text (good - easy to read) then stayed with yellow background but text changed to white
(bad - couldn’t read it).
Act of faith - pressed enter and prayed - all was good.
Then I succeeded with a multi-boot frugal install of Xprecise 5.7.1 retro on the same usb f2fs drive.
Used the f2fs installer in slacko64 again - very intuitive.
This is a catch all. Low RAM systems will crash if suspended from usb. That said, a test can be in place to see if there is , say, over 1GB RAM free and allow suspend on a usb install. 1GB is arbitrary, will really need to see what is safe. Don't want any data loss if it can be helped.Ray MK wrote:A small note regarding suspend / resume and slacko64.
When an f2fs is unmounted - it seems ok.
When an f2fs drive is mounted - it don’t work.
Code: Select all
# do not suspend if usb media mounted
#USBS=$(probedisk2|grep '|usb' | cut -d'|' -f1)
#for USB in $USBS
#do
#mount | grep -q "^$USB" && exit
#done