0.4.x VIA Kernel

3rd Party Package Requesting

0.4.x VIA Kernel

Postby dajudge » Mon Mar 03, 2014 9:16 pm

Looking for help making an 0.4.x kernel with SATA support for the VIA VT8237R series. I've tried the Triton kernels, with no luck.

Thanks
User avatar
dajudge
Newbie
 
Posts: 16
Joined: Sat Dec 14, 2002 4:17 pm

Re: 0.4.x VIA Kernel

Postby Lightning » Tue Mar 04, 2014 3:57 pm

can you use

cat /proc/pci >/devices

and post that file here. This can also be done from the command prompt in the control panel just by using

cat /proc/pci

Then copy and paste the information.
If you are afraid that you might make a mistake. The chances are high that you will never learn anything.
User avatar
Lightning
FREESCO GOD !!
 
Posts: 12079
Joined: Wed Nov 14, 2001 6:50 am
Location: Oregon, USA

Re: 0.4.x VIA Kernel

Postby dajudge » Wed Mar 05, 2014 11:51 pm

Code: Select all
[Control-Panel@Freesco] cat /proc/pci
PCI devices found:
  Bus  0, device  18, function  0:
    Ethernet controller: VIA Technologies Unknown device (rev 120).
      Vendor id=1106. Device id=3065.
      Medium devsel.  IRQ 12.  Master Capable.  Latency=32.  Min Gnt=3.Max Lat=8.
      I/O at 0xe400.
      Non-prefetchable 32 bit memory at 0xf6002000.
  Bus  0, device  17, function  0:
    ISA bridge: VIA Technologies Unknown device (rev 0).
      Vendor id=1106. Device id=3227.
      Medium devsel.  Master Capable.  No bursts. 
  Bus  0, device  16, function  4:
    USB Controller: VIA Technologies Unknown device (rev 134).
      Vendor id=1106. Device id=3104.
      Medium devsel.  IRQ 3.  Master Capable.  Latency=32. 
      Non-prefetchable 32 bit memory at 0xf6001000.
  Bus  0, device  16, function  3:
    USB Controller: VIA Technologies VT 82C586 Apollo USB (rev 129).
      Medium devsel.  IRQ 11.  Master Capable.  Latency=32. 
      I/O at 0xdc00.
  Bus  0, device  16, function  2:
    USB Controller: VIA Technologies VT 82C586 Apollo USB (rev 129).
      Medium devsel.  IRQ 11.  Master Capable.  Latency=32. 
      I/O at 0xd800.
  Bus  0, device  16, function  1:
    USB Controller: VIA Technologies VT 82C586 Apollo USB (rev 129).
      Medium devsel.  IRQ 12.  Master Capable.  Latency=32. 
      I/O at 0xd400.
  Bus  0, device  16, function  0:
    USB Controller: VIA Technologies VT 82C586 Apollo USB (rev 129).
      Medium devsel.  IRQ 12.  Master Capable.  Latency=32. 
      I/O at 0xd000.
  Bus  0, device  15, function  1:
    IDE interface: VIA Technologies VT 82C586 Apollo IDE (rev 6).
      Medium devsel.  Fast back-to-back capable.  IRQ 255.  Master Capable.  Latency=32. 
      I/O at 0xcc00.
  Bus  0, device  15, function  0:
    IDE interface: VIA Technologies Unknown device (rev 128).
      Vendor id=1106. Device id=3149.
      Medium devsel.  Fast back-to-back capable.  IRQ 11.  Master Capable.  Latency=32. 
      I/O at 0xb400.
      I/O at 0xb800.
      I/O at 0xbc00.
      I/O at 0xc000.
      I/O at 0xc400.
      I/O at 0xc800.
  Bus  0, device  13, function  0:
    Ethernet controller: VIA Technologies Unknown device (rev 141).
      Vendor id=1106. Device id=3065.
      Medium devsel.  IRQ 12.  Master Capable.  Latency=32.  Min Gnt=3.Max Lat=8.
      I/O at 0xb000.
      Non-prefetchable 32 bit memory at 0xf6000000.
  Bus  1, device   0, function  0:
    VGA compatible controller: VIA Technologies Unknown device (rev 2).
      Vendor id=1106. Device id=3118.
      Medium devsel.  IRQ 12.  Master Capable.  Latency=32.  Min Gnt=2.
      Prefetchable 32 bit memory at 0xf0000000.
      Non-prefetchable 32 bit memory at 0xf4000000.
  Bus  0, device   1, function  0:
    PCI bridge: VIA Technologies Unknown device (rev 0).
      Vendor id=1106. Device id=b198.
      Medium devsel.  Master Capable.  No bursts.  Min Gnt=14.
  Bus  0, device   0, function  4:
    Host bridge: VIA Technologies Unknown device (rev 0).
      Vendor id=1106. Device id=4259.
      Medium devsel.  Master Capable.  No bursts. 
  Bus  0, device   0, function  3:
    Host bridge: VIA Technologies Unknown device (rev 0).
      Vendor id=1106. Device id=3259.
      Medium devsel.  Master Capable.  No bursts. 
  Bus  0, device   0, function  2:
    Host bridge: VIA Technologies Unknown device (rev 0).
      Vendor id=1106. Device id=2259.
      Medium devsel.  Master Capable.  No bursts. 
  Bus  0, device   0, function  1:
    Host bridge: VIA Technologies Unknown device (rev 0).
      Vendor id=1106. Device id=1259.
      Medium devsel.  Master Capable.  No bursts. 
  Bus  0, device   0, function  0:
    Host bridge: VIA Technologies Unknown device (rev 0).
      Vendor id=1106. Device id=259.
      Medium devsel.  Master Capable.  Latency=8. 
      Prefetchable 32 bit memory at 0xe8000000.
