Release Candidates :: DSL v4.0rc2



I think the problems start when you plug and unplug more than one usb stick.

If I use only one usb stick - other than the one I boot from -  and take care to mount/unmount it each time I plug/unplug it will stay as sdb1 and everything works fine.

If I use more than one usb stick in sequence using the same port - other than the one I boot from - they will be added as sdb1, sdc1, sdd1, etc (as long as I mount/unmount each one after/before plugging/unplugging). If I then go back to the first one (sdb1), a device /mnt/sdb gets created which does not contain the files on sdb1, sdb1 will not mount using the mount device (but will mount using mount /dev/sdb1 /mnt/sdb1) and things go gradually south.

As I think has been said a few times before, there's not much that can be done about this in 2.4.26 - it seems to work much better in dsl-n
Quote (marvinudy @ Aug. 29 2007,13:07)
Robert,

Tried to boot DSL-4.0 rc2 with the 'sata' option and got a 'loading hang' at sata_vsc.0.....

Without the 'sata' option, boots fine but shows my 1st sata drive as hda and of course does not see sdb.  What did I miss?

Best regards,

marvinudy

Intel 6420, GA-965-ds3 r-3, sata Wd 250 & 160 hd, 2Gb pc-6400 memory.

Sorry, cannot say, as I don't own any SATA gear.
Perhaps someone with SATA gear can respond.
Otherwise I would suggest to check irq assignments, maybe try expert mode and load the sata module that corresponds to your hardware.

Without owning any SATA hardware to test, I can only direct you to try a few things...

DSL v4.0 has the kernel supplied SATA modules available during boot as shown in the boot time available modules:

[/tmp]# ls  mroot/modules/scsi/
BusLogic.o      aic7xxx.o       gdth.o          modules.lst     sata_nv.o       sata_via.o      ultrastor.o
NCR53c406a.o    ata_piix.o      hptraid.o       ncr53c8xx.o     sata_promise.o  sata_vsc.o      usb-ohci.o
a100u2w.o       ataraid.o       ide-cd.o        ohci1394.o      sata_qstor.o    sbp2.o          usb-storage.o
advansys.o      atp870u.o       ide-scsi.o      pas16.o         sata_sil.o      seagate.o       usb-uhci.o
aha152x.o       dtc.o           ieee1394.o      pci2000.o       sata_sis.o      silraid.o       usbcore.o
aha1542.o       eata.o          initio.o        pci2220i.o      sata_svw.o      t128.o          wd7000.o
aha1740.o       ehci-hcd.o      libata.o        pdcraid.o       sata_sx4.o      tmscsim.o
ahci.o          fdomain.o       megaraid.o      psi240i.o       sata_uli.o      u14-34f.o
[/tmp]#

When you are dumped to a limited shell try:

insmod /modules/scsi/libdata.o
insmod /modules/scsi/ahci.o
insmod /modules/scsi/ata_piix.o
insmod /modules/scsi/sata_??

See if you get a hit.

HTH
Kerry:
Quote
i think there's a problem with usb, i unplugged my usb mouse to move it to a different usb, so i could stick my usb key in, now the mouse no longer works.

Try unplugging and re-plugging in the console and see if you get any messages. That will also allow you to do a quick dmesg and see what's going on when you remove and re-plug the mouse.

As far as tray buttons go, why not assign those for what are, for most people anyway, the most frequently used menus? One for an internet menu, one for office menu, one for system menu...? (edited for clarity)

For others re: what Robert wrote about device names, there's a difference between device name and mount point. A device's name isn't sda1, that's it's mount point. The two aren't mapped together in 2.4, but they are in udev in 2.6.
http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev_vs_devfs
meo wrote:
Quote
...The boot-floppy doesn't seem to work with the cheatcode "frompcmcia" and since that is what I use I would really appreciate if that could be fixed (or added).


I have updated the bootfloppy.img to include the fromusb & frompcmcia boot options.
I also created a new pcmciafloppy.img that is required when using the frompcmcia option.

Both now posted in the release_candidate area.
Quote (roberts @ Aug. 30 2007,10:09)
Quote (marvinudy @ Aug. 29 2007,13:07)
Robert,

Tried to boot DSL-4.0 rc2 with the 'sata' option and got a 'loading hang' at sata_vsc.0.....

Without the 'sata' option, boots fine but shows my 1st sata drive as hda and of course does not see sdb.  What did I miss?

Best regards,

marvinudy

Intel 6420, GA-965-ds3 r-3, sata Wd 250 & 160 hd, 2Gb pc-6400 memory.

Sorry, cannot say, as I don't own any SATA gear.
Perhaps someone with SATA gear can respond.
Otherwise I would suggest to check irq assignments, maybe try expert mode and load the sata module that corresponds to your hardware.

Without owning any SATA hardware to test, I can only direct you to try a few things...

DSL v4.0 has the kernel supplied SATA modules available during boot as shown in the boot time available modules:

[/tmp]# ls  mroot/modules/scsi/
BusLogic.o      aic7xxx.o       gdth.o          modules.lst     sata_nv.o       sata_via.o      ultrastor.o
NCR53c406a.o    ata_piix.o      hptraid.o       ncr53c8xx.o     sata_promise.o  sata_vsc.o      usb-ohci.o
a100u2w.o       ataraid.o       ide-cd.o        ohci1394.o      sata_qstor.o    sbp2.o          usb-storage.o
advansys.o      atp870u.o       ide-scsi.o      pas16.o         sata_sil.o      seagate.o       usb-uhci.o
aha152x.o       dtc.o           ieee1394.o      pci2000.o       sata_sis.o      silraid.o       usbcore.o
aha1542.o       eata.o          initio.o        pci2220i.o      sata_svw.o      t128.o          wd7000.o
aha1740.o       ehci-hcd.o      libata.o        pdcraid.o       sata_sx4.o      tmscsim.o
ahci.o          fdomain.o       megaraid.o      psi240i.o       sata_uli.o      u14-34f.o
[/tmp]#

When you are dumped to a limited shell try:

insmod /modules/scsi/libdata.o
insmod /modules/scsi/ahci.o
insmod /modules/scsi/ata_piix.o
insmod /modules/scsi/sata_??

See if you get a hit.

HTH

Roberts,

I tried the 'expert' mode with the same result.  Manully, I entered all the mods with no effect.  I'm way over my head technically.  None of the insmod's made a difference.

I 'caught' the following error message on boot= kmod: failed to exec /sbin/modprobe -s -k scsi_hostadaptor, error=2.

Also, during 'autoconfiguring devices the following showed up: modprobe cant locate module block-error-2

Thanks for your input.


marvinudy
Next Page...
original here.