I have installed Debian Etch on a gigabyte motherboard GA-MA74GM-S2, having AMD 740G + SB700 Chipset. The website says it has ATI Radeon 2100 integrated graphics.
Output of lspci is as follows: 01:05.0 VGA compatible controller: ATI Technologies Inc Unknown device 796e
This driver selected for this is "vesa". If I try "ati", X server refuses to start.
But the main problem is resolution - it is set at 1280x1024. I tried using "dpkg-reconfigure xserver-xorg" and setting resolution to 1440X900, but at that, the resolution was set to 1400x1050 when X server was restarted.
Even adding the resolution manually to the Modes lines in xorg.conf and restarting X server did not solve the issue.
How can I fix this?
Thanks. -- Rohit V. Bhute
A few more points:
1. Some posts on a Debian support forum suggested adding a Modeline parameter to the Monitor section as my monitor is wide-screen, hence not standard. I added this using an online generator, but did not work.
2. The command xvidtune was suggested to get the modeline. This command returned an error message - "video modes cannot be tuned for this chip". I can't remember the exact message as I am not at home, so can't check it again.
3. Is this because I'm using vesa driver? Using the ati driver causes the X to stop starting and it asks me to fix the xorg.conf file. The error is (approximate again) - "No screens found".
Regards
On Monday 15 December 2008 09:58, rohit bhute wrote:
- Is this because I'm using vesa driver?
Vesa is the lowest level driver. It is generic and supported by all cards. However most of the advanced stuff wont work, including higher resolutions, or resolutions which are not 4:3 9 (afaik).
Using the ati driver causes the X to stop starting and it asks me to fix the xorg.conf file. The error is (approximate again) - "No screens found".
Check for the latest ati drivers at AMD. ATI was taken over by AMD.
On Mon, Dec 15, 2008 at 12:47 PM, jtd jtd@mtnl.net.in wrote:
Check for the latest ati drivers at AMD. ATI was taken over by AMD.
Checked here - http://ati.amd.com/support/driver.html - ATI Radeon 2100 is not to be found! But if you see this link[1], you will find clear mention of the graphics card that is on-board.
1. http://www.amd.com/us-en/0,,3715_14603_15646,00.html
Regards
rohit bhute wrote:
On Mon, Dec 15, 2008 at 12:47 PM, jtd jtd@mtnl.net.in wrote:
Check for the latest ati drivers at AMD. ATI was taken over by AMD.
Checked here - http://ati.amd.com/support/driver.html - ATI Radeon 2100 is not to be found! But if you see this link[1], you will find clear mention of the graphics card that is on-board.
See if this helps in any way.
http://en.kioskea.net/telecharger/telecharger-850-driver-ati-radeon-catalyst...
I gave up and went back to Ubuntu 8.10. The graphics were correctly detected. This seems just to be a case of latest drivers being available in Ubuntu.
Regards.
On Tue, Dec 16, 2008 at 10:59 PM, rohit bhute rvbhute@gmail.com wrote:
I gave up and went back to Ubuntu 8.10. The graphics were correctly detected. This seems just to be a case of latest drivers being available in Ubuntu.
Dont you dare complain. Did you take the time to actually understand what Debian Etch is all about? Let me ask you this question, what the hell were you thinking when you wrote that message in the LUG? First go and find out who is Debian Etch's target audience then write such preposterous emails asking for help.
On Wednesday 17 December 2008 09:59, Dinesh Joshi wrote:
On Tue, Dec 16, 2008 at 10:59 PM, rohit bhute rvbhute@gmail.com
wrote:
I gave up and went back to Ubuntu 8.10. The graphics were correctly detected. This seems just to be a case of latest drivers being available in Ubuntu.
Dont you dare complain. Did you take the time to actually understand what Debian Etch is all about? Let me ask you this question, what the hell were you thinking when you wrote that message in the LUG? First go and find out who is Debian Etch's target audience then write such preposterous emails asking for help.
!!!!!!!!!!!!!!!??????????????????? Did you perchance forget to add a few shoes and some choice @#!*?
Dinesh Joshi wrote:
Dont you dare complain. Did you take the time to actually understand what Debian Etch is all about? Let me ask you this question, what the hell were you thinking when you wrote that message in the LUG? First go and find out who is Debian Etch's target audience then write such preposterous emails asking for help.
I admit that I have kept only a casual watch on "Debian" over the last three years when I was using Ubuntu - what it is, its track records regarding stability and security, its target audience - may be it is nothing near the level what you know.
I installed Debian for a reason - Bluetooth is broken in Intrepid. Yes, I have "done my homework" and no, the answers are *not* "readily available on the internet". I have posted on the official forum and launched a bug report with all the logs requested. Only after that, did I decide to switch to Debian. Here I came to this screen resolution problem.
In the end, I had to choose the lesser of the two evils - screen or bluetooth. I just posted a follow-up that my problem was solved, for the time being.
As for the other mail which also you soundly booted, yes I'm aware that I should "do my homework" and that there are utilities which help me to do that. But I handle maybe 2 drives in 4 years while there are people here who handle ten or more daily. So I thought to tap into their experience.
If you think that I am complaining, being ungrateful or parasitic, I apologize on this LUG itself. In the future I will try to live up to the LUG standards.
Regards. -- Rohit V. Bhute
On Wednesday 17 Dec 2008, Rohit V Bhute wrote:
[snip] If you think that I am complaining, being ungrateful or parasitic, I apologize on this LUG itself. In the future I will try to live up to the LUG standards.
Speaking for myself, I didn't see any problems with what you mailed and the questions you asked -- they all seemed perfectly legitimate for this mailing list.
As for your screen resolution issue, I'd be glad to try and help if you're inclined towards switching back to Debian, as would numerous others, I'm sure.
Regards,
-- Raju
Raj Mathur wrote:
As for your screen resolution issue, I'd be glad to try and help if you're inclined towards switching back to Debian, as would numerous others, I'm sure.
Of course I'm going to try again. But as you probably know from my other thread, my machine is in the shop for a new drive. I am going to dual boot with Debian Lenny this time and get it going (and I will do my work before asking here :-) ); then make it the main OS on the machine.
As it is, all the data on my machine is on a external drive now, so switching OSes wouldn't cause much pain.
Regards. -- Rohit V. Bhute
On Wed, Dec 17, 2008 at 10:19 PM, Rohit V Bhute rvbhute@gmail.com wrote:
boot with Debian Lenny this time and get it going (and I will do my work before asking here :-) ); then make it the main OS on the machine.
Do you just have the habit of *not* thinking before you type? Lenny is frozen ( though it has a bunch of unfixed bugs ) so its nowhere near as bleeding edge as Ubuntu Intrepid Ibex. Even Sid is not as bleeding edge...
Rohit, Lets summarize what you said, you were an Ubuntu user. Your bluetooth didn't work so you thought, oh well, lets switch to debian because it'll solve all your issues. You claim you did your homework. I say you didn't. You wanna know why I say that? Its simply because you went ahead and installed Debian *Etch* or the more proper name would be Debian STABLE.
Now had you done your "homework" you would know Debian STABLE is NOT MEANT FOR END USERS WITH SHINY NEW MACHINES. Heck its not even meant for machines from 2 years ago. Did you even care to check what kernel version it was running? I'm sure it must be running 2.6.18 because thats what STABLE branch ( Etch ) is running.
Did you care to check what version of kernel was Ubuntu Intrepid Ibex was running? NO you DIDNT. Its running 2.6.27.
Now lets check out what version of X server Ubuntu Intrepid Ibex is running and compare it with Debian Etch's X server. I dont have the numbers off the top of my head but I'm pretty sure that Etch is still running Xfree86 while Ubuntu Intrepid is running Xorg's most bleeding edge branch.
Now in the light of all these facts lets review:
1. You claim you did your homework. 2. Facts show that you didn't.
There are only 2 valid conclusions:
1. Either you did your homework and your purposefully posted such a post complaining that Debian Etch doesn't support your screen resolution.
2. You didn't do your homework and whined about your screen resolution.
Take your pick Mr.Bhute. Which one will it be? In both cases you're tarnishing the well earned reputation of a distro such as Debian. Had you done your "homework" you would've atleast thought of installing Lenny or Sid rather than fooling around with Etch. Thats the reason I called your claims PREPOSTEROUS.
And to shed some more light on your issues, Debian Testing or Unstable is _not_ going to solve any of your issues. Ubuntu is by far more bleeding edge than Debian in all respects. You should try Fedora or some other distro to resolve your issue. If bluetooth is so important then might as well install a VM and some previous version of Ubuntu ( 8.04 maybe? ) in which bluetooth is functioning fine and then use it.
do that. But I handle maybe 2 drives in 4 years while there are people
Now lets come to this little piece of post that you made. Mr.Bhute I'd like to inform you that if you had done your homework on even this particular topic you would've known that SATA controllers aren't that well supported as are IDE controllers. Power management support for SATA a dicey topic. Hence you would've perhaps thought of investigating it further and posted some REAL question rather than posting something like "ooh...does Linux do this?".
If you think that I am complaining, being ungrateful or parasitic, I apologize on this LUG itself. In the future I will try to live up to the LUG standards.
Thanks to your post which has now gotten archived, Linux's reputation as an operating system has reduced a little. People all over the globe dont know what they're doing and often blame the software for their incompetency. I have nothing personal against you. I was probably in your position and I have NOT forgotten that. But atleast I made attempts at understanding what I did wrong before I went around blatantly blaming the software I was using. Such irresponsible behavior is NOT expected of a Linux supporter.
If you would step into #debian on freenode with such a question I'd see you being kicked and banned in a blink of an eye.
Maybe I'm the one who sees such posts as threat to Linux's desktop reputation. But I certainly will not stand by while some n00b tries to install the WRONG VERSION of Linux and then blame it on the distro. That is wrong on all levels.
On Thu, Dec 18 2008, Dinesh Joshi wrote:
And to shed some more light on your issues, Debian Testing or Unstable is _not_ going to solve any of your issues. Ubuntu is by far more bleeding edge than Debian in all respects.
Hmm? Since Ubuntu snapshots Debian unstable at some pointm and then proceeds to fall behind until release and the next sync, I don't think this is entirely accurate.
manoj
On Fri, Dec 19, 2008 at 7:36 PM, Manoj Srivastava srivasta@debian.org wrote:
Hmm? Since Ubuntu snapshots Debian unstable at some pointm and
then proceeds to fall behind until release and the next sync, I don't think this is entirely accurate.
Wrong! :) I'm running Debian Unstable and there are plenty of differences in the versions being used by Ubuntu Intrepid Ibex. Not to mention I've updated it frequently. Infact to get some "features" of Ubuntu, I needed to pull some packages from Debian's Experimental.
Fact for you, Ubuntu had 2.6.27 kernel since ages. I think since Ibex was alpha. But Debian Unstable still doesn't have it.
2008/12/19 Dinesh Joshi dinesh.a.joshi@gmail.com:
Fact for you, Ubuntu had 2.6.27 kernel since ages. I think since Ibex was alpha. But Debian Unstable still doesn't have it.
Dude, you don't get it :-) Debian testing is frozen and only packages that *normally* go to unstable are those which are expected to be released with lenny. You won't get any newer kernels in unstable before lenny is out of the door.
- Praveen
On Sat, Dec 20, 2008 at 1:17 AM, Praveen A pravi.a@gmail.com wrote:
Dude, you don't get it :-) Debian testing is frozen and only packages that *normally* go to unstable are those which are expected to be released with lenny. You won't get any newer kernels in unstable before lenny is out of the door.
You are explaining it to the wrong person. Please explain that to the people who say Ubuntu = Debian Unstable.
On Sat, Dec 20, 2008 at 12:12 PM, Dinesh Joshi dinesh.a.joshi@gmail.com wrote:
You are explaining it to the wrong person. Please explain that to the people who say Ubuntu = Debian Unstable.
In fact this is true: Ubuntu = Debian Unstable + Experimental and broken packages + More bugs
My 50p to this equation ;)
2008/12/19 Dinesh Joshi dinesh.a.joshi@gmail.com:
On Sat, Dec 20, 2008 at 1:17 AM, Praveen A pravi.a@gmail.com wrote:
Dude, you don't get it :-) Debian testing is frozen and only packages that *normally* go to unstable are those which are expected to be released with lenny. You won't get any newer kernels in unstable before lenny is out of the door.
You are explaining it to the wrong person. Please explain that to the people who say Ubuntu = Debian Unstable.
No. I was explaining to the right person, who did not do proper homework to understand why debian unstable did not have 2.6.27 kernel.
Ubnuntu = Debian Unstable - recompiled is true for majority (I believe it is close to 100%) for the universe component.
Ubuntu focus on about 1000 core components which includes linux, the kernel to maintain on its own and the rest depend on Debian.
"In universe you can find almost every piece of open source software, and software available under a variety of less open licences, all built automatically from a variety of public sources."
http://www.ubuntu.com/community/ubuntustory/components
And the major public source here is debian unstable repository which they fail to acknowledge.
- Praveen
On Sat, Dec 20, 2008 at 2:40 AM, Praveen A pravi.a@gmail.com wrote:
No. I was explaining to the right person, who did not do proper homework to understand why debian unstable did not have 2.6.27 kernel.
So what you're saying is basically the SAME that I've said. Debian is BEHIND Ubuntu in terms of including the most bleeding edged software. SO theres a good chance that Ubuntu will support your hardware out of the box and Debian wont. HENCE, Etch is a stupid choice for someone to install because his hardware isn't supported because Etch is ANCIENT.
Another end user example of how Debian is lagging behind Ubuntu and hence my point stands, Debian Sid installs gnome 2.22.3 while gnome-panel is stuck at 2.20.?? in the unstable repository. So, to get the shiny new "world clock" in the gnome-panel one has to dig through the experimental repository. This "feature" was available in Ubuntu around 8.04 or even before that.
2008/12/20 Dinesh Joshi dinesh.a.joshi@gmail.com:
So what you're saying is basically the SAME that I've said. Debian is BEHIND Ubuntu in terms of including the most bleeding edged software. SO theres a good chance that Ubuntu will support your hardware out of the box and Debian wont. HENCE, Etch is a stupid choice for someone to install because his hardware isn't supported because Etch is ANCIENT.
You have no clue how debian release process works or how software comes to unstable. So before starting bashing someone, I hope you will do some reading.
When the testing is frozen only those packages which is expected to be released with the next stable release are added to unstable. If you cannot include a new version you can add it to experimental.
The case of testing freeze is an exception to how normally unstable works.
Another end user example of how Debian is lagging behind Ubuntu and hence my point stands, Debian Sid installs gnome 2.22.3 while gnome-panel is stuck at 2.20.?? in the unstable repository. So, to get the shiny new "world clock" in the gnome-panel one has to dig through the experimental repository. This "feature" was available in Ubuntu around 8.04 or even before that.
You can continue to stick with your point, but I suggest you read about debian release process and what testing freeze means to packages in unstable. It is OK to be ignorant, but if some one go around shouting blunders, then the issue becomes different.
The reason why you don't see new packages in sid right now is because it lenny is frozen.
"A new version may only contain changes falling in one of the following categories (compared to the version in testing): - fixes for release critical bugs (i.e., bugs of severity critical, grave, and serious) in all packages; - changes for release goals, if they are not invasive; - fixes for severity: important bugs in packages of priority: optional or extra, only when this can be done via unstable; - translation updates - documentation fixes " http://release.debian.org/emails/release-update-200808
And when the stable release is out there is not such restrictions and packages hit sid even just after hours of the upstream release. If you had done some background reading than screaming 2.6.27 is not available in sid and hence sid must be older than ubuntu should not have happened.
Nobody is perfect dude. Please learn to respect others. I had to change my tone because you kept on ridiculing a new debian user.
- Praveen
On Sat, Dec 20, 2008 at 11:34 PM, Praveen A pravi.a@gmail.com wrote:
*snip*
The reason why you don't see new packages in sid right now is because it lenny is frozen.
*snip*
had done some background reading than screaming 2.6.27 is not available in sid and hence sid must be older than ubuntu should not have happened.
Uh...I dont give a damn how or why a certain package is in Ubuntu and isn't in Debian <Stick your favorite version here>. My points were based on facts. The facts stand. End of story. Can you contradict those facts and tell me otherwise? NO.
I never claimed to be the all knowing Oracle. Quite frankly we weren't even talking about the Debian release process or the Ubuntu release process. My facts are crystal clear:
1. Debian Etch has an older kernel, older packages hence compatibility with new hardware is limited. ( Someone pointed out that it worked well on new hardware, to which I replied with a FACTUAL example ). 2. Ubuntu contains far more bleeding edge packages hence its better on the driver front.
OP's thought that he would solve his problem by replacing Ubuntu Intrepid Ibex with Debian Etch is dumb because had he known in advance, he would've installed Sid or Lenny and then used the experimental repository. But he didnt which shows that he didn't care to go through the documentation of Debian to understand whether installing Debian would actually solve his problems...
And one more FACT for you, the Ubuntu kernel has several patches applied to it which aren't there in the Debian kernel. Hence comparing a Debian 2.6.18 kernel to Ubuntu 2.6.27 kernel is nonsensical.
change my tone because you kept on ridiculing a new debian user.
I never ridiculed the OP. I was OUTRAGED by the fact that a new user would be so irresponsible to go back 9 kernel releases and run older packages and complain that his system didn't support his shiny new display. My dear friend THAT is ridiculous.
2008/12/21 Dinesh Joshi dinesh.a.joshi@gmail.com:
I never ridiculed the OP. I was OUTRAGED by the fact that a new user would be so irresponsible to go back 9 kernel releases and run older packages and complain that his system didn't support his shiny new display. My dear friend THAT is ridiculous.
What is ridiculous is your language and tone. There are polite ways to express your views.
Anurag
On Sun, Dec 21, 2008 at 1:35 PM, Anurag anurag@gnuer.org wrote:
What is ridiculous is your language and tone. There are polite ways to express your views.
Seems politeness is not in these days. Extremists are getting all the attention. Especially on this list ;)
On Sun, Dec 21, 2008 at 11:24 PM, Dinesh Joshi dinesh.a.joshi@gmail.com wrote:
I never ridiculed the OP. I was OUTRAGED by the fact that a new user would be so irresponsible to go back 9 kernel releases and run older packages and complain that his system didn't support his shiny new display. My dear friend THAT is ridiculous.
I will be not Outraged when New User(s) in my office called me everytime when their so called bleeding edge panel hanged 10 times in a day and lone Debian users smiles to them.
Good Night!
On Mon, Dec 22, 2008 at 1:46 PM, Kartik Mistry kartik.mistry@gmail.com wrote:
I will be not Outraged when New User(s) in my office called me everytime when their so called bleeding edge panel hanged 10 times in a day and lone Debian users smiles to them.
I'm just going to blow past this alright... You're waay off here. This has *nothing* to do with what is / was being discussed here.
On Tue, Dec 23, 2008 at 11:04 AM, Dinesh Joshi dinesh.a.joshi@gmail.com wrote:
I'm just going to blow past this alright... You're waay off here. This has *nothing* to do with what is / was being discussed here.
Thanks for understanding, finally!
Rohit, Lets summarize what you said, you were an Ubuntu user. Your bluetooth didn't work so you thought, oh well, lets switch to debian because it'll solve all your issues. You claim you did your homework. I say you didn't. You wanna know why I say that? Its simply because you went ahead and installed Debian *Etch* or the more proper name would be Debian STABLE.
Now had you done your "homework" you would know Debian STABLE is NOT MEANT FOR END USERS WITH SHINY NEW MACHINES. Heck its not even meant for machines from 2 years ago. Did you even care to check what kernel version it was running? I'm sure it must be running 2.6.18 because thats what STABLE branch ( Etch ) is running.
Did you care to check what version of kernel was Ubuntu Intrepid Ibex was running? NO you DIDNT. Its running 2.6.27.
Now lets check out what version of X server Ubuntu Intrepid Ibex is running and compare it with Debian Etch's X server. I dont have the numbers off the top of my head but I'm pretty sure that Etch is still running Xfree86 while Ubuntu Intrepid is running Xorg's most bleeding edge branch.
Now in the light of all these facts lets review:
1. You claim you did your homework. 2. Facts show that you didn't.
There are only 2 valid conclusions:
1. Either you did your homework and your purposefully posted such a post complaining that Debian Etch doesn't support your screen resolution.
2. You didn't do your homework and whined about your screen resolution.
Take your pick Mr.Bhute. Which one will it be? In both cases you're tarnishing the well earned reputation of a distro such as Debian. Had you done your "homework" you would've atleast thought of installing Lenny or Sid rather than fooling around with Etch. Thats the reason I called your claims PREPOSTEROUS.
And to shed some more light on your issues, Debian Testing or Unstable is _not_ going to solve any of your issues. Ubuntu is by far more bleeding edge than Debian in all respects. You should try Fedora or some other distro to resolve your issue. If bluetooth is so important then might as well install a VM and some previous version of Ubuntu ( 8.04 maybe? ) in which bluetooth is functioning fine and then use it.
do that. But I handle maybe 2 drives in 4 years while there are people
Now lets come to this little piece of post that you made. Mr.Bhute I'd like to inform you that if you had done your homework on even this particular topic you would've known that SATA controllers aren't that well supported as are IDE controllers. Power management support for SATA a dicey topic. Hence you would've perhaps thought of investigating it further and posted some REAL question rather than posting something like "ooh...does Linux do this?".
If you think that I am complaining, being ungrateful or parasitic, I apologize on this LUG itself. In the future I will try to live up to the LUG standards.
Thanks to your post which has now gotten archived, Linux's reputation as an operating system has reduced a little. People all over the globe dont know what they're doing and often blame the software for their incompetency. I have nothing personal against you. I was probably in your position and I have NOT forgotten that. But atleast I made attempts at understanding what I did wrong before I went around blatantly blaming the software I was using. Such irresponsible behavior is NOT expected of a Linux supporter.
If you would step into #debian on freenode with such a question I'd see you being kicked and banned in a blink of an eye.
Maybe I'm the one who sees such posts as threat to Linux's desktop reputation. But I certainly will not stand by while some n00b tries to install the WRONG VERSION of Linux and then blame it on the distro. That is wrong on all levels.
-- Regards, Dinesh A. Joshi
On Thursday 18 Dec 2008, Dinesh Joshi wrote:
[snip] Take your pick Mr.Bhute. Which one will it be? In both cases you're tarnishing the well earned reputation of a distro such as Debian.
IMNSHO your posts are doing more to tarnish Debian's reputation than an infinite number of Rohits typing on an infinite number of computers for an infinite duration of time could. I doubt if anyone will want to post further Debian queries on this list, fearing a baseless, vitriolic ad hominem attack in response to their innocent questions.
Chill, dude.
Regards,
-- Raju
On Thu, Dec 18, 2008 at 10:52 PM, Dinesh Joshi dinesh.a.joshi@gmail.com wrote:
Now lets check out what version of X server Ubuntu Intrepid Ibex is running and compare it with Debian Etch's X server. I dont have the numbers off the top of my head but I'm pretty sure that Etch is still running Xfree86 while Ubuntu Intrepid is running Xorg's most bleeding edge branch.
Debian Etch runs Xorg.
Take your pick Mr.Bhute. Which one will it be? In both cases you're tarnishing the well earned reputation of a distro such as Debian. Had you done your "homework" you would've atleast thought of installing Lenny or Sid rather than fooling around with Etch. Thats the reason I called your claims PREPOSTEROUS.
And to shed some more light on your issues, Debian Testing or Unstable is _not_ going to solve any of your issues. Ubuntu is by far more bleeding edge than Debian in all respects. You should try Fedora or some other distro to resolve your issue. If bluetooth is so important
I have used Debian without any issues for any new hardware. May be you don't link Debian
do that. But I handle maybe 2 drives in 4 years while there are people
Maybe I'm the one who sees such posts as threat to Linux's desktop reputation. But I certainly will not stand by while some n00b tries to install the WRONG VERSION of Linux and then blame it on the distro. That is wrong on all levels.
Well, people completely new to the Linux world may not be aware of wrong or right versions. It is this forum's responsibility to help beginners. Or if you can point out some forums where the most dumb questions can be asked, that would help newbies. I fell that these harsh replies can be avoided.
On Fri, Dec 19, 2008 at 10:15 AM, Balachandran Sivakumar benignbala@gmail.com wrote:
May be you don't link Debian
May be he don't like Debian!
Hi,
On Fri, Dec 19, 2008 at 11:43 AM, Kartik Mistry kartik.mistry@gmail.com wrote:
On Fri, Dec 19, 2008 at 10:15 AM, Balachandran Sivakumar benignbala@gmail.com wrote:
May be you don't link Debian
May be he don't like Debian!
Yeah. Sorry. Typo.
On Thu, Dec 18, 2008 at 11:45 PM, Balachandran Sivakumar benignbala@gmail.com wrote:
I have used Debian without any issues for any new hardware.
May be you don't link Debian
Oh really? Can you give me some facts? I'll throw a fact at you. Try installing Etch on a C2D machine running Intel's DG965RY motherboard. Then you contradict me. This is not a one off incident. The FACT is Etch's kernel doesn't have a driver which is essential for the IDE controller. Its some JMicron controller.
Next time you better get your facts straight before shooting off a reply. I'm not here to have a childish "i'm right, no i'm right" debate. I've presented FACTS which are backed up by numbers.
On Sat, Dec 20, 2008 at 8:53 AM, Dinesh Joshi dinesh.a.joshi@gmail.com wrote:
On Thu, Dec 18, 2008 at 11:45 PM, Balachandran Sivakumar benignbala@gmail.com wrote:
I have used Debian without any issues for any new hardware.
May be you don't link Debian
Oh really? Can you give me some facts? I'll throw a fact at you. Try installing Etch on a C2D machine running Intel's DG965RY motherboard. Then you contradict me. This is not a one off incident. The FACT is Etch's kernel doesn't have a driver which is essential for the IDE controller. Its some JMicron controller.
Next time you better get your facts straight before shooting off a reply. I'm not here to have a childish "i'm right, no i'm right" debate. I've presented FACTS which are backed up by numbers.
If you could read my mail fully, I just said I didn't have any issues with Debian for any of my my new hardware. Did I anywhere mention that Debian supports everything under the sun. It didn't support your stuff, I agree. but just the same way that is a fact, my statement that it supported my hardware is a fact. I can't take it back just because you want me to.
For some facts, It has supported my modem, digital camera, mobile phone out-of-box. Thank you.
On Mon, Dec 22, 2008 at 1:41 AM, Balachandran Sivakumar benignbala@gmail.com wrote:
If you could read my mail fully, I just said I didn't have any
issues with Debian for any of my my new hardware. Did I anywhere mention that Debian supports everything under the sun. It didn't support your stuff, I agree. but just the same way that is a fact, my statement that it supported my hardware is a fact. I can't take it back just because you want me to.
For some facts, It has supported my modem, digital camera,
mobile phone out-of-box. Thank you.
Were we talking about your particular hardware? No. So whats your point buddy? Debian supports a lot of hardware. Etch supports a lot of hardware - pre-2005 maybe. I did not refute any of that. If you can't see a simple point - A more advanced kernel supports more hardware, a older kernel supports lesser - then you should go back and read MY post clearly.
2008/12/22 Dinesh Joshi dinesh.a.joshi@gmail.com:
Were we talking about your particular hardware? No. So whats your point buddy? Debian supports a lot of hardware. Etch supports a lot of hardware - pre-2005 maybe. I did not refute any of that. If you can't see a simple point - A more advanced kernel supports more hardware, a older kernel supports lesser - then you should go back and read MY post clearly.
Yes, "The rabbit you caught have three horns".
On Wed, Dec 17, 2008 at 9:59 AM, Dinesh Joshi dinesh.a.joshi@gmail.com wrote:
Dont you dare complain. Did you take the time to actually understand what Debian Etch is all about? Let me ask you this question, what the hell were you thinking when you wrote that message in the LUG? First go and find out who is Debian Etch's target audience then write such preposterous emails asking for help.
There is nothing wrong in Rohit's email.