The time now is Sat 21 Apr 2018, 12:08
All times are UTC - 4 |
Author |
Message |
FeodorF

Joined: 07 Jul 2010 Posts: 228 Location: Heidelberg, Germany
|
Posted: Wed 18 Jan 2017, 01:41 Post subject:
sr0 can not be mounted - but you can boot the live-CD |
|
Drive sr0 can not be mounted - but you can boot the live-CD.
CDs and DVDs are not detected by the system as mountable.
DVD drive works fine with Quirky Xerus 8.1.6 .
Used the SlaQ live-CD for testing.
|
Back to top
|
|
 |
linuxcbon
Joined: 09 Aug 2007 Posts: 1165
|
Posted: Wed 18 Jan 2017, 11:29 Post subject:
Re: SlaQ-8.1.6-amd64.iso |
|
Quirky SlaQ 8.1.6 x86_64
FeodorF wrote: | Solution to the problem: |
I know this already, but that's not a solution, it's a manual workaround. You need to find where the bug exactly comes from in the scripts and give a real solution.
- some useless folders :
/usr/bin/lib64/ -- empty
/usr/bin/svn-tools/ -- empty
/usr/etc/ -- empty
/usr/games/ -- empty
/usr/local/share/ -- empty
/usr/lib/modules/ -- empty
- /etc/profile too complex, what is only needed is export PATH= ...
- perl can be moved to devx or is it needed somewhere ?
|
Back to top
|
|
 |
belham2
Joined: 15 Aug 2016 Posts: 1512
|
Posted: Wed 18 Jan 2017, 11:50 Post subject:
|
|
Ok, this is to follow-up for those of you that want to 'frugal' install this latest Quirky-Slaq/Xenial and also have the ability to have a savefile recognized during boot. Currently, this latest edition (this goes for QuirkyXenial too) cannot see the savefile you created on the 1st frugal boot, and thus won't load it.
The problem is in the init script, which gets loaded from the initrd.q. This is how you solve it for now, until Barry can take a deeper look at why the latest changes in this 'init' script caused the problem:
1) It does not matter if you are booting into Slaq/Xenial for the 1st time, or if you've already created a savefile and are stumped why it isn't loading on subsequent boots.
2) go into your /mnt (or your desktop shortcut, if it exists) and get to where the vmlinuz and initrd.q are located (they should be un-mounted)
3) Left-click on the initrd.q (it has the black& white puppyface)
4) Up will pop a yellow dialog box. It says:
initrd.q: expand?
Do you want to open up initrd.q, and optionally edit it?
(click yes here)
5) Then a mint green dialog box pops-up. It tells you it opened/epxpanded the initrd.q to: /root/initrd-expanded
Also, it is helpful if you leave open the file manager above that still shows the black&white initrd.q file. We're going to need it in a minute.
(click 'ok' in this mint green dialog box)
6) up pops Rox with the expanded initrd.q. Right-click on the "init" file, and choose "open-as-text"
(we are going to edit this file)
7) once it is open in Geany, scrolldown just barely, near the top, and you will see the following lines (without the # comment outs):
hwclock --hctosys --localtime #160427 from util-linux. assuming hw clock set to local
if grep -qw aufs /proc/filesystems; then
LAYERFS='aufs'
RO='=ro'
else
LAYERFS='overlay'
RO=''
fi
(put a "#" in front of each and every one of these lines, so the init script will ignore them).
Now, go back to that Rox open window (we left it open) I mentioned to keep open above.
9) Left-click on the black&white puppy 'initrd.q' file
10) it will ask you if you want to save your edits to the initrd.q file:
initrd.q: update?
A CPIO-archive........./initrd.q?
(Click "Yes")
11) up will pop another mint-green dialog box saying:
initrd.q: success
File.........initrd-expanded.
(Click "Ok")
12) up pops a yellow dialog box:
initrd.q: finished
Do you want to delete /root/initrd.q-expanded? If in doubt, please choose Yes
(Defintely choose 'Yes' here)
13) That's it!! Close out any remaining Rox windows open, and either go about setting up your Quirky and the 'savefile', or just reboot (assuming you already have a 'savefile') and you will find that upon booting up, Quirky now sees your previously created 'savefile'.
***Please note: this exact same procedure will/should work in QuirkyXenial, as the inits are the same****
P.S. Barry, I just played it safe and had them comment out both the "hwclock" change you made, and also the offending "layer/aufs" section, which seems by itself to be the problem causing both QuirkyXenial and QuirkySlaq to not see any savefile created after first boot. I tested, and once this stuff is commented out, my savefile files (on a frugal install) are now being seen at boot and loading up perfectly.
Last edited by belham2 on Wed 18 Jan 2017, 12:10; edited 2 times in total
|
Back to top
|
|
 |