User avatar
dajudge
Newbie
 
Posts: 16
Joined: Sat Dec 14, 2002 4:17 pm

Re: 0.4.x VIA Kernel

Postby Lightning » Thu Mar 06, 2014 8:52 pm

I have a modified kernel source that MIGHT enable your hard drive. I have no way of testing it nor am I certain it will work and it possibly could turn your hard drive into a large paper wieght. But you can download it here
http://lewys-spot.dyndns.org/test/kernel.via

Rename it to "kernel" and replace the original.

If it works you can also add the "System.map" file along with this kernel in the /boot directory once it is on a hard drive to enable more accurate system logs from the kernel.
http://lewys-spot.dyndns.org/test/kernel.via.map

Rename it to "System.map" and it is case sensitive.
If you are afraid that you might make a mistake. The chances are high that you will never learn anything.
User avatar
Lightning
FREESCO GOD !!
 
Posts: 12079
Joined: Wed Nov 14, 2001 6:50 am
Location: Oregon, USA

Re: 0.4.x VIA Kernel

Postby dajudge » Thu Mar 06, 2014 11:26 pm

Thank you, will try to give it a shot this weekend. I'm running from a compact flash card (currently on a PATA adapter), so not too worried about damage.
User avatar
dajudge
Newbie
 
Posts: 16
Joined: Sat Dec 14, 2002 4:17 pm

Re: 0.4.x VIA Kernel

Postby dajudge » Fri Mar 07, 2014 8:38 pm

No luck, get the same error I got with the Triton kernels, "boot media or drive error.. stopping...".
User avatar
dajudge
Newbie
 
Posts: 16
Joined: Sat Dec 14, 2002 4:17 pm

Re: 0.4.x VIA Kernel

Postby Lightning » Sat Mar 08, 2014 1:55 pm

I guess my question is "How are you trying this kernel". a detailed explanation would possibly help me understand. It is possible that it just plainly won't work, but I would like to know the details.
If you are afraid that you might make a mistake. The chances are high that you will never learn anything.
User avatar
Lightning
FREESCO GOD !!
 
Posts: 12079
Joined: Wed Nov 14, 2001 6:50 am
Location: Oregon, USA

Re: 0.4.x VIA Kernel

Postby dajudge » Sat Mar 08, 2014 5:16 pm

Let's see, currently running Freesco v0.4.3, using HD install to the CF card, and DOS (boots to DOS, runs the router from a batch file). Used the following to install the new kernel after logging in:

cd /boot
snarf http://<some-mirror>/<custom-kernel>
mv kernel kernel.old
mv <custom-kernel> kernel
sync; sync;
reboot

Kernel seems to work fine with the CF card on a PATA adapter, but when I switch the card to the SATA adapter, it boots to DOS fine, starts Freesco, but I get the previous error when it tries to mount the boot dev (on the Freesco startup screen).

Motherboard is a VIA EPIA-EK.
User avatar
dajudge
Newbie
 
Posts: 16
Joined: Sat Dec 14, 2002 4:17 pm

