Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - hughtmccullough

Pages: [1] 2
1
wattOS R8 / Re: Hibernate after lid closing
« on: April 17, 2015, 11:09:05 AM »
I'm a bit late replying here.  Maybe you have already solved it.

Just to be clear, though, you don't need to use the XFCE desktop to use the power manager.  You say you are using R8 LXDE 32 bit.  That's what I have and the XFCE power manager was installed at the initial installation and is working with my LXDE desktop.  If I right-click on the battery monitor icon and select "Preferences" it brings up the dialogue that madjo refers to.

So, you can check if the power manager is installed in Synaptic Package Manager.  It is called xfce4-power-manager.  If it isn't installed (did you remove it?) then just do as madjo says.

Does your bottom panel have the system tray included in it?  You can check this by right-clicking in the panel, then "Panel Settings" and then the "Panel Applets" tab.  Add the system tray if it isn't there.

If you want the power manager to appear in the main menu, then you need to edit the desktop file, /usr/share/applications/xfce4-power-manager-settings.desktop.  Remove or comment out the line that says "OnlyShowIn=XFCE;".  It will then appear in the Preferences menu as "Power Manager".

2
wattOS R9 / Re: R9 Information
« on: March 06, 2015, 06:15:01 PM »
blaze, thanks.

Where do I get Debian Jessie LXDE/Openbox?  I haven't been able to find this anywhere.  Do I have to install another version of Debian and then add LXDE as a package?  I have read information about that but it seems that it takes a lot of setting up.  Is there a small/core distribution of Debian Jessie like WattOS or just the full bloat?  What is the best way to go?

3
wattOS R9 / Re: R9 Information
« on: March 05, 2015, 05:33:40 PM »
The reason I recently put a LOT of effort into getting WattOS R8 working was because of compatibility problems I was having with Ubuntu.  Going back to the WattOS Debian base got rid of those and I still had a nice lightweight LXDE/Openbox desktop.  I have read that upgrading from Wheezy to Jessie is normally a fairly painless process but I assume it won't work if I try it for the reasons mentioned above, i.e. the "deviation form Debian standard".  The one upgrade I really need is libc6 as more and more software is demanding v2.14 and above, some 2.17, and the current WattOS repositories only support version 2.13, even in the wheezy backports.  To say that I am disappointed with the idea of going back to Ubuntu would be putting it mildly but I do realise the world doesn't revolve around me.

It is a real shame that the diversity within Linux is starting to cause a Tower-of-Babel effect where if you move out of your cosy little corner within the Linux world you run into all sorts of issues.  Diversity is more and more becoming fragmentation.

4
wattOS R8 / Re: LibreOffice 4?
« on: March 05, 2015, 05:07:24 PM »
I'm sorry I've been away from this for a few days but it maybe deserves a few replies:

Maroman, thanks.  When I open that window, I don't get the middle of the three versions that you get.  So, I'm not sure what is different about my system.  Like you I am a little sad that we still can't completely do without Microsoft.

leenie, thanks to you too.  That is the one I was referring to in my second post above.  As I said then, unfortunately it doesn't support graphs and charts in spreadsheets and that is quite important to me.  However, for those for whom that is not a problem, in my experience, file import/export compatibility with MSO formats is very good indeed.

5
wattOS R8 / Re: LibreOffice 4?
« on: February 25, 2015, 11:18:45 PM »
Maroman,  I maybe wasn't clear in what I said.  I can get:

v3.5.4 (stable)
v4.3.3 (wheezy-backports)

Just those two - I don't see any other older version.

