Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
2.6 kernel, enabled SCSI and USB but can't use USB stick
View unanswered posts
View posts from last 24 hours

Goto page 1, 2  Next  
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware
View previous topic :: View next topic  
Author Message
Mr_Shameless
Tux's lil' helper
Tux's lil' helper


Joined: 17 Sep 2006
Posts: 90
Location: sumwhere in Asia

PostPosted: Sat Jun 09, 2007 12:44 pm    Post subject: 2.6 kernel, enabled SCSI and USB but can't use USB stick Reply with quote

Hi :)

Im using linux-2.6.20-gentoo-r8. I downloaded the source and compiled the kernel, choosing only what I needed.

I dont have any SCSI drive but I enable SCSI disk to use my USB stick.

I have these options enabled, all of which are built into the kernel:
CONFIG_SCSI, CONFIG_SCSI_PROCFS, CONFIG_BLK_DEV_SD,
CONFIG_USB, CONFIG_USB_DEVICEFS, CONFIG_USB_UHCI_HCD, CONFIG_USB_STORAGE,
CONFIG_FAT_FS, CONFIG_MSDOS_FS, CONFIG_VFAT_FS.

My USB port is only a 1.1 one, not 2.0.

This is the output when I #ls /dev:
Code:
cdrw1    ptyc7  ptyqf  ptyv7  ptyzf   tty7   ttye1  ttys9  ttyx1
console  ptyc8  ptyr0  ptyv8  random  tty8   ttye2  ttysa  ttyx2
core     ptyc9  ptyr1  ptyv9  rtc     tty9   ttye3  ttysb  ttyx3
cpu      ptyca  ptyr2  ptyva  shm     ttyS0  ttye4  ttysc  ttyx4
disk     ptycb  ptyr3  ptyvb  snd     ttyS1  ttye5  ttysd  ttyx5
dri      ptycc  ptyr4  ptyvc  sound   ttyS2  ttye6  ttyse  ttyx6
dsp      ptycd  ptyr5  ptyvd  stderr  ttyS3  ttye7  ttysf  ttyx7
dvd      ptyce  ptyr6  ptyve  stdin   ttya0  ttye8  ttyt0  ttyx8
fd       ptycf  ptyr7  ptyvf  stdout  ttya1  ttye9  ttyt1  ttyx9
fd0      ptyd0  ptyr8  ptyw0  tts     ttya2  ttyea  ttyt2  ttyxa
floppy   ptyd1  ptyr9  ptyw1  tty     ttya3  ttyeb  ttyt3  ttyxb
full     ptyd2  ptyra  ptyw2  tty0    ttya4  ttyec  ttyt4  ttyxc
hda      ptyd3  ptyrb  ptyw3  tty1    ttya5  ttyed  ttyt5  ttyxd
hda1     ptyd4  ptyrc  ptyw4  tty10   ttya6  ttyee  ttyt6  ttyxe
hda2     ptyd5  ptyrd  ptyw5  tty11   ttya7  ttyef  ttyt7  ttyxf
hda3     ptyd6  ptyre  ptyw6  tty12   ttya8  ttyp0  ttyt8  ttyy0
hda4     ptyd7  ptyrf  ptyw7  tty13   ttya9  ttyp1  ttyt9  ttyy1
hdc      ptyd8  ptys0  ptyw8  tty14   ttyaa  ttyp2  ttyta  ttyy2
hdd      ptyd9  ptys1  ptyw9  tty15   ttyab  ttyp3  ttytb  ttyy3
hpet     ptyda  ptys2  ptywa  tty16   ttyac  ttyp4  ttytc  ttyy4
initctl  ptydb  ptys3  ptywb  tty17   ttyad  ttyp5  ttytd  ttyy5
input    ptydc  ptys4  ptywc  tty18   ttyae  ttyp6  ttyte  ttyy6
kmem     ptydd  ptys5  ptywd  tty19   ttyaf  ttyp7  ttytf  ttyy7
kmsg     ptyde  ptys6  ptywe  tty2    ttyb0  ttyp8  ttyu0  ttyy8
log      ptydf  ptys7  ptywf  tty20   ttyb1  ttyp9  ttyu1  ttyy9
mem      ptye0  ptys8  ptyx0  tty21   ttyb2  ttypa  ttyu2  ttyya
misc     ptye1  ptys9  ptyx1  tty22   ttyb3  ttypb  ttyu3  ttyyb
mixer    ptye2  ptysa  ptyx2  tty23   ttyb4  ttypc  ttyu4  ttyyc
null     ptye3  ptysb  ptyx3  tty24   ttyb5  ttypd  ttyu5  ttyyd
port     ptye4  ptysc  ptyx4  tty25   ttyb6  ttype  ttyu6  ttyye
psaux    ptye5  ptysd  ptyx5  tty26   ttyb7  ttypf  ttyu7  ttyyf
ptmx     ptye6  ptyse  ptyx6  tty27   ttyb8  ttyq0  ttyu8  ttyz0
pts      ptye7  ptysf  ptyx7  tty28   ttyb9  ttyq1  ttyu9  ttyz1
ptya0    ptye8  ptyt0  ptyx8  tty29   ttyba  ttyq2  ttyua  ttyz2
ptya1    ptye9  ptyt1  ptyx9  tty3    ttybb  ttyq3  ttyub  ttyz3
ptya2    ptyea  ptyt2  ptyxa  tty30   ttybc  ttyq4  ttyuc  ttyz4
ptya3    ptyeb  ptyt3  ptyxb  tty31   ttybd  ttyq5  ttyud  ttyz5
ptya4    ptyec  ptyt4  ptyxc  tty32   ttybe  ttyq6  ttyue  ttyz6
ptya5    ptyed  ptyt5  ptyxd  tty33   ttybf  ttyq7  ttyuf  ttyz7
ptya6    ptyee  ptyt6  ptyxe  tty34   ttyc0  ttyq8  ttyv0  ttyz8
ptya7    ptyef  ptyt7  ptyxf  tty35   ttyc1  ttyq9  ttyv1  ttyz9
ptya8    ptyp0  ptyt8  ptyy0  tty36   ttyc2  ttyqa  ttyv2  ttyza
ptya9    ptyp1  ptyt9  ptyy1  tty37   ttyc3  ttyqb  ttyv3  ttyzb
ptyaa    ptyp2  ptyta  ptyy2  tty38   ttyc4  ttyqc  ttyv4  ttyzc
ptyab    ptyp3  ptytb  ptyy3  tty39   ttyc5  ttyqd  ttyv5  ttyzd
ptyac    ptyp4  ptytc  ptyy4  tty4    ttyc6  ttyqe  ttyv6  ttyze
ptyad    ptyp5  ptytd  ptyy5  tty40   ttyc7  ttyqf  ttyv7  ttyzf
ptyae    ptyp6  ptyte  ptyy6  tty41   ttyc8  ttyr0  ttyv8  urandom
ptyaf    ptyp7  ptytf  ptyy7  tty42   ttyc9  ttyr1  ttyv9  usbdev1.1_ep00
ptyb0    ptyp8  ptyu0  ptyy8  tty43   ttyca  ttyr2  ttyva  usbdev1.1_ep81
ptyb1    ptyp9  ptyu1  ptyy9  tty44   ttycb  ttyr3  ttyvb  vcs
ptyb2    ptypa  ptyu2  ptyya  tty45   ttycc  ttyr4  ttyvc  vcs1
ptyb3    ptypb  ptyu3  ptyyb  tty46   ttycd  ttyr5  ttyvd  vcs2
ptyb4    ptypc  ptyu4  ptyyc  tty47   ttyce  ttyr6  ttyve  vcs3
ptyb5    ptypd  ptyu5  ptyyd  tty48   ttycf  ttyr7  ttyvf  vcs4
ptyb6    ptype  ptyu6  ptyye  tty49   ttyd0  ttyr8  ttyw0  vcs5
ptyb7    ptypf  ptyu7  ptyyf  tty5    ttyd1  ttyr9  ttyw1  vcs6
ptyb8    ptyq0  ptyu8  ptyz0  tty50   ttyd2  ttyra  ttyw2  vcs7
ptyb9    ptyq1  ptyu9  ptyz1  tty51   ttyd3  ttyrb  ttyw3  vcsa
ptyba    ptyq2  ptyua  ptyz2  tty52   ttyd4  ttyrc  ttyw4  vcsa1
ptybb    ptyq3  ptyub  ptyz3  tty53   ttyd5  ttyrd  ttyw5  vcsa2
ptybc    ptyq4  ptyuc  ptyz4  tty54   ttyd6  ttyre  ttyw6  vcsa3
ptybd    ptyq5  ptyud  ptyz5  tty55   ttyd7  ttyrf  ttyw7  vcsa4
ptybe    ptyq6  ptyue  ptyz6  tty56   ttyd8  ttys0  ttyw8  vcsa5
ptybf    ptyq7  ptyuf  ptyz7  tty57   ttyd9  ttys1  ttyw9  vcsa6
ptyc0    ptyq8  ptyv0  ptyz8  tty58   ttyda  ttys2  ttywa  vcsa7
ptyc1    ptyq9  ptyv1  ptyz9  tty59   ttydb  ttys3  ttywb  zero


