Buffalo NAS-Central Forums

Welcome to the Linkstation Wiki community
It is currently Tue Feb 20, 2018 2:50 am

All times are UTC+01:00




Post new topic  Reply to topic  [ 283 posts ]  Go to page Previous 113 14 15 16 1719 Next
Author Message
PostPosted: Sat Apr 26, 2008 2:37 am 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
Sylver wrote:
... make the device run faster than previously (vanilla 2.6.25 kernel) !
...


ehhrrrmm... will this perhaps translate into faster network performance (NFS, Samba, iscsi, ftp, whatever...)?

:?:

...also, nice work, thanks for your continued efforts on kernel stuff that will make things better for us ...

_________________
LS1 (foonas, nfs, Tranmission & p910nd print server, Firefly for my Roku)
LS-HG500 (Lenny)
Various LS-Pros v1,v2 (unbricked w/ serial & jtag)
KuroPro, LS2 & KuroHG (foonas)
Working on davysweather.dyndns.org lately...

=> wooohooo!
wooohooo!
Unknown command 'wooohooo!' - try 'help'


Top
   
PostPosted: Sat Apr 26, 2008 8:59 pm 
Offline
Site Admin
User avatar

Joined: Tue Jul 12, 2005 11:26 am
Posts: 3701
Location: JAPAN
I will try this out then as I have always been reverting back to my 2.6.21.3 as it was faster than the vanilla.

_________________
LS used as PVR and streaming source


Top
   
PostPosted: Wed Apr 30, 2008 2:35 pm 
Offline
Newbie
User avatar

Joined: Mon Apr 14, 2008 3:01 pm
Posts: 17
Location: Prague, Czech Republic
Probably it's not interesting but by casuality I found this page, probably it can be useful :)

http://www.google.com/translate?u=http://www.pyon.net/diary/20080406.html


Top
   
PostPosted: Thu May 01, 2008 7:47 pm 
Offline
Developer

Joined: Mon Oct 03, 2005 11:32 pm
Posts: 399
Location: France
Japanese guys are certainly doing a lot of things with the kurobox pro, but we see nothing from them :p
Anyway, this will certainly be the final version of the kurobox pro/linkstation pro shutdown patch : http://marc.info/?l=linux-arm-kernel&m= ... 224741&w=2
Upladed the patch here :
http://terastationpro.free.fr/kuroboxpr ... down.patch
(to apply to git kernel until merged in)

_________________
Kurobox Pro 500GB (for dev) / Freelink / 2.6.26-rc4 kernel, QNAP TS-409 Pro 1TB, Maxtor Shared Storage II 500GB


Top
   
PostPosted: Wed Jul 09, 2008 7:14 pm 
Offline
Regular Member

Joined: Mon Nov 07, 2005 4:37 pm
Posts: 205
Location: Germany
Hi,

currently I try to get an vanilla kernel working on my linkstation pro duo.
Now, with 2.6.25 i've no success - nothing to see on serial output. With the current 2.6.26 release candidate the same. I tried now the checkout from the orion repository and get the kernel working, but it can't mount the root filesystem:
Code:
## Booting image at 00100000 ...
   Image Name:   linux
   Created:      2008-07-09  18:05:40 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1625736 Bytes =  1.6 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK
## Loading Ramdisk Image at 00800000 ...
   Image Name:   initrd
   Created:      2006-12-27  21:19:31 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    4563515 Bytes =  4.4 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK

Starting kernel ...

