Probleme beim Aufwachen nach ACPI S3

Debian auf Notebooks und speziellen Geräten wie eingebetteten Systemen, Routern, Set-Top-Boxen, ...
Antworten
HubertB
Beiträge: 77
Registriert: 20.07.2005 16:59:17

Probleme beim Aufwachen nach ACPI S3

Beitrag von HubertB » 03.11.2005 18:43:02

Hallo!

Ich kann mein Laptop mit

Code: Alles auswählen

echo -n "mem" > /sys/power/state
wunderbar schlafen legen. Aber beim Aufwachen bringt er mir folgendes:

Code: Alles auswählen

        Linu

Back to C!
Warning: CPU frequency out of sync: cpufreq and timingcore thinks of 663600, is
1526200 kHz.
PM: Finished up.
PCI: Enabling device 0000:00:0a.0 (0000 -> 0002)
ACPI: PCI interrupt 0000:00:0a.0[A] -> GSI 11 (level, low) -> IRQ 11
prism2_hw_init: initialized in 270 ms
PCI: Enabling device 0000:00:0b.0 (0000 -> 0003)
ACPI: PCI interrput 0000:00:0b.0[A] -> GSI 5 (level, low) -> IRQ 5
Dann passiert gar nichts mehr. Woran liegts?

Laptop ist ein Mitac 8375, Kernel 2.6.8 Debian Sarge.

lspci:

Code: Alles auswählen

0000:00:00.0 Host bridge: VIA Technologies, Inc. P/KN266 Host Bridge
0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP]
0000:00:09.0 CardBus bridge: ENE Technology Inc CB1410 Cardbus Controller
0000:00:0a.0 Network controller: Intersil Corporation Prism 2.5 Wavelan chipset (rev 01)
0000:00:0b.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80)
0000:00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
0000:00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
0000:00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82)
0000:00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
0000:00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
0000:00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50)
0000:00:11.6 Communication controller: VIA Technologies, Inc. Intel 537 [AC97 Modem] (rev 80)
0000:00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74)
0000:01:00.0 VGA compatible controller: S3 Inc. VT8375 [ProSavage8 KM266/KL266]
dmesg:

Code: Alles auswählen

