- openSUSE IA64

current build broken?
by Dr Markus Gross 08 Feb '07

08 Feb '07

Hi, Did somebody try to install the latest build? From Friday (2 FEB 07) night? I have trouble installing it. a) two missing dependencies: mkisofs + ia32el b) it does not seem to write the /boot properly, efi&elilo choke, elilo stops with file not found and repair of bootloader seems to be not possible due to lacking vfat support? Target system is a Intel quad IT2 system based on the Intel server platform, like the ones sold by DELL at some point. If you need more info, please ask. But this list seems to be not too active in the last while, so just in case nobody reads my lines I will stop here just now. Many thanks for any help, experience or hints! Regards, Markus. -- Dr Markus Gross University of Cambridge Innovative Manufacturing Research Centre Department of Engineering Unit 26A Cambridge Science Park Cambridge, CB4 0FP UK Room No. SPG-4 tel: +44 (0)1223 741857 fax: +44 (0)1223 741852 mob: +44 (0)7843 272195 email: msg30(a)cam.ac.uk skype: markus.s.gross "Nullius in verba" --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-ia64+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-ia64+help(a)opensuse.org

3 3

This list will be migrated to opensuse-ia64@opensuse.org
by Henne Vogelsang 08 Nov '06

08 Nov '06

Hi, as announced a while ago on the big lists [1] we will move this list to the new mailinglist server. We have also decided to rename it while moving it. All this will happen this friday (2006.11.10). I cant say exactly at which time but i will send a short heads-up mail right before we are doing it. This means a few things for you. 1. This list, suse-ia64(a)suse.com, will be renamed to opensuse-ia64(a)opensuse.org This means that mails to you will come from the new address and for posting you also have to send mail to opensuse-ia64(a)opensuse.org. The old list adress will still work but is depreceated. I will turn it off in the future (with notice). 2. Your subscription will get transfered to the new listserver. No action on your part is required to continue reciving mails from this list. 3. Because of the renaming the mailinglist headers will change. If you filter for headers in your mail setup please adopt your setup accordingly. New headers will look like this: Delivered-To: opensuse-ia64(a)lists4.opensuse.org Mailing-List: contact opensuse-ia64+help(a)opensuse.org; run by mlmmj X-Mailinglist: opensuse-ia64 List-Post: <mailto:opensuse-ia64@opensuse.org> List-Help: <mailto:opensuse-ia64+help@opensuse.org> List-Subscribe: <mailto:opensuse-ia64+subscribe@opensuse.org> List-Unsubscribe: <mailto:opensuse-ia64+unsubscribe@opensuse.org> List-Owner: <mailto:opensuse-ia64+owner@opensuse.org> 4. Mails will originate from the new server. If you accepts listmails only from the listserver adopt your setup accordingly. The mails will originate from DNS: lists4.suse.de IP: 195.135.221.135 5. The webarchive of this list is located at http://lists.opensuse.org/opensuse-ia64/ 6. We are using a new mailinglist manager on the new server. This means some aspects of using the list changed. Some features are dropped and some new features are added. For a complete list check out this post: http://lists.opensuse.org/opensuse-announce/2006-08/msg00005.html 7. If you have any problems at all with the new setup please dont hesitate to contact me! Henne [1] http://lists.suse.com/archive/suse-linux-e/2006-Nov/1464.html http://lists.suse.com/archive/suse-linux/2006-Nov/0440.html -- ml-admin

1 0

[opensuse-ipf] This list will be renamed
by Henne Vogelsang 08 Nov '06

08 Nov '06

Hi, by popular demand i will rename this list to opensuse-ia64 now. You wont have to do anything except using the new name when posting messages and adjust your filter settings if you filter for headers. If you have any questions dont hesitate to contact me. Henne -- ml-admin --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-ipf+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-ipf+help(a)opensuse.org

1 1

[opensuse-ipf] Need help with install issue
by jayme＠inreach.com 10 Oct '06

10 Oct '06