If SCSI is enabled, there should be some /dev/sda right?

BTW, I dont quite understand what those pty* are. I've used several linux distros (gentoo included) and FreeBSD, but none of my previous installs had so many devices like this. Is this normal? My previous Gentoo install was from a 700MB CD; I only emerged X and X applications from the internet. But this time I downloaded the minimal CD and installed from there. Maybe it was me doing something wrong here :D

And, the most important, what do I have to do to enable USB stick?

Thank you very much :roll:
Back to top
View user's profile Send private message
Mr_Shameless
Tux's lil' helper
Tux's lil' helper


Joined: 17 Sep 2006
Posts: 90
Location: sumwhere in Asia

PostPosted: Sat Jun 09, 2007 12:48 pm    Post subject: Reply with quote

O, this is the output when I #lsusb:
Code:
Bus 001 Device 001: ID 0000:0000

It doesnt matter if the stick is plugged or not. It's the same like that. I have 2 USB ports, and normally there should be 2 lines like that when nothing is plugged in. When the stick is plugged in, one of the two line displays its name.
Back to top
View user's profile Send private message
Decibels
Veteran
Veteran


Joined: 16 Aug 2002
Posts: 1630
Location: U.S.A.

PostPosted: Sat Jun 09, 2007 1:26 pm    Post subject: Reply with quote

Let's try a few things:

1) Can you stick something like knoppix livecd in and it works? (It will probably be callled something else on different livecd's. But just see if the usb key works.)
I didn't see where you mention you know it works and on this system, so forgive me if missed that.

2) Have you tried installing Hal and dbus stuff. That will really help and I don't know, you might need it nowdays. I really haven't kept track if you need it or not. I just have it and configured pmount and when I plug my key in, window pops up asking me what I want to do with it. Then it is mounted in /media folder.

3) Also did you configure 'USB Mass Storage support' in your kernel?

4) Does other usb stuff work. Just checking if you have the correct Uhci or Ohci support. You can check dmeg ( dmesg | grep -i ohci <if get nothing change ohci to uhci).
Make sure you have that one in the kernel and not the other.


Oh and to one of you questions: Some livecd's will call it something completely different. On my system my key comes up as: /dev/sdc1
_________________
Support bacteria – they’re the only culture some people have.”

– Steven Wright
Back to top
View user's profile Send private message
Mr_Shameless
Tux's lil' helper
Tux's lil' helper


Joined: 17 Sep 2006
Posts: 90
Location: sumwhere in Asia

PostPosted: Sat Jun 09, 2007 3:48 pm    Post subject: Reply with quote

Thank you for your suggestions :)

Quote:
1) Can you stick something like knoppix livecd in and it works? (It will probably be callled something else on different livecd's. But just see if the usb key works.)
I didn't see where you mention you know it works and on this system, so forgive me if missed that.

I have Windows dual booting with Gentoo. I havent tried it today but i remember yesterday it worked on Windows, which was after i installed Gentoo. Right now I'm emerging some stuff so I can't check it but after I'm done i will check it for sure :)

BTW, that thing called "dbus", is it vital? I tried googling it and the second entry read "... a simple way for applications to talk to one another", but i dont quite get it :D. I remember never enabling that USE flags when compiling programs. Could that be the reason? I thought USB devices had something to do with the kernel, not other programs...

Quote:
3) Also did you configure 'USB Mass Storage support' in your kernel?

I checked it. It is CONFIG_USB_STORAGE, isnt it? Then it's already enabled.

Quote:
4) Does other usb stuff work. Just checking if you have the correct Uhci or Ohci support. You can check dmeg ( dmesg | grep -i ohci <if get nothing change ohci to uhci).
Make sure you have that one in the kernel and not the other.

My chipset is an Intel i810. According to Gentoo's kernel guide, i should choose UHCI. I also tried #dmesg | grep -i ohci. Nothing :)

My situation seems hopeless huh? If you need any further information please tell me, i will post them.

Thank you very much :)
Back to top
View user's profile Send private message
Decibels
Veteran
Veteran


Joined: 16 Aug 2002
Posts: 1630
Location: U.S.A.

PostPosted: Sat Jun 09, 2007 4:21 pm    Post subject: Reply with quote

Quote:
I have Windows dual booting with Gentoo. I havent tried it today but i remember yesterday it worked on Windows, which was after i installed Gentoo. Right now I'm emerging some stuff so I can't check it but after I'm done i will check it for sure :)

I was mainly wanting to make sure it wasn't hardware. And a livecd is a good way to make sure that linux works with it. Just incase.

Quote:
BTW, that thing called "dbus", is it vital? I tried googling it and the second entry read "... a simple way for applications to talk to one another", but i dont quite get it :D. I remember never enabling that USE flags when compiling programs. Could that be the reason? I thought USB devices had something to do with the kernel, not other programs...

Vital? Like I said, not really sure. I do believe most people have it now, cause it makes it easier. I did forget if you use it and hal you want to put the USE Flags: hal dbus
in /etc/make.conf. Sorry forgot.
Yes, you do have to make sure usb works kernel wise, but there are 'userspace'/'userland' programs that actually use it. The kernel is just for the drivers. But to actually use it you need to have userland apps. Like dbus, hal,.... But I am not sure dbus and hal are vital, depends on your level of expertise and Desktop Manager (kde, gnome, blackbox,..... fluxbox) you use and wether you want to go the old way and configure usb. Much easier with dbus and hal and pmount.

Quote:
Quote:
3) Also did you configure 'USB Mass Storage support' in your kernel?

I checked it. It is CONFIG_USB_STORAGE, isnt it? Then it's already enabled.

Yes it is.

Quote:
Quote:
4) Does other usb stuff work. Just checking if you have the correct Uhci or Ohci support. You can check dmeg ( dmesg | grep -i ohci <if get nothing change ohci to uhci).
Make sure you have that one in the kernel and not the other.

My chipset is an Intel i810. According to Gentoo's kernel guide, i should choose UHCI. I also tried #dmesg | grep -i ohci. Nothing :)

Then you should have tried 'dmesg | grep -i uhci'
If you don't get anything then, you don't have the kernel setup correctly.
Also, if your box has usb2 capability, you might want to ALSO have Ehci in the kernel.

Quote:
My situation seems hopeless huh?

Nope. If doesn't work with livecd or windows, then it is hopeless. If it does, you can get it figured out.

Quote:
Thank you very much :)
Glad to help. :)
_________________
Support bacteria – they’re the only culture some people have.”

– Steven Wright
Back to top
View user's profile Send private message
daschapa
Tux's lil' helper
Tux's lil' helper


Joined: 01 Sep 2006
Posts: 80

PostPosted: Sat Jun 09, 2007 5:25 pm    Post subject: Reply with quote

I think you are missing SCSI generic support
_________________
======================
Back to top
View user's profile Send private message
Decibels
Veteran
Veteran


Joined: 16 Aug 2002
Posts: 1630
Location: U.S.A.

PostPosted: Sat Jun 09, 2007 5:47 pm    Post subject: Reply with quote

According to the kernel help (at least on my kernel). If he enables, which says has: USB Mass Storage. It turns on scsi and that he will probably need SD, which is in the list of what he has above: CONFIG_BLK_DEV_SD

USB Mass Storage support
Code:
CONFIG_USB_STORAGE:

Say Y here if you want to connect USB mass storage devices to your
computer's USB port. This is the driver you need for USB 
floppy drives, USB hard disks, USB tape drives, USB CD-ROMs,
USB flash devices, and memory sticks, along with   
similar devices. This driver may also be used for some cameras
and card readers.
                                                                                                     
This option 'selects' (turns on, enables) 'SCSI', but you   
probably also need 'SCSI device support: SCSI disk support'
(BLK_DEV_SD) for most USB storage devices.


