December 2005 - openSUSE Users - openSUSE Mailing Lists

R: Re: [SLE] XP strange behaviour after SUSE install
by ferdybassi＠tin.it 28 Dec '05

28 Dec '05

Update to my problem. It is not a AVG problem, since I restored a ghost image of WIndows XP "clean" (IE: XP + drivers only) and it doesn't boot. Ghost and Drive Image tell me that my HD has some partitions with some errors on some sectors. They aren't hardware errors: following what Drive Image says, there is some mistmatch between LBA and CHS (what is it?) numbers. It offers to repair them. After repairing Windows boots again. NOTE: if I use MS-DOS fdisk I see a 57 GB HD, if I use a linux fdisk I see a 55 GB HD... Is it correct or do I have to tweak something? So my new question is: what does in the hell SUSE 10 do to partitions? I've read somewhere in the web that Fedora Core 4 too is affected by this... Is there any way to avoid this? Does it depend from my hard disk? PS: Someone told me that this is not the right place to discuss about that. I apologise I post my question here, but I though it was (and it is) somehow related to SUSE installation.. Ferdinando ----Messaggio originale---- Da: kevanf1(a)gmail.com Data: 28- dic-2005 6.44 PM A: "suse-linux-e(a)suse.com"<suse-linux-e(a)suse.com> Ogg: Re: [SLE] XP strange behaviour after SUSE install Try booting into safe mode in Win XP and then making sure the auto update is off for AVG. I think it might be trying to update at system start up which can cause lock ups. I've used AVG for years on Win tins and it is the best bar none MS environment anti-virus software that you can get. So, with this in mind, I would hesitate at uninstalling AVG, it really is a great friend to have installed. -- ============================================== I am only human, please forgive me if I make a mistake it is not deliberate. ============================================== Take care this Xmas. PLEASE DON'T drink and drive. Kevan Farmer Linux user #373362 Cheslyn Hay Staffordshire WS6 7HR -- 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(a)suse.com

2 1

new to Suse ? [opensuse 10.0]
by Mehmet Fatih AKBULUT 28 Dec '05

28 Dec '05

hi all, i installed opensuse 10.0 for the first time. [new to suse but used to use linux distros for some time.] and have some questions to ask. and i wonder if there's something similar as apt-get of debian or yum of fedora ? and i skipped the package selection part during installation and now want to install openoffice. how can i achieve this ? help me please. regards, bye.

3 2

postfix and Authenticated SMTP
by Andre Truter 28 Dec '05

28 Dec '05

I have a SuSE 9.3 server set up as a mail server. postfix is set up to relay mail with authenticated smtp. I run SUSE 10 on my laptop with Evolution as Mail client. If I set up Evolution to send mail via the SuSE 9.3 box with authentcated smtp, then it works fine. The 9.3 box accepts the mail and relay it. But, I have also set up postfix on the laptop to use the 9.3 box as a relay with AUTH-SMTP, but it seems that postfix on the laptop do not use that. It tries to pass the mail on without authentication. THe 9.3 box bounce the mail. If I set up postfix to relay via another mail server with AUTH-SMTP, it works. Any ideas what could be wrong? THanks -- Andre Truter | Software Engineer | Registered Linux user #185282 ICQ #40935899 | AIM: trusoftzaf | http://www.trusoft.za.org ~ A dinosaur is a salamander designed to Mil Spec ~

2 1

yahoodsl
by Robert 28 Dec '05

28 Dec '05

Hi all When I tried and set up my mother's yahoosbc dsl, not knowing what I was doing I tried to do it with dhcp and my have set it in a loop for now she can not got to Yahoo.com or anywhere on Yahoo. Even when I got there dns numbers and entered them got there but then non of the links on the site work. Even when I do a google search and find Yahoo there all links fail with cannot find Yahoo. Thanks Robert

1 0

RE: [SLE] Problems with initrd after mkinitrd
by Patrick Freeman 28 Dec '05

28 Dec '05

