January 2015 - openSUSE Users - openSUSE Mailing Lists

[opensuse] big help needed with dual boot win 8.1 and 13.2
by Richard 08 Jan '15

08 Jan '15

Oh boy, I think I have done it now! Have been using suse for some time, since at least 6.x so far as I can remember. While I have sometimes had issues with install/upgrades I have usually been able to fix them with some book time. Now since Win 8.1 is involved, I am in more trouble. New laptop with 8.1, installed 13.2, clean install from downloaded DVD. Ran checksum and option to check disk before installing. At the end of the install I had a very crippled 13.2, not usable really, and worse, a BSOD replacing the Win 8.1. Could not re-boot into either. Win note finally said call the manufacturer. I did. Rep said probably a bad hard drive, return to replace the laptop. I was not so sure, felt I had smotched something during install, but kept quiet anyway. Exchanged. Being stalwart or stupid, take your pick, (either a long-standing characteristic of those of us non-gurus who venture into linux-land anyway), after insuring a working 8.1, I made recovery disks (had not known about those the first time), and tried again. More unhappiness: got 13.2 installed and working, with some effort, and at the completion read the release notes which appeared. Uh-oh: one talked about issues with 8.1 and a lot of explanation I did not follow, especially what to do about it, which mostly included hope and prayer. Neither worked, and again I had a non-working windows. No matter, I said, I have recovery disks this time. Well, apparently I did not. I had a disk, but it did not recover. Same messages as before, recovery media invalid, missing files, whatever, and contact manufacturer. I am loathe to do that since I am now pretty certain I have done something bad. Can anyone lead me by the nose thru this? My suse is working, including email. I copied files from the win partitions to make a disk with install files, I think. In any case an additional disk for recovery suggested by windows as probably not really necessary, but nice. Likely needed now. I would really like to get my win back. After all, I paid for it. Also need for a couple of specific programs that must run on win. I am really nervous about playing too much, especially around the MBR or whatever is being used now, and disabling my linux usage. Back about suse 8.x and 9.x I was more active, followed changes and all. Since then I have become much more a "user" simply using the system effectively but needing little more working knowledge than my wife has (she still searches for some letters on the keyboard, can't understand why they are not laid out alphabetically to make them easier to find). Thanks for any guidance. If some intrepid soul would be willing to hold my hand in this, I am willing to take it off list as this may be of little interest to most. Richard -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

11 21

[opensuse] Google Drive Ocamlfuse for 13.2
by Hans-Peter Jansen 08 Jan '15

08 Jan '15

Dear openSUSErs, I just want to inform you about the availibility of google-drive-ocamlfuse for 13.2 here: https://build.opensuse.org/project/show/home:frispete:ocaml http://download.opensuse.org/repositories/home:/frispete:/ocaml/openSUSE_13… It allows to mount Google Drives via fuse. Since build wasn't exactly straight forward, I expect a couple of failed attempts in the openSUSE community already. Given, how many packages were missing, it's a little frustrating to see collegues just adding a repo in debian/ubuntu, installing the package, and be done with it. Oh well. It seems to work fine, but bear with me, as I'm an Ocaml rookie. Ocamls build environment isn't the real Mc Coy, either. I'm interested in package build feedback of course, and you _might_ cc me for technical issues, but put them in the proper places, e.g.: https://github.com/astrada/google-drive-ocamlfuse/issues Get the fun back-ly y'rs, Pete -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 3

[opensuse] openSUSE virtualbox packages
by Patrick Shanahan 07 Jan '15

07 Jan '15

Do the current virtualbox packages hosted by openSUSE now provide usb access? tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.openSE.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 6

[opensuse] Major install problems with 13.2 -- Worse
by Joseph Comfort 07 Jan '15

07 Jan '15

The first thread got off track. I need a new one. Cpmputer: HP 6305 minitower, with HP motherboard. Latest BIOS BIOS provides 'Legacy Support' (= bios/mbr): enabled Secure boot is disabled Windows 7 Pro, 64 bit. Drives: /dev/sda -- came with computer; entirely filled up. /dev/sdb -- my addition to use for Linux With nothing on 'sdb', the system boots to Win-7 (Today I deleted all partition on sdb) Let me be clear: Windows boots with bios/MBR and the corresponding bootmgr. It will _not_ boot if the BIOS Legacy Support is turned off (= UEFI). (The system came with a Win-8 disk, and the computer could be set to use it. It never was.) The openSuSE 13.2 full install DVD, 4.4 GiB, (iso) was downloaded. Booting up to the DVD, there are no menu lines for either to boot from the installed system (only win-7) or for memtest. These items are present if the DVD is booted on other computers! Proceeding with installatiion, I construct ext4 partitions on sdb as I had done in the past. But the installer complains that there is no FAT partition for /boot/efi. Problem 1: Why should I need one? The computer is set for bios/mbr use. I push ahead and get the summary page. It lists efi mode for booting, and also that secure boot is turned on. Problem 2: Why is the installer ignoring the BIOS and my setup? I click on Booting, change the manager to GRUB2 (which had worked for me before, even on this coomputer), disable secure boot. The summary then says "Unsupported combination of hardware platform for x86_64 and grub2." Problem 3: What, What?? Ignoring, I am able to install the code. However, on reboot, there is _still_ no menu item to boot the installed system, and the installtion starts over again. Problem 4: Why aren't these items at least showing up now? I reboot the computer. Now I see a menu item for openSUSE that leads me to the system. But there is _No_ entry for Windows. Now, I can not even get into Win-7 ! Problem 5: Why isn't a Windows option automatic, as it has been for a very long time? I clean off sdb and tried to work with a GPT style, such as including a FAT partition for /boot/efi. I encountered messages such as "/ boot partition does not have a GPT disk label." It tells me to destroy the disk label in expert partitioner. But I am already in the expert partitioner, and there are no options to handle labels. I even tried the proposed default GTP setup. I again ended up with Problems 4 and 5. Let me note that, before all of this, I had Win-7 and oS 13.1 running well together on the computer. I don't know how I did that because the 13.1 DVD is now behaving the same way as 13.2. (Before you ask, this statement is true before and after the BIOS update.) There may be ways to work around these problems. But it should not be necessary -- certainluy not for the istall disk which the first contact between the SuSE OS and the public. I recall that the install DVD for a previous release (9.? or 10.?) had to be remastered due to major problems. It may be necessary again. Joe -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 9

[opensuse] How can I get unlimited core file size when booting openSUSE?
by Mitsutoshi NAKANO 07 Jan '15

07 Jan '15

I am using openSUSE 13.2 x64. I want to change core file size to unlimited. I changed /etc/security/limits.conf. * soft core unlimited And reboot openSUSE, but I got that core file size is 0. >ulimit -c 0 I wrote "ulimit -c unlimited" in ~/.bashrc, so I got unlimited core file size. >ulimit -c unlimited But I want to get unlimited core file size when booting openSUSE. (Especially, I want to debug daemons...) How can I get unlimited core file size when booting openSUSE? -- Mitsutoshi NAKANO <ItSANgo(a)gmail.com> <bkbin005(a)rinku.zaq.ne.jp> <https://twitter.com/ItSANgo> <http://d.hatena.ne.jp/Itisango/> -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 4

[opensuse] Reason #7 why bugreporting can be incredibly frustrating ....
by Per Jessen 06 Jan '15

06 Jan '15

Bughandlers/developers that close reports just because they can't reproduce the issue. WORKSFORYOU != WORKSFORME. Most recent example: https://bugzilla.opensuse.org/show_bug.cgi?id=899714 -- Per Jessen, Zürich (0.0°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 6

[opensuse] NFS permissions wrong
by Patrick Shanahan 06 Jan '15

06 Jan '15

Just reinstalled 13.2 -> Tw and had to reconfigure nfs server for one external usb ntfs drive and cannot get the permissions correct. for local-internal net only Setup nfs-server with yast and have: port open in firewall enable NFSv4 localdomain <directory> * rw,root_squash,sync.no_subtree_check disk configured via "yast disk" /dev/sde1 hpfs/ntfs /mnt/collector fstab: Device Name Mountable by user users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8,nofail /dev/sde1 presents itself as root:users and only root has w Before I had it owned <user>:users and rw But now I cannot seem to change write access or owner ??? what have I missed? tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] NFS debugging issue
by Greg Freemyer 05 Jan '15