Hello, I am trying to install OpenSuse on a new system, and everything seems perfect up to the very end, when I have configured the system and setup my user account. The system tells me it is time to restart the system and then I will be able to login and begin using linux. I click ok, and then the monitor flickered and went black, as what I assume is the welcome sound tried to play but was cut short. Then the hard drive light flickers occasionally, and the monitor power light flashes from amber to green, which I've neve seen before. After waiting for 20 minutes, I did a reboot via the reset button, and then the computer loads the bios and as soon as it tries to boot from the HD, all I get is a single beep and then the system hangs. I tried doing the automated repair option from the linux disk, but it never fixes the problem. I went through the entire installation process again, and the same result, when it is time to reboot and login, the system basically dies- the only difference is that the welcome sound didn't try to play after the second install. My system is only a month old, an Asus motherboard with a new AMD MX2 4200 processor, and a new Nvidia graphics card (4700, with 512 megs). I have 1 gig of ram, and was running WinXp Pro successfully- but now it won't boot either. I tried fixing the MBR in the Windows repair mode, but it did nothing I can detect. My next guess is that I will have to edit the boot.ini file, but I read about the grub file as well, and I'm wondering which takes priority during the initial boot phase. I am brand new to Linux (probably obvious), and need to figure out how to have a succesful dual-boot system with WinXP and Linux. However, I did all this right before leaving town for a conference, and it will be a couple of days before I get back home and can try anything. I am hoping that someone can point me to some good web resources I can study if nobody has an immediate answer. Please help, and thank you in advance! Jayme --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-ipf+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-ipf+help(a)opensuse.org

1 0

RE: [suse-ia64] Problem with fsck on boot
by Bruce Adams 25 Sep '06

25 Sep '06

Apologies for top-posting I'm presently stuck on outlook remote mail :(. The file system is ext3. I used hda3 from an older boot disk (which cannot actually install a working system for my machine). dumpe2fs and tune2fs look like what I need for a workaround. The next check appears to be due in 500 mounts or the 20th November according to dumpe2fs. This seems a little longer than it ought to be but explains why it took me so long to discover the problem. There is definitely a genuine problem somewhere as fsck should not be hanging in the first place. I'm not entirely sure where in boot process fsck is called. Perhaps it is reliant on a kernel module that isn't available until later? I have not tried running fsck with the system running as I am mindful if the warning that it could damage the file system. As its the root filesystem I can only unmount with umount -l (lazy). Is it safe to run fsck after a lazy unmount? Regards, Bruce. -----Original Message----- From: Rafa Grimán [mailto:*] Sent: Fri 9/22/2006 12:19 PM To: suse-ia64(a)suse.com Subject: Re: [suse-ia64] Problem with fsck on boot Hi :) El Jueves, 21 de Septiembre de 2006 15:52, Glen Christensen escribió: > shutdown -f now > > will prevent fsck from running upon reboot > > -Glen Christensen > > >>> "Bruce Adams" <Bruce.Adams(a)tns-global.com> 09/21/06 7:26 AM >>> > > Hi, > Apologies if this is not the correct list (the general list appears to > be jammed with spam). I'm running a 64bit Suse 10 install dual booting with > W*ndows XP on a dell with a SATA hard- drive. After a long time of > successful running I rebooted to a forced fsck check which hung the machine > (with no output from fsck at all). > > I was only able to recover by booting in recovery mode and running fsck. > Fsck found no errors but simply updated the last check time so that the > check at boot time was no longer required. > I think the problem may be SATA related. From the boot disk I ran fsck > /dev/hda3 to correct the problem but this filesystem is /dev/sda5 when > booting normally. SATA drives are /dev/sd, why did you use /dev/hda3? Is the drive configured as PATA? > Firstly, Is there a way to bypass the fsck check (perhaps using a boot > option) when it occurs? Alternatively is there a way to disable it > completely and run the check manually. My installation is all on one > partition (excluding swap) which presumably means creating a ram disk > containing fsck, unmounting the root file system and re- mounting it > following the check. I'm not sure how best to achieve this. Any ideas? > Regards, > Bruce. What filesystem do you have on your drive? If it's ext2/3, you can use tune2fs. Rafa -- "Even paranoids have enemies." Rafa Grimán Systems Engineer Silicon Graphics Spain Santa Engracia, 120 - Planta Baja 28003 Madrid Spain Tel: +34 91 3984200 Tel: +34 91 3984201 Móvil: +34 628 117 940 http://www.sgi.com OpenWengo: rgriman Skype: rgriman

2 1

Problem with fsck on boot
by Bruce Adams 22 Sep '06

22 Sep '06

