/ Forside / Teknologi / Operativsystemer / Linux / Nyhedsindlæg
Login
Glemt dit kodeord?
Brugernavn

Kodeord


Reklame
Top 10 brugere
Linux
#NavnPoint
o.v.n. 11177
peque 7911
dk 4814
e.c 2359
Uranus 1334
emesen 1334
stone47 1307
linuxrules 1214
Octon 1100
10  BjarneD 875
Problemer med PCI controller på 2.6.8 kern~
Fra : Kasper Nordal Lund


Dato : 07-01-05 22:38

Hej ng.

Jeg har en promise fasttrack 100 pci controller hvorpå der sidder 2
ide diske. Mit problem er at den ikke finder controlleren når jeg
booter med en 2.6 kerne, men der er ingen problemer med en 2.4 kerne.

Jeg kan se at den i 2.4 kernen bruger driveren pdc202xx_old til
kortet, men det virker ikke under 2.6. Jjeg har fosøgt at sætte både
pdc202xx_old og pdc202xx_new ind i /etc/modules men ligemeget hjælper
det. Den loadeer modulet fint nok, men ved lsmod staår der bare 0
(nul) ud for driveren - bliver den loadet for sent på denne måde eller
hvad?

Nogen der kan hjælpe mig så jeg igen kan se mine data?

Systemet er debian testing med en 2.8.6 kerne hentet med apt-get.

/Kasper

 
 
Thomas S. Iversen (07-01-2005)
Kommentar
Fra : Thomas S. Iversen


Dato : 07-01-05 23:30

Kasper Nordal Lund <someone@somewhere.com> skrev 2005-01-07:

> Nogen der kan hjælpe mig så jeg igen kan se mine data?

Har du selv kompileret din nye kerne?

Hvis ja så compiler support for de 2 promise drivere ind i kernen.

Ellers send den fejl du får når du prøver at loade modulerne under 2.6.8.

Thomas

Kasper Nordal Lund (08-01-2005)
Kommentar
Fra : Kasper Nordal Lund


Dato : 08-01-05 06:01

On 07 Jan 2005 22:29:50 GMT, "Thomas S. Iversen"
<zensonic@zensonic.dk> wrote:

>Kasper Nordal Lund <someone@somewhere.com> skrev 2005-01-07:
>
>> Nogen der kan hjælpe mig så jeg igen kan se mine data?
>
>Har du selv kompileret din nye kerne?

Nej den er installeret via apt-get og det er helt præcis den der
hedder 2.6.8-1-686

>Hvis ja så compiler support for de 2 promise drivere ind i kernen.
>
>Ellers send den fejl du får når du prøver at loade modulerne under 2.6.8.

Jeg får igen fejl når jeg loader det men det er som om at modulet
bliver loadet efter at der er scannet for pci devices for det virker
ikke - men det kan selvfølgfelig også være noget andet....

Der står som sagt et nul ud for navnet på modulet hvis jeg skriver
lsmod som indikerer at det ikke bliver brugt.

/Kasper



Thomas S. Iversen (08-01-2005)
Kommentar
Fra : Thomas S. Iversen


Dato : 08-01-05 12:20

On 2005-01-08, Kasper Nordal Lund <someone@somewhere.com> wrote:
> Der står som sagt et nul ud for navnet på modulet hvis jeg skriver
> lsmod som indikerer at det ikke bliver brugt.

Send lige outputtet af dmesg når maskinen er kommet op. Så kan du se hvad
driveren siger og hvilke diske den finder.

Thomas

Kasper Nordal Lund (08-01-2005)
Kommentar
Fra : Kasper Nordal Lund


Dato : 08-01-05 14:25

On 08 Jan 2005 11:19:32 GMT, "Thomas S. Iversen"
<zensonic@zensonic.dk> wrote:


>Send lige outputtet af dmesg når maskinen er kommet op. Så kan du se hvad
>driveren siger og hvilke diske den finder.

Kommer her:

