@Geri

Here is the tune2fs -l /dev/hde12 - a drive I set up but did NOT get to be recognized by UBOOT:

tune2fs 1.41.12 (17-May-2010)
Filesystem volume name: SQUEEZER
Last mounted on:
Filesystem UUID: 650e2b17-604f-4753-95c3-6ff62a9dc5ab
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index filetype sparse_super large_file
Filesystem flags: unsigned_directory_hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 1613824
Block count: 6448936
Reserved block count: 322446
Free blocks: 5992478
Free inodes: 1556556
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 1022
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8192
Inode blocks per group: 512
Filesystem created: Mon Feb 25 16:10:51 2013
Last mount time: Sat Mar 9 15:36:57 2013
Last write time: Sat Mar 9 15:37:07 2013
Mount count: 5
Maximum mount count: 38
Last checked: Mon Feb 25 16:10:51 2013
Check interval: 15552000 (6 months)
Next check after: Sat Aug 24 17:10:51 2013
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
Default directory hash: half_md4
Directory Hash Seed: be21b6e5-734a-41ce-bf98-6f734c0080e9
Journal backup: inode blocks

_________________
AmigaOne uA1-c 512M RAM - Only Amiga Makes It Possible!
Check my blog AmigaOne Computing

@scabit

Thanks!

Just to avoid misunderstandings: the slb_v2 directly loads the boot image from these partitions, right? Or do you use a separate boot partition where the a1boot.conf file and the Linux boot images reside?

_________________
A1SE: G3@600MHz, 2GB, 1GBit network card
A1XE: G4@933MHz, 2GB, refitted AC'97 codec
microA1: G3@800MHz, 1GB

- A1 Linux support -

@Geri

Quote:

the slb_v2 directly loads the boot image from these partitions, right?

Well, I believe so. I have the complete boot directory on my HDA4 for example which contains an a1boot.conf that lists this:

Squeeze_HDA10UUID /boot/boot.img.amigaone-2.6.31-1-powerpc root=UUID=c22ab024-28a7-42c4-9fb1-c07e3ff5e170 console=tty0

Squeeze_HDA4UUID /boot/boot.img.amigaone-2.6.31-1-powerpc root=UUID=e7572362-7ea5-494e-8ae4-5faaf73822df console=tty0

Squeeze_HDA4 /boot/boot.img.amigaone-2.6.31-1-powerpc root=/dev/hda4 console=tty0

Squeeze /boot/boot.img.amigaone-2.6.31-1-powerpc root=LABEL=SQUEEZE console=tty0

The first entry HDA10UUID is the one that I boot from. The UUID is for my hda10 drive which is NOT seen by uboot - that is, without hda4 (which was formatted using Lenny) hda10's a1boot.conf is not seen by uboot. Question...given the command line I have for HDA10UUID, does this line cause the amigaone boot image to be loaded from the current partition (i.e. hda4) or from the target path (hda10 via UUID)?

_________________
AmigaOne uA1-c 512M RAM - Only Amiga Makes It Possible!
Check my blog AmigaOne Computing

@Geri
@Hypex

Using the UBOOT pci display.b command, I have determined the following register values for my syba card USB I/O, where 08 is the device id, 00 and 01 are uhci and 02 is ehci registers:
-----------addr / value
00.08.00 41 10
00.08.01 41 10
00.08.02 41 00

00.08.02 40 00

00.08.02 49 20

00.08.02 4b 09

I have tried settings various combinations of thse 6 registers to the values Geri suggested and what we saw from the USB2 specs, but although I can cause different effects (for example, I can get errors starting up USB in Squeeze), or can cause Squeeze to not see USB devices (and not lock up) when they are plugged in, I have not yet gotten a successful combination to get USB2 working properly.
How would I use the Debian command setpci to read these values to see what they get changed to in Debian? THen we can know what is being modified by the kernel.

Thanks!

