[opensuse] Nuisance problem with my SSD hard disk on laptop
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Content-ID:
On Thu, 15 Feb 2018 22:13:54 +0100 (CET)
"Carlos E. R."
I have a problem with my SSD hard disk on my laptop, which replaced a rotating rust disk. It is currently at the nuisance level.
When I boot, the laptop does not recognize the disk and asks to insert one and press a key.
Just to be clear. Has the problem always been there with this disk? Or did it work perfectly and then develop a problem after some time? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2018-02-15 a las 21:23 -0000, Dave Howorth escribió:
On Thu, 15 Feb 2018 22:13:54 +0100 (CET) "Carlos E. R." <> wrote:
I have a problem with my SSD hard disk on my laptop, which replaced a rotating rust disk. It is currently at the nuisance level.
When I boot, the laptop does not recognize the disk and asks to insert one and press a key.
Just to be clear. Has the problem always been there with this disk? Or did it work perfectly and then develop a problem after some time?
Yes, I had this problem with this disk since day one. Initially I thought that perhaps SSDs are special and my laptop too old or something. Today I think I should try replugging. - -- Cheers Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlqF/8QACgkQja8UbcUWM1y/qwD/Y5b6PO3sq+mHwXDlMeYdOXlZ n70oIk0BxO85OFiL2iYA/0Ly59Q8Xr4zhVuBWJWqG75I54+vIROvOWevBufgrZbG =c176 -----END PGP SIGNATURE-----
On 02/15/2018 01:46 PM, Carlos E. R. wrote:
El 2018-02-15 a las 21:23 -0000, Dave Howorth escribió:
On Thu, 15 Feb 2018 22:13:54 +0100 (CET) "Carlos E. R." <> wrote:
I have a problem with my SSD hard disk on my laptop, which replaced a rotating rust disk. It is currently at the nuisance level.
When I boot, the laptop does not recognize the disk and asks to insert one and press a key.
Just to be clear. Has the problem always been there with this disk? Or did it work perfectly and then develop a problem after some time?
Yes, I had this problem with this disk since day one.
Initially I thought that perhaps SSDs are special and my laptop too old or something. Today I think I should try replugging.
Might have something to do with bios settings I suppose. Also, how are you trimming this disk? are you relying on discard in the mtab, or are you scheduling trim with systemd. (The latter is recommended). It might be doing some sort of boot up self test, during which it is un-responsive. I not seen this problem with my SSD, which is a different brand, but still a Sata interface model. -- After all is said and done, more is said than done.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2018-02-15 a las 14:41 -0800, John Andersen escribió:
On 02/15/2018 01:46 PM, Carlos E. R. wrote:
El 2018-02-15 a las 21:23 -0000, Dave Howorth escribió:
On Thu, 15 Feb 2018 22:13:54 +0100 (CET) "Carlos E. R." <> wrote:
I have a problem with my SSD hard disk on my laptop, which replaced a rotating rust disk. It is currently at the nuisance level.
When I boot, the laptop does not recognize the disk and asks to insert one and press a key.
Just to be clear. Has the problem always been there with this disk? Or did it work perfectly and then develop a problem after some time?
Yes, I had this problem with this disk since day one.
Initially I thought that perhaps SSDs are special and my laptop too old or something. Today I think I should try replugging.
Might have something to do with bios settings I suppose.
No adjustements in BIOS exist.
Also, how are you trimming this disk?
Trimming is only possible once the machine boots. This problem is before booting. - -- Cheers Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlqGDasACgkQja8UbcUWM1wK3gD9Evg6KP4N1NEtZfjK8Iy0V/N8 umRrqwjjk4SR3myna3QA/RILhv8fGI1/OpJfrpxm8KSKR1ZPqbV3WuZFK7HBJqWK =cSad -----END PGP SIGNATURE-----
On 02/15/2018 02:46 PM, Carlos E. R. wrote:
Trimming is only possible once the machine boots. This problem is before booting.
Think outside the box Carlos..... If you weren't trimming at all, or your trim didn't work, the device might need to force a trim at boot time. -- After all is said and done, more is said than done.
On 2018-02-16 01:19, John Andersen wrote:
On 02/15/2018 02:46 PM, Carlos E. R. wrote:
Trimming is only possible once the machine boots. This problem is before booting.
Think outside the box Carlos.....
If you weren't trimming at all, or your trim didn't work, the device might need to force a trim at boot time.
Not if the disk has just been installed and was bought new... minas-tirith:~ # systemctl status fstrim.timer ● fstrim.timer - Discard unused blocks once a week Loaded: loaded (/usr/lib/systemd/system/fstrim.timer; enabled; vendor preset: enabled) Active: active (waiting) since Thu 2018-02-15 19:56:28 CET; 15h ago Docs: man:fstrim minas-tirith:~ # minas-tirith:~ # grep fstrim /var/log/messages <3.6> 2018-01-29 00:00:21 minas-tirith fstrim 7952 - - /other: 1.8 GiB (1904267264 bytes) trimmed <3.6> 2018-01-29 00:00:21 minas-tirith fstrim 7952 - - /boot: 131.6 MiB (138023936 bytes) trimmed <3.6> 2018-01-29 00:00:21 minas-tirith fstrim 7952 - - /: 10.7 GiB (11448799232 bytes) trimmed <3.6> 2018-02-05 00:00:21 minas-tirith fstrim 3094 - - /other: 1.8 GiB (1904267264 bytes) trimmed <3.6> 2018-02-05 00:00:21 minas-tirith fstrim 3094 - - /boot: 131.6 MiB (138024960 bytes) trimmed <3.6> 2018-02-05 00:00:21 minas-tirith fstrim 3094 - - /: 10.7 GiB (11472986112 bytes) trimmed <3.6> 2018-02-14 09:58:39 minas-tirith fstrim 5014 - - /other: 0 B (0 bytes) trimmed <3.6> 2018-02-14 09:58:39 minas-tirith fstrim 5014 - - /boot: 4.6 MiB (4846592 bytes) trimmed <3.6> 2018-02-14 09:58:39 minas-tirith fstrim 5014 - - /: 683.3 MiB (716529664 bytes) trimmed minas-tirith:~ # minas-tirith:~ # zgrep fstrim /var/log/messages*z minas-tirith:~ # minas-tirith:~ # fstrim --all -v /other: 1.8 GiB (1904267264 bytes) trimmed /boot: 131.1 MiB (137501696 bytes) trimmed /: 9.3 GiB (9927008256 bytes) trimmed minas-tirith:~ # Interestingly, /home is not mentioned. Nor swap. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Le 15/02/2018 à 23:46, Carlos E. R. a écrit :
Trimming is only possible once the machine boots. This problem is before booting.
is this ssd working on an other machine? (sorry if the question whas already asked) jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-02-16 07:50, jdd@dodin.org wrote:
Le 15/02/2018 à 23:46, Carlos E. R. a écrit :
Trimming is only possible once the machine boots. This problem is before booting.
is this ssd working on an other machine? (sorry if the question whas already asked)
I bought the SSD new and has only been installed in the laptop. I cloned the previous rotating rust disk into it using dd and a caddy that does sata to USB. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Le 16/02/2018 à 11:21, Carlos E. R. a écrit :
On 2018-02-16 07:50, jdd@dodin.org wrote:
Le 15/02/2018 à 23:46, Carlos E. R. a écrit :
Trimming is only possible once the machine boots. This problem is before booting.
is this ssd working on an other machine? (sorry if the question whas already asked)
I bought the SSD new and has only been installed in the laptop. I cloned the previous rotating rust disk into it using dd and a caddy that does sata to USB.
it may simply be defective... jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-02-16 12:09, jdd@dodin.org wrote:
Le 16/02/2018 à 11:21, Carlos E. R. a écrit :
On 2018-02-16 07:50, jdd@dodin.org wrote:
Le 15/02/2018 à 23:46, Carlos E. R. a écrit :
Trimming is only possible once the machine boots. This problem is before booting.
is this ssd working on an other machine? (sorry if the question whas already asked)
I bought the SSD new and has only been installed in the laptop. I cloned the previous rotating rust disk into it using dd and a caddy that does sata to USB.
it may simply be defective...
Maybe. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On Fri, 16 Feb 2018 11:21:48 +0100 Carlos E. R. wrote:
I bought the SSD new and has only been installed in the laptop. I cloned the previous rotating rust disk into it using dd and a caddy that does sata to USB.
I've only ever used e.g. Clonezilla for operations like this. As I understand it, 'dd' operates in 'raw' read/write mode, so it will dutifully replicate a complete filesystem (create an 'image') on a target device irrespective of discrepancies in various attributes like drive geometries and block sizes, assuming the target has sufficient space to hold the image. I've watched many times as Clonezilla has reported 'resizing' this or that and 'adjusting alignments' to allow for these kinds of differences. Also, I don't know the vintage of the machine, but I've encountered situations in the past where an old BIOS was originally configured at the factory to use CHS (Cylinder-Head-Sector) addressing instead of LBA (Logical Block Addressing.) They took longer to boot, ran slowly and logged many strange errors. I'm sure you'd have spotted something like this, but I've tossed it out there 'just in case' :) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2018-02-16 a las 07:36 -0500, Carl Hartung escribió:
On Fri, 16 Feb 2018 11:21:48 +0100 Carlos E. R. wrote:
I bought the SSD new and has only been installed in the laptop. I cloned the previous rotating rust disk into it using dd and a caddy that does sata to USB.
I've only ever used e.g. Clonezilla for operations like this. As I understand it, 'dd' operates in 'raw' read/write mode, so it will dutifully replicate a complete filesystem (create an 'image') on a target device irrespective of discrepancies in various attributes like drive geometries and block sizes, assuming the target has sufficient space to hold the image. I've watched many times as Clonezilla has reported 'resizing' this or that and 'adjusting alignments' to allow for these kinds of differences.
Also, I don't know the vintage of the machine, but I've encountered situations in the past where an old BIOS was originally configured at the factory to use CHS (Cylinder-Head-Sector) addressing instead of LBA (Logical Block Addressing.) They took longer to boot, ran slowly and logged many strange errors. I'm sure you'd have spotted something like this, but I've tossed it out there 'just in case' :)
I intentionally used dd because I need Windows 10 to boot, which means don't change anything in the boot layout. It is hardcoded. It may be possible to do it another way, but I took no risks. The new disk is also 512/512. - -- Cheers Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlqHAJUACgkQja8UbcUWM1yungD+Nko/UgJiLggKO8IhfTkqj9I2 Y+8BUXgzKZIT7gzbMhwA/AtIVkzhGJv8UTcTE3V7ueN26ZnHdhVQ7svf4oHaWBlz =1wt+ -----END PGP SIGNATURE-----
On Thu, 2018-02-15 at 22:13 +0100, Carlos E. R. wrote:
The laptop is: "compaq presario CQ61-330SS", too old to have new firmware updates.
Hang on, that does not make sense. When it new, it would have got updates! It took some digging but the latest BIOS for it is version F.23 rev A, from Jan 14 2011. Is that what you are running? If not, I suggest that you upgrade to it. https://support.hp.com/ca-en/drivers/selfservice/compaq-presario-cq61-3 00-notebook-pc-series/3938633/model/4033892 I searched HP's website for: compaq presario CQ61-330SS latest bios Since what you describe is a startup problem, I think it is most likely firmware-related. -- Liam Proven - Technical Writer, SUSE Linux s.r.o. Corso II, Křižíkova 148/34, 186-00 Praha 8 - Karlín, Czechia Email: lproven@suse.com - Office telephone: +420 284 241 084 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Content-ID:
On Thu, 2018-02-15 at 22:13 +0100, Carlos E. R. wrote:
The laptop is: "compaq presario CQ61-330SS", too old to have new firmware updates.
Hang on, that does not make sense. When it new, it would have got updates!
I never had reason to apply any, the machine worked fine, and I failed to see the updates till you pointed to them. I only saw windows drivers.
It took some digging but the latest BIOS for it is version F.23 rev A, from Jan 14 2011. Is that what you are running?
If not, I suggest that you upgrade to it.
I have F.14, I just looked. You are right, I must upgrade.
https://support.hp.com/ca-en/drivers/selfservice/compaq-presario-cq61-3 00-notebook-pc-series/3938633/model/4033892
I searched HP's website for:
compaq presario CQ61-330SS latest bios
Since what you describe is a startup problem, I think it is most likely firmware-related.
Right. I will have a look there. Thankyou for finding it, I didn't. [...] What I see there is "software and drivers", not "bios upgrades". Where are they? Ok, I had to lie and say I have windows 7 (w10 is not in the list!), then I get a list of drivers, and one of the "drivers" is "bios". It is an exe file, I hope it runs in W10. I see three items under "bios": HP Notebook System BIOS Update (Intel Processors) WinFlash for HP Notebook System BIOS (for Notebooks with Intel Processors) F.11 Rev. A WinFlash for HP Notebook System BIOS (for Notebooks with Intel) F.13 A What is that WinFlash thing? Ah, I see. Type: BIOS Version: F.23 Rev. A Operating systems: Windows 7 (64-bit) Release date: Jan 14, 2011 File name: sp51527.exe (2.1 MB) Description: This package provides an update to the System BIOS. The update installs on supported notebook models using a supported Microsoft Windows Operating System. A reboot is required to complete the installation. Fix and enhancements: - - Fixes an issue where moving or clicking a USB mouse that is attached to the notebook during the Power-On Self-Test (POST) prevents the system from booting. - Fixes an intermittent issue that may result in an unexpected behavior, where the system stops responding (hangs) or a memory page fault is generated. This issue only occurs with 64-bit operating systems F.11 Rev. A Updates the WinFlash Utility to version 3.72.00. Updates the EC BIOS to version 21.22. Updates the Intel Memory Reference Code to version 2.9.Updates the WinFlash Utility to version 3.72.00. Updates the EC BIOS to version 21.22. Updates the Intel Memory Reference Code to version 2.9.Updates the WinFlash Utility to version 3.72.00. Updates the EC BIOS to version 21.22. Updates the Intel Memory Reference Code to version 2.9. F.13 A Updates the Computrace Option ROM to version 887. - -- Cheers Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlqG5TcACgkQja8UbcUWM1xxGAD+JgACBQJrqfHdmgqhZPsBVH2u DPHhxuoyJ+MBGkjzSjEBAI42K6RTH2EsbC3wXrlOUAQ545uCOfGitaKI1gBML7ER =J3Ei -----END PGP SIGNATURE-----
* Carlos E. R.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Content-ID:
El 2018-02-16 a las 13:08 +0100, Liam Proven escribió:
On Thu, 2018-02-15 at 22:13 +0100, Carlos E. R. wrote:
The laptop is: "compaq presario CQ61-330SS", too old to have new firmware updates.
Hang on, that does not make sense. When it new, it would have got updates!
I never had reason to apply any, the machine worked fine, and I failed to see the updates till you pointed to them. I only saw windows drivers.
It took some digging but the latest BIOS for it is version F.23 rev A, from Jan 14 2011. Is that what you are running?
If not, I suggest that you upgrade to it.
I have F.14, I just looked. You are right, I must upgrade.
https://support.hp.com/ca-en/drivers/selfservice/compaq-presario-cq61-3 00-notebook-pc-series/3938633/model/4033892
I searched HP's website for:
compaq presario CQ61-330SS latest bios
Since what you describe is a startup problem, I think it is most likely firmware-related.
Right. I will have a look there. Thankyou for finding it, I didn't.
[...]
What I see there is "software and drivers", not "bios upgrades". Where are they?
Ok, I had to lie and say I have windows 7 (w10 is not in the list!), then I get a list of drivers, and one of the "drivers" is "bios". It is an exe file, I hope it runs in W10.
I see three items under "bios":
HP Notebook System BIOS Update (Intel Processors) WinFlash for HP Notebook System BIOS (for Notebooks with Intel Processors) F.11 Rev. A WinFlash for HP Notebook System BIOS (for Notebooks with Intel) F.13 A
What is that WinFlash thing? Ah, I see.
Type: BIOS Version: F.23 Rev. A Operating systems: Windows 7 (64-bit) Release date: Jan 14, 2011 File name: sp51527.exe (2.1 MB)
Description:
This package provides an update to the System BIOS. The update installs on supported notebook models using a supported Microsoft Windows Operating System. A reboot is required to complete the installation.
Fix and enhancements: - - Fixes an issue where moving or clicking a USB mouse that is attached to the notebook during the Power-On Self-Test (POST) prevents the system from booting. - Fixes an intermittent issue that may result in an unexpected behavior, where the system stops responding (hangs) or a memory page fault is generated. This issue only occurs with 64-bit operating systems
F.11 Rev. A
Updates the WinFlash Utility to version 3.72.00.
Updates the EC BIOS to version 21.22.
Updates the Intel Memory Reference Code to version 2.9.Updates the WinFlash Utility to version 3.72.00.
Updates the EC BIOS to version 21.22.
Updates the Intel Memory Reference Code to version 2.9.Updates the WinFlash Utility to version 3.72.00.
Updates the EC BIOS to version 21.22.
Updates the Intel Memory Reference Code to version 2.9.
F.13 A
Updates the Computrace Option ROM to version 887.
- -- Cheers Carlos E. R.
(from openSUSE 42.3 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2
iF4EAREIAAYFAlqG5TcACgkQja8UbcUWM1xxGAD+JgACBQJrqfHdmgqhZPsBVH2u DPHhxuoyJ+MBGkjzSjEBAI42K6RTH2EsbC3wXrlOUAQ545uCOfGitaKI1gBML7ER =J3Ei -----END PGP SIGNATURE-----
there are apps specifically for updating a machine bios on linux using a windoz exe, one explanation: https://wiki.archlinux.org/index.php/Flashing_BIOS_from_Linux -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-02-16 15:25, Patrick Shanahan wrote:
* Carlos E. R. <> [02-16-18 09:07]:
there are apps specifically for updating a machine bios on linux using a windoz exe, one explanation: https://wiki.archlinux.org/index.php/Flashing_BIOS_from_Linux
As this laptop is double boot with Windows 10, I will try that route first. But thanks for the link, I'll have a look. Now I'm preparing to reboot to W10 without network, and try the firwmare update. Wish me luck ;-) -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" (Minas Tirith))
On 2018-02-16 15:29, Carlos E. R. wrote:
On 2018-02-16 15:25, Patrick Shanahan wrote:
* Carlos E. R. <> [02-16-18 09:07]:
there are apps specifically for updating a machine bios on linux using a windoz exe, one explanation: https://wiki.archlinux.org/index.php/Flashing_BIOS_from_Linux
As this laptop is double boot with Windows 10, I will try that route first. But thanks for the link, I'll have a look.
Now I'm preparing to reboot to W10 without network, and try the firwmare update.
Wish me luck ;-)
Done! Well, it still takes long before grub appears, but so far no error message. Of course it is too soon, will have to try longer. I did it from W10, but the above link has another link for HP computers using Linux. https://h30434.www3.hp.com/t5/Notebooks-Archive-Read-Only/How-to-update-BIOS... Ah, only some laptops are supported this way. It is a complicated procedure! -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" (Minas Tirith))
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2018-02-16 a las 15:59 +0100, Carlos E. R. escribió:
On 2018-02-16 15:29, Carlos E. R. wrote:
On 2018-02-16 15:25, Patrick Shanahan wrote:
* Carlos E. R. <> [02-16-18 09:07]:
there are apps specifically for updating a machine bios on linux using a windoz exe, one explanation: https://wiki.archlinux.org/index.php/Flashing_BIOS_from_Linux
As this laptop is double boot with Windows 10, I will try that route first. But thanks for the link, I'll have a look.
Now I'm preparing to reboot to W10 without network, and try the firwmare update.
Wish me luck ;-)
Done!
Well, it still takes long before grub appears, but so far no error message. Of course it is too soon, will have to try longer.
Today the error message appeared again, once :-( Still, I think I booted these days perhaps 5 times, with one failure today. Previously, each time I powered up the machine I had to try 2..4 times. So it is a big improvement. I noticed a forum of the disk brand, I'll try asking them if it is a known problem. - -- Cheers Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlqLQboACgkQja8UbcUWM1wi4AD/YqWR8TxL4enlD31YHO5ZrCDP 6hQSGU7W5PbPGuvwiT8BAIU4i1aMEas+hL193HlAKvrlUBqCnr+caTRrY9ZuOd+c =D7op -----END PGP SIGNATURE-----
On Fri, 2018-02-16 at 15:05 +0100, Carlos E. R. wrote:
Content-ID:
I never had reason to apply any, the machine worked fine, and I failed to see the updates till you pointed to them. I only saw windows drivers.
This is normal for manufacturers' support sites. Everything tends to be put together in 1 place. If there are separate sections, it is for docs + updates, or maybe docs, diags & updates. :-(
I have F.14, I just looked. You are right, I must upgrade.
I think there is a reasonable probability it might help. On my work desktop, updating from BIOS A01 as I got when this (several- year-old) machine passed to me, to the latest A19, took about 2 *minutes* off the bootup time.
Right. I will have a look there. Thankyou for finding it, I didn't.
It took a few goes!
Ok, I had to lie and say I have windows 7 (w10 is not in the list!)
It's too old, I think.
I see three items under "bios":
HP Notebook System BIOS Update (Intel Processors)
The actual firmware.
WinFlash for HP Notebook System BIOS (for Notebooks with Intel Processors) F.11 Rev. A WinFlash for HP Notebook System BIOS (for Notebooks with Intel ) F.13 A
The tool for installing it. I suggest the latest version. -- Liam Proven - Technical Writer, SUSE Linux s.r.o. Corso II, Křižíkova 148/34, 186-00 Praha 8 - Karlín, Czechia Email: lproven@suse.com - Office telephone: +420 284 241 084 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2018-02-16 a las 17:09 +0100, Liam Proven escribió:
On Fri, 2018-02-16 at 15:05 +0100, Carlos E. R. wrote:
I never had reason to apply any, the machine worked fine, and I failed to see the updates till you pointed to them. I only saw windows drivers.
This is normal for manufacturers' support sites. Everything tends to be put together in 1 place. If there are separate sections, it is for docs + updates, or maybe docs, diags & updates. :-(
After I applied it the "Windows way" I can understand why: from the user perspective it is done the same way as any other driver: just download it, run it, then press OK when asked, that's all. Thank you for pointing me to it! - -- Cheers Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlqHFJ8ACgkQja8UbcUWM1xTaAD8D4LhXLwieNNcY/qG0jZpjYxr RjodFiuHZV1W/rNUdU0A/A12J/W6NaC5fBR+ks4mq/1RVJ4YB3ZwNYIPqTxPNiNG =LtJW -----END PGP SIGNATURE-----
participants (7)
-
Carl Hartung -
Carlos E. R. -
Dave Howorth -
jdd＠dodin.org -
John Andersen -
Liam Proven -
Patrick Shanahan