Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #168314 > unrolled thread
| Started by | Mostafa Shahverdy <mostafa@mostafa.info> |
|---|---|
| First post | 2016-05-30 15:30 +0200 |
| Last post | 2016-06-04 21:20 +0200 |
| Articles | 19 on this page of 39 — 8 participants |
Back to article view | Back to linux.debian.user
How to properly install Radeon drivers for Sid Mostafa Shahverdy <mostafa@mostafa.info> - 2016-05-30 15:30 +0200
Re: How to properly install Radeon drivers for Sid Jörg-Volker Peetz <jvpeetz@web.de> - 2016-05-30 15:50 +0200
Re: How to properly install Radeon drivers for Sid Jörg-Volker Peetz <jvpeetz@web.de> - 2016-05-30 17:10 +0200
Re: How to properly install Radeon drivers for Sid Jörg-Volker Peetz <jvpeetz@web.de> - 2016-05-31 13:20 +0200
Re: How to properly install Radeon drivers for Sid Mostafa Shahverdy <mostafa@mostafa.info> - 2016-05-31 13:30 +0200
Re: How to properly install Radeon drivers for Sid Jörg-Volker Peetz <jvpeetz@web.de> - 2016-05-31 14:30 +0200
Re: How to properly install Radeon drivers for Sid Mostafa Shahverdy <mostafa@mostafa.info> - 2016-05-31 18:30 +0200
Re: How to properly install Radeon drivers for Sid The Wanderer <wanderer@fastmail.fm> - 2016-05-31 15:10 +0200
Re: How to properly install Radeon drivers for Sid Mostafa Shahverdy <mostafa@mostafa.info> - 2016-05-31 18:40 +0200
Re: How to properly install Radeon drivers for Sid Jörg-Volker Peetz <jvpeetz@web.de> - 2016-05-31 15:10 +0200
Re: How to properly install Radeon drivers for Sid Mostafa Shahverdy <mostafa@mostafa.info> - 2016-05-31 18:30 +0200
Re: How to properly install Radeon drivers for Sid Mostafa Shahverdy <mostafa@mostafa.info> - 2016-06-02 14:40 +0200
Re: How to properly install Radeon drivers for Sid Jörg-Volker Peetz <jvpeetz@web.de> - 2016-06-02 15:50 +0200
Re: How to properly install Radeon drivers for Sid Mostafa Shahverdy <mostafa@mostafa.info> - 2016-06-02 16:40 +0200
Re: How to properly install Radeon drivers for Sid Jörg-Volker Peetz <jvpeetz@web.de> - 2016-06-02 19:00 +0200
Re: How to properly install Radeon drivers for Sid Sven Arvidsson <sa@whiz.se> - 2016-06-02 20:50 +0200
Re: How to properly install Radeon drivers for Sid Mostafa Shahverdy <mostafa@mostafa.info> - 2016-06-04 08:20 +0200
Re: How to properly install Radeon drivers for Sid Jörg-Volker Peetz <jvpeetz@web.de> - 2016-06-04 13:10 +0200
Re: How to properly install Radeon drivers for Sid Mostafa Shahverdy <mostafa@mostafa.info> - 2016-06-04 17:10 +0200
Re: How to properly install Radeon drivers for Sid deloptes <deloptes@gmail.com> - 2016-05-30 21:50 +0200
Re: How to properly install Radeon drivers for Sid Mostafa Shahverdy <mostafa@mostafa.info> - 2016-05-31 12:50 +0200
Re: How to properly install Radeon drivers for Sid Lisi Reisz <lisi.reisz@gmail.com> - 2016-05-31 13:00 +0200
Re: How to properly install Radeon drivers for Sid Mostafa Shahverdy <mostafa@mostafa.info> - 2016-05-31 18:50 +0200
Re: How to properly install Radeon drivers for Sid Lisi Reisz <lisi.reisz@gmail.com> - 2016-05-31 19:10 +0200
Re: buntu kybosh (was: How to properly install...) Felix Miata <mrmazda@earthlink.net> - 2016-06-01 01:20 +0200
Re: buntu kybosh (was: How to properly install...) Lisi Reisz <lisi.reisz@gmail.com> - 2016-06-01 01:50 +0200
Re: buntu kybosh Felix Miata <mrmazda@earthlink.net> - 2016-06-01 02:40 +0200
Re: buntu kybosh Lisi Reisz <lisi.reisz@gmail.com> - 2016-06-01 09:50 +0200
Re: buntu kybosh Lisi Reisz <lisi.reisz@gmail.com> - 2016-06-01 11:00 +0200
Re: How to properly install Radeon drivers for Sid deloptes <deloptes@gmail.com> - 2016-06-01 21:10 +0200
Re: How to properly install Radeon drivers for Sid Paul Johnson <baloo@ursamundi.org> - 2016-05-31 10:30 +0200
Re: How to properly install Radeon drivers for Sid Mostafa Shahverdy <mostafa@mostafa.info> - 2016-05-31 13:10 +0200
Re: How to properly install Radeon drivers for Sid Paul Johnson <baloo@ursamundi.org> - 2016-05-31 18:00 +0200
Re: How to properly install Radeon drivers for Sid Felix Miata <mrmazda@earthlink.net> - 2016-05-31 11:40 +0200
Re: How to properly install Radeon drivers for Sid Felix Miata <mrmazda@earthlink.net> - 2016-05-31 15:40 +0200
Re: How to properly install Radeon drivers for Sid Felix Miata <mrmazda@earthlink.net> - 2016-06-03 06:00 +0200
Re: How to properly install Radeon drivers for Sid Mostafa Shahverdy <mostafa@mostafa.info> - 2016-06-04 07:50 +0200
Re: How to properly install Radeon drivers for Sid Felix Miata <mrmazda@earthlink.net> - 2016-06-04 08:50 +0200
Re: How to properly install Radeon drivers for Sid Mostafa Shahverdy <mostafa@mostafa.info> - 2016-06-04 21:20 +0200
Page 2 of 2 — ← Prev page 1 [2]
| From | Mostafa Shahverdy <mostafa@mostafa.info> |
|---|---|
| Date | 2016-05-31 12:50 +0200 |
| Message-ID | <rEPpf-1AT-13@gated-at.bofh.it> |
| In reply to | #168322 |
[Multipart message — attachments visible in raw view] — view raw
> > Why not try with older kernel that works with the driver? > I always keep my OS up to date, that's why I use Sid, I always want the latest updates :) -- Regards, Mostafa Shahverdy <http://www.mostafa.info/pgp>
[toc] | [prev] | [next] | [standalone]
| From | Lisi Reisz <lisi.reisz@gmail.com> |
|---|---|
| Date | 2016-05-31 13:00 +0200 |
| Message-ID | <rEPyW-1EG-33@gated-at.bofh.it> |
| In reply to | #168333 |
On Tuesday 31 May 2016 11:42:51 Mostafa Shahverdy wrote: > > Why not try with older kernel that works with the driver? > > I always keep my OS up to date, that's why I use Sid, I always want the > latest updates :) Why?? Lisi
[toc] | [prev] | [next] | [standalone]
| From | Mostafa Shahverdy <mostafa@mostafa.info> |
|---|---|
| Date | 2016-05-31 18:50 +0200 |
| Message-ID | <rEV1D-57j-1@gated-at.bofh.it> |
| In reply to | #168334 |
[Multipart message — attachments visible in raw view] — view raw
On Tue, May 31, 2016 at 11:50:14AM +0100, Lisi Reisz wrote: > On Tuesday 31 May 2016 11:42:51 Mostafa Shahverdy wrote: > > > Why not try with older kernel that works with the driver? > > > > I always keep my OS up to date, that's why I use Sid, I always want the > > latest updates :) > > Why?? Updates are not that bad ;) I keep me desktop up to date. I want stability for my servers though. -- Regards, Mostafa Shahverdy <http://www.mostafa.info/pgp>
[toc] | [prev] | [next] | [standalone]
| From | Lisi Reisz <lisi.reisz@gmail.com> |
|---|---|
| Date | 2016-05-31 19:10 +0200 |
| Message-ID | <rEVl1-5uA-59@gated-at.bofh.it> |
| In reply to | #168346 |
On Tuesday 31 May 2016 17:44:48 Mostafa Shahverdy wrote: > On Tue, May 31, 2016 at 11:50:14AM +0100, Lisi Reisz wrote: > > On Tuesday 31 May 2016 11:42:51 Mostafa Shahverdy wrote: > > > > Why not try with older kernel that works with the driver? > > > > > > I always keep my OS up to date, that's why I use Sid, I always want the > > > latest updates :) > > > > Why?? > > Updates are not that bad ;) I keep me desktop up to date. I want > stability for my servers though. I am always baffled by form over functionality - even on my desktop! I like things working if they can. Having said which, if I gave an experimental machine on the go .... And I have just kyboshed the computer I have attached to the television by trying Ubuntu MATE 16.04 as a dual boot. I am mentally working out the best way at least to make it take a very back seat, before I wipe the lot in frustration. And Debian Jessie was just working nicely. A liking for Sid I can in general understand - though I would use an old kernel and have my video working ;-) - but I can't get my head round Ubuntu. I keep trying. :-( Lisi
[toc] | [prev] | [next] | [standalone]
| From | Felix Miata <mrmazda@earthlink.net> |
|---|---|
| Date | 2016-06-01 01:20 +0200 |
| Subject | Re: buntu kybosh (was: How to properly install...) |
| Message-ID | <rF173-wS-11@gated-at.bofh.it> |
| In reply to | #168348 |
Lisi Reisz composed on 2016-05-31 18:06 (UTC+0100): > ...I have just kyboshed the computer I have attached > to the television by trying Ubuntu MATE 16.04 as a dual boot. I am mentally > working out the best way at least to make it take a very back seat, before I > wipe the lot in frustration. And Debian Jessie was just working nicely. Just what constituted the kyboshing? Neither boots? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
[toc] | [prev] | [next] | [standalone]
| From | Lisi Reisz <lisi.reisz@gmail.com> |
|---|---|
| Date | 2016-06-01 01:50 +0200 |
| Subject | Re: buntu kybosh (was: How to properly install...) |
| Message-ID | <rF1A6-H3-11@gated-at.bofh.it> |
| In reply to | #168376 |
On Wednesday 01 June 2016 00:15:20 Felix Miata wrote: > Lisi Reisz composed on 2016-05-31 18:06 (UTC+0100): > > ...I have just kyboshed the computer I have attached > > to the television by trying Ubuntu MATE 16.04 as a dual boot. I am > > mentally working out the best way at least to make it take a very back > > seat, before I wipe the lot in frustration. And Debian Jessie was just > > working nicely. > > Just what constituted the kyboshing? Neither boots? The word was a little stronger than is totally justified. This is attached to a television. I want to just turn it on. Ubuntu boots but is unusable, so I have to hover over it, grab GRUB and get into Debian, because Ubuntu has kyboshed (=destroyed) Debian's GRUB (of course!!). Since seeing the screen is difficult, and I watch television only when I am tired, this is tedious in the extreme, and it was working beautifully, all but Channel 4 replays, before I gave Ubuntu a chance. I thought that dual booting couldn't do any harm. I had forgotten Ubuntu's ability to do harm when in my hands. What was that Stephen said about guns and feet. ;-) Lisi
[toc] | [prev] | [next] | [standalone]
| From | Felix Miata <mrmazda@earthlink.net> |
|---|---|
| Date | 2016-06-01 02:40 +0200 |
| Subject | Re: buntu kybosh |
| Message-ID | <rF2mu-1c3-19@gated-at.bofh.it> |
| In reply to | #168379 |
Lisi Reisz composed on 2016-06-01 00:40 (UTC+0100): > On Wednesday 01 June 2016 00:15:20 Felix Miata wrote: >> Lisi Reisz composed on 2016-05-31 18:06 (UTC+0100): >> > ...I have just kyboshed the computer I have attached >> > to the television by trying Ubuntu MATE 16.04 as a dual boot. I am >> > mentally working out the best way at least to make it take a very back >> > seat, before I wipe the lot in frustration. And Debian Jessie was just >> > working nicely. >> Just what constituted the kyboshing? Neither boots? > The word was a little stronger than is totally justified. This is attached to > a television. I want to just turn it on. Ubuntu boots but is unusable, so I > have to hover over it, grab GRUB and get into Debian, because Ubuntu has > kyboshed (=destroyed) Debian's GRUB (of course!!). That's what *every* Linux installer will do if you do nothing to stop it, just like Windows will do unconditionally when it doesn't find compatible MBR code already installed. Had you installed Buntu first, then Debian after, Debian's installer would have usurped Buntu's Grub. Anytime anyone wants an additional Linux distro alongside (an) already installed other(s) on a BIOS system, and you *don't* want the existing bootloader usurped or otherwise tampered with, you absolutely *must* do whatever it takes to instruct the installer to *not* put bootloader on MBR - even if that means installing no bootloader at all. In most multiboot environments, MBR is the wrong place for a bootloader in the first place. Bootloader on MBR invites its own destruction in every BIOS multiboot environment: https://old-en.opensuse.org/Bugs/grub#How_does_a_PC_boot_.2F_How_can_I_set_up_a_working_GRUB.3F > Since seeing the screen is difficult, and I watch television only when I am > tired, this is tedious in the extreme, and it was working beautifully, all > but Channel 4 replays, before I gave Ubuntu a chance. I thought that dual > booting couldn't do any harm. I had forgotten Ubuntu's ability to do harm > when in my hands. What was that Stephen said about guns and feet. ;-) When you get a little ambitious, boot Buntu, reconfigure it with bootloader on / partition, then go into Grub menu next boot and choose to boot Debian. Reinstall Debian's bootloader back to MBR, and you should be good to go. Alternatively, as above URL suggests, install Debian's bootloader to Debian /, install generic MBR code, and mark Debian's / partition active. That way you'll be booting same as Windows and DOS, as PCs have been booting since two decades before Grub was conceived, and with a configuration that can be repaired from a DOS floppy if necessary in little more time than it takes to boot a floppy or CD. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
[toc] | [prev] | [next] | [standalone]
| From | Lisi Reisz <lisi.reisz@gmail.com> |
|---|---|
| Date | 2016-06-01 09:50 +0200 |
| Subject | Re: buntu kybosh |
| Message-ID | <rF94B-5yl-9@gated-at.bofh.it> |
| In reply to | #168383 |
On Wednesday 01 June 2016 01:31:26 Felix Miata wrote: > > The word was a little stronger than is totally justified. This is > > attached to a television. I want to just turn it on. Ubuntu boots but > > is unusable, so I have to hover over it, grab GRUB and get into Debian, > > because Ubuntu has kyboshed (=destroyed) Debian's GRUB (of course!!). > > That's what *every* Linux installer will do if you do nothing to stop it, > just like Windows will do unconditionally when it doesn't find compatible > MBR code already installed. Had you installed Buntu first, then Debian > after, Debian's installer would have usurped Buntu's Grub. That is why I said "of course". And that is why I said *I* kyboshed it and not *Ubuntu* kyboshed it. To be fair to myself, I did not expect Ubuntu to be completely unusable. Lisi
[toc] | [prev] | [next] | [standalone]
| From | Lisi Reisz <lisi.reisz@gmail.com> |
|---|---|
| Date | 2016-06-01 11:00 +0200 |
| Subject | Re: buntu kybosh |
| Message-ID | <rFaan-6aY-45@gated-at.bofh.it> |
| In reply to | #168387 |
On Wednesday 01 June 2016 08:40:39 Lisi Reisz wrote: > That is why I said "of course". And that is why I said *I* kyboshed it and > not *Ubuntu* kyboshed it. No I didn't. I said "*Ubuntu* kyboshed". Mea culpa. Lisi
[toc] | [prev] | [next] | [standalone]
| From | deloptes <deloptes@gmail.com> |
|---|---|
| Date | 2016-06-01 21:10 +0200 |
| Message-ID | <rFjGF-41O-3@gated-at.bofh.it> |
| In reply to | #168333 |
Mostafa Shahverdy wrote: >> >> Why not try with older kernel that works with the driver? >> > I always keep my OS up to date, that's why I use Sid, I always want the > latest updates :) > This is non sense! And you prove it with your question here. regards
[toc] | [prev] | [next] | [standalone]
| From | Paul Johnson <baloo@ursamundi.org> |
|---|---|
| Date | 2016-05-31 10:30 +0200 |
| Message-ID | <rENdM-eU-21@gated-at.bofh.it> |
| In reply to | #168314 |
[Multipart message — attachments visible in raw view] — view raw
On Mon, May 30, 2016 at 8:23 AM, Mostafa Shahverdy <mostafa@mostafa.info> wrote: > Hi everyone. > > I have an ultra wide monitor that supports 2560x1080. > While I have a Radeon 5450 graphic card, running Debian Sid, I only can > get 1920x1080. > I installed firmware-linux-nonfree to get it running. So why isn't my > complete resolution listed? > Also I experience some glitches while watching videos. > Have you tried the open drivers with arandr yet? At this point, most software runs more reliably and more smoothly on the open drivers and newer Steam titles might actually expect the open drivers. The only thing I've found that performs worse is Second Life, but to be fair, you pretty much have to have a cartoonist's workstation from Disney Animation to get flawless performance out of that virtual reality system anyway, so getting ~6-12 FPS out of a mid-low-end two year old laptop is doing decent as far as I'm concerned...
[toc] | [prev] | [next] | [standalone]
| From | Mostafa Shahverdy <mostafa@mostafa.info> |
|---|---|
| Date | 2016-05-31 13:10 +0200 |
| Message-ID | <rEPIC-1X8-21@gated-at.bofh.it> |
| In reply to | #168330 |
[Multipart message — attachments visible in raw view] — view raw
On Tue, May 31, 2016 at 03:24:07AM -0500, Paul Johnson wrote: > On Mon, May 30, 2016 at 8:23 AM, Mostafa Shahverdy <mostafa@mostafa.info> > wrote: > > Have you tried the open drivers with arandr yet? > No, what are the related package names? -- Regards, Mostafa Shahverdy <http://www.mostafa.info/pgp>
[toc] | [prev] | [next] | [standalone]
| From | Paul Johnson <baloo@ursamundi.org> |
|---|---|
| Date | 2016-05-31 18:00 +0200 |
| Message-ID | <rEUff-4Bu-23@gated-at.bofh.it> |
| In reply to | #168335 |
[Multipart message — attachments visible in raw view] — view raw
On Tue, May 31, 2016 at 6:05 AM, Mostafa Shahverdy <mostafa@mostafa.info> wrote: > On Tue, May 31, 2016 at 03:24:07AM -0500, Paul Johnson wrote: > > On Mon, May 30, 2016 at 8:23 AM, Mostafa Shahverdy <mostafa@mostafa.info > > > > wrote: > > > > Have you tried the open drivers with arandr yet? > > > > No, what are the related package names? In Jesse, that should be xserver-xorg-video-radeon and arandr
[toc] | [prev] | [next] | [standalone]
| From | Felix Miata <mrmazda@earthlink.net> |
|---|---|
| Date | 2016-05-31 11:40 +0200 |
| Message-ID | <rEOjw-Ur-23@gated-at.bofh.it> |
| In reply to | #168314 |
Mostafa Shahverdy composed on 2016-05-30 17:53 (UTC+0430): > I have an ultra wide monitor that supports 2560x1080. > While I have a Radeon 5450 graphic card, running Debian Sid, I only can get 1920x1080. > I installed firmware-linux-nonfree to get it running. So why isn't my complete resolution listed? I can't answer why, at least, not without seeing your Xorg.0.log. Does it show the FBDEV or VESA driver being used rather than modeset or RADEON? I don't have Sid on a 5450 system, but I do have Wheezy on a 5450, which does refuse 2560x1080. Same machine also has openSUSE 42.1, which was released last November, and does do 2560x1080 whether on VGA output or HDMI output, using the modeset driver built into Xorg 1.17.2 server itself. There should be no need for the AMD/ATI/Radeon driver when using recent server versions with most gfxchips that are new enough, as the 5450 is. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
[toc] | [prev] | [next] | [standalone]
| From | Felix Miata <mrmazda@earthlink.net> |
|---|---|
| Date | 2016-05-31 15:40 +0200 |
| Message-ID | <rES3M-3kr-29@gated-at.bofh.it> |
| In reply to | #168332 |
Mostafa Shahverdy composed on 2016-05-31 15:45 (UTC+0430): > On Tue, May 31, 2016 at 05:29:38AM -0400, Felix Miata wrote: >> I don't have Sid on a 5450 system, but I do have Wheezy on a 5450, which >> does refuse 2560x1080. Same machine also has openSUSE 42.1, which was >> released last November, and does do 2560x1080 whether on VGA output or HDMI >> output, using the modeset driver built into Xorg 1.17.2 server itself. > In order to check if 5450 really supports 2560x1080, I installed the > driver on Windows, and it works fine. >> There should be no need for the AMD/ATI/Radeon driver when using recent >> server versions with most gfxchips that are new enough, as the 5450 is. > So any solution in my case? > [ 78.587] (II) RADEON(0): Using hsync ranges from config file > [ 78.587] (II) RADEON(0): Using vrefresh ranges from config file Show us the config file this is referring to, either /etc/X11/xorg.conf or whatever is in /etc/X11/xorg.conf.d/. Is it a leftover from when you had a GeForce installed? If so, remove it and try. Most displays work with most gfxcards without any config file by using the display's EDID. Something else to try: If Plymouth is installed, purge it and try again. Mostafa Shahverdy composed on 2016-05-31 15:55 (UTC+0430): > On Tue, May 31, 2016 at 01:15:39PM +0200, Jörg-Volker Peetz wrote: >> Did your setup work before? >Yes, while I was using Gforce. What Gforce? Were you using it with the proprietary NVidia driver in the same Sid? If so, did you completely purge it and reverse all the changes it made to your FOSS configuration? If none of the above helps, put an xrandr command in a startup script, e.g.: /etc/X11/Xsession.d/95local containing xrandr --output HDMI-0 --mode 2560x1080 --rate 60 (--rate 60 optional, if necessary) Another thing to try (maybe first): purge xserver-xorg-video-ati and/or xserver-xorg-video-radeon, so that the modeset driver internal to Xorg will be used instead of radeon. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
[toc] | [prev] | [next] | [standalone]
| From | Felix Miata <mrmazda@earthlink.net> |
|---|---|
| Date | 2016-06-03 06:00 +0200 |
| Message-ID | <rFOr7-6ts-21@gated-at.bofh.it> |
| In reply to | #168314 |
Mostafa Shahverdy composed on 2016-05-30 17:53 (UTC+0430): > I have an ultra wide monitor that supports 2560x1080. > While I have a Radeon 5450 graphic card, running Debian Sid, I only can get 1920x1080. ... I suggest you try purging xserver-xorg-video-ati and xserver-xorg-video-radeon. I couldn't get Stretch's radeon to do 2560x1080 with HD5450 either, but 2560x1080 WFM with the built-in/native Xorg modeset driver, the recommended FOSS driver for non-ancient gfxchips in xserver versions >1.16.x: http://fm.no-ip.com/SS/KDE/d9tde-desktop-2560x1080.jpg -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
[toc] | [prev] | [next] | [standalone]
| From | Mostafa Shahverdy <mostafa@mostafa.info> |
|---|---|
| Date | 2016-06-04 07:50 +0200 |
| Message-ID | <rGcD7-4Nz-1@gated-at.bofh.it> |
| In reply to | #168456 |
[Multipart message — attachments visible in raw view] — view raw
On Thu, Jun 02, 2016 at 11:54:00PM -0400, Felix Miata wrote: > Mostafa Shahverdy composed on 2016-05-30 17:53 (UTC+0430): > > > I have an ultra wide monitor that supports 2560x1080. > > While I have a Radeon 5450 graphic card, running Debian Sid, I only can get 1920x1080. > ... > > I suggest you try purging xserver-xorg-video-ati and xserver-xorg-video-radeon. > I couldn't get Stretch's radeon to do 2560x1080 with HD5450 either, but > 2560x1080 WFM with the built-in/native Xorg modeset driver, the recommended > FOSS driver for non-ancient gfxchips in xserver versions >1.16.x: > > http://fm.no-ip.com/SS/KDE/d9tde-desktop-2560x1080.jpg I did. Now I get a better video (no glitches while playing movies). But still I can get only 1920x1080. I have to mention that using a DVI cable I can get 2560x1080, but it is very very noisy. -- Regards, Mostafa Shahverdy <http://www.mostafa.info/pgp>
[toc] | [prev] | [next] | [standalone]
| From | Felix Miata <mrmazda@earthlink.net> |
|---|---|
| Date | 2016-06-04 08:50 +0200 |
| Message-ID | <rGdzb-5nX-1@gated-at.bofh.it> |
| In reply to | #168520 |
Mostafa Shahverdy composed on 2016-06-04 10:16 (UTC+0430): > On Thu, Jun 02, 2016 at 11:54:00PM -0400, Felix Miata wrote: >> Mostafa Shahverdy composed on 2016-05-30 17:53 (UTC+0430): >> > I have an ultra wide monitor that supports 2560x1080. >> > While I have a Radeon 5450 graphic card, running Debian Sid, I only can get 1920x1080. >> ... >> I suggest you try purging xserver-xorg-video-ati and xserver-xorg-video-radeon. >> I couldn't get Stretch's radeon to do 2560x1080 with HD5450 either, but >> 2560x1080 WFM with the built-in/native Xorg modeset driver, the recommended >> FOSS driver for non-ancient gfxchips in xserver versions >1.16.x: >> http://fm.no-ip.com/SS/KDE/d9tde-desktop-2560x1080.jpg > I did. Now I get a better video (no glitches while playing movies). But > still I can get only 1920x1080. > I have to mention that using a DVI cable I can get 2560x1080, but it is > very very noisy. I don't know, but were it not that in Windows 2560x1080 works OK I would suspect this meant you might have cables that aren't up to the task, or a possibly borderline defective HD5450. Maybe Linux, either kernel or driver or Xorg, is less efficient and needs higher quality cabling? How long are the cables you tried? What gauge is the HDMI cable's wires? Which version does your HDMI cable support, 1.1? 1.2? 1.3? 1.4? Note that AIUI, DVI and HDMI video signals are the same, the main difference that I'm aware of between DVI and HDMI being that a DVI cable omits carriage of audio. Video noise on DVI could be a software issue, DE/theme or driver or server. If it's theme or DE, disabling compositing or switching themes might be workarounds. Possibly someone might be able to spot a remaining issue if you share this latest Xorg.0.log and .xsession-errors from using the HDMI cable and modeset driver - maybe even me. It could be a custom xorg.conf file could work around an EDID shortcoming that the Windows driver avoids. Booting some other distribution's live media might be telling. It could be that your particular hardware in combination with Sid uncovers an Xorg or kernel bug that does not manifest elsewhere. Try the Knoppix 7.6 DVD or one of openSUSE's (42.1, kernel 4.1.21/server 1.17.2 or Tumbleweed, kernel 4.6.0/server 1.18.3) or Fedora's latest (v23, kernel 4.5.5/server 1.18.3 via updates, or v24 beta, kernel 4.5.5/server 1.18.3). I don't think I know enough to suggest any more except to refer to this very thread[1] by starting a thread on the xorg-driver-ati@lists.x.org and/or the xorg@lists.x.org list. [1] https://lists.debian.org/debian-user/2016/05/msg01057.html -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
[toc] | [prev] | [next] | [standalone]
| From | Mostafa Shahverdy <mostafa@mostafa.info> |
|---|---|
| Date | 2016-06-04 21:20 +0200 |
| Message-ID | <rGph0-51C-3@gated-at.bofh.it> |
| In reply to | #168522 |
[Multipart message — attachments visible in raw view] — view raw
On Sat, Jun 04, 2016 at 02:43:25AM -0400, Felix Miata wrote: > Mostafa Shahverdy composed on 2016-06-04 10:16 (UTC+0430): > > > On Thu, Jun 02, 2016 at 11:54:00PM -0400, Felix Miata wrote: > > > > Mostafa Shahverdy composed on 2016-05-30 17:53 (UTC+0430): > > > > > I have an ultra wide monitor that supports 2560x1080. > > > > While I have a Radeon 5450 graphic card, running Debian Sid, I only can get 1920x1080. > > > ... > > > > I suggest you try purging xserver-xorg-video-ati and xserver-xorg-video-radeon. > > > I couldn't get Stretch's radeon to do 2560x1080 with HD5450 either, but > > > 2560x1080 WFM with the built-in/native Xorg modeset driver, the recommended > > > FOSS driver for non-ancient gfxchips in xserver versions >1.16.x: > > > > http://fm.no-ip.com/SS/KDE/d9tde-desktop-2560x1080.jpg > > > I did. Now I get a better video (no glitches while playing movies). But > > still I can get only 1920x1080. > > > I have to mention that using a DVI cable I can get 2560x1080, but it is > > very very noisy. > > I don't know, but were it not that in Windows 2560x1080 works OK I would > suspect this meant you might have cables that aren't up to the task, or a > possibly borderline defective HD5450. Maybe Linux, either kernel or driver > or Xorg, is less efficient and needs higher quality cabling? How long are > the cables you tried? What gauge is the HDMI cable's wires? Which version > does your HDMI cable support, 1.1? 1.2? 1.3? 1.4? At this moment I can't tell if my cables support different versions of HDMI or not, because I don't know how to check them. But I know one thing about my DVI cable. Although it has DVI-D Dual-Link connectors, but I think it is Single-Link, because it is thin. From this video https://www.youtube.com/watch?v=4lwwO-eNJPc I can say my cable is not proper. I have to check it using a Multimeter, which I don't have one at the moment. Also the lable on my DVI calbe (on cable itself, and not connectors) is "High Speed HDMI cable 20276 style 80c 30v vw-1 -- Made in CHINA". > > Note that AIUI, DVI and HDMI video signals are the same, the main difference > that I'm aware of between DVI and HDMI being that a DVI cable omits carriage > of audio. I think a Dual-Link DVI-D must be thicker thank HDMI, right? > > Video noise on DVI could be a software issue, DE/theme or driver or server. > If it's theme or DE, disabling compositing or switching themes might be > workarounds. > > Possibly someone might be able to spot a remaining issue if you share this > latest Xorg.0.log and .xsession-errors from using the HDMI cable and modeset > driver - maybe even me. It could be a custom xorg.conf file could work > around an EDID shortcoming that the Windows driver avoids. > > Booting some other distribution's live media might be telling. It could be > that your particular hardware in combination with Sid uncovers an Xorg or > kernel bug that does not manifest elsewhere. Try the Knoppix 7.6 DVD or one > of openSUSE's (42.1, kernel 4.1.21/server 1.17.2 or Tumbleweed, kernel > 4.6.0/server 1.18.3) or Fedora's latest (v23, kernel 4.5.5/server 1.18.3 via > updates, or v24 beta, kernel 4.5.5/server 1.18.3). > > I don't think I know enough to suggest any more except to refer to this very > thread[1] by starting a thread on the xorg-driver-ati@lists.x.org and/or the > xorg@lists.x.org list. I'm going to check cables, test a live OS and see results. If there was no luck I will continue on other lists. Thank you for your helps. > > [1] https://lists.debian.org/debian-user/2016/05/msg01057.html > -- > "The wise are known for their understanding, and pleasant > words are persuasive." Proverbs 16:21 (New Living Translation) > > Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! > > Felix Miata *** http://fm.no-ip.com/ > -- Regards, Mostafa Shahverdy <http://www.mostafa.info/pgp>
[toc] | [prev] | [standalone]
Page 2 of 2 — ← Prev page 1 [2]
Back to top | Article view | linux.debian.user
csiph-web