I have SG enabled in my kernel, but only for my scanner. So you can try it, but don't think you need scsi generic.
Tested mine and 'rmmod sg' since nothing is using it. Check is gone, plug the key in and comes back, still nothing using it. Window comes up asking if I want to open in new window. 'rmmod sg' again and doesn't come back and everything works fine. So don't know why exactly it loads it, but isn't using it. Everything works fine after I remove it. Just comes back when first plug in key. So might be blanket coverage or something from the kernel.

SCSI generic support
Code:
CONFIG_CHR_DEV_SG:                                                                         

If you want to use SCSI scanners, synthesizers or CD-writers or just                   
about anything having "SCSI" in its name other than hard disks,               
CD-ROMs or tapes, say Y here. These won't be supported by the kernel             
directly, so you need some additional software which knows how to               
 talk to these devices using the SCSI protocol:


Mr_Shameless, did you compile any of these as modules? Or in the kernel? If you did as modules did you also enable these in the kernel to automatically load them? The would be under Loadable module support in the kernel config.

[*] Enable loadable module support
[*] Automatic kernel module loading

If you don't you will have to manually loaded them up or put them in /etc/modules.autoload.d/kernel-2.6 file. If you want to know if they are loading, just type in command in console: lsmod
(it only shows modules, not stuff compiled into the kernel).
_________________
Support bacteria – they’re the only culture some people have.”

– Steven Wright
Back to top
View user's profile Send private message
gsoe
Apprentice
Apprentice


Joined: 10 Dec 2006
Posts: 289
Location: Denmark

PostPosted: Sat Jun 09, 2007 8:21 pm    Post subject: Reply with quote

Quote:
O, this is the output when I #lsusb:
Code:
Bus 001 Device 001: ID 0000:0000


It doesnt matter if the stick is plugged or not. It's the same like that. I have 2 USB ports, and normally there should be 2 lines like that when nothing is plugged in. When the stick is plugged in, one of the two line displays its name.
I don't think you're right here. A single USB bus has 2 ports:
Code:
newpc linux # lsusb
Bus 006 Device 001: ID 0000:0000
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 005: ID 03f0:0317 Hewlett-Packard LaserJet 1200
Bus 002 Device 003: ID 046d:c024 Logitech, Inc.
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
but when nothing is plugged in, it only shows one line, so I think your lsusb output is allright.

Your kernel config seems allright for USB sticks too, and you're right that the stick should show up as /dev/sda, but that device will only be there if the stick is plugged in and udev has picked it up. It should do that automatically, so check the output of
Code:
ls /dev | grep ^sd
when the stick is plugged and when it isn't. Now, if it shows that udev doesn't pick up the stick, try booting the machine with the stick plugged and check again. These steps should help in localizing the problem.
If the stick simply isn't there in any case, post the output of the following commands:
Code:
grep ^CONFIG_USB /usr/src/linux/.config
grep ^CONFIG_BLK /usr/src/linux/.config
grep ^CONFIG_SCSI /usr/src/linux/.config
grep ^CONFIG_HOTPLUG /usr/src/linux/.config
grep -i proc_fs /usr/src/linux/.config
grep -i tmpfs /usr/src/linux/.config
dmesg | grep -i uhci
ls /etc/udev/rules.d
Back to top
View user's profile Send private message
tranquilcool
Veteran
Veteran


Joined: 25 Mar 2005
Posts: 1246

PostPosted: Sun Jun 10, 2007 12:07 am    Post subject: Reply with quote

try;

mkdir /media/usbstick
chmod 666 /media/usbstick

try;

mount -t vfat /dev/sda1 /media/usbstick

if there are no errors,
then add to /etc/fstab

/dev/sda1 /media/usbstick auto defaults,user,noauto 0 0

add user to plugdev group.


maybe it works!
_________________
this is a strange strange world.
Back to top
View user's profile Send private message
Mr_Shameless
Tux's lil' helper
Tux's lil' helper


Joined: 17 Sep 2006
Posts: 90
Location: sumwhere in Asia

PostPosted: Sun Jun 10, 2007 6:11 am    Post subject: Reply with quote

Wow, so many helps, thank you all :)

I'm currently using Puppy LiveCD and my USB works.

Puppy doesn't have the lsusb command. I tried #dmesg | grep usb and here is the output:
Code:
usb 1-2: new full speed USB device using uhci_hcd and address 45
//Many similar lines here
usb 1-2: new full speed USB device using uhci_hcd and address 127
usb 1-2: new full speed USB device using uhci_hcd and address 2
usb 1-2: new full speed USB device using uhci_hcd and address 3
usb 1-2: new full speed USB device using uhci_hcd and address 4
usb 1-2: new full speed USB device using uhci_hcd and address 5
usb 1-2: configuration #1 chosen from 1 choice
usb-storage: device found at 5
usb-storage: waiting for device to settle before scanning
usb-storage: device scan complete


Hold on. I will go back to Gentoo and do the other things you told me to.

O, I forgot to mention that my USB worked with my previous Gentoo install, which was less "manual" than this one :D
Back to top
View user's profile Send private message
Mr_Shameless
Tux's lil' helper
Tux's lil' helper


Joined: 17 Sep 2006
Posts: 90
Location: sumwhere in Asia

PostPosted: Sun Jun 10, 2007 6:37 am    Post subject: Reply with quote

OK, im in Gentoo now.

The output of #dmesg | grep -i uhci is a series of lines like this:
Code:
usb 1-2: new full speed USB device using uhci_hcd and address $
where $ is a number from 2 to 127. It's very long. When it reaches 127 it goes back to 2 and repeats that many times. Sorry if I sound stupid here. I dont know anything so I just wanna be as descriptive as possible :D

#ls /dev | grep ^sd doesnt show anything.

#grep ^CONFIG_USB /usr/src/linux/.config
Code:
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB=y
CONFIG_USB_DEVICEFS=y
CONFIG_USB_UHCI_HCD=y
CONFIG_USB_STORAGE=y
CONFIG_USB_MON=y


#grep ^CONFIG_BLK /usr/src/linux/.config
Code:
CONFIG_BLK_DEV_FD=y
CONFIG_BLK_DEV_INITRD=y
CONFIG_BLK_DEV_IDE=y
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_BLK_DEV_IDECD=y
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
CONFIG_BLK_DEV_PIIX=y
CONFIG_BLK_DEV_IDEDMA=y
CONFIG_BLK_DEV_SD=y


#grep ^CONFIG_SCSI /usr/src/linux/.config
Code:
CONFIG_SCSI=y
CONFIG_SCSI_NETLINK=y
CONFIG_SCSI_PROC_FS=y
CONFIG_SCSI_SPI_ATTRS=y
CONFIG_SCSI_FC_ATTRS=y
CONFIG_SCSI_AIC7XXX=y
CONFIG_SCSI_AIC79XX=y


#grep ^CONFIG_HOTPLUG /usr/src/linux/.config
Code:
CONFIG_HOTPLUG=y


#grep -i proc_fs /usr/src/linux/.config
Code:

CONFIG_ACPI_SLEEP_PROC_FS=y
CONFIG_SCSI_PROC_FS=y
CONFIG_PROC_FS=y


#grep -i tmpfs /usr/src/linux/.config
Code:
CONFIG_TMPFS=y
CONFIG_TMPFS_POSIX_ACL=y


#ls /etc/udev/rules.d
Code:
05-udev-early.rules          70-persistent-net.rules
50-udev.rules                75-cd-aliases-generator.rules
60-persistent-input.rules    75-persistent-net-generator.rules
60-persistent-storage.rules  95-net.rules
70-persistent-cd.rules


Thank you for your patience :lol:
Back to top
View user's profile Send private message
Mr_Shameless
Tux's lil' helper
Tux's lil' helper


Joined: 17 Sep 2006
Posts: 90
Location: sumwhere in Asia

PostPosted: Sun Jun 10, 2007 6:42 am    Post subject: Reply with quote

to tranquilcool: I tried but it did not worked. It said
Code:
mount: special device /dev/sda1 does not exist
:)

Next im gonna try enabling SCSI generic.

O, about window managers, I use IceWM (mainly) and Fluxbox, case that helps.
Back to top
View user's profile Send private message
Mr_Shameless
Tux's lil' helper
Tux's lil' helper


Joined: 17 Sep 2006
Posts: 90
Location: sumwhere in Asia

PostPosted: Sun Jun 10, 2007 7:02 am    Post subject: Reply with quote

OK, done. I enabled SCSI generic but it didnt help.

(Looks like im spamming here, lol)
Back to top
View user's profile Send private message
Decibels
Veteran
Veteran


Joined: 16 Aug 2002
Posts: 1630
Location: U.S.A.