I take your point about v3.5 being good.  I actually still have it installed on WattOS (I was able to test a couple of v4.x on different distributions I have available but don't use very much).  As the formatting isn't significantly better in v4.x, there isn't so much to be gained from upgrading.

cheiron,  that's interesting information but if I really need to use MO, I would probably be as well using it on a Windows 7 installation I have.  I did once try Wine but it was a bad experience - too many bugs as you mention.

6
wattOS R8 / Re: LibreOffice 4?
« on: February 25, 2015, 05:04:04 PM »
My repositories only have one of the two old versions you mention.  However, thanks for your help - they do have the new one!  I didn't know about that trick.

I also spent a bit of time investigating the differences between Libreoffice and AOO.

It seems that the main trade-offs are that Libreoffice can be a bit more buggy than AOO but has newer features and is a bit more compatible with Microsoft Office.  Unfortunately, even Libreoffice 4 still isn't very good at importing Microsoft formatted documents.  I have had all sorts of formatting problems where the original formatting of the document gets screwed up by Libreoffice.  In the most recent, a spreadsheet had the row headers overlapping on top of the of the leftmost column.  This meant that the row headers and the cells in the first column were fighting each other to be displayed.  I was able to sort out the problem by first of all opening the document in WPS (aka Kingsoft Office), re-saving it and then opening it in Libreoffice but that is a major nuisance.  WPS isn't perfect either because it doesn't draw charts and graphs.

Those people who say it is easy to get a Microsoft Office compatible office suite in Linux need to stop marketing and get in touch with the real world.  The Libreoffice empire is put to shame by a very small WPS team!


7
wattOS R8 / LibreOffice 4?
« on: February 22, 2015, 10:43:56 PM »
The version of LibreOffice available in the repositories set up for WattOS R8 is 3.5.4 (in my installation anyway).  This is now rather old.  Is there a way of safely installing LibreOffice 4?  Do I have to wait for R9 or some other (Debian?) milestone to be able to get v4?

8
wattOS R8 / Re: nvidia driver for FX2700M
« on: February 17, 2015, 01:22:20 PM »
leenie, I had already discovered the mesa package and that brought up the direct rendering driver as you say.  Maybe it's a little hidden in my last post.  It won't give me CUDA though when I need it later on.  I have an Epson c900 which so far has worked perfectly in the 32 bit version of WattOS but refuses to install in the 64 bit version.  The packages all complain about missing dependencies, even though I have added i386 as a foreign architecture.  It may be that I have to rebuild the .deb packages or something but I haven't a clue where to start with that.

chieron, Thanks.  I think I understand now what you meant.  I was actually trying to use Synaptic Package Manager using the Debian site I referred to for information to determine what packages to download and in which order.  I just couldn't find the right one for nvidia-kernel-dkms.  How do I find the "system updates (proprietary drivers)" that you refer to? 

9
wattOS R8 / Re: nvidia driver for FX2700M
« on: February 16, 2015, 12:03:41 PM »
Cheiron,  Your message is a little confusing.  I had actually asked in my post about downloading the proprietary nvidia drivers but you seem to be suggesting I should use Nouveau, the open source driver.  Is this correct?

If not, then the questions in my original post still stand.

If so, then I did some more research on Nouveau and found that I needed to downloaded the mesa package.  This now shows up in hardinfo.  However, the fpu raytracing benchmark remains as poor as ever.  It is possible that this is a function of the benchmark and that complicates things a little.

I may want to use the CUDA facility of the graphics card and the Nouveau driver doesn't support this.  So, I think I will park this all for now and come back to it when I want to make serious use of the GPU.

Your sting in the tail could be a show stopper for WattOS.  If the 686 pae version is likely to cause problems, then I am left with no workable option:

1) If I use the 64 bit version, I can't get my printer to work as the 32 bit driver doesn't seem to recognise the i386 multi-architecture libc6 libraries.

2) If I use the non-pae 32 bit version, my cpu performance is crippled and I only have access to 3/4 of my RAM.

3) If I continue with the pae version, you are saying that I may experience other problems.

ergo, there is no solution...


10
wattOS R8 / nvidia driver for FX2700M
« on: February 14, 2015, 11:59:16 PM »
Taking Cheiron at his word, I am hoping that someone can help me get started with installing the nvidia driver for the FX2700M card.

A bit of background first:

I have now got WattOS 32 bit running stably on my HP 8730w, after a lot of effort.  I tried some benchmarks to check that things were more or less right.  The first thing I noticed was that, compared to LXLE 64 bit, some of the benchmarks were twice as slow.  I am using the 32 bit version of WattOS because I couldn't get my printer driver to play with the 64 bit version.  I tried loading the 686-pae kernel and this brought most of the benchmarks more or less into line with LXLE, presumably because it was using the other core of my core duo processor.  So far, so good.  The one exception was the FPU raytracing benchmark (part of the hardinfo package).  It was only running at about a quarter of the speed that I achieved on LXLE.  I still have the 64 bit version of WattOS installed, that I abandoned after failing to set up the printer driver.  This gave me similar performance to LXLE.  On exploring further I found that the Nouveau driver in WattOS 32 bit didn't seem to be recognising the graphics card and wasn't doing "direct rendering".  I believe that the FPU raytracing benchmark uses the GPU if it can and hence the difference.  That left me with two options - get Nouveau working or load the non-free nvidia driver.  I have read elsewhere that the nvidia driver is much better, particularly for 3D and CUDA, and decided that would be worth trying.

The nvidia web site says the version 340 driver is the one for my graphics card.  It also says that rather than follow their rather convoluted installation process I may be better using the one for my distro as it could manage a lot of the interactions.  I had a look in Synaptic Package Manager and, sure enough, there are a lot of nvidia driver packages.  I then had to guess what package to try to install (I have cloned the partition in case I mess things up completely).  A likely candidate seemed to be the nvidia version 340 binary kernel module for my 686-pae kernel.  However, this came up as broken.  I did a more specific search for nvidia-driver and the only one that came up was the version 304 legacy driver.