05 Jan '15

All, I am NOT an expert on NFS mounts. I have one I use in a cloud facility from my virtual machine. I just applied the latest round of patches for openSUSE 13.1 and rebooted. After the reboot the NFS mount is no longer mounting. Can someone point me at a troubleshooting guide that is relatively easy to follow? fyi: when I run "mount /mnt_point" I'm getting back "mount.nfs: Connection timed out" Thanks Greg -- Greg Freemyer -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

[opensuse] Intel WLAN Powersave limits RX to 54Mbps
by Jan Ritzerfeld 05 Jan '15

05 Jan '15

Hey, can anyone reproduce the following problem using an Intel WLAN adapter? 1. # iw dev wlp3s0 set power_save on 2. suspend and resume 3. # iw dev wlp3s0 station dump ...rx bitrate: 54.0 MBit/s... And the bit rate will never exceed 54Mbps again. The same holds true if you create an udev rule that activates powersave on boot. Enabling powersave at run-time does not limit the bit rate to 54Mbps. Disabling it at run-time will not help, too, if it was enabled at boot or suspend and resume! Gruß Jan -- Everything needs a little oil now and then. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 3

[opensuse] Support for openSUSE 12.3 in the KDE repositories.
by Raymond Wooninck 05 Jan '15

05 Jan '15

Dear KDE Users, Given that openSUSE 12.3 is no longer actively supported, the openSUSE KDE Community team received the request to remove the openSUSE 12.3 targets for the KDE repositories. This effectively means that for the KDE:Current, KDE:Extra, KDE:Unstable:Extra building is stopped for the openSUSE 12.3 based targets and the related packages would be removed as of February 1. Users are encouraged to upgrade to either openSUSE 13.1 or openSUSE 13.2. Regards Your openSUSE KDE Community Team -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0