Re: Re: MOL not working on Lenny - tun0 problem
Hi Gaudenz:
Thanks for replying. I recognize your name on some previous
communication about problems in MOL in Debian Lenny so I'm hoping you
can help. I was attempting to start up a MacOS 9.2.1 disk, although I
also tried to start up a disk image that had been successfully created
with MOL running on openSUSE 11.0 ppc and was copied to my Debian Lenny
installation. In both cases, the result was the same. Here is the full
output:
debian:/home/mfox# startmol
Mac-on-Linux 0.9.73-SVN [Aug 8 2008 16:45]
Copyright (C) 1997-2004 Samuel Rydh
Starting MOL session 0
Loading Mac-on-Linux kernel module:
insmod /lib/modules/2.6.26-1-powerpc/extra/mol/mol.ko
Creating the /dev/sheep_net device node.
Loading SheepNet kernel module:
insmod /lib/modules/2.6.26-1-powerpc/extra/mol/sheep.ko
Loading tun driver kernel module:
insmod /lib/modules/2.6.26-1-powerpc/kernel/drivers/net/tun.ko
Running in PowerPC 7400 mode, 256 MB RAM
Timebase: 18.43 MHz, Bus: 166.40 MHz, Clock: 1333 MHz
Using USB mouse on /dev/input/mice
OHCI USB controller registered
No protocol specified
Could not connect to X server :0.0
Fullscreen video on VT 8.
Could not open '/var/lib/mol/console.kbd'
Cache enabled for console-video
Video driver(s): [console_video]
1024* 768, depth 8,15,32 { 60.0, 70.0, 75.0 } Hz
1280* 854, depth 8,15,32 { 0.0, 60.0 } Hz
No video mode match the default one.
Autoswitching to console
---> The network interface 'eth0' is not configured!
Failed to initialize the sheep- device
DHCP nameserver exported: 192.168.1.1
Ethernet Interface (port 1) 'tun-' @ 00:00:0D:EA:DB:EE
ip/mask: 192.168.40.2/255.255.255.0 gw: 192.168.40.1
broadcast: 192.168.40.255 nameserver: 192.168.40.1
ALSA sound driver loaded (device 'default')
Available Disks:
CD /dev/cdrom CD/DVD --
HFS /home/mfox/os... OS9-MOL 1024 MB BOOT
HFS /dev/hda2 Untitled 128 MB
Unembedded HFS+ /dev/hda3 40852 MB
Unembedded HFS+ /dev/hda5 7296 MB
> /dev/hda7 might be a boot-strap partition.
--> /dev/hda9 is linux-mounted with write privileges.
Could not open '/dev/hda9' with read-write permissions
HFS /dev/hda11 Untitled 128 MB
> (disk_open) Device /dev/hda13 is zero length, refusing to use it.:
Bad file descriptor
> (disk_open) Device /dev/hda14 is zero length, refusing to use it.:
Bad file descriptor
> (disk_open) Device /dev/hda15 is zero length, refusing to use it.:
Bad file descriptor
> /dev/hda16 might be a boot-strap partition.
> (disk_open) Device /dev/hda17 is zero length, refusing to use it.:
Bad file descriptor
> (disk_open) Device /dev/hda18 is zero length, refusing to use it.:
Bad file descriptor
> (disk_open) Device /dev/hda19 is zero length, refusing to use it.:
Bad file descriptor
> (disk_open) Device /dev/hda20 is zero length, refusing to use it.:
Bad file descriptor
> (disk_open) Device /dev/hda21 is zero length, refusing to use it.:
Bad file descriptor
> (disk_open) Device /dev/hda22 is zero length, refusing to use it.:
Bad file descriptor
> (disk_open) Device /dev/hda23 is zero length, refusing to use it.:
Bad file descriptor
> (disk_open) Device /dev/hda24 is zero length, refusing to use it.:
Bad file descriptor
> (disk_open) Device /dev/hda25 is zero length, refusing to use it.:
Bad file descriptor
> (disk_open) Device /dev/hda26 is zero length, refusing to use it.:
Bad file descriptor
> (disk_open) Device /dev/hda27 is zero length, refusing to use it.:
Bad file descriptor
> (disk_open) Device /dev/hda28 is zero length, refusing to use it.:
Bad file descriptor
> (disk_open) Device /dev/hda29 is zero length, refusing to use it.:
Bad file descriptor
> (disk_open) Device /dev/hda30 is zero length, refusing to use it.:
Bad file descriptor
> (disk_open) Device /dev/hda31 is zero length, refusing to use it.:
Bad file descriptor
> (disk_open) Device /dev/hdb1 is zero length, refusing to use it.:
Bad file descriptor
> (disk_open) Device /dev/hdb2 is zero length, refusing to use it.:
Bad file descriptor
> (disk_open) Device /dev/hdb3 is zero length, refusing to use it.:
Bad file descriptor
> (disk_open) Device /dev/hdb4 is zero length, refusing to use it.:
Bad file descriptor
> (disk_open) Device /dev/hdb5 is zero length, refusing to use it.:
Bad file descriptor
> (disk_open) Device /dev/hdb6 is zero length, refusing to use it.:
Bad file descriptor
> (disk_open) Device /dev/hdb7 is zero length, refusing to use it.:
Bad file descriptor
> (disk_open) Device /dev/hdb8 is zero length, refusing to use it.:
Bad file descriptor
> (disk_open) Device /dev/hdb9 is zero length, refusing to use it.:
Bad file descriptor
> (disk_open) Device /dev/hdb10 is zero length, refusing to use it.:
Bad file descriptor
> (disk_open) Device /dev/hdb11 is zero length, refusing to use it.:
Bad file descriptor
Re: MOL not working on Lenny - tun0 problem
Hi Michael On Mon, Sep 22, 2008 at 12:33:10PM -0400, Michael Fox wrote: > I am trying to run the program Mac-on-Linux on Lenny running on my > PowerBook G4/1.33 and when I type in the startup command on a terminal, I > get the following. (I added the boldface to direct this question.) > > Starting MOL session 0 > Loading Mac-on-Linux kernel module: > insmod /lib/modules/2.6.26-1-powerpc/extra/mol/mol.ko > Creating the /dev/sheep_net device node. > Loading SheepNet kernel module: > insmod /lib/modules/2.6.26-1-powerpc/extra/mol/sheep.ko > Loading tun driver kernel module: > insmod /lib/modules/2.6.26-1-powerpc/kernel/drivers/net/tun.ko This indicates that the tun driver is loaded correctly. > Running in PowerPC 7400 mode, 256 MB RAM > ... Can you please post the complete log of your MOL run. > Message from [EMAIL PROTECTED] at Sep 21 22:31:57 ... > kernel:[ 603.624807] unregister_netdevice: waiting for tun0 to become > free. Usage count = 3 I've also seen this messages, but they seemd mostly harmless. At least it did not stop MOL from working for me. > Terminating threads... > DONE This is strange. MOL seems to just shut down. This should not happen unless MacOS terminates. Wheter the networking is setup correctly or not should not matter. MOL can run without networking. > > I never see a MOL startup screen outside of the Terminal except for a > very brief moment. It disappears almost immediately, reverting to > "waiting for tun0" command line messages and then back to the Terminal > where I copied this text from. I suspect that the problem is with tun0, > but I don't know anything about this or what it's doing. I didn't set up > a tun0, at least not consciously. Can anyone tell me what is going on > and how I can fix this? Which version of MacOS do you try to boot? MOL does currently only support MacOS up to 10.4.x. Can you also try to run 'ifconfig -a' and 'iptables -t nat -L -v' while MOL is running. This tells you if the networking is setup correctly. If you have problems interpreting the output just post it to the list. Gaudenz -- Ever tried. Ever failed. No matter. Try again. Fail again. Fail better. ~ Samuel Beckett ~ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
MOL not working on Lenny - tun0 problem
I am trying to run the program Mac-on-Linux on Lenny running on my PowerBook G4/1.33 and when I type in the startup command on a terminal, I get the following. (I added the boldface to direct this question.) Starting MOL session 0 Loading Mac-on-Linux kernel module: insmod /lib/modules/2.6.26-1-powerpc/extra/mol/mol.ko Creating the /dev/sheep_net device node. Loading SheepNet kernel module: insmod /lib/modules/2.6.26-1-powerpc/extra/mol/sheep.ko Loading tun driver kernel module: insmod /lib/modules/2.6.26-1-powerpc/kernel/drivers/net/tun.ko Running in PowerPC 7400 mode, 256 MB RAM ... Message from [EMAIL PROTECTED] at Sep 21 22:31:57 ... kernel:[ 603.624807] unregister_netdevice: waiting for tun0 to become free. Usage count = 3 Terminating threads... DONE I never see a MOL startup screen outside of the Terminal except for a very brief moment. It disappears almost immediately, reverting to "waiting for tun0" command line messages and then back to the Terminal where I copied this text from. I suspect that the problem is with tun0, but I don't know anything about this or what it's doing. I didn't set up a tun0, at least not consciously. Can anyone tell me what is going on and how I can fix this?
Re: ndiswrapper fails to build
Em Mon, 22 Sep 2008 10:18:29 +0200 Gaudenz Steinlin <[EMAIL PROTECTED]> escreveu: [...] > > If I'm not completely mistaken the clamshell iBook has an original > Airport card (not Airport Extreme). This card is supported by the > airport kernel module. > The one I am using doesn't have an AirportCard. I guess I could find one to stick in it. > b43 is for the Airport Extreme cards based on the Broadcom chipset. > > Gaudenz > Thanks, Gunther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ndiswrapper fails to build
Em Mon, 22 Sep 2008 03:12:05 +0200 benoar <[EMAIL PROTECTED]> escreveu: > On Sun, 21 Sep 2008 21:35:34 -0300, Gunther Furtado > <[EMAIL PROTECTED]> wrote: > > Hi, > > > > I've been trying to build ndiswrapper using module-assistant with no > > success. > > > > The machine is an clamshell iBook 300Mhz running debian lenny > > official kernel. > > > > Any hints? > > ndiswrapper can't work on ppc machines because the windows wifi > drivers are not emulated but are directly run on the processor, which > is impossible here as they are made for the x86 architecture. > Why do you want to use ndiswrapper ? Sorry! I assumed it would work because it was available for powerpc[1]. Is that for crosscompiling purposes? > What wifi chip are you using ? > If it's for the broadcom included in most macintoshes, the b43 driver > will do. This particular iBook doesn't have an airport card. This is what dmesg tells me about the stick i am trying to put to work: usb 1-1.2: new full speed USB device using ohci_hcd and address 7 usb 1-1.2: configuration #1 chosen from 1 choice usb 1-1.2: New USB device found, idVendor=1286, idProduct=1fab usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 1-1.2: Product: 54M USB Wireless NIC usb 1-1.2: Manufacturer: Tenda.. It worked perfectly on an Athlon machine (ndiswrapper way). Is there any hope for me? > benjamin > [1] http://packages.debian.org/lenny/ndiswrapper-source Thanks, --- Gunther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ndiswrapper fails to build
On Mon, Sep 22, 2008 at 03:12:05AM +0200, benoar wrote: > On Sun, 21 Sep 2008 21:35:34 -0300, Gunther Furtado <[EMAIL PROTECTED]> > wrote: > > Hi, > > > > I've been trying to build ndiswrapper using module-assistant with no > > success. > > > > The machine is an clamshell iBook 300Mhz running debian lenny official > > kernel. > > > > Any hints? > > ndiswrapper can't work on ppc machines because the windows wifi drivers are > not emulated but are directly run on the processor, which is impossible > here as they are made for the x86 architecture. > Why do you want to use ndiswrapper ? What wifi chip are you using ? If it's > for the broadcom included in most macintoshes, the b43 driver will do. If I'm not completely mistaken the clamshell iBook has an original Airport card (not Airport Extreme). This card is supported by the airport kernel module. b43 is for the Airport Extreme cards based on the Broadcom chipset. Gaudenz -- Ever tried. Ever failed. No matter. Try again. Fail again. Fail better. ~ Samuel Beckett ~ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