PostPosted: Sun Jun 10, 2007 9:00 am    Post subject: Reply with quote

Quote:
OK, done. I enabled SCSI generic but it didnt help.

I tested that out earlier and said didn't need SG driver. But never hurts to try.

I do see one thing that I have seen cause a conflict before. Having OHCI and UCHI both compiled in the kernel. I'm not dead set it is the problem. But back in the old days seen it happen to me. SO, since you have UCHI.

Remove the CONFIG_USB_ARCH_HAS_OHCI=y
and recompile your kernel, move it to boot partition and reboot. See if that helps. Won't hurt for sure, you don't need that driver.
Now, if you did them as modules, then it shouldn't be a problem cause the kernel should just load the ones it needs.

Plus I still think you should emerge hal and debug, add those USE Flags to make.conf. But to each his own.
_________________
Support bacteria – they’re the only culture some people have.”

– Steven Wright


Last edited by Decibels on Sun Jun 10, 2007 9:10 am; edited 1 time in total
Back to top
View user's profile Send private message
tranquilcool
Veteran
Veteran


Joined: 25 Mar 2005
Posts: 1246

PostPosted: Sun Jun 10, 2007 9:08 am    Post subject: Reply with quote

CONFIG_HID=y
CONFIG_USB_HID=y
CONFIG_USB_HIDDEV=y
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB=y
CONFIG_USB_DEVICEFS=y
CONFIG_USB_EHCI_HCD=m
CONFIG_USB_EHCI_SPLIT_ISO=y
CONFIG_USB_EHCI_ROOT_HUB_TT=y
CONFIG_USB_OHCI_HCD=m
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_UHCI_HCD=m
CONFIG_USB_STORAGE=y
CONFIG_USB_STORAGE_FREECOM=y
CONFIG_USB_MON=y
CONFIG_USB_SERIAL=m
CONFIG_USB_SERIAL_GENERIC=y
CONFIG_USB_SERIAL_OPTION=m
CONFIG_USB_BERRY_CHARGE=m
CONFIG_USB_SISUSBVGA=m


CONFIG_SCSI=y
CONFIG_BLK_DEV_SD=m
CONFIG_CHR_DEV_SG=m
CONFIG_SCSI_WAIT_SCAN=m

these are my usb and scsi sections in .config.
forget the test mount and just edit fstab reboot and retry
you must enable scsi generic
_________________
this is a strange strange world.


Last edited by tranquilcool on Sun Jun 10, 2007 9:11 am; edited 1 time in total
Back to top
View user's profile Send private message
DirtyHairy
l33t
l33t


Joined: 03 Jul 2006
Posts: 608
Location: Würzburg, Deutschland

PostPosted: Sun Jun 10, 2007 9:11 am    Post subject: Reply with quote

After plugging a USB mass storage device into a working system, dmesg should say something like
Code:
usb 1-2: new high speed USB device using ehci_hcd and address 2
usb 1-2: configuration #1 chosen from 1 choice
Initializing USB Mass Storage driver...
scsi2 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
scsi 2:0:0:0: Direct-Access     JetFlash TS128MJF2A       1.00 PQ: 0 ANSI: 2
SCSI device sdb: 254000 512-byte hdwr sectors (130 MB)
sdb: Write Protect is off
sdb: Mode Sense: 0b 00 00 08
sdb: assuming drive cache: write through
SCSI device sdb: 254000 512-byte hdwr sectors (130 MB)
sdb: Write Protect is off
sdb: Mode Sense: 0b 00 00 08
sdb: assuming drive cache: write through
 sdb: sdb1
sd 2:0:0:0: Attached scsi removable disk sdb
sd 2:0:0:0: Attached scsi generic sg2 type 0
usb-storage: device scan complete

HAL and dbus have absolutely nothing to do with this; you plug the device in, and if USB is working and the mass storage device driver is present, it will claim the device, scan it and, if it was succesful, udev will be notified which then creates the necessary device nodes. Afaik, HAL is just a piece of glue that provides a standardized way for applications (mainly desktop environments) to do tasks as mounting and unmounting; dbus is a demon that provides a sophisticated way of communication between applications.

Whats the content of those many lines you mention in dmesg? Also, what's the output of lspci?
Back to top
View user's profile Send private message
gsoe
Apprentice
Apprentice


Joined: 10 Dec 2006
Posts: 289
Location: Denmark

PostPosted: Sun Jun 10, 2007 9:39 am    Post subject: Reply with quote

DirtyHairy: Exactly!

Now lets see if the usbstick was found: After booting with the stick plugged do
Code:
dmesg | grep -i usb
You don't need to post all the usb 1-2: new full speed USB device using uhci_hcd and address lines, a description is fine.
Now, to see the full dmesg output caused by the stick alone do the following: Unplug the stick and run
Code:
dmesg -c
then plug it back in and run
Code:
dmesg
and post the output of the last command.

EDIT: About conflicts ohci/uhci: I never experienced that, but it won't hurt to remove ohci before doing the above. ehci is USB 2.0, remove that too.
EDIT EDIT: The CONFIG_USB_ARCH_HAS_OHCI/EHCI are different from the OHCI/EHCI drivers. They seem to be some kind of generic options that don't disappear, even if everything in the usb section is removed from menuconfig. Don't bother.
Back to top
View user's profile Send private message
Mr_Shameless
Tux's lil' helper
Tux's lil' helper


Joined: 17 Sep 2006
Posts: 90
Location: sumwhere in Asia

PostPosted: Sun Jun 10, 2007 11:08 am    Post subject: Reply with quote

When compiling the kernel, I did notice and disable EHCI and OHCI (CONFIG_USB_EHCI_HCD and CONFIG_USB_OHCI_HCD).

Quote:
Remove the CONFIG_USB_ARCH_HAS_OHCI=y
I searched for that in the menu, but it didnt display the path to it. I looked under "Device drivers" --> "USB Support" but couldn't find it. I editted the .config file by hand, trying to delete/comment out that line but after the kernel is compiled, i checked it and that line is brought back again.

Here are the outputs:
#dmesg | grep -i usb
Code:
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
usbmon: debugfs is not available
USB Universal Host Controller Interface driver v3.0
uhci_hcd 0000:00:1f.2: new USB bus registered, assigned bus number 1
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
Initializing USB Mass Storage driver...
usb 1-2: new full speed USB device using uhci_hcd and address 2
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usb 1-2: new full speed USB device using uhci_hcd and address 3
usb 1-2: new full speed USB device using uhci_hcd and address 4
usb 1-2: new full speed USB device using uhci_hcd and address 5

//Many lines like that, numbers running from 2 to 127 then back to 2, repeating many times.



#dmesg -c
Code:
Linux version 2.6.20-gentoo-r8 (root@phnguyen) (gcc version 4.1.1 (Gentoo 4.1.1-r3)) #7 PREEMPT Sun Jun 10 16:41:34 ICT 2007
BIOS-provided physical RAM map:
sanitize start
sanitize end
copy_e820_map() start: 0000000000000000 size: 000000000009fc00 end: 000000000009fc00 type: 1
copy_e820_map() type is E820_RAM
copy_e820_map() start: 000000000009fc00 size: 0000000000000400 end: 00000000000a0000 type: 2
copy_e820_map() start: 00000000000f0000 size: 0000000000010000 end: 0000000000100000 type: 2
copy_e820_map() start: 0000000000100000 size: 000000001fdf0000 end: 000000001fef0000 type: 1
copy_e820_map() type is E820_RAM
copy_e820_map() start: 000000001fef0000 size: 0000000000003000 end: 000000001fef3000 type: 4
copy_e820_map() start: 000000001fef3000 size: 000000000000d000 end: 000000001ff00000 type: 3
copy_e820_map() start: 00000000ffb00000 size: 0000000000500000 end: 0000000100000000 type: 2
 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 000000001fef0000 (usable)
 BIOS-e820: 000000001fef0000 - 000000001fef3000 (ACPI NVS)
 BIOS-e820: 000000001fef3000 - 000000001ff00000 (ACPI data)
 BIOS-e820: 00000000ffb00000 - 0000000100000000 (reserved)
510MB LOWMEM available.
Entering add_active_range(0, 0, 130800) 0 entries of 256 used
Zone PFN ranges:
  DMA             0 ->     4096
  Normal       4096 ->   130800
early_node_map[1] active PFN ranges
    0:        0 ->   130800
On node 0 totalpages: 130800
  DMA zone: 32 pages used for memmap
  DMA zone: 0 pages reserved
  DMA zone: 4064 pages, LIFO batch:0
  Normal zone: 989 pages used for memmap
  Normal zone: 125715 pages, LIFO batch:31
