Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

New Computer

11 views
Skip to first unread message

klee12

unread,
Jul 15, 2009, 2:45:43 AM7/15/09
to
Hello

My computer, running Slackware 10.x, died recently and I had a new one
made for me. It has an Intel DP43TF motherboard and a big SATA drive.
My old computer had just IDE drives. The new computer has Ubuntu on
it.

I installed my 2 old IDE drives on the new computer and tried to
access them from Ubuntu. I was unable to. I tried to su into root, but
was unable to. I reinstalled Ubuntu, and tried to give my login name
as root, but it the installation CD did not allow that.

OK, lets see if I could boot up on my old IDEs. I rebooted the
computer and told the BIOS to boot up on one of my IDEs. It booted up,
but I couldn't find my SATA hard disk, the network and the CDROM did
not work. This should be expected because the CDROM is SATA and I have
different network chips now than before. I was able to save some
files that had not been backed. up.

OK, I suppose I could boot up on my official Slackware 12.1 CDs and
try install Slackware. However I thought I might check with the
experts about what to expect. I expect that once the installation disk
boots, I'll be able to partition the SATA drive. The questions I have
are:

1. After I partition the SATA, how will I access them; i.e. /dev/
sdaX ?.

2. Will the partitions on the old IDE drives be accessed as /dev/hdaX?

3. Ubuntu uses GRUB and Slackware uses LILO. I had problems dual
booting using GRUB and LILO in the past. Is it easy to dual boot into
Slackware and Ubuntu using LILO? This is not critical.

Thanks in advance for any help

klee12

Chris Elvidge

unread,
Jul 15, 2009, 3:39:37 AM7/15/09
to
klee12 wrote:
> Hello
>
> My computer, running Slackware 10.x, died recently and I had a new one
> made for me. It has an Intel DP43TF motherboard and a big SATA drive.
> My old computer had just IDE drives. The new computer has Ubuntu on
> it.
>
> I installed my 2 old IDE drives on the new computer and tried to
> access them from Ubuntu. I was unable to. I tried to su into root, but

Ubuntu labels all drives as sd? afair

> was unable to. I reinstalled Ubuntu, and tried to give my login name
> as root, but it the installation CD did not allow that.

root is a built-in username. Use sudo passwd root to enable root


>
> OK, lets see if I could boot up on my old IDEs. I rebooted the
> computer and told the BIOS to boot up on one of my IDEs. It booted up,
> but I couldn't find my SATA hard disk, the network and the CDROM did
> not work. This should be expected because the CDROM is SATA and I have
> different network chips now than before. I was able to save some
> files that had not been backed. up.
>
> OK, I suppose I could boot up on my official Slackware 12.1 CDs and
> try install Slackware. However I thought I might check with the
> experts about what to expect. I expect that once the installation disk
> boots, I'll be able to partition the SATA drive. The questions I have
> are:
>
> 1. After I partition the SATA, how will I access them; i.e. /dev/
> sdaX ?.

sd?X

>
> 2. Will the partitions on the old IDE drives be accessed as /dev/hdaX?

see above

>
> 3. Ubuntu uses GRUB and Slackware uses LILO. I had problems dual
> booting using GRUB and LILO in the past. Is it easy to dual boot into
> Slackware and Ubuntu using LILO? This is not critical.

don't install lilo on the primary MBR

>
> Thanks in advance for any help
>
> klee12

HIH
CE

Mike Jones

unread,
Jul 15, 2009, 6:40:15 AM7/15/09
to
Responding to Chris Elvidge:


[...]


>> 3. Ubuntu uses GRUB and Slackware uses LILO. I had problems dual
>> booting using GRUB and LILO in the past. Is it easy to dual boot into
>> Slackware and Ubuntu using LILO? This is not critical.
>
> don't install lilo on the primary MBR


Not a problem, if you read this first...

http://www.troubleshooters.com/linux/lilo.htm

Why this info isn't in your face when you install, is a mystery.

--
*===( http://www.400monkeys.com/God/
*===( http://principiadiscordia.com/
*===( http://www.slackware.com/

klee12

unread,
Jul 16, 2009, 12:54:25 AM7/16/09
to
Thanks to all who replied.

I poked around and found a software package for Ubuntu to partition
the SATA drive. After doing that I slipped in the Slackware
installation CD and the BIOS booted up the CD and I found myself in
Slackware. I issued the command "ls /dev/s* " and did not find the
SATA drives. I tried to mount the installation CD so I could install
programs from it, but was unable to do so. IIRC, previously I would
issue the command
"mount -t iso9660 /dev/hdc /mnt" to mount the CDs. I should have not
been surprised since I now have an SATA CD reader.

I looked in "The Official Guide to Slackwqre Linux, 2nd edition" and
couldn't find anything reference to SATA drives. I even went to
Slacware site, downloaded the text of that book in PDF format and
searched for SATA. Couldn't find anything.

So, how does one, from the installation CD, mount the CD? How can one
specify the SATA partition to install Linux?

klee12

PS thanks for the tip on using sudo to issue root commands. In regard
to GRUB, I'll worry about that later ... I have built a dual (even
triple) boot system, but IIRC GRUB gave me problems which I never
resolved to my satisfaction. It might have involved passing parameters.

Helmut Hullen

unread,
Jul 16, 2009, 2:23:00 AM7/16/09
to
Hallo, klee12,

Du meintest am 14.07.09:

> OK, lets see if I could boot up on my old IDEs. I rebooted the
> computer and told the BIOS to boot up on one of my IDEs. It booted
> up, but I couldn't find my SATA hard disk, the network and the CDROM
> did not work.

Take the Slackware installation CD, boot the machine from CD.
Go to a console (maybe "alt f2") and type

fdisk -l

You should see all your harddisks.
You don't need to mount the CD - the machine is running from it.

Viele Gruesse
Helmut

"Ubuntu" - an African word, meaning "Slackware is too hard for me".

klee12

unread,
Jul 16, 2009, 4:04:45 PM7/16/09
to

Hello Gruesse

Thanks for your reply. I did as you suggested, and fdisk returned
information about the two IDE drives, but nothing about the stuff on
the SATA (on Ubuntu I got information on all three drives). I went
to /var/log and issued

grep SATA messages

and I copied the following lines of output

User. notice (none) Adaptec aic94xx SAS/SATA driver vesion 1.03
loaded

user.info kernel: Rocket RAID 3xxx SATA controller drive v1.2
070630


In Ubuntu when I greped messages in /var/log/message (or something
like that) I got more lines involving SATA. Last night I downloaded
and burned a Debian CD installation disk. That installation worked. I
much prefer Slackware but I may have to set up a primitive Debian
until I get Slackware working.

Thanks for your suggestions

klee12

Keith Keller

unread,
Jul 16, 2009, 4:51:21 PM7/16/09
to
On 2009-07-16, klee12 <kle...@alum.mit.edu> wrote:
> Thanks for your reply. I did as you suggested, and fdisk returned
> information about the two IDE drives, but nothing about the stuff on
> the SATA (on Ubuntu I got information on all three drives). I went
> to /var/log and issued
>
> grep SATA messages
>
> and I copied the following lines of output
>
> User. notice (none) Adaptec aic94xx SAS/SATA driver vesion 1.03
> loaded

This device, at least, looks like it might be a module in the stock
Slackware kernel. After booting the install CD, try

modprobe aic94xx

then see if you see the disks on that controller.

> user.info kernel: Rocket RAID 3xxx SATA controller drive v1.2
> 070630

I don't know what this controller could be. You might try an lsmod on
your Ubuntu install, and see if any of the module names look like they
could be for that controller, then modprobe it after booting the
Slackware CD. (The installer won't automatically load modules for
hardware, so you need to do that before running setup.)

--keith

--
kkeller...@wombat.san-francisco.ca.us
(try just my userid to email me)
AOLSFAQ=http://www.therockgarden.ca/aolsfaq.txt
see X- headers for PGP signature information

klee12

unread,
Jul 16, 2009, 6:52:54 PM7/16/09
to
On Jul 16, 1:51 pm, Keith Keller <kkeller-use...@wombat.san-

francisco.ca.us> wrote:
> On 2009-07-16, klee12 <kle...@alum.mit.edu> wrote:
>
>
> >     grep SATA messages
>
> > and I copied  the following lines  of output
>
> >     User. notice (none) Adaptec aic94xx SAS/SATA driver vesion 1.03
> > loaded
>
> This device, at least, looks like it might be a module in the stock
> Slackware kernel.  After booting the install CD, try
>
> modprobe aic94xx
>
> then see if you see the disks on that controller.
>

I did that and couldn't still couldn't see the SATA drive.


> I don't know what this controller could be.  You might try an lsmod on
> your Ubuntu install, and see if any of the module names look like they
> could be for that controller, then modprobe it after booting the
> Slackware CD.  (The installer won't automatically load modules for
> hardware, so you need to do that before running setup.)

I did that also, and it didn't seem to help. So I went to /var/log and
did "grep SATA dmesg > z" and it gave me


[ 17.366282] ata1: SATA max UDMA/133 cmd 0xf1b0 ctl 0xf1a0 bmdma
0xf170 irq 19
[ 17.366286] ata2: SATA max UDMA/133 cmd 0xf190 ctl 0xf180 bmdma
0xf178 irq 19
[ 18.160063] ata1.00: SATA link up 1.5 Gbps (SStatus 113 SControl
300)
[ 18.160077] ata1.01: SATA link down (SStatus 0 SControl 300)
[ 18.980063] ata2.00: SATA link up 3.0 Gbps (SStatus 123 SControl
300)
[ 18.980077] ata2.01: SATA link down (SStatus 0 SControl 300)
[ 19.145076] ata3: SATA max UDMA/133 cmd 0xf150 ctl 0xf140 bmdma
0xf110 irq 19
[ 19.145079] ata4: SATA max UDMA/133 cmd 0xf130 ctl 0xf120 bmdma
0xf118 irq 19
[ 19.474541] ata3: SATA link down (SStatus 0 SControl 300)
[ 19.802552] ata4: SATA link down (SStatus 0 SControl 300)

I don't know what that ata1 and ata2 are, but I have a feeling that's
what's missing.

I appreciate your help

klee12

klee12

unread,
Jul 16, 2009, 8:25:45 PM7/16/09
to
On thinking about this problem more, I wondered what Debian did. Once
more I did grep SATA dmesg in /var/log directory under Debian and got


21.752726] ata1: SATA max UDMA/133 cmd 0xf1b0 ctl 0xf1a0 bmdma
0xf170 irq 19
[ 21.752726] ata2: SATA max UDMA/133 cmd 0xf190 ctl 0xf180 bmdma
0xf178 irq 19
[ 22.316315] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 22.840770] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 22.974987] ata3: SATA max UDMA/133 cmd 0xf150 ctl 0xf140 bmdma
0xf110 irq 19
[ 22.974987] ata4: SATA max UDMA/133 cmd 0xf130 ctl 0xf120 bmdma
0xf118 irq 19
[ 23.343946] ata3: SATA link down (SStatus 0 SControl 300)
[ 23.716296] ata4: SATA link down (SStatus 0 SControl 300)