Billtoo

Joined: 07 Apr 2009 Posts: 3421 Location: Ontario Canada
|
Posted: Wed 18 Jan 2017, 11:56 Post subject:
|
|
@belham2
I sent you a pm regarding redshift.
|
Back to top
|
|
 |
belham2
Joined: 15 Aug 2016 Posts: 1512
|
Posted: Wed 18 Jan 2017, 12:18 Post subject:
|
|
Billtoo wrote: | @belham2
I sent you a pm regarding redshift. |
Thanks Bill!
|
Back to top
|
|
 |
belham2
Joined: 15 Aug 2016 Posts: 1512
|
Posted: Wed 18 Jan 2017, 12:52 Post subject:
Re: SlaQ-8.1.6-amd64.iso |
|
linuxcbon wrote: | Quirky SlaQ 8.1.6 x86_64
FeodorF wrote: | Solution to the problem: |
I know this already, but that's not a solution, it's a manual workaround. You need to find where the bug exactly comes from in the scripts and give a real solution.
- some useless folders :
/usr/bin/lib64/ -- empty
/usr/bin/svn-tools/ -- empty
/usr/etc/ -- empty
/usr/games/ -- empty
/usr/local/share/ -- empty
/usr/lib/modules/ -- empty
- /etc/profile too complex, what is only needed is export PATH= ...
- perl can be moved to devx or is it needed somewhere ? |
Hi Linuxcbon (and FeodorF)!
Hey, if you try my solution above (for the 'frugal' install savefile problem), somehow it not only cured the 'savefile' problem, but guess what came back to the quirky traybar? Everything (network, retrovol, storage, Bluetooth) I'm trying to parse what Barry did with the LAYER notations in the "init' script....something isn't making sense with them.....at least not yet Going to have to wait for him to chime in so we can see his thought process behind it.
|
Back to top
|
|
 |
belham2
Joined: 15 Aug 2016 Posts: 1512
|
Posted: Wed 18 Jan 2017, 13:04 Post subject:
|
|
Also, if you're having problems with Seamonkey, to fix it, try the following:
1) open /usr/bin/seamonkey (the script for 'spot')
2) in the 2nd line you'll see [ -f..........yada yada yada....]
3) In this 2nd line, remove the x86_64_linux-gnu. I'm not even sure how this got in there, as Seamonkey is not even located there. Just make sure that 2nd part of the line looks like this:
... && ln -snf /usr/lib/seamonkey/seamonkey /usr/bin/seamonkey.bin
Check and make sure the link is working too. If not, go back to the /usr/lib seamonkey shortcut, open it, and drag 'seamonkey' back over to /usr/bin and relative symlink it.
After making these changes, any opening and closing of Seamonkey should be ok.
Hope this helps.
|
Back to top
|
|
 |
FeodorF

Joined: 07 Jul 2010 Posts: 228 Location: Heidelberg, Germany
|
Posted: Fri 20 Jan 2017, 01:59 Post subject:
ReRe: SlaQ-8.1.6-amd64.iso Subject description: /root/.jwmrc |
|
linuxcbon wrote: | Quirky SlaQ 8.1.6 x86_64
FeodorF wrote: | Solution to the problem: |
I know this already, but that's not a solution, it's a manual workaround. You need to find where the bug exactly comes from in the scripts and give a real solution.
|
Well, it is not even a manual workaround!
It is good for nothing.
linuxcbon, have you ever mounted the q.sfs file of the SlaQ-8.1.6-amd64.iso and looked at /root/.jwmrc?
Well, this jwmrc runs from line 1 through 413.
The add up we see from line 414 through 824 is a duplicate of line 1 through 413.
What's strange about it? The lines 34, 55 and 74 are not duplicated.
Looks like that the layered filesystem is not o.k. or the i-node pointer.
|
Back to top
|
|
 |
