Hi,
Is there any patch or method for using USB to boot linux?
Jason Wang
Intern
Electronic Engineering Lab
Peking University
Beijing Technology Development Center
Advanced Micro Devices(AMD)
E-mail: Qingpei.Wang@amd.com
wangqingpei@hotmail.com
Phone:13426369984
-----Original Message-----
From: coreboot-bounces@coreboot.org
[mailto:coreboot-bounces@coreboot.org] On Behalf Of
coreboot-request@coreboot.org
Sent: Thursday, March 27, 2008 8:20 AM
To: coreboot@coreboot.org
Subject: coreboot Digest, Vol 37, Issue 175
Send coreboot mailing list submissions to
coreboot@coreboot.org
To subscribe or unsubscribe via the World Wide Web, visit
http://www.coreboot.org/mailman/listinfo/coreboot
or, via email, send a message with subject or body 'help' to
coreboot-request@coreboot.org
You can reach the person managing the list at
coreboot-owner@coreboot.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of coreboot digest..."
Today's Topics:
1. Re: ICH Series i82801xx EHCI (USB 2.0) problems (Uwe Hermann)
2. Re: filo booting cd problem (Russell Whitaker)
3. Re: filo booting cd problem (joe@smittys.pointclark.net)
4. Re: ICH Series i82801xx EHCI (USB 2.0) problems
(joe@smittys.pointclark.net)
5. Re: ICH Series i82801xx EHCI (USB 2.0) problems
(joe@smittys.pointclark.net)
6. MIPS Yamon replacement? (Jake Peavy)
7. Re: MIPS Yamon replacement? (Peter Stuge)
8. Re: [RFC] First K8 board to port to v3 (Rudolf Marek)
----------------------------------------------------------------------
Message: 1
Date: Wed, 26 Mar 2008 18:57:51 +0100
From: Uwe Hermann uwe@hermann-uwe.de
Subject: Re: [coreboot] ICH Series i82801xx EHCI (USB 2.0) problems
To: coreboot@coreboot.org
Message-ID: 20080326175751.GE26901@greenwood
Content-Type: text/plain; charset=us-ascii
On Tue, Mar 25, 2008 at 10:12:29PM -0400, joe@smittys.pointclark.net
wrote:
On Tue, Mar 25, 2008 at 06:51:24PM -0400, joe@smittys.pointclark.net
wrote:
I am having a problem getting coreboot->Linux initialize any high
speed USB 2.0 devices like flash drives. The USB works fine on low
Flash drive? You mean mounting a USB thumb drive? That should work
fine,
I tested that on various coreboot boards. Or do you mean an external
IDE/SATA drive which is connected via USB to the computer? I think
both should work fine.
Yes neithor of these are working. I have tried USB thumb drives, and a
IDE-to-USB 2.0 adapter with hard drive and DVD-rom drive.
Hm, that's strange, because the thumb drive should work even with
USB 1.1 only (it sure does on my boards).
Which ports did you try to use? AFAIUI only one or two of them will be
USB 2.0, the other ones have USB 1.1 speed only, no matter which
settings the BIOS uses.
If you can, please test some other high-speed USB device (not thumb
drives or disks).
Note that AFAICT the USB ports _should_ be intialized ok with
coreboot
if the board code is ok, but they might only act as "full speed"
(USB 1.1) devices.
Nope USB 2.0 devices (drives) are not detected at bootup, or by hot
plugging in Linux. USB 1.1 Keyboards, and mice, work fine.
Hm, the kernel init _seems_ to look ok to me, but maybe I'm missing
something.
Loading ehci-hcd.ko module
PCI: Found IRQ 7 for device 0000:00:1d.7
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 4
ehci_hcd 0000:00:1d.7: debug port 1
ehci_hcd 0000:00:1d.7: irq 7, io mem 0xf8180000
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 6 ports detected
Is the IRQ routing correct? If you attach and use USB devices on those
ports, do the numbers in /proc/interrrupts increase?
Not that I am aware, EHCI seems to setup ok in coreboot, except the
devices are not detected by coreboot, filo, or Linux.
What exactly does _not_ work btw?
When Linux is running and I plug in a USB flash drive, the led on the
drive comes on for a few seconds and then turns off, and Linux does
not
detect the drive. I have tried several different brands. They work
fine
with the original bios.
With or without a USB hub? If hub, is it a self-powered hub? Does the
drive get enough power?
Hm, not sure what's going on, maybe someone else can comment? It's
possible that you indeed have to do the init mentioned in the datasheet.
Uwe.
--
http://www.hermann-uwe.de |
http://www.holsham-traders.de
http://www.crazy-hacks.org |
http://www.unmaintained-free-software.org
------------------------------
Message: 2
Date: Wed, 26 Mar 2008 12:03:30 -0700 (PDT)
From: Russell Whitaker
russ@ashlandhome.net
Subject: Re: [coreboot] filo booting cd problem
To: Phani Babu Giddi
phanig@gmail.com
Cc: coreboot@coreboot.org
Message-ID:
Pine.LNX.4.64.0803261149170.4968@bigred.russwhit.org
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
On Wed, 26 Mar 2008, Phani Babu Giddi wrote:
> Yes I am using FILO with USE_GRUB=1 but while FILO is starting I press
the
> 'Esc' key and later I key in the kernel and initrd parameters.
>
> The absolute path is /boot/i386/loader/linux for the kernel image and
> /boot/i386/loader/initrd for the initrd. Ofcourse I would have to add
"hdb:"
> to the path.
>
> -Phani
>
> On Wed, Mar 26, 2008 at 10:12 AM,
joe@smittys.pointclark.net wrote:
>
>> Quoting Phani Babu Giddi
phanig@gmail.com:
>>
>>> # install
>>> label linux
>>> kernel linux
>>> append initrd=initrd splash=silent showopts
>>
On my main box I'm using factory bios + grub.
The kernel image is vmlinuz and is in the /boot directory.
Since I don't need to append any parameters, ny menu.lst looks like:
#grub configuration file
#by default, boot first entry
default 0
timeout 6
#first entry:
title slack.12
kernel (hd0,0)/boot/vmlinuz root=/dev/hda1
#second entry:
[...]
#fifth entry
title memtest86
kernel (hd0,0)/boot/memtest.bin
Note the full path to the kernel.
Hope this helps,
Russ
------------------------------
Message: 3
Date: Wed, 26 Mar 2008 15:30:06 -0400
From: joe@smittys.pointclark.net
Subject: Re: [coreboot] filo booting cd problem
To: Phani Babu Giddi
phanig@gmail.com
Cc: coreboot@coreboot.org
Message-ID:
20080326153006.ecdzlfy6zoo00g4w@www.smittys.pointclark.net
Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes";
format="flowed"
Quoting Phani Babu Giddi
phanig@gmail.com:
> Yes I am using FILO with USE_GRUB=1 but while FILO is starting I press
the
> 'Esc' key and later I key in the kernel and initrd parameters.
>
> The absolute path is /boot/i386/loader/linux for the kernel image and
> /boot/i386/loader/initrd for the initrd. Ofcourse I would have to add
"hdb:"
> to the path.
>
> -Phani
>
> On Wed, Mar 26, 2008 at 10:12 AM,
joe@smittys.pointclark.net wrote:
>
>> Quoting Phani Babu Giddi
phanig@gmail.com:
>>
>> > # install
>> > label linux
>> > kernel linux
>> > append initrd=initrd splash=silent showopts
>>
Ok then. So if it brings you to the filo shell (boot:) you probibly want
this:
boot: hdb:/boot/i386/loader/linux initrd=/boot/i386/loader/initrd
splash=silent showopts console=ttyS0,115200n8
If it brings you to the grub/filo shell (grub>) then you would
probibly want this:
grub>kernel hdb:/boot/i386/loader/linux splash=silent showopts
console=ttyS0,115200n8
Press <Enter>
grub>initrd hdb:/boot/i386/loader/initrd
Press <Enter>
grub>boot
Press <Enter>
Your system will now boot right into the Linux install. Hope that
helps:-)
Thanks - Joe
------------------------------
Message: 4
Date: Wed, 26 Mar 2008 15:43:28 -0400
From: joe@smittys.pointclark.net
Subject: Re: [coreboot] ICH Series i82801xx EHCI (USB 2.0) problems
To: Uwe Hermann
uwe@hermann-uwe.de
Cc: Peter Stuge
peter@stuge.se, coreboot@coreboot.org
Message-ID:
20080326154328.ao9pxp8ogoooos4k@www.smittys.pointclark.net
Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes";
format="flowed"
Quoting Uwe Hermann
uwe@hermann-uwe.de:
> On Wed, Mar 26, 2008 at 08:57:42AM -0400, joe@smittys.pointclark.net
wrote:
>>> Please send lspci from when you've booted with coreboot. Is the EHCI
>>> USB controller there at all? If so, there should be errors during
>>> boot when the ehci driver tries to load.
>>>
>>> (Or worst-case coreboot has done such a bad job at init that the
>>> driver thinks life is good but in fact nothing EHCI works. :()
>
> FWIW, here's the diff. I don't think the missing sybsystem IDs are a
> problem (and that could be fixed very easily anyway),
The strange thing is, the code is already setup to do this but it
doesn't for some reason???
> and the different
> IRQ and mem regions shouldn't be a problem per se either, correct?
Correct, this shouldn't matter.
>
>
>
> Might the SERR difference here cause problems?
Possible?
>
>
>
> The register differences in the EHCI device should probably be
analyzed
> in detail (using datasheet), haven't done that so far.
>
>
The only differences I can see are registers 0x68 and 0x6C.
Register 0x68 (USB EHCI Legacy Support Extended Capability) is
supposed to be read only so I don't get that one. And I am not sure
exactly that the register 0x6C (USB EHCI Legacy Support
Control/Status) has an issue. There is also a "Host Controller
Operational Registers" located in memory, but I am not exactly sure
how to read those.
Thanks - Joe
------------------------------
Message: 5
Date: Wed, 26 Mar 2008 15:51:23 -0400
From: joe@smittys.pointclark.net
Subject: Re: [coreboot] ICH Series i82801xx EHCI (USB 2.0) problems
To: Uwe Hermann
uwe@hermann-uwe.de
Cc: coreboot@coreboot.org
Message-ID:
20080326155123.yrrcso0b4808c00g@www.smittys.pointclark.net
Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes";
format="flowed"
Quoting Uwe Hermann
uwe@hermann-uwe.de:
> On Tue, Mar 25, 2008 at 10:12:29PM -0400, joe@smittys.pointclark.net
wrote:
>>> On Tue, Mar 25, 2008 at 06:51:24PM -0400, joe@smittys.pointclark.net
wrote:
>>>> I am having a problem getting coreboot->Linux initialize any high
>>>> speed USB 2.0 devices like flash drives. The USB works fine on low
>>>
>>> Flash drive? You mean mounting a USB thumb drive? That should work
fine,
>>> I tested that on various coreboot boards. Or do you mean an external
>>> IDE/SATA drive which is connected via USB to the computer? I think
>>> both should work fine.
>>>
>> Yes neithor of these are working. I have tried USB thumb drives, and
a
>> IDE-to-USB 2.0 adapter with hard drive and DVD-rom drive.
>
> Hm, that's strange, because the thumb drive should work even with
> USB 1.1 only (it sure does on my boards).
>
that's what I thought, very strange indeed
>
> Which ports did you try to use? AFAIUI only one or two of them will be
> USB 2.0, the other ones have USB 1.1 speed only, no matter which
> settings the BIOS uses.
>
both
>
> If you can, please test some other high-speed USB device (not thumb
> drives or disks).
>
ok
>
>>> Note that AFAICT the USB ports _should_ be intialized ok with
coreboot
>>> if the board code is ok, but they might only act as "full speed"
>>> (USB 1.1) devices.
>>>
>> Nope USB 2.0 devices (drives) are not detected at bootup, or by hot
>> plugging in Linux. USB 1.1 Keyboards, and mice, work fine.
>
> Hm, the kernel init _seems_ to look ok to me, but maybe I'm missing
> something.
>
Yes, that is why I am stumped:-(
>
> Loading ehci-hcd.ko module
> PCI: Found IRQ 7 for device 0000:00:1d.7
> ehci_hcd 0000:00:1d.7: EHCI Host Controller
> ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 4
> ehci_hcd 0000:00:1d.7: debug port 1
> ehci_hcd 0000:00:1d.7: irq 7, io mem 0xf8180000
> ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
> usb usb4: configuration #1 chosen from 1 choice
> hub 4-0:1.0: USB hub found
> hub 4-0:1.0: 6 ports detected
>
>
> Is the IRQ routing correct?
I think so? I will check this.
>
> If you attach and use USB devices on those
> ports, do the numbers in /proc/interrrupts increase?
>
Well for the keyboard and mouse yes, I have not checked it with a USB
2.0 device, I have not checked that.
>
>
>> Not that I am aware, EHCI seems to setup ok in coreboot, except the
>> devices are not detected by coreboot, filo, or Linux.
>>>
>>> What exactly does _not_ work btw?
>> When Linux is running and I plug in a USB flash drive, the led on the
>> drive comes on for a few seconds and then turns off, and Linux does
not
>> detect the drive. I have tried several different brands. They work
fine
>> with the original bios.
>
> With or without a USB hub? If hub, is it a self-powered hub? Does the
> drive get enough power?
>
No usb hub. Direct connect.
>
>
> Hm, not sure what's going on, maybe someone else can comment?
Please:-(
>
> It's
> possible that you indeed have to do the init mentioned in the
datasheet.
>
Possible, that is why I asked if anyone else was having this problem
and/or can confirm it works.
Thanks - Joe
------------------------------
Message: 6
Date: Wed, 26 Mar 2008 14:05:50 -0600
From: "Jake Peavy"
djstunks@gmail.com
Subject: [coreboot] MIPS Yamon replacement?
To: coreboot@coreboot.org
Message-ID:
c5221b990803261305k280e5c98hb4e67d462c2c4c0e@mail.gmail.com
Content-Type: text/plain; charset="iso-8859-1"
Hi all,
New member here so forgive this question if it's ridiculous.
Has anyone looked at porting Coreboot onto MIPS architecture? Can it be
used as a Yamon replacement?
Thanks,
Jake
--
-jp
If you're in a war, instead of throwing a hand grenade at the enemy,
throw
one of those small pumpkins. Maybe it'll make everyone think how stupid
war
is, and while they are thinking, you can throw a real grenade at them.
deepthoughtsbyjackhandy.com
