Perhaps I've found a reason why so many people are having problems with SuSE 9.1?
Maybe one of the update servers is hosed in terms of a kernel update. Reason I mention this is this. And yes, I'm back, giving it another go-around in spite of the problems that plagued me last time. I decided to pull some hardware, mess around with my bios. change some cables. Call me a glutton for punishment I guess. Anyway, I just did an install a few hours ago. Then I did an update. Then I tried to configure VMWare to work with my system. It didn't work and during vmware-config.pl it said that I was running the linux-2.6.4-5 kernel, but I had linux-2.6.4-52 sources. I rebooted, and my sound, my ethernet, nothing worked. So I reinstalled. This time I configured VMWare before doing an online update. Everything worked great. Everything was detected as linux-2.6.4-52, which I assume is correct unless the original kernel that comes with the box set is hosed. Either way, it's something. One of the mirrors is bad, perhaps? Either way, one minute I experienced the "sound not working" problem and saw a distinct reason why (my kernel was hosed) and after reinstalling everything is peachy. So what is going exactly? Anyone know? Preston
On Monday 31 May 2004 22:56, Preston Crawford wrote:
Maybe one of the update servers is hosed in terms of a kernel update. Reason I mention this is this. And yes, I'm back, giving it another go-around in spite of the problems that plagued me last time. I decided to pull some hardware, mess around with my bios. change some cables. Call me a glutton for punishment I guess.
Anyway, I just did an install a few hours ago. Then I did an update. Then I tried to configure VMWare to work with my system. It didn't work and during vmware-config.pl it said that I was running the linux-2.6.4-5 kernel, but I had linux-2.6.4-52 sources.
I rebooted, and my sound, my ethernet, nothing worked. So I reinstalled. This time I configured VMWare before doing an online update. Everything worked great. Everything was detected as linux-2.6.4-52, which I assume is correct unless the original kernel that comes with the box set is hosed. Either way, it's something. One of the mirrors is bad, perhaps?
Either way, one minute I experienced the "sound not working" problem and saw a distinct reason why (my kernel was hosed) and after reinstalling everything is peachy. So what is going exactly? Anyone know?
Preston
When you update a kernel you should also update your source tree because vmware requires the current source tree to match the running kernel. Sound/ethernet "nothing worked" after a reboot issue is probably because you run an ACPI machine and for some reason acpi was not properly loaded. ALSO the title of your post suggests that "so many people are having trouble with 9.1".... Where did you get that impression? Why would you come to a help forum for SuSE and assume everyone is having problems with suse? Its like going to a Ford dealership, and looking in the service bays at all the Fords being serviced and assuming Fords must be really problem prone! -- _____________________________________ John Andersen
Hi John, John Andersen wrote: [ snip ]
When you update a kernel you should also update your source tree because vmware requires the current source tree to match the running kernel.
Please, excuse this silly question: how do you update the source tree? is it a checkbox somewhere? :/ TIA, Martin [ snip ]
On Tue, Jun 01, 2004 at 01:21:29PM +0200, Martin Mielke wrote:
Please, excuse this silly question: how do you update the source tree? is it a checkbox somewhere? :/
There's a separate kernel source package. -- David Smith Work Email: Dave.Smith@st.com STMicroelectronics Home Email: David.Smith@ds-electronics.co.uk Bristol, England GPG Key: 0xF13192F2
On Tue, 2004-06-01 at 04:07, John Andersen wrote:
On Monday 31 May 2004 22:56, Preston Crawford wrote:
Maybe one of the update servers is hosed in terms of a kernel update. Reason I mention this is this. And yes, I'm back, giving it another go-around in spite of the problems that plagued me last time. I decided to pull some hardware, mess around with my bios. change some cables. Call me a glutton for punishment I guess.
Anyway, I just did an install a few hours ago. Then I did an update. Then I tried to configure VMWare to work with my system. It didn't work and during vmware-config.pl it said that I was running the linux-2.6.4-5 kernel, but I had linux-2.6.4-52 sources.
I rebooted, and my sound, my ethernet, nothing worked. So I reinstalled. This time I configured VMWare before doing an online update. Everything worked great. Everything was detected as linux-2.6.4-52, which I assume is correct unless the original kernel that comes with the box set is hosed. Either way, it's something. One of the mirrors is bad, perhaps?
Either way, one minute I experienced the "sound not working" problem and saw a distinct reason why (my kernel was hosed) and after reinstalling everything is peachy. So what is going exactly? Anyone know?
Preston
When you update a kernel you should also update your source tree because vmware requires the current source tree to match the running kernel.
That's the thing. The update server I used (and I was doing one of those "upgrade everything" YOU updates) didn't have the sources. It had the kernel, but not the sources. Now I have both. This time I got the updates from the main SuSE mirror. From there I got 2.6.4-54.5. From the US mirror I got (like I said earlier) 2.6.5, with no sources.
Sound/ethernet "nothing worked" after a reboot issue is probably because you run an ACPI machine and for some reason acpi was not properly loaded.
Hmmm... Even after X reboots. What do you do in that situation then?
ALSO the title of your post suggests that "so many people are having trouble with 9.1"....
Where did you get that impression? Why would you come to a help forum for SuSE and assume everyone is having problems with suse?
Because I was here earlier, I've read the archives and I'm on the usenet group and it seems like quite a few of us are having problems that revolve around the kernel. I thought that might help. The information I had.
Its like going to a Ford dealership, and looking in the service bays at all the Fords being serviced and assuming Fords must be really problem prone!
This isn't a dealership. It's a user list, isn't it? Preston
participants (4)
-
Dave Smith -
John Andersen -
Martin Mielke -
Preston Crawford