08-16-2014, 05:40 AM
Gold_finger, many thanks for the above, which I will try in the next few days while I still have some vacation left...!
A more basic problem with my laptop has presented itself in the last couple of days. I'm unsure whether it's a hardware issue and whether it can be resolved using the terminal.
For some reason. that I'm unable to fathom, the internal drives sda and sdb are not working together in a coordinated way. I'll just clarify this. Earlier this month, to maximise efficiency of operation, I put the core part of the distro OS on sda, and the /home, /mnt/DATA, and swap on sdb. It worked very well and I noticed, as you'd expect, a much crisper snappier response from the computer with open/closing files etc. However, this doesn't happen any longer. The entirety of the OS has to be installed on either sda or sda - no sharing of parts of the OS between sda & sdb works any more as I just get a blank (black) screen on boot up (i.e. no grub screen appears) and it just stays like that with the cursor blinking indefinitely. Curiously, the laptop will run two distros separately, that is one installed entirely on sda, the other on sdb and will show both of these listed on the grub screen at boot up.
The only thing that has changed with my set-up was that I bought a USB games steering wheel for my young son so that he could play supertuxkart. A few days later (after he began playing with this) the laptop cut out one day and powered off. The 3A fuse in the plug had blown and was replaced. I also noticed flicker with the graphics after this at the beginning of a game but it disappeared once the game was underway. At the time, with the steering wheel set-up, I was only using an OS installed entirely on sda. However since then I have lost coordinated operation between sda and sdb as described in the first para above. I don't know whether the two are linked and whether I can retrieve normal sda/sdb shared OS operation as before through the use of the terminal.
I'd be grateful for any views or ideas you might have on this. I'm hoping it is not time to fork out for a new laptop...
Kind regards
Mike
A more basic problem with my laptop has presented itself in the last couple of days. I'm unsure whether it's a hardware issue and whether it can be resolved using the terminal.
For some reason. that I'm unable to fathom, the internal drives sda and sdb are not working together in a coordinated way. I'll just clarify this. Earlier this month, to maximise efficiency of operation, I put the core part of the distro OS on sda, and the /home, /mnt/DATA, and swap on sdb. It worked very well and I noticed, as you'd expect, a much crisper snappier response from the computer with open/closing files etc. However, this doesn't happen any longer. The entirety of the OS has to be installed on either sda or sda - no sharing of parts of the OS between sda & sdb works any more as I just get a blank (black) screen on boot up (i.e. no grub screen appears) and it just stays like that with the cursor blinking indefinitely. Curiously, the laptop will run two distros separately, that is one installed entirely on sda, the other on sdb and will show both of these listed on the grub screen at boot up.
The only thing that has changed with my set-up was that I bought a USB games steering wheel for my young son so that he could play supertuxkart. A few days later (after he began playing with this) the laptop cut out one day and powered off. The 3A fuse in the plug had blown and was replaced. I also noticed flicker with the graphics after this at the beginning of a game but it disappeared once the game was underway. At the time, with the steering wheel set-up, I was only using an OS installed entirely on sda. However since then I have lost coordinated operation between sda and sdb as described in the first para above. I don't know whether the two are linked and whether I can retrieve normal sda/sdb shared OS operation as before through the use of the terminal.
I'd be grateful for any views or ideas you might have on this. I'm hoping it is not time to fork out for a new laptop...
Kind regards
Mike
64bit OS (32-bit on Samsung[i] netbook) installed in [i]Legacy mode on MBR-formatted SSDs (except pi which uses a micro SDHC card):
2017 - Raspberry pi 3B (4cores) ~ [email protected] - LibreElec, used for upgrading our Samsung TV (excellent for the task)
2012 - Lenovo G580 2689 (2cores; 4threads] ~ [email protected] - LL3.8/Win8.1 dual-boot (LL working smoothly)
2011 - Samsung NP-N145 Plus (1core; 2threads) ~ Intel Atom [email protected] - LL 3.8 32-bit (64-bit too 'laggy')
2008 - Asus X71Q (2cores) ~ Intel [email protected] - LL4.6/Win8.1 dual-boot, LL works fine with kernel 4.15
2007 - Dell Latitude D630 (2cores) ~ Intel [email protected] - LL4.6, works well with kernel 4.4; 4.15 doesn't work
2017 - Raspberry pi 3B (4cores) ~ [email protected] - LibreElec, used for upgrading our Samsung TV (excellent for the task)
2012 - Lenovo G580 2689 (2cores; 4threads] ~ [email protected] - LL3.8/Win8.1 dual-boot (LL working smoothly)
2011 - Samsung NP-N145 Plus (1core; 2threads) ~ Intel Atom [email protected] - LL 3.8 32-bit (64-bit too 'laggy')
2008 - Asus X71Q (2cores) ~ Intel [email protected] - LL4.6/Win8.1 dual-boot, LL works fine with kernel 4.15
2007 - Dell Latitude D630 (2cores) ~ Intel [email protected] - LL4.6, works well with kernel 4.4; 4.15 doesn't work