[opensuse] openSUSE 11.3 doesn't boot up after ram change
Can't find the reason why openSUSE 11.3 (32 bits) doesn't boot up when I change my laptop's ram cards. I changed 2gb 667Mhz (1gb x2) for 4gb 800Mhz (2gb x2). BIOS recognize the 4gb, GRUB comes up and then the black screen stops the load. The weird thing is that the system seems to be working behind but the screen doesn't display anything. I tested the ram running a live CD (100% ram). It works just fine. Someone told me that a re-installation should work but I want to be sure if this is related to an OS or motherboard issue. Thanks in advance. -- Hernán Thiers García Estudiante de Ingeniería en Informática / I.T. Engineering Student Home +56 - 45 - 287366 Mobile +56 - 9 - 3779421 Skype: +56 258 13910 # 565 / internaldrums Twitter: Hernan_CL Blog: http://hernanthiers.blogspot.com Temuco, Chile -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
El 26/10/10 10:20, Hernan Thiers escribió:
Can't find the reason why openSUSE 11.3 (32 bits) doesn't boot up when I change my laptop's ram cards. I changed 2gb 667Mhz (1gb x2) for 4gb 800Mhz (2gb x2). BIOS recognize the 4gb, GRUB comes up and then the black screen stops the load. The weird thing is that the system seems to be working behind but the screen doesn't display anything.
Did you tried booting in "safe mode" ? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
El 26/10/10 10:24, Cristian Rodríguez escribió:
El 26/10/10 10:20, Hernan Thiers escribió:
Can't find the reason why openSUSE 11.3 (32 bits) doesn't boot up when I change my laptop's ram cards. I changed 2gb 667Mhz (1gb x2) for 4gb 800Mhz (2gb x2). BIOS recognize the 4gb, GRUB comes up and then the black screen stops the load. The weird thing is that the system seems to be working behind but the screen doesn't display anything.
Did you tried booting in "safe mode" ?
Doesn't work neither. -- Hernán Thiers García Estudiante de Ingeniería en Informática / I.T. Engineering Student Home +56 - 45 - 287366 Mobile +56 - 9 - 3779421 Skype: +56 258 13910 # 565 / internaldrums Twitter: Hernan_CL Blog: http://hernanthiers.blogspot.com Temuco, Chile -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hernan Thiers wrote:
Can't find the reason why openSUSE 11.3 (32 bits) doesn't boot up when I change my laptop's ram cards. I changed 2gb 667Mhz (1gb x2) for 4gb 800Mhz (2gb x2). BIOS recognize the 4gb, GRUB comes up and then the black screen stops the load. The weird thing is that the system seems to be working behind but the screen doesn't display anything.
When you say the black screen stops the load, do you mean that you see the grub menu and choose a system to boot and then it goes black? If so, have you tried running memtest from the grub menu? If not, can you explain at exactly what point it does go black? Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
El 26/10/10 10:36, Dave Howorth escribió:
Hernan Thiers wrote:
Can't find the reason why openSUSE 11.3 (32 bits) doesn't boot up when I change my laptop's ram cards. I changed 2gb 667Mhz (1gb x2) for 4gb 800Mhz (2gb x2). BIOS recognize the 4gb, GRUB comes up and then the black screen stops the load. The weird thing is that the system seems to be working behind but the screen doesn't display anything.
When you say the black screen stops the load, do you mean that you see the grub menu and choose a system to boot and then it goes black?
If so, have you tried running memtest from the grub menu?
If not, can you explain at exactly what point it does go black?
Cheers, Dave
That's right. I choose normal or fail safe openSUSE option and just after those white lines (some selected system info) video goes black. There's no boot splash. I can't even get the verbose mode. By the way how can I try the memtest? Grub only offers the normal and fail safe modes. -- Hernán Thiers García Estudiante de Ingeniería en Informática / I.T. Engineering Student Home +56 - 45 - 287366 Mobile +56 - 9 - 3779421 Skype: +56 258 13910 # 565 / internaldrums Twitter: Hernan_CL Blog: http://hernanthiers.blogspot.com Temuco, Chile -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
* Hernan Thiers
By the way how can I try the memtest? Grub only offers the normal and fail safe modes.
try from a live cd since your grub menu does not offer. -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 26/10/10 15:53, Hernan Thiers wrote:
By the way how can I try the memtest? Grub only offers the normal and fail safe modes.
Memtest is available on the ISO installation image. Get it from the OpenSuSE website, burn it to a DVD and boot off that. When you reach the Grub menu, below "Boot from hard disk" and "Install", you will get more options, one of them being "Memtest". HTH Ph. A. -- *Philippe Andersson* Unix System Administrator IBA Particle Therapy | Tel: +32-10-475.983 Fax: +32-10-487.707 eMail: pan@iba-group.com http://www.iba-worldwide.com
On 10/26/2010 09:53 AM, Hernan Thiers wrote:
El 26/10/10 10:36, Dave Howorth escribió:
Hernan Thiers wrote:
Can't find the reason why openSUSE 11.3 (32 bits) doesn't boot up when I change my laptop's ram cards. I changed 2gb 667Mhz (1gb x2) for 4gb 800Mhz (2gb x2). BIOS recognize the 4gb, GRUB comes up and then the black screen stops the load. The weird thing is that the system seems to be working behind but the screen doesn't display anything.
When you say the black screen stops the load, do you mean that you see the grub menu and choose a system to boot and then it goes black?
If so, have you tried running memtest from the grub menu?
If not, can you explain at exactly what point it does go black?
Cheers, Dave
That's right. I choose normal or fail safe openSUSE option and just after those white lines (some selected system info) video goes black. There's no boot splash. I can't even get the verbose mode.
By the way how can I try the memtest? Grub only offers the normal and fail safe modes.
memtest should be an option on the live CD -- Michael S. Dunsavage -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 26 Oct 2010 14:53:22 Hernan Thiers wrote:
El 26/10/10 10:36, Dave Howorth escribió:
Hernan Thiers wrote:
Can't find the reason why openSUSE 11.3 (32 bits) doesn't boot up when I change my laptop's ram cards. I changed 2gb 667Mhz (1gb x2) for 4gb 800Mhz (2gb x2). BIOS recognize the 4gb, GRUB comes up and then the black screen stops the load. The weird thing is that the system seems to be working behind but the screen doesn't display anything.
When you say the black screen stops the load, do you mean that you see the grub menu and choose a system to boot and then it goes black?
If so, have you tried running memtest from the grub menu?
If not, can you explain at exactly what point it does go black?
Cheers, Dave
That's right. I choose normal or fail safe openSUSE option and just after those white lines (some selected system info) video goes black. There's no boot splash. I can't even get the verbose mode.
By the way how can I try the memtest? Grub only offers the normal and fail safe modes.
Have you checked your video memory settings if you are using shared mem as most laptops seem to then maybe it got messed up during the ram change .. Pete . -- Powered by openSUSE 11.3 (x86_64) Kernel: 2.6.34.7-0.4-desktop KDE Development Platform: 4.4.4 (KDE 4.4.4) "release 3" 18:52 up 17:51, 4 users, load average: 0.12, 0.14, 0.18 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
El 26/10/10 14:53, Peter Nikolic escribió:
On Tuesday 26 Oct 2010 14:53:22 Hernan Thiers wrote:
El 26/10/10 10:36, Dave Howorth escribió:
Hernan Thiers wrote:
Can't find the reason why openSUSE 11.3 (32 bits) doesn't boot up when I change my laptop's ram cards. I changed 2gb 667Mhz (1gb x2) for 4gb 800Mhz (2gb x2). BIOS recognize the 4gb, GRUB comes up and then the black screen stops the load. The weird thing is that the system seems to be working behind but the screen doesn't display anything.
When you say the black screen stops the load, do you mean that you see the grub menu and choose a system to boot and then it goes black?
If so, have you tried running memtest from the grub menu?
If not, can you explain at exactly what point it does go black?
Cheers, Dave
That's right. I choose normal or fail safe openSUSE option and just after those white lines (some selected system info) video goes black. There's no boot splash. I can't even get the verbose mode.
By the way how can I try the memtest? Grub only offers the normal and fail safe modes.
Have you checked your video memory settings if you are using shared mem as most laptops seem to then maybe it got messed up during the ram change ..
Pete .
I also thought about the video memory but didn't find anything related in BIOS settings. Any suggestion? -- Hernán Thiers García Estudiante de Ingeniería en Informática / I.T. Engineering Student Home +56 - 45 - 287366 Mobile +56 - 9 - 3779421 Skype: +56 258 13910 # 565 / internaldrums Twitter: Hernan_CL Blog: http://hernanthiers.blogspot.com Temuco, Chile -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
El 26/10/10 10:36, Dave Howorth escribió:
Hernan Thiers wrote:
Can't find the reason why openSUSE 11.3 (32 bits) doesn't boot up when I change my laptop's ram cards. I changed 2gb 667Mhz (1gb x2) for 4gb 800Mhz (2gb x2). BIOS recognize the 4gb, GRUB comes up and then the black screen stops the load. The weird thing is that the system seems to be working behind but the screen doesn't display anything.
When you say the black screen stops the load, do you mean that you see the grub menu and choose a system to boot and then it goes black?
If so, have you tried running memtest from the grub menu?
If not, can you explain at exactly what point it does go black?
Cheers, Dave
memtest says that there's no errors in ram. I'm seriously thinking in to re-install my OS :/ -- Hernán Thiers García Estudiante de Ingeniería en Informática / I.T. Engineering Student Home +56 - 45 - 287366 Mobile +56 - 9 - 3779421 Skype: +56 258 13910 # 565 / internaldrums Twitter: Hernan_CL Blog: http://hernanthiers.blogspot.com Temuco, Chile -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 26 October 2010 19:50:20 Hernan Thiers wrote:
memtest says that there's no errors in ram.
I'm seriously thinking in to re-install my OS :/
I have also changed RAM, but I haven't seen this behavior. You could try to repair your system instead of reinstalling everything. -- Bogdan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
El 26/10/10 13:50, Hernan Thiers escribió:
I'm seriously thinking in to re-install my OS :/
Ty this in secuence: 1. open the box, find JBAT1 jumper (usually near to a battery) it must be in pins 1 and 2, put it in pins 2,3 and then back to 1,2 2. Boot the machine, enter BIOS, load "optimized defaults" or "setup defaults if "optimized defaults" do not exist. 3. Boot the system again. share your findings. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
El 26/10/10 13:50, Hernan Thiers escribió:
I'm seriously thinking in to re-install my OS :/
Ty this in secuence:
1. open the box, find JBAT1 jumper (usually near to a battery) it must be in pins 1 and 2, put it in pins 2,3 and then back to 1,2
2. Boot the machine, enter BIOS, load "optimized defaults" or "setup defaults if "optimized defaults" do not exist.
3. Boot the system again.
share your findings.
This procedure is to "clear CMOS". Note that not all motherboards use jumpers; for some the method is to remove the battery (10 seconds will do). Furthermore, note any important bios configuration changes you may have made; these will be lost when you return the bios to its defaults. Re video memory, 2 things: At the grub menu hit Escape to drop the menu to text, highlight the menu entry, hit 'e' to edit it, and then remove everything on the kernel line except for the "root= . . . . " statement. Then add "edd=off". Some bios's include a memory check (not like memtest, but better than its simply reading the stick's SPD). The setting will be somewhere in the bios setup utiltity. You might also try swapping the sticks between the slots. And if the board supports dual-channel, make sure the sticks are installed accordingly. There are older bios's that even have a jumper to enable this. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
El 26/10/10 16:53, dwgallien escribió:
Ty this in secuence:
1. open the box, find JBAT1 jumper (usually near to a battery) it must be in pins 1 and 2, put it in pins 2,3 and then back to 1,2
2. Boot the machine, enter BIOS, load "optimized defaults" or "setup defaults if "optimized defaults" do not exist.
3. Boot the system again.
share your findings.
This procedure is to "clear CMOS". Note that not all motherboards use jumpers; for some the method is to remove the battery (10 seconds will do). Furthermore, note any important bios configuration changes you may have made; these will be lost when you return the bios to its defaults.
Re video memory, 2 things: At the grub menu hit Escape to drop the menu to text, highlight the menu entry, hit 'e' to edit it, and then remove everything on the kernel line except for the "root= . . . . " statement. Then add "edd=off".
Some bios's include a memory check (not like memtest, but better than its simply reading the stick's SPD). The setting will be somewhere in the bios setup utiltity.
You might also try swapping the sticks between the slots. And if the board supports dual-channel, make sure the sticks are installed accordingly. There are older bios's that even have a jumper to enable this.
The failsafe option already has that edd=off parameter. Anyway I tried it again removing all excepting the root part. This doesn't change anything. I tried to find something else at BIOS settings with no success. Also tried the "Load Default Settings" option with same results. -- Hernán Thiers García Estudiante de Ingeniería en Informática / I.T. Engineering Student Home +56 - 45 - 287366 Mobile +56 - 9 - 3779421 Skype: +56 258 13910 # 565 / internaldrums Twitter: Hernan_CL Blog: http://hernanthiers.blogspot.com Temuco, Chile -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 10/26/2010 12:50 PM, Hernan Thiers wrote:
El 26/10/10 10:36, Dave Howorth escribió:
Hernan Thiers wrote:
Can't find the reason why openSUSE 11.3 (32 bits) doesn't boot up when I change my laptop's ram cards. I changed 2gb 667Mhz (1gb x2) for 4gb 800Mhz (2gb x2). BIOS recognize the 4gb, GRUB comes up and then the black screen stops the load. The weird thing is that the system seems to be working behind but the screen doesn't display anything.
When you say the black screen stops the load, do you mean that you see the grub menu and choose a system to boot and then it goes black?
If so, have you tried running memtest from the grub menu?
If not, can you explain at exactly what point it does go black?
Cheers, Dave
memtest says that there's no errors in ram.
I'm seriously thinking in to re-install my OS :/
Does the machine still boot w/ the old memory ? Before we go reinstalling, let's make sure it's not the RAM. -- Michael S. Dunsavage -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 10/26/2010 12:50 PM, Hernan Thiers wrote:
El 26/10/10 10:36, Dave Howorth escribió:
Hernan Thiers wrote:
Can't find the reason why openSUSE 11.3 (32 bits) doesn't boot up when I change my laptop's ram cards. I changed 2gb 667Mhz (1gb x2) for 4gb 800Mhz (2gb x2). BIOS recognize the 4gb, GRUB comes up and then the black screen stops the load. The weird thing is that the system seems to be working behind but the screen doesn't display anything.
When you say the black screen stops the load, do you mean that you see the grub menu and choose a system to boot and then it goes black?
If so, have you tried running memtest from the grub menu?
If not, can you explain at exactly what point it does go black?
Cheers, Dave
memtest says that there's no errors in ram.
I'm seriously thinking in to re-install my OS :/
Does the machine still boot w/ the old memory ? Before we go reinstalling, let's make sure it's not the RAM.
And since you have 2 new sticks, you should try each of them independently, in each socket. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
El 26/10/10 22:53, dwgallien escribió:
On 10/26/2010 12:50 PM, Hernan Thiers wrote:
El 26/10/10 10:36, Dave Howorth escribió:
Hernan Thiers wrote:
Can't find the reason why openSUSE 11.3 (32 bits) doesn't boot up when I change my laptop's ram cards. I changed 2gb 667Mhz (1gb x2) for 4gb 800Mhz (2gb x2). BIOS recognize the 4gb, GRUB comes up and then the black screen stops the load. The weird thing is that the system seems to be working behind but the screen doesn't display anything.
When you say the black screen stops the load, do you mean that you see the grub menu and choose a system to boot and then it goes black?
If so, have you tried running memtest from the grub menu?
If not, can you explain at exactly what point it does go black?
Cheers, Dave
memtest says that there's no errors in ram.
I'm seriously thinking in to re-install my OS :/
Some news.
My last decision was to make a new installation from scratch. The surprise here was that this is not possible. (This looks like a bad joke). Useful info: Just after the kernel load at the openSUSE 11.3 installation the screen gets black just exactly the same way as in GRUB when I try to boot the installed OS. If I change video to text or VESA mode It DO works. I mean the installation starts in text mode. This tells me that the issue is related to video problems. Second useful info: If I try openSUSE 11.2 the installation starts without problems in normal video mode (1024x768). This tells me that the problem is related to this current kernel 2.6.34. No I know that I don't win anything reinstalling my OS. I need to find the way how to stand up my video in kernel 2.6.34 with 4GB of ram. -- Hernán Thiers García Estudiante de Ingeniería en Informática / I.T. Engineering Student Home +56 - 45 - 287366 Mobile +56 - 9 - 3779421 Skype: +56 258 13910 # 565 / internaldrums Twitter: Hernan_CL Blog: http://hernanthiers.blogspot.com Temuco, Chile -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 10/27/2010 10:07 AM, Hernan Thiers wrote:
No I know that I don't win anything reinstalling my OS. I need to find the way how to stand up my video in kernel 2.6.34 with 4GB of ram. We haven't determined it's the amount of RAM. We've determined those 2 sticks don't work.
-- Michael S. Dunsavage -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
El 27/10/10 11:15, Michael S. Dunsavage escribió:
On 10/27/2010 10:07 AM, Hernan Thiers wrote:
No I know that I don't win anything reinstalling my OS. I need to find the way how to stand up my video in kernel 2.6.34 with 4GB of ram.
We haven't determined it's the amount of RAM. We've determined those 2 sticks don't work.
That's right. In fact now I have found that my two ram modules aren't actually the same. The only difference is the latency: 5 and 6 (KVR800D2S5/2G and KVR800D2S6/2G). Does this could be related to this problem? I mean as you can see video make more sense for me but not really sure. Thanks guys. -- Hernán Thiers García Estudiante de Ingeniería en Informática / I.T. Engineering Student Home +56 - 45 - 287366 Mobile +56 - 9 - 3779421 Skype: +56 258 13910 # 565 / internaldrums Twitter: Hernan_CL Blog: http://hernanthiers.blogspot.com Temuco, Chile -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2010/10/27 12:55 (GMT-0300) Hernan Thiers composed:
Michael S. Dunsavage composed:
We haven't determined it's the amount of RAM. We've determined those 2 sticks don't work.
That's right. In fact now I have found that my two ram modules aren't actually the same. The only difference is the latency: 5 and 6 (KVR800D2S5/2G and KVR800D2S6/2G).
http://lists.opensuse.org/opensuse/2010-10/msg00821.html addressed this. I missed your answer to http://lists.opensuse.org/opensuse/2010-10/msg00820.html too.
Does this could be related to this problem? I mean as you can see video make more sense for me but not really sure.
Which video chip does your laptop use? Is nomodeset on your kernel Grub lines? All these things should have been addressed before reinstalling. -- "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 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
El 27/10/10 13:35, Felix Miata escribió:
On 2010/10/27 12:55 (GMT-0300) Hernan Thiers composed:
Michael S. Dunsavage composed:
We haven't determined it's the amount of RAM. We've determined those 2 sticks don't work.
That's right. In fact now I have found that my two ram modules aren't actually the same. The only difference is the latency: 5 and 6 (KVR800D2S5/2G and KVR800D2S6/2G).
http://lists.opensuse.org/opensuse/2010-10/msg00821.html addressed this. I missed your answer to http://lists.opensuse.org/opensuse/2010-10/msg00820.html too.
Does this could be related to this problem? I mean as you can see video make more sense for me but not really sure.
Which video chip does your laptop use? Is nomodeset on your kernel Grub lines? All these things should have been addressed before reinstalling.
About your past questions; - ram modules work alone. I tried each one independently and worked fine. - yes, machine still starts with two old memories. nomodeset is only on failsafe grub option. It's a ATI radeon 2400HD. -- Hernán Thiers García Estudiante de Ingeniería en Informática / I.T. Engineering Student Home +56 - 45 - 287366 Mobile +56 - 9 - 3779421 Skype: +56 258 13910 # 565 / internaldrums Twitter: Hernan_CL Blog: http://hernanthiers.blogspot.com Temuco, Chile -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2010/10/27 15:35 (GMT-0300) Hernan Thiers composed:
About your past questions; - ram modules work alone. I tried each one independently and worked fine. - yes, machine still starts with two old memories.
nomodeset is only on failsafe grub option. It's a ATI radeon 2400HD.
Boot to the openSUSE grub menu and add on the kernel line splash=verbose noresume nomodeset 3 then press enter, which will boot without starting X. If you get a shell prompt instead of boot failure or death screen: 1-login as root 2-mc 3-navigate to /var/log 4-inspect Xorg.0.log for lines containing (WW) & (EE) and report back what they say If you don't have mc installed, do 'zypper in mc' and try again. MC is the best friend of those with broken X (among others). Do this with the mismatched RAM modules installed, and again with only one of the two installed after running X via startx, and compare to see if there are differences. Xorg.0.log gets written anew on each X restart, so you may want to save by some other name for comparing multiple tries. The previous one is saved as Xorg.0.log.old each time, then overwritten the next time. -- "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 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
El 27/10/10 15:57, Felix Miata escribió:
On 2010/10/27 15:35 (GMT-0300) Hernan Thiers composed:
About your past questions; - ram modules work alone. I tried each one independently and worked fine. - yes, machine still starts with two old memories.
nomodeset is only on failsafe grub option. It's a ATI radeon 2400HD.
Boot to the openSUSE grub menu and add on the kernel line
splash=verbose noresume nomodeset 3
then press enter, which will boot without starting X. If you get a shell prompt instead of boot failure or death screen:
1-login as root 2-mc 3-navigate to /var/log 4-inspect Xorg.0.log for lines containing (WW) & (EE) and report back what they say
If you don't have mc installed, do 'zypper in mc' and try again. MC is the best friend of those with broken X (among others).
Do this with the mismatched RAM modules installed, and again with only one of the two installed after running X via startx, and compare to see if there are differences. Xorg.0.log gets written anew on each X restart, so you may want to save by some other name for comparing multiple tries. The previous one is saved as Xorg.0.log.old each time, then overwritten the next time.
Felix. First time I checked the Xorg log there was fglrx and screen errors then I uninstalled my proprietary ati drivers and the Xorg log shows now more significant errors. Here is where I found a "videoram" related problem. Check out the Xorg.0.log with free ati drivers (line #482): http://pastebin.com/2P6eR4y5 For me that means that Xorg is not able to resolve the video ram for current OS. -- Hernán Thiers García Estudiante de Ingeniería en Informática / I.T. Engineering Student Home +56 - 45 - 287366 Mobile +56 - 9 - 3779421 Skype: +56 258 13910 # 565 / internaldrums Twitter: Hernan_CL Blog: http://hernanthiers.blogspot.com Temuco, Chile -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 10/27/2010 04:14 PM, Hernan Thiers wrote:
El 27/10/10 15:57, Felix Miata escribió:
On 2010/10/27 15:35 (GMT-0300) Hernan Thiers composed:
About your past questions; - ram modules work alone. I tried each one independently and worked fine. - yes, machine still starts with two old memories.
nomodeset is only on failsafe grub option. It's a ATI radeon 2400HD.
Boot to the openSUSE grub menu and add on the kernel line
splash=verbose noresume nomodeset 3
then press enter, which will boot without starting X. If you get a shell prompt instead of boot failure or death screen:
1-login as root 2-mc 3-navigate to /var/log 4-inspect Xorg.0.log for lines containing (WW) & (EE) and report back what they say
If you don't have mc installed, do 'zypper in mc' and try again. MC is the best friend of those with broken X (among others).
Do this with the mismatched RAM modules installed, and again with only one of the two installed after running X via startx, and compare to see if there are differences. Xorg.0.log gets written anew on each X restart, so you may want to save by some other name for comparing multiple tries. The previous one is saved as Xorg.0.log.old each time, then overwritten the next time.
Felix. First time I checked the Xorg log there was fglrx and screen errors then I uninstalled my proprietary ati drivers and the Xorg log shows now more significant errors. Here is where I found a "videoram" related problem.
Check out the Xorg.0.log with free ati drivers (line #482): http://pastebin.com/2P6eR4y5
For me that means that Xorg is not able to resolve the video ram for current OS.
It looks like a load of all possible drivers is new in 11.3. From your pastebin: obviously fglrx is gone [ 15.801] (II) LoadModule: "fglrx" [ 15.807] (WW) Warning, couldn't open module fglrx [ 15.807] (II) UnloadModule: "fglrx" [ 15.807] (EE) Failed to load module "fglrx" (module does not exist, 0) radeonhd gets loaded [ 15.807] (II) LoadModule: "radeonhd" [ 15.807] (II) Loading /usr/lib/xorg/modules/drivers/radeonhd_drv.so [ 15.910] (II) Module radeonhd: vendor="AMD GPG" [ 15.910] compiled for 1.8.0, module version = 1.3.0 [ 15.910] Module class: X.Org Video Driver [ 15.910] ABI class: X.Org Video Driver, version 7.0 ati gets loaded [ 15.910] (II) LoadModule: "ati" [ 15.913] (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so [ 15.915] (II) Module ati: vendor="X.Org Foundation" [ 15.915] compiled for 1.8.0, module version = 6.13.0 [ 15.915] Module class: X.Org Video Driver [ 15.915] ABI class: X.Org Video Driver, version 7.0 radeon gets loaded [ 15.915] (II) LoadModule: "radeon" [ 15.918] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so [ 15.956] (II) Module radeon: vendor="X.Org Foundation" [ 15.956] compiled for 1.8.0, module version = 6.13.0 [ 15.956] Module class: X.Org Video Driver [ 15.956] ABI class: X.Org Video Driver, version 7.0 fbdev gets loaded (I have had issues with fbdev in the past) [ 15.956] (II) LoadModule: "fbdev" [ 15.957] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so [ 15.965] (II) Module fbdev: vendor="X.Org Foundation" [ 15.965] compiled for 1.8.0, module version = 0.4.1 [ 15.965] ABI class: X.Org Video Driver, version 7.0 vesa gets loaded [ 15.965] (II) LoadModule: "vesa" [ 15.968] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so [ 15.981] (II) Module vesa: vendor="X.Org Foundation" [ 15.981] compiled for 1.8.0, module version = 2.2.1 [ 15.981] Module class: X.Org Video Driver [ 15.981] ABI class: X.Org Video Driver, version 7.0 For 11.3, I have something similar: 18:14 zephyr:~> grep LoadModule /var/log/Xorg.0.log [ 32.524] (II) LoadModule: "extmod" [ 32.558] (II) LoadModule: "dbe" [ 32.575] (II) LoadModule: "glx" [ 32.576] (II) LoadModule: "record" [ 32.577] (II) LoadModule: "dri" [ 32.578] (II) LoadModule: "dri2" [ 32.579] (II) LoadModule: "fglrx" [ 32.583] (II) LoadModule: "radeonhd" [ 32.584] (II) LoadModule: "ati" [ 32.585] (II) LoadModule: "radeon" [ 32.587] (II) LoadModule: "fbdev" [ 32.588] (II) LoadModule: "vesa" [ 32.650] (II) LoadModule: "fbdevhw" [ 32.741] (II) LoadModule: "fb" [ 32.838] (II) LoadModule: "ramdac" [ 32.838] (II) LoadModule: "exa" [ 33.628] (II) LoadModule: "evdev" [ 33.733] (II) LoadModule: "synaptics" with the same: [ 32.582] (WW) Warning, couldn't open module fglrx [ 32.583] (EE) Failed to load module "fglrx" (module does not exist, 0) Stepping back for a moment and thinking about this issue, it would seem that the whole problem is the ram timing differences between the two sticks that is screwing up the 'Hyper-RAM' shared video memory for the 2400 gpu. If each stick will work fine alone, but the combination fails, then I think that is your answer. I don't claim to know how ATI inits the latency/timings for it's shared memory, but if it just inits a block of RAM and the RAM is in a dual-channel config, I can see that the video would freak out and just quit. The only suggestion I have would be to check if your bios allows you to manually set the ram timing. If so, manually set the ram timings to match the slower stick and try booting again. The fast stick should easily operate at the higher latency. However, the reverse isn't true. The bios should be smart enough to handle setting timings to the timings of the slower stick automatically, but if the bios is just setting the timings based on check of a single stick and assuming they are both the same, that could be your problem. These are just suggestions and I'm no ram timing expert, but based on the symptoms and on it working with each stick alone, it has to be something along these lines.... Good luck. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
El 27/10/10 20:30, David C. Rankin escribió:
On 10/27/2010 04:14 PM, Hernan Thiers wrote:
El 27/10/10 15:57, Felix Miata escribió:
On 2010/10/27 15:35 (GMT-0300) Hernan Thiers composed:
About your past questions; - ram modules work alone. I tried each one independently and worked fine. - yes, machine still starts with two old memories.
nomodeset is only on failsafe grub option. It's a ATI radeon 2400HD.
Boot to the openSUSE grub menu and add on the kernel line
splash=verbose noresume nomodeset 3
then press enter, which will boot without starting X. If you get a shell prompt instead of boot failure or death screen:
1-login as root 2-mc 3-navigate to /var/log 4-inspect Xorg.0.log for lines containing (WW) & (EE) and report back what they say
If you don't have mc installed, do 'zypper in mc' and try again. MC is the best friend of those with broken X (among others).
Do this with the mismatched RAM modules installed, and again with only one of the two installed after running X via startx, and compare to see if there are differences. Xorg.0.log gets written anew on each X restart, so you may want to save by some other name for comparing multiple tries. The previous one is saved as Xorg.0.log.old each time, then overwritten the next time.
Felix. First time I checked the Xorg log there was fglrx and screen errors then I uninstalled my proprietary ati drivers and the Xorg log shows now more significant errors. Here is where I found a "videoram" related problem.
Check out the Xorg.0.log with free ati drivers (line #482): http://pastebin.com/2P6eR4y5
For me that means that Xorg is not able to resolve the video ram for current OS.
It looks like a load of all possible drivers is new in 11.3. From your pastebin:
obviously fglrx is gone
[ 15.801] (II) LoadModule: "fglrx" [ 15.807] (WW) Warning, couldn't open module fglrx [ 15.807] (II) UnloadModule: "fglrx" [ 15.807] (EE) Failed to load module "fglrx" (module does not exist, 0)
radeonhd gets loaded
[ 15.807] (II) LoadModule: "radeonhd" [ 15.807] (II) Loading /usr/lib/xorg/modules/drivers/radeonhd_drv.so [ 15.910] (II) Module radeonhd: vendor="AMD GPG" [ 15.910] compiled for 1.8.0, module version = 1.3.0 [ 15.910] Module class: X.Org Video Driver [ 15.910] ABI class: X.Org Video Driver, version 7.0
ati gets loaded
[ 15.910] (II) LoadModule: "ati" [ 15.913] (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so [ 15.915] (II) Module ati: vendor="X.Org Foundation" [ 15.915] compiled for 1.8.0, module version = 6.13.0 [ 15.915] Module class: X.Org Video Driver [ 15.915] ABI class: X.Org Video Driver, version 7.0
radeon gets loaded
[ 15.915] (II) LoadModule: "radeon" [ 15.918] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so [ 15.956] (II) Module radeon: vendor="X.Org Foundation" [ 15.956] compiled for 1.8.0, module version = 6.13.0 [ 15.956] Module class: X.Org Video Driver [ 15.956] ABI class: X.Org Video Driver, version 7.0
fbdev gets loaded (I have had issues with fbdev in the past)
[ 15.956] (II) LoadModule: "fbdev" [ 15.957] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so [ 15.965] (II) Module fbdev: vendor="X.Org Foundation" [ 15.965] compiled for 1.8.0, module version = 0.4.1 [ 15.965] ABI class: X.Org Video Driver, version 7.0
vesa gets loaded
[ 15.965] (II) LoadModule: "vesa" [ 15.968] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so [ 15.981] (II) Module vesa: vendor="X.Org Foundation" [ 15.981] compiled for 1.8.0, module version = 2.2.1 [ 15.981] Module class: X.Org Video Driver [ 15.981] ABI class: X.Org Video Driver, version 7.0
For 11.3, I have something similar:
18:14 zephyr:~> grep LoadModule /var/log/Xorg.0.log [ 32.524] (II) LoadModule: "extmod" [ 32.558] (II) LoadModule: "dbe" [ 32.575] (II) LoadModule: "glx" [ 32.576] (II) LoadModule: "record" [ 32.577] (II) LoadModule: "dri" [ 32.578] (II) LoadModule: "dri2" [ 32.579] (II) LoadModule: "fglrx" [ 32.583] (II) LoadModule: "radeonhd" [ 32.584] (II) LoadModule: "ati" [ 32.585] (II) LoadModule: "radeon" [ 32.587] (II) LoadModule: "fbdev" [ 32.588] (II) LoadModule: "vesa" [ 32.650] (II) LoadModule: "fbdevhw" [ 32.741] (II) LoadModule: "fb" [ 32.838] (II) LoadModule: "ramdac" [ 32.838] (II) LoadModule: "exa" [ 33.628] (II) LoadModule: "evdev" [ 33.733] (II) LoadModule: "synaptics"
with the same: [ 32.582] (WW) Warning, couldn't open module fglrx [ 32.583] (EE) Failed to load module "fglrx" (module does not exist, 0)
Stepping back for a moment and thinking about this issue, it would seem that the whole problem is the ram timing differences between the two sticks that is screwing up the 'Hyper-RAM' shared video memory for the 2400 gpu. If each stick will work fine alone, but the combination fails, then I think that is your answer.
I don't claim to know how ATI inits the latency/timings for it's shared memory, but if it just inits a block of RAM and the RAM is in a dual-channel config, I can see that the video would freak out and just quit.
The only suggestion I have would be to check if your bios allows you to manually set the ram timing. If so, manually set the ram timings to match the slower stick and try booting again. The fast stick should easily operate at the higher latency. However, the reverse isn't true. The bios should be smart enough to handle setting timings to the timings of the slower stick automatically, but if the bios is just setting the timings based on check of a single stick and assuming they are both the same, that could be your problem.
These are just suggestions and I'm no ram timing expert, but based on the symptoms and on it working with each stick alone, it has to be something along these lines....
Good luck.
I understand but can't I relate this issue to the 2.6.34 kernel version? As I mentioned some e-mails ago, I can run without problem older versions like openSUSE 11.2 and Ubuntu 9 (what I found near). -- Hernán Thiers García Estudiante de Ingeniería en Informática / I.T. Engineering Student Home +56 - 45 - 287366 Mobile +56 - 9 - 3779421 Skype: +56 258 13910 # 565 / internaldrums Twitter: Hernan_CL Blog: http://hernanthiers.blogspot.com Temuco, Chile -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2010/10/27 21:05 (GMT-0300) Hernan Thiers composed:
I understand but can't I relate this issue to the 2.6.34 kernel version?
Try a 2.6.36 kernel from http://download.opensuse.org/repositories/Kernel:/HEAD/openSUSE_11.3/ and see. -- "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 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 10/27/2010 07:05 PM, Hernan Thiers wrote:
I understand but can't I relate this issue to the 2.6.34 kernel version? As I mentioned some e-mails ago, I can run without problem older versions like openSUSE 11.2 and Ubuntu 9 (what I found near).
Dunno, but I had nothing but trouble with 2.6.34. I am running 2.6.35 from kernel:/HEAD right now and I haven't had any issues. I didn't black-screen on boot with 2.6.34, but I had a lot of issues. 2.6.36beta is in kernel:/HEAD now. It would be worth giving it a shot. However, I had issues with the previous 2.6.36beta kernels as well. If you are running an i586 box, I can make the 2.6.35 kernel available (I still have the rpms) However, I don't think the kernel has anything to do with the ram timing/share video ram issue. (I could be wrong) Regardless, testing another kernel can't hurt.... -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
El 27/10/10 23:28, David C. Rankin escribió:
On 10/27/2010 07:05 PM, Hernan Thiers wrote:
I understand but can't I relate this issue to the 2.6.34 kernel version? As I mentioned some e-mails ago, I can run without problem older versions like openSUSE 11.2 and Ubuntu 9 (what I found near).
Dunno, but I had nothing but trouble with 2.6.34. I am running 2.6.35 from kernel:/HEAD right now and I haven't had any issues. I didn't black-screen on boot with 2.6.34, but I had a lot of issues. 2.6.36beta is in kernel:/HEAD now. It would be worth giving it a shot. However, I had issues with the previous 2.6.36beta kernels as well.
If you are running an i586 box, I can make the 2.6.35 kernel available (I still have the rpms)
However, I don't think the kernel has anything to do with the ram timing/share video ram issue. (I could be wrong) Regardless, testing another kernel can't hurt....
Would be great if I can get access to the 6.35 kernel as I always prefer stable releases. As you say kernel may has nothing to do with ram sharing but can't yet find a reason why other versions (older in this case) work. In fact I'm seriously thinking in to install openSUSE 11.2 in parallel. By the way, would you recommend me a way to upgrade my kernel? How can I get that 6.35 version? -- Hernán Thiers García Estudiante de Ingeniería en Informática / I.T. Engineering Student Home +56 - 45 - 287366 Mobile +56 - 9 - 3779421 Skype: +56 258 13910 # 565 / internaldrums Twitter: Hernan_CL Blog: http://hernanthiers.blogspot.com Temuco, Chile -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 10/27/2010 09:43 PM, Hernan Thiers wrote:
El 27/10/10 23:28, David C. Rankin escribió:
On 10/27/2010 07:05 PM, Hernan Thiers wrote:
I understand but can't I relate this issue to the 2.6.34 kernel version? As I mentioned some e-mails ago, I can run without problem older versions like openSUSE 11.2 and Ubuntu 9 (what I found near).
Dunno, but I had nothing but trouble with 2.6.34. I am running 2.6.35 from kernel:/HEAD right now and I haven't had any issues. I didn't black-screen on boot with 2.6.34, but I had a lot of issues. 2.6.36beta is in kernel:/HEAD now. It would be worth giving it a shot. However, I had issues with the previous 2.6.36beta kernels as well.
If you are running an i586 box, I can make the 2.6.35 kernel available (I still have the rpms)
However, I don't think the kernel has anything to do with the ram timing/share video ram issue. (I could be wrong) Regardless, testing another kernel can't hurt....
Would be great if I can get access to the 6.35 kernel as I always prefer stable releases. As you say kernel may has nothing to do with ram sharing but can't yet find a reason why other versions (older in this case) work. In fact I'm seriously thinking in to install openSUSE 11.2 in parallel.
By the way, would you recommend me a way to upgrade my kernel? How can I get that 6.35 version?
Here is my saved 2.6.35-1 kernel rpms from kernel:/HEAD http://www.3111skyline.com/dl/openSUSE_11.3/kernel/2.6.35/ it contains: kernel-debug-devel-2.6.35.1-1.1.i586.rpm kernel-default-2.6.35.1-1.1.i586.rpm kernel-default-base-2.6.35.1-1.1.i586.rpm kernel-default-devel-2.6.35.1-1.1.i586.rpm kernel-desktop-devel-2.6.35.1-1.1.i586.rpm kernel-devel-2.6.35.1-1.1.noarch.rpm kernel-pae-2.6.35.1-1.1.i586.rpm kernel-pae-base-2.6.35.1-1.1.i586.rpm kernel-pae-devel-2.6.35.1-1.1.i586.rpm kernel-source-2.6.35.1-1.1.noarch.rpm kernel-syms-2.6.35.1-1.1.i586.rpm kernel-xen-devel-2.6.35.1-1.1.i586.rpm The download will be a little slow. I only have 1/2 meg upstream connection. Just download the rpms to a directory and install with 'rpm -ivh *.rpm' That will *install* the new kernel without wiping out your existing kernel. You can also add the following as a repository and try the 2.6.36 kernel: http://download.opensuse.org/repositories/Kernel:/HEAD/openSUSE_11.3/ Just do (this is one line -- using '\' continuations, just copy and paste into an xterm as root): zypper ar --keep-packages --refresh \ http://download.opensuse.org/repositories/Kernel:/HEAD/openSUSE_11.3/ \ kernel-head Then use yast or 'zypper up --repo kernel-head' to grab 2.6.36. **NOTE: If you use yast or zypper, then to prevent *upgrading* and wiping out your existing kernel, set the following option in /etc/zypp/zypp.conf: multiversion = kernel-default,kernel-pae Let us know how it goes... -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
El 28/10/10 03:16, David C. Rankin escribió:
On 10/27/2010 09:43 PM, Hernan Thiers wrote:
El 27/10/10 23:28, David C. Rankin escribió:
On 10/27/2010 07:05 PM, Hernan Thiers wrote:
I understand but can't I relate this issue to the 2.6.34 kernel version? As I mentioned some e-mails ago, I can run without problem older versions like openSUSE 11.2 and Ubuntu 9 (what I found near).
Dunno, but I had nothing but trouble with 2.6.34. I am running 2.6.35 from kernel:/HEAD right now and I haven't had any issues. I didn't black-screen on boot with 2.6.34, but I had a lot of issues. 2.6.36beta is in kernel:/HEAD now. It would be worth giving it a shot. However, I had issues with the previous 2.6.36beta kernels as well.
If you are running an i586 box, I can make the 2.6.35 kernel available (I still have the rpms)
However, I don't think the kernel has anything to do with the ram timing/share video ram issue. (I could be wrong) Regardless, testing another kernel can't hurt....
Would be great if I can get access to the 6.35 kernel as I always prefer stable releases. As you say kernel may has nothing to do with ram sharing but can't yet find a reason why other versions (older in this case) work. In fact I'm seriously thinking in to install openSUSE 11.2 in parallel.
By the way, would you recommend me a way to upgrade my kernel? How can I get that 6.35 version?
Here is my saved 2.6.35-1 kernel rpms from kernel:/HEAD
http://www.3111skyline.com/dl/openSUSE_11.3/kernel/2.6.35/
it contains:
kernel-debug-devel-2.6.35.1-1.1.i586.rpm kernel-default-2.6.35.1-1.1.i586.rpm kernel-default-base-2.6.35.1-1.1.i586.rpm kernel-default-devel-2.6.35.1-1.1.i586.rpm kernel-desktop-devel-2.6.35.1-1.1.i586.rpm kernel-devel-2.6.35.1-1.1.noarch.rpm kernel-pae-2.6.35.1-1.1.i586.rpm kernel-pae-base-2.6.35.1-1.1.i586.rpm kernel-pae-devel-2.6.35.1-1.1.i586.rpm kernel-source-2.6.35.1-1.1.noarch.rpm kernel-syms-2.6.35.1-1.1.i586.rpm kernel-xen-devel-2.6.35.1-1.1.i586.rpm
The download will be a little slow. I only have 1/2 meg upstream connection. Just download the rpms to a directory and install with 'rpm -ivh *.rpm' That will *install* the new kernel without wiping out your existing kernel.
You can also add the following as a repository and try the 2.6.36 kernel:
http://download.opensuse.org/repositories/Kernel:/HEAD/openSUSE_11.3/
Just do (this is one line -- using '\' continuations, just copy and paste into an xterm as root):
zypper ar --keep-packages --refresh \ http://download.opensuse.org/repositories/Kernel:/HEAD/openSUSE_11.3/ \ kernel-head
Then use yast or 'zypper up --repo kernel-head' to grab 2.6.36.
**NOTE: If you use yast or zypper, then to prevent *upgrading* and wiping out your existing kernel, set the following option in /etc/zypp/zypp.conf:
multiversion = kernel-default,kernel-pae
Let us know how it goes...
Finally! As I thought the problem was because of the 2.6.34 kernel version. Don't know why but it doesn't works well on my laptop with 4GB on RAM. (No videoram). I took the 2.6.35 kernel version offered by David enabling the multi-kernel option (zypp.conf). The system starts and recognize the 4GB just perfect! Now I'm worried about the support for this 2.6.35 kernel version as the Kernel HEAD repo offers the 2.6.36 only. What woud be the best choice? An upgrade to the last 2.6.36 kernel (unstable)? or to keep this 2.6.35 unworried about anything? Thanks guys! :) -- Hernán Thiers García Estudiante de Ingeniería en Informática / I.T. Engineering Student Home +56 - 45 - 287366 Mobile +56 - 9 - 3779421 Skype: +56 258 13910 # 565 / internaldrums Twitter: Hernan_CL Blog: http://hernanthiers.blogspot.com Temuco, Chile -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 10/28/2010 11:01 AM, Hernan Thiers wrote:
What woud be the best choice? An upgrade to the last 2.6.36 kernel (unstable)? or to keep this 2.6.35 unworried about anything?
If 2.6.36 works -- use it. If not, then stay with 2.6.35. From a support standpoint, what you care about is that you have a working kernel that plays well with your system. openSuSE should have put out an update to 2.6.35 or 2.6.36 long ago for 11.3. The 2.6.34 kernel that shipped with 11.3 was just garbage on many laptops. Glad you got it working! -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
El 28/10/10 20:14, David C. Rankin escribió:
On 10/28/2010 11:01 AM, Hernan Thiers wrote:
What woud be the best choice? An upgrade to the last 2.6.36 kernel (unstable)? or to keep this 2.6.35 unworried about anything?
If 2.6.36 works -- use it. If not, then stay with 2.6.35. From a support standpoint, what you care about is that you have a working kernel that plays well with your system.
openSuSE should have put out an update to 2.6.35 or 2.6.36 long ago for 11.3. The 2.6.34 kernel that shipped with 11.3 was just garbage on many laptops.
Glad you got it working!
My sincerely thanks David! I'll try that .36 kernel soon although I feel like my laptop is breathing better than ever lol. -- Hernán Thiers García Estudiante de Ingeniería en Informática / I.T. Engineering Student Home +56 - 45 - 287366 Mobile +56 - 9 - 3779421 Skype: +56 258 13910 # 565 / internaldrums Twitter: Hernan_CL Blog: http://hernanthiers.blogspot.com Temuco, Chile -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, Oct 28, 2010 at 06:14:22PM -0500, David C. Rankin wrote: [ 8< ]
openSuSE should have put out an update to 2.6.35 or 2.6.36 long ago for 11.3. The 2.6.34 kernel that shipped with 11.3 was just garbage on many laptops.
From 20 different 11.3 installs I had one issue with the kernel. And I reported it via bugzilla. You filed a report too? Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
On 10/29/2010 04:18 AM, Lars Müller wrote:
On Thu, Oct 28, 2010 at 06:14:22PM -0500, David C. Rankin wrote: [ 8< ]
openSuSE should have put out an update to 2.6.35 or 2.6.36 long ago for 11.3. The 2.6.34 kernel that shipped with 11.3 was just garbage on many laptops.
From 20 different 11.3 installs I had one issue with the kernel. And I reported it via bugzilla.
You filed a report too?
Lars
Yep https://bugzilla.novell.com/show_bug.cgi?id=628166 ;-) -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (12)
-
Bogdan Cristea -
Cristian Rodríguez -
Dave Howorth -
David C. Rankin -
dwgallien -
Felix Miata -
Hernan Thiers -
Lars Müller -
Michael S. Dunsavage -
Patrick Shanahan -
Peter Nikolic -
Philippe Andersson