Internet worked during Live KDE, but not after installation

It seems that every linux distro I try works great during the LiveCD (in my case, USB stick) but after installation on my hard drive, some kind of distro-specific problem occurs… I am not using a virtual machine, I want to install a solid linux distro onto my Alienware M14x as the primary operating system.

So this is about openSUSE 13.1, I used the Live KDE version for a few days and everything worked fine. After I install to my hard drive (with a little difficulty about “allocating space” or something), it doesn’t recognize that I have any network interfaces at all… so after looking around the internet and my computer, i open network settings inside the control panel and it turns out YAST has no control over the network (as it showed in a warning dialog), and gave some instructions I didn’t understand… so i researched that too, and after switching it to “ifup” and rebooting, it still doesn’t work… so I look in the tray and clicked the “network management” icon, it says “network manager isnt running, please start it” (or something)… so I did more research to figure out how to start “network manager”… so i opened a terminal and got root access (i needed to be root for some reason) and typed “service NetworkManager start” and got the network manager to start, and only my ethernet port showed up. I still have no idea how to enable my wireless card… when I open the “manage connection”, all of the tabs are grayed out… except VPN, and Wired is now available after starting networkManager. How do I make my wireless work again?

I don’t want this OS to be a constant project like Mageia was… with constant posting of log files, executing shell commands, editing config files and other nonsense. I just want stuff to work, out of the box.

Boot the live dvd again and post the result of

/sbin/lspci -nnk

Lets see what driver is being used

Here is LIVE
http://wwi.picturesloaded.com/CIMG0047.jpg