arg:console=ttyS0,115200 mem=64m root=/dev/sda2 rw initrd=0x00800040,15M panic=5 BOOTVER=1.13
Uncompressing Linux...........................................................................................
Linux version 2.6.26-rc9-00107-gfac7962 (manuel@bigbrother) (gcc version 4.2.1 (CodeSourcery Sourcery G++ Lit8
CPU: Feroceon [41069260] revision 0 (ARMv5TEJ), cr=a0053177
Machine: Buffalo Linkstation Pro/Live
Clearing invalid memory bank 0KB@0xffffffff
Clearing invalid memory bank 0KB@0xffffffff
Clearing invalid memory bank 0KB@0xffffffff
Ignoring unrecognised tag 0x00000000
Ignoring unrecognised tag 0x00000000
Ignoring unrecognised tag 0x00000000
Ignoring unrecognised tag 0x41000403
Memory policy: ECC disabled, Data cache writeback
CPU0: D VIVT write-back cache
CPU0: I cache: 32768 bytes, associativity 1, 32 byte lines, 1024 sets
CPU0: D cache: 32768 bytes, associativity 1, 32 byte lines, 1024 sets
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 16256
Kernel command line: console=ttyS0,115200 mem=64m root=/dev/sda2 rw initrd=0x00800040,15M panic=5 BOOTVER=1.13
PID hash table entries: 256 (order: 8, 1024 bytes)
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 64MB = 64MB total
Memory: 61464KB available (3092K code, 209K data, 104K init)
SLUB: Genslabs=12, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
net_namespace: 192 bytes
NET: Registered protocol family 16
Orion ID: MV88F5182-A2. TCLK=166666667.
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
NET: Registered protocol family 1
NetWinder Floating Point Emulator V0.97 (double precision)
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
msgmni has been set to 120
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 3) is a 16550A
console [ttyS0] enabled
serial8250.1: ttyS1 at MMIO 0xf1012100 (irq = 4) is a 16550A
loop: module loaded
MV-643xx 10/100/1000 Ethernet Driver
net eth0: port 0 with MAC address 00:00:00:00:51:81
net eth0: scatter/gather enabled
net eth0: tx checksum offload
net eth0: napi enabled
Driver 'sd' needs updating - please use bus_type methods
sata_mv sata_mv.0: version 1.24
sata_mv sata_mv.0: slots 32 ports 2
scsi0 : sata_mv
scsi1 : sata_mv
ata1: SATA max UDMA/133 irq 29
ata2: SATA max UDMA/133 irq 29
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1.00: ATA-8: SAMSUNG HD501LJ, CR100-10, max UDMA7
ata1.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata1.00: configured for UDMA/133
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata2.00: ATA-8: SAMSUNG HD501LJ, CR100-12, max UDMA7
ata2.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata2.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access     ATA      SAMSUNG HD501LJ  CR10 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sda: sda1 sda2 sda4 < sda5 sda6 >
sd 0:0:0:0: [sda] Attached SCSI disk
scsi 1:0:0:0: Direct-Access     ATA      SAMSUNG HD501LJ  CR10 PQ: 0 ANSI: 5
sd 1:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 1:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sdb: sdb1 sdb2 sdb4 < sdb5 sdb6 >
sd 1:0:0:0: [sdb] Attached SCSI disk
physmap platform flash device: 00040000 at f4000000
Found: SST 39LF020
physmap-flash.0: Found 1 x8 devices at 0x0 in 8-bit bank
number of JEDEC chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
RedBoot partition parsing not available
orion-ehci orion-ehci.0: Marvell Orion EHCI
orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
orion-ehci orion-ehci.0: irq 17, io mem 0xf1050000
orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
orion-ehci orion-ehci.1: Marvell Orion EHCI
orion-ehci orion-ehci.1: new USB bus registered, assigned bus number 2
orion-ehci orion-ehci.1: irq 12, io mem 0xf10a0000
orion-ehci orion-ehci.1: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
usbcore: registered new interface driver usblp
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
i2c /dev entries driver
rtc-rs5c372 0-0032: rs5c372a found, 24hr, driver version 0.5
rtc-rs5c372 0-0032: rtc core: registered rtc-rs5c372 as rtc0
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
oprofile: using timer interrupt.
TCP cubic registered
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
VFP support v0.3: not present
rtc-rs5c372 0-0032: setting system clock to 2008-07-09 18:09:51 UTC (1215626991)
List of all partitions:
0800  488386584 sda driver: sd
  0801    1004031 sda1
  0802    5004247 sda2
  0804          1 sda4
  0805    1004031 sda5
  0806  480480021 sda6
0810  488386584 sdb driver: sd
  0811    1004031 sdb1
  0812    5004247 sdb2
  0814          1 sdb4
  0815    1004031 sdb5
  0816  480480021 sdb6
1f00        256 mtdblock0 (driver?)
No filesystem could mount root, tried:  ext3 ext2 cramfs msdos vfat
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,2)
Rebooting in 5 seconds..