This site looked promising:
https://wiki.debian.org/NvidiaGraphicsDrivers

However, my system doesn't recognise the aptitude command.  I was able to load the linux headers for my kernel in Synaptic Package Manager but got stuck trying to do the next line:
aptitude -t wheezy-backports -r install nvidia-kernel-dkms

Synaptic Package Manager doesn't seem to have an nvidia-kernel-dkms for version 340.  It only does one for version 304 and some other legacy ones.  Is that why the kernel module for version 340 came up as broken?

Any help on where to go next, or an explanation of how this all actually works, would be appreciated.

11
wattOS R8 / Re: SOLVED - WattOS freezes near end of boot sequence + wireless disabled after boot
« on: February 13, 2015, 03:57:38 PM »
Planet Watt is a very lonely place.  I have wandered around for hours and, apart from a brief glimpse of Biff, I have seen no one.  The terrain is rough and you have a lot of hills to climb to get anywhere.  It takes a lot of tenacity to keep going.

I eventually found a work-around for the wireless problem.  Continuing my comparison with LMDE (which just works!) I quickly came to the conclusion that the bit about modem-manager was a red herring.  The next line in the LMDE syslog was, "WiFi now enabled by radio killswitch".  On investigating this further I found that the RF kill switches and NetworkManager weren't interacting properly with each other.  The platform RF kill switch was set to a soft block and this set the phy0 RF kill switch to a hard block so that NetworkManager gave up.  The cludge (it isn't really a solution) was to add a line to /etc/rc.local: "rfkill unblock all" (first I had to install the rfkill tool).  Now it seems to work, although so far I only have a sample size of 2.

12
wattOS R8 / Re: WattOS freezes near end of boot sequence
« on: February 09, 2015, 12:21:54 PM »
I'm still stuck.

As far as I can see, the information Biff asked me to post looks fine.  I have been comparing the WattOS start up sequence with my Mint Debian one (which works perfectly) to see if I can spot any discrepancies.  The first and third of the listings in the previous post are identical and the middle one seems to be done a different way.

I tried looking at the syslog file to see what it would tell me.  Now, although it might as well be written in Latin as far as my knowledge is concerned, I can still spot differences.  I tried to pick out all of the wireless related lines by using:

cat /var/log/syslog | grep 'wifi\|wlan0\|NetworkManager\|WiFi\|80211\|Ifupdown\|wpa\|Wireless\|wireless\|rfkill\|radio'

If I missed out any important key words, please let me know.

This is the output for a boot sequence:

