Menu
▾
▴
mactel-linux-devel — mactel-linux Development
You can subscribe to this list here.
| 2006 |
Jan
|
Feb
(4) |
Mar
(135) |
Apr
(130) |
May
(82) |
Jun
(101) |
Jul
(75) |
Aug
(37) |
Sep
(28) |
Oct
(45) |
Nov
(114) |
Dec
(27) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2007 |
Jan
(22) |
Feb
(60) |
Mar
(81) |
Apr
(120) |
May
(29) |
Jun
(50) |
Jul
(67) |
Aug
(41) |
Sep
(36) |
Oct
(4) |
Nov
(4) |
Dec
|
| 2008 |
Jan
(5) |
Feb
(17) |
Mar
(5) |
Apr
(6) |
May
(5) |
Jun
(9) |
Jul
(5) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(6) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Matthew G. <mj...@sr...> - 2006-04-06 11:40:54
|
On Thu, Apr 06, 2006 at 01:23:25PM +0200, Tino Keitel wrote: > The Mini has Intel onboard graphics (i945G, also called GMA950), which > should be supported by XOrg. Only if you use the legacy bios support, since the driver currently uses the BIOS for mode setting. -- Matthew Garrett | mj...@sr... |
|
From: Tino K. <tin...@gm...> - 2006-04-06 11:23:33
|
On Thu, Apr 06, 2006 at 13:20:27 +0300, Panayotis Katsaloulis wrote: > On 4/6/06, Matthew Garrett <mj...@sr...> wrote: > > On Thu, Apr 06, 2006 at 12:36:43PM +0300, Panayotis Katsaloulis wrote: > > > > > They have accelerated drivers. Which means that having accelerated > > > drivers for Linux shouldn't be too far. > > > > That's something of a logical leap, but as it happens you're right that > > accelerated graphics support isn't too far away. It doesn't have > > anything to do with the Windows drivers, though. > > Not per se, but since there was an issue with the missing BIOS, since > now (with all that concept of including CSM after all) this is not an > issue, I suspect that there will be more easily produced drivers for > this card, either binary-only accelerated from ATI or not. The Mini has Intel onboard graphics (i945G, also called GMA950), which should be supported by XOrg. Regards, Tino |
|
From: Thomas G. <sit...@st...> - 2006-04-06 10:34:24
|
Hello,
> Yeah, that's what I wanted to say. Ordinary BIOS implementations have
> the possibility to intercept reads of the PS/2 controller, trap into
> System Management Mode and emulate the PS/2 keyboard by accessing the
> USB one.
that isn't the case. The BIOS has function calls which allow
applications in real mode to retrieve keystrokes without asking the
keyboard controller directly - and the bios can of course access the
keyboard controller or a usb device or both. But the BIOS doesn't
intercept the access on the io bus to keyboard to controller to fake in
usb keystrokes.
> They do? Have you tried a Bluetooth keyboard and it works in, like,
> LILO?
Otherwise it wouldn't be case, would it?
Thomas
|
|
From: Matthew G. <mj...@sr...> - 2006-04-06 10:26:03
|
On Thu, Apr 06, 2006 at 01:19:03PM +0300, Panayotis Katsaloulis wrote: > Not per se, but since there was an issue with the missing BIOS, since > now (with all that concept of including CSM after all) this is not an > issue, I suspect that there will be more easily produced drivers for > this card, either binary-only accelerated from ATI or not. The missing BIOS isn't an issue for the ATI hardware, at least as far as the free drivers go - I've no idea about ATI's binary ones. For the Intel hardware, http://lists.freedesktop.org/archives/xorg/2006-April/014555.html removes almost all of the need for the BIOS - there's a couple of code paths that still need some work, but other than that it's good. -- Matthew Garrett | mj...@sr... |
|
From: Panayotis K. <pan...@pa...> - 2006-04-06 10:20:45
|
T24gNC82LzA2LCBNYXR0aGV3IEdhcnJldHQgPG1qZzU5QHNyY2YudWNhbS5vcmc+IHdyb3RlOgo+ IE9uIFRodSwgQXByIDA2LCAyMDA2IGF0IDEyOjM2OjQzUE0gKzAzMDAsIFBhbmF5b3RpcyBLYXRz YWxvdWxpcyB3cm90ZToKPgo+ID4gVGhleSBoYXZlIGFjY2VsZXJhdGVkIGRyaXZlcnMuIFdoaWNo IG1lYW5zIHRoYXQgaGF2aW5nIGFjY2VsZXJhdGVkCj4gPiBkcml2ZXJzIGZvciBMaW51eCBzaG91 bGRuJ3QgYmUgdG9vIGZhci4KPgo+IFRoYXQncyBzb21ldGhpbmcgb2YgYSBsb2dpY2FsIGxlYXAs IGJ1dCBhcyBpdCBoYXBwZW5zIHlvdSdyZSByaWdodCB0aGF0Cj4gYWNjZWxlcmF0ZWQgZ3JhcGhp Y3Mgc3VwcG9ydCBpc24ndCB0b28gZmFyIGF3YXkuIEl0IGRvZXNuJ3QgaGF2ZQo+IGFueXRoaW5n IHRvIGRvIHdpdGggdGhlIFdpbmRvd3MgZHJpdmVycywgdGhvdWdoLgoKTm90IHBlciBzZSwgYnV0 IHNpbmNlIHRoZXJlIHdhcyBhbiBpc3N1ZSB3aXRoIHRoZSBtaXNzaW5nIEJJT1MsIHNpbmNlCm5v dyAod2l0aCBhbGwgdGhhdCBjb25jZXB0IG9mIGluY2x1ZGluZyBDU00gYWZ0ZXIgYWxsKSAgdGhp cyBpcyBub3QgYW4KaXNzdWUsIEkgc3VzcGVjdCB0aGF0IHRoZXJlIHdpbGwgYmUgbW9yZSBlYXNp bHkgcHJvZHVjZWQgZHJpdmVycyBmb3IKdGhpcyBjYXJkLCBlaXRoZXIgYmluYXJ5LW9ubHkgYWNj ZWxlcmF0ZWQgZnJvbSBBVEkgb3Igbm90LgotLQpQYW5heW90aXMK |
|
From: Matthew G. <mj...@sr...> - 2006-04-06 10:02:20
|
On Thu, Apr 06, 2006 at 12:36:43PM +0300, Panayotis Katsaloulis wrote: > They have accelerated drivers. Which means that having accelerated > drivers for Linux shouldn't be too far. That's something of a logical leap, but as it happens you're right that accelerated graphics support isn't too far away. It doesn't have anything to do with the Windows drivers, though. -- Matthew Garrett | mj...@sr... |
|
From: Panayotis K. <pan...@pa...> - 2006-04-06 09:36:53
|
T24gNC82LzA2LCBUaW5vIEtlaXRlbCA8dGluby5rZWl0ZWxAdGlrZWkuZGU+IHdyb3RlOgo+Cj4g SSdtIG9ubHkgd2FpdGluZyBmb3IgbmF0aXZlIGdyYXBoaWNzIG9uIHRoZSBNaW5pLCBzbyBoZWFk aW5nIGFueQo+IHBvc2l0aXZlIG5ld3MgcmVnYXJkaW5nIHRoaXMgd291bGQgYmUgZ3JlYXQuIERv ZXMgYW55b25lIGtub3cgaG93IHRoZQo+IFdpbmRvd3MgWFAgaW5zdGFsbGF0aW9uIGhhbmRsZXMg dGhlIGdyYXBoaWNzIGNoaXBzZXQ/Cj4KClRoZXkgaGF2ZSBhY2NlbGVyYXRlZCBkcml2ZXJzLiBX aGljaCBtZWFucyB0aGF0IGhhdmluZyBhY2NlbGVyYXRlZApkcml2ZXJzIGZvciBMaW51eCBzaG91 bGRuJ3QgYmUgdG9vIGZhci4KCi0tClBhbmF5b3Rpcwo= |
|
From: Tino K. <tin...@ti...> - 2006-04-06 09:31:14
|
On Wed, Apr 05, 2006 at 20:11:07 +0200, Thomas Glanzmann wrote: > Hello, > as someone tried the Mac Mini Firmware Update which comes with a BIOS > emulation? > > http://www.apple.com/support/downloads/macminiintelfirmwareupdate10.html > http://wsidecar.apple.com/cgi-bin/nph-reg3rdpty1.pl/product=10072&cat=1&platform=osx&method=sa/MacMiniFirmwareUpdater.dmg > > I will give it a try as soon as I gets hands on my mac mini tomorrow > morning. Hopefully it comes with an VGA Bios as well maybe X works > accelerated with that one, too? I'm only waiting for native graphics on the Mini, so heading any positive news regarding this would be great. Does anyone know how the Windows XP installation handles the graphics chipset? Regards, Tino |
|
From: Vincent R. <vin...@fr...> - 2006-04-06 08:29:31
|
Hi Michael, Michael Steil wrote: > On Apr 6, 2006, at 8:00 AM, Thomas Glanzmann wrote: [...] >> Btw. Bluetooth keyboards get >> simulated as USB HID devices by the Firmware somehow. > > They do? Have you tried a Bluetooth keyboard and it works in, like, LILO? I did not try the new firmware update but can confirm that my BT keyboards works from LILO/rEFIt. Thomas' assumption makes sense to me as I only get the first mactel liveCD version to work. It does not seem to load any BT modules with the kernel so I guess the firmware does the job behind the scenes. The second liveCD version on the other hand, does not work. I can clearly see my keyboard ceasing to work as soon as the kernel prints out its messages about the BT modules/subsystem being loaded. That's why I have been trying to rebuild my kernel to move out the BT drivers yet included the latest FS patches. Vincent -- Reclaim Your Inbox! http://www.mozilla.org/products/thunderbird |
|
From: Michael S. <mi...@c6...> - 2006-04-06 07:59:54
|
On Apr 6, 2006, at 8:00 AM, Thomas Glanzmann wrote: >> It seems like the BIOS doesn't have support for USB to PS/2 >> conversion via SMM, it just provides the INT hooks, and as soon as >> someone wants to access the PS/2 keyboard directly, it doesn't work >> any more. > > that is because the Mac Mini hasn't a keyboard controller. It is that > simple. If an OS polls the keyboard via BIOS function it works, if it > ask the nonexisting keyboard controller you're out of luck. So you > need > an operating system that supports USB HID. Yeah, that's what I wanted to say. Ordinary BIOS implementations have the possibility to intercept reads of the PS/2 controller, trap into System Management Mode and emulate the PS/2 keyboard by accessing the USB one. It's just odd that Apple's CSM doesn't seem to have this feature - didn't they just buy a BIOS? Why implement their own, stripped down one? If you boot into windows, run "debug" and enter "d f000:0000" and then enter "d" repeatedly, you can see the BIOS. I didn't see any interesting strings, but I think I should dump it properly and try again. At c000:0000, there's the video BIOS, and it's clearly Intel's on the Mac mini; it has lots of Intel strings in it. > Btw. Bluetooth keyboards get > simulated as USB HID devices by the Firmware somehow. They do? Have you tried a Bluetooth keyboard and it works in, like, LILO? Michael |
|
From: Thomas G. <sit...@st...> - 2006-04-06 06:01:46
|
Hello,
> It seems like the BIOS doesn't have support for USB to PS/2
> conversion via SMM, it just provides the INT hooks, and as soon as
> someone wants to access the PS/2 keyboard directly, it doesn't work
> any more.
that is because the Mac Mini hasn't a keyboard controller. It is that
simple. If an OS polls the keyboard via BIOS function it works, if it
ask the nonexisting keyboard controller you're out of luck. So you need
an operating system that supports USB HID. Btw. Bluetooth keyboards get
simulated as USB HID devices by the Firmware somehow.
Thomas
|
|
From: David B. <da...@da...> - 2006-04-06 03:21:27
|
On Thu, Apr 06, 2006 at 12:54:32AM +0200, Michael Steil wrote: > I assume the EFI chooser detects a partition table and a partition > marked "active" (and perhaps with the 0x55AA signature on the first > sector of that partition) and presents a disk called "Windows" to the > user. If it's selected, EFI starts the BIOS. I can imagine no end of horror if these two partition tables get out of sync. I just upgraded the firmware on my Mini. I now have an old-style partition table at the beginning of the disk. It is of type 'ee' 'EFI GPT' which makes sense. I'm guessing that the proper partition tools will shrink the EFI partition appropriately. I was able to boot Knoppix, but much of the hardware wasn't all that exciting. The framebuffer was 1024x768 using the vesa driver in X. It didn't find the network device so it wasn't all that useful. The firmware upgrade did seem to now decide that rEFIt should be the partition to boot, which is nicer than having to hold down 'Option' to be able to choose. Dave |
|
From: Michael S. <mi...@c6...> - 2006-04-05 23:32:50
|
I just tried to boot several operating systems in my collection: * QNX said "press ESC to boot alternate OS" but didn't react on ESC * the Win98 CD shows the menus from config.sys and lets me choose something, but the keyboard is dead when reaching the prompt * Darwin doesn't boot, I get a blinking cursor. * Yellowtab Zeta crashes somewhere between the booter and the OS... It seems like the BIOS doesn't have support for USB to PS/2 conversion via SMM, it just provides the INT hooks, and as soon as someone wants to access the PS/2 keyboard directly, it doesn't work any more. Michael |
|
From: Michael S. <mi...@c6...> - 2006-04-05 22:54:45
|
On Apr 6, 2006, at 12:21 AM, Jimmy Kaplowitz wrote: > Has anyone figured out how Apple sets up Windows XP to be bootable > from > the firmware graphical boot manager when installed via Boot Camp? This > appears to be key, since if I understand the process correctly none of > the drivers on the Macintosh Driver CD from Boot Camp are needed to > make > Windows boot (as it presumably does the first time after the WinXP > installer > completes). After installing Windows XP, there's a regular partition table on sector 0 - this region is unused by EFI for exactly that reason. I assume the EFI chooser detects a partition table and a partition marked "active" (and perhaps with the 0x55AA signature on the first sector of that partition) and presents a disk called "Windows" to the user. If it's selected, EFI starts the BIOS. Michael |
|
From: Christoph P. <cp...@ch...> - 2006-04-05 22:43:54
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Jimmy, > On Wed, Apr 05, 2006 at 08:21:07PM +0100, Matthew Garrett wrote: >> Unfortunately, while it's easy enough to boot a machine this way, >> it's >> less obvious how we're going to boot an installed Linux >> afterwards. You >> don't appear to be able to access EFI if you've booted in this >> way, so >> the nvram can't be pointed at elilo or refit. > > Has anyone figured out how Apple sets up Windows XP to be bootable > from > the firmware graphical boot manager when installed via Boot Camp? This > appears to be key, since if I understand the process correctly none of > the drivers on the Macintosh Driver CD from Boot Camp are needed to > make > Windows boot (as it presumably does the first time after the WinXP > installer > completes). From what I've learned so far, the actual Boot Camp package is just a minor piece of the puzzle. The major pieces are the firmware updates, which add BIOS emulation (a.k.a. CSM, Compatibility Support Module) and also extend the boot manager to recognize volumes with BIOS boot code in the boot sector. Another piece is the 10.4.6 update which brings an updated "Startup Disk" preference pane, allowing you to set the Windows partition as the default boot partition. The Boot Camp Assistant just adds re-partitioning (i.e. shrinking the HFS+ partition in-place) and the drivers CD to the mix. The drivers are not used during installation at all, just the CSM code in the firmware. So, to answer your question, there is no special setup needed for the partition to show up in the built-in boot manager, just the new firmware. However, Startup Disk uses completely different values for the "efi-boot-device" NVRAM variable when you select OS X vs. Windows. Still investigating that... So long, chrisp - -- chrisp a.k.a. Christoph Pfisterer "Any sufficiently advanced cp...@ch... - http://chrisp.de bug is indistinguishable PGP key & geek code available from a feature." -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFENEgLr/EAHkwpC28RApfpAJ0chydxhheJyC3sFmQSCdvZ5hwkEgCfZhrE 5rrolN8HeOfKjGOO5mnwYWk= =w3fN -----END PGP SIGNATURE----- |
|
From: Jimmy K. <ji...@ka...> - 2006-04-05 22:21:51
|
On Wed, Apr 05, 2006 at 08:21:07PM +0100, Matthew Garrett wrote: > Unfortunately, while it's easy enough to boot a machine this way, it's > less obvious how we're going to boot an installed Linux afterwards. You > don't appear to be able to access EFI if you've booted in this way, so > the nvram can't be pointed at elilo or refit. Has anyone figured out how Apple sets up Windows XP to be bootable from the firmware graphical boot manager when installed via Boot Camp? This appears to be key, since if I understand the process correctly none of the drivers on the Macintosh Driver CD from Boot Camp are needed to make Windows boot (as it presumably does the first time after the WinXP installer completes). - Jimmy Kaplowitz ji...@ka... |
|
From: Roberto G. <gri...@gm...> - 2006-04-05 21:32:06
|
On may macbook pro, the caps lock button don't function anymoure, what abou= t this? |
|
From: Jimmy K. <ji...@ka...> - 2006-04-05 21:17:10
|
On Wed, Apr 05, 2006 at 04:41:56PM -0400, Erik Osheim wrote: > Ideally I would like to try to write a device driver for it so it > could be used with things like lirc. I have a partially working device driver that provides basic functionality with the Apple remote. I will post the patch as soon as I get some free time to write up an explanation, hopefully over the weekend if not sooner. I could definitely use help getting the remaining features of the remote to function under Linux. - Jimmy Kaplowitz ji...@ka... |
|
From: Erik O. <er...@pl...> - 2006-04-05 20:42:18
|
Hi, Does anyone know anything about the IR receiver on the mac mini? I haven't found a good program under OS X to try to spy on the bus and see what kind of data it sends/receives under OS X. I managed to query a bunch of information from /proc and /sys, which told me which device it was, but I didn't get any hints as to how to send or receive data to or from it? Does anyone have any ideas on how to proceed? Under Windows, it looks like people use a program called USB Snoopy to see what is going on, but I'm not sure about Linux/Mac. I expect that once you activate the receiver you can just sit and listen to output from it, but based on its power settings I think you do have to turn it on somehow. In OS X unloading the kernel module seems to turn it off. I tried using USB Probe as well as HID Explorer under OS X but couldn't get any information on how it operated. Ideally I would like to try to write a device driver for it so it could be used with things like lirc. -- Erik |
|
From: Matthew G. <mj...@sr...> - 2006-04-05 19:21:44
|
Unfortunately, while it's easy enough to boot a machine this way, it's less obvious how we're going to boot an installed Linux afterwards. You don't appear to be able to access EFI if you've booted in this way, so the nvram can't be pointed at elilo or refit. -- Matthew Garrett | mj...@sr... |
|
From: Michael S. <mi...@c6...> - 2006-04-05 18:50:59
|
Cool, yeah, the firmware update really seems to come with a CSM. I inserted the OpenSuSE 10.0 install CD, and it booted! Now Linux must respect GPT... Michael On Apr 5, 2006, at 8:40 PM, Toshimitsu Tanaka wrote: > Hi, > > I updated the firmware of iMac. > Maybe, it contains CFM. > KNOPPIX works. > > http://toshi3.cocolog-nifty.com/.shared/image.html?/photos/ > uncategorized/img_0103.jpg > > On 2006/04/06, at 3:11, Thomas Glanzmann wrote: >> Hello, >> as someone tried the Mac Mini Firmware Update which comes with a BIOS >> emulation? > -- > Toshimitsu Tanaka > t_t...@db... > http://toshi3.cocolog-nifty.com/blog/ > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting > language > that extends applications into web and mobile media. Attend the > live webcast > and join the prime developer group breaking into this new coding > territory! > http://sel.as-us.falkag.net/sel? > cmd=lnk&kid=110944&bid=241720&dat=121642 > _______________________________________________ > Mactel-linux-devel mailing list > Mac...@li... > https://lists.sourceforge.net/lists/listinfo/mactel-linux-devel |
|
From: Toshimitsu T. <t_t...@db...> - 2006-04-05 18:40:26
|
Hi, I updated the firmware of iMac. Maybe, it contains CFM. KNOPPIX works. http://toshi3.cocolog-nifty.com/.shared/image.html?/photos/ uncategorized/img_0103.jpg On 2006/04/06, at 3:11, Thomas Glanzmann wrote: > Hello, > as someone tried the Mac Mini Firmware Update which comes with a BIOS > emulation? -- Toshimitsu Tanaka t_t...@db... http://toshi3.cocolog-nifty.com/blog/ |
|
From: Thomas G. <sit...@st...> - 2006-04-05 18:12:11
|
Hello, as someone tried the Mac Mini Firmware Update which comes with a BIOS emulation? http://www.apple.com/support/downloads/macminiintelfirmwareupdate10.html http://wsidecar.apple.com/cgi-bin/nph-reg3rdpty1.pl/product=10072&cat=1&platform=osx&method=sa/MacMiniFirmwareUpdater.dmg I will give it a try as soon as I gets hands on my mac mini tomorrow morning. Hopefully it comes with an VGA Bios as well maybe X works accelerated with that one, too? Thomas |
|
From: <rfl...@la...> - 2006-04-04 20:53:16
|
Hi, In my mac mini I have : - 1 output - 1 input - 1 internal speaker The 2 jacks are just on top of usb ports. The strange thing is that if I=20 plug something on the *input* I can hear sound (that's why I thought it=20 was an output...) I use madwifi-ng-r1486-20060329. R=E9mi. Erik Osheim wrote: >Thanks for responding! > >I have a couple of questions for you: > >1. I only see one headphone jack... is that the analog or digital one? >Or, do you mean that you have digital speakers that work, but the >analog ones don't? > >2. Which version of the madwifi driver are you using? The version I am >using is listed as something like: 0.1443.20060207 (which I think >means the version released on Feb. 7th, 2006). > >Thanks, > >-- Erik > >On Sun, Apr 02, 2006 at 10:16:36PM +0200, R?mi Flament wrote: > =20 > >>1. On my mac mini the sound is "half-working" : I have to use headphone= s=20 >>on the digital output. >>Headphones on the analog output doesn't work, and the internal speaker=20 >>doesn't work either. I guess internal speaker =3D analog so it means on= ly=20 >>the digital output works. It's strange because I see digital and analg=20 >>outputs in alsa... >> >>2. I am currently connected to an AP with the madwifi drivers for the=20 >>atheros airport card, but I use wep, not wpa. >> >> >> >>Erik Osheim wrote: >> >> =20 >> >>>On Sun, Apr 02, 2006 at 02:15:21AM +0200, gimli wrote: >>> >>> >>> =20 >>> >>>>A new patch is prepared. The framebuffer starts at a slightly differe= nt=20 >>>>pos. >>>> =20 >>>> >>>> =20 >>>> >>>Great! Please let us know when it can be downloaded! >>> >>> >>> >>> =20 >>> >>>>When you make a kernel compile with "make -j5" you see the cpus start= =20 >>>>doing their work ;) >>>> =20 >>>> >>>> =20 >>>> >>>Yeah, I figured out that this was the cpufreq governer that the live >>>CD was using ;) >>> >>>Here are two other questions for anyone with a mini: >>> >>>1. Have you gotten sound working? I have compiled ALSA and seem to get >>>a PCM control, but it doesn't seem to affect either the internal >>>speaker or the headphone jack. My device nodes exist, but nothing >>>happens if I write to them. >>> >>>2. Have you actually connected to an AP with the madwifi drivers for >>>the Atheros based Airport Extreme card? I built the madwifi drivers >>>and got ath0 to show up. I was using wpa_supplicant and was able to >>>see my AP, but for some reason couldn't connect. >>> >>>Anyway, I may just be doing something stupid, especially in the 2nd >>>case (both wpa_supplicant and madwifi are under heavy development so I >>>may just have a bad version or be doing something wrong). >>> >>>Regards, >>> >>>-- Erik >>> >>> >>>------------------------------------------------------- >>>This SF.Net email is sponsored by xPML, a groundbreaking scripting lan= guage >>>that extends applications into web and mobile media. Attend the live=20 >>>webcast >>>and join the prime developer group breaking into this new coding terri= tory! >>>http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D110944&bid=3D241720&da= t=3D121642 >>>_______________________________________________ >>>Mactel-linux-devel mailing list >>>Mac...@li... >>>https://lists.sourceforge.net/lists/listinfo/mactel-linux-devel >>> >>> >>> =20 >>> |
|
From: David B. <ma...@da...> - 2006-04-04 18:05:43
|
On Tue, Apr 04, 2006 at 09:34:28AM -0700, David Brown wrote: > I'm getting a kernel oops in efi_set_rtc_mmss(). It is very easy to > reproduce, I just start 'ntpd' and after about 10 seconds I get the oops. > > I'm not sure how to capture the oops trace, short of moving another > computer over next to it, and typing in the oops message. > > I've seen this with both 2.6.16 and 2.6.16.1. It happens on my dual-core > mini. The crash does not happen if I boot with 'maxcpus=1'. Correction, it does happen with maxcpus=1. Dave |
71 messages has been excluded from this view by a project administrator.
