Jump to content

terry1966

Anti-Spyware Brigade
  • Content Count

    9,289
  • Joined

  • Last visited

Posts posted by terry1966


  1. sorry been so long in getting back to you kurt, but after spending hrs trying different ways to resize a root partition and being able to log back in again after, i think you'll be better off just doing a clean install but with a bigger root partition to start with. :rofl3:

     

    anyway to cut a very very long story short, it is possible but it's also very convoluted.

     

    i finally succeeded by first logging in as root in run level 3, umount /home, resize it to minimum or size you want to add to root, create a new partition in empty space, dd /home across to new partition, mount new partition as home, delete old home. then reboot to a live cd so i could finally resize the root partition to use the free space left from when i deleted the old home partition.

     

    that was the only way i found i could resize things and still be able to boot into the desktop again after, don't know what the problem was doing things any other way but first i thought it might be a uuid issue in fstab but mounting partitions by label never fixed it, so i assume it must have been a permission issue copying the user folder back caused (even though i did try and set the folders permissions back to username and user group) any whatever the issues were i think using dd fixed that problem.

     

    upto you but if you want to try it anyway instead of doing a clean install i'll give detailed instructions on how i did it, but i can't guarantee they'll work for you even though i don't see why not. :mrgreen:

     

    :b33r:

     

    thinking about it, i don't think i tried dd when i just used a live cd to do everything, so might give that a try in a bit which if it works should make things a bit easier than the way i finally did it.


  2. can you make a live usb/cd/dvd? i think it might be easier for you if you can.

     

    if yes, but you need a live iso, then you can download the suse 13.2 kde 64bit live iso from here :- http://download.opensuse.org/distribution/13.2/iso/

    just find it and click on it and save file.

    or click on this direct link :- http://download.opensuse.org/distribution/13.2/iso/openSUSE-13.2-KDE-Live-x86_64.iso

     

    i use imagewriter in suse to then put the iso onto a usb so it's bootable, but there are other programs/ways to do it.

     

    :b33r:

     

    I miss the Disks app that I had before the update I did.

    what disks app? in what os?

     

    and congrats and good luck in your new job. :clap:


  3. don't m$ only release security updates 1ce a month unless the last update broke something then they try and release a fix as soon as possible?

     

    http://pcsupport.about.com/od/termsp/g/patch-tuesday.htm

     

    Some half-jokingly refer to the day after Patch Tuesday as Crash Wednesday, referring to the troubles that sometimes accompany a computer after the patches are installed.

     

     

    I usually start worrying once it gets to a week or 10 days without one.

    so no need to start worrying. ;)

     

    :b33r:


  4. sorry been a bit lazy today so haven't got around to it yet, just started installing a windows os on a pc so i can dual boot it with leap to give you a step by step guide.

     

    the guide will be a choice of 2 options, first choice and probably easiest will be using a live usb/cd/dvd, 2nd choice will be more complicated and will mean booting into level 3 and logging in as root because it's not possible to unmount /home when logged in as your user i believe, will know more when i start testing after getting everything setup.

     

    :b33r:


  5. what i would try and do is, copy the contents of the /home folder (make sure it's the root home folder contents you copy across, in /home will be a folder for every user on the system and it's those user folders you need to copy.) to windows partition.

     

    unmount and delete the home partition (assume / and home partitions are next to each other.) leaving free space, now you should be able to resize/expand the / partition into the free space, say 30 GB minimum, then create a new partition in the space left and mount it as home again, copy folders back from windows into home partition and that's it.

     

    :b33r:

     

    my root partitions are 40GB in size if your wondering.


  6. no idea on what the errors are or if they are anything to worry about.

     

    as to the root partition (what size is it anyway?), personally i wouldn't delete anything (way to easy to break something if you start deleting things.) and would look into expanding it if possible.

     

    :b33r:


  7. wow you have a lot of wifi hot spots near you, think there's only 5 near me. and yes that looks perfect so assume everything is as good now in linux as it is in windows, regarding wifi. :clap:

     

     

    Still getting those strings of errors on shutdown,

    which os?

     

    so things are working good now and you don't feel the need to look into anything else?

     

    :b33r:


  8. ok.

     

    if possible make sure everything is up to date with leap and also add the packman repository.

     

    how close to the wifi access point are you, don't forget the further away it is the weaker the signal is going to be anyway.

    i'm in the same room as my router and why i got a 70/70 signal when i tested.

    must admit though going by those results, it does seem to me like you don't have the new driver installed correctly yet.

     

    also is everything else working ok now?

    main concern is that you can boot into windows any time you like without problems and can also boot into leap when you feel like trying to sort through it's issues, so you don't feel the need to keep re-install things and starting from scratch any more.

     

    :b33r:


  9.  

    The reason I reinstalled Win was because you should be able to access the Win partition through Linux if you run as root. This is the message I get:

    the reason you can't access the windows partition when in linux i believe is because when you left the windows os it shuts down in such a way that makes booting windows again fast, (called fast startup.) it's a sort of hibernate and not a full shutdown of the os and locks the partition.

     

    so the answer to that is to not use fast startup.

     

    When you shut down a computer with Fast Startup enabled, Windows locks down the Windows hard disk. You won’t be able to access it from other operating systems if you have your computer configured to dual-boot. Even worse, if you boot into another OS and then access or change anything on the hard disk (or partition) that the hibernating Windows installation uses, it can cause corruption. If you’re dual booting, it’s best not to use Fast Startup or Hibernation at all.

    http://www.howtogeek.com/243901/the-pros-and-cons-of-windows-10s-fast-startup-mode/

     

    ok when that's done you shouldn't have any more problems booting either windows or leap, plus you should now be able to access the windows partition when in leap.

     

    now onto the wifi driver.

    did it make and install ok, did you add the options file?

    lets see what results you get for each ant_sel option, so you run these commands.

    sudo modprobe -v rtl8723be ant_sel=0
    sudo iwlist wlan0 scan | egrep "SSID|level"
    
    

    we want something like this :- "Quality=70/70 Signal level=-28 dBm" where it shows the quality=70/70 for your ssid, then we know it works and your using the correct option for best wifi reception.

    sudo modprobe -v rtl8723be ant_sel=1
    sudo iwlist wlan0 scan | egrep "SSID|level"
    
    
    sudo modprobe -v rtl8723be ant_sel=2
    sudo iwlist wlan0 scan | egrep "SSID|level"
    
    

    regardless of wifi strength first thing i'd do is a zypper -v up, to make sure default install is fully upto date with latest kernel, after that you will probably need to make the wifi driver again and test if it installed a new kernel.

     

     

    Sometimes if I step away for a minute from Leap, the screen goes blank and then when I go to restore it with a move of the mouse, the display goes haywire and I have to cold reboot.

    sounds like a graphics driver problem, easy option for now is to turn off screen saver and any screen power saving options, then we'll work on that later.

     

    :b33r:


  10.  

    It is all bloody wack.

    that doesn't really tell us what issues you had that made you think you needed to reinstall both leap and windows.

     

    i think you need to slow down and not get to click happy. :P

     

    in my opinion there was no reason to re-install either leap or windows.

    no idea why leap only offered you the chance to only install to windows partition but during leap install have you ever used the expert partitioning? in there you could see what partitions are on the drive and then just re-install leap to the partitions it's already used.

     

    errors during make usually just mean missing dependencies, when i install suse i always add the patterns for

    linux kernel development

    kde development

    base development

    c/c++ development

     

    then i usually find i have no problems when it comes to making my drivers.

     

    don't be in such a rush and take notes, stop when unsure, post what you've done so far then carry on when you have an answer.

     

    never used a laptop with uefi and windows 10 on it, so no experience with what problems windows 10 may cause when dual booting but i'm sure we can work any issues out just as long as you can be a bit more patient and post the problems before trying to fix them and starting from scratch all the time. ;)

     

    :b33r:


  11.  

    But this dual boot is not working for me.

    why what's the specific problem?

     

    are you having any problems with dual booting besides the wifi in suse?

    like are you having problems logging into either os on start up, if so explain them and i'm sure there's a simple solution just finding it sometimes can be a hassle.

     

    there really shouldn't be a need to keep re-installing suse for example.

     

    personally as long as you can boot into both operating systems then i'd leave suse on there and just work on any linux issues when you feel like it, and when you don't just log into the windows os and use that.

     

    as i said before though it's up to you but if you decide to try again sometime then we'll be here to try and help.

     

    just for info any pc that came with windows i would always leave windows os and recovery partitions on there and just set up a dual boot system that way when it came time to sell or give the pc away i wouldn't need to spend hours restoring it to factory condition.

     

    :b33r:


  12. to be honest from my understanding the ant_sel option makes no difference without first installing the newer driver.

    instructions are open a terminal and enter each of these commands

    git clone https://github.com/lwfinger/rtlwifi_new
    

    you'll now see a new folder in your home directory called rtlwifi_new.

    cd rtlwifi_new
    
    git checkout rock.new_btcoex
    
    make
    
    sudo make install
    
    sudo modprobe -rv rtl8723be
    
    sudo modprobe -v rtl8723be ips=0 ant_sel=0

    see what it works like now.

    if it now works fine then i think all you need in the config file is

    options rtl8723be ips=0 ant_sel=0
    

    if still have problems then try the ant_sel=1 or 2 and test each time.

    :b33r:

     

    you will need to follow instructions from the cd rtlwifi_new command every time your kernel is updated and breaks things so your wifi has a weak signal and the driver needs to be installed again to get a strong signal. (until of course the new kernel includes the latest driver. which is kernel 4.7 i believe.)


  13. ok.

     

    just for info, with a uefi dual boot, there are 2 ways to make sure it shows the grub menu on boot, first and best way in my opinion is what you've done and set it in the uefi and 2nd way is when in windows use bcdedit command.

    with secure boot enabled :- bcdedit /set {bootmgr} path \EFI\opensuse\shim.efi

    with secure boot disabled :- bcdedit /set {bootmgr} path \EFI\opensuse\grbx64.efi

    more info here :- https://tweakhound.com/2015/11/04/dual-boot-opensuse-leap-and-windows-10-uefi/

     

    as to the weak wifi signal, try adding a file named "rtl8723be.conf" (without quotes.) with this line in it.

    options rtl8723be ips=N fwlps=N swlps=N swenc=Y disable_watchdog=Y ant_sel=2 msi=1
    

    in the /etc/modprobe.d/ folder.

     

    no idea what all the options are for without more research, but worth a try to see if it helps you anyway, and if it doesn't you can always delete the file.

     

    :b33r:


  14. ok. lets start from beginning then.

     

    you shouldn't need to tap F9 to get an option to boot into leap if you have a dual boot setup, so sounds like you don't have a dualboot setup and just have leap installed on a flash drive (not recommended, way to many problems running from a flash drive in my experience.) which you boot by using the F9 key.

     

    just to check though in windows go into disk management and take a screenshot of your hard drives partitions and post it in next reply.

     

    once i see that we'll decide on what to do next, depending on what you want.

     

    creating a dualboot system will not overwrite your windows os and the first thing you'd do is shrink the windows 10 partition, leaving a certain amount of space free which is where the suse os will get installed, once installed the first thing you'd see is a menu to boot either leap or windows 10 without the need to tap any F keys.

    after install which os you set to boot as default if you don't make a choice is up to you but will be suse until you change it.

     

    :b33r:


  15.  

    i made lots of edits to previous post that you may have missed so please make sure you read everything there.

     

    Yes Terry, I could just copy-and-paste, but I don't know how to do that and then exit Leap and open Win 10 to post it.

    paste the terminal into a file saved on the windows partition then you can simply copy and paste from there into your reply's.

     

    Should I be using WPA-EAP or WPA-PSK in Yast setup. Infrastructure or Ad-hoc in NetworkManager? This is probably where I am bollocksing it up.

    depends on what encryption is being used but without checking i'd say it's usually "wpa-psk" in yast, and "wpa-psk2 personal" in manager.

    and for mode type in network manager again without testing i'd select infrastructure.

     

    but really you shouldn't need to manually add your network, and it should show up by doing a scan.

     

     

    Sometimes the taskbar icon shows my network, other times it won't. When it does, it will show the password entry box but after trying to connect it will fail. I'll try it again and get back to the Pit with the update.

    ok will need to look into that, as long as wifi networks show up then you know the driver is installed and the device is up and running, and if it doesn't connect we'll need to figure out why. if you've manually added a wifi network connection go into settings and delete them all so we're starting clean.

     

    :b33r:


  16. just for future reference kurt, you can just copy out of the terminal and then paste it into a reply, (preferable using a code box, <> next to quote icon.)

    linux-lm5d:/home/leap42.1 # ifconfig -a
    eth0      Link encap:Ethernet  HWaddr 00:1F:D0:DB:F0:E5  
              inet addr:192.168.1.2  Bcast:192.168.1.255  Mask:255.255.255.0
              inet6 addr: fe80::21f:d0ff:fedb:f0e5/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:433727 errors:0 dropped:4 overruns:0 frame:0
              TX packets:253943 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000 
              RX bytes:575092048 (548.4 Mb)  TX bytes:21149585 (20.1 Mb)
    
    lo        Link encap:Local Loopback  
              inet addr:127.0.0.1  Mask:255.0.0.0
              inet6 addr: ::1/128 Scope:Host
              UP LOOPBACK RUNNING  MTU:65536  Metric:1
              RX packets:654 errors:0 dropped:0 overruns:0 frame:0
              TX packets:654 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0 
              RX bytes:37076 (36.2 Kb)  TX bytes:37076 (36.2 Kb)
    
    wlan0     Link encap:Ethernet  HWaddr 00:1F:33:FE:16:E8  
              UP BROADCAST MULTICAST  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000 
              RX bytes:0 (0.0   TX bytes:0 (0.0 

    things look ok, just the eth0 and wlan0 are shutdown so i think it's just a case of configuring it to start them. (should have "UP BROADCAST MULTICAST MTU=1500 Metric:1" if started i believe, plus an ip address when connected of course.

     

    i assume you want to use network manager and not yast, go into yast under network settings, global options make sure networkmanager service is selected where it says network setup method. click ok and exit yast.

     

    now in the task bar bottom right you should see the networks icon, click on it and in the popup box does it find and show any wifi networks?

     

    if so just click on your wifi network where it says connect, a password box opens. enter your password and that should be it.

     

    :b33r:

     

    if no networks show up in networkmanager to connect to, then in a terminal as root type in

    ip link set wlan0 up
    
    

    and try again.

    linux-lm5d:/home/leap42.1 # ip link set wlan0 down
    linux-lm5d:/home/leap42.1 # ifconfig -a           
    eth0      Link encap:Ethernet  HWaddr 00:1F:D0:DB:F0:E5  
              inet addr:192.168.1.2  Bcast:192.168.1.255  Mask:255.255.255.0
              inet6 addr: fe80::21f:d0ff:fedb:f0e5/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:434618 errors:0 dropped:4 overruns:0 frame:0
              TX packets:254845 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000 
              RX bytes:575428860 (548.7 Mb)  TX bytes:21260923 (20.2 Mb)
    
    lo        Link encap:Local Loopback  
              inet addr:127.0.0.1  Mask:255.0.0.0
              inet6 addr: ::1/128 Scope:Host
              UP LOOPBACK RUNNING  MTU:65536  Metric:1
              RX packets:654 errors:0 dropped:0 overruns:0 frame:0
              TX packets:654 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0 
              RX bytes:37076 (36.2 Kb)  TX bytes:37076 (36.2 Kb)
    
    wlan0     Link encap:Ethernet  HWaddr 00:1F:33:FE:16:E8  
              BROADCAST MULTICAST  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000 
              RX bytes:0 (0.0   TX bytes:0 (0.0 
    
    linux-lm5d:/home/leap42.1 # ip link set wlan0 up
    linux-lm5d:/home/leap42.1 # ifconfig -a
    eth0      Link encap:Ethernet  HWaddr 00:1F:D0:DB:F0:E5  
              inet addr:192.168.1.2  Bcast:192.168.1.255  Mask:255.255.255.0
              inet6 addr: fe80::21f:d0ff:fedb:f0e5/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:435060 errors:0 dropped:4 overruns:0 frame:0
              TX packets:255299 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000 
              RX bytes:575597792 (548.9 Mb)  TX bytes:21423264 (20.4 Mb)
    
    lo        Link encap:Local Loopback  
              inet addr:127.0.0.1  Mask:255.0.0.0
              inet6 addr: ::1/128 Scope:Host
              UP LOOPBACK RUNNING  MTU:65536  Metric:1
              RX packets:654 errors:0 dropped:0 overruns:0 frame:0
              TX packets:654 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0 
              RX bytes:37076 (36.2 Kb)  TX bytes:37076 (36.2 Kb)
    
    wlan0     Link encap:Ethernet  HWaddr 00:1F:33:FE:16:E8  
              UP BROADCAST MULTICAST  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000 
              RX bytes:0 (0.0   TX bytes:0 (0.0 
    
    linux-lm5d:/home/leap42.1 # 
    
    

    notice when i shut the wlan0 device off using "ip link set wlan0 down" command it says "BROADCAST MULTICAST MTU:1500 Metric:1" and when i start it up again using the "ip link set wlan0 up" command it says "UP BROADCAST MULTICAST MTU:1500 Metric:1"

     

    yours needs to say "UP BROADCAST MULTICAST MTU:1500 Metric:1" and then you should find everything will work fine, fingers crossed. :mrgreen:


  17. you having problems with lan connected by wire, or wlan wifi connection? think you want help with wifi but not 100% sure.

     

    i'll need to find a wifi device so i can jog my memory on using wifi, until then open a terminal and as root type

    ifconfig -a
    

    and post the results.

     

    next type in

    ethtool -i wlan0
    

    and post the results for that too

     

    first command will show all network devices, 2nd command shows what driver is used for wifi device.

     

    :b33r:


  18.  

    Does Windows show that the Anniversary update was installed? Where? Mine just says Windows 10 Pro under computer Properties.

     

     

    I understand that you would like to view all your installed Windows updates on your system. Follow the steps on how to view installed Windows updates:

    1. Right click on the Start Menu and select Control Panel.
    2. Now select Programs and features.
    3. From the left side of the page select the option View Installed Updates.
    4. Now you will see the complete list of all Windows updates which is installed on your system.

    http://answers.microsoft.com/en-us/windows/forum/windows_10-update/where-to-find-windows-10-updates-list/3e0e1b3a-e44a-4aa2-a012-2f9415d2f1d5?auth=1

     

    this may be useful :- https://support.microsoft.com/en-us/help/12387/windows-10-update-history

     

    :b33r:


  19. i really wouldn't bother duan, just the heatsink will keep it cool enough i'd think, plus then you have the benefit of a total silent device without any fan wine to annoy you, if you find it does reach temps high enough to cause it to throttle and cause problems, only then i'd think about adding a fan.

     

    anyway have you had it up and running and tested kodi on it yet, and if so what os did you put on it?

     

    :b33r:


  20. nobody was asking "why?" :P

     

    and i can see the point in owning one, lots of things you can do with a small, low powered, cheap pc as shown by the loads of different projects people have used one for.

     

    :b33r:

×
×
  • Create New...