On Thursday 02 December 2004 21:52, p wrote: > On Thu, Dec 02, 2004 at 01:11:43PM -0800, Benedek Frank wrote: > > __deletia__ > > > Can you tell me, when the recompile is done, what do I do? How do I > > insert the module late, when KDM starts? Write a little script like > > > > modprobe esssolo1 > > > > ??? > > // > > insmod <name of module> > > kthxbye. > > b. > > //
Hi Now, the compile is done. The kernel works fine. :) The module still loads at boot, even I put it in the /etc/hotplug/blacklist file. Now, It makes me think, that something else loads the module before hotplug could even get to it. Here is a piece of the dmesg of the machine. Do you know what would load it? I checked the /etc/modules and /etc/modules.conf file, but there is no mention about the solo1. Thanks ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 hda: max request size: 128KiB hda: 39070080 sectors (20003 MB) w/2048KiB Cache, CHS=38760/16/63, UDMA(66) /dev/ide/host0/bus0/target0/lun0: p1 p2 p3 kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. Adding 488336k swap on /dev/hda1. Priority:-1 extents:1 EXT3 FS on hda2, internal journal Real Time Clock Driver v1.12 SCSI subsystem initialized Linux Kernel Card Services options: [pci] [cardbus] [pm] PCI: Enabling device 0000:00:03.0 (0000 -> 0002) ACPI: PCI interrupt 0000:00:03.0[A] -> GSI 9 (level, low) -> IRQ 9 Yenta: CardBus bridge found at 0000:00:03.0 [1033:80e3] Yenta: Enabling burst memory read transactions Yenta: Using CSCINT to route CSC interrupts to PCI Yenta: Routing CardBus interrupts to PCI Yenta TI: socket 0000:00:03.0, mfunc 0x000c1702, devctl 0x46 Yenta: ISA IRQ mask 0x0cf8, PCI irq 9 Socket status: 30000010 e100: Intel(R) PRO/100 Network Driver, 3.0.18 e100: Copyright(c) 1999-2004 Intel Corporation ACPI: PCI interrupt 0000:00:06.0[A] -> GSI 9 (level, low) -> IRQ 9 e100: eth0: e100_probe: addr 0xfc121000, irq 9, MAC addr 00:10:A4:77:2B:90 solo1: version v0.20 time 12:54:53 Dec 2 2004 ACPI: PCI interrupt 0000:00:04.0[A] -> GSI 11 (level, low) -> IRQ 11 solo1: joystick port at 0x14b1 solo1: ddma base address: 0x1480 usbcore: registered new driver usbfs usbcore: registered new driver hub ohci_hcd: 2004 Feb 02 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI) ohci_hcd: block sizes: ed 64 td 64 ACPI: PCI interrupt 0000:00:14.0[A] -> GSI 5 (level, low) -> IRQ 5 ohci_hcd 0000:00:14.0: ALi Corporation USB 1.1 Controller ohci_hcd 0000:00:14.0: irq 5, pci mem c00d0000 ohci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 1 hub 1-0:1.0: USB hub found hub 1-0:1.0: 2 ports detected input: PC Speaker input: PS/2 Generic Mouse on isa0060/serio1 irda_init() mice: PS/2 mouse device common for all mice NET: Registered protocol family 23 ts: Compaq touchscreen protocol output Linux agpgart interface v0.100 (c) Dave Jones eepro100.c:v1.09j-t 9/29/99 Donald Becker http://www.scyld.com/network/eepro100.html eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin <[EMAIL PROTECTED]> and others NET: Registered protocol family 10 Disabled Privacy Extensions on device c02e5440(lo) IPv6 over IPv4 tunneling driver cs: IO port probe 0x0100-0x04ff: excluding 0x170-0x177 0x370-0x377 cs: IO port probe 0x0800-0x08ff: clean. cs: IO port probe 0x0c00-0x0cff: clean. cs: IO port probe 0x0a00-0x0aff: clean. cs: memory probe 0xa0000000-0xa0ffffff: clean. orinoco.c 0.13e (David Gibson <[EMAIL PROTECTED]> and others) orinoco_cs.c 0.13e (David Gibson <[EMAIL PROTECTED]> and others) eth1: Station identity 001f:0004:0001:0007 eth1: Looks like an Intersil firmware version 1.7.4 eth1: Ad-hoc demo mode supported eth1: IEEE standard IBSS ad-hoc mode supported eth1: WEP supported, 104-bit key eth1: MAC address 00:09:5B:4B:F7:AD eth1: Station name "Prism I" eth1: ready eth1: index 0x01: Vcc 5.0, irq 3, io 0x0100-0x013f eth1: Error -110 setting multicast list. eth1: Error -110 setting multicast list. eth1: New link status: Association Failed (0006) eth1: New link status: Connected (0001) eth1: no IPv6 routers present spurious 8259A interrupt: IRQ7. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