> -----Original Message----- > From: Carl Hartung [mailto:suselinux@cehartung.com] <snip> > As I'm sure you're aware ;-) roughly a minute after you posted this, > Patrick > wrote that he meant "sector 2082" and not "cylinder." (I'm not convinced, > however, that /he's/ convinced, so I'm afraid we'll both have to stay > tuned...) Ok so I looked -- that is cylinder 2082 (sorry about being a dolt but I have a tendancy to *fuzz* up that which I don't absolutely need to know after I've checked it out -- all I really knew, was that there should be no issues with BIOS access to the disk. I appreciate your gentle nudges, however, instead of calling me an idiot (which might have been warranted here). I am very interested in what you had said in another post about C,H,S being defaulted in the BIOS, I am going to look through the Intel docs on this to see if there is any reference. [after looking: this document: ftp://download.intel.com/support/motherboards/server/se7520bd2/sb/se7520 bd2_server_board_tps_r23.pdf on page 62 indicates that LBA is the default in the BIOS for devices that support it]. <snip> > I don't know that Patrick was actually /using/ fdisk, only that sectors > are a > natural metric for partitioning drives that use LBA. Yes, I was using fdisk, but I had long since memorized the number for scripts or hand editing, and hadn't looked at it in a while -- here is an 'fdisk -l /dev/hda' for the curious: Disk /dev/hda: 40.0 GB, 40007761920 bytes 16 heads, 63 sectors/track, 77520 cylinders Units = cylinders of 1008 * 512 = 516096 bytes Device Boot Start End Blocks Id System /dev/hda1 1 2081 1048792+ 82 Linux swap / Solaris /dev/hda2 * 2082 77520 38021256 83 Linux <snip> > - One, less frequent, is the failure of some of the cloned drives to boot > immediately after they've been created and installed. He is presently > overcoming this 'flavor' of boot failure by reinstalling Grub. Correct. > - The second 'flavor,' which is occurring more frequently, is a failure to > boot after modifying the normally running system and creating a new initrd > (with mkinitrd.) IOW, these cloned drives have /not/ failed to boot, > initially, and the systems have been running normally for some time. Then, > after installing updates, he's run mkinitrd and the systems suddenly fail > to > boot. He is presently overcoming this 'flavor' by tarring up the drive > contents, repartitioning the drive and restoring the contents. Correct. > In both cases, the boot failures are occurring *only* on the drives that > have > been cloned. He is not experiencing either type of boot failure in those > systems where the drives have been installed raw and the systems have been > built and upgraded from scratch. I'm sorry -- I haven't been clear enough. The second flavor occurs on *all* drives after updates (where *all* means that the sample set can be of either type (fresh-install or imaged) and produces the same 30%ish hang rate after mkinitrd). I've sort of been thinking-out-loud in these posts -- and in the process have been a bit confusing -- I apologize. Some posts have made me realize I didn't think about some thing or another, and so I look back at it -- I think the response was to the thought that there might be a some kind of problem with BIOS accessing the drive so -- I assumed that fresh installs are going to write near the front of the disk first and subsequent updates would potentially get written elsewhere. Then I later remembered that the partition started at cylinder 2082 (but then confused cylinder and sector) and continued to be perplexed. So my state at that point was: I thought that the description of the problem (BIOS not able to read part of the disk where the initrd resides) fit very well with the behavior I was seeing, even though I *knew* that that particular problem *shouldn't* affect me and thus came to the same hypothesis that Carlos did, which was: That some potentially *unknown* BIOS problem that causes part of the disk to not be accessible might be the issue. The main behavior is intermittent, and while it could be hardware related (BTW WD recommended us not to use the drive because the drive was designed for a desktop (not server) duty cycle). Subsequent updates on drives that hung previously sometimes hang and sometimes do not. In my swamped-ness, I have looked now and again at *what* I was doing and could find no *reason*. The most recent hang was due to an updated xfs driver -- a minor modification of the source that we made in house and compiled on a different machine. The module loads fine on a running system and in this case was updated in the initrd without issue on 2 out of 5 machines. <snip> > But he is building new systems using contemporary components that support > Logical Block Addressing. As I understand it, these systems should have no > difficulty booting from any location on a 40GB disk. Exactly why I hadn't considered BIOS to be at issue. > I agree that the BIOS limitation you're alluding to is still a common > problem, > but I think it only concerns older hardware than what Patrick is dealing > with. I am increasingly confident that the error lies somewhere in the > realm > of drive address calculations and/or translations. What you state here (about calculations/translations), could explain the problem quite nicely (and actually, I think, is a great fit for what Carlos is saying). > That is /my/ educated guess. I am still thinking about ways to test the > drives > for proof, though. Any ideas? I have the used blocks ( -D ) output from debugreiserfs from both a working and a hung system. I think it has enough information to tell what part of the filesystem the initrd is in -- I am not sure if it indicates the LBA sectors. If it does, I will be able to glean that in a *very* tedious process. But this still wouldn't answer your question, I think, since it wouldn't tell us if the BIOS can properly address and read those blocks. So, I am curious, too (but I am also very grateful for the help I have already received and do not want to appear greedy). <snip> Thanks, Patrick

3 2

Gnome. right click send to
by Moby 28 Dec '05

28 Dec '05

How does one change the right click "Send To" option in the Gnome file manager? Any time I go into the file manager, right click a file, and choose "Send to", it wants to open evolution. I would like for it to use Thunderbird, how would I set about changing this? Thanks in advance for any help, -- --Moby They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -- Benjamin Franklin First they came for the Jews and I did not speak out because I was not a Jew. Then they came for the Communists and I did not speak out because I was not a Communist. Then they came for the trade unionists and I did not speak out because I was not a trade unionist. Then they came for me and there was no one left to speak out for me. -- Pastor Martin Niemöller

2 2

Re: [SLE] R: Re: [SLE] XP strange behaviour after SUSE install
by Clint Tinsley 28 Dec '05

28 Dec '05

Sounds to me like there was a partition table error for whatever reason and Drive Image fixed that (PartitionMagic would do also, Question is would QTParted?). LBA (Large Block Addressing) is the bios parameters and they didn't match up with Cylinders/Heads/Sectors (CHS) being reported in the partition table. Did Grub survive all this and you are able to dual boot both Windoze and SuSE? It is a hardware issue more than a SuSE problem. ----- Original Message ----- From: "ferdybassi(a)tin.it" <ferdybassi(a)tin.it> To: suse-linux-e(a)suse.com Subject: [SLE] R: Re: [SLE] XP strange behaviour after SUSE install Date: Wed, 28 Dec 2005 19:43:21 +0100 (GMT+01:00) > > Update to my problem. > It is not a AVG problem, since I restored a ghost > image of WIndows XP "clean" (IE: XP + drivers only) and it doesn't > boot. Ghost and Drive Image tell me that my HD has some partitions with > some errors on some sectors. They aren't hardware errors: following > what Drive Image says, there is some mistmatch between LBA and CHS > (what is it?) numbers. It offers to repair them. After repairing > Windows boots again. > NOTE: if I use MS-DOS fdisk I see a 57 GB HD, if I > use a linux fdisk I see a 55 GB HD... Is it correct or do I have to > tweak something? > So my new question is: what does in the hell SUSE 10 > do to partitions? > I've read somewhere in the web that Fedora Core 4 too > is affected by this... > Is there any way to avoid this? > Does it depend > from my hard disk? > > PS: Someone told me that this is not the right > place to discuss about that. I apologise I post my question here, but I > though it was (and it is) somehow related to SUSE installation.. > > Ferdinando > > ----Messaggio originale---- > Da: kevanf1(a)gmail.com > Data: 28- > dic-2005 6.44 PM > A: "suse-linux-e(a)suse.com"<suse-linux-e(a)suse.com> > Ogg: > Re: [SLE] XP strange behaviour after SUSE install > > Try booting into > safe mode in Win XP and then making sure the auto > update is off for > AVG. I think it might be trying to update at system > start up which can > cause lock ups. I've used AVG for years on Win > tins and it is the best > bar none MS environment anti-virus software > that you can get. So, with > this in mind, I would hesitate at > uninstalling AVG, it really is a > great friend to have installed. > -- > ============================================== > I am only human, please > forgive me if I make a mistake it is not deliberate. > ============================================== > Take care this Xmas. > PLEASE DON'T drink and drive. > Kevan Farmer > > Linux user #373362 > > Cheslyn > Hay > Staffordshire > WS6 7HR > > -- > 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(a)suse.com > > > > > > > -- > Check the headers for your unsubscription address > For additional commands send e-mail to suse-linux-e-help(a)suse.com > Also check the archives at http://lists.suse.com > Please read the FAQs: suse-linux-e-faq(a)suse.com

1 0

SuSE 10.1 Alpha question
by Richard A Sharpe 28 Dec '05

28 Dec '05

Hi I have been testing the Alpha for 10.1 and most things work just fine, the one problem I seem to have I can't get my dialup to work, keeps coming up with can't contact server and does not dial, I configured the modem and provider as I did in 9.2 but just will not work. Has anyone else come across this and if so did you correct it? If you did could you let me know what you did? Thanks Rich

1 0

cleaning the subject header
by Peter Groff 28 Dec '05

28 Dec '05

Hi, I am using fetchmail to fetch mail from my ISP and kmail for reading mail. One mailinglist - no, not this one - adds a [LIST] to the subject of each mail. Sometimes the subject looks like Re: [LIST] Re: [LIST] Re: [LIST] ... I would like to filter out the multiple [LIST] entries, leaving only the first one, because I need that for filtering in kmail. How could this be done, either with fetchmail or kmail? Or would I need procmail/formail for this? I never used those. TIA

4 6

Wireless on Acer
by a.bridge＠insightbb.com 28 Dec '05

28 Dec '05

I have an Acer TravelMate 4010 running OpenSUSE 10 that as with most laptops has a button to turn wireless on and off. I have all my settings in YAST correct including encryption. However, I cannot get the button to turn on. I cannot find anything on the ACER webpage or anywhere else concerning this. Any help will be greatly appreciated. Thanks, Aaron

2 1