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?
that will make the /dev/sgX devices.
]]>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
]]>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.
]]>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.
]]>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
]]>(Maybe you compiled your own kernel? Whatever, forcing should do the trick.)
]]>[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
]]>In this kernel 2.6.13, I use the following to reach x-org.conf:
===============================================
cd /etc/X11
nano xorg.conf
================================================
The listing in this kernel 2.6.13 for the USB Mouse is identical to that for the kernel 2.6.14-4. In this kernel,2.6.13, the scroll wheel operates correctly.
It seems there may be a problem with the ordering of the installed USB devices. They get initialized almost as the last thing during boot-up, just before the arch log-in and the subsequent loading of Kde.
I have confidence that the parameters loaded for the USB mouse are correct in Kernel 2.6.14-4 as loaded by the arch 0.7.1CD.
It remains a mystery as to why it fails to scroll.
Thanks for your reply
]]>sOLar;
Pleased to hear from you on the subject of the scroll mouse parameter.
The present install of arch 0.7.1 requires the user to utilize the following procedure to get the xorg.conf display:
#hwd -x
# cd /etc/X11
# nano xorg.conf.hwdThe following is the listing of the pertinent mouse device parameters for USB mouse as provided by the install of kernel 2.6.14-4:
============================================================
Section "InputDevice"
Identifier "USB Mouse"
Driver "mouse"
Option "Device" "/dev/input/mice"
Option "SendCoreEvents" "true"
Option "Protocol" "IMPS/2"
Option "ZAxisMapping" "4 5"
Option "Buttons" "5"
EndSection
==============================================================I assume from this detail that the correct parameter information is installed in my system. The scroll does not function.
My system does not have nvidia agp. I have 8500LE ATI agp without accel.I appreciate any help in resolving this difficulty.
Happy Thanksgiving
====================================================
When God made YogiBear, he said "I made a boo-boo"
Try changing the /dev/input/mice to /dev/psaux.
nano -w /etc/X11/xorg.conf as root.
I don't know how to install ATI drivers since I use nvidia hardware. You can easily use the ati drivers provided automatically, only when you want to play games it can become a problem.
First of I am using a custom 2.6.14 patched with ck5. I built it with the PKGBUILD from the 2.6.14.2-1 package in testing using the config from that package. I actually wanted to see if this would be any faster then archck which I have been running since I don't use any of the extra stuff thats included in archck. Anyway enough reasoning here is my problem.
It runs through the first 90% of the initrd loading fine, but once it tries to mount the real root filesystem it encounters a problem. It's trying to mount /dev/hdc3 as the root filesystem, which under the working archck kernel w/o initrd is correct. But if I scroll up in the messages its giving me as it was booting and I look at the list of diferent hd devices its been detecting I find they are in a new order. My cdrw and dvd have moved from hda and hdb to hde and hdf, my 2 160gb data drives have moved from hde and hdg to hda and hdc (both of these drives are unformated). The data drives are attached to an onboard MegaRAID IDE card which as of yet I have not been able to get to work so both of those drives remain unformated. My former main drive with my root filesystem has been moved from hdc to hdg. Once I found this I though no problem, I ran mkinitrd again and specified /dev/hdg3 as the root device instead of letting it auto detect. I rebooted and now it is looking for the root filesystem in the right place but it is still unable to fine it. I cd'd into /dev at the busybox prompt to figure out why and I found that it only makes nodes for hda-hdd. Is there any way I can get around this? I noticed in the messages as I was scrolling through them that I actualy detected and initialized something megaraid related and I'm kind of hoping I can get that stupid raid controler to work once I can get it to boot this new kernel.
andy
[EDIT]
I seem to have answered my own question.
It wasn't that hard once I read up on initrd.
Anyway this is how I did it.
[all this assumes that you have already run mkinirtd]
Mount initrd image rw so I can edit it:
# cd /tmp
# mkdir initrd
# gunzip < /boot/initrd-2.6.14-ck5-ARCH.img > initrd.img
# mount: -o loop initrd.img initrd
Then I added the following lines to linuxrc in the initrd image to make the device nodes for hdg:
mknod /dev/hdg3 b 34 3
I placed it after the line to make the node for hdd12 but it probably doesn't matter where it is as long as it comes before it tries to actually mount the filesystem.
(btw you can figure out the major and minor numbers by reading devices.txt in the documentation directory of your kernel source. You'd have this if you built a custom kernel like I did, but if not I'm sure you can get it from kernel.org or some where else on the web.)
Then I copied my new initrd image into /boot, don't foget to back up incase the new initrd image doesn't work (not that the old one did actually work, but its always good to backup):
# umount initrd
# mv /boot/initrd-2.6.14-ck5-ARCH.img /boot/initrd-2.6.14-ck5-ARCH.img.bak
# gzip < initrd.img > /boot/initrd-2.6.14-ck5-ARCH.img
After that it was just a matter of making a new fstab to reflect the new names my drives would have and then rebooting.
I'm now in the new kernel and everything is running fine, except that stupid raid controler. I didn't really think it was going to work anyway.
[/EDIT]