Re: 0.4.x VIA Kernel

Postby Lightning » Sun Mar 09, 2014 5:05 pm

Ok, it is probable the drive will change to the SATA connector and /dev/hda1 may not work. Using the new kernel on the PATA use the "cat /proc/pci" again and post it along with "dmesg" and copy and paste all of that information and it would be helpful if there was a device plugged into the SATA interface when booted. Not giving up quite just yet. :wink:
If you are afraid that you might make a mistake. The chances are high that you will never learn anything.
User avatar
Lightning
FREESCO GOD !!
 
Posts: 12079
Joined: Wed Nov 14, 2001 6:50 am
Location: Oregon, USA

Re: 0.4.x VIA Kernel

Postby dajudge » Mon Mar 10, 2014 7:54 pm

Here ya go..
Code: Select all
[Control-Panel@Freesco] cat /proc/pci
PCI devices found:
  Bus  0, device  18, function  0:
    Ethernet controller: VIA Technologies Unknown device (rev 120).
      Vendor id=1106. Device id=3065.
      Medium devsel.  IRQ 12.  Master Capable.  Latency=32.  Min Gnt=3.Max Lat=8.
      I/O at 0xe400.
      Non-prefetchable 32 bit memory at 0xf6002000.
  Bus  0, device  17, function  0:
    ISA bridge: VIA Technologies Unknown device (rev 0).
      Vendor id=1106. Device id=3227.
      Medium devsel.  Master Capable.  No bursts. 
  Bus  0, device  16, function  4:
    USB Controller: VIA Technologies Unknown device (rev 134).
      Vendor id=1106. Device id=3104.
      Medium devsel.  IRQ 3.  Master Capable.  Latency=32. 
      Non-prefetchable 32 bit memory at 0xf6001000.
  Bus  0, device  16, function  3:
    USB Controller: VIA Technologies VT 82C586 Apollo USB (rev 129).
      Medium devsel.  IRQ 11.  Master Capable.  Latency=32. 
      I/O at 0xdc00.
  Bus  0, device  16, function  2:
    USB Controller: VIA Technologies VT 82C586 Apollo USB (rev 129).
      Medium devsel.  IRQ 11.  Master Capable.  Latency=32. 
      I/O at 0xd800.
  Bus  0, device  16, function  1:
    USB Controller: VIA Technologies VT 82C586 Apollo USB (rev 129).
      Medium devsel.  IRQ 12.  Master Capable.  Latency=32. 
      I/O at 0xd400.
  Bus  0, device  16, function  0:
    USB Controller: VIA Technologies VT 82C586 Apollo USB (rev 129).
      Medium devsel.  IRQ 12.  Master Capable.  Latency=32. 
      I/O at 0xd000.
  Bus  0, device  15, function  1:
    IDE interface: VIA Technologies VT 82C586 Apollo IDE (rev 6).
      Medium devsel.  Fast back-to-back capable.  IRQ 255.  Master Capable.  Latency=32. 
      I/O at 0xcc00.
  Bus  0, device  15, function  0:
    IDE interface: VIA Technologies Unknown device (rev 128).
      Vendor id=1106. Device id=3149.
      Medium devsel.  Fast back-to-back capable.  IRQ 11.  Master Capable.  Latency=32. 
      I/O at 0xb400.
      I/O at 0xb800.
      I/O at 0xbc00.
      I/O at 0xc000.
      I/O at 0xc400.
      I/O at 0xc800.
  Bus  0, device  13, function  0:
    Ethernet controller: VIA Technologies Unknown device (rev 141).
      Vendor id=1106. Device id=3065.
      Medium devsel.  IRQ 12.  Master Capable.  Latency=32.  Min Gnt=3.Max Lat=8.
      I/O at 0xb000.
      Non-prefetchable 32 bit memory at 0xf6000000.
  Bus  1, device   0, function  0:
    VGA compatible controller: VIA Technologies Unknown device (rev 2).
      Vendor id=1106. Device id=3118.
      Medium devsel.  IRQ 12.  Master Capable.  Latency=32.  Min Gnt=2.
      Prefetchable 32 bit memory at 0xf0000000.
      Non-prefetchable 32 bit memory at 0xf4000000.
  Bus  0, device   1, function  0:
    PCI bridge: VIA Technologies Unknown device (rev 0).
      Vendor id=1106. Device id=b198.
      Medium devsel.  Master Capable.  No bursts.  Min Gnt=14.
  Bus  0, device   0, function  4:
    Host bridge: VIA Technologies Unknown device (rev 0).
      Vendor id=1106. Device id=4259.
      Medium devsel.  Master Capable.  No bursts. 
  Bus  0, device   0, function  3:
    Host bridge: VIA Technologies Unknown device (rev 0).
      Vendor id=1106. Device id=3259.
      Medium devsel.  Master Capable.  No bursts. 
  Bus  0, device   0, function  2:
    Host bridge: VIA Technologies Unknown device (rev 0).
      Vendor id=1106. Device id=2259.
      Medium devsel.  Master Capable.  No bursts. 
  Bus  0, device   0, function  1:
    Host bridge: VIA Technologies Unknown device (rev 0).
      Vendor id=1106. Device id=1259.
      Medium devsel.  Master Capable.  No bursts. 
  Bus  0, device   0, function  0:
    Host bridge: VIA Technologies Unknown device (rev 0).
      Vendor id=1106. Device id=259.
      Medium devsel.  Master Capable.  Latency=8. 
      Prefetchable 32 bit memory at 0xe8000000.