Hi, Apologies if this is not the correct list (the general list appears to be jammed with spam). I'm running a 64bit Suse 10 install dual booting with W*ndows XP on a dell with a SATA hard-drive. After a long time of successful running I rebooted to a forced fsck check which hung the machine (with no output from fsck at all). I was only able to recover by booting in recovery mode and running fsck. Fsck found no errors but simply updated the last check time so that the check at boot time was no longer required. I think the problem may be SATA related. From the boot disk I ran fsck /dev/hda3 to correct the problem but this filesystem is /dev/sda5 when booting normally. Firstly, Is there a way to bypass the fsck check (perhaps using a boot option) when it occurs? Alternatively is there a way to disable it completely and run the check manually. My installation is all on one partition (excluding swap) which presumably means creating a ram disk containing fsck, unmounting the root file system and re-mounting it following the check. I'm not sure how best to achieve this. Any ideas? Regards, Bruce.

3 2

[opensuse-ipf] openSUSE 10.2 Alpha 4 installation report
by Émeric Maschino 08 Sep '06

08 Sep '06

Hi, I successfully installed openSUSE 10.2 Alpha 4 on my hp workstation zx6000 system. Some problems at this time: - GDM isn't started at boot time, although I'm in runlevel 5 - GDK applications are crashing (see https://bugzilla.novell.com/show_bug.cgi?id=204365 for details); may be related to the above - the GNOME screensaver doesn't recognize my password, although the same password allowed me to log in a GNOME session (see https://bugzilla.novell.com/show_bug.cgi?id=204364 for details) - DRI isn't working (don't have time yet to discover why). Cheers, Emeric

1 0

Bug in parted command .
by MASTHAN DUDEKULA 25 Aug '06

25 Aug '06

Hi All, Here an intresting issue on parted command. I have a device of size 1074 MB and i tried to create partitions with parted command. The intresting issue is, the start position of first partition is not constant. The following snippet explain you more on this. lx88245:~ # parted -s /dev/sdc print Disk geometry for /dev/sdc: 0kB - 1074MB Disk label type: msdos Number Start End Size Type File system Flags lx88245:~ # parted -s /dev/sdc mklabel msdos lx88245:~ # parted -s /dev/sdc mkpart p 0 1065 lx88245:~ # parted -s /dev/sdc print Disk geometry for /dev/sdc: 0kB - 1074MB Disk label type: msdos Number Start End Size Type File system Flags 1 1kB 1065MB 1065MB primary type=83 lx88245:~ # parted -s /dev/sdc rm 1 lx88245:~ # parted -s /dev/sdc print Disk geometry for /dev/sdc: 0kB - 1074MB Disk label type: msdos Number Start End Size Type File system Flags lx88245:~ # parted -s /dev/sdc mklabel msdos lx88245:~ # parted -s /dev/sdc mkpart p 0 1069 lx88245:~ # parted -s /dev/sdc print Disk geometry for /dev/sdc: 0kB - 1074MB Disk label type: msdos Number Start End Size Type File system Flags 1 32kB 1069MB 1069MB primary ext3 type=83 lx88245:~ # parted -s /dev/sdc rm 1 lx88245:~ # parted -s /dev/sdc mklabel msdos lx88245:~ # parted -s /dev/sdc mkpart p 0 1071 lx88245:~ # parted -s /dev/sdc print Disk geometry for /dev/sdc: 0kB - 1074MB Disk label type: msdos Number Start End Size Type File system Flags 1 1kB 1071MB 1071MB primary type=83 lx88245:~ # In the first ( parted -s /dev/sdc mkpart p 0 1065) and third ( parted -s /dev/sdc mkpart p 0 1071) case the start position of first partition is 1 KB ( first block ) but in second case ( parted -s /dev/sdc mkpart p 0 1069) it is ( 32 kB). Can anyone explain it why it is happening like this ? is it bug in parted command ? Your help is appreciated ? Regards Masthan

1 1

Is qla2xxx driver supports SLES 10 ?
by MASTHAN DUDEKULA 17 Aug '06

17 Aug '06

Hi , At the time of booting , SUSE 10 (ia64 m/c) chowing that, qla2xxx driver is not supportd by novell , tainted flag is enabled ( Not exactly this , iam saying in my own words ). Is qla2xxx driver supports SLES 10 ? Thanks in advance Regards Masthan

1 0

[opensuse-ipf] Mailinglist migrated
by Henne Vogelsang 10 Aug '06

10 Aug '06

Hi, this list is migrated to the new mailinglist server. Henne -- Henne Vogelsang, Core Services "Rules change. The Game remains the same." - Omar (The Wire)

1 0