Re: mounting USB flash disk

<[email protected]>
Newsgroups gmane.linux.gentoo.ppc
Message-ID <39287.70.109.137.82.1134337694.squirrel@webmail.macintoshclub.com>
here is the dmesg output I finally got from booting.
Thanks so much,
nick
> Hello Nick,
> please start syslog-ng -d on a command line, so that you see debug
> messages. Best reagrds Joerg
>
> Am Sonntag 11 Dezember 2005 20:52 schrieb [email protected]:
>> Sorry, links ate the rest of my message.
>> syslog-ng dies with "bad config file"
>> hotplug usb:
>> Bad USB agent invocation, no action
>> and dmesg still only shows the keypresses (I got rid of Kernel
>> hacking-> debugging). I also added SCSI multi-LUN support, HD support,
>> and general device support. USB mass storage became module (to test in
>> MOL). and I also tried to fix my windowing problems with GNOME, KDE,
>> and XFCE (all installed, all failing) by making radeonfb a module.
>> sorry,
>> nick
>>
>> > and the root hubs (ID 0000:0000)
>> > Thanks
>> > nick
>> >
>> >> Am Sonntag 11 Dezember 2005 17:07 schrieb [email protected]:
>> >>> > I am on a powerbook G4 800mhz and it is
>> >>> >> plugged into the back of the computer (port 2). Does anyone
>> know
>> >>> how to solve this problem?
>> >>> >> thanks
>> >>> >> nick
>> >>> >
>> >>> > First, next time, please start a new thread instead of replying
>> to
>> >>> an existing one.
>> >>> >
>> >>> > That said, you'll have to provide more information.  Can you
>> give
>> >>> us
>> >>> the
>> >>> >  kernel messages from dmesg related to the USB stick?  Are you
>> sure
>> >>> you
>> >>> > have USB disk support and generic scsi disk support in your
>> kernel?
>> >>> >
>> >>> > -Joe
>> >>> > --
>> >>> > [email protected] mailing list
>> >>> Sorry about replying instead of starting again.
>> >>> Are there any just-X11 browsers besides links -g that I can use?
>> Whenever I press the back arrow it goes back and deletes the email
>> I was writing.
>> >>>
>> >>> Anyway, the only messages in dmesg (I do not know why) are
>> keypress
>> >> events!?!
>> >>> I used to be informative, but now all it has are keypresses...
>> >>>
>> >>> I have SCSI support, and USB mass storage (with all sub-options)
>> >> compiled-in.
>> >>> Do I need to add support for SCSI disks, CDROMS, generic devices,
>> etc in order for USB versions of those to work?
>> >>> Thanks,
>> >>> nick
>> >>>
>> >>>
>> >>> --
>> >>> [email protected] mailing list
>> >>>
>> >>>
>> >> Hello Nick,
>> >> You need modules for SCSI device support, SCSI disk support and
>> please enable  'Probe all LUNs on each SCSI device' as it helps
>> with Multi Card Readers. As long as the USB is hotpluggable, you
>> should install hotplug and udev  packages.
>> >> A good idea is to put the USB Disk in and to have look in dmesg
>> and/or /var/log/messages.
>> >> Normally I the disk should recognized by the kernel and produce at
>> least some  messages. (May be a lsusb show if there is something
>> recognized.) Best regards Joerg
>> >> --
>> >> [email protected] mailing list
>>
>>
>>
>> --
>> [email protected] mailing list
>>
>>
> --
> [email protected] mailing list
dmesg (text/plain, 15.1 KB)
egistered as minor 2
i2c_adapter i2c-2: registered as adapter #2
Found KeyWest i2c on "mac-io", 1 channel, stepping: 4 bits
tas driver [TAS3004 driver V 0.3])
using i2c address: 0x35 from device-tree
i2c-core: driver tas registered.
i2c_adapter i2c-2: client [tas Digital Equalizer] registered to adapter
registering 2-0035
ohci1394: fw-host0: IntEvent: 00030010
ohci1394: fw-host0: irq_handler: Bus reset requested
ohci1394: fw-host0: Cancel request received
ohci1394: fw-host0: Got RQPkt interrupt status=0x00008409
ohci1394: fw-host0: SelfID interrupt received (phyid 0, root)
ohci1394: fw-host0: SelfID packet 0x807f8842 received
ieee1394: Including SelfID 0x807f8842
ohci1394: fw-host0: SelfID for this node is 0x807f8842
ohci1394: fw-host0: SelfID complete
ohci1394: fw-host0: PhyReqFilter=ffffffffffffffff
ieee1394: selfid_complete called with successful SelfID stage ... irm_id: 0xFFC0 node_id: 0xFFC0
ieee1394: NodeMgr: Processing host reset for knodemgrd_0
ohci1394: fw-host0: Single packet rcv'd
ohci1394: fw-host0: Got phy packet ctx=0 ... discarded
Audio jack unplugged, enabling speakers.
chan: 0, addr: 0x35, transfer len: 1, read: 0
using interrupt mode...
transfer done, result: 0
chan: 0, addr: 0x35, transfer len: 1, read: 0
using interrupt mode...
transfer done, result: 0
chan: 0, addr: 0x35, transfer len: 15, read: 0
using interrupt mode...
transfer done, result: 0
chan: 0, addr: 0x35, transfer len: 15, read: 0
using interrupt mode...
transfer done, result: 0
chan: 0, addr: 0x35, transfer len: 15, read: 0
using interrupt mode...
transfer done, result: 0
chan: 0, addr: 0x35, transfer len: 15, read: 0
using interrupt mode...
transfer done, result: 0
chan: 0, addr: 0x35, transfer len: 15, read: 0
using interrupt mode...
transfer done, result: 0
chan: 0, addr: 0x35, transfer len: 15, read: 0
using interrupt mode...
transfer done, result: 0
chan: 0, addr: 0x35, transfer len: 15, read: 0
using interrupt mode...
transfer done, result: 0
chan: 0, addr: 0x35, transfer len: 15, read: 0
using interrupt mode...
transfer done, result: 0
chan: 0, addr: 0x35, transfer len: 15, read: 0
using interrupt mode...
transfer done, result: 0
chan: 0, addr: 0x35, transfer len: 15, read: 0
using interrupt mode...
transfer done, result: 0
chan: 0, addr: 0x35, transfer len: 15, read: 0
using interrupt mode...
transfer done, result: 0
chan: 0, addr: 0x35, transfer len: 15, read: 0
using interrupt mode...
transfer done, result: 0
chan: 0, addr: 0x35, transfer len: 15, read: 0
using interrupt mode...
transfer done, result: 0
chan: 0, addr: 0x35, transfer len: 15, read: 0
using interrupt mode...
transfer done, result: 0
chan: 0, addr: 0x35, transfer len: 6, read: 0
using interrupt mode...
transfer done, result: 0
chan: 0, addr: 0x35, transfer len: 1, read: 0
using interrupt mode...
transfer done, result: 0
chan: 0, addr: 0x35, transfer len: 1, read: 0
using interrupt mode...
transfer done, result: 0
chan: 0, addr: 0x35, transfer len: 6, read: 0
using interrupt mode...
transfer done, result: 0
chan: 0, addr: 0x35, transfer len: 9, read: 0
using interrupt mode...
transfer done, result: 0
chan: 0, addr: 0x35, transfer len: 9, read: 0
using interrupt mode...
transfer done, result: 0
chan: 0, addr: 0x35, transfer len: 9, read: 0
using interrupt mode...
transfer done, result: 0
chan: 0, addr: 0x35, transfer len: 9, read: 0
using interrupt mode...
transfer done, result: 0
chan: 0, addr: 0x35, transfer len: 9, read: 0
using interrupt mode...
transfer done, result: 0
chan: 0, addr: 0x35, transfer len: 9, read: 0
using interrupt mode...
transfer done, result: 0
chan: 0, addr: 0x35, transfer len: 1, read: 0
using interrupt mode...
transfer done, result: 0
chan: 0, addr: 0x35, transfer len: 1, read: 0
using interrupt mode...
transfer done, result: 0
chan: 0, addr: 0x35, transfer len: 1, read: 0
using interrupt mode...
evbug.c: Connected device: "dmasound beeper", macio/input0
AE-Init snapper mixer
PowerMac Snapper  DMA sound driver rev 016 installed
Core driver edition 01.06 : PowerMac Built-in Sound driver edition 00.07
Write will use    4 fragments of   32768 bytes as default
Read  will use    4 fragments of   32768 bytes as default
Advanced Linux Sound Architecture Driver Version 1.0.9rc2  (Thu Mar 24 10:33:39 2005 UTC).
transfer done, result: 0
chan: 0, addr: 0x35, transfer len: 6, read: 0
using interrupt mode...
pmac: can't request resource 0!
ALSA device list:
  No soundcards found.