which seems to be pretty much what Ubuntu did.

Then I did, under Debian, lsmod and got

Module Size Used by
ext2 54504 1
sbp2 18572 0
loop 12748 0
snd_hda_intel 325688 0
snd_pcm 62596 1 snd_hda_intel
snd_timer 17800 1 snd_pcm
snd 45604 3 snd_hda_intel,snd_pcm,snd_timer
serio_raw 4740 0
soundcore 6368 1 snd
intel_agp 22556 0
pcspkr 2432 0
i2c_i801 7920 0
psmouse 32336 0
agpgart 28776 1 intel_agp
snd_page_alloc 7816 2 snd_hda_intel,snd_pcm
i2c_core 19828 1 i2c_i801
button 6096 0
evdev 8000 0
ext3 105512 1
jbd 39444 1 ext3
mbcache 7108 2 ext2,ext3
sg 26964 0
ide_disk 10496 5
sd_mod 22200 3
sr_mod 13316 0
cdrom 30176 1 sr_mod
usb_storage 77024 0
usbhid 35904 0
hid 33184 1 usbhid
ff_memless 4392 1 usbhid
ide_pci_generic 3908 0 [permanent]
jmicron 2208 0 [permanent]
ide_core 96136 3 ide_disk,ide_pci_generic,jmicron
ata_piix 14180 2
ohci1394 24944 0
ieee1394 75800 2 sbp2,ohci1394
ata_generic 4676 0
libata 140416 2 ata_piix,ata_generic
scsi_mod 129324 6
sbp2,sg,sd_mod,sr_mod,usb_storage,libata
uhci_hcd 18672 0
ehci_hcd 28396 0
dock 8304 1 libata
usbcore 118224 5 usb_storage,usbhid,uhci_hcd,ehci_hcd
e1000e 84612 0
thermal 15228 0
processor 32544 1 thermal
fan 4164 0
thermal_sys 10856 3 thermal,processor,fan

Under Ubunto lsmod gives

Module Size Used by
isofs 39844 1
udf 87716 0
crc_itu_t 10112 1 udf
binfmt_misc 16776 1
ppdev 15620 0
bridge 56340 0
stp 10500 1 bridge
bnep 20224 2
video 25360 0
output 11008 1 video
input_polldev 11912 0
lp 17156 0
parport 42220 2 ppdev,lp
snd_hda_intel 434100 3
psmouse 61972 0
pcspkr 10496 0
iTCO_wdt 19108 0
iTCO_vendor_support 11652 1 iTCO_wdt
serio_raw 13316 0
snd_pcm_oss 46336 0
snd_mixer_oss 22656 1 snd_pcm_oss
snd_pcm 82948 2 snd_hda_intel,snd_pcm_oss
snd_seq_dummy 10756 0
snd_seq_oss 37760 0
snd_seq_midi 14336 0
snd_rawmidi 29696 1 snd_seq_midi
snd_seq_midi_event 15104 2 snd_seq_oss,snd_seq_midi
snd_seq 56880 6
snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
snd_timer 29704 2 snd_pcm,snd_seq
snd_seq_device 14988 5
snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
intel_agp 34108 0
snd 62628 15
snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
soundcore 15200 1 snd
snd_page_alloc 16904 2 snd_hda_intel,snd_pcm
agpgart 42696 1 intel_agp
usb_storage 99520 0
usbhid 42336 0
ohci1394 38576 0
ieee1394 94660 1 ohci1394
e1000e 121136 0
fbcon 46112 0
tileblit 10752 1 fbcon
font 16384 1 fbcon
bitblit 13824 1 fbcon
softcursor 9984 1 bitblit
~


The modules are different; I guessed that the ata modules were
involved with SATA but Ubuntu doesn't seem to have them loaded.
Perhaps Ubuntu compiled them into the kernel. I went into

/usr/src/linux-headers-2.6.28-11/drivers/ata

and in that directory is a Makefile. I did a grep SATA on the makefile
and got


bj-$(CONFIG_SATA_AHCI) += ahci.o
obj-$(CONFIG_SATA_SVW) += sata_svw.o
obj-$(CONFIG_SATA_PROMISE) += sata_promise.o
obj-$(CONFIG_SATA_QSTOR) += sata_qstor.o
obj-$(CONFIG_SATA_SIL) += sata_sil.o
obj-$(CONFIG_SATA_SIL24) += sata_sil24.o
obj-$(CONFIG_SATA_VIA) += sata_via.o
obj-$(CONFIG_SATA_VITESSE) += sata_vsc.o
obj-$(CONFIG_SATA_SIS) += sata_sis.o
obj-$(CONFIG_SATA_SX4) += sata_sx4.o
obj-$(CONFIG_SATA_NV) += sata_nv.o
obj-$(CONFIG_SATA_ULI) += sata_uli.o
obj-$(CONFIG_SATA_MV) += sata_mv.o
obj-$(CONFIG_SATA_INIC162X) += sata_inic162x.o
obj-$(CONFIG_SATA_FSL) += sata_fsl.o
libata-$(CONFIG_SATA_PMP) += libata-pmp.o
~
~
I
I'm a little over my head in all this, but I get the feeling I didn't
do anything wrong ... the ata stuff may have been left out of the
Slackware kernel I'm usinig. I'm going to have to sleep on this.

klee12

Helmut Hullen

unread,
Jul 17, 2009, 3:12:00 AM7/17/09
to
Hallo, klee12,

Du meintest am 16.07.09:

> I did that also, and it didn't seem to help. So I went to /var/log
> and did "grep SATA dmesg > z" and it gave me


> [ 17.366282] ata1: SATA max UDMA/133 cmd 0xf1b0 ctl 0xf1a0 bmdma
> 0xf170 irq 19
> [ 17.366286] ata2: SATA max UDMA/133 cmd 0xf190 ctl 0xf180 bmdma
> 0xf178 irq 19
> [ 18.160063] ata1.00: SATA link up 1.5 Gbps (SStatus 113 SControl
> 300)
> [ 18.160077] ata1.01: SATA link down (SStatus 0 SControl 300)
> [ 18.980063] ata2.00: SATA link up 3.0 Gbps (SStatus 123 SControl
> 300)
> [ 18.980077] ata2.01: SATA link down (SStatus 0 SControl 300)
> [ 19.145076] ata3: SATA max UDMA/133 cmd 0xf150 ctl 0xf140 bmdma
> 0xf110 irq 19
> [ 19.145079] ata4: SATA max UDMA/133 cmd 0xf130 ctl 0xf120 bmdma
> 0xf118 irq 19
> [ 19.474541] ata3: SATA link down (SStatus 0 SControl 300)
> [ 19.802552] ata4: SATA link down (SStatus 0 SControl 300)

Looks like 4 slots for S-ATA data cables. Slot 1 may be up.

What tells
lspci
lspci -n

(both commands)
they should tell the name of the S-ATA controller and its vendor ID.
That's a (not quite simple) way to find the appropriate module.

Henrik Carlqvist

unread,
Jul 17, 2009, 6:26:20 AM7/17/09
to
klee12 <kle...@alum.mit.edu> wrote:
> previously I would issue the command
> "mount -t iso9660 /dev/hdc /mnt" to mount the CDs. I should have not
> been surprised since I now have an SATA CD reader.

There is a very nice command that could be useful:

dmesg

That command will show you the kernel bootup messages. Among those
messages you will see the brand of your CD reader and which deveice name
it got. You will also see which harddisks you have connected and which
partitions they have. Dmesg will probably also tell you which network
adapter you have and which driver it uses, but only if your installation
successfully has loaded a driver for your network card. If your old
Slackware installation is unable to find your network card but ubuntu sees
it you might be able to use dmesg in ubuntu to find out which driver you
should use in Slackware. However, as your Slackware 10.x is rather old
ther is a risk that it doesn't include a NIC driver for your new hardware.
If the driver were included hotplug would probably have loaded it
automagically. With Slackware 12.x udev will probably load the right
driver for you.

regards Henrik
--
The address in the header is only to prevent spam. My real address is:
hc3(at)poolhem.se Examples of addresses which go to spammers:
root@localhost postmaster@localhost

klee12

unread,
Jul 18, 2009, 12:15:52 PM7/18/09
to
Thanks to all who replied.

I did lspci and lspci -n but didn't find anything interesting.

I did a grep SATA on /var/log/messages and reported results on the
fourth message on this thread. I thing that is the same thing as
dmesg.

I got the inspiration to look in /proc/scsi/scsi following:

After booting up on my old Slackware 10.1 distribution I got:

Attached devices:
Host: scsi2 Channel: 00 Id: 00 Lun: 00
Vendor: SanDisk Model: U3 Titanium Rev: 2.18
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi3 Channel: 00 Id: 00 Lun: 00
Vendor: Generic Model: Flash HS-CF Rev: 4.44
Type: Direct-Access ANSI SCSI revision: 00


After booting from the Slackware 12.1 installation disk I found


Attached devices:
Host: scsi2 Channel: 00 Id: 00 Lun: 00
Vendor: SanDisk Model: U3 Titanium Rev: 2.18
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi2 Channel: 00 Id: 00 Lun: 01
Vendor: SanDisk Model: U3 Titanium Rev: 2.18
Type: CD-ROM ANSI SCSI revision: 02
Host: scsi3 Channel: 00 Id: 00 Lun: 00
Vendor: Generic Model: Flash HS-CF Rev: 4.44
Type: Direct-Access ANSI SCSI revision: 00
Host: scsi3 Channel: 00 Id: 00 Lun: 01
Vendor: Generic Model: Flash HS-COMBO Rev: 4.44
Type: Direct-Access ANSI SCSI revision: 00

That's funny the CD-ROM they claim was made by SanDisk, and it has the
same model
as my usb stick. Could it be that the installation disk was made, in
part, by using dd on a usb stick? Anyway, I don't see the SATA drive,
and previously I was unable to install from the CD-ROM>

On Ubuntu I found

Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: HL-DT-ST Model: DVDRAM GH22NS50 Rev: TN00
Type: CD-ROM ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 00 Lun: 00
Vendor: ATA Model: ST3500418AS Rev: CC34
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi4 Channel: 00 Id: 00 Lun: 00
Vendor: ATA Model: IBM-DTTA-371010 Rev: T77O
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi4 Channel: 00 Id: 01 Lun: 00
Vendor: ATA Model: IC35L060AVVA07-0 Rev: VA3O
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi6 Channel: 00 Id: 00 Lun: 00
Vendor: SanDisk Model: U3 Titanium Rev: 2.18
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi6 Channel: 00 Id: 00 Lun: 01
Vendor: SanDisk Model: U3 Titanium Rev: 2.18
Type: CD-ROM ANSI SCSI revision: 02
Host: scsi8 Channel: 00 Id: 00 Lun: 00
Vendor: Generic Model: Flash HS-CF Rev: 4.44
Type: Direct-Access ANSI SCSI revision: 00
Host: scsi8 Channel: 00 Id: 00 Lun: 01
Vendor: Generic Model: Flash HS-COMBO Rev: 4.44
Type: Direct-Access ANSI SCSI revision: 00

The second device refers to the SATA drive.

Finally on the Debian distribution I found

Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: HL-DT-ST Model: DVDRAM GH22NS50 Rev: TN00
Type: CD-ROM ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 00 Lun: 00
Vendor: ATA Model: ST3500418AS Rev: CC34
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 00 Lun: 00
Vendor: SanDisk Model: U3 Titanium Rev: 2.18
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi2 Channel: 00 Id: 00 Lun: 01
Vendor: SanDisk Model: U3 Titanium Rev: 2.18
Type: CD-ROM ANSI SCSI revision: 02
Host: scsi5 Channel: 00 Id: 00 Lun: 00
Vendor: Generic Model: Flash HS-CF Rev: 4.44
Type: Direct-Access ANSI SCSI revision: 00
Host: scsi5 Channel: 00 Id: 00 Lun: 01
Vendor: Generic Model: Flash HS-COMBO Rev: 4.44
Type: Direct-Access ANSI SCSI revision: 00

Again here I see the SATA drive.

All three distributions use the same code for the kernel, drivers, and
libraries. The hardware is the same. They may differ in what modules
to load. So it seems to me that the problem with slackware has to do
with the libraries.


Funny, I was unable to install Slackware on from the Slackware 12.1
distribution disks from the CD-ROM on my IDEs previously. I'll have
to try again.

klee12

Helmut Hullen

unread,
Jul 18, 2009, 12:22:00 PM7/18/09
to
Hallo, klee12,

Du meintest am 18.07.09:

> I did lspci and lspci -n but didn't find anything interesting.

Can you please show the output? Thank you!

klee12

unread,
Jul 18, 2009, 4:40:40 PM7/18/09
to
On Jul 18, 9:22 am, hel...@hullen.de (Helmut Hullen) wrote:
> Hallo, klee12,
>
> Du meintest am 18.07.09:
>
> > I did lspci and lspci -n but didn't find anything interesting.
>
> Can you please show the output? Thank you!
>
Yes of course I can. And thank you for your efforts

I have output from Slackware version 10 of lspci is

0:00.0 Host bridge: Intel Corporation Unknown device 2e20 (rev 03)
00:01.0 PCI bridge: Intel Corporation Unknown device 2e21 (rev 03)
00:03.0 Communication controller: Intel Corporation Unknown device
2e24 (rev 03)
00:19.0 Ethernet controller: Intel Corporation Unknown device 10ce
00:1a.0 USB Controller: Intel Corporation Unknown device 3a37
00:1a.1 USB Controller: Intel Corporation Unknown device 3a38
00:1a.2 USB Controller: Intel Corporation Unknown device 3a39
00:1a.7 USB Controller: Intel Corporation Unknown device 3a3c
00:1b.0 Audio device: Intel Corporation Unknown device 3a3e
00:1c.0 PCI bridge: Intel Corporation Unknown device 3a40
00:1c.3 PCI bridge: Intel Corporation Unknown device 3a46
00:1d.0 USB Controller: Intel Corporation Unknown device 3a34
00:1d.1 USB Controller: Intel Corporation Unknown device 3a35
00:1d.2 USB Controller: Intel Corporation Unknown device 3a36
00:1d.7 USB Controller: Intel Corporation Unknown device 3a3a
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 90)
00:1f.0 ISA bridge: Intel Corporation Unknown device 3a18
00:1f.2 IDE interface: Intel Corporation Unknown device 3a20
00:1f.3 SMBus: Intel Corporation Unknown device 3a30
00:1f.5 IDE interface: Intel Corporation Unknown device 3a26
01:00.0 VGA compatible controller: nVidia Corporation Unknown device
0640 (rev a1)
03:00.0 IDE interface: JMicron Technologies, Inc. JMB368 IDE
controller
04:06.0 FireWire (IEEE 1394): Agere Systems FW323 (rev 70)
~
and of lspci -n is

0:00.0 0600: 8086:2e20 (rev 03)
00:01.0 0604: 8086:2e21 (rev 03)
00:03.0 0780: 8086:2e24 (rev 03)
00:19.0 0200: 8086:10ce
00:1a.0 0c03: 8086:3a37
00:1a.1 0c03: 8086:3a38
00:1a.2 0c03: 8086:3a39
00:1a.7 0c03: 8086:3a3c
00:1b.0 0403: 8086:3a3e
00:1c.0 0604: 8086:3a40
00:1c.3 0604: 8086:3a46
00:1d.0 0c03: 8086:3a34
00:1d.1 0c03: 8086:3a35
00:1d.2 0c03: 8086:3a36
00:1d.7 0c03: 8086:3a3a
00:1e.0 0604: 8086:244e (rev 90)
00:1f.0 0601: 8086:3a18
00:1f.2 0101: 8086:3a20
00:1f.3 0c05: 8086:3a30
00:1f.5 0101: 8086:3a26
01:00.0 0300: 10de:0640 (rev a1)
03:00.0 0101: 197b:2368
04:06.0 0c00: 11c1:5811 (rev 70)

I don't have it for Slackware version 12 which is what I'm trying to
install. When in insert the installation CD, drop into root I'm told
that lspci is not available.

I forget to the output to lspci and lspci for a working Slack 12 which
is available when I boot into Debian or Ubunto. I'll post the results
of lspci soon.

I poked around some more. After bringing up Slackware from the
installation disk, I tried to install Slackware on one of my IDEs.
When the menu from setup comes up, I go to the Installation section
and tell it to install from CD. The installation scans for but cannot
find the CD. I drop to the root and find that the /dev/cdrom is
linked to /dev/sr0. I mount /dev/sr0 and do an ls on the mount point.
I get

LaunchPad.zip*
LaunchU3.exe*
autorun.inf*

Then I do a df on the mount point and I get

Filesystem 1k-blocks Used Available Use% Mounted on
/dev/sr0 5618 5618 0 100% /t

Seems that the installation disk contains the contents of the two
installation floppies that Slackware used to use. The installation
disk, according to the labels disk, is supposed to contain packages
for A, AP, etc. It looks like packages are on the Installation disk
but cannot be found by sr0.

Back to my adventures with the new computer.

klee12


Helmut Hullen

unread,
Jul 18, 2009, 4:50:00 PM7/18/09
to
Hallo, klee12,

Du meintest am 18.07.09:

> 0:00.0 Host bridge: Intel Corporation Unknown device 2e20 (rev 03)

No SATA.

> 0:00.0 0600: 8086:2e20 (rev 03)
> 00:01.0 0604: 8086:2e21 (rev 03)
> 00:03.0 0780: 8086:2e24 (rev 03)
> 00:19.0 0200: 8086:10ce
> 00:1a.0 0c03: 8086:3a37
> 00:1a.1 0c03: 8086:3a38
> 00:1a.2 0c03: 8086:3a39
> 00:1a.7 0c03: 8086:3a3c
> 00:1b.0 0403: 8086:3a3e
> 00:1c.0 0604: 8086:3a40
> 00:1c.3 0604: 8086:3a46
> 00:1d.0 0c03: 8086:3a34
> 00:1d.1 0c03: 8086:3a35
> 00:1d.2 0c03: 8086:3a36
> 00:1d.7 0c03: 8086:3a3a
> 00:1e.0 0604: 8086:244e (rev 90)
> 00:1f.0 0601: 8086:3a18
> 00:1f.2 0101: 8086:3a20
> 00:1f.3 0c05: 8086:3a30
> 00:1f.5 0101: 8086:3a26
> 01:00.0 0300: 10de:0640 (rev a1)
> 03:00.0 0101: 197b:2368
> 04:06.0 0c00: 11c1:5811 (rev 70)

And again no SATA.
But a firewire controller.

If you have connected your SATA harddisk somewhere: where have you
connected it?

klee12

unread,
Jul 18, 2009, 6:10:35 PM7/18/09
to
Hello Helmut

First let me give the output of lspci and lspci -n for the Ubunto
distribution which does recognize the SATA drives. The outputs for
lspci are


ls

> If you have connected your SATA harddisk somewhere: where have you
> connected it?

00:00.0 Host bridge: Intel Corporation 4 Series Chipset DRAM
Controller (rev 03)
00:01.0 PCI bridge: Intel Corporation 4 Series Chipset PCI Express
Root Port (rev 03)
00:03.0 Communication controller: Intel Corporation 4 Series Chipset
HECI Controller (rev 03)
00:19.0 Ethernet controller: Intel Corporation 82567V-2 Gigabit
Network Connection
00:1a.0 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB
UHCI Controller #4
00:1a.1 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB
UHCI Controller #5
00:1a.2 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB
UHCI Controller #6
00:1a.7 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB2
EHCI Controller #2
00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD
Audio Controller
00:1c.0 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI
Express Port 1
00:1c.3 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI
Express Port 4
00:1d.0 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB
UHCI Controller #1
00:1d.1 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB
UHCI Controller #2
00:1d.2 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB
UHCI Controller #3
00:1d.7 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB2
EHCI Controller #1


00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 90)

00:1f.0 ISA bridge: Intel Corporation 82801JIB (ICH10) LPC Interface
Controller
00:1f.2 IDE interface: Intel Corporation 82801JI (ICH10 Family) 4 port
SATA IDE Controller
00:1f.3 SMBus: Intel Corporation 82801JI (ICH10 Family) SMBus
Controller
00:1f.5 IDE interface: Intel Corporation 82801JI (ICH10 Family) 2 port
SATA IDE Controller
01:00.0 VGA compatible controller: nVidia Corporation GeForce 9500 GT


(rev a1)
03:00.0 IDE interface: JMicron Technologies, Inc. JMB368 IDE
controller
04:06.0 FireWire (IEEE 1394): Agere Systems FW323 (rev 70)

and for lspci-n is


00:00.0 0600: 8086:2e20 (rev 03)


00:01.0 0604: 8086:2e21 (rev 03)
00:03.0 0780: 8086:2e24 (rev 03)
00:19.0 0200: 8086:10ce
00:1a.0 0c03: 8086:3a37
00:1a.1 0c03: 8086:3a38
00:1a.2 0c03: 8086:3a39
00:1a.7 0c03: 8086:3a3c
00:1b.0 0403: 8086:3a3e
00:1c.0 0604: 8086:3a40
00:1c.3 0604: 8086:3a46
00:1d.0 0c03: 8086:3a34
00:1d.1 0c03: 8086:3a35
00:1d.2 0c03: 8086:3a36
00:1d.7 0c03: 8086:3a3a
00:1e.0 0604: 8086:244e (rev 90)
00:1f.0 0601: 8086:3a18
00:1f.2 0101: 8086:3a20
00:1f.3 0c05: 8086:3a30
00:1f.5 0101: 8086:3a26
01:00.0 0300: 10de:0640 (rev a1)
03:00.0 0101: 197b:2368
04:06.0 0c00: 11c1:5811 (rev 70)

> If you have connected your SATA harddisk somewhere: where have you
> connected it?

Well, I had someone put together the computer for me. I have an Intel
DP43TF board and it has several connerctors for the SATA drives. I
assume they're plugged in correctly because Ubuntu and Debian can see
them. Even Slackware 12.1 was able to boot up the installation disk.
For this reason I don't think the problem is hardware (though I may be
wrong). Maybe the installation disk kernel didn't include a module?

klee12

klee12

unread,
Jul 18, 2009, 7:14:22 PM7/18/09
to
On Jul 18, 3:10 pm, klee12 <kle...@alum.mit.edu> wrote:

Hello Helmut

I thought of one more thing. I booted up on the Slackware 12
installation disk, dropped to root and did

cat /var/log/message | grep -i scsi and got

Jul 17 15:18:42 (none) user.notice kernel: SCSI subsystem initialized
Jul 17 15:18:42 (none) user.info kernel: Loading iSCSI transport class
v2.0-724.
Jul 17 15:18:42 (none) user.warn kernel: scsi: <fdomain> Detection
failed (no card)
Jul 17 15:18:42 (none) user.notice kernel: iscsi: registered transport
(qla4xxx)
Jul 17 15:18:42 (none) user.info kernel: QLogic iSCSI HBA Driver
Jul 17 15:18:42 (none) user.warn kernel: Emulex LightPulse Fibre
Channel SCSI driver 8.2.2
Jul 17 15:18:42 (none) user.warn kernel: Failed initialization of
WD-7000 SCSI card!
Jul 17 15:18:42 (none) user.info kernel: ipr: IBM Power RAID SCSI
Device Driver version: 2.4.1 (April 24, 2007)
Jul 17 15:18:42 (none) user.info kernel: I2O SCSI Peripheral OSM
v1.316
Jul 17 15:18:42 (none) user.info kernel: scsi2 : SCSI emulation for
USB Mass Storage devices
Jul 17 15:18:46 (none) user.notice kernel: scsi 2:0:0:0: Direct-
Access Generic Flash HS-CF 4.44 PQ: 0 ANSI: 0
Jul 17 15:18:46 (none) user.notice kernel: sd 2:0:0:0: [sda] Attached
SCSI removable disk
Jul 17 15:18:46 (none) user.notice kernel: scsi 2:0:0:1: Direct-
Access Generic Flash HS-COMBO 4.44 PQ: 0 ANSI: 0
Jul 17 15:18:46 (none) user.notice kernel: sd 2:0:0:1: [sdb] Attached
SCSI removable disk
Jul 17 15:20:12 (none) user.info kernel: scsi3 : SCSI emulation for
USB Mass Storage devices
Jul 17 15:20:17 (none) user.notice kernel: scsi 3:0:0:0: Direct-
Access SanDisk U3 Titanium 2.18 PQ: 0 ANSI: 2
Jul 17 15:20:17 (none) user.notice kernel: sd 3:0:0:0: [sdc] Attached
SCSI removable disk
Jul 17 15:20:17 (none) user.notice kernel: scsi 3:0:0:1: CD-
ROM SanDisk U3 Titanium 2.18 PQ: 0 ANSI: 2
Jul 17 15:20:17 (none) user.warn kernel: sr0: scsi3-mmc drive: 8x/40x
writer xa/form2 cdda tray
Jul 17 15:20:17 (none) user.debug kernel: sr 3:0:0:1: Attached scsi CD-
ROM sr0


I don't understand, but let make some guesses. sda is for what
Slackware would be used with /dev/sda and sdb is for /dev/sdb. They're
on the same IDE bus and attached to slot 2. Slot 3 is for usb devices,
and one might be for the usb stick, the other for the CD-ROM. I don't
see anythng for the SATA hard disk. Are my guesses close to correct?


I also did cat /var/log/messages | grep -i sata and got

Jul 17 15:18:42 (none) user.notice kernel: aic94xx: Adaptec aic94xx
SAS/SATA driver version 1.0.3 loaded
Jul 17 15:18:42 (none) user.info kernel: RocketRAID 3xxx SATA
Controller driver v1.2 (070830)

klee12

klee12

unread,
Jul 18, 2009, 7:53:41 PM7/18/09
to
Hello, first I made some typos in the previous post. When I guessed at
what some of the meanings from messages when I grepped for sata, I
should have said /dev/hda and /dev/hdb when I wrote /dev/hda and /dev/
hdb.

I had grepped for SATA when I grepped the messages file Ubuntu, I
should have said

cat /var/log/messages | grep -i SATA. I just did that and got

Jul 18 09:26:47 i2500 kernel: [ 0.424817] SCSI subsystem
initialized
Jul 18 09:26:47 i2500 kernel: [ 17.366197] scsi0 : ata_piix
Jul 18 09:26:47 i2500 kernel: [ 17.366256] scsi1 : ata_piix
Jul 18 09:26:47 i2500 kernel: [ 19.073337] scsi 0:0:0:0: CD-
ROM HL-DT-ST DVDRAM GH22NS50 TN00 PQ: 0 ANSI: 5
Jul 18 09:26:47 i2500 kernel: [ 19.077030] sr0: scsi3-mmc drive: 10x/
10x writer dvd-ram cd/rw xa/form2 cdda tray
Jul 18 09:26:47 i2500 kernel: [ 19.077171] sr 0:0:0:0: Attached scsi
generic sg0 type 5
Jul 18 09:26:47 i2500 kernel: [ 19.077225] scsi 1:0:0:0: Direct-
Access ATA ST3500418AS CC34 PQ: 0 ANSI: 5
Jul 18 09:26:47 i2500 kernel: [ 19.129606] sd 1:0:0:0: [sda]
Attached SCSI disk
Jul 18 09:26:47 i2500 kernel: [ 19.129635] sd 1:0:0:0: Attached scsi
generic sg1 type 0
Jul 18 09:26:47 i2500 kernel: [ 19.129711] scsi2 : ata_piix
Jul 18 09:26:47 i2500 kernel: [ 19.129748] scsi3 : ata_piix
Jul 18 09:26:47 i2500 kernel: [ 19.786900] scsi4 : pata_jmicron
Jul 18 09:26:47 i2500 kernel: [ 19.786943] scsi5 : pata_jmicron
Jul 18 09:26:47 i2500 kernel: [ 20.220143] scsi 4:0:0:0: Direct-
Access ATA IBM-DTTA-371010 T77O PQ: 0 ANSI: 5
Jul 18 09:26:47 i2500 kernel: [ 20.268662] sd 4:0:0:0: [sdb]
Attached SCSI disk
Jul 18 09:26:47 i2500 kernel: [ 20.268690] sd 4:0:0:0: Attached scsi
generic sg2 type 0
Jul 18 09:26:47 i2500 kernel: [ 20.268742] scsi 4:0:1:0: Direct-
Access ATA IC35L060AVVA07-0 VA3O PQ: 0 ANSI: 5
Jul 18 09:26:47 i2500 kernel: [ 20.344144] sd 4:0:1:0: [sdc]
Attached SCSI disk
Jul 18 09:26:47 i2500 kernel: [ 20.344171] sd 4:0:1:0: Attached scsi
generic sg3 type 0
Jul 18 09:26:47 i2500 kernel: [ 23.586991] scsi6 : SCSI emulation


for USB Mass Storage devices

Jul 18 09:26:47 i2500 kernel: [ 28.593756] scsi 6:0:0:0: Direct-


Access Generic Flash HS-CF 4.44 PQ: 0 ANSI: 0

Jul 18 09:26:47 i2500 kernel: [ 28.597026] scsi 6:0:0:1: Direct-


Access Generic Flash HS-COMBO 4.44 PQ: 0 ANSI: 0

Jul 18 09:26:47 i2500 kernel: [ 28.601602] sd 6:0:0:0: [sdd]
Attached SCSI removable disk
Jul 18 09:26:47 i2500 kernel: [ 28.601672] sd 6:0:0:0: Attached scsi
generic sg4 type 0
Jul 18 09:26:47 i2500 kernel: [ 28.650687] sd 6:0:0:1: [sde]
Attached SCSI removable disk
Jul 18 09:26:47 i2500 kernel: [ 28.650753] sd 6:0:0:1: Attached scsi
generic sg5 type 0
Jul 18 14:39:49 i2500 kernel: [ 0.424857] SCSI subsystem
initialized
Jul 18 14:39:49 i2500 kernel: [ 17.366195] scsi0 : ata_piix
Jul 18 14:39:49 i2500 kernel: [ 17.366254] scsi1 : ata_piix
Jul 18 14:39:49 i2500 kernel: [ 19.073371] scsi 0:0:0:0: CD-
ROM HL-DT-ST DVDRAM GH22NS50 TN00 PQ: 0 ANSI: 5
Jul 18 14:39:49 i2500 kernel: [ 19.077064] sr0: scsi3-mmc drive: 10x/
10x writer dvd-ram cd/rw xa/form2 cdda tray
Jul 18 14:39:49 i2500 kernel: [ 19.077205] sr 0:0:0:0: Attached scsi
generic sg0 type 5
Jul 18 14:39:49 i2500 kernel: [ 19.077259] scsi 1:0:0:0: Direct-
Access ATA ST3500418AS CC34 PQ: 0 ANSI: 5
Jul 18 14:39:49 i2500 kernel: [ 19.123092] sd 1:0:0:0: [sda]
Attached SCSI disk
Jul 18 14:39:49 i2500 kernel: [ 19.123121] sd 1:0:0:0: Attached scsi
generic sg1 type 0
Jul 18 14:39:49 i2500 kernel: [ 19.123202] scsi2 : ata_piix
Jul 18 14:39:49 i2500 kernel: [ 19.123242] scsi3 : ata_piix
Jul 18 14:39:49 i2500 kernel: [ 19.778896] scsi4 : pata_jmicron
Jul 18 14:39:49 i2500 kernel: [ 19.778937] scsi5 : pata_jmicron
Jul 18 14:39:49 i2500 kernel: [ 20.208143] scsi 4:0:0:0: Direct-
Access ATA IBM-DTTA-371010 T77O PQ: 0 ANSI: 5
Jul 18 14:39:49 i2500 kernel: [ 20.256864] sd 4:0:0:0: [sdb]
Attached SCSI disk
Jul 18 14:39:49 i2500 kernel: [ 20.256892] sd 4:0:0:0: Attached scsi
generic sg2 type 0
Jul 18 14:39:49 i2500 kernel: [ 20.256944] scsi 4:0:1:0: Direct-
Access ATA IC35L060AVVA07-0 VA3O PQ: 0 ANSI: 5
Jul 18 14:39:49 i2500 kernel: [ 20.322389] sd 4:0:1:0: [sdc]
Attached SCSI disk
Jul 18 14:39:49 i2500 kernel: [ 20.322415] sd 4:0:1:0: Attached scsi
generic sg3 type 0
Jul 18 14:39:49 i2500 kernel: [ 23.582961] scsi6 : SCSI emulation


for USB Mass Storage devices

Jul 18 14:39:49 i2500 kernel: [ 28.589680] scsi 6:0:0:0: Direct-


Access Generic Flash HS-CF 4.44 PQ: 0 ANSI: 0

Jul 18 14:39:49 i2500 kernel: [ 28.592930] scsi 6:0:0:1: Direct-


Access Generic Flash HS-COMBO 4.44 PQ: 0 ANSI: 0

Jul 18 14:39:49 i2500 kernel: [ 28.597399] sd 6:0:0:0: [sdd]
Attached SCSI removable disk
Jul 18 14:39:49 i2500 kernel: [ 28.597470] sd 6:0:0:0: Attached scsi
generic sg4 type 0
Jul 18 14:39:49 i2500 kernel: [ 28.648036] sd 6:0:0:1: [sde]
Attached SCSI removable disk
Jul 18 14:39:49 i2500 kernel: [ 28.648103] sd 6:0:0:1: Attached scsi
generic sg5 type 0
Jul 18 16:31:27 i2500 kernel: [ 0.424900] SCSI subsystem
initialized
Jul 18 16:31:27 i2500 kernel: [ 17.366195] scsi0 : ata_piix
Jul 18 16:31:27 i2500 kernel: [ 17.366254] scsi1 : ata_piix
Jul 18 16:31:27 i2500 kernel: [ 19.073356] scsi 0:0:0:0: CD-
ROM HL-DT-ST DVDRAM GH22NS50 TN00 PQ: 0 ANSI: 5
Jul 18 16:31:27 i2500 kernel: [ 19.077049] sr0: scsi3-mmc drive: 10x/
10x writer dvd-ram cd/rw xa/form2 cdda tray
Jul 18 16:31:27 i2500 kernel: [ 19.077190] sr 0:0:0:0: Attached scsi
generic sg0 type 5
Jul 18 16:31:27 i2500 kernel: [ 19.077243] scsi 1:0:0:0: Direct-
Access ATA ST3500418AS CC34 PQ: 0 ANSI: 5
Jul 18 16:31:27 i2500 kernel: [ 19.126929] sd 1:0:0:0: [sda]
Attached SCSI disk
Jul 18 16:31:27 i2500 kernel: [ 19.126958] sd 1:0:0:0: Attached scsi
generic sg1 type 0
Jul 18 16:31:27 i2500 kernel: [ 19.127039] scsi2 : ata_piix
Jul 18 16:31:27 i2500 kernel: [ 19.127079] scsi3 : ata_piix
Jul 18 16:31:27 i2500 kernel: [ 19.782893] scsi4 : pata_jmicron
Jul 18 16:31:27 i2500 kernel: [ 19.782934] scsi5 : pata_jmicron
Jul 18 16:31:27 i2500 kernel: [ 20.188152] scsi 4:0:0:0: Direct-
Access ATA IBM-DTTA-371010 T77O PQ: 0 ANSI: 5
Jul 18 16:31:27 i2500 kernel: [ 20.237679] sd 4:0:0:0: [sdb]
Attached SCSI disk
Jul 18 16:31:27 i2500 kernel: [ 20.237706] sd 4:0:0:0: Attached scsi
generic sg2 type 0
Jul 18 16:31:27 i2500 kernel: [ 20.237758] scsi 4:0:1:0: Direct-
Access ATA IC35L060AVVA07-0 VA3O PQ: 0 ANSI: 5
Jul 18 16:31:27 i2500 kernel: [ 20.309915] sd 4:0:1:0: [sdc]
Attached SCSI disk
Jul 18 16:31:27 i2500 kernel: [ 20.309942] sd 4:0:1:0: Attached scsi
generic sg3 type 0
Jul 18 16:31:27 i2500 kernel: [ 23.403672] scsi6 : SCSI emulation


for USB Mass Storage devices

Jul 18 16:31:27 i2500 kernel: [ 28.409799] scsi 6:0:0:0: Direct-


Access Generic Flash HS-CF 4.44 PQ: 0 ANSI: 0

Jul 18 16:31:27 i2500 kernel: [ 28.413024] scsi 6:0:0:1: Direct-


Access Generic Flash HS-COMBO 4.44 PQ: 0 ANSI: 0

Jul 18 16:31:27 i2500 kernel: [ 28.417494] sd 6:0:0:0: [sdd]
Attached SCSI removable disk
Jul 18 16:31:27 i2500 kernel: [ 28.417565] sd 6:0:0:0: Attached scsi
generic sg4 type 0
Jul 18 16:31:27 i2500 kernel: [ 28.468252] sd 6:0:0:1: [sde]
Attached SCSI removable disk
Jul 18 16:31:27 i2500 kernel: [ 28.468310] sd 6:0:0:1: Attached scsi
generic sg5 type 0

This is much different from what I got using the Slackware 12.1
installation disk.

klee12

Jerry Peters

unread,
Jul 18, 2009, 8:22:21 PM7/18/09
to

No, it's some stupid windoze feature that Sandisk installs. The USB
stick looks like both a CDROM & a memory stick. I've got a Sandisk
Cruzer that does the same thing. Researching it I found that
removing this mis-feature requires windoze.

Jerry

Grant

unread,
Jul 18, 2009, 8:46:06 PM7/18/09
to

Wake up Helmut -- the slack-10 lspci database (pci-ids) is out of date here ;)

Grant.
--
http://bugsplatter.id.au

Dan C

unread,
Jul 18, 2009, 11:05:21 PM7/18/09
to

Can you please learn how to use a sig delimiter on the signature that you
stole from me? Thanks.


--
"Ubuntu" -- an African word, meaning "Slackware is too hard for me".
The Usenet Improvement Project: http://improve-usenet.org
Ahhhhhhhh!: http://brandybuck.site40.net/pics/relieve.jpg

Sidney Lambe

unread,
Jul 19, 2009, 1:09:01 AM7/19/09
to
Dan C[odbrain] <youmust...@lan.invalid> wrote:
> On Sat, 18 Jul 2009 18:22:00 +0200, Helmut Hullen wrote:
>
>> Hallo, klee12,
>>
>> Du meintest am 18.07.09:
>>
>>> I did lspci and lspci -n but didn't find anything interesting.
>>
>> Can you please show the output? Thank you!
>>
>> Viele Gruesse
>> Helmut
>>
>> "Ubuntu" - an African word, meaning "Slackware is too hard for me".
>
> Can you please learn how to use a sig delimiter on the signature that you
> stole from me? Thanks.

Should have known that stupid sig came from you.

Like a lot of people, I run Slackware because it is _simpler_
than distros like Ubuntu.

More evidence here that you don't even run Linux, much less
Slackware, and are just stealing people's User-Agent headers
to make it look like you are running Linux.

It's not that you aren't intelligent enough to run Linux (with
a Windows-clone kindergarten training wheel interface like KDE), it's
that you spend all your wandering the Internet and verbally
abusing people under a hundred aliases.

> --
> "Ubuntu" -- an African word, meaning "Slackware is too hard for me".

Wrong. Any way you compare them, Slackware is simpler than Ubuntu.

> The Usenet Improvement Project: http://improve-usenet.org

The best way I can think of to improve the usenet is to have
all the newsadmins agree to force people to post using one
alias only. For them to keep a private, shared database to aid this
process.

This would put stinking trolls like Dan C[odbrain] out of business.

> Ahhhhhhhh!: http://brandybuck.site40.net/pics/relieve.jpg

What's that a picture of? You trying to find your dick with a
magifying glass?

I wouldn't go to a URL you suggested for anything.

Sid

Helmut Hullen

unread,
Jul 19, 2009, 1:48:00 AM7/19/09
to
Hallo, klee12,

Du meintest am 18.07.09:

> 00:1f.0 ISA bridge: Intel Corporation 82801JIB (ICH10) LPC Interface


> Controller
> 00:1f.2 IDE interface: Intel Corporation 82801JI (ICH10 Family) 4
> port SATA IDE Controller
> 00:1f.3 SMBus: Intel Corporation 82801JI (ICH10 Family) SMBus
> Controller
> 00:1f.5 IDE interface: Intel Corporation 82801JI (ICH10 Family) 2
> port SATA IDE Controller

There it is!

But my search in the "drivers" directories of kernel 2.6.29.6 got no
hit.

Helmut Hullen

unread,
Jul 19, 2009, 1:53:00 AM7/19/09
to
Hallo, klee12,

Du meintest am 18.07.09:

> Jul 18 09:26:47 i2500 kernel: [ 17.366197] scsi0 : ata_piix


> Jul 18 09:26:47 i2500 kernel: [ 17.366256] scsi1 : ata_piix

Maybe that this driver fits for the 82801JT too but slackware doesn't
dare to use it.

What tells

lsmod | grep piix

Try "modprobe ata_piix".

klee12

unread,
Jul 19, 2009, 12:31:18 PM7/19/09
to

Hello Helmut

I did "lsmod | grep piix" and "modprobe ata_piix" and got nothing.

I did slocate piix and got

/usr/include/asm-i386/mach-visws/piix4.h
/usr/src/linux-2.6.21.5/Documentation/i2c/busses/i2c-piix4
/usr/src/linux-2.6.21.5/drivers/ide/pci/piix.c
/usr/src/linux-2.6.21.5/drivers/i2c/busses/i2c-piix4.c
/usr/src/linux-2.6.21.5/drivers/ata/pata_mpiix.c
/usr/src/linux-2.6.21.5/drivers/ata/pata_oldpiix.c
/usr/src/linux-2.6.21.5/drivers/ata/ata_piix.c
/usr/src/linux-2.6.21.5/include/asm-mips/mips-boards/piix4.h
/usr/src/linux-2.6.21.5/include/config/i2c/piix4.h
/usr/src/linux-2.6.21.5/include/config/blk/dev/piix.h
/usr/src/linux-2.6.21.5/include/config/ata/piix.h
/usr/src/linux-2.6.21.5/include/config/pata/mpiix.h
/usr/src/linux-2.6.21.5/include/config/pata/oldpiix.h
/usr/src/linux-2.6.21.5/include/asm-i386/mach-visws/piix4.h
/lib/modules/2.6.21.5/kernel/drivers/i2c/busses/i2c-piix4.ko
/lib/modules/2.6.21.5/kernel/drivers/ata/pata_oldpiix.ko
/lib/modules/2.6.21.5/kernel/drivers/ata/pata_mpiix.ko
/lib/modules/2.6.21.5-smp/kernel/drivers/i2c/busses/i2c-piix4.ko
/lib/modules/2.6.21.5-smp/kernel/drivers/ata/pata_oldpiix.ko
/lib/modules/2.6.21.5-smp/kernel/drivers/ata/pata_mpiix.ko
/hdb10/Pasture/Junk/Lm_sensors-2.9.1/lm_sensors-2.9.1_untarred/doc/
busses/i2c-piix4
/hdb10/Pasture/Junk/Lm_sensors-2.9.1/lm_sensors-2.9.1_untarred/kernel/
busses/i2c-piix4.c

Ignore the last two lines; they are somethings I tried once.

There might be something on the disk that I didn't install, so I
looked at the MANIFEST from the disk. I forgot that I had upgraded to
Slackware 12.0 and was no longer running Slackware. Stupid of me; I
hope it didn't cause problems. Anyway I did grep piix Manifest and got


-rw-r--r-- root/root 11066 2007-06-19 15:18 lib/modules/2.6.21.5/
kernel/drivers/i2c/busses/i2c-piix4.ko
-rw-r--r-- root/root 7196 2007-06-19 15:18 lib/modules/2.6.21.5/
kernel/drivers/ata/pata_oldpiix.ko
-rw-r--r-- root/root 6810 2007-06-19 15:18 lib/modules/2.6.21.5/
kernel/drivers/ata/pata_mpiix.ko
-rw-r--r-- root/root 14906 2007-06-19 14:54 lib/modules/2.6.21.5-
smp/kernel/drivers/i2c/busses/i2c-piix4.ko
-rw-r--r-- root/root 11156 2007-06-19 14:54 lib/modules/2.6.21.5-
smp/kernel/drivers/ata/pata_oldpiix.ko
-rw-r--r-- root/root 10778 2007-06-19 14:54 lib/modules/2.6.21.5-
smp/kernel/drivers/ata/pata_mpiix.ko
-rw-r--r-- root/root 2581 2007-06-11 13:37 usr/include/asm-i386/
mach-visws/piix4.h
-rw-r--r-- root/root 4207 2007-06-11 13:37 usr/src/linux-2.6.21.5/
Documentation/i2c/busses/i2c-piix4
-rw-r--r-- root/root 20965 2007-06-11 13:37 usr/src/linux-2.6.21.5/
drivers/ide/pci/piix.c
-rw-r--r-- root/root 13410 2007-06-11 13:37 usr/src/linux-2.6.21.5/
drivers/i2c/busses/i2c-piix4.c
-rw-r--r-- root/root 8756 2007-06-11 13:37 usr/src/linux-2.6.21.5/
drivers/ata/pata_mpiix.c
-rw-r--r-- root/root 9149 2007-06-11 13:37 usr/src/linux-2.6.21.5/
drivers/ata/pata_oldpiix.c
-rw-r--r-- root/root 32920 2007-06-11 13:37 usr/src/linux-2.6.21.5/
drivers/ata/ata_piix.c
-rw-r--r-- root/root 2676 2007-06-11 13:37 usr/src/linux-2.6.21.5/
include/asm-mips/mips-boards/piix4.h
-rw-r--r-- root/root 0 2007-06-19 14:44 usr/src/linux-2.6.21.5/
include/config/pata/mpiix.h
-rw-r--r-- root/root 0 2007-06-19 14:44 usr/src/linux-2.6.21.5/
include/config/pata/oldpiix.h
-rw-r--r-- root/root 0 2007-06-19 14:44 usr/src/linux-2.6.21.5/
include/config/blk/dev/piix.h
-rw-r--r-- root/root 0 2007-06-19 14:44 usr/src/linux-2.6.21.5/
include/config/i2c/piix4.h
-rw-r--r-- root/root 0 2007-06-19 14:44 usr/src/linux-2.6.21.5/
include/config/ata/piix.h
-rw-r--r-- root/root 2581 2007-06-11 13:37 usr/src/linux-2.6.21.5/
include/asm-i386/mach-visws/piix4.h


This is all for Slackware 12.0 and not 12.1 since I couldn't access
the Slackware 12.1 disks .

I think this is the problem and I would appreciate suggestions on how
to fix it. I don't want to make a big mistake.

Thanks

klee12

Helmut Hullen

unread,
Jul 19, 2009, 1:16:00 PM7/19/09
to
Hallo, klee12,

Du meintest am 19.07.09:

>> Try "modprobe ata_piix".
>>

> /usr/src/linux-2.6.21.5/drivers/ata/ata_piix.c

Hmm - that file is related to the module.

Can you take a look into the ".config" file of the kernel? There should
somewhere be an entry like

CONFIG_ATA_PIIX=m

(search for PIIX)

No PATA, no "old", no I2C - that is other hardware.

Dan C

unread,
Jul 19, 2009, 11:08:39 PM7/19/09
to
On Sun, 19 Jul 2009 07:09:01 +0200, Sidney Lambe wrote:

>> Can you please learn how to use a sig delimiter on the signature that
>> you stole from me? Thanks.

> Should have known that stupid sig came from you.

It's quite an admired sig throughout Usenet. I'm quite proud of it.

> Like a lot of people, I run Slackware because it is _simpler_ than
> distros like Ubuntu.
>
> More evidence here that you don't even run Linux, much less Slackware,
> and are just stealing people's User-Agent headers to make it look like
> you are running Linux.

HAR! Hahaha! Good one, Alan Connor!

> It's not that you aren't intelligent enough to run Linux (with a
> Windows-clone kindergarten training wheel interface like KDE), it's that
> you spend all your wandering the Internet and verbally abusing people
> under a hundred aliases.

Wrong, twice. I don't use KDE and never have (other than to take a look
at it). I use Xfce. The second error you made is thinking that I use "a
hundred aliases". Absolutely untrue - I post under this name, only.

>> "Ubuntu" -- an African word, meaning "Slackware is too hard for me".

> Wrong. Any way you compare them, Slackware is simpler than Ubuntu.

Not really. Not for Win-droid n00bs coming to Linux for the first time.

>> The Usenet Improvement Project: http://improve-usenet.org
>
> The best way I can think of to improve the usenet is to have all the
> newsadmins agree to force people to post using one alias only. For them
> to keep a private, shared database to aid this process.

Well, that would keep you off Usenet, wouldn't it? You used to post as
"Alan Connor", then "Tom Newton" for a while, and now "Sidney Lambe".
I've also seen the occasional post from you as "Evergreen", and there
were a few names prior to the Alan Connor era. Care to comment on this
apparent contradiction, Alan?

> This would put stinking trolls like Dan C[odbrain] out of business.

Nope. As I said, I post *ONLY* with this name.



>> Ahhhhhhhh!: http://brandybuck.site40.net/pics/relieve.jpg
>
> What's that a picture of? You trying to find your dick with a magifying
> glass?
>
> I wouldn't go to a URL you suggested for anything.

Whatever blows your dress up, Alan.

> Sid

Bugger off, Alan.

Oh, almost forgot to ask... How come you replied directly to my post,
Alan? You have claimed forever to have me KF'd and to not read a word of
what I say. How come you're reading/replying to me now?


--
"Ubuntu" -- an African word, meaning "Slackware is too hard for me".

The Usenet Improvement Project: http://improve-usenet.org

Ahhhhhhhh!: http://brandybuck.site40.net/pics/relieve.jpg

klee12

unread,
Aug 4, 2009, 4:37:14 PM8/4/09
to
I installed Debian but couldn't couldn't get the Slackware problem out
of my mind. I preferred Slackware. Then I remembered that Slackware
12.1 was not newest version, maybe Slackware 12.2 would work. So I
tried it and

It worked ! Oh Joy, I could see the SATA drive.

I took about a day to move all the stuff over from 12.0 to 12.2 but I
think I'm in business

So thanks all for all the time you spent with me.

In poking about the Slackware site, I learned that the official forum
of Slackware is now LinuxQuestons/Slackware so I'll be mostly posting
there in the future

klee12

0 new messages