Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #230005 > unrolled thread
| Started by | The Wanderer <wanderer@fastmail.fm> |
|---|---|
| First post | 2020-12-26 23:30 +0100 |
| Last post | 2020-12-30 04:10 +0100 |
| Articles | 12 on this page of 72 — 14 participants |
Back to article view | Back to linux.debian.user
No GRUB with brand-new GPU The Wanderer <wanderer@fastmail.fm> - 2020-12-26 23:30 +0100
Re: No GRUB with brand-new GPU Georgi Naplatanov <gosho@oles.biz> - 2020-12-26 23:40 +0100
Re: No GRUB with brand-new GPU The Wanderer <wanderer@fastmail.fm> - 2020-12-26 23:50 +0100
Re: No GRUB with brand-new GPU Linux-Fan <Ma_Sys.ma@web.de> - 2020-12-27 01:00 +0100
Re: No GRUB with brand-new GPU The Wanderer <wanderer@fastmail.fm> - 2020-12-27 01:20 +0100
Re: No GRUB with brand-new GPU Linux-Fan <Ma_Sys.ma@web.de> - 2020-12-27 01:50 +0100
Re: No GRUB with brand-new GPU The Wanderer <wanderer@fastmail.fm> - 2020-12-27 02:00 +0100
Re: No GRUB with brand-new GPU Felix Miata <mrmazda@earthlink.net> - 2020-12-27 00:30 +0100
Re: No GRUB with brand-new GPU The Wanderer <wanderer@fastmail.fm> - 2020-12-27 00:50 +0100
Re: No GRUB with brand-new GPU Felix Miata <mrmazda@earthlink.net> - 2020-12-27 01:40 +0100
Re: No GRUB with brand-new GPU Sven Joachim <svenjoac@gmx.de> - 2020-12-27 09:00 +0100
Re: No GRUB with brand-new GPU The Wanderer <wanderer@fastmail.fm> - 2020-12-27 13:20 +0100
Re: No GRUB with brand-new GPU The Wanderer <wanderer@fastmail.fm> - 2020-12-27 16:30 +0100
Re: No GRUB with brand-new GPU Anssi Saari <as@sci.fi> - 2020-12-27 22:40 +0100
Re: No GRUB with brand-new GPU The Wanderer <wanderer@fastmail.fm> - 2020-12-27 23:10 +0100
Re: No GRUB with brand-new GPU <tomas@tuxteam.de> - 2020-12-27 23:30 +0100
Re: No GRUB with brand-new GPU The Wanderer <wanderer@fastmail.fm> - 2020-12-27 23:40 +0100
Re: No GRUB with brand-new GPU Andrei POPESCU <andreimpopescu@gmail.com> - 2020-12-28 09:20 +0100
Re: No GRUB with brand-new GPU Anssi Saari <as@sci.fi> - 2020-12-28 13:50 +0100
Re: No GRUB with brand-new GPU The Wanderer <wanderer@fastmail.fm> - 2020-12-28 14:00 +0100
Re: No GRUB with brand-new GPU The Wanderer <wanderer@fastmail.fm> - 2020-12-28 22:20 +0100
Re: No GRUB with brand-new GPU Felix Miata <mrmazda@earthlink.net> - 2020-12-28 23:10 +0100
Re: No GRUB with brand-new GPU The Wanderer <wanderer@fastmail.fm> - 2020-12-28 23:30 +0100
Re: No GRUB with brand-new GPU Felix Miata <mrmazda@earthlink.net> - 2020-12-29 00:30 +0100
Re: No GRUB with brand-new GPU The Wanderer <wanderer@fastmail.fm> - 2020-12-29 00:40 +0100
Re: No GRUB with brand-new GPU Felix Miata <mrmazda@earthlink.net> - 2020-12-29 01:30 +0100
Re: No GRUB with brand-new GPU Linux-Fan <Ma_Sys.ma@web.de> - 2020-12-29 02:40 +0100
Re: No GRUB with brand-new GPU The Wanderer <wanderer@fastmail.fm> - 2020-12-29 13:30 +0100
Re: No GRUB with brand-new GPU Anssi Saari <as@sci.fi> - 2020-12-29 11:20 +0100
Re: No GRUB with brand-new GPU "Thomas Schmitt" <scdbackup@gmx.net> - 2020-12-29 12:10 +0100
Re: No GRUB with brand-new GPU The Wanderer <wanderer@fastmail.fm> - 2020-12-29 13:00 +0100
Re: No GRUB with brand-new GPU Andrei POPESCU <andreimpopescu@gmail.com> - 2020-12-29 19:10 +0100
Re: No GRUB with brand-new GPU The Wanderer <wanderer@fastmail.fm> - 2020-12-29 19:20 +0100
Re: No GRUB with brand-new GPU Romualdas Taluntis <romualdas@taluntis.lt> - 2020-12-29 20:30 +0100
Re: No GRUB with brand-new GPU The Wanderer <wanderer@fastmail.fm> - 2020-12-29 20:30 +0100
Re: No GRUB with brand-new GPU Romualdas Taluntis <romualdas@taluntis.lt> - 2020-12-29 21:00 +0100
Re: No GRUB with brand-new GPU The Wanderer <wanderer@fastmail.fm> - 2020-12-29 21:20 +0100
Re: No GRUB with brand-new GPU The Wanderer <wanderer@fastmail.fm> - 2020-12-29 21:40 +0100
Re: No GRUB with brand-new GPU Georgi Naplatanov <gosho@oles.biz> - 2020-12-29 21:40 +0100
Re: No GRUB with brand-new GPU Michael Stone <mstone@debian.org> - 2020-12-29 21:20 +0100
Re: No GRUB with brand-new GPU Felix Miata <mrmazda@earthlink.net> - 2020-12-29 22:50 +0100
Re: No GRUB with brand-new GPU The Wanderer <wanderer@fastmail.fm> - 2020-12-29 23:00 +0100
Re: No GRUB with brand-new GPU Michael Stone <mstone@debian.org> - 2020-12-29 23:40 +0100
Re: No GRUB with brand-new GPU Felix Miata <mrmazda@earthlink.net> - 2020-12-30 03:50 +0100
Re: No GRUB with brand-new GPU Michael Stone <mstone@debian.org> - 2020-12-30 04:40 +0100
Re: No GRUB with brand-new GPU Felix Miata <mrmazda@earthlink.net> - 2020-12-30 05:00 +0100
Re: No GRUB with brand-new GPU Doug McGarrett <dmcgarrett@optonline.net> - 2020-12-30 06:00 +0100
Re: No GRUB with brand-new GPU <tomas@tuxteam.de> - 2020-12-30 10:20 +0100
Re: No GRUB with brand-new GPU Michael Stone <mstone@debian.org> - 2020-12-30 15:00 +0100
Re: No GRUB with brand-new GPU Felix Miata <mrmazda@earthlink.net> - 2020-12-30 19:40 +0100
Re: No GRUB with brand-new GPU Andrei POPESCU <andreimpopescu@gmail.com> - 2020-12-30 20:10 +0100
Re: No GRUB with brand-new GPU Michael Stone <mstone@debian.org> - 2020-12-30 20:20 +0100
Re: No GRUB with brand-new GPU Felix Miata <mrmazda@earthlink.net> - 2020-12-30 22:10 +0100
Re: No GRUB with brand-new GPU Michael Stone <mstone@debian.org> - 2020-12-30 22:40 +0100
Re: No GRUB with brand-new GPU The Wanderer <wanderer@fastmail.fm> - 2020-12-29 13:20 +0100
Re: No GRUB with brand-new GPU Anssi Saari <as@sci.fi> - 2020-12-29 22:50 +0100
Re: No GRUB with brand-new GPU The Wanderer <wanderer@fastmail.fm> - 2020-12-29 23:00 +0100
Re: No GRUB with brand-new GPU Tony Rowe <torowe@gmail.com> - 2020-12-27 02:10 +0100
Re: No GRUB with brand-new GPU The Wanderer <wanderer@fastmail.fm> - 2020-12-27 02:20 +0100
Re: No GRUB with brand-new GPU David Wright <deblis@lionunicorn.co.uk> - 2020-12-27 05:10 +0100
Re: No GRUB with brand-new GPU The Wanderer <wanderer@fastmail.fm> - 2020-12-27 13:10 +0100
Re: No GRUB with brand-new GPU David Wright <deblis@lionunicorn.co.uk> - 2020-12-28 02:50 +0100
Re: No GRUB with brand-new GPU Andrei POPESCU <andreimpopescu@gmail.com> - 2020-12-27 08:40 +0100
Re: No GRUB with brand-new GPU The Wanderer <wanderer@fastmail.fm> - 2020-12-27 13:10 +0100
Re: No GRUB with brand-new GPU Andrei POPESCU <andreimpopescu@gmail.com> - 2020-12-28 09:30 +0100
Re: No GRUB with brand-new GPU Romualdas Taluntis <romualdas@taluntis.lt> - 2020-12-29 14:00 +0100
Re: No GRUB with brand-new GPU The Wanderer <wanderer@fastmail.fm> - 2020-12-29 14:00 +0100
Re: No GRUB with brand-new GPU Felix Miata <mrmazda@earthlink.net> - 2020-12-29 18:10 +0100
Re: No GRUB with brand-new GPU The Wanderer <wanderer@fastmail.fm> - 2020-12-29 18:20 +0100
Re: No GRUB with brand-new GPU Felix Miata <mrmazda@earthlink.net> - 2020-12-29 18:40 +0100
Re: No GRUB with brand-new GPU Michael Stone <mstone@debian.org> - 2020-12-29 19:20 +0100
Re: No GRUB with brand-new GPU Felix Miata <mrmazda@earthlink.net> - 2020-12-30 04:10 +0100
Page 4 of 4 — ← Prev page 1 2 3 [4]
| From | The Wanderer <wanderer@fastmail.fm> |
|---|---|
| Date | 2020-12-27 13:10 +0100 |
| Message-ID | <BqD23-bE-13@gated-at.bofh.it> |
| In reply to | #230019 |
[Multipart message — attachments visible in raw view] — view raw
On 2020-12-26 at 23:01, David Wright wrote: > On Sat 26 Dec 2020 at 17:19:32 (-0500), The Wanderer wrote: > >> I have for some years been running Debian with an older model of >> AMD GPU (Radeon HD 6870) for graphics. >> >> I recently purchased a relatively recent model of GPU (Radeon RX >> 5700 XT), and today swapped it in and attempted to boot with it. > >> Any suggestions for what to try? > > Did you take the old card out and then reboot and save the CMOS > settings? Then put the new card in and ditto? I'm not sure what exact sequence of actions you're suggesting. AFAIK, this motherboard doesn't have integrated graphics, and if it does I don't have a cable suitable to connect them to my monitor; I therefore can't meaningfully boot (much less reboot), let alone get into the CMOS to "save settings", after removing the old card and before putting in the new. I have gone into the CMOS, and (by chance) IIRC even made and saved a change, after putting in the new card. It didn't help. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2020-12-28 02:50 +0100 |
| Message-ID | <BqPPA-8ar-9@gated-at.bofh.it> |
| In reply to | #230025 |
On Sun 27 Dec 2020 at 07:02:53 (-0500), The Wanderer wrote: > On 2020-12-26 at 23:01, David Wright wrote: > > On Sat 26 Dec 2020 at 17:19:32 (-0500), The Wanderer wrote: > > > >> I have for some years been running Debian with an older model of > >> AMD GPU (Radeon HD 6870) for graphics. > >> > >> I recently purchased a relatively recent model of GPU (Radeon RX > >> 5700 XT), and today swapped it in and attempted to boot with it. > > > >> Any suggestions for what to try? > > > > Did you take the old card out and then reboot and save the CMOS > > settings? Then put the new card in and ditto? > > I'm not sure what exact sequence of actions you're suggesting. > > AFAIK, this motherboard doesn't have integrated graphics, and if it does > I don't have a cable suitable to connect them to my monitor; Fair enough. As I said, it's a while back, and some mobos had integral graphics and some didn't. (I didn't control their purchase, and some were second-use.) > I therefore > can't meaningfully boot (much less reboot), How meaningful it is depends on what sort of notice the mobo takes of the lack of the old card. But you should certainly be able to boot and the POST should run. > let alone get into the CMOS > to "save settings", after removing the old card and before putting in > the new. True, when there's no onboard graphics, though actually I could type unseen the necessary keystrokes to Exit Saving Changes in the Phoenix BIOS. > I have gone into the CMOS, and (by chance) IIRC even made and saved a > change, after putting in the new card. It didn't help. I'm guessing that my problem involved the configuration of the card by the bus, whereas yours is later on, involving drivers etc. Cheers, David.
[toc] | [prev] | [next] | [standalone]
| From | Andrei POPESCU <andreimpopescu@gmail.com> |
|---|---|
| Date | 2020-12-27 08:40 +0100 |
| Message-ID | <BqyOK-5TB-9@gated-at.bofh.it> |
| In reply to | #230005 |
[Multipart message — attachments visible in raw view] — view raw
On Sb, 26 dec 20, 17:19:32, The Wanderer wrote: > > With the new GPU in place, I get video output during POST and in the > BIOS (yes, this machine is old enough that it doesn't have a UEFI) > without problems. That demonstrates that the GPU isn't dead on arrival, > and that signal is getting through to the monitor on a basic level. At this apoint you might want to query your monitor for the resolution used, might be helpful in case you want to configure grub with a known working resolution (as per other suggestions). > However, as soon as the machine tries to hand over control to the > bootloader, I get a hard freeze; the screen goes black (albeit I think > still with backlight), the keyboard light toggle keys stop responding, > and the GRUB menu never appears. Waiting a long time doesn't change > anything; even after roughly half an hour of waiting, pressing the Power > button once (no press-and-hold) shuts the system off immediately, which > indicates that the system hasn't progressed much (if at all) past early > boot. Maybe changing some BIOS setting could help. The suggestion to try a live image is also good. As far as I know the Debian Installer is using very basic VGA graphics, for maximum compatibility, so result might be different than a full live system. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser
[toc] | [prev] | [next] | [standalone]
| From | The Wanderer <wanderer@fastmail.fm> |
|---|---|
| Date | 2020-12-27 13:10 +0100 |
| Message-ID | <BqD23-bE-9@gated-at.bofh.it> |
| In reply to | #230020 |
[Multipart message — attachments visible in raw view] — view raw
On 2020-12-27 at 02:31, Andrei POPESCU wrote: > On Sb, 26 dec 20, 17:19:32, The Wanderer wrote: > >> With the new GPU in place, I get video output during POST and in >> the BIOS (yes, this machine is old enough that it doesn't have a >> UEFI) without problems. That demonstrates that the GPU isn't dead >> on arrival, and that signal is getting through to the monitor on a >> basic level. > > At this apoint you might want to query your monitor for the > resolution used, might be helpful in case you want to configure grub > with a known working resolution (as per other suggestions). I know my monitor resolution; it's 2560x1600, and supports many exact-subset lower resolutions. What type of query were you thinking of? The output of xrandr is one possibility, and that of 'get-edid | parse-edid' (with /dev/ mounted exec) is another; the latter is closer to a true "query the monitor", but seems to provide less information. >> However, as soon as the machine tries to hand over control to the >> bootloader, I get a hard freeze; the screen goes black (albeit I >> think still with backlight), the keyboard light toggle keys stop >> responding, and the GRUB menu never appears. Waiting a long time >> doesn't change anything; even after roughly half an hour of >> waiting, pressing the Power button once (no press-and-hold) shuts >> the system off immediately, which indicates that the system hasn't >> progressed much (if at all) past early boot. > > Maybe changing some BIOS setting could help. I already checked, and didn't see any settings that seemed relevant. IIRC I did change an unrelated setting which I noticed along the way. This behavior didn't change afterward. > The suggestion to try a live image is also good. > > As far as I know the Debian Installer is using very basic VGA > graphics, for maximum compatibility, so result might be different > than a full live system. If it can get *anything* after the BIOS handover, it's at least progress from where I currently sit. Validating with those basic minimal graphics is actually a good thing, IMO, although you're right that it only goes so far. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw
[toc] | [prev] | [next] | [standalone]
| From | Andrei POPESCU <andreimpopescu@gmail.com> |
|---|---|
| Date | 2020-12-28 09:30 +0100 |
| Message-ID | <BqW4F-3ZS-1@gated-at.bofh.it> |
| In reply to | #230024 |
[Multipart message — attachments visible in raw view] — view raw
On Du, 27 dec 20, 07:08:28, The Wanderer wrote: > On 2020-12-27 at 02:31, Andrei POPESCU wrote: > > > On Sb, 26 dec 20, 17:19:32, The Wanderer wrote: > > > >> With the new GPU in place, I get video output during POST and in > >> the BIOS (yes, this machine is old enough that it doesn't have a > >> UEFI) without problems. That demonstrates that the GPU isn't dead > >> on arrival, and that signal is getting through to the monitor on a > >> basic level. > > > > At this apoint you might want to query your monitor for the > > resolution used, might be helpful in case you want to configure grub > > with a known working resolution (as per other suggestions). > > I know my monitor resolution; it's 2560x1600, and supports many > exact-subset lower resolutions. We know for sure that the card works properly in the specific video mode it is in *during POST* (not latter). This is very unlikely to be the native resolution of your monitor (the BIOS doesn't support that), it's more likely something like 640x480. Your monitor should be able to tell you that (poke its menu / settings). > > Maybe changing some BIOS setting could help. > > I already checked, and didn't see any settings that seemed relevant. > IIRC I did change an unrelated setting which I noticed along the way. > This behavior didn't change afterward. BIOS options are sometimes quite cryptic. You might want to (re-)read the user manual for your motherboard. Basically anything that is PCIe related could be relevant, in addition to the obvious settings for anything graphics related. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser
[toc] | [prev] | [next] | [standalone]
| From | Romualdas Taluntis <romualdas@taluntis.lt> |
|---|---|
| Date | 2020-12-29 14:00 +0100 |
| Message-ID | <BrmLv-575-1@gated-at.bofh.it> |
| In reply to | #230005 |
If your motherboard is legacy BIOS only (non-UEFI) then that's almost certainly the problem and messing with GRUB won't help. There are a couple of easy ways to go about it: -Return your card, -Upgrade your whole system; and a couple of not very easy and not guaranteed to work: -try booting with your 5700 in a secondary PCI-E slot and your old GPU in the main slot, check if Debian detects both video cards, force certain applications to use new video card and use it like this if it works. -check if there is a different BIOS available for your new GPU which enables legacy support. On 2020-12-27 00:19, The Wanderer wrote: > I have for some years been running Debian with an older model of AMD GPU > (Radeon HD 6870) for graphics. > > I recently purchased a relatively recent model of GPU (Radeon RX 5700 > XT), and today swapped it in and attempted to boot with it. > > I was expecting to get no graphics support (e.g., X, et cetera) until > after adjusting some combination of installed driver- and > firmware-related packages, module-blacklist settings, boot-time options, > initrd state, GRUB configuration, and possibly other (again, e.g., X) > config files. I'm generally fine with wrangling that, and based on my > pre-swap research, was expecting to be able to get up and running with > the new GPU today. > > What I got, instead, was not even that far. > > With the new GPU in place, I get video output during POST and in the > BIOS (yes, this machine is old enough that it doesn't have a UEFI) > without problems. That demonstrates that the GPU isn't dead on arrival, > and that signal is getting through to the monitor on a basic level. > > However, as soon as the machine tries to hand over control to the > bootloader, I get a hard freeze; the screen goes black (albeit I think > still with backlight), the keyboard light toggle keys stop responding, > and the GRUB menu never appears. Waiting a long time doesn't change > anything; even after roughly half an hour of waiting, pressing the Power > button once (no press-and-hold) shuts the system off immediately, which > indicates that the system hasn't progressed much (if at all) past early > boot. > > Thus far, Google has not been helpful. I find plenty about black screens > after GRUB, but very little about before GRUB and after POST, and what > little I find is from other distros - some Ubuntu (earlier versions, > mostly 2010-era), some Arch, some RHEL - which don't necessarily handle > either graphics drivers or GRUB in a way that will let their directions > reliably translate to Debian. > > > Any suggestions for what to try? > > I'm back up now with the old GPU, since researching this on my > smartphone was going nowhere. I've dug into /etc/grub* and /boot/ > looking for anything which seemed related, with no promising hits yet. > > Barring other discoveries, my current next step is to dig up a suitably > recent Debian-based live-boot environment, boot to that, and see what it > does. If it gives me usable graphics, I want to see what it's doing at > bootloader time, and what parts I might be able to transpose into my > primary install. > > However, given that live-boot setups don't always handle the early parts > of boot the same way as hard-drive installs do, I'm not positive this > will be fruitful. Also, given how relatively new this card is, I'm not > sure I'll be able to find a suitable environment which does work with it > to the level I need. > -- Pagarbiai Romualdas Taluntis
[toc] | [prev] | [next] | [standalone]
| From | The Wanderer <wanderer@fastmail.fm> |
|---|---|
| Date | 2020-12-29 14:00 +0100 |
| Message-ID | <BrmLv-575-7@gated-at.bofh.it> |
| In reply to | #230072 |
[Multipart message — attachments visible in raw view] — view raw
On 2020-12-29 at 07:27, Romualdas Taluntis wrote: > If your motherboard is legacy BIOS only (non-UEFI) then that's almost > certainly the problem and messing with GRUB won't help. There are a > couple of easy ways to go about it: > > -Return your card, Not on my list; I'd sooner build a new system to go with the card. > -Upgrade your whole system; This is similar to "build a new system", except in the number of parts retained. I'd prefer it, except that I don't think I can fix this problem without replacing the motherboard, and at that point I have to replace so many parts that at *most* it might be worth keeping the hard drives and the case. > and a couple of not very easy and not guaranteed to work: > > -try booting with your 5700 in a secondary PCI-E slot and your old > GPU in the main slot, check if Debian detects both video cards, force > certain applications to use new video card and use it like this if > it works. I... can see how that might work, but it's not an approach I'd find satisfying, or care to take. Thanks for suggesting it, though. > -check if there is a different BIOS available for your new GPU which > enables legacy support. That's a decent suggestion! I'll look into it. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw
[toc] | [prev] | [next] | [standalone]
| From | Felix Miata <mrmazda@earthlink.net> |
|---|---|
| Date | 2020-12-29 18:10 +0100 |
| Message-ID | <BrqFs-7JF-11@gated-at.bofh.it> |
| In reply to | #230073 |
The Wanderer composed on 2020-12-29 07:57 (UTC-0500): > Romualdas Taluntis wrote: >> -try booting with your 5700 in a secondary PCI-E slot and your old >> GPU in the main slot, check if Debian detects both video cards, force >> certain applications to use new video card and use it like this if >> it works. > I... can see how that might work, but it's not an approach I'd find > satisfying, or care to take. Thanks for suggesting it, though. If it is a PS issue, then that would confirm it, but that assumes you have enough 6 or 8 wire power connectors for both cards. That brings to mind another idea about PS capacity. Given you need 7 SATA ports, you could try booting with the power connectors for all but the one you are booting from disconnected, giving the PS some reserve capacity to use for the 5700. If it it proceeds to display Grub instead of locking up, you know where the fault lies. -- Evolution as taught in public schools, like religion, is based on faith, not on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
[toc] | [prev] | [next] | [standalone]
| From | The Wanderer <wanderer@fastmail.fm> |
|---|---|
| Date | 2020-12-29 18:20 +0100 |
| Message-ID | <BrqP7-7ML-3@gated-at.bofh.it> |
| In reply to | #230076 |
[Multipart message — attachments visible in raw view] — view raw
On 2020-12-29 at 12:08, Felix Miata wrote: > The Wanderer composed on 2020-12-29 07:57 (UTC-0500): > >> Romualdas Taluntis wrote: > >>> -try booting with your 5700 in a secondary PCI-E slot and your >>> old GPU in the main slot, check if Debian detects both video >>> cards, force certain applications to use new video card and use >>> it like this if it works. > >> I... can see how that might work, but it's not an approach I'd >> find satisfying, or care to take. Thanks for suggesting it, >> though. > > If it is a PS issue, then that would confirm it, but that assumes you > have enough 6 or 8 wire power connectors for both cards. I probably do, although I'd have to dig them up; that's one advantage of PSU modularity. > That brings to mind another idea about PS capacity. Given you need 7 > SATA ports, you could try booting with the power connectors for all > but the one you are booting from disconnected, giving the PS some > reserve capacity to use for the 5700. If it it proceeds to display > Grub instead of locking up, you know where the fault lies. Trouble is, six of my seven drives (the seventh being an optical drive) are joined into two RAID arrays: a two-drive RAID-1 array of fast storage for programs and the OS and so forth, and a four-drive RAID-6 array of slower bulk storage for everything else - and owing to a misunderstanding when I designed the layout, /var is on the latter, even though it and its exact contents are apparently necessary for system operation. I could at the furthest extreme cut things down to one drive from the RAID-1 array and two from the RAID-6, but I'd be hesitant to do that, since I've had data-loss and array-loss scares before; the latter took 3-to-9 months and over $5000 to recover from. That said, I'd be less concerned about booting to removable media with *all* of the drives disconnected, and that might achieve the same end. That goes on my list of things to try next time I do a swap-out for testing. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw
[toc] | [prev] | [next] | [standalone]
| From | Felix Miata <mrmazda@earthlink.net> |
|---|---|
| Date | 2020-12-29 18:40 +0100 |
| Message-ID | <Brr8u-7SI-5@gated-at.bofh.it> |
| In reply to | #230077 |
The Wanderer composed on 2020-12-29 12:18 (UTC-0500): > ...I'd be less concerned about booting to removable media with > *all* of the drives disconnected, and that might achieve the same end. I agree. I can't imagine how it could not. Still, after 8 years, I'd open the PS up for cleaning if nothing else, unless it's been operating in a clean room all those years. -- Evolution as taught in public schools, like religion, is based on faith, not on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
[toc] | [prev] | [next] | [standalone]
| From | Michael Stone <mstone@debian.org> |
|---|---|
| Date | 2020-12-29 19:20 +0100 |
| Message-ID | <BrrLc-8rr-5@gated-at.bofh.it> |
| In reply to | #230078 |
On Tue, Dec 29, 2020 at 12:34:49PM -0500, Felix Miata wrote: >I agree. I can't imagine how it could not. Still, after 8 years, I'd open the PS >up for cleaning if nothing else, unless it's been operating in a clean room all >those years. FWIW, I wouldn't do that and consider it to be a bit nuts. :)
[toc] | [prev] | [next] | [standalone]
| From | Felix Miata <mrmazda@earthlink.net> |
|---|---|
| Date | 2020-12-30 04:10 +0100 |
| Message-ID | <BrA25-6c4-5@gated-at.bofh.it> |
| In reply to | #230080 |
Michael Stone composed on 2020-12-29 13:17 (UTC-0500): > On Tue, Dec 29, 2020 at 12:34:49PM -0500, Felix Miata wrote: >>I agree. I can't imagine how it could not. Still, after 8 years, I'd open the PS >>up for cleaning if nothing else, unless it's been operating in a clean room all >>those years. > FWIW, I wouldn't do that and consider it to be a bit nuts. :) It's very common here. I don't have any PS testers that won't lie. I must open the older ones up to confirm no lurking motherboard killers innumm. I replace caps when feasible rather than junking dead or flaky ones. Less than a week ago there was a tight cluster of four with 3 bad (and one elsewhere replaceable), in non-available spec matches (10mmX35mm & 40mm 2200uF & 3300uF in 10V & 16V, never available by any but junk manufacturers; 12mm can't fit the tight space), so whole PS had to be junked. -- Evolution as taught in public schools, like religion, is based on faith, not on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
[toc] | [prev] | [standalone]
Page 4 of 4 — ← Prev page 1 2 3 [4]
Back to top | Article view | linux.debian.user
csiph-web