View previous topic :: View next topic |
Author |
Message |
asimon l33t
Joined: 27 Jun 2002 Posts: 979 Location: Germany, Old Europe
|
Posted: Thu Jul 08, 2004 1:42 pm Post subject: |
|
|
Jakub wrote: |
And what about the owner and group of a symlink? Is it always set to root:root but actually never used as well (the owner and group of the original file is important)? |
Yes, if you access a file though it's link the owner and group of the target are used and not of the link itself.
Group and owner of a link can be changed but I don't know why (I still remember a time when a link's owner and group couldn't be changed on Linux). |
|
Back to top |
|
|
Jakub Guru
Joined: 04 Oct 2003 Posts: 377 Location: Warsaw, Poland
|
Posted: Thu Jul 08, 2004 2:07 pm Post subject: |
|
|
Oh, I understand. Thanks. But now I begin to wonder: my user account which isn't in the 'disk' group:
Code: |
romek@mymachine romek $ id
uid=1000(romek) gid=100(users) groups=10(wheel),11(floppy),18(audio),19(cdrom),27(video),35(games),
80(cdrw),85(usb),100(users),250(portage)
|
is able to read from devices /dev/cdroms/cdrom0 and /dev/cdroms/cdrom1, although the permissions set on /dev/hda and /dev/hdd allow reading only for members of the disk group:
Code: |
romek@mymachine romek $ ls -l /dev/hd*
brw-rw---- 1 root disk 3, 0 Jul 8 16:07 /dev/hda
brw-rw---- 1 root disk 22, 64 Jul 8 16:07 /dev/hdd
|
Why is that so? |
|
Back to top |
|
|
asimon l33t
Joined: 27 Jun 2002 Posts: 979 Location: Germany, Old Europe
|
Posted: Thu Jul 08, 2004 3:13 pm Post subject: |
|
|
Jakub wrote: | But now I begin to wonder: my user account which isn't in the 'disk' group [...] is able to read from devices /dev/cdroms/cdrom0 and /dev/cdroms/cdrom1, although the permissions set on /dev/hda and /dev/hdd allow reading only for members of the disk group:
Why is that so? |
How to you read from these devices? Maybe though some cd software which is set suid? Does 'head /dev/cdroms/cdrom0' work? If this works on your system for someone not in the disk groups, than something really strange is going on -- either on your system, or my brain (with preference for the second) |
|
Back to top |
|
|
Jakub Guru
Joined: 04 Oct 2003 Posts: 377 Location: Warsaw, Poland
|
Posted: Thu Jul 08, 2004 3:25 pm Post subject: |
|
|
Well, that's the output:
Code: |
romek@mymachine romek $ head /dev/cdroms/cdrom0
head: cannot open `/dev/cdroms/cdrom0' for reading: Permission denied
|
However, I can view the files on the cd (as an ordinary user) with less, nano, copy them etc. I thought the permissions would not allow it but 'read permissions' probably means something else (and the problem is I'm not knowledgeable enough ). Sorry for bugging you with those stupid questions.
Last edited by Jakub on Mon Jul 26, 2004 1:24 pm; edited 1 time in total |
|
Back to top |
|
|
cyfred Retired Dev
Joined: 23 Aug 2002 Posts: 596
|
Posted: Mon Jul 26, 2004 1:20 pm Post subject: |
|
|
nvidia-kernel-1.0.6106-r1 will now create the devices correctly. |
|
Back to top |
|
|
luisfeser Guru
Joined: 22 May 2004 Posts: 543 Location: /España/Toledo
|
Posted: Tue Aug 17, 2004 6:54 am Post subject: |
|
|
BlindSpy wrote: | After i updated to 2.6.5, my framebuffer resolution has been lowest possible even with vga set to the highest in grub. Any suggestions? |
I have de same problem.
What's the trick?? _________________ AMD Athlon XP-M 2500+ @2200MhHz|1GB DDR @400MHz Dual-Chanel|NVIDIA GeForce4 MX 420|SB Live 5.1|ADSL 512/128 Arsys
gentoo ~x86 |
|
Back to top |
|
|
luisfeser Guru
Joined: 22 May 2004 Posts: 543 Location: /España/Toledo
|
Posted: Wed Aug 18, 2004 3:24 pm Post subject: |
|
|
it seem to be right now (i don't sure why).
But now, when i do depclean it want to remove:
sys-fs/devfsd
It safe to do it? _________________ AMD Athlon XP-M 2500+ @2200MhHz|1GB DDR @400MHz Dual-Chanel|NVIDIA GeForce4 MX 420|SB Live 5.1|ADSL 512/128 Arsys
gentoo ~x86 |
|
Back to top |
|
|
hippysurfer n00b
Joined: 14 Nov 2003 Posts: 51
|
Posted: Thu Aug 19, 2004 9:27 am Post subject: udev rule not creating symlink |
|
|
This has been driving me up the wall.
System:
udev-030
hotplug-20040401
2.6.7-gentoo-r5 (recent clean install)
I am trying to get udev to create a symlink to the mass storage device on my camera. When the camera is plugged in the scsi device is correctly created. The exact name of the device changes but it is always of the form /dev/sd?1:
Quote: |
ant dev # ls -l /dev/sda1
lr-xr-xr-x 1 root root 35 Aug 19 10:11 /dev/sda1 -> scsi/host10/bus0/target0/lun0/part1
|
I have tried both of the following rules in /etc/udev/rules.d/10-local.rules:
Quote: |
BUS="scsi", SYSFS{vendor}="FUJIFILM", NAME="%k", SYMLINK="camera"
BUS="usb", SYSFS{product}="USB Mass Storage", KERNEL="sd?1", NAME="%k", SYMLINK="camera1"
|
I then run udevstart and try connecting and disconnecting the camera, but I never get the symlink.
The udevinfo output is:
Quote: |
ant rules.d # udevinfo -a -p /sys/block/sda/sda1
udevinfo starts with the device the node belongs to and then walks up the
device chain, to print for every device found, all possibly useful attributes
in the udev key format.
Only attributes within one device section may be used together in one rule,
to match the device for which the node will be created.
looking at class device '/sys/block/sda/sda1':
SYSFS{dev}="8:1"
SYSFS{size}="2100609"
SYSFS{start}="63"
SYSFS{stat}=" 178 178 0 0"
follow the class device's "device"
looking at the device chain at '/sys/devices/pci0000:00/0000:00:04.2/usb1/1-2/1-2:1.0/host10/10:0:0:0':
BUS="scsi"
ID="10:0:0:0"
SYSFS{detach_state}="0"
SYSFS{device_blocked}="0"
SYSFS{max_sectors}="240"
SYSFS{model}="USB-DRIVEUNIT "
SYSFS{queue_depth}="1"
SYSFS{rev}="1.00"
SYSFS{scsi_level}="3"
SYSFS{state}="running"
SYSFS{timeout}="30"
SYSFS{type}="0"
SYSFS{vendor}="FUJIFILM"
looking at the device chain at '/sys/devices/pci0000:00/0000:00:04.2/usb1/1-2/1-2:1.0/host10':
BUS=""
ID="host10"
SYSFS{detach_state}="0"
looking at the device chain at '/sys/devices/pci0000:00/0000:00:04.2/usb1/1-2/1-2:1.0':
BUS="usb"
ID="1-2:1.0"
SYSFS{bAlternateSetting}=" 0"
SYSFS{bInterfaceClass}="08"
SYSFS{bInterfaceNumber}="00"
SYSFS{bInterfaceProtocol}="00"
SYSFS{bInterfaceSubClass}="05"
SYSFS{bNumEndpoints}="03"
SYSFS{detach_state}="0"
SYSFS{iInterface}="00"
looking at the device chain at '/sys/devices/pci0000:00/0000:00:04.2/usb1/1-2':
BUS="usb"
ID="1-2"
SYSFS{bConfigurationValue}="1"
SYSFS{bDeviceClass}="00"
SYSFS{bDeviceProtocol}="00"
SYSFS{bDeviceSubClass}="00"
SYSFS{bMaxPower}=" 0mA"
SYSFS{bNumConfigurations}="1"
SYSFS{bNumInterfaces}=" 1"
SYSFS{bcdDevice}="1000"
SYSFS{bmAttributes}="c0"
SYSFS{detach_state}="0"
SYSFS{devnum}="11"
SYSFS{idProduct}="010d"
SYSFS{idVendor}="04cb"
SYSFS{maxchild}="0"
SYSFS{product}="USB Mass Storage"
SYSFS{serial}="Y-348^^^^^020822XFPX0001002816"
SYSFS{speed}="12"
SYSFS{version}=" 1.10"
looking at the device chain at '/sys/devices/pci0000:00/0000:00:04.2/usb1':
BUS="usb"
ID="usb1"
SYSFS{bConfigurationValue}="1"
SYSFS{bDeviceClass}="09"
SYSFS{bDeviceProtocol}="00"
SYSFS{bDeviceSubClass}="00"
SYSFS{bMaxPower}=" 0mA"
SYSFS{bNumConfigurations}="1"
SYSFS{bNumInterfaces}=" 1"
SYSFS{bcdDevice}="0206"
SYSFS{bmAttributes}="c0"
SYSFS{detach_state}="0"
SYSFS{devnum}="1"
SYSFS{idProduct}="0000"
SYSFS{idVendor}="0000"
SYSFS{manufacturer}="Linux 2.6.7-gentoo-r5 uhci_hcd"
SYSFS{maxchild}="2"
SYSFS{product}="VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller"
SYSFS{serial}="0000:00:04.2"
SYSFS{speed}="12"
SYSFS{version}=" 1.10"
looking at the device chain at '/sys/devices/pci0000:00/0000:00:04.2':
BUS="pci"
ID="0000:00:04.2"
SYSFS{class}="0x0c0300"
SYSFS{detach_state}="0"
SYSFS{device}="0x3038"
SYSFS{irq}="9"
SYSFS{subsystem_device}="0x1234"
SYSFS{subsystem_vendor}="0x0925"
SYSFS{vendor}="0x1106"
looking at the device chain at '/sys/devices/pci0000:00':
BUS=""
ID="pci0000:00"
SYSFS{detach_state}="0"
|
One thing that looks a little odd to me is that devfs appears to be running on the /dev filesystem, is this what things are suppose to look like when running the standard gentoo udev setup?
Quote: |
ant rules.d # ps auxww | grep dev
root 1021 0.0 0.0 1684 480 ? S Jul26 0:00 /sbin/devfsd /dev
root 4181 0.0 0.0 1308 336 ? S< 07:11 0:00 udevd
|
Any help or pointers would be very much appreciated.
Richard |
|
Back to top |
|
|
jmusits Tux's lil' helper
Joined: 19 Jan 2004 Posts: 117 Location: New York
|
Posted: Tue Aug 24, 2004 1:33 am Post subject: |
|
|
First off I want to sat thanks to Decible and dsd for the guides they have made. Great work guys, made getting udev up on my system painless. But I do have one problem.
Recently I migrated from gentoo-sources-2.4.25 with devfs to gentoo-dev-sources-2.6.8 with udev. My Sony CLIE and my USB thumbdrive both work fine with udev, even wrote some some rules to get persistent names. But now for my problem I have a HP Photo Scanner 1000 which worked with devfs through usb-storage and sd_mod. However it does not work with udev.
Code: | Aug 23 21:27:36 particle usb 1-1: new full speed USB device using address 3
Aug 23 21:27:37 particle usb-storage: probe of 1-1:1.0 failed with error -1
|
It seems as though udev is getting the info about the device:
Code: | root@particle linux# lsusb -v
Bus 001 Device 003: ID 03f0:1001 Hewlett-Packard
Language IDs: none (invalid length string descriptor 09; len=39)
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.00
bDeviceClass 0 Interface
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x03f0 Hewlett-Packard
idProduct 0x1001
bcdDevice 1.00
iManufacturer 0
iProduct 0
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 39
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk (Zip)
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type none
wMaxPacketSize 2
bInterval 20
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type none
wMaxPacketSize 64
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type none
wMaxPacketSize 64
bInterval 0
Language IDs: none (invalid length string descriptor 09; len=39)
|
However /dev/sda1 is never created as it was w/ devfs.
Anyone have any ideas on what I can try? Am I missing something? I have searched the forums and google for the past week and can't find anything related to my problem.
Thanks,
Jason _________________ If you got the DO RE I got MI.
--Jerry Garcia "Run For The Roses" |
|
Back to top |
|
|
jmusits Tux's lil' helper
Joined: 19 Jan 2004 Posts: 117 Location: New York
|
|
Back to top |
|
|
OldTango l33t
Joined: 21 Feb 2004 Posts: 718
|
Posted: Sun Aug 29, 2004 4:26 pm Post subject: |
|
|
I need a little help with an issue i have on booting with udev.
First i udated my system to the 2004.2 profile.
removed XFREE and installed Xorg
updated system and world files
installed gentoo-dev-sources-2.6.8-r3 kernel
installed udev and configure it according to the docs
installed all dependicies
booted to the new kernel
all is well except that I get this error during boot-up
Code: | /sbin/rc : line 534 5151 segmentation fault /sbin/pam_consel_apply -r
getgrnam failed for cdrw |
and i can't use my cd-writer
my fstab <snip>
Code: | /dev/hda2 /boot ext2 noauto,noatime 1 2
/dev/hda4 / reiserfs notail,rw 0 0
/dev/hda3 none swap sw 0 0
/dev/cdroms/cdrom0 /mnt/cdrom iso9660 noauto,users,ro 0 0
/dev/cdroms/cdrom1 /mnt/cdrw iso9660 noauto,users,ro 0 0
/dev/fd0 /mnt/floppy auto noauto,users 0 0 |
the mount point is in my /mnt directory and the /dev/cdroms/cdrom0 and cdrom1 point to the correct block devices, hdc and hdd respectively.
that is to only place that I am aware of where the trem cdrw is used except in the console.perms file here <snip>
Code: | # permission definitions
<console> 0660 <serial> 0660 root.tty
<console> 0660 <floppy> 0660 root.floppy
<console> 0600 <sound> 0600 root.audio
<console> 0600 <cdrom> 0660 root.cdrom
<console> 0600 <pilot> 0660 root.uucp
<console> 0600 <jaz> 0660 root.disk
<console> 0600 <zip> 0660 root.disk
<console> 0600 <ls120> 0660 root.disk
<console> 0600 <scanner> 0600 root
<console> 0600 <camera> 0600 root
<console> 0600 <memstick> 0600 root
<console> 0600 <flash> 0600 root
<console> 0600 <diskonkey> 0660 root.disk
<console> 0600 <rem_ide> 0660 root.disk
<console> 0600 <fb> 0600 root
<console> 0600 <kbd> 0600 root
<console> 0600 <joystick> 0600 root
<console> 0600 <v4l> 0600 root.sys
<console> 0700 <gpm> 0700 root
<console> 0600 <mainboard> 0600 root
<console> 0660 <burner> 0660 root.cdrw
<console> 0600 <usb> 0660 root.usb
<console> 0600 <rio500> 0600 root
<xconsole> 0600 /dev/console 0600 root.root
<xconsole> 0600 <dri> 0600 root |
can someone point me in the right direction to fix this error. |
|
Back to top |
|
|
Decibels Veteran
Joined: 16 Aug 2002 Posts: 1623 Location: U.S.A.
|
Posted: Mon Aug 30, 2004 4:56 am Post subject: |
|
|
Not on my box right now, but the fix is in console.perms. Look above your snippet there.
Similar to this:
Code: | <burner>=/dev/scd* /dev/sg* /dev/pcd* /dev/pg* /dev/cdwriter /dev/scsi/*/*/*/*/generic |
Basically boils down to changing the /dev/cdrw you might have in there to /dev/cdwriter like above. Had to do this recently myself, but not at home right now.
Check out this thread for more details.
gergrnam error link _________________ Support bacteria – they’re the only culture some people have.”
– Steven Wright |
|
Back to top |
|
|
OldTango l33t
Joined: 21 Feb 2004 Posts: 718
|
Posted: Wed Sep 08, 2004 3:29 pm Post subject: |
|
|
Ok I completely rebuilt my gentoo test drive. Pure udev, no devfs at all in my kernel. However when I emerged my system it emerged devfs. Is it safe to unmerge devfs and then what is the best way to keep it from being emerged during system and world updates.
My kernel is gentoo-dev-sources 2.6.8-r3
So far everything is working great.............................
I also am not using the save tar at all and am going to change the load devfs to no as I do not have support for it complied into my kernel. |
|
Back to top |
|
|
mahir l33t
Joined: 05 Dec 2003 Posts: 725 Location: London
|
Posted: Tue Oct 05, 2004 4:58 pm Post subject: problems |
|
|
i dont get it working
why is htis being mean with me..
Code: | In file included from /usr/src/linux/include/asm/signal.h:7,
from ../klibc/include/signal.h:12,
from ../klibc/syscommon.h:9,
from syscalls/__brk.c:1:
/usr/src/linux/include/linux/compiler.h:120:1: warning: this is the location of the previous definition
make[3]: *** [syscalls/__brk.o] Error 1
make[3]: Leaving directory `/var/tmp/genkernel/udev-030/klibc/klibc'
make[2]: *** [syscalls/static.obj] Error 2
make[2]: Leaving directory `/var/tmp/genkernel/udev-030/klibc/klibc'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/var/tmp/genkernel/udev-030/klibc'
make: *** [/var/tmp/genkernel/udev-030/klibc/klibc/crt0.o] Error 2
* Gentoo Linux Genkernel; Version 3.0.2g
* ERROR: Failed to compile the "KERNEL_DIR=/usr/src/linux USE_KLIBC=true USE_LOG=false DEBUG=false udevdir=/dev all etc/udev/udev.conf" target...
* -- End log... --
|
Code: |
root@jt mahir # emerge --info
Portage 2.0.51_rc7 (gcc34-x86-2004.2, gcc-3.4.2, glibc-2.3.4.20040808-r0, 2.6.9-rc1-love2 i686)
=================================================================
System uname: 2.6.9-rc1-love2 i686 Intel(R) Pentium(R) 4 CPU 3.06GHz
Gentoo Base System version 1.4.16
ccache version 2.3 [enabled]
Autoconf: sys-devel/autoconf-2.59-r4
Automake: sys-devel/automake-1.8.5-r1
Binutils: sys-devel/binutils-2.14.90.0.8-r1
Headers: sys-kernel/linux26-headers-2.6.7-r4
Libtools: sys-devel/libtool-1.5.2-r5
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-O3 -march=pentium4 -mtune=pentium4 -funroll-loops -fomit-frame-pointer -pipe"
CHOST="i686-pc-linux-gnu"
COMPILER=""
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O3 -march=pentium4 -mtune=pentium4 -funroll-loops -fomit-frame-pointer -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache distlocks sandbox"
GENTOO_MIRRORS="http://ftp.heanet.ie/pub/gentoo/"
MAKEOPTS="-j3"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage /usr/local/bmg-main"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="X aalib alsa apm avi berkdb bitmap-fonts cdr chroot crypt cups dvd dvdr eds encode esd esound evo fbcon flac foomaticdb gdbm gif gnome gpm gstreamer gtk gtk2 hal imlib java javascript jpeg libg++ libwww mad mikmod mmx mmx2 motif mozilla mpeg nas ncurses nls nptl oav oggvorbis opengl oss pam pdflib perl png python quicktime readline samba sdl slang sndfile spell sse sse2 ssl svga tcltk tcpd tiff truetype x86 xml2 xmms xprint xv zlib"
other info |
can anyone help/guide me please.. _________________ "wa ma tawfiqi illah billah"
Mahir Sayar |
|
Back to top |
|
|
Decibels Veteran
Joined: 16 Aug 2002 Posts: 1623 Location: U.S.A.
|
Posted: Tue Nov 02, 2004 4:03 pm Post subject: |
|
|
New addition that might be important to some folks. Udev Palm Pilot tutorial by Chris Atkinson. You can find the link in Menu: Misc Devices
or go straight here: Palm Pilot & Udev _________________ Support bacteria – they’re the only culture some people have.”
– Steven Wright |
|
Back to top |
|
|
OldTango l33t
Joined: 21 Feb 2004 Posts: 718
|
Posted: Wed Nov 10, 2004 4:13 pm Post subject: |
|
|
I did an today and it updated udev to .043 everything seemed to go ok except for 2 problems. First I already had to many devices in /dev, 438 to be exact which I think is excessive. After the update I had 694, over 200 more devices were added. The question is why and why are 100's of tty?s and pty?s necessary. Is there a way to control how many get created and how many do I really need?
The second problem is a major headache. When I try to do a reboot of my system, it starts off ok and then segfaults and hangs. I can only reboot by hiting ctrl+c and than the arrow up key and enter again. The system reboots immediately, but on restarting complains about the file system not being cleanly umounted. I am concerned this will cause file coruption sooner than later.
Any ideas on what may be wrong?
TIA |
|
Back to top |
|
|
BetterUnborn n00b
Joined: 28 Sep 2004 Posts: 57 Location: Germany
|
Posted: Fri Dec 31, 2004 3:09 pm Post subject: still havin /dev/pmu problem on ppc |
|
|
Hi there,
udev doesn't create a /dev/pmu device node, so pbbuttonsd won't start up. I've read that I have to crate the device manually by typing Code: | mknod /dev/pmu c 10 154 | But this doesn't help, the command finishes without an error and there is a /dev/pmu but pbbuttonsd still won't start up, it simply tells me Code: | ERROR: Can't open PMU device /dev/pmu: No such device |
I have changed nothing about udev, all configuration files are set up as gentoo did it on installation. |
|
Back to top |
|
|
dsd Developer
Joined: 30 Mar 2003 Posts: 2162 Location: nr London
|
Posted: Fri Dec 31, 2004 3:58 pm Post subject: |
|
|
means that the driver isnt loaded, or that the driver has not detected that particular device _________________ http://dev.gentoo.org/~dsd |
|
Back to top |
|
|
BetterUnborn n00b
Joined: 28 Sep 2004 Posts: 57 Location: Germany
|
Posted: Sat Jan 01, 2005 8:50 pm Post subject: |
|
|
Sorry about that, my bad ...
I forgot to enable Power Management Support for PowerBooks
Now everything is fine and running. |
|
Back to top |
|
|
Loke Apprentice
Joined: 25 May 2002 Posts: 274 Location: Norway
|
Posted: Sun Jan 09, 2005 10:23 pm Post subject: |
|
|
This has probably been answered before, but how do I make udev rescan the scsi-bus? Udev doesnt recognize my cardreader on boot, but if I replug it its recognized and configured correctly. So somehow I need to be able to rescan the scsi bus until this behaviour is fixed.
I read about a rescan_scsi_bus.sh script, but I cant seem to find it...? _________________ I'm not saying there should be capital punishment for stupidity, I'm saying why don't we take the warning labels off of everything, and let the problem take care of itself? |
|
Back to top |
|
|
dsd Developer
Joined: 30 Mar 2003 Posts: 2162 Location: nr London
|
|
Back to top |
|
|
Loke Apprentice
Joined: 25 May 2002 Posts: 274 Location: Norway
|
Posted: Mon Jan 10, 2005 12:06 am Post subject: |
|
|
That didnt resolve my problem, unfortunately. It doesnt make any difference running udevstart, but unplugging the device and replugging it will set it up correctly. However, the cardreader is of the internal type so I have to open up my machine to replug it _________________ I'm not saying there should be capital punishment for stupidity, I'm saying why don't we take the warning labels off of everything, and let the problem take care of itself? |
|
Back to top |
|
|
dsd Developer
Joined: 30 Mar 2003 Posts: 2162 Location: nr London
|
Posted: Mon Jan 10, 2005 12:55 am Post subject: |
|
|
what is your exact problem? is it that you have /dev/sda but not /dev/sda1?
if so, you just need to run "touch /dev/sda" _________________ http://dev.gentoo.org/~dsd |
|
Back to top |
|
|
Loke Apprentice
Joined: 25 May 2002 Posts: 274 Location: Norway
|
Posted: Mon Jan 10, 2005 2:54 am Post subject: |
|
|
dsd wrote: | what is your exact problem? is it that you have /dev/sda but not /dev/sda1?
if so, you just need to run "touch /dev/sda" |
Ive got an internal card reader which is not recognized at boot. (It might not be udev fault, but rather usb-storage. Actually lsusb doesnt display it either at first.) Its the internal type, connected to a USB header on the motherboard. If I disconnect the card reader and reconnect it, usb-storage detects the cardreader, lsusb shows the correct device and udev creates the correct dev entries and everything is working just fine.
However, I cant keep disconnecting and reconnecting the header on the motherboard just to get it working. This behaviour started with a recent kernel upgrade - everything has been working before. Any suggestions appreciated.
Edit: Just to clarify, Im not using the new ub usb structure, but the old one - so my card reader gets dev entries sdb and sdc from udev (main hdd is sda) _________________ I'm not saying there should be capital punishment for stupidity, I'm saying why don't we take the warning labels off of everything, and let the problem take care of itself? |
|
Back to top |
|
|
Loke Apprentice
Joined: 25 May 2002 Posts: 274 Location: Norway
|
Posted: Mon Jan 10, 2005 3:12 am Post subject: |
|
|
This is what dmesg shows during boot:
Code: |
usb 3-1: new full speed USB device using address 2
usb 3-1: control timeout on ep0out
usb 3-1: control timeout on ep0out
usb 3-1: device not accepting address 2, error -110
usb 3-1: new full speed USB device using address 3
usb 3-1: control timeout on ep0out
usb 3-1: control timeout on ep0out
usb 3-1: device not accepting address 3, error -110
|
After unplugging and replugging the card reader I get this:
Code: |
usb 3-1: new full speed USB device using address 4
usb 3-1: can't set config #1, error -110
usb 3-1: new full speed USB device using address 5
scsi2 : SCSI emulation for USB Mass Storage devices
Vendor: USB2.0 Model: CardReader CF RW Rev: 0.0>
Type: Direct-Access ANSI SCSI revision: 02
Attached scsi removable disk sdb at scsi2, channel 0, id 0, lun 0
Attached scsi generic sg1 at scsi2, channel 0, id 0, lun 0, type 0
Vendor: USB2.0 Model: CardReader Combo Rev: 0.0>
Type: Direct-Access ANSI SCSI revision: 02
Attached scsi removable disk sdc at scsi2, channel 0, id 0, lun 1
Attached scsi generic sg2 at scsi2, channel 0, id 0, lun 1, type 0
USB Mass Storage device found at 5
Device not ready. Make sure there is a disc in the drive.
|
It seems to me the cardreader want device 5 on usb3 before it will work, and that usb-storage only probe 1,2 and 3 during boot (?) I really dont understand this.. It can of course be hardware error, but seeing as it worked just fine until a couple of days ago with 2.6.9-r9 but not after upgrading I find it hard to believe. _________________ I'm not saying there should be capital punishment for stupidity, I'm saying why don't we take the warning labels off of everything, and let the problem take care of itself? |
|
Back to top |
|
|
|