cking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay loop... 3022.84 BogoMIPS
Security Scaffold v1.0.0 initialized
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: After generic identify, caps: 0383fbff c1cbfbff 00000000 00000000
CPU: After vendor identify, caps:  0383fbff c1cbfbff 00000000 00000000
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 256K (64 bytes/line)
CPU: After all inits, caps:        0383fbff c1cbfbff 00000000 00000020
CPU: AMD mobile AMD Athlon(tm) XP 1800+ stepping 00
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
Checking for popad bug... OK.
enabled ExtINT on CPU#0
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
Using local APIC timer interrupts.
calibrating APIC timer ...
..... CPU clock speed is 1525.0554 MHz.
..... host bus clock speed is 265.0313 MHz.
checking if image is initramfs...it isn't (ungzip failed); looks like an initrd
Freeing initrd memory: 4216k freed
NET: Registered protocol family 16
EISA bus registered
PCI: PCI BIOS revision 2.10 entry at 0xe8b24, last bus=1
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
ACPI: Subsystem revision 20040326
ACPI: IRQ9 SCI: Edge set to Level Trigger.
spurious 8259A interrupt: IRQ7.
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (00:00)
PCI: Probing PCI hardware (bus 00)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: Embedded Controller [EC0] (gpe 5)
ACPI: PCI Interrupt Link [LNKA] (IRQs 5 7 *10 11)
ACPI: PCI Interrupt Link [LNKB] (IRQs 5 7 10 *11)
ACPI: PCI Interrupt Link [LNKC] (IRQs *5 7 10 11)
ACPI: PCI Interrupt Link [LNKD] (IRQs 5 7 10 *11)
ACPI: Power Resource [PFAN] (off)
Linux Plug and Play Support v0.97 (c) Adam Belay
PnPBIOS: Scanning system for PnP BIOS support...
PnPBIOS: Found PnP BIOS installation structure at 0xc00ff020
PnPBIOS: PnP BIOS version 1.0, entry 0xea000:0x3ee0, dseg 0xea000
PNPBIOS fault.. attempting recovery.
PnPBIOS: Warning! Your PnP BIOS caused a fatal error. Attempting to continue
PnPBIOS: You may need to reboot with the "nobiospnp" option to operate stably
PnPBIOS: Check with your vendor for an updated BIOS
PnPBIOS: dev_node_info: unexpected status 0x28
PnPBIOS: Unable to get node info.  Aborting.
PCI: Using ACPI for IRQ routing
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 11
ACPI: PCI interrupt 0000:00:09.0[A] -> GSI 11 (level, low) -> IRQ 11
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11
ACPI: PCI interrupt 0000:00:0a.0[A] -> GSI 11 (level, low) -> IRQ 11
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 5
ACPI: PCI interrupt 0000:00:0b.0[A] -> GSI 5 (level, low) -> IRQ 5
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 10
ACPI: PCI interrupt 0000:00:10.0[A] -> GSI 10 (level, low) -> IRQ 10
ACPI: PCI interrupt 0000:00:10.1[B] -> GSI 11 (level, low) -> IRQ 11
ACPI: PCI interrupt 0000:00:10.3[D] -> GSI 11 (level, low) -> IRQ 11
ACPI: PCI interrupt 0000:00:11.1[A]: no GSI
ACPI: PCI interrupt 0000:00:11.5[C] -> GSI 5 (level, low) -> IRQ 5
ACPI: PCI interrupt 0000:00:11.6[C] -> GSI 5 (level, low) -> IRQ 5
ACPI: PCI interrupt 0000:00:12.0[A] -> GSI 10 (level, low) -> IRQ 10
ACPI: PCI interrupt 0000:01:00.0[A] -> GSI 10 (level, low) -> IRQ 10
Simple Boot Flag at 0x37 set to 0x1
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 $ 54 ports, IRQ sharing enabled
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
i8042.c: Detected active multiplexing controller, rev 1.1.
serio: i8042 AUX0 port at 0x60,0x64 irq 12
serio: i8042 AUX1 port at 0x60,0x64 irq 12
serio: i8042 AUX2 port at 0x60,0x64 irq 12
serio: i8042 AUX3 port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
input: AT Translated Set 2 keyboard on isa0060/serio0
EISA: Probing bus 0 at eisa0
EISA: Detected 0 cards.
NET: Registered protocol family 2
IP: routing cache hash table of 4096 buckets, 32Kbytes
TCP: Hash tables configured (established 32768 bind 65536)
NET: Registered protocol family 8
NET: Registered protocol family 20
ACPI: (supports S0 S3 S4 S5)
RAMDISK: cramfs filesystem found at block 0
RAMDISK: Loading 4216 blocks [1 disk] into ram disk... done.
VFS: Mounted root (cramfs filesystem) readonly.
Freeing unused kernel memory: 204k freed
vesafb: probe of vesafb0 failed with error -6
NET: Registered protocol family 1
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller at PCI slot 0000:00:11.1
ACPI: PCI interrupt 0000:00:11.1[A]: no GSI
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt8235 (rev 00) IDE UDMA133 controller on pci0000:00:11.1
    ide0: BM-DMA at 0x1100-0x1107, BIOS settings: hda:DMA, hdb:pio
    ide1: BM-DMA at 0x1108-0x110f, BIOS settings: hdc:DMA, hdd:pio
hda: ST94011A, ATA DISK drive
Using anticipatory io scheduler
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: max request size: 1024KiB
hda: 78140160 sectors (40007 MB) w/2048KiB Cache, CHS=16383/255/63, UDMA(100)
 /dev/ide/host0/bus0/target0/lun0: p1 p2 p3
hdc: CD-224E-BA, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
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: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
Adding 1004020k swap on /dev/hda1.  Priority:-1 extents:1
EXT3 FS on hda2, internal journal
Generic RTC Driver v1.07
hdc: ATAPI 24X CD-ROM drive, 128kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
Synaptics Touchpad, model: 1
 Firmware: 5.1
 180 degree mounted touchpad
 Sensor: 15
 new absolute packet format
 Touchpad has extended capability bits
 -> four buttons
 -> multifinger detection
 -> palm detection
