[opensuse-factory] Unable to update from 10.2 to 10.3 RC1 on IBM R40
Hi! Trying to update from a openSUSE 10.2 to 10.3 RC1 on an IBM R40 fails. When initializing the Setup system it shows the following dialog: "The partitioning on disk /dev/sda is not readable by the partitioning tool parted, which is used to change the partition table. You can use the partitions on disk /dev/sda as they are. you can format them and assign mount points to them, but you cannot add, edit, resize or remove partitions from that disk with this tool. When I afterwards select the update option and continue it shows all three partitions on this disk, but seems not recognize the openSUSE 10.2 on /dev/sda1 and therefore will not let me update. Looking at the boot log a lot of "attempt to access beyond end of device" can be seem, which make me guess this is another variant of BUG #327612. However the solution there won't work for me as I don't have a running 10.3, yet. I attached the contents of /var/log. Kind Regards, Matthias -- Matthias Bach - www.marix.org GPG/PGP Key-ID: 0xF0818B12
Hi,
Looking at the boot log a lot of "attempt to access beyond end of device" can be seem, which make me guess this is another variant of BUG #327612. However the solution there won't work for me as I don't have a running 10.3, yet.
I attached the contents of /var/log. You should certainly open a bugreport at bugzilla.novell.com and attach you YaST logs.
Good luck! Felix Möller --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Felix Möller wrote:
Hi,
Looking at the boot log a lot of "attempt to access beyond end of device" can be seem, which make me guess this is another variant of BUG #327612. However the solution there won't work for me as I don't have a running 10.3, yet.
I attached the contents of /var/log. You should certainly open a bugreport at bugzilla.novell.com and attach you YaST logs.
I had this too, bug #327513 which was also marked as a duplicate of #327612 - not too helpful, is it, when you are trying to install! My fix (see my bug!) was to boot the installer with 'brokenmodules=pata_via'. It might be a different module causing your problem - take a look at the logs as the installer loads, it will attempt to detect the platform and decide which modules it wants e.g. for HD controllers. The first one list for me was pata_via so my first stab was to disable that and all was fine. NB - I allowed network access and remote repositories, so the kernel loaded for the installed system was newer & didn't show the problem. HTH -- Richard (MQ) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Hi! Am Mittwoch 26 September 2007 schrieb richard (MQ):
I had this too, bug #327513 which was also marked as a duplicate of #327612 - not too helpful, is it, when you are trying to install! My fix (see my bug!) was to boot the installer with 'brokenmodules=pata_via'.
It might be a different module causing your problem - take a look at the logs as the installer loads, it will attempt to detect the platform and decide which modules it wants e.g. for HD controllers. The first one list for me was pata_via so my first stab was to disable that and all was fine.
Thanks for the tip. Looks like the problem was with the module ata_piix, however, seeing that this problem occurs in multiple modules there seems to be more behind it than just a problem about the modules.
NB - I allowed network access and remote repositories, so the kernel loaded for the installed system was newer & didn't show the problem.
Sadly this is not an option for me. I could only access the network via WLAN, and while YAST seems to properly load the drivers for the intel chipset I cannot use it because that part of the network configuration is missing in the installer. Again, thanks for the help, Matthias -- Matthias Bach www.marix.org "Was nicht mit einer gewissen Unsicherheit behaftet ist, kann unmöglich die Wahrheit sein." - Richard P. Feynman
Matthias Bach wrote:
NB - I allowed network access and remote repositories, so the kernel loaded for the installed system was newer & didn't show the problem.
Sadly this is not an option for me. I could only access the network via WLAN, and while YAST seems to properly load the drivers for the intel chipset I cannot use it because that part of the network configuration is missing in the installer.
You're right, WLAN configuration is not part of the Network Setup in the First Stage installation. It should have been just a simple static/dhcp configuration. See bug #293609 for more details. Anyway, you might want to setup the WLAN manually :) Before selecting the installation mode (plus [x] Online Repositories), switch to the console 2 and set it up. http://en.opensuse.org/SDB:Ndiswrapper See "Manual Interface Configuration" Bye Lukas
Am Mittwoch 26 September 2007 schrieb richard (MQ):
I had this too, bug #327513 which was also marked as a duplicate of #327612 - not too helpful, is it, when you are trying to install! My fix (see my bug!) was to boot the installer with 'brokenmodules=pata_via'.
It might be a different module causing your problem - take a look at the logs as the installer loads, it will attempt to detect the platform and decide which modules it wants e.g. for HD controllers. The first one list for me was pata_via so my first stab was to disable that and all was fine.
Thanks for the tip. Looks like the problem was with the module ata_piix, however, seeing that this problem occurs in multiple modules there seems to be more behind it than just a problem about the modules.
NB - I allowed network access and remote repositories, so the kernel loaded for the installed system was newer & didn't show the problem.
Sadly this is not an option for me. I could only access the network via WLAN, and while YAST seems to properly load the drivers for the intel chipset I cannot use it because that part of the network configuration is missing in the installer.
Again, thanks for the help, Matthias
You're welcome. I think your best bet is to wait for RC2! -- Cheers Richard (MQ) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Wednesday 26 September 2007 10:34:13 Richard (MQ) wrote:
You're welcome. I think your best bet is to wait for RC2!
RC2 has already been sync'd to OSS-Factory and won't be sent out as ISO's (as already mentioned in other emails). If you wait, your next test will be with the final release on Oct 4. You could try test with http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/boot/bo... from OSS-Factory or the RC2 Live CD's From coolo's "Announcing 10.3 RC2 Live CDs" on opensuse-announce@opensuse.org:
http://download.opensuse.org/distribution/10.3-RC2/iso/cd/
80397c4ffb1c33097303b70c6863b63e openSUSE-10.3-RC2-GNOME-Live-i386.iso ed7abd1d1517e5dd6505a03c17343a71 openSUSE-10.3-RC2-KDE-Live-i386.iso
To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Warren Stockton wrote:
On Wednesday 26 September 2007 10:34:13 Richard (MQ) wrote:
You're welcome. I think your best bet is to wait for RC2!
RC2 has already been sync'd to OSS-Factory and won't be sent out as ISO's (as already mentioned in other emails).
Quite so - culpe mea. My memory is going...
If you wait, your next test will be with the final release on Oct 4.
You could try test with http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/boot/bo... from OSS-Factory or the RC2 Live CD's
From coolo's "Announcing 10.3 RC2 Live CDs" on opensuse-announce@opensuse.org:
The former is impractical unless the OP can get the WLAN up for installation (another sub-thread), in which case the 'brokenmodules=xxx' fix is probably viable too. I'd be interested to know how that goes, though I rarely use my own WLAN due to it's lack of security... The latter should at least show how the hardware behaves with a newer kernel. -- Regards, Richard (MQ) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (6)
-
Felix Möller -
Lukas Ocilka -
Matthias Bach -
Richard (MQ) -
richard (MQ)
-
Warren Stockton