Hi,

I have an external HDD. With the default (GENERIC) kernel it was
getting detected whenever I'd plug the thing to one of the USB ports.

May 23 16:59:54 take2 /netbsd: umass0: Myson Century, Inc. USB Mass
Storage Device, rev 2.00/b0.07, addr 2
May 23 16:59:54 take2 /netbsd: umass0: using ATAPI over Bulk-Only
May 23 16:59:54 take2 /netbsd: atapibus1 at umass0: 2 targets
May 23 16:59:54 take2 /netbsd: sd0 at atapibus1 drive 0: <TOSHIBA,
MK1032GAX, AB21> disk fixed
May 23 16:59:54 take2 /netbsd: sd0: fabricating a geometry
May 23 16:59:54 take2 /netbsd: sd0: 95396 MB, 95396 cyl, 64 head, 32
sec, 512 bytes/sect x 195371568 sectors
May 23 16:59:55 take2 /netbsd: set{u,g}id pid 28890 (gnome-pty-helper)
was invoked by uid 1000 ppid 3583 (gnome-terminal) with fd 2 closed
May 23 17:00:16 take2 /netbsd: sd0: fabricating a geometry
May 23 17:00:41 take2 /netbsd: sd0: fabricating a geometry
May 23 17:01:19 take2 /netbsd: sd0: fabricating a geometry

Yesterday I compiled a kernel of my own. I took care to make sure
nothing that popped up in "dmesg" was commented out by me, but I
dunno, I guess I goofed up somewhere -- the HDD doesn't get detected
any more! :( I plug it into the USB port, I get no messages.

I went back to the kernel config file. I found lines like the ones below --

# USB Mass Storage
umass*  at uhub? port ? configuration ? interface ?
scsibus* at umass?
wd*     at umass?

-- but I didnt find anything that said "atapibus* at umass?" or
something. (The reason I checked for that is coz of the line
"atapibus1 at umass0: 2 targets" in my GENERIC kernel dmesg output).
So I even added a line like that and compiled -- but nopes, the kernel
doesn't recognize the HDD still.

Ofcourse, I know I can use the HDD with the GENERIC kernel. But I am
curious -- any pointers on what I might have commented out by mistake
to stop the HDD from getting detected? I suppose more ppl have faced
similar problems before ...? Looking forward to any suggestions ...

Thanks,
Rakhesh