DMI 2.1 present.
ACPI: RSDP (v000 GBT                                   ) @ 0x000f6a00
ACPI: RSDT (v001 GBT    AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x1fef3000
ACPI: FADT (v001 GBT    AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x1fef3040
ACPI: DSDT (v001 GBT    AWRDACPI 0x00001000 MSFT 0x0100000c) @ 0x00000000
ACPI: PM-Timer IO Port: 0x4008
Allocating PCI resources starting at 20000000 (gap: 1ff00000:dfc00000)
Detected 668.216 MHz processor.
Built 1 zonelists.  Total pages: 129779
Kernel command line: root=/dev/hda3
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 8192 bytes)
Console: colour VGA+ 80x25
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 513180k/523200k available (3116k kernel code, 9468k reserved, 1099k data, 212k init, 0k highmem)
virtual kernel memory layout:
    fixmap  : 0xffff8000 - 0xfffff000   (  28 kB)
    vmalloc : 0xe0800000 - 0xffff6000   ( 503 MB)
    lowmem  : 0xc0000000 - 0xdfef0000   ( 510 MB)
      .init : 0xc0522000 - 0xc0557000   ( 212 kB)
      .data : 0xc040b3d2 - 0xc051e1b8   (1099 kB)
      .text : 0xc0100000 - 0xc040b3d2   (3116 kB)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 1337.10 BogoMIPS (lpj=668552)
Mount-cache hash table entries: 512
CPU: After generic identify, caps: 0383f9ff 00000000 00000000 00000000 00000000 00000000 00000000
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 128K
CPU: After all inits, caps: 0383f9ff 00000000 00000000 00000040 00000000 00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Compat vDSO mapped to ffffe000.
CPU: Intel Celeron (Coppermine) stepping 03
Checking 'hlt' instruction... OK.
ACPI: Core revision 20060707
 tbxface-0107 [01] load_tables           : ACPI Tables successfully acquired
Parsing all Control Methods:
Table [DSDT](id 0005) - 424 Objects with 32 Devices 94 Methods 33 Regions
ACPI Namespace successfully loaded at root c05a4c70
ACPI: setting ELCR to 0200 (from 0820)
evxfevnt-0089 [02] enable                : Transition to ACPI mode successful
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xfb0d0, last bus=1
PCI: Using configuration type 1
Setting up standard PCI resources
evgpeblk-0951 [04] ev_create_gpe_block   : GPE 00 to 0F [_GPE] 2 regs on int 0x9
evgpeblk-0951 [04] ev_create_gpe_block   : GPE 10 to 1F [_GPE] 2 regs on int 0x9
evgpeblk-1048 [03] ev_initialize_gpe_bloc: Found 1 Wake, Enabled 0 Runtime GPEs in this block
evgpeblk-1048 [03] ev_initialize_gpe_bloc: Found 2 Wake, Enabled 0 Runtime GPEs in this block
Completing Region/Field/Buffer/Package initialization:.........................................................................................
Initialized 33/33 Regions 25/25 Fields 23/23 Buffers 8/11 Packages (433 nodes)
Initializing Device/Processor/Thermal objects by executing _INI methods:..
Executed 2 _INI methods requiring 1 _STA executions (examined 36 objects)
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
ACPI: Assume root bridge [\_SB_.PCI0] bus is 0
Boot video device is 0000:00:01.0
PCI quirk: region 4000-407f claimed by ICH4 ACPI/GPIO/TCO
PCI quirk: region 4080-40bf claimed by ICH4 GPIO
PCI: Transparent bridge - 0000:00:1e.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 *5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 *5 6 7 10 11 12 14 15)
Linux Plug and Play Support v0.97 (c) Adam Belay
SCSI subsystem initialized
libata version 2.00 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
PCI: Ignore bogus resource 6 [0:0] of 0000:00:01.0
PCI: Bridge: 0000:00:1e.0
  IO window: c000-cfff
  MEM window: d4000000-d40fffff
  PREFETCH window: disabled.
PCI: Setting latency timer of device 0000:00:1e.0 to 64
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 16384 bind 8192)
TCP reno registered
Total HugeTLB memory allocated, 0
NTFS driver 2.1.28 [Flags: R/W].
io scheduler noop registered
io scheduler deadline registered (default)
io scheduler cfq registered
Real Time Clock Driver v1.12ac
intel_rng: FWH not detected
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Detected an Intel i810 E Chipset.
agpgart: AGP aperture is 64M @ 0xd0000000
Hangcheck: starting hangcheck timer 0.9.0 (tick is 180 seconds, margin is 60 seconds).
Hangcheck: Using get_cycles().
input: Power Button (FF) as /class/input/input0
ACPI: Power Button (FF) [PWRF]
input: Power Button (CM) as /class/input/input1
ACPI: Power Button (CM) [PWRB]
input: Sleep Button (CM) as /class/input/input2
ACPI: Sleep Button (CM) [SLPB]
ACPI: Fan [FAN] (on)
ACPI: CPU0 (power states: C1[C1] C2[C2])
ACPI: Processor [CPU0] (supports 2 throttling states)
ACPI: Thermal Zone [THRM] (27 C)
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ICH: IDE controller at PCI slot 0000:00:1f.1
ICH: chipset revision 2
ICH: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:pio
    ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
Probing IDE interface ide0...
hda: QUANTUM FIREBALLP AS20.5, ATA DISK drive
hda: hw_config=604d
hda: hw_config=604d
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: ASUS DVD-E616A2, ATAPI CD/DVD-ROM drive
hdd: SAMSUNG CD-R/RW SW-252B, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 128KiB
hda: 40132503 sectors (20547 MB) w/1902KiB Cache, CHS=39813/16/63<6>hda: hw_config=604d
, UDMA(66)
hda: cache flushes not supported
 hda: hda1 hda2 hda3 hda4
hdc: ATAPI 48X DVD-ROM drive, 2048kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
hdd: ATAPI 52X CD-ROM CD-R/RW drive, 8192kB Cache, UDMA(33)
usbmon: debugfs is not available
USB Universal Host Controller Interface driver v3.0
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 5
PCI: setting IRQ 5 as level-triggered
ACPI: PCI Interrupt 0000:00:1f.2[D] -> Link [LNKD] -> GSI 5 (level, low) -> IRQ 5
PCI: Setting latency timer of device 0000:00:1f.2 to 64
uhci_hcd 0000:00:1f.2: UHCI Host Controller
uhci_hcd 0000:00:1f.2: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:1f.2: irq 5, io base 0x0000d000
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
Initializing USB Mass Storage driver...
usb 1-2: new full speed USB device using uhci_hcd and address 2
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
PNP: No PS/2 controller found. Probing ports directly.
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
input: AT Translated Set 2 keyboard as /class/input/input3
Advanced Linux Sound Architecture Driver Version 1.0.14rc1 (Tue Jan 09 09:56:17 2007 UTC).
ALSA device list:
  No soundcards found.
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 10
IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
Using IPI Shortcut mode
ACPI: (supports S0 S1 S3 S4 S5)
Time: tsc clocksource has been installed.
Time: acpi_pm clocksource has been installed.
usb 1-2: new full speed USB device using uhci_hcd and address 3
input: ImPS/2 Generic Wheel Mouse as /class/input/input4
ReiserFS: hda3: found reiserfs format "3.6" with standard journal
ReiserFS: hda3: using ordered data mode
ReiserFS: hda3: journal params: device hda3, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: hda3: checking transaction log (hda3)
ReiserFS: hda3: Using r5 hash to sort names
VFS: Mounted root (reiserfs filesystem) readonly.
Freeing unused kernel memory: 212k freed
usb 1-2: new full speed USB device using uhci_hcd and address 4
usb 1-2: new full speed USB device using uhci_hcd and address 5
usb 1-2: new full speed USB device using uhci_hcd and address 6
usb 1-2: new full speed USB device using uhci_hcd and address 7
usb 1-2: new full speed USB device using uhci_hcd and address 8
usb 1-2: new full speed USB device using uhci_hcd and address 9
usb 1-2: new full speed USB device using uhci_hcd and address 10
usb 1-2: new full speed USB device using uhci_hcd and address 11
usb 1-2: new full speed USB device using uhci_hcd and address 12
usb 1-2: new full speed USB device using uhci_hcd and address 13
usb 1-2: new full speed USB device using uhci_hcd and address 14
usb 1-2: new full speed USB device using uhci_hcd and address 15
usb 1-2: new full speed USB device using uhci_hcd and address 16
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 5
ACPI: PCI Interrupt 0000:01:05.0[A] -> Link [LNKC] -> GSI 5 (level, low) -> IRQ 5
8139too Fast Ethernet driver 0.9.28
usb 1-2: new full speed USB device using uhci_hcd and address 17
usb 1-2: new full speed USB device using uhci_hcd and address 18
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11
PCI: setting IRQ 11 as level-triggered
ACPI: PCI Interrupt 0000:01:03.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
eth0: RealTek RTL8139 at 0xe085a000, 00:11:3b:05:90:ed, IRQ 11
eth0:  Identified 8139 chip type 'RTL-8100B/8139D'
usb 1-2: new full speed USB device using uhci_hcd and address 19
usb 1-2: new full speed USB device using uhci_hcd and address 20
usb 1-2: new full speed USB device using uhci_hcd and address 21
usb 1-2: new full speed USB device using uhci_hcd and address 22
Adding 500464k swap on /dev/hda4.  Priority:-1 extents:1 across:500464k
usb 1-2: new full speed USB device using uhci_hcd and address 23
usb 1-2: new full speed USB device using uhci_hcd and address 24
usb 1-2: new full speed USB device using uhci_hcd and address 25