Last edited by scabit on 14-Mar-2013 at 08:18 PM.
Last edited by scabit on 14-Mar-2013 at 08:18 PM.

_________________
AmigaOne uA1-c 512M RAM - Only Amiga Makes It Possible!
Check my blog AmigaOne Computing

Okay, here are some of the combinations I have tried for getting the USB2 ports on the syba PCI card to work. Remember, I don't know which of these may be getting set by the Debian kernel 2.6.31-1, so it may be that some of these changes would work but for how they are being initialized in the kernel modules.
In general, all of these attempts fail, mostly with the effect of having Debian lock up completely whenever a USB device is plugged into one of the Syba VIA USB2 ports, which is just how it behaves when none of these changes are made. Note - each time I made a change I undid my previous changes and set them back to the default values.
Remember, my device ID for the USB on the syba card is 08.

1) 00.08.02 40 80 - usb_usb2:can't set config #, error 108
......................................uhci_hcd 0000:00:08.0: HC died (messages in Debian boot, debian halts boot process)

2) 00.08.02 49 40 - debian boots ok, locks up when USB device inserted

3) 00.08.02 49 80 - debian boots. no longer locks up when USB devices plugged in, but USB devices are not seen!

4) 00.08.02 49 80 + 00.08.02 4b 29 - debian boots ok, locks up when USB device plugged in to USB

5) 00.08.02 41 10 - debian boots, locks up when USB device inserted

6) 00.08.02 41 10 + 00.08.00 41 00 + 00.08.01 41 00 - debian boots, locks up with USB device insert

7) 00.08.00 41 00 + 00.08.01 41 00 + 00.08.02 41 10 + 00.08.02 49 00 + 00.08.02 4b 29 + 00.08.02 40 80 - debian boots, locks up with USB device insert

8) 00.08.02 49 c0 + 00.08.02 4b 29 - debian boots, locks with USB device insert

9) 00.08.02 4b 29 - debian boots, locks with USB device insert

Another note - I did not try removing the 3com device from the load modules because I noticed that the 3com device uses interrupt 7 (via lspci -v). This is not used by any of the USB ports!

Here are my debian squeeze kernel 2.6.31-1 interrupts:

IRQ device
10 audio controller
11 modem AC 97
11 radeon ATI graphics
11 USB 2 controller on syba
9 RAID/IDE controller on syba
9 USB 1.1 on syba
10 USB 1.1 on syba
7 Ethernet 3com

So the 3com device does not use the same interrupt in Squeeze as any of the USB I/O. However, the USB I/O shares the same interrupts as both the Radeon video and the AC'97 controller. I can;t disable the onboard video (the only video I have) to get USB 2 working!

_________________
AmigaOne uA1-c 512M RAM - Only Amiga Makes It Possible!
Check my blog AmigaOne Computing

Bump

_________________
AmigaOne uA1-c 512M RAM - Only Amiga Makes It Possible!
Check my blog AmigaOne Computing

@scabit

Sorry, I had to take a break over the weekend.

Regarding the SATA link error: did you check the cabling? Did you use the IDE to SATA converter with the Syba card also under kernel 2.6.18?

_________________
A1SE: G3@600MHz, 2GB, 1GBit network card
A1XE: G4@933MHz, 2GB, refitted AC'97 codec
microA1: G3@800MHz, 1GB

- A1 Linux support -

@Geri

Quote:

Regarding the SATA link error: did you check the cabling? Did you use the IDE to SATA converter with the Syba card also under kernel 2.6.18?

I believe that I connected everything the same way as I did with Lenny using kernel 2.6.18. I guess I can double check and verify that for you.


Seems that now that the PATA/RAID IDE I/O works in Squeeze on the Syba card, the remaining issues are simply:
1) Get the SATA Stuff that worked in LEnny working in Squeeze
2) Coerce USB2 into working

and also possibly

3) Figure out why the Squeeze partitioner formats partitions that UBOOT does not recognize as valid.

Scott