Code: Select all
[Control-Panel@Freesco] dmesg
Memory: sized by int13 0e801h
Console: 16 point font, 400 scans
Console: colour VGA+ 80x25, 1 virtual console (max 63)
pcibios: BIOS32 Service structure at 0x000fa440
pcibios: BIOS32 Service entry at 0xfa8c0
pcibios: PCI BIOS 2.10 entry at 0xfa910
Probing PCI hardware.
Calibrating delay loop.. ok - 532.48 BogoMIPS
Memory: 449956k/458688k available (744k kernel code, 384k reserved, 6608k data, 0k badram)
Swansea University Computer Society NET3.035 for Linux 2.0
NET3: Unix domain sockets 0.13 for Linux NET3.035.
Swansea University Computer Society TCP/IP for NET3.034
IP Protocols: IGMP, ICMP, UDP, TCP
Linux IP multicast router 0.07.
Checking 386/387 coupling... fpu using exception 16.
Checking 'hlt'... Ok.
Linux version 2.0.40 (Lewis@Official-FREESCO-kernel) #23 Thu Mar 6 17:41:31 PST 2014
Starting kswapd v 1.4.2.2
Serial driver version 4.13p1 with PCI enabled
ttyS02 at 0x03e8 (irq = 4) is a 16550A
ttyS03 at 0x02e8 (irq = 3) is a 16550A
lp1 at 0x0378, (polling)
APM BIOS version 1.2 Flags 0x07 (Driver version 1.2)
    Entry f000:964c cseg16 f000 dseg fdf5 cseg len 7400, dseg len 0
    Connection version 1.1
    AC on line, battery status unknown, battery life unknown
    battery flag 0x80, battery life unknown
Real Time Clock Driver v1.09
Ramdisk driver initialized : 16 ramdisks of 16384K size
loop: registered device at major 7
ide: VIA VT82C586B (split FIFO) UDMA Bus Mastering IDE
    Controller on PCI bus 0 function 121
    ide0: BM-DMA at 0xcc00-0xcc07
    ide1: BM-DMA at 0xcc08-0xcc0f
ide: VIA VT82C586B (split FIFO) UDMA Bus Mastering IDE
    Controller on PCI bus 0 function 120
hda: TOSHIBA THNCF1G02QG, 976MB w/2kB Cache, CHS=992/32/63
ide2: ports already in use, skipping probe
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Floppy drive(s): fd0 is 9ç, fd1 is 9ç
floppy0: no floppy controllers found
Ethernet Bridge 002 for NET3.035 (Linux 2.0)
PPP: version 2.3.11 (demand dialing)
TCP compression code copyright 1989 Regents of the University of California
PPP line discipline registered.
SLIP: version 0.8.4-NET3.019-NEWTTY (dynamic channels, max=256).
CSLIP: code copyright 1989 Regents of the University of California.
Partition check:
 hda: [PTBL] [124/255/63] hda1
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).
VFS: Disk change detected on device 03:01
 hda: hda1
hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hda: drive_cmd: error=0x04 { DriveStatusError }
VFS: Disk change detected on device 03:01
 hda: hda1
VFS: Can't find an ext2 filesystem on dev 03:01.
hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hda: drive_cmd: error=0x04 { DriveStatusError }
VFS: Disk change detected on device 03:01
 hda: hda1
hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hda: drive_cmd: error=0x04 { DriveStatusError }
VFS: Disk change detected on device 03:01
 hda: hda1
UMSDOS Beta 0.6 (compatibility level 0.4, fast msdos)
pci-scan.c:v1.12 7/30/2003  Donald Becker <becker@scyld.com> http://www.scyld.com/linux/drivers.html
3c59x.c:v0.99Zc 12/15/2003 Donald Becker, becker@scyld.com
  http://www.scyld.com/network/vortex.html
eepro100.c:v1.28a 12/05/2003 Donald Becker <becker@scyld.com>
  http://www.scyld.com/network/eepro100.html
RTL8169 Gigabit Ethernet driver 2.0f loaded
eth0: VIA VT6102 Rhine-II at 0xb000, 00:40:63:e8:71:10, IRQ 12.
eth0: MII PHY found
eth1: VIA VT6102 Rhine-II at 0xe400, 00:40:63:e8:71:0f, IRQ 12.
eth1: MII PHY found
User avatar
dajudge
Newbie
 
Posts: 16
Joined: Sat Dec 14, 2002 4:17 pm

Re: 0.4.x VIA Kernel

Postby Lightning » Mon Mar 10, 2014 9:22 pm

Unfortunately there is absolutely no mention of the SATA ports. However I have made one final change to see if it will work. Again no idea if it will work, but it is worth a try. I would still fire the machine up using the PATA port with a drive attached to the SATA port and see if the file outputs as above show anything.

The kernel name and download is the same as before.
If you are afraid that you might make a mistake. The chances are high that you will never learn anything.
User avatar
Lightning
FREESCO GOD !!
 
Posts: 12079
Joined: Wed Nov 14, 2001 6:50 am
Location: Oregon, USA

Re: 0.4.x VIA Kernel

Postby dajudge » Mon Mar 10, 2014 10:16 pm

Looks about the same, and this is using an actual SATA hdd (still booting from the CF card on PATA).

Code: Select all
[Control-Panel@Freesco] cat /proc/pci
PCI devices found:
  Bus  0, device  18, function  0:
    Ethernet controller: VIA Technologies Unknown device (rev 120).
      Vendor id=1106. Device id=3065.
      Medium devsel.  IRQ 12.  Master Capable.  Latency=32.  Min Gnt=3.Max Lat=8.
      I/O at 0xe400.
      Non-prefetchable 32 bit memory at 0xf6002000.
  Bus  0, device  17, function  0:
    ISA bridge: VIA Technologies Unknown device (rev 0).
      Vendor id=1106. Device id=3227.
      Medium devsel.  Master Capable.  No bursts. 
  Bus  0, device  16, function  4:
    USB Controller: VIA Technologies Unknown device (rev 134).
      Vendor id=1106. Device id=3104.
      Medium devsel.  IRQ 3.  Master Capable.  Latency=32. 
      Non-prefetchable 32 bit memory at 0xf6001000.
  Bus  0, device  16, function  3:
    USB Controller: VIA Technologies VT 82C586 Apollo USB (rev 129).
      Medium devsel.  IRQ 11.  Master Capable.  Latency=32. 
      I/O at 0xdc00.
  Bus  0, device  16, function  2:
    USB Controller: VIA Technologies VT 82C586 Apollo USB (rev 129).
      Medium devsel.  IRQ 11.  Master Capable.  Latency=32. 
      I/O at 0xd800.
  Bus  0, device  16, function  1:
    USB Controller: VIA Technologies VT 82C586 Apollo USB (rev 129).
      Medium devsel.  IRQ 12.  Master Capable.  Latency=32. 
      I/O at 0xd400.
  Bus  0, device  16, function  0:
    USB Controller: VIA Technologies VT 82C586 Apollo USB (rev 129).
      Medium devsel.  IRQ 12.  Master Capable.  Latency=32. 
      I/O at 0xd000.
  Bus  0, device  15, function  1:
    IDE interface: VIA Technologies VT 82C586 Apollo IDE (rev 6).
      Medium devsel.  Fast back-to-back capable.  IRQ 255.  Master Capable.  Latency=32. 
      I/O at 0xcc00.
  Bus  0, device  15, function  0:
    IDE interface: VIA Technologies Unknown device (rev 128).
      Vendor id=1106. Device id=3149.
      Medium devsel.  Fast back-to-back capable.  IRQ 11.  Master Capable.  Latency=32. 
      I/O at 0xb400.
      I/O at 0xb800.
      I/O at 0xbc00.
      I/O at 0xc000.
      I/O at 0xc400.
      I/O at 0xc800.
  Bus  0, device  13, function  0:
    Ethernet controller: VIA Technologies Unknown device (rev 141).
      Vendor id=1106. Device id=3065.
      Medium devsel.  IRQ 12.  Master Capable.  Latency=32.  Min Gnt=3.Max Lat=8.
      I/O at 0xb000.
      Non-prefetchable 32 bit memory at 0xf6000000.
  Bus  1, device   0, function  0:
    VGA compatible controller: VIA Technologies Unknown device (rev 2).
      Vendor id=1106. Device id=3118.
      Medium devsel.  IRQ 12.  Master Capable.  Latency=32.  Min Gnt=2.
      Prefetchable 32 bit memory at 0xf0000000.
      Non-prefetchable 32 bit memory at 0xf4000000.
  Bus  0, device   1, function  0:
    PCI bridge: VIA Technologies Unknown device (rev 0).
      Vendor id=1106. Device id=b198.
      Medium devsel.  Master Capable.  No bursts.  Min Gnt=14.
  Bus  0, device   0, function  4:
    Host bridge: VIA Technologies Unknown device (rev 0).
      Vendor id=1106. Device id=4259.
      Medium devsel.  Master Capable.  No bursts. 
  Bus  0, device   0, function  3:
    Host bridge: VIA Technologies Unknown device (rev 0).
      Vendor id=1106. Device id=3259.
      Medium devsel.  Master Capable.  No bursts. 
  Bus  0, device   0, function  2:
    Host bridge: VIA Technologies Unknown device (rev 0).
      Vendor id=1106. Device id=2259.
      Medium devsel.  Master Capable.  No bursts. 
  Bus  0, device   0, function  1:
    Host bridge: VIA Technologies Unknown device (rev 0).
      Vendor id=1106. Device id=1259.
      Medium devsel.  Master Capable.  No bursts. 
  Bus  0, device   0, function  0:
    Host bridge: VIA Technologies Unknown device (rev 0).
      Vendor id=1106. Device id=259.
      Medium devsel.  Master Capable.  Latency=8. 
      Prefetchable 32 bit memory at 0xe8000000.