//Many lines, too


#dmesg
Code:
usb 1-2: new full speed USB device using uhci_hcd and address 116
usb 1-2: new full speed USB device using uhci_hcd and address 117
usb 1-2: new full speed USB device using uhci_hcd and address 118
usb 1-2: new full speed USB device using uhci_hcd and address 119
usb 1-2: new full speed USB device using uhci_hcd and address 120
usb 1-2: new full speed USB device using uhci_hcd and address 121
usb 1-2: new full speed USB device using uhci_hcd and address 122
usb 1-2: new full speed USB device using uhci_hcd and address 123
usb 1-2: new full speed USB device using uhci_hcd and address 124
usb 1-2: new full speed USB device using uhci_hcd and address 125


Thank you for your patience :D

PS: O, btw, my USB doesnt flash at all.
Back to top
View user's profile Send private message
kernelOfTruth
Watchman
Watchman


Joined: 20 Dec 2005
Posts: 6111
Location: Vienna, Austria; Germany; hello world :)

PostPosted: Sun Jun 10, 2007 11:49 am    Post subject: Reply with quote

if your usb-part doesn't want to work in all cases, please consider trying out a higher kernel-version or lower (e.g. 2.6.21-r2, you mgiht need to unmask it in /etc/portage/package.keywords)

I happened to encounter a similar behavior with some 2.6.20-kernels :roll:

good luck :wink:
_________________
https://github.com/kernelOfTruth/ZFS-for-SystemRescueCD/tree/ZFS-for-SysRescCD-4.9.0
https://github.com/kernelOfTruth/pulseaudio-equalizer-ladspa

Hardcore Gentoo Linux user since 2004 :D
Back to top
View user's profile Send private message
Decibels
Veteran
Veteran


Joined: 16 Aug 2002
Posts: 1630
Location: U.S.A.

PostPosted: Sun Jun 10, 2007 11:51 am    Post subject: Reply with quote

I wasn't mentioning hal and dbus as fixes, just making life easier when he got it working. Which I also thought would have happened by now. :(

I wasn't at home to check but if you have Ohci compiled in or as module it will show as this:
CONFIG_USB_OHCI_HCD=y or m for module


Something no one has mentioned. See if udev is even seeing your key, maybe it is calling it something else? Who knows but you can try this: (and at the end you can see my partition is 'finally' called /dev/sdc1 and the key is /dev/sdc )
type: udevmonitor --env (as root) and hit enter. Then plug the usb key in and see if prints anything out to console. We should see something here to tell us where to look next.

Code:
linux # udevmonitor --env
udevmonitor prints the received event from the kernel [UEVENT]
and the event which udev sends out after rule processing [UDEV]

UEVENT[1181476138.754855] add@/devices/pci0000:00/0000:00:02.2/usb1/1-1
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:02.2/usb1/1-1
SUBSYSTEM=usb
SEQNUM=1987
PHYSDEVBUS=usb
PHYSDEVDRIVER=usb

UEVENT[1181476138.754921] add@/devices/pci0000:00/0000:00:02.2/usb1/1-1/usbdev1.5_ep00
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:02.2/usb1/1-1/usbdev1.5_ep00
SUBSYSTEM=usb_endpoint
SEQNUM=1988
MAJOR=442
MINOR=4

UEVENT[1181476138.755071] add@/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1:1.0
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1:1.0
SUBSYSTEM=usb
SEQNUM=1989
PHYSDEVBUS=usb
DEVICE=/proc/bus/usb/001/005
PRODUCT=67b/2515/1
TYPE=9/0/1
INTERFACE=9/0/0
MODALIAS=usb:v067Bp2515d0001dc09dsc00dp01ic09isc00ip00

UDEV  [1181476138.757650] add@/devices/pci0000:00/0000:00:02.2/usb1/1-1
UDEV_LOG=3
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:02.2/usb1/1-1
SUBSYSTEM=usb
SEQNUM=1987
PHYSDEVBUS=usb
PHYSDEVDRIVER=usb
UDEVD_EVENT=1
DRIVER=usb
IN_HOTPLUG=1

UDEV  [1181476138.790670] add@/devices/pci0000:00/0000:00:02.2/usb1/1-1/usbdev1.5_ep00
UDEV_LOG=3
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:02.2/usb1/1-1/usbdev1.5_ep00
SUBSYSTEM=usb_endpoint
SEQNUM=1988
MAJOR=442
MINOR=4
UDEVD_EVENT=1
IN_HOTPLUG=1
DEVNAME=/dev/usbdev1.5_ep00

UDEV  [1181476138.803017] add@/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1:1.0
UDEV_LOG=3
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1:1.0
SUBSYSTEM=usb
SEQNUM=1989
PHYSDEVBUS=usb
DEVICE=/proc/bus/usb/001/005
PRODUCT=67b/2515/1
TYPE=9/0/1
INTERFACE=9/0/0
MODALIAS=usb:v067Bp2515d0001dc09dsc00dp01ic09isc00ip00
UDEVD_EVENT=1
IN_HOTPLUG=1

UEVENT[1181476138.857407] add@/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1:1.0/usbdev1.5_ep81
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1:1.0/usbdev1.5_ep81
SUBSYSTEM=usb_endpoint
SEQNUM=1990
MAJOR=442
MINOR=4

UEVENT[1181476138.857449] add@/class/usb_device/usbdev1.5
ACTION=add
DEVPATH=/class/usb_device/usbdev1.5
SUBSYSTEM=usb_device
SEQNUM=1991
PHYSDEVPATH=/devices/pci0000:00/0000:00:02.2/usb1/1-1
PHYSDEVBUS=usb
PHYSDEVDRIVER=usb
MAJOR=189
MINOR=4

UDEV  [1181476138.875275] add@/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1:1.0/usbdev1.5_ep81
UDEV_LOG=3
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1:1.0/usbdev1.5_ep81
SUBSYSTEM=usb_endpoint
SEQNUM=1990
MAJOR=442
MINOR=4
UDEVD_EVENT=1
IN_HOTPLUG=1
DEVNAME=/dev/usbdev1.5_ep81

UDEV  [1181476138.898662] add@/class/usb_device/usbdev1.5
UDEV_LOG=3
ACTION=add
DEVPATH=/class/usb_device/usbdev1.5
SUBSYSTEM=usb_device
SEQNUM=1991
PHYSDEVPATH=/devices/pci0000:00/0000:00:02.2/usb1/1-1
PHYSDEVBUS=usb
PHYSDEVDRIVER=usb
MAJOR=189
MINOR=4
UDEVD_EVENT=1
IN_HOTPLUG=1
DEVNAME=/dev/bus/usb/001/005

UEVENT[1181476139.163025] add@/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1.1
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1.1
SUBSYSTEM=usb
SEQNUM=1992
PHYSDEVBUS=usb
PHYSDEVDRIVER=usb

UEVENT[1181476139.163066] add@/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1.1/usbdev1.6_ep00
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1.1/usbdev1.6_ep00
SUBSYSTEM=usb_endpoint
SEQNUM=1993
MAJOR=442
MINOR=5

UEVENT[1181476139.163880] add@/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1.1/1-1.1:1.0
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1.1/1-1.1:1.0
SUBSYSTEM=usb
SEQNUM=1994
PHYSDEVBUS=usb
DEVICE=/proc/bus/usb/001/006
PRODUCT=67b/2517/1
TYPE=0/0/0
INTERFACE=8/5/80
MODALIAS=usb:v067Bp2517d0001dc00dsc00dp00ic08isc05ip50

