Kirjoittaja Aihe: ytimen kääntämisestä..  (Luettu 4180 kertaa)

Sledgehammer

  • Käyttäjä
  • Viestejä: 41
    • Profiili
ytimen kääntämisestä..
« : 19.12.05 - klo:11.59 »
Löysin täältä foorumilta ohjeen yhimen kääntämiseen..

http://forum.ubuntu-fi.org/index.php?topic=113.0

4. Konfiguroidaan ydin ja käännetään se asennuspaketiksi
cd linux
make menuconfig Konfigurointi. Tiedä mitä teet!
make-kpkg clean Puhdistetaan mahdollisesti käännetty roina
make-kpkg –revision=2.6.12.4+xxxxxx kernel_image Määritellään nimi asennuspaketille ja aloitetaan kääntäminen. Tämä on pitkällinen prosessi riippuen paljon valituista moduuleista ja sisään rakennetuista tuista kuten myös luonnollisesti suorittimen tehosta. Aikaa menee puolesta tunnista useisiin tunteihin.
dpkg –i ../kernel-image-2.6.12.4+xxxxxx.deb Asennetaan luotu ydin

Mitähän "make-kpkg –revision=2.6.12.4+xxxxxx kernel_image" -kohdassa pitäisi tehdä? pitääkö xxxxxx ja kernel_image paikalle kirjoittaa jotain?

juyli

  • Vieras
Re: ytimen kääntämisestä..
« Vastaus #1 : 19.12.05 - klo:12.30 »
http://forum.ubuntu-fi.org/index.php?topic=113.0

Tuo annettu HOWTO on nimenomaan Ubuntu/Debian spesifi. Ehkä kuitenkin on hyödyksi tutustua ihan standardiin ohjeeseen ytimen kääntämiseksi, joka toimii kaikissa jakeluissa:
http://www.wiki.linux.fi/mediawiki-1.5.2/index.php/Kernelin_k%C3%A4%C3%A4nt%C3%A4minen


Sledgehammer

  • Käyttäjä
  • Viestejä: 41
    • Profiili
Re: ytimen kääntämisestä..
« Vastaus #2 : 19.12.05 - klo:13.31 »
Sain käännettyän ytimen ja linux menee päälle aivan normaalisti. :) Kuitenkin ytimen latausvaiheessa tulee aivan selvästi jotain virheilmoituksia. Mitenkä saan nähtyä mitä ne virheet ovat?

_Pete_

  • Käyttäjä
  • Viestejä: 1845
  • Fufufuuffuuu
    • Profiili
Re: ytimen kääntämisestä..
« Vastaus #3 : 19.12.05 - klo:14.01 »
Sain käännettyän ytimen ja linux menee päälle aivan normaalisti. :) Kuitenkin ytimen latausvaiheessa tulee aivan selvästi jotain virheilmoituksia. Mitenkä saan nähtyä mitä ne virheet ovat?

Komentamalla bootin jälkeen konsolissa:

sudo dmesg


Sledgehammer

  • Käyttäjä
  • Viestejä: 41
    • Profiili
Re: ytimen kääntämisestä..
« Vastaus #4 : 19.12.05 - klo:14.13 »
sudo dmesg:


60/serio0. Some program, like XFree86, might be trying access hardware directly.[17179579.180000] atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly.
[17179579.200000] atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly.
[17179579.204000] atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly.
[17179579.208000] atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly.
[17179579.212000] ieee1394: Initialized config rom entry `ip1394'
[17179579.216000] atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly.
[17179579.220000] atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly.
[17179579.224000] atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly.
[17179579.232000] atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly.
[17179579.236000] atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly.
[17179579.240000] atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly.
[17179579.248000] atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly.
[17179579.248000] sbp2: $Rev: 1306 $ Ben Collins <bcollins@debian.org>
[17179579.248000] ieee1394: sbp2: Driver forced to serialize I/O (serialize_io=1)
[17179579.248000] ieee1394: sbp2: Try serialize_io=0 for better performance
[17179579.252000] atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly.
[17179579.256000] atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly.
[17179579.264000] atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly.
[17179579.268000] atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly.
[17179579.272000] atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly.
[17179579.280000] atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly.
[17179579.284000] atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly.
[17179579.292000] atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly.
[17179579.296000] atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly.
[17179579.356000] atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly.
[17179579.656000] ide0: I/O resource 0x1F0-0x1F7 not free.
[17179579.656000] ide0: ports already in use, skipping probe
[17179579.656000] ide1: I/O resource 0x170-0x177 not free.
[17179579.656000] ide1: ports already in use, skipping probe
[17179582.544000] device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-devel@redhat.com
[17179583.356000] synaptics reset failed
[17179583.620000] device-mapper: dm-linear: Device lookup failed
[17179583.620000] device-mapper: error adding target to table
[17179583.624000] device-mapper: dm-linear: Device lookup failed
[17179583.624000] device-mapper: error adding target to table
[17179583.628000] device-mapper: dm-linear: Device lookup failed
[17179583.628000] device-mapper: error adding target to table
[17179583.632000] device-mapper: dm-linear: Device lookup failed
[17179583.632000] device-mapper: error adding target to table
[17179583.636000] device-mapper: dm-linear: Device lookup failed
[17179583.636000] device-mapper: error adding target to table
[17179583.636000] device-mapper: dm-linear: Device lookup failed
[17179583.636000] device-mapper: error adding target to table
[17179583.644000] device-mapper: dm-linear: Device lookup failed
[17179583.644000] device-mapper: error adding target to table
[17179583.648000] device-mapper: dm-linear: Device lookup failed
[17179583.648000] device-mapper: error adding target to table
[17179583.648000] device-mapper: dm-linear: Device lookup failed
[17179583.648000] device-mapper: error adding target to table
[17179583.648000] device-mapper: dm-linear: Device lookup failed
[17179583.648000] device-mapper: error adding target to table
[17179583.648000] device-mapper: dm-linear: Device lookup failed
[17179583.648000] device-mapper: error adding target to table
[17179583.648000] device-mapper: dm-linear: Device lookup failed
[17179583.648000] device-mapper: error adding target to table
[17179583.652000] device-mapper: dm-linear: Device lookup failed
[17179583.652000] device-mapper: error adding target to table
[17179583.652000] device-mapper: dm-linear: Device lookup failed
[17179583.652000] device-mapper: error adding target to table
[17179583.652000] device-mapper: dm-linear: Device lookup failed
[17179583.652000] device-mapper: error adding target to table
[17179583.652000] device-mapper: dm-linear: Device lookup failed
[17179583.652000] device-mapper: error adding target to table
[17179583.656000] device-mapper: dm-linear: Device lookup failed
[17179583.656000] device-mapper: error adding target to table
[17179583.656000] device-mapper: dm-linear: Device lookup failed
[17179583.656000] device-mapper: error adding target to table
[17179583.656000] device-mapper: dm-linear: Device lookup failed
[17179583.656000] device-mapper: error adding target to table
[17179583.660000] device-mapper: dm-linear: Device lookup failed
[17179583.660000] device-mapper: error adding target to table
[17179583.880000] kjournald starting.  Commit interval 5 seconds
[17179583.880000] EXT3 FS on sda4, internal journal
[17179583.880000] EXT3-fs: mounted filesystem with ordered data mode.
[17179583.900000] NTFS driver 2.1.24 [Flags: R/O MODULE].
[17179583.972000] NTFS volume version 3.1.
[17179584.024000] NTFS volume version 3.1.
[17179585.540000] Linux agpgart interface v0.101 (c) Dave Jones
[17179585.544000] agpgart: Detected an Intel 915GM Chipset.
[17179585.564000] agpgart: AGP aperture is 256M @ 0x0
[17179585.740000] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[17179585.792000] shpchp: shpc_init : shpc_cap_offset == 0
[17179585.792000] shpchp: shpc_init : shpc_cap_offset == 0
[17179585.792000] shpchp: shpc_init : shpc_cap_offset == 0
[17179585.792000] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[17179586.248000] ACPI: PCI Interrupt 0000:00:1b.0[A] -> Link [LNKA] -> GSI 10 (level, low) -> IRQ 10
[17179586.248000] PCI: Setting latency timer of device 0000:00:1b.0 to 64
[17179586.848000] USB Universal Host Controller Interface driver v2.3
[17179586.852000] ACPI: PCI Interrupt Link [LNKH] enabled at IRQ 11
[17179586.852000] ACPI: PCI Interrupt 0000:00:1d.0[A] -> Link [LNKH] -> GSI 11 (level, low) -> IRQ 11
[17179586.852000] PCI: Setting latency timer of device 0000:00:1d.0 to 64
[17179586.852000] uhci_hcd 0000:00:1d.0: UHCI Host Controller
[17179586.856000] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
[17179586.856000] uhci_hcd 0000:00:1d.0: irq 11, io base 0x00001800
[17179586.860000] hub 1-0:1.0: USB hub found
[17179586.860000] hub 1-0:1.0: 2 ports detected
[17179586.964000] ACPI: PCI Interrupt 0000:00:1d.1 -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11
[17179586.964000] PCI: Setting latency timer of device 0000:00:1d.1 to 64
[17179586.964000] uhci_hcd 0000:00:1d.1: UHCI Host Controller
[17179586.968000] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
[17179586.968000] uhci_hcd 0000:00:1d.1: irq 11, io base 0x00001820
[17179586.976000] hub 2-0:1.0: USB hub found
[17179586.976000] hub 2-0:1.0: 2 ports detected
[17179587.080000] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10
[17179587.080000] ACPI: PCI Interrupt 0000:00:1d.2[C] -> Link [LNKC] -> GSI 10 (level, low) -> IRQ 10
[17179587.080000] PCI: Setting latency timer of device 0000:00:1d.2 to 64
[17179587.080000] uhci_hcd 0000:00:1d.2: UHCI Host Controller
[17179587.080000] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3
[17179587.080000] uhci_hcd 0000:00:1d.2: irq 10, io base 0x00001840
[17179587.088000] hub 3-0:1.0: USB hub found
[17179587.088000] hub 3-0:1.0: 2 ports detected
[17179587.192000] ACPI: PCI Interrupt 0000:00:1d.3[D] -> Link [LNKA] -> GSI 10 (level, low) -> IRQ 10
[17179587.192000] PCI: Setting latency timer of device 0000:00:1d.3 to 64
[17179587.192000] uhci_hcd 0000:00:1d.3: UHCI Host Controller
[17179587.192000] uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 4
[17179587.192000] uhci_hcd 0000:00:1d.3: irq 10, io base 0x00001860
[17179587.204000] hub 4-0:1.0: USB hub found
[17179587.204000] hub 4-0:1.0: 2 ports detected
[17179587.356000] synaptics reset failed
[17179587.432000] usb 3-2: new low speed USB device using uhci_hcd and address 2[17179587.644000] ACPI: PCI Interrupt 0000:00:1d.7[A] -> Link [LNKH] -> GSI 11 (level, low) -> IRQ 11
[17179587.644000] PCI: Setting latency timer of device 0000:00:1d.7 to 64
[17179587.644000] ehci_hcd 0000:00:1d.7: EHCI Host Controller
[17179587.644000] ehci_hcd 0000:00:1d.7: debug port 1
[17179587.652000] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 5
[17179587.652000] ehci_hcd 0000:00:1d.7: irq 11, io mem 0xc8004000
[17179587.656000] PCI: cache line size of 32 is not supported by device 0000:00:1d.7
[17179587.656000] ehci_hcd 0000:00:1d.7: USB 2.0 initialized, EHCI 1.00, driver 10 Dec 2004
[17179587.660000] hub 5-0:1.0: USB hub found
[17179587.660000] hub 5-0:1.0: 8 ports detected
[17179587.696000] usb 3-2: USB disconnect, address 2
[17179587.824000] usbcore: registered new driver hiddev
[17179587.876000] hw_random: RNG not detected
[17179587.892000] Synaptics Touchpad, model: 1, fw: 5.9, id: 0x126eb1, caps: 0xa04713/0x4000
[17179587.892000] input: SynPS/2 Synaptics TouchPad on isa0060/serio1
[17179587.972000] input: AT Translated Set 2 keyboard on isa0060/serio0
[17179588.008000] usbcore: registered new driver usbhid
[17179588.008000] drivers/usb/input/hid-core.c: v2.6:USB HID core driver
[17179588.440000] usb 3-2: new low speed USB device using uhci_hcd and address 3[17179588.628000] ieee80211_crypt: registered algorithm 'NULL'
[17179588.636000] input: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:1d.2-2
[17179588.720000] ipw2200: Unknown parameter `led'
[17179588.836000] ts: Compaq touchscreen protocol output
[17179588.932000] tg3.c:v3.42 (Oct 3, 2005)
[17179588.932000] ACPI: PCI Interrupt 0000:06:06.0[A]: no GSI - using IRQ 10
[17179588.960000] eth0: Tigon3 [partno(BCM95788A50) rev 3003 PHY(5705)] (PCI:33MHz:32-bit) 10/100/1000BaseT Ethernet 00:c0:9f:b8:3f:4b
[17179588.960000] eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[0] TSOcap[1]
[17179588.960000] eth0: dma_rwctrl[763f0000]
[17179589.072000] ohci1394: $Rev: 1313 $ Ben Collins <bcollins@debian.org>
[17179589.072000] ACPI: PCI Interrupt 0000:06:07.0[A]: no GSI - using IRQ 11
[17179589.128000] ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[11]  MMIO=[c8215000-c82157ff]  Max Packet=[2048]
[17179589.252000] ACPI: PCI Interrupt 0000:06:09.0[A] -> Link [LNKE] -> GSI 10 (level, low) -> IRQ 10
[17179589.252000] Yenta: CardBus bridge found at 0000:06:09.0 [1025:0070]
[17179589.252000] Yenta O2: res at 0x94/0xD4: ea/00
[17179589.252000] Yenta O2: enabling read prefetch/write burst
[17179589.380000] Yenta: ISA IRQ mask 0x00b8, PCI irq 10
[17179589.380000] Socket status: 30000006
[17179589.380000] pcmcia: parent PCI bridge I/O window: 0x3000 - 0x3fff
[17179589.380000] cs: IO port probe 0x3000-0x3fff: clean.
[17179589.380000] pcmcia: parent PCI bridge Memory window: 0xc8200000 - 0xc82fffff
[17179589.380000] pcmcia: parent PCI bridge Memory window: 0x50000000 - 0x51ffffff
[17179589.644000] Yenta: no bus associated with 0000:06:09.1! (try 'pci=assign-busses')
[17179589.644000] Yenta: no bus associated with 0000:06:09.3! (try 'pci=assign-busses')
[17179590.400000] ieee1394: Host added: ID:BUS[0-00:1023]  GUID[00c09f00005c9a8a]
[17179590.992000] Real Time Clock Driver v1.12
[17179591.696000] NET: Registered protocol family 17
[17179593.352000] tg3: eth1: Link is up at 100 Mbps, full duplex.
[17179593.352000] tg3: eth1: Flow control is off for TX and off for RX.
[17179602.556000] NET: Registered protocol family 10
[17179602.556000] Disabled Privacy Extensions on device c02ba180(lo)
[17179602.556000] IPv6 over IPv4 tunneling driver
[17179603.404000] ACPI: AC Adapter [ACAD] (on-line)
[17179603.464000] ACPI: Battery Slot [BAT1] (battery present)
[17179603.464000] ACPI: Battery Slot [BAT2] (battery absent)
[17179603.484000] ACPI: Power Button (FF) [PWRF]
[17179603.484000] ACPI: Lid Switch [LID]
[17179603.484000] ACPI: Power Button (CM) [PWRB]
[17179603.484000] ACPI: Sleep Button (CM) [SLPB]
[17179603.524000] Using specific hotkey driver
[17179603.552000] ibm_acpi: ec object not found
[17179603.584000] toshiba_acpi: Unknown parameter `hotkeys_over_acpi'
[17179603.596000] ACPI: Video Device [VGA] (multi-head: yes  rom: no  post: no)
[17179604.664000]     ACPI-0339: *** Error: Looking up [Z00G] in namespace, AE_NOT_FOUND
[17179604.664000] search_node c18e0ac0 start_node c18e0ac0 return_node 00000000
[17179604.664000]     ACPI-0508: *** Error: Method execution failed [\_SB_.BAT1._BST] (Node c18e09c0), AE_NOT_FOUND
[17179604.684000]     ACPI-0339: *** Error: Looking up [Z00G] in namespace, AE_NOT_FOUND
[17179604.684000] search_node c18e0ac0 start_node c18e0ac0 return_node 00000000
[17179604.684000]     ACPI-0508: *** Error: Method execution failed [\_SB_.BAT1._BST] (Node c18e09c0), AE_NOT_FOUND
[17179610.436000] mtrr: no more MTRRs available
[17179610.436000] mtrr: no more MTRRs available
[17179610.436000] mtrr: no more MTRRs available
[17179610.436000] mtrr: no more MTRRs available
[17179610.436000] mtrr: no more MTRRs available
[17179612.764000] apm: BIOS not found.
[17179612.892000] eth1: no IPv6 routers present
[17179613.340000] pcmcia: Detected deprecated PCMCIA ioctl usage.
[17179613.340000] pcmcia: This interface will soon be removed from the kernel; please expect breakage unless you upgrade to new tools.
[17179613.340000] pcmcia: see http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html for details.
[17179613.340000] cs: IO port probe 0x100-0x4ff: excluding 0x370-0x377 0x3f0-0x3f7 0x4d0-0x4d7
[17179613.344000] cs: IO port probe 0xc00-0xcf7: clean.
[17179613.344000] cs: IO port probe 0xa00-0xaff: clean.
[17179613.680000] Bluetooth: Core ver 2.7
[17179613.680000] NET: Registered protocol family 31
[17179613.680000] Bluetooth: HCI device and connection manager initialized
[17179613.680000] Bluetooth: HCI socket layer initialized
[17179613.704000] Bluetooth: L2CAP ver 2.7
[17179613.704000] Bluetooth: L2CAP socket layer initialized
[17179613.732000] Bluetooth: RFCOMM ver 1.5
[17179613.732000] Bluetooth: RFCOMM socket layer initialized
[17179613.732000] Bluetooth: RFCOMM TTY layer initialized
[17179620.672000] synaptics: using relaxed packet validation
[17179634.376000]     ACPI-0339: *** Error: Looking up [Z00G] in namespace, AE_NOT_FOUND
[17179634.376000] search_node c18e0ac0 start_node c18e0ac0 return_node 00000000
[17179634.376000]     ACPI-0508: *** Error: Method execution failed [\_SB_.BAT1._BST] (Node c18e09c0), AE_NOT_FOUND


tollainen tuli.. mitähän tosta pitäis ottaa selville?  ;D

Sledgehammer

  • Käyttäjä
  • Viestejä: 41
    • Profiili
Re: ytimen kääntämisestä..
« Vastaus #5 : 19.12.05 - klo:18.30 »
Niin osaisko joku kertoa mitä mun pitäis muuttaa että toi uus kerneli toimis täydellisesti?

_Pete_

  • Käyttäjä
  • Viestejä: 1845
  • Fufufuuffuuu
    • Profiili
Re: ytimen kääntämisestä..
« Vastaus #6 : 20.12.05 - klo:08.52 »
Niin osaisko joku kertoa mitä mun pitäis muuttaa että toi uus kerneli toimis täydellisesti?

Minusta tuo näyttää aivan normaalilta. Eikö sitten joku ominaisuus toimi uudessa kernelissä ?


Sledgehammer

  • Käyttäjä
  • Viestejä: 41
    • Profiili
Re: ytimen kääntämisestä..
« Vastaus #7 : 20.12.05 - klo:10.01 »
Niin osaisko joku kertoa mitä mun pitäis muuttaa että toi uus kerneli toimis täydellisesti?

Minusta tuo näyttää aivan normaalilta. Eikö sitten joku ominaisuus toimi uudessa kernelissä ?



Toimii uus kerneli hyvin mutta kun ajattelin että kun tossa on ettei löydy kaikkia ajureita jne.. Haittaako ne jotain?

_Pete_

  • Käyttäjä
  • Viestejä: 1845
  • Fufufuuffuuu
    • Profiili
Re: ytimen kääntämisestä..
« Vastaus #8 : 20.12.05 - klo:14.21 »
Toimii uus kerneli hyvin mutta kun ajattelin että kun tossa on ettei löydy kaikkia ajureita jne.. Haittaako ne jotain?

Sinä varmaan tiedät sen paremmin kuin me. Eli jos kaikki toimii niin kuin pitää, ei haittaa.