Code: Select all
[Control-Panel@Freesco] dmesg
Memory: sized by int13 0e801h
Console: 16 point font, 400 scans
Console: colour VGA+ 80x25, 1 virtual console (max 63)
pcibios: BIOS32 Service structure at 0x000fa440
pcibios: BIOS32 Service entry at 0xfa8c0
pcibios: PCI BIOS 2.10 entry at 0xfa910
Probing PCI hardware.
Calibrating delay loop.. ok - 532.48 BogoMIPS
Memory: 449956k/458688k available (744k kernel code, 384k reserved, 6608k data, 0k badram)
Swansea University Computer Society NET3.035 for Linux 2.0
NET3: Unix domain sockets 0.13 for Linux NET3.035.
Swansea University Computer Society TCP/IP for NET3.034
IP Protocols: IGMP, ICMP, UDP, TCP
Linux IP multicast router 0.07.
Checking 386/387 coupling... fpu using exception 16.
Checking 'hlt'... Ok.
Linux version 2.0.40 (Lewis@Official-FREESCO-kernel) #24 Mon Mar 10 18:42:14 PST 2014
Starting kswapd v 1.4.2.2
Serial driver version 4.13p1 with PCI enabled
ttyS02 at 0x03e8 (irq = 4) is a 16550A
ttyS03 at 0x02e8 (irq = 3) is a 16550A
lp1 at 0x0378, (polling)
APM BIOS version 1.2 Flags 0x07 (Driver version 1.2)
    Entry f000:964c cseg16 f000 dseg fdf5 cseg len 73e0, dseg len 0
    Connection version 1.1
    AC on line, battery status unknown, battery life unknown
    battery flag 0x80, battery life unknown
Real Time Clock Driver v1.09
Ramdisk driver initialized : 16 ramdisks of 16384K size
loop: registered device at major 7
ide: VIA VT82C586B (split FIFO) UDMA Bus Mastering IDE
    Controller on PCI bus 0 function 121
    ide0: BM-DMA at 0xcc00-0xcc07
ide: VIA VT82C586B (split FIFO) UDMA Bus Mastering IDE
    Controller on PCI bus 0 function 121
