I always do a clean installation from DVD, and I have this partition settings right now: SUSE Paste
The 43 Gb partition is Windows 7, the 81 Gb one is for data and backups (no boot from here). The rest of partitions are Linux system ones (as it can be seen). Though I was willing to first switching from Win 7 to Win 8, using the 43 Gb partition, then installing openSUSE 12.3 (it’s said that a Windows installation unfortunately corrupts Grub and makes Linux unbootable).
So I had some doubts:
Are my settings right, or could they potentially give problems with Windows 8 and openSUSE 12.3?
Why is it that there seems to be several boot, Nvidia, or probably other kind of problems? (I’m Nvidia user…)
You setup looks fine to me… Although 24GB is pretty small for /root and /home both but it will probably work for a while. Just use ext4, you will not get any benefit from using btrfs in any way.
When ever I set up a dual boot pc there are always a few rules I pay attention to and it seems to work out. Do not skip any rules and follow them in order.
make sure you have a bios that will let you switch around the boot drives, in your case this does not matter since you only have one HDD, sda.
make sure on your First install that the bootloader is always installed to the root partition and Not the MBR of the drive you are booting.
make sure you are installing the boot loader to where you want it to be in either the /root or the MBR of the drive /sda, /sdb etc…you want to use. In your case you only have one so it will be the /root on /dev/sda6.
make sure you can boot everything including Windows before you install the bootloader to the MBR.
Once everything is booting as expected then you May want to install the bootloader to the MBR but I usually just leave it where it is.
If you have questions about the installer settings to accomplish the above then make another post.
Thanks for you help.
But now, why do you think there are being several problems form users with 12.3, as mentioned in the links?
Oh, and I heard about another important problem: multimedia codecs. Seems the multimedia guide for 12.3 has some kind of errors because most of the packages it mentions have conflicts! My friend told me he first had to do the one-click way first, then open an iTunes trailer and see what missing packages it asked for, then install them with Yast Software Manager.
What errors specifically?
I used it myself and it was fine, though it required some input on my part. I was tempted to say intelligent input, but that may be pushing it
What codecs?
fluendo should automagically installed with your first update.
yast software management
packman should have the rest yast software repositories add specify url Index of /pub/linux/packman/suse/openSUSE_12.3
I mean the multimedia packages issue I already mentioned. I was told that by following the guide for 12.3 many packages conflicted or installed but not correctly, or kind of.
I don’t know why are you suggesting that mirror instead of the standard inode.at one, they seem to have the same packages.
But before this gets offtopic, perhaps I should better post it on the other subforum, though it’d be nice if mr Caf could answer as well…
Am 19.03.2013 01:06, schrieb eionmac:
> This is useless for a LIVE LINUX system so KDE live linux does not work
> Repeat does not work!
>
Not sure but have you tried in a terminal
su -
rcnetwork restart
that fixes the network problem in 12.3 for me without having to do a reboot.
Does the network problem apply at all to a live CD?
–
PC: oS 12.2 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.10.1 | GTX 650 Ti
ThinkPad E320: oS 12.2 x86_64 | i3@2.30GHz | 8GB | KDE 4.10.1 | HD 3000
eCAFE 800: oS 12.2 i586 | AMD Geode LX 800@500MHz | 512MB | KDE 3.5.10
[QUOTE=martin_helm;2537624]Am 19.03.2013 01:06, schrieb eionmac:
> This is useless for a LIVE LINUX system so KDE live linux does not work
> Repeat does not work!
>
Not sure but have you tried in a terminal
su -
rcnetwork restart
that fixes the network problem in 12.3 for me without having to do a reboot.
Does the network problem apply at all to a live CD?
I simply switched mine to network manager and left it did not really try to get idup working. This is on a older desktop machine
“Does not work” is not very informative. Repeating that is no help at all.
Using a 4G USB flash drive with the live KDE image, I booted on a desktop system with an ethernet connection. The network connection came up without a problem. I did not that Kwin crashed on shutdown, probably a nouveau driver problem.
Using the same KDE live image, I booted a UEFI box with WiFi. The network did not connect until I selected a network and entered the WPA key. And then there was an annoying kdewallet popup - I’m not sure why they don’t set that up in advance with a blank key for the live iso. Apart from that the network worked just fine.
Those were both 64bit boots. I haven’t created or tested 32 bit KDE live.
On 2013-03-19 03:46, gogalthorp wrote:
>
> eionmac;2537614 Wrote:
>> This is useless for a LIVE LINUX system so KDE live linux does not work
>> Repeat does not work!
>
> Worked for me…
>
> I burned tot USB stick and installed from there. A bit of a hassle with
> old 6800+ NVIDIA card but all is well now.
But you are installing the live system, you are not running the live
system without installing it. The claim is that the live system has no
network and is thus useless.
Of course, the OP still has to say if “rcnetwork restart” works.
If this does not work, it has to be reported in Bugzilla as a critical
problem.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
[QUOTE=martin_helm;2537624]Am 19.03.2013 01:06, schrieb eionmac:
> This is useless for a LIVE LINUX system so KDE live linux does not work
> Repeat does not work!
>
Not sure but have you tried in a terminal
su -
rcnetwork restart
that fixes the network problem in 12.3 for me without having to do a reboot.
Does the network problem apply at all to a live CD?
REPLY.
Sorry for uninformative and ‘rude’ post, but this is first Live Linux disc of many ( many dozens?) used since 1996 that does not automatically detect 'wired Ethernet connections" or 'wireless connections active within range; OR give on landing page instructions how to find and connect!
I do not use a USB memory but a dvd/cd, I have not tried by USB. It is usual for me to only use DVD/CD live linux.
After network ticked in the network manager pop up (which is loaded at start) it does noting. All boxes except wired and VPN greyed out. Selecting Wired does not allow to add as buttons greyed out. VPN does give ability to add but is not applicable.
Regret the “su - rcnetwork restart” shows only “user rcnetwork does not exist”
However after much experimenting, YAST and DSL selection eventually came into being, but it needs knowledge to set up (DNS etc) not normal for a novice to know. (YAsT would be unknown to a newbie trying a live linux from this download!
Using DNS set up in YAST I got connected, so you get this message.
I have never registered a bug so do not know how to , Please advise.
However this Live Linux download is not useable by the folk who would be given a Live Linux to try and introduce them to Linux. (refer Puppy or Knoppix Live Linux distros, Knoppix finds, Puppy give explicit instructions on first loading screen).
I always try Live Linux first before any loads to hard drives.
See lower post. Sorry for rude post, but hours of frustration came into play. when all DVD/CD Live Linuxs since 1996 I have tried
auto detect or show on landing page how to connect.
Live Linux DVD did not detect any wired or wireless networks to chose from. Eventually connected via YAST , DNS connection etc, but a newbie or those who try Linux from Live DVD would be unable to find/understand and would be immediately switched off.
I had the same idea. I sarted up a fresh install of openSUSE and low and behold it didn’t detect a wireless signal. This is the first Distro to do that to me in years. I started digging around in settings trying to find an answer. For me the answer was that, in Yast, in the network settings. It is set to **not **use the Desktop Network Manager. Clicking this one box fixed my problem. Seems counter-intuituve to set it up this way to me.