Code: [Select]
Feb  9 09:55:20 8730w kernel: [    6.955508] cfg80211: Calling CRDA to update world regulatory domain
Feb  9 09:55:20 8730w kernel: [    7.212699] Intel(R) Wireless WiFi driver for Linux, in-tree:
Feb  9 09:55:20 8730w kernel: [    7.212782] iwlwifi 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control
Feb  9 09:55:20 8730w kernel: [    7.212823] iwlwifi 0000:03:00.0: irq 49 for MSI/MSI-X
Feb  9 09:55:20 8730w kernel: [    7.801081] iwlwifi 0000:03:00.0: firmware: direct-loading firmware iwlwifi-5000-5.ucode
Feb  9 09:55:20 8730w kernel: [    7.801255] iwlwifi 0000:03:00.0: loaded firmware version 8.83.5.1 build 33692 op_mode iwldvm
Feb  9 09:55:20 8730w kernel: [    8.751428] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUG disabled
Feb  9 09:55:20 8730w kernel: [    8.751432] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUGFS disabled
Feb  9 09:55:20 8730w kernel: [    8.751433] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEVICE_TRACING disabled
Feb  9 09:55:20 8730w kernel: [    8.751435] iwlwifi 0000:03:00.0: Detected Intel(R) Ultimate N WiFi Link 5300 AGN, REV=0x24
Feb  9 09:55:20 8730w kernel: [    8.751516] iwlwifi 0000:03:00.0: L1 Disabled - LTR Disabled
Feb  9 09:55:20 8730w kernel: [    8.751899] iwlwifi 0000:03:00.0: RF_KILL bit toggled to disable radio.
Feb  9 09:55:20 8730w kernel: [    8.827612] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs'
Feb  9 09:55:20 8730w kernel: [   10.121395] cfg80211: World regulatory domain updated:
Feb  9 09:55:20 8730w kernel: [   10.121398] cfg80211:  DFS Master region: unset
Feb  9 09:55:20 8730w kernel: [   10.121399] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
Feb  9 09:55:20 8730w kernel: [   10.121401] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
Feb  9 09:55:20 8730w kernel: [   10.121403] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
Feb  9 09:55:20 8730w kernel: [   10.121404] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
Feb  9 09:55:20 8730w kernel: [   10.121406] cfg80211:   (5170000 KHz - 5250000 KHz @ 160000 KHz), (N/A, 2000 mBm), (N/A)
Feb  9 09:55:20 8730w kernel: [   10.121408] cfg80211:   (5250000 KHz - 5330000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
Feb  9 09:55:20 8730w kernel: [   10.121409] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
Feb  9 09:55:20 8730w kernel: [   10.121411] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
Feb  9 09:55:20 8730w kernel: [   10.121413] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
Feb  9 09:55:24 8730w NetworkManager[3095]: <info> NetworkManager (version 0.9.4.0) is starting...
Feb  9 09:55:24 8730w NetworkManager[3095]: <info> Read config file /etc/NetworkManager/NetworkManager.conf
Feb  9 09:55:24 8730w NetworkManager[3095]:    SCPlugin-Ifupdown: init!
Feb  9 09:55:24 8730w NetworkManager[3095]:    SCPlugin-Ifupdown: update_system_hostname
Feb  9 09:55:24 8730w NetworkManager[3095]:    SCPluginIfupdown: management mode: unmanaged
Feb  9 09:55:24 8730w NetworkManager[3095]:    SCPlugin-Ifupdown: devices added (path: /sys/devices/pci0000:00/0000:00:19.0/net/eth0, iface: eth0)
Feb  9 09:55:24 8730w NetworkManager[3095]:    SCPlugin-Ifupdown: device added (path: /sys/devices/pci0000:00/0000:00:19.0/net/eth0, iface: eth0): no ifupdown configuration found.
Feb  9 09:55:24 8730w NetworkManager[3095]:    SCPlugin-Ifupdown: devices added (path: /sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/net/wlan0, iface: wlan0)
Feb  9 09:55:24 8730w NetworkManager[3095]:    SCPlugin-Ifupdown: device added (path: /sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/net/wlan0, iface: wlan0): no ifupdown configuration found.
Feb  9 09:55:24 8730w NetworkManager[3095]:    SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/lo, iface: lo)
Feb  9 09:55:24 8730w NetworkManager[3095]:    SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found.
Feb  9 09:55:24 8730w NetworkManager[3095]:    SCPlugin-Ifupdown: end _init.
Feb  9 09:55:24 8730w NetworkManager[3095]: <info> Loaded plugin ifupdown: (C) 2008 Canonical Ltd.  To report bugs please use the NetworkManager mailing list.
Feb  9 09:55:24 8730w NetworkManager[3095]: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.
Feb  9 09:55:24 8730w NetworkManager[3095]:    Ifupdown: get unmanaged devices count: 0
Feb  9 09:55:24 8730w NetworkManager[3095]:    SCPlugin-Ifupdown: (138347760) ... get_connections.
Feb  9 09:55:24 8730w NetworkManager[3095]:    SCPlugin-Ifupdown: (138347760) ... get_connections (managed=false): return empty list.
Feb  9 09:55:24 8730w NetworkManager[3095]:    keyfile: parsing Wireless connection 1 ...
Feb  9 09:55:25 8730w NetworkManager[3095]:    keyfile:     read connection 'Wireless connection 1'
Feb  9 09:55:25 8730w NetworkManager[3095]:    Ifupdown: get unmanaged devices count: 0
Feb  9 09:55:25 8730w NetworkManager[3095]: <info> trying to start the modem manager...
Feb  9 09:55:25 8730w NetworkManager[3095]: <info> monitoring kernel firmware directory '/lib/firmware'.
Feb  9 09:55:25 8730w NetworkManager[3095]: <info> monitoring ifupdown state file '/run/network/ifstate'.
Feb  9 09:55:25 8730w NetworkManager[3095]: <info> found WiFi radio killswitch rfkill3 (at /sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/ieee80211/phy0/rfkill3) (driver (unknown))
Feb  9 09:55:25 8730w NetworkManager[3095]: <info> found WiFi radio killswitch rfkill0 (at /sys/devices/platform/hp-wmi/rfkill/rfkill0) (driver hp-wmi)
Feb  9 09:55:25 8730w NetworkManager[3095]: <info> WiFi disabled by radio killswitch; enabled by state file
Feb  9 09:55:25 8730w NetworkManager[3095]: <info> WWAN enabled by radio killswitch; enabled by state file
Feb  9 09:55:25 8730w NetworkManager[3095]: <info> WiMAX enabled by radio killswitch; enabled by state file
Feb  9 09:55:25 8730w NetworkManager[3095]: <info> Networking is enabled by state file
Feb  9 09:55:25 8730w NetworkManager[3095]: <warn> failed to allocate link cache: (-12) Object not found
Feb  9 09:55:25 8730w NetworkManager[3095]: <info> (eth0): carrier is OFF
Feb  9 09:55:25 8730w NetworkManager[3095]: <info> (eth0): new Ethernet device (driver: 'e1000e' ifindex: 2)
Feb  9 09:55:25 8730w NetworkManager[3095]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/0
Feb  9 09:55:25 8730w NetworkManager[3095]: <info> (eth0): now managed
Feb  9 09:55:25 8730w NetworkManager[3095]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Feb  9 09:55:25 8730w NetworkManager[3095]: <info> (eth0): bringing up device.
Feb  9 09:55:25 8730w NetworkManager[3095]: <info> (eth0): preparing device.
Feb  9 09:55:25 8730w NetworkManager[3095]: <info> (eth0): deactivating device (reason 'managed') [2]
Feb  9 09:55:25 8730w NetworkManager[3095]: <info> Added default wired connection 'Wired connection 1' for /sys/devices/pci0000:00/0000:00:19.0/net/eth0
Feb  9 09:55:25 8730w NetworkManager[3095]: <info> (wlan0): using nl80211 for WiFi device control
Feb  9 09:55:25 8730w NetworkManager[3095]: <info> (wlan0): new 802.11 WiFi device (driver: 'iwlwifi' ifindex: 3)
Feb  9 09:55:25 8730w NetworkManager[3095]: <info> (wlan0): exported as /org/freedesktop/NetworkManager/Devices/1
Feb  9 09:55:25 8730w NetworkManager[3095]: <info> (wlan0): now managed
Feb  9 09:55:25 8730w NetworkManager[3095]: <info> (wlan0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Feb  9 09:55:25 8730w NetworkManager[3095]: <info> (wlan0): bringing up device.
Feb  9 09:55:25 8730w NetworkManager[3095]: <info> (wlan0): deactivating device (reason 'managed') [2]
Feb  9 09:55:25 8730w NetworkManager[3095]: <info> modem-manager is now available

When I did the same in Mint Debian, the output was very similar and what looked to me like a key difference was that the Mint Debian log had no mention of modem-manager.  As you can see from the above, just after the "parsing of Wireless connection 1", there is a line that says "trying to start the modem manager".  This is missing in the Mint Debian log.  Also, at this point, Mint Debian picked up the IP addresses for the computer and the internet gateway wheres WattOS didn't.  The last line of the listing above says, "modem-manager is now available" and, at this point, the process comes to an abrupt stop.

Is this significant?  I don't know what it means or how to do anything about it.  Can someone tell me if I am on the right lines and where to go next?

13
wattOS R8 / Re: WattOS freezes near end of boot sequence
« on: February 06, 2015, 12:11:38 PM »
Biff,

Thanks for getting back to me.

Grub seems to have settled.  After the latest update-grub I have had consistently successful boot performance except for the wireless issue.

Wireless:

Rebooting has the same problem as cold boot, i.e. wireless is disabled after booting up but clicking "enable wireless" starts it.

/var/lib/NetworkManager//NetwrokManager.state:
Code: [Select]
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true

/etc/network/interfaces
Code: [Select]
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
# allow-hotplug eth0
# iface eth0 inet dhcp

/etc/NetworkManager/nm-system-settings.conf doesn' exist.

The only file in there was /etc/NetworkManager/NetworkManager.conf:
Code: [Select]
[main]
plugins=ifupdown,keyfile

[ifupdown]
managed=false

I didn't have to change any "false" settings as they were all already set to "true".

14
wattOS R8 / Re: WattOS freezes near end of boot sequence
« on: February 05, 2015, 03:58:34 PM »
I would still like some help on this but things have moved on a bit and the following is an update.

I should have said that I have a number of partitions on the hd with a few different operating systems.  Grub2 is run from a partition (logical) that runs LXLE.  There is a primary partition with Windows 7.  The extended partition includes two other logical partitions that are set up for Linux Mint Debian and WattOS.  There is a swap partition and another, empty logical partition.

I re-installed WattOS and performed another update-grub from the LXLE installation and WattOS became bootable.  However, the boot process isn't reliable.  All of the other operating systems consistently boot up correctly but WattOS has hiccups.  Sometimes it boots fine and other times it stalls at the line, "Booting the kernel".  Also, there still seems to be a problem with the wireless booting up and I'm not sure if it is related.  Every time that WattOS actually boots up, the wireless is disabled.  If I open Network Manager from the icon and click "enable wireless", it starts up fine but I can't get it to start during boot.  The flags for automatic start and use by all users are both ticked in the Network Manager screen.

I would really like to get WattOS going well. I like the fact that LMDE runs Debian and I like the openbox/LXDE combination of LXLE.  It seems that WattOS would give me the best of both worlds.  From what I have read, I should be able to boot up multiple operating systems this way and the wireless should be enabled during the boot sequence.  I'm not sure if these are related or separate issues but, if anyone can tell me what to do next with either I would much appreciate it. or let me know if you need more information (I'm not sure what all is relevant).