UEVENT[1181476139.163913] add@/class/scsi_host/host5
ACTION=add
DEVPATH=/class/scsi_host/host5
SUBSYSTEM=scsi_host
SEQNUM=1995
PHYSDEVPATH=/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1.1/1-1.1:1.0/host5

UEVENT[1181476139.163932] add@/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1.1/1-1.1:1.0/usbdev1.6_ep01
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1.1/1-1.1:1.0/usbdev1.6_ep01
SUBSYSTEM=usb_endpoint
SEQNUM=1996
MAJOR=442
MINOR=5

UEVENT[1181476139.163953] add@/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1.1/1-1.1:1.0/usbdev1.6_ep82
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1.1/1-1.1:1.0/usbdev1.6_ep82
SUBSYSTEM=usb_endpoint
SEQNUM=1997
MAJOR=442
MINOR=5

UEVENT[1181476139.163974] add@/class/usb_device/usbdev1.6
ACTION=add
DEVPATH=/class/usb_device/usbdev1.6
SUBSYSTEM=usb_device
SEQNUM=1998
PHYSDEVPATH=/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1.1
PHYSDEVBUS=usb
PHYSDEVDRIVER=usb
MAJOR=189
MINOR=5

UDEV  [1181476139.167499] add@/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1.1
UDEV_LOG=3
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1.1
SUBSYSTEM=usb
SEQNUM=1992
PHYSDEVBUS=usb
PHYSDEVDRIVER=usb
UDEVD_EVENT=1
DRIVER=usb
IN_HOTPLUG=1

UDEV  [1181476139.203961] add@/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1.1/usbdev1.6_ep00
UDEV_LOG=3
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1.1/usbdev1.6_ep00
SUBSYSTEM=usb_endpoint
SEQNUM=1993
MAJOR=442
MINOR=5
UDEVD_EVENT=1
IN_HOTPLUG=1
DEVNAME=/dev/usbdev1.6_ep00

UDEV  [1181476139.210285] add@/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1.1/1-1.1:1.0
UDEV_LOG=3
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1.1/1-1.1:1.0
SUBSYSTEM=usb
SEQNUM=1994
PHYSDEVBUS=usb
DEVICE=/proc/bus/usb/001/006
PRODUCT=67b/2517/1
TYPE=0/0/0
INTERFACE=8/5/80
MODALIAS=usb:v067Bp2517d0001dc00dsc00dp00ic08isc05ip50
UDEVD_EVENT=1
IN_HOTPLUG=1

UDEV  [1181476139.213021] add@/class/scsi_host/host5
UDEV_LOG=3
ACTION=add
DEVPATH=/class/scsi_host/host5
SUBSYSTEM=scsi_host
SEQNUM=1995
PHYSDEVPATH=/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1.1/1-1.1:1.0/host5
UDEVD_EVENT=1
IN_HOTPLUG=1

UDEV  [1181476139.245395] add@/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1.1/1-1.1:1.0/usbdev1.6_ep82
UDEV_LOG=3
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1.1/1-1.1:1.0/usbdev1.6_ep82
SUBSYSTEM=usb_endpoint
SEQNUM=1997
MAJOR=442
MINOR=5
UDEVD_EVENT=1
IN_HOTPLUG=1
DEVNAME=/dev/usbdev1.6_ep82

UDEV  [1181476139.250609] add@/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1.1/1-1.1:1.0/usbdev1.6_ep01
UDEV_LOG=3
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1.1/1-1.1:1.0/usbdev1.6_ep01
SUBSYSTEM=usb_endpoint
SEQNUM=1996
MAJOR=442
MINOR=5
UDEVD_EVENT=1
IN_HOTPLUG=1
DEVNAME=/dev/usbdev1.6_ep01

UDEV  [1181476139.273601] add@/class/usb_device/usbdev1.6
UDEV_LOG=3
ACTION=add
DEVPATH=/class/usb_device/usbdev1.6
SUBSYSTEM=usb_device
SEQNUM=1998
PHYSDEVPATH=/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1.1
PHYSDEVBUS=usb
PHYSDEVDRIVER=usb
MAJOR=189
MINOR=5
UDEVD_EVENT=1
IN_HOTPLUG=1
DEVNAME=/dev/bus/usb/001/006

UEVENT[1181476144.166394] add@/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1.1/1-1.1:1.0/host5/target5:0:0/5:0:0:0
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1.1/1-1.1:1.0/host5/target5:0:0/5:0:0:0
SUBSYSTEM=scsi
SEQNUM=1999
PHYSDEVBUS=scsi

UEVENT[1181476144.166437] add@/class/scsi_disk/5:0:0:0
ACTION=add
DEVPATH=/class/scsi_disk/5:0:0:0
SUBSYSTEM=scsi_disk
SEQNUM=2000
PHYSDEVPATH=/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1.1/1-1.1:1.0/host5/target5:0:0/5:0:0:0
PHYSDEVBUS=scsi
PHYSDEVDRIVER=sd

UEVENT[1181476144.172371] add@/block/sdc
ACTION=add
DEVPATH=/block/sdc
SUBSYSTEM=block
SEQNUM=2001
MINOR=32
MAJOR=8
PHYSDEVPATH=/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1.1/1-1.1:1.0/host5/target5:0:0/5:0:0:0
PHYSDEVBUS=scsi
PHYSDEVDRIVER=sd

UEVENT[1181476144.172402] add@/block/sdc/sdc1
ACTION=add
DEVPATH=/block/sdc/sdc1
SUBSYSTEM=block
SEQNUM=2002
MINOR=33
MAJOR=8
PHYSDEVPATH=/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1.1/1-1.1:1.0/host5/target5:0:0/5:0:0:0
PHYSDEVBUS=scsi
PHYSDEVDRIVER=sd

UEVENT[1181476144.172430] add@/class/scsi_device/5:0:0:0
ACTION=add
DEVPATH=/class/scsi_device/5:0:0:0
SUBSYSTEM=scsi_device
SEQNUM=2003
PHYSDEVPATH=/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1.1/1-1.1:1.0/host5/target5:0:0/5:0:0:0
PHYSDEVBUS=scsi
PHYSDEVDRIVER=sd

UEVENT[1181476144.172454] add@/class/scsi_generic/sg2
ACTION=add
DEVPATH=/class/scsi_generic/sg2
SUBSYSTEM=scsi_generic
SEQNUM=2004
PHYSDEVPATH=/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1.1/1-1.1:1.0/host5/target5:0:0/5:0:0:0
PHYSDEVBUS=scsi
PHYSDEVDRIVER=sd
MAJOR=21
MINOR=2

UDEV  [1181476144.194953] add@/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1.1/1-1.1:1.0/host5/target5:0:0/5:0:0:0
UDEV_LOG=3
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1.1/1-1.1:1.0/host5/target5:0:0/5:0:0:0
SUBSYSTEM=scsi
SEQNUM=1999
PHYSDEVBUS=scsi
UDEVD_EVENT=1
IN_HOTPLUG=1

UDEV  [1181476144.201664] add@/class/scsi_disk/5:0:0:0
UDEV_LOG=3
ACTION=add
DEVPATH=/class/scsi_disk/5:0:0:0
SUBSYSTEM=scsi_disk
SEQNUM=2000
PHYSDEVPATH=/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1.1/1-1.1:1.0/host5/target5:0:0/5:0:0:0
PHYSDEVBUS=scsi
PHYSDEVDRIVER=sd
UDEVD_EVENT=1
IN_HOTPLUG=1

UDEV  [1181476144.202850] add@/class/scsi_generic/sg2
UDEV_LOG=3
ACTION=add
DEVPATH=/class/scsi_generic/sg2
SUBSYSTEM=scsi_generic
SEQNUM=2004
PHYSDEVPATH=/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1.1/1-1.1:1.0/host5/target5:0:0/5:0:0:0
PHYSDEVBUS=scsi
PHYSDEVDRIVER=sd
MAJOR=21
MINOR=2
UDEVD_EVENT=1
IN_HOTPLUG=1
DEVNAME=/dev/sg2