input: SynPS/2 Synaptics TouchPad on isa0060/serio3
ieee1394: Initialized config rom entry `ip1394'
SCSI subsystem initialized
sbp2: $Rev: 1219 $ Ben Collins <bcollins@debian.org>
ACPI: Processor [CPU0] (supports C1 C2)
powernow: PowerNOW! Technology present. Can scale: frequency and voltage.
powernow: FSB: 132.720 MHz
mice: PS/2 mouse device common for all mice
ts: Compaq touchscreen protocol output
powernow: Found PSB header at c00f0e40
powernow: Table version: 0x12
powernow: Flags: 0x0 (Mobile voltage regulator)
powernow: Settling Time: 100 microseconds.
powernow: Has 1 PST tables. (Only dumping ones relevant to this CPU).
powernow: PST:0 (@c00f0e50)
powernow:  cpuid: 0x780 fsb: 133        maxFID: 0x1     startvid: 0x9
powernow:    FID: 0x4 (5.0x [663MHz])   VID: 0x19 (1.050V)
powernow:    FID: 0x6 (6.0x [796MHz])   VID: 0x19 (1.050V)
powernow:    FID: 0x7 (6.5x [862MHz])   VID: 0x17 (1.100V)
powernow:    FID: 0x8 (7.0x [929MHz])   VID: 0x15 (1.150V)
powernow:    FID: 0x9 (7.5x [995MHz])   VID: 0x13 (1.200V)
powernow:    FID: 0xa (8.0x [1061MHz])  VID: 0x11 (1.250V)
powernow:    FID: 0xb (8.5x [1128MHz])  VID: 0xe (1.300V)
powernow:    FID: 0xc (9.0x [1194MHz])  VID: 0xd (1.350V)
powernow:    FID: 0xd (9.5x [1260MHz])  VID: 0xc (1.400V)
powernow:    FID: 0xe (10.0x [1327MHz]) VID: 0xb (1.450V)
powernow:    FID: 0xf (10.5x [1393MHz]) VID: 0xa (1.500V)
powernow:    FID: 0x1 (11.5x [1526MHz]) VID: 0x9 (1.550V)
powernow: SGTC: 13333
powernow: Minimum speed 663 MHz. Maximum speed 1526 MHz.
Capability LSM initialized
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda3, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Linux Kernel Card Services
  options:  [pci] [cardbus] [pm]
ACPI: PCI interrupt 0000:00:09.0[A] -> GSI 11 (level, low) -> IRQ 11
Yenta: CardBus bridge found at 0000:00:09.0 [1071:8375]
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:09.0, mfunc 0x010c1672, devctl 0x44
Yenta: ISA IRQ mask 0x0010, PCI irq 11
Socket status: 30000006
ohci1394: $Rev: 1223 $ Ben Collins <bcollins@debian.org>
ACPI: PCI interrupt 0000:00:0b.0[A] -> GSI 5 (level, low) -> IRQ 5
ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[5]  MMIO=[fedff800-fedfffff]  Max Packet=[2048]
irda_init()
NET: Registered protocol family 23
IrDA: Registered device irda0
via-rhine.c:v1.10-LK1.1.20-2.6 May-23-2004 Written by Donald Becker
ACPI: PCI interrupt 0000:00:12.0[A] -> GSI 10 (level, low) -> IRQ 10
eth0: VIA Rhine II at 0xe300, 00:40:d0:2d:99:c2, IRQ 10.
eth0: MII PHY found at address 1, status 0x7849 advertising 05e1 Link 0000.
Via 686a/8233/8235 audio driver 1.9.1-ac4-2.5
ACPI: PCI interrupt 0000:00:11.5[C] -> GSI 5 (level, low) -> IRQ 5
via82cxxx: Six channel audio available
PCI: Setting latency timer of device 0000:00:11.5 to 64
ac97_codec: AC97 Audio codec, id: VIA97 (Unknown)
via82cxxx: board #1 at 0xE100, IRQ 5
usbcore: registered new driver usbfs
usbcore: registered new driver hub
USB Universal Host Controller Interface driver v2.2
ACPI: PCI interrupt 0000:00:10.0[A] -> GSI 10 (level, low) -> IRQ 10
uhci_hcd 0000:00:10.0: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
uhci_hcd 0000:00:10.0: irq 10, io base 00001200
uhci_hcd 0000:00:10.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
ACPI: PCI interrupt 0000:00:10.1[B] -> GSI 11 (level, low) -> IRQ 11
uhci_hcd 0000:00:10.1: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (#2)
uhci_hcd 0000:00:10.1: irq 11, io base 00001300
uhci_hcd 0000:00:10.1: new USB bus registered, assigned bus number 2
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ieee1394: Host added: ID:BUS[0-00:1023]  GUID[0040d001000a530b]
ACPI: PCI interrupt 0000:00:10.3[D] -> GSI 11 (level, low) -> IRQ 11
ehci_hcd 0000:00:10.3: VIA Technologies, Inc. USB 2.0
ehci_hcd 0000:00:10.3: irq 11, pci mem dea10000
ehci_hcd 0000:00:10.3: new USB bus registered, assigned bus number 3
ehci_hcd 0000:00:10.3: USB 2.0 enabled, EHCI 1.00, driver 2004-May-10
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 4 ports detected
ip1394: $Rev: 1224 $ Ben Collins <bcollins@debian.org>
ip1394: eth1: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0)
Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected VIA Apollo Pro266 chipset
agpgart: Maximum main memory to use for agp memory: 409M
agpgart: AGP aperture is 64M @ 0xa0000000
cpci_hotplug: CompactPCI Hot Plug Core version: 0.2
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: acpi_pciehprm:\_SB_.PCI0 evaluate _BBN fail=0x5
pciehp: acpi_pciehprm:get_device PCI ROOT HID fail=0x5
shpchp: acpi_shpchprm:\_SB_.PCI0 evaluate _BBN fail=0x5
shpchp: acpi_shpchprm:get_device PCI ROOT HID fail=0x5
hostap_crypt: registered algorithm 'NULL'
hostap_pci: 0.3.7 - 2005-02-12 (Jouni Malinen <jkmaline@cc.hut.fi>)
ACPI: PCI interrupt 0000:00:0a.0[A] -> GSI 11 (level, low) -> IRQ 11
hostap_pci: Registered netdevice wifi0
wifi0: Original COR value: 0x0
prism2_hw_init: initialized in 196 ms
wifi0: NIC: id=0x8013 v1.0.0
wifi0: PRI: id=0x15 v1.1.1
wifi0: STA: id=0x1f v1.8.0
wifi0: Intersil Prism2.5 PCI: mem=0xa4000000, irq=11
wifi0: registered netdevice wlan0
ACPI: Battery Slot [BAT0] (battery present)
ACPI: AC Adapter [AC] (off-line)
ACPI: Power Button (FF) [PWRF]
ACPI: Sleep Button (CM) [SBTN]
ACPI: Lid Switch [LID]
ACPI: Fan [FAN0] (off)
ACPI: Thermal Zone [THRM] (45 C)
cs: IO port probe 0x0100-0x04ff: excluding 0x378-0x37f 0x4d0-0x4d7
cs: IO port probe 0x0800-0x08ff: clean.
cs: IO port probe 0x0c00-0x0cff: clean.
cs: IO port probe 0x0a00-0x0aff: clean.
NET: Registered protocol family 10
Disabled Privacy Extensions on device c02cc960(lo)
IPv6 over IPv4 tunneling driver
vmmon: module license 'unspecified' taints kernel.
/dev/vmmon[2436]: Module vmmon: registered with major=10 minor=165
/dev/vmmon[2436]: Module vmmon: initialized
parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE]
parport0: irq 7 detected
/dev/vmnet: open called by PID 2457 (vmnet-bridge)
/dev/vmnet: hub 0 does not exist, allocating memory.
/dev/vmnet: port on hub 0 successfully opened
bridge-eth0: enabling the bridge
bridge-eth0: up
bridge-eth0: already up
bridge-eth0: attached
/dev/vmnet: open called by PID 2470 (vmnet-netifup)
/dev/vmnet: hub 8 does not exist, allocating memory.
/dev/vmnet: port on hub 8 successfully opened
/dev/vmnet: open called by PID 2495 (vmnet-netifup)
/dev/vmnet: hub 1 does not exist, allocating memory.
/dev/vmnet: port on hub 1 successfully opened
/dev/vmnet: open called by PID 2469 (vmnet-natd)
/dev/vmnet: port on hub 8 successfully opened
/dev/vmnet: open called by PID 2520 (vmnet-dhcpd)
/dev/vmnet: port on hub 1 successfully opened
/dev/vmnet: open called by PID 2521 (vmnet-dhcpd)
/dev/vmnet: port on hub 8 successfully opened
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
apm: overridden by ACPI.
eth0: no IPv6 routers present
vmnet8: no IPv6 routers present
vmnet1: no IPv6 routers present
[/code]

Benutzeravatar
peschmae
Beiträge: 4844
Registriert: 07.01.2003 12:50:33
Lizenz eigener Beiträge: MIT Lizenz
Wohnort: nirgendwo im irgendwo

Beitrag von peschmae » 03.11.2005 21:21:22

Das kann an irgendwas liegen. Versuch am besten mal einen aktuelleren Kernel als 2.6.8.
An ACPI gibts ständig Verbesserungen die in den Kernel kommen.

MfG Peschmä
"er hätte nicht in die usa ziehen dürfen - die versauen alles" -- Snoopy

HubertB
Beiträge: 77
Registriert: 20.07.2005 16:59:17

Beitrag von HubertB » 05.11.2005 16:38:20

Ich habe mir eben einen 2.6.14 gebaut. Der bootet auch soweit gut, allerdings bekomme ich immernoch die Fehlermeldung, nur das sie jetzt ein ganz klein wenig anders aussieht.

Wer weis Rat?

HubertB
Beiträge: 77
Registriert: 20.07.2005 16:59:17

Beitrag von HubertB » 07.11.2005 08:44:58

Nachtrag: Hier ist die Fehlermeldung, die der Kernel 2.6.14 produziert.

Code: Alles auswählen

    Linu

Back to C!
PCI: Setting latency timeer of device 0000:00:01.0 to 64
ACPI: PCI interrupt 0000:00:09.0[A] -> Link [LNKB] -> GSI 11 (level, low) -> IRQ 11
PCI: Enabling device 0000:00:0b.0 (0080 -> 0083)
ACPI: PCI interrput 0000:00:0b.0[A] -> Link [LNKB] -> GSI 5 (level, low) -> IRQ 5
PCI: Via IRQ fixup for 0000:00:0b.0, from 0 to 5

garp0909
Beiträge: 12
Registriert: 01.11.2005 18:59:42
Wohnort: Vordertaunus nähe Frankfurt/M.

Beitrag von garp0909 » 14.11.2005 23:02:31

etwas OT - aber für mich wegen ACPI-Fragestellungen zu EPIA-Boards interessant:

Da Du von 3.1 den Kernel auf 2.6.14 gehoben hast:
* Kann man auf ein pures stable-System mit 2.6.8-Kernel "einfach so" auf 2.6.14 anheben? apt-get testing kernel....? Bleibt der Rest "stable"?
* Mit welchen Vorteilen hinsichtlich ACPI ist zu rechnen?
* Mit welchen Nachteilen (allgemein) ist zu rechnen?

Danke!

Live long and prosper,
Carsten

HubertB
Beiträge: 77
Registriert: 20.07.2005 16:59:17

Beitrag von HubertB » 15.11.2005 18:21:35

Hi!

Ich hab mir die Sourcen von http://www.kernel.org/ gezogen und mich dann mittles "make menuconfig" durch die Kernelkonfig gekämpft.

Vorteil: Nen aktuellen Kernel (auch wenns bei mir keine Veränderung bringt)

Nachteil: Mehr graue Haare und Falten, bis der selber gebaute Kernel auch wirklich läuft

garp0909
Beiträge: 12
Registriert: 01.11.2005 18:59:42
Wohnort: Vordertaunus nähe Frankfurt/M.

Beitrag von garp0909 » 19.11.2005 13:06:14

Hi,

ich weiß: OT. Aber als letzte Frage von mir passt es hier halt gerade hin:

Ginge das statt über http://www.kernel.org nicht auch mit APT-Mitteln in der Form "apt-get testing kernel 2.6.14<whatever>"? Wäre mir lieber, da ich dann (noch) nicht selber Hand anlegen müsste und ich von der Erfahrung der Paketersteller profitiere. Bleibe also am Standard - nicht am "stable", aber immerhin am "testing". Den Kernel für die Hardware zu optimieren kann ich mir dann noch aufheben...<zitter>

Live long and prosper,
carsten

HubertB
Beiträge: 77
Registriert: 20.07.2005 16:59:17

Beitrag von HubertB » 20.11.2005 17:04:16

Wenn du Testing fährst kannste natürlich auch so nen Kernel installieren. Allerdings heist es ja nicht umsonst testing, kann also auch passieren das der "neue" nicht funktioniert.

Und selber bauen ist nicht wirklich schwer, du musst halt darauf achten, das das / Dateisystem genauso wie die Treiber für die Platte, auf der dieses Dateisystem liegt (SCSI, IDE, ...) fest in den Kernel einkompiliert wird.

Antworten