hda: TOSHIBA THNCF1G02QG, 976MB w/2kB Cache, CHS=992/32/63
ide2: ports already in use, skipping probe
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Floppy drive(s): fd0 is 9ç, fd1 is 9ç
floppy0: no floppy controllers found
Ethernet Bridge 002 for NET3.035 (Linux 2.0)
PPP: version 2.3.11 (demand dialing)
TCP compression code copyright 1989 Regents of the University of California
PPP line discipline registered.
SLIP: version 0.8.4-NET3.019-NEWTTY (dynamic channels, max=256).
CSLIP: code copyright 1989 Regents of the University of California.
Partition check:
 hda: [PTBL] [124/255/63] hda1
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).
VFS: Disk change detected on device 03:01
 hda: hda1
hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hda: drive_cmd: error=0x04 { DriveStatusError }
VFS: Disk change detected on device 03:01
 hda: hda1
VFS: Can't find an ext2 filesystem on dev 03:01.
hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hda: drive_cmd: error=0x04 { DriveStatusError }
VFS: Disk change detected on device 03:01
 hda: hda1
hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hda: drive_cmd: error=0x04 { DriveStatusError }
VFS: Disk change detected on device 03:01
 hda: hda1
UMSDOS Beta 0.6 (compatibility level 0.4, fast msdos)
pci-scan.c:v1.12 7/30/2003  Donald Becker <becker@scyld.com> http://www.scyld.com/linux/drivers.html
3c59x.c:v0.99Zc 12/15/2003 Donald Becker, becker@scyld.com
  http://www.scyld.com/network/vortex.html
eepro100.c:v1.28a 12/05/2003 Donald Becker <becker@scyld.com>
  http://www.scyld.com/network/eepro100.html
RTL8169 Gigabit Ethernet driver 2.0f loaded
eth0: VIA VT6102 Rhine-II at 0xb000, 00:40:63:e8:71:10, IRQ 12.
eth0: MII PHY found
eth1: VIA VT6102 Rhine-II at 0xe400, 00:40:63:e8:71:0f, IRQ 12.
eth1: MII PHY found
IP fw-in rej eth0 TCP 192.81.1.86:1353 67.189.55.60:80 L=52 S=0x20 I=9364 F=0x4000 T=119
IP fw-in rej eth0 UDP 192.81.1.86:62080 67.189.55.60:80 L=47 S=0x20 I=9367 F=0x0000 T=119
IP fw-in rej eth0 TCP 192.81.1.86:1353 67.189.55.60:80 L=52 S=0x20 I=9370 F=0x4000 T=119
IP fw-in rej eth0 TCP 192.81.1.86:1353 67.189.55.60:80 L=52 S=0x20 I=9382 F=0x4000 T=119
User avatar
dajudge
Newbie
 
Posts: 16
Joined: Sat Dec 14, 2002 4:17 pm

Re: 0.4.x VIA Kernel

Postby Lightning » Tue Mar 11, 2014 9:59 am

Hmmmmmm bummer, I am not seeing any signs of the SATA controller. So unfortunately without any information on the device there isn't much chance of initializing it, sorry. :(
If you are afraid that you might make a mistake. The chances are high that you will never learn anything.
User avatar
Lightning
FREESCO GOD !!
 
Posts: 12079
Joined: Wed Nov 14, 2001 6:50 am
Location: Oregon, USA

Re: 0.4.x VIA Kernel

Postby dajudge » Tue Mar 11, 2014 9:28 pm

Oh well, I thank you for taking some time out to help :)
Much appreciated.
User avatar
dajudge
Newbie
 
Posts: 16
Joined: Sat Dec 14, 2002 4:17 pm

Re: 0.4.x VIA Kernel

Postby dajudge » Tue Mar 11, 2014 10:27 pm

A little hunting on Via's website, I did manage to find some source code, though it appears to be for 2.1.0 kernel, not sure if it's possible/worth the time to try to compile it on 2.0.38-2.0.40.. Not sure if this is just for adding Raid support though. If you're interested.

via_raid_linux_v100_20040412.zip @ http://download.viatech.com/DownloadDriverSvl?driver_id=94
User avatar
dajudge
Newbie
 
Posts: 16
Joined: Sat Dec 14, 2002 4:17 pm

Next

Return to 3rd Party Package Requesting

Who is online

Users browsing this forum: No registered users and 3 guests

cron