Linux version 2.6.8-1-686 (joshk@trollwife) (gcc version 3.3.5 (Debian
1:3.3.5-2)) #1 Thu Nov 25 04:34:30 UTC 2004
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000004c000000 (usable)
BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
320MB HIGHMEM available.
896MB LOWMEM available.
found SMP MP-table at 000f0200
On node 0 totalpages: 311296
DMA zone: 4096 pages, LIFO batch:1
Normal zone: 225280 pages, LIFO batch:16
HighMem zone: 81920 pages, LIFO batch:16
DMI 2.3 present.
ACPI: RSDP (v000 COMPAQ ) @
0x000e0010
ACPI: RSDT (v001 COMPAQ CPQD030 0x00000001 0x00000000) @ 0x000e0080
ACPI: FADT (v001 COMPAQ ProLiant 0x00000001 IECs 0x00000001) @
0x000e00d0
ACPI: MADT (v001 COMPAQ MAPICTBL 0x00000001 IECs 0x00000000) @
0x000e0144
ACPI: SSDT (v001 COMPAQ VILLTBL1 0x00000001 MSFT 0x0100000b) @
0x000e1740
ACPI: SSDT (v001 COMPAQ PNP_PRSS 0x00000001 MSFT 0x0100000b) @
0x000e26c5
ACPI: DSDT (v001 COMPAQ DSDT 0x00000001 MSFT 0x0100000b) @
0x00000000
ACPI: PM-Timer IO Port: 0xf808
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 6:8 APIC version 17
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
IOAPIC[0]: Assigned apic_id 8
IOAPIC[0]: apic_id 8, version 17, address 0xfec00000, GSI 0-15
ACPI: IOAPIC (id[0x03] address[0xfec01000] gsi_base[16])
IOAPIC[1]: Assigned apic_id 3
IOAPIC[1]: apic_id 3, version 17, address 0xfec01000, GSI 16-31
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 low level)
ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 low level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
ACPI: IRQ10 used by override.
ACPI: IRQ11 used by override.
Enabling APIC mode: Flat. Using 2 I/O APICs
Using ACPI (MADT) for SMP configuration information
Built 1 zonelists
Kernel command line: root=/dev/sda1 ro
Initializing CPU#0
PID hash table entries: 4096 (order 12: 32768 bytes)
Detected 662.681 MHz processor.
Using pmtmr for high-res timesource
Console: colour VGA+ 80x25
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 1226172k/1245184k available (1545k kernel code, 17884k
reserved, 684k data, 148k init, 327680k highmem)
Checking if this processor honours the WP bit even in supervisor
mode... Ok.
Calibrating delay loop... 1314.81 BogoMIPS
Security Scaffold v1.0.0 initialized
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: After generic identify, caps: 0383fbff 00000000 00000000 00000000
CPU: After vendor identify, caps: 0383fbff 00000000 00000000 00000000
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 256K
CPU: After all inits, caps: 0383fbff 00000000 00000000 00000040
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: Intel Pentium III (Coppermine) stepping 03
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
enabled ExtINT on CPU#0
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
ENABLING IO-APIC IRQs
init IO_APIC IRQs
IO-APIC (apicid-pin) 8-0, 3-0, 3-1, 3-2, 3-3, 3-4, 3-5, 3-6, 3-7,
3-8, 3-9, 3-10, 3-11, 3-12, 3-13, 3-14, 3-15 not connect
ed.
...TIMER: vector=0x31 pin1=2 pin2=-1
...MP-BIOS bug: 8254 timer not connected to IO-APIC
....trying to set up timer (IRQ0) through the 8259A ... failed.
....trying to set up timer as Virtual Wire IRQ... works.
Using local APIC timer interrupts.
calibrating APIC timer ...
...... CPU clock speed is 662.0122 MHz.
...... host bus clock speed is 132.0424 MHz.
checking if image is initramfs...it isn't (ungzip failed); looks like
an initrd
Freeing initrd memory: 4600k freed
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xeda2c, last bus=5
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
ACPI: Subsystem revision 20040326
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Interrupt Link [LNK0] (IRQs 3 4 5 7 10 11 14 15) *0,
disabled.
ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 7 10 11 14 15) *0,
disabled.
ACPI: PCI Interrupt Link [LNK2] (IRQs 3 4 5 7 10 11 14 15) *0,
disabled.
ACPI: PCI Interrupt Link [LNK3] (IRQs 3 4 5 7 10 11 14 15) *0,
disabled.
ACPI: PCI Interrupt Link [LNK4] (IRQs 3 4 5 7 10 11 14 15) *0,
disabled.
ACPI: PCI Interrupt Link [LNK5] (IRQs 3 4 5 7 10 11 14 15) *0,
disabled.
ACPI: PCI Interrupt Link [LNK6] (IRQs 3 4 5 7 10 11 14 *15)
ACPI: PCI Interrupt Link [LNK7] (IRQs 3 4 5 7 10 *11 14 15)
ACPI: PCI Interrupt Link [LNK8] (IRQs 3 4 5 7 *10 11 14 15)
ACPI: PCI Interrupt Link [LNK9] (IRQs 3 4 *5 7 10 11 14 15)
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 7 10 11 14 *15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 7 10 11 14 15) *0,
disabled.
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 7 10 11 14 15) *0,
disabled.
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 7 10 11 14 15) *0,
disabled.
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 7 10 11 14 15) *0,
disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 7 10 11 14 15) *0,
disabled.
ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 7 10 11 14 15) *0,
disabled.
ACPI: PCI Root Bridge [PCI0] (00:00)
PCI: Probing PCI hardware (bus 00)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Root Bridge [PCI5] (00:05)
PCI: Probing PCI hardware (bus 05)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI5._PRT]
Linux Plug and Play Support v0.97 (c) Adam Belay
PnPBIOS: Scanning system for PnP BIOS support...
PnPBIOS: Found PnP BIOS installation structure at 0xc00fe1c0
PnPBIOS: PnP BIOS version 1.0, entry 0xf0000:0x6614, dseg 0xf0000
pnp: 00:10: ioport range 0x208-0x20f has been reserved
pnp: 00:10: ioport range 0x4d0-0x4d1 has been reserved
pnp: 00:10: ioport range 0xc00-0xc01 has been reserved
pnp: 00:11: ioport range 0xf800-0xf81f has been reserved
pnp: 00:11: ioport range 0xf820-0xf83f has been reserved
pnp: 00:11: ioport range 0xf840-0xf85f has been reserved
pnp: 00:11: ioport range 0xf860-0xf87f has been reserved
pnp: 00:11: ioport range 0xfa00-0xfa1f has been reserved
pnp: 00:11: ioport range 0xfa20-0xfa3f has been reserved
pnp: 00:11: ioport range 0xfc00-0xfc0f has been reserved
pnp: 00:11: ioport range 0xfe00-0xfe1f has been reserved
PnPBIOS: 16 nodes reported by PnP BIOS; 16 recorded by driver
PCI: Using ACPI for IRQ routing
ACPI: PCI interrupt 0000:00:02.0[A] -> GSI 26 (level, low) -> IRQ 169
ACPI: PCI interrupt 0000:01:04.0[A] -> GSI 22 (level, low) -> IRQ 177
ACPI: PCI interrupt 0000:01:05.0[A] -> GSI 23 (level, low) -> IRQ 185
ACPI: PCI interrupt 0000:01:06.0[A] -> GSI 24 (level, low) -> IRQ 193
ACPI: PCI interrupt 0000:01:07.0[A] -> GSI 25 (level, low) -> IRQ 201
number of MP IRQ sources: 15.
number of IO-APIC #8 registers: 16.
number of IO-APIC #3 registers: 16.
testing the IO APIC.......................
IO APIC #8......
..... register #00: 08000000
........ : physical APIC id: 08
........ : Delivery Type: 0
........ : LTS : 0
..... register #01: 000F0011
........ : max redirection entries: 000F
........ : PRQ implemented: 0
........ : IO APIC version: 0011
..... register #02: 08000000
........ : arbitration: 08
..... IRQ redirection table:
NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
00 000 00 1 0 0 0 0 0 0 00
01 001 01 0 0 0 0 0 1 1 39
02 000 00 1 0 0 0 0 0 0 00
03 001 01 0 0 0 0 0 1 1 41
04 001 01 0 0 0 0 0 1 1 49
05 001 01 0 0 0 0 0 1 1 51
06 001 01 0 0 0 0 0 1 1 59
07 001 01 0 0 0 0 0 1 1 61
08 001 01 0 0 0 0 0 1 1 69
09 001 01 0 1 0 1 0 1 1 71
0a 001 01 1 1 0 1 0 1 1 79
0b 001 01 1 1 0 1 0 1 1 81
0c 001 01 0 0 0 0 0 1 1 89
0d 001 01 0 0 0 0 0 1 1 91
0e 001 01 0 0 0 0 0 1 1 99
0f 001 01 0 0 0 0 0 1 1 A1
IO APIC #3......
..... register #00: 03000000
........ : physical APIC id: 03
........ : Delivery Type: 0
........ : LTS : 0
..... register #01: 000F0011
........ : max redirection entries: 000F
........ : PRQ implemented: 0
........ : IO APIC version: 0011
..... register #02: 03000000
........ : arbitration: 03
..... IRQ redirection table:
NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
00 000 00 1 0 0 0 0 0 0 00
01 000 00 1 0 0 0 0 0 0 00
02 000 00 1 0 0 0 0 0 0 00
03 000 00 1 0 0 0 0 0 0 00
04 000 00 1 0 0 0 0 0 0 00
05 000 00 1 0 0 0 0 0 0 00
06 001 01 1 1 0 1 0 1 1 B1
07 001 01 1 1 0 1 0 1 1 B9
08 001 01 1 1 0 1 0 1 1 C1
09 001 01 1 1 0 1 0 1 1 C9
0a 001 01 1 1 0 1 0 1 1 A9
0b 000 00 1 0 0 0 0 0 0 00
0c 000 00 1 0 0 0 0 0 0 00
0d 000 00 1 0 0 0 0 0 0 00
0e 000 00 1 0 0 0 0 0 0 00
0f 000 00 1 0 0 0 0 0 0 00
Using vector-based indexing
IRQ to pin mappings:
IRQ0 -> 0:2
IRQ1 -> 0:1
IRQ3 -> 0:3
IRQ4 -> 0:4
IRQ5 -> 0:5
IRQ6 -> 0:6
IRQ7 -> 0:7
IRQ8 -> 0:8
IRQ9 -> 0:9
IRQ10 -> 0:10
IRQ11 -> 0:11
IRQ12 -> 0:12
IRQ13 -> 0:13
IRQ14 -> 0:14
IRQ15 -> 0:15
IRQ177 -> 1:6
IRQ185 -> 1:7
IRQ193 -> 1:8
IRQ201 -> 1:9
IRQ169 -> 1:10
..................................... done.
highmem bounce pool size: 64 pages
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x0
Initializing Cryptographic API
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Serial: 8250/16550 driver $Revision: 1.90 $ 48 ports, IRQ sharing
enabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a NS16550A
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
input: AT Translated Set 2 keyboard on isa0060/serio0
NET: Registered protocol family 2
IP: routing cache hash table of 16384 buckets, 128Kbytes
TCP: Hash tables configured (established 524288 bind 65536)
NET: Registered protocol family 8
NET: Registered protocol family 20
ACPI: (supports S0 S4 S5)
RAMDISK: cramfs filesystem found at block 0
RAMDISK: Loading 4600 blocks [1 disk] into ram disk... \
done.
VFS: Mounted root (cramfs filesystem) readonly.
Freeing unused kernel memory: 148k freed
vesafb: probe of vesafb0 failed with error -6
NET: Registered protocol family 1
SCSI subsystem initialized
ACPI: PCI interrupt 0000:01:04.0[A] -> GSI 22 (level, low) -> IRQ 177
sym0: <895a> rev 0x1 at pci 0000:01:04.0 irq 177
sym0: using 64 bit DMA addressing
sym0: No NVRAM, ID 7, Fast-40, LVD, parity checking
sym0: SCSI BUS has been reset.
scsi0 : sym-2.1.18j
Using anticipatory io scheduler
Vendor: COMPAQ Model: BB00921B91 Rev: 3B07
Type: Direct-Access ANSI SCSI revision: 02
sym0:0:0: tagged command queuing enabled, command queue depth 16.
scsi(0:0:0:0): Beginning Domain Validation
sym0:0: wide asynchronous.
sym0:0: FAST-40 WIDE SCSI 80.0 MB/s ST (25.0 ns, offset 15)
scsi(0:0:0:0): Domain Validation skipping write tests
scsi(0:0:0:0): Ending Domain Validation
SCSI device sda: 17773524 512-byte hdwr sectors (9100 MB)
SCSI device sda: drive cache: write through
/dev/scsi/host0/bus0/target0/lun0: p1 p2 < p5 >
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Adding 400360k swap on /dev/sda5. Priority:-1 extents:1
EXT3 FS on sda1, internal journal
Real Time Clock Driver v1.12
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
Capability LSM initialized
e100: Intel(R) PRO/100 Network Driver, 3.0.18
e100: Copyright(c) 1999-2004 Intel Corporation
ACPI: PCI interrupt 0000:01:05.0[A] -> GSI 23 (level, low) -> IRQ 185
e100: eth0: e100_probe: addr 0xb1200000, irq 185, MAC addr
00:50:8B:EA:26:82
parport: PnPBIOS parport detected.
parport0: PC-style at 0x378 (0x778), irq 7, dma 3
[PCSPP,TRISTATE,COMPAT,EPP,ECP,DMA]
inserting floppy driver for 2.6.8-1-686
Floppy drive(s): fd0 is 1.44M
FDC 0 is a National Semiconductor PC87306
input: PC Speaker
Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Maximum main memory to use for agp memory: 1125M
agpgart: unable to determine aperture size.
agpgart: agp_backend_initialize() failed.
agpgart-serverworks: probe of 0000:00:00.0 failed with error -22
agpgart: Maximum main memory to use for agp memory: 1125M
agpgart: unable to determine aperture size.
agpgart: agp_backend_initialize() failed.
agpgart-serverworks: probe of 0000:00:00.1 failed with error -22
cpci_hotplug: CompactPCI Hot Plug Core version: 0.2
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pciehp: PCI Express Hot Plug Controller Driver version: 0.4
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 <saw@saw.sw.com.sg> and others
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
USB Universal Host Controller Interface driver v2.2
e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
NET: Registered protocol family 17
NET: Registered protocol family 10
Disabled Privacy Extensions on device c02fd020(lo)
IPv6 over IPv4 tunneling driver
eth0: no IPv6 routers present
e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
eth0: no IPv6 routers present

