Dear all,
I am just trying ot update my old 7.1 system to 8.0.
I bought the 7.1 DVD and am trying to upgrade via ftp/boot disk. I
manage to get the update running and get all of my 620 or so packages
updated. Then the system tried the first boot and I shortly see a screen
with a few error messages (looks like missing shared libraries for/of qt
or so) which is immediately followed with an error message that the
upgrade failed.
Does anyone know what this is about and/or how to fix it ?
For information: I have a Dell Inspiron 8000 laptop, for details see:
http://www.slac.stanford.edu/~hadig/projects/dell/dell.html
By the way: I have another problem: After loading the PCMCIA modules,
my floppy drive is dead which makes loading of the network drivers
impossible. Solution to this is to NOT insert the modules3 disk when
asked for but choose "Back" and then load the network modules by hand
from disk modules3. Hope that helps.
Ciao
Thomas
----------------------------------------------------------------------------
Thomas Hadig MS 62, 2575 Sand Hill Road, Menlo Park CA 94025, USA
hadig(a)slac.stanford.edu Tel.: +1 650 926 2810
http://www.slac.stanford.edu/~hadig/
----------------------------------------------------------------------------
In a world without walls and fences, who needs windows and gates ?
----------------------------------------------------------------------------
I am trying to get this to run on my wifes 760xl laptop. it doesnot suppert
booting form the cdrom so I of course used rawrite to create a boot disk
from bootdisk in the suse/disks/ directory
when I restart laptop the suse logo comes up and I get:
Could not fine ramdisk: initrd
Pres a key to reboot.
I found initrd on the live eval cd under suse/images/boot/, but am unsure on
how to go about creating the bootdisk so I can boot the cdrom.
If this works and she likes it I may be able to pull one more wincomp off my
network.
Any suggestions, pointers greatly appreciated and TIA,
Bill Day
Linux 2.2.20-1tr i586
1:10pm up 21:53, 0 users, load average: 0.00, 0.00, 0.00
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.373 / Virus Database: 208 - Release Date: 7/1/02
Hi All
I have some questions to autoyast2, perhaps there is one on this list, who could
help me.
I want to install linux on several different systems.
How could i solve the following problem:
1.) There a differnce between IDE and SCSI, ist it possible to have one
controlfile, that handles both plattforms (fdsik, fromat, lilo, and so on)?
2.) There are also different NIC's on this system. I defined no module in the
controlfile and it will work , but after installation every user will be ask to
install an new NIC, thats allready installed
<interfaces config:type="list" >
<interface>
<BOOTPROTO>dhcp</BOOTPROTO>
<STARTMODE>onboot</STARTMODE>
<UNIQUE></UNIQUE>
<device>eth0</device>
<module></module>
<options></options>
</interface>
</interfaces>
3.) Is there a way to autoprobe the graphical interface ( hardewareinterface and
resolution)?
4.) After installing by using autoyast2 i get the KDM-Login frist time,
secondtime i get the consolen-Login
5.) When i try to install an extented package-list i allways get a failure about
some packages, that was not found - Is there a solution for this Problem?
<software>
<addons config:type="list" />
<base>my-list</base>
</software>
the list 'my-list' is in the same directory as the default one
6.) Is there a way to include an automatic sound autoprobe by installing and
only there is a problem the user could change it manually after installation?
Thanks for help!
bye
Alexander Gehrig
Hi again,
I just discovered that there is a problem in the SuSE 8.0 network-/ dsl-setup which screws the order in which the networkdevices are initialized in the bootprocess. Good thing is that there is a patch which fixes this problem.
http://sdb.suse.de/en/sdb/html/thallma_dsl_80.html
Thanks to everyone for all the help and good advice
Sebastian
-----Ursprüngliche Nachricht-----
Von: Sebastian.Beckmann(a)t-online.de
[mailto:Sebastian.Beckmann@t-online.de]
Gesendet: Freitag, 5. Juli 2002 13:57
An: suse-autoinstall(a)suse.com
Betreff: [suse-autoinstall] Autoinstall, multiple NICs, DSL-Problem
after YAST-Setup, SuSE 8.0
Hi all,
I want to install a DSL-Router with multiple NICs. The
Softwareinsatllation via Autoyast works real nice. But now comes my
problem:
When I set up the DSL-configuration via YAST everything is working
pretty fine at first, but after the next reboot neither DSL or the rest
of my NICs are working proberly. It seems that the complete
network-setup is messed up. I tried every ethernetcable on each NIC and
discovered that the interfaces changed somehow. The routes are still ok
but somehow all networkdevices switched place.
Before reboot:
eth0: 3com-card
eth1: 3com card
eth2: realtek card
after reboot:
eth0: realtek card (WHY?)
eth1: 3com card
eth2: 3com card
I've noticed that after setting up a fresh system and running YAST,
YAST does not recognise the allready working NICs and proposes to set
them up again, this time as eth3 till eth5.
Am I doing something wrong while installing the system via Autoyast?
Here is my snippet from the autoinst.xml
-----8<-----
<interfaces config:type="list">
<interface>
<BOOTPROTO>static</BOOTPROTO>
<BROADCAST>192.168.1.255</BROADCAST>
<IPADDR>192.168.1.10</IPADDR>
<NETMASK>255.255.255.0</NETMASK>
<NETWORK>192.168.1.0</NETWORK>
<STARTMODE>onboot</STARTMODE>
<UNIQUE/>
<device>eth0</device>
<module>3c59x</module>
<options/>
</interface>
<interface>
<BOOTPROTO>static</BOOTPROTO>
<BROADCAST>192.168.2.255</BROADCAST>
<IPADDR>192.168.2.10</IPADDR>
<NETMASK>255.255.255.0</NETMASK>
<NETWORK>192.168.2.0</NETWORK>
<STARTMODE>onboot</STARTMODE>
<UNIQUE/>
<device>eth1</device>
<module>3c59x</module>
<options/>
</interface>
<interface>
<BOOTPROTO>static</BOOTPROTO>
<BROADCAST>192.168.3.255</BROADCAST>
<IPADDR>192.168.3.10</IPADDR>
<NETMASK>255.255.255.0</NETMASK>
<NETWORK>192.168.3.0</NETWORK>
<STARTMODE>onboot</STARTMODE>
<UNIQUE/>
<device>eth2</device>
<module>8139too</module>
<options/>
</interface>
</interfaces>
-----8<-----
Mit freundlichen Grüßen
Sebastian Beckmann
--
To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com
For additional commands, e-mail: suse-autoinstall-help(a)suse.com
SuSE mailinglist: [suse-autoinstall] Autoinstall, multiple NICsHi Sebastien,
> Before reboot:
> eth0: 3com-card
> eth1: 3com card
> eth2: realtek card
> after reboot:
> eth0: realtek card (WHY?)
> eth1: 3com card
> eth2: 3com card
The interfaces are defined based on the order in which the modules are loaded, if the
realtek module is loaded before the 3com module, then you will get the affect you
observed. During auto-install it probes for the cards in a certain order, this may not be
reflected in the final config.
I had ths problem and resolved it by settting the variable INITRD_MODULES in
/etc/rc.config with the modules listed in the order I wanted them loaded.
e.g.:
INITRD_MODULES="pcnet32 eepro100"
Then run 'mk_initrd' to generate the initial ramdisk containing these modules.
Check that the /etc/lilo.conf (or whatever boot loader you use) loads the initrd generated
above.
e.g.: In /etc/lilo.conf, the entry would read:
image = /boot/vmlinuz
root = /dev/xxx
label = linux
initrd=/boot/initrd
After reboot, the modules are loaded in the order specified. This method makes sure that
modules are loaded before the root partition boots. If you use LVM are as module and want
to boot from an LVM partition then you also need to include 'lvm' in the INITRD_MODULES
list.
Rgds,
Simon
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Monday 08 July 2002 15:10, Jussi Jaaskelainen wrote:
> There was an error loading the module About-Page for Konqueror.
> The diagnostics is:
> /opt/kde3/lib/libkdeprint.so.4: undefined symbol:
> addColumn__9KListViewRC7QStringi
So there is nobody else who had same problems?!? ;-(
- - --
Jussi Jääskeläinen, Audio Riders Oy
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8
iQA/AwUBPSvFiiCdxta+jYblEQJrPwCfdqLdIahcL7sG3G44cBHDMtwO4sQAoO3r
DBfUsIoX5mI5i2xnCFeAc8ws
=DD+A
-----END PGP SIGNATURE-----
Hi all,
I want to install a DSL-Router with multiple NICs. The
Softwareinsatllation via Autoyast works real nice. But now comes my
problem:
When I set up the DSL-configuration via YAST everything is working
pretty fine at first, but after the next reboot neither DSL or the rest
of my NICs are working proberly. It seems that the complete
network-setup is messed up. I tried every ethernetcable on each NIC and
discovered that the interfaces changed somehow. The routes are still ok
but somehow all networkdevices switched place.
Before reboot:
eth0: 3com-card
eth1: 3com card
eth2: realtek card
after reboot:
eth0: realtek card (WHY?)
eth1: 3com card
eth2: 3com card
I've noticed that after setting up a fresh system and running YAST,
YAST does not recognise the allready working NICs and proposes to set
them up again, this time as eth3 till eth5.
Am I doing something wrong while installing the system via Autoyast?
Here is my snippet from the autoinst.xml
-----8<-----
<interfaces config:type="list">
<interface>
<BOOTPROTO>static</BOOTPROTO>
<BROADCAST>192.168.1.255</BROADCAST>
<IPADDR>192.168.1.10</IPADDR>
<NETMASK>255.255.255.0</NETMASK>
<NETWORK>192.168.1.0</NETWORK>
<STARTMODE>onboot</STARTMODE>
<UNIQUE/>
<device>eth0</device>
<module>3c59x</module>
<options/>
</interface>
<interface>
<BOOTPROTO>static</BOOTPROTO>
<BROADCAST>192.168.2.255</BROADCAST>
<IPADDR>192.168.2.10</IPADDR>
<NETMASK>255.255.255.0</NETMASK>
<NETWORK>192.168.2.0</NETWORK>
<STARTMODE>onboot</STARTMODE>
<UNIQUE/>
<device>eth1</device>
<module>3c59x</module>
<options/>
</interface>
<interface>
<BOOTPROTO>static</BOOTPROTO>
<BROADCAST>192.168.3.255</BROADCAST>
<IPADDR>192.168.3.10</IPADDR>
<NETMASK>255.255.255.0</NETMASK>
<NETWORK>192.168.3.0</NETWORK>
<STARTMODE>onboot</STARTMODE>
<UNIQUE/>
<device>eth2</device>
<module>8139too</module>
<options/>
</interface>
</interfaces>
-----8<-----
Mit freundlichen Grüßen
Sebastian Beckmann
It turns out the problem I was having had nothing to do with SCSI or RAID.
What happened was that my partitioning scheme was something along the lines
of this:
sda5: 512M
sda6: 512M swap
sda7: 2048M
sda8: max <--- here's the problem
sda9: 2048M
The way I was using 'max' was that it allots the remaining space to its
partition after ALL other partitions have been accounted for. Apparently,
what actually happens is that it allots the remaining space taking into
account only those partitions that have already been defined. This means
that if you specify a 'max' partition it must always be last. Because all
the space had already been allotted, YaST complained that the partition
table was invalid.
I think it'd be beneficial to allow a 'max' partition to be anywhere in the
partitioning order. I imagine it'd probably be pretty easy to implement in
code. I'd do it myself but I haven't seen any source code for this project.
Thanks,
Robert
> -----Original Message-----
> From: Volkmar Glauche [mailto:glauche@uke.uni-hamburg.de]
> Sent: Tuesday, July 09, 2002 4:06 AM
> To: Robert Alonso
> Cc: suse-autoinstall(a)suse.com
> Subject: RE: [suse-autoinstall] YaST2 not starting from inst-sys
>
>
> On Mon, 8 Jul 2002 ralonso(a)lis.state.oh.us wrote:
>
> > Thanks Volkmar. I tried replacing the root image using
> mkcramfs and I was
> > successful to a certain degree. Now my problem is that I'm
> unable to
> > partition the hard drive. YaST2 complains that the hard
> drive's partition
> > table is unsupported. I've seen this error before and it
> was due to YaST
> > trying to create all partitions as primary. See
> > http://www.suse.de/~nashif/autoinstall/bugs.html#AEN60.
> That's why I wanted
> > to use the inst-sys directory, so that I could use the
> updated package.
> > Using the updated package has worked before on a standard
> IDE hard drive,
> > but now I'm using two SCSI drives with RAID support and
> can't get the
> > auto-partitioning to work.
>
> Which RAID support do you use? If you want to create lvm volume groups
> from partitions on both drives, this will not work with even
> the newest
> available autoinstall module. I have got such a configuration on all
> workstations (15+) in our department and I am still waiting with the
> update until SuSE releases a working patch to the autoinstall
> module. I
> hope such a patch will be made available for 8.0 before the
> 8.1 release
> is shipped.
>
> > Has anyone had any success using autoyast with this type of
> configuration?
> > Any hints?
>
> Volkmar
>
> --
> Volkmar Glauche
>
> Department of Neurology E-Mail
> glauche(a)uke.uni-hamburg.de
> UKE Hamburg WWW http://glauche.home.pages.de/
> Martinistr. 52 Phone 49(0)40-42803-5781
> 20246 Hamburg Fax 49(0)40-42803-9955
>
>
>
>
> --
> To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com
> For additional commands, e-mail: suse-autoinstall-help(a)suse.com
>
hi,
i found this mail from may and my question, is there allready any
documentation about creating a custom cd?
################################################################################
Date: Thu, 2 May 2002 17:14:48 +0200
From: Anas Nashif <nashif(a)suse.de>
Message-ID: <20020502151448.GB18698(a)suse.de>
Subject: Re: [suse-autoinstall] Yast2 Autoinstall Custom CDs?
* Kevin Winner <krwinner(a)ix.netcom.com> [May 02. 2002 14:13]:
> Will Yast2 autoinstall ever support creation of custom CDs to allow for adding
> additional custom rpms like alice does now with make_inst_cd?
>
Yes. AutoYaST2 will have ALL those features that were available with
alice and many more.
Of course it is possible now but it has to be done manually. I will be
adding some documentation on how this can be done shortly.
Anas
> Thanks,
> Kevin
any documentation
--
*************************************************
Avitech Aviation Management Technologies GmbH
Marc Peter
Bahnhofplatz 1
D-88045 Friedrichshafen
Phone: +49 7541/282-451
Fax: +49 7541/282-199
mailto:marc.peter@avitech.de
*************************************************
Thanks Volkmar. I tried replacing the root image using mkcramfs and I was
successful to a certain degree. Now my problem is that I'm unable to
partition the hard drive. YaST2 complains that the hard drive's partition
table is unsupported. I've seen this error before and it was due to YaST
trying to create all partitions as primary. See
http://www.suse.de/~nashif/autoinstall/bugs.html#AEN60. That's why I wanted
to use the inst-sys directory, so that I could use the updated package.
Using the updated package has worked before on a standard IDE hard drive,
but now I'm using two SCSI drives with RAID support and can't get the
auto-partitioning to work.
Has anyone had any success using autoyast with this type of configuration?
Any hints?
Thanks,
Robert
> -----Original Message-----
> From: Volkmar Glauche [mailto:glauche@uke.uni-hamburg.de]
> Sent: Sunday, July 07, 2002 11:11 AM
> To: Robert Alonso
> Cc: suse-autoinstall(a)suse.com
> Subject: Re: [suse-autoinstall] YaST2 not starting from inst-sys
>
>
> On Fri, 5 Jul 2002 ralonso(a)lis.state.oh.us wrote:
>
> > Hi all,
> >
> > For some reason, the root image (<path to suse
> > installation>/suse/images/root) is still being read instead
> of inst-sys
> > (<path to suse installation>/suse/inst-sys). I needed the inst-sys
> > directory so that I could run the updated version
> yast2-module-autoinst. I
> > did this according to the directions at
> > http://www.suse.de/~nashif/autoinstall/bugs.html#AEN110.
> This worked
> > successfully when I tested installation of my workstation.
> YaST2 started
> > from inst-sys. But now I'm trying to do the installation
> onto another
> > machine, and it keeps trying to read the the root image
> instead of inst-sys.
> > Any idea why the behavior differs between these two machines?
>
> I did not get the installation booting from the inst-sys
> directory at all.
> However, I did not find it very difficult to mkcramfs the updated
> installation directory to create a new root image. So I replaced the
> original image with the updated one and everything worked fine.
>
> Volkmar
>
> --
> Volkmar Glauche
>
> Department of Neurology E-Mail
> glauche(a)uke.uni-hamburg.de
> UKE Hamburg WWW http://glauche.home.pages.de/
> Martinistr. 52 Phone 49(0)40-42803-5781
> 20246 Hamburg Fax 49(0)40-42803-9955
>
>
>
>
> --
> To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com
> For additional commands, e-mail: suse-autoinstall-help(a)suse.com
>