Sorry folks, but to me v9.1 is a damn waste of money, and a pain in the bum to boot. I was really looking forward to getting 9.1 but now am sorry I got it. The annoyances may be small (from those I found so far) but nevertheless they point out the lack of quality control of the product. Firtsly, v9.1 is NOT modem friendly. It may be OK for those using it on broadband - and those who wrote and tested it on broadband - but for me who is on a dialup modem v9.1 is totally useless. I've had a "soft" modem connected to my second machine (the one on which everything is tested before being applied on my main computer - this one, the one I'm typing this message on) for over 6 months and I've had no problems with it while running v9.0 was released. I even had no trouble with it when I installed the Mantel kernels of the 2.6.5+ variety. But I install v9.1 and nothing works. To test what was what, I installed an external modem from my one of my other computers - with the same result: 3 hours to download a 1Mb file. Not to be deterred, I went out in the afternoon and bought a new modem - just in case. Same result: VERY, VERY poor thruput. Pathetic is a better description. Anyway, I re-installed v9.0, made sure that all the settings were the same as with v9.1 and - the modem is now "flying", downloading Mozilla (13Mb) at 4.5Kb/s (aver) and without skipping a beat. The other thing- how the heck do you turn-off the damn screen saver? or rather stop the screen from blanking out after some (?)10 minutes or so? With the screen saver turned off the screen blanks - to GREAT annoyance to me - unless something is constantly displayed on the screen. I'll throw another one in. On every previous version of Suse the soundfonts for my sound card (SB Live!) were installed without any hassle during the configuration of the sound card. But not in 9.1. 9.1 informs me that there are no soundfonts to be installed on the CD, yet 9.0 (et alia) can find them. Some weeks ago (23/3 actually) I mentioned that I had purchased a tvtuner card with the Conexant 23x chipset and which v9.0 does not recognise. I wrote to Suse tech and was advised that I needed the 2.6.x default kernel and someone also mentioned that I needed the cx88 driver (or something) but which is still being developed. I installed (on 9.0) the Mantel kernel and got nowhere with having my Winfast DV2000 card recognised and was looking forward to v9.1 because based on the comment from Suse tech I assumed that v9.1 will recognise the card. I am actaully dreading installing the card on the test computer to see if v9.1 does recognise it because I suspect that it won't. Anyone with a tvtuner card with the Conexant 23x chipset tell me if it is recognised by Suse 9.1? Cheers. -- I am not young enough to know everything.
Basil Chupin wrote:
Sorry folks, but to me v9.1 is a damn waste of money, and a pain in the bum to boot.
I was really looking forward to getting 9.1 but now am sorry I got it.
The annoyances may be small (from those I found so far) but nevertheless they point out the lack of quality control of the product.
Firtsly, v9.1 is NOT modem friendly. It may be OK for those using it on broadband - and those who wrote and tested it on broadband - but for me who is on a dialup modem v9.1 is totally useless.
I've had a "soft" modem connected to my second machine (the one on which everything is tested before being applied on my main computer - this one, the one I'm typing this message on) for over 6 months and I've had no problems with it while running v9.0 was released. I even had no trouble with it when I installed the Mantel kernels of the 2.6.5+ variety. But I install v9.1 and nothing works.
To test what was what, I installed an external modem from my one of my other computers - with the same result: 3 hours to download a 1Mb file.
Not to be deterred, I went out in the afternoon and bought a new modem - just in case. Same result: VERY, VERY poor thruput. Pathetic is a better description.
Anyway, I re-installed v9.0, made sure that all the settings were the same as with v9.1 and - the modem is now "flying", downloading Mozilla (13Mb) at 4.5Kb/s (aver) and without skipping a beat.
Oh Boy! The only modem I have working is a PCMCIA one on an x86_64 laptop and that works fine. The internal soft (as in the head) modem does not as it contains a 32-bit module and won't build on 64-bit, tried 32-bit build which failed, but this is early days yet for 64-bit stuff.
The other thing- how the heck do you turn-off the damn screen saver? or rather stop the screen from blanking out after some (?)10 minutes or so? With the screen saver turned off the screen blanks - to GREAT annoyance to me - unless something is constantly displayed on the screen.
I have mine turned on, but I shall try configuring KDE later to see if it obeys the command.
I'll throw another one in.
On every previous version of Suse the soundfonts for my sound card (SB Live!) were installed without any hassle during the configuration of the sound card.
But not in 9.1. 9.1 informs me that there are no soundfonts to be installed on the CD, yet 9.0 (et alia) can find them.
Some weeks ago (23/3 actually) I mentioned that I had purchased a tvtuner card with the Conexant 23x chipset and which v9.0 does not recognise. I wrote to Suse tech and was advised that I needed the 2.6.x default kernel and someone also mentioned that I needed the cx88 driver (or something) but which is still being developed. I installed (on 9.0) the Mantel kernel and got nowhere with having my Winfast DV2000 card recognised and was looking forward to v9.1 because based on the comment from Suse tech I assumed that v9.1 will recognise the card. I am actaully dreading installing the card on the test computer to see if v9.1 does recognise it because I suspect that it won't.
Anyone with a tvtuner card with the Conexant 23x chipset tell me if it is recognised by Suse 9.1?
My Hauppauge tuner card is on Mandrake and it's kept on working through 9.0, 9.1, 9.2 and 10.0 upgrades. I've never tried it on this box as I prefer to watch while I work. There was an update to kernel 2.6.5 for your card, it's included in the kernel.org 2.6.6-mm2 kernel I'm using. One of the first things I do after installing or upgrading is to bin the SuSE kernel and install the latest one from kernel.org, that's how I was able to upgrade my x86_64 laptop and get all the stuff working, including a USB serial port. SuSE kernels sometimes don't have all the stuff I need, so kernel.org ones are preferred, at times the SuSE oned lag a bit behind on support of some hardware, the apps can also be downlevel, so I make wholesale changes after an install or upgrade. The one problem I haven't yet seen a fix for is the php4 not working one, I may try rolling my own php4 install. Regards Sid.
Cheers.
-- Sid Boyce .... Hamradio G3VBV and keen Flyer Linux Only Shop.
Sid Boyce wrote:
Basil Chupin wrote:
Sorry folks, but to me v9.1 is a damn waste of money, and a pain in the bum to boot.
I was really looking forward to getting 9.1 but now am sorry I got it.
The annoyances may be small (from those I found so far) but nevertheless they point out the lack of quality control of the product.
Firtsly, v9.1 is NOT modem friendly. It may be OK for those using it on broadband - and those who wrote and tested it on broadband - but for me who is on a dialup modem v9.1 is totally useless.
I've had a "soft" modem connected to my second machine (the one on which everything is tested before being applied on my main computer - this one, the one I'm typing this message on) for over 6 months and I've had no problems with it while running v9.0 was released. I even had no trouble with it when I installed the Mantel kernels of the 2.6.5+ variety. But I install v9.1 and nothing works.
To test what was what, I installed an external modem from my one of my other computers - with the same result: 3 hours to download a 1Mb file.
Not to be deterred, I went out in the afternoon and bought a new modem - just in case. Same result: VERY, VERY poor thruput. Pathetic is a better description.
Anyway, I re-installed v9.0, made sure that all the settings were the same as with v9.1 and - the modem is now "flying", downloading Mozilla (13Mb) at 4.5Kb/s (aver) and without skipping a beat.
Oh Boy! The only modem I have working is a PCMCIA one on an x86_64 laptop and that works fine. The internal soft (as in the head) modem does not as it contains a 32-bit module and won't build on 64-bit, tried 32-bit build which failed, but this is early days yet for 64-bit stuff.
If, when, you try the 32-bit modem install please let me (us) know of the results.
The other thing- how the heck do you turn-off the damn screen saver? or rather stop the screen from blanking out after some (?)10 minutes or so? With the screen saver turned off the screen blanks - to GREAT annoyance to me - unless something is constantly displayed on the screen.
I have mine turned on, but I shall try configuring KDE later to see if it obeys the command.
Answer provided by Kenneth (in this thread). Simply turning off the screensaver from the Desktop Config is not enough.
I'll throw another one in.
On every previous version of Suse the soundfonts for my sound card (SB Live!) were installed without any hassle during the configuration of the sound card.
But not in 9.1. 9.1 informs me that there are no soundfonts to be installed on the CD, yet 9.0 (et alia) can find them.
Some weeks ago (23/3 actually) I mentioned that I had purchased a tvtuner card with the Conexant 23x chipset and which v9.0 does not recognise. I wrote to Suse tech and was advised that I needed the 2.6.x default kernel and someone also mentioned that I needed the cx88 driver (or something) but which is still being developed. I installed (on 9.0) the Mantel kernel and got nowhere with having my Winfast DV2000 card recognised and was looking forward to v9.1 because based on the comment from Suse tech I assumed that v9.1 will recognise the card. I am actaully dreading installing the card on the test computer to see if v9.1 does recognise it because I suspect that it won't.
Anyone with a tvtuner card with the Conexant 23x chipset tell me if it is recognised by Suse 9.1?
My Hauppauge tuner card is on Mandrake and it's kept on working through 9.0, 9.1, 9.2 and 10.0 upgrades. I've never tried it on this box as I prefer to watch while I work.
In all those versions of Mandrake? I am now thinking that after the current experiences I am having with 9.1, plus the article called SuSE's Frankenstein's monster on The Inquirer site (www.theinquirer.net) it might be time to start thinking, say, Mandrake. I paid $AU98 for 9.1 Pro upgrade while Mandrake 10.0 is $AU18 - and I've spending the big $$$ on every upgrade of SuSE Pro since 7.1. And I (and others from the messages I've just read here) can't get my modem(s) to work! If that is progress then I'm a monkey's uncle.
There was an update to kernel 2.6.5 for your card, it's included in the kernel.org 2.6.6-mm2 kernel I'm using. One of the first things I do after installing or upgrading is to bin the SuSE kernel and install the latest one from kernel.org, that's how I was able to upgrade my x86_64 laptop and get all the stuff working, including a USB serial port. SuSE kernels sometimes don't have all the stuff I need, so kernel.org ones are preferred, at times the SuSE oned lag a bit behind on support of some hardware, the apps can also be downlevel, so I make wholesale changes after an install or upgrade.
Thanks for that, Sid. I'll try the 2.6.6 out. But you know, I, or anyone else, should not have to go thru this rubbish to get something to work on a version of distro which has just been released and with the Conexant 2388x chipset being around for some, what, 12 months? At the least there should be a kernel update to the current one in 9.1 for this chipset.
The one problem I haven't yet seen a fix for is the php4 not working one, I may try rolling my own php4 install.
Ahem. what is "php4"? :-) Cheers. -- I am not young enough to know everything.
The other thing- how the heck do you turn-off the damn screen saver? or rather stop the screen from blanking out after some (?)10 minutes or so? With the screen saver turned off the screen blanks - to GREAT annoyance to me - unless something is constantly displayed on the screen.
It's the X blank/standby/suspend/offtime options that do this. I don't know if there's an elegant SuSE way to take care of this, but I've turned it off using the following X options (in XF86Config): Option "BlankTime" "time" sets the inactivity timeout for the blanking phase of the screensaver. time is in minutes. This is equivalent to the Xserver's `-s' flag, and the value can be changed at run-time with xset(1) . Default: 10 minutes. Option "StandbyTime" "time" sets the inactivity timeout for the "standby" phase of DPMS mode. time is in minutes, and the value can be changed at run-time with xset(1) . Default: 20 minutes. This is only suitable for VESA DPMS compatible monitors, and may not be supported by all video drivers. It is only enabled for screens that have the "DPMS" option set (see the MONITOR section below). Option "SuspendTime" "time" sets the inactivity timeout for the "suspend" phase of DPMS mode. time is in minutes, and the value can be changed at run-time with xset(1) . Default: 30 minutes. This is only suitable for VESA DPMS compatible monitors, and may not be supported by all video drivers. It is only enabled for screens that have the "DPMS" option set (see the MONITOR section below). Option "OffTime" "time" sets the inactivity timeout for the "off" phase of DPMS mode. time is in minutes, and the value can be changed at run-time with xset(1) . Default: 40 minutes. This is only suitable for VESA DPMS compatible monitors, and may not be supported by all video drivers. It is only enabled for screens that have the "DPMS" option set (see the MONITOR section below). Set them all to 0 in your Serverflags Section, and your problem should disappear (after an X reboot of course:). Regards, Pieter Hulshoff
On Mon, 2004-05-17 at 12:46, Pieter Hulshoff wrote:
The other thing- how the heck do you turn-off the damn screen saver? or rather stop the screen from blanking out after some (?)10 minutes or so? With the screen saver turned off the screen blanks - to GREAT annoyance to me - unless something is constantly displayed on the screen.
It's the X blank/standby/suspend/offtime options that do this. I don't know if there's an elegant SuSE way to take care of this, but I've turned it off using the following X options (in XF86Config):
You should also be able to turn this off in the KDE Control Center --> Power Control --> uncheck the box for Enable Display Power Control -- Ken Schneider unix user since 1989 linux user since 1994 SuSE user since 1998 (5.2)
Kenneth Schneider wrote:
On Mon, 2004-05-17 at 12:46, Pieter Hulshoff wrote:
The other thing- how the heck do you turn-off the damn screen saver? or rather stop the screen from blanking out after some (?)10 minutes or so? With the screen saver turned off the screen blanks - to GREAT annoyance to me - unless something is constantly displayed on the screen.
It's the X blank/standby/suspend/offtime options that do this. I don't know if there's an elegant SuSE way to take care of this, but I've turned it off using the following X options (in XF86Config):
You should also be able to turn this off in the KDE Control Center --> Power Control --> uncheck the box for Enable Display Power Control
Thanks, Kenneth, this did the trick. This feature is also in v9.0 but I didn't have to invoke it to stop the screensaver from working so what this means is that SuSE 9.1 has another bug in it. Cheers. -- I am not young enough to know everything.
Pieter Hulshoff wrote:
The other thing- how the heck do you turn-off the damn screen saver? or rather stop the screen from blanking out after some (?)10 minutes or so? With the screen saver turned off the screen blanks - to GREAT annoyance to me - unless something is constantly displayed on the screen.
It's the X blank/standby/suspend/offtime options that do this. I don't know if there's an elegant SuSE way to take care of this, but I've turned it off using the following X options (in XF86Config):
[rest pruned] Thanks for the suggestion. That's what made it all work out -- but, as you would have read, Kenneth had the same solution in a more "efficient" way. Cheers. -- I am not young enough to know everything.
On Monday 17 May 2004 16:44, Basil Chupin wrote:
Sorry folks, but to me v9.1 is a damn waste of money, and a pain in the bum to boot.
I was really looking forward to getting 9.1 but now am sorry I got it.
The annoyances may be small (from those I found so far) but nevertheless they point out the lack of quality control of the product.
Firtsly, v9.1 is NOT modem friendly. It may be OK for those using it on broadband - and those who wrote and tested it on broadband - but for me who is on a dialup modem v9.1 is totally useless.
I've had a "soft" modem connected to my second machine (the one on which everything is tested before being applied on my main computer - this one, the one I'm typing this message on) for over 6 months and I've had no problems with it while running v9.0 was released. I even had no trouble with it when I installed the Mantel kernels of the 2.6.5+ variety. But I install v9.1 and nothing works.
From 9.0 to 9.1 SuSE has apparently dropped the drivers for the Intel-Ambient 536ep pci modem and the Logitech Quickcam. Neither of these is so old as to deserve it! I managed to download and compile the sourceforge driver for the Quickcam, it installs and works fine. I've failed to compile the 536ep source for the modem. Isn't it a backward step for SuSE to drop support like this? There are few enough drivers for Linux as it is! Are there SuSE 9.1 drivers for these hiding somewhere else than the DVDs? Geoff
Geoff Horn wrote:
On Monday 17 May 2004 16:44, Basil Chupin wrote:
Sorry folks, but to me v9.1 is a damn waste of money, and a pain in the bum to boot.
I was really looking forward to getting 9.1 but now am sorry I got it.
The annoyances may be small (from those I found so far) but nevertheless they point out the lack of quality control of the product.
Firtsly, v9.1 is NOT modem friendly. It may be OK for those using it on broadband - and those who wrote and tested it on broadband - but for me who is on a dialup modem v9.1 is totally useless.
I've had a "soft" modem connected to my second machine (the one on which everything is tested before being applied on my main computer - this one, the one I'm typing this message on) for over 6 months and I've had no problems with it while running v9.0 was released. I even had no trouble with it when I installed the Mantel kernels of the 2.6.5+ variety. But I install v9.1 and nothing works.
From 9.0 to 9.1 SuSE has apparently dropped the drivers for the Intel-Ambient 536ep pci modem and the Logitech Quickcam. Neither of these is so old as to deserve it! I managed to download and compile the sourceforge driver for the Quickcam, it installs and works fine. I've failed to compile the 536ep source for the modem. Isn't it a backward step for SuSE to drop support like this? There are few enough drivers for Linux as it is! Are there SuSE 9.1 drivers for these hiding somewhere else than the DVDs?
I could have included this in my original message but then it would have been too long and possibly with too much detail but- the internal modems I have use the Conexant chipset(s) so the drivers for them are available from linuxant.com. One of the modems is an HCF PCI modem. I've had it now for some 5 years and it performs faultlessly (outperforms some of the external modems I've owned/own). The other is el-cheapo HSF PCI modem (and this is the modem under discussion here) which I've been using without a hitch on SuSE 9.0 for some 7 months- until v9.1. Linuxant.com actually have the new driver for it to suit the kernel in SuSE 9.1 but I don't know how Linuxant ever got it to work on 9.1 because there is no way it will work here. And I have just re-installed 9.1 again today just to re-check my earlier results. They also have the generic driver which you compile to suit the kernel you have installed but the same thing happens as with the pre-compiled driver: no entry in /dev is created for the modem and so the modem is not recognised. On v9.0 I was running kernel 2.6.5-73 and had absolutely no problems with the modem after compiling the generic driver for this kernel. Cheers. -- I am not young enough to know everything.
I agree the 9.1 boot issue is a disaster. I am finally up and running as you can see from various messages here: After 4 days and a new hard drive as well as many cancelled appointments. Summary of pain: 1. was not able to boot into windows 2. Tried every single MBR recovery know to man. 3. Tried to repair Windows. 4. Had to format and start over. 5. New hard drive changed to lilo. 6. install missed many files 7. reinstall 8. reinstall 9. Could not update linux partition not found. 10. Yast tries to install updates on windows partition. (sorry I'm getting some steam off my chest) On Wednesday 19 May 2004 09:55, Basil Chupin wrote:
Geoff Horn wrote:
On Monday 17 May 2004 16:44, Basil Chupin wrote:
Sorry folks, but to me v9.1 is a damn waste of money, and a pain in the bum to boot.
I was really looking forward to getting 9.1 but now am sorry I got it.
The annoyances may be small (from those I found so far) but nevertheless they point out the lack of quality control of the product.
Firtsly, v9.1 is NOT modem friendly. It may be OK for those using it on broadband - and those who wrote and tested it on broadband - but for me who is on a dialup modem v9.1 is totally useless.
I've had a "soft" modem connected to my second machine (the one on which everything is tested before being applied on my main computer - this one, the one I'm typing this message on) for over 6 months and I've had no problems with it while running v9.0 was released. I even had no trouble with it when I installed the Mantel kernels of the 2.6.5+ variety. But I install v9.1 and nothing works.
From 9.0 to 9.1 SuSE has apparently dropped the drivers for the Intel-Ambient 536ep pci modem and the Logitech Quickcam. Neither of these is so old as to deserve it! I managed to download and compile the sourceforge driver for the Quickcam, it installs and works fine. I've failed to compile the 536ep source for the modem. Isn't it a backward step for SuSE to drop support like this? There are few enough drivers for Linux as it is! Are there SuSE 9.1 drivers for these hiding somewhere else than the DVDs?
I could have included this in my original message but then it would have been too long and possibly with too much detail but- the internal modems I have use the Conexant chipset(s) so the drivers for them are available from linuxant.com.
One of the modems is an HCF PCI modem. I've had it now for some 5 years and it performs faultlessly (outperforms some of the external modems I've owned/own). The other is el-cheapo HSF PCI modem (and this is the modem under discussion here) which I've been using without a hitch on SuSE 9.0 for some 7 months- until v9.1.
Linuxant.com actually have the new driver for it to suit the kernel in SuSE 9.1 but I don't know how Linuxant ever got it to work on 9.1 because there is no way it will work here. And I have just re-installed 9.1 again today just to re-check my earlier results.
They also have the generic driver which you compile to suit the kernel you have installed but the same thing happens as with the pre-compiled driver: no entry in /dev is created for the modem and so the modem is not recognised.
On v9.0 I was running kernel 2.6.5-73 and had absolutely no problems with the modem after compiling the generic driver for this kernel.
Cheers.
-- I am not young enough to know everything.
-- Thom Nuzum Realtor technology (DC, Virginia, and Maryland)
Hi, On Wednesday 19 May 2004 16:46, Thom Nuzum wrote:
I agree the 9.1 boot issue is a disaster. I am finally up and running as you can see from various messages here: After 4 days and a new hard drive as well as many cancelled appointments. Summary of pain: 1. was not able to boot into windows 2. Tried every single MBR recovery know to man. 3. Tried to repair Windows. 4. Had to format and start over. 5. New hard drive changed to lilo. 6. install missed many files 7. reinstall 8. reinstall 9. Could not update linux partition not found. 10. Yast tries to install updates on windows partition. (sorry I'm getting some steam off my chest)
Since today we have a machine at hand where we can reproduce the problem. It appears to be some kind of "misunderstanding" between what Windows, BIOS and Kernel 2.6 assume about disk geometry. It doesn't look like an easy one. But at least we have a chance now ... Stay tuned. Greetings from Bremen hartmut
*** Reply to message from Hartmut Meyer
Since today we have a machine at hand where we can reproduce the problem. It appears to be some kind of "misunderstanding" between what Windows, BIOS and Kernel 2.6 assume about disk geometry. It doesn't look like an easy one. But at least we have a chance now ...
Stay tuned.
Hartmut, Does your test computer ,which reproduces the errors Thom Numzum is reporting.. once it's solved. Or on the chance the "misunderstanding " of the Windows ,Bios, and it could be a partial cure for a problem w/ a desktop. The computer itself is and Emachine T2842.With 2.8gig Celeron ; 512 megs ddr2700 or (2100?) ram and an addittion we made was a pci video card, and S3 Virge dx . The problem we have had w/ this box is the live evaluation disk hangs just after it appears to have located the usb items (Intelliflash USB 6 in 1 flash card reader etc.) once it gets to the check point of the pcmcia card(s) that we do not have. It never gets past that point, and the worry would be it might do the same on an install.. So questions.. one) could the computer restore itself to a more desireable state? Or would an install result in a *stop*( commplete lock/freeze/nothing is going to EVER! move) during an install ( of the full pro version. I bought it for my daughter and also got a 9.1 UG for myself and our office consulting team. Since Mr. Nuzum's appears to have installed okay. Which leads to question two: Will the full pro volume install on that emachine , w/ it equipped as described above? Ttheuser having that machine is having panicy 2nd thoughts about the whole idea of updating his box. I have even shown him an older E-machine out of similar materiels And it is chugging along nicely. There have been no updates; and no other OS on it. So, for the time being I am putting him on a machine which installed from the pro discs and there were no prroblems in attemmpting the full Pro install and the newer vesion of the Crossover Office, which he has used for about as long as he has used Linux. I have read most of the readmes. And evenn scimmed thru the database of kknown problems and don't see it reported. Any suggestions? TIA, jfweber -- j -- nemo me impune lacessit it's just an afterthought; okay ? : Life is a riddle; unfortunately the answer's not written on the back of anything.
Hi, On Tuesday 18 May 2004 22:06, jfweber@bellsouth.net wrote: ^^^^^ Your date is wrong (24 hours back). Also there was something wrong with your "To:" line: mailing@suse.de, list@suse.de, suse-linux-e@suse.com
Does your test computer ,which reproduces the errors Thom Numzum is reporting.. once it's solved.
I don't understand this sentence.
Or on the chance the "misunderstanding " of the Windows ,Bios, and it could be a partial cure for a problem w/ a desktop.
This one I don't understand either. Are you trying to ask whether or not the described dual boot problem is related to the issues that you have yourself (described below)?
The computer itself is and Emachine T2842.With 2.8gig Celeron ; 512 megs ddr2700 or (2100?) ram and an addittion we made was a pci video card, and S3 Virge dx .
The problem we have had w/ this box is the live evaluation disk hangs just after it appears to have located the usb items (Intelliflash USB 6 in 1 flash card reader etc.) once it gets to the check point of the pcmcia card(s) that we do not have. It never gets past that point, and the worry would be it might do the same on an install..
So questions..
one) could the computer restore itself to a more desireable state? Or would an install result in a *stop*( commplete lock/freeze/nothing is going to EVER! move) during an install ( of the full pro version.
I'm not sure I understand this question correctly. But yes, those problems should be solvable (if they show up on a real installation). First thing to try if any problems show up is the installation option "installation - safe settings" from the boot menu of the installation media.
Which leads to question two:
Will the full pro volume install on that emachine , w/ it equipped as described above?
I would expect so. The described dual boot problem does effect only a minority of users/systems. Greetings from Bremen hartmut
*** Reply to message from Hartmut Meyer
Your date is wrong (24 hours back). Also there was something wrong with your "To:" line:
mailing@suse.de, list@suse.de, suse-linux-e@suse.com
Ohhhh boy, Well, where to start. When I wrote this I shouldn't have been allowed near a computer or anything w/ sharp edges, or wheels and an engine. I hadn't' slept at all in a couple of days, and although I kept intending to go home to sleep, things that just had to be attended right that minute kept intruding, as they will. I suspect the first part was at least partially written by my face hitting the keyboard (heavy sigh) So covered w/ embarrassment, I try again to explain my problem. Your discussion w/ Thom Numzum , reminded me of one problem I had had while demonstrating the Live Evaluation CD , the one that comes w/ Suse Personal, which I had bought for my daughter.
This one I don't understand either. Are you trying to ask whether or not the described dual boot problem is related to the issues that you have yourself (described below)?
yes, sadly, I was. The machine is as described, and it is happily running 9.0 but user wishes to take advantage of the new kernal. You however, in spite of my somewhat quixotic language managed to winkle out the questions and answer them.. Now If I could only get my own computer to obey the instructions to check the time daily, it *should* also keep my date in check. I do apologized for the headache I must have caused you as you did manage to puzzle out my problem... I shall send some (good) Karma points to your account immediately. Thank you , I really am greatful. I can now finish up the conversion of this office to Suse9.1 jfweber -- j -- nemo me impune lacessit it's just an afterthought; okay ? : Poverty is the root of all evil.
Hi, On Friday 21 May 2004 01:38, jfweber@bellsouth.net wrote:
Ohhhh boy,
Well, where to start. When I wrote this I shouldn't have been allowed near a computer or anything w/ sharp edges, or wheels and an engine. I hadn't' slept at all in a couple of days, and although I kept intending to go home to sleep, things that just had to be attended right that minute kept intruding, as they will. I suspect the first part was at least partially written by my face hitting the keyboard (heavy sigh)
So covered w/ embarrassment, I try again to explain my problem.
Much better now ;-)
Now If I could only get my own computer to obey the instructions to check the time daily, it *should* also keep my date in check.
Easy (at least with 9.1). I assume you have a dial-up connection, right? If so everything is prepared for you: the script /etc/ppp/poll.tcpip is already prepeared to take care of it (it get's called each time you dial in to your ISP): --- snip ----- [...] # # Now set system time if we have some NTP servers # and no running xntp. # while true ; do set -- $(/sbin/runlevel) test -e /etc/init.d/rc${2}.d/S*xntpd && break test -x /usr/sbin/ntpdate || break checkproc /usr/sbin/xntpd &> /dev/null && break /usr/sbin/rcxntpd ntptimeset break done [...] --- snip ----- Now, all you have to do is to edit your /etc/ntp.conf and add a server line like this: --- snip ----- ## Outside source of synchronized time ## ## server xx.xx.xx.xx # IP address of server server 129.217.131.3 # ntp1.hrz.uni-dortmund.de --- snap ----- Don't take the server from my example (doesn't make sense for you) but pick one from http://www.eecis.udel.edu/~mills/ntp/servers.html *Don't* activate xntp as a service. Just edit the /etc/ntp.conf file and that sould be it. To check if the server is working for you do ntpdate 129.217.131.3 and see the result (of course: again choose your server). Greetings from Bremen hartmut
I spoke too soon. On my fourth boot into Windows I have lost my Boot Loader completely and what followed was an awful clicking sound and a boot into SuSE. My system bios now flashes around like crazy opening and closing things. My hard drive is new so I can return it. I suspect it is finished. Can anyone recommend a workable hard drive if thats my problem. Mine was a Maxtor 250GB (they were on sale and had the Novell stamp of approval) very funny. On Wednesday 19 May 2004 13:46, Hartmut Meyer wrote:
Hi,
On Wednesday 19 May 2004 16:46, Thom Nuzum wrote:
I agree the 9.1 boot issue is a disaster. I am finally up and running as you can see from various messages here: After 4 days and a new hard drive as well as many cancelled appointments. Summary of pain: 1. was not able to boot into windows 2. Tried every single MBR recovery know to man. 3. Tried to repair Windows. 4. Had to format and start over. 5. New hard drive changed to lilo. 6. install missed many files 7. reinstall 8. reinstall 9. Could not update linux partition not found. 10. Yast tries to install updates on windows partition. (sorry I'm getting some steam off my chest)
Since today we have a machine at hand where we can reproduce the problem. It appears to be some kind of "misunderstanding" between what Windows, BIOS and Kernel 2.6 assume about disk geometry. It doesn't look like an easy one. But at least we have a chance now ...
Stay tuned.
Greetings from Bremen hartmut
-- Thom Nuzum Realtor technology (DC, Virginia, and Maryland)
* Thom Nuzum (linux@tendata.com) [040519 16:50]:
I spoke too soon. On my fourth boot into Windows I have lost my Boot Loader completely and what followed was an awful clicking sound and a boot into SuSE. My system bios now flashes around like crazy opening and closing things. My hard drive is new so I can return it. I suspect it is finished. Can anyone recommend a workable hard drive if thats my problem. Mine was a Maxtor 250GB (they were on sale and had the Novell stamp of approval) very funny.
But that was for Netware. If you want to use SUSE then you have to choose Seagate. ;) I refuse to buy Maxtors after I had 3 die on me in a 6 month period. I avoid them if possible. -- "There is no need to teach that stars can fall out of the sky and land on a flat Earth in order to defend religious faith."
Thanks Ben, Well I rebooted a couple of times and I am back in Windows with no clicking sound. I think I will keep rebooting until something goes, but will exchange it Tomorrow anyway: i don't know what else the sound could have been.
* Thom Nuzum (linux@tendata.com) [040519 16:50]:
I spoke too soon. On my fourth boot into Windows I have lost my Boot Loader completely and what followed was an awful clicking sound and a boot into SuSE. My system bios now flashes around like crazy opening and closing things. My hard drive is new so I can return it. I suspect it is finished. Can anyone recommend a workable hard drive if thats my problem. Mine was a Maxtor 250GB (they were on sale and had the Novell stamp of approval) very funny.
But that was for Netware. If you want to use SUSE then you have to choose Seagate. ;)
I refuse to buy Maxtors after I had 3 die on me in a 6 month period. I avoid them if possible.
-- "There is no need to teach that stars can fall out of the sky and land on a flat Earth in order to defend religious faith."
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Wednesday 19 May 2004 20:31, Thom Nuzum wrote:
Thanks Ben, Well I rebooted a couple of times and I am back in Windows with no clicking sound. I think I will keep rebooting until something goes, but will exchange it Tomorrow anyway: i don't know what else the sound could have been.
* Thom Nuzum (linux@tendata.com) [040519 16:50]:
I spoke too soon. On my fourth boot into Windows I have lost my Boot Loader completely and what followed was an awful clicking sound and a boot into SuSE. My system bios now flashes around like crazy opening and closing things. My hard drive is new so I can return it. I suspect it is finished. Can anyone recommend a workable hard drive if thats my problem. Mine was a Maxtor 250GB (they were on sale and had the Novell stamp of approval) very funny.
But that was for Netware. If you want to use SUSE then you have to choose Seagate. ;)
I refuse to buy Maxtors after I had 3 die on me in a 6 month period. I avoid them if possible.
/snip/ All hd's fail sooner or later. I've had better luck with IBM than any others, over a period of maybe 15 years of hd's, but one of my IBM SCSI's just died. It was maybe 7 years old, at most. Of course, it was the one that had Linux on it. This machine is running SuSE 9.1 and MSW on IBM EIDE's. My first EIDE's in a long time, and I have no history for them. The machine is new. --doug
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 19 May 2004 18:48, Thom Nuzum wrote:
I spoke too soon. On my fourth boot into Windows I have lost my Boot Loader completely and what followed was an awful clicking sound and a boot into SuSE. My system bios now flashes around like crazy opening and closing things. My hard drive is new so I can return it. I suspect it is finished. Can anyone recommend a workable hard drive if thats my problem. Mine was a Maxtor 250GB (they were on sale and had the Novell stamp of approval) very funny.
On Wednesday 19 May 2004 13:46, Hartmut Meyer wrote:
Hi,
On Wednesday 19 May 2004 16:46, Thom Nuzum wrote:
I agree the 9.1 boot issue is a disaster. I am finally up and running as you can see from various messages here: After 4 days and a new hard drive as well as many cancelled appointments. Summary of pain: 1. was not able to boot into windows 2. Tried every single MBR recovery know to man. 3. Tried to repair Windows. 4. Had to format and start over. 5. New hard drive changed to lilo. 6. install missed many files 7. reinstall 8. reinstall 9. Could not update linux partition not found. 10. Yast tries to install updates on windows partition. (sorry I'm getting some steam off my chest)
Since today we have a machine at hand where we can reproduce the problem. It appears to be some kind of "misunderstanding" between what Windows, BIOS and Kernel 2.6 assume about disk geometry. It doesn't look like an easy one. But at least we have a chance now ...
Stay tuned.
Greetings from Bremen hartmut
-- Thom Nuzum Realtor technology (DC, Virginia, and Maryland) I had trouble w/a couple Maxtors... I like Seagate, myself.
...CH Avoid doing business with 'The Link' ISP. SuSE Is All U Need Linux user# 313696 Linux box# 199365 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFArAfP1rD/PgIdojIRAiT7AKChd1uRjvcCnIsmyy/QPIEqkvw5TgCfSKsm nYksxK26Qu1ycr20mgs04Aw= =eJ+Y -----END PGP SIGNATURE-----
On Wednesday May 19 2004 7:48 pm, Thom Nuzum wrote:
I spoke too soon. On my fourth boot into Windows I have lost my Boot Loader completely and what followed was an awful clicking sound and a boot into SuSE. My system bios now flashes around like crazy opening and closing things. My hard drive is new so I can return it. I suspect it is finished. Can anyone recommend a workable hard drive if thats my problem. Mine was a Maxtor 250GB (they were on sale and had the Novell stamp of approval) very funny.
NEITHER Linux nor 'Bloze caused the demise of your hard drive! Fred -- "The only secure Microsoft software is what's still shrink-wrapped in their warehouse..." (Forno)
Thom Nuzum wrote:
I agree the 9.1 boot issue is a disaster. I am finally up and running as you can see from various messages here: After 4 days and a new hard drive as well as many cancelled appointments. Summary of pain: 1. was not able to boot into windows 2. Tried every single MBR recovery know to man. 3. Tried to repair Windows. 4. Had to format and start over. 5. New hard drive changed to lilo. 6. install missed many files 7. reinstall 8. reinstall 9. Could not update linux partition not found. 10. Yast tries to install updates on windows partition. (sorry I'm getting some steam off my chest)
On Wednesday 19 May 2004 09:55, Basil Chupin wrote:
Geoff Horn wrote:
On Monday 17 May 2004 16:44, Basil Chupin wrote:
Sorry folks, but to me v9.1 is a damn waste of money, and a pain in the bum to boot.
I was really looking forward to getting 9.1 but now am sorry I got it.
The annoyances may be small (from those I found so far) but nevertheless they point out the lack of quality control of the product.
Firtsly, v9.1 is NOT modem friendly. It may be OK for those using it on broadband - and those who wrote and tested it on broadband - but for me who is on a dialup modem v9.1 is totally useless.
I've had a "soft" modem connected to my second machine (the one on which everything is tested before being applied on my main computer - this one, the one I'm typing this message on) for over 6 months and I've had no problems with it while running v9.0 was released. I even had no trouble with it when I installed the Mantel kernels of the 2.6.5+ variety. But I install v9.1 and nothing works.
From 9.0 to 9.1 SuSE has apparently dropped the drivers for the Intel-Ambient 536ep pci modem and the Logitech Quickcam. Neither of these is so old as to deserve it! I managed to download and compile the sourceforge driver for the Quickcam, it installs and works fine. I've failed to compile the 536ep source for the modem. Isn't it a backward step for SuSE to drop support like this? There are few enough drivers for Linux as it is! Are there SuSE 9.1 drivers for these hiding somewhere else than the DVDs?
I could have included this in my original message but then it would have been too long and possibly with too much detail but- the internal modems I have use the Conexant chipset(s) so the drivers for them are available from linuxant.com.
One of the modems is an HCF PCI modem. I've had it now for some 5 years and it performs faultlessly (outperforms some of the external modems I've owned/own). The other is el-cheapo HSF PCI modem (and this is the modem under discussion here) which I've been using without a hitch on SuSE 9.0 for some 7 months- until v9.1.
Linuxant.com actually have the new driver for it to suit the kernel in SuSE 9.1 but I don't know how Linuxant ever got it to work on 9.1 because there is no way it will work here. And I have just re-installed 9.1 again today just to re-check my earlier results.
They also have the generic driver which you compile to suit the kernel you have installed but the same thing happens as with the pre-compiled driver: no entry in /dev is created for the modem and so the modem is not recognised.
On v9.0 I was running kernel 2.6.5-73 and had absolutely no problems with the modem after compiling the generic driver for this kernel.
Cheers.
HIJACKER! :-) I started a thread re the modem and the tvtuner card plus one or 2 other things and nowhere do I, or anyone responding to me to this point, mention anything about boot problems and "lost" linux partitions. Now of course this thread is talking about HD geometry! So, to whose message were you replying? :-) I think this points out the problem with top-posting replies to messages. Cheers. -- I am not young enough to know everything.
sorry I could not get back to my thread having lost my mail and hard drive and BAH! seemed as obscure as any.
Thom Nuzum wrote:
I agree the 9.1 boot issue is a disaster. I am finally up and running as you can see from various messages here: After 4 days and a new hard drive as well as many cancelled appointments. Summary of pain: 1. was not able to boot into windows 2. Tried every single MBR recovery know to man. 3. Tried to repair Windows. 4. Had to format and start over. 5. New hard drive changed to lilo. 6. install missed many files 7. reinstall 8. reinstall 9. Could not update linux partition not found. 10. Yast tries to install updates on windows partition. (sorry I'm getting some steam off my chest)
On Wednesday 19 May 2004 09:55, Basil Chupin wrote:
Geoff Horn wrote:
On Monday 17 May 2004 16:44, Basil Chupin wrote:
Sorry folks, but to me v9.1 is a damn waste of money, and a pain in the bum to boot.
I was really looking forward to getting 9.1 but now am sorry I got it.
The annoyances may be small (from those I found so far) but nevertheless they point out the lack of quality control of the product.
Firtsly, v9.1 is NOT modem friendly. It may be OK for those using it on broadband - and those who wrote and tested it on broadband - but for me who is on a dialup modem v9.1 is totally useless.
I've had a "soft" modem connected to my second machine (the one on which everything is tested before being applied on my main computer - this one, the one I'm typing this message on) for over 6 months and I've had no problems with it while running v9.0 was released. I even had no trouble with it when I installed the Mantel kernels of the 2.6.5+ variety. But I install v9.1 and nothing works.
From 9.0 to 9.1 SuSE has apparently dropped the drivers for the Intel-Ambient 536ep pci modem and the Logitech Quickcam. Neither of these is so old as to deserve it! I managed to download and compile the sourceforge driver for the Quickcam, it installs and works fine. I've failed to compile the 536ep source for the modem. Isn't it a backward step for SuSE to drop support like this? There are few enough drivers for Linux as it is! Are there SuSE 9.1 drivers for these hiding somewhere else than the DVDs?
I could have included this in my original message but then it would have been too long and possibly with too much detail but- the internal modems I have use the Conexant chipset(s) so the drivers for them are available from linuxant.com.
One of the modems is an HCF PCI modem. I've had it now for some 5 years and it performs faultlessly (outperforms some of the external modems I've owned/own). The other is el-cheapo HSF PCI modem (and this is the modem under discussion here) which I've been using without a hitch on SuSE 9.0 for some 7 months- until v9.1.
Linuxant.com actually have the new driver for it to suit the kernel in SuSE 9.1 but I don't know how Linuxant ever got it to work on 9.1 because there is no way it will work here. And I have just re-installed 9.1 again today just to re-check my earlier results.
They also have the generic driver which you compile to suit the kernel you have installed but the same thing happens as with the pre-compiled driver: no entry in /dev is created for the modem and so the modem is not recognised.
On v9.0 I was running kernel 2.6.5-73 and had absolutely no problems with the modem after compiling the generic driver for this kernel.
Cheers.
HIJACKER!
:-)
I started a thread re the modem and the tvtuner card plus one or 2 other things and nowhere do I, or anyone responding to me to this point, mention anything about boot problems and "lost" linux partitions. Now of course this thread is talking about HD geometry!
So, to whose message were you replying? :-)
I think this points out the problem with top-posting replies to messages.
Cheers.
-- I am not young enough to know everything.
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
participants (12)
-
Basil Chupin -
Ben Rosenberg -
C Hamel -
Doug McGarrett -
Fred Miller -
Geoff Horn -
Hartmut Meyer -
jfweber＠bellsouth.net -
Kenneth Schneider -
Pieter Hulshoff -
Sid Boyce -
Thom Nuzum