Jeg kan ikke se at den finder nogen ide diske og jeg kan heller ikke
se at den finder controlleren, men det er måske bare mig der ikke ved
hvad jeg skal se efter.

/Kasper

Thomas S. Iversen (08-01-2005)
Kommentar
Fra : Thomas S. Iversen


Dato : 08-01-05 16:52

On 2005-01-08, Kasper Nordal Lund <someone@somewhere.com> wrote:
> Jeg kan ikke se at den finder nogen ide diske og jeg kan heller ikke
> se at den finder controlleren, men det er måske bare mig der ikke ved
> hvad jeg skal se efter.

Nej den finder hverken diske eller controller

Hvilket medium booter du fra?

Og hvad sker der hvis du laver en

modprobe <drivernavn>

Bare de sidste 5-10 linier efter modprobe er fint fra en dmesg

Thomas

Kasper Nordal Lund (10-01-2005)
Kommentar
Fra : Kasper Nordal Lund


Dato : 10-01-05 12:55

On 08 Jan 2005 15:51:39 GMT, "Thomas S. Iversen"
<zensonic@zensonic.dk> wrote:

>
>Bare de sidste 5-10 linier efter modprobe er fint fra en dmesg

Der sker absolut intet i dmesg hverken med pdc202xx_old eller
pdc202xx_new.


