Hyperion Entertainment Message Boards

Posted: **Mon Oct 28, 2013 2:28 pm**

I know it might be because of the third party program but here goes.

I get a reproduceable crash on bootup with AddNetInterface.

To reproduce do the following.

1) Install DiskLED.docky from the depot
2) Open up the DiskLED.docky icon file with "Information"
3) Switch to the "Icon" tab
4) Add to the tooltypes:

Code: Select all

DEVICE=rtl8139.device,0

5) Save
6) Add the docky to AmiDock (the Device is known and gets a light)
7) Reboot and crash

Crashlog...

Hidden Text - Click to Show :

Not sure what the problem is here, but i might think it's a forbidden(?) or too early access to the device?

Posted: **Mon Oct 28, 2013 4:05 pm**

Looks like a possible bug in rtl8139.device to me.

Posted: **Mon Oct 28, 2013 10:31 pm**

I do wonder if it's the same bug that causes a GR for me every so often with the 8139.device. I did roll the kernel back to v53.57 a few days ago & no GRs since.

Raziel, I can't duplicate your crash, could you roll the kernel back to v53.57 & test, if your crash stops, I can file a BZ.

Posted: **Tue Oct 29, 2013 11:30 am**

sundown wrote:I do wonder if it's the same bug that causes a GR for me every so often with the 8139.device. I did roll the kernel back to v53.57 a few days ago & no GRs since.

Raziel, I can't duplicate your crash, could you roll the kernel back to v53.57 & test, if your crash stops, I can file a BZ.

I am unfortunately not able to roll back to 53.57, i only have 53.39 available (and with this kernel i don't even get any net access)

Posted: **Tue Oct 29, 2013 4:22 pm**

I tried the DiskLED docky with ONLY the rtl8139 active and nothing internet related works, including Prefs., but no crash. All latest updates installed.

Posted: **Wed Oct 30, 2013 3:26 am**

Raziel wrote:I know it might be because of the third party program but here goes.

I get a reproduceable crash on bootup with AddNetInterface.

To reproduce do the following.

Add to the tooltype:
DEVICE=rtl8139.device,0

If you look closely there is a coma between device & 0 instead of a period. If I put a coma there, I get the error you describe, no working internet & a lockup. I'm hoping its just that simple.

Even so, the docky shows no internet activity at all, only HD activity. I suspect this is a docky bug & not a system bug.

Posted: **Wed Oct 30, 2013 9:55 am**

Why would you want the ",0" after the device name, anyway? The Ethernet device does not have multiple Units.

What happens if you simply say "DEVICE=rtl8139.device" ?

Posted: **Wed Oct 30, 2013 11:42 am**

@sundown

If you look closely there is a coma between device & 0 instead of a period. If I put a coma there, I get the error you describe, no working internet & a lockup. I'm hoping its just that simple.

Even so, the docky shows no internet activity at all, only HD activity. I suspect this is a docky bug & not a system bug.

See the manual below, it shouldn't work with a period, it clearly says there needs to be a comma.

edit: and it doesn't work for me when using a period, it ignores that tooltype.
What you are seeing is probably a second hdd entry?

A SANA device access is actually YELLOW

52.3 (11.7.2007)
- Added support for SERIAL and PARALLEL devices, the colours are now
trackdisk: green = read, red = write
sana2: yellow
serial: blue
parallel: white
- If less than 9 devices are monitored the displayed LEDs are centered.

@tonyw

Why would you want the ",0" after the device name, anyway? The Ethernet device does not have multiple Units.

What happens if you simply say "DEVICE=rtl8139.device" ?

Because that is how the docky is designed to work.
And if the ethernet device doesn't have multiple units why am i able to change the unit number in internet prefs?

I am not very firm with the internals of devices, i simply read the readme and thought, hey lets try out the ethernet device

If i leave out the ",0" nothing happens, no device is added, the doky simply reads over the tooltype without processing it

A docky which displays the usage of up to 12 drives, as well as other
devices.
Can be used as HD LED replacement if you are using several controllers
but only have a single HD LED in your case, or you computer is located
somewhere where you can't see the LED. It is using different colours
for reading and writing, displays seperate LEDs for each drive, and it
delays disabling them with the usual delay filesystems use, i.e. unlike
real HD LEDs it's safe to reboot or switch off the computer when they
are off.

ToolTypes:
DEVICE=name,unit
You can use up to 12 DEVICE tooltypes to configure the device(s) which
should be monitored. Actually you can add more DEVICE tooltypes, up to
the first 12 devices/units which can be opened will be monitored and
displayed in the order top->down, left->right in the docky.
Currently only TRACKDISK, SANA2, SERIAL and PARALLEL devices are
supported.

Posted: **Thu Oct 31, 2013 3:36 pm**

Here is my TOOLTYPE and it works flawlessly :

DEVICE=a1ide.device,0
DEVICE=sii3114ide.device,1
DEVICE=eth3com.device,0

Posted: **Thu Oct 31, 2013 4:26 pm**

Raziel wrote:if the ethernet device doesn't have multiple units why am i able to change the unit number in internet prefs?

An ethernet driver can have multiple units. If you have multiple NICs of the same type in your system, each is driven by a different unit of the same driver.

Hyperion Entertainment Message Boards

AddNetInterface crash

AddNetInterface crash

Re: AddNetInterface crash

Re: AddNetInterface crash

Re: AddNetInterface crash

Re: AddNetInterface crash

Re: AddNetInterface crash

Re: AddNetInterface crash

Re: AddNetInterface crash

Re: AddNetInterface crash

Re: AddNetInterface crash