On 2011-03-21 21:36, hbco2 wrote:
>
> No, pondered your suggestion to manually update, and don’t have enough
> information to establish a procedure. Are you suggesting the use of an
> ftp file manager to open the update repository and find several files
> related to timezone, including a patch to the update (?), apply the
> patch to the update (don’t have any idea how), then manually perform the
> update. Don’t know how to do that, either. Maybe it is an rpm, that I
> can install. Frankly, can’t see how the download process is somehow
> affected by a timezone update.
I don’t know how many updates you have pending, I thought you would have
more than “timezone”. But let’s assume you wanted to update “timezone”
manually, as an example. And assume you have the 64 bit version.
The easiest to install (manually) is the second one. Click on it, or
download using wget, whatever. Get it. Run “rpm --upgrade packagename”,
done. I believe it is also possible to do:
11.4 Freeze ? I’m supposed to remember those details?
Re: boot issue could you post an fdisk -l and /etc/fstab output?
Re: Screen. Easy way. roughly
1 Shutdown PC, connect PC to DVI on monitor and boot.
2 Add nomodset to grub command.
3 When in suse use proprietary software of vga to generate clean xorg.conf.
Hard way
1 Reboot
2 As in 2 above
3 use terminal to run gtf 2048 1024 60 and generate a modeset line for that resolution
4 update /etc/X11/xorg.conf by adding the modeset line from gtf to your monitor section. Yours will be different from
Regarding nomodset and ModeLine, would an xorg.conf from SuSE 11.2 suffice? The xorg.conf-11.2 file worked in 11.3 and it is installed in /etc/X11 on this 11.4 system. xorg.conf apparently defines the monitor when it is recognized by the operating system, although recognition is intermittent. Intermittent in the sense that it takes several computer on-off cycles/reboots to establish a working linux system. As mentioned, either CPU timeout dumps appear as text after a udev failure (udev stalls), or the system comes up with an incorrect resolution set for the screen. Or the system boots normally (as it has and I am using it at this time).
The xorg.conf file can be viewed at SUSE Paste
I have tried to manually upgrate timezone. I was able to find the files (including the delta). Unfortunately, I installed the timezone update before applying the delta. Apparently the delta should have been applied first, as attempting to run the rpm after yielded an “already installed” error.
At any rate, there must be something wrong with the file system, as attempting other updates yielded the same problem. Downloading a wine update, for example, reached 98% before the B/s counter slowly decreased from 300+ B/s to 0. I skipped that update, but ran into several others in the list of 38 updates.
I notice in fdisk-l the announcement “Partition table entries are not in disk order.” I wonder if that might be the problem.
On 2011-03-22 10:06, hbco2 wrote:
>
> robin listas
>
> I have tried to manually upgrate timezone. I was able to find the
> files (including the delta). Unfortunately, I installed the timezone
> update before applying the delta. Apparently the delta should have been
> applied first, as attempting to run the rpm after yielded an “already
> installed” error.
I think you misunderstood. It is either the rpm from the update repo, or
the delta. One of them, not both.
> At any rate, there must be something wrong with the file system, as
> attempting other updates yielded the same problem. Downloading a wine
> update, for example, reached 98% before the B/s counter slowly decreased
> from 300+ B/s to 0. I skipped that update, but ran into several others
> in the list of 38 updates.
I don’t know about that. I would try to manually apply all the updates I
could, just in case one of them helps. Anything related to udev, glib, etc.
> I notice in fdisk-l the announcement “Partition table entries are not
> in disk order.” I wonder if that might be the problem.
No, that doesn’t matter at all.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
> As
> mentioned, either CPU timeout dumps appear as text after a udev failure
> (udev stalls), or the system comes up with an incorrect resolution set
> for the screen. Or the system boots normally (as it has and I am using
> it at this time).
Considering you are connecting your display via a switch, I would remove it
temporarily and try.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
Yes if you’re satisfied with resolution 1280x1024. I thought you wanted 2048x1024.
Re: reboots:
How did you partition your drive and install 11.4?
I assume your /home is on a seaparte partititon to avoid formatting and losing your data?
IMHO, you’re had a bad install for some reason and if you back up the /etc configuration files, you could reinstall 11.4. Then you could restore your /etc/X11/xorg.conf, /etc/hosts*, etc.
The drive was auto partitioned by the 11.3 installation program. Upgrade to 11.4 was accomplished online through zypper after redefining repositories. There shouldn’t have been anything unusual about the install, but fair warning to anyone wishing to use online upgrade. 11.3 was running fine.
Am still trying to tease zypper update, but it is still stalling in an attempt to download packages. It downloads some completely, but others, such as a wine upgrade/reinstall file downloads to 98%, then the B/s counter slowly fades to zero.
Yes, a reinstall seems ever more likely. As mentioned, after all the fussing, it will likely be a 12 hour project.
Thank you for your attention.
Finally managed to get an install disk and rescue system operating. Attempting to run fsck -p /dev/sda yields “bad magic number in superblock while trying to open /dev/sda”
fsck -p /dev/sda2 yields “short read… could this be a zero-length partition?”
No luck here either…
That sounds okay. Can I refresh your status? Solved:
GLIB errors
Resolution size at 1280x1024 and you’re using xorg.conf from 11.3.
Unsolved:
Still long intermittent boot
Can’t use zypper or YaST to update
Re: boot
In your /etc/fstab it looks like there’s a Maxtor 80Gb containing /dev/sda partitions
and a /mnt/SONYVAULT defined as /dev/sda1. Is the SONYVAULT now /dev/sdb of 2Gb? If true, then change the /etc/fstab to /dev/sdb1
Re: Zypper
Have you run
su -c "shutdown -Fr now"
since installing 11.4?
Can you run
zypper lr -pD
zypper verify
su -c "zypper clean"
su -c "zypper refresh"
Please paste the output from zypper lr (you can use SUSE Paste or use html [foo] wrappers [foo] replacing the word “foo” with the word “code”.
I don’t have to write it but man zypper anyway.
Thanks
/dev/sda3 yields the Linux partition. No bad blocks. Upon completion, fsck reported the system had been changed (something about groups). However, upon IPL, looks like nothing has changed. On to a reinstall when time is avail. Tnx again.
GLIB errors persist, workaround is after setting su root, to set su - root at a terminal prompt.
Resolution size 1024X2048 has always worked, but intermittently. For some reason, may be only chance or perhaps from an upgrade, once past the udev block, the system boots to the proper resolution.
SONYVAULT is a removable flash drive and now removed from the system. A windows partition exists, linux is apparently in /dev/sda3.
Just ran su -c “shutdown -Fr now” and rebooted, noted file system checks, no errors.
Results of your requests can be seen at SUSE Paste. The tests were run under su root (as opposed to su root/su - root).
