Hi, I'm trying to get my twinMOS mobile disk IV 512MB usb stick to work with fedora 2. When I insert the stick the following window pops up: Window heading: KWrited - listening on Device /dev/pts/0
And it has the following message: Message from syslogd@dsl-69-134 at Mon Sep 27 11:48:08 2004 ... dsl-69-134 kernel: Disabling IRQ #9
Then, my KEYBOARD stops working, and i need to reboot my computer without the stick to get it back....
I'm running kernel 2.6.8-1.521 How can I get it to work, and what is the correct way to mount & unmount it without loosing any work?
Thanx Tor Harald Thorland
Tor Harald Thorland wrote:
I'm trying to get my twinMOS mobile disk IV 512MB usb stick to work with fedora 2. When I insert the stick the following window pops up: Window heading: KWrited - listening on Device /dev/pts/0
And it has the following message: Message from syslogd@dsl-69-134 at Mon Sep 27 11:48:08 2004 ... dsl-69-134 kernel: Disabling IRQ #9
Then, my KEYBOARD stops working, and i need to reboot my computer without the stick to get it back....
Let me guess, you've got a USB keyboard. Something about the disk is causing the kernel to disable the USB interrupt, IRQ 9. So it won't listen to any events from your keyboard.
Do you have a USB mouse, too? You should be able to use the GUI to reset the computer, but without a working mouse, that's not possible, either.
Is there any chance you could borrow a PS/2 keyboard to watch what's happening?
Is there anything else interesting in /var/log/messages ?
One piece of advice: please leave the system for at least a minute before resetting it. That way, data generated when the USB problems occurred should have reached disk.
Thanks,
James.
man, 27.09.2004 kl. 14.44 skrev James Wilkinson:
Tor Harald Thorland wrote:
I'm trying to get my twinMOS mobile disk IV 512MB usb stick to work with fedora 2. When I insert the stick the following window pops up: Window heading: KWrited - listening on Device /dev/pts/0
And it has the following message: Message from syslogd@dsl-69-134 at Mon Sep 27 11:48:08 2004 ... dsl-69-134 kernel: Disabling IRQ #9
Then, my KEYBOARD stops working, and i need to reboot my computer without the stick to get it back....
Let me guess, you've got a USB keyboard. Something about the disk is causing the kernel to disable the USB interrupt, IRQ 9. So it won't listen to any events from your keyboard.
Do you have a USB mouse, too? You should be able to use the GUI to reset the computer, but without a working mouse, that's not possible, either.
Is there any chance you could borrow a PS/2 keyboard to watch what's happening?
Is there anything else interesting in /var/log/messages ?
It is on a laptop. Only the mouse is USB, and the mouse continued working. I've tryed it a little bit more, and the /dev/pts/0 has changed to 1 and now my keyboard & mouse is working, but the messages has lots of text:
Sep 27 15:55:41 dsl-69-134 kernel: irq 9: nobody cared! (screaming interrupt?) Sep 27 15:55:41 dsl-69-134 kernel: irq 9: Please try booting with acpi=off and report a bug Sep 27 15:55:41 dsl-69-134 kernel: Stack pointer is garbage, not printing trace Sep 27 15:55:41 dsl-69-134 kernel: handlers: Sep 27 15:55:41 dsl-69-134 kernel: [<021e316b>] (acpi_irq+0x0/0x14) Sep 27 15:55:41 dsl-69-134 kernel: Disabling IRQ #9 Sep 27 15:55:41 dsl-69-134 kernel: ohci_hcd 0000:00:02.0: wakeup Sep 27 15:55:41 dsl-69-134 kernel: usb 1-1: new full speed USB device using address 2 Sep 27 15:55:47 dsl-69-134 kernel: usb 1-1: device not accepting address 2, error -110 Sep 27 15:55:47 dsl-69-134 kernel: usb 1-1: new full speed USB device using address 3 Sep 27 15:55:51 dsl-69-134 kernel: usb 1-1: device not accepting address 3, error -110 Sep 27 15:55:52 dsl-69-134 kernel: ohci_hcd 0000:00:02.0: IRQ INTR_SF lossage
Thanx Tor Harald Thorland
Tor Harald Thorland wrote:
It is on a laptop. Only the mouse is USB, and the mouse continued working. I've tryed it a little bit more, and the /dev/pts/0 has changed to 1 and now my keyboard & mouse is working, but the messages has lots of text:
Sep 27 15:55:41 dsl-69-134 kernel: irq 9: nobody cared! (screaming interrupt?)
Can you post the contents of /proc/interrupts?
Sep 27 15:55:41 dsl-69-134 kernel: irq 9: Please try booting with acpi=off and report a bug
Can you try booting with acpi=off (at the end of the kernel comand line: edit it in grub or in /boot/grub/grub.conf)? I know that it's not really a proper solution on a laptop, but it might help you find one.
I don't really know enough about the ins and outs of acpi to tell, but if acpi=off cures the problem, then acpi=noirq might be worth trying.
Sep 27 15:55:41 dsl-69-134 kernel: Stack pointer is garbage, not printing trace Sep 27 15:55:41 dsl-69-134 kernel: handlers: Sep 27 15:55:41 dsl-69-134 kernel: [<021e316b>] (acpi_irq+0x0/0x14) Sep 27 15:55:41 dsl-69-134 kernel: Disabling IRQ #9 Sep 27 15:55:41 dsl-69-134 kernel: ohci_hcd 0000:00:02.0: wakeup Sep 27 15:55:41 dsl-69-134 kernel: usb 1-1: new full speed USB device using address 2 Sep 27 15:55:47 dsl-69-134 kernel: usb 1-1: device not accepting address 2, error -110 Sep 27 15:55:47 dsl-69-134 kernel: usb 1-1: new full speed USB device using address 3 Sep 27 15:55:51 dsl-69-134 kernel: usb 1-1: device not accepting address 3, error -110 Sep 27 15:55:52 dsl-69-134 kernel: ohci_hcd 0000:00:02.0: IRQ INTR_SF lossage
Ultimately, this should go to the Linux Kernel Mailing List and/or Fedora bugzilla and/or the kernel bugzilla, but I'd recommend getting all the debugging info you can first.
Hope this helps,
James.
man, 27.09.2004 kl. 18.30 skrev James Wilkinson:
Tor Harald Thorland wrote:
It is on a laptop. Only the mouse is USB, and the mouse continued working. I've tryed it a little bit more, and the /dev/pts/0 has changed to 1 and now my keyboard & mouse is working, but the messages has lots of text:
Sep 27 15:55:41 dsl-69-134 kernel: irq 9: nobody cared! (screaming interrupt?)
Can you post the contents of /proc/interrupts?
CPU0 0: 416416 XT-PIC timer 1: 290 XT-PIC i8042 2: 0 XT-PIC cascade 8: 1 XT-PIC rtc 10: 10911 XT-PIC ohci_hcd 11: 2960 XT-PIC ohci_hcd, eth0, ALI 5451 14: 16827 XT-PIC ide0 15: 930 XT-PIC ide1 NMI: 0 ERR: 0
Sep 27 15:55:41 dsl-69-134 kernel: irq 9: Please try booting with acpi=off and report a bug
Can you try booting with acpi=off (at the end of the kernel comand line: edit it in grub or in /boot/grub/grub.conf)? I know that it's not really a proper solution on a laptop, but it might help you find one.
I don't really know enough about the ins and outs of acpi to tell, but if acpi=off cures the problem, then acpi=noirq might be worth trying.
Sep 27 15:55:41 dsl-69-134 kernel: Stack pointer is garbage, not printing trace Sep 27 15:55:41 dsl-69-134 kernel: handlers: Sep 27 15:55:41 dsl-69-134 kernel: [<021e316b>] (acpi_irq+0x0/0x14) Sep 27 15:55:41 dsl-69-134 kernel: Disabling IRQ #9 Sep 27 15:55:41 dsl-69-134 kernel: ohci_hcd 0000:00:02.0: wakeup Sep 27 15:55:41 dsl-69-134 kernel: usb 1-1: new full speed USB device using address 2 Sep 27 15:55:47 dsl-69-134 kernel: usb 1-1: device not accepting address 2, error -110 Sep 27 15:55:47 dsl-69-134 kernel: usb 1-1: new full speed USB device using address 3 Sep 27 15:55:51 dsl-69-134 kernel: usb 1-1: device not accepting address 3, error -110 Sep 27 15:55:52 dsl-69-134 kernel: ohci_hcd 0000:00:02.0: IRQ INTR_SF lossage
Ultimately, this should go to the Linux Kernel Mailing List and/or Fedora bugzilla and/or the kernel bugzilla, but I'd recommend getting all the debugging info you can first.
The messages file now contains the following:
Sep 27 20:11:00 dsl-69-134 kernel: ohci_hcd 0000:00:02.0: wakeup Sep 27 20:11:00 dsl-69-134 kernel: usb 1-1: new full speed USB device using address 2 Sep 27 20:11:00 dsl-69-134 kernel: Initializing USB Mass Storage driver... Sep 27 20:11:00 dsl-69-134 kernel: scsi0 : SCSI emulation for USB Mass Storage devices Sep 27 20:11:00 dsl-69-134 kernel: Vendor: USB 2.0 Model: Mobile Disk N4M Rev: 1.00 Sep 27 20:11:00 dsl-69-134 kernel: Type: Direct-Access ANSI SCSI revision: 02 Sep 27 20:11:00 dsl-69-134 kernel: Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 0 Sep 27 20:11:00 dsl-69-134 kernel: usbcore: registered new driver usb-storage Sep 27 20:11:00 dsl-69-134 kernel: USB Mass Storage support registered. Sep 27 20:11:00 dsl-69-134 kernel: SCSI device sda: 999424 512-byte hdwr sectors (512 MB) Sep 27 20:11:01 dsl-69-134 kernel: sda: Write Protect is off Sep 27 20:11:01 dsl-69-134 kernel: sda: assuming drive cache: write through Sep 27 20:11:01 dsl-69-134 kernel: sda: sda1 Sep 27 20:11:01 dsl-69-134 kernel: Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0 Sep 27 20:11:01 dsl-69-134 kernel: updfstab: Using deprecated /dev/sg mechanism instead of SG_IO on the actual device Sep 27 20:11:01 dsl-69-134 scsi.agent[2425]: disk at /devices/pci0000:00/0000:00:02.0/usb1/1-1/1-1:1.0/host0/0:0:0:0
The system also is not restarting correctly when i have inserted the stick. When i press the restart icon from the login screen, the screen goes black and the cursor is blinking.
I then have to press ctrl alt del. to restart it, and during this restart the screen continues to be black.
according to twinmos the stick is supposed to work with kernel 2.4 and above... thats why i bought it.
What does the acpi do?
And what is the correct way to mount this stick?
Thanx Tor Harald Thorland
Tor Harald Thorland was having trouble with a USB disk.
I suggested:
Can you try booting with acpi=off (at the end of the kernel comand line: edit it in grub or in /boot/grub/grub.conf)? I know that it's not really a proper solution on a laptop, but it might help you find one.
I don't really know enough about the ins and outs of acpi to tell, but if acpi=off cures the problem, then acpi=noirq might be worth trying.
He replied:
The messages file now contains the following:
Sep 27 20:11:00 dsl-69-134 kernel: ohci_hcd 0000:00:02.0: wakeup Sep 27 20:11:00 dsl-69-134 kernel: usb 1-1: new full speed USB device using address 2 Sep 27 20:11:00 dsl-69-134 kernel: Initializing USB Mass Storage driver... Sep 27 20:11:00 dsl-69-134 kernel: scsi0 : SCSI emulation for USB Mass Storage devices Sep 27 20:11:00 dsl-69-134 kernel: Vendor: USB 2.0 Model: Mobile Disk N4M Rev: 1.00 Sep 27 20:11:00 dsl-69-134 kernel: Type: Direct-Access ANSI SCSI revision: 02 Sep 27 20:11:00 dsl-69-134 kernel: Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 0 Sep 27 20:11:00 dsl-69-134 kernel: usbcore: registered new driver usb-storage Sep 27 20:11:00 dsl-69-134 kernel: USB Mass Storage support registered. Sep 27 20:11:00 dsl-69-134 kernel: SCSI device sda: 999424 512-byte hdwr sectors (512 MB) Sep 27 20:11:01 dsl-69-134 kernel: sda: Write Protect is off Sep 27 20:11:01 dsl-69-134 kernel: sda: assuming drive cache: write through Sep 27 20:11:01 dsl-69-134 kernel: sda: sda1 Sep 27 20:11:01 dsl-69-134 kernel: Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0 Sep 27 20:11:01 dsl-69-134 kernel: updfstab: Using deprecated /dev/sg mechanism instead of SG_IO on the actual device Sep 27 20:11:01 dsl-69-134 scsi.agent[2425]: disk at /devices/pci0000:00/0000:00:02.0/usb1/1-1/1-1:1.0/host0/0:0:0:0
Sounds like things are getting further, then. What happens if you try mounting /dev/sda1 somewhere?
mount /dev/sda1 /misc
What does the acpi do?
Too much, and not well enough. The Advanced Configuration and Power Interface is the subject of many a rant by kernel developers. It's supposed to be a standard way for hardware to tell software the details of what's there, how to configure it, and how to put it into power- saving mode. In practice, this means that the kernel has to rely on data from the BIOS, whose writers often consider it debugged if Windows boots.
It also affects the way that IRQs are detected and handled.
James.
tor, 30.09.2004 kl. 14.30 skrev James Wilkinson:
Tor Harald Thorland was having trouble with a USB disk.
Suggestion:
Can you try booting with acpi=off (at the end of the kernel comand line: edit it in grub or in /boot/grub/grub.conf)? I know that it's not really a proper solution on a laptop, but it might help you find one.
I don't really know enough about the ins and outs of acpi to tell, but if acpi=off cures the problem, then acpi=noirq might be worth trying.
I replied:
The messages file now contains the following:
Sep 27 20:11:00 dsl-69-134 kernel: ohci_hcd 0000:00:02.0: wakeup Sep 27 20:11:00 dsl-69-134 kernel: usb 1-1: new full speed USB device using address 2 Sep 27 20:11:00 dsl-69-134 kernel: Initializing USB Mass Storage driver... Sep 27 20:11:00 dsl-69-134 kernel: scsi0 : SCSI emulation for USB Mass Storage devices Sep 27 20:11:00 dsl-69-134 kernel: Vendor: USB 2.0 Model: Mobile Disk N4M Rev: 1.00 Sep 27 20:11:00 dsl-69-134 kernel: Type: Direct-Access ANSI SCSI revision: 02 Sep 27 20:11:00 dsl-69-134 kernel: Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 0 Sep 27 20:11:00 dsl-69-134 kernel: usbcore: registered new driver usb-storage Sep 27 20:11:00 dsl-69-134 kernel: USB Mass Storage support registered. Sep 27 20:11:00 dsl-69-134 kernel: SCSI device sda: 999424 512-byte hdwr sectors (512 MB) Sep 27 20:11:01 dsl-69-134 kernel: sda: Write Protect is off Sep 27 20:11:01 dsl-69-134 kernel: sda: assuming drive cache: write through Sep 27 20:11:01 dsl-69-134 kernel: sda: sda1 Sep 27 20:11:01 dsl-69-134 kernel: Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0 Sep 27 20:11:01 dsl-69-134 kernel: updfstab: Using deprecated /dev/sg mechanism instead of SG_IO on the actual device Sep 27 20:11:01 dsl-69-134 scsi.agent[2425]: disk at /devices/pci0000:00/0000:00:02.0/usb1/1-1/1-1:1.0/host0/0:0:0:0
Sounds like things are getting further, then. What happens if you try mounting /dev/sda1 somewhere?
Yes, Its getting further... I can now mount /dev/sda1 to /mnt/flash (or wathever) when I have the ACPI=off.
I tryed to make the ACPI=noirq. Then the I rebooted, and the computer hang, right after the graphical boot said: setting hostname (or something.. I have norwegian text on it) Also the my usb mouse dident work during this startup (it normaly does work).
I then had to edit the kernel parameter from grub to make it boot.
I also has a Apacer handy steno 1.1 256mb disk, i was also able to make this work with the ACPI=off. The only thing here is that the Apacer stick is /dev/sda, even if only this stick is in the usb port.
Why does 1 of them use /dev/sda, when the other comes in as /dev/sda1 ?
I've added both of them to /etc/fstab as: /dev/sda /mnt/flash vfat noauto,user,rw 0 0 /dev/sda1 /mnt/flash2 vfat noauto,user,rw 0 0
Is this the correct way to do it? and if I set it to auto instead of noauto, will it then automaticly mount when I insert it?
Also, how can I disable the graphical boot to see wats going on when the hangs during the boot?
James was also earlyer talking about maby making a bugzilla entry about this.. Is this problem something to add to bugzilla, and if so.. how?
Many thanx for all the good help James!!
THT
Tor Harald Thorland was having trouble with a USB disk.
I suggested:
... booting with acpi=off (at the end of the kernel comand line: edit it in grub or in /boot/grub/grub.conf)? I know that it's not really a proper solution on a laptop, but it might help you find one.
Tor replied:
Yes, Its getting further... I can now mount /dev/sda1 to /mnt/flash (or wathever) when I have the ACPI=off.
Hooray. You have nailed down the problem to the ACPI subsystem.
I tryed to make the ACPI=noirq. Then the I rebooted, and the computer hang, right after the graphical boot said: setting hostname (or something.. I have norwegian text on it) Also the my usb mouse dident work during this startup (it normaly does work).
Hmm. I suspect we can get the USB mouse to work later.
What happens if you turn off quiet and rhgb in the kernel command line (the same place you put the acpi=noirq)? It will still hang, we just might get to see what's causing the hanging.
I also has a Apacer handy steno 1.1 256mb disk, i was also able to make this work with the ACPI=off. The only thing here is that the Apacer stick is /dev/sda, even if only this stick is in the usb port.
Why does 1 of them use /dev/sda, when the other comes in as /dev/sda1 ?
Manufacturer differences. Some put a partition table on their USB disks, as though they are hard disks, and you get sda1. Others don't, as though the disks are floppies or CDs, and you get sda.
Persons with sufficient spare time may experiment with partitioning CDs and not partitioning hard disks. The end results should work in Unix- based systems, but the rest of the world will probably get horribly confused.
Also, how can I disable the graphical boot to see wats going on when the hangs during the boot?
That's the removing rhgb I was talking about earlier.
James was also earlyer talking about maby making a bugzilla entry about this.. Is this problem something to add to bugzilla, and if so.. how?
Yes please.
Visit bugzilla.redhat.com, specify the kernel as the component cauing you grief.
One other thing to consider: I don't know if your laptop supports APM, the older equivalent. You might investigate turning ACPI off permanently, which should enable APM. You'd then have to configure the laptop to use APM to do laptop-style stuff like power management and suspend. I can't really help you there.
James.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
James Wilkinson wrote: | | Manufacturer differences. Some put a partition table on their USB disks, | as though they are hard disks, and you get sda1. Others don't, as though | the disks are floppies or CDs, and you get sda. | | Persons with sufficient spare time may experiment with partitioning CDs | and not partitioning hard disks. The end results should work in Unix- | based systems, but the rest of the world will probably get horribly | confused. |
I have done this with Iomega Zip disks. Under Windows-DOS-OS/2, the zip disk is expected to have a partition table with one partition numbered 4 formatted as FAT. Under Linux this works out to hdX4 . I have been able to delete the partition table and create file systems directly on the raw disk and mount it using hdX . Windows chokes on a disk like this. Apple formatted zip disk use yet another scheme.
I assume that the USB flash disk might be accessible and modifiable in this way, although the partition scheme might be implemented in the device's firmware. Trying to change these settings might render the device unusable.
William
man, 04.10.2004 kl. 14.18 skrev James Wilkinson:
Tor Harald Thorland was having trouble with a USB disk.
James suggested:
... booting with acpi=off (at the end of the kernel comand line:
Tor replied:
Yes, Its getting further... I can now mount /dev/sda1 to /mnt/flash (or wathever) when I have the ACPI=off.
James: Hooray. You have nailed down the problem to the ACPI subsystem.
Tor: I tryed to make the ACPI=noirq. Then the I rebooted, and the computer hang, right after the graphical boot said: setting hostname (or something.. I have norwegian text on it) Also the my usb mouse dident work during this startup (it normaly does work).
James: Hmm. I suspect we can get the USB mouse to work later.
What happens if you turn off quiet and rhgb in the kernel command line (the same place you put the acpi=noirq)? It will still hang, we just might get to see what's causing the hanging.
I have turned them off now, and got the following: Before the welcome to fedora..... I had some ACPI errors, it is too much text to write down and reproduce her, is there some way to log the startup text to a file or something?
After the welcome i got the following: (Freely translated from norwegian to english) Setting hostname localhost [OK] Initializing USB controller (ohci-hcd) [OK] Mounting USB-filesystem [OK]
Then the system hang....
Is there also a way to keep the whole starup in English instead of norwegian?
James: One other thing to consider: I don't know if your laptop supports APM, the older equivalent. You might investigate turning ACPI off permanently, which should enable APM. You'd then have to configure the laptop to use APM to do laptop-style stuff like power management and suspend. I can't really help you there.
I have a 1 year old Fujitsu Siemens Amilo A7600.... If anyone reading this has some info on this please supply it :-) I've tryed the power management thing without success
Thanx Again! Tor Harald Thorland
Tor Harald Thorland wrote:
I have turned them off now, and got the following: Before the welcome to fedora..... I had some ACPI errors, it is too much text to write down and reproduce her, is there some way to log the startup text to a file or something?
Well, if you boot correctly, you can look at /var/log/dmesg. That gets over-written each boot, though. That's at around line 843 of /etc/rc.d/rc.sysinit: you could alter this file (carefully) to make it save the log somewhere else, and earlier or later.
After the welcome i got the following: (Freely translated from norwegian to english) Setting hostname localhost [OK] Initializing USB controller (ohci-hcd) [OK] Mounting USB-filesystem [OK]
Then the system hang....
That's around line 220 of the same file. How are you at shell scripting? Can you put echo statements in at suitable places, so we can see where everything is hanging?
Is there also a way to keep the whole starup in English instead of norwegian?
It looks like this is picked up from /etc/sysconfig/i18n by about line 20 of /etc/init.d/functions.
There are a number of ways of making sure that LANG gets set to en_US, en_GB, or C.
Hope this helps,
James.
tir, 05.10.2004 kl. 14.22 skrev James Wilkinson:
Tor Harald Thorland wrote:
I have turned them off now, and got the following: Before the welcome to fedora..... I had some ACPI errors, it is too much text to write down and reproduce her, is there some way to log the startup text to a file or something?
Well, if you boot correctly, you can look at /var/log/dmesg. That gets over-written each boot, though. That's at around line 843 of /etc/rc.d/rc.sysinit: you could alter this file (carefully) to make it save the log somewhere else, and earlier or later.
I took a copy of this file when it booted correctly, and edited it on another pc, to be the same as the text on my laptop, when it hang. I have attached it to this mail if you could look at it.
The dmesg program should have an append option :-)
After the welcome i got the following: (Freely translated from norwegian to english) Setting hostname localhost [OK] Initializing USB controller (ohci-hcd) [OK] Mounting USB-filesystem [OK]
Then the system hang....
That's around line 220 of the same file. How are you at shell scripting? Can you put echo statements in at suitable places, so we can see where everything is hanging?
I havent done this :-) But is it easy? It must be somwhere in this USB mounting thing, because the next thing for it to carry out is checking the file system..
Is there also a way to keep the whole starup in English instead of norwegian?
It looks like this is picked up from /etc/sysconfig/i18n by about line 20 of /etc/init.d/functions.
There are a number of ways of making sure that LANG gets set to en_US, en_GB, or C.
I will try this later today :-)
Thanx again!
Tor Harald
-
James Wilkinson -
Tor Harald Thorland -
William Anderson