[opensuse] 10.3 problems after 11.0 install
Hello SuSE people, Back again after harrowing experiences with the install of 11.0 with KDE4. Could not get my 10.2 or my work OS, 10.3 to boot after the 11.0 install. Finally reinstalled 11.0 with KDF3.5. (Other problems there but not for this thread. Anyway, I can now boot my 10.3 but have lost a good deal of functionality, The first thing, enough for this plea for help is: None of my USB stuff works. A look at the boot log or dmesg makes no mention of the usb devices. There is a line in fstab for usb. Following: usbfs /proc/bus/usb usbfs noauto 0 0 Nothing to be seen in /proc either. The second thing is the sound is gone. Yast and Alsa do not find the sound chip on the MB. The third thing is the printer has stopped working. Some problem with cups. Just mentioning these last two in case they are all related. Any help in figuring this out foe me would be really appreciated. Bob S -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Bob S wrote:
Hello SuSE people,
The second thing is the sound is gone. Yast and Alsa do not find the sound chip on the MB.
The third thing is the printer has stopped working. Some problem with cups. Just mentioning these last two in case they are all related.
Any help in figuring this out foe me would be really appreciated.
Bob S
Can't help with the USB, but I just noticed my sound is gone as well in 11.0. I'll investigate and report back. -- 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
David C. Rankin wrote:
Bob S wrote:
Hello SuSE people,
The second thing is the sound is gone. Yast and Alsa do not find the sound chip on the MB.
The third thing is the printer has stopped working. Some problem with cups. Just mentioning these last two in case they are all related.
Any help in figuring this out foe me would be really appreciated.
Bob S
Can't help with the USB, but I just noticed my sound is gone as well in 11.0. I'll investigate and report back.
The problem WAS YAST. Somehow, Yast had lost its mind again and had the "front" volume turned to "0" (zero). Restoring the front volume fixed the problem. No, I didn't do it either ;-) -- 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
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Content-ID:
thread. Anyway, I can now boot my 10.3 but have lost a good deal of functionality,
The first thing, enough for this plea for help is: None of my USB stuff works. ... The second thing is the sound is gone. Yast and Alsa do not find the sound chip on the MB. ... The third thing is the printer has stopped working. Some problem with cups. Just mentioning these last two in case they are all related.
Any help in figuring this out foe me would be really appreciated.
My wild guess is the kernel parameters in grub. Maybe you need "apic" or something of the sort. If it worked previously, compare with your backup. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkjIxqwACgkQtTMYHG2NR9UxkQCfbF+kpnEiiMG2M35E2cbf+zPG tbUAn1E4cfAfBGgitdvQ5xQoyDPX/r7C =d/Sq -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 11 September 2008 03:20:09 am Carlos E. R. wrote:
Content-ID:
The Wednesday 2008-09-10 at 03:51 -0400, Bob S wrote:
thread. Anyway, I can now boot my 10.3 but have lost a good deal of functionality,
The first thing, enough for this plea for help is: None of my USB stuff works.
The second thing is the sound is gone. Yast and Alsa do not find the sound chip on the MB.
The third thing is the printer has stopped working. Some problem with cups. Just mentioning these last two in case they are all related.
Any help in figuring this out foe me would be really appreciated.
My wild guess is the kernel parameters in grub. Maybe you need "apic" or something of the sort. If it worked previously, compare with your backup.
Hi Carlos, thanks for replying. Possibly a good wild guess. Unfortunately my backup is on the usb hard drive. Here is my section of Grub which pertains to 10.3. Does it look anything like yours? ###Don't change this command - Yast identifier: Original name: openSUSE 10.3 title openSUSE 10.3 root (hd2,7) kernel /boot/vmlinuz-2.6.22.18-0.2-default root=/dev/disk/by-label/10.3 resume=/dev/sdc3 splash=silent showopts initrd /boot/initrd-2.6.22.18-0.2-default Bob S -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2008-09-10 at 06:11 -0400, Bob S wrote:
My wild guess is the kernel parameters in grub. Maybe you need "apic" or something of the sort. If it worked previously, compare with your backup.
Hi Carlos, thanks for replying.
Possibly a good wild guess. Unfortunately my backup is on the usb hard drive.
Arg. :-( Mine too. Don't you have another partition with another linux? I always have at least the older suse version and factory, which can be used in emergencies. Have a good look at the /var/log/boot.msg file for ideas. Look for errors. Maybe some clue is there.
Here is my section of Grub which pertains to 10.3. Does it look anything like yours?
###Don't change this command - Yast identifier: Original name: openSUSE 10.3 title openSUSE 10.3 root (hd2,7) kernel /boot/vmlinuz-2.6.22.18-0.2-default root=/dev/disk/by-label/10.3 resume=/dev/sdc3 splash=silent showopts initrd /boot/initrd-2.6.22.18-0.2-default
mine was: title MAIN openSUSE 10.3 (default) root (hd0,5) kernel /vmlinuz root=/dev/disk/by-label/160_root vga=0x317 resume=/dev/disk/by-label/320_swap splash=verbose showopts apic initrd /initrd I know I had to explicitly activate apic previously or somethings would not work (old computer, kernel thought apic not reliable due to bios date). Thus I forced it. The 11.0 destroyed the previous menu.lst, many entries were erased. I have to check them. The current boot entry is: ###Don't change this comment - YaST2 identifier: Original name: linux### title openSUSE 11.0 - 2.6.25.16-0.1 root (hd0,5) kernel /vmlinuz-2.6.25.16-0.1-pae root=/dev/disk/by-id/ata-ST3160021A_5JS4VV1F-part6 hwprobe=-modules.pata resume=/dev/hda5 splash=silent showopts vga=0x317 initrd /initrd-2.6.25.16-0.1-pae - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkjKQJsACgkQtTMYHG2NR9XDBQCfQdK/cRAqU4jgfG9wmnvpI8BG LXsAmwVyll4XnLCFDM4EEWO1B01zh6S2 =/nNT -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 12 September 2008 06:12:42 am Carlos E. R. wrote:
The Wednesday 2008-09-10 at 06:11 -0400, Bob S wrote:
My wild guess is the kernel parameters in grub. Maybe you need "apic" or something of the sort. If it worked previously, compare with your backup.
Hi Carlos, thanks for replying.
Possibly a good wild guess. Unfortunately my backup is on the usb hard drive.
Arg. :-(
Mine too.
.....<snipped a bunch>...... Well Carlos, thanks so much for your analysis and trying to help. I really appreciate it and is filed away for future use. The fix was simple, and I feel so stupid. I checked the BIOS again, more carefully this time. The usb controller and the ac97 sound chip were both disabled. Turned them on again, reconfigured, and all is well. I didn't think that SuSE touched the bios. Evidently I was wrong. Stupid, Stupid, Stupid Thanks again for helping Bob S -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 10 September 2008 07:03:56 pm Bob S wrote: ...
The fix was simple. I checked the BIOS again, more carefully this time. The usb controller and the ac97 sound chip were both disabled. ...
Thank you for sharing this. The hardest thing to do is to admit mistake to check elementary things. Everyone of us has a list of problems that made us troubleshoot for hours something that eventually showed up as very simple, but no one tend to publish them. There is not so new page: http://en.opensuse.org/Troubleshooting I hope that other will help with ideas and by creating structure that will make access to knowledge, as easy as possible. -- Regards, Rajko -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2008-09-10 at 20:03 -0400, Bob S wrote:
.....<snipped a bunch>......
Well Carlos, thanks so much for your analysis and trying to help. I really appreciate it and is filed away for future use.
Welcome.
The fix was simple, and I feel so stupid. I checked the BIOS again, more carefully this time. The usb controller and the ac97 sound chip were both disabled. Turned them on again, reconfigured, and all is well. I didn't think that SuSE touched the bios. Evidently I was wrong.
Not possible. I mean, it is not possible for linux to touch the bios configuration. Possibly you or someone else touched something in the bios and the bios configuration program touched the rest. Not possible because there is no universal API to configure the bios from an operating system. It is simply a memory space, very small (way less than 1 kilobyte) inside the chip that keeps the clock (the battery used for the clock also backs the cmos memory). Knowing what means each particular byte depends on each bios make, each motherboard, and who knows. The memory is accesable from the OS, but no knowing what each particular byte does in your particular system means that is is not feasible to configure it from the OS.
Stupid, Stupid, Stupid
No, simply we did not think of the simple and obvious. We think of more complex things that may go wrong. If you had had a second operating system in your machine, or had tried a live linux on CD, you might have seen it also would not work; therefore we would have thought of something not dependant on the OS (hardware, probably). - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkjLiykACgkQtTMYHG2NR9Xa/wCfdzQR+B8/ZmKISo4rQoeLRZr2 sC8An1aB1fVUkn/YLrGzdo002C4ZinFv =jDoa -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 13 September 2008 05:43:03 am Carlos E. R. wrote:
The Wednesday 2008-09-10 at 20:03 -0400, Bob S wrote:
.....<snipped a bunch>......
Well Carlos, thanks so much for your analysis and trying to help. I really appreciate it and is filed away for future use.
Welcome.
The fix was simple, and I feel so stupid. I checked the BIOS again, more carefully this time. The usb controller and the ac97 sound chip were both disabled. Turned them on again, reconfigured, and all is well. I didn't think that SuSE touched the bios. Evidently I was wrong.
Not possible. I mean, it is not possible for linux to touch the bios configuration. Possibly you or someone else touched something in the bios and the bios configuration program touched the rest.
Not possible because there is no universal API to configure the bios from an operating system. It is simply a memory space, very small (way less than 1 kilobyte) inside the chip that keeps the clock (the battery used for the clock also backs the cmos memory). Knowing what means each particular byte depends on each bios make, each motherboard, and who knows. The memory is accesable from the OS, but no knowing what each particular byte does in your particular system means that is is not feasible to configure it from the OS.
I don't know what to tell you. I certainly don't doubt what you have said. I swear on a stack of bible's that I did not touch the bios, and there is....no one....else that could have done it. (As I look around and feel a chill ccoming over me, hearing chains rattling in the darkened hallway behind me) Oh well....All is good now. I have my important system back now. SuSE 11.0 and KDE4 is another story. Nothing that I'm gonna worry about though. Thanks again. Bob S. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2008-09-11 at 13:05 -0400, Bob S wrote:
Not possible. I mean, it is not possible for linux to touch the bios configuration. Possibly you or someone else touched something in the bios and the bios configuration program touched the rest.
...
I don't know what to tell you. I certainly don't doubt what you have said. I swear on a stack of bible's that I did not touch the bios, and there is....no one....else that could have done it. (As I look around and feel a chill ccoming over me, hearing chains rattling in the darkened hallway behind me)
:-)
Oh well....All is good now. I have my important system back now. SuSE 11.0 and KDE4 is another story. Nothing that I'm gonna worry about though. Thanks again.
Welcome. It's weird, though... We could say "¡Cosmic rays!". Yep, things like that could flip a bit in memory, but... chat cmos chip has a checksum, and if it doesn't check the thing (or the bios, dunno) erases and resets it entirely. I can't believe a bunch of cosmic rays altering the bits and the checksum in a consistent manner. Huh, have you seen KIT near your neighbourhood lately? ;-p No, but seriously, I have seen the bios altered previously. I have no idea how. It could even be me and I forgot, who knows! :-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkjM43sACgkQtTMYHG2NR9V/BQCeL9PmU9C77brNpJ3qj5ja8nNL mRUAoImW01RNKtBOqHH1TwFBsS2blSNw =uLQx -----END PGP SIGNATURE-----
participants (4)
-
Bob S
-
Carlos E. R.
-
David C. Rankin
-
Rajko M.