Hello, people!
After latest kernel upgrading becam I a very stragne problem - if I plugg in USB-stick, freezed SUSE immediatly. Does anybody know what to do?
System: openSUSE 11.4 (x86_64)
That’s odd. I’ve just upgraded and it’s OK.
So, here’s a few questions:
[LIST=N]
[li]what command did you use to upgrade?[/li][li]what DE are you using (KDE, GNome, other?)?[/li][li]how are your repos structured (what do you get from this command: zypper lr)?[/li][li]and what kernel (do you get from this command: uname -r)?[/li][li]and this one: cat /etc/filesystems[/li][li]and was it an NTFS drive or a VFAT drive or some other?[/li][/LIST]
Hi,swerdna,
thank you for quick reply.
- upgrade via kpackegekit.
- KDE 4.6.3
3.repos enabled: Tumbleweed, Packman-tumbleweed, 11.4 Updates
4.kernel-default 2.6.38.6-28.1
6.it´s vfat drive
Sorry, more details come later, i have any access to my pc now :shame:
I see two processes here that might have given you a bad update (note the “might”, I’m not sure).
The first is kpackagekit which IMO doesn’t simulate a “zypper dup” process (that is the recommended way to go about regular updates).
The second is the repos. Greg k-h (the package maintainer for Tumbleweed) is developing and testing Tumbleweed with these repositories enabled when doing updates: opensuse-oss, opensuse-non-oss and opensuse-updates, as well as Tumbleweed repos of course.
So I recommend that you add opensuse-oss and opensuse-non-oss and then (as root) run the command “zypper dup”.
That’s not top say it will fix your problem, but it will at least give you a Tumbleweed that’s “like” the recommended one, and thus take away one question mark about your problem.
If you’re nervous about running zypper dup, do a dummy run first (zypper dup -D).
PS don’t forget Q5
What is packagekit capable of? Vendor change possible?
- compare what packages packagekit wants to install with “zypper dup”
- analyze the priorities of your enabled repositories.
Kpackegekit because i can see immediatly when new packeges come. It seems to me i have your instructions not fully undestood. But i have a question: should i do allways
“zypper dup”, even if it is only new gstreamer-package, or only for “great” upgrades as
kernel or kde?
I don’t trust kpackagekit in the Tumbleweed context. It gave me some bad advice once or twice (after I changed my distro to Tumbleweed) so I turned it off permanently. I run the simple zypper dup nowdays and take a careful look at what zypper is proposing to do.
It’s up to you of course. There are simple situations and not-simple situations. I would say though, that what you have right now, is possibly a mixture and that you should make it right to see whether the mixture is causing the lock up (maybe it is, maybe it isn’t).
The method I’m advocating is the method used by the package maintainer to test the Tumbleweed repos and the evolution of Tumbleweed. Have a read here, the second portion titled: Updating your RPMs from this point forwards. That’s my interpretation of direct query on the mailing list about how to roll forward.
Hi there,
just one short question: After rebooting, did you connect the USB stick again?
I am asking, as I observed, that on my system (11.4, 32bit) the new kernel from Tumbleweed does not request a restart. The kernel is basically working, but appearently the module versions do not match anymore, so I cannot mount a USB device until I reboot…
Good luck!
to swerdna:
5. eugeniak1:/home/eugeniak1/ # cat /etc/filesystems
vfat
hfs
minix
reiserfs
*
Yes, I did, but nothing has changed. I cannot mount a USB device before and after rebooting.
Vendor change is possible. Now I´ll fall back to previous kernel version to upgrade it with zypper dup and then I can compare the set of packages.
I´ve checked- all priorities set to 99.
to swerdna:
I´ve fall back to 2.6.38.6-27, added oss and non-oss repositories, then zypper-dup -
and - wonder! - I can mount USB!!!
Thank you very mutch!lol!
You’re welcome.
Just an aside, but your results from cat /etc/filesystems show that you should add an extra line so the file looks like this:
vfat
hfs
minix
reiserfs
ntfs
*
It’s a different matter, a different bug to be fixed, needs to be done.
I´ve done it. I see any difference in suse behavior, but what have to be done have to be done. Thank you.
I have compared. The proposition was the same.
It seems Tumbleweed is under heavy development. Some days ago I suggested to ever blindly do a “zypper dup”, until kde4 Tumbleweed build broke and this suggestion would have ruined my system, because all old kde4 packages had been removed from Tumbleweed before the new packages had been cleanly build. The ultimate suggestion to handle Tumbleweed: There is no!
Two alternatives:
-
“zypper dup” is needed if there are sets of packages (for example kde) which were mixed on Tumbleweed and opensuse-11.4 until now, but there is a newer upgrade kde waiting on Tumbleweed, which needs to fully vendor change to Tumbleweed for consistency of that set of packages.
-
“zypper up” is sufficent, if all package sets that need consistency had been previously fully changed “verndor”, like the kernel packages.
My way:
-
Analyzing: constantly answering ‘n’ for no action and carefully looking at outputs of:
zypper -vv up
zypper -vv up -r tumbleweed
zypper -v dup -r tumbleweed
zypper -v dup -r packman
zypper -vv dup -
Action phase: I often end up doing:
zypper -v up -r openSUSEupdates
zypper -v dup -r packman
zypper -v dup -r tumbleweed
Which has the effect that “tumbleweed” overwrites not only openSUSE but also packman packages. Tumbleweed is not that easy to handle, there are times of broken package set, which need consistency to function, and you have to wait …
I think my issue might be related. I own an HTC phone with fat32 formatted integrated SD storage. With recent kernel updates (at least the latest 2 versions) the file system would mount as read only. Even when mounted manually and for both - normal and root user.
I tried reformatting the storage and i could mount it again as writable but it only worked once so I’m pretty sure the issue is with the kernel. I haven’t tried downgrading yet.
Also, this is my only fat32 storage device. Ntfs work fine.
# mount
/dev/sdb1 on /media/htc type vfat (ro,relatime,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
# touch /media/htc/tmp
touch: cannot touch `/media/htc/tmp': Read-only file system