Find the answer to your Linux question:
Results 1 to 3 of 3
Hi, I'm trying to upgrade my Slackware 10 (2.4.26) to the 2.6.7 kernel. Everything went well until reboot, when the system froze right after "Using anticipatory io scheduler", and a ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Jun 2004
    Posts
    8

    Ghost Floppy Disk and ACPI


    Hi,

    I'm trying to upgrade my Slackware 10 (2.4.26) to the 2.6.7 kernel. Everything went well until reboot, when the system froze right after "Using anticipatory io scheduler", and a "no cont in shutdown!" message would show up. I went back to the 2.4 kernel and noticed that that's where the floppy modules are being looked for. I figured this could be an IRQ conflict and I booted again with the 2.6 kernel with "acpi=off", and the system booted fine (all the useful laptop stuff and sound gone, though). I've attached the successful boot sequence below, right to the point where the system would freeze without the acpi=off option.

    The question is, is there any way to get the kernel not to look for the floppy controllers? I looked in /etc with the hope that I could comment something out, but no luck. Do I need to recompile the kernel with no floppy disk support or something?

    I should add I have a toshiba 5005 laptop w/ an external USB floppy drive, so it's no surprise that "floppy0: no floppy controllers found" shows up at that point in the boot sequence.

    Any ideas?

    Thanks
    Carlos



    Linux version 2.6.7 (root@trauco) (gcc version 3.3.4) #2 Sat Sep 18 12:18:37 EDT 2004
    BIOS-provided physical RAM map:
    BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
    BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
    BIOS-e820: 00000000000e0000 - 00000000000eee00 (reserved)
    BIOS-e820: 00000000000eee00 - 00000000000ef000 (ACPI NVS)
    BIOS-e820: 00000000000ef000 - 0000000000100000 (reserved)
    BIOS-e820: 0000000000100000 - 000000001fff0000 (usable)
    BIOS-e820: 000000001fff0000 - 0000000020000000 (ACPI data)
    BIOS-e820: 00000000feea0000 - 00000000feec0000 (reserved)
    BIOS-e820: 00000000ffb80000 - 00000000ffc00000 (reserved)
    BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
    511MB LOWMEM available.
    On node 0 totalpages: 131056
    DMA zone: 4096 pages, LIFO batch:1
    Normal zone: 126960 pages, LIFO batch:16
    HighMem zone: 0 pages, LIFO batch:1
    DMI 2.3 present.
    Built 1 zonelists
    Kernel command line: BOOT_IMAGE=Linux2.6 ro root=307 acpi=off
    Initializing CPU#0
    PID hash table entries: 2048 (order 11: 16384 bytes)
    Detected 1096.886 MHz processor.
    Using tsc for high-res timesource
    Console: colour dummy device 80x25
    Memory: 515796k/524224k available (1871k kernel code, 7664k reserved, 854k data, 156k init, 0k highmem)
    Checking if this processor honours the WP bit even in supervisor mode... Ok.
    Calibrating delay loop... 2170.88 BogoMIPS
    Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
    Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
    Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
    CPU: After generic identify, caps: 0383f9ff 00000000 00000000 00000000
    CPU: After vendor identify, caps: 0383f9ff 00000000 00000000 00000000
    CPU: L1 I cache: 16K, L1 D cache: 16K
    CPU: L2 cache: 256K
    CPU: After all inits, caps: 0383f9ff 00000000 00000000 00000040
    Intel machine check architecture supported.
    Intel machine check reporting enabled on CPU#0.
    CPU: Intel Pentium III (Coppermine) stepping 0a
    Enabling fast FPU save and restore... done.
    Enabling unmasked SIMD FPU exception support... done.
    Checking 'hlt' instruction... OK.
    checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
    Freeing initrd memory: 390k freed
    NET: Registered protocol family 16
    PCI: PCI BIOS revision 2.10 entry at 0xfd144, last bus=4
    PCI: Using configuration type 1
    mtrr: v2.0 (20020519)
    ACPI: Subsystem revision 20040326
    ACPI: Interpreter disabled.
    Linux Plug and Play Support v0.97 (c) Adam Belay
    SCSI subsystem initialized
    usbcore: registered new driver usbfs
    usbcore: registered new driver hub
    PCI: Probing PCI hardware
    PCI: Probing PCI hardware (bus 00)
    PCI: Transparent bridge - 0000:00:1e.0
    vesafb: framebuffer at 0xf0000000, mapped to 0xe0800000, size 3072k
    vesafb: mode is 1024x768x16, linelength=2048, pages=1
    vesafb: protected mode interface info at c000:d4e0
    vesafb: scrolling: redraw
    vesafb: directcolor: size=0:5:6:5, shift=0:11:5:0
    fb0: VESA VGA frame buffer device
    VFS: Disk quotas dquot_6.5.1
    Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
    Initializing Cryptographic API
    pci_hotplug: PCI Hot Plug PCI Core version: 0.5
    isapnp: Scanning for PnP cards...
    isapnp: No Plug & Play device found
    Console: switching to colour frame buffer device 128x48
    Real Time Clock Driver v1.12
    Serial: 8250/16550 driver $Revision: 1.90 $ 48 ports, IRQ sharing enabled
    PCI: Enabling device 0000:00:1f.6 (0000 -> 0001)
    PCI: No IRQ known for interrupt pin B of device 0000:00:1f.6. Please try using pci=biosirq.
    Using anticipatory io scheduler
    floppy0: no floppy controllers found

  2. #2
    Linux User
    Join Date
    Jul 2004
    Location
    USA, Michigan, Detroit
    Posts
    329
    Did you use a stock kernel or compile one on the laptop you are using?
    Long live the revolution!
    Have a nice day.
    If you want real change vote Libertarian!

  3. #3
    Just Joined!
    Join Date
    Jun 2004
    Posts
    8
    Quote Originally Posted by copycon
    Did you use a stock kernel or compile one on the laptop you are using?
    I compiled it myself, but not very carefully, basically using the defaults of the slackware package file + acpi. I did it again since my last post and unchecked all suport for floppy disks, and now it loads just fine. I wish I knew why the same basic configuration was working w/2.4 and froze with 2.6. In any case, I'm all set now.

    Thanks for your answer.

  4. $spacer_open
    $spacer_close

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •