А можно ли на Mpx 220 линух поставить?
ЗЫ: Просто интересно.
ЗЫ: Просто интересно.
Здравствуйте, гость ( Вход | Регистрация ) |
[MPx220] Объединённая тема по Linux на Mpx220, Linux + Qtopia на MPx220. |
Crayzer666 |
20.3.2008, 17:27
|
Новичок Группа: Пользователи Сообщений: 26 Регистрация: 7.6.2005 Пользователь №: 43 745 Модель телефона: MPx 220 Рейтинг: 0 |
А можно ли на Mpx 220 линух поставить?
ЗЫ: Просто интересно. |
silix |
11.4.2008, 13:56
|
Опытный Группа: Разработчики Сообщений: 121 Регистрация: 16.9.2004 Из: Ахтубинск Пользователь №: 12 905 Модель телефона: Mpx220 Прошивка: 1.47 rus Рейтинг: 112.5 |
11 апреля 2008г 17:57 - Состоялся запуск пробного ядра Linux на МРх220
Сразу же выкладываю лог загрузки, разбиратся буду потом Linux version 2.6.25-rc6-omap1 (root@localhost) (gcc version 4.0.1) #5 PREEMPT Fri Apr 11 17:46:10 MSD 2008 CPU: ARM926EJ-S [41069263] revision 3 (ARMv5TEJ), cr=00053177 Machine: Generic OMAP1510/1610/1710 Memory policy: ECC disabled, Data cache writeback OMAP1611b revision 2 handled as 16xx id: 5a045567210b1a0e SRAM: Mapped pa 0x20000000 to va 0xd7000000 size: 0x100000 CPU0: D VIVT write-back cache CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets CPU0: D cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets Built 1 zonelists in Zone order, mobility grouping on. Total pages: 8128 Kernel command line: console=ttyS0 Clocks: ARM_SYSST: 0x1000 DPLL_CTL: 0x2813 ARM_CKCTL: 0x050e Clocking rate (xtal/DPLL1/MPU): 12.0/192.0/192.0 MHz Total of 128 interrupts in 4 interrupt banks PID hash table entries: 128 (order: 7, 512 bytes) Console: colour dummy device 80x30 Dentry cache hash table entries: 4096 (order: 2, 16384 bytes) Inode-cache hash table entries: 2048 (order: 1, 8192 bytes) Memory: 32MB = 32MB total Memory: 29320KB available (2792K code, 210K data, 112K init) Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok net_namespace: 152 bytes NET: Registered protocol family 16 OMAP DMA hardware version 1 DMA capabilities: 000c0000:00000000:01ff:003f:007f OMAP GPIO hardware version 1.0 Initializing OMAP McBSP system omap_dsp_init() done USB: hmc 16, usb0 6 wires SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb Time: mpu_timer2 clocksource has been installed. NET: Registered protocol family 2 IP route cache hash table entries: 1024 (order: 0, 4096 bytes) TCP established hash table entries: 1024 (order: 1, 8192 bytes) TCP bind hash table entries: 1024 (order: 0, 4096 bytes) TCP: Hash tables configured (established 1024 bind 1024) TCP reno registered Power Management for TI OMAP. NetWinder Floating Point Emulator V0.97 (double precision) OMAP OCPI interconnect driver loaded io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled serial8250.0: ttyS0 at MMIO 0xfffb0000 (irq = 46) is a ST16654 console [ttyS0] enabled serial8250.0: ttyS1 at MMIO 0xfffb0800 (irq = 47) is a ST16654 serial8250.0: ttyS2 at MMIO 0xfffb9800 (irq = 15) is a ST16654 brd: module loaded loop: module loaded PPP generic driver version 2.4.2 drivers/net/usb/rtl8150.c: rtl8150 based usb-ethernet driver v0.6.2 (2004/08/27) usbcore: registered new interface driver rtl8150 usbcore: registered new interface driver asix usbcore: registered new interface driver cdc_ether usbcore: registered new interface driver net1080 usbcore: registered new interface driver cdc_subset usbcore: registered new interface driver zaurus i2c /dev entries driver Driver 'sd' needs updating - please use bus_type methods Driver 'sr' needs updating - please use bus_type methods usbmon: debugfs is not available ohci ohci: OMAP OHCI ohci ohci: new USB bus registered, assigned bus number 1 ohci ohci: irq 38, io mem 0xfffba000 usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 3 ports detected usb usb1: New USB device found, idVendor=1d6b, idProduct=0001 usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb1: Product: OMAP OHCI usb usb1: Manufacturer: Linux 2.6.25-rc6-omap1 ohci_hcd usb usb1: SerialNumber: ohci Initializing USB Mass Storage driver... hub 1-0:1.0: Cannot enable port 1. Maybe the USB cable is bad? hub 1-0:1.0: Cannot enable port 1. Maybe the USB cable is bad? hub 1-0:1.0: Cannot enable port 1. Maybe the USB cable is bad? hub 1-0:1.0: Cannot enable port 1. Maybe the USB cable is bad? usbcore: registered new interface driver usb-storage USB Mass Storage support registered. mice: PS/2 mouse device common for all mice OMAP Keypad Driver omap_rtc omap_rtc: rtc core: registered omap_rtc as rtc0 omap_rtc: already running usbcore: registered new interface driver usbhid drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver TCP cubic registered NET: Registered protocol family 1 NET: Registered protocol family 17 RPC: Registered udp transport module. RPC: Registered tcp transport module. omap_rtc omap_rtc: setting system clock to 2008-04-11 17:53:41 UTC (1207936421) VFS: Cannot open root device "<NULL>" or unknown-block(0,0) Please append a correct "root=" boot option; here are the available partitions: 0100 8192 ram0 (driver?) 0101 8192 ram1 (driver?) 0102 8192 ram2 (driver?) 0103 8192 ram3 (driver?) 0104 8192 ram4 (driver?) 0105 8192 ram5 (driver?) 0106 8192 ram6 (driver?) 0107 8192 ram7 (driver?) 0108 8192 ram8 (driver?) 0109 8192 ram9 (driver?) 010a 8192 ram10 (driver?) 010b 8192 ram11 (driver?) 010c 8192 ram12 (driver?) 010d 8192 ram13 (driver?) 010e 8192 ram14 (driver?) 010f 8192 ram15 (driver?) Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) |
Текстовая версия | Сейчас: 2.6.2024, 3:34 |
Форум живёт: