On Wed, 23 Aug 2006, Nguyen, Hai wrote:
> I'm using g4u-2.3alpha5 and it will load to welcome screen, but when I
> type 'disks' nothing shows up.  So, this looks like it's not mounting
> the hard drive.

You're jumping to conclusions here - before you can mount a harddrive (or 
rather,  a filesystem on it, not that g4u would do that!), you have to 
detect both the drive and the controller on which the drive is, plus
maybe even the bus on which the controller is.

My guess is that the SATA controller is not found/recognized for some 
reason.


> Here is the "dmesg" output on the hard drive:
>
> Boot device: <unknown>
> Root on md0a dumps on md0b
> Root file system type: ffs
> Wpi0: could not read firmware file
> Wpi0: could not read firmware file
> Wpi0: could not read firmware file
> Wpi0: could not read firmware file
> Ubt0 at uhub0 port 1 configuration 1 interface 0
> Ubt0: Broadcom Corp HP Integrated Module, rev 2.00/1.00, addr 2


That's not the information on the harddisk. wpi(4) is about your wlan 
adapter (which requires seperate firmware to be installed, which g4u 
doesn't offer; and which it probably can't, thanks to the binary-only 
availability), ubt(4) is some bluetooth module as you can see.

What we would be looking for indeed is something like a drive which would 
most likely be something like wd0, which would be attached to some 
IDE/SATA controller (the name most likely has an 'ide' in it, even for 
SATA), plus again what bus that controller is attached to.

Here's an example for the relevant parts of my PC:

        viaide0 at pci0 dev 7 function 1
        viaide0: VIA Technologies VT82C596A (Apollo Pro) ATA66 controller
        viaide0: bus-master DMA support present
        viaide0: primary channel configured to compatibility mode
        viaide0: primary channel interrupting at irq 14
        atabus0 at viaide0 channel 0
        viaide0: secondary channel configured to compatibility mode
        viaide0: secondary channel interrupting at irq 15
        atabus1 at viaide0 channel 1
        ...
        atapibus0 at atabus0: 2 targets
        ...
        wd0 at atabus0 drive 0: <ST320413A>
        wd0: drive supports 16-sector PIO transfers, LBA addressing
        wd0: 19092 MB, 38792 cyl, 16 head, 63 sec, 512 bytes/sect x 39102336 
sectors
        wd0: 32-bit data port
        wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100)
        wd0(viaide0:0:0): using PIO mode 4, Ultra-DMA mode 4 (Ultra/66) (using 
DMA)

>From this we can see information about the drive (wd0), the controller 
(viaide0) and the bus (pci0).

My guess is that the whole PCI bus on which your controller is isn't 
found right now.


  - Hubert

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
g4u-help mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/g4u-help

Reply via email to