Re: Debian 9 rocks, really
On Sat, Mar 24, 2018 at 10:31:11PM +, Andre Rodier wrote: > […] Yeah! I've not come such a long way yet, considering I am only 27 years old, but I have been using Linux systems for 14 years now. Started with SuSE 7.2 (with a short visit to 5.3 for fun), switched to Ubuntu later and the nto Gentoo for a few years, until arriving at Debian many years ago. Watching Debian's development (and contributing to it) is a great joy - while some time ago there were valid reasons for creating Ubuntu, and users had reasons to consider Debian outdated and complicated, all that is gone now. Take a Debian 9 installer (in some cases, maybe the non-free firmware version), and it installs on the most awkward of hardware without complaining. If it doesn't, just fix it, because it gives you everything you need to do so. Most important, Debian is the distribution that kept me satisfied for long enough that I am now a developer (keyring update pending ;)). I lost track of becoming one with Gentoo, because they were cool but did not have good quality assurance, and I los ttrack at SuSE because they had great quality but the community was questionnable (that changed by now, mind you) - Debian has the best of both worlds, a great community, great tools, and QA anddevelopment tools that make it fun to work with and still get respected in enterprise environments. So thank you, Debian! Cheers, Nik signature.asc Description: PGP signature
Re: Debian 9 rocks, really
On Sat, 24 Mar 2018 22:31:11 + Andre Rodier wrote: > Hello all, > > I have been using Linux since more than 20 years, and Debian Linux > since Potato. I even remember the time when you had to carefully read > the documentation of your monitor to avoid damaging it, by choosing > the wrong frequencies for the X server. > > I am using a lot of computers, from small workstations to big servers > in data centres or in the clouds, like Rackspace, AWS or Google > cloud. If you are a little bit careful with the question asked, and > have a minimum of IT knowledge, the Debian installer is wonderful. It > always give you the control if something goes wrong, for instance by > activating another console. > > The task selection concept is great, for those who want to install > their favourite desktop environment easily. I love the fact that > multiple DE are given, and I can install and try more than one. > > I recently re-discovered preseed, and I really enjoy it as well. > > Thank you for making my life easier, and my work so beneficial. > Debian people are really a great team !!! > Indeed they are, and patient, by and large. Amazing - considering they have to put up with people like me :-) I don't even want to think about having to run my desktop without Debian. - Dan
Re: Debian 9 rocks, really
On Sat, 2018-03-24 at 22:31 +, Andre Rodier wrote: > Hello all, > > > > Thank you for making my life easier, and my work so beneficial. > Debian > people are really a great team !!! > > André Rodier. > I concur. It's come a long way and is treat to use. Forest
Re: Debian 9 rocks, really
Hahahaha -- +1, for me, for what's turning out to be a very entertaining weekend... Introduced to Debian in 2003, stayed on it though 2008, then Ubuntu for a while but defaulting to Debian full time for the past few years A particular moment to send thanks to the community and to these lists, for teaching me more than I could imagine to know about the whole system, from all sorts of interesting nooks and crannies to some of the fundamental design features of a well-maintained distribution. Especially in light of recent events concerning the way the consequences of our seemingly trivial computer use can be manipulated in opaque ways, a deeper commitment to really understanding how some of these systems work is all the more important, and engaging with open systems and a building a responsive community becomes more critical. So yeah -- maybe some haters, but full speed ahead, to Buster and beyond! On 03/24/2018 06:31 PM, Andre Rodier wrote: Hello all, I have been using Linux since more than 20 years, and Debian Linux since Potato. I even remember the time when you had to carefully read the documentation of your monitor to avoid damaging it, by choosing the wrong frequencies for the X server. I am using a lot of computers, from small workstations to big servers in data centres or in the clouds, like Rackspace, AWS or Google cloud. If you are a little bit careful with the question asked, and have a minimum of IT knowledge, the Debian installer is wonderful. It always give you the control if something goes wrong, for instance by activating another console. The task selection concept is great, for those who want to install their favourite desktop environment easily. I love the fact that multiple DE are given, and I can install and try more than one. I recently re-discovered preseed, and I really enjoy it as well. Thank you for making my life easier, and my work so beneficial. Debian people are really a great team !!! André Rodier.
Re: Debian 9 sucks really badly
On 2018-03-24, Fekete Tamás wrote: > > And stop telling us that the OS is crap. In turn, you made the impression > that you are a negative person, but just because of this I will not go to > your home and your neighborhood to tell you are a(n) ... > It's only water off a penguin's back. And the penguin's back! -- Bah, the latest news, the latest news is not the last. Samuel Beckett
Re: Debian 9 sucks really badly
To the original sender (Chris Anderson), we have a huge community. If you don't feel comfortable with this product switch back to something which better fit to your needs. And stop telling us that the OS is crap. In turn, you made the impression that you are a negative person, but just because of this I will not go to your home and your neighborhood to tell you are a(n) ... - Tamas Fekete 2018-03-24 19:35 GMT+01:00 Brad Rogers : > On Sat, 24 Mar 2018 14:26:38 -0400 > Roberto C. Sánchez wrote: > > Hello Roberto, > > >good responses are better than nothing in this case. > > Good arguments, but I'm afraid vague won't do for help in the future. > Things will have changed, including Debian's installer. > > One thing does ring out loud and clear, though: Help is available, no > matter what. In that sense, a win. > > -- > Regards _ > / ) "The blindingly obvious is > / _)radnever immediately apparent" > I hope I live to relive the days gone by > Old Before I Die - Robbie Williams >
Re: Debian 9 sucks really badly
On Sat, 24 Mar 2018 14:26:38 -0400 Roberto C. Sánchez wrote: Hello Roberto, >good responses are better than nothing in this case. Good arguments, but I'm afraid vague won't do for help in the future. Things will have changed, including Debian's installer. One thing does ring out loud and clear, though: Help is available, no matter what. In that sense, a win. -- Regards _ / ) "The blindingly obvious is / _)radnever immediately apparent" I hope I live to relive the days gone by Old Before I Die - Robbie Williams pgp2OBybWCx0C.pgp Description: OpenPGP digital signature
Re: Debian 9 sucks really badly
On Sat, Mar 24, 2018 at 02:51:27PM +, Brad Rogers wrote: > Why is anybody replying to this? > > It's quite clearly a drive-by complaint. The OP is *not* going to > listen to advice or hear offers of help. They won't get them - they're > not subbed to the list. > There are those who will read this thread months or years down the line. Despite the lack of information in the initial post, reasonable responses that try to point users in the right direction might give clues to future readers of this thread. Those responses will also possibly save some readers the frustration of finding something that resembles there own problem without any follow-up. Granted, the original post and the follow-ups in this case are by necessity vague. However, good responses are better than nothing in this case. Regards, -Roberto -- Roberto C. Sánchez
Re: Nu B
On 2018-03-24, Curt wrote: > On 2018-03-24, Michelle Konzack wrote: >> Hello, >> >> Am 2018-03-24 hackte jmc...@gmail.com in die Tasten: >>> I was planing on getting Debian 64bit version on a live/install dvd, >>> but >> >> No "BUT", just try it. If the Live-DVD works correctly, >> you can install Debian at any time on the Laptop. >> > > I'm uncertain that does work correctly, in fact (install from the live DVD). > > I've heard right here that it may not. > > I'd recommend the netinstall--or if that's not practicable--the > downloaded CD #1 methodology myself, regardless of the hardware involved > (though if networking would require non-free firmware maybe the unofficial > firmware netinstall iso might be easiest route). > Hey maybe I misinterpreted what you said. Test with the live dvd by all means, but install otherwise. Out. -- Bah, the latest news, the latest news is not the last. Samuel Beckett
Re: Debian 9 sucks really badly
true, is not as stable and user friendly as (k)ubuntu or Opensuse, but it works. André Op 24-3-2018 om 14:44 schreef Eike Lantzsch: > On Saturday, March 24, 2018 2:01:13 PM -03 Chris Anderson wrote: >> Hello >> >> I have been using different flavours of Linux since slackware 96 over 20 >> years ago. Since then I have installed and used at least a dozen >> different flavours. By far the most challenging was the X windows system >> for slackware but I managed to get it installed and running with no >> problems. >> >> Last week I bought a new PC and decided to try debian so I downloaded >> the DVD version 9 and performed a fresh install besides windows 10. >> Right from the off, it fucked up, Grubb was a hassle as this was the >> default boot loader,(I have always used LILO), it would not find the >> windows partition, I managed to fix this. Then it didn't give me a >> choice of X windows manager, I was stuck with KDE, which I am familiar >> with and am aware of its may limitations and given the choice I wouldn't >> use KDE for installation and configuration. >> >> Nearly everything fucked up from the Network install to the gcc make >> command, what a hassle and after spending nearly a week trying to get it >> all working I've had enough and am not wasting any more of my time on >> this awful software. >> >> So thanks for wasting my time Debian and for future reference, go and >> get fucked!!! >> >> >> Chris Anderson > > What you are telling us is: > > 1) You are able to eloquently express your dismay in writing > 2) You are unwilling to either read menu items nor manuals nor release notes > 3) You are expecting Debian install to have everything your way without > contributing to Debian development > 4) You don't ask for directions before walking down that lane nor asking for > help being halfway down that lane > 5) You never contributed anything to any mailinglist, not even slackware, > under the e-mail address you used > 6) You use words in writing that many would not touch with a pole > 7) You show the traits of a toxic personality (whether you actually have one > we don't know) > > verdict: Troll > > ZP6CGE QRZ > >
Re: Nu B
On 2018-03-24, Michelle Konzack wrote: > Hello, > > Am 2018-03-24 hackte jmc...@gmail.com in die Tasten: >> I was planing on getting Debian 64bit version on a live/install dvd, >> but > > No "BUT", just try it. If the Live-DVD works correctly, > you can install Debian at any time on the Laptop. > I'm uncertain that does work correctly, in fact (install from the live DVD). I've heard right here that it may not. I'd recommend the netinstall--or if that's not practicable--the downloaded CD #1 methodology myself, regardless of the hardware involved (though if networking would require non-free firmware maybe the unofficial firmware netinstall iso might be easiest route). -- Bah, the latest news, the latest news is not the last. Samuel Beckett
Re: Nu B
Not necessarily, some dell laptops block installation of other operating systems. I had this happen with a Dell aspire I think 1540 several years ago. On Sat, 24 Mar 2018, Michelle Konzack wrote: Date: Sat, 24 Mar 2018 12:38:08 From: Michelle Konzack To: debian-user@lists.debian.org Subject: Re: Nu B Resent-Date: Sat, 24 Mar 2018 16:38:25 + (UTC) Resent-From: debian-user@lists.debian.org Hello, Am 2018-03-24 hackte jmc...@gmail.com in die Tasten: I was planing on getting Debian 64bit version on a live/install dvd, but No "BUT", just try it. If the Live-DVD works correctly, you can install Debian at any time on the Laptop. now delayed because the recent negative comments I read about Debian 9 on this list. so help me out please advice and comments welcome. Ignore such idiots. They only complain but do not want to hear anything about help. If you install Debian and have problems, ask gently on this list and you get the desired help. So here i am fresh meat needs to be cured, cooked and served up. We all have started like this. Me in 1999 with Debian 2.1 Slink! This was a time, where documentation was very rare and you had to bite in the sauer appel if you want to get GNU/Linux installed (no mather which Distribution) thank you friends, jimmy, southern plains USA Have a nice weekend and greetings from Estonia with -8?C on the field where I was just working --
Re: Nu B
Hello, Am 2018-03-24 hackte jmc...@gmail.com in die Tasten: > I was planing on getting Debian 64bit version on a live/install dvd, > but No "BUT", just try it. If the Live-DVD works correctly, you can install Debian at any time on the Laptop. > now delayed because the recent negative comments I read about Debian 9 > on this list. so help me out please advice and comments welcome. Ignore such idiots. They only complain but do not want to hear anything about help. If you install Debian and have problems, ask gently on this list and you get the desired help. > So here i am fresh meat needs to be cured, cooked and served up. We all have started like this. Me in 1999 with Debian 2.1 Slink! This was a time, where documentation was very rare and you had to bite in the sauer appel if you want to get GNU/Linux installed (no mather which Distribution) > thank you friends, jimmy, southern plains USA Have a nice weekend and greetings from Estonia with -8°C on the field where I was just working -- Michelle KonzackMiila ITSystems @ TDnet GNU/Linux Developer 00372-54541400
Re: Can't get an OpenGL context above 1.3 in Stretch
On Sat, Mar 24, 2018 at 03:26:03PM +0100, Hans wrote:
> Am Samstag, 24. März 2018, 14:58:41 CET schrieb Daniel Keast:
> Hi Daniel,
>
> maybe I am wrong, but I believe, that the problem might be your hardware.
>
> Some hardware is not capable on opengl2, only on opengl1. On my netbook I am
> using an
> Intel i945 graphics chip, which is only opengl1.0 capable.
I think this cpu is sandy bridge, which if I'm reading this right means I should
be able to get up to Open GL 3.3:
https://en.wikipedia.org/wiki/Intel_HD_and_Iris_Graphics#Capabilities
Which is what supertuxkart seems to be reporting as it's GL_VERSION. That's the
thing that's throwing me at the moment, supertuxkart seems to work fine...
there's something different in my code, but I can't get my head around the
difference.
> However, I can use opengl2, as this is software based! In mesa-1.3 there was
> a software
> opengl2 solution, which is no more in higher versions. The developer decided
> to get rid of
> it, because it was too difficult to maintain it any more.
I think when I run LIBGL_SOFTWARE_ALWAYS=true it forces mesa to use it's
software driver (I think that's what Gallium 0.4 on llvmpipe (LLVM 3.9, 256
bits)) means.
> So I downgraded the following packages and theire dependencies to version 1.3:
>
> libgl1-mesa-dri libgl1-mesa-glx libglapi-mesa
>
> After that, I set these three packages to hold by using aptitude:
>
> aptitude hold libgl1-mesa-dri libgl1-mesa-glx libglapi-mesa
I get this when I try the downgrade:
# dpkg -i libgl*
dpkg: warning: downgrading libgl1-mesa-dri:amd64 from 13.0.6-1+b2 to
10.3.2-1+deb8u1
(Reading database ... 325277 files and directories currently installed.)
Preparing to unpack libgl1-mesa-dri_10.3.2-1+deb8u1_amd64.deb ...
Unpacking libgl1-mesa-dri:amd64 (10.3.2-1+deb8u1) over (13.0.6-1+b2) ...
dpkg: warning: downgrading libgl1-mesa-glx:amd64 from 13.0.6-1+b2 to
10.3.2-1+deb8u1
Preparing to unpack libgl1-mesa-glx_10.3.2-1+deb8u1_amd64.deb ...
Unpacking libgl1-mesa-glx:amd64 (10.3.2-1+deb8u1) over (13.0.6-1+b2) ...
dpkg: warning: downgrading libglapi-mesa:amd64 from 13.0.6-1+b2 to
10.3.2-1+deb8u1
Preparing to unpack libglapi-mesa_10.3.2-1+deb8u1_amd64.deb ...
Unpacking libglapi-mesa:amd64 (10.3.2-1+deb8u1) over (13.0.6-1+b2) ...
dpkg: dependency problems prevent configuration of libgl1-mesa-dri:amd64:
libgl1-mesa-dri:amd64 depends on libllvm3.5; however:
Package libllvm3.5 is not installed.
dpkg: error processing package libgl1-mesa-dri:amd64 (--install):
dependency problems - leaving unconfigured
Setting up libglapi-mesa:amd64 (10.3.2-1+deb8u1) ...
Setting up libgl1-mesa-glx:amd64 (10.3.2-1+deb8u1) ...
Processing triggers for libc-bin (2.24-11+deb9u3) ...
Processing triggers for glx-alternative-mesa (0.7.4) ...
Processing triggers for libc-bin (2.24-11+deb9u3) ...
Errors were encountered while processing:
libgl1-mesa-dri:amd64
Starts sounding a bit scary, is there anything else you've done?
> so they are not updated automatically. For me, this solution is working very
> well, as I can
> still use opengl2 (I love the special effects in KDE, which need opengl2) and
> until today I
> got in no problems. Even games are running faster (also in wine).
>
> Maybe this does help. It is a pity, that the software opengl2 is been gone in
> mesa, but that
> how are things change.
I'm confused since the software renderer above gives me a 3.0 context... perhaps
it's part of the intel driver are implemented in software that got removed?
> Best regards, happy hacking and good luck!
>
> Hans
Thanks a lot for your help, it's definitely more information than I had!
>
>
>
> > Heya All,
> >
> > I have some OpenGL code that used to work fine on Jessie, but now I'm
> > running Stretch I can't seem to get a context above 1.3. I have a ThinkPad
> > X220, with cpuinfo reporting that it has an "Intel(R) Core(TM) i5-2520M CPU
> > @ 2.50GHz".
> >
> > This I think is the relevant bit of code, but I'm happy to provide the rest,
> > it's just noddy glued together examples to make a cube spin:
> >
> > window = SDL_CreateWindow("SDL", SDL_WINDOWPOS_CENTERED,
> > SDL_WINDOWPOS_CENTERED, 0, 0,
> > SDL_WINDOW_FULLSCREEN_DESKTOP
> >
> > | SDL_WINDOW_OPENGL);
> >
> > if (!window) sdl_fail();
> >
> > if (SDL_ShowCursor(SDL_DISABLE) < 0) sdl_fail();
> >
> > /* initialise opengl */
> > if (SDL_GL_SetAttribute(SDL_GL_CONTEXT_MAJOR_VERSION, 2) != 0) sdl_fail
> > if (SDL_GL_SetAttribute(SDL_GL_CONTEXT_MINOR_VERSION, 1) != 0) sdl_fail
> > if (SDL_GL_SetAttribute(SDL_GL_DOUBLEBUFFER, 1) != 0) sdl_fail();
> >
> > if (!SDL_GL_CreateContext(window)) sdl_fail();
> > glEnable(GL_DEPTH_TEST);
> >
> > {
> > GLenum err = glewInit();
> > if (GLEW_OK != err) {
> >
Nu B
i really want to get Debian so i have been lurking this list for a while. I have Ubuntu on a loptop (Using Now) and want to use Debian on another used one i just bought. it is a Dell latitude E6400. device name = DTOP-HSAM375, PROCESSOR = Intel Core2 Duo CPU P8600 @ 2.40GHz 2.40 Ghz, Installed RAM = 4.00 GB Product type = 00330-50295-66418-AAOEM System Type = 64-bit op sys x64-based processor it came has win 10 pro installed and licensed OEM software long range i want to add the boat navigation open software pkg openCPM. I was planing on getting Debian 64bit version on a live/install dvd, but now delayed because the recent negative comments I read about Debian 9 on this list. so help me out please advice and comments welcome. So here i am fresh meat needs to be cured, cooked and served up. thank you friends, jimmy, southern plains USA
issue with iptables antispoofing rules in xen4.8
Hi all I have isses with the on domU startup automatically generated antispoofing rules by /etc/xen/scripts/vif-bridge and /etc/xen/scripts/vif-common.sh Both are part of the xen-utils-common package (4.8.3+comet2+shim4.10.0+comet3-1+deb9u5 installed on Debian 9.4). A domU test01 has two virtual interfaces - vif-test01-INT and vif-test01-TEST, both are connected to separate bridges named brINT and brTEST. The brINT is just an internal bridge without connectivity to an outside network to just connect all domUs and the dom0. The IP addressfor the vif-test01-INT interface is 192.168.240.68. The automatically generated rules per domU are: 1 ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-out vif-test01-INT --physdev-is-bridged 2 ACCEPT udp -- anywhere anywhere PHYSDEV match --physdev-in vif-test01-INT --physdev-is-bridged udp spt:bootpc dpt:bootps 3 ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-out vif-test01-INT --physdev-is-bridged 4 ACCEPT all -- 192.168.240.68 anywhere PHYSDEV match --physdev-in vif-test01-INT --physdev-is-bridged 5 ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-out vif-test01-TEST --physdev-is-bridged 6 ACCEPT udp -- anywhere anywhere PHYSDEV match --physdev-in vif-test01-TEST --physdev-is-bridged udp spt:bootpc dpt:bootps 7 ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-out vif-test01-TEST --physdev-is-bridged 8 ACCEPT all -- test01 anywhere PHYSDEV match --physdev-in vif-test01-TEST --physdev-is-bridged ... 33 REJECT all -- anywhere anywhere reject-with icmp-port-unreachable >From what I see is that the rules 1/3 and 5/7 are doubled. The next issue is that antispoofing rules just don't work. If I change the ip adress of the vif-test01-INT interface to something like 192.168.240.168 IP packets between test01 and other domUs are still forwarded. If I manually change the iptables rules to something like (in this example just for the brINT connected interface): -A FORWARD -m physdev --physdev-is-bridged --physdev-in vif-test01-INT -p all ! -s 192.168.240.68 -j DROP -A FORWARD -m physdev --physdev-is-bridged --physdev-out vif-test01-INT -p all ! -d 192.168.240.68 -j DROP -A FORWARD -m physdev --physdev-is-bridged --physdev-in vif-test01-INT -p all -j ACCEPT -A FORWARD -m physdev --physdev-is-bridged --physdev-out vif-test01-INT -p all -j ACCEPT ... -A FORWARD -j REJECT --reject-with icmp-port-unreachable then antispoofing works and IP packets with IP addresses different then 192.168.240.68 get dropped. Can somebody confirm this is an issue? Or do I just not understand how the antispoofing rules work on a virtual bridge? Is there a way to diable generation of antispoofing rules automatically on domU startup? I could configure a different vif.default.script in xl.conf and write a wrapper script, but it might be easier to just disable it and load iptables rules manually. -- Cheers, Sebastian EMail: s...@gmxpro.de
Re: Debian 9 sucks really badly
Why is anybody replying to this? It's quite clearly a drive-by complaint. The OP is *not* going to listen to advice or hear offers of help. They won't get them - they're not subbed to the list. Even if we could go to their home and help set it up, they'd not be interested because that would prove them wrong. The OP will simply bad mouth Debian at any opportunity henceforth. -- Regards _ / ) "The blindingly obvious is / _)radnever immediately apparent" You're all invited to a party, you don't even have to come Get The Funk Out - Extreme pgph1cTSli3y0.pgp Description: OpenPGP digital signature
Re: Debian 9 sucks really badly
Hi there! Since DOS 6.0 and later in SuSE and Debian I learnd one thing: Whenever things do not work, it is mostly my own fault. So, when I hear "It's not working!" or hardwer "This one sucks!", then the op mostly means "I do not know, how to fix it!" or harder "I am too stupid and not responsible, and also I am unwillingly to read or learn, how to fix it!" My advice: If things do not work, Just use this friendly and helpful list, and ask kindly and nicely for help. Believe me, there is always a nice and kindly response. And if you know something more than somebody else, let him know your knowledge and enlighten him. This is the way: Give, what you can give, and take, what you are offered. Work hand in hand. I myself are no coder, but when I can help, I try to do. I am not always correct, nor do I know much better than others, but if I think, I can help, I try. Have a nice weekend and have fun! Best Hans
Re: Debian 9 sucks really badly
On 03/23/2018 08:31 PM, Chris Anderson wrote: Hello I have been using different flavours of Linux since slackware 96 over 20 years ago. Since then I have installed and used at least a dozen different flavours. By far the most challenging was the X windows system for slackware but I managed to get it installed and running with no problems. Last week I bought a new PC and decided to try debian so I downloaded the DVD version 9 and performed a fresh install besides windows 10. Right from the off, it fucked up, Grubb was a hassle as this was the default boot loader,(I have always used LILO), it would not find the windows partition, I managed to fix this. Then it didn't give me a choice of X windows manager, I was stuck with KDE, which I am familiar with and am aware of its may limitations and given the choice I wouldn't use KDE for installation and configuration. Nearly everything fucked up from the Network install to the gcc make command, what a hassle and after spending nearly a week trying to get it all working I've had enough and am not wasting any more of my time on this awful software. So thanks for wasting my time Debian and for future reference, go and get fucked!!! Chris Anderson Linus! Is that you? -- Jimmy Johnson Debian Sid/Testing - Trinity KDE 3.5 - AMD A8-7600 - EXT4 at sda8 Registered Linux User #380263
Re: Can't get an OpenGL context above 1.3 in Stretch
Am Samstag, 24. März 2018, 14:58:41 CET schrieb Daniel Keast:
Hi Daniel,
maybe I am wrong, but I believe, that the problem might be your hardware.
Some hardware is not capable on opengl2, only on opengl1. On my netbook I am
using an
Intel i945 graphics chip, which is only opengl1.0 capable.
However, I can use opengl2, as this is software based! In mesa-1.3 there was a
software
opengl2 solution, which is no more in higher versions. The developer decided to
get rid of
it, because it was too difficult to maintain it any more.
So I downgraded the following packages and theire dependencies to version 1.3:
libgl1-mesa-dri libgl1-mesa-glx libglapi-mesa
After that, I set these three packages to hold by using aptitude:
aptitude hold libgl1-mesa-dri libgl1-mesa-glx libglapi-mesa
so they are not updated automatically. For me, this solution is working very
well, as I can
still use opengl2 (I love the special effects in KDE, which need opengl2) and
until today I
got in no problems. Even games are running faster (also in wine).
Maybe this does help. It is a pity, that the software opengl2 is been gone in
mesa, but that
how are things change.
Best regards, happy hacking and good luck!
Hans
> Heya All,
>
> I have some OpenGL code that used to work fine on Jessie, but now I'm
> running Stretch I can't seem to get a context above 1.3. I have a ThinkPad
> X220, with cpuinfo reporting that it has an "Intel(R) Core(TM) i5-2520M CPU
> @ 2.50GHz".
>
> This I think is the relevant bit of code, but I'm happy to provide the rest,
> it's just noddy glued together examples to make a cube spin:
>
> window = SDL_CreateWindow("SDL", SDL_WINDOWPOS_CENTERED,
> SDL_WINDOWPOS_CENTERED, 0, 0,
> SDL_WINDOW_FULLSCREEN_DESKTOP
>
> | SDL_WINDOW_OPENGL);
>
> if (!window) sdl_fail();
>
> if (SDL_ShowCursor(SDL_DISABLE) < 0) sdl_fail();
>
> /* initialise opengl */
> if (SDL_GL_SetAttribute(SDL_GL_CONTEXT_MAJOR_VERSION, 2) != 0) sdl_fail
> if (SDL_GL_SetAttribute(SDL_GL_CONTEXT_MINOR_VERSION, 1) != 0) sdl_fail
> if (SDL_GL_SetAttribute(SDL_GL_DOUBLEBUFFER, 1) != 0) sdl_fail();
>
> if (!SDL_GL_CreateContext(window)) sdl_fail();
> glEnable(GL_DEPTH_TEST);
>
> {
> GLenum err = glewInit();
> if (GLEW_OK != err) {
> fprintf(stderr, "Error: %s\n", glewGetErrorString(err));
> exit(1);
> }
> }
>
> printf("GL_RENDERER:\t%s\n", glGetString(GL_RENDERER));
> printf("GL_VERSION:\t%s\n", glGetString(GL_VERSION));
> printf("GL_VENDOR:\t%s\n", glGetString(GL_VENDOR));
>
> Just running as it is, I get this output:
>
> $ ./glthing
> MESA-LOADER: failed to retrieve device information
> GL_RENDERER:Mesa DRI Unknown Intel Chipset
> GL_VERSION: 1.3 Mesa 13.0.6
> GL_VENDOR: Intel Open Source Technology Center
> Segmentation fault
>
> The segfault is happening just below this code, when it tries to call
> glBindBuffers (which isn't in OpenGL 1.3). If I request an OpenGL 3.0
> context (I think this cpu should support slightly above that) it fails when
> creating the context:
>
> $ ./glthing
> MESA-LOADER: failed to retrieve device information
>
> Could not create GL context: GLXBadFBConfig
>
> If I dont use GLEW, and just use the OpenGL headers directly (and remove
> anything not OpenGL 1) then I get the higher context, this seems to match
> what happens with glxgears (which from the code seems to use the immediate
> mode):
>
> $ glxgears -info 2>&1 | grep GL_ | head -n 3
> GL_RENDERER = Mesa DRI Intel(R) Sandybridge Mobile
> GL_VERSION= 3.0 Mesa 13.0.6
> GL_VENDOR = Intel Open Source Technology Center
>
> There's no mention of the MESA-LOADER line in the raw output of glxgears.
> Some searching online doesn't seem to have gotten me anything useful about
> what that might be caused by.
>
> Supertuxkart reports that same GLXBadFBConfig line, and then seems to work
> anyway (reporting a 3.0 context).
>
> $ supertuxkart --log=2 | sed -ne '/Irrlicht/,$p'
> Irrlicht Engine version 1.8.0
Can't get an OpenGL context above 1.3 in Stretch
Heya All,
I have some OpenGL code that used to work fine on Jessie, but now I'm running
Stretch I can't seem to get a context above 1.3. I have a ThinkPad X220, with
cpuinfo reporting that it has an "Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz".
This I think is the relevant bit of code, but I'm happy to provide the rest,
it's just noddy glued together examples to make a cube spin:
window = SDL_CreateWindow("SDL", SDL_WINDOWPOS_CENTERED,
SDL_WINDOWPOS_CENTERED, 0, 0,
SDL_WINDOW_FULLSCREEN_DESKTOP
| SDL_WINDOW_OPENGL);
if (!window) sdl_fail();
if (SDL_ShowCursor(SDL_DISABLE) < 0) sdl_fail();
/* initialise opengl */
if (SDL_GL_SetAttribute(SDL_GL_CONTEXT_MAJOR_VERSION, 2) != 0) sdl_fail
if (SDL_GL_SetAttribute(SDL_GL_CONTEXT_MINOR_VERSION, 1) != 0) sdl_fail
if (SDL_GL_SetAttribute(SDL_GL_DOUBLEBUFFER, 1) != 0) sdl_fail();
if (!SDL_GL_CreateContext(window)) sdl_fail();
glEnable(GL_DEPTH_TEST);
{
GLenum err = glewInit();
if (GLEW_OK != err) {
fprintf(stderr, "Error: %s\n", glewGetErrorString(err));
exit(1);
}
}
printf("GL_RENDERER:\t%s\n", glGetString(GL_RENDERER));
printf("GL_VERSION:\t%s\n", glGetString(GL_VERSION));
printf("GL_VENDOR:\t%s\n", glGetString(GL_VENDOR));
Just running as it is, I get this output:
$ ./glthing
MESA-LOADER: failed to retrieve device information
GL_RENDERER:Mesa DRI Unknown Intel Chipset
GL_VERSION: 1.3 Mesa 13.0.6
GL_VENDOR: Intel Open Source Technology Center
Segmentation fault
The segfault is happening just below this code, when it tries to call
glBindBuffers (which isn't in OpenGL 1.3). If I request an OpenGL 3.0 context
(I think this cpu should support slightly above that) it fails when creating the
context:
$ ./glthing
MESA-LOADER: failed to retrieve device information
Could not create GL context: GLXBadFBConfig
If I dont use GLEW, and just use the OpenGL headers directly (and remove
anything not OpenGL 1) then I get the higher context, this seems to match what
happens with glxgears (which from the code seems to use the immediate mode):
$ glxgears -info 2>&1 | grep GL_ | head -n 3
GL_RENDERER = Mesa DRI Intel(R) Sandybridge Mobile
GL_VERSION= 3.0 Mesa 13.0.6
GL_VENDOR = Intel Open Source Technology Center
There's no mention of the MESA-LOADER line in the raw output of glxgears. Some
searching online doesn't seem to have gotten me anything useful about what that
might be caused by.
Supertuxkart reports that same GLXBadFBConfig line, and then seems to work
anyway (reporting a 3.0 context).
$ supertuxkart --log=2 | sed -ne '/Irrlicht/,$p'
Irrlicht Engine version 1.8.0
Linux 4.9.0-6-amd64 #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02) x86_64
[warn ] [IrrDriver Temp Logger]: Level 2: X Error: GLXBadFBConfig
[warn ] [IrrDriver Temp Logger]: Level 2: From call : unknown
[warn ] [IrrDriver Temp Logger]: Level 3: Vertex shader compilation
failed at position -1:
[warn ] [IrrDriver Temp Logger]: Level 3: Pixel shader compilation failed
at position -1:
[warn ] [IrrDriver Temp Logger]: Level 3: Vertex shader compilation
failed at position -1:
[warn ] [IrrDriver Temp Logger]: Level 3: Pixel shader compilation failed
at position -1:
[warn ] [IrrDriver Temp Logger]: Level 3: Vertex shader compilation
failed at position -1:
[warn ] [IrrDriver Temp Logger]: Level 3: Pixel shader compilation failed
at position -1:
[info ] IrrDriver: OpenGL version: 3.3
[info ] IrrDriver: OpenGL vendor: Intel Open Source Technology Center
[info ] IrrDriver: OpenGL renderer: Mesa DRI Intel(R) Sandybridge Mobile
[info ] IrrDriver: OpenGL version string: 3.3 (Core Profile) Mesa 13.0.6
I don't have any Xorg.conf.d lines now, although I've tried the intel and
modesetting driver, and both sna and uxa.
Oh, also if I use the LIBGL_SOFTWARE_ALWAYS=true environment variable the code
runs perfetly fine:
$ LIBGL_ALWAYS_SOFTWARE=true ./glthing
GL_VERSION: Gallium 0.4 on llvmpipe (LLVM 3.9, 256 bits)
GL_VERSION: 3.0 Mesa 13.0.6
GL_VERSION: VMware, Inc.
For the complexity of things that I'm rendering right now, software is perfectly
fine... it'd just be nice to have some idea of what's going on. Any chance
anyone could shed some light on this for me?
--
Daniel Keast
signature.asc
Description: PGP signature
Re: Debian 9 sucks really badly
On Saturday, March 24, 2018 2:01:13 PM -03 Chris Anderson wrote: > Hello > > I have been using different flavours of Linux since slackware 96 over 20 > years ago. Since then I have installed and used at least a dozen > different flavours. By far the most challenging was the X windows system > for slackware but I managed to get it installed and running with no > problems. > > Last week I bought a new PC and decided to try debian so I downloaded > the DVD version 9 and performed a fresh install besides windows 10. > Right from the off, it fucked up, Grubb was a hassle as this was the > default boot loader,(I have always used LILO), it would not find the > windows partition, I managed to fix this. Then it didn't give me a > choice of X windows manager, I was stuck with KDE, which I am familiar > with and am aware of its may limitations and given the choice I wouldn't > use KDE for installation and configuration. > > Nearly everything fucked up from the Network install to the gcc make > command, what a hassle and after spending nearly a week trying to get it > all working I've had enough and am not wasting any more of my time on > this awful software. > > So thanks for wasting my time Debian and for future reference, go and > get fucked!!! > > > Chris Anderson What you are telling us is: 1) You are able to eloquently express your dismay in writing 2) You are unwilling to either read menu items nor manuals nor release notes 3) You are expecting Debian install to have everything your way without contributing to Debian development 4) You don't ask for directions before walking down that lane nor asking for help being halfway down that lane 5) You never contributed anything to any mailinglist, not even slackware, under the e-mail address you used 6) You use words in writing that many would not touch with a pole 7) You show the traits of a toxic personality (whether you actually have one we don't know) verdict: Troll ZP6CGE QRZ
Re: domain names, was: hostname
Hi, Am 2018-03-24 hackte Miles Fidelman in die Tasten: > On 3/23/18 8:46 PM, David Wright wrote: >>> Not actually sure of that. Verizon stopped offering mail a while >>> ago (sent people to AOL), and then there are folks who have >>> university or work accounts. >> Verizon own AOL. >> > Right. Forgot about that. Hmmm, AOL? -- Does this mean All-Off-Line? ;-) > Miles Have a nice weekend -- Michelle KonzackMiila ITSystems @ TDnet GNU/Linux Developer 00372-54541400
Re: Debian 9 sucks really badly
Hi, > I guess its one of those brain fucked idiots Although I realy agree with you, I don't think your tone is by any means better, and you should instead lead by example and not insult anyone on a Debian mailing list even if you are angry. Cheers, Nik signature.asc Description: PGP signature
Re: domain names, was: hostname
On 3/23/18 8:46 PM, David Wright wrote: On Fri 23 Mar 2018 at 13:05:17 (-0400), Miles Fidelman wrote: On 3/23/18 1:01 PM, David Wright wrote: On Fri 23 Mar 2018 at 11:59:06 (-0400), Miles Fidelman wrote: At some point, the network name that one's PC inserts into outgoing mail might become important. I venture to suggest that many (most?) .home users will be using their ISP's smarthost, which would mean that the ISP (a) usually insist on authentication and (b) and likely to have issued the network name (like ip70-179-161-106.fv.ks.cox.net) themselves. Not actually sure of that. Verizon stopped offering mail a while ago (sent people to AOL), and then there are folks who have university or work accounts. Verizon own AOL. Right. Forgot about that. Miles -- In theory, there is no difference between theory and practice. In practice, there is. Yogi Berra
Re: Debian 9 sucks really badly
Dominik George wrote: > I think the main problem here is that the user considers himself too > much of an expert and stops seeing the easy things, like the step in the > installer asking explicitly for the desktop environment to install. It's > right there, but they are too l33t to simply open their eyes. I guess its one of those brain fucked idiots that thinks he knows everything better and does not understand why he should follow rules. After this he comes and complains. In the meanwhile such people never have time to read docs, because of course they know everything better and they do not listen to anyone for the same reason. But yeah they can scream regards
Re: Debian 9 sucks really badly
Chris Anderson wrote: > Nearly everything fucked up from the Network install to the gcc make > command, what a hassle and after spending nearly a week trying to get it > all working I've had enough and am not wasting any more of my time on > this awful software. > > So thanks for wasting my time Debian and for future reference, go and > get fucked!!! Don't blame others for your incompetence. It is your own problem - see there are hundreds of thousands or perhaps millions of people using Debian and you think it is problem with Debian - I think the problem is in your head. Even more being rude shows the missing parts of your education as if someone forced you to spend time with Debian - OMG what an IDIOT. I don't wonder anymore from alledged Russian connections of Trump, to alledged poisoning in Solsbery PLEASE shut down Facebook and Twitter and all the stupid and useless web pages and SAVE THE PLANET and HUMANITY! regards
Re: Debian 9 sucks really badly
On Sat, Mar 24, 2018 at 02:01:13PM +1030, Chris Anderson wrote: > Hello > > I have been using different flavours of Linux since slackware 96 over 20 > years ago. Since then I have installed and used at least a dozen different > flavours. By far the most challenging was the X windows system for slackware > but I managed to get it installed and running with no problems. > I am curious how if X for Slackware was by far the most challenging how you managed to get it installed and running with no problems. Even in distributions other than Slackware the configuration of X was challenging during the time period you referenced. > Last week I bought a new PC and decided to try debian so I downloaded the > DVD version 9 and performed a fresh install besides windows 10. Right from > the off, Did you read the installation manual [0] and release notes [1] first? Did you do any research to see if your hardware vendor supports Linux in general or Debian specifically? Did you do any research to see if anyone had reported successfully installing Debian on that hardware? Is it very new (e.g., new chipsets, video card, etc.) released in just the last few months? Debian Stretch was released nearly a year ago and so very new hardware may not be well supported. > Grubb was a hassle as this was the default boot > loader,(I have always used LILO), Debian has used grub as the default boot loader for many years now. I am curious what specific problem or defect you encountered here. Could you describe it in detail and perhaps provide the associated error messages? It would help with ensuring that there is a bug report regarding the problem or documentation of a workaround. > it would not find the windows partition, I > managed to fix this. How did you fix this? It would be helpful to others searching the list archives if you could describe the problem and how you solved it. > Then it didn't give me a choice of X windows manager, I > was stuck with KDE, which I am familiar with and am aware of its may > limitations and given the choice I wouldn't use KDE for installation and > configuration. > Again, did you read the installation manual? It clearly states installing from CD may not make all graphical environments available. Did you happen to download an installation CD with KDE as the default environment? I am not aware of there being such differentiation for the installation DVDs, so I would very much like to know where you downloaded the DVD that forced installation of KDE. > Nearly everything > from the Network install How did the network install fail? Is it that you used a netinstall image and that did not produce the expected result, or did you use a standard installer that failed to configure your machine's network hardware, or both? Did the installer prompt you to load missing firmware files? This also is documented in the installation manual. > to the gcc make > command, There is no "gcc make" command. The "make" and "gcc" commands are two separate things. Michelle already addressed how to get this working in another post. Though, I am very surprised that someone using Linux for over 20 years would not have previously encountered this and known about it. > what a hassle and after spending nearly a week trying to get it all > working I've had enough and am not wasting any more of my time on this awful > software. > I can certainly understand that if you spent your valuable time dealing with unexpected installation problems that you would be frustrated. If you experienced some difficulty and would like some assistance in resolving the issues you encountered, it would be more helpful and productive to provide information about the precise steps that you took, the precise error messages that you encountered, and the result that you expected. > So thanks for wasting my time Debian and for future reference, go and get > This is most definitely not constructive and is not the sort of language or behavior that will encourage most people to try to help out. That said, I have my doubts about your actual experience. It seems more like you specifically sought an excuse to rant, or that you plunged into an installation without noting that you had the incorrect installation media or without first reading the documentation. I hope that I am mistaken. If you would like assistance in resolving the issues you encountered, please provide the additional details requested. Regards, -Roberto [0] https://www.debian.org/releases/stretch/installmanual [1] https://www.debian.org/releases/stretch/releasenotes -- Roberto C. Sánchez
Re: Debian 9 sucks really badly
Chris Anderson wrote: > Hello ... sounds like these mistakes: - not using a netinst - not reading the installation guide so sorry... songbird
Re: Debian 9 sucks really badly
___ /| /| | | ||__|| | Please don't | / O O\__ feed | / \ the trolls| / \ \| / _\ \ -- /|\\ \ || / | | | |\/ || / \|_|_|/ |__|| / / \|| || / | | /|| --| | | |// | --| * _| |_|_|_| | \-/ *-- _--\ _ \ // | / _ \\ _ // |/ * / \_ /- | - | | * ___ c_c_c_C/ \C_c_c_c -- QOTD: "I'm on a seafood diet -- I see food and I eat it." Eduardo M KALINOWSKI edua...@kalinowski.com.br
Re: Debian 9 sucks really badly
> In the Free Software world, the response to something not > working is generally: > 1)If you know how, fix it and send the fix to the project so > it helps everyone, or, > 2)If you don't know how to fix it, report the problem in a > useful way, so someone else can fix it and help everyone. I think the main problem here is that the user considers himself too much of an expert and stops seeing the easy things, like the step in the installer asking explicitly for the desktop environment to install. It's right there, but they are too l33t to simply open their eyes. Sometimes I make that mistake myself, actually ;). -nik signature.asc Description: PGP signature
Re: Debian 9 sucks really badly
On 03/23/2018 11:31 PM, Chris Anderson wrote: Hello I have been using different flavours of Linux since slackware 96 over 20 years ago. Since then I have installed and used at least a dozen different flavours. By far the most challenging was the X windows system for slackware but I managed to get it installed and running with no problems. Hey, me too! Last week I bought a new PC and decided to try debian so I downloaded the DVD version 9 and performed a fresh install besides windows 10. Right from the off, it fucked up, Grubb was a hassle as this was the default boot loader,(I have always used LILO), it would not find the windows partition, I managed to fix this. Then it didn't give me a choice of X windows manager, I was stuck with KDE, which I am familiar with and am aware of its may limitations and given the choice I wouldn't use KDE for installation and configuration. Nearly everything fucked up from the Network install to the gcc make command, what a hassle and after spending nearly a week trying to get it all working I've had enough and am not wasting any more of my time on this awful software. So thanks for wasting my time Debian and for future reference, go and get fucked!!! Constructive. I have issues with Debian, but screaming anger fits generally speaking haven't helped me fix them. I've tried things I don't like more than once in my life, and I've rarely found that screaming anger fits helped. In the Free Software world, the response to something not working is generally: 1)If you know how, fix it and send the fix to the project so it helps everyone, or, 2)If you don't know how to fix it, report the problem in a useful way, so someone else can fix it and help everyone. -- Carl Fink
Re: Debian 9 sucks really badly
On 2018-03-24 03:31, Chris Anderson wrote: Hello I have been using different flavours of Linux since slackware 96 over 20 years ago. Since then I have installed and used at least a dozen different flavours. By far the most challenging was the X windows system for slackware but I managed to get it installed and running with no problems. Yah! Slackware that was my introduction to Linux when it was on like 40 floppies, if you managed that Debian should be a doddle. So thanks for wasting my time Debian and for future reference, go and get fucked!!! LOL mick -- Key ID 4BFEBB31
