Western Digital and OpenSuse

[whitewater3505]

Alright so I have made the switch from Ubuntu to OpenSuse, not really sure why. I guess I wanted some change. Now I have a tid bit of a problem. I have a Western Digital Passport, which is recognized by XP (friends machine I swear :) ) , and was recognized by Ubuntu, but is not being recognized by Suse.

What I have done

rdawson@3(NXDOMAIN):~>dmesg | grep "SCSI"
SCSI subsystem initialized
sd 0:0:0:0: [sda] Attached SCSI disk


Thats my laptop's drive. So then I tried


rdawson@3(NXDOMAIN):~> sudo fdisk -l /dev/sdb


I tried that for /dev/sd[a-d]
and
/dev/hd[a-d]

Only one found was sda which is again my laptops drive.

More Info:
kernel -> 2.6.22.5-31
OS -> OpenSuse
I have ntfs-3g installed
The external hard drive is formatted in NTFS (can't change, I do a lot of development in Windows at school :( )

If you need anything else from me let me know. I have tried several forums, including this one, and they all go off into a tangent about something not relevant.

Tank You!

[bwkaz]

Assuming that's USB, unplug it, then plug it back in. Then wait maybe ten seconds, and dmesg | tail -n 30 (or so). Post the results (or just look through them).

Apparently you aren't getting any messages with SCSI in them, but when that happens, it's a good idea to look at everything that gets logged, in case the issue is obvious from one of the other messages. :)

[whitewater3505]

lol i get a bunch of wireless stuff... Here is the results good luck reading it


rdawson@3(NXDOMAIN):~> dmesg | tail -n 30 > output.txt


here is output.txt

http://cs.txstate.edu/~cd1214/output.txt

I grep'd through it and found nothing in significance.

UPDATE:

I tried 2 USB drives:
2GB fat32 --> the power led did not turn on
1GB ext3 --> the power led also did not turn on

But the Western Digital Passport power led is on

Also, on Suse first boot I got an ACPI error, don't remember the exact one. So they are probably related.


dmesg | grep "acpi"
If you got timer trouble try acpi_use_timer_override
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])


hope this helps!

[whitewater3505]

Ok problem solved.

I need to boot with noapic...

On Ubuntu if i didnt boot with noapic then it would cause a kernel panic, but Suse just kinda let me boot without it...

So Problem Solved!!

[bwkaz]

lol i get a bunch of wireless stuff... Here is the results good luck reading it OK then: scratch that. What you need to do is disable the wireless card, then plug the USB disk in, then wait about ten seconds, and (finally) redo the dmesg. Then re-enable the card.

(Alternately, remove the rules from your firewall that LOG packets, since I bet you never look at those logs anyway. ;))

(Or, reading on, never mind since it's fixed. Still, for future reference I'll leave that in.)

On Ubuntu if i didnt boot with noapic then it would cause a kernel panic, but Suse just kinda let me boot without it... The kernel won't panic every time it's unable to work with certain hardware, so that's probably why SuSE didn't panic.

The noapic will be required until your motherboard's interrupt controller either (a) gets better support in the kernel, or (b) stops being buggy. Which one of those is possible depends on what the problem is: if there are bugs in the interrupt controller, then I'm guessing noapic will always be required (unless a BIOS update is able to fix the bugs). If the kernel just hasn't been patched to work with that controller yet, then noapic may eventually become unnecessary.