Thomas S. Iversen (10-01-2005)
Kommentar
Fra : Thomas S. Iversen


Dato : 10-01-05 13:37

>>Bare de sidste 5-10 linier efter modprobe er fint fra en dmesg
>
> Der sker absolut intet i dmesg hverken med pdc202xx_old eller
> pdc202xx_new.

Hmm, jeg har lige forsøgt at loade modulet (har ikke en controller).
Det gik fint. Det bliver loadet. Jeg får ingen i /var/log/kern.log (dmsg)

Den burde give dig en ROM enabled at bla bla bla når chippen blev
fundet.

Har du chippen enablet i bios?

ellers send lige outputtet af: lspci -n

THomas

Kasper Nordal Lund (11-01-2005)
Kommentar
Fra : Kasper Nordal Lund


Dato : 11-01-05 10:42

On 10 Jan 2005 12:36:54 GMT, "Thomas S. Iversen"
<zensonic@zensonic.dk> wrote:

>
>Har du chippen enablet i bios?

Jeg er ret siker på at den er enablet, da den virkede på samme maskine
med 2.4 kernel på en standard woody installation.
Jeg har reinstalleret med en testing og her detecter den fint at der
er en controller med 2.4 kernen men den skriver at den er unknown.

Med 2.6 kernen er det stadig samme problem.

>ellers send lige outputtet af: lspci -n

kommer her:

0000:00:00.0 0600: 1166:0009 (rev 05)
0000:00:00.1 0600: 1166:0009 (rev 05)
0000:00:01.0 0604: 1011:0024 (rev 03)
0000:00:02.0 0180: 105a:4d30 (rev 02)
0000:00:0f.0 0601: 1166:0200 (rev 4f)
0000:00:0f.1 0101: 1166:0211
0000:01:04.0 0100: 1000:0012 (rev 01)
0000:01:05.0 0200: 8086:1229 (rev 08)
0000:01:06.0 0300: 1002:4752 (rev 27)
0000:01:07.0 0880: 0e11:a0f0


/Kasper


Søg
Reklame
Statistik
Spørgsmål : 177550
Tips : 31968
Nyheder : 719565
Indlæg : 6408823
Brugere : 218887

Månedens bedste
Årets bedste
Sidste års bedste