NET: Registered protocol family 2
transfer done, result: 0
chan: 0, addr: 0x35, transfer len: 1, read: 0
using interrupt mode...
transfer done, result: 0
chan: 0, addr: 0x35, transfer len: 15, read: 0
using interrupt mode...
transfer done, result: 0
chan: 0, addr: 0x35, transfer len: 15, read: 0
using interrupt mode...
transfer done, result: 0
chan: 0, addr: 0x35, transfer len: 15, read: 0
using interrupt mode...
transfer done, result: 0
chan: 0, addr: 0x35, transfer len: 15, read: 0
using interrupt mode...
transfer done, result: 0
chan: 0, addr: 0x35, transfer len: 15, read: 0
using interrupt mode...
IP: routing cache hash table of 4096 buckets, 32Kbytes
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
IPv4 over IPv4 tunneling driver
transfer done, result: 0
chan: 0, addr: 0x35, transfer len: 15, read: 0
using interrupt mode...
ieee1394: send packet local: ffc00140 ffc0ffff f0000400
ieee1394: received packet: ffc00140 ffc0ffff f0000400
ieee1394: send packet local: ffc00160 ffc00000 00000000 04041ee6
ieee1394: received packet: ffc00160 ffc00000 00000000 04041ee6
IPVS: Registered protocols ()
IPVS: Connection hash table configured (size=4096, memory=32Kbytes)
ieee1394: send packet local: ffc00540 ffc0ffff f0000404
ieee1394: received packet: ffc00540 ffc0ffff f0000404
ieee1394: send packet local: ffc00560 ffc00000 00000000 31333934
ieee1394: received packet: ffc00560 ffc00000 00000000 31333934
ieee1394: send packet local: ffc00940 ffc0ffff f0000408
ieee1394: received packet: ffc00940 ffc0ffff f0000408
ieee1394: send packet local: ffc00960 ffc00000 00000000 e064a232
ieee1394: received packet: ffc00960 ffc00000 00000000 e064a232
ieee1394: send packet local: ffc00d40 ffc0ffff f000040c
ieee1394: received packet: ffc00d40 ffc0ffff f000040c
ieee1394: send packet local: ffc00d60 ffc00000 00000000 000393ff
ieee1394: received packet: ffc00d60 ffc00000 00000000 000393ff
ieee1394: send packet local: ffc01140 ffc0ffff f0000410
ieee1394: received packet: ffc01140 ffc0ffff f0000410
ieee1394: send packet local: ffc01160 ffc00000 00000000 fe8024f2
ieee1394: received packet: ffc01160 ffc00000 00000000 fe8024f2
ieee1394: send packet local: ffc01550 ffc0ffff f0000400 04000000
ieee1394: received packet: ffc01550 ffc0ffff f0000400 04000000
ieee1394: send packet local: ffc01570 ffc00000 00000000 04000000
ieee1394: received packet: ffc01570 ffc00000 00000000 04000000
ieee1394: NodeMgr: raw=0xe064a232 irmc=1 cmc=1 isc=1 bmc=0 pmc=0 cyc_clk_acc=100 max_rec=2048 max_rom=1024 gen=3 lspd=2
ieee1394: Host added: ID:BUS[0-00:1023]  GUID[000393fffe8024f2]
ieee1394: send packet 100: ffff0100 ffc0ffff f0000234 c000001f
ohci1394: fw-host0: Inserting packet for node 0-63:1023, tlabel=0, tcode=0x0, speed=0
ohci1394: fw-host0: Starting transmit DMA ctx=0
ohci1394: fw-host0: IntEvent: 00000001
ohci1394: fw-host0: Got reqTxComplete interrupt status=0x00008011
ohci1394: fw-host0: Packet sent to node 63 tcode=0x0 tLabel=0 ack=0x11 spd=0 data=0x1F0000C0 ctx=0
transfer done, result: 0
chan: 0, addr: 0x35, transfer len: 15, read: 0
using interrupt mode...
transfer done, result: 0
chan: 0, addr: 0x35, transfer len: 15, read: 0
using interrupt mode...
transfer done, result: 0
chan: 0, addr: 0x35, transfer len: 15, read: 0
using interrupt mode...
transfer done, result: 0
chan: 0, addr: 0x35, transfer len: 15, read: 0
using interrupt mode...
transfer done, result: 0
chan: 0, addr: 0x35, transfer len: 15, read: 0
using interrupt mode...
transfer done, result: 0
chan: 0, addr: 0x35, transfer len: 15, read: 0
using interrupt mode...
transfer done, result: 0
chan: 0, addr: 0x35, transfer len: 15, read: 0
using interrupt mode...
IPVS: ipvs loaded.
NET: Registered protocol family 17
transfer done, result: 0
chan: 0, addr: 0x35, transfer len: 15, read: 0
using interrupt mode...
transfer done, result: 0
chan: 0, addr: 0x35, transfer len: 1, read: 0
using interrupt mode...
transfer done, result: 0
Bridge firewalling registered
802.1Q VLAN Support v1.8 Ben Greear <[email protected]>
All bugs added by David S. Miller <[email protected]>
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: hda11: orphan cleanup on readonly fs
ext3_orphan_cleanup: deleting unreferenced inode 18354
EXT3-fs: hda11: 1 orphan inode deleted
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 324k init 4k chrp 8k prep
evbug.c: Event. Dev: adb3:3.01/input, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 0, Value: 8
evbug.c: Event. Dev: adb3:3.01/input, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 0, Value: 15
evbug.c: Event. Dev: adb3:3.01/input, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 0, Value: 17
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 1, Value: 1
evbug.c: Event. Dev: adb3:3.01/input, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 0, Value: 17
evbug.c: Event. Dev: adb3:3.01/input, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 0, Value: 22
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 1, Value: -2
evbug.c: Event. Dev: adb3:3.01/input, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 0, Value: 25
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 1, Value: -6
evbug.c: Event. Dev: adb3:3.01/input, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 0, Value: 28
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 1, Value: -11
evbug.c: Event. Dev: adb3:3.01/input, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 0, Value: 31
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 1, Value: -15
evbug.c: Event. Dev: adb3:3.01/input, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 0, Value: 28
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 1, Value: -20
evbug.c: Event. Dev: adb3:3.01/input, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 0, Value: 4
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 1, Value: -4
evbug.c: Event. Dev: adb3:3.01/input, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 0, Value: -13
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 1, Value: -5
evbug.c: Event. Dev: adb3:3.01/input, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 0, Value: -19
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 1, Value: -8
evbug.c: Event. Dev: adb3:3.01/input, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 0, Value: -30
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 1, Value: -7
evbug.c: Event. Dev: adb3:3.01/input, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 0, Value: -38
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 1, Value: -7
evbug.c: Event. Dev: adb3:3.01/input, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 0, Value: -48
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 1, Value: -4
evbug.c: Event. Dev: adb3:3.01/input, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 0, Value: -56
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 1, Value: -3
evbug.c: Event. Dev: adb3:3.01/input, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 0, Value: -61
evbug.c: Event. Dev: adb3:3.01/input, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 0, Value: 61
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 1, Value: 2
evbug.c: Event. Dev: adb3:3.01/input, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 0, Value: 58
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 1, Value: 4
evbug.c: Event. Dev: adb3:3.01/input, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 0, Value: 59
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 1, Value: 9
evbug.c: Event. Dev: adb3:3.01/input, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 0, Value: 63
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 1, Value: 12
evbug.c: Event. Dev: adb3:3.01/input, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 0, Value: -60
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 1, Value: 14
evbug.c: Event. Dev: adb3:3.01/input, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 0, Value: -56
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 1, Value: 18
evbug.c: Event. Dev: adb3:3.01/input, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 0, Value: -52
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 1, Value: 19
evbug.c: Event. Dev: adb3:3.01/input, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 0, Value: -36
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 1, Value: 23
evbug.c: Event. Dev: adb3:3.01/input, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 0, Value: -3
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 1, Value: 4
evbug.c: Event. Dev: adb3:3.01/input, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 0, Value: 17
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 1, Value: 6
evbug.c: Event. Dev: adb3:3.01/input, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 0, Value: 26
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 1, Value: 7
evbug.c: Event. Dev: adb3:3.01/input, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 0, Value: 33
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 1, Value: 10
evbug.c: Event. Dev: adb3:3.01/input, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 0, Value: 36
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 1, Value: 12
evbug.c: Event. Dev: adb3:3.01/input, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 0, Value: 37
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 1, Value: 14
evbug.c: Event. Dev: adb3:3.01/input, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 0, Value: 8
evbug.c: Event. Dev: adb3:3.01/input, Type: 2, Code: 1, Value: 2
evbug.c: Event. Dev: adb3:3.01/input, Type: 0, Code: 0, Value: 0
Adding 524280k swap on /dev/hda10.  Priority:-1 extents:1
EXT3 FS on hda11, internal journal
HFS+-fs warning: Filesystem was not cleanly unmounted, running fsck.hfsplus is recommended.  mounting read-only.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.