You are not logged in.
Hi!
I've just tried to upgrade from 2.6.13 (stock) to 2.6.14.2-1 and I got following error messages:
[waldek@wolfblade etc]$ sudo pacman -S kernel26
Targets: mkinitrd-1.01-16 kernel26-2.6.14.2-1
Total Package Size: 16.8 MB
Proceed with upgrade? [Y/n] y
checking package integrity... done.
loading package data... done.
checking for file conflicts...
error: the following file conflicts were found:
kernel26: /boot/System.map26: exists in filesystem
kernel26: /boot/kconfig26: exists in filesystem
kernel26: /boot/vmlinuz26: exists in filesystem
errors occurred, no packages were upgraded.
I know they exist, they should I guess.
the upgrade from 2.6.14-1 to 2.6.14.2-1 works fine (I have it on VMware when I'm testing stuff). Any ideas? I could not find any entries from people having the same problem so either you go from 2.6.14-1 to 2.6.14.2-1 or I messed up my system somehow (I can't imagine how though). I cannot imagine even I can screw up "pacman -S kernel26' Any ideas?
cheers
waldek
Offline
Simply force it. :twisted:
(Maybe you compiled your own kernel? Whatever, forcing should do the trick.)
Offline
I'm running the original 2.6.13 from the current repo. I know I can force it but I prefere to wait till 2.6.14 goes to the current - if nobody reports the same problem then I'll force it.
Offline
It seems there's a difference between:
pacman -S packagename
and
pacman -Su
the later one, besides of upgrading the system, removes the package first, the former one does not. It would work with "-Su" but I don't want to upgrade kde (I know I could flag it wiyh NoUpgrade but I'd rather be able to selectively upgrade packages).
Anyway I renamed the kernel 2.6.13 and updated grub, renamed two other files as well, I was told the kernel will work without them and it does. The installed the new one with "-S packagename".
Force would help but now I know the reason (at least I hope so).
cheers
wadlek
Offline
to stop from loading a lot of modules i did what u said about lshwd | grep IDE and its output was this
00:11.1 IDE interface: VIA Technologies|VT82C586 IDE [Apollo] (snd_via82xx)
so then i went to the mkinitrd.conf file and put it on the host controller ide , then i rebooted and *boom* im stuck after some messages.so i started with some live cd and chrooted the enviroment and deleted the snd_via82xx module.
the rebooted back to my arch linux and i noticed that on the loaded modules was one that say via82cxxx so i put this instead. Then rebooted to the arhclinux and it worked fine with this addition.
So i just wanted to recall that lshwd | grep IDE didnt worked for me and lets hope anothers dont fall into this.
I had same problem. Unfortunelly, i read it after my computer couldn't start.
Instead of lshwd, i tried then tpowa's beautiful tool:
hwdetect --show-ide
...and got this
IDE : ide-cd ide-core ide-disk generic via82cxxx
So, i would suggest to change the wiki from lshwd to hwdetect. I guess it detects devices better than hwd.
All your base are belong to us
Offline
I already added some lines to the wiki explaining hwdetect stuff.
All your base are belong to us
Offline
I already added some lines to the wiki explaining hwdetect stuff.
don't change it - hwd is still a valid app, and just because hwdetect is "better" doesn't mean you should remove hwd - just write a new page.
Offline
I have a dvd-rom (hdc) and a dvd burner (hdd) and encountered strange behaviour when trying to mount a dvd-rw. With the dvd-rom it's just working fine, mounts correctly and shows the content, but mounting with the burner just don't work (neither does blanking). I tried that both with a custom kernel (2.6.14) and the latest Arch kernel (2.6.14-4) with initrd. It's been maybe two months since I'd burned or mounted a dvd-rw so I'm not sure if its working with kernel versions 2.6.13-x. The custom kernel has ide-cd compiled into the kernel while the Arch kernel loads the needed modules just fine. The dvd-rw was burned with the same burner I'm now trying to mount it with, and I could mount it with the burner before (as I said it's been a while). I tried to burn a regular data cd this morning and it was working so I'm positive to say the burner is definetely not broken.
Does anybody have similar problems? I don't know if it's a kernel thing or maybe a problem of udev and/or hal/dbus. If it's of any interest I tried with module autoloading (rc.conf) and with hwd. I missed out trying with hotplug but can do this late this night...
Susu
Album reviews (in german): http://schallwelle.filzo.de
Offline
My biggest issue is my SCSI CD-ROM...
It did work with -archck kernel, and it IS present with the current one. BUT it's only at /dev/scd0 (while udev expects a SCSI CD-ROM to a place like /dev/sg0, where there's no valid device- although the node does exist), and so some applications (= K3B ) do not see the device at all, and more than that it can't be added by k3bsetup.
Another annoyance is that xsane now sees my (USB) scanner only as root, but I guess I will find a way out for that...
Maybe it's the only package from testing I have ( udev 0.78-1) the one to blame.
Of course I can still return to -archck, but the new kernel is noticeably faster.
Microshaft delenda est
Offline
scarecrow: modprobe sg
that will make the /dev/sgX devices.
Offline
scarecrow: modprobe sg
that will make the /dev/sgX devices.
Thanks for the tip, but I had already tried it- but still no valid sgx devices.
My etc/udev/rules.d/00.rules file is pretty straightforward:
BUS="usb", SYSFS{serial}="614714000042", KERNEL="sd?1", NAME="%k", SYMLINK="usbdrive", GROUP="storage"
BUS="usb", SYSFS{serial}="A12000043431", KERNEL="sd?1", NAME="%k", SYMLINK="usbhd", GROUP="storage"
BUS="scsi", KERNEL=="sg[0-9]*", SYSFS{type}=="5", NAME="%k", GROUP="optical"
The first two (pendrive and external harddrive, respectively) work fine, the last one not. CD media inserted in the drive mount fine, provided that I keep a /dev/scd0 entry in fstab, but that's all I can do...
Is udev 0.78 problematic, or am I missing something?
Do I need inserting a device serial for the SCSI CD-ROM?
Microshaft delenda est
Offline