00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor Family DRAM Controller [8086:0104] (rev 09)
Subsystem: Dell Device [1028:0491]
00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port [8086:0101] (rev 09)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09)
Subsystem: Dell Device [1028:0491]
Kernel driver in use: i915
Kernel modules: i915
00:16.0 Communication controller [0780]: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 [8086:1c3a] (rev 04)
Subsystem: Dell Device [1028:0491]
Kernel driver in use: mei_me
00:1b.0 Audio device [0403]: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller [8086:1c20] (rev 05)
Subsystem: Dell Device [1028:0491]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 [8086:1c10] (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.2 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 [8086:1c14] (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.3 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 [8086:1c16] (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.5 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 [8086:1c1a] (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1d.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 [8086:1c26] (rev 05)
Subsystem: Dell Device [1028:0491]
Kernel driver in use: ehci-pci
Kernel modules: ehci_pci
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev a5)
00:1f.0 ISA bridge [0601]: Intel Corporation HM67 Express Chipset Family LPC Controller [8086:1c4b] (rev 05)
Subsystem: Dell Device [1028:0491]
Kernel driver in use: lpc_ich
Kernel modules: lpc_ich
00:1f.2 SATA controller [0106]: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller [8086:1c03] (rev 05)
Subsystem: Dell Device [1028:0491]
Kernel driver in use: ahci
Kernel modules: ahci
00:1f.3 SMBus [0c05]: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller [8086:1c22] (rev 05)
Subsystem: Dell Device [1028:0491]
Kernel modules: i2c_i801
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF116M [GeForce GT 555M/635M] [10de:124d] (rev a1)
Subsystem: Dell GeForce GT 555M [1028:0491]
Kernel driver in use: nouveau
Kernel modules: nvidiafb, nouveau
07:00.0 Ethernet controller [0200]: Qualcomm Atheros AR8151 v2.0 Gigabit Ethernet [1969:1083] (rev c0)
Subsystem: Dell Device [1028:0491]
Kernel driver in use: atl1c
Kernel modules: atl1c
0d:00.0 Network controller [0280]: Intel Corporation Centrino Wireless-N 1000 [Condor Peak] [8086:0083]
Subsystem: Intel Corporation Centrino Wireless-N 1000 BGN [8086:1325]
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi
13:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5209 PCI Express Card Reader [10ec:5209] (rev 01)
Subsystem: Dell Device [1028:0491]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
13:00.1 SD Host controller [0805]: Realtek Semiconductor Co., Ltd. RTS5209 PCI Express Card Reader [10ec:5209] (rev 01)
Subsystem: Dell Device [1028:0491]
Kernel driver in use: sdhci-pci
Kernel modules: sdhci_pci
19:00.0 USB controller [0c03]: NEC Corporation uPD720200 USB 3.0 Host Controller [1033:0194] (rev 04)
Subsystem: Dell Device [1028:0491]
Kernel driver in use: xhci_hcd
Kernel modules: xhci_hcd

Here is installed
http://wwi.picturesloaded.com/CIMG0048.jpg

00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor Family DRAM Controller [8086:0104] (rev 09)
Subsystem: Dell Device [1028:0491]
00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port [8086:0101] (rev 09)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09)
Subsystem: Dell Device [1028:0491]
Kernel driver in use: i915
Kernel modules: i915
00:16.0 Communication controller [0780]: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 [8086:1c3a] (rev 04)
Subsystem: Dell Device [1028:0491]
Kernel driver in use: mei_me
00:1b.0 Audio device [0403]: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller [8086:1c20] (rev 05)
Subsystem: Dell Device [1028:0491]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 [8086:1c10] (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.2 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 [8086:1c14] (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.3 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 [8086:1c16] (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.5 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 [8086:1c1a] (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1d.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 [8086:1c26] (rev 05)
Subsystem: Dell Device [1028:0491]
Kernel driver in use: ehci-pci
Kernel modules: ehci_pci
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev a5)
00:1f.0 ISA bridge [0601]: Intel Corporation HM67 Express Chipset Family LPC Controller [8086:1c4b] (rev 05)
Subsystem: Dell Device [1028:0491]
Kernel driver in use: lpc_ich
Kernel modules: lpc_ich
00:1f.2 SATA controller [0106]: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller [8086:1c03] (rev 05)
Subsystem: Dell Device [1028:0491]
Kernel driver in use: ahci
00:1f.3 SMBus [0c05]: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller [8086:1c22] (rev 05)
Subsystem: Dell Device [1028:0491]
Kernel modules: i2c_i801
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF116M [GeForce GT 555M/635M] [10de:124d] (rev a1)
Subsystem: Dell GeForce GT 555M [1028:0491]
Kernel driver in use: nouveau
Kernel modules: nvidiafb, nouveau
07:00.0 Ethernet controller [0200]: Qualcomm Atheros AR8151 v2.0 Gigabit Ethernet [1969:1083] (rev c0)
Subsystem: Dell Device [1028:0491]
Kernel driver in use: atl1c
Kernel modules: atl1c
0d:00.0 Network controller [0280]: Intel Corporation Centrino Wireless-N 1000 [Condor Peak] [8086:0083]
Subsystem: Intel Corporation Centrino Wireless-N 1000 BGN [8086:1325]
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi
13:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5209 PCI Express Card Reader [10ec:5209] (rev 01)
Subsystem: Dell Device [1028:0491]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
13:00.1 SD Host controller [0805]: Realtek Semiconductor Co., Ltd. RTS5209 PCI Express Card Reader [10ec:5209] (rev 01)
Subsystem: Dell Device [1028:0491]
Kernel driver in use: sdhci-pci
Kernel modules: sdhci_pci
19:00.0 USB controller [0c03]: NEC Corporation uPD720200 USB 3.0 Host Controller [1033:0194] (rev 04)
Subsystem: Dell Device [1028:0491]
Kernel driver in use: xhci_hcd
Kernel modules: xhci_hcd

With your wired connection
Install rfkill (it’s in Packman) see this: https://forums.opensuse.org/blogs/caf4926/opensuse-13-1-multi-media-restricted-format-installation-guide-149/

Then post the result of

/usr/sbin/rfkill list

Do you have “kernel-firmware” installed? That’s needed for the intel wifi to work.

Is NetworkManager actually activated? YaST->Network Devices->Network Settings->Global Options.

On 2013-12-07 05:56, frustrated user56 wrote:

> around the internet and my computer, i open network settings inside the
> control panel and it turns out YAST has no control over the network (as
> it showed in a warning dialog), and gave some instructions I didn’t
> understand…

> and rebooting, it still doesn’t work… so I look in the tray and clicked
> the “network management” icon, it says “network manager isnt running,
> please start it” (or something)… so I did more research to figure out

There are two mutually excluyent (?) network configuration modes in
openSUSE. If you tell YaST that you are going to use ifup, then network
manager is disabled, you have to do all the configuration in yast.

To use network manager, you have to tell yast that the network will be
user managed, so that it disables ifup and the network manager icon appears.


Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

^mutually exclusive

Whether I have the radiobox in “Global Options” set to Network Manager or Traditional ifup doesn’t matter… neither setting works. The only thing I did after installation of openSUSE was install VirtualBox stuff (through YAST because the RPM from virtualbox.org didn’t work)… I checked all of the virtualbox checkboxes in the software installation utility and pressed “Apply”. When I tried to copy my virtual machine (via USB) onto the computer, I got an error that said “filesystem exfat is not recognized” (or something)… I tried to research the error and find out how to make it recognize exfat, and noticed the internet wasn’t working anymore.

It sounds like I am going to have to dedicate an afternoon to JUST TO MAKE THE INTERNET WORK AGAIN… I am almost tempted to dig up the Windows 7 DVD and install that… almost.

I’ll post the other requested command output when I have the time (I have to copy it to a text file and transfer it via USB drive to post it)… maybe I should reinstall openSUSE and hope for better luck next time? I wish stuff would work like it’s supposed to without me having to execute shell commands, analyze output and spelunk through menus and config files, double check driver configuration and other such nonsense… or worry about what I install breaking basic system functions LIKE INTERNET.

My Alienware is my workhorse, it’s and crippled right now. I’m getting sick of using this Macbook, I need a powerful system >:(

openSUSE is still awesome! Thanks to all who have contributed to this thread so far, I appreciate the support. rotfl!

On 2013-12-07 20:26, frustrated user56 wrote:
>
> ^mutually exclusive
>
> Whether I have the radiobox in “Global Options” set to Network Manager
> or Traditional ifup doesn’t matter… neither setting works. The only
> thing I did after installation of openSUSE was install VirtualBox stuff
> (through YAST because the RPM from virtualbox.org didn’t work)… I
> checked all of the virtualbox checkboxes in the software installation
> utility and pressed “Apply”. When I tried to copy my virtual machine
> (via USB) onto the computer, I got an error that said “filesystem exfat
> is not recognized” (or something)…

That’s complicated. Easiest is to reformat that stick in Windows as
plain FAT, or NTFS. The new format “exfat” (look it up in the wikipedia)
is not currently supported in Linux; I think there is some experimental
support, as that format is heavily proprietary and protected. Microsoft
does not want other people to use it, specially for free. They want
royalties, and that is not going to happen in the Linux world.

> It sounds like I am going to have to dedicate an afternoon to JUST TO
> MAKE THE INTERNET WORK AGAIN… I am almost tempted to dig up the Windows
> 7 DVD and install that… almost.

Did you try the suggestion about kernel-firmware?

>
> I’ll post the other requested command output when I have the time (I
> have to copy it to a text file and transfer it via USB drive to post
> it)… maybe I should reinstall openSUSE and hope for better luck next
> time?

That kind of thing (luck) happens with Windows, but seldom in Linux.
Unless you choose different options, you get the same result.

> I wish stuff would work like it’s supposed to without me having to
> execute shell commands, analyze output and spelunk through menus and
> config files, double check driver configuration and other such
> nonsense… or worry about what I install breaking basic system functions
> LIKE INTERNET.

Linux is free and gratis, but you pay with extra work. Just live with it
and enjoy… :wink:

>
> My Alienware is my workhorse, it’s and crippled right now. I’m getting
> sick of using this Macbook, I need a powerful system >:(
>
>
> openSUSE is still awesome! Thanks to all who have contributed to this
> thread so far, I appreciate the support. rotfl!

When you find what the problem was, you can create a bugzilla entry so
that the issue is solved in the future automatically.


Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

On 2013-12-07 22:54, Carlos E. R. wrote:
> On 2013-12-07 20:26, frustrated user56 wrote:

> That’s complicated. Easiest is to reformat that stick in Windows as
> plain FAT, or NTFS. The new format “exfat” (look it up in the wikipedia)
> is not currently supported in Linux; I think there is some experimental
> support, as that format is heavily proprietary and protected. Microsoft
> does not want other people to use it, specially for free. They want
> royalties, and that is not going to happen in the Linux world.

View this
thread here


Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

I looked everywhere including the attic and I do not have an ethernet cable, I believe I donated it to the Computer History Museum in Mountain View, CA… so I cannot install rfkill without network… Nor can I uninstall any of the VirtualBox files I added without internet (which doesn’t make sense… why do I need internet to uninstall something?)

I opened Software Management to see if I have kernel-firmware installed, and I get this warning “PackageKit is blocking software management…” (another conflict?)… I asked it to quit and searched for “kernel-firmware”… it is already installed (20130714git-2.1.1)

The filesystem thing is another issue… I don’t have a Windows machine, so NTFS is out of the question… my backup laptop is a Macbook with OSX 10.6.8… it is not capable of formatting as nor writing data to NTFS filesystem, it is only capable of formatting (through Disk Utility) as the following filesystems: Mac OS Extended, Mac OS Extended (journaled), MS-DOS (FAT) and exFAT. Due to the filesize limitations of FAT, I cannot copy my VirtualBox .vdi file onto it because it is 22Gb.

I tried another Live installation… I didn’t choose any custom settings this time (or last time), I just keep pressing the Next button until I can walk away. After installation, internet still doesn’t work… and it won’t let me open YAST anymore because I didn’t set a root password this time.

Plan B, I tried Ubuntu 13.1 from a LiveUSB and I pretty much hate it… it installs something from Amazon on my launcher and the software manager is laid out like an app store… back to openSUSE…

I am now formatting the HDD completely and doing a clean openSUSE installation, just pressing the Next button again (but setting up a user, password, and root password… as it seems to be REQUIRED). Immediately, I have this memory allocating error again… system error code was: -3003 “swapon: /dev/sda1: swapon failed: Cannot allocate memory”… installation aborted.

Rebooting, trying again… resized the swap partition to 1.00gb instead of 2.01gb (default) and pressed the Next button a bunch of times (setting up a user, password and root password… as is required). Progress bar, progress bar… reboot, automatic configuration… progress bar, progress bar… DESKTOP.

Same situation… no wireless internet. I open YAST, enter the root password, open Network Configuration and immediately see the error from last time…

Warning
Network is currently controlled by NetworkManager and its settings cannot be edited by YaST.

To edit the settings, use the NetworkManager connection editor or switch the network setup method to Traditional with ifup

so uhh… free = some assembly required eh?

Fine, I found this purchase page for openSUSE Enterprise Desktop… I’m looking at the Standard package for $120, but it says it’s a subscription for one year (are you kidding?)… does that mean the OS will stop working after 1 year, or is that just the length of the support?

SLED and SLES are enterprise products and probably not what you are looking for. Just forget that for now.

You should use Network Manager to control networks
When you start the settings for Network in Yast and Network Manager is active you get a warning as you quoted. Just ignore it and leave the settings.

From what you posted earlier, in live and installed, both show the driver the same.
In the live session, please look in /lib/firmware/
I’m guessing but I expect there to be a folder related to your quoted wireless device. Copy the folder and put it on a pen drive.
Now try in the real install to copy over the said folder. You may have one in the real install already, so you will need to rename it and copy over the one from the pen drive.

Now try this

su -
modprobe -rv iwlwifi
modprobe -v iwlwifi

On 2013-12-08 05:46, frustrated user56 wrote:
>
> I looked everywhere including the attic and I do not have an ethernet
> cable, I believe I donated it to the Computer History Museum in Mountain
> View, CA… so I cannot install rfkill without network…

You should always have a cable backup :slight_smile:

> Nor can I
> uninstall any of the VirtualBox files I added without internet (which
> doesn’t make sense… why do I need internet to uninstall something?)

Yes, you can.

You can use the command “rpm” for that. Or you can disable all internet
repositories, then use YaST.

> I opened Software Management to see if I have kernel-firmware installed,
> and I get this warning “PackageKit is blocking software management…”

Kill it.

> The filesystem thing is another issue… I don’t have a Windows machine,
> so NTFS is out of the question…

Then why are you using an exfat stick? Reformat it as plain fat, if you
need it for exchanging files with other people using Windows. Or
reformat as ext4 without journal if you only use Linux.

> my backup laptop is a Macbook with OSX
> 10.6.8… it is not capable of formatting as nor writing data to NTFS
> filesystem, it is only capable of formatting (through Disk Utility) as
> the following filesystems: Mac OS Extended, Mac OS Extended (journaled),
> MS-DOS (FAT) and exFAT. Due to the filesize limitations of FAT, I cannot
> copy my VirtualBox .vdi file onto it because it is 22Gb.

Well, if you absolutely need exfat, then read the thread I told you.

> Same situation… no wireless internet. I open YAST, enter the root
> password, open Network Configuration and immediately see the error from
> last time…
>
>> Warning
>> Network is currently controlled by NetworkManager and its settings
>> cannot be edited by YaST.

I told you about that.

> Fine, I found ‘this purchase page for openSUSE Enterprise Desktop’
> (https://www.suse.com/products/desktop/how-to-buy/)… I’m looking at the
> Standard package for $120, but it says it’s a subscription for one year
> (are you kidding?)… does that mean the OS will stop working after 1
> year, or is that just the length of the support?

Length of support. But that may not solve your issues, as they have
hardware requirements you must meet.


Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

You’re right… maybe my spec’d up Alienware doesn’t meet the hardware requirements of SLED… it’s almost 2 years old.

My VM is not on a USB stick, it’s an old 40Gb SATA HDD designated for my 37Gb virtual machine backup, connected through a USB converter cable… Yes, I “absolutely need” exFAT because as I said, the stupid Apple computer cannot handle NTFS, and FAT cannot handle large files… Nobody uses FAT anymore, it’s from the late 70’s and was made for use on floppy disks. Furthermore, why would you tell me to read 3 pages worth of nonsense posts from another thread instead of just telling me to install fuse-exfat?

I found a solution to all of this, I installed Mageia3 from a USB stick. It makes sure I have my preferred internet connection method operational during install, no problem. VirtualBox installed perfectly through the Mageia Control Center (which is laid out much better than openSUSE’s YAST), and I found an rpm from pbone that enables exFAT on Mageia3 (in like 30 seconds)… I plugged in my exFAT formatted HDD and it worked fine, copied my virtual machine and added it to VirtualBox, now my Windows 7 VM works as expected. All in all, I had my system 100% functional with everything I need in less than an hour, even had time to customize my KDE UI. I spent 2 days on openSUSE trying to get the installation to work… WOT

caf4926, you were very helpful without being condescending, but I have run out of patience. I really like openSUSE, it looks nice and feels very solid (and it works with my HDMI port), but I have reverted back to my old ways because the weekend is over and I need a workable system by Monday.

On 2013-12-08 22:46, frustrated user56 wrote:

> Furthermore, why would you tell me to read 3 pages worth of nonsense
> posts from another thread instead of just telling me to install
> fuse-exfat?

Because I don’t know how it is done. I simply have a note to myself
where I noted that thread explains how.

> to VirtualBox, now my Windows 7 VM works as expected. All in all, I had
> my system 100% functional with everything I need in less than an hour,
> even had time to customize my KDE UI. I spent 2 days on openSUSE trying
> to get the installation to work… WOT

Good for you :slight_smile:


Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

I can’t really help with OS X, I can use it on a basic level, after all it’s basically just a Pimped up NIX under the glossy exterior.

Feel free to come back when you feel you a moment. Perhaps we can get you working. But in some cases, it’s often just best to use what works.

I also had the live disk work with KDE and then could not surf even though I was connected to my wifi router with Intel chipset. I thought it was ipv6 causing the trouble but after trying the advice about setting DNS to google it surfs fine now. I had already turned ipv6 off before trying this. It always worked fine with a LAN cable but not with wifi.

Maybe manually setting DNS to 8.8.8.8 and 8.8.4.4 like I did will help you?

On another note, it disturbs me to have to use a google anything these days after the NSA revelations from Snowden…:open_mouth:

For an Android tablet that I have I made a new email account that I will never use for anything so that I could use the tablet and not provide email they could search for their uses. I even mark the mail from them as spam in the account when I occasionally log in to look at it.

Just thinking out loud.

cheers all

X31 ThinkPad
Intel wifi 2200 calexico
KDE 4.11
Pentium M cpu

There are alternatives, such as https://duckduckgo.com/

There is also the TOR project which purportedly helps to prevent illegal spying : https://www.torproject.org/

The above work with openSUSE (I have tested same).

Having noted the above links, efforts to avoid such spying is likely to draw more attention from those whose spying one considers illegal, and their spying will possibly be achieved via other means on all and sundry. According to same revelations, once they are focused on one, they ‘own you’.

IMHO the best way to deal with this is through democratic process, during the next election - ie elect officials who agree to have the system fixed.

Also, my having typed the above, this borders on the political and hence likely not an appropriate topic for our forum. Definitely not a topic for Network/Internet, and if discussed anywhere it may be appropriate in ‘Chat’ or ‘Soapbox’.

I have what seems to be the same problem with 13.1, on a Lenovo Ideapad S205 that worked fine in this regard under opensuse 12.3. The problem affects both wifi and cabled networking. But in my case a large number of reboots have shown that I get network up and running approximately one time out of four, and now I am relying mainly on hibernation instead of completely shutting down, which makes the situation largely manageable. I see no pattern in the success and failure. Last night I almost gave up on it after so many failed attempts but this morning it worked at the first attempt.

I would like to share my /var/log/messages file for a bad boot and a good one but I don’t know how to do that for such a large chunk of text. Can someone please suggest a way to do that. I think it provides valuable clues for those who can read it properly. I myself see differences and error messages but I don’t know what to make of it.

Thanks!

On 2014-01-02 18:36, Guttagrynna wrote:

> I would like to share my /var/log/messages file for a bad boot and a
> good one but I don’t know how to do that for such a large chunk of text.

at susepaste.org, perhaps. You can copy the log to your home, edit it, create two different chunks,
one for a failed boot, another for a good boot. Upload both separately, instead of the entire
messages file. Even both chunks together should be far less than the entire file.


Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” (Elessar))