If it helps, this is the relevant bit out of grub.cfg:

Code: [Select]
# menuentry 'Debian GNU/Linux (7.8) (on /dev/sda8)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-8e0921b6-b15f-4763-9652-27552bd5f36a' {
menuentry 'Debian GNU/Linux (7.8)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-8e0921b6-b15f-4763-9652-27552bd5f36a' {
insmod part_msdos
insmod ext2
set root='hd0,msdos8'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos8 --hint-efi=hd0,msdos8 --hint-baremetal=ahci0,msdos8  8e0921b6-b15f-4763-9652-27552bd5f36a
else
  search --no-floppy --fs-uuid --set=root 8e0921b6-b15f-4763-9652-27552bd5f36a
fi
linux /boot/vmlinuz-3.13-0.bpo.1-amd64 root=UUID=8e0921b6-b15f-4763-9652-27552bd5f36a ro quiet
initrd /boot/initrd.img-3.13-0.bpo.1-amd64
}
submenu 'Advanced options for Debian GNU/Linux (7.8)' $menuentry_id_option 'osprober-gnulinux-advanced-8e0921b6-b15f-4763-9652-27552bd5f36a' {
menuentry 'wattOS-R8, with Linux 3.13-0.bpo.1-amd64' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-3.13-0.bpo.1-amd64--8e0921b6-b15f-4763-9652-27552bd5f36a' {
insmod part_msdos
insmod ext2
set root='hd0,msdos8'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos8 --hint-efi=hd0,msdos8 --hint-baremetal=ahci0,msdos8  8e0921b6-b15f-4763-9652-27552bd5f36a
else
  search --no-floppy --fs-uuid --set=root 8e0921b6-b15f-4763-9652-27552bd5f36a
fi
linux /boot/vmlinuz-3.13-0.bpo.1-amd64 root=UUID=8e0921b6-b15f-4763-9652-27552bd5f36a ro quiet
initrd /boot/initrd.img-3.13-0.bpo.1-amd64
}
menuentry 'wattOS-R8, with Linux 3.13-0.bpo.1-amd64 (recovery mode)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-3.13-0.bpo.1-amd64-root=UUID=8e0921b6-b15f-4763-9652-27552bd5f36a ro single-8e0921b6-b15f-4763-9652-27552bd5f36a' {
insmod part_msdos
insmod ext2
set root='hd0,msdos8'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos8 --hint-efi=hd0,msdos8 --hint-baremetal=ahci0,msdos8  8e0921b6-b15f-4763-9652-27552bd5f36a
else
  search --no-floppy --fs-uuid --set=root 8e0921b6-b15f-4763-9652-27552bd5f36a
fi
linux /boot/vmlinuz-3.13-0.bpo.1-amd64 root=UUID=8e0921b6-b15f-4763-9652-27552bd5f36a ro single
initrd /boot/initrd.img-3.13-0.bpo.1-amd64
}
}

