vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| I've got a new Dell 420SC here, and a 3.6 CD. Trying to get them married, with no luck. The CD boots, the kernel probes all the devices and finds them. But as soon as it tries to read the disk label from the Maxtor SATA disk, it hangs. Any bright ideas? I'm running the built-in diagnostics; so far, no complaints. My understanding was that the SATA interface looked "just" like another IDE device? Thanks, chris |
| |||
| Christopher A. Kantarjiev wrote: > I've got a new Dell 420SC here, and a 3.6 CD. Trying to get them > married, with no luck. The CD boots, the kernel probes all the devices > and finds them. But as soon as it tries to read the disk label from the > Maxtor SATA disk, it hangs. > > Any bright ideas? I'm running the built-in diagnostics; so far, no > complaints. My understanding was that the SATA interface looked "just" > like another IDE device? > > Thanks, > chris Oh. I see. SATA support is perhaps not fully there in the 3.6 CD. The probe says pciide2 at pci0 dev 31 function 2 vendor "Intel", unknown product 0x2652 rev 0x3: DMA (unsupported), channel 0 configured to native-PCI, channel 1 configured to native-PCI I guess the "unsupported" should have been a clue. Is this product ID the elusive ICH6R, that is only supported post-3.6? |
| |||
| Oh, yippee. The Broadcom ethernet chip isn't supported in the CD image, either, but seems to be in -current. So plugging the PATA drive into this system didn't do me any good. Am I likely to be able to build a -current on a 3.4 system (which is all I've got handy)? Disk space shouldn't be a problem. Sigh. Thanks, chris |
| ||||
| Sorry for the very serial nature of this - I've been digging on my own while casting bottles into the sea. I wrote a CD with the latest snapshot and booted successfully. The SATA drives are now working, and the Broadcom 5751 is recognized ... as a 5750? That doesn't seem right, and more concerning is that after the kernel probe, the link light is turned off. Perhaps a bug? |
| Thread Tools | |
| Display Modes | |
| |