hii all
about cf booting
for automatic booting i dong file it's name
autoexec.bat
& put in it the file u want to boot (name.exe)
thnx
fabianmejia <> wrote: After some searching on the internet and this group, I found a similar situation: http://tech.groups.yahoo.com/group/ts-7000/message/1174 Andrew mention formatting with -O none option. And ... this worked! This
is the option description: -O feature[,... ]
Create filesystem with given features (filesystem options).
Filesystems that may need to be mounted on pre-2.2 Linux or other
kernels should be created with -O none (or -r 0 for Linux 1.2) which
will disable these features, even if mke2fs is run on a system which
can support them.
I think it has to be with the kernel version I am using.
I am a newbie so, can somebody tellme why Do I have to do this?
according to the documentation (TS Arm Developers manual, page 5)
when the system boots up, a "linux kernel" is loaded from flash (is
this kernel than the kernel in the CF?) so this means that the "flash
kernel" in the memory flash is really old?
Finally, I just have to add that, although the system is running
properly, I still get this error:
> hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete
Error }
> hda: task_no_data_intr: error=0x04 { DriveStatusError }
If anyone knows how to get rid of this I will really appreciate that.
--- In .com, "fabianmejia" <fabianmejia@...> wrote:
>
> It's me again.
> I posted some time ago with the same issue.
> I thought the CF was Damaged, so yesterday I bought a new one.
>
> Unfortunately I still have the following with the new CF:
>
> ----------------------------------------------------------
> hda: SanDisk SDCFB-1024, CFA DISK drive
> ide0 at 0x8d000000-0x8d000007,0x88400006 on irq 32
> hda: attached ide-disk driver.
> hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete
Error }
> hda: task_no_data_intr: error=0x04 { DriveStatusError }
> hda: 2001888 sectors (1025 MB)
w/1KiB Cache, CHS=1986/16/63
> Partition check:
> /dev/ide/host0/bus0/target0/lun0: p1
> ----------------------------------------------------------
>
> As this error happens, the TS7200 boots from the TS-Linux:
>
>
> ----------------------------------------------------------
> Technologic Systems TS-LINUX/arm 7.0
> ts7200 login: root
> login[78]: root login on `ttyAM0'
> ----------------------------------------------------------
>
> So, I started again, partition the disk from Ubuntu (also setting
it
> as boot), formatted it with mkfs.ext2, an installed the Debian.
>
> Again, the system shows the same error.
>
> Well, One thing I noticed is that I can mount the CF after I loggin
> into the TS-Linux:
>
>
----------------------------------------------------------
> $ mount /dev/ide/host0/bus0/target0/lun0/part1 /mnt/cf/
> /dev/ide/host0/bus0/target0/lun0: p1
> /dev/ide/host0/bus0/target0/lun0: p1
> $ cd /mnt/cf
> ----------------------------------------------------------
>
> So, I suppose that the CF is ok, because I can see the whole Debian
> files inside of it. Moreover, I can upload files from FTP to the CF.
>
> Is it possible that this message is generated for some reason when
> partitioning and formatting under Ubuntu? What Kernel version are
you
> using?
> (The following queries show TS and Ubuntu version)
> ----------------------------------------------------------
> TS:
> $ uname -r
> 2.4.26-ts11
>
>
Ubuntu:
> laptop:/# uname -r
> 2.6.17-10-generic
> ----------------------------------------------------------
>
> Maybe is it useful for you the following:
>
> ----------------------------------------------------------
> $ hdparm -i /dev/ide/host0/bus0/target0/lun0/disc
> /dev/ide/host0/bus0/target0/lun0: p1
>
> /dev/ide/host0/bus0/target0/lun0/disc:
>
> Model=SanDisk SDCFB-1024, FwRev=HDX 4.03, SerialNo=014209J2906A3817
> Config={ HardSect NotMFM Removeable DTR>10Mbs nonMagnetic }
> RawCHS=1986/16/63, TrkSize=0, SectSize=576, ECCbytes=4
> BuffType=DualPort, BuffSize=1kB, MaxMultSect=4, MultSect=4
> CurCHS=1986/16/63, CurSects=2001888, LBA=yes, LBAsects=2001888
> IORDY=no, tPIO={min:120,w/IORDY:120},
tDMA={min:120,rec:120}
> PIO modes: pio0 pio1 pio2 pio3 pio4
> DMA modes: mdma0 mdma1 mdma2
> AdvancedPM=no
> Drive conforms to: device does not report version: 4
>
> * signifies the current active mode
> ----------------------------------------------------------
>
> I could not sleep well thinking about what the hell is going on
with
> this system (I don't have access to any other SBC).
>
> Is there anyway to check if the CF is damaged? (I don't think so as
I
> bought that one yesterday)
>
> Is it possible that the booting files are damaged? Where are those
> files located?
>
> Do I have to create the hda Node under the dev folder?
>
> I've read some pages related to this error and they mention
something
> with the DMA, is it possible?
>
>
Thanks for all the help you can provide.
>
Moody friends. Drama queens. Your life? Nope! - their life, your story.
Play Sims Stories at Yahoo! Games.
__._,_.___
![]()
SPONSORED LINKS
__,_._,___
|