[opensuse] Howto boot HP elitebook 8760w in legacy mode?
All, I've gotten a new old laptop (HP EliteBook 8760w) and I cannot get it to boot. It came with Win10 which boots in Legacy mode and all UEFI options in the bios disabled. I've tried a traditions MBR setup: # fdisk -l /dev/sda Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0xff7d45aa Device Boot Start End Sectors Size Id Type /dev/sda1 2048 1953525167 1953523120 931.5G 5 Extended /dev/sda5 * 4096 1028095 1024000 500M 83 Linux /dev/sda6 1030144 105887743 104857600 50G 83 Linux /dev/sda7 105889792 1951383551 1845493760 880G 83 Linux /dev/sda8 1951385600 1953525167 2139568 1G 82 Linux swap / Solaris I've tried GPT with bios_boot: # fdisk -l /dev/sda Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 00B6A48C-CBDB-4071-A1EC-97FA828A6C26 Device Start End Sectors Size Type /dev/sda1 2048 4095 2048 1M BIOS boot /dev/sda2 4096 1028095 1024000 500M Linux filesystem /dev/sda3 1028096 105885695 104857600 50G Linux filesystem /dev/sda4 105885696 1949282303 1843396608 879G Linux filesystem /dev/sda5 1949282304 1951379455 2097152 1G Linux swap I've even tried enabling UEFI and partitioning with a UEFI scheme and booting via systemd, no joy: # fdisk -l /dev/sda Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 00B6A48C-CBDB-4071-A1EC-97FA828A6C26 Device Start End Sectors Size Type /dev/sda1 2048 4095 2048 1M BIOS boot /dev/sda2 4096 1028095 1024000 500M EFI System /dev/sda3 1028096 105885695 104857600 50G Linux filesystem /dev/sda4 105885696 1949282303 1843396608 879G Linux filesystem /dev/sda5 1949282304 1951379455 2097152 1G Linux swap (on this model use of UEFI is not recommended -- which explains why it was disabled to begin with) The odd thing about it is I can boot with any .iso with grub and choose to "Boot existing OS" (changing 'hd0 0' to 'hd1 0') and boot just fine. I just have to boot from USB because the laptop will not see grub any other way. Has anyone else encountered a stubborn HP laptop that takes something out of the ordinary to boot with a simple MBR setup? The frustrating thing is I can throw the Win10 disk back in and it boots just fine. Nothing explains to my why I can boot from an .iso in legacy mode just fine, but cannot boot from the hard drive the same way. There have been no errors on grub install or on grub.cfg generation (the problem is it is just not seeing grub on the drive to begin with) grub is right where it should be, because choosing "Boot existing OS" brings the grub menu right up and boots to a fully functioning install. Currently I'm working with the Arch .iso given the direct access to grubs command line. Does anybody have any thoughts on what to check to see what is causing the bootloader being missed on the hard drives? In nearly 20 years of Linux, probably 50-100 installs, this is the first time I've ever run into a box that just will not see grub on a hard drive. I've reset bios defaults, pulled all batteries, held the power on to drain any residual power, etc.. and the issue isn't an embedded drive signature the box is trying to boot (it wouldn't like the USB if that were the case.) All Disk Lock and other bios security features are disabled. (the bios is actually a very limited laptop bios with very few settings to complicate things.) It's not a question of the laptop not seeing the drive. I've installed a full plasma/KDE5 setup on the drive, I just have to boot it from a darn USB. Does the braintrust have an tips or diagnostics that may shed light on this issue? -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon 07 Nov 2016 03:57:49 PM CST, David C. Rankin wrote:
All,
I've gotten a new old laptop (HP EliteBook 8760w) and I cannot get it to boot. It came with Win10 which boots in Legacy mode and all UEFI options in the bios disabled.
I've tried a traditions MBR setup:
# fdisk -l /dev/sda Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0xff7d45aa
Device Boot Start End Sectors Size Id Type /dev/sda1 2048 1953525167 1953523120 931.5G 5 Extended /dev/sda5 * 4096 1028095 1024000 500M 83 Linux /dev/sda6 1030144 105887743 104857600 50G 83 Linux /dev/sda7 105889792 1951383551 1845493760 880G 83 Linux /dev/sda8 1951385600 1953525167 2139568 1G 82 Linux swap / Solaris
I've tried GPT with bios_boot:
# fdisk -l /dev/sda Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 00B6A48C-CBDB-4071-A1EC-97FA828A6C26
Device Start End Sectors Size Type /dev/sda1 2048 4095 2048 1M BIOS boot /dev/sda2 4096 1028095 1024000 500M Linux filesystem /dev/sda3 1028096 105885695 104857600 50G Linux filesystem /dev/sda4 105885696 1949282303 1843396608 879G Linux filesystem /dev/sda5 1949282304 1951379455 2097152 1G Linux swap
I've even tried enabling UEFI and partitioning with a UEFI scheme and booting via systemd, no joy:
# fdisk -l /dev/sda Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 00B6A48C-CBDB-4071-A1EC-97FA828A6C26
Device Start End Sectors Size Type /dev/sda1 2048 4095 2048 1M BIOS boot /dev/sda2 4096 1028095 1024000 500M EFI System /dev/sda3 1028096 105885695 104857600 50G Linux filesystem /dev/sda4 105885696 1949282303 1843396608 879G Linux filesystem /dev/sda5 1949282304 1951379455 2097152 1G Linux swap
(on this model use of UEFI is not recommended -- which explains why it was disabled to begin with)
The odd thing about it is I can boot with any .iso with grub and choose to "Boot existing OS" (changing 'hd0 0' to 'hd1 0') and boot just fine. I just have to boot from USB because the laptop will not see grub any other way.
Has anyone else encountered a stubborn HP laptop that takes something out of the ordinary to boot with a simple MBR setup? The frustrating thing is I can throw the Win10 disk back in and it boots just fine. Nothing explains to my why I can boot from an .iso in legacy mode just fine, but cannot boot from the hard drive the same way. There have been no errors on grub install or on grub.cfg generation (the problem is it is just not seeing grub on the drive to begin with)
grub is right where it should be, because choosing "Boot existing OS" brings the grub menu right up and boots to a fully functioning install. Currently I'm working with the Arch .iso given the direct access to grubs command line. Does anybody have any thoughts on what to check to see what is causing the bootloader being missed on the hard drives?
In nearly 20 years of Linux, probably 50-100 installs, this is the first time I've ever run into a box that just will not see grub on a hard drive.
I've reset bios defaults, pulled all batteries, held the power on to drain any residual power, etc.. and the issue isn't an embedded drive signature the box is trying to boot (it wouldn't like the USB if that were the case.) All Disk Lock and other bios security features are disabled. (the bios is actually a very limited laptop bios with very few settings to complicate things.)
It's not a question of the laptop not seeing the drive. I've installed a full plasma/KDE5 setup on the drive, I just have to boot it from a darn USB.
Does the braintrust have an tips or diagnostics that may shed light on this issue?
Hi Won't boot with disk gpt, unless it's set as hybrid? Use gdisk with gpt; gdisk -l /dev/sda Wipe the gpt and set the disk to dos, plus clean out the mbr (can do this with gdisk x and z keys, destructive so if no data wanted on the disk reset the disk to dos and then use legacy boot. Maybe UEFI is troublesome because the UEFI defaults to "Windows Boot Manager" and doesn't respect the UEFI boot order... there are ways around this if only single booting. Check for a BIOS update as well if want to stick with UEFI. -- Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890) openSUSE Leap 42.1|GNOME 3.16.2|4.1.34-33-default up 9 days 6:36, 4 users, load average: 0.60, 0.38, 0.38 CPU AMD Athlon(tm) II X4 635 @ 2.90GHz | GPU Nvidia GeForce 8800 GT -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
(sorry Malcom, you get 2-copies, I forgot to change the reply-to address :) On 11/07/2016 05:42 PM, Malcolm wrote:
Hi Won't boot with disk gpt, unless it's set as hybrid?
Use gdisk with gpt;
gdisk -l /dev/sda
Wipe the gpt and set the disk to dos, plus clean out the mbr (can do this with gdisk x and z keys, destructive so if no data wanted on the disk reset the disk to dos and then use legacy boot.
Thanks Malcolm, I've actually got 2 disks I'm messing with (laptop has 3 disk bays - 1 holding the CD/DVD and 2 hard drive bays). The MBR disk has the full install, the GPT disk has just the minimal install to work with the different boot setups to find one that works.
Maybe UEFI is troublesome because the UEFI defaults to "Windows Boot Manager" and doesn't respect the UEFI boot order... there are ways around this if only single booting. Check for a BIOS update as well if want to stick with UEFI.
UEFI was incorporated by HP as 'Experimental' on this laptop (2011-2012) and disabled by default. That is what has me so confused. Win10 boots fine in Legacy mode (UEFI has always been *completely* disabled in the bios until I turned it on to test the UEFI boot) An then you get a big warning screen about the experimental state of the UEFI implementation. I've confirmed the legacy setup windows uses via both bcdedit /enum as well as msinfo32, UEFI should not be involved at all in the boot process. What concerns me is the quasi (or part) implementation that may be following some stray path set by windows that prevents grub from being seen (I know virtually nothing about the modern windows side of things) But without UEFI active in the bios, I don't see how any of the UEFI NVRAM settings could derail grub (but something is doing it). Further, if that was the case, how is it that it boots from USB flawlessly. I'll keep picking away at this one, but if anyone has any other ideas or other diagnostics that may shed light on this, I would appreciate your input as well. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue 08 Nov 2016 04:34:17 AM CST, David C. Rankin wrote: <snip>
I'll keep picking away at this one, but if anyone has any other ideas or other diagnostics that may shed light on this, I would appreciate your input as well.
Hi So if you have drives to play with, I usually do manual installs of windows (7, 8.1 or 10) and openSUSE/SLE eg UEFI; Windows 10, SLED, openSUSE 42.2 and openSUSE Tumbleweed; lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 111.8G 0 disk ├─sda1 8:1 0 260M 0 part /boot/efi (boots TW and SLED) ├─sda2 8:2 0 40G 0 part ├─sda3 8:3 0 40G 0 part / └─sda4 8:4 0 31.5G 0 part /data sdb 8:16 0 111.8G 0 disk ├─sdb1 8:17 0 300M 0 part ├─sdb2 8:18 0 100M 0 part (Boots WinX and 42.2) ├─sdb3 8:19 0 128M 0 part ├─sdb4 8:20 0 62.9G 0 part ├─sdb5 8:21 0 450M 0 part (Windows needed to upgrade the build) ├─sdb6 8:22 0 8G 0 part [SWAP] └─sdb7 8:23 0 40G 0 part For MBR I normally allocate an extended partition and set grub there, eg; sda1: 100M sda2: Windows sda3: extended sda5: /boot sda6..7 etc as required Now I wonder since it's windows 10 on MBR it still needs extra partitions. For windows UEFI it does need a 0c01 of 128MB, windows 10 has an extra 300MB type 2700 one as well... -- Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890) openSUSE Leap 42.1|GNOME 3.16.2|4.1.34-33-default up 9 days 19:26, 3 users, load average: 0.17, 0.17, 0.24 CPU AMD Athlon(tm) II X4 635 @ 2.90GHz | GPU Nvidia GeForce 8800 GT -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue 08 Nov 2016 07:28:04 AM CST, Malcolm wrote:
On Tue 08 Nov 2016 04:34:17 AM CST, David C. Rankin wrote:
<snip>
I'll keep picking away at this one, but if anyone has any other ideas or other diagnostics that may shed light on this, I would appreciate your input as well.
Hi So if you have drives to play with, I usually do manual installs of windows (7, 8.1 or 10) and openSUSE/SLE
eg UEFI; Windows 10, SLED, openSUSE 42.2 and openSUSE Tumbleweed;
lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 111.8G 0 disk ├─sda1 8:1 0 260M 0 part /boot/efi (boots TW and SLED) ├─sda2 8:2 0 40G 0 part ├─sda3 8:3 0 40G 0 part / └─sda4 8:4 0 31.5G 0 part /data sdb 8:16 0 111.8G 0 disk ├─sdb1 8:17 0 300M 0 part ├─sdb2 8:18 0 100M 0 part (Boots WinX and 42.2) ├─sdb3 8:19 0 128M 0 part ├─sdb4 8:20 0 62.9G 0 part ├─sdb5 8:21 0 450M 0 part (Windows needed to upgrade the build) ├─sdb6 8:22 0 8G 0 part [SWAP] └─sdb7 8:23 0 40G 0 part
For MBR I normally allocate an extended partition and set grub there, eg;
sda1: 100M sda2: Windows sda3: extended sda5: /boot sda6..7 etc as required
Now I wonder since it's windows 10 on MBR it still needs extra partitions.
For windows UEFI it does need a 0c01 of 128MB, windows 10 has an extra 300MB type 2700 one as well...
Hi Also I had a HP ProBook 4330s that was in that category, I just hacked it with the grub file renamed and popped into /boot/efi/EFI/BOOT (maybe case sensitive?), but just left as a single boot system... The HP ProBook 4440s worked fine. If push comes to shove, just press F9 and select the efi entry to boot from? My HP ProBook 455 G1 was a bit funky, wanted CSM to install winX, then would work in Native mode after that for dual booting. I would look at upgrading the BIOS and you might find changes (check the release notes at the download page as well as any previous releases). I have a HP Pavilion g6 with win8.1, need to have a play with that once I get some time to clean out the blocked fan... -- Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890) openSUSE Leap 42.1|GNOME 3.16.2|4.1.34-33-default up 9 days 21:16, 3 users, load average: 0.30, 0.43, 0.28 CPU AMD Athlon(tm) II X4 635 @ 2.90GHz | GPU Nvidia GeForce 8800 GT -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/08/2016 08:27 AM, Malcolm wrote:
Hi Also I had a HP ProBook 4330s that was in that category, I just hacked it with the grub file renamed and popped into /boot/efi/EFI/BOOT (maybe case sensitive?), but just left as a single boot system... The HP ProBook 4440s worked fine.
If push comes to shove, just press F9 and select the efi entry to boot from?
My HP ProBook 455 G1 was a bit funky, wanted CSM to install winX, then would work in Native mode after that for dual booting.
I would look at upgrading the BIOS and you might find changes (check the release notes at the download page as well as any previous releases).
I have a HP Pavilion g6 with win8.1, need to have a play with that once I get some time to clean out the blocked fan...
Yes, this just keeps getting stranger. The windows 10 driver (128G SSD) is MBR and the only boot files on the driver are: bootmgr BOOTNXT BOOTSECT.BAK BOOTBCD BOOTSTAT.DAT bootvhd.dll en-us bootmgr.exe.mui memtest.ext.mui That's plane-Jane MBR legacy boot. I'm not worried about dual booting at all, I just take the windows drive out and put it on a shelf. I'm just concerned with getting the box to boot something other than windows. The only other plausible explanation I've read about is the difficulty some elitebooks have with large drive recognition. The concern SSD's and not normal platter drives, but I haven't run into any reasonably recent bios that doesn't recognize 1T drives. I'm still completely bewildered by the situation. I've probably done 50-100 installs in the past 16-17 years and I've not run into this situation before. Thanks you for your suggestions, I'll keep picking at this problem. Other than this boot problem, the rest of the box is working fine. I've done a full plasma/kde install, and am writing this from tbird on the MBR drive -- I just have to boot from USB (one heck of an unintended security feature...) -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue 08 Nov 2016 05:48:56 PM CST, David C. Rankin wrote:
On 11/08/2016 08:27 AM, Malcolm wrote:
Hi Also I had a HP ProBook 4330s that was in that category, I just hacked it with the grub file renamed and popped into /boot/efi/EFI/BOOT (maybe case sensitive?), but just left as a single boot system... The HP ProBook 4440s worked fine.
If push comes to shove, just press F9 and select the efi entry to boot from?
My HP ProBook 455 G1 was a bit funky, wanted CSM to install winX, then would work in Native mode after that for dual booting.
I would look at upgrading the BIOS and you might find changes (check the release notes at the download page as well as any previous releases).
I have a HP Pavilion g6 with win8.1, need to have a play with that once I get some time to clean out the blocked fan...
Yes, this just keeps getting stranger. The windows 10 driver (128G SSD) is MBR and the only boot files on the driver are:
bootmgr BOOTNXT BOOTSECT.BAK BOOTBCD BOOTSTAT.DAT bootvhd.dll en-us bootmgr.exe.mui memtest.ext.mui
That's plane-Jane MBR legacy boot. I'm not worried about dual booting at all, I just take the windows drive out and put it on a shelf. I'm just concerned with getting the box to boot something other than windows.
The only other plausible explanation I've read about is the difficulty some elitebooks have with large drive recognition. The concern SSD's and not normal platter drives, but I haven't run into any reasonably recent bios that doesn't recognize 1T drives.
I'm still completely bewildered by the situation. I've probably done 50-100 installs in the past 16-17 years and I've not run into this situation before.
Thanks you for your suggestions, I'll keep picking at this problem. Other than this boot problem, the rest of the box is working fine. I've done a full plasma/kde install, and am writing this from tbird on the MBR drive -- I just have to boot from USB (one heck of an unintended security feature...)
Hi If you press the F9 key, do you see something like "OS boot Manager"? I tried out the g6, UEFI though, it adds the HDD boot order back, so if wanting single boot would need to create a systemd service to reset the boot order with efibootmgr -n NNNN to it's entry would overcome this. -- Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890) openSUSE Leap 42.1|GNOME 3.16.2|4.1.34-33-default up 10 days 7:56, 3 users, load average: 0.27, 0.28, 0.48 CPU AMD Athlon(tm) II X4 635 @ 2.90GHz | GPU Nvidia GeForce 8800 GT -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/8/2016 7:09 PM, Malcolm wrote:
Hi If you press the F9 key, do you see something like "OS boot Manager"?
I tried out the g6, UEFI though, it adds the HDD boot order back, so if wanting single boot would need to create a systemd service to reset the boot order with efibootmgr -n NNNN to it's entry would overcome this.
Yes, I tried enabling UEFI and get a big WARNING, UEFI is provided as experimental only and not recommended. (this laptop is circa 2011-2012 and the UEFI implementation by HP, was experimental only and disabled by default) Enabling UEFI and creating the fat32 partition and systemd service results in a blinking underline in the middle of the screen and then ... 'nothing' (windows won't even boot with UEFI enabled) The only thing that I'm reading that makes sense, is that despite having UEFI disabled, HP embedded/hardcoded the path the bootmgr.exe in the firmware, which the firmware uses in some way as part of its boot scheme. The frustrating part, is I can boot syslinux from the iso just fine and then load grub flawlessly. (even the 1600x900-32 vesafb mode is set correctly despite using the Nvidia proprietary drivers.) Oh, well, I'm going to keep working on it. Currently I have the windows SSD drive in bay 1, the 1T platter drive in bay 2, and since I have to set the clock anyway between Win and Linux boots (I'm not hacking the Win10 registry to put the UTC cludge in), I just pop an iso in the USB port and boot with the iso, then boot the Linux install as 'hd2 0'. (which loads grub2 from the MBR just fine) My goal is to remove the windows drive altogether, and virtualize windows (I have hardware support in the CPU), but that will have to wait until the boot issue is solved. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun 13 Nov 2016 11:31:27 AM CST, David C. Rankin wrote:
On 11/8/2016 7:09 PM, Malcolm wrote:
Hi If you press the F9 key, do you see something like "OS boot Manager"?
I tried out the g6, UEFI though, it adds the HDD boot order back, so if wanting single boot would need to create a systemd service to reset the boot order with efibootmgr -n NNNN to it's entry would overcome this.
Yes, I tried enabling UEFI and get a big WARNING, UEFI is provided as experimental only and not recommended.
(this laptop is circa 2011-2012 and the UEFI implementation by HP, was experimental only and disabled by default)
Enabling UEFI and creating the fat32 partition and systemd service results in a blinking underline in the middle of the screen and then ... 'nothing' (windows won't even boot with UEFI enabled)
The only thing that I'm reading that makes sense, is that despite having UEFI disabled, HP embedded/hardcoded the path the bootmgr.exe in the firmware, which the firmware uses in some way as part of its boot scheme.
The frustrating part, is I can boot syslinux from the iso just fine and then load grub flawlessly. (even the 1600x900-32 vesafb mode is set correctly despite using the Nvidia proprietary drivers.)
Oh, well, I'm going to keep working on it. Currently I have the windows SSD drive in bay 1, the 1T platter drive in bay 2, and since I have to set the clock anyway between Win and Linux boots (I'm not hacking the Win10 registry to put the UTC cludge in), I just pop an iso in the USB port and boot with the iso, then boot the Linux install as 'hd2 0'. (which loads grub2 from the MBR just fine)
My goal is to remove the windows drive altogether, and virtualize windows (I have hardware support in the CPU), but that will have to wait until the boot issue is solved.
Hi You would need to install Windows in UEFI mode... download the latest build and do a test install? Grab your product key via ProduKey, I dump the folder on my windows install USB devices, I also remove the ei.cfg file to allow any win version to install. I use the RealTimeIsUniversal hack, works fine... No CSM mode to UEFI boot, or just UEFI and Legacy? Disable fastboot as well if there is a BIOS option. -- Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890) openSUSE Leap 42.1|GNOME 3.16.2|4.1.34-33-default up 1 day 2:34, 3 users, load average: 2.49, 2.37, 2.18 CPU AMD Athlon(tm) II X4 635 @ 2.90GHz | GPU Nvidia GeForce 8800 GT -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (2)
-
David C. Rankin
-
Malcolm