_________________
AmigaOne uA1-c 512M RAM - Only Amiga Makes It Possible!
Check my blog AmigaOne Computing

@scabit

Quote:

scabit wrote: @Geri Seems that now that the PATA/RAID IDE I/O works in Squeeze on the Syba card, the remaining issues are simply: 1) Get the SATA Stuff that worked in LEnny working in Squeeze 2) Coerce USB2 into working

Can you also give the 2.6.32 or 3.2 kernel a try for these two items? The post with the installation instructions for the Debian kernel package in this thread is up to date. Also the kernels can coexist with the 2.6.31 kernel.

The kernel log you sent me reports a problem with the loading order of the uhci/ehci_hcd modules that seems to be fixed with the 2.6.32 kernel here. It would be good, if this is working before any real tests with USB2.0 are done.

Quote:

3) Figure out why the Squeeze partitioner formats partitions that UBOOT does not recognize as valid.

Yes, I already planned to do some tests for this next week on my A1SE (using different versions of mke2fs).

_________________
A1SE: G3@600MHz, 2GB, 1GBit network card
A1XE: G4@933MHz, 2GB, refitted AC'97 codec
microA1: G3@800MHz, 1GB

- A1 Linux support -

@Geri

with the new kernel no more reboots but again stuck after the initdram loading message..

_________________
--------------------------------------
Search and Destroy
---------------------------------------

@Geri

Quote:

Can you also give the 2.6.32 or 3.2 kernel a try for these two items?

I downloaded the kernel 2.6.32-48 dated 3-10-13 and installed it using "dpkg --install xxxx.deb" on my Squeeze root partition. I then copied the kernel image, map and other files from the root /boot directory to my hda2 /boot directory which was formatted under Lenny and modified the a1boot.conf to add a squeeze32 entry pointing to the hda10 root drive, just as i did with squeeze kernel 2.6.18 (which works).
Upon booting into kernel 2.6.32 I get the following:

no filesystem could mount root, tried
kernel panic - not syncing: unable to mount root filesystem on unknown block (0,0);

thats it.

Do I need to do a depmod or something else after the dpkg --install of this kernel .deb file to get it all to work? Am I using the right version (3-10-13) or should I use an earlier one?

Thanks, let me know!

Scott

_________________
AmigaOne uA1-c 512M RAM - Only Amiga Makes It Possible!
Check my blog AmigaOne Computing

@damned

Quote:

damned wrote: @Geri with the new kernel no more reboots but again stuck after the initdram loading message..

Strange! Any chance to get a debug output that shows some messages of the IDE/SATA drivers? Maybe just a picture? Otherwise I'm in the dark.

BTW: Normally the initramfs offers you to run a shell, if no root partition could be mounted. This allows you to examine the boot process.

@scabit

Quote:

scabit wrote: @Geri Quote: Can you also give the 2.6.32 or 3.2 kernel a try for these two items? I downloaded the kernel 2.6.32-48 dated 3-10-13 and installed it using "dpkg --install xxxx.deb" on my Squeeze root partition. I then copied the kernel image, map and other files from the root /boot directory to my hda2 /boot directory which was formatted under Lenny and modified the a1boot.conf to add a squeeze32 entry pointing to the hda10 root drive, just as i did with squeeze kernel 2.6.18 (which works). Upon booting into kernel 2.6.32 I get the following: no filesystem could mount root, tried kernel panic - not syncing: unable to mount root filesystem on unknown block (0,0); thats it. Do I need to do a depmod or something else after the dpkg --install of this kernel .deb file to get it all to work? Am I using the right version (3-10-13) or should I use an earlier one?

Did you exactly follow the installation instructions described here? Let me know, if there is something unclear!

Last edited by Geri on 19-Mar-2013 at 10:35 AM.

_________________
A1SE: G3@600MHz, 2GB, 1GBit network card
A1XE: G4@933MHz, 2GB, refitted AC'97 codec
microA1: G3@800MHz, 1GB

- A1 Linux support -

@Geri

Quote:

Save the following text in "/etc/initramfs-tools/modules":

Okay, I did the dpkg --install of the linux-image-2.6.32-5 etc etc

But there is not any directory named /etc/initramfs-tools! I can create it and copy your modules file into it, but I cannot edit the initramfs.conf file because it doesn't exist!

Any idea why the install of the kernel.deb does not create a /etc/initramfs-tools directory?

Thanks,

Scott

_________________
AmigaOne uA1-c 512M RAM - Only Amiga Makes It Possible!
Check my blog AmigaOne Computing

@scabit

Quote:

scabit wrote: @Geri Quote: Save the following text in "/etc/initramfs-tools/modules": Okay, I did the dpkg --install of the linux-image-2.6.32-5 etc etc But there is not any directory named /etc/initramfs-tools! I can create it and copy your modules file into it, but I cannot edit the initramfs.conf file because it doesn't exist! Any idea why the install of the kernel.deb does not create a /etc/initramfs-tools directory?

It's created by the initramfs-tools package, which doesn't seem to be installed. Please try to install this package with:

Quote:

$ apt-get install initramfs-tools

_________________
A1SE: G3@600MHz, 2GB, 1GBit network card
A1XE: G4@933MHz, 2GB, refitted AC'97 codec
microA1: G3@800MHz, 1GB

- A1 Linux support -

@Geri


Quote:

apt-get install initramfs-tools

Okay...duh. Installed it, as well as uboot-mkimage, went through all your steps to build the kernel image, and have now booted successfully into Squeeze Kernel 2.6.32-5-book3s-amigaone (as per uname -r).

Wohoo!

Checked the onboard micro A1 USB ports first - before installing the Syba card (still using the sil0680 controller) and both front and rear internal USB ports seem to work fine - used a memory stick to download large files from both front and rear USB ports...no errors.

Now to plug in the Syba card....

_________________
AmigaOne uA1-c 512M RAM - Only Amiga Makes It Possible!
Check my blog AmigaOne Computing

@scabit

Quote:

scabit wrote: @Geri Quote: apt-get install initramfs-tools Okay...duh. Installed it, as well as uboot-mkimage, went through all your steps to build the kernel image, and have now booted successfully into Squeeze Kernel 2.6.32-5-book3s-amigaone (as per uname -r). Wohoo!

Quote:

Checked the onboard micro A1 USB ports first - before installing the Syba card (still using the sil0680 controller) and both front and rear internal USB ports seem to work fine - used a memory stick to download large files from both front and rear USB ports...no errors.

Okay, please post the kernel log when you switched the card so that I can check, if the ehci/uhci_hcd module loading oder problem disappeared (or send it as an e-mail).

_________________
A1SE: G3@600MHz, 2GB, 1GBit network card
A1XE: G4@933MHz, 2GB, refitted AC'97 codec
microA1: G3@800MHz, 1GB

- A1 Linux support -

@Geri

I'll email you the kernel log using dmesg shortly.

Hooked the Syba card up, added my VSATA ubbot commands to run before loading Linux, and wired the Syba Raid/PATA port to my working IDE drive.
Squeeze Kernel 32 sees my IDE and DVD drives on the Syba card PATA interface...however, whereas in LEnny drive partitions were listed as hde1, hde2 and hde4...in Squeeze with kernel 32 they are listed as sda1, sda2 and sda4. They still work fine.
Verified both internal micro USB ports work okay - front and rear both work with a memory stick. Neither is turned off in uboot (yet).
Plug the memory stick into the Syba USB2 port - Squeeze locks up cold.
Powered down, unplugged the RAID/PATA connections from the Syba card and plugged in the SATA connections on the same IDE drive as used on the RAID/PATA port, only now with a SATA to IDE converter.
Boot Squeeze with kernel 32. See some SATA link errors - slow to respond. errno -16 and several retries with delays. Finally boots up but with SATA interface failed.