Someone with an idea, what's wrong here? The root filesystem is formatted with ext3.

prodigy7

_________________
LS2 (U-Boot + Freelink) | Kurobox (U-Boot + Deboostraped) | LS Pro Duo (Freelink)


Top
   
PostPosted: Wed Jul 09, 2008 9:27 pm 
Offline
Regular Member

Joined: Mon Nov 07, 2005 4:37 pm
Posts: 205
Location: Germany
Okay ... now I can contribute something ;-)
The previous error was my fault. I forgot, that the root partition use xfs and I'hadnt enabled the xfs filesystem. The kernel boots now completly on my linkstation pro duo:
Code:
Linux version 2.6.26-rc9-00107-gfac7962 (manuel@bigbrother) (gcc version 4.2.1 (CodeSourcery Sourcery G++ Lite 2007q3-53)) #6 PREEMPT Wed Jul 9 22:01:50 CEST 2008
CPU: Feroceon [41069260] revision 0 (ARMv5TEJ), cr=a0053177
Machine: Buffalo Linkstation Pro/Live
Clearing invalid memory bank 0KB@0xffffffff
Clearing invalid memory bank 0KB@0xffffffff
Clearing invalid memory bank 0KB@0xffffffff
Ignoring unrecognised tag 0x00000000
Ignoring unrecognised tag 0x00000000
Ignoring unrecognised tag 0x00000000
Ignoring unrecognised tag 0x41000403
Memory policy: ECC disabled, Data cache writeback
On node 0 totalpages: 16384
  DMA zone: 128 pages used for memmap
  DMA zone: 0 pages reserved
  DMA zone: 16256 pages, LIFO batch:3
  Normal zone: 0 pages used for memmap
  Movable zone: 0 pages used for memmap