15
wattOS R8 / SOLVED - WattOS freezes near end of boot sequence + wireless disabled after boot
« on: February 02, 2015, 04:14:01 PM »
I have just installed WattOS 64bit LXDE.  It booted up fine and I
1) set up the wireless and achieved internet access
2) made changes to synaptics touchpad to allow single tap = left click
3) changed the keyboard to gb. 
Now it freezes during boot.  Instead of going to the desktop, a blinking cursor appears at the top left of an otherwise blank screen.  At this point a short press of the power button performs the halt and power off sequence.
It seems to stop somewhere around the network start up.  I managed to get at the syslog by booting on a different partition and mounting the WattOS partition.  The last bit of it is as follows:

Feb  2 16:02:44 8730w NetworkManager[3451]: <info> NetworkManager (version 0.9.4.0) is starting...
Feb  2 16:02:44 8730w NetworkManager[3451]: <info> Read config file /etc/NetworkManager/NetworkManager.conf
Feb  2 16:02:44 8730w udev-configure-printer: add /module/lp
Feb  2 16:02:44 8730w kernel: [   16.180833] lp0: using parport0 (interrupt-driven).
Feb  2 16:02:44 8730w udev-configure-printer: Failed to get parent
Feb  2 16:02:44 8730w udev-configure-printer: add /devices/pnp0/00:08/printer/lp0
Feb  2 16:02:44 8730w udev-configure-printer: Failed to get parent
Feb  2 16:02:44 8730w dbus[3072]: [system] Activating service name='org.freedesktop.PolicyKit1' (using servicehelper)
Feb  2 16:02:44 8730w kernel: [   16.320856] ppdev: user-space parallel port driver
Feb  2 16:02:45 8730w polkitd[3515]: started daemon version 0.105 using authority implementation `local' version `0.105'
Feb  2 16:02:45 8730w dbus[3072]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Feb  2 16:02:45 8730w NetworkManager[3451]:    SCPlugin-Ifupdown: init!
Feb  2 16:02:45 8730w NetworkManager[3451]:    SCPlugin-Ifupdown: update_system_hostname
Feb  2 16:02:45 8730w NetworkManager[3451]:    SCPluginIfupdown: guessed connection type (eth0) = 802-3-ethernet
Feb  2 16:02:45 8730w NetworkManager[3451]:    SCPlugin-Ifupdown: update_connection_setting_from_if_block: name:eth0, type:802-3-ethernet, id:Ifupdown (eth0), uuid: 681b428f-beaf-8932-dce4-687ed5bae28e
Feb  2 16:02:45 8730w NetworkManager[3451]:    SCPlugin-Ifupdown: adding eth0 to iface_connections
Feb  2 16:02:45 8730w NetworkManager[3451]:    SCPlugin-Ifupdown: adding iface eth0 to well_known_interfaces
Feb  2 16:02:45 8730w NetworkManager[3451]:    SCPlugin-Ifupdown: autoconnect
Feb  2 16:02:45 8730w NetworkManager[3451]:    SCPluginIfupdown: management mode: unmanaged
Feb  2 16:02:45 8730w NetworkManager[3451]:    SCPlugin-Ifupdown: devices added (path: /sys/devices/pci0000:00/0000:00:19.0/net/eth0, iface: eth0)
Feb  2 16:02:45 8730w NetworkManager[3451]:    SCPluginIfupdown: locking wired connection setting
Feb  2 16:02:45 8730w NetworkManager[3451]:    SCPlugin-Ifupdown: devices added (path: /sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/net/wlan0, iface: wlan0)
Feb  2 16:02:45 8730w NetworkManager[3451]:    SCPlugin-Ifupdown: device added (path: /sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/net/wlan0, iface: wlan0): no ifupdown configuration found.
Feb  2 16:02:45 8730w NetworkManager[3451]:    SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/lo, iface: lo)
Feb  2 16:02:45 8730w NetworkManager[3451]:    SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found.
Feb  2 16:02:45 8730w NetworkManager[3451]:    SCPlugin-Ifupdown: end _init.
Feb  2 16:02:45 8730w NetworkManager[3451]: <info> Loaded plugin ifupdown: (C) 2008 Canonical Ltd.  To report bugs please use the NetworkManager mailing list.
Feb  2 16:02:45 8730w NetworkManager[3451]: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.
Feb  2 16:02:45 8730w NetworkManager[3451]:    Ifupdown: get unmanaged devices count: 1
Feb  2 16:02:45 8730w NetworkManager[3451]:    SCPlugin-Ifupdown: (23921456) ... get_connections.
Feb  2 16:02:45 8730w NetworkManager[3451]:    SCPlugin-Ifupdown: (23921456) ... get_connections (managed=false): return empty list.
Feb  2 16:02:45 8730w NetworkManager[3451]:    keyfile: parsing Wireless connection 1 ...
Feb  2 16:02:45 8730w NetworkManager[3451]:    keyfile:     read connection 'Wireless connection 1'
Feb  2 16:02:45 8730w NetworkManager[3451]:    Ifupdown: get unmanaged devices count: 1
Feb  2 16:02:45 8730w NetworkManager[3451]: <info> trying to start the modem manager...
Feb  2 16:02:45 8730w dbus[3072]: [system] Activating service name='org.freedesktop.ModemManager' (using servicehelper)
Feb  2 16:02:45 8730w NetworkManager[3451]: <info> monitoring kernel firmware directory '/lib/firmware'.
Feb  2 16:02:45 8730w NetworkManager[3451]: <info> monitoring ifupdown state file '/run/network/ifstate'.
Feb  2 16:02:45 8730w NetworkManager[3451]: <info> found WiFi radio killswitch rfkill3 (at /sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/ieee80211/phy0/rfkill3) (driver (unknown))
Feb  2 16:02:45 8730w NetworkManager[3451]: <info> found WiFi radio killswitch rfkill0 (at /sys/devices/platform/hp-wmi/rfkill/rfkill0) (driver hp-wmi)
Feb  2 16:02:45 8730w NetworkManager[3451]: <info> WiFi disabled by radio killswitch; enabled by state file
Feb  2 16:02:45 8730w NetworkManager[3451]: <info> WWAN enabled by radio killswitch; enabled by state file
Feb  2 16:02:45 8730w NetworkManager[3451]: <info> WiMAX enabled by radio killswitch; enabled by state file
Feb  2 16:02:45 8730w NetworkManager[3451]: <info> Networking is enabled by state file
Feb  2 16:02:45 8730w NetworkManager[3451]: <warn> failed to allocate link cache: (-12) Object not found
Feb  2 16:02:45 8730w NetworkManager[3451]: <info> (eth0): carrier is OFF
Feb  2 16:02:45 8730w NetworkManager[3451]: <info> (eth0): new Ethernet device (driver: 'e1000e' ifindex: 2)
Feb  2 16:02:45 8730w NetworkManager[3451]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/0
Feb  2 16:02:45 8730w NetworkManager[3451]: <info> (wlan0): using nl80211 for WiFi device control
Feb  2 16:02:45 8730w NetworkManager[3451]: <info> (wlan0): new 802.11 WiFi device (driver: 'iwlwifi' ifindex: 3)
Feb  2 16:02:45 8730w NetworkManager[3451]: <info> (wlan0): exported as /org/freedesktop/NetworkManager/Devices/1
Feb  2 16:02:45 8730w NetworkManager[3451]: <info> (wlan0): now managed
Feb  2 16:02:45 8730w NetworkManager[3451]: <info> (wlan0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Feb  2 16:02:45 8730w NetworkManager[3451]: <info> (wlan0): bringing up device.
Feb  2 16:02:45 8730w NetworkManager[3451]: <info> (wlan0): deactivating device (reason 'managed') [2]
Feb  2 16:02:46 8730w laptop-mode: Warning: Configuration file /etc/laptop-mode/conf.d/board-specific/*.conf is not readable, skipping.
Feb  2 16:02:46 8730w laptop-mode: enabled, not active
Feb  2 16:02:46 8730w modem-manager[3522]: <info>  ModemManager (version 0.5.2.0) starting...
Feb  2 16:02:46 8730w dbus[3072]: [system] Successfully activated service 'org.freedesktop.ModemManager'
Feb  2 16:02:46 8730w NetworkManager[3451]: <info> modem-manager is now available
Feb  2 16:02:46 8730w modem-manager[3522]: <info>  Loaded plugin AnyData
Feb  2 16:02:46 8730w modem-manager[3522]: <info>  Loaded plugin Ericsson MBM
Feb  2 16:02:46 8730w modem-manager[3522]: <info>  Loaded plugin Option
Feb  2 16:02:46 8730w modem-manager[3522]: <info>  Loaded plugin Huawei
Feb  2 16:02:46 8730w modem-manager[3522]: <info>  Loaded plugin Generic
Feb  2 16:02:46 8730w modem-manager[3522]: <info>  Loaded plugin MotoC
Feb  2 16:02:46 8730w modem-manager[3522]: <info>  Loaded plugin Sierra
Feb  2 16:02:46 8730w modem-manager[3522]: <info>  Loaded plugin ZTE
Feb  2 16:02:46 8730w modem-manager[3522]: <info>  Loaded plugin Option High-Speed
Feb  2 16:02:46 8730w modem-manager[3522]: <info>  Loaded plugin SimTech
Feb  2 16:02:46 8730w modem-manager[3522]: <info>  Loaded plugin Gobi
Feb  2 16:02:46 8730w modem-manager[3522]: <info>  Loaded plugin Wavecom
Feb  2 16:02:46 8730w modem-manager[3522]: <info>  Loaded plugin Novatel
Feb  2 16:02:46 8730w modem-manager[3522]: <info>  Loaded plugin Nokia
Feb  2 16:02:46 8730w modem-manager[3522]: <info>  Loaded plugin Samsung
Feb  2 16:02:46 8730w modem-manager[3522]: <info>  Loaded plugin Linktop
Feb  2 16:02:46 8730w modem-manager[3522]: <info>  Loaded plugin X22X
Feb  2 16:02:46 8730w modem-manager[3522]: <info>  Loaded plugin Longcheer
Feb  2 16:02:46 8730w modem-manager[3522]: <info>  (ttyS0) opening serial port...
Feb  2 16:02:47 8730w minissdpd[4036]: setsockopt(udp, IP_ADD_MEMBERSHIP)(0.0.0.0): No such device
Feb  2 16:02:47 8730w minissdpd[4036]: Failed to add IPv4 multicast membership for interface 0.0.0.0.
Feb  2 16:02:49 8730w dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
Feb  2 16:02:58 8730w modem-manager[3522]: <info>  (ttyS0) closing serial port...
Feb  2 16:02:58 8730w modem-manager[3522]: <info>  (ttyS0) serial port closed
Feb  2 16:02:58 8730w modem-manager[3522]: <info>  (ttyS0) opening serial port...
Feb  2 16:02:59 8730w dbus[3072]: [system] Activating service name='org.freedesktop.ConsoleKit' (using servicehelper)
Feb  2 16:02:59 8730w dbus[3072]: [system] Successfully activated service 'org.freedesktop.ConsoleKit'

The bit after that is just the shutdown sequence.  Is there something obvious here to the more trained eye or should I just start again with a fresh install?

Pages: [1] 2