I went to try to change the local.conf file in /etc/modprobe.d to add the line options sata_sil slow_down=1 but this file looks like this:

# Local module settings
# Created by the Debian installer

options ide_core nodma=0.0 nodma=0.1 nodma=1.0 nodma=1.1

Not like you show in your previous post. I'll try adding the line anyway.
I'll also try turning off the internal USB ports in uboot for the micro and let you know.

Scott

_________________
AmigaOne uA1-c 512M RAM - Only Amiga Makes It Possible!
Check my blog AmigaOne Computing

@scabit

Quote:

scabit wrote: @Geri Hooked the Syba card up, added my VSATA ubbot commands to run before loading Linux, and wired the Syba Raid/PATA port to my working IDE drive. Squeeze Kernel 32 sees my IDE and DVD drives on the Syba card PATA interface...however, whereas in LEnny drive partitions were listed as hde1, hde2 and hde4...in Squeeze with kernel 32 they are listed as sda1, sda2 and sda4. They still work fine.

Well, but under Lenny they were connected to a Sil0680 controller, right? This controller uses an IDE driver in Debian Squeeze and older releases. The VIA controller however is handled by a libata driver, which enumerates devices like the SCSI subsystem (sdx...harddisk, sr...CDROM, etc.). So the partition names are fine.

Quote:

Verified both internal micro USB ports work okay - front and rear both work with a memory stick. Neither is turned off in uboot (yet).

Okay. Also the ehci/uhci_hcd module ordering problem is gone with this kernel version.

Quote:

Plug the memory stick into the Syba USB2 port - Squeeze locks up cold.

To be honest I didn't expect that the new kernel would fix this, but you could give the hardware workaround another try now that the module ordering problem is fixed.

Quote:

Powered down, unplugged the RAID/PATA connections from the Syba card and plugged in the SATA connections on the same IDE drive as used on the RAID/PATA port, only now with a SATA to IDE converter. Boot Squeeze with kernel 32. See some SATA link errors - slow to respond. errno -16 and several retries with delays. Finally boots up but with SATA interface failed.

People report problems like this for several SATA controllers and a wide range of kernel versions (from 2.6.17 to 2.6.35 AFAICT). However it looks like nobody found a solution. I can only propose to play around with another kernel version or some libata kernel parameters:

1. Try it with the "3.2.0-0.bpo.4-book3s-amigaone+" kernel package. The installation procedure should be the same as for the 2.6.32 kernel. You only have to create a new /boot/mkbootimg* script with the adapted names for the cuImage, initramfs and the final boot image and add a new entry to the a1boot.conf file.

2. Play with some libata.force options:
Quote:

libata.force= [LIBATA] Force configurations. The format is comma separated list of "[ID:]VAL" where ID is PORT[.DEVICE]. PORT and DEVICE are decimal numbers matching port, link or device. Basically, it matches the ATA ID string printed on console by libata. If the whole ID part is omitted, the last PORT and DEVICE values are used. If ID hasn't been specified yet, the configuration applies to all ports, links and devices. If only DEVICE is omitted, the parameter applies to the port and all links and devices behind it. DEVICE number of 0 either selects the first device or the first fan-out link behind PMP device. It does not select the host link. DEVICE number of 15 selects the host link and device attached to it. The VAL specifies the configuration to force. As long as there's no ambiguity shortcut notation is allowed. For example, both 1.5 and 1.5G would work for 1.5Gbps. The following configurations can be forced. * Cable type: 40c, 80c, short40c, unk, ign or sata. Any ID with matching PORT is used. * SATA link speed limit: 1.5Gbps or 3.0Gbps. * Transfer mode: pio[0-7], mwdma[0-4] and udma[0-7]. udma[/][16,25,33,44,66,100,133] notation is also allowed. * [no]ncq: Turn on or off NCQ. * nohrst, nosrst, norst: suppress hard, soft and both resets. * rstonce: only attempt one reset during hot-unplug link recovery * dump_id: dump IDENTIFY data. If there are multiple matching configurations changing the same attribute, the last one is used.

You could for example force the SATA speed to 1.5Gbps and turn off NCQ with libata.force=1.5G,noncq. I would also play with the "*rst*" options.

Quote:

I went to try to change the local.conf file in /etc/modprobe.d to add the line options sata_sil slow_down=1 but this file looks like this:

The "slow_down" option is only for the sata_sil driver (sil3112, sil 3114 controller). The sata_via driver will not make use of it.

Quote:

# Local module settings # Created by the Debian installer options ide_core nodma=0.0 nodma=0.1 nodma=1.0 nodma=1.1 Not like you show in your previous post. I'll try adding the line anyway.

Well, this was added automatically by the Debian installer. However the ide_core module is directly compiled into the kernel so the options in the local.conf file wont have any effect (you would have to add them to the kernel command line).
But you should definitely add the line for the onboard ethernet! Otherwise the system will lock up on large data transfers over the network.

Quote:

I'll also try turning off the internal USB ports in uboot for the micro and let you know.

The kernel will still recognize the internal USB ports, even if they are switched off in U-Boot. You would have to blacklist the uhci_hcd module to get rid of them. Naturally/unfortunately that also disables the USB1.1 ports on your Syba card.

_________________
A1SE: G3@600MHz, 2GB, 1GBit network card
A1XE: G4@933MHz, 2GB, refitted AC'97 codec
microA1: G3@800MHz, 1GB

- A1 Linux support -

@Geri

Quote:

Well, but under Lenny they were connected to a Sil0680 controller, right?

No, remember, I have only a single PCI slot. Under Squeeze kernel 31, with the Syba card in my PCI slot, the drives connected to the PATA bus of the Syba card are shows as hde1,hde2,hde4. Under Squeeze with kernel 32 they are seen as sda1,sda2 and sda4.

When i got the SATA to work in Lenny, it was because the Syba card was in the PCI slot, and I was booting (as I am now in Squeeze) from the internal micro IDE bus. The hardware configuration when Lenny identified the SATA drives as sda1,sda2 and sda4 was identical to what I am trying now to do with Squeeze.

I think (but may be wrong) that in my current setup - i.e. Syba card in PCI slot, no SIL, booting from internal IDE in microA1, the Syba PATA/RAID port devices should show up as hdeX and the SATA drives should show up as sdaX .... no? That is what I was expecting.

Quote:

Also the ehci/uhci_hcd module ordering problem is gone with this kernel version.

Hurray! Perhaps now I can try the USB2 uboot modifications....

Quote:

2. Play with some libata.force options

It makes sense to me to try option #2 first. I'll see if I can discover where this file exists and make the changes you suggest and see what happens.

Quote:

But you should definitely add the line for the onboard ethernet! Otherwise the system will lock up on large data transfers over the network.

Hmmmm...interesting. I'll test that out. So far I haven't seen any lockups due to large downloads - I just downloaded some huge stuff to install a vector graphics drawing program in Squeeze that was supposed to (but doesn't) recognize .eps files.

Quote:

The kernel will still recognize the internal USB ports, even if they are switched off in U-Boot.

Pesky. I'll verify that that is true. I seem to recall that having the internal USB ports on somehow conflicted with the Syba USB ports.

I'll let you know what I find.

Thanks!

_________________
AmigaOne uA1-c 512M RAM - Only Amiga Makes It Possible!
Check my blog AmigaOne Computing

@Geri

Okay, I just rebooted into Squeeze using kernel 2.6.31-1 and it looks like the RAID/PATA drives are being seen as sda1,sda2 and sda4! I KNOW that when I did this a couple weeks ago using the exact same hardware configuration and kernel image, they were hde1,hde2 amd hde4.

What exactly determines the name that is assigned to a hard drive?

_________________
AmigaOne uA1-c 512M RAM - Only Amiga Makes It Possible!
Check my blog AmigaOne Computing