CPU0: D VIVT write-back cache
CPU0: I cache: 32768 bytes, associativity 1, 32 byte lines, 1024 sets
CPU0: D cache: 32768 bytes, associativity 1, 32 byte lines, 1024 sets
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 16256
Kernel command line: console=ttyS0,115200 mem=64m root=/dev/sda2 rw initrd=0x00800040,15M panic=5 BOOTVER=1.13
PID hash table entries: 256 (order: 8, 1024 bytes)
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 64MB = 64MB total
Memory: 45688KB available (3504K code, 187K data, 128K init)
SLUB: Genslabs=12, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Calibrating delay loop... 265.42 BogoMIPS (lpj=1327104)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
net_namespace: 192 bytes
NET: Registered protocol family 16
Orion ID: MV88F5182-A2. TCLK=166666667.
SCSI subsystem initialized
libata version 3.00 loaded.
NET: Registered protocol family 2
Switched to high resolution mode on CPU 0
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
NET: Registered protocol family 1
checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
Freeing initrd memory: 15360K
NetWinder Floating Point Emulator V0.97 (double precision)
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
SGI XFS with ACLs, security attributes, no debug enabled
SGI XFS Quota Management subsystem
msgmni has been set to 119
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 3) is a 16550A
console [ttyS0] enabled
serial8250.1: ttyS1 at MMIO 0xf1012100 (irq = 4) is a 16550A
brd: module loaded
loop: module loaded
MV-643xx 10/100/1000 Ethernet Driver
net eth0: port 0 with MAC address 00:00:00:00:51:81
net eth0: scatter/gather enabled
net eth0: tx checksum offload
net eth0: napi enabled
Driver 'sd' needs updating - please use bus_type methods
sata_mv sata_mv.0: version 1.24
sata_mv sata_mv.0: slots 32 ports 2
scsi0 : sata_mv
scsi1 : sata_mv
ata1: SATA max UDMA/133 irq 29
ata2: SATA max UDMA/133 irq 29
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1.00: ATA-8: SAMSUNG HD501LJ, CR100-10, max UDMA7
ata1.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata1.00: configured for UDMA/133
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata2.00: ATA-8: SAMSUNG HD501LJ, CR100-12, max UDMA7
ata2.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata2.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access     ATA      SAMSUNG HD501LJ  CR10 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sda: sda1 sda2 sda4 < sda5 sda6 >
sd 0:0:0:0: [sda] Attached SCSI disk
scsi 1:0:0:0: Direct-Access     ATA      SAMSUNG HD501LJ  CR10 PQ: 0 ANSI: 5
sd 1:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 1:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sdb: sdb1 sdb2 sdb4 < sdb5 sdb6 >
sd 1:0:0:0: [sdb] Attached SCSI disk
physmap platform flash device: 00040000 at f4000000
CFI: Found no physmap-flash.0 device at location zero
Found: SST 39LF020
physmap-flash.0: Found 1 x8 devices at 0x0 in 8-bit bank
number of JEDEC chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
RedBoot partition parsing not available
i2c /dev entries driver
i2c-gpio: probe failed: -19
rtc-rs5c372 0-0032: rs5c372a found, 24hr, driver version 0.5
rtc-rs5c372 0-0032: rtc core: registered rtc-rs5c372 as rtc0
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
md: raid10 personality registered for level 10
md: multipath personality registered for level -4
md: faulty personality registered for level -5
device-mapper: ioctl: 4.13.0-ioctl (2007-10-18) initialised: dm-devel@redhat.com
oprofile: using timer interrupt.
TCP cubic registered
NET: Registered protocol family 17
VFP support v0.3: not present
rtc-rs5c372 0-0032: setting system clock to 2008-07-09 20:08:58 UTC (1215634138)
md: Autodetecting RAID arrays.
md: Scanned 2 and added 2 devices.
md: autorun ...
md: considering sdb6 ...
md:  adding sdb6 ...
md:  adding sda6 ...
md: created md2
md: bind<sda6>
md: bind<sdb6>
md: running: <sdb6><sda6>
raid1: raid set md2 active with 2 out of 2 mirrors
md: ... autorun DONE.
RAMDISK: Compressed image found at block 0
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
XFS mounting filesystem sda2
Ending clean XFS mount for filesystem: sda2
VFS: Mounted root (xfs filesystem).
Trying to move old root to /initrd ... okay
Freeing init memory: 128K
Adding 1004020k swap on /dev/sda5.  Priority:-1 extents:1 across:1004020k
Adding 1003896k swap on /dev/sdb5.  Priority:-2 extents:1 across:1003896k
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on md2, internal journal
EXT3-fs: mounted filesystem with ordered data mode.

Following questions/hints to the developers:
  • The configuration set "rtc0" as devicename for the clock device. This device can't be found by the hwclock command in the buffalo ramdisk and from the debian 4.0 hwclock command. Maybe "rtc" is the better kernel default value?
  • Is that normal, that the vanilla network driver returns another mac like the buffalo one? With buffalo kernel, I've a 00:16:01:41:87:xx mac, with mv643xx_eth_port a 00:00:00:00:51:81 mac. The last one doesn't look to me as an valid mac address. That's also the reason, why the network for eth1 isn't configured during bootup. This can be fixed in the udev rules...
  • The GPIO driver doesn't work. Under /proc no entries can be found which gives the typical buffalo informations or let set some configuration values. The problem is (and this can make vanilla kernels currently DANGEROUS !!!!!): The case fan doesn't run! Is that here maybe the reason?
    Code:
    i2c-gpio: probe failed: -19
    I enabled this module, think I need it because the device hasn't an micon controller
Ok - i reboot now back with an buffalo kernel because I need an running fan ;-)

Edit: I forgot - the tested kernel version was 2.6.26-rc9-00107-gfac7962

_________________
LS2 (U-Boot + Freelink) | Kurobox (U-Boot + Deboostraped) | LS Pro Duo (Freelink)


Top
   
PostPosted: Wed Jul 09, 2008 9:38 pm 
Offline
Developer

Joined: Tue Jul 24, 2007 4:43 pm
Posts: 113
Location: UK
prodigy7 wrote:
Following questions/hints to the developers:
  • The configuration set "rtc0" as devicename for the clock device. This device can't be found by the hwclock command in the buffalo ramdisk and from the debian 4.0 hwclock command. Maybe "rtc" is the better solution?

What are you using as the rootfs? If it's a debian debootstrap then you probably need to install udev.
prodigy7 wrote:
  • Is that normal, that the vanilla network driver returns another mac like the buffalo one? With buffalo kernel, I've a 00:16:01:41:87:xx mac, with mv643xx_eth_port a 00:00:00:00:51:81 mac. The last one doesn't look to me as an valid mac address. That's also the reason, why the network for eth1 isn't configured during bootup. This can be fixed in the udev rules...

  • This can be set as a u-boot variable which mv643xx_eth will use or in the network config. Any idea where the stock kernel reads this value from?
    prodigy7 wrote:
  • The GPIO driver doesn't work. Under /proc no entries can be found which gives the typical buffalo informations or let set some configuration values. The problem is (and this can make vanilla kernels currently DANGEROUS !!!!!): The case fan doesn't run!
  • Ok - i reboot now back with an buffalo kernel because I need an running fan ;-)

    The fan on the lspro (not sure about duo but I suspect it's the same) is connected to the microcontroller. If you're running something like debootstrap debian then you need to install micro_evtd. If you're still using the stock firmware with the new kernel then it probably won't work because there is no kernel-space code to handle the interrupts.

    _________________
    Byron Bradley


    Top
       
    PostPosted: Wed Jul 09, 2008 9:40 pm 
    Offline
    Developer

    Joined: Tue Jul 24, 2007 4:43 pm
    Posts: 113
    Location: UK
    prodigy7 wrote:
    The case fan doesn't run! Is that here maybe the reason?
    Code:
    i2c-gpio: probe failed: -19
    I enabled this module, think I need it because the device hasn't an micon controller


    Are you sure it doesn't have a microcontroller? If so it probably needs another mach-type registered for this machine with a setup file that will provide functions for power off, led, button, fan and temperature control.

    _________________
    Byron Bradley


    Top
       
    PostPosted: Thu Jul 10, 2008 6:04 am 
    Offline
    Regular Member

    Joined: Mon Nov 07, 2005 4:37 pm
    Posts: 205
    Location: Germany
    bbradley wrote:
    Are you sure it doesn't have a microcontroller? If so it probably needs another mach-type registered for this machine with a setup file that will provide functions for power off, led, button, fan and temperature control.

    Yes - I'm sure. Which mach-type would be the right one?

    _________________
    LS2 (U-Boot + Freelink) | Kurobox (U-Boot + Deboostraped) | LS Pro Duo (Freelink)


    Top
       
    PostPosted: Thu Jul 10, 2008 6:09 am 
    Offline
    Regular Member

    Joined: Mon Nov 07, 2005 4:37 pm
    Posts: 205
    Location: Germany
    bbradley wrote:
    What are you using as the rootfs? If it's a debian debootstrap then you probably need to install udev.

    I'm using an freelink rootfs. Maybe an symlink (the case, how I solved it quickly) would also do the job.
    bbradley wrote:
    This can be set as a u-boot variable which mv643xx_eth will use or in the network config. Any idea where the stock kernel reads this value from?
    I think, because the stockware kernel is the first one, which is normally booted on a maschine, it get automatically eth0 and when you boot then with another driver, the kernel enumerate the next "new" interfaces. Normally this can be fixed by changing eth1 in the corresponding udev rule to eth0 - but it should be important for everyone, that this needs to modify before a new kernel is booted. And the problem here is then, that the "new" mac must be known or an universal udev rule must be set
    bbradley wrote:
    The fan on the lspro (not sure about duo but I suspect it's the same) is connected to the microcontroller. If you're running something like debootstrap debian then you need to install micro_evtd. If you're still using the stock firmware with the new kernel then it probably won't work because there is no kernel-space code to handle the interrupts.

    The stuff is already installed because I take the freelink rootfs. Also it works with the stockware and an own compiled stockware kernel.

    _________________
    LS2 (U-Boot + Freelink) | Kurobox (U-Boot + Deboostraped) | LS Pro Duo (Freelink)


    Top
       
    PostPosted: Thu Jul 10, 2008 11:56 am 
    Offline
    Developer

    Joined: Tue Jul 24, 2007 4:43 pm
    Posts: 113
    Location: UK
    prodigy7 wrote:
    bbradley wrote:
    Are you sure it doesn't have a microcontroller? If so it probably needs another mach-type registered for this machine with a setup file that will provide functions for power off, led, button, fan and temperature control.

    Yes - I'm sure. Which mach-type would be the right one?


    Currently none of them, the duo isn't supported yet. Some devices have I2C fan controllers so maybe there is one of those? Any idea what IC8 is? Looks like that might be connected to the fan (http://buffalo.nas-central.org/images/6 ... _front.jpg). http://nas-central.org/index.php/Orion_ ... tion_guide has more information about supporting a new device.

    _________________
    Byron Bradley


    Top
       
    PostPosted: Thu Jul 10, 2008 12:28 pm 
    Offline
    Regular Member

    Joined: Mon Nov 07, 2005 4:37 pm
    Posts: 205
    Location: Germany
    If you'll download the duo linux sources, you'll find in the linux root an subdirectory buffalo which contains the "special" modul for gpio.

    Can I support you with any debug output?

    _________________
    LS2 (U-Boot + Freelink) | Kurobox (U-Boot + Deboostraped) | LS Pro Duo (Freelink)


    Top
       
    PostPosted: Thu Jul 10, 2008 12:51 pm 
    Offline
    Developer

    Joined: Tue Jul 24, 2007 4:43 pm
    Posts: 113
    Location: UK
    prodigy7 wrote:
    If you'll download the duo linux sources, you'll find in the linux root an subdirectory buffalo which contains the "special" modul for gpio.

    Can I support you with any debug output?


    Thanks prodigy7, I've created a new mach-type (http://www.arm.linux.org.uk/developer/m ... st&id=1831) and I'll take a look at the sources. I'm moving house tomorrow so I'm going to be slow to reply for a while.

    _________________
    Byron Bradley


    Top
       
    PostPosted: Thu Jul 10, 2008 1:12 pm 
    Offline
    Regular Member

    Joined: Mon Nov 07, 2005 4:37 pm
    Posts: 205
    Location: Germany
    bbradley wrote:
    Thanks prodigy7, I've created a new mach-type (http://www.arm.linux.org.uk/developer/m ... st&id=1831) and I'll take a look at the sources. I'm moving house tomorrow so I'm going to be slow to reply for a while.

    Okay - contact me if you need informations. I'll support the community so far as i can.

    _________________
    LS2 (U-Boot + Freelink) | Kurobox (U-Boot + Deboostraped) | LS Pro Duo (Freelink)


    Top
       
    PostPosted: Mon Aug 11, 2008 7:04 am 
    Offline
    Regular Member
    User avatar

    Joined: Tue Oct 09, 2007 9:01 am
    Posts: 117
    Martin Michlmayr posted a 2.6.27-rc2 test kernel image with initrd:

    Martin Michlmayr wrote:
    I've built some kernel snapshots for armel based on 2.6.27-rc2.
    I only briefly booted on some Orion machines, so consider these
    completely untested. Try only if you have a serial console.

    You can find the kernel packages at
    http://people.debian.org/~tbm/armel/kernel/r12030/

    --
    Martin Michlmayr
    http://www.cyrius.com/


    According to Per Andersson it boots fine on a KuroPro. Will try it out when i get home today.


    Top
       
    Display posts from previous:  Sort by  
    Post new topic  Reply to topic  [ 283 posts ]  Go to page Previous 113 14 15 16 1719 Next

    All times are UTC+01:00


    Who is online

    Users browsing this forum: No registered users and 3 guests


    You cannot post new topics in this forum
    You cannot reply to topics in this forum
    You cannot edit your posts in this forum
    You cannot delete your posts in this forum
    You cannot post attachments in this forum

    Search for:
    Powered by phpBB® Forum Software © phpBB Limited