don570

Joined: 10 Mar 2010 Posts: 4987 Location: Ontario
|
Posted: Thu 02 Feb 2017, 20:53 Post subject:
|
|
I was able to run the graphics app nathive to run in 64 bit xersus
First install python2 addons
https://drive.google.com/file/d/0B672gIlbo7iVcDlaUkh3RmkwR1E/view?usp=sharing
Then download and install the app
http://www.nathive.org/dl/nathive_0.924-1_amd64.deb
Then run in console
---------------------------------------------------------------------------
|
Back to top
|
|
 |
gcav

Joined: 25 May 2012 Posts: 73 Location: Ontario
|
Posted: Sat 04 Feb 2017, 13:32 Post subject:
nathive in SlaQ and python |
|
I see you mentioned Xerus, but wanted to try it in SlaQ. yet have issues with pygtk. what packages are needed for slaq Have not played with python for a while.
any ideas?
gcav
|
Back to top
|
|
 |
don570

Joined: 10 Mar 2010 Posts: 4987 Location: Ontario
|
Posted: Sat 04 Feb 2017, 16:59 Post subject:
|
|
pygtk is difficult to compile.
You first must have all the dev files for python installed.
nathive app isn't worth the trouble to try to do it.
_______________________________________
|
Back to top
|
|
 |
linuxcbon
Joined: 09 Aug 2007 Posts: 1165
|
Posted: Tue 07 Feb 2017, 12:39 Post subject:
|
|
OUT OF TOPIC
Hi Barry,
for a new cheap laptop, what it should have, in my opinion :
- 4 GB RAM (because 2GB laptops are at around the same price)
- USB 3.0
- Bluethooth 4.1 or 4.0
- card reader : micro SD, micro SDHC, micro SDXC (maybe not important)
- hard disk : eMMC 32GB at least
After some quick search :
- ASUS EeeBook L200HA-FD0093T blue
It doesnt have touch screen.
There is better but more expensive. Let me know what you think.
Cheers, linuxcbon
Last edited by linuxcbon on Thu 09 Feb 2017, 13:01; edited 1 time in total
|
Back to top
|
|
 |
don570

Joined: 10 Mar 2010 Posts: 4987 Location: Ontario
|
Posted: Wed 08 Feb 2017, 20:43 Post subject:
|
|
ASUS EeeBook L200HA-FD0093T
Make sure that it is running a 64 bit version of windows,
since there are a few 32bit computers (using UEFI) that aren't very
friendly to Linux
_______________________________________________
|
Back to top
|
|
 |
Sage
Joined: 04 Oct 2005 Posts: 5370 Location: GB
|
Posted: Thu 09 Feb 2017, 03:42 Post subject:
|
|
Quote: | ASUS EeeBook L200HA-FD0093T |
Check reviews carefully. Have the keys stopped falling off? Remember this will be an heavily used k/b!
|
Back to top
|
|
 |
linuxcbon
Joined: 09 Aug 2007 Posts: 1165
|
Posted: Thu 09 Feb 2017, 12:31 Post subject:
|
|
Hi,
I never trust users reviews. One example : last time I bought my smartphone, the company had put many fake good reviews on the internet, so I thought it was good. Fake good reviews are very used by companies marketing crews. They created one time use accounts just to write one fake good review... Now I don't trust any review, except professional reviews from serious tech newspapers.
About that particular laptop :
- it doesn't have touch screen.
- it is sold with windows 10 64 bits.
- Asus has excellent reputation for laptops (Toshiba and Lenovo too).
- it is new so it doesn't have many reviews.
- not sure if compatible with linux ??
Cheers
|
Back to top
|
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You can download files in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|