UDEV  [1181476144.231600] add@/block/sdc
UDEV_LOG=3
ACTION=add
DEVPATH=/block/sdc
SUBSYSTEM=block
SEQNUM=2001
MINOR=32
MAJOR=8
PHYSDEVPATH=/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1.1/1-1.1:1.0/host5/target5:0:0/5:0:0:0
PHYSDEVBUS=scsi
PHYSDEVDRIVER=sd
UDEVD_EVENT=1
IN_HOTPLUG=1
ID_VENDOR=USB_2.0_Flash_Disk
ID_MODEL=USB_Mass_Storage_Device
ID_REVISION=0001
ID_SERIAL=USB_2.0_Flash_Disk_USB_Mass_Storage_Device
ID_TYPE=floppy
ID_BUS=usb
ID_PATH=pci-0000:00:02.2-usb-0:1.1:1.0-scsi-0:0:0:0
DEVNAME=/dev/sdc
DEVLINKS=/dev/disk/by-id/usb-USB_2.0_Flash_Disk_USB_Mass_Storage_Device /dev/disk/by-path/pci-0000:00:02.2-usb-0:1.1:1.0-scsi-0:0:0:0

UDEV  [1181476144.289036] add@/class/scsi_device/5:0:0:0
UDEV_LOG=3
ACTION=add
DEVPATH=/class/scsi_device/5:0:0:0
SUBSYSTEM=scsi_device
SEQNUM=2003
PHYSDEVPATH=/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1.1/1-1.1:1.0/host5/target5:0:0/5:0:0:0
PHYSDEVBUS=scsi
PHYSDEVDRIVER=sd
UDEVD_EVENT=1
IN_HOTPLUG=1

UDEV  [1181476144.507508] add@/block/sdc/sdc1
UDEV_LOG=3
ACTION=add
DEVPATH=/block/sdc/sdc1
SUBSYSTEM=block
SEQNUM=2002
MINOR=33
MAJOR=8
PHYSDEVPATH=/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1.1/1-1.1:1.0/host5/target5:0:0/5:0:0:0
PHYSDEVBUS=scsi
PHYSDEVDRIVER=sd
UDEVD_EVENT=1
IN_HOTPLUG=1
ID_VENDOR=USB_2.0_Flash_Disk
ID_MODEL=USB_Mass_Storage_Device
ID_REVISION=0001
ID_SERIAL=USB_2.0_Flash_Disk_USB_Mass_Storage_Device
ID_TYPE=floppy
ID_BUS=usb
ID_PATH=pci-0000:00:02.2-usb-0:1.1:1.0-scsi-0:0:0:0
ID_FS_USAGE=filesystem
ID_FS_TYPE=vfat
ID_FS_VERSION=FAT32
ID_FS_UUID=24A9-6E38
ID_FS_LABEL=
ID_FS_LABEL_SAFE=
DEVNAME=/dev/sdc1
DEVLINKS=/dev/flash1 /dev/disk/by-id/usb-USB_2.0_Flash_Disk_USB_Mass_Storage_Device-part1 /dev/disk/by-path/pci-0000:00:02.2-usb-0:1.1:1.0-scsi-0:0:0:0-part1 /dev/disk/by-uuid/24A9-6E38

UEVENT[1181476144.888985] mount@/block/sdc/sdc1
ACTION=mount
DEVPATH=/block/sdc/sdc1
SUBSYSTEM=block
SEQNUM=2005
MINOR=33
MAJOR=8
PHYSDEVPATH=/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1.1/1-1.1:1.0/host5/target5:0:0/5:0:0:0
PHYSDEVBUS=scsi
PHYSDEVDRIVER=sd

UDEV  [1181476144.892552] mount@/block/sdc/sdc1
UDEV_LOG=3
ACTION=mount
DEVPATH=/block/sdc/sdc1
SUBSYSTEM=block
SEQNUM=2005
MINOR=33
MAJOR=8
PHYSDEVPATH=/devices/pci0000:00/0000:00:02.2/usb1/1-1/1-1.1/1-1.1:1.0/host5/target5:0:0/5:0:0:0
PHYSDEVBUS=scsi
PHYSDEVDRIVER=sd
UDEVD_EVENT=1
IN_HOTPLUG=1

                                                                             

_________________
Support bacteria – they’re the only culture some people have.”

– Steven Wright
Back to top
View user's profile Send private message
DirtyHairy
l33t
l33t


Joined: 03 Jul 2006
Posts: 608
Location: Würzburg, Deutschland

PostPosted: Sun Jun 10, 2007 12:40 pm    Post subject: Reply with quote

The dmesg output looks like a communication problem between stick and host; the stick seems to reconnect repeatedly and is not correctly scanned by usb_storage. I second KernelOfTruth; you should propably try up- or downgrading your kernel and seee if it fixes things (sometimes, it is also helpful to reconfigure the new kernel from scratch, although I doubt your problem is related to a faulty configuration). Oh, before you do that, can you check if other USB devices work (e.g. mouse) or if possibly the problem is something as trivial as a bad USB cable or possible a broken port (try sticking it into another port)?

Also, what's your lspci output (there are some buggy hardware implementations of USB that can cause problems, it's propably worth identifying your host controller and googling if there are any know issues with it).
Back to top
View user's profile Send private message
gsoe
Apprentice
Apprentice


Joined: 10 Dec 2006
Posts: 289
Location: Denmark

PostPosted: Sun Jun 10, 2007 1:42 pm    Post subject: Reply with quote

DirtyHairy wrote
Quote:
The dmesg output looks like a communication problem between stick and host;
That's the point; the last #dmesg shows that it is registered that something happens, but there is nothing like
Code:
usb-storage: device found at 5
usb-storage: waiting for device to settle before scanning
usb-storage: device scan complete
telling that the stick is recognized. Now, there are some possibilities left in the kernel config to try: In menuconfig go to Device drivers -> Block devices -> Low performance USB block driver and enable that. Look in help and notice the advice to enable USB_LIBUSUAL. Find that under Device drivers -> USB support -> The shared table of .... and enable that too. Then recompile, install kernel and give it another try.
Back to top
View user's profile Send private message
Mr_Shameless
Tux's lil' helper
Tux's lil' helper


Joined: 17 Sep 2006
Posts: 90
Location: sumwhere in Asia

PostPosted: Sun Jun 10, 2007 2:42 pm    Post subject: Reply with quote

to Decibels: #udevmonitor --env didnt print out anything when I plugged my USB in :roll:

to gsoe: under Puppy LiveCD I did get those 3 lines. I tried recompiling the kernel as you told me but it's just the same. I guess I will try another kernel. OMG, i've never installed anything [ Masked ]. Im scared, lol :D. Im going to read the handbook again to make sure how to do it. Thank God there's no dependency things with kernels :roll:

BTW, about the "many pty*", when looking at "Device Drivers" --> "Character Devices" --> "Legacy (BSD) PTY support", i guess it is this setting that create many pty*'s in my /dev. They say it's safe to say No, so I say no :D. I dont want anything i dont need.
Back to top
View user's profile Send private message
Mr_Shameless
Tux's lil' helper
Tux's lil' helper


Joined: 17 Sep 2006
Posts: 90
Location: sumwhere in Asia

PostPosted: Sun Jun 10, 2007 3:19 pm    Post subject: Reply with quote

I dont know how to downgrade softwares.

Currently the newest source on Gentoo is gentoo-sources-2.6.21-r2. I should choose that rather than gentoo-sources-2.6.21 right?

This is not gonna mess up my computer right? After compiling, I copy the image to /boot and add another entry to /etc/grub.conf without removing the old ones right?

So Im gonna do this:
Code:
#ACCEPT_KEYWORDS="~x86" emerge -v =gentoo-sources-2.6.21-r2


God bless me :D

PS: O I figured it out. Downgrading softwares is exactly the same :D
Back to top
View user's profile Send private message
gsoe
Apprentice
Apprentice


Joined: 10 Dec 2006
Posts: 289
Location: Denmark

PostPosted: Sun Jun 10, 2007 3:24 pm    Post subject: Reply with quote

Ok, yes I noticed. Lets just recap where we stand now:

First, we've eliminated a hardware error. Other OS work.

Next possibility is a kernel error or misconfiguration. This is where we stand right now. dmesg tells us that the kernel recognizes, when something is plugged in, but the kernel doesn't know your usbstick. For now you can forget about anything udev; that's a userspace thing. Only when the kernel level works, does udev take over to create your /dev/sd* devices. I expect that to work fine, when we get that far.

What I suggest now is that you boot the puppy linux or cd that works. Then, with the stick plugged in, post the output of lsmod. That should give us an idea about what kernel options we need, as most kernel options will be compiled as modules.

By the way, did the gentoo install cd pick up the stick. If it did, what kernel version is on it?
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware All times are GMT
Goto page 1, 2  Next
Page 1 of 2

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum